Your SlideShare is downloading. ×
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
simemense KPI
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

simemense KPI

1,064

Published on

zc

zc

Published in: Education
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,064
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
172
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SiemensInformationSystemPM: SBS Key Performance Indicators (optional issue)A30808-X3247-M47-1-7618Date : 06.10.2005Release : BR8.0
  • 2. Information PM: SBS Key Performance IndicatorsSystemContents 1 INTRODUCTION ............................................................................................................................................. 5 1.1 Purpose.............................................................................................................................................. 5 1.2 Reference Documents ........................................................................................................................ 5 1.3 Issue History...................................................................................................................................... 5 1.4 Definition of Terms............................................................................................................................ 6 2 IMMEDIATE ASSIGNMENT ANALYSIS............................................................................................................ 9 2.1 Number of Immediate Assignment Attempts .................................................................................... 11 2.2 Number of Immediate Assignment Losses ....................................................................................... 11 2.3 Number of Immediate Assignments by BSC procedure ................................................................... 12 2.4 Number of AGCH Losses................................................................................................................. 13 2.5 Number of Immediate Assignment Commands sent to MS via AGCH............................................. 13 2.6 Number of Immediate Assignments without MS Seizure.................................................................. 14 2.7 Number of successful Immediate Assignments ................................................................................ 14 2.8 Immediate Assignment Loss Rate .................................................................................................... 15 2.9 AGCH Loss Rate.............................................................................................................................. 15 2.10 Immediate Assignment without MS Seizure Rate............................................................................. 16 2.11 Immediate Assignment Success Rate ............................................................................................... 16 3 SSS PROCEDURES ANALYSIS ..................................................................................................................... 17 3.1 Number of successful Immediate Assignments related to Call Setups............................................. 19 3.2 Number of Dropped SDCCH Connections related to Call Setups................................................... 20 3.3 Number of SSS Procedure Failures related to Call Setups ............................................................. 20 3.4 SDCCH Drop Rate related to Call Setups....................................................................................... 21 3.5 SSS Procedures Failure Rate related to Call Setups ....................................................................... 21 3.6 SSS Procedures Success Rate related to Call Setups....................................................................... 22 4 ASSIGNMENT ANALYSIS ............................................................................................................................. 23 4.1 Number of Assignment Attempts...................................................................................................... 25 4.2 Number of Assignment Failures ...................................................................................................... 26 4.3 Number of successful Assignments .................................................................................................. 27 4.4 Assignment Failure Rate ................................................................................................................. 28 4.5 Assignment Success Rate ................................................................................................................. 29 4.6 Assignment success rate when radio resources available ............................................................... 29 5 CALL SETUP ANALYSIS .............................................................................................................................. 30 5.1 Number of Call Setup Attempts........................................................................................................ 31 5.2 Number of Successful Call Setups ................................................................................................... 31 5.3 Call Setup Success Rate................................................................................................................... 32 5.4 Number of Call Setup Failures ........................................................................................................ 32 5.5 Call Setup Failure Rate ................................................................................................................... 34 6 TCH DROP RELATED PERFORMANCE INDICATORS ..................................................................................... 35 6.1 Number of Dropped TCH Connections ........................................................................................... 35 6.2 TCH Drop Distribution ................................................................................................................... 36 6.3 TCH Drop Rate................................................................................................................................ 39 6.4 Call Drop Rate ................................................................................................................................ 40 6.5 Mean Time between TCH Drop....................................................................................................... 42 6.6 TCH Drops per Erlanghour............................................................................................................. 42 7 SDCCH DROP RELATED PERFORMANCE INDICATORS ............................................................................... 43 7.1 Number of dropped SDCCH Connections ....................................................................................... 43 7.2 SDCCH Drop Rate .......................................................................................................................... 43 7.3 Mean Time between SDCCH Drop.................................................................................................. 44 7.4 SDCCH Drops per Erlanghour ....................................................................................................... 44 8 TCH LOAD RELATED PERFORMANCE INDICATORS .................................................................................... 45 8.1 TCH Load for Circuit Switched Traffic ........................................................................................... 45 8.2 Combined time slot utilisation for CS and PO Traffic..................................................................... 54 9 SDCCH LOAD RELATED PERFORMANCE INDICATORS ............................................................................... 56 9.1 SDCCH Traffic Offered ................................................................................................................... 56 9.2 SDCCH Traffic Carried................................................................................................................... 57 9.3 SDCCH Traffic Lost ........................................................................................................................ 57 9.4 SDCCH Blocking Rate..................................................................................................................... 572 A30808-X3247-B912-1-7618
  • 3. Information PM: SBS Key Performance IndicatorsSystem 9.5 SDCCH Loss Rate ........................................................................................................................... 58 9.6 SDCCH Mean Holding Time ........................................................................................................... 58 9.7 SDCCH Traffic Utilisation .............................................................................................................. 59 10 CCCH LOAD RELATED PERFORMANCE INDICATORS ............................................................................ 60 10.1 PCH load of downlink CCCH channels .......................................................................................... 62 10.2 AGCH load of downlink CCCH channels........................................................................................ 62 10.3 CCCH load downlink....................................................................................................................... 63 10.4 CCCH load uplink ........................................................................................................................... 63 10.5 PCH Loss Rate ................................................................................................................................ 64 10.6 AGCH Loss Rate.............................................................................................................................. 64 10.7 Invalid RACH Rate .......................................................................................................................... 65 11 PCCH LOAD RELATED PERFORMANCE INDICATORS ............................................................................ 66 11.1 PPCH load of downlink PCCCH channels...................................................................................... 68 11.2 PAGCH load of downlink PCCCH channels................................................................................... 68 11.3 PCCCH load downlink .................................................................................................................... 69 11.4 PCCCH load uplink......................................................................................................................... 69 11.5 PPCH Loss Rate .............................................................................................................................. 70 11.6 PAGCH Loss Rate ........................................................................................................................... 70 11.7 Invalid PRACH Rate........................................................................................................................ 71 12 SERVICE RELATED PERFORMANCE INDICATORS ................................................................................... 72 12.1 Total number of Service Requests.................................................................................................... 72 12.2 Service Request Distribution Rate ................................................................................................... 72 12.3 Rate of Service Requests served in the highest layer ....................................................................... 73 13 FEATURE RELATED PERFORMANCE INDICATORS .................................................................................. 74 13.1 Abis pool supervision....................................................................................................................... 74 14 HANDOVER RELATED PERFORMANCE INDICATORS ............................................................................... 76 14.1 Intra Cell Handovers ....................................................................................................................... 76 14.2 Inter Cell Intra BSC Handovers ...................................................................................................... 82 14.3 Inter Cell Inter BSC Handovers ...................................................................................................... 90 14.4 Inter System Handover between GSM and UMTS ........................................................................... 96 14.5 Other Handover Performance Indicators...................................................................................... 101 15 POWER AND QUALITY MEASUREMENTS ............................................................................................. 107 15.1 Interference Band Rate on idle TCH ............................................................................................. 107 15.2 Quality Link for N% FER .............................................................................................................. 107 15.3 Mean FER UpLink......................................................................................................................... 107 15.4 Power and Quality limits for N% Percentile on busy TCH ........................................................... 109 15.5 Distribution of power control levels on busy TCH ........................................................................ 110 15.6 Mean Level and Quality on busy TCH........................................................................................... 111 15.7 TA Distribution.............................................................................................................................. 112 15.8 RXQUAL Distribution ................................................................................................................... 112 15.9 RXLEV Distribution....................................................................................................................... 113 15.10 FER Distribution ........................................................................................................................... 113 15.11 Mean FER UpLink per RXQUAL .................................................................................................. 114 15.12 Mean RXLEV per RXQUAL Band ................................................................................................. 115 15.13 Mean RXLEV per TA Band............................................................................................................ 116 15.14 High RXLEV with Low RXQUAL Rate .......................................................................................... 117 15.15 TCH Traffic Type Distribution ...................................................................................................... 118 15.16 SDCCH Traffic Type Distribution ................................................................................................. 119 15.17 Adaptive Multirate Distribution .................................................................................................... 120 15.18 Adaptive Multirate True Frame Erasure Rate............................................................................... 121 16 AVAILABILITY RELATED PERFORMANCE INDICATORS .......... FEHLER! TEXTMARKE NICHT DEFINIERT. 16.1 Transceiver Availability ................................................................................................................ 122 16.2 TCH Distribution Rate................................................................................................................... 122 16.3 TCH Availability............................................................................................................................ 122 16.4 SDCCH Availability ...................................................................................................................... 124 17 GPRS RELATED PERFORMANCE INDICATORS .................................................................................... 125 17.1 User oriented KPIs ........................................................................................................................ 125 17.2 Network planning (dimensioning) ................................................................................................. 140 17.3 Network optimization..................................................................................................................... 152 17.4 Cell Reselection ............................................................................................................................. 156 18 MISCELLANEOUS PERFORMANCE INDICATORS ................................................................................... 1603 A30808-X3247-B912-1-7618
  • 4. Information PM: SBS Key Performance IndicatorsSystem 18.1 BSC Processorload........................................................................................................................ 160 18.2 BTSE Processorload...................................................................................................................... 161 18.3 Paging Response / Location Update Ratio per Cell ...................................................................... 161 18.4 BSC <-> MSC/SMLC CCS7 Load................................................................................................. 162 19 BSS RELATED KPIS AT SIEMENS MSC............................................................................................... 163 20 APPENDIX ........................................................................................................................................... 164 20.1 List of BSS Performance Measurements........................................................................................ 1644 A30808-X3247-B912-1-7618
  • 5. Information PM: SBS Key Performance IndicatorsSystem1 Introduction1.1 PurposeThe purpose of this document is the definitions of SBS Key Performance Indicators,which can be used in a uniform way. It is possible to compare Key PerformanceIndicators of different networks or to give statements about Quality, Performance,Capacity and more.This document will describe the most important Key Performance Indicators relevantfor GSM Mobile Networks. All listed formulas are valid for one elementary object andfor one elementary measurement period. Evaluation of multiple objects and formultiple measurement periods can be done as described in chapter 1.4..This KPI document does not provide planning rules for network dimensioning. It onlyprovides input data used for planning tools.1.2 Reference DocumentsFurther information about Performance Measurements can be found in the followingdocuments:• PM:SBS Counters, A30808-X3247-M40-#• PM:SBS Message Flow, A30808-X3247-M41-#• Training Documentation 1736 : BSS Performance Measurement• 3GPP TS52.402 Telecommunication management; Performance Management (PM); Performance measurements - GSM1.3 Issue HistoryIssue Date of issue Reason for of issueVersionBR8.0 AFI0.1 23.6.2005 First version for new release 8.0BR8.0 AFI0.2 11.8.2005 Second version for new release 8.0 - Modifications related to review comments - New KPIs added in chapter 10 and 13BR8.0 IUS 1.0 06.10.2005 SDCA KPI’s added, chapter 125 A30808-X3247-B912-1-7618
  • 6. Information PM: SBS Key Performance IndicatorsSystem1.4 Definition of TermsLong nameThis is the full name of the described key performance indicator (KPI).Short nameThis is an abbreviation of the described key performance indicator.DescriptionThe description will give you a short explanation of the described key performanceindicator.FormulaThe formula will deliver the exact calculation of the described key performanceindicator. The formula is related to one elementary object and to one elementaryperiod. Multiple objects and multiple elementary periods can be added as describedunder ‘Evaluation of multiple objects for multiple elementary periods‘.Used parameterHere you can find either the SBS short identification of the used SBS performancemeasurement counters or the short name of the used key performance indicators.The related long names of SBS performance measurement counters you can find inthe appendix under ‘List of Performance Measurements‘. The SBS short identificationis a combination of measurement type and sub-counter. A measurement type canhave several sub-counters. Therefore the used sub-counters are listed in bracketswith following meaning:• [1] sub-counter 1 has to be taken.• [1,2,4] sub-counters 1, 2 and 4 have to be added.• [1..4] sub-counters 1, 2, 3 and 4 have to be added.• [1..4, 7..10] sub-counters 1, 2, 3, 4, 7, 8, 9 and 10 have to be added.• [all] all sub-counters have to be added.It is also possible that key performance indicators can have sub-indicators. In thiscase they are also listed in brackets.6 A30808-X3247-B912-1-7618
  • 7. Information PM: SBS Key Performance IndicatorsSystemElementary objectThis 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”RemarkHere you will find additional important information for the key performance indicator.AggregationThe aggregation field will show you how to evaluate the KPI for multiple objects andfor multiple elementary periods. There are:• Daily aggregation: for every KPI we can calculate: - MAX/min value: the KPI value for the granularity period of one day is recorded. These values are processed to find the peak value, maximum (MAX) or the minimum value (min); - MAX/min Time provides the starting time of the granularity period of the peak value (MAX and min); - Mean/Sum daily value represents the mean/sum of the counter value, used in KPI’s formula, collected for the granularity period; it is the aggregation standard1 . - SPBH (Sample at Peak Busy Hour2) is the value of the KPI at reference BH and is calculated only in the busy hour; - SPBH Time provides the starting time of the hour of SPBH;• Several days aggregation: - MAX/MIN value: all the KPI values recorded for each granularity period for each day are processed to find the highest value (MAX) or the minimum value (min); - MAX/MIN Time provides the starting time and date of the granularity period of the MAX/min value; - TCMAX/TCMIN (Time Coherent MAX/min): for a number of days, counter values for each granularity period for each day are recorded. The values for the same granularity period for each day are averaged, determining the average day. The counter value in the granularity period in this average day give the highest value (TCMAX) or the lower value (TCmin) is taken; - TCMAX/TCMIN Time provides the starting time related to TCMAX/TCmin value; - Mean/Sum value: all the counter values, used in KPI’s formula, recorded for granularity periods for each day are processed to find the mean/sum value, it is the aggregation standard (refer to note 1); - ASPBH (Average Sample at Peak Busy Hour): each day the sample at peak busy hour is recorded and then these values are averaged;7 A30808-X3247-B912-1-7618
  • 8. Information PM: SBS Key Performance IndicatorsSystem - 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 SPBHaggregation Function referring to BSC Processor Load measurement: - KPI(Aggregation Function[Reference variable]) - InterCellHOSuccRate(SPBH[BSCPRCLD[2]])1 Standard means that the evaluation can be done by adding or averaging thecounter values for single objects and single periods in the following way (standardaggregation):Counter (n, m) = ∑ Counter (i, t) i,t Counter (n, m) = Counter (i, t)i elementary objectt elementary periodn object (sum of elementary objects)m measurement period (sum of elementary periods)2 The busy hour is the hour in which the reference variable assumes the highestvalue within one day for a measured object for any performance indicator. When thegranularity period is smaller than 1 hour, this value is calculated with the slidingwindow algorithm.Not in any case it makes sense to evaluate the busy hour for each singleperformance indicator. It is also possible to make an assumption, that for Randomtraffic the busy hour for most different measurement objects will correlate. Thatmeans the busy hour is derived from a particular performance indicator and can beused for other performance indicators. E.g. the busy hour could be derived from theperformance indicator ‘BSC Processor load‘ and could than be used for all otherperformance indicators.8 A30808-X3247-B912-1-7618
  • 9. Information PM: SBS Key Performance IndicatorsSystem2 Immediate Assignment AnalysisThe 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 theevents related to Mobile Stations. The message flow of the Immediate AssignmentProcedure is listed below. The numbers in brackets will indicate available SBSperformance measurements.MS BTS BSC CHANNEL REQUEST [1] CHANNEL REQUIRED [2] SDCCH CONGESTIONS CHANNEL ACTIV CHANNEL ACTIV ACK CHANNEL ACTIV NACK IMM. ASS CMD [3] [4] [5] IMM. ASS IMM. ASS REJECT [5] DELETE INDICATION SABM UA [6] ESTABLISH INDIC.Fig. 1 Message flow: Immediate Assignment ProcedureSBS Counter[1] CHANNEL REQUIRED ATIMASCA [1..14][2] SDCCH CONGESTIONS ATSDCMBS [1] (Congestions due to SDCCH HO are also counted)[3] IMM. ASS CMD (Abis Interface) SUIMASCA [1..6] (IMM. ASS. CMD. messages, which contain an IMM. ASS. REJ. message are not counted)[4] IMM. ASS CMD (Abis Interface) TACCBPRO [2] (including those IMM. ASS. CMD. messages that contain an IMM. ASS. REJ. message)[5] IMM. ASS CMD / IMM. ASS. REJ. (Um Interface) NACSUCPR [2] (difference between IMM. ASS.CMD and Del. Ind., including those IMM. ASS. CMD. messages that contain an IMM. ASS. REJ. message)[6] ESTABLISH INDICATION NSUCCHPC [1..22]9 A30808-X3247-B912-1-7618
  • 10. Information PM: SBS Key Performance IndicatorsSystemThe following figure shows you the traffic flow. [1] Number of Immediate Assignment Attempts [3] Number of Imm Ass. by BSC procedure [2] Number of Immediate Assignment Losses [5] Imm Ass Command sent to MS via AGCH [4] Number of AGCH Losses [6] Number of Immediate Assignments [7] Number of successful without MS Seizure Immediate AssignmentsFig. 2 Traffic flow: Immediate Assignment ProcedureThis chapter contains the following ‘Number related’ KPIs:• Number of Immediate Assignment Attempts: [1]• Number of Immediate Assignment Losses : [2]= [1] – [3]• Number of Immediate Assignments by BSC procedure : [3] = [1] – [2])• Number of AGCH Losses: [4] = [9] * [3]• Number of Immediate Assignment Commands sent to MS via AGCH: [5] = [3] – [4] = (1- [9]) * [3]•• Number of Immediate Assignments without MS Seizure : [6] = [5] – [7] = [3] – [4] - [7]• Number of successful Immediate Assignments: [7]And the following ‘Rate related’ KPIs:• Immediate Assignment Loss Rate : [8] = [2] / [1]• AGCH Loss Rate: [9] = [4] / [3])• Immediate Assignment without MS Seizure Rate : [10] = [6] / [5]• Immediate Assignment Success Rate : [11] = [7] / ([1] – [6]) (Phantom RACHs are not counted, because they are not related to MS)The Immediate Assignment Failure Rate can be calculated as follows:Immediate Assignment Failure Rate = 1 - Immediate Assignment Success Rate orImmediate Assignment Failure Rate = Immediate Assignment Loss Rate * AGCH Loss Rate * Immediate Assignment without MS Seizure Rate10 A30808-X3247-B912-1-7618
  • 11. Information PM: SBS Key Performance IndicatorsSystem2.1 Number of Immediate Assignment AttemptsLong name: (a) Number of Immediate Assignment AttemptsShort name: (a) ImmAssAttDescription: These indicators will give you the number of started Immediate Assignment procedures from MS point of view by counting the number of Channel Required messages.Formula: (a) ImmAssAtt = ATIMASCA[1 ..14]Used param.: ATIMASCA[1..14]Elem. Object: CellUnit: NoneRemarks: Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and therefore a BTS Timer will expire. These unforeseen messages will also be counted. In BR 7.0 a note was added in counter ATIMASCA. This fact does not affect the meaning or definition of the KPI.2.2 Number of Immediate Assignment LossesLong name: (a) Number of Immediate Assignment LossesShort name: (a) ImmAssLossDescription: These indicators will give you the number of SDCCH/TCH request, which were rejected, because no SDCCH/TCH was available or because of BTS channel activation failures.Formula: (a) ImmAssLoss = ImmAssAtt - ImmAssBSCp rocUsed param.: ImmAssAtt (2.1(a)) , ImmAssBSCproc (2.3(a))Elem. Object: CellUnit: NoneRemarks: Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and therefore a BTS Timer will expire. These unforeseen messages will also be counted. In BR 7.0 a note was added in counters ATIMASCA(1,9) and SUIMASCA8(1,10). This fact does not affect the meaning or definition of the KPI.11 A30808-X3247-B912-1-7618
  • 12. Information PM: SBS Key Performance IndicatorsSystem2.3 Number of Immediate Assignments by BSC procedureLong name: (a) Number of Immediate Assignments by BSC internal procedureShort name: (a) ImmAssBSCprocDescription: These indicators will give you the number of successful Immediate Assignments of a channel by BSC internal procedure I. e. the indicator counts the cases when the Immediate Assignment Attempts (RACH) can be satisfied by an according idle channel.Formula: (a) ImmAssBSCp roc = SUIMASCA[1 ..6]Used param.: SUIMASCA[1..6]Elem. Object: CellUnit: NoneRemarks: Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and therefore a BTS Timer will expire. These unforeseen messages will also be counted.12 A30808-X3247-B912-1-7618
  • 13. Information PM: SBS Key Performance IndicatorsSystem2.4 Number of AGCH LossesLong name: (a) Number of AGCH lossesShort name: (a) AGCHLossDescription: These indicators will give you the number AGCH losses by meaning of not transmitted Immediate Assignment Command messages over the AGCH on the Air Interface. Reason for AGCH failures are mainly AGCH overload. This formula is related to MS point of view, by meaning each MS related immediate assignment procedure should be stepped once. Therefore events, where no SDCCH/TCH was available or BTS channel activation failured are counted in the formula ‘Number of Immediate Assignment Losses’. => Only Delete Indication messages related to Immediate Assignment Command messages not containing an Immediate Assignment reject messages will rightly be counted.Formula: (a) AGCHLoss = AGCHLossRate * ImmAssBSCprocUsed param.: AGCHLossRate (2.9(a)) ,ImmAssBSCproc (2.3(a))Elem. Object: CellUnit: NoneRemarks: 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.2.5 Number of Immediate Assignment Commands sent to MS via AGCHLong name: (a) Number of Immediate Assignments Commands sent to MS via AGCHShort name: (a) ImmAssCmdAGCHDescription: The KPI provides the number of Immediate Assignments Commands sent to MS via AGCHFormula: (a) ImmAssCmdAGCH = (1 − AGCHLossRate) * ImmAssBSCprocUsed param.: ImmAssBSCproc (2.3(a)), AGCHLossRate (2.9(a))Elem. Object: CellUnit: NoneRemarks: 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.13 A30808-X3247-B912-1-7618
  • 14. Information PM: SBS Key Performance IndicatorsSystem2.6 Number of Immediate Assignments without MS SeizureLong name: (a) Number of Immediate Assignments without MS SeizureShort name: (a) ImmAssNoSeizDescription: These indicators will give you the number of immediate assignments without seizure by MS. The main reasons for this behavior are Phantom RACHs, messages not foreseen for the observed cell. Other reasons are not received SABM messages due to air interface problems. This formula will count the difference between Immediate Assignment Command messages sent to the MS and the number of Establishment Indication messages. => not answered Immediate Assignment Commands.Formula: (a) ImmAssNoSe = ImmAssBSCp - AGCHLoss- ImmAssSucc iz rocUsed param.: ImmAssBSCproc (2.3(a)), AGCHLoss (2.4(a)), ImmAssSucc (2.7(a))Elem. Object: CellUnit: NoneRemarks: The formula will mainly detect Phantom RACHs. Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is started, but will not be successful, because no MS will reply with a SABM message. A BTS Timer will expire. In case of RACH repetitions (abnormal amount of time => Expiry of timer NSLOTST), it can happen that subsequent Immediate Assignment Commands will not receive a positive reply from the MS. Nevertheless from MS point of view the call setup was successful.2.7 Number of successful Immediate AssignmentsLong name: (a) Number of successful Immediate AssignmentsShort name: (a) ImmAssSuccDescription: These indicators will give you the number of successful Immediate Assignments from MS point of view. A Immediate Assignment procedure is successful if the BTS returns an establishment indication message on Abis.Formula: (a) ImmA ssSucc = NSUCCHPC[1 .. 6, 9 ..14, 17 .. 22]Used param.: NSUCCHPC[1 .. 6, 9 .. 14, 17 .. 22]Elem. Object: CellUnit: NoneRemarks: SMS related counters in NSUCCHPC have not to be considered in the KPI formula, because they are also included in other sub-counters of measurement NSUCCHPC.14 A30808-X3247-B912-1-7618
  • 15. Information PM: SBS Key Performance IndicatorsSystem2.8 Immediate Assignment Loss RateLong name: (a) Immediate Assignment Loss RateShort name: (a) ImmAssLossRateDescription: These indicators will give you the SDCCH/TCH Loss Rate, which were rejected, because no SDCCH/TCH was available or because of BTS channel activation failures.Formula: Im mAssLoss (a) ImmAssLossRate = Im mAssAttUsed param.: ImmAssAtt (2.1(a)), ImmAssLoss (2.2(a))Elem. Object: CellUnit: NoneRemarks: Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and therefore a BTS Timer will expire. These unforeseen messages will also be counted (in ImmAssAtt).2.9 AGCH Loss RateLong name: (a) AGCH Loss RateShort name: (a) AGCHLossRateDescription: These indicators will give you the AGCH Loss Rate by meaning of not transmitted Immediate Assignment Command messages over the AGCH on the Air Interface. Reason for AGCH failures are mainly AGCH overload. This formula is related to MS point of view, by meaning each MS related immediate assignment procedure should be stepped once. Therefore events, where no SDCCH/TCH was available or BTS channel activation failured are counted in the formula ‘Number of Immediate Assignment Losses’. => Only Delete Indication messages related to Immediate Assignment Command messages not containing an Immediate Assignment reject messages will rightly be considered.Formula: TACCBPRO[2] - NACSUCPR[2] (a) AGCHLossRate = TACCBPRO[2]Used param.: TACCBPRO [2], NACSUCPR [2]Elem. Object: CellUnit: NoneRemarks: Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and therefore a BTS Timer will expire. These unforeseen messages will also be counted.15 A30808-X3247-B912-1-7618
  • 16. Information PM: SBS Key Performance IndicatorsSystem2.10 Immediate Assignment without MS Seizure RateLong name: (a) Immediate Assignment without MS Seizure RateShort name: (a) ImmAssNoSeizRateDescription: These indicators will give you the immediate assignment without MS seizure rate . The main reasons for this behaviour are Phantom RACHs, messages not foreseen for the observed cell. Other reasons are not received SABM messages due to air interface problems. This formula will count number of not answered Immediate Assignment Command messages related to the Immediate Assignment Command messages sent to the MS.Formula: ImmAssNoSeiz (a) ImmAssNoSeizRate = ImmAssCmdAGCHUsed param.: ImmAssNoSeiz (0(a)), ImmAssCmdAGCH (2.5(a))Elem. Object: CellUnit: NoneRemarks: The formula will mainly detect Phantom RACHs. Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is started, but will not be successful, because no MS will reply with a SABM message. A BTS Timer will expire.2.11 Immediate Assignment Success RateLong name: (a) Immediate Assignment Success RateShort name: (a) ImmAssSuccRateDescription: These indicators will give you the immediate assignment success rate from MS point of view. A Immediate Assignment procedure is successful if the BTS returns an establishment indication message.Formula: ImmAssSucc (a) ImmAssSuccRate = Im mAssAtt − Im mAssNoSeizUsed param.: ImmAssAtt (2.1(a)), ImmAssSucc (2.7(a)), ImmAssNoSeiz (0(a))Elem. Object: CellUnit: NoneRemarks: Phantom RACHs are not included in this formula, because they are not related to MS of the observed cell. Um-Interface problems may lead to decoding errors of the Mobile’s L2 SABM- frame and therefore are not considered here.16 A30808-X3247-B912-1-7618
  • 17. Information PM: SBS Key Performance IndicatorsSystem3 SSS Procedures AnalysisThe KPIs of this section are mainly used for the derivation of the Call Setup SuccessRate (CSSR) and Call Setup Failure Rate (CSFR). The Key Performance Indicators(KPIs) are mostly related to the Mobile Station point of view, by meaning they willcount the events related to Mobile Stations. There exists the following SSSProcedures which used during Call Setup related to the parameter setting in theMSC: Identity Check (IMEI), Authentication (IMSI), Ciphering, Call Control: SetupMS BTS BSC MSC SABM [1] Establishment Ind. CR(Compl Layer3Info) CC Authentification Request Authentification Response Identity Request Identity Response Ciphering Command Ciphering Command Ciphering Complete Ciphering Complete Setup Call Proceeding [2] Assignment Req. Assignment CommandFig. 3 Message flow: SSS Procedures during Call Setup (MOC)SBS Counter[1] ESTABLISH INDICATION NSUCCHPC[1..4,9..12,17..20] – NSUCCHPC[8] (related to Call Setups)[2] ASSIGNMENT ATTEMPTS TASSATT [2..3]Sub-counters are listed in BracketsThe different number of failures and failure rates can be evaluated with SiemensMSC counter per MSC. All events are cell independent. Therefore it is sufficient tocalculate them for the elementary object MSC.It is also very important to evaluate the number of SDCCH drops during call setup.SDCCH drops mainly occur in the time when SSS Procedures are running. Thereforethey can be evaluated together with the SSS Procedure formulas. With SBSperformance measurement counter it is possible to calculate the SSS ProcedureSuccess and Failure Rate related to Call Setups.17 A30808-X3247-B912-1-7618
  • 18. Information PM: SBS Key Performance IndicatorsSystemThe following figure shows you the traffic flow. [1]Successful Immediate Assignments [2]SDCCH Drops [3] SSS Procedure failures [4] Assignment AttemptsFig. 4 Traffic flow: SSS Procedures during Call SetupSDCCH Drops can occur before SSS Procedure Failure and vice versa.This chapter contains the following ‘Number related’ KPIs:• Number of successful Immediate Assignments related to Call Setups: [1]• Number of Dropped SDCCH Connections related to Call Setups: [2]• Number of SSS Procedure Failures related to Call Setups: [3] = [1] - [4] - [2]And the following ‘Rate related’ KPIs:• SDCCH Drop Rate related to Call Setups = [2] / [1]• SSS Procedures Failure Rate related to Call Setups = [3] / [1]• SSS Procedures Failure Rate related to Call Setups = [4] / [1]Referenced KPI from chapter 4 Assignment Analysis• Number of Assignment Attempts: [4]18 A30808-X3247-B912-1-7618
  • 19. Information PM: SBS Key Performance IndicatorsSystem3.1 Number of successful Immediate Assignments related to Call SetupsLong name: (a) Number of successful Immediate Assignments related to Call SetupsShort name: (a) ImmAssSuccCSDescription: These indicators will give you the number of successful Immediate Assignments related to Call Setups. A Immediate Assignment procedure related to a Call Setup is successful if the BTS returns an establishment indication message related to Mobile Originated Calls (MOC), Mobile Terminated Calls (MTC), Emergency Calls or Call Reestablishment.Formula: (a) ImmAssSuccCS = NSUCCHPC[1 ..4,9..12,17..20]- NSUCCHPC[8 ]Used param.: NSUCCHPC[1..4, 8 ..12,17..20]Elem. Object: CellUnit: NoneRemarks: • Partly elimination of systematic error in formula by subtracting the SMS-MT related counter values NSUCCHPC[8] (SDCCH assigned for SMS-MT). The new SMS counters are triggered on arrival of Establish Confirm (SAPI 3) • Remark (background information) The counters NSUCCHPC [16,24] must not be subtracted since they mainly are triggered where an SMS MT arrives when the MS has an ongoing TCH call. In that case no immediate TCH assignment in connection with the SMS MT takes place at all and thus an elimination of SMSes in formula 3.1 by subtracting "- NSUCCHPC [16,24]" is not necessary. • Remaining systematic error: The formula has a small systematic error when "Direct TCH Assignment” is enabled. For that scenario the counters NSUCCHPC [16,24] might also be triggered when an SMT MT arrives for an idle MS, which requests an immediate TCH assignment as paging response. The number of these concurrencies has in principle to be subtracted in formula 3.1. But NSUCCHPC [16,24] does no distinguish between arrival of SMS MT for an idle MS and for an MS with ongoing TCH call (the call processing trigger point used for NSUCCHPC [16,24] has no knowledge about the history of the existing TCH assignment).19 A30808-X3247-B912-1-7618
  • 20. Information PM: SBS Key Performance IndicatorsSystem3.2 Number of Dropped SDCCH Connections related to Call SetupsLong name: (a) Number of Dropped SDCCH Connections related to Call SetupsShort name: (a) SDCCHDropCSDescription: This indicator will give you the number of dropped SDCCH connections related to Call Setups. SDCCH drops mainly occur during running SSS Procedures. This formula is related to the assumption that the number of dropped SDCCH connections is random distributed to all kind of assignment causes (MOC, MTC, Locupd, …). Therefore this formula contains a factor for the ratio of MOC and MTC to all kind of assignment causes to get the relation to Call Setups.Formula: ImmAssSuccCS (a) SDCCHDropCS = SDCCHDrop * ImmAssSuccUsed param.: SDCCHDrop(7.1(a)), ImmAssSucc (2.7(a)), ImmAssSuccCS (3.1(a))Elem. Object: CellUnit: NoneRemarks:3.3 Number of SSS Procedure Failures related to Call SetupsLong name: (a) Number of SSS Procedure Failures related to Call SetupsShort name: (a) SSSProcFailCSDescription: This indicator will give you the number of SSS Procedure failures related to Call Setups.Formula: (a) SSSProcFai lCS = ImmAssSuccCS - AssAtt - SDCCHDropC SUsed param.: ImmAssSuccCS (3.1(a), AssAtt (0(a)), SDCCHDropCS (3.2(a))Elem. Object: CellUnit: NoneRemarks: Please note that Authentication-, Identity-, Ciphering- and MSC failures are counted in this formula although they are not related to the BSS. User Release before assignment of a TCH is also included in this formula. Assignments of SDCCH are not considered.20 A30808-X3247-B912-1-7618
  • 21. Information PM: SBS Key Performance IndicatorsSystem3.4 SDCCH Drop Rate related to Call SetupsLong name: (a) SDCCH Drop Rate related to Call SetupsShort name: (a) SDCCHDropRateCSDescription: This indicator will give you the SDCCH Drop Rate related to Call Setups. SDCCH drops mainly occur during running SSS Procedures. This formula is related to the assumption that the number of dropped SDCCH connections is random distributed to all kind of assignment causes (MOC, MTC, Locupd, …). Therefore this formula is equal to the SDCCH Drop Rate.Formula: SDCCHDropC S (a) SDCCHDropR ateCS = ≈ SDCCHDropR ate Im mAssSuccCSUsed param.: SDCCHDropCS (3.2(a)), ImmAssSuccCS (3.1(a)), SDCCHDropRate (7.2(a))Elem. Object: CellUnit: NoneRemarks: SDCCH Handovers are not considered here.3.5 SSS Procedures Failure Rate related to Call SetupsLong name: (a) SSS Procedures Failure Rate related to Call SetupsShort name: (a) SSSProcFailRateCSDescription: This indicator will give you the SSS Procedures Failure Rate by meaning the number of failures during SSS Procedures compared to the number of successful Immediate Assignment Procedures (Establishment Indication).Formula: SSS Pr ocFailCS (a) SSSProcFai lRateCS = Im mAssSuccCSUsed param.: SSSProcFailCS (3.3(a)), ImmAssSuccCS (3.1(a))Elem. Object: CellUnit: NoneRemarks: Please note that Authentication-, Identity-, Ciphering- and MSC failures are counted in this formula although they are not related to the BSS. User Release before assignment of a TCH is also included in this formula. Assignments of SDCCH are not considered.21 A30808-X3247-B912-1-7618
  • 22. Information PM: SBS Key Performance IndicatorsSystem3.6 SSS Procedures Success Rate related to Call SetupsLong name: (a) SSS Procedures Success Rate related to Call Setups (b) Total SSS Procedures Success Rate related to Call SetupsShort name: (a) SSSProcSuccRateCS (b) SSSProcSuccRateCStotalDescription: The first Indicator will give you the SSS Procedures Success Rate related to Call Setups by meaning the rate for successful allocated Timeslots from MSC point of view (Assignment Request Message) minus the SDCCH Drop Rate related to Call Setups. This indicator is related to the Radio Network and is therefore recommended to find out Radio Network failures. The second indicator will give you the SSS Procedures Success Rate related to Call Setups by meaning the number of started Assignment Procedures (Assignment Requests) compared to the number of successful Immediate Assignment Procedures (Establishment Indications) related to Call Setups. Authentication-, Identity-, Ciphering- and MSC failures are among others counted within this indicator although they are not related to the BSS.Formula: (a) SSSProcSuccRateCS = 1 - SDCCHDropRateCS AssAtt (b) SSSProcSuccRateCStotal = or ImmAssSuccCS SSSProcSuccRateCStotal = 1 − SDCCHDropRateCS − SSS Pr ocFailRateCSUsed param.: ImmAssSuccCS (3.1(a)), AssAtt (0(a)), SDCCHDropRateCS (3.4(a)), SSSProcFailRateCS (3.5(a))Elem. Object: CellUnit: NoneRemarks: SSSProcSuccRateCStotal: Please note that Authentication-, Identity-, Ciphering- and MSC failures will lead to a worse Success Rate although they are not related to the BSS. User Release before assignment of a TCH is also included in the second formula. Assignments of SDCCH are not considered.22 A30808-X3247-B912-1-7618
  • 23. Information PM: SBS Key Performance IndicatorsSystem4 Assignment AnalysisThe KPIs of this section are mainly used for the derivation of the Call Setup SuccessRate (CSSR) and Call Setup Failure Rate (CSFR). The Key Performance Indicators(KPIs) are mostly related to the Mobile Station point of view, by meaning they willcount the events related to Mobile Stations. The messageflow of the AssignmentProcedure is listed below (normal case). The numbers in brackets will indicateavailable SBS performance measurements.MS BTS BSC MSC [1] TASSATT (MTCHBUTI) ASSIGNMENT REQUEST PHYS CONTEXT REQ PHYS CONTEXT CONF CHAN ACTIV CHAN ACTIV ACK CHANNEL ACTIV NEG ACK [5] TASSFAIL ASSIGNMENT FAILURE ASSIGNMENT COMMAND ASSIGNMENT COMMAND SABM (TNTCHCL) ESTABLISH INDICATION UA ASSIGNMENT COMPLETE ASSIGNMENT COMPLETE [4] TASSSUCC ASSIGNMENT COMPLETEFig. 5 Message flow: Assignment Procedure (normal case)BSS Counter[1] ASSIGMENT ATTEMPS TASSATT [2..3][2] INCOMING REDIRECTED TASSSUCC [4..5][3] OUTGOING REDIRECTED CALLS SINTHINT [7] + SUINBHDO [10*n+7]; n = 0 ...31 (n= number of GSM ADJ-ids) + SUOISHDO[10 * m + 7] ; m = 0 ...63 (m= number of UMTS ADJ-ids)[4] ASSIGMENT COMPLETE (normal Assignm.) TASSSUCC [2..3][5] ASSIGMENT FAILURE TASSFAIL [6,7,8,10,11,12,13,15][6] Queuing Failure NMSGDISQ [1,2]23 A30808-X3247-B912-1-7618
  • 24. Information PM: SBS Key Performance Indicators System The following figure shows you the traffic flow. Single Cell / Observed Cell [1] Assignment Attempts [5] Assignment [3]+[4] Assignment success [6] Queuing Failure[2] Successful inc. redirected Calls [4] Assignment Complete [3] Successful Outgoing redirected Calls Fig. 6 Traffic flow: Assignment Procedure The observed cell is the cell where the call establishment has been started (immediate assignment procedure). By aid of the feature Directed Retry a TCH may be assigned in a cell different from the observed cell. Also in that case the “success” is counted for the observed cell. The Assignment procedure is used to allocate a TCH. Because of new feature the Assignment Success Rate is not easy to evaluate. The Directed Retries have also to be considered. The concept how to evaluate Directed Retries for the Assignment Success Rate is comparable with the Handover Success Rate, where only outgoing Handover will be considered. Therefore all Directed Retries for an observed cell have to be counted, which where started in the observed cell and were successful in any target cell with neighbor cell measurements. Under this assumption the Assignment Success Rate can be evaluated as follows: Assignment Success Rate = (Assignment Complete [4] + Successful outgoing redirected Calls [3]) / Assignment Attempts [1] This chapter contains the following ‘Number related’ KPIs: • Number of Assignment Attempts: [1], see chapter 0. • Number of Assignment Failures: [5] ,see chapters 4.2(a), (b), (c) • Number of successful Assignments = [3]+[4], see chapter 4.3 • Number of Queuing Failures: [6], see chapter 4.2(d) This chapter contains the following ‘Rate related’ KPIs: • Assignment Failure Rate, see chapter 4.4 • Assignment Success Rate, see chapter 4.5 • "Assignment success rate when radio resources available, see chapter 4.6(a) 24 A30808-X3247-B912-1-7618
  • 25. Information PM: SBS Key Performance IndicatorsSystem4.1 Number of Assignment AttemptsLong name: (a) Number of Assignment AttemptsShort name: (a) AssAttDescription: These indicators will give you the number of Assignment procedures started by the MSC.Formula: (a) AssAtt = TASSATT[2, 3]Used param.: TASSATT[2,3]Elem. Object: CellUnit: NoneRemarks: Only TCH assignments are considered. Assignments of SDCCHs are not considered. Only the assignment procedure triggered by the MSC is considered but not the Immediate Assignment procedure. Incoming handovers are also not considered.25 A30808-X3247-B912-1-7618
  • 26. Information PM: SBS Key Performance IndicatorsSystem4.2 Number of Assignment FailuresLong name: (a) Number of TCH Losses (b) Number of Assignment Failures by Message (c) Number of Assignment Failures due to other Reason (d) Number of Queuing Failures (e) Total Number of Assignment FailuresShort name: (a) TCHLoss (b) AssFailbyMess (c) AssFailOther (d) QueFail (e) AssFailDescription: These indicators will give you the number of failed Assignments of a TCH.Formula: (a) TCHLoss = TASSFAIL[8,13] (b) AssFailbyM ess = TASSFAIL[6 ,7,10,11,1 2,15] (c) AssFailOther = AssAtt - AssSucc - TCHLoss - AssFailbyMess - QueFail (d) QueFail = NMSGDISQ[1,2] (e) AssFail = TASSFAIL[6..8, 10..13,15] + NRCLRREQ[22]Used param.: TASSFAIL [6,7,8,10,11,12,13,15], AssAtt (0(a)) , AssSucc (4.3(a)), NMSGDSIQ[1,2], NRCLRREQ[22]Elem. Object: CellUnit: NoneRemarks: • Directed Retries are not considered, because they ares not related to assignment failures • Assignments of SDCCH are not considered. • Sub-counters TASSFAIL[10] and TASSFAIL[15] (All other causes) used in formula (b) includes the A-interface and equipment related causes (see GSM 08.08). • Queuing failures are completely covered in formula (e). Measurement NMSDISQ[1,2] must not be added. But measurement NRCLRREQ[22] is included in case a queued subscriber is pre-empted before expiry of timer T11. • Formula (c) AssFailOther contains all other causes related to internal and transmission failures.26 A30808-X3247-B912-1-7618
  • 27. Information PM: SBS Key Performance IndicatorsSystem4.3 Number of successful AssignmentsLong name: (a) Number of successful AssignmentsShort name: (a) AssSuccDescription: These indicators will give you the number of successful completed Assignment procedures. Successful completed Assignment procedures are incremented even with successful outgoing directed retry, because it represents an assignment of TCH for the originating cell.Formula: AssSucc = TASSSUCC[2,3] 31 63 + SINTHINT[7] + ∑ SUINBHDO[10 * n + 7] + ∑ SUOISHDO[10 * m + 7] (a) n =0 m =0 with n for the number of GSM neighbourcell relation (n=0..31) with m for the number of UMTS neighbourcell relation (m=0..63)Used param.: TASSSUCC[2,3], SINTHINT[7], SUINBHDO[10 * n + 7], SUOISHDO[10 * m + 7]Elem. Object: CellUnit: NoneRemarks: • Assignments of SDCCH are not considered. • Intersystem Directed Retry to UMTS are considered27 A30808-X3247-B912-1-7618
  • 28. Information PM: SBS Key Performance IndicatorsSystem4.4 Assignment Failure RateLong name: (a) TCH Loss Rate (b) Assignment Failure Rate by Message (c) Assignment Failure Rate due to other Reason (d) Queuing Failure Rate (e) Assignment Failure RateShort name: (a) TCHLossRate (b) AssFailbyMessRate (c) AssFailOtherRate (d) QueFailRate (e) AssFailRateDescription: These indicators will give you the Assignment Failure Rates. The Assignment procedure is unsuccessful if the BSC returns a Assignment Failure message to the MSC or if the directed retry in the target cell was not successful.Formula: TCHLoss (a) TCHLossRate = AssAtt AssFailbyMess (b) AssFailbyMessRate = AssAtt AssFailOther (c) AssFailOtherRate = AssAtt QueFail (d) QueFailRate = AssAtt AssFail (e) AssFailRate = AssAttUsed param.: AssAtt(0(a)), TCHLoss (4.2(a)), AssFailbyMess (4.2(b)), AssFailOther (4.2(c)), QueFail (4.2(d)), AssFail (4.2(d)),Elem. Object: CellUnit: NoneRemarks: • Directed Retries are not considered, because they ares not related to assignment failures. • Assignments of SDCCH are not considered28 A30808-X3247-B912-1-7618
  • 29. Information PM: SBS Key Performance IndicatorsSystem4.5 Assignment Success RateLong name: (a) Assignment Success RateShort name: (a) AssSuccRateDescription: These indicators will give you the Assignment Success Rate. The Assignment procedure is successful if the BSC returns an Assignment Complete message to the MSC or if the directed retry in the target cell was successful.Formula: AssSucc (a) AssSuccRate = or 1 − AssFailRate AssAttUsed param.: AssAtt(0(a)), AssSucc (4.3(a)), AssFailRate (4.4(e))Elem. Object: CellUnit: NoneRemarks: • Assignments of SDCCH are not considered. • Inter System Directed Retry (e.g. UMTS) are also considered4.6 Assignment success rate when radio resources availableLong name: (a) Assignment success probability when radio resource availableShort name: (a) SuccAssProbNoTCHBlockingDescription: This indicator provides the radio failures during the TCH assignment procedureFormula: AssFailbyMess (a) SuccAssProbNoTCHBlocking = 1 − AssAtt - TCHLossUsed param.: AssAtt(0(a)), TCHLoss (4.2(a)), AssFailbyMess (4.2(b))Elem. Object: CellUnit NoneRemarks: 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 available29 A30808-X3247-B912-1-7618
  • 30. Information PM: SBS Key Performance IndicatorsSystem5 Call Setup AnalysisThe KPIs of the previous sections are mainly used for the derivation of the Call SetupSuccess Rate (CSSR) and Call Setup Failure Rate (CSFR). The Call Setup SuccessRate and Call Setup Failure Rate are related to the Mobile Station point of view, bymeaning they will count the events related to Mobile Stations.Overview Call Setup AnalysisCS (5.3) CSSR Call Setup Success Rate BSS (5.5) CSFR Call Setup Failure Rate Call Setup Failure Rate due to Immediate Assignment Losses Call Setup Failure Rate due to AGCH Loss Call Setup Failure Rate due to Immediate Assignment without MS Seizure Call Setup Failure Rate due to SDCCH Drops Call Setup Failure Rate due to SSS Procedure Failure Call Setup Failure Rate due to TCH Loss Call Setup Failure Rate due to Assignment Failures by Message Call Setup Failure Rate due to Assignment Failures with other Reasons Call Setup Failure Rate due to Queuing FailuresComparable 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 FailuresAnd the following ‘Rate related’ KPIs:• Call Setup Success Rate• Call Setup Failure Rate30 A30808-X3247-B912-1-7618
  • 31. Information PM: SBS Key Performance IndicatorsSystem5.1 Number of Call Setup AttemptsLong name: (a) Number of Call Setup AttemptsShort name: (a) CSAttDescription: This indicator counts all attempts at the BSS to setup up an end to end connection. The indicator deals with the call setup attempts from the perspective of the MSFormula: ImmAssSuccCS (a) CSAtt = ImmAssSuccRateUsed param.: ImmAssSuccCS (3.1a), ImmAssLossRate (2.6a), AGCHLossRate (2.7a), ImmAssNoSeizRate (2.8a)Elem. Object: CellUnit: NoneRemarks: Phantom RACHs are channel required messages not foreseen for the observed cell. The Immediate Assignment procedure to allocate an SDCCH/TCH is then started, but will not be successful, because no MS will reply with a SABM message and therefore a BTS Timer will expire. Phantom RACHs are not considered as call setup attempts. Systematic error A mobile station may also not answer to an IMM ASS Command due to bad radio conditions. Such radio events will not be considered as call setup attempts Be aware of parameter settings for RACHBT and RXLEVAMI The Immediate Assignment failures are independent to the different call types (MOC, MTC, Locupd, SMS, ...). Therefore the Immediate Assignment Failure Rates for any call type are used in the above formula.5.2 Number of Successful Call SetupsLong name: (a) Number of Successful Call SetupsShort name: (a) CSSuccDescription: This indicator counts all successful Call Setups at the BSS to setup up an end to end connection. A Call Setup was successful if the MS was able to seize a TCH.Formula: (a) CSSucc = AssSuccUsed param.: AssSucc (4.3a)Elem. Object: CellUnit: NoneRemarks: Assignment of SDCCH are not considered31 A30808-X3247-B912-1-7618
  • 32. Information PM: SBS Key Performance IndicatorsSystem5.3 Call Setup Success RateLong name: (a) Call Setup Success Rate (b) Call Setup Success Rate BSSShort name: (a) CSSuccRate (b) CSSuccRateBSSDescription: This indicator will give you the BSS observed Call Setup Success Rate to setup up an end to end connection. Two indicators are available, one that takes into account all Call Setup rejections (BSS immediate assignment, SSS security and TCH assignment), one that only takes into account BSS related Call Setup rejections (BSS immediate assignment and TCH assignment).Formula: (a) CSSuccRate = ImmAssSucc Rate * SSSProcSuc cRateCStot al * AssSuccRat e (b) CSSuccRateBSS = ImmAssSuccRate * ( 1 - SDCCHDropRateCS) * AssSuccRateUsed param.: ImmAssSuccRate (2.11(a)), SSSProcSuccRateCStotal (3.6(b)), AssSuccRate (4.5(a)), SDCCHDropRateCS (3.4(a))Elem. Object: CellUnit: NoneRemarks: BR7: correction CSSuccRateBSS: factor (1-SDCCHDropRateCS) included in formula BR7: KPI CSSuccRateSSS cancelled (just another name for KPI SSSProcSuccRateCStotal (3.6(b)) Systematic errors can occur as described in the used KPIs.5.4 Number of Call Setup FailuresLong name: (a) Number of Call Setup Failures (b) Number of Call Setup Failures due to Immediate Assignment Losses (c) Number of Call Setup Failures due to AGCH Loss (d) Number of Call Setup Failures due to Immediate Assignment without MS Seizure (e) Number of Call Setup Failures due to SDCCH Drops (f) Number of Call Setup Failures due to SSS Procedure Failure (g) Number of Call Setup Failures due to TCH Loss (h) Number of Call Setup Failures due to Assignment Failures by Message (i) Number of Call Setup Failures due to Assignment Failures with other Reasons (j) Number of Call Setup Failures due to Queuing FailuresShort name: (a) CSFail (b) CSFailImmAssLoss (c) CSFailAGCHLoss (d) CSFailImmAssNoSeiz32 A30808-X3247-B912-1-7618
  • 33. Information PM: SBS Key Performance IndicatorsSystem (e) CSFailSDCCHDrop (f) CSFailSSSProcFail (g) CSFailTCHLoss (h) CSFailAssFailbyMess (i) CSFailAssFailOther (j) CSFailQueFailDescription: These indicators will give you the number of unsuccessful Call Setups. Different indicators distinguish between different causes used in the different procedures (Immediate Assignment, SSS Procedures and Assignment).Formula: (a) CSFail = CSAtt - CSSucc (b) CSFailImmAssLoss = CSAtt * ImmAssLossRate (c) CSFailAGCHLoss = CSAtt * AGCHLossRate (d) CSFailImmAssNoSeiz = CSAtt * ImmAssNoSeizRate (e) CSFailSDCCHDrop = CSAtt * ImmAssSuccRate * SDCCHDropRateCS (f) CSFailSSSProcFail = CSAtt * ImmAssSuccRate * SSSProcFailRateCS (g) CSFailTCHLoss = TCHLoss (h) CSFailAssFailbyMess = AssFailbyMess (i) CSFailAssFailOther = AssFailOther (j) CSFailQueFail = QueFailUsed param.: CSAtt (5.1(a)), CSSucc (5.2(a)), ImmAssLossRate(2.8(a)), AGCHLossRate(2.9(a)), ImmAssNoSeizRate(2.10 (a)), ImmAssSuccRate (2.11(a)), SDCCHDropRateCS(3.4(a)), SSSProcFailRateCS(3.5(a)), TCHLoss(4.2 (a)), AssFailbyMess(4.2(b)), AssFailOther(4.2(c)), QueFail(4.2(c))Elem. Object: CellUnit: NoneRemarks: See remarks in the referenced KPIs33 A30808-X3247-B912-1-7618
  • 34. Information PM: SBS Key Performance IndicatorsSystem5.5 Call Setup Failure RateLong name: (a) Call Setup Failure Rate (b) Call Setup Failure Rate due to Immediate Assignment Losses (c) Call Setup Failure Rate due to AGCH Loss (d) Call Setup Failure Rate due to Immediate Assignment without MS Seizure (e) Call Setup Failure Rate due to SDCCH Drops (f) Call Setup Failure Rate due to SSS Procedure Failure (g) Call Setup Failure Rate due to TCH Loss (h) Call Setup Failure Rate due to Assignment Failures by Message (i) Call Setup Failure Rate due to Assignment Failures with other Reasons (j) Call Setup Failure Rate due to Queuing FailuresShort name: (a) CSFailRate (b) CSFailRateImmAssLoss (c) CSFailRateAGCHLoss (d) CSFailRateImmAssNoSeiz (e) CSFailRateSDCCHDrops (f) CSFailRateSSSProcFail (g) CSFailRateTCHLoss (h) CSFailRateAssFailbyMess (i) CSFailRateAssFailOther (j) CSFailRateQueFailDescription: These indicators will give you the Call Setup Failure Rate. Different indicators distinguish between different causes used in the different procedures (Immediate Assignment, SSS Procedures and Assignment).Formula: (a) CSFailRate = 1 – CSSuccRate (b) CSFailRateImmAssLoss = ImmAssLossRate (c) CSFailRateAGCHLoss = AGCHLossRate (d) CSFailRateImmAssNoSeiz = ImmAssNoSeizRate (e) CSFailRateSDCCHDrops = SDCCHDropRateCS (f) CSFailRateSSSProcFail = SSSProcFailRateCS (g) CSFailRateTCHLoss = TCHLossRate (h) CSFailRateAssFailbyMess = AssFailbyMessRate (i) CSFailRateAssFailOther = AssFailOtherRate (j) CSFailRateQueFail = QueFailRateUsed param.: CSSuccRate (5.3(a)), ImmAssLossRate(2.8(a)), AGCHLossRate(2.9(a)), ImmAssNoSeizRate(2.10(a)), SDCCHDropRateCS(3.4(a)), SSSProcFailRateCS(3.5(a)), TCHLossRate(4.4(a)), AssFailbyMessRate(4.4(b)), AssFailOtherRate(4.4(c)), QueFailRate(4.4(d))Elem. Object: CellUnit: NoneRemarks: See remarks in the referenced KPIs34 A30808-X3247-B912-1-7618
  • 35. Information PM: SBS Key Performance IndicatorsSystem6 TCH Drop related Performance Indicators6.1 Number of Dropped TCH ConnectionsLong name: (a) Number of Dropped TCH ConnectionsShort name: (a) TCHDropDescription: This indicator will give you the number of dropped TCH connections related to Mobile Stations. Only drops related to the BSS including the radio interface are considered. But drops detected by the MSC call processing reasons are excluded. (Therefore among others drops arising from the remote BSS and the remote radio interface are not considered)Formula: (a) TCHDrop = NRCLRREQ[1.. 3, 5.. 12, 14 ..18]Use case: Observation of customer satisfactionUsed param.: NRCLRREQ[1 .. 3, 5.. 12, 14 ..18]Elem. Object: CellUnit: NoneRemarks: 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 triggered35 A30808-X3247-B912-1-7618
  • 36. Information PM: SBS Key Performance IndicatorsSystem6.2 TCH Drop DistributionLong name: (a) TCH drop distribution due to expiry of timer T200 (b) TCH drop distribution due to unsolicited DM response (c) TCH drop distribution due to sequence error (d) TCH drop distribution due to expiry of timer T_MSRFPCI (e) TCH drop distribution due to distance limit exceeded (f) TCH drop distribution due to handover access failures (g) TCH drop distribution due to radio link failures (h) TCH drop distribution due to remote transcoder failures (i) TCH drop distribution due to other connection failures (j) TCH drop distribution due to intra cell handovers (k) TCH drop distribution due to inter cell intra bsc handovers (l) TCH drop distribution due to inter bsc handovers (m) TCH drop distribution due to equipment failure (n) TCH drop distribution due to protocol error (o) TCH drop distribution due to distance error (p) TCH drop distribution due to preemption (q) TCH drop distribution due to O&M intervention (r) TCH drop distribution due to other reasonsShort name: (a) TCHDropDist.T200 (b) TCHDropDist.UnsolDMRes (c) TCHDropDist.SeqErr (d) TCHDropDist.TMSRFPCI (e) TCHDropDist.Distance (f) TCHDropDist.HOAccess (g) TCHDropDist.RadLinkFail (h) TCHDropDist.RemTranscFail (i) TCHDropDist.ConnOther (j) TCHDropDist.IntraCellHO (k) TCHDropDist.InterCellHO (l) TCHDropDist.InterBSCHO (m) TCHDropDist.EquipFail (n) TCHDropDist.ProtErr (o) TCHDropDist.DistErr (p) TCHDropDist.Preempt (q) TCHDropDist.OAM (r) TCHDropDist.OtherDescription: This indicator will give you the TCH Drop Distribution showing the particular TCH drops related to the total number of drops related to TCH connections.Use case: Detection of network problems: e.g. insufficient coverage For network optimization normally additional KPIs would be considered, e.g. KPIs for the supervision of transmission power, interference and HO)36 A30808-X3247-B912-1-7618
  • 37. Information PM: SBS Key Performance IndicatorsSystemFormula: NRFLTCH[1, 10,19,28] (a) TCHDropDis t.T200 = TCHDrop NRFLTCH[2, 11,20,29] (b) TCHDropDist.UnsolDMRes = TCHDrop NRFLTCH[3,12,21,30] (c) TCHDropDist.SeqErr = TCHDrop NRFLTCH[4, 13,22,31] t.TMSRFPCI = (d) TCHDropDis TCHDrop NRFLTCH[5, 14,23,32] (e) TCHDropDist.Distance = TCHDrop NRFLTCH[6, 15,24,33] (f) TCHDropDist.HOAccess= TCHDrop NRFLTCH[7,16,25,34] (g) TCHDropDist.RadLinkFail = TCHDrop NRFLTCH[8,17,26,35] (h) TCHDropDist.RemTranscFail = TCHDrop NRFLTCH[9, 18,27,36] t.ConnOthe = (i) TCHDropDis r TCHDrop UNIHIALC[1 ] (j) TCHDropDist.IntraCellHO = TCHDrop UNIHIRLC[1 ] (k) TCHDropDist.InterCellHO = TCHDrop InterBSCHODrop (l) TCHDropDist.InterBSCHO = TCHDrop NRCLRREQ[1 ,10] (m) TCHDropDist.EquipFail = TCHDrop (n) TCHDropDis NRCLRREQ[5,14] t.ProtErr = TCHDrop (o) TCHDropDis NRCLRREQ[6,15] t.DistErr = TCHDrop (p) TCHDropDis NRCLRREQ[7,16] t.Preempt = TCHDrop (q) TCHDropDist.OAM = NRCLRREQ[8,17] TCHDrop (r) TCHDropDist.Other = NRCLRREQ[9,18] TCHDropUsed param.: NRFLTCH[1..36], UNIHIALC[1], UNIHIRLC[1], InterBSCHODrop(0(a)), TCHDrop(6.1(a)), NRCLRREQ [1..18]Elem. Object: CellUnit: NoneRemarks: Handover Access failures are included in formulas TCHDropDist.HOAccess and37 A30808-X3247-B912-1-7618
  • 38. Information PM: SBS Key Performance IndicatorsSystem TCHDropDist.InterBSCHO. TCH drops during pending incoming inter BSC handover are not counted in formulas TCHDropDist.HOAccess. This avoids double counting of drops during pending HO (during pending HO the TCH drops are only counted in the originating cell). Therefore NRCLRREQ in fact counts the number of dropped TCH calls from the perspective of the Mobile Station (customer dissatisfaction) If the feature SDCCH Handover is activated, then this will lead to a systematic error.38 A30808-X3247-B912-1-7618
  • 39. Information PM: SBS Key Performance IndicatorsSystem6.3 TCH Drop RateLong name: (a) TCH Drop RateShort name: (a) TCHDropRateDescription: This indicator will give you the rate of all drops of TCH connections. Drops comprise all BSC caused terminations of TCH connection. I.e. connection termination induced by an MSC is not counted as TCH drop within the scope of the present radio network related document. The TCH drops are related to all seizures of a TCH in the observed cell. A TCH may be seized during call setup and additionally for handover (including Directed Retry). Therefore on call in the view of a mobile subscriber may cause the seizure of more than one TCH spread over several cellsFormula: TCHDrop (a) TCHDropRate = SUCTCHSE[1..2]Used param.: TCHDrop(6.1(a)), SUCTCHSE[1..2]Elem. Object: CellUnit: NoneRemarks: Please note that there can be systematic errors caused by timer settings (Ny, T3105, TTrau, TSync, T_MSRFPCI, T8). If the feature SDCCH Handover is activated, then this will lead to a systematic error. This KPI is not only related to Call Setups. It is related to any TCH seizure (e.g. incoming Handovers). Therefore for network optimization it is recommended to use KPI ‘TCH Drops per Erlanghour ‘, because increasing number of Handovers (e.g. Ping Pong Handovers) will decrease the TCH Drop Rate.39 A30808-X3247-B912-1-7618
  • 40. Information PM: SBS Key Performance IndicatorsSystem6.4 Call Drop RateLong name: (a) Number of terminated calls (b) Call Drop RateShort name: (a) NumTermCalls (b) CallDropRateDescription: This indicator provides the number of terminated calls and the call drop rate from the view of the MS (customer satisfaction). Preconditions: 1. A call is established when the MS has seized the TCH • Ass Failure in connection with a following Clear Command is not considered as call, since the MS has not yet seized a TCH. (e.g. AssFail: No radio resource available, MSC controlled Directed Retry) • Queuing timer expiry is not considered • Expiry of timer T_MSRFPCI is not considered 2. Call termination (and especially call drop) is counted for that cell, where the TCH was seized by the MS at the time of the call termination (especially call drop) • Call termination (and especially call drop) during pending HO is counted for the old cell 3. Only call drops initiated by the BSS are considered • Drops comprise all BSC caused terminations of calls. I.e. call termination induced by an MSC is not counted as call drop within the scope of the present radio network related document • Release of TCH in connection with HO reversion to old cell is not considered (e.g.: Inter BSC HO -> HO access failure -> Clear Command). Reason: no TCH drop from the MS perspective. •Formula: (a) NumTermCalls = NRCLRCMD[1.. 2, 4 .. 8, 10 ..12] - NRCLRREQ[4,13] - TASSFAIL[6.. 8,11..13] TCHDrop (b) CallDropRate = NumTermCallsUsed param.: TCHDrop(6.1(a)), NRCLRCMD[1 .. 2, 4 .. 8, 10..12], TASSFAIL[6.. 8,11 .. 13], NRCLRREQ[4,13], NumTermCalls(6.4(a))Elem. Object: CellUnit: NoneRemarks: 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 triggers40 A30808-X3247-B912-1-7618
  • 41. Information PM: SBS Key Performance IndicatorsSystem NRCLRREQ[4,13]; this also lead to triggering of NRCLRCMD[1,7] (“BSS initiated”) • Unsuccessful TCH Assignment Procedure with Loss of ASSIGNMENT COMMAND (T10 Expiry): In that case the BSC sends Assignment Failure to the MSC and triggers TASSFAIL[6,11]; this also leads to triggering of NRCLRCMD[2,8] (“Call Control”) • Unsuccessful Directed Retry, Intra-BSC, with Reversion to SDCCH (T3124 Expiry): In that case the BSC sends Assignment Failure to the MSC and triggers TASSFAIL[7,12]; this also leads to triggering of NRCLRCMD[2,8] (“Call Control”) • No TCH available (no queuing): In that case the BSC sends Assignment Failure to the MSC and triggers TASSFAIL[8,13]; this also leads to triggering of NRCLRCMD[2,8] (“Call Control”) Systematic failures in the formulas: • Inter BSC handover with reversion to old cell: In that case the MSC receives HO_Failure from the old BSC and sends Clear Command (“equipment failure”) the target BSC which triggers NRCLRCMD[4] for the target cell -> this effect slightly improve the CallDropRate by pretending that more call have existed than in reality. • Inter BSC directed retry with no successful TCH seizure: In that case the BSC send assignment Failure and triggers Tassfail[9,14]; this lead also to a Clear Command (“Call Control”) which triggers NRCLRCMD[2] -> this effect slightly improve the CallDropRate by pretending that more call have existed than in reality. • Expiry of timer T_MSRFPCI during assignment: In that case NRCLRREQ is triggered. This can only occur when T_MSRFPCI is not well adjusted (< T10) -> this effect slightly deteriorates the call drop rate (numerator and denominator are increased) • There can be systematic errors caused by timer settings (Ny1, T3105, TTrau, TSync, T_MSRFPCI, T8). If the feature SDCCH Handover is activated, then this will lead to a systematic error. -> this effect slightly deteriorates the call drop rate (numerator and denominator are increased) Recommendation: Drop per Erlang/hour is recommended to be used for quality assessment of radio network performance. Reason: the call drop rate is depending on the average call duration. The call drop rate is proportional to the call duration.41 A30808-X3247-B912-1-7618
  • 42. Information PM: SBS Key Performance IndicatorsSystem6.5 Mean Time between TCH DropLong name: (a) Mean Time between TCH DropShort name: (a) MTBTCHDropDescription: This indicator will give you mean time between TCH Drop, by meaning the time in seconds until the occurrence of the loss of a TCH connection.Formula: TCHTrafCarrDR * Granularity * 60s (a) MTBTCHDrop = TCHDropUsed param.: TCHDrop(6.1(a)), TCHTrafCarrDR(8.1.4(c)), Granularity in minutesElem. Object: CellUnit: SecondsRemarks: SDCCH Handovers are not considered and can therefore lead to systematic errors.6.6 TCH Drops per ErlanghourLong name: (a) TCH Drops per ErlanghourShort name: (a) TCHDropErlhDescription: This indicator will give you TCH Drops per Erlanghour., by meaning the number of losses of TCH connections related to one Erlanghour.Formula: TCHDrop 60 (a) TCHDropErlh = * TCHTrafCarrDR GranularityUsed param.: TCHDrop(6.1(a)), TCHTrafCarrDR(8.1.4(c)), Granularity in minutesElem. Object: CellUnit: NoneRemarks: SDCCH Handovers are not considered and can therefore lead to systematic errors.42 A30808-X3247-B912-1-7618
  • 43. Information PM: SBS Key Performance IndicatorsSystem7 SDCCH Drop related Performance Indicators7.1 Number of dropped SDCCH ConnectionsLong name: (a) Number of dropped SDCCH ConnectionsShort name: (a) SDCCHDropDescription: This indicator will give you the number of dropped SDCCH Connections, which can occur for any call type (MOC, MTC, Locupd, SMS, ...).Formula: (a) SDCCHDrop = NRCLRREQ[19 .. 21, 23 .. 26] + TASSFAIL[1,6,11]Used param.: NRCLRREQ[19 .. 21, 23 .. 26], TASSFAIL[1,6,11]Elem. Object: CellUnit: NoneRemarks: This KPI is based on NRCLRREQ counters, because drops caused by the BSC must be considered.7.2 SDCCH Drop RateLong name: (a) SDCCH Drop Rate (b) SDCCH Drop Rate per SDCCH connectionShort name: (a) SDCCHDropRate (b) SDCCHDropConnRateDescription: This indicator will give you the rate all losses of connections during a SDCCH Connection.Formula: SDCCHDrop (a) SDCCHDropRate = NSUCCHPC[1..6] SDCCHDrop (b) SDCCHDropConnRate = NRCLRCMD[13,14,16..18]Used param.: SDCCHDrop(7.1(a)), NSUCCHPC[1..6], NRCLRCMD[13,14,16..18]Elem. Object: CellUnit: NoneRemarks: MSC controlled SDCCH Handover drops are also counted (Expiry of Timer T8). BSC controlled SDCCH Handover drops are not counted and will lead to small systematic errors.43 A30808-X3247-B912-1-7618
  • 44. Information PM: SBS Key Performance IndicatorsSystem7.3 Mean Time between SDCCH DropLong name: (a) Mean Time between SDCCH DropShort name: (a) MTBSDCCHDropDescription: This indicator will give you mean time between SDCCH Drop, by meaning the time in seconds until the occurrence of the loss of a SDCCH connection.Formula: SDCCHTrafCarr * Granularity * 60s (a) MTBSDCCHDrop = SDCCHDropUsed param.: SDCCHDrop(7.1(a)), SDCCHTrafCarr(9.2(a)) , Granularity in minutesElem. Object: CellUnit: SecondsRemarks: SDCCH Handovers Drops are not considered.7.4 SDCCH Drops per ErlanghourLong name: (a) SDCCH Drops per ErlanghourShort name: (a) SDCCHDropErlhDescription: This indicator will give you SDCCH Drops per Erlanghour., by meaning the number of losses of SDCCH connections related to one Erlang.Formula: SDCCHDrop 60 (a) SDCCHDropErlh = * SDCCHTrafCarr GranularutyUsed param.: SDCCHDrop(7.1(a)), SDCCHTrafCarr(9.2(a)), Granularity in minutesElem. Object: CellUnit: NoneRemarks: SDCCH Handovers Drops are not considered.44 A30808-X3247-B912-1-7618
  • 45. Information PM: SBS Key Performance IndicatorsSystem8 TCH Load related Performance Indicators8.1 TCH Load for Circuit Switched TrafficThe following figure will give you an overview about the load related performanceindicators used in the traffic theory. Traffic Offered A [Erl] Traffic Carried Y [Er Call Attempts CA Number of Calls Carried CC channels N Traffic Lost R [Erl] Calls Rejected CR Loss B [%]Fig. 7 Overview Load related performance indicatorsFor the estimation of the Load of GSM Telecom Systems the Erlang B formula fornon queuing Telefon Systems and the Erlang C formula for Queuing TelefonSystems can be used. Further information about the traffic theory can be found in the‘Siemens Tabellenbuch Fernsprechtheorie ISBN 3-8009-1343-7’.8.1.1 TCH Traffic Distribution RateLong name: (a) TCH Full Rate Traffic (b) TCH Half Rate TrafficShort name: (a) FRT (b) HRTDescription: This indicator will give you the Rate of Full Rate and Half Rate traffic on TCH compared to the total traffic.Formula: MEBUSTCH [1, 3] (a) FRT = MEBUSTCH [1..4] MEBUSTCH [2, 4] (b) HRT = MEBUSTCH [1..4]Used param.: MEBUSTCH[1..4]Elem. Object: CellUnit: NoneRemarks: This KPI can be used by network planning to calculate the number of needed45 A30808-X3247-B912-1-7618
  • 46. Information PM: SBS Key Performance IndicatorsSystem TRX.8.1.2 TCH Loss RateLong name: (a) TCH seizure blocked rate Full Rate (b) TCH seizure blocked Rate Half Rate (c) TCH seizure blocked Rate Dual Rate (d) TCH seizure blocked Rate Waiting System Full Rate (e) TCH seizure blocked Rate Waiting System Half Rate (f) TCH seizure blocked Rate Waiting System Dual Rate (g) TCH seizure blocked RateShort name: (a) TCHSeizBlckRateFR (b) TCHSeizBlckRateHR (c) TCHSeizBlckRateDR (d) TCHSeizBlckRateWSFR (e) TCHSeizBlckRateWSHR (f) TCHSeizBlckRateWSDR (g) TCHSeizBlckRateDescription: This indicator will give you the TCH seizure blocked rate by meaning the rate where new TCH Seizure Attempts could not be handled by the observed cell, because all traffic channels were occupied / blocked. TCH seizure attempts for HO and Directed Retry are included in the formulas. Therefore from the perspective of a mobile subscriber, the call setup might become successful by assigning a TCH in another cell through (e.g. by applying the feature Directed Retry) even when a TCH blocking is counted. I.e. the KPIs consider the TCH access on cell level but not on connection level. Performance Indicators for waiting systems are also provided and will consider only the TCH Seizure attempts discarded from the TCH queue.Formula: ATCHSMBS [1, 3] (a) TCHSeizBlckRateFR = ATTCHSEI [1] ATCHSMBS [2, 4] (b) TCHSeizBlckRateHR = ATTCHSEI [2] ATCHSMBS [1 .. 4] (c) TCHSeizBlckRateDR = ATTCHSEI [1,2] NMSGDISQ [1, 3] (d) TCHSeizBlckRateWSFR = ATTCHSEI [1] NMSGDISQ [2,4] (e) TCHSeizBlckRateWSHR = ATTCHSEI [2] NMSGDISQ [1..4] (f) TCHSeizBlckRateWSDR = ATTCHSEI [1..2] ATCHSMBS[1..4] + NMSGDISQ [1..4] (g) TCHSeizBlckRate = ATTCHSEI [1..2]46 A30808-X3247-B912-1-7618
  • 47. Information PM: SBS Key Performance IndicatorsSystemUsed param.: ATCHSMBS[1..4], ATTCHSEI[1..2], NMSGDISQ[1..4]Elem. Object: CellUnit: Subscriber redial behaviour influences the blocking rate. Further the HO periodicity timer influences the TCH blocking rateRemarks: For Dual Rate Channels (formula c) the Full Rate and Half Rate channels must be weighted with the TCH Traffic distribution Rate. Please note, after expiry of Timer THORQST an intercell or intracell handover will be re-attempted and counter ATCHSMBS can be pegged again, if no resource is still available. In BR 7.0 the measurement ATCHSMBS was modified to count also in case of Abis pool congestion (extension of Trigger events-list). This fact does not affect the meaning or definition of the KPI.8.1.3 TCH Traffic OfferedLong name: (a) TCH Traffic Offered Full Rate (b) TCH Traffic Offered Half Rate (c) TCH Traffic Offered Dual RateShort name: (a) TCHTrafOffFR (b) TCHTrafOffHR (c) TCHTrafOffDRDescription: This indicator will give you the theoretical amount of traffic in Erlang which was offered to a cell. The indicators comprise the traffic explicitly induced by mobile subscribers and also additional virtual traffic emerged from radio network internal features like Directed retry and Handover. In the course of the performance of these two features a traffic demand my be offered successively to more than one possible target cell.Use case: Radio network capacity planning: The indicators may be used for radio network capacity planning. But they should not be used isolated since they pretend a higher demand of TCH resources as needed in reality for mobile subscriber satisfaction. The indicators should rather be used in connection with subscriber satisfaction oriented indicators (e.g. refer to chapter 5.5 (g): Call Setup Failure Rate due to TCH Loss)Formula: MEBUSTCH [1, 3] (a) TCHTrafOffFR = 1 - TCHLossRateFR MEBUSTCH [2, 4] (b) TCHTrafOffHR = 1 - TCHLossRateHR (c) TCHTrafOffDR = TCHTrafOffFR + TCHTrafOffHRUsed param.: MEBUSTCH[1..4] , TCHLossRateFR(8.1.2(a)), TCHLossRateHR(8.1.2(b))Elem. Object: CellUnit: ErlangRemarks: None47 A30808-X3247-B912-1-7618
  • 48. Information PM: SBS Key Performance IndicatorsSystem8.1.4 TCH Traffic CarriedLong name: (a) TCH Traffic Carried Full Rate (b) TCH Traffic Carried Half Rate (c) TCH Traffic Carried Dual RateShort name: (a) TCHTrafCarrFR (b) TCHTrafCarrHR (c) TCHTrafCarrDRDescription: This indicator will give you the amount of carried traffic in Erlang on TCH.Formula: (a) TCHTrafCarrFR = MEBUSTCH [1, 3] (b) TCHTrafCarrHR = MEBUSTCH [2, 4] (c) TCHTrafCarrDR = TCHTrafCarrFR + TCHTrafCarrHRUsed param.: MEBUSTCH[1..4]Elem. Object: CellUnit: ErlangRemarks: None48 A30808-X3247-B912-1-7618
  • 49. Information PM: SBS Key Performance IndicatorsSystem8.1.5 TCH Traffic LostLong name: (a) TCH Traffic Lost Full Rate (b) TCH Traffic Lost Half Rate (c) TCH Traffic Lost Dual Rate (d) TCH Traffic Lost Waiting System Full Rate (e) TCH Traffic Lost Waiting System Half Rate (f) TCH Traffic Lost Waiting System Dual RateShort name: (a) TCHTrafLostFR (b) TCHTrafLostHR (c) TCHTrafLostDR (d) TCHTrafLostWSFR (e) TCHTrafLostWSHR (f) TCHTrafLostWSDRDescription: This indicator will give you the amount of circuit switched traffic (measured in Erlang), which was lost for a cell due to lack of TCH resources. The indicators are not related to the loss of traffic a subscriber experiences. If for example during HO execution a certain target cell candidate is fully occupied this situation is counted as lost traffic for that target cell; but from the perspective of the subscriber the HO might become successful in another target cell. Additional indicator deal with waiting systems (queuing): • Amount of circuit switched traffic (measured in Erlang), which was lost due to discard from the TCH waiting queue.Formula: (a) TCHTrafLostFR = TCHTrafOffFR - TCHTrafCarrFR (b) TCHTrafLostHR = TCHTrafOffHR - TCHTrafCarrHR (c) TCHTrafLos tDR = TCHTrafOff DR - TCHTrafCar rDR TCHMHTFR (d) TCHTrafLostWSFR = NMSGDISQ[13] * , Granularity * 60s TCHMHTHR (e) TCHTrafLostWSHR = NMSGDISQ[2,4] * Granularity * 60s TCHMHTDR (f) TCHTrafLos tWSDR = NMSGDISQ[1 ..4] * Granularit * 60s yUsed param.: TCHTrafOffFR(8.1.3(a)), TCHTrafOffHR(8.1.3(b)), TCHTrafOffDR(8.1.3(c)), TCHTrafCarrFR(8.1.4(a)), TCHTrafCarrHR(8.1.4(b)), TCHTrafCarrDR(8.1.4(c)) NMSGDISQ[1..4], TCHMHTFR (8.1.7(a)), TCHMHTHR(8.1.7(b)), TCHMHTDR(8.1.7(c)),Elem. Object: CellUnit: ErlangRemarks: None49 A30808-X3247-B912-1-7618
  • 50. Information PM: SBS Key Performance IndicatorsSystem8.1.6 TCH Blocking RateLong name: (a) TCH Blocking Rate Full Rate (b) TCH Blocking Rate Half Rate (c) TCH Blocking Rate Dual RateShort name: (a) TCHBlockRateFR (b) TCHBlockRateHR (c) TCHBlockRateDRDescription: This indicator will give you the TCH Blocking Rate by meaning the rate were all traffic channels were occupied.Formula: AALTCHTI[1] (a) TCHBlockRateFR = Granularity * 60s AALTCHTI[4] (b) TCHBlockRateHR = Granularity * 60s (c) TCHBlockRateDR = TCHBlockRateFR * FRT + TCHBlockRateHR * HRTUsed param.: AALTCHTI[1,4], FRT(8.1.1(a)), HRT(8.1.1(b)), Granularity in MinutesElem. Object: CellUnit: NoneRemarks: For Dual Rate Channels (formula c) the Full Rate and Half Rate channels must be weighted with the TCH Traffic distribution Rate. Due to feature ‘Smooth Channel Modification’ the measurement type AALTCHTI keeps track of the number of timeslots belonging to the TCH_Pool, TCH/SD_Pool and SDCCH_Backup Pool.50 A30808-X3247-B912-1-7618
  • 51. Information PM: SBS Key Performance IndicatorsSystem8.1.7 TCH Mean Holding TimeLong name: (a) TCH Mean Holding Time Full Rate (b) TCH Mean Holding Time Half Rate (c) TCH Mean Holding Time Dual RateShort name: (a) TCHMHTFR (b) TCHMHTHR (c) TCHMHTDRDescription: This indicator will give you the mean holding Time in seconds for occupied TCHs in a cell.Formula: MEBUSTCH[1,3] * Granularity * 60 (a) TCHMHTFR = TNTCHCL [1, 3] MEBUSTCH[2,4] * Granularity * 60 (b) TCHMHTHR = TNTCHCL [2, 4] MEBUSTCH[1..4] * Granularity * 60 (c) TCHMHTDR = TNTCHCL [1..4]Used param.: MEBUSTCH[1..4], TNTCHCL[1..4], Granularity in minutesElem. Object: CellUnit: SecondsRemarks: A weighting with the TCH Traffic distribution Rate is not necessary here, because Erlang values are used.51 A30808-X3247-B912-1-7618
  • 52. Information PM: SBS Key Performance IndicatorsSystem8.1.8 TCH Traffic UtilizationLong name: TCH Traffic Utilisation Full Rate TCH Traffic Utilisation Half Rate TCH Traffic Utilisation Dual Rate TCH Traffic Utilisation Full Rate based on Erlang TCH Traffic Utilisation Half Rate based on Erlang TCH Traffic Utilisation Dual Rate based on ErlangShort name: TCHTrafUtilFR TCHTrafUtilHR TCHTrafUtilDR TCHTrafUtilFRErl TCHTrafUtilHRErl TCHTrafUtilDRErlDescription: 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: MEBUSTCH[1 ,3] TCHTrafUti = lFR NRDEFTCH[2 ,8] MEBUSTCH[2 ,4] TCHTrafUtilFR = NRDEFTCH[5 ,11] MEBUSTCH[1..4] TCHTrafUti = lFR NRDEFTCH[2 ,5,8,11] MEBUSTCH[1 ,3] lFRErl= TCHTrafUti A Erlang B formula: A = f(N, B) = f(NRDEFTCH[2,8], B) Erlang C formula: A = f(N, B, Ql, Qd) = f(NRDEFTCH[2,8], B, MTCHQLEN[1 MDURTCRQ[1 ], ]) MEBUSTCH[2,4] TCHTrafUtilHRErl = A Erlang B formula: A = f(N, B) = f(NRDEFTCH[5,11], B) Erlang C formula A = f(N, B, Ql, Qd) = f(NRDEFTCH[5,11], B, MTCHQLEN[2], MDURTCRQ[2]) MEBUSTCH[1 ..4] TCHTrafUti lDRErl = A Erlang B formula: A = f(N, B) = f(NRDEFTCH[2,5,8,11], B) Erlang C formula: A = f(N, B, Ql, Qd) = f(NRDEFTCH [2,5,8,11] , B, MTCHQLEN[1 ,2], MDURTCRQ[1 ,2]) with A = Offered Load in Erlang52 A30808-X3247-B912-1-7618
  • 53. Information PM: SBS Key Performance IndicatorsSystem B = Blocking Probability (Planning Parameter)Used param.: MEBUSTCH[1..4], NRDEFTCH [2,5,8,11], MTCHQLEN[1,2], MDURTCRQ[1,2]Elem. Object: CellUnit: NoneRemarks: If Queuing is activated, Erlang C instead of Erlang B formula has to be taken. A weighting with the TCH Traffic distribution Rate is not necessary here, because Erlang values are used.53 A30808-X3247-B912-1-7618
  • 54. Information PM: SBS Key Performance IndicatorsSystem8.2 Combined time slot utilisation for CS and PO Traffic8.2.1 Combined time slot occupation rate for CS and PO TrafficLong name: (a) Mean overall time slot occupation rate for CS and PO TrafficShort name: (a) MeaOcTsCDescription: This KPI provided the mean occupation rate of those timeslots of a cell, which can be assigned to users. All timeslots are considered independent if they are dedicated to CS or PO Traffic or if they can be used for both types of traffic. Only those timeslots are considered, which bear logical channels, which are under control of radio resource management (TCH, SDCCH, PDTCH); i.e. the timeslot consumption for common control channels and broadcast control channels is not considered.Formula: (a) MeaOcTsC = NALLPDCH [3,6] + MEBUSTCH [1,3] + MEBUSTCH [2,4]/2 + MBUSYSDC [1]/8 NDEFPDCH[3 ] + NRDEFTCH[3 ,9] + NRDEFTCH[6 ,12] / 2 + NDFTCHSD[1 ] + NDESDCCH[3 ]/8Used param.: NDEFPDCH[3]: number of defined PDCH, NALLPDCH [3,6]: mean number of occupied PDCH UL and DL (active TBF) NRDEFTCH[3,6,9,12]: mean number of defined TCH [3,9] full rate, [6,12] half rate (1/2 time slot) NDESDCCH[3]: mean number of defined SDCCHs (1/8 time slots) NDFTCHSD[1]: mean number of defined TCH/SD MEBUSTCH [1 .. 4]: Mean Number of busy TCHs [1,3] full rate, [2,4] half rate (1/2 time slot) MBUSYSDC [1]: Mean Number of busy SDCCHs (1/8 time slots)Elem. Object: CellUnit: NoneRemarks: NALLPDCH: Mean number of active TBF PDCH NDEFPDCH (and NAVPDCH) include also the packet channels used as PBCCH and PCCCH; but NALLPDCH does not contain these channels. This leads to a systematic error. Improvement by BR8 FRS 86899:54 A30808-X3247-B912-1-7618
  • 55. Information PM: SBS Key Performance IndicatorsSystem8.2.2 Combined time slot availability rate for CS and PO TrafficLong name: (b) Mean overall time slot availability rate for CS and PO TrafficShort name: (b) MeaAvTsCDescription: This KPI provided the availability rate of those timeslots of a cell, which can be assigned to users. All timeslots are considered independent if they are dedicated to CS or PO Traffic or if they can be used for both types of traffic. Only those timeslots are considered, which bear logical channels, which are under control of radio resource management (TCH, SDCCH, PDTCH); i.e. the timeslot consumption for common control channels and broadcast control channels is not considered.Formula: (b) MeaAvTsC = NAVPDCH[3] + NAVTCH[3,9] + NAVTCH[6,12] /2 + NAVSDCCH[3]/8 NDEFPDCH[3] + NRDEFTCH[3,9] + NRDEFTCH[6,12] / 2 + NDFTCHSD[1] + NDESDCCH[3]/8Used param.: NDEFPDCH[3]: number of defined PDCH, NAVPDCH[3]: number of available PDCH, NRDEFTCH[3,6,9,12]: mean number of defined TCH [3,9] full rate, [6,12] half rate (1/2 time slot) NAVTCH[3,6,9,12]: mean number of Available TCHs [3,9] full rate, [6,12] half rate (1/2 time slot) NDESDCCH[3]: mean number of defined SDCCHs (1/8 time slots) NAVSDCCH[3]: mean number of available SDCCHs (1/8 time slots) NDFTCHSD[1]: mean number of defined TCH/SD NAVTCHSD[3]: mean number of available TCH/SDElem. Object: CellUnit: NoneRemarks: None55 A30808-X3247-B912-1-7618
  • 56. Information PM: SBS Key Performance IndicatorsSystem9 SDCCH Load related Performance IndicatorsThe following figure will give you an overview about the load related performanceindicators used in the traffic theory. Traffic Offered A [Erl] Number of Traffic Carried Y [Eel] Call Attempts CA channels N Calls Carried CC Traffic Lost [Erl] Calls Rejected CR Loss BFig. 8 Overview Load related performance indicatorsFor the estimation of the Load of GSM Telecom Systems the Erlang B formula canbe used. Further information about the traffic theory you can find in the ‘SiemensTabellenbuch Fernsprechtheorie ISBN 3-8009-1343-7’.9.1 SDCCH Traffic OfferedLong name: (a) SDCCH Traffic OfferedShort name: (a) SDCCH TrafOffDescription: This indicator will give you the amount of traffic in Erlang on SDCCH the MS subscribers wanted to have due to the traffic theorie.Formula: MBUSYSDC [1] (a) SDCCHTrafOff = 1 - SDCCHLossRateUsed param.: MBUSYSDC[1], SDCCHLossRate(9.5(a))Elem. Object: CellUnit: ErlangRemarks: None56 A30808-X3247-B912-1-7618
  • 57. Information PM: SBS Key Performance IndicatorsSystem9.2 SDCCH Traffic CarriedLong name: (a) SDCCH Traffic CarriedShort name: (a) SDCCH TrafCarrDescription: This indicator will give you the amount of carried traffic in Erlang on SDCCH.Formula: (a) SDCCHTrafCarr = MBUSYSDC [1]Used param.: MBUSYSDC[1]Elem. Object: CellUnit: ErlangRemarks: None9.3 SDCCH Traffic LostLong name: (a) SDCCH Traffic LostShort name: (a) SDCCHTrafLostDescription: This indicator will give you the amount of traffic in Erlang on SDCCH which were lost (e.g. Blockings).Formula: (a) SDCCHTrafLost = SDCCHTrafOff - SDCCHTrafCarrUsed param.: SDCCHTrafOff(9.1(a)), SDCCHTrafCarr(9.2(a))Elem. Object: CellUnit: ErlangRemarks: None9.4 SDCCH Blocking RateLong name: (a) SDCCH Blocking RateShort name: (a) SDCCHBlockRateDescription: This indicator will give you the SDCCH Blocking Rate by meaning the rate where all SDCCH were occupied.Formula: ASDCALTI [1] (a) SDCCHBlockRate = Granularity * 60sUsed param.: ASDCALTI[1], Granularity in minutesElem. Object: CellUnit: NoneRemarks: Due to feature ‘Smooth Channel Modification’ the measurement type ASDCALTI keeps track of the number of timeslots belonging to the SDCCH_Pool and SDCCH_Backup_Pool and TCH/SD_Pool.57 A30808-X3247-B912-1-7618
  • 58. Information PM: SBS Key Performance IndicatorsSystem9.5 SDCCH Loss RateLong name: (a) SDCCH Loss RateShort name: (a) SDCCHLossRateDescription: This indicator will give you the SDCCH Traffic Loss Rate by meaning the rate where new SDCCH Seizure Attempts could not be handled, because all SDCCH were occupied / blocked.Formula: ATSDCMBS [1] (a) SDCCHLossRate = NATTSDPE [1]Used param.: ATSDCMBS[1], NATTSDPE[1]Elem. Object: CellUnit: NoneRemarks: None9.6 SDCCH Mean Holding TimeLong name: (a) SDCCH Mean Holding TimeShort name: (a) SDCCHMHTDescription: This indicator will give you the mean holding Time in seconds for occupied SDCCH in a cell.Formula: MBUSYSDC [1] * Granularity * 60s (a) SDCCHMHT = NSUCCHPC[1..6]Used param.: MBUSYSDC[1], NSUCCHPC[1..6], Granularity in minutesElem. Object: CellUnit: SecondsRemarks: None58 A30808-X3247-B912-1-7618
  • 59. Information PM: SBS Key Performance IndicatorsSystem9.7 SDCCH Traffic UtilisationLong name: SDCCH Traffic Utilisation SDCCH Traffic Utilisation based on Erlang formulaShort name: SDCCHTrafUtil SDCCHTrafUtilErlDescription: This indicator will give you the SDCCH Traffic Utilisation by meaning of the carried traffic divided through the number of available SDCCH. Formula b) is based on the Erlang B function.Formula: MBUSYSDC[1] (a) SDCCHTrafUtil = NDESDCCH[2] MBUSYSDC[1 ] (b) SDCCHTrafUtilErl = A Erlang B formula: A = f(N, B) = f(NDESDCCH[2], B) with A = Offered Load in Erlang B = Blocking Probability (Planning Parameter)Used param.: MBUSYSDC[1], NDESDCCH[2]Elem. Object: CellUnit: NoneRemarks: None59 A30808-X3247-B912-1-7618
  • 60. Information PM: SBS Key Performance IndicatorsSystem10 CCCH Load related Performance IndicatorsThe common control channels CCCH consist of a set of logical channels, which are used forcommon control signaling to start a connection setup: RACH MS requests a UL Random Access dedicated channel Channel from network CCCH Common AGCH answer to RACH, Access Grant dedicated signaling Control Channel Channels DL channel allocation PCH paging of a MS in a Paging Channel location area (MTC) NCH paging of MSs in a Notification voice group call Channel areaFig. 9 Overview Common Control ChannelsThe SBS supports several channel combinations resulting in different capacities for theCCCHs. 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 theCCCH. The downlink parts (AGCH, PCH) may need a higher capacity. Therefore, theconfiguration of CCCH is determined by the capacity needed for the downlink channels. TheRACH configuration is not critical.The PCH and the AGCH share the same TDMA frame mapping (modulo 51) when combinedonto a basic physical radio channel. PCH channels may be used as AGCH channels but notvice versa. However, to ensure a mobile a satisfactory access to the system, there is acontrol parameter (NBLKACGR) to define a fixed number of AGCH blocks in the 51multiframe (a block consists of 4 consecutive TDMA frames). This number reduces thenumber of available paging blocks.In all cells where the advanced speech call item (ASCI) service is enabled, a notificationchannel (NCH) is defined. A parameter (NOCHBLKN) indicates the number of CCCH blocksto be used for the NCH channel. This logical channel is mapped onto contiguous blocksreserved for AGCHs, i.e. if this NCH is used, it takes capacity from the blocks reserved forAGCH 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 theallocated channel combination looks like this: FCCH + SCH + BCCH + CCCH + 4 (SDCCH + SACCH) MBCCHCThe timeslot will then run in the 51-Multiframe organization:60 A30808-X3247-B912-1-7618
  • 61. Information PM: SBS Key Performance IndicatorsSystem F S BCCH CCCH F S CCCH CCCH F S SDCCH0 SDCCH1 F S SDCCH2 SDCCH3 F S SACCH0 SACCH1 I 1. 0 1 2 3 4 5 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 F S BCCH CCCH F S CCCH CCCH F S SDCCH0 SDCCH1 F S SDCCH2 SDCCH3 F S SACCH2 SACCH3 I 2. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 ‘downlink’ BCCH + CCCH + 4 SDCCH / 4, F = FCCH, S = SCH SDCCH3 R R SACCH2 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 1. 0 1 2 3 4 5 6 7 8 9 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 SDCCH3 R R SACCH0 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 2. 0 1 2 3 4 5 6 7 8 9 10 11 1213 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 ‘uplink’ R = RACH + SDCCH / 4Fig. 10 Structure for an exemplary common control channel combinationIn the downlink direction, for this example, there are 12 frames available for CCCH, whichcan be used as PCH, NCH, AGCH frames. But with the parameter NBLKACGR (number ofblocks reserved for AGCH) some blocks can be inhibited for paging. A CCCH block consistsof 4 consecutive TDMA frames (see above figure).In the uplink direction, for this example, there are 27 frames available for CCCH, which canbe used as RACH frames.Note:The NCH channel is not considered, since Notification messages are used only by a verylimited number of customers. Additionally, the portion of NCH channels is fixed byconfiguration and does not depend on any traffic load situations. Therefore, for dimensioningof the required downlink capacity of CCCH channels, only the load of the AGCH and PCH isimportant. If NCH channels are configured but not used (accessed), this capacity is availablefor AGCH channels.61 A30808-X3247-B912-1-7618
  • 62. Information PM: SBS Key Performance IndicatorsSystem10.1 PCH load of downlink CCCH channelsLong name: PCH load of downlink CCCH channelsShort name: CCCHLDPCHDescription: This indicator will give you the PCH load of downlink CCCH channels, by meaning the number of accessed PCH frames over the air interface in relation to the number of defined CCCH frames downlink.Formula: Number of accessed PCH frames downlink CCCHLDPCH = Number of all defined CCCH frames downlink NTDMPCH[5] CCCHLDPCH = NDEFCCCH[2]Used param.: NTDMPCH[5], NDEFCCCH[2]Elem. Object: CellUnit: NoneRemarks: None10.2 AGCH load of downlink CCCH channelsLong name: AGCH load of downlink CCCH channelsShort name: CCCHLDAGCHDescription: This indicator will give you the AGCH load of downlink CCCH channels, by meaning the number of accessed AGCH frames over the air interface in relation to the number of defined CCCH frames downlink.Formula: Number of accessed AGCH frames downlink CCCHLDAGCH = Number of all defined CCCH frames downlink NTDMAGCH[1,2] CCCHLDAGCH = NDEFCCCH[2]Used param.: NTDMAGCH[1,2], NDEFCCCH[2]Elem. Object: CellUnit: NoneRemarks: None62 A30808-X3247-B912-1-7618
  • 63. Information PM: SBS Key Performance IndicatorsSystem10.3 CCCH load downlinkLong name: CCCH load downlinkShort name: CCCHLDDLDescription: This indicator will give you the CCCH load downlink, by meaning the number of accessed frames (PCH, AGCH) over the air interface in relation to the number of defined CCCH frames downlink.Formula: Number of accessed CCCH frames downlink CCCHLDDL = Number of all defined CCCH frames downlink NTDMPCH[5]+ NTDMAGCH[1,2] CCCHLDDL = NDEFCCCH[2]Used param.: NTDMPCH[5], NTDMAGCH[1,2], NDEFCCCH[2]Elem. Object: CellUnit: NoneRemarks: The NCH channel is not considered, since Notification messages are used only by a very limited number of customers. Additionally, the portion of NCH channels is fixed by configuration and does not depend on any traffic load situations. Therefore, for dimensioning of the required downlink capacity of CCCH channels, only the load of the AGCH and PCH is important. If NCH channels are configured but not used (accessed), this capacity is available for AGCH channels.10.4 CCCH load uplinkLong name: CCCH load uplinkShort name: CCCHLDULDescription: This indicator will give you the CCCH load uplink, by meaning the number of received (RACH) over the air interface in relation to the number of defined CCCH frames uplink.Formula: Number of received RACH frames uplink CCCHLDUL = Number of all defined CCCH frames uplink NACSUCPR[3] + NINVRACH[1,2,3] CCCHLDUL = NDEFCCCH[1]Used param.: NACSUCPR[3], NINVRACH[1,2,3], NDEFCCCH[1]Elem. Object: CellUnit: NoneRemarks: None63 A30808-X3247-B912-1-7618
  • 64. Information PM: SBS Key Performance IndicatorsSystem10.5 PCH Loss RateLong name: PCH Loss RateShort name: PCHLossRateDescription: This indicator will give you the PCH Loss Rate by meaning the number of discarded subscriber pagings from the PCH queue related to the total number of subscriber pagings for transmission at the BTS. Each paging queue place in the BTS can be seized by one PAGING REQUEST message, which itself can contain the mobile subscriber identities (IMSI or TMSI) of up to 4 mobile subscribers simultaneously. This means that the PAGING REQUEST message can contain the mobile subscriber identities from up to 4 PAGING commands that were received from the BSC before. Whereas a discarded paging is always represented by one PAGING command message, that includes one TMSI or IMSI, which could not be placed in any BTS paging queue and therefore had to be discarded.Formula: NTDMPCH[3, 4] PCHLossRat e = NTDMPCH [1 .. 4 ]Used param.: NTDMPCH[1..4]Elem. Object: CellUnit: NoneRemarks: None10.6 AGCH Loss RateLong name: AGCH Loss RateShort name: AGCHLossRateDescription: This indicator will give you the AGCH Loss Rate by meaning the number of discarded messages from the AGCH queue related to the total number of messages for transmission over the AGCH at the BTS.Formula: NTDMAGCH[3 ,4] AGCHLossRa te = NTDMAGCH [1 .. 4 ]Used param.: NTDMAGCH[1..4]Elem. Object: CellUnit: NoneRemarks: None64 A30808-X3247-B912-1-7618
  • 65. Information PM: SBS Key Performance IndicatorsSystem10.7 Invalid RACH RateLong name: Invalid RACH RateShort name: InvRACHRateDescription: This indicator will give you the invalid RACH Rate by meaning the number of messages received on the RACH, which did not result in a CHANNEL REQUIRED message toward the BSC (e.g. Signal level too week) and therefore did not result in an SDCCH assignment attempt.Formula: NINVRACH[1 ..3] InvRACHRat e = NINVRACH [1 .. 3] + NACSUCPR [3]Used param.: NINVRACH[1..3], NACSUCPR[3]Elem. Object: CellUnit: NoneRemarks: It has to be considered that the NINVRACH does not represent the total amount of all RACH signals that are discarded by the BTS! The Um layer 1 SW subsystem of the BTS continuously observes the signals received on the RACH slots. As even without any real MS RACH access there are always at least some ‘noise’ signals on the RACH, the task of the BTS layer 1 SW subsystem is to evaluate the received signal with respect to specific criteria that classify a signal as noisy or not noisy. These checks are performed prior to the evaluation of the criteria excessive distance, signal level too weak and CRC checksum error. Signals classified as noisy are immediately discarded and are not counted by NINVRACH (!). An increase of the NINVRACH counts and thus an increase of the ‘Invalid RACH Rate’ as calculated by the above formula does not mean a worse performance of the BTS. Instead, variations of the NINVRACH counts and variations of the Invalid RACH Rate between the different sites mainly depend on the radio environment conditions, i.e. increased values of NINVRACH and this KPI are no indication for a poor system performance. Moreover, both figures depend on characteristics of the used TRX HW (old HW usually shows lower counter values, although the performance of the newer HW is better!). For this reason the above formula cannot be regarded as a ‘System Performance Indicator’ but rather provides, taking into account which TRX HW is used, a rough idea about the radio conditions that influence the RACH performance! For further details please refer to the NINVRACH counter description in the document PM:SBS Counter.65 A30808-X3247-B912-1-7618
  • 66. Information PM: SBS Key Performance IndicatorsSystem11 PCCH Load related Performance IndicatorsThe packet common control channels PCCCH consist of a set of logical channels, which areused for common control signaling to start a GPRS-connection setup: PRACH GPRS-MS access UL Packet Random request for UL packet Access Channel data transmission PCCCH Packet PAGCH answer to PRACH, Packet Access dedicated signaling Common Grant Channel Control DL channel allocation Channels PPCH paging of a GPRS- Packet Paging MS in a location Channel area (MTC) PNCH notification for Packet Notification GPRS-MSs for PtM Channel transactionFig. 11 Overview Packet Common Control ChannelsThe SBS supports several channel combinations resulting in different utilization for thePCCCHs. 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 PCCCHis 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) whencombined 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 definea fixed number of PAGCH blocks in the 52 multiframe. This number reduces the number ofavailable paging blocks.A packet notification channel (PNCH), belonging to PCCCHs, is defined for notifying a groupof MSs of an upcoming Point-to-Multipoint (PtM) transaction. This logical channel is mappedonto 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 stealingmode on the same PDCH.For the number of defined PCCCH frames, the following is defined:66 A30808-X3247-B912-1-7618
  • 67. Information PM: SBS Key Performance IndicatorsSystem PDCH with the 52-Multiframe Structure 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48 50 Block 0 Block 1 Block 2 T Block 3 Block 4 Block 5 I Block 6 Block 7 Block 8 T Block 9 Block 10 Block 11 I A A TA Timing Advance control frame I Search frame for measurements Example for a PCCCH Configuration BSPBBLK = 2 (PBCCH blocks) 0 1 2 3 4 5 6 7 8 9 10 11 BPAGCHR = 3 (no paging on these blocks) Available Paging BlocksFig. 12 Structure for an exemplary packet common control channel combinationThe number of all defined PCCCH channels is dependent on the channel configurationdefined by the parameter GDCH (GPRSDedicatedChannel). It can have the values PCCCHand PBCCH.If PCCCH is selected, then 12 blocks are available for PCCCH (see above figure). A blockconsists of 4 consecutive TDMA frames.If PBCCH is selected, then additionally the parameter BSPBBLK (number of blocks allocatedfor PBCCH) is relevant, because it reduces the number of available PCCCH blocks by thenumber 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 forPAGCH, PDTCH, PACCH) some blocks can be inhibited for paging.In uplink direction all defined PCCCH blocks can be used as PRACH, PDTCH, PACCH. Butwith the parameter BPRACHR (number of blocks reserved for the PRACH channel) thenumber 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 callprocessing 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 withcommon control channels.Therefore, for dimensioning of the required capacity of PCCCH channels, only the load of thePAGCH and PPCH (downlink) and PRACH (uplink) is important.67 A30808-X3247-B912-1-7618
  • 68. Information PM: SBS Key Performance IndicatorsSystem11.1 PPCH load of downlink PCCCH channelsLong name: PPCH load of downlink PCCCH channelsShort name: PCCCHLDPPCHDescription: This indicator will give you the PPCH load of downlink PCCCH channels, by meaning the number of accessed PPCH frames over the air interface in relation to the number of defined PCCCH frames downlink.Formula: Number of accessed PPCH frames downlink PCCCHLDPPCH = Number of all defined PCCCH frames downlink NTDMPPCH[1,2] PCCCHLDPPCH = NDEFPCCC[2]Used param.: NTDMPPCH[1,2], NDEFPCCC[2]Elem. Object: CellUnit: NoneRemarks: None11.2 PAGCH load of downlink PCCCH channelsLong name: PAGCH load of downlink PCCCH channelsShort name: PCCCHLDPAGCHDescription: This indicator will give you the PAGCH load of downlink PCCCH channels, by meaning the number of accessed PAGCH frames over the air interface in relation to the number of defined PCCCH frames downlink.Formula: Number of accessed PAGCH frames downlink PCCCHLDPAGCH = Number of all defined PCCCH frames downlink NTDMPAGC[1,2] PCCCHLDPAGCH = NDEFPCCC[2]Used param.: NTDMPAGC[1,2], NDEFPCCC[2]Elem. Object: CellUnit: NoneRemarks: None68 A30808-X3247-B912-1-7618
  • 69. Information PM: SBS Key Performance IndicatorsSystem11.3 PCCCH load downlinkLong name: PCCCH load downlinkShort name: PCCCHLDDLDescription: This indicator will give you the PCCCH load downlink, by meaning the number of accessed frames (PPCH, PAGCH) over the air interface in relation to the number of defined PCCCH frames downlink.Formula: Number of accessed PCCCH frames downlink PCCCHLDDL = Number of all defined PCCCH frames downlink NTDMPPCH[1,2] + NTDMPAGC[1,2] PCCCHLDDL = NDEFPCCC[2]Used param.: NTDMPPCH[1,2], NTDMPAGC[1,2], NDEFPCCC[2]Elem. Object: CellUnit: NoneRemarks: 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 important11.4 PCCCH load uplinkLong name: PCCCH load uplinkShort name: PCCCHLDULDescription: This indicator will give you the PCCCH load uplink, by meaning the number of received (PRACH) over the air interface in relation to the number of defined PCCCH frames uplink.Formula: Number of received PRACH frames uplink PCCCHLDUL = Number of all defined PCCCH frames uplink NSAPRACH[1] PCCCHLDUL = NDEFPCCC[1]Used param.: NSAPRACH[1], NDEFPCCC[1]Elem. Object: CellUnit: NoneRemarks: The following channels are not considered: PDTCH since these channels are mapped onto PCCCH channels (uplink/downlink) only, if there is spare capacity, i.e. in case of PCCCH channels being not fully loaded with common control channels. Only the load of the PRACH is important.69 A30808-X3247-B912-1-7618
  • 70. Information PM: SBS Key Performance IndicatorsSystem11.5 PPCH Loss RateLong name: PPCH Loss RateShort name: PPCHLossRateDescription: This indicator will give you the PPCH Loss Rate by meaning the number of discarded subscriber pagings from the PPCH queue related to the total number of subscriber pagings for transmission at the BSC. Each Packet Paging Request message contains one or more mobile subscriber identities (IMSI or TMSI), by meaning the number of discarded paging messages correspond to the minimum number of discarded subscriber pagings.Formula: NTDMPPCH[3 ,4] PPCHLossRa te = NTDMPPCH [1 .. 4 ]Used param.: NTDMPPCH[1..4]Elem. Object: CellUnit: NoneRemarks: None11.6 PAGCH Loss RateLong name: PAGCH Loss RateShort name: PAGCHLossRateDescription: This indicator will give you the PAGCH Loss Rate by meaning the number of discarded messages from the PAGCH queue related to the total number of messages for transmission over the PAGCH at the BTS.Formula: NTDMPAGC[2 ] PAGCHLossR ate = NTDMPAGC [1 .. 2 ]Used param.: NTDMPAGC[1..2]Elem. Object: CellUnit: NoneRemarks: None70 A30808-X3247-B912-1-7618
  • 71. Information PM: SBS Key Performance IndicatorsSystem11.7 Invalid PRACH RateLong name: Invalid PRACH RateShort name: InvPRACHRateDescription: This indicator will give you the invalid PRACH Rate by meaning the number of messages received on the PRACH, which did not result in a Packet CHANNEL REQUIRED message toward the BSC (e.g. Signal level too week) and therefore did not result in an assignment of a TBF.Formula: NSAPRACH [ 2 .. 4 ] (a) InvPRACHRa te = NSAPRACH[1 ..4]Used param.: NSAPRACH[1..4]Elem. Object: CellUnit: NoneRemarks: This formula will be valid starting with late BR8.0, due to a correction for measurement type NINVPRACH and NSAPRACH. For the second It has to be considered that the NSAPRACH does not represent the total amount of all PRACH signals that are discarded by the BTS! The Um layer 1 SW subsystem of the BTS continuously observes the signals received on the PRACH slots. As even without any real MS PRACH access there are always at least some ‘noise’ signals on the PRACH, the task of the BTS layer 1 SW subsystem is to evaluate the received signal with respect to specific criteria that classify a signal as noisy or not noisy. These checks are performed prior to the evaluation of the criteria excessive distance, signal level too weak and CRC checksum error. Signals classified as noisy are immediately discarded and are not counted by NSAPRACH (!). An increase of the NSAPRACH counts and thus an increase of the ‘Invalid PRACH Rate’ as calculated by the above formula does not mean a worse performance of the BTS. Instead, variations of the NSAPRACH counts and variations of the Invalid PRACH Rate between the different sites mainly depend on the radio environment conditions, i.e. increased values of NSAPRACH and this KPI are no indication for a poor system performance. Moreover, both figures depend on characteristics of the used TRX HW (old HW usually shows lower counter values, although the performance of the newer HW is better!). For this reason the above formula cannot be regarded as a ‘System Performance Indicator’ but rather provides, taking into account which TRX HW is used, a rough idea about the radio conditions that influence the PRACH performance! For further details please refer to the NSAPRACH counter description in the document PM:SBS Counter.71 A30808-X3247-B912-1-7618
  • 72. Information PM: SBS Key Performance IndicatorsSystem12 Service related Performance Indicators12.1 Total number of Service RequestsLong name: (a) Total number of service requestsShort name: (a) ServRequestsDescription: This indicator provides the total number of Service requests including all service types, triggered by CHANNEL ALLOCATION REQUEST.Formula: (a) ServRequests = CHALNHLY[19..27]Used param.: CHALNHLY[19..27]Elem. Object: BTSUnit NoneRemarks: None12.2 Service Request Distribution RateLong name: (a) SDCA Distribution for Signaling (SDCCH) (b) SDCA Distribution for CS speech (c) SDCA Distribution for CS speech AMR FR (d) SDCA Distribution for CS speech AMR HR (e) SDCA Distribution for CS data (f) SDCA Distribution for HSCSD (g) SDCA Distribution for GPRS (h) SDCA Distribution for EGPRS (i) SDCA Distribution for ASCIShort name: (a) SDCADistSignal (b) SDCADistCS (c) SDCADistAMRFR (d) SDCADistAMRHR (e) SDCADistCSData (f) SDCADistHSCSD (g) SDCADistGPRS (h) SDCADistEGPRS (i) SDCADistASCIDescription: 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[1 9] (a) SDCADistSignal = ServRequests CHALNHLY[2 0] (b) SDCADistCS= ServRequests72 A30808-X3247-B912-1-7618
  • 73. Information PM: SBS Key Performance IndicatorsSystem CHALNHLY[2 1] (c) SDCADistAMRFR = ServRequests CHALNHLY[2 2] (d) SDCADistAMRHR = ServRequests CHALNHLY[2 3] (e) SDCADistCSData = ServRequests CHALNHLY[2 4] (f) SDCADistHSCSD = ServRequests CHALNHLY[2 5] (g) SDCADistGP = RS ServRequests CHALNHLY[2 6] (h) SDCADistEGPRS = ServRequests CHALNHLY[2 7] (i) SDCADistAS = CI ServRequestsUsed param.: CHALNHLY[19..27], ServRequests(12.1(a))Elem. Object: BTSUnit NoneRemarks: 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 available12.3 Rate of Service Requests served in the highest layerLong name: (a) Rate of Service Requests served in highest layerShort name: (a) ServRequestsRateDescription: These indicators will give you the Service Request Success Rate. All Service Channel Requests served in the highest layer are considered.Formula: CHALNHLY[1 ..18] tRate =1 − (a) ServReques ServRequestsUsed param.: CHALNHLY[1..18], ServRequests(12.1 (a))Elem. Object: BTSUnit NoneRemarks: Service requests not supported and not served in the highest layer are subtracted.73 A30808-X3247-B912-1-7618
  • 74. Information PM: SBS Key Performance IndicatorsSystem13 Feature related Performance Indicators13.1 Abis pool supervisionLong name: Mean number of defined Abis subchannels Mean number of available Abis subchannels Abis subchannel availability rate Number of attempted Abis subchannel seizures Number of successful Abis subchannel seizures Number of unsuccessful Abis subchannel seizure attempts Abis Pool Traffic offered Abis Pool Traffic carried Abis Pool Traffic lost Abis Pool Loss Rate Abis Pool Blocking Probability Abis Pool Traffic Utilisation Abis Pool Peak Traffic UtilisationShort name: AbisPDefCh AbisPAvailCh AbisPAvailRate AbisPAttSeiz AbisPSuccSeiz AbisPUnsuccSeiz AbisPTrOff AbisPTrCar AbisPTrLost AbisPLossRate AbisPBlockProb AbisPTrafUtil AbisPTrafUtilPeakDescription: With the Abis Pool Supervision measurements it is possible to evaluate the most important load, capacity and quality related KPIs for the Abis Interface.Formula: AbisPDefCh = ABISPSUP[1] AbisPAvail Ch = ABISPSUP[2 ] ABISPSUP[2] AbisPAvailRate = ABISPSUP[1] AbisPAttSeiz = ABISPSUP[6] + ABISPSUP[7] AbisPSuccSeiz = ABISPSUP[6] AbisPUnsuccSeiz = ABISPSUP[7] ABISPSUP[7] AbisPTrOff = ABISPSUP[3] * (1 + ) ABISPSUP[6]74 A30808-X3247-B912-1-7618
  • 75. Information PM: SBS Key Performance IndicatorsSystem AbisPTrCar = ABISPSUP[3] ABISPSUP[7] AbisPTrLost = ABISPSUP[3] * ABISPSUP[6] ABISPSUP[7] AbisPLossRate = ABISPSUP[6] + ABISPSUP[7] ABISPSUP[5] AbisPBlockProb = Granularity Period ABISPSUP[3] AbisPTrafUtil = ABISPSUP[1] ABISPSUP[4 ] AbisPTrafU tilPeak = ABISPSUP[1 ]Used param.: ABISPSUP[1..7]Elem. Object: CellUnit: NoneRemarks: None75 A30808-X3247-B912-1-7618
  • 76. Information PM: SBS Key Performance IndicatorsSystem14 Handover related Performance Indicators14.1 Intra Cell Handovers14.1.1 Handover Success RateLong name: (a) Number of Intra Cell Handover Attempts (b) Number of Intra Cell Handover Successes (c) Intra Cell Handover Success Rate (d) Intra Cell Handover Success Rate per causeShort name: (a) IntraCellHOAtt (b) IntraCellHOSucc (c) IntraCellHOSuccRate (d) IntraCellHOSuccRateCDescription: These indicators will give you the number and rate of successful Intra Cell Handovers. The indicators on the HO success rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause valueFormula: (a) IntraCellHOAtt = ATINHIAC[1..14] (b) IntraCellHOSucc = SINTHITA[1..14] IntraCellHOSucc (c) IntraCellHOSuccRate = IntraCellHOAtt SINTHITA[c ] (d) IntraCellH OSuccRateC [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/EFRUsed param.: SINTHITA[1..14], ATINHIAC[1..14]76 A30808-X3247-B912-1-7618
  • 77. Information PM: SBS Key Performance IndicatorsSystemElem. Object: CellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas.14.1.2 Handover Failure RateLong name: (a) Number of Intra Cell Handover Failures (b) Intra Cell Handover Failure Rate (c) Intra Cell Handover Failure Rate per Handover CauseShort name: (a) IntraCellHOFail (b) IntraCellHOFailRate (c) IntraCellHOFailRateCDescription: These indicators will give you the number and rate of Intra Cell Handover Failures by meaning of unsuccessful Handovers without loss of MS connection because of reversion to old channel. The indicators on the HO failure rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause valueFormula: (a) IntraCellHOFail = UNINHOIA[1..14] IntraCellHOFail (b) IntraCellHOFailRate = IntraCellHOAtt UNINHOIA[c] (c) IntraCellHOFailRateC[c] = ATINHIAC[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/EFRUsed param.: UNINHOIA[1..14], , ATINHIAC[1..14], IntraCellHOAtt (14.1.1(a))Elem. Object: CellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas.77 A30808-X3247-B912-1-7618
  • 78. Information PM: SBS Key Performance IndicatorsSystem14.1.3 Handover Drop RateLong name: (a) Number of Intra Cell Handover Drops (b) Intra Cell Handover Drop Rate (c) Intra Cell Handover Drop Rate per Handover CauseShort name: (a) IntraCellHODrop (b) IntraCellHODropRate (c) IntraCellHODropRateCDescription: 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 valueFormula: (a) IntraCellHODrop = UNIHIALC[1] IntraCellHODrop (b) IntraCellHODropRate = IntraCellHOAtt ATINHIAC[c] - SINTHITA[c] - UNINHOIA[c] (c) IntraCellHODropRateC[c] = ATINHIAC[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/EFRUsed param.: UNIHIALC[1], ATINHIAC[1..14], SINTHITA[1..14], UNINHOIA[1..14], IntraCellHOAtt (14.1.1(a))Elem. Object: CellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas. User release during Handover will lead to very small systematic errors.78 A30808-X3247-B912-1-7618
  • 79. Information PM: SBS Key Performance IndicatorsSystem14.1.4 Handover DistributionLong name: (a) Intra Cell Handover Distribution per Handover causeShort name: (a) IntraCellHODistDescription: These indicators will give you the Intra Cell Handover Distribution for analyzing the reason (=cause) for started Intra Cell Handovers.Formula: ATINHIAC[c ] (a) IntraCellH ODist[c] = IntraCellH OAtt with c for the HO cause number: c=1 uplink quality c=2 downlink quality c=3 inner to complete area c=4 complete to inner area c=5 near to far area c=6 far to near area c=7 forced handover due to O&M c=8 TCH/F to TCH/H due to AMR c=9 TCH/H to TCH/F due to AMR c=10 forced intracell handover due to enhanced pairing c=11 forced intracell handover due to preferred TRX c=12 forced HO due to Multislot calls c=13 compression HO from FR/EFR to HR c=14 decompression HO from HR to FR/EFRUsed param.: ATINHIAC[1..14], IntraCellHOAtt (14.1.1(a))Elem. Object: CellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas.79 A30808-X3247-B912-1-7618
  • 80. Information PM: SBS Key Performance IndicatorsSystem14.1.5 SDCCH Handover Success RateLong name: (a) Number of Intra Cell SDCCH Handover Attempts (b) Number of Intra Cell SDCCH Handover Successes (c) Intra Cell SDCCH Handover Success RateShort name: (a) IntraCellSDHOAtt (b) IntraCellSDHOSucc (c) IntraCellSDHOSuccRateDescription: These indicators will give you the rate of successful Intra Cell SDCCH Handovers.Formula: (a) IntraCellSDHOAtt = AISHINTR[1] (b) IntraCellSDHOSucc = SISHINTR[1] IntraCellSDHOSucc (c) IntraCellSDHOSuccRate = IntraCellSDHOAttUsed param.: AISHINTR[1], SISHINTR[1]Elem. Object: CellUnit: NoneRemarks: None14.1.6 SDCCH Handover Failure RateLong name: (a) Number of Intra Cell SDCCH Handover Failures (b) Intra Cell SDCCH Handover Failure RateShort name: (a) IntraCellSDHOFail (b) IntraCellSDHOFailRateDescription: These indicators will give you the number and rate of Intra Cell SDCCH Handover Failures by meaning of unsuccessful SDCCH Handovers without loss of MS connection because of reversion to old cell.Formula: (a) IntraCellSDHOFail = UISHINTR[ 1] IntraCellSDHOFail (b) IntraCellSDHOFailRate = IntraCellSDHOAttUsed param.: UISHINTR[1], IntraCellSDHOAtt (14.1.5(a))Elem. Object: CellUnit: NoneRemarks: None80 A30808-X3247-B912-1-7618
  • 81. Information PM: SBS Key Performance IndicatorsSystem14.1.7 SDCCH Handover Drop RateLong name: (a) Number of Intra Cell SDCCH Handover Drops (b) Intra Cell SDCCH Handover Drop RateShort name: (a) IntraCellSDHODrop (b) IntraCellSDHODropRateDescription: These indicators will give you the number and rate of Intra Cell SDCCH Handover Drops by meaning of unsuccessful SDCCH Handovers with loss of MS connection.Formula: (a) IntraCellSDHODrop = UISHIALC[1] IntraCellSDHODrop (b) IntraCellSDHODropRate = IntraCellSDHOAttUsed param.: UISHIALC[1], IntraCellHOAtt (14.1.5(a))Elem. Object: CellUnit: NoneRemarks: None81 A30808-X3247-B912-1-7618
  • 82. Information PM: SBS Key Performance IndicatorsSystem14.2 Inter Cell Intra BSC Handovers14.2.1 Handover Success RateLong name: (a) Number of Inter Cell Intra BSC Handover Attempts (b) Number of Inter Cell Intra BSC Handover Successes (c) Inter Cell Intra BSC Handover Success Rate (d) Inter Cell Intra BSC Handover Success Rate per causeShort name: (a) InterCellHOAtt (b) InterCellHOSucc (c) InterCellHOSuccRate (d) InterCellHOSuccRateCDescription: 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: 11 3 (a) InterCellHOAtt[n] = ∑ ∑ AOUINIRH[n * 44 + i * 11 + c] C =1 i =0 11 3 (b) InterCellHOSucc[n] = ∑ ∑ SOUINIRH[n * 44 + i * 11 + c] C =1 i = 0 InterCellH OSucc[n] (c) InterCellH OSuccRate[ n] = InterCellH OAtt[n] 3 ∑ SOUINIRH[n * 44 + i *11 + c] (d) InterCellHOSuccRateC[n, c] = i =0 3 ∑ AOUINIRH[n * 44 + i *11 + c] i =0 with n for the number of the neighbourcell relation (n=0..31) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to O&M c=9 traffic c=10 fast uplink c=11 forced handover due to preemption with i for the type of cell area: i=0 complete-complete area82 A30808-X3247-B912-1-7618
  • 83. Information PM: SBS Key Performance IndicatorsSystem i=1 complete-inner area i=2 inner-complete area i=3 inner-inner areaUsed param.: AOUINIRH[all], SOUINIRH[all]Elem. Object: NeighbourcellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas.83 A30808-X3247-B912-1-7618
  • 84. Information PM: SBS Key Performance IndicatorsSystem14.2.2 Handover Failure RateLong name: (a) Number of Inter Cell Intra BSC Handover Failures (b) Inter Cell Intra BSC Handover Failure Rate (c) Inter Cell Intra BSC Handover Failure Rate per Handover CauseShort name: (a) InterCellHOFail (b) InterCellHOFailRate (c) InterCellHOFailRateCDescription: These indicators will give you the number and rate of Inter Cell Intra BSC Handover Failures by meaning of unsuccessful Handovers without loss of MS connection because of reversion to old cell. The indicators on the HO failure rate are provided as an aggregation over all HO causes and are additionally provided per HO cause valueFormula: 11 (a) InterCellHOFail[n] = ∑ UNINHOIE [n *11 + c] C =1 InterCellHOFail[n] (b) InterCellHOFailRate[n] = InterCellHOAtt[n] UNINHOIE [n * 11 + c] (c) InterCellHOFailRateC[n, c] = 3 ∑ AOUINIRH[n * 44 + i * 11 + c] i=0 with n for the number of the neighbourcell relation (n=0..31) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to O&M c=9 traffic c=10 fast uplink c=11 forced handover due to preemption with i for the type of cell area: i=0 complete-complete area i=1 complete-inner area i=2 inner-complete area i=3 inner-inner areaUsed param.: UNINHOIE[all], AOUINIRH[all], InterCellHOAtt[all] (14.2.1(a))Elem. Object: NeighbourcellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas.84 A30808-X3247-B912-1-7618
  • 85. Information PM: SBS Key Performance IndicatorsSystem14.2.3 Handover Drop RateLong name: (a) Number of Inter Cell Intra BSC Handover Drops (b) Inter Cell Intra BSC Handover Drop Rate (c) Inter Cell Intra BSC Handover Drop Rate per causeShort name: (a) InterCellHODrop (b) InterCellHODropRate (c) InterCellHODropRateCDescription: These indicators will give you the number and rate of Inter Cell Handover Drops per neighbour cell by meaning of unsuccessful Handovers with loss of MS connection. The indicators on the HO drop rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause valueFormula: (a) InterCellHODrop[n] = InterCellHOAtt[n] - InterCellHOSucc[n] - InterCellHOFail[n] InterCellH ODrop[n] (b) InterCellH ODropRate[ n] = InterCellH OAtt[n] InterCellHODropRateC[n, c] = 3 (c) ∑ (AOUINIRH - SOUINIRH)[n * 44 + i *11 + c] - UNINHOIE[n *11 + c] i =0 3 ∑ AOUINIRH[n* 44 + i *11 + c] i =0 with n for the number of the neighbourcell relation (n=0..31) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to O&M c=9 traffic c=10 fast uplink c=11 forced handover due to preemption with i for the type of cell area: i=0 complete-complete area i=1 complete-inner area i=2 inner-complete area i=3 inner-inner area85 A30808-X3247-B912-1-7618
  • 86. Information PM: SBS Key Performance IndicatorsSystemUsed param.: AOUINIRH[all], SOUINIRH[all], UNINHOIE[all], InterCellHOAtt[all] (14.2.1(a)), InterCellHOSucc[all] (14.2.1(b)), InterCellHOFail[all] (14.2.2(a))Elem. Object: NeighbourcellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas. User release during Handover will lead to systematic errors.86 A30808-X3247-B912-1-7618
  • 87. Information PM: SBS Key Performance IndicatorsSystem14.2.4 Handover DistributionLong name: (a) Inter Cell Intra BSC Handover Distribution (b) Imperative Inter Cell Handover RateShort name: (a) InterCellHODist (b) ImpInterCellHORateDescription: These indicators will give you the Inter Cell Intra BSC Handover Distribution for analyzing the reason (cause) for started Inter Cell Intra BSC Handovers. Imperative handovers are not whished but rather reflect possible problems in the network topologyFormula: 3 ∑ AOUINIRH[n* 44 + i *11 + c] (a) InterCellHODist[n, c] = i =0 InterCellHOAtt[n] 5 3 ∑ ∑ AOUINIRH[n * 44 + i * 11 + c] (b) ImpInterCe llHORate[n ] = C =1 i = 0 InterCellH OAtt[n] with n for the number of the neighbourcell relation (n=0..31) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to O&M c=9 traffic c=10 fast uplink c=11 forced handover due to preemption with i for the type of cell area: i=0 complete-complete area i=1 complete-inner area i=2 inner-complete area i=3 inner-inner areaUsed param.: AOUINIRH[all], InterCellHOAtt (14.2.1(a))Elem. Object: NeighbourcellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas.87 A30808-X3247-B912-1-7618
  • 88. Information PM: SBS Key Performance IndicatorsSystem14.2.5 Incoming Handover Success RateLong name: Inter Cell Intra BSC Incoming Handover Success RateShort name: InterCellIncHOSuccRateDescription: This indicator will give you the rate of successful Inter Cell Intra BSC Incoming Handovers per neighbour cell relation.Formula: SININIRH[n] InterCellIncHOSuccRate[n] = AININIRH[n] with n for the nth number of neighbourcell relation (n=0..31)Used param.: SININIRH[1..32], AININIRH[1..32]Elem. Object: NeighbourcellUnit: NoneRemarks: SDCCH handovers are also increment in the counters used for this formula and that fact can lead to systematic errors.14.2.6 SDCCH Handover Success RateLong name: (a) Number of Inter Cell SDCCH Handover Attempts (b) Number of Inter Cell SDCCH Handover Successes (c) Inter Cell SDCCH Handover Success RateShort name: (a) InterCellSDHOAtt (b) InterCellSDHOSucc (c) InterCellSDHOSuccRateDescription: These indicators will give you the rate of successful Inter Cell SDCCH Handovers.Formula: (a) InterCellSDHOAtt = AISHINTE[1] (b) InterCellSDHOSucc = SISHINTE[1] InterCellSDHOSucc (c) InterCellSDHOSuccRate = InterCellSDHOAttUsed param.: AISHINTE[1], SISHINTE[1]Elem. Object: CellUnit: NoneRemarks: None88 A30808-X3247-B912-1-7618
  • 89. Information PM: SBS Key Performance IndicatorsSystem14.2.7 SDCCH Handover Failure RateLong name: Number of Inter Cell SDCCH Handover Failures Inter Cell SDCCH Handover Failure RateShort name: InterCellSDHOFail InterCellSDHOFailRateDescription: These indicators will give you the number and rate of Inter Cell SDCCH Handover Failures by meaning of unsuccessful SDCCH Handovers without loss of MS connection because of reversion to old cell.Formula: InterCellSDHOFail = UISHINTE[ 1] InterCellSDHOFail InterCellSDHOFailRate = InterCellSDHOAttUsed param.: UISHINTE[1], InterCellSDHOAtt (14.2.6(a))Elem. Object: CellUnit: NoneRemarks: None14.2.8 SDCCH Handover Drop RateLong name: Number of Inter Cell SDCCH Handover Drops Inter Cell SDCCH Handover Drop RateShort name: InterCellSDHODrop InterCellSDHODropRateDescription: These indicators will give you the number and rate of Inter Cell SDCCH Handover Drops by meaning of unsuccessful SDCCH Handovers with loss of MS connection.Formula: InterCellSDHODrop = UISHIRLC[1] InterCellSDHODrop InterCellSDHODropRate = InterCellSDHOAttUsed param.: UISHIRLC[1], InterCellSDHOAtt (14.2.6(a))Elem. Object: CellUnit: NoneRemarks: None89 A30808-X3247-B912-1-7618
  • 90. Information PM: SBS Key Performance IndicatorsSystem14.3 Inter Cell Inter BSC Handovers14.3.1 Handover Success RateLong name: (a) Number of Inter Cell Inter BSC Handover Attempts (b) Number of Inter Cell Inter BSC Handover Successes (c) Inter Cell Inter BSC Handover Success Rate (d) Inter Cell Inter BSC Handover Success Rate per causeShort name: (a) InterBSCHOAtt (b) InterBSCHOSucc (c) InterBSCHOSuccRate (d) InterBSCHOSuccRateCDescription: 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 valueFormula: 10 (a) InterBSCHOAtt[n] = ∑ ATINBHDO [n * 10 + c] C =1 10 (b) InterBSCHOSucc[n] = ∑ SUINBHDO [n * 10 + c] C =1 InterBSCHOSucc[n] (c) InterBSCHOSuccRate[n ] = InterBSCHOAtt[n] SUINBHDO[n *10 + c] (d) InterBSCHOSuccRateC[n, c] = ATINBHDO[n *10 + c] with n for the number of the neighbourcell relation (n=0..31) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to O&M c=9 fast uplink c=10 forced handover due to preemptionUsed param.: ATINBHDO [all], SUINBHDO[all]Elem. Object: NeighbourcellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas.90 A30808-X3247-B912-1-7618
  • 91. Information PM: SBS Key Performance IndicatorsSystem14.3.2 Handover Failure RateLong name: (a) Number of Inter Cell Inter BSC Handover Failures (b) Inter Cell Inter BSC Handover Failure Rate (c) Inter Cell Inter BSC Handover Failure Rate per causeShort name: (a) InterBSCHOFail (b) InterBSCHOFailRate (c) InterBSCHOFailRateCDescription: These indicators will give you the rate and number of Inter Cell Inter BSC Handover. Failures by meaning of unsuccessful Handovers without loss of MS connection because of reversion to old cell. The indicators on the HO failure rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause valueFormula: 10 (a) InterBSCHOFail[n] = ∑ NRUNINHD [n * 10 + c] C =1 InterBSCHOFail[n] (b) InterBSCHOFailRate[n] = InterBSCHOAtt[n] NRUNINHD[n *10 + c ] (c) InterBSCHOFailRateC[n, c] = ATINBHDO[n *10 + c] with n for the number of the neighbourcell relation (n=0..31) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to O&M c=9 fast uplink c=10 forced handover due to preemptionUsed param.: NRUNINHD[all], ATINBHDO[all], InterBSCHOAtt[all] (14.3.1(a))Elem. Object: NeighbourcellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas.91 A30808-X3247-B912-1-7618
  • 92. Information PM: SBS Key Performance IndicatorsSystem14.3.3 Handover Drop RateLong name: (a) Number of Inter Cell Inter BSC Handover Drops (b) Inter Cell Inter BSC Handover Drop Rate (c) Inter Cell Inter BSC Handover Drop Rate per causeShort name: (a) InterBSCHODrop (b) InterBSCHODropRate (c) InterBSCHODropRateCDescription: These indicators will give you the rate and number of Inter Cell Inter BSC Handover Drops per neighbour cell by meaning of unsuccessful Handovers with loss of MS connection. The indicators on the HO drop rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause valueFormula: (a) InterBSCHODrop[n] = InterBSCHOAtt[n] - InterBSCHOSucc[n] - InterBSCHOFail[n] InterBSCHODrop[n] (b) InterBSCHODropRate[n] = InterBSCHOAtt[n] (ATINBHDO - SUINBHDO - NRUNINHD)[n * 10 + c] (c) InterBSCHODropRateC[n, c] = ATINBHDO[n * 10 + c] with n for the number of the neighbourcell relation (n=0..31) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to O&M c=9 fast uplink c=10 forced handover due to preemptionUsed param.: ATINBHDO[all], SUINBHDO[all], NRUNINHD[all], InterBSCHOAtt[all] (14.3.1(a)), InterBSCHOSucc[all] (14.3.1(b)), InterBSCHOFail[all] (14.3.2(a))Elem. Object: NeighbourcellUnit: NoneRemarks: SDCCH handovers are also incremented in this formulas. User release during Handover will lead to very small systematic errors.92 A30808-X3247-B912-1-7618
  • 93. Information PM: SBS Key Performance IndicatorsSystem14.3.4 Handover DistributionLong name: (a) Inter Cell Inter BSC Handover Distribution (b) Imperative Inter Cell Inter BSC Handover RateShort name: (a) InterBSCHODist (b) ImpInterBSCHORateDescription: These indicators will give you the Inter Cell Inter BSC Handover Distribution for analysing the reason for started Inter Cell Inter BSC Handovers. Imperative handovers are not whished but reflect possible problems in the network topologyFormula: ATINBHDO[n *10 + c] (a) InterBSCHODist[n, c] = InterBSCHOAtt[n] 5 ∑ ATINBHDO[n *10 + c] (b) ImpInterBSCHORate[n] = c =1 InterBSCHOAtt[n] with n for the number of the neighbourcell relation (n=0..31) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to O&M c=9 fast uplink c=10 forced handover due to preemptionUsed param.: ATINBHDO[all], InterBSCHOAtt[all] (14.3.1(a)),Elem. Object: NeighbourcellUnit: NoneRemarks: SDCCH handovers are also incremented in these formulas.93 A30808-X3247-B912-1-7618
  • 94. Information PM: SBS Key Performance IndicatorsSystem14.3.5 SDCCH Handover Success RateLong name: (a) Number of Inter Cell Inter BSC SDCCH Handover Attempts (b) Number of Inter Cell Inter BSC SDCCH Handover Successes (c) Inter Cell Inter BSC SDCCH Handover Success RateShort name: (a) InterBSCSDHOAtt (b) InterBSCSDHOSucc (c) InterBSCSDHOSuccRateDescription: These indicators will give you the rate of successful Inter Cell Inter BSC SDCCH Handovers.Formula: (a) InterBSCSDHOAtt = AOINTESH[1] (b) InterBSCSDHOSucc = SOINTESH[1] InterBSCSDHOSucc (c) InterBSCSDHOSuccRate = InterBSCSDHOAttUsed param.: AOINTESH[1], SOINTESH[1]Elem. Object: CellUnit: NoneRemarks: None14.3.6 SDCCH Handover Failure RateLong name: Number of Inter Cell Inter BSC SDCCH Handover Failures Inter Cell Inter BSC SDCCH Handover Failure RateShort name: InterBSCSDHOFail InterBSCSDHOFailRateDescription: These indicators will give you the number and rate of Inter Cell Inter BSC SDCCH Handover Failures by meaning of unsuccessful SDCCH Handovers without loss of MS connection because of reversion to old cell.Formula: InterBSCSDHOFail = UOINTESH[ 1] InterBSCSDHOFail InterBSCSDHOFailRate = InterBSCSDHOAttUsed param.: UOINTESH[1], InterBSCSDHOAtt (14.3.5(a))Elem. Object: CellUnit: NoneRemarks: None94 A30808-X3247-B912-1-7618
  • 95. Information PM: SBS Key Performance IndicatorsSystem14.3.7 SDCCH Handover Drop RateLong name: Number of Inter Cell Inter BSC SDCCH Handover Drops Inter Cell Inter BSC SDCCH Handover Drop RateShort name: InterBSCSDHODrop InterBSCSDHODropRateDescription: These indicators will give you the number and rate of Inter Cell Inter BSC SDCCH Handover Drops by meaning of unsuccessful SDCCH Handovers with loss of MS connection.Formula: InterBSCDHODrop = UMCSHLC[1 ] InterBSCSDHODrop InterBSCSDHODropRate = InterBSCSDHOAttUsed param.: UMCSHLC[1], InterBSCSDHOAtt (14.3.5(a))Elem. Object: CellUnit: NoneRemarks: None95 A30808-X3247-B912-1-7618
  • 96. Information PM: SBS Key Performance IndicatorsSystem14.4 Inter System Handover between GSM and UMTS14.4.1 Outgoing Inter System Handover Success RateLong name: (a) Outgoing Inter System Handover Attempts (b) Outgoing Inter System Handover Successes (c) Outgoing Inter System Handover Success Rate (d) Outgoing Inter System Handover Success Rate per causeShort name: (a) InterSysOtgHOAtt (b) InterSysOtgHOSucc (c) InterSysOtgHOSuccRate (d) InterSysOtgHOSuccRateCDescription: 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 valueFormula: 10 (a) InterSysOtgHOAtt[n] = ∑ ATOISHDO [n *10 + c] c =1 10 (b) InterSysOtgHOSucc[n] = ∑ SUOISHDO [n * 10 + c] c =1 InterSysOtgHOSucc[n] (c) InterSysOtgHOSuccRat e[n] = InterSysOtgHOAtt[n] SUOISHDO[n *10 + c] (d) InterSysOtgHOSuccRateC[n, c] = ATOISHDO[n *10 + c] with n for the number of the neighbourcell relation (n=0..63) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to pre-emption c=9 forced handover due to O&M intervention c=10 sufficient UMTS coverageUsed param.: ATOISHDO [all], SUOISHDO[all]Elem. Object: NeighbourcellUnit: NoneRemarks: None96 A30808-X3247-B912-1-7618
  • 97. Information PM: SBS Key Performance IndicatorsSystem14.4.2 Outgoing Inter System Handover Failure RateLong name: (a) Outgoing Inter System Handover Failure (b) Outgoing Inter System Handover Failure Rate (c) Outgoing Inter System Handover Failure Rate per causeShort name: (a) InterSysOtgHOFail (b) InterSysOtgFailRate (c) InterSysOtgFailRateCDescription: These indicators will give you the rate and number of Outgoing Inter System Handover Failures by meaning of unsuccessful Handovers without loss of MS connection because of reversion to old cell. The indicators on the HO failure rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause valueFormula: 10 (a) InterSysOtgHOFail[n] = ∑ UNOISHDO [n * 10 + c] c =1 InterSysOtgHOFail[n] (b) InterSysOtgHOFailRate[n] = InterSysOtgHOAtt[n] UNOISHDO[n *10 + c] (c) InterSysOtgHOFailRateC[n, c] = ATOISHDO[n *10 + c] with n for the number of the neighbourcell relation (n=0..63) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to pre-emption c=9 forced handover due to O&M intervention c=10 sufficient UMTS coverageUsed param.: UNOISHDO[all], ATOISHDO[all], InterSysOtgHOAtt[all] (14.4.1(a))Elem. Object: NeighbourcellUnit: NoneRemarks: None97 A30808-X3247-B912-1-7618
  • 98. Information PM: SBS Key Performance IndicatorsSystem14.4.3 Outgoing Inter System Handover Drop RateLong name: (a) Outgoing Inter System Handover Drops (b) Outgoing Inter System Handover Drop Rate (c) Outgoing Inter System Handover Drop Rate per causeShort name: (a) InterSysOtgHODrop (b) InterSysOtgHODropRate (c) InterSysOtgHODropRateCDescription: These indicators will give you the rate and number of Outgoing Inter System Handover Drops per neighbour cell by meaning of unsuccessful Handovers with loss of MS connection. The indicators on the HO drop rate are provided as an aggregation over all HO causes and are provided in addition separated per HO cause value.Formula: (a) InterSysOtgHODrop = InterSysOtgHOAtt - InterSysOtgHOSucc - InterSysOtgHOFail InterSysOtgHODrop (b) InterSysOtgHODropRate = InterSysOtgHOAtt (ATOISHDO - SUOISHDO - UNOISHDO)[n * 10 + c] (c) InterSysOtgHODropRateC[n, c] = ATOISHDO[n * 10 + c] with n for the number of the neighbourcell relation (n=0..63) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to pre-emption c=9 forced handover due to O&M intervention c=10 sufficient UMTS coverageUsed param.: ATOISHDO[all], SUOISHDO[all], UNOISHDO[all], InterSysOtgHOAtt[all] (14.4.1(a)), InterSYSHOSucc[all] (14.4.1(b)), InterSYSHOFail[all] (14.4.2(a))Elem. Object: NeighbourcellUnit: NoneRemarks: Systematic error: call release during HO is included in the formula98 A30808-X3247-B912-1-7618
  • 99. Information PM: SBS Key Performance IndicatorsSystem14.4.4 Outgoing Inter System Handover DistributionLong name: (a) Outgoing Inter Cell Inter System Handover Distribution (b) Outgoing Imperative Inter Cell Inter System Handover RateShort name: (a) InterSysOtgHODist (b) ImpInterSysOtgHORateDescription: These indicators will give you the Inter Cell Inter System Handover Distribution for analyzing the reason for started Inter Cell Inter System Handovers. Imperative handovers are not whished but reflect possible problems in the network topologyFormula: ATOISHDO[n *10 + c] (a) InterSysOtgHODist[n, c] = InterSysOtgHOAtt[n] 5 ∑ ATOISHDO[n *10 + c] (b) ImpInterSysOtgHORate[n] = c =1 InterSysOtgHOAtt[n] with n for the number of the neighbourcell relation (n=0..63) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance c=6 better cell c=7 directed retry c=8 forced handover due to pre-emption c=9 forced handover due to O&M intervention c=10 sufficient UMTS coverageUsed param.: ATOISHDO[all], InterSysOtgHOAtt[all] (14.4.1(a))Elem. Object: NeighbourcellUnit: NoneRemarks:99 A30808-X3247-B912-1-7618
  • 100. Information PM: SBS Key Performance IndicatorsSystem14.4.5 Incoming Inter System Handover Success RateLong name: (a) Successful Incoming Inter System HO from UMTS (b) Attempted Incoming Inter System HO from UMTS (c) Success Rate for Incoming Inter System HO from UMTSShort name: (a) InterSysIncHOSucc (b) InterSysIncHOAtt (c) InterSysIncHOSuccRateDescription: These indicators will give you the rate and number of successful Incoming Inter System HO from UMTS.Formula: (a) InterSysIncHOSucc = SUIISHDO [1] (b) InterSysIncHOAtt = RQIISHDO[1] InterSysIncHOSucc (c) InterSysIncHOSuccRate = InterSysIncHOAttUsed param.: RQIISHDO[1]: Number of requested incoming intersystem handovers SUIISHDO[1]: Number of successful incoming intersystem handoversElem. Object: BSCUnit: NoneRemarks:100 A30808-X3247-B912-1-7618
  • 101. Information PM: SBS Key Performance IndicatorsSystem14.5 Other Handover Performance Indicators14.5.1 Handovers per ErlanghourLong name: (a) Handover per ErlanghourShort name: (a) HOperErlhDescription: This indicator will give you the ratio between successful Handovers and the traffic in Erlanghour per cell. Aggregation over all neighbors of the observed cell and all HO causes is performedFormula: (a) HOperErlh = SINTHITA[all] + SINTHINT[all] + SUINBHDO[all] + SUOISHDO[all] 60 * MEBUSTCH [all] Granularit yUsed param.: SINTHITA[all], SINTHINT [all], SUINBHDO[all], SUOISHDO[all], MEBUSTCH[all], Granularity in minutesElem. Object: CellUnit: NoneRemarks: • 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 considered14.5.2 Handovers per Call RateLong name: (a) Handovers per Call RateShort name: (a) HOperCallRatioDescription: This indicator will give you the ratio between Handovers and successful Call Setups per cell. Aggregation over all neighbors of the observed cell and all HO causes is performedFormula: (a) HoperCallRatio = SINTHITA[all] + SINTHINT[all] + SUINBHDO[all] + SUOISHDO[all] TASSSUCC[2..5]Used param.: SINTHITA[all], SINTHINT [all], SUINBHDO[all], SUOISHDO[all], TASSSUCC[2..5],Elem. Object: CellUnit: NoneRemarks: • 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 considered101 A30808-X3247-B912-1-7618
  • 102. Information PM: SBS Key Performance IndicatorsSystem14.5.3 Successful Directed RetriesLong name: (a) Number of Successful Directed Retries to GSM target cell (b) Number of Successful Directed Retries to UMTStarget cellShort name: (a) NoSuccDirectedRetryGSM (b) NoSuccDirectedRetryUMTSDescription: This indicator will give you the number of successful outgoing Handovers due to directed retry (Inter and Intra BSC and Inters System) per GSM and per UMTS neighbour cell.Formula: (a) NoSuccDirectedRetryGSM[m] 3 = SUINBHDO [m * 10 + 7 ] + ∑ SOUINIRH [m * 44 + i * 11 + 7 ] i =0 (b) NoSuccDirectedRetryUMTS[n] = SUOISHDO[n * 10 + 7] with m for the mth number of GSM neighbourcell relation (m=0..31) with n for the nth number of UMTS neighbourcell relation (n=0..63) with i for the type of cell area: i=0 complete-complete area i=1 complete-inner area i=2 inner-complete area i=3 inner-inner areaUsed param.: SUINBHDO[m*10+7], SOUINIRH[m*44+i*11+7], SUOISHDO[n*10+7],Elem. Object: NeighbourcellUnit: NoneRemarks: Intersystem HO to UMTS are considered102 A30808-X3247-B912-1-7618
  • 103. Information PM: SBS Key Performance IndicatorsSystem14.5.4 Imperative Outgoing Handover RateLong name: (a) Imperative Outgoing Handover Rate for GSM target cell (b) Imperative Outgoing Handover Rate for UMTS target cellShort name: (a) ImpOutgHORateGSM (b) ImpOutgHORateUMTSDescription: This indicator will give you the rate of handovers due to Imperative reasons (namely UpLink/DownLink Strength and UpLink/DownLink Quality and Distance) from the total number of outgoing Handovers (Inter and Intra BSC and inter system HO to UMTS). The indicator is per GSM resp. per UMTS neighbour cellFormula: (a) ImpOutgHORateGSM[m]= 5 ⎛ 3 ⎞ ∑⎝ c =1 ⎜ ATINBHDO[m *10 + c] + ∑ AOUINIRH[m * 44 + i * 11 + c] ⎟ i =0 ⎠ InterBSCHOAtt[m] + InterCellHOAtt[m] 5 ∑ ATOISHDO[n * 10 + c] c =1 (b) ImpOutgHORateUMTS[n]= InterSysOt gHOAtt[n] with m for the mth number of GSM neighbourcell relation (m=0..31) with n for the nth number of UMTS neighbourcell relation (n=0..63) with c for the cause number: c=1 uplink quality c=2 downlink quality c=3 uplink strength c=4 downlink strength c=5 distance with i for the type of cell area: i=0 complete-complete area i=1 complete-inner area i=2 inner-complete area i=3 inner-inner areaUsed param.: AOUINIRH[m*44+i*11+c] , ATINBHDO[m*10+c], ATOISHDO[n*10+c], InterCellHOAtt[m] (14.2.1(a)), InterBSCHOAtt[m] (14.3.1(a)), InterSysOtgHOAtt[n] (14.4.1(a))Elem. Object: NeighbourcellUnit: NoneRemarks: 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 formula103 A30808-X3247-B912-1-7618
  • 104. Information PM: SBS Key Performance IndicatorsSystem14.5.5 Incoming Handover Success RateLong name: (a) Number of Successful Inter BSC Incoming HO (b) Number of Attempted Inter BSC Incoming HO (c) Inter Cell Inter BSC Incoming Handover Success RateShort name: (a) InterBSCIncHOSucc (b) InterBSCIncHOAtt (c) InterBSCIncHOSuccRateDescription: These indicators will give you the rate and number of successful Inter Cell Inter BSC Incoming Handovers including incoming HO from UMTS.Formula: (a) InterBSCIncHOSucc = SUCTCHSE[1 ,2] - TASSSUCC[2 ,3] - IntraCellHOSucc - NSUCCHPC[9 .. 14, 17 .. 22] - SININIRH[1..44] (b) InterBSCIncHOAtt = ATTCHSEI[1,2] - TASSATT[2,3] - IntraCellHOAtt - ATIMASCA[7..14] - AININIRH[1..44] InterBSCIncHOSucc (c) InterBSCIncHOSuccRate = InterBSCIncHOAttUsed param.: SUCTCHSE[1,2], TASSSUCC[2,3], NSUCCHPC[9...14,17...22], SININIRH[1..44], ATTCHSEI[1,2], TASSATT[2,3], ATIMASCA[7..14], AININIRH[1..44], IntraCellHOSucc(14.1.1(b)), IntraCellHOAtt(14.1.1(a))Elem. Object: CellUnit: NoneRemarks: • 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 considered104 A30808-X3247-B912-1-7618
  • 105. Information PM: SBS Key Performance IndicatorsSystem14.5.6 Handover Indication Rejection RateLong name: (a) Handover Indication Rejection RateShort name: (a) HOIndRejRateDescription: This indicator will give you the Handover Indication Rejection Rate by meaning the number of Handover indications not resulting in a Handover Attempt divided by the number of all Handover indications. Reasons for this can be congestions or coverage problems. The KPI considers all types of outgoing HO: Inter and Intra BSC and inter system HO to UMTS.Formula: (a) HOIndRejRate = NHOINRHA [1..4] 31 31 63 NHOINRHA [1..4] + IntraCellH OAtt + ∑ InterCellH OAtt + ∑ InterBSCHO Att + ∑ InterSysOt gHOAtt m=0 m=0 n=0 with m for the mth number of GSM neighbourcell relation (m=0..31) with n for the nth number of UMTS neighbourcell relation (n=0..63)Used param.: NHOINRHA [1..4], IntraCellHOAtt(14.1.1(a)), InterCellHOAtt[m] (14.2.1(a)), InterBSCHOAtt[m] (14.3.1(a)), InterSysOtgHOAtt[n] (14.4.1(a))Elem. Object: CellUnit: NoneRemarks: • 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 considered105 A30808-X3247-B912-1-7618
  • 106. Information PM: SBS Key Performance IndicatorsSystem14.5.7 Total Handover Rate’sLong name: (a) Total Number of Handover Attempts (b) Total Number of Handover Successes (c) Total Number of Handover Failures (d) Total Number of Handover Drops (e) Total Handover Success Rate (f) Total Handover Failure Rate (g) Total Handover Drop RateShort name: (a) HOAtt (b) HOSucc (c) HOFail (d) HODrop (e) HOSuccRate (f) HOFailRate (g) HODropRateDescription: These indicators will give you Handover statistics related to (Intra Cell, Inter Cell, Inter BSC and Inter System) Handovers.Formula: (a) HOAtt = ATINHIAC[all] + ATINHIRC[all] + ATINBHDO[all] + ATOISHDO[a ll] (b) HOSucc = SINTHITA[all] + SINTHINT[a ll] + SUINBHDO[all] + SUOISHDO[a ll] (c) HOFail = UNINHOIA[all] + UNINHOIE[all] + NRUNINHD[all] + UNOISHDO[all] HODrop = UNIHIALC[1] + UNIHIRLC[1] + (d) (ATINBHDO[all] - SUINBHDO[all] − NRUNINHD[all] ) + (ATOISHDO[all] - SUOISHDO[all] - UNOISHDO[all]) (e) HOSuccRate = HOSucc HOAtt (f) HOFailRate = HOFail HOAtt (g) HODropRate = HODrop HOAttUsed param.: ATINHIAC[all], SINTHITA[all], UNINHOIA[all], UNINHIALC[all], ATINHIRC[all], SINTHINT[all], UNINHOIE[all], UNIHIRLC[all], ATINBHDO[all], SUINBHDO[all], NRUNINHD[all], ATOISHDO[all], SUOISHDO[all], UNOISHDO[all]Elem. Object: CellUnit: NoneRemarks: It can happen, that during a running Handover procedures the user will terminate the call and the call will be released before completion of the Handover procedure.. Therefore the number of Handover Successes can be smaller than the difference of HO Attempts – HO Failures – HO Drops. This will lead to a small systematic error for formula (d) and (g).106 A30808-X3247-B912-1-7618
  • 107. Information PM: SBS Key Performance IndicatorsSystem15 Power and Quality Measurements15.1 Interference Band Rate on idle TCHLong name: (a) Interference Band Rate on idle TCHShort name: (a) IfBandRate[n]Description: This indicator will give you Interference Band Rate on idle TCH. Several indicators distinguish between different interference bands.Formula: MEITCHIB [n] (a) IfBandRate[n] = MEITCHIB [1..5] with n=1 for Interference band 1 with n=2 for Interference band 2 with n=3 for Interference band 3 with n=4 for Interference band 4 with n=5 for Interference band 5Used param.: MEITCHIB[1..5]Elem. Object: CellUnit: NoneRemarks: None15.2 Quality Link for N% FERLong name: (a) Quality Link for N% FERShort name: (a) QualityLinkNFERDescription: This indicator will give you the total reported FER uplink values that were under the threshold FER=N%. It is an indicator of the speech quality provided to the TRX users.Formula: n ∑ CFERRXQU [i * 8 + 1..i * 8 + 8] i =0 (a) QualityLinkNFER = CFERRXQU [1..64] Where n is the FER band that has it’s upper limit equal or lower to N%Used param,: CFERRXQU[1..64]Elem. Object: TRXUnit: NoneRemarks: None15.3 Mean FER UpLinkLong name: (a) Mean FER UpLink107 A30808-X3247-B912-1-7618
  • 108. Information PM: SBS Key Performance IndicatorsSystemShort name: (a) MeanFERULDescription: This indicator provides the average FER Band on the Uplink.Formula: 7 ∑ ((i + 1) * CFERRXQU [i * 8 + 1..i * 8 + 8]) i =0 (a) MeanFERUL = CFERRXQU [1..64]Used param,: CFERRXQU[1..64]Elem. Object: TRXUnit: FER BandRemarks: None.108 A30808-X3247-B912-1-7618
  • 109. Information PM: SBS Key Performance IndicatorsSystem15.4 Power and Quality limits for N% Percentile on busy TCHLong name: (a) RXLEV for N% Percentile Uplink on busy TCH (b) RXLEV for N% Percentile Downlink on busy TCH (c) RXQUAL for N% Percentile Uplink on busy TCH (d) RXQUAL for N% Percentile Downlink on busy TCHShort name: (a) RxLvNPercentileUL (b) RxLvNPercentileDL (c) RxQuNPercentileUL (d) RxQuNPercentileDLDescription: These indicators will give you the information that N% of the measurements on busy channels registered a received Power Level below a certain Level Band and that N% of the measurements on busy channels registered a received Quality below a certain Quality Band. Two indicators distinguish between uplink and downlink.Formula: n ∑ (PWRUPDW [i]) (a) RxLvNPercentileUL = n with n such that i=1 = N PWRUPDW [1..64] 100 n ∑ (PWRUPDW [72 + i]) (b) RxLvNPercentileDL = n with n such that i =1 = N PWRUPDW [73..136] 100 n ∑ (PWRUPDW [64 + i]) (c) RxQuNPercentileUL = n with n such that i=1 = N PWRUPDW [65..72] 100 n ∑ (PWRUPDW [136 + i]) (d) RxQuNPercentileDL = n with n such that i=1 N = PWRUPDW [137..144] 100Used param.: PWRUPWD[all]Elem. Object: ChannelUnit: NoneRemarks: None109 A30808-X3247-B912-1-7618
  • 110. Information PM: SBS Key Performance IndicatorsSystem15.5 Distribution of power control levels on busy TCHLong name: (a) Power Control level distribution on busy TCH in UL direction (b) Power Control level distribution on busy TCH in DL directionShort name: (a) PWContrDistrUL (b) PWContrDistrDLDescription: This indicator provides the distribution of the registered power control levels per TCH for UL and DL direction.Use case: Network optimization: Evaluation of the Power Control efficiency and detection of planning problems (e.g. unintended intensive usage of the highest power control values for a TCH)Formula: PWRUPDW [n + 1] (a) PWContrDistrUL[n] = PWRUPDW [1..64] PWRUPDW [n + 73] (b) PWContrDistrDL[n] = PWRUPDW [73 ..136] with n = 0 , .. 63 for the power control levelUsed param.: PWRUPWD[all]Elem. Object: ChannelUnit: NoneRemarks: None110 A30808-X3247-B912-1-7618
  • 111. Information PM: SBS Key Performance IndicatorsSystem15.6 Mean Level and Quality on busy TCHLong name: (a) Mean RXLEV Uplink on busy TCH (b) Mean RXLEV Downlink on busy TCH (c) Mean RXQUAL Uplink on busy TCH (d) Mean RXQUAL Downlink on busy TCHShort name: (a) MeanRxLvUL (b) MeanRxLvDL (c) MeanRxQuUL (d) MeanRxQuDLDescription: These indicators will give you the mean RXLEV and RXQUAL on busy TCH. Two indicators distinguish between uplink and downlink.Formula: 64 ∑ (i * PWRUPDW [i]) (a) MeanRxLvUL = i =1 PWRUPDW [1..64] 64 ∑ (i * PWRUPDW [72 + i]) (b) MeanRxLvDL = i =1 PWRUPDW [73..136] 8 ∑ (i * PWRUPDW [64 + i]) (c) MeanRxQuUL = i =1 PWRUPDW [65..72] 8 ∑ (i * PWRUPDW [136 + i]) (d) MeanRxQuDL = i =1 PWRUPDW [137..144]Used param: PWRUPWD[all]Elem. Object: ChannelUnit: NoneRemarks: None111 A30808-X3247-B912-1-7618
  • 112. Information PM: SBS Key Performance IndicatorsSystem15.7 TA DistributionLong name: (a) TA DistributionShort name: (a) TADist[n]Description: These indicators provide the rate of received samples having timing advance in TA Band equal to ‘n’ .Formula: 7 ∑ (CRXLVTAD + CRXLVTAU) [i × 8 + n + 1] i =0 (a) TADist[n] = (CRXLVTAD + CRXLVTAU) [1..64] Where n=0..7Used param.: CRXLVTAD[1..64], CRXLVTAU[1..64]Elem. Object: TRXUnit: NoneRemarks: The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.15.8 RXQUAL DistributionLong name: (a) RXQUAL Distribution DownLink (b) RXQUAL Distribution UpLinkShort name: (a) RxQuDistDL[n] (b) RxQuDistUL[n]Description: These indicators provide the rate of received samples having the received BER in Quality Band equal to ‘n’. Two indicators distinguish between uplink and downlink.Formula: 7 ∑ CRXLVQUD [i × 8 + n + 1] i =0 (a) RxQuDistDL[n] = CRXLVQUD [1..64] 7 ∑ CRXLVQUU [i × 8 + n + 1] i =0 (b) RxQuDistUL[n] = CRXLVQUU [1..64] Where n=0..7Used param.: CRXLVQUD[1..64], CRXLVQUU[1..64]Elem. Object: TRXUnit: NoneRemarks: The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.112 A30808-X3247-B912-1-7618
  • 113. Information PM: SBS Key Performance IndicatorsSystem15.9 RXLEV DistributionLong name: (a) RXLEV Distribution DownLink (b) RXLEV Distribution UpLinkShort name: (a) RxLvDistDL[n] (b) RxLvDistUL[n]Description: These indicators provide the rate of received samples having the received Level in Level Band equal to ‘n’. Two indicators distinguish between uplink and downlink.Formula: CRXLVQUD [n × 8 + 1..n × 8 + 8] (a) RxLvDistDL[n] = CRXLVQUD [1..64] CRXLVQUU [n × 8 + 1..n × 8 + 8] (b) RxLvDistUL[n] = CRXLVQUU [1..64] Where n=0..7Used param.: CRXLVQUD[1..64], CRXLVQUU[1..64]Elem. Object: TRXUnit: NoneRemarks: The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.15.10 FER DistributionLong name: (a) FER DistributionShort name: (a) FERDist[n]Description: These indicators provide the rate of received samples having the uplink FER in FER Band equal to ‘n’.Formula: CFERRXQU [n × 8 + 1..n × 8 + 8] (a) FERDist[n] = CFERRXQU [1..64] Where n=0..7Used param.: CFERRXQU[1..64]Elem. Object: TRXUnit: NoneRemarks: The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.113 A30808-X3247-B912-1-7618
  • 114. Information PM: SBS Key Performance IndicatorsSystem15.11 Mean FER UpLink per RXQUALLong name: (a) Mean FER UpLink per RXQUAL BandShort name: (a) MeanFERULforRxQu[n]Description: These indicators provide the average FER Band on the uplink for each Quality Band. The implementation of certain features like frequency hoping improves the FER for the same RXQUAL values and therefore, FER is more accurate indicator for analysing the quality of the connection or speech quality.Formula: 7 ∑ ((i + 1)× CFERRXQU [i × 8 + n + 1]) i =0 (a) MeanFERULforRxQu [n] = 7 ∑ CFERRXQU [i × 8 + n + 1] i =0 Where n =0..7Used param,: CFERRXQU[1..64]Elem. Object: TRXUnit: FER BandRemarks: The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.114 A30808-X3247-B912-1-7618
  • 115. Information PM: SBS Key Performance IndicatorsSystem15.12 Mean RXLEV per RXQUAL BandLong name: (a) Mean RXLEV per RXQUAL Band DownLink (b) Mean RXLEV per RXQUAL Band UpLinkShort name: (a) MeanRxLvforRxQuDL[n] (b) MeanRxLvforRxQuUL[n]Description: These indicators provide the average RXLEV Band for each Quality Band either Uplink or Downlink. High interference levels can be associated to high RXLEV averages in the higher Quality Bands.Formula: 7 ∑ ((i + 1)× CRXLVQUD [i × 8 + n + 1]) i =0 (a) MeanRxLvforRxQuDL [n] = 7 ∑ CRXLVQUD [i × 8 + n + 1] i =0 7 ∑ ((i + 1)× CRXLVQUU [i × 8 + n + 1]) i =0 (b) MeanRxLvforRxQuUL [n] = 7 ∑ CRXLVQUU [i × 8 + n + 1] i =0 Where n =0..7Used param,: CRXLVQUU[1..64], CRXLVQUD[1..64]Elem. Object: TRXUnit: Level BandRemarks: The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.115 A30808-X3247-B912-1-7618
  • 116. Information PM: SBS Key Performance IndicatorsSystem15.13 Mean RXLEV per TA BandLong name: (a) Mean RXLEV per TA Band DownLink (b) Mean RXLEV per TA Band UpLinkShort name: (a) MeanRxLvforTADL (b) MeanRxLvforTAULDescription: These indicators provide the average RXLEV Band for each Timing Advance Band either Uplink or Downlink.Formula: 7 ∑ ((i + 1) * CRXLVTAD [i * 8 + n + 1]) i =0 (a) MeanRxLvforTADL [n] = 7 ∑ CRXLVTAD [i * 8 + n + 1] i =0 7 ∑ ((i + 1) * CRXLVTAU [i * 8 + n + 1]) i =0 (b) MeanRxLvforTAUL [n] = 7 ∑ CRXLVTAU [i * 8 + n + 1] i =0 Where n =0..7Used param.: CRXLVTAD[1..64], CRXLVTAU[1..64]Elem. Object: TRXUnit: Level BandRemarks: The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.116 A30808-X3247-B912-1-7618
  • 117. Information PM: SBS Key Performance IndicatorsSystem15.14 High RXLEV with Low RXQUAL RateLong name: (a) High RXLEV With Low RXQUAL Rate DownLink (b) High RXLEV With Low RXQUAL Rate UpLinkShort name: (a) HighLvLowQuRateDL (b) HighLvLowQuRateULDescription: These indicators will give the rate of RXLEVs that were reported for the two highest Level Bands (i.e. Level Bands: RXLEV_6 and RXLEV_7) and for the four highest Quality Bands (i.e. Quality Bands: RXQUAL_4, RXQUAL_5, RXQUAL_6 and RXQUAL_7) from the total samples for the four highest Quality Bands. High values for this indicator are usually related to interference problems.Formula: (a) HighLvLowQuRateDL = CRXLVQUD [53..56,61..64] CRXLVQUD [5..8,13..16,21..24,29..32,37..40,45..48,53..56,61..64] (b) HighLvLowQuRateUL = CRXLVQUU [53..56,61..64] CRXLVQUU [5..8,13..16,21..24, 29..32,37. .40,45..48 ,53..56,61 ..64]Used param.: CRXLVQUD [5..8,13..16,21..24,29..32,37..40,45..48,53..56,61..64], CRXLVQUU [5..8,13..16,21..24,29..32,37..40,45..48,53..56,61..64]Elem. Object: TRXUnit: NoneRemarks: The range of the used measurements (SCANCTRX measurements) can be configured and is therefore relevant for the analysis of the results.117 A30808-X3247-B912-1-7618
  • 118. Information PM: SBS Key Performance IndicatorsSystem15.15 TCH Traffic Type DistributionLong name: (a) TCH full rate speech traffic channel Rate (b) TCH enhanced full rate speech traffic channel Rate (c) TCH adaptive multirate full rate speech traffic channel Rate (d) TCH full rate data traffic channel Rate (e) TCH half rate speech traffic channel Rate (f) TCH adaptive multirate half rate speech traffic channel RateShort name: (a) TCHFSRate (b) TCHEFSRate (c) TCHAFSRate (d) TCHFDRate (e) TCHHSRate (f) TCHAHSRateDescription: These indicators provide the TCH Traffic Type Distribution, by meaning the traffic for a individual traffic type compared to the total traffic for all traffic channels. Different indicators distinguish between full rate speech, enhanced full rate speech, adaptive multirate full rate speech, full rate data, half rate speech and adaptive multirate half rate speech TCHs.Formula: MBTCHCHT [1] (a) TCHFSRate = MBTCHCHT[1..6] MBTCHCHT [2] (b) TCHEFSRate = MBTCHCHT[1..6] MBTCHCHT [3] (c) TCHAFSRate = MBTCHCHT[1..6] MBTCHCHT [4] (d) TCHFDRate = MBTCHCHT[1..6] MBTCHCHT [5] (e) TCHHSRate = MBTCHCHT[1..6] MBTCHCHT [6] (f) TCHAHSRate = MBTCHCHT[1..6]Used param.: MBTCHCHT [1..6]Elem. Object: CellUnit: NoneRemarks: None118 A30808-X3247-B912-1-7618
  • 119. Information PM: SBS Key Performance IndicatorsSystem15.16 SDCCH Traffic Type DistributionLong name: (a) SDCCH Load caused by speech signaling (b) SDCCH Load caused by SMS signaling (c) SDCCH Load caused by USSD signaling (d) SDCCH Load caused by SS signaling (e) SDCCH Load caused by other signaling procedures (f) SDCCH Load caused by abnormal casesShort name: (a) SDCCHLoadSpeech (b) SDCCHLoadSMS (c) SDCCHLoadUSSD (d) SDCCHLoadSS (e) SDCCHLoadOther (f) SDCCHLoadAbnormalDescription: These indicators provide the SDCCH Traffic Type Distribution, by meaning the SDCCH Load for a individual signaling procedure compared to the total SDCCH Load. Different indicators distinguish between the signaling procedures for speech, SMS, USSD, SS, others signaling procedures and abnormal cases. These indicators can be used for supervision and verification of the SDCCH resources.Formula: MBUSYSSP1[1] (a) SDCCHLoadSpeech = MBUSYSSP1[all] MBUSYSSP1[2] (b) SDCCHLoadSMS = MBUSYSSP1[all] MBUSYSSP1[3] (c) SDCCHLoadUSSD = MBUSYSSP1[all] MBUSYSSP1[4] (d) SDCCHLoadSS = MBUSYSSP1[all] MBUSYSSP1[5] (e) SDCCHLoadOther = MBUSYSSP1[all] MBUSYSSP1[6] (f) SDCCHLoadAbnormal = MBUSYSSP1[all]Used param.: MBUSYSSP[all]Elem. Object: CellUnit: NoneRemarks: 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.119 A30808-X3247-B912-1-7618
  • 120. Information PM: SBS Key Performance IndicatorsSystem15.17 Adaptive Multirate DistributionLong name: (a) Adaptive Multirate channel type usageShort name: (a) AMRCHTUsageDescription: These indicators provide the Adaptive Multirate channel type usage and will give you an overview about the quality of the feature Adaptive multirate (AMR). Separate counters distinguish between the different adaptive multirate channel types (8 for adaptive multirate full rate speech, and 5 for adaptive multirate half rate speech) and between uplink / downlink transmission. These indicators provide how often a specific adaptive multirate channel type was used related to all adaptive multirate channel types for one direction (uplink / downlink).Formula: AMRCHDIS[n] (a) AMRCHTUsage[n] = 100 with n = 1 for TCH/AFS 12.2 uplink (AMR full rate speech, 12.2 kbit/s, uplink) 2 for TCH/AFS 10.2 uplink (AMR full rate speech, 10.2 kbit/s, uplink) 3 for TCH/AFS 7.95 uplink (AMR full rate speech, 7.95 kbit/s, uplink) 4 for TCH/AFS 7.4 uplink (AMR full rate speech, 7.5 kbit/s, uplink) 5 for TCH/AFS 6.7 uplink (AMR full rate speech, 6.7 kbit/s, uplink) 6 for TCH/AFS 5.9 uplink (AMR full rate speech, 5.9 kbit/s, uplink) 7 for TCH/AFS 5.15 uplink (AMR full rate speech, 5.15 kbit/s, uplink) 8 for TCH/AFS 4.75 uplink (AMR full rate speech, 4.75 kbit/s, uplink) 9 for TCH/AHS 7.4 uplink (AMR half rate speech, 7.4 kbit/s, uplink) 10for TCH/AHS 6.7 uplink (AMR half rate speech, 6.7 kbit/s, uplink) 11 for TCH/AHS 5.9 uplink (AMR half rate speech, 5.9 kbit/s, uplink) 12 for TCH/AHS 5.15 uplink (AMR half rate speech, 5.15 kbit/s, uplink) 13 for TCH/AHS 4.75 uplink (AMR half rate speech, 4.75 kbit/s, uplink) 14 for TCH/AFS 12.2 downlink (AMR full rate speech, 12.2 kbit/s, downlink) 15 for TCH/AFS 10.2 downlink (AMR full rate speech, 10.2 kbit/s, downlink) 16 for TCH/AFS 7.95 downlink (AMR full rate speech, 7.95 kbit/s, downlink) 17 for TCH/AFS 7.4 downlink (AMR full rate speech, 7.5 kbit/s, downlink) 18 for TCH/AFS 6.7 downlink (AMR full rate speech, 6.7 kbit/s, downlink) 19 for TCH/AFS 5.9 downlink (AMR full rate speech, 5.9 kbit/s, downlink) 20 for TCH/AFS 5.15 downlink (AMR full rate speech, 5.15 kbit/s, downlink) 21 for TCH/AFS 4.75 downlink (AMR full rate speech, 4.75 kbit/s, downlink) 22 for TCH/AHS 7.4 downlink (AMR half rate speech, 7.4 kbit/s, downlink) 23 for TCH/AHS 6.7 downlink (AMR half rate speech, 6.7 kbit/s, downlink) 24 for TCH/AHS 5.9 downlink (AMR half rate speech, 5.9 kbit/s, downlink) 25 for TCH/AHS 5.15 downlink (AMR half rate speech, 5.15 kbit/s, downlink) 26 for TCH/AHS 4.75 downlink (AMR half rate speech, 4.75 kbit/s, downlink)Used param.: AMRCHDIS[1..26]Elem. Object: CellUnit: NoneRemarks: • AMRCHDIS must be divided by 100 in this formula, because the measured value is in percent and KPI`s shouldn`t be in percent.120 A30808-X3247-B912-1-7618
  • 121. Information PM: SBS Key Performance IndicatorsSystem15.18 Adaptive Multirate True Frame Erasure RateLong name: (a) Adaptive Multirate Average Frame Erasure Rate Uplink (b) Adaptive Multirate Average Frame Erasure Rate Uplink per channel type (c) Adaptive Multirate Average Frame Erasure Rate DownlinkShort name: (a) AMRTFERUL (b) AMRTFERULCHT (c) AMRTFERDLDescription: These indicators provide the Adaptive Multirate True Frame Erasure Rate FER: • The True FER is provided as an average over all channel types (coded modes) for the uplink and downlink directions • In addition for the uplink direction the True FER is provided for each channel type separately.Formula: (a) AMRTFERUL = ∑ AMRFRMUL [n + 13] * AMRCHDIS[n ] 13 n =1 AMRFRMUL [n, n + 13] 100 (b) AMRTFERULC HT[n] = AMRFRMUL [n + 13] AMRFRMUL [n, n + 13] with n = 1 for TCH/AFS 12.2 2 for TCH/AFS 10.2 3 for TCH/AFS 7.95 4 for TCH/AFS 7.4 5 for TCH/AFS 6.7 6 for TCH/AFS 5.9 7 for TCH/AFS 5.15 8 for TCH/AFS 4.75 9 for TCH/AHS 7.4 10for TCH/AHS 6.7 11 for TCH/AHS 5.9 12 for TCH/AHS 5.15 13 for TCH/AHS 4.75 (c) AMRTFERDL = AMRFRMDL [2] AMRFRMDL [1,2]Used param.: AMRFRMUL[1..26], AMRFRMDL[1..2], AMRCHDIS[1..13]Elem. Object: CellUnit: NoneRemarks: • AMRCHDIS is in units of percent and must therefore be divided by 100 to get the weighting factor per channel mode121 A30808-X3247-B912-1-7618
  • 122. Information PM: SBS Key Performance IndicatorsSystem16 Availability related Performance Indicators16.1 Transceiver AvailabilityLong name: (a) Tranceiver AvailabilityShort name: (a) TRXAvailDescription: This indicator will give you the TRX Availability.Formula: TRANAVTI [1] (a) TRXAvail = Granularity * 60sUsed param.: TRANAVTI[1], Granularity in minutesElem. Object: TRXUnit: NoneRemarks: None16.2 TCH Distribution RateLong name: (a) TCH Full Rate (b) TCH Half RateShort name: (a) FR (b) HRDescription: This indicator will give you the Rate of configured Full Rate and Half Rate traffic channels compared to the total number of traffic channels.Formula: NRDEFTCH[3,9] (a) FR = NRDEFTCH[3,6,9,12] NRDEFTCH[6,12] (b) HR = NRDEFTCH[3,6,9,12]Used param.: NRDEFTCH[1..12]Elem. Object: CellUnit: NoneRemarks: • Static GPRS channels (configured with GMAPERTCHRES) are not considered into NRDEFTCH measurement • Due to feature ‘Smooth Channel Modification’ now all timeslots configured as TCH and or TCH/SD with pooltype TCH_Pool or TCH/SD with pooltype TCH_SD_Pool are considered for measurement NRDEFTCH.16.3 TCH AvailabilityLong name: (a) TCH Availability Full Rate122 A30808-X3247-B912-1-7618
  • 123. Information PM: SBS Key Performance IndicatorsSystem (b) TCH Availability Half Rate (c) TCH Availability Dual RateShort name: (a) TCHAvailFR (b) TCHAvailHR (c) TCHAvailDRDescription: This indicator will give you the TCH Availability (Rate).Formula: NAVTCH[3,9 ] (a) TCHAvailFR = NRDEFTCH[3 ,9] NAVTCH[6,12] (b) TCHAvailHR = NRDEFTCH[6 ,12] NAVTCH[3,9] + 0,5 * NAVTCH[6,12] (c) TCHAvailDR = NRDEFTCH[3,9] + 0,5 * NRDEFTCH[6,12]Used param.: NAVTCH[3,6,9,12], NRDEFTCH[3,6,9,12]Elem. Object: CellUnit: NoneRemarks: • Reserved GPRS channels (defined by parameters GMANPRESPRM and GMANPRESCOM in the PTPPKF object) are not considered into NRDEFTCH and NAVTCH measurements. • Due to feature ‘Smooth Channel Modification’ now all timeslots configured as TCH and or TCH/SD with pooltype TCH_Pool or TCH/SD with pooltype TCH_SD_Pool are considered for measurement NRDEFTCH. • Due to feature ‘Smooth Channel Modification’ now all available timeslots possible to use as TCH are considered for measurement NAVTCH (Timeslots configured as TCH or TCH/SD with pooltype TCH_Pool or TCH/SD with pooltype TCH_SD_Pool).123 A30808-X3247-B912-1-7618
  • 124. Information PM: SBS Key Performance IndicatorsSystem16.4 SDCCH AvailabilityLong name: (a) SDCCH AvailabilityShort name: (a) SDCCHAvailDescription: This indicator will give you the SDCCH Availability (Rate).Formula: NAVSDCCH [3] (a) SDCCHAvail = NDESDCCH[3]Used param.: NAVSDCCH[3], NDESDCCH[3]Elem. Object: CellUnit: NoneRemarks: Due to feature ‘Smooth Channel Modification’ now all timeslots configured as SDCCH and TCH/SD with pooltype SDCCH_Pool are considered for measurement NDESDCCH. Due to feature ‘Smooth Channel Modification’ now all available timeslots to be used as SDCCH are considered for measurement NAVSDCCH (Timeslots configured as SDCCH or TCH/SD with pooltype ‘SDCCH_Pool’) .124 A30808-X3247-B912-1-7618
  • 125. Information PM: SBS Key Performance IndicatorsSystem17 GPRS Related Performance Indicators17.1 User oriented KPIs17.1.1 Number of TBF establishment attemptsLong Name: (a) TBF establishment attempts uplink (b) TBF establishment attempts downlinkShort Name: (a) TBFEstAttUL (b) TBFEstAttDLDescription : This indicator provides the number of TBF establishments for uplink and downlink.Formula: (a) TBFEstAttUL = NUACATCL[1] (b) TBFEstAttDL = NUACATCL[2]Used param.: NUACATCL[1,2]]Elem. Object: CellUnit: NoneRemark:17.1.2 Number of TBF establishment failuresLong Name: (a) TBF establishment failed due to PDCH Congestion uplink (b) TBF establishment failed due to PDCH Congestion downlink (c) TBF establishment failed due to no reaction from mobile station uplink (d) TBF establishment failed due to no reaction from mobile station downlinkShort Name: (a) TBFEstFailConUL (b) TBFEstFailConDL (c) TBFEstFailNoReacUL (d) TBFEstFailNoReacDLDescription : This indicator provides the number of TBF establishment failures per cause. This indicator will measure in uplink and downlink direction.Formula: (a) TBFEstFailConUL = REJPDASS [1], (b) TBFEstFailConDL = REJPDASS [3], (c) TBFEstFailNoReactUL = SUCPDASA [1] - SULACCEL[1]125 A30808-X3247-B912-1-7618
  • 126. Information PM: SBS Key Performance IndicatorsSystem (d) TBFEstFailNoReacDL = SUCPDASA [2] - SULACCEL[2]Used param.: REJPDASS [1,3], SUCPDASA [1,2], SULACCEL[1,2]Elem. Object: CellUnit: NoneRemark:17.1.3 Number of successful TBF establishmentsLong Name: (a) TBF establishment Success Uplink (b) TBF establishment Success DownlinkShort Name: (a) TBFEstSuccUL (b) TBFEstSuccDLDescription : This indicator calculates the total number of successfully established TBFs in a cell for the uplink and downlink direction.Formula: (a) TBFEstSuccUL = SULACCEL[1] (b) TBFEstSuccDL = SULACCEL[2]Used param.: SULACCEL[1,2];Elem. Object: CellUnit: NoneRemark:17.1.4 TBF establishment success rateLong Name: (a) TBF establishment Success Rate Uplink (b) TBF establishment Success Rate DownlinkShort Name: (a) TBFEstSuccRateUL (b) TBFEstSuccRateDLDescription : This indicator provides the TBF establishment success probability considering uplink and downlink directions.Formula: SULACCEL[1] (a) TBFEstSuccRateUL = NUACATCL[1] SULACCEL[2] (b) TBFEstSuccRateDL = NUACATCL[2]Used param.: SULACCEL[1,2]; NUACATCL[1,2]Elem. Object: CellUnit: None126 A30808-X3247-B912-1-7618
  • 127. Information PM: SBS Key Performance IndicatorsSystemRemark:17.1.5 TBF establishment failure rate (TBF loss rate)Long Name: (a) TBF establishment failure rate for PDCH congestion Uplink (b) TBF establishment failure rate for PDCH congestion Downlink (c) TBF establishment failure rate for no reaction from mobile Uplink (d) TBF establishment failure rate for no reaction from mobile DownlinkShort Name: (a) TBFEstFailRateConUL (b) TBFEstFailRateConDL (c) TBFEstFailRateNoReacUL (d) TBFEstFailRateNoReacDLDescription : This indicator provides the TBF establishment failure rate per cause considering uplink and downlink directions.Formula: REJPDASS[1] (a) TBFEstFailRateConUL = NUACATCL[1] REJPDASS[3] (b) TBFEstFailRateConDL = NUACATCL[2] SUCPDASA [1] - SULACCEL[1] (c) TBFEstFailRateNoReacUL = NUACATCL[1] SUCPDASA [2] - SULACCEL[2] (d) TBFEstFailRateNoReacDL = NUACATCL[2]Used param.: REJPDASS [1,3], NUACATCL[1,2], SUCPDASA[1,2], SULACCEL[1,2]Elem. Object: CellUnit: NoneRemark:17.1.6 Rate for successful TBF establishment with reduced PDCH assignmentLong Name: (a) Rate of successful UL TBF establishment with reduced PDCH assignment (b) Rate of successful DL TBF establishment with reduced PDCH assignmentShort Name: (a) TBFEstSuccRedRateUL (b) TBFEstSuccRedRateDLDescription : 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 PDCH resources. The indicator distinguishes uplink and downlink direction.Formula: (a) TBFEstSuccRedRateUL = UNSPDCSE[1] / SULACCEL[1]127 A30808-X3247-B912-1-7618
  • 128. Information PM: SBS Key Performance IndicatorsSystem (b) TBFEstSuccRedRateDL = UNSPDCSE[2] / SULACCEL[2]Used param.: UNSPDCSE[1,2], SULACCEL[1,2],Elem. Object: CellUnit:Remark:17.1.7 Total number of normally released TBFsLong Name: a) Normal Uplink TBF release b) Normal Downlink TBF releaseShort Name: (a) TBFNormRelUl (b) TBFNormRelDLDescription : This indicator provides the number of normally released TBFs considering uplink and downlink directions.Formula: (a) TBFNormRelUl = SUCTETBF[1,2] (b) TBFNormRelDL = SUCTETBF[3,4]Used param.: SUCTETBF[1…4]Elem. Object: CellUnit: NoneRemark:17.1.8 Total number of dropped TBFsLong Name: a) Uplink TBF dropped due to any cause b) Downlink TBF dropped due to any causeShort Name: (a) TBFDrAllCauseUL (b) TBFDrAllCauseDLDescription : This indicator provides the number of dropped TBFs for all causes considering uplink and downlink directions.Formula: (a) TBFDrAllCauseUL = UNSTETBF[1,3,4,5,6,10,12,14,16] (b) TBFDrAllCauseDL = UNSTETBF[2,7,8,9,11,13,15,17]Used param.: UNSTETBF[all]Elem. Object: CellUnit: NoneRemark: • “Dropped” means that a TBF is terminated in an abnormal way. But128 A30808-X3247-B912-1-7618
  • 129. Information PM: SBS Key Performance IndicatorsSystem a TBF drop does not necessarily indicate system misbehavior. E.g. UNSTETBF[1] (T3169 expiry) is not only counted when the MS is “lost” but is also counted in case of MS based cell reselection during uplink TBF and in case of circuit switched call setup during uplink TBF (and additionally in some other cases). • Counter NRRFPDU [1] Number of Received FLUSH-PDUs on Gb per Cell has not been considered in the formulas: Reason: The reception of a FLUSH-PDU is counted regardless if a TBF is active for the affected TLLI or not. Therefore the counter NRRFPDU does not necessarily count the number of lost TBFs due to cell reselection, but also reselection during GMM Ready State without an active packet transfer.17.1.9 TBF drop distribution on causesLong Name: (a) Share of UL TBF drop due to expiry of supervision timer (T3169) (b) Share of DL TBF drop due to expiry of supervision timer (T3195) (c) Share of UL TBF drop due to preemption (d) Share of DL TBF drop due to preemption (e) Share of UL TBF drop due to ordering of cell reselection (network controlled cell reselection) (f) Share of DL TBF drop due to ordering of cell reselection (network controlled cell reselection)Short Name: (a) TBFDrShareTimerExpUL (b) TBFDrShareTimerExpDL (c) TBFDrSharePreemptionUL (d) TBFDrSharePreemptionDL (e) TBFDrShareCellResOrdUL (f) TBFDrShareCellResOrdDLDescription : This indicator provides the distribution of TBF drops per cause considering uplink and downlink directions.Formula: UNSTETBF[1 ] TimerExpUL = (a) TBFDrShare TBFDrAllCauseUL UNSTETBF[2 ] (b) TimerExpDL = TBFDrShare TBFDrAllCauseDL UNSTETBF[3 ,4,5,6] (c) Preemption = TBFDrShare UL TBFDrAllCauseUL UNSTETBF[7 ,8,9] (d) Preemption = TBFDrShare DL TBFDrAllCauseDL UNSTETBF[1 4] (e) TBFDrShareCellResOrd = UL TBFDrAllCa useUL UNSTETBF[1 5] (f) TBFDrShareCellResOrd = DL TBFDrAllCa useDL129 A30808-X3247-B912-1-7618
  • 130. Information PM: SBS Key Performance IndicatorsSystemUsed param.: UNSTETBF[1..9,14,15], TBFDrAllCauseUL (17.1.8(a)), TBFDrAllCauseDL (17.1.8(b)))Elem. Object: CellUnit: NoneRemark:17.1.10 TBF drop rateLong Name: (a) Uplink TBF drop rate (b) Downlink TBF drop rateShort Name: (a) TBFDropRateUL (b) TBFDropRateDLDescription : This indicator provides the total TBF drop rate form MS point of view considering uplink and downlink directions.Formula: UNSTETBF[1 ,10,12] eUL = (a) TBFDropRat SULACCEL[1] UNSTETBF[2 ,11,13] eDL = (b) TBFDropRat SULACCEL[2]Used param.: SULACCEL[1,2], UNSTETBF[1,2,10,11,12,13]Elem. Object: CellUnit: NoneRemark: • SULACCEL shall be taken as denominator because only TBFs shall be considered which are assigned from MS point of view and because also UNSTETBF start counting in BR8.0 after the TBF is assigned from MS point of view. • Preemption, Packet Cell Change Order and Flush_LL counters shall not be considered. • There will be a systematic error if Timer T3169 or T3195 expires in case a cell reselection was executed. • Phantom (P)RACHs (spurious (P)RACHs) shall not be considered.17.1.11 TBF Drop frequencyLong Name: (a) Uplink TBF drops frequency (b) Downlink TBF drops frequencyShort Name: (a) TBFDrFrequUL (b) TBFDrFrequDLDescription : This indicator provides the TBF drop frequency as the mean number of TBF drops per hour TBF duration. Uplink and downlink directions are considered.130 A30808-X3247-B912-1-7618
  • 131. Information PM: SBS Key Performance IndicatorsSystemFormula: 60 TBFDrAllCauseUL * gran (a) TBFDrFrequUL = NACTTBF[2] 60 TBFDrAllCauseDL * gran (b) TBFDrFrequDL = NACTTBF[4]Used param.: (a) NACTTBF[2,4]; TBFDrAllCauseUL (17.1.8(a)), TBFDrAllCauseDL (17.1.8(b))Elem. Object: CellUnit: Occurrences per hour = (1 / hour)Remark: In case of low number of TBFs and short TBF duration (e.g. mainly GMM and SM) related data transfer on radio interface the formulas produce an inaccurate result under certain circumstances. Reasons: • NACTTBF[2,4] is sampled on a second basis (GMM and SM related TBFs might be shorter) • NACTTBF[2,4] is a real number with 2 digits after decimal point (x.yy). In case of low number (and short duration) of TBFs during a granularity period the result might be 0.01 or 0.00. Alternative formula (proposal): 3600 TBFDrFrequUL = TBFDrAllCauseUL * NACTTBF[1] * MEANTBFL[1] Advantage: • Formula works also In case of low number of TBFs and short TBF duration Disadvantage: • Formula might produce inaccurate result when considerable amount of TBFs are established (triggering of NACTTBF[1,3]) and released (triggering of MEANTBFL[1,2]) in different measurement intervals.17.1.12 Mean time between TBF dropLong Name: (a) Mean time between TBF drop of uplink TBF (b) Mean time between TBF drop of downlink TBFShort Name: (a) TBFDrMeanTimeUL (b) TBFDrMeanTimeDLDescription : This indicator provides the mean time between TBF drops related to one hour TBF duration. Uplink and downlink directions are considered.Formula: 3600 (a) TBFDrMeanTimeUL = TBFDrFrequUL131 A30808-X3247-B912-1-7618
  • 132. Information PM: SBS Key Performance IndicatorsSystem 3600 (b) TBFDrMeanTimeDL = TBFDrFrequDLUsed param.: TBFDrFrequUL (17.1.11(a)), TBFDrFrequDL(17.1.11(b))Elem. Object: CellUnit: SecondsRemark: Possible inaccuracy of formula: See remark on KPI 17.1.11 TBF Drop frequency17.1.13 User data throughput per TBF on the air interfaceLong Name: (a) Mean user data throughput per uplink TBF averaged over all Coding Schemes (b) Mean user data throughput per downlink TBF averaged over all Coding Schemes (c) Mean user data throughput per uplink TBF depending on Coding Scheme (d) Mean user data throughput per downlink TBF depending on Coding SchemeShort Name: (a) UserDataThrTBFAvUL (b) UserDataThrTBFAvDL (c) UserDataThrTBFCSUL (d) UserDataThrTBFCSDLDescription : 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 subscriber’s mobile) will experience. The uplinkdownlink 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 timeUse case Network planning - comparison of user throughput between cells - comparison of user throughput between Coding Schemes - monitoring of trendsFormula: MUTHRF[1..13] 8 (a) UserDataThrTBFAvUL = * NACTTBF [2] 1000 MUTHRF[14.. 26] - REMUTHRF[14.. 26] 8 (b) UserDataThrTBFAvDL = * NACTTBF [4] 1000132 A30808-X3247-B912-1-7618
  • 133. Information PM: SBS Key Performance IndicatorsSystem (c) UserDataThrTBFCSUL[c] = MUTHRF[c] 8 * NACTTBF [2] * CSDistrCellUL[c] 1000 MUTHRF[c + 13] - REMUTHRF[c + 13] 8 (d) UserDataThrTBFCSDL[c] = * NACTTBF [4] * CSDistrCellDL[c] 1000 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 MCS9Used param.: (a) NACTTBF [2,4], MUTHRF[all], REMUTHRF[14 .. 26], CSDistrCellUL (17.3.4(a)), CSDistrCellDL (17.3.4(b)): weighting factors for the distribution of transmission durations for the different Coding Schemes.Elem. Object: CellUnit: kbit per secondRemark: • Interpretation of KPI result: The observed throughput per user might be unexpectedly low due to the following phenomenon: • The release of a DL TBF is normally delayed for 1,5 seconds (default value of configuration parameter TIMTBFREL). o During its lifetime a DL TBF may contain once or several times in the state “delayed TBF release”. o During that TBF state no LLC data are transmitted. • The amount of short duration TBFs for GMM (GPRS Mobility management) and SM (Session management) might be high compared to TBF which serve for transmission of end-to-end user data o The duration of GMM and SM TBFs is typically 0.3 seconds. During that time typically only one ore two RLC/MACC blocks are transmitted (i.e. 20ms or 40ms of LLC PDU transmission time). o Background: At the begin an at the end of the TBF lifetime no LLC data are transmitted. During these periods only RLC/MAC signaling takes place: e.g. MS confirmation of TBF establishment, confirmation of last received RLC/MAC block. o This effect has more affect on the throughput of short-lived TBFs (GMM, SM) as on long-lived TBFs (end-to-end data transmission)133 A30808-X3247-B912-1-7618
  • 134. Information PM: SBS Key Performance IndicatorsSystem • Different treatment of UL and DL direction in the formula DL throughput: o The retransmitted throughput in DL direction is included in the measurement MUTHRF (UL); therefore REMUTHRF (UL) has to be subtracted UL throughput: o Retransmissions due to bad radio link quality are not included in measurement MUTHRF (UL). • Systematic error on formula: See remark on KPI 17.2.2 User Throughput on radio interface per cell • Possible inaccuracy of formula: See remark on KPI 17.1.11 TBF Drop frequency17.1.14 Packet resource reassignment attemptsLong Name: (a) Number of packet resource reassignment attempts for uplink TBFs (b) Number of packet resource reassignment attempts for downlink TBFsShort Name: (a) ReasAttTBFUL (b) ReasAttTBFDLDescription : This indicator provides the mean number of packet resource reassignment attempts per cell separated for uplink and downlink TBFs.Use case Network optimizationFormula: (a) ReasAttTBFUL = NATPRRE[1] (b) ReasAttTBFDL = NATPRRE[2]Used param.: NATPRRE[all]Elem. Object: CellUnit: noneRemark:17.1.15 Packet resource reassignment failuresLong Name: (a) Number of unsuccessful packet resource reassignment procedures for uplink TBFs (b) Number of unsuccessful packet resource reassignment procedures for downlink TBFsShort Name: (a) ReasFailTBFUL (b) ReasFailTBFDLDescription : This indicator provides the mean number of unsuccessful packet resource134 A30808-X3247-B912-1-7618
  • 135. Information PM: SBS Key Performance IndicatorsSystem reassignment procedures per cell separated for uplink and downlink TBFs.Use case Network optimizationFormula: (a) ReasFailTBFUL = NATPRRE[1] - NSUPRRE[1] (b) ReasFailTBFDL = NATPRRE[2] - NSUPRRE[2]Used param.: NATPRRE[all], NSUPRRE[all]Elem. Object: CellUnit: noneRemark:17.1.16 Packet resource reassignment success rateLong Name: (a) Packet resource reassignment success rate for uplink TBFs (b) Packet resource reassignment success rate for downlink TBFsShort Name: (a) ReasSuccRateTBFUL (b) ReasSuccRateTBFDLDescription : This indicator provides packet resource reassignment success rate per cell separated for uplink and downlink TBFs.Use case Network optimizationFormula: NSUPRRE[1] (a) ReasSuccRateTBFUL = NATPRRE[1] NSUPRRE[2] (b) ReasSuccRateTBFDL = NATPRRE[2]Used param.: NATPRRE[all], NSUPRRE[all]Elem. Object: CellUnit: noneRemark:17.1.17 Packet resource reassignment failure rateLong Name: (a) Packet resource reassignment failure rate for uplink TBFs (b) Packet resource reassignment failure rate for downlink TBFsShort Name: (a) ReasFailRateTBFUL (b) ReasFailRateTBFDLDescription : This indicator provides packet resource reassignment failure rate per cell135 A30808-X3247-B912-1-7618
  • 136. Information PM: SBS Key Performance IndicatorsSystem separated for uplink and downlink TBFs.Use case Network optimizationFormula: NSUPRRE [1] (a) Re asFailRateTBFUL = 1 − NATPRRE[1] NSUPRRE [2] (b) Re asFailRateTBFDL = 1 − NATPRRE[2]Used param.: NATPRRE[all], NSUPRRE[all]Elem. Object: CellUnit: noneRemark:17.1.18 TBF downgrade / upgrade frequencyLong Name: (a) Uplink TBF upgrade frequency (b) Uplink TBF downgrade frequency (c) Downlink TBF upgrade frequency (d) Downlink TBF downgrade frequencyShort Name: (a) TBFUpgrFrequUL (b) TBFDowngrFrequUL (c) TBFUpgrFrequDL (d) TBFDowngrFrequDLDescription : 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: 60 SERVUGDG [1] * gran (a) TBFUpgrFrequUL = NALLPDCH[3] 60 SERVUGDG [2] * gran (b) TBFDowngrFrequUL = NALLPDCH[3] 60 SERVUGDG [3] * gran (c) TBFUpgrFrequDL = NALLPDCH[6] 60 SERVUGDG [4] * gran (d) TBFDowngrFrequDL = NALLPDCH[6]Used param.: SERVUGDG [1 .. 4], NALLPDCH[3,6]136 A30808-X3247-B912-1-7618
  • 137. Information PM: SBS Key Performance IndicatorsSystemElem. Object: CellUnit: Occurrences per hour = (1 / hour)Remark:17.1.19 Mean TBF durationLong Name: (a) Mean Uplink TBF duration (b) MeanDownlink TBF durationShort Name: (a) MeanTBFDurUL (b) MeanTBFDurDLDescription : This indicator provides the average TBF duration considering uplink and downlink directions.Use case Network planning and optimizationFormula: (a) MeanTBFDurUL = MEANTBFL[1] (b) MeanTBFDurDL = MEANTBFL[2]Used param.: MEANTBFL[1,2]Elem. Object: CellUnit: SecondsRemark:17.1.20 Link adaptation frequencyLong Name: (a) Upward link adaptation frequency for uplink TBF (b) downward link adaptation frequency for uplink TBF (c) Upward link adaptation frequency for downlink TBF (d) downward link adaptation frequency for downlink TBFShort Name: (a) LinkAdaptFrequUpwUL (b) LinkAdaptFrequDownwUL (c) LinkAdaptFrequUpwDL (d) LinkAdaptFrequDownwDLDescription : 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 CaseFormula: 60 LADAPTUD [1] * gran (a) LinkAdaptFrequUpwUL = NALLPDCH[3]137 A30808-X3247-B912-1-7618
  • 138. Information PM: SBS Key Performance IndicatorsSystem 60 LADAPTUD [2] * gran (b) LinkAdaptFrequDownwUL = NALLPDCH[3] 60 LADAPTUD [3] * gran (c) LinkAdaptFrequUpwDL = NALLPDCH[6] 60 LADAPTUD [4] * gran (d) LinkAdaptFrequDownwDL = NALLPDCH[6]Used param.: LADAPTUD [1 .. 4], NALLPDCH[3,6]Elem. Object: CellUnit: Occurrences per hour (= 1 / hour)Remark:17.1.21 Total number of discarded LLC framesLong Name: (a) Total number of discarded Uplink LLC Frames per Interactive class (b) Total number of discarded Uplink LLC Frames per Streaming class (c) Total number of discarded Uplink LLC Frames per Background class (d) Total number of discarded Downlink LLC Frames per Interactive class (e) Total number of discarded Downlink LLC Frames per Streaming class (f) Total number of discarded Downlink LLC Frames per Background classShort Name: (a) LLCIntFrDiscTotUL (b) LLCStFrDiscTotUL (c) LLCBgFrDiscTotUL (d) LLCIntFrDiscTotDL (e) LLCStFrDiscTotDL (f) LLCBgFrDiscTotDLDescription : This indicator provides the total number of LLC frame discards for all causes per cell and per traffic class (interactive, streaming, background services). Uplink and downlink directions are considered.Use case network optimization from operator view, trouble shootingFormula: (a) LLCIntFrDiscTotUL= DISCLPDU[11..13] (b) LLCStFrDiscTotUL= DISCLPDU[25..27] (c) LLCBgFrDiscTotUL= DISCLPDU[39..41] (d) LLCIntFrDiscTotDL= DISCLPDU[1..10, 14] (e) LLCStFrDiscTotDL= DISCLPDU[15..24, 28] (f) LLCBgFrDiscTotDL= DISCLPDU[29..38, 42]Used param.: DISCLPDU[all]138 A30808-X3247-B912-1-7618
  • 139. Information PM: SBS Key Performance IndicatorsSystemElem. Object: CellUnit: NoneRemark:17.1.22 LLC Frame discard rateLong Name: (a) Rate for Uplink LLC Frame Discard per Interactive class (b) Rate for Uplink LLC Frame Discard per Streaming class (c) Rate for Uplink LLC Frame Discard per Background class (d) Rate for Downlink LLC Frame Discard per Interactive class (e) Rate for Downlink LLC Frame Discard per Streaming class (f) Rate for Downlink LLC Frame Discard per Background classShort Name: (a) LLCIntFrDiscRateUL (b) LLCStFrDiscRateUL (c) LLCBgFrDiscRateUL (d) LLCIntFrDiscRateDL (e) LLCStFrDiscRateDL (f) LLCBgFrDiscRateDLDescription : This indicator provides the LLC frame discard rate for all causes per traffic class (interactive, streaming, background services). Uplink and downlink directions are considered.Use case network optimization from operator view, trouble shootingFormula: DISCLPDU[11..13] scRateUL = (a) LLCIntFrDi NTRLLCFR[1 ] DISCLPDU[25..27] cRateUL = (b) LLCStFrDis NTRLLCFR[2 ] DISCLPDU[3 9..41] cRateUL = (c) LLCBgFrDis NTRLLCFR[3 ] DISCLPDU[1 ..10,14] scRateDL = (d) LLCIntFrDi NTRLLCFR[4 ] DISCLPDU[1 5..24, 28] cRateDL = (e) LLCStFrDis NTRLLCFR[5] DISCLPDU[2 9..38, 42] cRateDL = (f) LLCBgFrDis NTRLLCFR[6]Used param.: DISCLPDU[all], NTRLLCFR[all]Elem. Object: CellUnit: NoneRemark:139 A30808-X3247-B912-1-7618
  • 140. Information PM: SBS Key Performance IndicatorsSystem17.2 Network planning (dimensioning)17.2.1 Total Throughput on air interface per cellLong Name: (a) Total packet Throughput per cell on radio interface in uplink direction (b) Total packet Throughput per cell on radio interface in downlink directionShort Name: (a) TotThrUmCellUL (b) TotThrUmCellDLDescription : The indicators measure the air interface related packet load of a cell in terms of throughput The signaling and retransmission loads are included. The uplinkdownlink directions are separated.Use Case Network capacity planning.Formula: (a) TotThrUmCellUL = (MUTHRF[1..13] + REMUTHRF[1..13] + MSTHRF[1]) * 8 1000 (b) TotThrUmCellDL = (MUTHRF[14..26] + MSTHRF[2] ) * 8 1000Used param.: MUTHRF[all], REMUTHRF[1 .. 13], MSTHRF[1,2]Elem. Object: CellUnit: kbit/secRemark: The DL retransmitted throughput is included in MUTHRF but not the UL retransmitted throughput17.2.2 User Throughput on radio interface per cellLong Name: (a) User Data Throughput per cell on radio interface uplink (b) User Data Throughput per cell on radio interface downlinkShort Name: (b) UserThrUmCellUL (c) UserThrUmCellDLDescription : This indicator provides the mean LLC throughput on the air interface per cell. Retransmissions are excluded; therefore only the amount of data transmitted on behalf of the application layer (here LLC) is considered The uplinkdownlink directions are separated. The KPI does not indicate the packet throughput experienced by a single subscriber. Instead the KPI refers to the mean user packet load of a whole cell according to the following model: The user packet volume transmitted for140 A30808-X3247-B912-1-7618
  • 141. Information PM: SBS Key Performance IndicatorsSystem a cell is accumulated over the whole granularity period and afterwards divided by the length of granularity periodUse Case Network capacity planning.Formula: 8 (a) UserThrUmCellUL = MUTHRF[1..13] * 1000 8 (b) UserThrUmCellDL = (MUTHRF[14..26] - REMUTHRF[14..26]) * 1000Used param.: MUTHRF[all], REMUTHRF[14 .. 26],Elem. Object: CellUnit: kbit/secRemark: DL throughput: • The retransmitted throughput in DL direction is included in the measurement MUTHRF (UL); therefore REMUTHRF (UL) 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).17.2.3 Uplink / Downlink distribution of user throughput on radio interface per cellLong Name: (c) Uplink share of user throughput on radio interface (d) Downlink share of user throughput on radio interfaceShort Name: (a) UserThrUmCellULShare (b) UserThrUmCellDLShareDescription : This indicator provides the uplink and downlink distribution of user packet data transmission per cell on radio interface.Formula: UserThrUmCellUL (a) UserThrUmCellULShare = UserThrUmCellUL + UserThrUmCellDL UserThrUmCellDL (b) UserThrUmCellDLShare = UserThrUmCellUL + UserThrUmCellDLUsed param.: UserThrUmCellUL (17.2.2 (a)) UserThrUmCellDL (17.2.2 (c))Elem. Object: CellUnit: None141 A30808-X3247-B912-1-7618
  • 142. Information PM: SBS Key Performance IndicatorsSystemRemark: None17.2.4 Total packet volume transmitted on radio interface per cellLong Name: (a) Total packet volume transmitted on radio interface per cell in uplink direction including retransmitted throughput (b) Total packet volume transmitted on radio interface per cell in downlink direction including retransmitted throughputShort Name: (a) TotVolUmCellUL (b) TotVolUmCellDLDescription : The indicators measure the air interface related packet load of a cell in terms of transmitted data volume. The signaling and retransmission loads are included. The uplinkdownlink directions are separated.Use Case Network capacity planning.Formula: (a) TotVolUmCellUL = TotThrUmCellUL * gran * 60 (b) TotVolUmCellDL = TotThrUmCellDL * gran * 60Used param.: TotThrUmCellUL, TotThrUmCellDL (17.2.1), granularity period “gran” in minutesElem. Object: CellUnit: kbitRemark:17.2.5 Total packet Throughput on Gb interface per cellLong Name: (a) Total packet throughput on Gb uplink (b) Total packet throughput on Gb downlinkShort Name: (a) TotThrGbCellUL (b) TotThrGbCellDLDescription : This indicator provides the total packet throughput per cell on the Gb interface in the uplink/downlink direction. The total packet throughput comprises user data (LLC layer) from traffic classes (interactive, streaming, background services) including BSSGP header and BSSGP signaling142 A30808-X3247-B912-1-7618
  • 143. Information PM: SBS Key Performance IndicatorsSystemFormula: 8 (a) TotThrGbCellUL = (MUTHBS[1..3] + MSTHBS[1]) * 1000 8 (b) TotThrGbCellDL = (MUTHBS[4..6] + MSTHBS[2]) * 1000Used param.: MUTHBS[all];MSTHBS[1,2];Elem. Object: CellUnit: kbit/secRemark: None17.2.6 User data Throughput on Gb interface per cellLong Name: (a) User Data Throughput on Gb uplink (b) User Data Throughput on Gb downlinkShort Name: (a) UserThrGbCellUL (b) UserThrGbCellDLDescription : This indicator provides the mean user data throughput on LLC layer per cell on the Gb interface in the uplink/downlink direction.Formula: 8 (a) UserThrGbCellUL = MUTHBS[1..3] * 1000 8 (b) UserThrGbCellDL = MUTHBS[4..6] * 1000Used param.: MUTHBS[all]Elem. Object: CellUnit: kbit/secRemark: None17.2.7 Mean number of busy PDCH per cellLong Name: (a) Mean number of PDCHs busy per cell for UL transmission (b) Mean number of PDCHs busy per cell for DL transmissionShort Name: (a) MeanPDCHBusyCellUL (b) MeanPDCHBusyCellDLDescription : This KPI provides the mean number of PDCHs per cell with at least one UL TBF respectively at least one downlink TBF in progress143 A30808-X3247-B912-1-7618
  • 144. Information PM: SBS Key Performance IndicatorsSystemUse case Network planingFormula: (a) MeanPDCHBusyCellUL = NALLPDCH [3] (b) MeanPDCHBusyCellDL = NALLPDCH [6]Used param.: NALLPDCH [3,6]Elem. Object: CellUnit: NoneRemark: None17.2.8 PDCH utilization rateLong Name: (a) Average utilization rate of UL busy PDCHs in terms of used transmission time (b) Average utilization rate of DL busy PDCHs in terms of used transmission timeShort Name: (a) MeanBusyPdchUtilCellUL (b) MeanBusyPdchUtilCellDLDescription : This KPI provides the average utilisation of busy PDCHs in terms of the number of transmitted PDUs relative to the possible PDUs. In order to measure the overall utilization the retransmissions and the signaling PDUs are included. The KPI is for uplink and downlink direction. Difference to TCH utilization: - A TCH is fully utilized by a single CS connection. - The capacity of a PDCH is normally not fully occupied when one or more TBFs are allocated to that PDCH. The TBFs will in most cases occupy only a part of the PDCHs transmission capacity.Use case Network planningFormula: (a) MeanBusyPdchUtilCellUL = (NTRAPDU[1..11] + NRETPDU [1 ..11]) + ½ (NTRAPDU[11.13] + NRETPDU [11.13]) MSTHRF[1] 2*( + ) gran * 60 20 NALLPDCH [3]144 A30808-X3247-B912-1-7618
  • 145. Information PM: SBS Key Performance IndicatorsSystem MeanBusyPdchUtilCellDL = (b) NTRAPDU[14..23] + ½ NTRAPDU[24..26] MSTHRF[2] 2*( + ) gran * 60 20 NALLPDCH[6]Used param.: NTRAPDU [all], NRETPDU [1 .. 13], MSTHRF[1,2], NALLPDCH [3,6]Elem. Object: CellUnit: percentageRemark: It is noted that for CS1 .. CS4 and MSC1 .. MSC7 a PDCH can transport 50 RCL/MAC PDUs per second in each direction (UL and DL). I.e. one PDU represents a transmission time of 20ms. In other words: one PDU per second equals to 2% occupation time of a PDCH. For MSC7 .. MSC 9 an RLC/MAC PDU occupies only half a radio block. I.e. in that case one RLC/MAC PDU represents a transmission time of only 10ms. In other words: one PDU per second equals to 1% occupation time of a PDCH. For BR7 NTRAPDU does not include the RLC/MAC signaling. Therefore the number of signaling PDUs has to be added. That number will be calculated from the signaling throughput (MSTHRH) by assuming that each signaling PDU has exactly a length of 20bytes (maximum length of CS1 frame)17.2.9 Mean Throughput per busy PDCHLong Name: (a) Mean User Throughput Uplink per busy PDCH cumulated on all Coding Schemes (b) Mean User Throughput Downlink per busy PDCH cumulated on all Coding Schemes (c) Mean User Throughput Uplink per busy PDCH depending on the Coding Scheme (d) Mean User Throughput Downlink per busy PDCH depending on the Coding SchemeShort Name: (a) MeanUserThrBusyPdchUL (b) MeanUserThrBusyPdchDL (c) MeanUserThrBusyPdchCSUL (d) MeanUserThrBusyPdchCSDLDescription : This indicator provides the mean RLC packet throughput per busy PDCH per cell. The uplink and downlink directions are separated. Indicators are provided for the throughput depending on the used Coding Scheme and in addition for the throughput cumulated over all Coding Schemes145 A30808-X3247-B912-1-7618
  • 146. Information PM: SBS Key Performance IndicatorsSystem The KPI for the throughput depending on the used Coding Scheme is based on the model that an observed busy PDCH has used that Coding Scheme throughout the complete granularity period. This is the achieved throughput if a PDCH were operated exclusively in that Coding Scheme during the granularity periodUse 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 cellFormula: AvgRadioBitRateUL (a) MeanUserThrBusyPdchUL = NALLPDCH[3] AvgRadioBitRateDL (b) MeanUserThrBusyPdchDL = NALLPDCH[6] RadioBitRateULCS[c] (c) MeanUserThrBusyPdchCSUL[c] = NALLPDCH [3] * CSDistrCellUL [c] (d) MeanUserThrBusyPdchCSDL[c] = RadioBitRateDLCS[c] NALLPDCH[6] * CSDistrCellDL [c] With parameter c for the observed coding scheme: c=1 coding scheme CS1 c=2 coding scheme CS2 c=3 coding scheme CS4 c=4 coding scheme CS5 c=5 coding scheme MCS1 c=6 coding scheme MCS2 c=7 coding scheme MCS3 c=8 coding scheme MCS4 c=9 coding scheme MCS5 c = 10 coding scheme MCS6 c = 11 coding scheme MCS7 c = 12 coding scheme MCS8 c = 13 coding scheme MCS9Used param.: NALLPDCH [3,6], CSDistrCellUL (17.3.4(a)), CSDistrCellDL (17.3.4 (b)): weighting factors for the distribution of transmission durations for the different Coding Schemes. AvgRadioBitRateUL (17.2.14(a)), AvgRadioBitRateDL (17.2.14(b)), RadioBitRateULCS (17.2.13(a)), RadioBitRateDLCS (17.2.13 (b))Elem. Object: CellUnit: kbit/secRemark: • 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 layers146 A30808-X3247-B912-1-7618
  • 147. Information PM: SBS Key Performance IndicatorsSystem per PDCH is higher. • Interpretation of KPI result: The observed throughput per user might be unexpectedly low due to the following phenomenon: • The release of a DL TBF is normally delayed for 1,5 seconds (default value of configuration parameter TIMTBFREL). o During its lifetime a DL TBF may contain once or several times in the state “delayed TBF release”. o During that TBF state no LLC data are transmitted. • The amount of short duration TBFs for GMM (GPRS Mobility management) and SM (Session management) might be high compared to TBF which serve for transmission of end-to-end user data o The duration of GMM and SM TBFs is typically 0.3 seconds. During that time typically only one ore two RLC/MACC blocks are transmitted (i.e. 20ms or 40ms of LLC PDU transmission time). o Background: At the begin and at the end of the TBF lifetime no LLC data are transmitted. During these periods only RLC/MAC signaling takes place: e.g. MS confirmation of TBF establishment, confirmation of last received RLC/MAC block. o This effect has more affect on the throughput of short-lived TBFs (GMM, SM) as on long-lived TBFs (end-to-end data transmission) • Different treatment of UL and DL direction in the formula DL throughput: o The retransmitted throughput in DL direction is included in the measurement MUTHRF (UL); therefore REMUTHRF (UL) has to be subtracted UL throughput: o Retransmissions due to bad radio link quality are not included in measurement MUTHRF (UL). • Systematic error on formula: See remark on KPI 17.2.2 User Throughput on radio interface per cell • Possible inaccuracy of formula: See remark on KPI 17.1.11 TBF Drop frequency17.2.10 Mean number of simultaneously active TBFs per cellLong Name: (a) Mean number of simultaneously active TBF per cell uplink (b) Mean number of simultaneously active TBF per cell downlinkShort Name: (a) MeanActTbfUL (b) MeanActTbfDLDescription : This indicator provides the mean number of simultaneously active TBFs for147 A30808-X3247-B912-1-7618
  • 148. Information PM: SBS Key Performance IndicatorsSystem the uplink and downlink direction.Use case Network planning: how many MS have data transmission simultaneously in a cell.Formula: (a) MeanActTbfUL = NACTTBF[2]; (b) MeanActTbfDL = NACTTBF[4];Used param.: NACTTBF[2,4];Elem. Object: CellUnit: NoneRemark: None17.2.11 Mean number of TBFs multiplexed on same PDCHLong Name: (a) Mean number of uplink TBFs multiplexed on the same PDCH (b) Mean number of downlink TBFs multiplexed on the same PDCHShort Name: (a) MeanTBFMultiplPDCHUL (b) MeanTBFMultiplPDCHDLDescription : This indicator provides the mean number of TBFs multiplexed on the same PDCH (horizontal allocation) for the uplink and downlink direction.Use case Network optimization. E.g. tuning of the parameters for PDCH allocation (in connection with the KPIs for packet throughput per user, see chapter 17.1.13)Formula: (a) MeanTBFMultiplPDCHUL = NTBFPDC[2]; (b) MeanTBFMultiplPDCHDL = NTBFPDC[4];Used param.: NTBFPDC[2,4];Elem. Object: CellUnit: NoneRemark: None17.2.12 Mean number of allocated PDCHs per TBFLong Name: (a) Mean number of allocated PDCHs per uplink TBF (b) Mean number of allocated PDCHs per downlink TBFShort Name: (a) MeanAllocPdchTbfUL (b) MeanAllocPdchTbfDLDescription : This indicator provides the mean number of PDCHs assigned to a TBF for the uplink and downlink direction (horizontal allocation)Use case Monitoring of MS behavior: penetration of the MS multi slot classes148 A30808-X3247-B912-1-7618
  • 149. Information PM: SBS Key Performance IndicatorsSystemFormula: NTBFPDC[2]* NALLPDCH[3] (a) MeanAllocPdchTbfUL = NACTTBF[2], NTBFPDC[4]* NALLPDCH[6] (b) MeanAllocPdchTbfDL = NACTTBF[4]Used param.: NACTTBF[2,4]; NALLPDCH [3,6]; NTBFPDC[2,4]Elem. Object: CellUnit: NoneRemark: 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 NTBFPDC[4]* NALLPDCH[6] MeanAllocPdchTbfDL = NACTTBF[4] NTBFPDC[4] = 2.5 NALLPDCH[6] = 4 PDCH * 3 min / 15min = 0.8 PDCH NACTTBF[4] = (3min * 60 * 3TBFs / (15min * 60) = 0.6 Note: NACTTBF = = The measurement determines in intervals of 1 second the number of TBFs currently active. At the end of the granularity period the arithmetic149 A30808-X3247-B912-1-7618
  • 150. Information PM: SBS Key Performance IndicatorsSystem mean value of the samples is calculated. MeanAllocPdchTbfDL = 2.5 * 0.8/0.6 = 3.33 PDCHs/TBF17.2.13 PDCH Bit Rate per Coding SchemeLong Name: (a) PDCH Bit Rate per cell per coding scheme in uplink direction (b) PDCH Bit Rate per cell per coding scheme in downlink directionShort Name: (a) PDCHBitRateULCS (b) PDCHBitRateDLCSDescription : This indicator provides the LLC packet throughput per coding scheme per cell. The uplink and downlink directions are separated. Indicators are provided for the throughput depending on the used Coding Scheme.Formula: NTRAPDU[c] BlocSize (a) PDCHBitRateULCS[c] = * NTRAPDU[c]+ NRETPDU[c] 20(ms) (b) PDCHBitRateDLCS[c] = ⎡ NTRAPDU [c + 13] − NRETPDU [c + 13] ⎤ BlocSize ⎢ NTRAPDU [c + 13] ⎥ * 20(ms ) ⎣ ⎦Used param.: NTRAPDU[all], NRETPDU[all], with parameter c for the observed coding scheme. BlocSize: the size of the RLC/MAC data bloc depending on the coding scheme in bits c= Coding scheme BlocSize (bits) c=1 CS-1 160 c=2 CS-2 240 c=3 CS-3 288 c=4 CS-4 400 c=5 MCS-1 176 c=6 MCS-2 224 c=7 MCS-3 296 c=8 MCS-4 352 c=9 MCS-5 448 c=10 MCS-6 592 c=11 MCS-7 896 c=12 MCS-8 1088 c=13 MCS-9 1184Elem. Object: CellUnit: kbit/secRemark: • Please note that RLC/MAC signaling is included in this indicator. Also retransmissions are considered. • Different treatment of UL and DL direction in the formula150 A30808-X3247-B912-1-7618
  • 151. Information PM: SBS Key Performance IndicatorsSystem 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).17.2.14 Mean PDCH Bit RateLong Name: (a) Mean PDCH Bit Rate per cell in uplink direction (b) Mean PDCH Bit Rate per cell in downlink directionShort Name: (a) MeanPDCHBitRateUL (b) MeanPDCHBitRateDLDescription : This indicator provides the average LLC packet throughput per cell. The uplink and downlink directions are separated. Indicators are provided for the throughput cumulated over all Coding Schemes.Use caseFormula: 13 (a) MeanPDCHBitRateUL = ∑ PDCHBitRateUL[c] * CSDistrCellUL[c] c =1 13 (b) MeanPDCHBitRateDL = ∑ PDCHBitRateDL[c] * CSDistrCellDL[c] c =1Used param.: PDCHBitRateULCS[all], PDCHBitRateDLCS[all] CSDistrCellUL (17.3.4(a)), CSDistrCellDL (17.3.4 (b)): weighting factors for the distribution of transmission durations for the different Coding Schemes.Elem. Object: CellUnit: kbit/secRemark: None151 A30808-X3247-B912-1-7618
  • 152. Information PM: SBS Key Performance IndicatorsSystem17.3 Network optimization17.3.1 Retransmission Rate on radio interface per cell per coding schemeLong Name: (a) Uplink retransmission Rate on radio interface per cell per coding scheme (b) Downlink retransmission Rate on radio interface per cell per coding schemeShort Name: (a) RetransRateUmCellULCS (b) RetransRateUmCellDLCSDescription : This indicator provides the retransmission rate on the radio interface per coding scheme by the ratio of the number of RLC/MAC PDUs needed for user data retransmission and the overall number of transmitted user data PDUs. The uplink and downlink directions are considered separatelyUse case KPI used for Network quality optimization: -> optimize C/I thresholds for coding scheme selectionFormula: NRETPDU[c] (a) RetransRateUmCellULCS[c] = NTRAPDU[c]+ NRETPDU[c] NRETPDU[13+ c] (b) RetransRateUmCellDLCS[c] = NTRAPDU[13+ c] With parameter c for the observed coding scheme: c=1 coding scheme CS1 c=2 coding scheme CS2 c=3 coding scheme CS3 c=4 coding scheme CS4 c=5 coding scheme MCS1 c=6 coding scheme MCS2 c=7 coding scheme MCS3 c=8 coding scheme MCS4 c=9 coding scheme MCS5 c = 10 coding scheme MCS6 c = 11 coding scheme MCS7 c = 12 coding scheme MCS8 c = 13 coding scheme MCS9Used param.: NTRAPDU[all], NRETPDU[all],Elem. Object: CellUnit: none152 A30808-X3247-B912-1-7618
  • 153. Information PM: SBS Key Performance IndicatorsSystemRemark: In DL direction NTRAPDU contains the retransmitted PDUs. But in UL directions retransmission is not included in NTRAPDU.17.3.2 Retransmitted user throughput on radio interface per cell per coding schemeLong 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 directionShort Name: (a) UserThrRetrCellUmULCS (b) UserThrRetrCellUmDLCSDescription : This indicator provides the retransmitted user Throughput on the radio interface per cell per coding scheme. The uplinkdownlink directions are separated.Use Case KPI used for Network quality optimization: -> optimize C/I thresholds for coding scheme selectionFormula: 8 (a) UserThrRetrCellUmULCS[c] = REMUTHRF[c] * 1000 8 (b) UserThrRetrCellUmDLCS[c] = REMUTHRF[13 + c] * 1000 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 MCS9Used param.: REMUTHRF[all],Elem. Object: CellUnit: kbit/secRemark:153 A30808-X3247-B912-1-7618
  • 154. Information PM: SBS Key Performance IndicatorsSystem17.3.3 Distribution of user throughput on radio interface on Coding Schemes per cellLong 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 schemesShort Name: (a) UserDataUmCellULCSDistr (b) UserDataUmCellDLCSDistrDescription : This indicator provides the distribution of the user data throughput on the radio interface on Coding Schemes. The uplink and downlink directions are considered separatelyUse Case During the planning phase of a radio network (i.e. before deployment) the distribution of the user throughput on Coding Schemes is predicted by simulation results. By aid of the presents KPIs these simulation results may be replaced by the experiences of an operating network. This could help e.g. for the planning of future network expansions (capacity enhancements or expansion of the coverage area of the network)Formula: MUTHRF[c] (a) UserDataUmCellULCSDistr[c] = MUTHRF[1..13] MUTHRF[13+ c] (b) UserDataUmCellDLCSDistr[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 MCS9Used param.: MUTHRF[all],Elem. Object: CellUnit: none154 A30808-X3247-B912-1-7618
  • 155. Information PM: SBS Key Performance IndicatorsSystemRemark: Remarks In DL directions the retransmission is included in MUTHRF[13 .. 26] but in UL direction the retransmission is excluded from MUTHRF[1.. 13]. For simplicity it is assumed that the throughput distribution on coding schemes is mainly independent from the inclusion or exclusion of retransmissions.17.3.4 Timely distribution of the coding scheme utilization on the radio interfaceLong 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 cellShort Name: (a) CSDistrCellUL (b) CSDistrCellDLDescription : 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 separatelyUse Case During the planning phase of a radio network (i.e. before deployment) the distribution of the user data transmission on Coding Schemes is predicted by simulation results. By aid of the presents KPIs these simulation results may be replaced by the experiences of an operating network. This could help e.g. for the planning of future network expansions (capacity enhancements or expansion of the coverage area of the network)Formula: NTRAPDU[c] (a) CSDistrCellUL[c] = NTRAPDU[1..10] + ½ * NTRAPDU[11..13] for c = 1 .. 10 ½ * NTRAPDU[c] CSDistrCellUL[c] = NTRAPDU[1..10] + ½ * NTRAPDU[11..13] for c = 11 .. 13 NTRAPDU[c + 13] (b) CSDistrCellDL[c] = NTRAPDU[14.. 23] + ½ * NTRAPDU[24.. 26] for c = 1 .. 10 ½ * NTRAPDU[c + 13] CSDistrCellDL[c] = NTRAPDU[14.. 23] + ½ * NTRAPDU[24.. 26] 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 CS5155 A30808-X3247-B912-1-7618
  • 156. Information PM: SBS Key Performance IndicatorsSystem 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 MCS9Used param.: NTRAPDU[all]Elem. Object: CellUnit: noneRemark: Remarks • In DL directions the retransmission is included in NTRAPDU[13 .. 26] but in UL direction the retransmission is excluded from NTRAPDU[1.. 13]. For simplicity it is assumed that the timely CS distribution is mainly independent from the inclusion or exclusion of retransmissions • An RLC/MAC PDU for coding schemes MSC7 .. MSC9 occupies half of a radio block (i.e. the duration is ½ * 20ms). Whereas for all other coding schemes an RLC/MAC PDU occupies a full radio block (i.e. the duration is 20ms).17.4 Cell Reselection17.4.1 Number of network controlled Intra BSC cell reselection attempts per cellLong name: (a) Number of network controlled Intra BSC cell reselection attempts per cellShort name: (a) NumNCIntrBSCCellResAttDescription: This indicator provides the number of network controlled Intra BSC cell reselection attempts per cellFormula: (a) NumNCIntrBSCCellResAtt = ATCRORIG [1]Used param.: ATCRORIG [1]Elem. Object: CellUnit: NoneRemarks: None156 A30808-X3247-B912-1-7618
  • 157. Information PM: SBS Key Performance IndicatorsSystem17.4.2 Number of successful network controlled Intra BSC cell reselections per cellLong name: (a) Number of successful network controlled Intra BSC cell reselections per cellShort name: (a) NumNCIntrBSCCellResSucDescription: This indicator provides the number of successful network controlled Intra BSC cell reselections per cellFormula: (a) NumNCIntrBSCCellResSuc = SUCRORIG[1]Used param.: SUCRORIG[1]Elem. Object: CellUnit: NoneRemarks: None17.4.3 Number of network controlled Intra BSC cell reselection failures per cell per causeLong name: (a) Number of network controlled Intra BSC cell reselection failures per cell due to Frequency not implemented (b) Number of network controlled Intra BSC cell reselection failures per cell due to No response on target cell (c) Number of network controlled Intra BSC cell reselection failures per cell due to Imm. Assignment Reject or Packet Access Reject on target cell (d) Number of network controlled Intra BSC cell reselection failures per cell due to Ongoing CS connection (e) Number of network controlled Intra BSC cell reselection failures per cell due to Anonymous Access (f) Number of network controlled Intra BSC cell reselection failures per cell due to MS in GMM standby state (g) Number of network controlled Intra BSC cell reselection failures per cell due to Forced to the standby stateShort name: (a) NumNCIntrBSCCellResFailFrequNotImpl (b) NumNCIntrBSCCellResFailFrequNoRespTarget (c) NumNCIntrBSCCellResFailAccessRejTarget (d) NumNCIntrBSCCellResFailCSOngoing (e) NumNCIntrBSCCellResFailAnonyAccess (f) NumNCIntrBSCCellResFailGMMStandby (g) NumNCIntrBSCCellResFailForcedStandbyDescription: These indicators provides the number of unsuccessful network controlled Intra BSC cell reselections per cell per cause157 A30808-X3247-B912-1-7618
  • 158. Information PM: SBS Key Performance IndicatorsSystemFormula: (a) NumNCIntrBSCCellResFailFrequNotImpl = UNCRORIG [1] (b) NumNCIntrBSCCellResFailFrequNoRespTarget = UNCRORIG [2] (c) NumNCIntrBSCCellResFailAccessRejTarget = UNCRORIG [3] (d) NumNCIntrBSCCellResFailCSOngoing = UNCRORIG [4] (e) NumNCIntrBSCCellResFailAnonyAccess = UNCRORIG S [5] (f) NumNCIntrBSCCellResFailGMMStandby = UNCRORIG [6] (g) NumNCIntrBSCCellResFailForcedStandby = UNCRORIG [7]Used param.: UNCRORIG [all]Elem. Object: CellUnit: NoneRemarks: None17.4.4 Network controlled Intra BSC cell reselection success rateLong name: (a) Success rate for network controlled Intra BSC cell reselectionsShort name: (a) NCIntrBSCCellSucRateDescription: This indicator provides the success rate for network controlled Intra BSC cell reselection per cellFormula: SUCRORIG[1] (a) NCIntrBSCCellSucRate = ATCRORIG [1]Used param.: SUCRORIG[1], ATCRORIG [1]Elem. Object: CellUnit: NoneRemarks: None17.4.5 Network controlled Intra BSC cell reselection failure rateLong name: (a) Network controlled Intra BSC cell reselection failure rate for cause Frequency not implemented (b) Network controlled Intra BSC cell reselection failure rate for cause No response on target cell (c) Network controlled Intra BSC cell reselection failure rate for cause Imm. Assignment Reject or Packet Access Reject on target cell (d) Network controlled Intra BSC cell reselection failure rate for cause Ongoing CS connection (e) Network controlled Intra BSC cell reselection failure rate for cause MS in GMM standby state (f) Network controlled Intra BSC cell reselection failure rate for cause Forced to158 A30808-X3247-B912-1-7618
  • 159. Information PM: SBS Key Performance IndicatorsSystem the standby stateShort name: (a) NCIntrBSCResFailRateFrequNotImpl (b) NCIntrBSCResFailRateNoRespTarget (c) NCIntrBSCResFailRateAccessRejTarget (d) NCIntrBSCResFailRateCSOngoing (e) NCIntrBSCResFailRateGMMStandby (f) NCIntrBSCResFailRateForcedStandbyDescription: These indicators provides the number of unsuccessful network controlled Intra BSC cell reselections per causeFormula: UNCRORIG[1] (a) NCIntrBSCResFailRateFrequNotImpl = ATCRORIG[1] UNCRORIG[2] (b) NCIntrBSCResFailRateNoRespTarget = ATCRORIG[1] UNCRORIG[3] (c) NCIntrBSCResFailRateAccessRejTarget = ATCRORIG[1] UNCRORIG[4] (d) NCIntrBSCResFailRateCSOngoing = ATCRORIG[1] UNCRORIG[5] (e) NCIntrBSCResFailRateGMMStandby = ATCRORIG[1] UNCRORIG[6] (f) NCIntrBSCResFailRateForcedStandby = ATCRORIG[1]Used param.: UNCRORIG[1..6], ATCRORIG [1]Elem. Object: CellUnit: NoneRemarks: None17.4.6 Network controlled cell reselection failure rateLong name: (a) Network controlled cell reselection failure rateShort name: (a) NCResFailRateDescription: This indicator provides the number of unsuccessful network controlled cell reselections.Formula: UNCRORIG[all] (a) NCResFailRate = ATCRORIG[1,2,3,9,10]Used param.: UNCRORIG[all], ATCRORIG [1,2,3,9,10]Elem. Object: CellUnit: NoneRemarks: In general this formula count as far as possible from network point of view.159 A30808-X3247-B912-1-7618
  • 160. Information PM: SBS Key Performance IndicatorsSystem18 Miscellaneous Performance Indicators18.1 BSC ProcessorloadLong name: (a) Mean BSC MPCC Processor load (b) Mean BSC TDPC Processor load (c) Mean BSC PPXU / PCU Processor load (x)Short name: (a) MPPCLoad (b) TDPCLoad (c) PPXULoad(x)Description: These indicators provide the processor load at the BSC for the MPCC (Administrative Processor), TDPC (Telephony Processor) and for the Packet Control Units (PPCUs / PPXUs) (up to 12)Formula: BSCPRCLD[2 ] (a) MPPCLoad = 100 BSCPRCLD[4 ] (b) TDPCLoad = 100 BSCPRCLD[31 + x] (c) PPXULoad(x) = 100 x = PPXU / PCU number (Range=0..11)Used param.: BSCPRCLD[2, 4, 31..42]Elem. Object: BSCUnit: NoneRemarks: None160 A30808-X3247-B912-1-7618
  • 161. Information PM: SBS Key Performance IndicatorsSystem18.2 BTSE ProcessorloadLong name: (a) Mean BTSE Processor loadShort name: (a) BTSEPRLDDescription: This indicator provides the mean BTSE processor load.Formula: BTSEPRLD[1 ] BTSEPRLD= (a) 100Used param.: BTSEPRLD[1]Elem. Object: BTSMUnit: NoneRemarks: None18.3 Paging Response / Location Update Ratio per CellLong name: (a) Paging Response / Location Update Ratio per CellShort name: (a) PagRespLocUpdRatioPerCellDescription: This indicator will give you the ratio between Pagings and Location Updates within a single cell.Formula: NSUCCHPC [1, 9, 17] (a) PagRespLocUpdRatioPer Cell = NSUCCHPC [5,13,21]Used param.: NSUCCHPC [1,5,9,13,17,21]Elem. Object: CellUnit: NoneRemarks: The Paging Response Ratio / Location Update Ratio per cell is related to the Immediate Assignment Procedure.161 A30808-X3247-B912-1-7618
  • 162. Information PM: SBS Key Performance IndicatorsSystem18.4 BSC <-> MSC/SMLC CCS7 LoadLong name: (a) BSC -> MSC CCS7 Load (b) MSC -> BSC CCS7 Load (c) Total BSC <-> MSC CCS7 Load (d) BSC -> SMLC CCS7 Load (e) SMLC -> BSC CCS7 Load (f) Total BSC <-> SMLC CCS7 LoadShort name: (a) Y_BSC->MSC (b) Y_MSC->BSC (c) Y_BSC<->BSC (d) Y_BSC->SMLC (e) Y_SMLC->BSC (f) Y_BSC<->SMLCDescription: Approximate load on the Link Set between BSC and MSC, which were caused of MSUs sent by BSC, vice versa and total.Formula: NMSUTRAS[1] ⋅ ∅MSU _ Length ⋅ 1Min (a) Y _ BSC − > MSC = Erl GRAN ⋅ 8000byte / s ⋅ 60s NMSUREC[1] ⋅ ∅MSU _ Length ⋅ 1Min (b) Y _ MSC − > BSC = Erl GRAN ⋅ 8000byte / s ⋅ 60s Y_BSC- > MSC + Y_MSC- > BSC (c) Y_BSC < - > MSC = Erl 2 NMSUTRAS[2] ⋅ ∅MSU _ Length ⋅ 1Min (d) Y _ BSC − > SMLC = Erl GRAN ⋅ 8000byte / s ⋅ 60 s NMSUREC[2] ⋅ ∅MSU _ Length ⋅ 1Min (e) Y _ SMLC − > BSC = Erl GRAN ⋅ 8000byte / s ⋅ 60 s Y_BSC- > SMLC + Y_SMLC- > BSC (f) Y_BSC < - > MSC = Erl 2Used param.: NMSUTRAS[1,2], NMSUREC[1,2], Granularity in minutesElem. Object: CellUnit: ErlangRemarks: ∅MSU_Length : Average length of a MSU. This value cannot be measured with the existing scanners. An assumption has to be made with the help of traffic models. At the present message structure the MSU has an average length about 35byte. With introduction or extension of services (for example SMS) this value will increase in future.162 A30808-X3247-B912-1-7618
  • 163. Information PM: SBS Key Performance IndicatorsSystem19 BSS related KPIs at Siemens MSCAt the Siemens MSC/VLR it is also possible to start the following measurement jobsfor BSS specific measurements:• REC INTCELL: BSS specific measurements per cell• REC LOCAREA: BSS specific measurements per Location Area• RECMSC: MSC and BSS specific measurements per MSCWith the above Siemens performance measurements it is possible to evaluate atleast the following key performance indicators:• Location Update Success Rate per Location Area• Paging Success Rate per Location Area• Paging Ratio / Location Update Ratio per Location Area• Handover Failures per Cell• Handover Successes per Cell• Dropped Calls per Cell• Call Setup Failures per Cell• Assignment Failures per Cell• TCH Requests per Cell• Busy Hour Call Attempts (BHCA) per MSC• Mean Holding Time per MSC• MOC / MTC / MTM distributionFor more information please refer to the SSS customer documentation.163 A30808-X3247-B912-1-7618
  • 164. Information PM: SBS Key Performance IndicatorsSystem20 Appendix20.1 List of BSS Performance MeasurementsShort Name Long NameAALTCHTI All available TCH allocated timeABISPDIS Abis Pool DistributionABISPSUP Abis Pool SupervisionACADMCDMA Number of Calls Admitted on the DMA LayerACREJCDMA Number of Calls Rejected on the DMA LayerAININIRH Attempted incoming internal intercell Handovers per originating cellAISHINTE Attempted Internal SDCCH Handovers IntercellAISHINTR Attempted internal SDCCH Handovers IntracellAMRCHDIS Adaptive Multirate channel type uplink/downlink distributionAMRFRMDL Frame measurements for Adaptive Multi-Rate (AMR) on uplink busy TCHs’AMRFRMUL Frame measurements for Adaptive Multi-Rate (AMR) on downlink busy TCHs’AMRSIDUL SID_UPDATE frame measurements for Adaptive Multi-Rate (AMR) on uplink busy TCHs’AMRVAR Voice Activity Rate for Adaptive Multi-Rate (AMR) on uplink/downlink busy TCHs’AOINTESH Attempted MSC controlled SDCCH HandoversAOUINIRH Attempted outgoing intercell Handovers per cause, per neigh-bourcell relationshipASDCALTI All available SDCCH allocated timeATCHSMBS Attempted TCH seizures meeting a TCH blocked state (Full-rate/Halfrate)ATCRORIG Attempted network supported cell reselections per cause.ATIMASCA Attempted immediate assignment procedures, per causeATINBHDO Attempted outgoing inter BSC Handovers per neighbour cell re-lationshipATINHIAC Attempted internal Handovers, intracell, per causeATINHIRC Attempted internal Handovers, intercell, per causeATOISHDO Attempted Outgoing Intersystem Handover per neighbourcell per causeATSDCMBS Attempted SDCCH seizure meeting an SDCCH blocked stateATTCHSEI Attempted TCH seizures (Fullrate/Halfrate)BSCPRCLD BSC processor loadBTSEPRLD BTSE processor loadCFERRXQU Correlated FER to RXQUAL measurementsCHALNHLY Number of Channel Allocation Requests Not Served in the Highest Layer or at allCRXLVQUD Correlated RXLEV to RXQUAL measurements (downlink)CRXLVQUU Correlated RXLEV to RXQUAL measurements (uplink)CRXLVTAD Correlated RXLEV to Time Advance measurements (downlink)CRXLVTAU Correlated RXLEV to Time Advance measurements (uplink)DASPUNT Duration of Adjacent Signalling Point (ASP) unavailable conditionDISCLPDU Number of discarded LLC PDU per cell per cause per traffic classDLKSERST Duration of link in-service stateDLKUNCON Duration of the linkset unavailable conditions164 A30808-X3247-B912-1-7618
  • 165. Information PM: SBS Key Performance IndicatorsSystemDSLUNAV Duration of signaling link unavailabilityHOFITABS Total number of Handover failures, intra BSCIFRMABIS I-frame measurementsILUPLKIC Interference measurements on idle TCHsLADAPTUD Link adaptation measurements (uplink/downlink) per cellLLCQULEV DL LLC PDU Queues Filling Level per CellLOCAUTCH Number of locally generated automatic changeoversMAXBUSDC Maximum number of busy SDCCHs per cellMBTCHCHT Mean number of busy TCH per channel typeMBUSYSDC Mean number of busy SDCCHsMBUSYSSP Mean Number of Busy SDCCHs per Signalling ProcedureMDURTCRQ Mean duration a TCH is queued (Fullrate/Halfrate)MDURTCSD Mean Duration a TCH/SD with TCH_SD_Pool can be used as SDCCHMEANTBFL Mean TBF length (uplink/downlink) per cellMEBUSTCH Mean number of busy TCHs (Fullrate/Halfrate)MEBUTSLY Mean Number of Busy ChannelsMEITCHIB Mean number of idle TCHs per interference bandMSTHBS Mean signaling data throughput (uplink/downlink) per cell on the BSSGP Layer Gb interfaceMSTHRF Mean signaling data throughput (uplink/downlink) per cell on the RF interfaceMTCHBUTI Mean TCH busy time (Fullrate/Halfrate)MTCHQLEN Mean TCH queue length (Fullrate/Halfrate)MUTHBS Mean user data throughput (uplink/downlink) per cell per Traffic class on the BSSGP Layer Gb interfaceMUTHRF Mean user data throughput (uplink/downlink) per cell on the RF InterfaceNACSUCPR Number of accesses with a successful result by procedure (PCH, AGCH and RACH)NACTTBF Total, Mean number of active TBFNALIPDCH Min, max, mean number of activated PDCHs per cellNALLPDCH Min, max, mean number of used (active TBF) PDCHs (uplink/downlink) per cellNASPAVUN Number of transitions of the Adjacent Signalling Point (ASP) from available to unavailableNASUSDPE Number of successful SDCCH seizures in a periodNATPRRE Number of attempted packet resource reassignment procedures per cellNATTSDPE Number of attempted SDCCH seizures in a periodNAVPDCH Number of available PDCH per cellNAVSDCCH Number of available SDCCHsNAVTCH Number of available TCHs (Fullrate/Halfrate)NAVTCHSD Number of available TCH/SD per CellNDEFCCCH Number of All Defined CCCH ChannelsNDEFPCCC Number of Defined PCCCH FramesNDEFPDCH Min, max, mean number of defined (configured) PDCHs per cellNDESDCCH Number of defined SDCCHsNDFTCHSD Number of defined TCH/SDNHOINRHA Number of handover indications not resulting in a handover at-temptNINVPRACH Number of invalid PRACH messages per cell per causeNINVRACH Number of invalid RACH messages per causeNMSGDISQ Number of messages discarded from the TCH queue per cell (Fullrate/Halfrate)NMSUREC Number of Message Signal Units (MSUs) receivedNMSUTRAS Number of Message Signal Units (MSUs) transmittedNNNOTNCH Number of new Notifications to be sent on the Notification Channel (NCH)165 A30808-X3247-B912-1-7618
  • 166. Information PM: SBS Key Performance IndicatorsSystemNPDCHPCU Min, max, mean number of activated PDCHs per BSCNRCLRCMD Number of Clear Command messages per cell per cause per channel typeNRCLRREQ Number of Clear Request messages per cell per cause per channel typeNRDEFTCH Number of defined TCHs (Fullrate/Halfrate)NRETPDU Number of retransmitted PDUs (uplink/downlink)NRFLSDCC Number of lost radio links while using an SDCCHNRFLTCH Number of lost radio links while using a TCH (Fullrate/Halfrate)NRINHDFL Number of inter BSC Handover failuresNRRFPDU Number of received FLUSH-PDU on Gb per cellNRUNINHD Number of unsuccessful outgoing inter BSC Handovers per neighbour cell relationshipNSAPRACH Number of Accesses to the PRACH ChannelNSUCCHPC Successful immediate assignments of signalling channels per causeNSUGPPAG Number of successful GPRS paging proceduresNSUPRRE Number of successful packet resource reassignment procedure attempts per cellNSUSDSUS Number of Successful Seizures for USSD SignallingNTBFPDC Max, mean number of TBFs allocated per PDCH (uplink/downlink) per cellNTCHSDCM Number of TCH-SDCCH channel modificationsNTDMAGCH Number of transmitted and discarded messages on the AGCH per cellNTDMPAGC Number of transmitted and discarded messages on the PAGCH per cellNTDMPCH Number of transmitted and discarded messages on the PCH per cellNTDMPPCH Number of transmitted and discarded Paging messages on the PPCH per cellNTRLLCFR Number of transmitted LLC frames (uplink/downlink) per cell per Traffic Class on the BSSGP layer GB interfaceNUACATCL Number of attempted PDCH assignments (uplink/downlink) per cellNTRAPDU Number of transmitted PDUs (uplink/downlink) per coding scheme per cell on the RF interfacePWRUPDW Power and quality measurements on uplink/downlink busy TCHsREJPDASS Number of rejected PDCH assignments (uplink/downlink) per causeREMUTHRF Retransmitted mean user data throughput (uplink/downlink) per coding scheme per cell on the RF interfaceRFDBCUN Routing failure, DPC unavailableRFSUBUN Routing failure, subsystem unavailableRQIISHDO Number of Requested Incoming Intersystem Handover per BSCSERVUGDG Service upgrade/downgrade measurements (uplink/downlink) per cellSINHOBSC Successful internal Handovers per causeSININIRH Successful incoming internal intercell Handovers per originating cellSINTHINT Successful internal Handovers, intercell, per causeSINTHITA Successful internal Handovers, intracell, per causeSISHINTE Successful Internal SDCCH Handovers IntercellSISHINTR Successful internal SDCCH Handovers IntracellSLFAILAL Signalling link failureSOINTESH Successful MSC controlled SDCCH HandoversSOUINIRH Successful outgoing intercell Handovers per cause, per neighbour cell relationshipSUCPDASA Number of successful PDCH assignments (uplink/downlink) per cellSUCRORIG Successful network supported cell reselections per cellSUCTCHSE Successful TCH seizures (Fullrate/Halfrate)SUCTETBF Number of successful terminated TBFs (uplink/downlink) per cellSUIISHDO Number of Successful Incoming Intersystem Handover per BSCSUIMASCA Successful immediate assignment procedures, per cause166 A30808-X3247-B912-1-7618
  • 167. Information PM: SBS Key Performance IndicatorsSystemSUINBHDO Successful outgoing inter BSC Handovers per neighbour cell relationshipSULACCEL Number of successful PDCH seizures (uplink/downlink) per cellSUOISHDO Successful Outgoing Intersystem Handover per neighbourcell per causeTACCBPRO Total number of accesses by procedures (PCH, AGCH)TANRGPRS Number of attempted GPRS accesses per cell with no GPRS radio resources allocatedTASSATT Total number of assignment attempts per cell per channel typeTASSATVS Total number of assignment attempts relevant to VBS/VGCS Broadcast/Group Channels, per cellTASSFAIL Total number of assignment failures per cell, per cause, per channel typeTASSSUCC Total number of successful assignments per cell per channel typeTASSUCVS Total number of successful assignments relevant to VBS/VGCS Broadcast/Group Channels, per cellTCMSGREC Total number of connectionless messages receivedTCMSGSND Total number of connectionless messages sentTMSGREC Total number of messages receivedTMSHHDL Total number of messages handledTNMSCNCL Total number of multislot (HSCSD) connections per cellTNSUDHSC Number of service upgrades/downgrades for HSCSD callsTNTCHCL Total number of TCH connections, per cell (Fullrate/Halfrate)TRANAVTI Transceiver available timeUISHIALC Unsuccessful Internal SDCCH Handovers Intracell with Loss of ConnectionUISHINTE Unsuccessful Internal SDCCH Handovers IntercellUISHINTR Unsuccessful internal SDCCH Handovers IntracellUISHIRLC Unsuccessful Internal SDCCH Handovers Intercell with Loss of ConnectionUMCSHLC Unsuccessful MSC-Controlled SDCCH Handovers with Loss of ConnectionUNCRORIG Unsuccessful network controlled cell reselections per cell per causeUNIHIALC Unsuccessful internal Handover, intracell, with loss of MSUNIHIRLC Unsuccessful internal Handovers, intercell, with loss of MSUNIISHDO Number of Unsuccessful Incoming Intersystem Handover per BSCUNINHOIA Unsuccessful internal Handovers, intracellUNINHOIE Unsuccessful internal HOs, intercell, with reconnection to the old channel, cause, per target cellUNOISHDO Unsuccessful Outgoing Intersystem Handover per neighbourcell per causeUNSPDCSE Number of degraded PDCH seizures (uplink/downlink) per cellUNSTETBF Number of unsuccessful terminated TBFs (uplink/downlink) per cell per causeUOINTESH Unsuccessful MSC controlled SDCCH HandoversWPSSUPV Wireless Priority Services (WPS) SupervisionWUTHBS Weighted User Data Throughput (Uplink/Downlink) per Traffic Class per Cell on the BSSGP Layer Gb Interface167 A30808-X3247-B912-1-7618

×