Counters volume 1 - rnc counters nn-20500-028 p1-07 03_standard_july_2007

NN-20500-028

Wireless Service Provider Solutions

UMTSPerformance ManagementUMTS Access Network PerformanceReference Observation Counters - Volume 1:RNC CountersNN-20500-028 07.03 Standard July 2007

Wireless Service Provider Solutions

UMTSPerformance ManagementUMTS Access Network Performance ReferenceObservation Counters - Volume 1: RNC Counters

Document number: NN-20500-028Document issue: 07.03Document status: StandardProduct release: UMTS 5.1Date: July 2007

Copyright © 2003-2007 Alcatel-Lucent, All Rights Reserved

ALCATEL-LUCENT CONFIDENTIAL

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "writeprotected"; it may be altered only by authorized persons. While copies may be printed, it is notrecommended. Viewing of the master electronically ensures access to the current issue. Any hardcopiestaken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property ofAlcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep allinformation contained herein confidential, shall disclose the information only to its employees with a needto know, and shall protect the information from disclosure and dissemination to third parties. Except asexpressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the informationcontained herein. If you have received this document in error, please notify the sender and destroy itimmediately.

PUBLICATION HISTORYSYSTEM RELEASE UMTS 5.1

July 2007

Issue 07.03/EN Standard

Update for UA 5.0 Channel Readiness.

March 2007

Issue 07.02/EN Preliminary

Update after internal review.

November 2006

Issue 07.01/EN Draft

Update for OAM 5.1.0 / UA 5.0 [UMTS 5.1]

SYSTEM RELEASE UMTS V5.0

November 2006


Update for OAM 5.0.0.6 / UA 4.2.6 [UMTS V5.0 Post-ChR Load]

October 2006


Resolution of the following CR:

• Q01458257

October 2006


Update for OAM 5.0.0.5 / UA 4.2.5 [UMTS V5.0 Post-ChR Load]

July 2006


Update for Post-Channel Readiness

Resolution of the following CR :

• Q01408175

Alcatel-Lucent Confidential Publication history i

Copyright © 2003-2007 Alcatel-Lucent UMTS Access Network Performance Reference ObservationCounters - Volume 1: RNC Counters

June 2006


Update for Post-Channel Readiness

April 2006


Update for Channel Readiness

November 2005


Update for RANV4.2 after internal review

October 2005


Update for RAN V4.2


October 2005


Update for RAN V4.1

August 2005


Update for RAN V4.1

Resolution of the following CRs :

• Q01173557

• Q01173549

• Q01173564

• Q01173750

June 2005


Update for RAN V4.1

Change of the NTP structure: review of the content and split into 3 volumes

Alcatel-Lucent Confidential Publication history ii

NN-20500-028 07.03 Standard July 2007 Copyright © 2003-2007 Alcatel-Lucent

March 2005


Update for Customer Readness after internal review

Resolution of the following CRs:

• Q00862233

• Q01033167

• Q01033176

• Q01034927

• Q01039681

February 2005


Update for RAN V4.1


February 2005


Update for Channel Readness

November 2004



October 2004

Issue 04.04/EN Pre-standard

Update for Pre-Channel Readness

Resolution of the CR Q00982652

June 2004



May 2004


Alcatel-Lucent Confidential Publication history iii


Update for RAN V4.0


March 2004



February 2004


Update for RAN V3.2


February 2004

Issue 03.04a/EN Standard


November 2003



May 2003



April 2003


Update for RAN V3.1

March 2003


Update for RAN V3.1

Alcatel-Lucent Confidential Publication history iv


1 About this publication................................................................................................................................................... 1

2 Road map to UTRAN documentation........................................................................................................................... 4

3 What's new......................................................................................................................................................................5

4 Access Network observation counters........................................................................................................................6

4.1 How Access Network observation counters are defined........................................................................................... 7

4.2 How Access Network observation counters are described......................................................................................13

5 RNC C-Node counter families..................................................................................................................................... 16

5.1 Radio Link Management..........................................................................................................................................17

5.2 Handover................................................................................................................................................................. 48

5.3 Soft Handover........................................................................................................................................................101

5.4 Power Management...............................................................................................................................................117

5.5 RRC Connection....................................................................................................................................................125

5.6 IU Connection........................................................................................................................................................148

5.7 RAB and RB Management.................................................................................................................................... 204

5.8 Security..................................................................................................................................................................297

5.9 Paging....................................................................................................................................................................301

5.10 Mobility.................................................................................................................................................................324

5.11 Radio Measurement............................................................................................................................................ 372

5.12 QOS Performance............................................................................................................................................... 402

5.13 User Plane Common Traffic................................................................................................................................ 501

5.14 IUR Interface........................................................................................................................................................513

5.15 User Plane Dedicated Traffic...............................................................................................................................534

5.16 Statistic Counter.................................................................................................................................................. 612

5.17 CDMA Handover..................................................................................................................................................694

5.18 Platform............................................................................................................................................................... 700

5.19 Synthetic..............................................................................................................................................................702

6 Screening Appendices...............................................................................................................................................709

7 MIB Appendices......................................................................................................................................................... 716

8 CNode Counters Index...............................................................................................................................................722

Alcatel-Lucent Confidential Table of contents v


Figure 1 - RNC C-Node containment tree............................................................................................. ............. ........... 8

Alcatel-Lucent Confidential List of figures vi


Table 1 - Table of aggregation rules..................................................................................................... ............. ......... 12

Table 2 - VS.RadioLinkSetupUnsuccess - #2....................................................................................... ............. ......... 17

Table 3 - VS.RadioLinkAdditionUnsuccess - #4................................................................................................. ......... 19

Table 4 - VS.RadioLinkDeletionSuccess - #5....................................................................................... ............. ......... 20

Table 5 - VS.RadioLinkDeletionUnsuccess - #6................................................................................... ............. ......... 21

Table 6 - VS.RadioLinkReconfigurationPrepareUnsuccess - #8........................................................................ ......... 22

Table 7 - VS.RrcSleepyCellInactivity - #15........................................................................................... ............. ......... 23

Table 8 - VS.RlSleepyCellInactivity - #16........................................................................................................... ......... 24

Table 9 - VS.PagingSleepyCellInactivity - #17...................................................................................... ............. ......... 25

Table 10 - VS.RadioLinkFailureIndication - #18.................................................................................... ............. ......... 26

Table 11 - VS.RadioLinkFirstSetupFailure - #20................................................................................... ............. ......... 28

Table 12 - VS.UeWithNRadioLinksEstCellsBts - #25......................................................................................... ......... 29

Table 13 - VS.RadioLinkReconfigurationCancel - #26.......................................................................... ............. ......... 31

Table 14 - VS.RadioLinkFirstSetupRequest - #27................................................................................ ............. ......... 32

Table 15 - VS.RadioLinkSetupSuccess - #29....................................................................................... ............. ......... 33

Table 16 - VS.RadioLinkAdditionSuccess - #30................................................................................................. ......... 34

Table 17 - VS.RadioLinkReconfigurationPrepareSuccess - #31........................................................................ ......... 36

Table 18 - VS.RadioLinkReconfigurationCommit - #32...................................................................................... ......... 38

Table 19 - VS.RadioLinkEstablishedPerCell - #33................................................................................ ............. ......... 40

Table 20 - VS.RadioLinkDroppedLastRadioLink - #34....................................................................................... ......... 41

Table 21 - VS.RadioLinkSetupRequest - #35....................................................................................... ............. ......... 42

Table 22 - VS.RadioLinkAdditionReq - #36........................................................................................................ ......... 44

Table 23 - VS.RadioLinkReconfPrepReq - #37.................................................................................................. ......... 46

Table 24 - VS.RrcCellChangeOrderNeighbRnc - #106......................................................................... ............. ......... 49

Table 25 - VS.RrcCellChangeOrderFailureNeighbRnc - #108.............................................................. ............. ......... 50

Table 26 - VS.WithoutIurIncomingHardHoAttempt - #122.................................................................... ............. ......... 51

Table 27 - VS.WithoutIurIncomingHardHoFailure - #123...................................................................... ............. ......... 52

Table 28 - VS.WithoutIurIncomingHardHoSuccess - #124................................................................... ............. ......... 54

Table 29 - VS.InterPlmnOutgoingHardHoAttempt - #128..................................................................... ............. ......... 55

Table 30 - VS.InterPlmnOutgoingHardHoFailure - #129....................................................................... ............. ......... 56

Table 31 - VS.InterRncWithoutIurOutgoingHardHoAttempt - #131....................................................... ............. ......... 57

Table 32 - VS.InterRncWithoutIurOutgoingHardHoFailure - #132........................................................ ............. ......... 59

Table 33 - VS.InterRncWithoutIurOutgoingHardHoSuccess - #133................................................................... ......... 60

Table 34 - VS.3g2gOutHoFailure - #135............................................................................................................ ......... 61

Table 35 - VS.WithIurOutgoSrnsRelocAttempt - #142.......................................................................... ............. ......... 63

Table 36 - VS.WithIurOutgoSrnsRelocFail - #143.............................................................................................. ......... 64

Table 37 - VS.WithIurOutgoSrnsRelocSuccess - #144......................................................................... ............. ......... 65

Table 38 - VS.WithIurOutgoSrnsRelocSucPrTc - #145...................................................................................... ......... 66

Table 39 - VS.WithIurOutgoSrnsRelocFailPrTc - #146......................................................................... ............. ......... 67

Table 40 - VS.WithIurIncomSrnsRelocAttempt - #147.......................................................................... ............. ......... 68

Table 41 - VS.WithIurIncomSrnsRelocFail - #148.............................................................................................. ......... 69

Alcatel-Lucent Confidential List of tables vii


Table 42 - VS.WithIurIncomSrnsRelocSuccess - #149......................................................................... ............. ......... 70

Table 43 - VS.WithIurIncomSrnsRelocSucPrTc - #150...................................................................................... ......... 71

Table 44 - VS.WithIurIncomSrnsRelocFailPrTc - #151......................................................................... ............. ......... 72

Table 45 - VS.RrcHoFromUtranCmdTrigByEcNo - #154...................................................................... ............. ......... 74

Table 46 - VS.RrcHoFromUtranCmdTrigByEcNoNRnc - #155............................................................. ............. ......... 75

Table 47 - VS.RrcHoFromUtranCmdTrigByRscp - #156.................................................................................... ......... 76

Table 48 - VS.RrcHoFromUtranCmdTrigByRscpNRnc - #157........................................................................... ......... 77

Table 49 - VS.RrcHoFromUtranCmdTrigRnc - #158.......................................................................................... ......... 78

Table 50 - VS.RrcHoFromUtranCmdTrigRncNrnc - #159..................................................................... ............. ......... 79

Table 51 - VS.RrcHoFromUtranFailure - #160...................................................................................... ............. ......... 80

Table 52 - VS.RrcHoFromUtranFailureNeighbRnc - #161.................................................................... ............. ......... 81

Table 53 - IRATHO.AttOutPSUTRAN - #162........................................................................................ ............. ......... 82

Table 54 - IRATHO.FailOutPSUTRAN - #163.................................................................................................... ......... 83

Table 55 - VS.3gto2gHoDetectionFromFddcell - #164......................................................................... ............. ......... 84

Table 56 - VS.3gto2gHoDetectionFromFddcellNeighbRnc - #165..................................................................... ......... 85

Table 57 - VS.InterPlmnOutgoingHardHoSuccess - #166.................................................................... ............. ......... 86

Table 58 - VS.3gto2gOutHoSuccess - #167......................................................................................... ............. ......... 87

Table 59 - VS.3gto2gOutHoSuccessNrnc - #168............................................................................................... ......... 89

Table 60 - VS.3g2gOutHoFailureNrnc - #169....................................................................................... ............. ......... 90

Table 61 - VS.IntraRncOutInterFreqHoAttempt - #170......................................................................... ............. ......... 91

Table 62 - VS.IntraRncOutInterFreqHoFail - #171................................................................................ ............. ......... 92

Table 63 - VS.IntraRncIncInterFreqHoAttempt - #172.......................................................................... ............. ......... 94

Table 64 - VS.IntraRncIncInterFreqHoFail - #173................................................................................. ............. ......... 95

Table 65 - VS.OutGoInterFreqHoAtt - #174.......................................................................................... ............. ......... 96

Table 66 - VS.OutGoInterFreqHoSuc - #175........................................................................................ ............. ......... 97

Table 67 - VS.IncomInterFreqHoAtt - #176........................................................................................... ............. ......... 98

Table 68 - VS.IncomInterFreqHoSuc - #177......................................................................................... ............. ......... 99

Table 69 - VS.UtranSideSofterHOAtt - #201......................................................................................... ............. ....... 101

Table 70 - VS.UtranSideSofterHOSucc - #202..................................................................................... ............. ....... 102

Table 71 - VS.UtranSideSofterHOUnsucc - #203................................................................................. ............. ....... 103

Table 72 - VS.UtranSideSoftHOAtt - #204............................................................................................ ............. ....... 104

Table 73 - VS.UtranSideSoftHOSucc - #205........................................................................................ ............. ....... 105

Table 74 - VS.UtranSideSoftHOUnsucc - #206.................................................................................... ............. ....... 105

Table 75 - VS.UtranSideDelHOAtt - #207............................................................................................. ............. ....... 106

Table 76 - VS.UtranSideDelHOSucc - #208......................................................................................... ............. ....... 107

Table 77 - VS.UeSideHOAtt - #209.................................................................................................................... ....... 108

Table 78 - VS.UeSideHOSucc - #210................................................................................................... ............. ....... 109

Table 79 - VS.UeSideHOUnsucc - #211............................................................................................... ............. ....... 110

Table 80 - VS.UtranSideIurSoftHOAtt - #212........................................................................................ ............. ....... 111

Table 81 - VS.UtranSideIurSoftHOSucc - #213.................................................................................... ............. ....... 112

Table 82 - VS.UtranSideIurSoftHOUnsucc - #214................................................................................ ............. ....... 113

Table 83 - VS.UtranSideIurDelSoftHOAtt - #215.................................................................................. ............. ....... 114

Alcatel-Lucent Confidential List of tables viii


Table 84 - VS.UtranSideIurDelSoftHOSucc - #216............................................................................... ............. ....... 115

Table 85 - VS.AveragePowerUsedForSpeech - #301........................................................................................ ....... 117

Table 86 - VS.AveragePowerUsedForData - #302............................................................................... ............. ....... 118

Table 87 - VS.UplinkRssi - #303........................................................................................................... ............. ....... 119

Table 88 - VS.AveragePowerUsedForSignalling - #304....................................................................... ............. ....... 120

Table 89 - VS.AveragePowerUsedForMiscellaneous - #305................................................................ ............. ....... 120

Table 90 - VS.IrmcacPowerDist - #306................................................................................................. ............. ....... 121

Table 91 - VS.DistDlTtlPwrRatio - #307................................................................................................ ............. ....... 123

Table 92 - VS.RrcActiveSetUpdateUnsuccess - #402.......................................................................... ............. ....... 125

Table 93 - RRC.SuccConnEstab - #403............................................................................................... ............. ....... 126

Table 94 - RRC.FailConnEstab - #404............................................................................................................... ....... 128

Table 95 - VS.RrcConnectionRelease - #405....................................................................................... ............. ....... 130

Table 96 - VS.RrcActiveSetUpdateUnsuccessNeighbRnc - #407........................................................ ............. ....... 132

Table 97 - VS.RrcConnectionReleaseNeighbRnc - #408..................................................................... ............. ....... 133

Table 98 - RRC.AttConnEstab - #409................................................................................................... ............. ....... 134

Table 99 - VS.RrcTransitionCellFachToCellDch - #412........................................................................ ............. ....... 136

Table 100 - VS.RrcTransitionCellDchToCellFach - #413...................................................................... ............. ....... 137

Table 101 - VS.RrcAvgNbrCellFach - #414.......................................................................................... ............. ....... 138

Table 102 - VS.RrcActiveSetUpdateCompleteProcedure - #415.......................................................... ............. ....... 139

Table 103 - VS.RrcConnectionSetup - #416......................................................................................... ............. ....... 140

Table 104 - SHO - #418........................................................................................................................ ............. ....... 141

Table 105 - VS.FirstRrcConnectionRequest - #419.............................................................................. ............. ....... 142

Table 106 - VS.RrcRel - #420............................................................................................................... ............. ....... 144

Table 107 - VS.ActiveSetUpdatePerRnc - #421................................................................................... ............. ....... 145

Table 108 - VS.RrcActiveSetUpdateSuccessNeighbRnc - #422.......................................................... ............. ....... 146

Table 109 - VS.IuSccpCnxUnsuccess - #502....................................................................................... ............. ....... 149

Table 110 - VS.IuReleaseCommandCs - #505..................................................................................... ............. ....... 150

Table 111 - IRATHO.SuccOutCS - #505............................................................................................................ ....... 151

Table 112 - VS.IuReleaseCommandPs - #506..................................................................................... ............. ....... 152

Table 113 - RATHO.SuccOutPSUTRAN - #506................................................................................... ............. ....... 154

Table 114 - VS.IuReceivedSccpAbnormalDisconnectsCs - #516......................................................... ............. ....... 155

Table 115 - VS.IuEmittedSccpAbnormalDisconnectsPs - #517............................................................ ............. ....... 155

Table 116 - VS.IuReceivedSccpAbnormalDisconnectsPs - #518......................................................... ............. ....... 156

Table 117 - VS.IuEmittedSccpAbnormalDisconnectsCs - #532......................................................................... ....... 157

Table 118 - VS.IuRelocationRequests - #535....................................................................................... ............. ....... 158

Table 119 - VS.IuRelocationRequestFailuresCs - #536..................................................................................... ....... 159

Table 120 - VS.IuRelocationRequestFailuresPs - #537........................................................................ ............. ....... 162

Table 121 - VS.IuSccpCnxSuccess - #548........................................................................................... ............. ....... 163

Table 122 - VS.IuReleaseCommandCs - #552..................................................................................... ............. ....... 164

Table 123 - IRATHO.SuccOutCS - #552............................................................................................................ ....... 166

Table 124 - VS.IuReleaseCommandPs - #553..................................................................................... ............. ....... 167

Table 125 - IRATHO.SuccOutPS - #553............................................................................................... ............. ....... 168

Alcatel-Lucent Confidential List of tables ix


Table 126 - VS.IuRelocationRequired - #556..................................................................................................... ....... 169

Table 127 - VS.IuRelocationCommands - #557.................................................................................... ............. ....... 170

Table 128 - VS.IuRelocationCmdFailuresCs - #558............................................................................. ............. ....... 171

Table 129 - VS.IuRelocationCommandFailuresPs - #559.................................................................................. ....... 173

Table 130 - VS.IuAbnormRelReqCsNrnc - #560................................................................................................ ....... 175

Table 131 - VS.IuAbnormRelReqPsNrnc - #561................................................................................... ............. ....... 176

Table 132 - VS.IuReleaseCompleteCsNrnc - #562............................................................................................ ....... 177

Table 133 - VS.IuReleaseCmdAfterCcConAck - #564.......................................................................... ............. ....... 179

Table 134 - VS.IuReleaseReqAfterCcConAck - #565........................................................................... ............. ....... 180

Table 135 - VS.IuReleaseCmdBeforeCcConAck - #566....................................................................... ............. ....... 181

Table 136 - VS.IuReleaseReqBeforeCcConAck - #567........................................................................ ............. ....... 182

Table 137 - VS.IuRelocationCancels - #568......................................................................................... ............. ....... 183

Table 138 - VS.IuRelocationCompletes - #569..................................................................................... ............. ....... 184

Table 139 - VS.IuRelocationDetects - #570.......................................................................................... ............. ....... 185

Table 140 - VS.IuReleaseCompleteCs - #571...................................................................................... ............. ....... 186

Table 141 - VS.IuAbnormalReleaseRequestCs - #572......................................................................... ............. ....... 188

Table 142 - VS.IuAbnormalReleaseRequestPs - #573......................................................................... ............. ....... 189

Table 143 - VS.IubcSabpMsg - #574.................................................................................................... ............. ....... 191

Table 144 - VS.IubcSabpWrtRplcFail - #575........................................................................................ ............. ....... 192

Table 145 - VS.IuReleaseReqCs - #576............................................................................................... ............. ....... 193

Table 146 - VS.IuReleaseReqPs - #577............................................................................................... ............. ....... 195

Table 147 - VS.IuAvgNbrSccpCnxCs - #578........................................................................................ ............. ....... 196

Table 148 - VS.IuAvgNbrSccpCnxPs - #579...................................................................................................... ....... 198

Table 149 - VS.IuReleaseRequestCsNrnc - #580.............................................................................................. ....... 200

Table 150 - VS.IuReleaseRequestPsNrnc - #581................................................................................. ............. ....... 201

Table 151 - VS.RadioBearerSetupUnsuccess - #602........................................................................... ............. ....... 206

Table 152 - VS.RadioBearerReleaseUnsuccess - #609....................................................................... ............. ....... 207

Table 153 - VS.RadioBearerSetupUnsuccessNeighbRnc - #611......................................................... ............. ....... 208

Table 154 - VS.RadioBearerEstablishmentUnsuccessNeighbRnc - #612............................................ ............. ....... 209

Table 155 - VS.RadioBearerReleaseUnsuccessNeighbRnc - #614..................................................... ............. ....... 210

Table 156 - VS.RadioBearerReconfigurationUnsuccess - #616........................................................... ............. ....... 211

Table 157 - VS.RadioBearerReconfigurationUnsuccessNeighbRnc - #618......................................... ............. ....... 212

Table 158 - VS.RadioBearerEstablishmentUnsuccess - #631.............................................................. ............. ....... 213

Table 159 - VS.RabAssignmentRequestUeCapabilitiesCheckFailure - #635....................................... ............. ....... 215

Table 160 - VS.RabAssignmentRequestUeCapabilitiesCheckAccept - #636....................................... ............. ....... 216

Table 161 - VS.RabrReconfiCompl3Gto3GReloc - #638...................................................................... ............. ....... 217

Table 162 - VS.CallEstablishmentDuration - #639................................................................................ ............. ....... 218

Table 163 - VS.UEDlRBRateAdapActiv - #640..................................................................................... ............. ....... 219

Table 164 - VS.UEDlRBRateAdapDeactiv - #641................................................................................. ............. ....... 221

Table 165 - VS.UEUlRBRateAdapActiv - #642..................................................................................... ............. ....... 222

Table 166 - VS.UEUlRBRateAdapDeactiv - #643................................................................................. ............. ....... 223

Table 167 - VS.UEDlRBRateAdapDownReq - #644............................................................................. ............. ....... 224

Alcatel-Lucent Confidential List of tables x


Table 168 - VS.UEDlRBRateAdapUpReq - #645............................................................................................... ....... 225

Table 169 - VS.UEDlRBRateAdapDownSucc - #646......................................................................................... ....... 226

Table 170 - VS.UEDlRBRateAdapUpSucc - #647................................................................................ ............. ....... 227

Table 171 - VS.UEUlRBRateAdapDownReq - #648............................................................................. ............. ....... 229

Table 172 - VS.UEUlRBRateAdapUpReq - #649............................................................................................... ....... 230

Table 173 - VS.UEUlRBRateAdapDownSucc - #650......................................................................................... ....... 231

Table 174 - VS.UEUlRBRateAdapUpSucc - #651................................................................................ ............. ....... 232

Table 175 - VS.UERBRateAdapDownReqCell - #652.......................................................................... ............. ....... 233

Table 176 - VS.UERBRateAdapUpReqCell - #653............................................................................... ............. ....... 234

Table 177 - VS.UERBRateAdapDownSuccCell - #654......................................................................... ............. ....... 235

Table 178 - VS.UERBRateAdapUpSuccCell - #655............................................................................. ............. ....... 236

Table 179 - VS.UERBRateAdapDownReqNeighbCell - #656............................................................... ............. ....... 237

Table 180 - VS.UERBRateAdapUpReqNeighbCell - #657................................................................... ............. ....... 238

Table 181 - VS.UERBRateAdapDownSuccNeighbCell - #658............................................................. ............. ....... 239

Table 182 - VS.UERBRateAdapUpSuccNeighbCell - #659.................................................................. ............. ....... 239

Table 183 - VS.RabModifReq - #666.................................................................................................... ............. ....... 240

Table 184 - VS.RabModifSucc - #667................................................................................................................ ....... 241

Table 185 - VS.CallAttemptsUeCat - #668......................................................................................................... ....... 242

Table 186 - VS.RbEstabUnsucPerDlRbType - #669.......................................................................................... ....... 244

Table 187 - VS.RadioBearerReconfigFailure - #670............................................................................. ............. ....... 246

Table 188 - VS.RabEstablishmentRequestsPerRabType - #671....................................................................... ....... 247

Table 189 - VS.RabEstablishmentSuccessPerRequestedRabType - #672.......................................... ............. ....... 249

Table 190 - VS.RabEstablishmentSuccessPerGrantedRabType - #673.............................................. ............. ....... 251

Table 191 - VS.RabReleaseRequest - #674......................................................................................... ............. ....... 253

Table 192 - VS.NumberOfRabEstablished - #675................................................................................ ............. ....... 255

Table 193 - VS.RabNormalRelease - #676........................................................................................... ............. ....... 256

Table 194 - VS.RabAssignmentSetupUnsuccess - #677...................................................................... ............. ....... 258

Table 195 - VS.RabAssignmentReleaseSuccess - #678...................................................................... ............. ....... 260

Table 196 - VS.RabAssignmentReleaseUnsuccess - #679.................................................................. ............. ....... 262

Table 197 - VS.RabOutgoingRefCell - #680......................................................................................... ............. ....... 264

Table 198 - VS.RabIncomingRefCell - #681......................................................................................... ............. ....... 265

Table 199 - VS.RabEstabSuccPerReqRabTypRefCell - #682.............................................................. ............. ....... 267

Table 200 - VS.RabAbnormRelPerReqRabTypRefCel - #683.............................................................. ............. ....... 269

Table 201 - VS.RadioBearerReconfigurationSuccess - #684............................................................... ............. ....... 270

Table 202 - VS.RadioBearerReconfigureRequest - #685..................................................................... ............. ....... 272

Table 203 - VS.RadioBearerReconfigurationSuccessNeighbRnc - #686............................................. ............. ....... 274

Table 204 - VS.RadioBearerSetupSuccess - #687............................................................................... ............. ....... 276

Table 205 - VS.RadioBearerReleaseSuccess - #688........................................................................... ............. ....... 277

Table 206 - VS.RadioBearerSetupSuccessNeighbRnc - #689............................................................. ............. ....... 279

Table 207 - VS.RadioBearerReleaseSuccessNeighbRnc - #690......................................................... ............. ....... 281

Table 208 - VS.RadioBearerSetupRequest - #691............................................................................... ............. ....... 284

Table 209 - VS.DlAsConfIdAvgNbrEstablished - #692......................................................................... ............. ....... 285

Alcatel-Lucent Confidential List of tables xi


Table 210 - VS.UlAsConfIdAvgNbrEstablished - #693......................................................................... ............. ....... 287

Table 211 - VS.SucEdchToDchTrans - #694........................................................................................ ............. ....... 289

Table 212 - VS.UnsucEdchToDchTrans - #695.................................................................................... ............. ....... 290

Table 213 - VS.SucDchToEdchTrans - #696........................................................................................ ............. ....... 290

Table 214 - VS.UnsucDchToEdchTrans - #697.................................................................................... ............. ....... 291

Table 215 - VS.SucHspaToDchFallbackCell - #1601........................................................................... ............. ....... 292

Table 216 - VS.SucHspaToDchFallbackNrnc - #1602.......................................................................... ............. ....... 293

Table 217 - VS.UnsucHspaToDchFallbackCell - #1603....................................................................... ............. ....... 294

Table 218 - VS.UnsucHspaToDchFallbackNrnc - #1604...................................................................... ............. ....... 295

Table 219 - VS.SmcSuccess - #701..................................................................................................... ............. ....... 297

Table 220 - VS.RejectedSmc - #702.................................................................................................................. ....... 298

Table 221 - VS.FailedRrcSmc - #703................................................................................................................. ....... 299

Table 222 - VS.ReceivedPagingRequest - #801................................................................................................ ....... 301

Table 223 - VS.ReceivedPagingRequestType2CellDch - #802............................................................ ............. ....... 302

Table 224 - VS.ReceivedPagingRequestType2CellFach - #803.......................................................... ............. ....... 303

Table 225 - VS.PagingMessagesSentOnPcch - #805.......................................................................... ............. ....... 304

Table 226 - VS.PagingCancelledRecords - #807............................................................................................... ....... 305

Table 227 - VS.PagingRejectedRequests - #808............................................................................................... ....... 306

Table 228 - VS.PagingDelayedRecords - #809.................................................................................... ............. ....... 307

Table 229 - VS.UnhandledPagingRequestsCs - #810.......................................................................... ............. ....... 308

Table 230 - VS.UnhandledPagingRequestsPs - #811.......................................................................... ............. ....... 309

Table 231 - VS.PagingRecordsSentOnPcchCs - #812......................................................................... ............. ....... 310

Table 232 - VS.PagingRecordsSentOnPcchPs - #813......................................................................... ............. ....... 312

Table 233 - VS.PagingRecordsUnscheduledCs - #814........................................................................ ............. ....... 313

Table 234 - VS.PagingRecordsUnscheduledPs - #815........................................................................ ............. ....... 315

Table 235 - VS.PagingRecordsType2SentCs - #816............................................................................ ............. ....... 316

Table 236 - VS.PagingRecordsType2SentPs - #817............................................................................ ............. ....... 318

Table 237 - VS.PagingRecordsType2PagCauseCs - #818.................................................................. ............. ....... 319

Table 238 - VS.PagingRequestsIuPagCauseCs - #819..................................................................................... ....... 320

Table 239 - VS.UtranPagingRecSentOnPcch - #820......................................................................................... ....... 322

Table 240 - VS.NbrCellUpdates - #901................................................................................................. ............. ....... 325

Table 241 - VS.NbrCellUpdateRejects - #902.................................................................................................... ....... 326

Table 242 - VS.CsLocationReportingControlDefaultLs - #903.............................................................. ............. ....... 327

Table 243 - VS.CsLocationUebasedAgpsSuccess - #913.................................................................... ............. ....... 328

Table 244 - VS.CsLocationUebasedAgpsUnsuccess - #914................................................................ ............. ....... 329

Table 245 - VS.UeLocationUebasedAgpsSuccess - #915.................................................................... ............. ....... 330

Table 246 - VS.UeLocationUebasedAgpsSuccessNeighbRnc - #916.................................................. ............. ....... 331

Table 247 - VS.UeLocationUebasedAgpsUnsuccess - #917................................................................ ............. ....... 333

Table 248 - VS.UeLocationUebasedAgpsUnsuccessNeighbRnc - #918.............................................. ............. ....... 334

Table 249 - VS.PsLocationUeBasedAgpsSuccess - #919.................................................................... ............. ....... 335

Table 250 - VS.PsLocationUebasedAgpsUnsuccess - #920................................................................ ............. ....... 336

Table 251 - VS.PsLocationReportingControlGeoLs - #921................................................................................ ....... 337

Alcatel-Lucent Confidential List of tables xii


Table 252 - VS.PsLocationReportSuccessGeoLsWithinQos - #922..................................................... ............. ....... 338

Table 253 - VS.PsLocationReportSuccessGeoLsOutsideQos - #923.................................................. ............. ....... 339

Table 254 - VS.PsLocationReportUnsuccessGeoLs - #924................................................................. ............. ....... 340

Table 255 - VS.CsLocationReportSuccessGeoLsOutsideQos - #925.................................................. ............. ....... 341

Table 256 - VS.CsLocationReportingControlGeoLs - #926.................................................................. ............. ....... 342

Table 257 - VS.PsLocationReportingControlSaLs - #927..................................................................... ............. ....... 343

Table 258 - VS.CsLocationReportSuccessSaLs - #928..................................................................................... ....... 344

Table 259 - VS.CsLocationReportUnsuccessSaLs - #929................................................................................. ....... 345

Table 260 - VS.CsLocationReportSuccessGeoLsWithinQoS - #930.................................................... ............. ....... 346

Table 261 - VS.CsLocationReportUnsuccessGeoLs - #931................................................................. ............. ....... 347

Table 262 - VS.PsLocationReportSuccessSaLs - #932........................................................................ ............. ....... 348

Table 263 - VS.PsLocationReportUnsuccessSaLs - #933.................................................................... ............. ....... 349

Table 264 - VS.RrcAvgNbrCellPch - #934............................................................................................ ............. ....... 350

Table 265 - VS.RrcAvgNbrUraPch - #935.......................................................................................................... ....... 351

Table 266 - VS.RrcAvgNbrCellFachRnc - #936.................................................................................... ............. ....... 352

Table 267 - VS.NbrUraUpdates - #937................................................................................................. ............. ....... 353

Table 268 - VS.NbrUraUpdatesRej - #938............................................................................................ ............. ....... 354

Table 269 - VS.RrcTransCellPchToUraPch - #939............................................................................... ............. ....... 355

Table 270 - VS.RrcTransDchToPch - #940........................................................................................................ ....... 356

Table 271 - VS.HsdpaMobilitySuccess - #950...................................................................................... ............. ....... 357

Table 272 - VS.HsdpaMobilityUnsuccessful - #951.............................................................................. ............. ....... 358

Table 273 - VS.HsdpaCellDeletion - #952............................................................................................ ............. ....... 359

Table 274 - VS.HsdpaDCHToHsdpaTransSucc - #953........................................................................ ............. ....... 360

Table 275 - VS.HsdpaToDCHSucc - #954............................................................................................ ............. ....... 361

Table 276 - VS.DCHToHsdpaUnsuccessful - #955.............................................................................. ............. ....... 362

Table 277 - VS.HsdpaToDCHUnsuccessful - #956.............................................................................. ............. ....... 363

Table 278 - VS.HsdpaCACSuccess - #957........................................................................................................ ....... 364

Table 279 - VS.HsdpaCACUnsuccessful - #958................................................................................... ............. ....... 365

Table 280 - VS.HsdpaIuRelAbnormal - #959........................................................................................ ............. ....... 366

Table 281 - VS.EdchSucMobility - #960............................................................................................................. ....... 367

Table 282 - VS.EdchUnsucMobility - #961......................................................................................................... ....... 368

Table 283 - VS.EdchCellDeletion - #962............................................................................................................ ....... 369

Table 284 - VS.EdchIuRelAbnormal - #963.......................................................................................... ............. ....... 370

Table 285 - VS.AvgTxPower - #1002................................................................................................................. ....... 373

Table 286 - VS.CmConfigurationFailure - #1003.................................................................................. ............. ....... 373

Table 287 - VS.CmActivationSuccess - #1004..................................................................................... ............. ....... 374

Table 288 - VS.CmActivationFailure - #1005........................................................................................ ............. ....... 375

Table 289 - VS.CmConfigurationSuccess - #1006............................................................................................. ....... 376

Table 290 - VS.IntraFreqMeasAverageOfCallPeriodicModeCell - #1011............................................. ............. ....... 377

Table 291 - VS.IntraFreqMeasAverageOfCallPeriodicModeNeighRnc - #1012................................................. ....... 378

Table 292 - VS.IntraFreqMeasAverageOfCallEventModeCell - #1013................................................. ............. ....... 379

Table 293 - VS.IntraFreqMeasAverageOfCallEventModeNeighRnc - #1014....................................... ............. ....... 380

Alcatel-Lucent Confidential List of tables xiii


Table 294 - VS.MeasurementControlCellListSize - #1016.................................................................... ............. ....... 381

Table 295 - VS.MeasEvent1ACell - #1017......................................................................................................... ....... 382

Table 296 - VS.MeasEvent1BCell - #1018......................................................................................................... ....... 383

Table 297 - VS.MeasEvent1CCell - #1019........................................................................................... ............. ....... 384

Table 298 - VS.MeasEvent1DCell - #1020........................................................................................... ............. ....... 384

Table 299 - VS.MeasEvent1ECell - #1021......................................................................................................... ....... 385

Table 300 - VS.MeasEvent1FCell - #1022............................................................................................ ............. ....... 386

Table 301 - VS.MeasEvent2DCell - #1023........................................................................................... ............. ....... 387

Table 302 - VS.MeasEvent2FCell - #1024............................................................................................ ............. ....... 388

Table 303 - VS.MeasCallFailTraceDetectCell - #1027....................................................................................... ....... 389

Table 304 - VS.MeasEvent1BNeighRNC - #1029.............................................................................................. ....... 390

Table 305 - VS.MeasEvent1CNeighRNC - #1030................................................................................ ............. ....... 391

Table 306 - VS.MeasEvent1DNeighRNC - #1031................................................................................ ............. ....... 391

Table 307 - VS.MeasEvent1ENeighRNC - #1032.............................................................................................. ....... 392

Table 308 - VS.MeasEvent1FNeighRNC - #1033................................................................................. ............. ....... 393

Table 309 - VS.MeasEvent2DNeighRNC - #1034................................................................................ ............. ....... 394

Table 310 - VS.MeasEvent2FNeighRNC - #1035................................................................................. ............. ....... 395

Table 311 - VS.MeasCallFailTraceDetectNeighRNC - #1038............................................................................ ....... 396

Table 312 - VS.MeasurementControlFailure - #1039......................................................................................... ....... 397

Table 313 - VS.DistPropDelayPerRange - #1041................................................................................. ............. ....... 398

Table 314 - VS.DistRssi - #1042........................................................................................................... ............. ....... 399

Table 315 - VS.IrmcacDistributionEcN0 - #1043................................................................................................ ....... 400

Table 316 - VS.IrmcacMaintainedHighPriority - #1111......................................................................... ............. ....... 404

Table 317 - VS.IrmcacDowngradedHighPriority - #1112...................................................................... ............. ....... 406

Table 318 - VS.IrmcacRejectedHighPriority - #1113.......................................................................................... ....... 409

Table 319 - VS.IrmcacMaintainedMediumPriority - #1114.................................................................... ............. ....... 411

Table 320 - VS.IrmcacDowngradedMediumPriority - #1115................................................................. ............. ....... 414

Table 321 - VS.IrmcacRejectedMediumPriority - #1116....................................................................... ............. ....... 417

Table 322 - VS.IrmcacMaintainedLowPriority - #1117.......................................................................... ............. ....... 419

Table 323 - VS.IrmcacDowngradedLowPriority - #1118....................................................................... ............. ....... 422

Table 324 - VS.IrmcacRejectedLowPriority - #1119............................................................................. ............. ....... 424

Table 325 - VS.IRMTimeCellRadioColorRed - #1124........................................................................... ............. ....... 427

Table 326 - VS.IRMTimeCellRadioColorYellow - #1125....................................................................... ............. ....... 428

Table 327 - VS.IRMTimeFreeDlCodesBySpreadingFactor - #1126................................................................... ....... 429

Table 328 - VS.IrmcacRadioLinkColorRed - #1129.............................................................................. ............. ....... 430

Table 329 - VS.IrmcacRadioLinkColorGreen - #1130........................................................................... ............. ....... 431

Table 330 - VS.IrmUpgradingActivation - #1131................................................................................... ............. ....... 432

Table 331 - VS.IrmUpgradingActivationDelayed - #1132................................................................................... ....... 433

Table 332 - VS.IrmUpgradingDeactivation - #1134............................................................................................ ....... 434

Table 333 - VS.IrmPreemptionTimeCellColorCongested - #1136........................................................ ............. ....... 434

Table 334 - VS.IrmPreemptionTimeCellColorCongestedBecauseOfOvsfCodes - #1137..................... ............. ....... 435

Table 335 - VS.IrmPreemptionTimeCellColorCongestedBecauseOfPower - #1138............................ ............. ....... 436

Alcatel-Lucent Confidential List of tables xiv


Table 336 - VS.IrmPreemptionRbHighPriorityDowngraded - #1139..................................................... ............. ....... 437

Table 337 - VS.IrmPreemptionRbHighPriorityRejected - #1140........................................................... ............. ....... 440

Table 338 - VS.IrmPreemptionRbMediumPriorityDowngraded - #1141............................................................. ....... 443

Table 339 - VS.IrmPreemptionRbMediumPriorityRejected - #1142...................................................... ............. ....... 447

Table 340 - VS.IrmPreemptionRbLowPriorityDowngraded - #1143...................................................... ............. ....... 450

Table 341 - VS.IrmPreemptionRbLowPriorityRejected - #1144............................................................ ............. ....... 453

Table 342 - VS.RrcNwkTransPchToFachOrDch - #1157................................................................................... ....... 456

Table 343 - VS.IrmcacDistributionRscp - #1158................................................................................... ............. ....... 457

Table 344 - VS.DownsizingStep1Success - #1159............................................................................... ............. ....... 458

Table 345 - VS.DownsizingStep1SuccessNeighbRnc - #1160............................................................. ............. ....... 460

Table 346 - VS.DownsizingStep1Unsuccess - #1161........................................................................... ............. ....... 461

Table 347 - VS.DownsizingStep1UnsuccessNeighbRnc - #1162......................................................... ............. ....... 462

Table 348 - VS.DownsizingStep2Success - #1163............................................................................... ............. ....... 464

Table 349 - VS.DownsizingStep2SuccessNeighbRnc - #1164............................................................. ............. ....... 465

Table 350 - VS.UpsizingSuccess - #1165............................................................................................. ............. ....... 466

Table 351 - VS.UpsizingSuccessNeighbRnc - #1166........................................................................... ............. ....... 467

Table 352 - VS.UpsizingUnsuccess - #1167......................................................................................... ............. ....... 468

Table 353 - VS.UpsizingUnsuccessNeighbRnc - #1168....................................................................... ............. ....... 470

Table 354 - VS.IRMSchedulingDowngradedSuccess - #1169.............................................................. ............. ....... 471

Table 355 - VS.IRMSchedulingDowngradedFailure - #1170................................................................ ............. ....... 472

Table 356 - VS.IRMSchedulingDowngradedSuccessNeighbRnc - #1171............................................ ............. ....... 474

Table 357 - VS.IRMSchedulingDowngradedFailureNeighbRnc - #1172............................................................ ....... 475

Table 358 - VS.IrmUpgradingSuccessful - #1173................................................................................. ............. ....... 476

Table 359 - VS.IrmUpgradingCommand - #1174.................................................................................. ............. ....... 477

Table 360 - VS.IrmUpgradingCommandNrnc - #1175.......................................................................... ............. ....... 478

Table 361 - VS.IrmUpgradingSuccessfulNrnc - #1176......................................................................... ............. ....... 479

Table 362 - VS.QosDlCemLdClrYellow - #1177................................................................................... ............. ....... 480

Table 363 - VS.QosDlCemLdClrRed - #1178....................................................................................... ............. ....... 481

Table 364 - VS.QosDlCemLdCellPreemptClrCngstd - #1179............................................................... ............. ....... 482

Table 365 - VS.QosUlCemLdClrYellow - #1180................................................................................... ............. ....... 483

Table 366 - VS.QosUlCemLdClrRed - #1181....................................................................................... ............. ....... 484

Table 367 - VS.IrmTimeDlIubTransportColorRed - #1182.................................................................... ............. ....... 484

Table 368 - VS.IrmTimeDlIubTransportColorYellow - #1183................................................................ ............. ....... 485

Table 369 - VS.UlIrmcacMaintainedGold - #1184................................................................................. ............. ....... 486

Table 370 - VS.UlIrmcacMaintainedSilver - #1185............................................................................... ............. ....... 487

Table 371 - VS.UlIrmcacMaintainedBronze - #1186............................................................................. ............. ....... 488

Table 372 - VS.UlIrmcacDowngradedGold - #1187.............................................................................. ............. ....... 490

Table 373 - VS.UlIrmcacDowngradedSilver - #1188.......................................................................................... ....... 491

Table 374 - VS.UlIrmcacDowngradedBronze - #1189.......................................................................... ............. ....... 492

Table 375 - VS.UlIrmcacRejectedGold - #1190.................................................................................... ............. ....... 493

Table 376 - VS.UlIrmcacRejectedSilver - #1191................................................................................... ............. ....... 494

Table 377 - VS.UlIrmcacRejectedBronze - #1192................................................................................ ............. ....... 494

Alcatel-Lucent Confidential List of tables xv


Table 378 - VS.IRMTimeULRadioLoadColorYellow - #1193................................................................ ............. ....... 495

Table 379 - VS.IRMTimeULRadioLoadColorRed - #1194.................................................................... ............. ....... 496

Table 380 - VS.HsPdschDynCodeMgmtStealing - #1195..................................................................... ............. ....... 497

Table 381 - VS.HsPdschDynCodeMgmtRealloc - #1196...................................................................... ............. ....... 498

Table 382 - VS.NumHsPdschCodes - #1197........................................................................................ ............. ....... 499

Table 383 - VS.CommonMacDownlinkPcchSdu - #1213...................................................................... ............. ....... 501

Table 384 - VS.CommonMacDownlinkCcchSdu - #1214................................................................................... ....... 502

Table 385 - VS.CommonMacDownlinkDcchOverFachSdu - #1215...................................................... ............. ....... 503

Table 386 - VS.CommonMacDownlinkDtchOverFachSdu - #1216.................................................................... ....... 504

Table 387 - VS.CommonMacUplinkCcchSdu - #1217.......................................................................... ............. ....... 504

Table 388 - VS.CommonMacUplinkDcchOverRachSdu - #1218.......................................................... ............. ....... 505

Table 389 - VS.CommonMacUplinkDtchOverRachSdu - #1219........................................................... ............. ....... 506

Table 390 - VS.CommonRlcCcchDownlinkKbytes - #1220................................................................................ ....... 507

Table 391 - VS.CommonRlcCcchDownlinkSdu - #1221....................................................................... ............. ....... 508

Table 392 - VS.CommonRlcCcchDiscardSdu - #1222....................................................................................... ....... 509

Table 393 - VS.CommonRlcCcchPadding - #1223............................................................................... ............. ....... 510

Table 394 - VS.CommonUplinkTrafficChnlSyncFrames - #1224.......................................................... ............. ....... 510

Table 395 - VS.CommonUplinkTimingAdjustmentFrames - #1225.................................................................... ....... 511

Table 396 - VS.IurDrncRadioLinkSetupUnsuccess - #1302................................................................. ............. ....... 513

Table 397 - VS.IurDrncRadioLinkAdditionUnsuccess - #1304.............................................................. ............. ....... 514

Table 398 - VS.IurDrncRadioLinkDeletionSuccess - #1306............................................................................... ....... 516

Table 399 - VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess - #1308..................................... ............. ....... 517

Table 400 - VS.IurSccpCnxSuccess - #1311........................................................................................ ............. ....... 518

Table 401 - VS.IurSccpCnxUnsuccess - #1312.................................................................................... ............. ....... 519

Table 402 - VS.IurAvgNbrInitSccpCnx - #1315..................................................................................... ............. ....... 520

Table 403 - VS.IurAvgNbrTermSccpCnx - #1316................................................................................. ............. ....... 521

Table 404 - VS.IurEmittedSccpAbnormalDisconnects - #1317............................................................. ............. ....... 522

Table 405 - VS.IurReceivedSccpAbnormalDisconnects - #1318.......................................................... ............. ....... 523

Table 406 - VS.IurDrncRadioLinkReconfigurationCancel - #1319........................................................ ............. ....... 524

Table 407 - VS.IurDrncRadioLinkSetupSuccess - #1320..................................................................... ............. ....... 525

Table 408 - VS.IurDrncRadioLinkAdditionSuccess - #1321.................................................................. ............. ....... 526

Table 409 - VS.IurDrncRadioLinkReconfigurationPrepareSuccess - #1322......................................... ............. ....... 528

Table 410 - VS.IurDrncRadioLinkReconfigurationCommit - #1323....................................................... ............. ....... 530

Table 411 - VS.IurSrncRelocCommit - #1324....................................................................................... ............. ....... 532

Table 412 - VS.IurDrncRelocCommit - #1325....................................................................................... ............. ....... 532

Table 413 - VS.IuCsTimingAdjustmentRequests - #1437..................................................................... ............. ....... 535

Table 414 - VS.IuCsTimingAdjustmentAcks - #1438............................................................................ ............. ....... 536

Table 415 - VS.IuCsTimingAdjustmentNacks - #1439.......................................................................... ............. ....... 537

Table 416 - VS.IuCsTimingAdjustmentUnsupported - #1440............................................................... ............. ....... 539

Table 417 - VS.IuCsTimingAdjustmentTimeouts - #1441..................................................................... ............. ....... 540

Table 418 - VS.HsdpaIubFPDiscardedBytes - #1470........................................................................... ............. ....... 541

Table 419 - VS.DedicatedUplinkBadPdusRlcRefCell - #1471.............................................................. ............. ....... 542

Alcatel-Lucent Confidential List of tables xvi


Table 420 - VS.DedicatedUplinkKbytesRlc - #1472.............................................................................. ............. ....... 544

Table 421 - VS.DedicatedDownlinkKbytesRlc - #1473......................................................................... ............. ....... 545

Table 422 - VS.DedicatedUplinkPduRlc - #1474.................................................................................. ............. ....... 547

Table 423 - VS.DedicatedDownlinkPduRlc - #1475.............................................................................. ............. ....... 549

Table 424 - VS.DedicatedUplinkSduRlc - #1476.................................................................................. ............. ....... 550

Table 425 - VS.DedicatedDownlinkSduRlc - #1477.............................................................................. ............. ....... 552

Table 426 - VS.DedicatedUplinkMissingPduRlc - #1478...................................................................... ............. ....... 553

Table 427 - VS.DedicatedDownlinkDiscardSduRlc - #1479............................................................................... ....... 555

Table 428 - VS.DedicatedDownlinkPaddingSduRlc - #1480.............................................................................. ....... 557

Table 429 - VS.DedicatedUplinkBadPdus - #1481............................................................................... ............. ....... 559

Table 430 - VS.DedicatedUplinkKbytesRlcActiveCells - #1484............................................................ ............. ....... 561

Table 431 - VS.DedicatedDownlinkKbytesRlcActiveCells - #1485....................................................... ............. ....... 562

Table 432 - VS.DedicatedUplinkKbytesRlcReferenceCell - #1486....................................................... ............. ....... 564

Table 433 - VS.DedicatedDownlinkKbytesRlcReferenceCell - #1487.................................................. ............. ....... 566

Table 434 - VS.DedicatedUplinkPdusRlcReferenceCell - #1488.......................................................... ............. ....... 568

Table 435 - VS.DedicatedDownlinkPdusRlcReferenceCell - #1489..................................................... ............. ....... 570

Table 436 - VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell - #1490............................... ............. ....... 572

Table 437 - VS.RlcUnrecoverableError - #1491................................................................................................. ....... 574

Table 438 - VS.DlDiscardNonConfTraffic - #1492................................................................................ ............. ....... 576

Table 439 - VS.UlDiscardNonConfTraffic - #1493................................................................................ ............. ....... 577

Table 440 - VS.EdchIubTnlCongestIndc - #1494............................................................................................... ....... 579

Table 441 - VS.EdchMacTsnReassemblyErr - #1495........................................................................................ ....... 580

Table 442 - VS.EdchFpRetransHarq - #1496....................................................................................... ............. ....... 581

Table 443 - VS.BmcCtchTrafVol - #1497.............................................................................................. ............. ....... 582

Table 444 - VS.HsdschIubUlXoFrmCnt - #1502................................................................................... ............. ....... 583

Table 445 - VS.HsdschIubDlTrfcBlkTmCnt - #1503.............................................................................. ............. ....... 584

Table 446 - VS.DchIubDlTrfcBlkTmCnt - #1504................................................................................... ............. ....... 585

Table 447 - VS.IuDlAmrFrmFqc - #1505............................................................................................... ............. ....... 586

Table 448 - VS.DdUlAmrABtGoodFrm - #1506.................................................................................................. ....... 587

Table 449 - VS.DdUlAmrABtBadFrm - #1507....................................................................................... ............. ....... 589

Table 450 - VS.HsdpaIubDlControlFrames - #1508........................................................................................... ....... 590

Table 451 - VS.HsdpaIubNonZeroCapacityAlloc - #1509..................................................................... ............. ....... 591

Table 452 - VS.HsdpaIubZeroCapacityAlloc - #1510......................................................................................... ....... 592

Table 453 - VS.HsdpaIubCreditsRequested - #1511............................................................................ ............. ....... 592

Table 454 - VS.HsdpaIubCreditsConsumed - #1512............................................................................ ............. ....... 593

Table 455 - VS.AmrClDlRt - #1513....................................................................................................... ............. ....... 594

Table 456 - VS.AmrClUlRt - #1514....................................................................................................... ............. ....... 596

Table 457 - VS.DlAmrRtChg - #1515.................................................................................................... ............. ....... 597

Table 458 - VS.IuRcvdAmrRtCtrl - #1516............................................................................................. ............. ....... 598

Table 459 - VS.OvinCnAccLaDscrd - #1521......................................................................................... ............. ....... 599

Table 460 - VS.OvinNiDscrd - #1522.................................................................................................... ............. ....... 600

Table 461 - VS.OvinRabRrcConReqDscrd - #1523.............................................................................. ............. ....... 601

Alcatel-Lucent Confidential List of tables xvii


Table 462 - VS.DedicatedUplinkSduRlcRefCell - #1524.................................................................................... ....... 601

Table 463 - VS.DedicatedDownlinkSduRlcRefCell - #1525.................................................................. ............. ....... 603

Table 464 - VS.DedicatedDownlinkActivityRlcRefCell - #1526............................................................. ............. ....... 605

Table 465 - VS.DedicatedUplinkActivityRlcRefCell - #1527............................................................................... ....... 607

Table 466 - VS.IrmcacDistIubLoad - #1528.......................................................................................... ............. ....... 608

Table 467 - VS.DedicatedUplinkBadPdusRlcReferenceCell - #1529................................................... ............. ....... 609

Table 468 - VS.RRCAtt - #2001............................................................................................................ ............. ....... 614

Table 469 - VS.CallAttNorMoCs - #2002.............................................................................................. ............. ....... 616

Table 470 - VS.CallAttNorMoPs - #2003............................................................................................................ ....... 617

Table 471 - VS.CallAttNorMtCs - #2004............................................................................................... ............. ....... 618

Table 472 - VS.CallAttNorMtPs - #2005............................................................................................................. ....... 619

Table 473 - VS.CallAttMulMoCs - #2006.............................................................................................. ............. ....... 620

Table 474 - VS.CallAttMulMoPs - #2007............................................................................................................ ....... 621

Table 475 - VS.CallAttMulMtCs - #2008............................................................................................... ............. ....... 622

Table 476 - VS.CallAttMulMtPs - #2009............................................................................................................. ....... 623

Table 477 - VS.RabAttNorMoCs - #2010.............................................................................................. ............. ....... 624

Table 478 - VS.RabAttNorMoPs - #2011.............................................................................................. ............. ....... 625

Table 479 - VS.RabAttNorMtCs - #2012............................................................................................... ............. ....... 627

Table 480 - VS.RabAttNorMtPs - #2013............................................................................................... ............. ....... 628

Table 481 - VS.RabAttMulMoCs - #2014.............................................................................................. ............. ....... 629

Table 482 - VS.RabAttMulMoPs - #2015.............................................................................................. ............. ....... 630

Table 483 - VS.RabAttMulMtCs - #2016............................................................................................... ............. ....... 631

Table 484 - VS.RabAttMulMtPs - #2017............................................................................................... ............. ....... 632

Table 485 - VS.RabRspNorMoCs - #2018............................................................................................ ............. ....... 633

Table 486 - VS.RabRspNorMoPs - #2019............................................................................................ ............. ....... 634

Table 487 - VS.RabRspNorMtCs - #2020............................................................................................. ............. ....... 636

Table 488 - VS.RabRspNorMtPs - #2021............................................................................................. ............. ....... 636

Table 489 - VS.RabRspMulMoCs - #2022............................................................................................ ............. ....... 638

Table 490 - VS.RabRspMulMoPs - #2023............................................................................................ ............. ....... 639

Table 491 - VS.RabRspMulMtCs - #2024............................................................................................. ............. ....... 640

Table 492 - VS.RabRspMulMtPs - #2025............................................................................................. ............. ....... 641

Table 493 - VS.CallAnswNorMoCs - #2026.......................................................................................... ............. ....... 642

Table 494 - VS.CallAnswNorMoPs - #2027.......................................................................................... ............. ....... 643

Table 495 - VS.CallAnswNorMtCs - #2028........................................................................................... ............. ....... 645

Table 496 - VS.CallAnswNorMtPs - #2029........................................................................................... ............. ....... 646

Table 497 - VS.CallAnswMulMoCs - #2030.......................................................................................... ............. ....... 647

Table 498 - VS.CallAnswMulMoPs - #2031.......................................................................................... ............. ....... 648

Table 499 - VS.CallAnswMulMtCs - #2032........................................................................................... ............. ....... 649

Table 500 - VS.CallAnswMulMtPs - #2033........................................................................................... ............. ....... 650

Table 501 - VS.FailState1NorMo - #2034............................................................................................. ............. ....... 651

Table 502 - VS.FailNotState1NorMoCs - #2035................................................................................... ............. ....... 652

Table 503 - VS.FailNotState1NorMoPs - #2036................................................................................... ............. ....... 653

Alcatel-Lucent Confidential List of tables xviii


Table 504 - VS.FailState1NorMt - #2037.............................................................................................. ............. ....... 655

Table 505 - VS.FailNotState1NorMtCs - #2038.................................................................................... ............. ....... 655

Table 506 - VS.FailNotState1NorMtPs - #2039.................................................................................... ............. ....... 657

Table 507 - VS.FailNotState1MulMoCs - #2040................................................................................... ............. ....... 658

Table 508 - VS.FailNotState1MulMoPs - #2041................................................................................... ............. ....... 659

Table 509 - VS.FailNotState1MulMtCs - #2042.................................................................................... ............. ....... 661

Table 510 - VS.FailNotState1MulMtPs - #2043.................................................................................... ............. ....... 662

Table 511 - VS.LocRegRRCAtt - #2044............................................................................................................. ....... 663

Table 512 - VS.LocRegCallAtt - #2045................................................................................................. ............. ....... 664

Table 513 - VS.LocRegCallAnsw - #2046............................................................................................. ............. ....... 665

Table 514 - VS.LocRegFail - #2047...................................................................................................... ............. ....... 666

Table 515 - VS.PagingRsp - #2049.................................................................................................................... ....... 667

Table 516 - VS.CsMoState2Failure - #2050......................................................................................... ............. ....... 668

Table 517 - VS.PsMoState2Failure - #2051....................................................................................................... ....... 670





Table 522 - VS.CsMtState2Failure - #2056.......................................................................................... ............. ....... 675

Table 523 - VS.PsMtState2Failure - #2057........................................................................................................ ....... 676





Table 528 - VS.LocalRegState1Failure - #2062................................................................................................. ....... 682

Table 529 - VS.CsLocalRegState2Failure - #2063............................................................................... ............. ....... 683

Table 530 - VS.PsLocalRegState2Failure - #2064............................................................................... ............. ....... 684

Table 531 - VS.CsMoCallAvgHoldingTime - #2065.............................................................................. ............. ....... 685

Table 532 - VS.PsMoCallAvgHoldingTime - #2066.............................................................................. ............. ....... 686

Table 533 - VS.CsMtCallAvgHoldingTime - #2067............................................................................... ............. ....... 687

Table 534 - VS.PsMtCallAvgHoldingTime - #2068............................................................................... ............. ....... 688

Table 535 - VS.CsMoRabCallAvgSetupTime - #2069.......................................................................... ............. ....... 689

Table 536 - VS.PsMoRabCallAvgSetupTime - #2070........................................................................................ ....... 690

Table 537 - VS.CsMtRabCallAvgSetupTime - #2071........................................................................... ............. ....... 691

Table 538 - VS.PsMtRabCallAvgSetupTime - #2072......................................................................................... ....... 692

Table 539 - VS.RRCCdmaHOFromUtranCmd - #2101...................................................................................... ....... 694

Table 540 - VS.RRCCdmaHOFromUtranFail - #2102.......................................................................... ............. ....... 695

Table 541 - VS.RRCCdmaHOFromUtranComp - #2103.................................................................................... ....... 696

Table 542 - VS.RRCCdmaHOPrepAtt - #2104..................................................................................... ............. ....... 697

Table 543 - VS.RRCCdmaHOPrepFail - #2105.................................................................................... ............. ....... 697

Table 544 - VS.RRCCdmaHOPrePSucc - #2106................................................................................. ............. ....... 698

Table 545 - VS.RncCallCleanup - #3002.............................................................................................. ............. ....... 700

Alcatel-Lucent Confidential List of tables xix


Table 546 - SHO.AttRLAddUTRANSide - #SHO.AttRLAddUTRANSide.............................................. ............. ....... 702

Table 547 - SHO.SuccRLAddUTRANSide - #SHO.SuccRLAddUTRANSide....................................... ............. ....... 703

Table 548 - FAILED RADIO LINK CREATIONS (UTRAN SIDE) - #SHO.FailRLAddUTRANSide..................... ....... 704

Table 549 - SHO.AttRLDelUTRANSide - #SHO.AttRLDelUTRANSide................................................ ............. ....... 705

Table 550 - SHO.SuccRLDelUTRANSide - #SHO.SuccRLDelUTRANSide......................................... ............. ....... 706

Table 551 - ATTEMPTED OUTGOING CIRCUIT SWITCHED INTER-RAT HANDOVERS -#IRATHO.................................................................................................................................................

............. ....... 707

Alcatel-Lucent Confidential List of tables xx


1 About this publication

This publication provides a list of UMTS Access Network observation counters collected by theAPM/ADI applications of the Performance server.

This section consists of the following topics:

• "Applicability"

• "Audience"

• "Prerequisites"

• "Related publications"

• "How this publication is organized"

• "Vocabulary conventions"

Applicability

This publication applies to RAN 5.0 of the UMTS 5.1 System Release.

Audience

This publication is intended for network controllers responsible for the Performance Management ofthe UMTS Access Network.

Prerequisites

It is recommended that readers become familiar with the following Technical Publications :

• UMTS Access Network Performance Management (NN-20500-034)

• UMTS Access Network Overview (NN-20500-031) provides a functional overview of theOperation, Administration and Maintenance (OAM) subsystem of the Access Network.

Related publications• UMTS Access Network Performance Management (NN-20500-033)

How this publication is organized

This publication consists of the following modules:

• "Road map to Utran" presents the documents in the UTRAN documentation suite.

• "What is new in Access Network Observation Counters" presents the changes and, or thenew features introduced for the UMTS 5.1 release.

• "UMTS Access Network Performance Reference Observation Counters" is split into thefollowing sections:

Alcatel-Lucent Confidential 1


— "How Access Network observation counters are defined" provides information about thecounter definition template, counter types on the OAM GUI, and counter hierarchy.

— "How Access Network observation counters are described" describes the AccessNetwork observation counters.

• "RNC C-Node counter families" lists RNC C-Node counter families and presents their counters.Each counter is described separately in a table, and these tables are arranged in alphanumericalorder.

• Screening Appendices

• MIB Appendices

• CNode Counters Index presents the index of each Access Network observation counter.

Vocabulary conventions

For a list of UMTS terms used in this document, see the UMTS Access Terminology(NN-20500-002).

The specific acronyms used in this publication are the following:

A. Release Available Release

CC Cumulative Counter

CFN Connection Frame Number

CUM CUMulative

DER Discrete Event Registration counter

DTD Document Type Definition

mW milliWatt

NEI NEIghboring

SI Status Inspection

VAL VALue counter

The specific terms used in this publication are the following:

Access Stratum Config-uration

Pointer to a pre-defined set of Radio Bearers providing a given Ra-dio Access Bearer service.

For example:

• the Downlink (DL) access stratum configuration which number is1 is dedicated to voice support; it comprises the following RadioBearers : 3 x 12.2 Kbps CS RBs on DTCH and 3 x 3.4 KbpsSRB on DCCH.

• the DL access stratum configuration which number is 2 is dedic-ated to packet support at 64 Kbps; it comprises the following Ra-dio Bearers : 1 x 64 Kbps PS RB on DTCH and 3 x 3.4 KbpsSRB for DCCH.

Refer to the following configurations:



— Downlink Access Stratum Configuration (DASC)

— Downlink Radio Bearer Set Configuration (DRBSC)

— Uplink Access Stratum Configuration (UASC)

— Uplink Radio Bearer Set Configuration (URBSC)

Connection Frame Num-ber (CFN)

CFN is the frame counter used for the L2/transport channel syn-chronisation between UE and UTRAN. A CFN value is associated toeach Transport Block Set (TBS) and it is passed together with itthrough the MAC-L1 SAP. CFN provides a common frame reference(at L2) to be used that is for synchronized transport channel recon-figuration.

Measurement Term used in 3GPP TS 32.104 specifications. It has the samemeaning as the word 'counter' and is used in this publication to dis-tinguish a counter from a '(radio) measurement'.

Reference cell Cell ranking first in a UE active set considering a radio criteria , thatmeans the cell supposed to provide on average the best radio qual-ity for the reception of the next frames.

The reference cell is the primary cell considered in RRM.



2 Road map to UTRAN documentation

For collection roadmaps information, see UMTS Access Document Collection - Overview and updatesummary (NN-20500-050).



3 What's new

For information about What's new section, see : UTRAN 5.0 / W-NMS 5.1 Release OperationalImpactsNN-20500-052, Vol3, Annex C



4 Access Network observation counters

This section includes the following topics:

• "How Access Network observation counters are defined"

• "How Access Network observation counters are described"



4.1 How Access Network observation counters are defined

A standard observation counter is a device used in Performance Management to calculate thenumber of occurrences of an event. For further definitions for observation counters, refer to 3GPP TS32.104 specifications.

This section describes the following topics:

• "Counter families"

• "Object hierarchy"

• "Wording assumption"

• "Counter definition template"

• "Counter types on the OAM GUI"

• "Counter hierarchy"

• "Aggregation rules"

Counter families

The counters specified in this publication are grouped into families of counters. A family of countersis attached to a given UMTS feature. For example the "Radio Link Management Family" groupstogether counters involved with Radio Link Management (i.e.: Setup, Addition, Deletion,Reconfiguration..).

Object hierarchy

Counters are reported on objects (that is located) according to their hierarchy.

The following figure show the hierarchy of objects.



Figure 1 RNC C-Node containment tree

For more information about UTRAN objects and their relationships, refer to the UMTS AccessNetwork Overview (NN-20500-031) publication.

Wording assumption

Both wordings counter and measurement are equally used in this document to identify the sameconcept. Usually, Alcatel-Lucent uses the term counter to distinguish a counter from a (radio)measurement

3GPP Performance Management specifications preferably use measurement. When the contextrefers to 3GPP specifications, measurement is used, while counter is used in Alcatel-Lucentspecific part, but both wordings are equivalent.

Counter definition template

The following template used to describe the counters is extracted from 3GPP TS 32.104specifications.

Measurement name (section header)

This is a descriptive name of the measurement type.



A-Description

This section contains an explanation of the measurement operation.

B-Collection

This section contains the form of the obtained measurement data:

• CC (Cumulative Counter) is incremented by 1 each time the counted event occurs.

• GAUGE (dynamic variable), data being measured can vary during the period of measurement.

• DER (Discrete Event Registration), data related to a particular event is captured every nth event,where n can be 1 or larger.

• SI (Status Inspection), data related to the mean value is captured every nth sampling, where ncan be 1 or larger.

C-Condition (Event)

This section contains the condition that causes the measurement result data to be updated.

The condition is defined by identifying protocol related triggering events that either start or stop themeasurement processes or by updating the current measurement result value. When a precisecondition cannot be provided, the conditional circumstances behind the update are stated.

D-Result

This section contains a description of expected result value(s) (for example, a single integer value). Ifmore than one value is provided, the measurement is screened according to criteria, for example, anumber of call releases may be screened according to the cause of the call releases.

The number of call releases related to a given cause can be considered a subcounter. In that case,the measurement result specification item includes a 'screening paragraph' that specifies the varioussubcounters and their meanings.

E-Type

This section contains a short form of the measurement name specified in the header, which is usedto identify the measurement type in the result files.

F-Object Instance

This section contains the object class and its instance. The "measObjInstId" field identifies themeasured object class and its instance; for example, trunk1 means that object class trunk instance#1 is being measured. The object class and instance values used for this purpose will be inaccordance with 3GPP TS 32.106. This means the NE or resource object model (defined in the BasicCM IRP Information Model - 3GPP TS 32.106-5) and naming conventions (defined in the NamingConvention for Managed Objects - 3GPP TS 32.106-8). This parameter, if applicable, will be



provided in the measurement job.

G-Switching

This section contains the Switching domain(s). Its measurement is applicable to Circuit Switchedand, or Packet Switched domains.

H-3GPP Compliance

This section states the compliance of the Alcatel-Lucent measurement with 3GPP specifications:

• the statement is "3GPP specified counter" if the Alcatel-Lucent implementation is fully compliantwith the 3GPP specification.

• the statement is "Alcatel-Lucent specified counter" if the counter is not considered by the 3GPPspecification.

I-Range

This section contains the range of the counter.

J-Unit

This section contains the unit of the counter.

K-Available Release

This section states the Alcatel-Lucent UMTS system release(s) in which the counter had beenintroduced.

L-Aggregation Rule

This section contains one of these three values :RLoad, RVal and Rtotal. Each value defines theaggregation rule type. The counter type defines the aggregation rule value.

Three types of counters :

The three types of user-accessible observation counters available on the OAM GUI are as follows:

• CUMULATIVE (or TOTAL)

• VALUE

• LOAD

CUMULATIVE counters

CUMULATIVE counters provide raw counts. A CUMULATIVE counter is a CUM (CC) type counter,as identified in 3GPP TS 32.104 specifications. It is incremented by 1 each time the counted eventoccurs, and it provides the cumulated value. One NE cumulative counter provides one counter at the



OAM GUI level.

VALUE counters

VALUE counters are elaborated according to the mechanism defined by 3GPP TS 32.104, in order toimplement a DER (VAL) type measurement. This mechanism provides average values from rawcounts obtained by internal events (the time interval between two events is random and is notaccessible to users). The counter is incremented by a value attached to the event itself.Alcatel-Lucent provides the following:

• the cumulated value (.Cum in XML files)

• the number of events (.Nbevt in XML files)

• the averaged value (.Avg in XML files)

• the maximum added value (.Max in XML files)

• the minimum added value (.Min in XML files)

Note: The averaged value is equal to cumulated value over number of events

LOAD counters

LOAD counters are elaborated according to the mechanism defined by 3GPP TS 32.104, in order toimplement an SI type measurement. This mechanism provides average values from raw countsobtained by internal sampling (the time interval between two events is constant and is not accessibleto users). The counter is incremented by a sampled value on the sampling event occurrence.Alcatel-Lucent provides the following:

• the cumulated value (.Cum in XML files)

• the number of samplings (.Nbevt in XML files)

• the averaged value (.Avg in XML files)

• the maximum sampled value (.Max in XML files)

• the minimum sampled value (.Min in XML files)

Note: The averaged value is equal to cumulated value/number of samplings. This gives a timeweighted average.

Note: Alcatel-Lucent does not generally implement GAUGE type measurements becauseproviding the current value of a measurement by incrementing it by 1 when a positive event occursand by decrementing it by 1 when a negative event occurs, can lead to some shifts if an event ismissed.

Counter hierarchy

An observation counter stored in XML files can contain one or several levels.

A dot (.) separates two successive levels.

The following example shows the counter hierarchy with five levels.



Example:

radioLink.establishment.failure.cause<Name>.Avg

Counters with one level do not end with a dot.

Example:

droppedLastRadioLink

Aggregation rules

When aggregating counters from different periods of observation (temporal aggregation) you mustfollow the following rules.

Let X1,X2,...,Xn the measurements from periods 1,2,...,n and X the resulting value over the totalperiod.

The following table presents a rule for each counter.

Table 1 Table of aggregation rules

Rule Results Apply to

Rtotal X.cum = X1.cum + X2.cum + ... + Xn.cum CUM (CC) counters

Rload/Rval X.cum = X1.cum + ... + Xn.cum

X.nbevt = X1.nbevt + ... + Xn.nbevt

X.avg = (X1.cum + ... + Xn.cum) / (X1.nbevt + ... +Xn.nbevt)

X.min = min (X1.min,...,Xn.min)

X.max = max (X1.max,...,Xn.max)

Some LOAD and VALcounters

Rload* Same as Rload but resulting X.cum has no phys-ical meaning due to the nature of the measure-ment (like percents) and is not interpreted but isnecessary for intermediate computations.

Some LOAD counters

Ravg X = Xi / n

where Xi (i = 1 to n) represent average values

Passport counters

Radd X = ΣXi

where Xi (i = 1 to n) represent cumulative values

Passport counters

Rmin X = min (Xi)

where Xi (i = 1 to n) represent minimum values

Passport counters

Rmax X = max (Xi)

where Xi (i = 1 to n) represent maximum values

Passport counters



4.2 How Access Network observation counters are described

An observation counter is a measurement used to report data for network PerformanceManagement.

Observation counters are stored in XML record files. These XML files are created by theperformance server through mediation of the raw data files obtained from the CNode.

Each record file contains the counters produced by a single NE collection.

Access Network observation counters handled by the ADI application for the UMTS 5.1 systemrelease are as follows:

• C-Node application counters

• I-Node platform counters

• Node B counters

These counters have been divided into the three following sets of families:

• "RNC counter families"

• "BTS counter families"

• "Passport counter families"

Each counter family is attached to a given UMTS feature (for example, Handover counters, wherehard handover performances are reported) or to a Performance Management purpose for example,User Plane Traffic counters, where counters related to traffic observation are grouped together).

Access observation file structure

Some observation counters are processed in order to provide temporal and spatial aggregations. Thefollowing observation counter records are available:

• single period

• hourly aggregated

• daily aggregated

Each observation file produces single, hourly and daily observation counter records. At the dedicatedNE level, a predetermined subset of these data are aggregated.

The following figure illustrates an example of the aggregated observation file structure.

The file name convention for an observation is as follows:

<type><startdate>.<starttime>-<endtime>_<NE>.xml.

Where:



type is set to A which indicates one of the following aggregated observations:

• the observation file contains data originated from a single NE for a unique time period.

• the observation file contains data originated from a single NE for an hourly aggregated file.

• the observation file contains data originated from a single NE for a daily aggregated file.

startdate is the beginning date of the granularity period; its format must be <YYYYMMDD>.

starttime is the beginning time of the granularity period; its format must be <hhmm+#GMT>.

endtime is the end time of the granularity period; its format must be <hhmm+#GMT>.

NE is the Network Element type ID that means a unique numerical identifier as 3GPP using<NE Type>-<NE userlabel> _[CN|AN|IN] pattern (for example, RNC-RNC535_CN). Or the BTSname using the NE userLabel as a NE ID (for example BTSEq-A10km215).

Refer to the following table for an interpretation of the codes:

Code Description

YYYY The 4-digit year

MM The month of the year (01, 02,..., 12) for file creation time at RNC level

DD The day of the month (01, 02,..., 31) for file creation time at RNC level

hh The 2-digit hour (00, 01,..., 23). In the case of daily aggregation files, hh is al-ways 00.

mm The 2-digit minute of the hour. Possible values are by increments of fiveminutes: 00, 05, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55. In the case ofhourly or daily aggregation files, mm is always 00.

#GMT Difference between local time and Greenwich Meridian Time (+/-hhmm). At10:15:02 in Paris, the 13 April 2005 in Paris, the #GMT is +0100 = thehhmm#GMT is 1015+0100.At 18:12:11 in New York, the 13 April 2005, the#GMT is #0500 = the hhmm#GMT is 1812-0500.

RNC observation XML file

The XML format is compliant with 3 GPP dtd file: 32.401-02.dtd. The granularity period defines, inminutes, the periodicity of the generation of the counter; the values supported are 15, 30 and 60.

The directory of the RNC C-Node observation XML file on PerfServer is as follows:

/opt/nortel/data/utran/observation/stats/<YYYYMMDD>/<RNC>–<RNCUserLabel>_CN

Example:

/opt/nortel/data/utran/observation/stats/20070113/RNCCN-RNC2453

For more information about RNC XML record files, refer to the UMTS Access Network PerformanceManagement(NN-20500-034) publication.

RNC C-Node observation during OMU SWACT



The OMU SWACT (SWitch of ACTivity) is a mechanism allowing to switch over the active OMU. Thismechanism is specific to the RNC C-Node.

When an OMU SWACT occurs, counters do not appear in PrOptma application for the 15-minutewindow, and the file transmitted from the new active OMU to the perfServer contains only a portion ofdata.

Let the following example based on a 15-minute collect time, the last collect launched by OMU at2:15 p.m., and notification sent and received at 2:20 p.m. (that means the preceding collect is endedand is correctly handled)

The impacts of the OMU SWACT are given in the following cases:

• Case 1. If SWACT occurs at 2:21 p.m., thus after the last collect or notification, and the restarttakes one minute, the TMUs remain running and computing statistics; at 2:30 p.m., the OMU willsend a collect request to all entities. Therefore there is no impact from OAM.

• Case 2: If SWACT occurs at 2:29 p.m., and when the OMU becomes active again, for example at2:32 p.m., it will be too late to send a collect request. Therefore the next collect time will be at2.45pm and lasts 30 minutes. This is a restriction.

• Case 3. If the collect request is sent at 2:30 p.m. but OMU SWACT occurs at 2:31 p.m. beforeany end of computing or before all the TMUs have time to send to the OMU their collect, the filewill be closed, and remain on disk with only header, or part of the information or all of theinformation if writing already started. The next period of collect will be aligned on the correct15-minute period. Therefore there is no notification sent to the OAM, and the period of collectfrom 2:25 to 2:30 p.m. is lost. The next collect will be on a valid period. This is a restriction.

• Case 4. If the collect request is sent at 2:30 p.m. but not all the LAs have received the collectrequest before SWACT occurs, that occurrence is quite rare, but remains possible. Thereforethere is no collect for 2:15 p.m. to 2:30 p.m. period, and a bad collect period from 2:30 p.m. to2:45 p.m. is recorded. This is a restriction.



5 RNC C-Node counter families

• Radio Link Management

• Handover

• Soft Handover

• Power Management

• RRC Connection

• IU Connection

• RAB and RB Management

• Security

• Paging

• Mobility

• Radio Measurement

• QOS Performance

• User Plane Common Traffic

• IUR Interface

• User Plane Dedicated Traffic

• Statistic Counter

• CDMA Handover

• Platform

• Synthetic



5.1 Radio Link Management

The reference document for NBAP management is 3GPP TS25.433 UTRAN Iub Interface NBAPSignaling.

Alcatel-Lucentcounter number

Counter name

#2 VS.RadioLinkSetupUnsuccess

#4 VS.RadioLinkAdditionUnsuccess

#5 VS.RadioLinkDeletionSuccess

#6 VS.RadioLinkDeletionUnsuccess

#8 VS.RadioLinkReconfigurationPrepareUnsuccess

#15 VS.RrcSleepyCellInactivity

#16 VS.RlSleepyCellInactivity

#17 VS.PagingSleepyCellInactivity

#18 VS.RadioLinkFailureIndication

#20 VS.RadioLinkFirstSetupFailure

#25 VS.UeWithNRadioLinksEstCellsBts

#26 VS.RadioLinkReconfigurationCancel

#27 VS.RadioLinkFirstSetupRequest

#29 VS.RadioLinkSetupSuccess

#30 VS.RadioLinkAdditionSuccess

#31 VS.RadioLinkReconfigurationPrepareSuccess

#32 VS.RadioLinkReconfigurationCommit

#33 VS.RadioLinkEstablishedPerCell

#34 VS.RadioLinkDroppedLastRadioLink

#35 VS.RadioLinkSetupRequest

#36 VS.RadioLinkAdditionReq

#37 VS.RadioLinkReconfPrepReq

Table 2 VS.RadioLinkSetupUnsuccess - #2

A-Description

the number of radio links failed in setup on a NBAP point of view, screened by detecting event.

B-Collection

CUM

CUMulative



C-Condition (Event)

This measurement is based on three different events: - RNC Call Admission Control refusingthe establishment of the new radio link (lack of RF Power, OVSF code or ATM resources) - Re-ceipt of a NBAP RADIO LINK SETUP FAILURE message sent by Node B to the ControllingRNC in response to a RADIO LINK SETUP REQUEST message (the measurement considerseach Radio Link referred as failed in the NBAP RADIO LINK SETUP FAILURE message). -Time-out expired without reception of a RADIO LINK SETUP RESPONSE message or RADIOLINK SETUP FAILURE message (the measurement considers each Radio Link required to set-up in the NBAP RADIO LINK SETUP REQUEST message).

D-Result

A set of subcounters screened on: Family error cause.25433 (9.2.1.6 cause), or time-out.Causes are not screened

• Sub-Counter #0 : RADIO_LINK_SETUP_FAILURE

• Sub-Counter #1 : Timeout

• Sub-Counter #2 : Rrm refusal

• Sub-Counter #3 : Unused

• Sub-Counter #4 : Rrm refusal (DL NodeB resource lack, or NodeB resource lack)

• Sub-Counter #5 : Rrm refusal (UL NodeB resource lack)

• Sub-Counter #6 : Lack of CID on the Iub

• Sub-Counter #7 : Lack of bandwidth on the Iub

• Sub-Counter #8 : INode refusal

E-Type

• VS.RadioLinkSetupUnsuccess.VS.RadioLinkSetupUnsuccess.RadioLinkSetupFailure

• VS.RadioLinkSetupUnsuccess.VS.RadioLinkSetupUnsuccess.TimeOut

• VS.RadioLinkSetupUnsuccess.VS.RadioLinkSetupUnsuccess.RrmRefusal

• VS.RadioLinkSetupUnsuccess.VS.RadioLinkSetupUnsuccess.unused

• VS.RadioLinkSetupUnsuccess.VS.RadioLinkSetupUnsuccess.LackOfNodeBDlProcessingResources

• VS.RadioLinkSetupUnsuccess.VS.RadioLinkSetupUnsuccess.LackOfNodeBUlProcessingResources

• VS.RadioLinkSetupUnsuccess.VS.RadioLinkSetupUnsuccess.LackCidIub

• VS.RadioLinkSetupUnsuccess.VS.RadioLinkSetupUnsuccess.LackBwthIub

• VS.RadioLinkSetupUnsuccess.VS.RadioLinkSetupUnsuccess.InodeRefusal

F-Object Instance

Cell

G-Switching



NA

H-3GPP Compliance

N-ALCATEL-LUCENT specified counter-#2

I-Range

31 Bits

J-Unit

event

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 3 VS.RadioLinkAdditionUnsuccess - #4

A-Description

Number of unsuccessfull radio link setup

B-Collection

CUM

CUMulative

C-Condition (Event)

unsuccessfull management of radio link setup (RADIO_LINK_SETUP_FAILURE ORTIMEOUT) (counted per radio link and not per message)

D-Result

A set of subcounters screened on: Family error cause.25433 (9.2.1.6 cause) and Timeout.Causes are not screened

• Sub-Counter #0 : RADIO_LINK_ADDITION_FAILURE






E-Type

• VS.RadioLinkAdditionUnsuccess.VS.RadioLinkAdditionUnsuccess.RadioLinkAdditionFailure



• VS.RadioLinkAdditionUnsuccess.VS.RadioLinkAdditionUnsuccess.Timeout

• VS.RadioLinkAdditionUnsuccess.VS.RadioLinkAdditionUnsuccess.RrmRefusal

• VS.RadioLinkAdditionUnsuccess.VS.RadioLinkAdditionUnsuccess.INodeRefusal

• VS.RadioLinkAdditionUnsuccess.VS.RadioLinkAdditionUnsuccess.LackOfNodeBDlProcessingResources

• VS.RadioLinkAdditionUnsuccess.VS.RadioLinkAdditionUnsuccess.LackOfNodeBUlProcessingResources

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance

N-Alcatel-Lucent defined counter-#4

I-Range

31 Bits

J-Unit

event

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 4 VS.RadioLinkDeletionSuccess - #5

A-Description

the number of radio-links successfully deleted on a NBAP point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a NBAP RADIO LINK DELETION RESPONSE message sent by Node B to theServing RNC in response to a RADIO LINK DELETION REQUEST. The measurement con-siders each Radio Link referred in the NBAP RADIO LINK DELETION RESPONSE message

D-Result

one measurement



E-Type

VS.RadioLinkDeletionSuccess

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V1.2

L-Aggregation Rule

Rtotal

Table 5 VS.RadioLinkDeletionUnsuccess - #6

A-Description

the number of radio links failed in deletion on a NBAP point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Time-out expired without reception of a RADIO LINK DELETION RESPONSE

D-Result

one measurement

E-Type

VS.RadioLinkDeletionUnsuccess

F-Object Instance

Cell

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V1.2

L-Aggregation Rule

Rtotal

Table 6 VS.RadioLinkReconfigurationPrepareUnsuccess - #8

A-Description

the number of times a radio link failed to do reconfiguration preparation.

B-Collection

CUM

CUMulative

C-Condition (Event)

This measurement is based on four different events: - Receipt of a NBAP RADIO LINK RE-CONFIGURATION FAILURE message sent by Node B to the Controlling RNC in response to aRADIO LINK RECONFIGURATION PREPARE message. - No reception of RADIO LINK RE-CONFIGURATION READY message before a time-out - RRM refusal (e.g. no power alloca-tion, no code allocation) - RNC I-Node refusal (e.g. no CID allocation)

D-Result

A set of subcounters screened on: Family error cause.25433 (9.2.1.6 cause) and Timeout.Causes are not screened

• Sub-Counter #0 : RADIO_LINK_RECONFIGURATION_FAILURE

• Sub-Counter #1 : Timeout nbap










E-Type

• VS.RadioLinkReconfigurationPrepareUnsuccess.VS.RadioLinkReconfigurationPrepareUnsuccess.RadioLinkReconfigurationFailure

• VS.RadioLinkReconfigurationPrepareUnsuccess.VS.RadioLinkReconfigurationPrepareUnsuccess.TimeoutNbap

• VS.RadioLinkReconfigurationPrepareUnsuccess.VS.RadioLinkReconfigurationPrepareUnsuccess.RrmRefusal

• VS.RadioLinkReconfigurationPrepareUnsuccess.VS.RadioLinkReconfigurationPrepareUnsuccess.unused

• VS.RadioLinkReconfigurationPrepareUnsuccess.VS.RadioLinkReconfigurationPrepareUnsuccess.LackOfNodeBDlProcessingResources

• VS.RadioLinkReconfigurationPrepareUnsuccess.VS.RadioLinkReconfigurationPrepareUnsuccess.LackOfNodeBUlProcessingResources

• VS.RadioLinkReconfigurationPrepareUnsuccess.VS.RadioLinkReconfigurationPrepareUnsuccess.LackCid

• VS.RadioLinkReconfigurationPrepareUnsuccess.VS.RadioLinkReconfigurationPrepareUnsuccess.LackBwthIub

• VS.RadioLinkReconfigurationPrepareUnsuccess.VS.RadioLinkReconfigurationPrepareUnsuccess.INodeRefusal

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 7 VS.RrcSleepyCellInactivity - #15



A-Description

This measurement represents the number of minutes since last RRC activity was detected forthis cell. The number of minutes is rounded down to the nearest multiple of minutes in a report-ing period.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reset to zero on an RRC Connection Setup Complete on this cell..

D-Result

one measurement

E-Type

VS.RrcSleepyCellInactivity

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

minutes

K-Available Release

V4.1

L-Aggregation Rule

Rnone

Table 8 VS.RlSleepyCellInactivity - #16

A-Description

This measurement represents the number of minutes since last NBAP Radio-link activity wasdetected for this cell. The number of minutes is rounded down to the nearest multiple ofminutes in a reporting period.

B-Collection



CUM

CUMulative

C-Condition (Event)

Reset to zero on an NBAP RL Setup Response on this cell..

D-Result

one measurement

E-Type

VS.RlSleepyCellInactivity

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

minutes

K-Available Release

V4.1

L-Aggregation Rule

Rnone

Table 9 VS.PagingSleepyCellInactivity - #17

A-Description

This measurement represents the number of minutes since the last successful paging activity.The number of minutes is rounded down to the nearest multiple of minutes in a reporting peri-od.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reset to zero on an RRC Connection Request with any cause that is mobile-terminating



(response to a paging) on this cell..

D-Result

one measurement

E-Type

VS.PagingSleepyCellInactivity

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

minutes

K-Available Release

V4.1

L-Aggregation Rule

Rnone

Table 10 VS.RadioLinkFailureIndication - #18

A-Description

the number of NBAP RADIO_LINK_FAILURE message received from the Node B. The call willnot drop if there are still other radio-links in the active set.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of NBAP RADIO_LINK_FAILURE for a radio-link in this cell.

D-Result

A set of subcounters screened on: Failure cause

• Sub-Counter #0 : OAM Intervention

• Sub-Counter #1 : Invalid CM Settings



• Sub-Counter #2 : Transport Resources Unavailable

• Sub-Counter #3 : Control Processing Overload

• Sub-Counter #4 : Synchronisation Failure

• Sub-Counter #5 : Hardware Failure

• Sub-Counter #6 : Not enough resources for CM

• Sub-Counter #7 : IMA Defense

• Sub-Counter #8 : Other Causes

E-Type

• VS.RadioLinkFailureIndication.VS.RadioLinkFailureIndication.OamIntervention

• VS.RadioLinkFailureIndication.VS.RadioLinkFailureIndication.InvalidCmSettings

• VS.RadioLinkFailureIndication.VS.RadioLinkFailureIndication.TransportResourcesUnavailable

• VS.RadioLinkFailureIndication.VS.RadioLinkFailureIndication.ControlProcessingOverload

• VS.RadioLinkFailureIndication.VS.RadioLinkFailureIndication.SynchronisationFailure

• VS.RadioLinkFailureIndication.VS.RadioLinkFailureIndication.HardwareFailure

• VS.RadioLinkFailureIndication.VS.RadioLinkFailureIndication.NotEnoughResourcesForCm

• VS.RadioLinkFailureIndication.VS.RadioLinkFailureIndication.ImaDefense

• VS.RadioLinkFailureIndication.VS.RadioLinkFailureIndication.OtherCauses

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal



Table 11 VS.RadioLinkFirstSetupFailure - #20

A-Description

the number of failures on the first Radio-Link setup (see counter #0019). This excludes Radio-link setups for soft handover.

B-Collection

CUM

CUMulative

C-Condition (Event)

This measurement is based on three different events (only in case of first NBAP RL Setup): -NBAP RADIO LINK SETUP REQUEST no sent by the RNC because of Call Admission Controlrejection - Receipt of a NBAP RADIO LINK SETUP FAILURE message sent by Node B to theControlling RNC in response to a RADIO LINK SETUP REQUEST message (the measurementconsiders each Radio Link referred as failed in the NBAP RADIO LINK SETUP FAILURE mes-sage). - Time-out expired without reception of a RADIO LINK SETUP RESPONSE message orRADIO LINK SETUP FAILURE message (The measurement considers each Radio Link re-quired to set-up in the NBAP RADIO LINK SETUP REQUEST message)

D-Result

A set of subcounters screened on: Family error cause.25433 (9.2.1.6 cause), or time-out.Causes are not screened

• Sub-Counter #0 : RADIO_LINK_SETUP_FAILURE









E-Type

• VS.RadioLinkFirstSetupFailure.VS.RadioLinkFirstSetupFailure.RadioLinkSetupFailure

• VS.RadioLinkFirstSetupFailure.VS.RadioLinkFirstSetupFailure.TimeOut

• VS.RadioLinkFirstSetupFailure.VS.RadioLinkFirstSetupFailure.RrmRefusal

• VS.RadioLinkFirstSetupFailure.VS.RadioLinkFirstSetupFailure.unused

• VS.RadioLinkFirstSetupFailure.VS.RadioLinkFirstSetupFailure.LackOfNodeBDlProcessingResources

• VS.RadioLinkFirstSetupFailure.VS.RadioLinkFirstSetupFailure.LackOfNodeBUlProcessing



Resources

• VS.RadioLinkFirstSetupFailure.VS.RadioLinkFirstSetupFailure.LackCidIub

• VS.RadioLinkFirstSetupFailure.VS.RadioLinkFirstSetupFailure.LackBwthIub

• VS.RadioLinkFirstSetupFailure.VS.RadioLinkFirstSetupFailure.InodeRefusal

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 12 VS.UeWithNRadioLinksEstCellsBts - #25

A-Description

Distribution of the number of mobiles having N Radio-Links in their Active Set

B-Collection

LOAD

C-Condition (Event)

NBAP Radio link setup response, NBAP Radio link addition response, NBAP Radio link addi-tion failure (if some radio link are successful), NBAP Radio link deletion request, Change ofprimary cell (sending of RRC MEASUREMENT CONTROL)

D-Result

A set of subcounters screened on: Number of radio links

• Sub-Counter #0 : 1 Radio Link

• Sub-Counter #1 : 2 RL (Reference Cell + 1 RL on the same BTS)

• Sub-Counter #2 : 2 RL (Reference Cell + 1 RL on another BTS)



• Sub-Counter #3 : 3 RL (Reference Cell + 2 RL on the same BTS)

• Sub-Counter #4 : 3 RL (Reference Cell + 1 RL on the same BTS + 1 RL on another BTS)








• Sub-Counter #12 : 6 RL or more (Reference Cell + 2 RL on the same BTS + 3 or more RLon another BTS)

• Sub-Counter #13 : 6 RL or more (Reference Cell + 1 RL on the same BTS + 4 or more RLon another BTS)

• Sub-Counter #14 : 6 RL or more (Reference Cell + 5 or more RL on another BTS)

E-Type

• VS.UeWithNRadioLinksEstCellsBts.VS.UeWithNRadioLinksEstCellsBts.N1Rl

• VS.UeWithNRadioLinksEstCellsBts.VS.UeWithNRadioLinksEstCellsBts.N2RL1Rc1SBts

• VS.UeWithNRadioLinksEstCellsBts.VS.UeWithNRadioLinksEstCellsBts.N2RL1Rc1ABts

• VS.UeWithNRadioLinksEstCellsBts.VS.UeWithNRadioLinksEstCellsBts.N3RL1Rc2SBts

• VS.UeWithNRadioLinksEstCellsBts.VS.UeWithNRadioLinksEstCellsBts.N3RL1Rc1SBts1ABts













F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 13 VS.RadioLinkReconfigurationCancel - #26

A-Description

the number of NBAP RADIO LINK RECONFIGURATION CANCEL messages.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a NBAP RADIO LINK RECONFIGURATION CANCEL message by the RNC to aNode B.

D-Result

one measurement

E-Type

VS.RadioLinkReconfigurationCancel

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 14 VS.RadioLinkFirstSetupRequest - #27

A-Description

the number of NBAP Radio-Link setups for the first radio-link of a call (call establishment). Thisexcludes Radio-link setups for soft handover. If the call has been through cell_FACH (AlwaysON in Cell_FACH for example for a PS call), then the counter will also be incremented whenthe call goes back to Cell_DCH.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of the first NBAP RADIO LINK SETUP REQUEST towards Node B since the UE is incell_DCH : - cell_FACH to cell_DCH transition (at call establishment or Always ON upsizing) -RRC Connection Setup on Cell_DCH - incoming relocation

D-Result

one measurement

E-Type

VS.RadioLinkFirstSetupRequest

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 15 VS.RadioLinkSetupSuccess - #29

A-Description

the number of radio-links successfully setup on a NBAP point of view, screened by DownlinkAccess Stratum configuration.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a "RADIO LINK SETUP RESPONSE" or "RADIO LINK SETUP FAILURE" NBAPmessage sent by Node B to the Controlling RNC in response to a RADIO LINK SETUP RE-QUEST message. The measurement considers each Radio Link mentioned as set-up in the"RADIO LINK SETUP RESPONSE" or "RADIO LINK SETUP FAILURE" NBAP message.

D-Result

A set of subcounters screened on: Target type of call for Radio Link Reconfiguration , see alsoAnnex: T05

• Sub-Counter #0 : Other Type of Call

• Sub-Counter #1 : Signalling Only

• Sub-Counter #2 : CS speech

• Sub-Counter #3 : CS data

• Sub-Counter #4 : Any CS Streaming

• Sub-Counter #5 : Any PS Streaming

• Sub-Counter #6 : Any PS interactive/background

• Sub-Counter #7 : CS speech and any PS interactive/background

• Sub-Counter #8 : CS data and any PS interactive/background

• Sub-Counter #9 : PS Streaming and any PS interactive/background

• Sub-Counter #10 : CS speech and any PS streaming



• Sub-Counter #11 : CS speech and any PS streaming and any PS interactive/background

E-Type

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfOther

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfSig

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfCsSpeech

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfCsData

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfCsStr

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfPsStr

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfPsIB

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfCsSpeechPsIB

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfCsDataPsIB

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfPsStrPsIB

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfCsSpeechPsStr

• VS.RadioLinkSetupSuccess.VS.RadioLinkSetupSuccess.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 16 VS.RadioLinkAdditionSuccess - #30

A-Description

the number of radio-links successfully added on a NBAP point of view, screened by DownlinkAccess Stratum configuration.



B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a RADIO LINK ADDITION RESPONSE or RADIO LINK ADDITION FAILURE NBAPmessage sent by Node B to the Controlling RNC in response to a RADIO LINK SETUP RE-QUEST message. The measurement considers each Radio Link mentioned as added in theRADIO LINK ADDITION RESPONSE or RADIO LINK ADDITION FAILURE NBAP message.

D-Result














E-Type

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfOther

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfSig

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfCsSpeech

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfCsData

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfCsStr

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfPsStr

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfPsIB

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfCsSpeechPsIB

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfCsDataPsIB

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfPsStrPsIB



• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfCsSpeechPsStr

• VS.RadioLinkAdditionSuccess.VS.RadioLinkAdditionSuccess.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 17 VS.RadioLinkReconfigurationPrepareSuccess - #31

A-Description

the number of radio-links successfully prepared for reconfiguration, screened by Downlink Ac-cess Stratum configuration.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a valid NBAP RADIO LINK RECONFIGURATION READY message. The meas-urement considers each Radio Link referred in the NBAP RADIO LINK RECONFIGURATIONREADY message.

D-Result
















E-Type

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfOther

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfSig

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfCsSpeech

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfCsData

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfCsStr

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfPsStr

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfPsIB

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfCsSpeechPsIB

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfCsDataPsIB

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfPsStrPsIB

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfCsSpeechPsStr

• VS.RadioLinkReconfigurationPrepareSuccess.VS.RadioLinkReconfigurationPrepareSuccess.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 18 VS.RadioLinkReconfigurationCommit - #32

A-Description

the number of NBAP RADIO LINK RECONFIGURATION COMMIT messages.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a NBAP RADIO LINK RECONFIGURATION COMMIT message by the RNC to aNode B

D-Result
















E-Type

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfOther

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfSig

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfCsSpeech

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfCsData

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfCsStr

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfPsStr

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfPsIB

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfCsSpeechPsIB

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfCsDataPsIB

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfPsStrPsIB

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfCsSpeechPsStr

• VS.RadioLinkReconfigurationCommit.VS.RadioLinkReconfigurationCommit.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule



Rtotal

Table 19 VS.RadioLinkEstablishedPerCell - #33

A-Description

the average, minimum and maximum number of NBAP radio-links established in a cell during areporting period.

B-Collection

LOAD

C-Condition (Event)

Each setup success, delete success, delete un-success, addition success on a radio-link of thecell (counted per radio-link and not per message). The number of radio-links is sampled each100ms.

D-Result














E-Type

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfOther

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfSig

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfCsSpeech

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfCsData

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfCsStr

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfPsStr

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfPsIB



• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfCsSpeechPsIB

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfCsDataPsIB

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfPsStrPsIB

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfCsSpeechPsStr

• VS.RadioLinkEstablishedPerCell.VS.RadioLinkEstablishedPerCell.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 20 VS.RadioLinkDroppedLastRadioLink - #34

A-Description

the number of dropped calls (on last radio-link release), for each cell controlled by the RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

On reception of NBAP RL Failure Indication which force the communication to be lost. Themeasurement is only incremented by one even if more than one radio-link fail simultaneouslyand make the call to be dropped. It is incremented on last failing FDDCell (which is in fact thelast reference cell for the call).

D-Result



A set of subcounters screened on: Type of call for dropped last radio link , see also Annex: T13


• Sub-Counter #1 : SRB (DCH or cell FACH)




• Sub-Counter #5 : Any PS I/B or PS Streaming

• Sub-Counter #6 : HSDPA

E-Type

• VS.RadioLinkDroppedLastRadioLink.VS.RadioLinkDroppedLastRadioLink.DlAsCnfOther

• VS.RadioLinkDroppedLastRadioLink.VS.RadioLinkDroppedLastRadioLink.DlAsCnfSig

• VS.RadioLinkDroppedLastRadioLink.VS.RadioLinkDroppedLastRadioLink.DlAsCnfCsSpeech

• VS.RadioLinkDroppedLastRadioLink.VS.RadioLinkDroppedLastRadioLink.DlAsCnfCsData

• VS.RadioLinkDroppedLastRadioLink.VS.RadioLinkDroppedLastRadioLink.DlAsCnfCsStr

• VS.RadioLinkDroppedLastRadioLink.VS.RadioLinkDroppedLastRadioLink.DlAsCnfPsIbPsStr

• VS.RadioLinkDroppedLastRadioLink.VS.RadioLinkDroppedLastRadioLink.DlAsCnfHsdpa

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 21 VS.RadioLinkSetupRequest - #35



A-Description

Number of internal events that would lead to a radio link setup request

B-Collection

CUM

CUMulative

C-Condition (Event)

Internal event that would lead to the sending of NBAP Radio Link Setup Request message(tobe counted per radio link and not per message).

D-Result














E-Type

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfOther

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfSig

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfCsSpeech

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfCsData

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfCsStr

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfPsStr

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfPsIB

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfCsSpeechPsIB

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfCsDataPsIB

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfPsStrPsIB



• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfCsSpeechPsStr

• VS.RadioLinkSetupRequest.VS.RadioLinkSetupRequest.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 22 VS.RadioLinkAdditionReq - #36

A-Description

Number of internal events that would lead to a radio link addition request.

B-Collection

CUM

CUMulative

C-Condition (Event)

Internal event that would lead to the sending of NBAP Radio Link Addition Request mes-sage(to be counted per radio link and not per message).

D-Result
















E-Type

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfOther

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfSig

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfCsSpeech

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfCsData

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfCsStr

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfPsStr

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfPsIB

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfCsSpeechPsIB

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfCsDataPsIB

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfPsStrPsIB

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfCsSpeechPsStr

• VS.RadioLinkAdditionReq.VS.RadioLinkAdditionReq.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0



L-Aggregation Rule

Rtotal

Table 23 VS.RadioLinkReconfPrepReq - #37

A-Description

Number of internal event that would lead a radio link reconfiguration prepare.

B-Collection

CUM

CUMulative

C-Condition (Event)

Internal event that would lead to the sending of NBAP Radio Link reconfiguration prepare mes-sage (to be counted per radio link and not per message).

D-Result














E-Type

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfOther

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfSig

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfCsSpeech

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfCsData

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfCsStr

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfPsStr



• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfPsIB

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfCsSpeechPsIB

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfCsDataPsIB

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfPsStrPsIB

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfCsSpeechPsStr

• VS.RadioLinkReconfPrepReq.VS.RadioLinkReconfPrepReq.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.2 Handover

The reference document for hard hand-overs, detailing data flows and procedures, isUMT/SYS/DD/0054 UMTS Radio Mobility.


Counter name

#106 VS.RrcCellChangeOrderNeighbRnc

#108 VS.RrcCellChangeOrderFailureNeighbRnc

#122 VS.WithoutIurIncomingHardHoAttempt

#123 VS.WithoutIurIncomingHardHoFailure

#124 VS.WithoutIurIncomingHardHoSuccess

#128 VS.InterPlmnOutgoingHardHoAttempt

#129 VS.InterPlmnOutgoingHardHoFailure

#131 VS.InterRncWithoutIurOutgoingHardHoAttempt

#132 VS.InterRncWithoutIurOutgoingHardHoFailure

#133 VS.InterRncWithoutIurOutgoingHardHoSuccess

#135 VS.3g2gOutHoFailure

#142 VS.WithIurOutgoSrnsRelocAttempt

#143 VS.WithIurOutgoSrnsRelocFail

#144 VS.WithIurOutgoSrnsRelocSuccess

#145 VS.WithIurOutgoSrnsRelocSucPrTc

#146 VS.WithIurOutgoSrnsRelocFailPrTc

#147 VS.WithIurIncomSrnsRelocAttempt

#148 VS.WithIurIncomSrnsRelocFail

#149 VS.WithIurIncomSrnsRelocSuccess

#150 VS.WithIurIncomSrnsRelocSucPrTc

#151 VS.WithIurIncomSrnsRelocFailPrTc

#154 VS.RrcHoFromUtranCmdTrigByEcNo

#155 VS.RrcHoFromUtranCmdTrigByEcNoNRnc

#156 VS.RrcHoFromUtranCmdTrigByRscp

#157 VS.RrcHoFromUtranCmdTrigByRscpNRnc

#158 VS.RrcHoFromUtranCmdTrigRnc

#159 VS.RrcHoFromUtranCmdTrigRncNrnc

#160 VS.RrcHoFromUtranFailure

#161 VS.RrcHoFromUtranFailureNeighbRnc

#162 IRATHO.AttOutPSUTRAN




Counter name

#163 IRATHO.FailOutPSUTRAN

#164 VS.3gto2gHoDetectionFromFddcell

#165 VS.3gto2gHoDetectionFromFddcellNeighbRnc

#166 VS.InterPlmnOutgoingHardHoSuccess

#167 VS.3gto2gOutHoSuccess

#168 VS.3gto2gOutHoSuccessNrnc

#169 VS.3g2gOutHoFailureNrnc

#170 VS.IntraRncOutInterFreqHoAttempt

#171 VS.IntraRncOutInterFreqHoFail

#172 VS.IntraRncIncInterFreqHoAttempt

#173 VS.IntraRncIncInterFreqHoFail

#174 VS.OutGoInterFreqHoAtt

#175 VS.OutGoInterFreqHoSuc

#176 VS.IncomInterFreqHoAtt

#177 VS.IncomInterFreqHoSuc

Table 24 VS.RrcCellChangeOrderNeighbRnc - #106

A-Description

the number of RRC CELL CHANGE ORDER FROM UTRAN messages sent by an RNC (3G to2G handover for PS only), for each neighboring RNC. Neighboring RNCs act as Drift RNCscontrolling the reference cell of procedure involved UEs, i.e. an involved UE in the procedure isserved by a RNC which is not the controlling RNC of its reference cell.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a RRC CELL CHANGE ORDER FROM UTRAN message by the RNC to the UE.The event is only considered when the UE has a reference cell outside the control of the RNCin charge of the measurement..

D-Result

A set of subcounters screened on: HO reason for which the rrcCELL_CHANGE_ORDER_FROM_UTRAN message is sent

• Sub-Counter #0 : rescue PS

• Sub-Counter #1 : No resource available (CAC failure)

E-Type



• VS.RrcCellChangeOrderNeighbRnc.VS.RrcCellChangeOrderNeighbRnc.RescuePs

• VS.RrcCellChangeOrderNeighbRnc.VS.RrcCellChangeOrderNeighbRnc.NoRsrcCacFailure

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 25 VS.RrcCellChangeOrderFailureNeighbRnc - #108

A-Description

the number of "RRC CELL CHANGE ORDER FROM UTRAN FAILURE" messages receivedby a RNC (3G to 2G handover for PS only), for each neighboring RNC. Neighboring RNCs actas Drift RNCs controlling the reference cell of procedure involved UEs, i.e. an involved UE inthe procedure is served by a RNC which is not the controlling RNC of its reference cell.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RRC CELL CHANGE ORDER FROM UTRAN FAILURE message sent by UEto the Serving RNC in response to a RRC CELL CHANGE ORDER FROM UTRAN message.The event is only considered when the UE has a reference cell under the control of the RNC incharge of the measurement.

D-Result






E-Type

• VS.RrcCellChangeOrderFailureNeighbRnc.VS.RrcCellChangeOrderFailureNeighbRnc.RescuePs

• VS.RrcCellChangeOrderFailureNeighbRnc.VS.RrcCellChangeOrderFailureNeighbRnc.NoRsrcCacFailure

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 26 VS.WithoutIurIncomingHardHoAttempt - #122

A-Description

the number of attempted incoming Hard Handovers from a source cell in a different RNC,without Iur between the two RNCs (inter and intra PLMN)

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RANAP RELOCATION REQUEST with relocation source = UMTS

D-Result

A set of subcounters screened on: HO without Iur attempt reason



• Sub-Counter #0 : Time critical relocation

• Sub-Counter #1 : Relocation desireable for radio reasons

• Sub-Counter #2 : Directed retry

• Sub-Counter #3 : Unexpected Cause

E-Type

• VS.WithoutIurIncomingHardHoAttempt.VS.WithoutIurIncomingHardHoAttempt.TimeCriticalRelocation

• VS.WithoutIurIncomingHardHoAttempt.VS.WithoutIurIncomingHardHoAttempt.RelocationDesireableForRadioReasons

• VS.WithoutIurIncomingHardHoAttempt.VS.WithoutIurIncomingHardHoAttempt.DirectedRetry

• VS.WithoutIurIncomingHardHoAttempt.VS.WithoutIurIncomingHardHoAttempt.UnexpectedCause

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 27 VS.WithoutIurIncomingHardHoFailure - #123

A-Description

the number of failed incoming Hard Handovers from a source cell in a different RNC, withoutIur between the two RNCs (inter and intra PLMN).

B-Collection

CUM



CUMulative

C-Condition (Event)

Delivery of a RANAP RELOCATION FAILURE or reception of a RANAP IU RELEASE COM-MAND

D-Result

A set of subcounters screened on: HO without Iur failure reason

• Sub-Counter #0 : Failure in relocation procedures

• Sub-Counter #1 : Failure in security procedures

• Sub-Counter #2 : Failure in RNC procedures


E-Type

• VS.WithoutIurIncomingHardHoFailure.VS.WithoutIurIncomingHardHoFailure.FailureInRelocationProcedures

• VS.WithoutIurIncomingHardHoFailure.VS.WithoutIurIncomingHardHoFailure.FailureInSecurityProcedures

• VS.WithoutIurIncomingHardHoFailure.VS.WithoutIurIncomingHardHoFailure.FailureInRncProcedures

• VS.WithoutIurIncomingHardHoFailure.VS.WithoutIurIncomingHardHoFailure.UnexpectedCause

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal



Table 28 VS.WithoutIurIncomingHardHoSuccess - #124

A-Description

the number of successful incoming Hard Handovers from a source cell in a different RNC,without Iur between the two RNCs.

B-Collection

CUM

CUMulative

C-Condition (Event)

Delivery of a RANAP RELOCATION COMPLETE to Core Network

D-Result

A set of subcounters screened on: HO without Iur attempt reason


• Sub-Counter #1 : Relocation desireable for radio reasons

• Sub-Counter #2 : Directed retry


E-Type

• VS.WithoutIurIncomingHardHoSuccess.VS.WithoutIurIncomingHardHoSuccess.TimeCriticalRelocation

• VS.WithoutIurIncomingHardHoSuccess.VS.WithoutIurIncomingHardHoSuccess.RelocationDesireableForRadioReasons

• VS.WithoutIurIncomingHardHoSuccess.VS.WithoutIurIncomingHardHoSuccess.DirectedRetry

• VS.WithoutIurIncomingHardHoSuccess.VS.WithoutIurIncomingHardHoSuccess.UnexpectedCause

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V3.1

L-Aggregation Rule

Rtotal

Table 29 VS.InterPlmnOutgoingHardHoAttempt - #128

A-Description

the number of attempted outgoing Hard Handovers to a target cell in a different PLMN.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a RANAP RELOCATION REQUIRED by the RNC to the Core Network for a 3G to3G relocation with target cell PLMN different from source cell PLMN.

D-Result

A set of subcounters screened on: HO attempt reason

• Sub-Counter #0 : Inter Frequency Time critical relocation

• Sub-Counter #1 : Intra Frequency Time critical relocation

• Sub-Counter #2 : Service relocation

• Sub-Counter #3 : No resource available (CAC failure) relocation

E-Type

• VS.InterPlmnOutgoingHardHoAttempt.VS.InterPlmnOutgoingHardHoAttempt.InterFreqTimeCriticalRelocation

• VS.InterPlmnOutgoingHardHoAttempt.VS.InterPlmnOutgoingHardHoAttempt.IntraFreqTimeCriticalRelocation

• VS.InterPlmnOutgoingHardHoAttempt.VS.InterPlmnOutgoingHardHoAttempt.ServiceReloc

• VS.InterPlmnOutgoingHardHoAttempt.VS.InterPlmnOutgoingHardHoAttempt.NoRscrAvailReloc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V3.2

L-Aggregation Rule

Rtotal

Table 30 VS.InterPlmnOutgoingHardHoFailure - #129

A-Description

the number of failed outgoing Hard Handovers to a target cell in a different PLMN.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RANAP RELOCATION PREPARATION FAILURE or RANAP RELOCATIONCANCEL or IU RELEASE COMMAND (cause relocation cancel) or RRC HO FAILURE or time-out (in case of 3G to 3G relocation with target cell PLMN different from source cell PLMN).

D-Result

A set of subcounters screened on: HO Inter PLMN failure reason

• Sub-Counter #0 : Inter Frequency Failure in relocation procedures 0


• Sub-Counter #2 : Inter Frequency Failure in RNC procedures

• Sub-Counter #3 : Inter Frequency Failure in radio procedures

• Sub-Counter #4 : Inter Frequency Unexpected case

• Sub-Counter #5 : Intra Frequency Failure in relocation procedures 0


• Sub-Counter #7 : Intra Frequency Failure in RNC procedures

• Sub-Counter #8 : Intra Frequency Failure in radio procedures

• Sub-Counter #9 : Intra Frequency Unexpected case

E-Type

• VS.InterPlmnOutgoingHardHoFailure.VS.InterPlmnOutgoingHardHoFailure.InterFreqFailureInRelocationProcedures0

• VS.InterPlmnOutgoingHardHoFailure.VS.InterPlmnOutgoingHardHoFailure.InterFreqFailur



eInRelocationProcedures1

• VS.InterPlmnOutgoingHardHoFailure.VS.InterPlmnOutgoingHardHoFailure.InterFreqFailureInRncProcedures

• VS.InterPlmnOutgoingHardHoFailure.VS.InterPlmnOutgoingHardHoFailure.InterFreqFailureInRadioProcedures

• VS.InterPlmnOutgoingHardHoFailure.VS.InterPlmnOutgoingHardHoFailure.InterFreqUnexpectedCase

• VS.InterPlmnOutgoingHardHoFailure.VS.InterPlmnOutgoingHardHoFailure.IntraFreqFailureInRelocationProcedures0

• VS.InterPlmnOutgoingHardHoFailure.VS.InterPlmnOutgoingHardHoFailure.IntraFreqFailureInRelocationProcedures1

• VS.InterPlmnOutgoingHardHoFailure.VS.InterPlmnOutgoingHardHoFailure.IntraFreqFailureInRncProcedures

• VS.InterPlmnOutgoingHardHoFailure.VS.InterPlmnOutgoingHardHoFailure.IntraFreqFailureInRadioProcedures

• VS.InterPlmnOutgoingHardHoFailure.VS.InterPlmnOutgoingHardHoFailure.IntraFreqUnexpectedCase

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.2

L-Aggregation Rule

Rtotal

Table 31 VS.InterRncWithoutIurOutgoingHardHoAttempt - #131

A-Description

the number of attempted outgoing Hard Handovers to a target cell in a different RNC, withoutIur between the two RNCs (intra PLMN).



B-Collection

CUM

CUMulative

C-Condition (Event)

Delivery of a RANAP RELOCATION REQUIRED (first one in case of multi-domain) to the CoreNetwork with target cell PLMN equal to reference cell PLMN.

D-Result






E-Type

• VS.InterRncWithoutIurOutgoingHardHoAttempt.VS.InterRncWithoutIurOutgoingHardHoAttempt.InterFreqTimeCriticalRelocation

• VS.InterRncWithoutIurOutgoingHardHoAttempt.VS.InterRncWithoutIurOutgoingHardHoAttempt.IntraFreqTimeCriticalRelocation

• VS.InterRncWithoutIurOutgoingHardHoAttempt.VS.InterRncWithoutIurOutgoingHardHoAttempt.ServiceReloc

• VS.InterRncWithoutIurOutgoingHardHoAttempt.VS.InterRncWithoutIurOutgoingHardHoAttempt.NoRscrAvailReloc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule



Rtotal

Table 32 VS.InterRncWithoutIurOutgoingHardHoFailure - #132

A-Description

the number of failed outgoing Hard Handovers to a target cell in a different RNC, without Iurbetween the two RNCs (intra PLMN).

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of RANAP RELOCATION PREPARATION FAILURE or RRC HO FAILURE orRANAP IU RELEASE COMMAND (cause : Normal Release, Relocation Cancelled) or RANAPRAB RELEASE REQUEST (cause : UTRAN generated reason) or delivery of RANAP RELO-CATION CANCEL.

D-Result

A set of subcounters screened on: HO Inter PLMN failure reason



• Sub-Counter #2 : Inter Frequency Failure in RNC procedures

• Sub-Counter #3 : Inter Frequency Failure in radio procedures

• Sub-Counter #4 : Inter Frequency Unexpected case



• Sub-Counter #7 : Intra Frequency Failure in RNC procedures

• Sub-Counter #8 : Intra Frequency Failure in radio procedures

• Sub-Counter #9 : Intra Frequency Unexpected case

E-Type

• VS.InterRncWithoutIurOutgoingHardHoFailure.VS.InterRncWithoutIurOutgoingHardHoFailure.InterFreqFailureInRelocationProcedures0

• VS.InterRncWithoutIurOutgoingHardHoFailure.VS.InterRncWithoutIurOutgoingHardHoFailure.InterFreqFailureInRelocationProcedures1

• VS.InterRncWithoutIurOutgoingHardHoFailure.VS.InterRncWithoutIurOutgoingHardHoFailure.InterFreqFailureInRncProcedures

• VS.InterRncWithoutIurOutgoingHardHoFailure.VS.InterRncWithoutIurOutgoingHardHoFailure.InterFreqFailureInRadioProcedures

• VS.InterRncWithoutIurOutgoingHardHoFailure.VS.InterRncWithoutIurOutgoingHardHoFail



ure.InterFreqUnexpectedCase

• VS.InterRncWithoutIurOutgoingHardHoFailure.VS.InterRncWithoutIurOutgoingHardHoFailure.IntraFreqFailureInRelocationProcedures0

• VS.InterRncWithoutIurOutgoingHardHoFailure.VS.InterRncWithoutIurOutgoingHardHoFailure.IntraFreqFailureInRelocationProcedures1

• VS.InterRncWithoutIurOutgoingHardHoFailure.VS.InterRncWithoutIurOutgoingHardHoFailure.IntraFreqFailureInRncProcedures

• VS.InterRncWithoutIurOutgoingHardHoFailure.VS.InterRncWithoutIurOutgoingHardHoFailure.IntraFreqFailureInRadioProcedures

• VS.InterRncWithoutIurOutgoingHardHoFailure.VS.InterRncWithoutIurOutgoingHardHoFailure.IntraFreqUnexpectedCase

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 33 VS.InterRncWithoutIurOutgoingHardHoSuccess - #133

A-Description

the number of successful outgoing Hard Handovers to a target cell in a different RNC, withoutIur between the two RNCs.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of RANAP IU RELEASE COMMAND (cause : Successful Relocation).



D-Result






E-Type

• VS.InterRncWithoutIurOutgoingHardHoSuccess.VS.InterRncWithoutIurOutgoingHardHoSuccess.InterFreqTimeCriticalRelocation

• VS.InterRncWithoutIurOutgoingHardHoSuccess.VS.InterRncWithoutIurOutgoingHardHoSuccess.IntraFreqTimeCriticalRelocation

• VS.InterRncWithoutIurOutgoingHardHoSuccess.VS.InterRncWithoutIurOutgoingHardHoSuccess.ServiceReloc

• VS.InterRncWithoutIurOutgoingHardHoSuccess.VS.InterRncWithoutIurOutgoingHardHoSuccess.NoRscrAvailReloc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 34 VS.3g2gOutHoFailure - #135

A-Description

Number of failed outgoing Handovers from 3G to 2G.

B-Collection



CUM

CUMulative

C-Condition (Event)

UE_CALL receives from IU_CALL a IudRelocPrepFailure (issued either from RANAP Reloca-tion Preparation Failure or as a consequence of a RANAP Relocation Cancel (with TRELOC-prep expiry)) or UE_CALL receives from IU_CALL a IudReleaseCmd (issued from RANAP IuRelease Command) with cause: Relocation Cancelled(10), Normal Release(83), Release dueto UTRAN Generated Reason(15), or UE_CALL receives a RRC HO From UTRAN Failure, orIncremented based on reference cell (either FDDCELL or Neighboring RNC).

D-Result

A set of subcounters screened on: Reason for initiating the 3G to 2G HO

• Sub-Counter #0 : Relocation Preparation Failure/Cancellation

• Sub-Counter #1 : Relocation Completion Failure

• Sub-Counter #2 : CS Failure in the radio procedures

• Sub-Counter #3 : PS Failure in the radio procedures

• Sub-Counter #4 : Unexpected cause

E-Type

• VS.3g2gOutHoFailure.VS.3g2gOutHoFailure.RelocPrepOrCancel

• VS.3g2gOutHoFailure.VS.3g2gOutHoFailure.RelocComplFail

• VS.3g2gOutHoFailure.VS.3g2gOutHoFailure.CsFailureRadioProc

• VS.3g2gOutHoFailure.VS.3g2gOutHoFailure.PsFailureRadioproc

• VS.3g2gOutHoFailure.VS.3g2gOutHoFailure.Unexpected

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V4.2

L-Aggregation Rule

Rtotal

Table 35 VS.WithIurOutgoSrnsRelocAttempt - #142

A-Description

Number of attempted outgoing SRNS Relocation with IuR.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Relocation Required with relocationSource = UMTS and relocation type = 'UE not in-volved' sent on the Iu interface (first message sent in the multi-domain case).

D-Result

A set of subcounters screened on: Reason for initiating the Iur SRNS Relocation (Ref. 25.413).

• Sub-Counter #0 : Resource optimization relocation.

• Sub-Counter #1 : Other cause

E-Type

• VS.WithIurOutgoSrnsRelocAttempt.VS.WithIurOutgoSrnsRelocAttempt.RsrcOptReloc

• VS.WithIurOutgoSrnsRelocAttempt.VS.WithIurOutgoSrnsRelocAttempt.OtherCause

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule



Rtotal

Table 36 VS.WithIurOutgoSrnsRelocFail - #143

A-Description

Number of failed outgoing SRNS Relocation with IuR.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Relocation Preparation Failure or RANAP Iu Release Command (with cause relocationcancelled, normal release or release due to UTRAN generated reason) received on the Iu In-terface, or RANAP Relocation Cancel (with TRelocPrep expiry) sent on the Iu interface (firstmessage sent or received in the multi-domain case).

D-Result

A set of subcounters screened on: Failure cause for Iur Outgoing SRNS Relocation (internalRNC cause, not from 25.413).

• Sub-Counter #0 : Failure in the relocation procedures (relocation failure in Target CN/RNC,Relocation not supported in Target RNC, Trelocalloc expiry, Trelocprep expiry).

• Sub-Counter #1 : Failure in the relocation procedures (relocation cancelled, normal re-lease, release due to UTRAN generated reason)

• Sub-Counter #2 : Failure in RNC procedures (Unknown Target RNC)

• Sub-Counter #3 : Failure in radio procedures


E-Type

• VS.WithIurOutgoSrnsRelocFail.VS.WithIurOutgoSrnsRelocFail.FailRelocProcTarget

• VS.WithIurOutgoSrnsRelocFail.VS.WithIurOutgoSrnsRelocFail.FailRelocProcCanNormUtran

• VS.WithIurOutgoSrnsRelocFail.VS.WithIurOutgoSrnsRelocFail.FailRncProc

• VS.WithIurOutgoSrnsRelocFail.VS.WithIurOutgoSrnsRelocFail.FailRadioProc

• VS.WithIurOutgoSrnsRelocFail.VS.WithIurOutgoSrnsRelocFail.FailOtherCause

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 37 VS.WithIurOutgoSrnsRelocSuccess - #144

A-Description

Number of successful outgoing SRNS Relocation with IuR.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Iu Release Command (with cause Successful Relocation) received on the Iu interfacefor all domains.

D-Result




E-Type

• VS.WithIurOutgoSrnsRelocSuccess.VS.WithIurOutgoSrnsRelocSuccess.RsrcOptReloc

• VS.WithIurOutgoSrnsRelocSuccess.VS.WithIurOutgoSrnsRelocSuccess.OtherCause

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 38 VS.WithIurOutgoSrnsRelocSucPrTc - #145

A-Description

Number of successful outgoing SRNS Relocation with IuR per traffic class.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Iu Release Command (with cause Successful Relocation) received on the Iu interfacefor each domain.

D-Result

A set of subcounters screened on: CN Domain.

• Sub-Counter #0 : CS Conversational.

• Sub-Counter #1 : CS Streaming

• Sub-Counter #2 : PS Interactive

• Sub-Counter #3 : PS Background

• Sub-Counter #4 : PS Streaming

E-Type

• VS.WithIurOutgoSrnsRelocSucPrTc.VS.WithIurOutgoSrnsRelocSucPrTc.CsCnvrs

• VS.WithIurOutgoSrnsRelocSucPrTc.VS.WithIurOutgoSrnsRelocSucPrTc.CsStrm

• VS.WithIurOutgoSrnsRelocSucPrTc.VS.WithIurOutgoSrnsRelocSucPrTc.PsIntr

• VS.WithIurOutgoSrnsRelocSucPrTc.VS.WithIurOutgoSrnsRelocSucPrTc.PsBkgnd

• VS.WithIurOutgoSrnsRelocSucPrTc.VS.WithIurOutgoSrnsRelocSucPrTc.PsStrm

F-Object Instance

Neighbouring RNC

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 39 VS.WithIurOutgoSrnsRelocFailPrTc - #146

A-Description

Number of successful outgoing SRNS Relocation with IuR per traffic class

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Relocation Preparation Failure or RANAP Iu Release Command (with cause relocationcancelled, normal release or release due to UTRAN generated reason) received on the Iu In-terface, or RANAP Relocation Cancel (with TRelocPrep expiry) sent on the Iu interface.

D-Result







E-Type

• VS.WithIurOutgoSrnsRelocFailPrTc.VS.WithIurOutgoSrnsRelocFailPrTc.CsCnvrs

• VS.WithIurOutgoSrnsRelocFailPrTc.VS.WithIurOutgoSrnsRelocFailPrTc.CsStrm

• VS.WithIurOutgoSrnsRelocFailPrTc.VS.WithIurOutgoSrnsRelocFailPrTc.PsIntr



• VS.WithIurOutgoSrnsRelocFailPrTc.VS.WithIurOutgoSrnsRelocFailPrTc.PsBkgnd

• VS.WithIurOutgoSrnsRelocFailPrTc.VS.WithIurOutgoSrnsRelocFailPrTc.PsStrm

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 40 VS.WithIurIncomSrnsRelocAttempt - #147

A-Description

Number of attempted incoming SRNS Relocation with IuR.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Relocation Required with relocationSource = UMTS and relocation type = UE not in-volved received on Iu interface.

D-Result





E-Type

• VS.WithIurIncomSrnsRelocAttempt.VS.WithIurIncomSrnsRelocAttempt.RsrcOptReloc



• VS.WithIurIncomSrnsRelocAttempt.VS.WithIurIncomSrnsRelocAttempt.TimeCritReloc

• VS.WithIurIncomSrnsRelocAttempt.VS.WithIurIncomSrnsRelocAttempt.OtherCause

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 41 VS.WithIurIncomSrnsRelocFail - #148

A-Description

Number of failed incoming SRNS Relocation with IuR.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Iu Release Command received on the Iu interface or RANAP Relocation Failure senton the Iu interface when relocation type = 'UE not involved' (first message sent in the multi-domain case).

D-Result

A set of subcounters screened on: Failure cause for Iur Incoming SRNS Relocation (internalRNC cause, not from 25.413).

• Sub-Counter #0 : Failure in the relocation procedures (if Relocation cancelled, Treloccom-plete or Trelocoverall expiry, coordination issues, erroneous parameters in messages andcontainers).

• Sub-Counter #1 : Failure in the security procedures (feature locking, erroneous paramet-



ers, in messages and containers)

• Sub-Counter #2 : Failure in RNC procedures (Trelocalloc expiry, Release due to UTRANgenerated reason, feature locking, unavailable or unsupported RAB)


E-Type

• VS.WithIurIncomSrnsRelocFail.VS.WithIurIncomSrnsRelocFail.FailRelocProc

• VS.WithIurIncomSrnsRelocFail.VS.WithIurIncomSrnsRelocFail.FailSecurProc

• VS.WithIurIncomSrnsRelocFail.VS.WithIurIncomSrnsRelocFail.FailRncProc

• VS.WithIurIncomSrnsRelocFail.VS.WithIurIncomSrnsRelocFail.OtherCause

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 42 VS.WithIurIncomSrnsRelocSuccess - #149

A-Description

Number of successful incoming SRNS Relocation with IuR.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Relocation Complete when relocation type = UE not involved sent on Iu interface (firstmessage sent in the multi-domain case).



D-Result





E-Type

• VS.WithIurIncomSrnsRelocSuccess.VS.WithIurIncomSrnsRelocSuccess.RsrcOptReloc

• VS.WithIurIncomSrnsRelocSuccess.VS.WithIurIncomSrnsRelocSuccess.TimeCritReloc

• VS.WithIurIncomSrnsRelocSuccess.VS.WithIurIncomSrnsRelocSuccess.OtherCause

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 43 VS.WithIurIncomSrnsRelocSucPrTc - #150

A-Description

Number of successful incoming SRNS Relocation with IuR per traffic class.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Relocation Complete when relocation type = UE not involved sent on Iu interface foreach domain



D-Result







E-Type

• VS.WithIurIncomSrnsRelocSucPrTc.VS.WithIurIncomSrnsRelocSucPrTc.CsCnvrs

• VS.WithIurIncomSrnsRelocSucPrTc.VS.WithIurIncomSrnsRelocSucPrTc.CsStrm

• VS.WithIurIncomSrnsRelocSucPrTc.VS.WithIurIncomSrnsRelocSucPrTc.PsIntr

• VS.WithIurIncomSrnsRelocSucPrTc.VS.WithIurIncomSrnsRelocSucPrTc.PsBkgnd

• VS.WithIurIncomSrnsRelocSucPrTc.VS.WithIurIncomSrnsRelocSucPrTc.PsStrm

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 44 VS.WithIurIncomSrnsRelocFailPrTc - #151

A-Description

Number of unsuccessful incoming SRNS Relocation with IuR per traffic class

B-Collection

CUM



CUMulative

C-Condition (Event)

RANAP Iu Release Command received on the Iu interface or RANAP Relocation Failure senton the Iu interface when relocation type = 'UE not involved' (first message sent in the multi-domain case).

D-Result







E-Type

• VS.WithIurIncomSrnsRelocFailPrTc.VS.WithIurIncomSrnsRelocFailPrTc.CsCnvrs

• VS.WithIurIncomSrnsRelocFailPrTc.VS.WithIurIncomSrnsRelocFailPrTc.CsStrm

• VS.WithIurIncomSrnsRelocFailPrTc.VS.WithIurIncomSrnsRelocFailPrTc.PsIntr

• VS.WithIurIncomSrnsRelocFailPrTc.VS.WithIurIncomSrnsRelocFailPrTc.PsBkgnd

• VS.WithIurIncomSrnsRelocFailPrTc.VS.WithIurIncomSrnsRelocFailPrTc.PsStrm

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 45 VS.RrcHoFromUtranCmdTrigByEcNo - #154

A-Description

Number of Inter Rat handover from utran command sent by RNC with a reference cell forwhich the RNC is serving and the handover has been initiated because of Ec/No. This is in thescope of 3G to 2G handover, CS only.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RRC/HANDOVER_FROM_UTRAN_COMMAND message when reference cell ison serving RNC and the handover has been initiated because of Ec/No. Incremented based onreference cell.

D-Result

A set of subcounters screened on: HO reason - EC/No - triggering sending of RRC/HANDOVER_FROM_UTRAN_COMMAND

• Sub-Counter #0 : rescue CS

E-Type

• VS.RrcHoFromUtranCmdTrigByEcNo.VS.RrcHoFromUtranCmdTrigByEcNo.RescueCs

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 46 VS.RrcHoFromUtranCmdTrigByEcNoNRnc - #155

A-Description

Number of Inter-RAT handover from Utran command sent by RNC with a reference cell forwhich the RNC is drift, and the handover has been initiated because of Ec/No. This is in thescope of 3G to 2G handover, CS only.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RRC/HANDOVER_FROM_UTRAN_COMMAND message when reference cell ison drift RNC and the handover has been initiated because of Ec/No. Incremented based onreference cell on the .

D-Result

A set of subcounters screened on: HO reason - EC/No on Drift RNC - triggering sending ofRRC/HANDOVER_FROM_UTRAN_COMMAND


E-Type

• VS.RrcHoFromUtranCmdTrigByEcNoNRnc.VS.RrcHoFromUtranCmdTrigByEcNoNRnc.RescueCs

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 47 VS.RrcHoFromUtranCmdTrigByRscp - #156

A-Description

Number of Inter-RAT handover from Utran command sent by RNC with a reference cell forwhich the RNC is serving, and the handover has been initiated because of RSCP criteria. Thisis in the scope of 3G to 2G handover, CS only.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RRC/HANDOVER_FROM_UTRAN_COMMAND message when reference cell ison serving RNC and the handover has been initiated because of RSCP criteria. Incrementedbased on reference cell.

D-Result

A set of subcounters screened on: HO reason - RSCP - triggering sending of RRC/HANDOVER_FROM_UTRAN_COMMAND


E-Type

• VS.RrcHoFromUtranCmdTrigByRscp.VS.RrcHoFromUtranCmdTrigByRscp.RescueCs

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 48 VS.RrcHoFromUtranCmdTrigByRscpNRnc - #157

A-Description

Number of Inter-RAT handover from Utran command sent by RNC with a reference cell forwhich the RNC is drift, and the handover has been initiated because of RSCP criteria. This is inthe scope of 3G to 2G handover, CS only.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RRC/HANDOVER_FROM_UTRAN_COMMAND message when reference cell ison drift RNC and the handover has been initiated because of RSCP criteria. Incrementedbased on reference cell.

D-Result

A set of subcounters screened on: HO reason - RSCP on Drift RNC - triggering sending ofRRC/HANDOVER_FROM_UTRAN_COMMAND


E-Type

• VS.RrcHoFromUtranCmdTrigByRscpNRnc.VS.RrcHoFromUtranCmdTrigByRscpNRnc.RescueCs

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 49 VS.RrcHoFromUtranCmdTrigRnc - #158

A-Description

Number of Inter-RAT handover from Utran command sent by RNC with a reference cell forwhich the RNC is serving, and the handover has been initiated because of CAC failure eventsor Service events, NOT because of Alarm radio condition. This is in the scope of 3G to 2G han-dover, CS only.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RRC/HANDOVER_FROM_UTRAN_COMMAND message when reference cell ison serving RNC and the handover has been initiated because of CAC failure events or Serviceevents. Incremented based on reference cell.

D-Result

A set of subcounters screened on: HO reason - not Alarm Radio - triggering sending of RRC/HANDOVER_FROM_UTRAN_COMMAND

• Sub-Counter #0 : service CS


E-Type

• VS.RrcHoFromUtranCmdTrigRnc.VS.RrcHoFromUtranCmdTrigRnc.ServiceCs

• VS.RrcHoFromUtranCmdTrigRnc.VS.RrcHoFromUtranCmdTrigRnc.NoRsrcAvailCacFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0



L-Aggregation Rule

Rtotal

Table 50 VS.RrcHoFromUtranCmdTrigRncNrnc - #159

A-Description

Number of Inter-RAT handover from Utran command sent by RNC with a reference cell forwhich the RNC is drift, and the handover has been initiated because of CAC failure events,NOT because of Alarm radio condition. This is in the scope of 3G to 2G handover, CS only.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RRC/HANDOVER_FROM_UTRAN_COMMAND message when reference cell ison drift RNC,and the handover has been initiated because of CAC failure events. Incrementedbased on reference cell.

D-Result

A set of subcounters screened on: HO reason - Not Alarm Radio on Drift RNC - triggeringsending of RRC/HANDOVER_FROM_UTRAN_COMMAND


E-Type

• VS.RrcHoFromUtranCmdTrigRncNrnc.VS.RrcHoFromUtranCmdTrigRncNrnc.NoRsrcAvailCacFailure

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0



L-Aggregation Rule

Rtotal

Table 51 VS.RrcHoFromUtranFailure - #160

A-Description

the number of RRC HANDOVER FROM UTRAN FAILURE messages (3G to 2G handover forCS or CS+PS) received by an RNC, acting as serving RNC, for each cell controlled by thisRNC. The reference cell of the involved UE has to be under the control of this RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RRC HANDOVER FROM UTRAN FAILURE message by a RRC from a UEhaving its reference controlled by the considered RNC

D-Result

A set of subcounters screened on: HO reason for which the RRC / HAN-DOVER_FROM_UTRAN_COMMAND message is sent




E-Type

• VS.RrcHoFromUtranFailure.VS.RrcHoFromUtranFailure.RescueCs

• VS.RrcHoFromUtranFailure.VS.RrcHoFromUtranFailure.ServiceCs

• VS.RrcHoFromUtranFailure.VS.RrcHoFromUtranFailure.NoRsrcAvailCacFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event



K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 52 VS.RrcHoFromUtranFailureNeighbRnc - #161

A-Description

the number of RRC HANDOVER FROM UTRAN FAILURE (3G to 2G handover for CS orCS+PS) messages received by an RNC acting as serving, for each neighboring RNC. Neigh-boring RNCs act as Drift RNCs controlling the reference cell of the involved UEs, i.e. an in-volved UE in the procedure is served by a RNC which is not the controlling RNC of its refer-ence cell.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RRC HANDOVER FROM UTRAN FAILURE message by a RRC from a UEhaving its reference cell controlled by another RNC

D-Result

A set of subcounters screened on: HO reason for which the RRC / HAN-DOVER_FROM_UTRAN_COMMAND message is sent



E-Type

• VS.RrcHoFromUtranFailureNeighbRnc.VS.RrcHoFromUtranFailureNeighbRnc.RescueCs

• VS.RrcHoFromUtranFailureNeighbRnc.VS.RrcHoFromUtranFailureNeighbRnc.NoRsrcAvailCacFailure

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 53 IRATHO.AttOutPSUTRAN - #162

A-Description

the number of RRC CELL CHANGE ORDER FROM UTRAN messages (3G to 2G handoverfor PS only) emitted by an RNC, acting as serving RNC, for each cell controlled by this RNC.The reference cell of the involved UE has to be under the control of this RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a RRC CELL CHANGE ORDER FROM UTRAN message from the RNC to the UE.The event is only considered when the UE has a reference cell under the control of the RNC incharge of the measurement.

D-Result


• Sub-Counter #0 : Rescue PS

• Sub-Counter #1 : Service PS


E-Type

• IRATHO.AttOutPSUTRAN.IRATHO.AttOutPSUTRAN.RescuePs

• IRATHO.AttOutPSUTRAN.IRATHO.AttOutPSUTRAN.ServicePs

• IRATHO.AttOutPSUTRAN.IRATHO.AttOutPSUTRAN.NoRsrcCacFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance



Y-3GPP specified counter (3GPP specification is applied for the cells which are controlled bythe SRNC)-#162

I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 54 IRATHO.FailOutPSUTRAN - #163

A-Description

the number of RRC CELL CHANGE ORDER FROM UTRAN FAILURE messages received bya RNC (3G to 2G handover for PS only), for each cell controlled by the RNC and acting as areference cell, i.e. an involved UE in the procedure is served by a RNC which is the controllingRNC of its reference cell.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RRC CELL CHANGE ORDER FROM UTRAN FAILURE message sent by anUE to the Serving RNC in response to a RRC CELL CHANGE ORDER FROM UTRAN mes-sage. The event is only considered when the UE has a reference cell under the control of theRNC in charge of the measurement.

D-Result





E-Type

• IRATHO.FailOutPSUTRAN.IRATHO.FailOutPSUTRAN.RescuePs

• IRATHO.FailOutPSUTRAN.IRATHO.FailOutPSUTRAN.ServicePs

• IRATHO.FailOutPSUTRAN.IRATHO.FailOutPSUTRAN.NoRsrcCacFailure



F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance

Y-3GPP specified counter (3GPP specification is applied for the cells which are controlled bythe SRNC)-#163

I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 55 VS.3gto2gHoDetectionFromFddcell - #164

A-Description

the number of RRM decisions for a 3G TO 2G handover performed by a RNC, screened by ref-erence cell from which the UEs have left the 3G Network, when these cells are controlled bythe considered RNC. This measurement considers both CS and PS handovers.

B-Collection

CUM

CUMulative

C-Condition (Event)

RRM decision for a UE handover from 3G to 2G network. The event is only considered whenthe UE has a reference cell under the control of the RNC in charge of the measurement.

D-Result


• Sub-Counter #0 : Rescue CS


• Sub-Counter #2 : Service


E-Type



• VS.3gto2gHoDetectionFromFddcell.VS.3gto2gHoDetectionFromFddcell.RescueCs

• VS.3gto2gHoDetectionFromFddcell.VS.3gto2gHoDetectionFromFddcell.RescuePs

• VS.3gto2gHoDetectionFromFddcell.VS.3gto2gHoDetectionFromFddcell.Service

• VS.3gto2gHoDetectionFromFddcell.VS.3gto2gHoDetectionFromFddcell.NoRsrcAvailCacFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 56 VS.3gto2gHoDetectionFromFddcellNeighbRnc - #165

A-Description

the number of RRM decisions for a 3G TO 2G handover performed by a RNC, screened byneighboring RNC grouping reference cells from which the UEs have left the 3G Network. Thismeasurement considers both CS and PS handovers.

B-Collection

CUM

CUMulative

C-Condition (Event)

RRM decision for a UE handover from 3G to 2G network. The event is only considered whenthe UE has a reference cell under the control of the RNC which is not the RNC in charge of themeasurement.

D-Result




• Sub-Counter #0 : Rescue CS



E-Type

• VS.3gto2gHoDetectionFromFddcellNeighbRnc.VS.3gto2gHoDetectionFromFddcellNeighbRnc.RescueCs

• VS.3gto2gHoDetectionFromFddcellNeighbRnc.VS.3gto2gHoDetectionFromFddcellNeighbRnc.RescuePs

• VS.3gto2gHoDetectionFromFddcellNeighbRnc.VS.3gto2gHoDetectionFromFddcellNeighbRnc.NoRsrcAvailCacFailure

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 57 VS.InterPlmnOutgoingHardHoSuccess - #166

A-Description

the number of successfull outgoing Hard Handovers to a target cell in a different PLMN.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of Iu Release Command with cause "Successfull relocation" for an inter-PLMN han-dover.



D-Result

A set of subcounters screened on: Relocation cause





E-Type

• VS.InterPlmnOutgoingHardHoSuccess.VS.InterPlmnOutgoingHardHoSuccess.InterFreqTimeCriticalRelocation

• VS.InterPlmnOutgoingHardHoSuccess.VS.InterPlmnOutgoingHardHoSuccess.IntraFreqTimeCriticalRelocation

• VS.InterPlmnOutgoingHardHoSuccess.VS.InterPlmnOutgoingHardHoSuccess.ServiceReloc

• VS.InterPlmnOutgoingHardHoSuccess.VS.InterPlmnOutgoingHardHoSuccess.NoRscrAvailReloc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 58 VS.3gto2gOutHoSuccess - #167

A-Description

the number of successfull 3G to 2G outgoing Handovers.

B-Collection



CUM

CUMulative

C-Condition (Event)

Reception of iud_Iu_Release_Command with cause Successful Relocation

D-Result

A set of subcounters screened on: HO reason for which a 3G to 2G Relocation was initiated.





• Sub-Counter #4 : No resource available CS (CAC failure)

• Sub-Counter #5 : No resource available PS (CAC failure)

E-Type

• VS.3gto2gOutHoSuccess.VS.3gto2gOutHoSuccess.RescueCs

• VS.3gto2gOutHoSuccess.VS.3gto2gOutHoSuccess.RescuePs

• VS.3gto2gOutHoSuccess.VS.3gto2gOutHoSuccess.ServiceCs

• VS.3gto2gOutHoSuccess.VS.3gto2gOutHoSuccess.ServicePs

• VS.3gto2gOutHoSuccess.VS.3gto2gOutHoSuccess.NoRsrcCs

• VS.3gto2gOutHoSuccess.VS.3gto2gOutHoSuccess.NoRsrcPs

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 59 VS.3gto2gOutHoSuccessNrnc - #168

A-Description

Number of successful outgoing Hard Handovers from 3G to 2G when reference cell is on driftRNC

B-Collection

CUM

CUMulative

C-Condition (Event)

When UE_CALL receives from IU_CALL iud_Iu_Release_Command with cause SuccessfulRelocation (issued from RANAP/IU_RELEASE_COMMAND) in the case of 3G to 2G reloca-tion. when reference cell is on drift RNC. Incremented based on reference cell (NeighbouringRNC).

D-Result

A set of subcounters screened on: HO reason for which a 3G to 2G Relocation was initiated.



• Sub-Counter #2 : No resource available CS (CAC failure)

• Sub-Counter #3 : No resource available PS (CAC failure)

E-Type

• VS.3gto2gOutHoSuccessNrnc.VS.3gto2gOutHoSuccessNrnc.3gTo2GOutGoHoNrncRsnRscCs

• VS.3gto2gOutHoSuccessNrnc.VS.3gto2gOutHoSuccessNrnc.3gTo2GOutGoHoNrncRsnRscPs

• VS.3gto2gOutHoSuccessNrnc.VS.3gto2gOutHoSuccessNrnc.3gTo2GOutGoHoNrncRsnNoRsrcCs

• VS.3gto2gOutHoSuccessNrnc.VS.3gto2gOutHoSuccessNrnc.3gTo2GOutGoHoNrncRsnNoRsrcPs

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 60 VS.3g2gOutHoFailureNrnc - #169

A-Description

Number of failed outgoing Handovers from 3G to 2G when reference cell is on drift RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

With reference cell on drift RNC, UE_CALL receives from IU_CALL a IudRelocPrepFailure(issued either from RANAP Relocation Preparation Failure, or as a consequence of a RANAPRelocation Cancel (with TRELOCprep expiry)), or UE_CALL receives from IU_CALL a IudRe-leaseCmd (issued from RANAP Iu Release Command) with cause: Relocation Cancelled(10),Normal Release(83), Release due to UTRAN Generated Reason(15), or UE_CALL receives aRRC HO From UTRAN Failure, or Incremented based on reference cell (either FDDCELL orNeighboring RNC).

D-Result


• Sub-Counter #0 : Relocation Preparation Failure/Cancellation

• Sub-Counter #1 : Relocation Completion Failure

• Sub-Counter #2 : CS Failure in the radio procedures

• Sub-Counter #3 : PS Failure in the radio procedures

• Sub-Counter #4 : Unexpected cause

E-Type

• VS.3g2gOutHoFailureNrnc.VS.3g2gOutHoFailureNrnc.RelocPrepOrCancel

• VS.3g2gOutHoFailureNrnc.VS.3g2gOutHoFailureNrnc.RelocComplFail

• VS.3g2gOutHoFailureNrnc.VS.3g2gOutHoFailureNrnc.CsFailureRadioProc

• VS.3g2gOutHoFailureNrnc.VS.3g2gOutHoFailureNrnc.PsFailureRadioproc



• VS.3g2gOutHoFailureNrnc.VS.3g2gOutHoFailureNrnc.Unexpected

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 61 VS.IntraRncOutInterFreqHoAttempt - #170

A-Description

the number of Intra RNC outgoing Hard Handovers attempted from this cell to another cell us-ing another frequency in the same RNC (using blind HO).

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a NBAP RADIO_LINK_SETUP_REQUEST message for a cell using another fre-quency in the same RNC or a RRC CONNECTION SETUP on a cell different from the cell ofthe RACH

D-Result

A set of subcounters screened on: Reason for initiating the Intra RNC HHO

• Sub-Counter #0 : HO without CM measurements

• Sub-Counter #1 : HO with CM measurements

• Sub-Counter #2 : HSDPA capable mobile to HSDPA layer

• Sub-Counter #3 : HSDPA capable mobile to non-HSDPA layer



• Sub-Counter #4 : Non-HSDPA capable mobile to non-HSDPA layer

E-Type

• VS.IntraRncOutInterFreqHoAttempt.VS.IntraRncOutInterFreqHoAttempt.HoWithOutCmMeas

• VS.IntraRncOutInterFreqHoAttempt.VS.IntraRncOutInterFreqHoAttempt.HoWithCmMeas

• VS.IntraRncOutInterFreqHoAttempt.VS.IntraRncOutInterFreqHoAttempt.HsdpaMobToHsdpaLayer

• VS.IntraRncOutInterFreqHoAttempt.VS.IntraRncOutInterFreqHoAttempt.HsdpaMobToNonHsdpaLayer

• VS.IntraRncOutInterFreqHoAttempt.VS.IntraRncOutInterFreqHoAttempt.NonHsdpaMobToNonHsdpaLayer

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 62 VS.IntraRncOutInterFreqHoFail - #171

A-Description

the number of Intra RNC outgoing Hard Handover failures from this cell to another cell usinganother frequency in the same RNC (using blind HO).

B-Collection

CUM

CUMulative

C-Condition (Event)



Reception of a NBAP RADIO_LINK_SETUP_FAILURE message or a RADIO BEARER RE-CONF FAILURE message related to the target cell.

D-Result

A set of subcounters screened on: Failure reason for Intra RNC HHO

• Sub-Counter #0 : HO with measurements Not enough resources

• Sub-Counter #1 : HO with measurements NodeB failure

• Sub-Counter #2 : HO with measurements Failure on RRC

• Sub-Counter #3 : HO with CM measurement Not enough resources

• Sub-Counter #4 : HO with CM measurement NodeB failure

• Sub-Counter #5 : HO with CM measurement Failure on RRC

E-Type

• VS.IntraRncOutInterFreqHoFail.VS.IntraRncOutInterFreqHoFail.HoWithMeasNoRsrc

• VS.IntraRncOutInterFreqHoFail.VS.IntraRncOutInterFreqHoFail.HoWithMeasNodeBFail

• VS.IntraRncOutInterFreqHoFail.VS.IntraRncOutInterFreqHoFail.HoWithMeasFailRRC

• VS.IntraRncOutInterFreqHoFail.VS.IntraRncOutInterFreqHoFail.HoWithCmMeasNoRsrc

• VS.IntraRncOutInterFreqHoFail.VS.IntraRncOutInterFreqHoFail.HoWithCmMeasNodeBFail

• VS.IntraRncOutInterFreqHoFail.VS.IntraRncOutInterFreqHoFail.HoWithCmMeasFailRRC

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 63 VS.IntraRncIncInterFreqHoAttempt - #172

A-Description

the number of attempted Intra RNC incoming Hard Handovers from another cell using anotherfrequency in the same RNC to this cell (only Blind HO).

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a NBAP RADIO_LINK_SETUP_REQUEST message for this cell for a call suppor-ted by another cell with a different frequency in the same RNC or emission of a RRC connec-tion setup on cell different from the cell of the RACH.

D-Result

A set of subcounters screened on: Reason for initiating the Intra RNC HHO

• Sub-Counter #0 : HO without CM measurements

• Sub-Counter #1 : HO with CM measurements

• Sub-Counter #2 : HSDPA capable mobile to HSDPA layer

• Sub-Counter #3 : HSDPA capable mobile to non-HSDPA layer

• Sub-Counter #4 : Non-HSDPA capable mobile to non-HSDPA layer

E-Type

• VS.IntraRncIncInterFreqHoAttempt.VS.IntraRncIncInterFreqHoAttempt.HoWithOutCmMeas

• VS.IntraRncIncInterFreqHoAttempt.VS.IntraRncIncInterFreqHoAttempt.HoWithCmMeas

• VS.IntraRncIncInterFreqHoAttempt.VS.IntraRncIncInterFreqHoAttempt.HsdpaMobToHsdpaLayer

• VS.IntraRncIncInterFreqHoAttempt.VS.IntraRncIncInterFreqHoAttempt.HsdpaMobToNonHsdpaLayer

• VS.IntraRncIncInterFreqHoAttempt.VS.IntraRncIncInterFreqHoAttempt.NonHsdpaMobToNonHsdpaLayer

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 64 VS.IntraRncIncInterFreqHoFail - #173

A-Description

the number of failed Intra RNC incoming Hard Handovers from another cell using another fre-quency in the same RNC to this cell (only Blind HO in V3).

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a NBAP RADIO_LINK_SETUP_FAILURE message or a RRC RADIO BEARERRECONFIGURATION FAILURE message for this celll.

D-Result

A set of subcounters screened on: Failure reason for Intra RNC HHO

• Sub-Counter #0 : HO with measurements Not enough resources

• Sub-Counter #1 : HO with measurements NodeB failure

• Sub-Counter #2 : HO with measurements Failure on RRC

• Sub-Counter #3 : HO with CM measurement Not enough resources

• Sub-Counter #4 : HO with CM measurement NodeB failure

• Sub-Counter #5 : HO with CM measurement Failure on RRC

E-Type

• VS.IntraRncIncInterFreqHoFail.VS.IntraRncIncInterFreqHoFail.HoWithMeasNoRsrc

• VS.IntraRncIncInterFreqHoFail.VS.IntraRncIncInterFreqHoFail.HoWithMeasNodeBFail

• VS.IntraRncIncInterFreqHoFail.VS.IntraRncIncInterFreqHoFail.HoWithMeasFailRRC

• VS.IntraRncIncInterFreqHoFail.VS.IntraRncIncInterFreqHoFail.HoWithCmMeasNoRsrc

• VS.IntraRncIncInterFreqHoFail.VS.IntraRncIncInterFreqHoFail.HoWithCmMeasNodeBFail

• VS.IntraRncIncInterFreqHoFail.VS.IntraRncIncInterFreqHoFail.HoWithCmMeasFailRRC

F-Object Instance



Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 65 VS.OutGoInterFreqHoAtt - #174

A-Description

Number of hard handovers attempted from this cell to another inter-frequency cell locatedeither in the same RNC or in a neighbouring RNC (a Iur link is setup towards the inter-fre-quency cell).

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RL Setup message for a cell of another frequency

D-Result

A set of subcounters screened on: Reason for initiating the inter-frequency HHO

• Sub-Counter #0 : Rescue



E-Type

• VS.OutGoInterFreqHoAtt.VS.OutGoInterFreqHoAtt.Rescue

• VS.OutGoInterFreqHoAtt.VS.OutGoInterFreqHoAtt.Service

• VS.OutGoInterFreqHoAtt.VS.OutGoInterFreqHoAtt.NoRsrcAvailCacFailure



F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 66 VS.OutGoInterFreqHoSuc - #175

A-Description

Number of successful hard handovers from this cell located on the serving RNC to anotherinter-frequency cell located either in the same RNC or in a neighbouring RNC (a Iur link issetup towards the inter-frequency cell).

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RL deletion message for the old cell

D-Result





E-Type

• VS.OutGoInterFreqHoSuc.VS.OutGoInterFreqHoSuc.Rescue

• VS.OutGoInterFreqHoSuc.VS.OutGoInterFreqHoSuc.Service



• VS.OutGoInterFreqHoSuc.VS.OutGoInterFreqHoSuc.NoRsrcAvailCacFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 67 VS.IncomInterFreqHoAtt - #176

A-Description

Number of Hard Handovers attempted to this cell located on Serving RNC from another cell ona different frequency from the same RNC

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a RL Setup message for this cell

D-Result





E-Type

• VS.IncomInterFreqHoAtt.VS.IncomInterFreqHoAtt.Rescue

• VS.IncomInterFreqHoAtt.VS.IncomInterFreqHoAtt.Service



• VS.IncomInterFreqHoAtt.VS.IncomInterFreqHoAtt.NoRsrcAvailCacFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 68 VS.IncomInterFreqHoSuc - #177

A-Description

Number of successful Hard Handovers to this cell located on Serving RNC from another cell ona different frequency from the same RNC

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RL deletion message for the old cell

D-Result





E-Type

• VS.IncomInterFreqHoSuc.VS.IncomInterFreqHoSuc.Rescue

• VS.IncomInterFreqHoSuc.VS.IncomInterFreqHoSuc.Service



• VS.IncomInterFreqHoSuc.VS.IncomInterFreqHoSuc.NoRsrcAvailCacFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.3 Soft Handover


Counter name

#201 VS.UtranSideSofterHOAtt

#202 VS.UtranSideSofterHOSucc

#203 VS.UtranSideSofterHOUnsucc

#204 VS.UtranSideSoftHOAtt

#205 VS.UtranSideSoftHOSucc

#206 VS.UtranSideSoftHOUnsucc

#207 VS.UtranSideDelHOAtt

#208 VS.UtranSideDelHOSucc

#209 VS.UeSideHOAtt

#210 VS.UeSideHOSucc

#211 VS.UeSideHOUnsucc

#212 VS.UtranSideIurSoftHOAtt

#213 VS.UtranSideIurSoftHOSucc

#214 VS.UtranSideIurSoftHOUnsucc

#215 VS.UtranSideIurDelSoftHOAtt

#216 VS.UtranSideIurDelSoftHOSucc

Table 69 VS.UtranSideSofterHOAtt - #201

A-Description

Number of attempted Softer Handovers counted against the reference cell from a UTRAN pointof view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a RADIO_LINK_ADDITION_REQUEST NBAP message by SRNC to NodeB

D-Result

one measurement

E-Type

VS.UtranSideSofterHOAtt



F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 70 VS.UtranSideSofterHOSucc - #202

A-Description

Number of successful Softer Handovers counted against the reference cell from an UTRANpoint of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RADIO_LINK_ADDITION_RESPONSE NBAP message on SRNC from NodeB.

D-Result

one measurement

E-Type

VS.UtranSideSofterHOSucc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 71 VS.UtranSideSofterHOUnsucc - #203

A-Description

Number of failed Softer Handovers counted against the reference cell from a UTRAN point ofview.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RADIO_LINK_ADDITION_FAILURE NBAP message on SRNC from NodeB. ortimeout expired without reception of a RADIO_LINK_ADDITION_RESPONSE or FAILURE .

D-Result

one measurement

E-Type

VS.UtranSideSofterHOUnsucc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 72 VS.UtranSideSoftHOAtt - #204

A-Description

Number of attempted Soft Handovers counted against the reference cell from a UTRAN pointof view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a RADIO_LINK_SETUP_REQUEST NBAP message by SRNC to NodeB

D-Result

one measurement

E-Type

VS.UtranSideSoftHOAtt

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 73 VS.UtranSideSoftHOSucc - #205

A-Description

Number of successful Soft Handovers counted against the reference cell from a UTRAN pointof view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RADIO_LINK_SETUP_RESPONSE NBAP message on SRNC from NodeB.

D-Result

one measurement

E-Type

VS.UtranSideSoftHOSucc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 74 VS.UtranSideSoftHOUnsucc - #206

A-Description

Number of failed Soft Handovers counted against the reference cell from a UTRAN point ofview.

B-Collection



CUM

CUMulative

C-Condition (Event)

Reception of a RADIO_LINK_SETUP_FAILURE NBAP message on SRNC from NodeB. orTime-out expired without reception of RADIO_LINK_SETUP_RESPONSE or FAILURE

D-Result

one measurement

E-Type

VS.UtranSideSoftHOUnsucc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 75 VS.UtranSideDelHOAtt - #207

A-Description

Number of attempted Soft Handover or Softer Handover radio link deletions counted againstthe reference cell from a UTRAN point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a RADIO_LINK_DELETION_REQUEST NBAP message by SRNC to NodeB



D-Result

A set of subcounters screened on: Soft or Softer Handover

• Sub-Counter #0 : Softer HO Radio Link Delete

• Sub-Counter #1 : Soft HO Radio Link Delete

E-Type

• VS.UtranSideDelHOAtt.VS.UtranSideDelHOAtt.SofterHORLDel

• VS.UtranSideDelHOAtt.VS.UtranSideDelHOAtt.SoftHORLDel

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 76 VS.UtranSideDelHOSucc - #208

A-Description

Number of successful Soft Handover or Softer Handover radio link deletions counted againstthe reference cell from a UTRAN point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RADIO_LINK_DELETION_RESPONSE NBAP message on SRNC from NodeB.

D-Result

A set of subcounters screened on: Soft or Softer Handover





E-Type

• VS.UtranSideDelHOSucc.VS.UtranSideDelHOSucc.SofterHORLDel

• VS.UtranSideDelHOSucc.VS.UtranSideDelHOSucc.SoftHORLDel

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 77 VS.UeSideHOAtt - #209

A-Description

Number of attempted Handovers (Softer or Soft radio link additions and deletions) countedagainst the reference cell from a UE point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of an ACTIVE_SET_UPDATE_RRC message by SRNC to UE

D-Result

A set of subcounters screened on: Softer or Soft Handover modifications

• Sub-Counter #0 : Softer HO Radio Link Addition

• Sub-Counter #1 : Soft HO Radio Link Setup





E-Type

• VS.UeSideHOAtt.VS.UeSideHOAtt.SofterHORLAdd

• VS.UeSideHOAtt.VS.UeSideHOAtt.SoftHORLSetup

• VS.UeSideHOAtt.VS.UeSideHOAtt.SofterHORLDel

• VS.UeSideHOAtt.VS.UeSideHOAtt.SoftHORLDel

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 78 VS.UeSideHOSucc - #210

A-Description

Number of successful Handovers (Softer or Soft radio link additions and deletions) countedagainst the reference cell from a UE point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of the ACTIVE_SET_UPDATE_COMPLETE RRC message on SRNC from UE

D-Result








E-Type

• VS.UeSideHOSucc.VS.UeSideHOSucc.SofterHORLAdd

• VS.UeSideHOSucc.VS.UeSideHOSucc.SoftHORLSetup

• VS.UeSideHOSucc.VS.UeSideHOSucc.SofterHORLDel

• VS.UeSideHOSucc.VS.UeSideHOSucc.SoftHORLDel

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 79 VS.UeSideHOUnsucc - #211

A-Description

Number of failed Handovers (Softer or Soft radio link additions and deletions) counted againstthe reference cell from a UE point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of the ACTIVE_SET_UPDATE_FAILURE RRC message on SRNC from UE or



Timeout expired without reception of a ACTIVE_SET_UPDATE_COMPLETE or FAILUREmessage

D-Result





• Sub-Counter #3 : Soft HO Radio Link DeleteFailSoftHORLDel

E-Type

• VS.UeSideHOUnsucc.VS.UeSideHOUnsucc.SofterHORLAdd

• VS.UeSideHOUnsucc.VS.UeSideHOUnsucc.SoftHORLSetup

• VS.UeSideHOUnsucc.VS.UeSideHOUnsucc.SofterHORLDel

• VS.UeSideHOUnsucc.VS.UeSideHOUnsucc.SoftHORLDel

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 80 VS.UtranSideIurSoftHOAtt - #212

A-Description

Number of attempted Soft Handovers on IUR counted against the reference cell from a UTRANpoint of view.

B-Collection



CUM

CUMulative

C-Condition (Event)

Sending of a RADIO_LINK_SETUP_REQUEST or RADIO_LINK_ADDITION_REQUESTRNSAP message by SRNC to DRNC

D-Result

one measurement

E-Type

VS.UtranSideIurSoftHOAtt

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 81 VS.UtranSideIurSoftHOSucc - #213

A-Description

Number of successful Soft Handovers on IUR counted against the reference cell from a UT-RAN point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RADIO_LINK_SETUP_RESPONSE or RADIO_LINK_ADDITION_RESPONSE



RNSAP message on SRNC from DRNC.

D-Result

one measurement

E-Type

VS.UtranSideIurSoftHOSucc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 82 VS.UtranSideIurSoftHOUnsucc - #214

A-Description

Number of failed Soft Handover on IUR counted against the reference cell from a UTRAN pointof view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RADIO_LINK_SETUP_FAILURE or RADIO_LINK_ADDITION_FAILURERNSAP message on SRNC from DRNC, or Timeout expired without reception of RA-DIO_LINK_SETUP_RESPONSE or RADIO_LINK_ADDITION_RESPONSE or FAILURE

D-Result

one measurement



E-Type

VS.UtranSideIurSoftHOUnsucc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 83 VS.UtranSideIurDelSoftHOAtt - #215

A-Description

Number of attempted Soft Handover radio link deletions on IUR counted against the referencecell from a UTRAN point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a RADIO_LINK_DELETION_REQUEST RNSAP message by SRNC to DRNC

D-Result

one measurement

E-Type

VS.UtranSideIurDelSoftHOAtt

F-Object Instance

Cell(Reference)

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 84 VS.UtranSideIurDelSoftHOSucc - #216

A-Description

Number of successful Soft Handover radio link deletions on IUR counted against the referencecell from a UTRAN point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RADIO_LINK_DELETION_RESPONSE RNSAP message by on SRNC fromDRNC

D-Result

one measurement

E-Type

VS.UtranSideIurDelSoftHOSucc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.4 Power Management

The reference document for power management is UMT/SYS/DD/0086 Power Management.


Counter name

#301 VS.AveragePowerUsedForSpeech

#302 VS.AveragePowerUsedForData

#303 VS.UplinkRssi

#304 VS.AveragePowerUsedForSignalling

#305 VS.AveragePowerUsedForMiscellaneous

#306 VS.IrmcacPowerDist

#307 VS.DistDlTtlPwrRatio

Table 85 VS.AveragePowerUsedForSpeech - #301

A-Description

the average cell power used for speech calls during a reporting period. It also provides the min-imum and maximum powers during the reporting period. Note since V5.0 (PM30069), powercontrol is taken into account.

B-Collection

VAL

VALue counter

C-Condition (Event)

The cell power used for speech calls is updated on each addition/deletion of a radio-link sup-porting a speech call in this cell.

D-Result

one measurement

E-Type

VS.AveragePowerUsedForSpeech

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

0.1mW

K-Available Release

V1.0

L-Aggregation Rule

Rval

Table 86 VS.AveragePowerUsedForData - #302

A-Description

the average cell power used for data calls (PS and CS data) during a reporting period. It alsoprovides the minimum and maximum powers during the reporting period. Note since V5.0(PM30069), power control is taken into account.

B-Collection

VAL

VALue counter

C-Condition (Event)

The cell power used for data calls is updated on each addition/deletion of a radio-link support-ing a data call in this cell.

D-Result

one measurement

E-Type

VS.AveragePowerUsedForData

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



0.1mW

K-Available Release

V1.0

L-Aggregation Rule

Rval

Table 87 VS.UplinkRssi - #303

A-Description

the Averaged uplink RSSI per cell during a reporting period. The minimum and maximum RSSIduring the reporting period are also provided.

B-Collection

VAL

VALue counter

C-Condition (Event)

The Averaged uplink RSSI is updated on each reception on a NBAP common measurement(each one contains an uplink RSSI measurement).

D-Result

one measurement

E-Type

VS.UplinkRssi

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

mW

K-Available Release

V1.0

L-Aggregation Rule



Rval

Table 88 VS.AveragePowerUsedForSignalling - #304

A-Description

the average cell power used for signalling during a reporting period. It also provides the minim-um and maximum powers during the reporting period. Note since V5.0 (PM30069), power con-trol is taken into account.

B-Collection

VAL

VALue counter

C-Condition (Event)

The cell power used for signalling is updated on each addition/deletion of a radio-link support-ing a signalling call in this cell.

D-Result

one measurement

E-Type

VS.AveragePowerUsedForSignalling

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

0.1mW

K-Available Release

V2.0

L-Aggregation Rule

Rval

Table 89 VS.AveragePowerUsedForMiscellaneous - #305

A-Description



the average cell power used for miscellaneous (multi-service CS+PS) during a reporting peri-od. It also provides the minimum and maximum powers during the reporting period. Note sinceV5.0 (PM30069), power control is taken into account.

B-Collection

VAL

VALue counter

C-Condition (Event)

The average cell power used for miscellaneous is updated on each addition/deletion of a radio-link supporting a multi-service call in this cell.

D-Result

one measurement

E-Type

VS.AveragePowerUsedForMiscellaneous

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

0.1mW

K-Available Release

V3.1

L-Aggregation Rule

Rval

Table 90 VS.IrmcacPowerDist - #306

A-Description

Number of seconds per range of power considered by the CAC algorithm for that cell. The per-centage is calculated as PowerReserved divided by MaxTxPower.

B-Collection

CUM



CUMulative

C-Condition (Event)

Each time IRMCAC(Intelligent Resource Management Call Admission Control) takes place

D-Result

A set of subcounters screened on: Number of seconds per range of power considered by theCAC algorithm for that cell. The percentage is to be computed by dividing the PowerReservedby the MaxTxPower.

• Sub-Counter #0 : 0 to 40 percent of total power





E-Type

• VS.IrmcacPowerDist.VS.IrmcacPowerDist.Rng0to40pcTotPwr





F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 91 VS.DistDlTtlPwrRatio - #307

A-Description

DL TX power ratio P/Pmax received from NBAP common measurement per cell. It details thenumber of common measurements, according to their respective ranges and during the report-ing period

B-Collection

CUM

CUMulative

C-Condition (Event)

The reception of NBAP COMMON MEASUREMENT from NodeB to RNC including Tx Powermeasurements

D-Result

A set of subcounters screened on: Power ratio

• Sub-Counter #0 : 0 to 40 pc





E-Type

• VS.DistDlTtlPwrRatio.VS.DistDlTtlPwrRatio.PwrRt00To40pc





F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.5 RRC Connection

The reference document for RRC management is 3GPP TS25.331 Radio Resource Control (RRC)Protocol Specification.


Counter name

#402 VS.RrcActiveSetUpdateUnsuccess

#403 RRC.SuccConnEstab

#404 RRC.FailConnEstab

#405 VS.RrcConnectionRelease

#407 VS.RrcActiveSetUpdateUnsuccessNeighbRnc

#408 VS.RrcConnectionReleaseNeighbRnc

#409 RRC.AttConnEstab

#412 VS.RrcTransitionCellFachToCellDch

#413 VS.RrcTransitionCellDchToCellFach

#414 VS.RrcAvgNbrCellFach

#415 VS.RrcActiveSetUpdateCompleteProcedure

#416 VS.RrcConnectionSetup

#418 SHO

#419 VS.FirstRrcConnectionRequest

#420 VS.RrcRel

#421 VS.ActiveSetUpdatePerRnc

#422 VS.RrcActiveSetUpdateSuccessNeighbRnc

Table 92 VS.RrcActiveSetUpdateUnsuccess - #402

A-Description

the number of failed RRC ACTIVE SET UPDATE procedures managed by a RNC, for each cellcontrolled by the RNC. The measurement attached to a given cell is incremented for a failedaddition or removal of this cell from the active set.

B-Collection

CUM

CUMulative

C-Condition (Event)

This measurement is based on two different events:. - Receipt of a RRC ACTIVE SET UP-DATE FAILURE message sent by UE to the Serving RNC in response to a RRC ACTIVE SET



UPDATE message. - Time-out expired without reception of a ACTIVE SET UPDATE COM-PLETE message or a ACTIVE SET UPDATE FAILURE message. The events are only con-sidered for cells belonging to the active set which are under the control of the RNC in charge ofthe measurement.

D-Result

A set of subcounters screened on: Family error cause

• Sub-Counter #0 : RRC_ACTIVE_SET_UPDATE_FAILURE


E-Type

• VS.RrcActiveSetUpdateUnsuccess.VS.RrcActiveSetUpdateUnsuccess.RrcActiveSetUpdateFailure

• VS.RrcActiveSetUpdateUnsuccess.VS.RrcActiveSetUpdateUnsuccess.Timeout

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance

N-3GPP specified counter-#402

I-Range

31 Bits

J-Unit

event

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 93 RRC.SuccConnEstab - #403

A-Description

the number of successful RRC connection establishments screened by establishment cause(see Annexe 2).

B-Collection

CUM

CUMulative



C-Condition (Event)

Reception by the RNC of a RRC CONNECTION SETUP COMPLETE message following aRRC connection establishment attempt. A RRC connection establishment attempt is con-sidered on the reception by the RNC of a RRC CONNECTION REQUEST message.

D-Result

A set of subcounters screened on: Cause for rrc establishement, from 3GPP TS 25.331

• Sub-Counter #0 : Originating Conversational call

• Sub-Counter #1 : Originating Streaming Call

• Sub-Counter #2 : Originating Interactive Call

• Sub-Counter #3 : Originating Background Call

• Sub-Counter #4 : Originating Subscribed Traffic Call

• Sub-Counter #5 : Terminating Conversational call

• Sub-Counter #6 : Terminating Streaming Call

• Sub-Counter #7 : Terminating Interactive Call

• Sub-Counter #8 : Terminating Background Call

• Sub-Counter #9 : Emergency Call

• Sub-Counter #10 : Inter-RAT cell re-selection

• Sub-Counter #11 : Inter-RAT cell change order

• Sub-Counter #12 : registration

• Sub-Counter #13 : Detach

• Sub-Counter #14 : Originating High Priority Signalling

• Sub-Counter #15 : Originating Low Priority Signalling

• Sub-Counter #16 : Call re-establishment

• Sub-Counter #17 : Terminating High Priority Signalling

• Sub-Counter #18 : Terminating Low Priority Signalling

• Sub-Counter #19 : Terminating- cause unknown

• Sub-Counter #20 : Spare 12

E-Type

• RRC.SuccConnEstab.RRC.SuccConnEstab.0























F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance

Y-3GPP specified counter-#403

I-Range

31 Bits

J-Unit

event

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 94 RRC.FailConnEstab - #404

A-Description

the number of RRC connection establishment failures screened by establishment failure cause(see Annexe 3).



B-Collection

CUM

CUMulative

C-Condition (Event)

The measurement counts the number of RRC connection establishment attempts which havenot evolved into an RRC connection establishment. A RRC connection establishment attemptis considered on the reception by the RNC of a RRC CONNECTION REQUEST message. ARRC connection establishment is considered on the reception by the RNC of a RRC CON-NECTION SETUP COMPLETE message following a RRC connection attempt. Two scenariiare considered: -1-RRC Connection Setup has been sent, but no RRC Connection Setup Com-plete has been received from the mobile, thus meaning T352 timeout expiry Screening #0 cor-responds to this scenario. -2- RRC connection Setup has not been sent from RNC to UE andan RRC Connection Reject is sent towards the mobile Screenings different from #0 correspondto this scenario.

D-Result

A set of subcounters screened on: Per family of error cause

• Sub-Counter #0 : timeout

• Sub-Counter #1 : unavailable dl code resources

• Sub-Counter #2 : unavailable dl power resources

• Sub-Counter #3 : Unspecified

• Sub-Counter #4 : RSSI

• Sub-Counter #5 : Cell Fach Unspecified CAC

• Sub-Counter #6 : Overload

• Sub-Counter #7 : 3G to 2G Redirection for Emergency Calls

• Sub-Counter #8 : RRC context CAC, pegged when CAC fails for the current RRC connec-tion request.

• Sub-Counter #9 : Unavailable RRC context resource, pegged when the number of RRCcontexts is exhausted

• Sub-Counter #10 : Unavailable FACH context resource, pegged when the number of FACHcontexts in RNC_CALL is exhausted.

• Sub-Counter #11 : No answer from the NodeB

• Sub-Counter #12 : Lack of C-RNTI

• Sub-Counter #13 : UE Ec/No lower than qQualityMin

E-Type

• RRC.FailConnEstab.RRC.FailConnEstab.0
















F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance

Y-3GPP specified counter ; ALCATEL-LUCENT provides more screenings than specified in3GPP. 3GPP specifies only 3 screenings, Congestion, Time-out, and Unspecified.-#404

I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 95 VS.RrcConnectionRelease - #405

A-Description

Number of rrc connection release

B-Collection

CUM



CUMulative

C-Condition (Event)

send RRC_CONNECTION_RELEASE

D-Result

A set of subcounters screened on: Cause for rrc release, from 3GPP TS 25.331

• Sub-Counter #0 : Normal event

• Sub-Counter #1 : unspecified + SCCP release cause

• Sub-Counter #2 : pre-emptive release

• Sub-Counter #3 : congestion

• Sub-Counter #4 : re-establishment reject

• Sub-Counter #5 : user inactivity

• Sub-Counter #6 : directed signalling connection re-establishement

• Sub-Counter #7 : RELCAUSE_SPARE

E-Type

• VS.RrcConnectionRelease.VS.RrcConnectionRelease.NormalEvent

• VS.RrcConnectionRelease.VS.RrcConnectionRelease.UnspecifiedSccpReleaseCause

• VS.RrcConnectionRelease.VS.RrcConnectionRelease.PreemptiveRelease

• VS.RrcConnectionRelease.VS.RrcConnectionRelease.Congestion

• VS.RrcConnectionRelease.VS.RrcConnectionRelease.ReestablishmentReject

• VS.RrcConnectionRelease.VS.RrcConnectionRelease.UserInactivity

• VS.RrcConnectionRelease.VS.RrcConnectionRelease.DirectedSignallingConnectionReestablishement

• VS.RrcConnectionRelease.VS.RrcConnectionRelease.RelcauseSpare

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event



K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 96 VS.RrcActiveSetUpdateUnsuccessNeighbRnc - #407

A-Description

the number of failed RRC ACTIVE SET UPDATE procedures managed by a RNC, for eachneighboring RNC. During such a procedure, the measurement attached to a given neighboringRNC is incremented as many times as there are cells it controls which are concerned by theprocedure failure.

B-Collection

CUM

CUMulative

C-Condition (Event)

This measurement is based on two different events: Receipt of a RRC ACTIVE SET UPDATEFAILURE message sent by UE to the Serving RNC in response to a RRC ACTIVE SET UP-DATE message. Time-out expired without reception of a ACTIVE SET UPDATE COMPLETEmessage or a ACTIVE SET UPDATE FAILURE message. The events are considered for cellsbelonging to the active set which are outside the control of the RNC in charge of the measure-ment.

D-Result

A set of subcounters screened on: Family error cause

• Sub-Counter #0 : RRC_ACTIVE_SET_UPDATE_FAILURE


E-Type

• VS.RrcActiveSetUpdateUnsuccessNeighbRnc.VS.RrcActiveSetUpdateUnsuccessNeighbRnc.RrcActiveSetUpdateFailure

• VS.RrcActiveSetUpdateUnsuccessNeighbRnc.VS.RrcActiveSetUpdateUnsuccessNeighbRnc.Timeout

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 97 VS.RrcConnectionReleaseNeighbRnc - #408

A-Description

the number of RRC connection releases managed by a RNC, screened by release cause, foreach neighboring RNC. During such a procedure, the measurement attached to a given neigh-boring RNC is incremented if the neighboring RNC controls the reference cell of the involvedUE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of the first RRC CONNECTION RELEASE message. The event is onlyconsidered when the UE has a reference cell outside the control of the RNC in charge of themeasurement.

D-Result

A set of subcounters screened on: Cause for rrc release, from 3GPP TS 25.331

• Sub-Counter #0 : Normal event

• Sub-Counter #1 : unspecified + SCCP release cause

• Sub-Counter #2 : pre-emptive release

• Sub-Counter #3 : congestion

• Sub-Counter #4 : re-establishment reject

• Sub-Counter #5 : user inactivity

• Sub-Counter #6 : directed signalling connection re-establishement

• Sub-Counter #7 : RELCAUSE_SPARE

E-Type

• VS.RrcConnectionReleaseNeighbRnc.VS.RrcConnectionReleaseNeighbRnc.NormalEvent



• VS.RrcConnectionReleaseNeighbRnc.VS.RrcConnectionReleaseNeighbRnc.UnspecifiedSccpReleaseCause

• VS.RrcConnectionReleaseNeighbRnc.VS.RrcConnectionReleaseNeighbRnc.PreemptiveRelease

• VS.RrcConnectionReleaseNeighbRnc.VS.RrcConnectionReleaseNeighbRnc.Congestion

• VS.RrcConnectionReleaseNeighbRnc.VS.RrcConnectionReleaseNeighbRnc.ReestablishmentReject

• VS.RrcConnectionReleaseNeighbRnc.VS.RrcConnectionReleaseNeighbRnc.UserInactivity

• VS.RrcConnectionReleaseNeighbRnc.VS.RrcConnectionReleaseNeighbRnc.DirectedSignallingConnectionReestablishement

• VS.RrcConnectionReleaseNeighbRnc.VS.RrcConnectionReleaseNeighbRnc.RelcauseSpare

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance

N-3GPP specified counter-#408

I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 98 RRC.AttConnEstab - #409

A-Description

the number of RRC connection requests screened by establishment cause (see Annexe 2).

B-Collection

CUM

CUMulative

C-Condition (Event)



Reception by the RNC of a RRC CONNECTION REQUEST message.

D-Result























E-Type

• RRC.AttConnEstab.RRC.AttConnEstab.0























F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance

Y-3GPP specified counter-#409

I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 99 VS.RrcTransitionCellFachToCellDch - #412

A-Description

the number of RRC state transitions from Cell_FACH to CELL_DCH.

B-Collection

CUM

CUMulative



C-Condition (Event)

RRC state change from CELL_FACH to CELL_DCH.

D-Result

A set of subcounters screened on: Transition Cause

• Sub-Counter #0 : Call establishment

• Sub-Counter #1 : Always on upgrade

• Sub-Counter #2 : Multi-service

E-Type

• VS.RrcTransitionCellFachToCellDch.VS.RrcTransitionCellFachToCellDch.CallEstablishment

• VS.RrcTransitionCellFachToCellDch.VS.RrcTransitionCellFachToCellDch.AlwaysOnUpgrade

• VS.RrcTransitionCellFachToCellDch.VS.RrcTransitionCellFachToCellDch.Multiservice

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 100 VS.RrcTransitionCellDchToCellFach - #413

A-Description

the number of RRC state transitions from Cell_DCH to CELL_FACH.

B-Collection

CUM



CUMulative

C-Condition (Event)

Last RL_DELETE_SUCCESS and RRC state change to CELL_FACH. Incremented on targetcell.

D-Result

one measurement

E-Type

VS.RrcTransitionCellDchToCellFach

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 101 VS.RrcAvgNbrCellFach - #414

A-Description

the average number of calls in Cell Fach state in a cell during a reporting period. The minimumand maximum number of calls in Cell FACH during the measurement collection interval arealso provided.

B-Collection

LOAD

C-Condition (Event)

The measurement is updated on each event making a RRC context to enter / to leave CellFach state. This measurement is sampled each 100ms.

D-Result



one measurement

E-Type

VS.RrcAvgNbrCellFach

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rload

Table 102 VS.RrcActiveSetUpdateCompleteProcedure - #415

A-Description

the number of successful RRC Active Set Update procedures, for which the cell is the in the listof the active set before or after the Active Set Update execution (even if it is added or removeddue to this procedure). It is incremented once per procedure, whatever the number of cells.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of an RRC Active Set Update Complete from the UE.

D-Result

one measurement

E-Type

VS.RrcActiveSetUpdateCompleteProcedure

F-Object Instance



Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.2

L-Aggregation Rule

Rtotal

Table 103 VS.RrcConnectionSetup - #416

A-Description

the number of RRC CONNECTION SETUP messages sent by the RNC in response to RRCCONNECTION REQUEST. The RNC can send an RRC Connection Request message severaltimes if no answer is received from the mobile. The number of times the RNC resends RRCConnection Request and the time between successive RRC Connection Request messagesare controlled by N351 and T351 respectively. Moreover, the RNC can also "quick" repeat themessage (if CPICH Ec/N0 or CPICH RSCP measured by the UE and put in the RRC CON-NECTION REQUEST are below thresholds and if quick-repeat is activated). In this case themessage is duplicated by RLC and sent on several consecutive radio frames.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of an RRC CONNECTION SETUP in response to a RRC CONNECTION REQUESTor on T351 expiry (only on first expiry). (If Quick-repeat is enabled, the counter is incrementedonce for all duplications).

D-Result

A set of subcounters screened on: Per family of error cause

• Sub-Counter #0 : Initial RRC Cnx Setup without quick repeat

• Sub-Counter #1 : Initial RRC Cnx Setup with quick repeat



• Sub-Counter #2 : first repetition of RRC Cnx Setup without quick repeat

• Sub-Counter #3 : first repetition of RRC Cnx Setup with quick repeat

E-Type

• VS.RrcConnectionSetup.VS.RrcConnectionSetup.InitialWithoutQuickRepeat

• VS.RrcConnectionSetup.VS.RrcConnectionSetup.InitialWithQuickRepeat

• VS.RrcConnectionSetup.VS.RrcConnectionSetup.FirstRepetitionWithoutQuickRepeat

• VS.RrcConnectionSetup.VS.RrcConnectionSetup.FirstRepetitionWithQuickRepeat

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 104 SHO - #418

A-Description

Number of successfull RRC ACTIVE SET UPDATE, incremented for each radio link added orremoved.

B-Collection

CUM

CUMulative

C-Condition (Event)

reception of RRC ACTIVE_SET_UPDATE_COMPLETE successful

D-Result

A set of subcounters screened on: Cause for update of the active set on that cell



• Sub-Counter #0 : radio link addition on cell

• Sub-Counter #1 : radio link deletion on the cell

E-Type

• SHO.SHO.SuccRLAddUESide

• SHO.SHO.SuccRLDelUESide

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance

Y-3GPP defined counter-#418

I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 105 VS.FirstRrcConnectionRequest - #419

A-Description

Number of first RRC connection requests for a given UE on a given cell.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of first RRC_CONNECTION_REQUEST in a TMU for a given UE from a given avail-able cell.

D-Result

























E-Type

• VS.FirstRrcConnectionRequest.VS.FirstRrcConnectionRequest.0























F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 106 VS.RrcRel - #420

A-Description

Number of Rrc Released

B-Collection

CUM

CUMulative

C-Condition (Event)

RRC Release

D-Result

A set of subcounters screened on: Per type of RRC Release

• Sub-Counter #0 : UnSpecSccpCcchAtt



• Sub-Counter #1 : DirectSigCcchAtt

E-Type

• VS.RrcRel.VS.RrcRel.UnSpecSccpCcchAtt

• VS.RrcRel.VS.RrcRel.DirectSigCcchAtt

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 107 VS.ActiveSetUpdatePerRnc - #421

A-Description

Number of active set update per RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

The sending of RRC active set update by RNC to UE.

D-Result

one measurement

E-Type

VS.ActiveSetUpdatePerRnc

F-Object Instance



RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 108 VS.RrcActiveSetUpdateSuccessNeighbRnc - #422

A-Description

Number of successfull RRC ACTIVE SET UPDATE on any cell of the active set belonging to aneighbouring RNC

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of RRC ACTIVE_SET_UPDATE_COMPLETE successful

D-Result

A set of subcounters screened on: Cause for update of the active set on that cell

• Sub-Counter #0 : Radio link addition on cell

• Sub-Counter #1 : Radio link removal of cell

E-Type

• VS.RrcActiveSetUpdateSuccessNeighbRnc.VS.RrcActiveSetUpdateSuccessNeighbRnc.RadioLinkAdditionOnCell

• VS.RrcActiveSetUpdateSuccessNeighbRnc.VS.RrcActiveSetUpdateSuccessNeighbRnc.RadioLinkRemovalOfCell

F-Object Instance



Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.6 IU Connection

The reference document for IU management is 3GPP TS25.413 Iu Interface RANAP Signaling.


Counter name

#502 VS.IuSccpCnxUnsuccess

#505 VS.IuReleaseCommandCs

#505 IRATHO.SuccOutCS

#506 VS.IuReleaseCommandPs

#506 RATHO.SuccOutPSUTRAN

#516 VS.IuReceivedSccpAbnormalDisconnectsCs

#517 VS.IuEmittedSccpAbnormalDisconnectsPs

#518 VS.IuReceivedSccpAbnormalDisconnectsPs

#532 VS.IuEmittedSccpAbnormalDisconnectsCs

#535 VS.IuRelocationRequests

#536 VS.IuRelocationRequestFailuresCs

#537 VS.IuRelocationRequestFailuresPs

#548 VS.IuSccpCnxSuccess

#552 VS.IuReleaseCommandCs

#552 IRATHO.SuccOutCS

#553 VS.IuReleaseCommandPs

#553 IRATHO.SuccOutPS

#556 VS.IuRelocationRequired

#557 VS.IuRelocationCommands

#558 VS.IuRelocationCmdFailuresCs

#559 VS.IuRelocationCommandFailuresPs

#560 VS.IuAbnormRelReqCsNrnc

#561 VS.IuAbnormRelReqPsNrnc

#562 VS.IuReleaseCompleteCsNrnc

#564 VS.IuReleaseCmdAfterCcConAck

#565 VS.IuReleaseReqAfterCcConAck

#566 VS.IuReleaseCmdBeforeCcConAck

#567 VS.IuReleaseReqBeforeCcConAck

#568 VS.IuRelocationCancels

#569 VS.IuRelocationCompletes




Counter name

#570 VS.IuRelocationDetects

#571 VS.IuReleaseCompleteCs

#572 VS.IuAbnormalReleaseRequestCs

#573 VS.IuAbnormalReleaseRequestPs

#574 VS.IubcSabpMsg

#575 VS.IubcSabpWrtRplcFail

#576 VS.IuReleaseReqCs

#577 VS.IuReleaseReqPs

#578 VS.IuAvgNbrSccpCnxCs

#579 VS.IuAvgNbrSccpCnxPs

#580 VS.IuReleaseRequestCsNrnc

#581 VS.IuReleaseRequestPsNrnc

Table 109 VS.IuSccpCnxUnsuccess - #502

A-Description

the number of failed SCCP connections at Iu interface, screened by CN domain and by peerentity having refused the connection

B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccessful SCCP connection establishment

D-Result

A set of subcounters screened on: per type of core, per sens of refusal

• Sub-Counter #0 : Fail Iu-cs connection req by Rnc

• Sub-Counter #1 : Fail Iu-cs connection req by Core Network CS

• Sub-Counter #2 : Fail Iu-ps connection req by Rnc

• Sub-Counter #3 : Fail Iu-ps connection req by Core Network PS

E-Type

• VS.IuSccpCnxUnsuccess.VS.IuSccpCnxUnsuccess.FailIucsConnectionReqByRnc

• VS.IuSccpCnxUnsuccess.VS.IuSccpCnxUnsuccess.FailIucsConnectionReqByCoreNetworkCs

• VS.IuSccpCnxUnsuccess.VS.IuSccpCnxUnsuccess.FailIupsConnectionReqByRnc

• VS.IuSccpCnxUnsuccess.VS.IuSccpCnxUnsuccess.FailIupsConnectionReqByCoreNetwor



kPs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 110 VS.IuReleaseCommandCs - #505

A-Description

Number of RANAP/IU_RELEASE_COMMAND messages received by RNC on the IU-CS inter-face when the reference cell is located on a Drift RNC..

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of IU_RELEASE_COMMAND from CS domain

D-Result

A set of subcounters screened on: per family of cause (iRNC internal cause and not 3GPP-25.413 which support up to 64 causes)

• Sub-Counter #0 : Normal Release

• Sub-Counter #2 : Release due to UTRAN Generated Reason

• Sub-Counter #3 : other

• Sub-Counter #4 : Relocation Cancelled




• Sub-Counter #6 : Unspecified Failure

• Sub-Counter #7 : User Inactivity

• Sub-Counter #8 : No Remaining RAB

• Sub-Counter #9 : Successful 3G3G relocation

E-Type

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.NormalRelease

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.ReleaseDueToUtranGeneratedReason

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.Other

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.RelocationCancelled

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.OamIntervention

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.UnspecifiedFailure

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.UserInactivity

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.NoRemainingRab

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.Succ3G3GReloc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 111 IRATHO.SuccOutCS - #505

A-Description

Number of RANAP/IU_RELEASE_COMMAND messages received by RNC.



B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result


• Sub-Counter #1 : Successful relocation

E-Type

• IRATHO.SuccOutCS.IRATHO.SuccOutCS.

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 112 VS.IuReleaseCommandPs - #506

A-Description

Number of RANAP/IU_RELEASE_COMMAND messages received by RNC on the IU-PS inter-face when the reference cell is located on a Drift RNC..

B-Collection

CUM

CUMulative



C-Condition (Event)

Reception of IU_RELEASE_COMMAND from PS domain

D-Result


• Sub-Counter #0 : Normal Release (corresponds to RANAP cause value 83)

• Sub-Counter #2 : Release due to UTRAN Generated Reason (corresponds to RANAPcause value 15) or each time RNC previously sent an IU RELEASE REQUEST

• Sub-Counter #3 : other (any cause not mapped to one of the other screening values)

• Sub-Counter #4 : Relocation Cancelled (corresponds to RANAP cause value 10)

• Sub-Counter #5 : OAM Intervention (corresponds to RANAP cause value 113)

• Sub-Counter #6 : Unspecified Failure (corresponds to RANAP cause value 115)

• Sub-Counter #7 : User Inactivity (corresponds to RANAP cause value 16)

• Sub-Counter #8 : No Remaining RAB (corresponds to RANAP cause value 31)


E-Type

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.NormalRelease

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.ReleaseDueToUtranGeneratedReason

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.Other

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.RelocationCancelled

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.OamIntervention

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.UnspecifiedFailure

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.UserInactivity

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.NoRemainingRab

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.Succ3G3GReloc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

event

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 113 RATHO.SuccOutPSUTRAN - #506

A-Description

Number of RANAP/IU_RELEASE_COMMAND messages received by RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result



E-Type

• RATHO.SuccOutPSUTRAN.RATHO.SuccOutPSUTRAN.

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V3.0

L-Aggregation Rule

Rtotal

Table 114 VS.IuReceivedSccpAbnormalDisconnectsCs - #516

A-Description

the number of received SCCP abnormal disconnections on Iu CS

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception by the RNC of an SCCP disconnections on Iu CS inidicating an error condition

D-Result

one measurement

E-Type

VS.IuReceivedSccpAbnormalDisconnectsCs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 115 VS.IuEmittedSccpAbnormalDisconnectsPs - #517

A-Description



the number of emitted SCCP abnormal disconnections on Iu PS

B-Collection

CUM

CUMulative

C-Condition (Event)

Emitted SCCP abnormal disconnections on Iu PS

D-Result

A set of subcounters screened on: Tx SCCP abnormal disconnect cause

• Sub-Counter #0 : End user originated

• Sub-Counter #1 : End user congestion

• Sub-Counter #2 : End user failure

E-Type

• VS.IuEmittedSccpAbnormalDisconnectsPs.VS.IuEmittedSccpAbnormalDisconnectsPs.EndUserOriginated

• VS.IuEmittedSccpAbnormalDisconnectsPs.VS.IuEmittedSccpAbnormalDisconnectsPs.EndUserCongestion

• VS.IuEmittedSccpAbnormalDisconnectsPs.VS.IuEmittedSccpAbnormalDisconnectsPs.EndUserFailure

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 116 VS.IuReceivedSccpAbnormalDisconnectsPs - #518



A-Description

the number of received SCCP abnormal disconnections on Iu PS

B-Collection

CUM

CUMulative

C-Condition (Event)

Received SCCP abnormal disconnections on Iu PS

D-Result

one measurement

E-Type

VS.IuReceivedSccpAbnormalDisconnectsPs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 117 VS.IuEmittedSccpAbnormalDisconnectsCs - #532

A-Description

the number of SCCP disconnections on Iu CS emitted by the RNC for an abnormal reason.

B-Collection

CUM

CUMulative

C-Condition (Event)



Emitted SCCP abnormal disconnections on Iu CS (ie. Due to an error condition)

D-Result





E-Type

• VS.IuEmittedSccpAbnormalDisconnectsCs.VS.IuEmittedSccpAbnormalDisconnectsCs.EndUserOriginated

• VS.IuEmittedSccpAbnormalDisconnectsCs.VS.IuEmittedSccpAbnormalDisconnectsCs.EndUserCongestion

• VS.IuEmittedSccpAbnormalDisconnectsCs.VS.IuEmittedSccpAbnormalDisconnectsCs.EndUserFailure

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 118 VS.IuRelocationRequests - #535

A-Description

the number of RANAP RELOCATION_ REQUEST messages received by the target RNC on Iu

B-Collection

CUM

CUMulative



C-Condition (Event)

Reception of a RANAP RELOCATION_ REQUEST message by the RNC on Iu

D-Result

A set of subcounters screened on: Per type of relocation and CN Domain

• Sub-Counter #0 : CS 3G-3G Relocation

• Sub-Counter #1 : PS 3G-3G Relocation

• Sub-Counter #2 : CS 2G-3G Relocation

• Sub-Counter #3 : CS 3G-3G Relocation, UE not involved

• Sub-Counter #4 : PS 3G-3G Relocation, UE not involved

E-Type

• VS.IuRelocationRequests.VS.IuRelocationRequests.Cs3Gto3GRelocation

• VS.IuRelocationRequests.VS.IuRelocationRequests.Ps3Gto3GRelocation

• VS.IuRelocationRequests.VS.IuRelocationRequests.Cs2Gto3GRelocation

• VS.IuRelocationRequests.VS.IuRelocationRequests.Cs3Gto3GRelocationUeNotInv

• VS.IuRelocationRequests.VS.IuRelocationRequests.Ps3Gto3GRelocationUeNotInv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 119 VS.IuRelocationRequestFailuresCs - #536

A-Description

the number of RANAP RELOCATION_ FAILURE messages sent by the target RNC on Iu-PS,



because of the failure of an incoming relocation request. For Ps Nortel uses only UE involvedrelocation procedures, and they are used here only for incoming Ps 3G to 3G Relocation.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a RANAP RELOCATION_FAILURE message by the RNC on Iu CS

D-Result

A set of subcounters screened on: RANAP Relocation request failure per relocation type on CSIu interface

• Sub-Counter #0 : 3G-3G UE involved. Relocation timeout

• Sub-Counter #1 : 3G-3G UE involved. Relocation failure in target system

• Sub-Counter #2 : 3G-3G UE involved. Relocation unable to establish

• Sub-Counter #3 : 3G-3G UE involved. Other relocation failure

• Sub-Counter #4 : 2G-3G Relocation timeout

• Sub-Counter #5 : 2G-3G Relocation failure in target system

• Sub-Counter #6 : 2G-3G Relocation unable to establish

• Sub-Counter #7 : 2G-3G Other relocation failure

• Sub-Counter #8 : 3G-3G UE involved. RRC Context CAC. Pegged when CAC fails for theentering CS reloc.

• Sub-Counter #9 : 2G-3G RRC Context CAC. Pegged when CAC fails for the entering CSreloc.

• Sub-Counter #10 : 3G-3G UE involved. Unavailable IU CNX context resources. Peggedwhen the IU connexion contexts are exhausted for the entering CS reloc.

• Sub-Counter #11 : 2G-3G Unavailable IU CNX context resources. Pegged when the IUconnexion contexts are exhausted for the entering CS reloc.

• Sub-Counter #12 : 3G-3G UE not involved. Relocation timeout (TRelocAlloc).

• Sub-Counter #13 : 3G-3G UE not involved. Relocation failure in target system.

• Sub-Counter #14 : 3G-3G UE not involved. Unavailable IU CNX context resources. Peggedwhen the IU connexion contexts are exhausted for the entering CS reloc.

• Sub-Counter #15 : 3G-3G UE not involved. Other relocation failure.

E-Type

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.3Gto3GRejectionDueToTimeOut

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.3Gto3GRejectionDueToFailureInTargetSystem

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.3Gto3GRejectionC



annotEstablishLocation

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.3Gto3GRejectionOtherCauses

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.2Gto3GRejectionDueToTimeOut

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.2Gto3GRejectionDueToFailureInTargetSystem

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.2Gto3GRejectionCannotEstablishLocation

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.2Gto3GRejectionOtherCauses

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.3Gto3GRRCCtxt

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.2Gto3GRRCCtxt

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.3Gto3GIuCnxCtxt

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.2Gto3GIuCnxCtxt

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.3Gto3GRelocTimeOutUeNotInv

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.3Gto3GRelocFailureInTargetSysUeNotInv

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.3Gto3GIuCnxCtxtUeNotInv

• VS.IuRelocationRequestFailuresCs.VS.IuRelocationRequestFailuresCs.3Gto3GOtherRelocFailureUeNotInv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.0

L-Aggregation Rule



Rtotal

Table 120 VS.IuRelocationRequestFailuresPs - #537

A-Description

the number of RANAP RELOCATION_ FAILURE messages sent by the target RNC on Iu-PS,because of the failure of an incoming relocation request.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a RANAP RELOCATION_FAILURE message by the RNC on Iu PS

D-Result

A set of subcounters screened on: RANAP Relocation request failure per relocation type on PSIu interface

• Sub-Counter #0 : 3G-3G UE involved. Relocation time out




• Sub-Counter #4 : 3G-3G UE involved. RRC Context CAC. Pegged when CAC fails for thenentering PS reloc.

• Sub-Counter #5 : 3G-3G UE involved. Unavailable IU CNX context resources. Peggedwhen the IU connexion contexts are exhausted for the entering PS reloc.

• Sub-Counter #6 : 3G-3G UE not involved. Relocation timeout (TRelocAlloc).


• Sub-Counter #8 : 3G-3G UE not involved. Unavailable IU CNX context resources. Peggedwhen the IU connexion contexts are exhausted for the entering PS reloc.


E-Type

• VS.IuRelocationRequestFailuresPs.VS.IuRelocationRequestFailuresPs.3Gto3GRejectionDueToTimeOut

• VS.IuRelocationRequestFailuresPs.VS.IuRelocationRequestFailuresPs.3Gto3GRejectionDueToFailureInTargetSystem

• VS.IuRelocationRequestFailuresPs.VS.IuRelocationRequestFailuresPs.3Gto3GRejectionCannotEstablishLocation

• VS.IuRelocationRequestFailuresPs.VS.IuRelocationRequestFailuresPs.3Gto3GRejectionOtherCauses

• VS.IuRelocationRequestFailuresPs.VS.IuRelocationRequestFailuresPs.3Gto3GRRCCtxt



• VS.IuRelocationRequestFailuresPs.VS.IuRelocationRequestFailuresPs.3Gto3GIuCnxCtxt

• VS.IuRelocationRequestFailuresPs.VS.IuRelocationRequestFailuresPs.3Gto3GRelocTimeOutUeNotInv

• VS.IuRelocationRequestFailuresPs.VS.IuRelocationRequestFailuresPs.3Gto3GRelocFailureInTargetSysUeNotInv

• VS.IuRelocationRequestFailuresPs.VS.IuRelocationRequestFailuresPs.3Gto3GIuCnxCtxtUeNotInv

• VS.IuRelocationRequestFailuresPs.VS.IuRelocationRequestFailuresPs.3Gto3GOtherRelocFailureUeNotInv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.0

L-Aggregation Rule

Rtotal

Table 121 VS.IuSccpCnxSuccess - #548

A-Description

Number of successful sccp connection at Iu interface

B-Collection

CUM

CUMulative

C-Condition (Event)

At correct connection establishement (confirm ok)

D-Result

A set of subcounters screened on: Per type of core and originator



• Sub-Counter #0 : With CS core network (connection requested by RNC)

• Sub-Counter #1 : With PS core network (connection requested by RNC)

• Sub-Counter #2 : With CS core network (connection requested by core network)

• Sub-Counter #3 : With PS core network (connection requested by core network)

E-Type

• VS.IuSccpCnxSuccess.VS.IuSccpCnxSuccess.CsReqByRNC

• VS.IuSccpCnxSuccess.VS.IuSccpCnxSuccess.PsReqByRNC

• VS.IuSccpCnxSuccess.VS.IuSccpCnxSuccess.CsReqByCN

• VS.IuSccpCnxSuccess.VS.IuSccpCnxSuccess.PsReqByCN

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 122 VS.IuReleaseCommandCs - #552

A-Description

Number of RANAP/IU_RELEASE_COMMAND messages received by RNC on the IU-CS inter-face when the reference cell is located on a Drift RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)




D-Result











E-Type

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.NormalRelease

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.ReleaseDueToUtranGeneratedReason

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.Other

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.RelocationCancelled

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.OamIntervention

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.UnspecifiedFailure

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.UserInactivity

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.NoRemainingRab

• VS.IuReleaseCommandCs.VS.IuReleaseCommandCs.Succ3G3GReloc

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V4.2

L-Aggregation Rule

Rtotal

Table 123 IRATHO.SuccOutCS - #552

A-Description

Number of RANAP/IU_RELEASE_COMMAND messages received by RNC on the IU-CS inter-face when the reference cell is located on a Drift RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result



E-Type

• IRATHO.SuccOutCS.IRATHO.SuccOutCS.

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal



Table 124 VS.IuReleaseCommandPs - #553

A-Description

Number of RANAP/IU_RELEASE_COMMAND messages received by RNC on the IU-PS inter-face when the reference cell is located on a Drift RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result











E-Type

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.NormalRelease

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.ReleaseDueToUtranGeneratedReason

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.Other

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.RelocationCancelled

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.OamIntervention

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.UnspecifiedFailure

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.UserInactivity

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.NoRemainingRab

• VS.IuReleaseCommandPs.VS.IuReleaseCommandPs.Succ3G3GReloc

F-Object Instance



Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 125 IRATHO.SuccOutPS - #553

A-Description

Number of RANAP/IU_RELEASE_COMMAND messages received by RNC on the IU-PS inter-face when the reference cell is located on a Drift RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result



E-Type

• IRATHO.SuccOutPS.IRATHO.SuccOutPS.

F-Object Instance

Neighbouring RNC

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 126 VS.IuRelocationRequired - #556

A-Description

Number of relocation required at Iu interface

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Relocation Required

D-Result

A set of subcounters screened on: Per type of core and type of relocation

• Sub-Counter #0 : 3G-3G CS, UE involved

• Sub-Counter #1 : 3G-3G PS, UE involved

• Sub-Counter #2 : 3G-2G CS

• Sub-Counter #3 : 3G-3G CS, UE not involved

• Sub-Counter #4 : 3G-3G PS, UE not involved

E-Type

• VS.IuRelocationRequired.VS.IuRelocationRequired.3Gto3GCs

• VS.IuRelocationRequired.VS.IuRelocationRequired.3Gto3GPs

• VS.IuRelocationRequired.VS.IuRelocationRequired.3Gto2GCs

• VS.IuRelocationRequired.VS.IuRelocationRequired.3Gto3GCsUeNotInv

• VS.IuRelocationRequired.VS.IuRelocationRequired.3Gto3GPsUeNotInv

F-Object Instance



RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 127 VS.IuRelocationCommands - #557

A-Description

Number of relocation commands at Iu interface

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Relocation Command

D-Result

A set of subcounters screened on: Per type of core and type of relocation

• Sub-Counter #0 : 3G-3G CS, UE involved

• Sub-Counter #1 : 3G-3G PS, UE involved


• Sub-Counter #3 : 3G-3G CS, UE not involved

• Sub-Counter #4 : 3G-3G PS, UE not involved

E-Type

• VS.IuRelocationCommands.VS.IuRelocationCommands.3Gto3GCs

• VS.IuRelocationCommands.VS.IuRelocationCommands.3Gto3GPs

• VS.IuRelocationCommands.VS.IuRelocationCommands.3Gto2GCs



• VS.IuRelocationCommands.VS.IuRelocationCommands.3Gto3GCsUeNotInv

• VS.IuRelocationCommands.VS.IuRelocationCommands.3Gto3GPsUeNotInv

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 128 VS.IuRelocationCmdFailuresCs - #558

A-Description

Number of relocation command failures on CS Iu interface

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP Relocation Command failures on CS Iu interface

D-Result

A set of subcounters screened on: IU Relocation command failure causes

• Sub-Counter #0 : 3G to 3G UE involved. Relocation timeout

• Sub-Counter #1 : 3G to 3G UE involved. Relocation already in progress

• Sub-Counter #2 : 3G to 3G UE involved. Relocation failure in target system

• Sub-Counter #3 : 3G to 3G UE involved. Relocation unable to establish

• Sub-Counter #4 : 3G to 3G UE involved. Other relocation failure

• Sub-Counter #5 : 3G to 2G UE involved. Relocation timeout



• Sub-Counter #6 : 3G to 2G UE involved. Relocation already in progress

• Sub-Counter #7 : 3G to 2G UE involved. Relocation failure in target system

• Sub-Counter #8 : 3G to 2G UE involved. Relocation unable to establish

• Sub-Counter #9 : 3G to 2G UE involved. Other relocation failure

• Sub-Counter #10 : 3G to 3G UE not involved. Relocation timeout

• Sub-Counter #11 : 3G to 3G UE not involved. Relocation already in progress

• Sub-Counter #12 : 3G to 3G UE not involved. Relocation failure in target system

• Sub-Counter #13 : 3G to 3G UE not involved. Other relocation failure

E-Type

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto3GRelocTimeoutUeInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto3GAlreadyInProgrUeInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto3GFailTargetUeInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto3GUnableToEstabUeInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto3GOtherUeInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto2GRelocTimeoutUeInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto2GAlreadyInProgrUeInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto2GFailTargetUeInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto2GUnableToEstabUeInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto2GOtherUeInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto3GRelocTimeoutUeNotInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto3GAlreadyInProgrUeNotInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto3GFailTargetUeNotInv

• VS.IuRelocationCmdFailuresCs.VS.IuRelocationCmdFailuresCs.3Gto3GOtherUeNotInv

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 129 VS.IuRelocationCommandFailuresPs - #559

A-Description

the number of RANAP RELOCATION_PREPARATION_FAILURE messages received by theS-RNC on Iu PS In case of TRELOCAlloc expiry, CN answers with Relocation Command Fail-ure, cause Relocation time-out. If a relocation is already in progress, CN answers with Reloca-tion Command failure, cause Relocation already in progress. Other relocation failures aretriggered by the target RNC answering to the CN as described in Relocation Resource alloca-tion in 25.413. The UE being involved in the Relocation, if some requested RABs are not sup-ported by the target RNC, the cause "relocation unable to establish" will be provided by the tar-get RNC, then to the CN, then to the source RNC in Relocation Command Failure. In case oflack of resources in the target system, CN answers with Relocation Command Failure, cause"Relocation failure in target system".

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RANAP RELOCATION_PREPARATION_FAILURE message by the RNC on IuPS

D-Result

A set of subcounters screened on: IU Relocation command failure causes

• Sub-Counter #0 : 3G-3G UE involved. Relocation timeout.

• Sub-Counter #1 : 3G-3G UE involved. Relocation already in progress




• Sub-Counter #5 : 3G-3G UE not involved. Relocation timeout.



• Sub-Counter #6 : 3G-3G UE not involved. Relocation already in progress.



E-Type

• VS.IuRelocationCommandFailuresPs.VS.IuRelocationCommandFailuresPs.RelocTimeoutUeInv

• VS.IuRelocationCommandFailuresPs.VS.IuRelocationCommandFailuresPs.RelocAlreadyInProgressUeInv

• VS.IuRelocationCommandFailuresPs.VS.IuRelocationCommandFailuresPs.RelocFailureInTargetSystemUeInv

• VS.IuRelocationCommandFailuresPs.VS.IuRelocationCommandFailuresPs.RelocUnableEstablishUeInv

• VS.IuRelocationCommandFailuresPs.VS.IuRelocationCommandFailuresPs.RelocOtherCausesUeInv

• VS.IuRelocationCommandFailuresPs.VS.IuRelocationCommandFailuresPs.RelocTimeoutUeNotInv

• VS.IuRelocationCommandFailuresPs.VS.IuRelocationCommandFailuresPs.RelocAlreadyInProgressUeNotInv

• VS.IuRelocationCommandFailuresPs.VS.IuRelocationCommandFailuresPs.RelocFailureInTargetSystemUeNotInv

• VS.IuRelocationCommandFailuresPs.VS.IuRelocationCommandFailuresPs.RelocOtherCausesUeNotInv

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 130 VS.IuAbnormRelReqCsNrnc - #560

A-Description

Number of Iu CS release requests due to abnormal conditions, when the reference FddCell ofthese calls is located on the drift RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

Whenever RNC requests Iu CS release due to abnormal conditions

D-Result

A set of subcounters screened on: Derived AsConf Screening for CS DlAsConfId , see also An-nex: T10

• Sub-Counter #0 : Other




• Sub-Counter #4 : CS Streaming 57.6


• Sub-Counter #6 : CS Signalling + PS

E-Type

• VS.IuAbnormRelReqCsNrnc.VS.IuAbnormRelReqCsNrnc.DlAsCnfOther

• VS.IuAbnormRelReqCsNrnc.VS.IuAbnormRelReqCsNrnc.DlAsCnfSig

• VS.IuAbnormRelReqCsNrnc.VS.IuAbnormRelReqCsNrnc.DlAsCnfCsSpeech

• VS.IuAbnormRelReqCsNrnc.VS.IuAbnormRelReqCsNrnc.DlAsCnfCsData

• VS.IuAbnormRelReqCsNrnc.VS.IuAbnormRelReqCsNrnc.DlAsCnfCsStr57_6

• VS.IuAbnormRelReqCsNrnc.VS.IuAbnormRelReqCsNrnc.DlAsCnfCsStr14_4

• VS.IuAbnormRelReqCsNrnc.VS.IuAbnormRelReqCsNrnc.DlAsCnfCsSigPs

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 131 VS.IuAbnormRelReqPsNrnc - #561

A-Description

Number of Iu PS release requests due to abnormal conditions, when the reference FddCell ofthese calls is located on the drift RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

Whenever RNC requests Iu PS release due to abnormal conditions

D-Result

A set of subcounters screened on: Derived AsConf Screening for PS DlAsConfId , see also An-nex: T09


• Sub-Counter #1 : PS Streaming 16




• Sub-Counter #5 : TRB on cell FACH

• Sub-Counter #6 : PS I/B 8









• Sub-Counter #13 : PS Signalling + CS

E-Type

• VS.IuAbnormRelReqPsNrnc.VS.IuAbnormRelReqPsNrnc.DlAsCnfSig

• VS.IuAbnormRelReqPsNrnc.VS.IuAbnormRelReqPsNrnc.DlAsCnfPsStr16




• VS.IuAbnormRelReqPsNrnc.VS.IuAbnormRelReqPsNrnc.DlAsCnfTrbCellFach

• VS.IuAbnormRelReqPsNrnc.VS.IuAbnormRelReqPsNrnc.DlAsCnfPsIB8






• VS.IuAbnormRelReqPsNrnc.VS.IuAbnormRelReqPsNrnc.DlAsCnfHsdpa

• VS.IuAbnormRelReqPsNrnc.VS.IuAbnormRelReqPsNrnc.DlAsCnfPsSigCs

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 132 VS.IuReleaseCompleteCsNrnc - #562

A-Description



Number of RANAP Iu Release Complete sent by RNC to CN on the Iu interface on CS domain,when the reference FDDCELL of these calls is located on the drift RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RANAP Iu Release Complete on CS domain

D-Result









E-Type

• VS.IuReleaseCompleteCsNrnc.VS.IuReleaseCompleteCsNrnc.DlAsCnfOther

• VS.IuReleaseCompleteCsNrnc.VS.IuReleaseCompleteCsNrnc.DlAsCnfSig

• VS.IuReleaseCompleteCsNrnc.VS.IuReleaseCompleteCsNrnc.DlAsCnfCsSpeech

• VS.IuReleaseCompleteCsNrnc.VS.IuReleaseCompleteCsNrnc.DlAsCnfCsData

• VS.IuReleaseCompleteCsNrnc.VS.IuReleaseCompleteCsNrnc.DlAsCnfCsStr57_6

• VS.IuReleaseCompleteCsNrnc.VS.IuReleaseCompleteCsNrnc.DlAsCnfCsStr14_4

• VS.IuReleaseCompleteCsNrnc.VS.IuReleaseCompleteCsNrnc.DlAsCnfCsSigPs

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 133 VS.IuReleaseCmdAfterCcConAck - #564

A-Description

Number of RANAP Iu Release Command messages received by the RNC on the Iu after CCConnect Ack.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of RANAP Iu Release Commannd

D-Result

A set of subcounters screened on: IU release cause after CC Connect Ack

• Sub-Counter #0 : Other (any CS bearer not listed below)

• Sub-Counter #1 : CS Speech

• Sub-Counter #2 : CS Data 64



E-Type

• VS.IuReleaseCmdAfterCcConAck.VS.IuReleaseCmdAfterCcConAck.Other

• VS.IuReleaseCmdAfterCcConAck.VS.IuReleaseCmdAfterCcConAck.CsSpeech

• VS.IuReleaseCmdAfterCcConAck.VS.IuReleaseCmdAfterCcConAck.CsData64

• VS.IuReleaseCmdAfterCcConAck.VS.IuReleaseCmdAfterCcConAck.CsStrm144

• VS.IuReleaseCmdAfterCcConAck.VS.IuReleaseCmdAfterCcConAck.CsStrm576

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 134 VS.IuReleaseReqAfterCcConAck - #565

A-Description

Number of RANAP Iu Release Request messages sent by RNC on the Iu after CC ConnectAck.

B-Collection

CUM

CUMulative

C-Condition (Event)

The sending of a RANAP Iu Release Request by the RNC after CC_Connect_Ack on the IU-CS interface.

D-Result

A set of subcounters screened on: IU release cause after CC Connect Ack






E-Type

• VS.IuReleaseReqAfterCcConAck.VS.IuReleaseReqAfterCcConAck.Other

• VS.IuReleaseReqAfterCcConAck.VS.IuReleaseReqAfterCcConAck.CsSpeech

• VS.IuReleaseReqAfterCcConAck.VS.IuReleaseReqAfterCcConAck.CsData64

• VS.IuReleaseReqAfterCcConAck.VS.IuReleaseReqAfterCcConAck.CsStrm144

• VS.IuReleaseReqAfterCcConAck.VS.IuReleaseReqAfterCcConAck.CsStrm576

F-Object Instance



Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 135 VS.IuReleaseCmdBeforeCcConAck - #566

A-Description

Number of RANAP Iu Release Command messages received by RNC on the Iu before CCConnect Ack.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of RANAP Iu Release Commannd

D-Result

A set of subcounters screened on: IU release cause before CC Connect Ack


• Sub-Counter #1 : SRB





E-Type

• VS.IuReleaseCmdBeforeCcConAck.VS.IuReleaseCmdBeforeCcConAck.Other



• VS.IuReleaseCmdBeforeCcConAck.VS.IuReleaseCmdBeforeCcConAck.Srb

• VS.IuReleaseCmdBeforeCcConAck.VS.IuReleaseCmdBeforeCcConAck.CsSpeech

• VS.IuReleaseCmdBeforeCcConAck.VS.IuReleaseCmdBeforeCcConAck.CsData64

• VS.IuReleaseCmdBeforeCcConAck.VS.IuReleaseCmdBeforeCcConAck.CsStrm144

• VS.IuReleaseCmdBeforeCcConAck.VS.IuReleaseCmdBeforeCcConAck.CsStrm576

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 136 VS.IuReleaseReqBeforeCcConAck - #567

A-Description

Number of RANAP Iu Release Request messages sent by RNC to the Iu before CC ConnectAck.

B-Collection

CUM

CUMulative

C-Condition (Event)

The sending of RANAP Iu Release Request by RNC to IU

D-Result

A set of subcounters screened on: IU release cause before CC Connect Ack


• Sub-Counter #1 : SRB







E-Type

• VS.IuReleaseReqBeforeCcConAck.VS.IuReleaseReqBeforeCcConAck.Other

• VS.IuReleaseReqBeforeCcConAck.VS.IuReleaseReqBeforeCcConAck.Srb

• VS.IuReleaseReqBeforeCcConAck.VS.IuReleaseReqBeforeCcConAck.CsSpeech

• VS.IuReleaseReqBeforeCcConAck.VS.IuReleaseReqBeforeCcConAck.CsData64

• VS.IuReleaseReqBeforeCcConAck.VS.IuReleaseReqBeforeCcConAck.CsStrm144

• VS.IuReleaseReqBeforeCcConAck.VS.IuReleaseReqBeforeCcConAck.CsStrm576

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 137 VS.IuRelocationCancels - #568

A-Description

the number of RANAP RELOCATION_ CANCEL messages sent by the source RNC on Iu

B-Collection

CUM

CUMulative

C-Condition (Event)



Emission of a RANAP RELOCATION_ CANCEL message by the source RNC on Iu

D-Result

A set of subcounters screened on: Per type of relocation and CN domain


• Sub-Counter #1 : 3G-3G PS


E-Type

• VS.IuRelocationCancels.VS.IuRelocationCancels.3Gto3GCs

• VS.IuRelocationCancels.VS.IuRelocationCancels.3Gto3GPs

• VS.IuRelocationCancels.VS.IuRelocationCancels.3Gto2GCs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 138 VS.IuRelocationCompletes - #569

A-Description

the number of RANAP RELOCATION_ COMPLETE messages sent by the target RNC on Iu

B-Collection

CUM

CUMulative

C-Condition (Event)



Emission of a RANAP RELOCATION_ COMPLETE message by the target RNC on Iu

D-Result





E-Type

• VS.IuRelocationCompletes.VS.IuRelocationCompletes.3Gto3GCs

• VS.IuRelocationCompletes.VS.IuRelocationCompletes.3Gto3GPs

• VS.IuRelocationCompletes.VS.IuRelocationCompletes.2Gto3GCs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 139 VS.IuRelocationDetects - #570

A-Description

the number of RANAP RELOCATION_ DETECT messages sent by the target RNC on Iu

B-Collection

CUM

CUMulative

C-Condition (Event)



Emission of a RANAP RELOCATION_ DETECT message by the target RNC on Iu

D-Result





E-Type

• VS.IuRelocationDetects.VS.IuRelocationDetects.3Gto3GCs

• VS.IuRelocationDetects.VS.IuRelocationDetects.3Gto3GPs

• VS.IuRelocationDetects.VS.IuRelocationDetects.2Gto3GCs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 140 VS.IuReleaseCompleteCs - #571

A-Description

Number of RANAP Iu Release Complete sent by RNC to CN on the Iu interface on CS domain.This counter (CS part) will be incremented, with the DlAsConf present, when the RANAP IURELEASE COMMAND from the CS domain is received. In normal call relaese scenarios whreRABs are released before the IU release, the SRB DlAsConf will be incremented. Note that inscenarios where a PS RAB is running with a signalling connection for CS (but thre is no CSTRB), the CS release procedure will increment this counter with a PS DlAsConf(Q01158696-01, Q01206156, Q01158560)

B-Collection



CUM

CUMulative

C-Condition (Event)

Sending of RANAP Iu Release Complete on CS domain

D-Result









E-Type

• VS.IuReleaseCompleteCs.VS.IuReleaseCompleteCs.DlAsCnfOther

• VS.IuReleaseCompleteCs.VS.IuReleaseCompleteCs.DlAsCnfSig

• VS.IuReleaseCompleteCs.VS.IuReleaseCompleteCs.DlAsCnfCsSpeech

• VS.IuReleaseCompleteCs.VS.IuReleaseCompleteCs.DlAsCnfCsData

• VS.IuReleaseCompleteCs.VS.IuReleaseCompleteCs.DlAsCnfCsStr57_6

• VS.IuReleaseCompleteCs.VS.IuReleaseCompleteCs.DlAsCnfCsStr14_4

• VS.IuReleaseCompleteCs.VS.IuReleaseCompleteCs.DlAsCnfCsSigPs

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V5.0

L-Aggregation Rule

Rtotal

Table 141 VS.IuAbnormalReleaseRequestCs - #572

A-Description

This measurement represents the number of Iu CS release requests due to abnormal condi-tions.

B-Collection

CUM

CUMulative

C-Condition (Event)

On RNC requests Iu CS release due to abnormal conditions : - O&M intervention - Repeatedintegrity check failure - Radio connection lost - Relocation timeout (corresponding to timeout ofTrelocoverallExpiry and TrelocCompleteExpiry) - Unspecified failure

D-Result









E-Type

• VS.IuAbnormalReleaseRequestCs.VS.IuAbnormalReleaseRequestCs.DlAsCnfOther

• VS.IuAbnormalReleaseRequestCs.VS.IuAbnormalReleaseRequestCs.DlAsCnfSig

• VS.IuAbnormalReleaseRequestCs.VS.IuAbnormalReleaseRequestCs.DlAsCnfCsSpeech

• VS.IuAbnormalReleaseRequestCs.VS.IuAbnormalReleaseRequestCs.DlAsCnfCsData

• VS.IuAbnormalReleaseRequestCs.VS.IuAbnormalReleaseRequestCs.DlAsCnfCsStr57_6

• VS.IuAbnormalReleaseRequestCs.VS.IuAbnormalReleaseRequestCs.DlAsCnfCsStr14_4

• VS.IuAbnormalReleaseRequestCs.VS.IuAbnormalReleaseRequestCs.DlAsCnfCsSigPs

F-Object Instance



Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 142 VS.IuAbnormalReleaseRequestPs - #573

A-Description

This measurement represents the number of Iu PS release requests due to abnormal condi-tions.

B-Collection

CUM

CUMulative

C-Condition (Event)

On RNC requests Iu PS release due to abnormal conditions : - O&M intervention - Repeatedintegrity check failure - Radio connection lost - Relocation timeout (corresponding to timeout ofTrelocoverallExpiry and TrelocCompleteExpiry) - Unspecified failure

D-Result

A set of subcounters screened on: Derived AsConf Screening for PS DlAsConfId , see also An-nex: T09
















• Sub-Counter #13 : PS Signalling + CS

E-Type

• VS.IuAbnormalReleaseRequestPs.VS.IuAbnormalReleaseRequestPs.DlAsCnfSig

• VS.IuAbnormalReleaseRequestPs.VS.IuAbnormalReleaseRequestPs.DlAsCnfPsStr16




• VS.IuAbnormalReleaseRequestPs.VS.IuAbnormalReleaseRequestPs.DlAsCnfTrbCellFach

• VS.IuAbnormalReleaseRequestPs.VS.IuAbnormalReleaseRequestPs.DlAsCnfPsIB8






• VS.IuAbnormalReleaseRequestPs.VS.IuAbnormalReleaseRequestPs.DlAsCnfHsdpa

• VS.IuAbnormalReleaseRequestPs.VS.IuAbnormalReleaseRequestPs.DlAsCnfPsSigCs

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event



K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 143 VS.IubcSabpMsg - #574

A-Description

Number of Incoming and outgoing SABP messages over the IuBC interface (Interface betweenRNC and the CBC for the Cell Broadcast Service feature)

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception or Sending of a SABP message over the IuBC interface

D-Result

A set of subcounters screened on: SABP message reason

• Sub-Counter #0 : Write-replace

• Sub-Counter #1 : Write-replace complete

• Sub-Counter #2 : Kill

• Sub-Counter #3 : Kill complete

• Sub-Counter #4 : Reset

• Sub-Counter #5 : Reset complete

• Sub-Counter #6 : Load query

• Sub-Counter #7 : Load query complete

• Sub-Counter #8 : Message status query

• Sub-Counter #9 : Message status query complete

• Sub-Counter #10 : Restart

• Sub-Counter #11 : Failure or Error Indication

E-Type

• VS.IubcSabpMsg.VS.IubcSabpMsg.WrtRplc

• VS.IubcSabpMsg.VS.IubcSabpMsg.WrtRplcCmplt

• VS.IubcSabpMsg.VS.IubcSabpMsg.Kill

• VS.IubcSabpMsg.VS.IubcSabpMsg.KillCmplt

• VS.IubcSabpMsg.VS.IubcSabpMsg.Reset



• VS.IubcSabpMsg.VS.IubcSabpMsg.ResetCmplt

• VS.IubcSabpMsg.VS.IubcSabpMsg.LoadQry

• VS.IubcSabpMsg.VS.IubcSabpMsg.LoadQryCmplt

• VS.IubcSabpMsg.VS.IubcSabpMsg.MsgStsQry

• VS.IubcSabpMsg.VS.IubcSabpMsg.MsgStsQryCmplt

• VS.IubcSabpMsg.VS.IubcSabpMsg.Restart

• VS.IubcSabpMsg.VS.IubcSabpMsg.FailErrInd

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 144 VS.IubcSabpWrtRplcFail - #575

A-Description

Each time a SABP WRITE-REPLACE Failure message is sent to CBC, the number of failedSAI (FddCell) is incremented per cause of failure.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a WRITE-REPLACE Failure SABP message over the IuBC interface

D-Result

A set of subcounters screened on: SABP write-replace failure reason



• Sub-Counter #0 : Valid CN message not identified

• Sub-Counter #1 : Service Area identity not valid

• Sub-Counter #2 : RNC capacity or memory exceeded

• Sub-Counter #3 : Service Area broadcast not supported

• Sub-Counter #4 : Service Area broadcast not operational

• Sub-Counter #5 : Message reference already used

• Sub-Counter #6 : Message not compatible with receiver state

• Sub-Counter #7 : Invalid parameter or decoding Error

E-Type

• VS.IubcSabpWrtRplcFail.VS.IubcSabpWrtRplcFail.VldCnMsgNotId

• VS.IubcSabpWrtRplcFail.VS.IubcSabpWrtRplcFail.SrvcArIdNotVld

• VS.IubcSabpWrtRplcFail.VS.IubcSabpWrtRplcFail.RncCapMemXcd

• VS.IubcSabpWrtRplcFail.VS.IubcSabpWrtRplcFail.SrvcArBcNotSup

• VS.IubcSabpWrtRplcFail.VS.IubcSabpWrtRplcFail.SrvcArBcNotOpr

• VS.IubcSabpWrtRplcFail.VS.IubcSabpWrtRplcFail.MsgRfAlrdyUsd

• VS.IubcSabpWrtRplcFail.VS.IubcSabpWrtRplcFail.MsgNotCmptRcvrSt

• VS.IubcSabpWrtRplcFail.VS.IubcSabpWrtRplcFail.InvldParmDcdErr

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 145 VS.IuReleaseReqCs - #576



A-Description

Number of RANAP/IU_RELEASE_REQUEST sent by RNC to CoreNetwork CS

B-Collection

CUM

CUMulative

C-Condition (Event)

At sending of IU_RELEASE_REQUEST to CS domain

D-Result

A set of subcounters screened on: Reason to send Release Request CS Cause



• Sub-Counter #2 : Repeated Integrity Check Failure

• Sub-Counter #3 : UE generated signalling cnx release

• Sub-Counter #4 : Radio cnx with UE lost

• Sub-Counter #5 : Abnormal condition with cause TRelocOveral expiry

• Sub-Counter #6 : Other causes

• Sub-Counter #7 : DL RLC error on SRB

• Sub-Counter #8 : UL RLC error on SRB

• Sub-Counter #9 : T360 Expiry

E-Type

• VS.IuReleaseReqCs.VS.IuReleaseReqCs.OamIntervention

• VS.IuReleaseReqCs.VS.IuReleaseReqCs.UnspecifiedFailure

• VS.IuReleaseReqCs.VS.IuReleaseReqCs.RepeatedIntegrityCheckFailure

• VS.IuReleaseReqCs.VS.IuReleaseReqCs.UeGeneratedSignallingConnectionRelease

• VS.IuReleaseReqCs.VS.IuReleaseReqCs.RadioConnectionWithUeLost

• VS.IuReleaseReqCs.VS.IuReleaseReqCs.AbnormalConditionTimerRelocExpiry

• VS.IuReleaseReqCs.VS.IuReleaseReqCs.OtherCause

• VS.IuReleaseReqCs.VS.IuReleaseReqCs.DlRLCErrSRB

• VS.IuReleaseReqCs.VS.IuReleaseReqCs.UlRLCErrSRB

• VS.IuReleaseReqCs.VS.IuReleaseReqCs.T360Expiry

F-Object Instance

Cell(Reference)

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 146 VS.IuReleaseReqPs - #577

A-Description

Number of RANAP/IU_RELEASE_REQUEST sent by RNC to CoreNetwork PS

B-Collection

CUM

CUMulative

C-Condition (Event)

At sending of IU_RELEASE_REQUEST to PS domain

D-Result

A set of subcounters screened on: Release Request Cause PS


• Sub-Counter #1 : IU User Plane Failure










• Sub-Counter #11 : DL RLC error on TRB



• Sub-Counter #12 : UL RLC error on TRB


E-Type

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.UserInactivity

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.IuUserPlaneFailure

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.OamIntervention

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.UnspecifiedFailure

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.RepeatedIntegrityCheckFailure

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.UeGeneratedSignallingConnectionRelease

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.RadioCnxUeLost

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.AbnormalConditionTimerRelocExpiry

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.OtherCause

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.DlRLCErrSRB

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.UlRLCErrSRB

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.DlRLCErrTRB

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.UlRLCErrTRB

• VS.IuReleaseReqPs.VS.IuReleaseReqPs.T360Expiry

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 147 VS.IuAvgNbrSccpCnxCs - #578



A-Description

Average number of sccp connections on Iu CS interface

B-Collection

LOAD

C-Condition (Event)

Iu sccp connection establishments and take downs on Iu CS interface

D-Result

A set of subcounters screened on: CsCoreNetworkAccess RdnId

• Sub-Counter #0 : RdnId 0
















E-Type

• VS.IuAvgNbrSccpCnxCs.VS.IuAvgNbrSccpCnxCs.RdnId0


















F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 148 VS.IuAvgNbrSccpCnxPs - #579

A-Description

Average number of sccp connections on Iu PS interface

B-Collection

LOAD

C-Condition (Event)

Iu sccp connection establishments and take downs on Iu PS interface

D-Result

A set of subcounters screened on: PsCoreNetworkAccess RdnId



















E-Type

• VS.IuAvgNbrSccpCnxPs.VS.IuAvgNbrSccpCnxPs.RdnId0
















F-Object Instance

RNC

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 149 VS.IuReleaseRequestCsNrnc - #580

A-Description

Number of RANAP/IU_RELEASE_REQUEST messages sent by RNC to CS Core Networkwhen the reference cell is located on a Drift RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of IU_RELEASE_REQUEST to CS domain

D-Result

A set of subcounters screened on: Reason to send Release Request CS Cause













E-Type

• VS.IuReleaseRequestCsNrnc.VS.IuReleaseRequestCsNrnc.OamIntervention

• VS.IuReleaseRequestCsNrnc.VS.IuReleaseRequestCsNrnc.UnspecifiedFailure

• VS.IuReleaseRequestCsNrnc.VS.IuReleaseRequestCsNrnc.RepeatedIntegrityCheckFailure

• VS.IuReleaseRequestCsNrnc.VS.IuReleaseRequestCsNrnc.UeGeneratedSignallingConnectionRelease

• VS.IuReleaseRequestCsNrnc.VS.IuReleaseRequestCsNrnc.RadioConnectionWithUeLost

• VS.IuReleaseRequestCsNrnc.VS.IuReleaseRequestCsNrnc.AbnormalConditionTimerRelocExpiry

• VS.IuReleaseRequestCsNrnc.VS.IuReleaseRequestCsNrnc.OtherCause

• VS.IuReleaseRequestCsNrnc.VS.IuReleaseRequestCsNrnc.DlRLCErrSRB

• VS.IuReleaseRequestCsNrnc.VS.IuReleaseRequestCsNrnc.UlRLCErrSRB

• VS.IuReleaseRequestCsNrnc.VS.IuReleaseRequestCsNrnc.T360Expiry

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 150 VS.IuReleaseRequestPsNrnc - #581

A-Description

Number of RANAP/IU_RELEASE_REQUEST messages sent by RNC to PS Core Networkwhen the reference cell is located on a Drift RNC.

B-Collection



CUM

CUMulative

C-Condition (Event)

Sending of IU_RELEASE_REQUEST to PS domain

D-Result

A set of subcounters screened on: Release Request Cause PS


• Sub-Counter #1 : IU User Plane Failure










• Sub-Counter #11 : DL RLC error on TRB

• Sub-Counter #12 : UL RLC error on TRB


E-Type

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.UserInactivity

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.IuUserPlaneFailure

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.OamIntervention

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.UnspecifiedFailure

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.RepeatedIntegrityCheckFailure

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.UeGeneratedSignallingConnectionRelease

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.RadioCnxUeLost

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.AbnormalConditionTimerRelocExpiry

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.OtherCause

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.DlRLCErrSRB

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.UlRLCErrSRB



• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.DlRLCErrTRB

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.UlRLCErrTRB

• VS.IuReleaseRequestPsNrnc.VS.IuReleaseRequestPsNrnc.T360Expiry

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.7 RAB and RB Management

The reference document for RAB management is 3GPP TS25.413 Iu Interface RANAP Signaling.


Counter name

#602 VS.RadioBearerSetupUnsuccess

#609 VS.RadioBearerReleaseUnsuccess

#611 VS.RadioBearerSetupUnsuccessNeighbRnc

#612 VS.RadioBearerEstablishmentUnsuccessNeighbRnc

#614 VS.RadioBearerReleaseUnsuccessNeighbRnc

#616 VS.RadioBearerReconfigurationUnsuccess

#618 VS.RadioBearerReconfigurationUnsuccessNeighbRnc

#631 VS.RadioBearerEstablishmentUnsuccess

#635 VS.RabAssignmentRequestUeCapabilitiesCheckFailure

#636 VS.RabAssignmentRequestUeCapabilitiesCheckAccept

#638 VS.RabrReconfiCompl3Gto3GReloc

#639 VS.CallEstablishmentDuration

#640 VS.UEDlRBRateAdapActiv

#641 VS.UEDlRBRateAdapDeactiv

#642 VS.UEUlRBRateAdapActiv

#643 VS.UEUlRBRateAdapDeactiv

#644 VS.UEDlRBRateAdapDownReq

#645 VS.UEDlRBRateAdapUpReq

#646 VS.UEDlRBRateAdapDownSucc

#647 VS.UEDlRBRateAdapUpSucc

#648 VS.UEUlRBRateAdapDownReq

#649 VS.UEUlRBRateAdapUpReq

#650 VS.UEUlRBRateAdapDownSucc

#651 VS.UEUlRBRateAdapUpSucc

#652 VS.UERBRateAdapDownReqCell

#653 VS.UERBRateAdapUpReqCell

#654 VS.UERBRateAdapDownSuccCell

#655 VS.UERBRateAdapUpSuccCell

#656 VS.UERBRateAdapDownReqNeighbCell

#657 VS.UERBRateAdapUpReqNeighbCell




Counter name

#658 VS.UERBRateAdapDownSuccNeighbCell

#659 VS.UERBRateAdapUpSuccNeighbCell

#666 VS.RabModifReq

#667 VS.RabModifSucc

#668 VS.CallAttemptsUeCat

#669 VS.RbEstabUnsucPerDlRbType

#670 VS.RadioBearerReconfigFailure

#671 VS.RabEstablishmentRequestsPerRabType

#672 VS.RabEstablishmentSuccessPerRequestedRabType

#673 VS.RabEstablishmentSuccessPerGrantedRabType

#674 VS.RabReleaseRequest

#675 VS.NumberOfRabEstablished

#676 VS.RabNormalRelease

#677 VS.RabAssignmentSetupUnsuccess

#678 VS.RabAssignmentReleaseSuccess

#679 VS.RabAssignmentReleaseUnsuccess

#680 VS.RabOutgoingRefCell

#681 VS.RabIncomingRefCell

#682 VS.RabEstabSuccPerReqRabTypRefCell

#683 VS.RabAbnormRelPerReqRabTypRefCel

#684 VS.RadioBearerReconfigurationSuccess

#685 VS.RadioBearerReconfigureRequest

#686 VS.RadioBearerReconfigurationSuccessNeighbRnc

#687 VS.RadioBearerSetupSuccess

#688 VS.RadioBearerReleaseSuccess

#689 VS.RadioBearerSetupSuccessNeighbRnc

#690 VS.RadioBearerReleaseSuccessNeighbRnc

#691 VS.RadioBearerSetupRequest

#692 VS.DlAsConfIdAvgNbrEstablished

#693 VS.UlAsConfIdAvgNbrEstablished

#694 VS.SucEdchToDchTrans

#695 VS.UnsucEdchToDchTrans

#696 VS.SucDchToEdchTrans

#697 VS.UnsucDchToEdchTrans

#1601 VS.SucHspaToDchFallbackCell

#1602 VS.SucHspaToDchFallbackNrnc




Counter name

#1603 VS.UnsucHspaToDchFallbackCell

#1604 VS.UnsucHspaToDchFallbackNrnc

Table 151 VS.RadioBearerSetupUnsuccess - #602

A-Description

the number of RB establishment procedures failures, screened by establishment failure cause,for each cell controlled by the RNC which is the primary cell. During such a procedure, themeasurement attached to a given cell is incremented if the cell is in the primary cell of the act-ive set of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

The measurement counts the number of RB establishment attempts which have evolved intothe emission by the RNC of a RRC RADIO BEARER SETUP message but for which no sub-sequent RADIO BEARER SETUP COMPLETE message has been received. The measure-ment is only incremented when the UE's primary cell is under the control of its SRNC.

D-Result

A set of subcounters screened on: Internal screening criteria


• Sub-Counter #1 : RADIO_BEARER_SETUP_FAILURE

E-Type

• VS.RadioBearerSetupUnsuccess.VS.RadioBearerSetupUnsuccess.Timeout

• VS.RadioBearerSetupUnsuccess.VS.RadioBearerSetupUnsuccess.RadioBearerSetupFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

event

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 152 VS.RadioBearerReleaseUnsuccess - #609

A-Description

the number of RB release failures screened by release failure cause, for each cell controlled bythe RNC which is the primary cell. During such a procedure, the measurement attached to agiven cell is incremented if the cell is the primary cell of the active set of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

The measurement counts the number of emissions by the RNC of a RRC RADIO BEARERRELEASE message for which any subsequent RADIO BEARER RELEASE COMPLETE mes-sage has been received. The measurement is only incremented when the UE's primary cell isunder the control of its SRNC.

D-Result



• Sub-Counter #1 : RADIO_BEARER_RELEASE_FAILURE

E-Type

• VS.RadioBearerReleaseUnsuccess.VS.RadioBearerReleaseUnsuccess.Timeout

• VS.RadioBearerReleaseUnsuccess.VS.RadioBearerReleaseUnsuccess.RadioBearerReleaseFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 153 VS.RadioBearerSetupUnsuccessNeighbRnc - #611

A-Description

the number of RB establishment failures, screened by establishment failure cause, for eachneighboring RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

RB establishment attempt - which has evolved into the emission by the RNC of a RRC RADIOBEARER SETUP message - for which no subsequent RADIO BEARER SETUP COMPLETEmessage has been received The event is only considered when the UE has its reference cellunder the control of a DRNS.

D-Result

A set of subcounters screened on: Internal to RNC cause of unsuccess


• Sub-Counter #1 : RADIO_BEARER_SETUP_FAILURE

E-Type

• VS.RadioBearerSetupUnsuccessNeighbRnc.VS.RadioBearerSetupUnsuccessNeighbRnc.Timeout

• VS.RadioBearerSetupUnsuccessNeighbRnc.VS.RadioBearerSetupUnsuccessNeighbRnc.RadioBearerSetupFailure

F-Object Instance

Neighbouring RNC

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 154 VS.RadioBearerEstablishmentUnsuccessNeighbRnc - #612

A-Description

the number of RB establishment refusals before any sending of RRC RADIO BEARERSETUP, screened by establishment refusal cause, for each neighboring RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

RB establishment attempt which has not evolved into the sending of a RADIO BEARERSETUP message. A RB establishment attempt is considered when the RNC takes into accounta need to establish a RB. If the RNC considers the need can not be satisfied, it refuses the RBestablishment and does not send any RADIO BEARER SETUP message. The event is onlyconsidered when the UE has its reference cell under the control of a DRNS.

D-Result

A set of subcounters screened on: Internal to RNC cause of unsuccess

• Sub-Counter #0 : invalid RAB parameters value

• Sub-Counter #1 : problem radio resource


E-Type

• VS.RadioBearerEstablishmentUnsuccessNeighbRnc.VS.RadioBearerEstablishmentUnsuccessNeighbRnc.InvalidRabParametersValue

• VS.RadioBearerEstablishmentUnsuccessNeighbRnc.VS.RadioBearerEstablishmentUnsuccessNeighbRnc.ProblemRadioResource

• VS.RadioBearerEstablishmentUnsuccessNeighbRnc.VS.RadioBearerEstablishmentUnsuc



cessNeighbRnc.Unspecified

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 155 VS.RadioBearerReleaseUnsuccessNeighbRnc - #614

A-Description

the number of RB release failures screened by release failure cause, for each neighboringRNC. During such a procedure, the measurement attached to a given neighboring RNC is in-cremented as many times as there are cells in the active set which are controlled by this neigh-boring RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RRC RADIO BEARER RELEASE message for which any sub-sequent RADIO BEARER RELEASE COMPLETE message has been received. The event isonly considered when the UE has one or several cells in its active set which are outside thecontrol of its SRNC. The counter is incremented as many times as there are cells of the activeset on this neighboring RNC.

D-Result





• Sub-Counter #1 : RADIO_BEARER_RELEASE_FAILURE

E-Type

• VS.RadioBearerReleaseUnsuccessNeighbRnc.VS.RadioBearerReleaseUnsuccessNeighbRnc.Timeout

• VS.RadioBearerReleaseUnsuccessNeighbRnc.VS.RadioBearerReleaseUnsuccessNeighbRnc.RadioBearerReleaseFailure

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 156 VS.RadioBearerReconfigurationUnsuccess - #616

A-Description

the number of RB reconfiguration failures screened by release failure cause, for each cell con-trolled by the RNC which is the primary cell. During such a procedure, the measurement at-tached to a given cell is incremented if the cell is the reference cell of the active set of the in-volved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Failure or time-out after RB set-up, addition or reconfiguration which entails the last Radio-bearer of a call releasing. The measurement is only incremented when the UE's primary cell isunder the control of its SRNC.

D-Result





• Sub-Counter #1 : RADIO_BEARER_RECONFIGURATION_FAILURE

E-Type

• VS.RadioBearerReconfigurationUnsuccess.VS.RadioBearerReconfigurationUnsuccess.Timeout

• VS.RadioBearerReconfigurationUnsuccess.VS.RadioBearerReconfigurationUnsuccess.RadioBearerReconfigurationFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 157 VS.RadioBearerReconfigurationUnsuccessNeighbRnc - #618

A-Description

the number of RB reconfiguration failures screened by release failure cause, for each neigh-boring RNC. During such a procedure, the measurement attached to a given neighboring RNCis incremented as many times as there are cells in the active set which are controlled by thisneighboring RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RRC RADIO BEARER RECONFIGURATION message for which



any subsequent RADIO BEARER RECONFIGURATION COMPLETE message has been re-ceived. The event is only considered when the UE has one or several cells in its active setwhich are outside the control of its SRNC. The counter is incremented as many times as thereare cells of the active set on this neighboring RNC.

D-Result



• Sub-Counter #1 : RADIO_BEARER_RECONFIGURATION_FAILURE

E-Type

• VS.RadioBearerReconfigurationUnsuccessNeighbRnc.VS.RadioBearerReconfigurationUnsuccessNeighbRnc.Timeout

• VS.RadioBearerReconfigurationUnsuccessNeighbRnc.VS.RadioBearerReconfigurationUnsuccessNeighbRnc.RadioBearerReconfigurationFailure

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 158 VS.RadioBearerEstablishmentUnsuccess - #631

A-Description

the number of Radio-Bearer establishments that have been rejected by the RNC (no RB SetupRequest sent).

B-Collection

CUM



CUMulative

C-Condition (Event)

Any event that prevents to setup the RB successfully before to sent the RA-DIO_BEARER_SETUP_REQUEST.

D-Result


• Sub-Counter #0 : invalid RAB parameters value

• Sub-Counter #1 : unavailable dl code ressources

• Sub-Counter #2 : unavailable dl power ressources




• Sub-Counter #6 : CAC RNC Processing resources

• Sub-Counter #7 : Unavailable DL NodeB processing resources or NodeB processing re-sources if global capacity is used

• Sub-Counter #8 : Unavailable UL NodeB processing resources

• Sub-Counter #9 : Lack of CID on the Iu

• Sub-Counter #10 : Lack of bandwidth on the Iu

• Sub-Counter #11 : Lack of CID on the Iur

• Sub-Counter #12 : Lack of bandwidth on the Iur



E-Type

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.InvalidRabParametersValue

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.UnavailableDlCodeResources

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.UnavailableDlPowerResources

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.Unspecified

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.4Unused

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.5Unused

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.LackOfRncProcessingResources



• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBDlProcessingResources

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.LackOfNodeBUlProcessingResources

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.LackCidIu

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.LackBwthIu

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.LackCidIur

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.LackBwthIur

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.LackCidIub

• VS.RadioBearerEstablishmentUnsuccess.VS.RadioBearerEstablishmentUnsuccess.LackBwthIub

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 159 VS.RabAssignmentRequestUeCapabilitiesCheckFailure - #635

A-Description

This measurements provides the number of times a RANAP RAB Assignment Request (RabSetUp/Addition/Modify) was rejected due to the UE Radio Access Capabilities Check (UE isnot able to handle the RAB).

B-Collection



CUM

CUMulative

C-Condition (Event)

Failure of a Rab Assignement Request due to a reject caused by the check of the UE RadioAccess Capabilities.

D-Result

one measurement

E-Type

VS.RabAssignmentRequestUeCapabilitiesCheckFailure

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 160 VS.RabAssignmentRequestUeCapabilitiesCheckAccept - #636

A-Description

the number of times a RANAP RAB Assignment Request (RAB Setup/Addition/Modify) was ac-cepted but the RAB bitrate has to be downgraded because of the UE Radio Capabilities.

B-Collection

CUM

CUMulative

C-Condition (Event)

Success of a Rab Assignement Request but with a downgrade due to the check of the UE Ra-



dio Access Capabilities

D-Result

A set of subcounters screened on: Type of Downgrade

• Sub-Counter #0 : DL downgrade

• Sub-Counter #1 : UL downgrade

• Sub-Counter #2 : UL and DL downgrade

E-Type

• VS.RabAssignmentRequestUeCapabilitiesCheckAccept.VS.RabAssignmentRequestUeCapabilitiesCheckAccept.DlDowngraded

• VS.RabAssignmentRequestUeCapabilitiesCheckAccept.VS.RabAssignmentRequestUeCapabilitiesCheckAccept.UlDowngraded

• VS.RabAssignmentRequestUeCapabilitiesCheckAccept.VS.RabAssignmentRequestUeCapabilitiesCheckAccept.DlAndUlDowngraded

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 161 VS.RabrReconfiCompl3Gto3GReloc - #638

A-Description

Number of RRC/Radio Bearer Reconfiguration complete received for 3G->3G relocation pur-pose

B-Collection

CUM



CUMulative

C-Condition (Event)

On the receipt of a Radio Bearer Reconfiguration complete for 3G->3G relocation purpose.

D-Result

A set of subcounters screened on: Per type of relocation and CN Domain



• Sub-Counter #2 : 3G-3G CS+PS

E-Type

• VS.RabrReconfiCompl3Gto3GReloc.VS.RabrReconfiCompl3Gto3GReloc.Cs

• VS.RabrReconfiCompl3Gto3GReloc.VS.RabrReconfiCompl3Gto3GReloc.Ps

• VS.RabrReconfiCompl3Gto3GReloc.VS.RabrReconfiCompl3Gto3GReloc.CsPs

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 162 VS.CallEstablishmentDuration - #639

A-Description

Duration of the successful call establishment

B-Collection

VAL



VALue counter

C-Condition (Event)

Time elapsed between the receipt of the first RRC Connection Request and the first successfulRAB Assignment Response sent.

D-Result

A set of subcounters screened on: Traffic class

• Sub-Counter #0 : conversational

• Sub-Counter #1 : streaming

• Sub-Counter #2 : interactive

• Sub-Counter #3 : background

E-Type

• VS.CallEstablishmentDuration.VS.CallEstablishmentDuration.Conversational

• VS.CallEstablishmentDuration.VS.CallEstablishmentDuration.Streaming

• VS.CallEstablishmentDuration.VS.CallEstablishmentDuration.Interactive

• VS.CallEstablishmentDuration.VS.CallEstablishmentDuration.Background

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rval

Table 163 VS.UEDlRBRateAdapActiv - #640

A-Description

Number of activation/modification of the traffic monitoring



B-Collection

CUM

CUMulative

C-Condition (Event)

Successful RRM order of RB eligible to RB rate adaptation.

D-Result

A set of subcounters screened on: DlRbSetId derived screening

• Sub-Counter #0 : Other Dl

• Sub-Counter #1 : Dl PS Rb 32kbps





E-Type

• VS.UEDlRBRateAdapActiv.VS.UEDlRBRateAdapActiv.PsRBOtherD

• VS.UEDlRBRateAdapActiv.VS.UEDlRBRateAdapActiv.PsRB32D





F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule



Rtotal

Table 164 VS.UEDlRBRateAdapDeactiv - #641

A-Description

Number of deactivation of the traffic monitoring

B-Collection

CUM

CUMulative

C-Condition (Event)

Loss of eligibility of the RB to RB rate adaptation.

D-Result








E-Type

• VS.UEDlRBRateAdapDeactiv.VS.UEDlRBRateAdapDeactiv.PsRBOtherD

• VS.UEDlRBRateAdapDeactiv.VS.UEDlRBRateAdapDeactiv.PsRB32D





F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 165 VS.UEUlRBRateAdapActiv - #642

A-Description

Number of activation/modification of the traffic monitoring

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful RRM order of RB eligible to RB rate adaptation.

D-Result

A set of subcounters screened on: UlRbSetId derived screening

• Sub-Counter #0 : Other Ul

• Sub-Counter #1 : Ul PS Rb 32kbps




E-Type

• VS.UEUlRBRateAdapActiv.VS.UEUlRBRateAdapActiv.PsRBOtherU

• VS.UEUlRBRateAdapActiv.VS.UEUlRBRateAdapActiv.PsRB32U




F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 166 VS.UEUlRBRateAdapDeactiv - #643

A-Description

Number of deactivation of the traffic monitoring

B-Collection

CUM

CUMulative

C-Condition (Event)

Loss of eligibility of the RB to RB rate adaptation.

D-Result







E-Type

• VS.UEUlRBRateAdapDeactiv.VS.UEUlRBRateAdapDeactiv.PsRBOtherU

• VS.UEUlRBRateAdapDeactiv.VS.UEUlRBRateAdapDeactiv.PsRB32U




F-Object Instance

RNC



G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 167 VS.UEDlRBRateAdapDownReq - #644

A-Description

Number of RB rate downsize triggered by the traffic monitoring.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result








E-Type

• VS.UEDlRBRateAdapDownReq.VS.UEDlRBRateAdapDownReq.PsRBOtherD

• VS.UEDlRBRateAdapDownReq.VS.UEDlRBRateAdapDownReq.PsRB32D







F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 168 VS.UEDlRBRateAdapUpReq - #645

A-Description

Number of RB rate upsize triggered by the traffic monitoring.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result










E-Type

• VS.UEDlRBRateAdapUpReq.VS.UEDlRBRateAdapUpReq.PsRBOtherD

• VS.UEDlRBRateAdapUpReq.VS.UEDlRBRateAdapUpReq.PsRB32D





F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 169 VS.UEDlRBRateAdapDownSucc - #646

A-Description

Number of successful SRLR resulting from the RB rate downsize

B-Collection

CUM

CUMulative

C-Condition (Event)

The SRLR triggered by the traffic monitoring is successfully completed.

D-Result










E-Type

• VS.UEDlRBRateAdapDownSucc.VS.UEDlRBRateAdapDownSucc.PsRBOtherD

• VS.UEDlRBRateAdapDownSucc.VS.UEDlRBRateAdapDownSucc.PsRB32D





F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 170 VS.UEDlRBRateAdapUpSucc - #647

A-Description

Number of successful SRLR resulting from the RB rate upsize

B-Collection



CUM

CUMulative

C-Condition (Event)


D-Result








E-Type

• VS.UEDlRBRateAdapUpSucc.VS.UEDlRBRateAdapUpSucc.PsRBOtherD

• VS.UEDlRBRateAdapUpSucc.VS.UEDlRBRateAdapUpSucc.PsRB32D





F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal



Table 171 VS.UEUlRBRateAdapDownReq - #648

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result







E-Type

• VS.UEUlRBRateAdapDownReq.VS.UEUlRBRateAdapDownReq.PsRBOtherU

• VS.UEUlRBRateAdapDownReq.VS.UEUlRBRateAdapDownReq.PsRB32U




F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V4.2

L-Aggregation Rule

Rtotal

Table 172 VS.UEUlRBRateAdapUpReq - #649

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result







E-Type

• VS.UEUlRBRateAdapUpReq.VS.UEUlRBRateAdapUpReq.PsRBOtherU

• VS.UEUlRBRateAdapUpReq.VS.UEUlRBRateAdapUpReq.PsRB32U




F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 173 VS.UEUlRBRateAdapDownSucc - #650

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result







E-Type

• VS.UEUlRBRateAdapDownSucc.VS.UEUlRBRateAdapDownSucc.PsRBOtherU

• VS.UEUlRBRateAdapDownSucc.VS.UEUlRBRateAdapDownSucc.PsRB32U




F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 174 VS.UEUlRBRateAdapUpSucc - #651

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result







E-Type

• VS.UEUlRBRateAdapUpSucc.VS.UEUlRBRateAdapUpSucc.PsRBOtherU

• VS.UEUlRBRateAdapUpSucc.VS.UEUlRBRateAdapUpSucc.PsRB32U




F-Object Instance

RNC



G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 175 VS.UERBRateAdapDownReqCell - #652

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: Downlink or Uplink

• Sub-Counter #0 : DOWNLINK

• Sub-Counter #1 : UPLINK

E-Type

• VS.UERBRateAdapDownReqCell.VS.UERBRateAdapDownReqCell.Downlink

• VS.UERBRateAdapDownReqCell.VS.UERBRateAdapDownReqCell.Uplink

F-Object Instance

Cell(Reference)

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 176 VS.UERBRateAdapUpReqCell - #653

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




E-Type

• VS.UERBRateAdapUpReqCell.VS.UERBRateAdapUpReqCell.Downlink

• VS.UERBRateAdapUpReqCell.VS.UERBRateAdapUpReqCell.Uplink

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 177 VS.UERBRateAdapDownSuccCell - #654

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




E-Type

• VS.UERBRateAdapDownSuccCell.VS.UERBRateAdapDownSuccCell.Downlink

• VS.UERBRateAdapDownSuccCell.VS.UERBRateAdapDownSuccCell.Uplink

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 178 VS.UERBRateAdapUpSuccCell - #655

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




E-Type

• VS.UERBRateAdapUpSuccCell.VS.UERBRateAdapUpSuccCell.Downlink

• VS.UERBRateAdapUpSuccCell.VS.UERBRateAdapUpSuccCell.Uplink

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V4.2

L-Aggregation Rule

Rtotal

Table 179 VS.UERBRateAdapDownReqNeighbCell - #656

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




E-Type

• VS.UERBRateAdapDownReqNeighbCell.VS.UERBRateAdapDownReqNeighbCell.Downlink

• VS.UERBRateAdapDownReqNeighbCell.VS.UERBRateAdapDownReqNeighbCell.Uplink

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule



Rtotal

Table 180 VS.UERBRateAdapUpReqNeighbCell - #657

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




E-Type

• VS.UERBRateAdapUpReqNeighbCell.VS.UERBRateAdapUpReqNeighbCell.Downlink

• VS.UERBRateAdapUpReqNeighbCell.VS.UERBRateAdapUpReqNeighbCell.Uplink

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal



Table 181 VS.UERBRateAdapDownSuccNeighbCell - #658

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




E-Type

• VS.UERBRateAdapDownSuccNeighbCell.VS.UERBRateAdapDownSuccNeighbCell.Downlink

• VS.UERBRateAdapDownSuccNeighbCell.VS.UERBRateAdapDownSuccNeighbCell.Uplink

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 182 VS.UERBRateAdapUpSuccNeighbCell - #659

A-Description




B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




E-Type

• VS.UERBRateAdapUpSuccNeighbCell.VS.UERBRateAdapUpSuccNeighbCell.Downlink

• VS.UERBRateAdapUpSuccNeighbCell.VS.UERBRateAdapUpSuccNeighbCell.Uplink

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 183 VS.RabModifReq - #666

A-Description

Number of RAB modification requested

B-Collection

CUM



CUMulative

C-Condition (Event)

RANAP/RAB assignment request message

D-Result

A set of subcounters screened on: RAB modification target type

• Sub-Counter #0 : New Traffic Class (TC) requested

• Sub-Counter #1 : New Maximum Bit Rate (MBR) requested

• Sub-Counter #2 : New Guaranteed Bit Rate (GBR) requested

• Sub-Counter #3 : Allocation/Retention Priority (ARP) requested

E-Type

• VS.RabModifReq.VS.RabModifReq.TC

• VS.RabModifReq.VS.RabModifReq.MBR

• VS.RabModifReq.VS.RabModifReq.GBR

• VS.RabModifReq.VS.RabModifReq.ARP

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 184 VS.RabModifSucc - #667

A-Description

Number of successful RAB modification

B-Collection



CUM

CUMulative

C-Condition (Event)

RANAP/RAB Assignment response message

D-Result

A set of subcounters screened on: RAB modification target type

• Sub-Counter #0 : New Traffic Class (TC) requested

• Sub-Counter #1 : New Maximum Bit Rate (MBR) requested

• Sub-Counter #2 : New Guaranteed Bit Rate (GBR) requested

• Sub-Counter #3 : Allocation/Retention Priority (ARP) requested

E-Type

• VS.RabModifSucc.VS.RabModifSucc.TC

• VS.RabModifSucc.VS.RabModifSucc.MBR

• VS.RabModifSucc.VS.RabModifSucc.GBR

• VS.RabModifSucc.VS.RabModifSucc.ARP

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 185 VS.CallAttemptsUeCat - #668

A-Description

The number of call attempts, with each UE category number (#1~12), per cell



B-Collection

CUM

CUMulative

C-Condition (Event)

The receipt of RRC-Connect-Complete message from UE

D-Result

A set of subcounters screened on: UE Category

• Sub-Counter #0 : UE Category 1












E-Type

• VS.CallAttemptsUeCat.VS.CallAttemptsUeCat.UeCategory1












F-Object Instance

RNC



G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 186 VS.RbEstabUnsucPerDlRbType - #669

A-Description

Number of Radio Bearer setups not successfully established, with no RA-DIO_BEARER_SETUP_REQUEST sent (based on procedure count, not RBs).

B-Collection

CUM

CUMulative

C-Condition (Event)

Any event that prevents the successful setup of the RB before sending the RA-DIO_BEARER_SETUP_REQUEST.

D-Result

A set of subcounters screened on: Target Type of call setup mapping , see also Annex: T14

• Sub-Counter #0 : Other combinations


• Sub-Counter #2 : CS Data















E-Type

• VS.RbEstabUnsucPerDlRbType.VS.RbEstabUnsucPerDlRbType.TgtCallOther

• VS.RbEstabUnsucPerDlRbType.VS.RbEstabUnsucPerDlRbType.TgtCallCsSpeech

• VS.RbEstabUnsucPerDlRbType.VS.RbEstabUnsucPerDlRbType.TgtCallCsData

• VS.RbEstabUnsucPerDlRbType.VS.RbEstabUnsucPerDlRbType.TgtCallCsStr

• VS.RbEstabUnsucPerDlRbType.VS.RbEstabUnsucPerDlRbType.TgtCallPsStr16




• VS.RbEstabUnsucPerDlRbType.VS.RbEstabUnsucPerDlRbType.TgtCallPsIb8






• VS.RbEstabUnsucPerDlRbType.VS.RbEstabUnsucPerDlRbType.TgtCallHsdpa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event



K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 187 VS.RadioBearerReconfigFailure - #670

A-Description

The number of Radio Bearers that failed to be reconfigured.

B-Collection

CUM

CUMulative

C-Condition (Event)

Any event that prevents the reconfiguration of an RB.

D-Result


• Sub-Counter #0 : Unavailable DL code resources

• Sub-Counter #1 : Unavailable DL power resources


• Sub-Counter #3 : CAC RNC Processing resources

• Sub-Counter #4 : Lack of bandwidth on the Iu



E-Type

• VS.RadioBearerReconfigFailure.VS.RadioBearerReconfigFailure.NoDlCodeRsrc

• VS.RadioBearerReconfigFailure.VS.RadioBearerReconfigFailure.NoDlPwrRsrc

• VS.RadioBearerReconfigFailure.VS.RadioBearerReconfigFailure.Unspecified

• VS.RadioBearerReconfigFailure.VS.RadioBearerReconfigFailure.CacRncProcRsrc

• VS.RadioBearerReconfigFailure.VS.RadioBearerReconfigFailure.LackBwIu

• VS.RadioBearerReconfigFailure.VS.RadioBearerReconfigFailure.LackBwIur

• VS.RadioBearerReconfigFailure.VS.RadioBearerReconfigFailure.LackBwIub

F-Object Instance

Cell(Reference)

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 188 VS.RabEstablishmentRequestsPerRabType - #671

A-Description

the number of RAB establishment attempts. RAB type used is one selected before RAB match-ing. When requested to setup an Interactive or Background service, the RNC will peg thescreening ID (corresponding to the bit rate) that most closely matches the requested RAB forsetup. The bit rates are selected from those currently available in DCH at the UTRAN level,even if HSDPA is available to carry Interactive and Background Traffic. In the case which re-quests the addition of two PS64KXPS64K RABs simultaneously (say, in a single RAB assign-ment request), the counter will peg twice for the addition of a PS64KXPS64K RAB. Thiscounter pegs based upon the RAB requested. In this case, two RABs have been requested.Screenings 27, 28 are always zero. This counter pegs also on RANAP Relocation Request(CR Q01458257).

B-Collection

CUM

CUMulative

C-Condition (Event)

The counter is pegged on reception of - a RANAP Rab Assignment Request - a RANAP Relo-cation Request

D-Result

A set of subcounters screened on: DlRbSetId,UlRbSetId,TrafficClass derived screening per re-quested Rab , see also Annex: T03

• Sub-Counter #0 : Other Dl, Ul, Traffic Class combinations

• Sub-Counter #1 : Dl and Ul are CS Speech, TC is Conversational

• Sub-Counter #2 : Dl and Ul are CSD 64, TC is Conversational



• Sub-Counter #3 : Dl and Ul are CS 14.4, TC is Streaming


• Sub-Counter #5 : Dl is any low rate PS I/B, Ul is any PS I/B, TC is Interative

• Sub-Counter #6 : Dl is any low rate PS I/B, Ul is any PS I/B, TC is Background

• Sub-Counter #7 : Dl and Ul are any PS Str, TC is Streaming

• Sub-Counter #8 : Dl is any high rate PS I/B, Ul is any PS I/B, TC is Interative

• Sub-Counter #9 : Dl is any high rate PS I/B, Ul is any PS I/B, TC is Background

E-Type

• VS.RabEstablishmentRequestsPerRabType.VS.RabEstablishmentRequestsPerRabType.ReqRabOther

• VS.RabEstablishmentRequestsPerRabType.VS.RabEstablishmentRequestsPerRabType.ReqRabCsSpeechConv

• VS.RabEstablishmentRequestsPerRabType.VS.RabEstablishmentRequestsPerRabType.ReqRabCsConv64

• VS.RabEstablishmentRequestsPerRabType.VS.RabEstablishmentRequestsPerRabType.ReqRabCsStr14_4

• VS.RabEstablishmentRequestsPerRabType.VS.RabEstablishmentRequestsPerRabType.ReqRabCsStr57_6

• VS.RabEstablishmentRequestsPerRabType.VS.RabEstablishmentRequestsPerRabType.ReqRabPsLowRateInter

• VS.RabEstablishmentRequestsPerRabType.VS.RabEstablishmentRequestsPerRabType.ReqRabPsLowRateBgnd

• VS.RabEstablishmentRequestsPerRabType.VS.RabEstablishmentRequestsPerRabType.ReqRabPsStr

• VS.RabEstablishmentRequestsPerRabType.VS.RabEstablishmentRequestsPerRabType.ReqRabPsHighRateInter

• VS.RabEstablishmentRequestsPerRabType.VS.RabEstablishmentRequestsPerRabType.ReqRabPsHighRateBgnd

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 189 VS.RabEstablishmentSuccessPerRequestedRabType - #672

A-Description

the number of successful RAB establishment, screened per requested RAB type (to map thesuccesses with the requests). RAB type used is one selected before RAB matching. When re-quested to setup an Interactive or a Background service, the RNC will peg the screening Id(corresponding to the bit rate) that most closely matches the requested RAB for setup. The bitrates are selected from those currently available in DCH at the UTRAN level, even if HSDPA isavailable to carry Interactive and Background traffic. In the case which requests the addition oftwo PS64KXPS64K RABs simultaneously (say, in a single RAB assignment request), thecounter will peg twice for the addition of a PS64KXPS64K rab. This counter pegs based uponthe RAB requested. In this case, two RABs have been requested. Screenings 27, 28 are al-ways zero. This counter pegs also in case of Relocation Ack (CR Q01458257).

B-Collection

CUM

CUMulative

C-Condition (Event)

The counter is pegged: - before sending RANAP Rab Assignment Response - before sendingRanap Relocation Ack

D-Result














E-Type

• VS.RabEstablishmentSuccessPerRequestedRabType.VS.RabEstablishmentSuccessPerRequestedRabType.ReqRabOther

• VS.RabEstablishmentSuccessPerRequestedRabType.VS.RabEstablishmentSuccessPerRequestedRabType.ReqRabCsSpeechConv

• VS.RabEstablishmentSuccessPerRequestedRabType.VS.RabEstablishmentSuccessPerRequestedRabType.ReqRabCsConv64

• VS.RabEstablishmentSuccessPerRequestedRabType.VS.RabEstablishmentSuccessPerRequestedRabType.ReqRabCsStr14_4

• VS.RabEstablishmentSuccessPerRequestedRabType.VS.RabEstablishmentSuccessPerRequestedRabType.ReqRabCsStr57_6

• VS.RabEstablishmentSuccessPerRequestedRabType.VS.RabEstablishmentSuccessPerRequestedRabType.ReqRabPsLowRateInter

• VS.RabEstablishmentSuccessPerRequestedRabType.VS.RabEstablishmentSuccessPerRequestedRabType.ReqRabPsLowRateBgnd

• VS.RabEstablishmentSuccessPerRequestedRabType.VS.RabEstablishmentSuccessPerRequestedRabType.ReqRabPsStr

• VS.RabEstablishmentSuccessPerRequestedRabType.VS.RabEstablishmentSuccessPerRequestedRabType.ReqRabPsHighRateInter

• VS.RabEstablishmentSuccessPerRequestedRabType.VS.RabEstablishmentSuccessPerRequestedRabType.ReqRabPsHighRateBgnd

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 190 VS.RabEstablishmentSuccessPerGrantedRabType - #673

A-Description

the number of successful RAB establishment, screened per granted RAB type. Granted shouldbe understood as after RNC CAC (iRM..).

B-Collection

CUM

CUMulative

C-Condition (Event)

On reception of a RANAP RAB Assignment Response message.

D-Result

A set of subcounters screened on: DlRbSetId,UlRbSetId,TrafficClass derived screening pergranted Rab , see also Annex: T04






• Sub-Counter #5 : Dl is any PS I/B, Ul is any PS I/B, TC is Interative

• Sub-Counter #6 : Dl is any PS I/B, Ul is any PS I/B, TC is Background


• Sub-Counter #8 : Dl is any 2x PS I/B, Ul is any 2x PS I/B, TC is Interative

• Sub-Counter #9 : Dl is any 2x PS I/B, Ul is any 2x PS I/B, TC is Background

• Sub-Counter #10 : Dl is HSDPA, Ul is any PS I/B, TC is Interactive

• Sub-Counter #11 : Dl is HSDPA, Ul is any PS I/B, TC is Background

• Sub-Counter #12 : Dl is HSDPA, Ul is HSUPA, TC is Interactive

• Sub-Counter #13 : Dl is HSDPA, Ul is HSUPA, TC is Background

• Sub-Counter #14 : Dl is HSDPA, Ul is any 2x PS I/B, TC is Interactive

• Sub-Counter #15 : Dl is HSDPA, Ul is any 2x PS I/B, TC is Background

• Sub-Counter #16 : Dl is HSDPA, Ul is any PS Str, TC is Streaming

E-Type

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabOther

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabCSSpeechConv

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGran



tedRabType.GrntdRabCsConv64

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabCsStr14_4

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabCsStr57_6

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabPsInter

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabPsBgnd

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabPsStr

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabPs2xInter

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabPs2xBgnd

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabHsdpaPsInter

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabHsdpaPsBgnd

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabHsdpaHsupaInter

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabHsdpaHsupaBgnd

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabHsdpa2xPsInter

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabHsdpa2xPsBgnd

• VS.RabEstablishmentSuccessPerGrantedRabType.VS.RabEstablishmentSuccessPerGrantedRabType.GrntdRabHsdpaPsStr

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 191 VS.RabReleaseRequest - #674

A-Description

the number of RAB release requested by the RNC, screened per RAB type (currently alloc-ated).

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a RANAP RAB RELEASE REQUEST.

D-Result





















E-Type

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabOther

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabCSSpeechConv

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabCsConv64

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabCsStr14_4

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabCsStr57_6

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabPsInter

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabPsBgnd

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabPsStr

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabPs2xInter

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabPs2xBgnd

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabHsdpaPsInter

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabHsdpaPsBgnd

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabHsdpaHsupaInter

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabHsdpaHsupaBgnd

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabHsdpa2xPsInter

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabHsdpa2xPsBgnd

• VS.RabReleaseRequest.VS.RabReleaseRequest.GrntdRabHsdpaPsStr

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 192 VS.NumberOfRabEstablished - #675

A-Description

This counter is the average number of RABs established of the "granted RAB type" in the RNSduring a reporting period. Hence, the counter does not peg when an Always On Downsize oc-curs. Minimum and maximum number of RABs over the period are also provided. RAB grantedshould be understood as RAB effectively established (iRM can modify the characteristics of aRAB, either at call admission or during the call for PS : iRM Scheduling downgrade, upgrade,Always ON).

B-Collection

LOAD

C-Condition (Event)

Establishment, release (RAB Assignment Request or Iu Release Request RANAP procedures)or internal reconfiguration of a RAB. The number of established RAB is sampled each 100ms.

D-Result



















E-Type

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabOther



• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabCSSpeechConv

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabCsConv64

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabCsStr14_4

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabCsStr57_6

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabPsInter

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabPsBgnd

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabPsStr

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabPs2xInter

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabPs2xBgnd

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabHsdpaPsInter

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabHsdpaPsBgnd

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabHsdpaHsupaInter

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabHsdpaHsupaBgnd

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabHsdpa2xPsInter

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabHsdpa2xPsBgnd

• VS.NumberOfRabEstablished.VS.NumberOfRabEstablished.GrntdRabHsdpaPsStr

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 193 VS.RabNormalRelease - #676

A-Description



the number of normal RAB release per RAB type (to map the RAB release with the RAB estab-lished).

B-Collection

CUM

CUMulative

C-Condition (Event)

Every time RNC releases a RAB for a normal reason : - Successful HHO, ie Iu Release Com-mand with cause successful relocation - Always ON step 2, ie Iu Release Command for a RABasked to be released by the RNC due to user inactivity (this is not double-counted with the fol-lowing reason) - normal Core release messages : Iu Release Command or RAB AssignmentReq for release with cause Normal Release or User Inactivity

D-Result



















E-Type

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabOther

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabCSSpeechConv

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabCsConv64



• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabCsStr14_4

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabCsStr57_6

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabPsInter

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabPsBgnd

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabPsStr

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabPs2xInter

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabPs2xBgnd

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabHsdpaPsInter

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabHsdpaPsBgnd

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabHsdpaHsupaInter

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabHsdpaHsupaBgnd

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabHsdpa2xPsInter

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabHsdpa2xPsBgnd

• VS.RabNormalRelease.VS.RabNormalRelease.GrntdRabHsdpaPsStr

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 194 VS.RabAssignmentSetupUnsuccess - #677

A-Description

the number of RAB that could not be established by the RNC. This is incremented for anytraffic class (Rabid) for which a setup has been answered as failed through arab_assignment_response message. When requested to setup an Interactive or a Background



service, the RNC will peg the screening Id (corresponding to the bit rate) that most closelymatches the requested RAB for setup. The bit rates are selected from those currently availablein DCH at the UTRAN level, even if HSDPA is available to carry Interactive and Backgroundtraffic. Screenings 27, 28 are always zero.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a RAB Assignement Response with some RABs not successfully established. Thecounter is incremented by the number of RAB that could not be established.

D-Result












E-Type

• VS.RabAssignmentSetupUnsuccess.VS.RabAssignmentSetupUnsuccess.ReqRabOther

• VS.RabAssignmentSetupUnsuccess.VS.RabAssignmentSetupUnsuccess.ReqRabCsSpeechConv

• VS.RabAssignmentSetupUnsuccess.VS.RabAssignmentSetupUnsuccess.ReqRabCsConv64

• VS.RabAssignmentSetupUnsuccess.VS.RabAssignmentSetupUnsuccess.ReqRabCsStr14_4

• VS.RabAssignmentSetupUnsuccess.VS.RabAssignmentSetupUnsuccess.ReqRabCsStr57_6

• VS.RabAssignmentSetupUnsuccess.VS.RabAssignmentSetupUnsuccess.ReqRabPsLowRateInter

• VS.RabAssignmentSetupUnsuccess.VS.RabAssignmentSetupUnsuccess.ReqRabPsLowRateBgnd



• VS.RabAssignmentSetupUnsuccess.VS.RabAssignmentSetupUnsuccess.ReqRabPsStr

• VS.RabAssignmentSetupUnsuccess.VS.RabAssignmentSetupUnsuccess.ReqRabPsHighRateInter

• VS.RabAssignmentSetupUnsuccess.VS.RabAssignmentSetupUnsuccess.ReqRabPsHighRateBgnd

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 195 VS.RabAssignmentReleaseSuccess - #678

A-Description

the number of successful Radio Access Bearer releases, screened by RAB type. This is incre-mented for any traffic class (Rabid) for which a release has been correctly acknowledgedthrough a rb_assignement_response message. When requested to release an Interactive or aBackground service, the RNC will peg the screening Id (corresponding to the bit rate) that mostclosely matches the requested Rab for release. The bit rates are selected from those currentlyavailable in DCH at the UTRAN level, even if HSDPA is available to carry Interactive and Back-ground traffic. Screenings 27, 28 are always zero.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of RAB ASSIGNMENT RESPONSE message(s) following the receptionof a RANAP RAB ASSIGNMENT REQUEST message. The RAB ASSIGNMENT RE-SPONSE(s) may report RABs successfully established or modified and RABs released. The



measurement considers (and only considers) each successfully released RAB as requested inthe RANAP RAB ASSIGNMENT REQUEST message.

D-Result












E-Type

• VS.RabAssignmentReleaseSuccess.VS.RabAssignmentReleaseSuccess.ReqRabOther

• VS.RabAssignmentReleaseSuccess.VS.RabAssignmentReleaseSuccess.ReqRabCsSpeechConv

• VS.RabAssignmentReleaseSuccess.VS.RabAssignmentReleaseSuccess.ReqRabCsConv64

• VS.RabAssignmentReleaseSuccess.VS.RabAssignmentReleaseSuccess.ReqRabCsStr14_4

• VS.RabAssignmentReleaseSuccess.VS.RabAssignmentReleaseSuccess.ReqRabCsStr57_6

• VS.RabAssignmentReleaseSuccess.VS.RabAssignmentReleaseSuccess.ReqRabPsLowRateInter

• VS.RabAssignmentReleaseSuccess.VS.RabAssignmentReleaseSuccess.ReqRabPsLowRateBgnd

• VS.RabAssignmentReleaseSuccess.VS.RabAssignmentReleaseSuccess.ReqRabPsStr

• VS.RabAssignmentReleaseSuccess.VS.RabAssignmentReleaseSuccess.ReqRabPsHighRateInter

• VS.RabAssignmentReleaseSuccess.VS.RabAssignmentReleaseSuccess.ReqRabPsHighRateBgnd

F-Object Instance

RNC

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 196 VS.RabAssignmentReleaseUnsuccess - #679

A-Description

the number of failed Radio Access Bearer releases, screened by RAB type. Behaviour hasbeen modified (for multiple PS RAB handling; this applies also to #621, #622, #623, #627,#629, #632, #633). If the DL/UL RB Setid are unknown when pegging, the default MAX valuewill be used (e.g. typical defense cases). When requested to release an Interactive or a Back-ground service, the RNC will peg the screening Id (corresponding to the bit rate) that mostclosely matches the requested Rab for release. The bit rates are selected from those currentlyavailable in DCH at the UTRAN level, even if HSDPA is available to carry Interactive and Back-ground traffic. Screenings 27, 28 are always zero.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of RAB ASSIGNMENT RESPONSE message(s) following the receptionof a RANAP RAB ASSIGNMENT REQUEST message. The RAB ASSIGNMENT RE-SPONSE(s) may report RABs successfully established or modified and RABs released. Themeasurement considers (and only considers) each RAB requested to be released in theRANAP RAB ASSIGNMENT REQUEST message which is not mentioned as released in thesubsequent RAB ASSIGNMENT RESPONSE(s).

D-Result














E-Type

• VS.RabAssignmentReleaseUnsuccess.VS.RabAssignmentReleaseUnsuccess.ReqRabOther

• VS.RabAssignmentReleaseUnsuccess.VS.RabAssignmentReleaseUnsuccess.ReqRabCsSpeechConv

• VS.RabAssignmentReleaseUnsuccess.VS.RabAssignmentReleaseUnsuccess.ReqRabCsConv64

• VS.RabAssignmentReleaseUnsuccess.VS.RabAssignmentReleaseUnsuccess.ReqRabCsStr14_4

• VS.RabAssignmentReleaseUnsuccess.VS.RabAssignmentReleaseUnsuccess.ReqRabCsStr57_6

• VS.RabAssignmentReleaseUnsuccess.VS.RabAssignmentReleaseUnsuccess.ReqRabPsLowRateInter

• VS.RabAssignmentReleaseUnsuccess.VS.RabAssignmentReleaseUnsuccess.ReqRabPsLowRateBgnd

• VS.RabAssignmentReleaseUnsuccess.VS.RabAssignmentReleaseUnsuccess.ReqRabPsStr

• VS.RabAssignmentReleaseUnsuccess.VS.RabAssignmentReleaseUnsuccess.ReqRabPsHighRateInter

• VS.RabAssignmentReleaseUnsuccess.VS.RabAssignmentReleaseUnsuccess.ReqRabPsHighRateBgnd

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 197 VS.RabOutgoingRefCell - #680

A-Description

the number of times in which that cell stops being the reference cell with an active RAB. "Act-ive RAB" means "RAB established", meaning that calls on SRB shall not be counted. When anInteractive or a Background service call is moving its reference cell, on the former referencecell, the RNC will peg the screening Id (corresponding to the bit rate) that most closely matchesthe last Rab characteristics provided by the Core Network. The bit rates are selected fromthose currently available in DCH at the UTRAN level, even if HSDPA available to carry Inter-active and Background traffic. Screenings 27, 28 are always zero.

B-Collection

CUM

CUMulative

C-Condition (Event)

Cell stops being the reference cell with an active RAB

D-Result












E-Type



• VS.RabOutgoingRefCell.VS.RabOutgoingRefCell.ReqRabOther

• VS.RabOutgoingRefCell.VS.RabOutgoingRefCell.ReqRabCsSpeechConv

• VS.RabOutgoingRefCell.VS.RabOutgoingRefCell.ReqRabCsConv64

• VS.RabOutgoingRefCell.VS.RabOutgoingRefCell.ReqRabCsStr14_4

• VS.RabOutgoingRefCell.VS.RabOutgoingRefCell.ReqRabCsStr57_6

• VS.RabOutgoingRefCell.VS.RabOutgoingRefCell.ReqRabPsLowRateInter

• VS.RabOutgoingRefCell.VS.RabOutgoingRefCell.ReqRabPsLowRateBgnd

• VS.RabOutgoingRefCell.VS.RabOutgoingRefCell.ReqRabPsStr

• VS.RabOutgoingRefCell.VS.RabOutgoingRefCell.ReqRabPsHighRateInter

• VS.RabOutgoingRefCell.VS.RabOutgoingRefCell.ReqRabPsHighRateBgnd

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 198 VS.RabIncomingRefCell - #681

A-Description

This measurement counts the number of times in which that cell becomes a reference cell withan active RAB. "Active RAB" means "RAB established", meaning that calls on SRB shall not becounted. When an Interactive or a Background service call is moving its reference cell, on thenew reference cell, the RNC will peg the screening Id (corresponding to the bit rate) that mostclosely matches the last Rab characteristics provided by the Core Network. The bit rates areselected from those currently available in DCH at the UTRAN level, even if HSDPA available tocarry Interactive and Background traffic. Screenings 27, 28 are always zero.

B-Collection



CUM

CUMulative

C-Condition (Event)

Cell becomes a reference cell with an active RAB.

D-Result












E-Type

• VS.RabIncomingRefCell.VS.RabIncomingRefCell.ReqRabOther

• VS.RabIncomingRefCell.VS.RabIncomingRefCell.ReqRabCsSpeechConv

• VS.RabIncomingRefCell.VS.RabIncomingRefCell.ReqRabCsConv64

• VS.RabIncomingRefCell.VS.RabIncomingRefCell.ReqRabCsStr14_4

• VS.RabIncomingRefCell.VS.RabIncomingRefCell.ReqRabCsStr57_6

• VS.RabIncomingRefCell.VS.RabIncomingRefCell.ReqRabPsLowRateInter

• VS.RabIncomingRefCell.VS.RabIncomingRefCell.ReqRabPsLowRateBgnd

• VS.RabIncomingRefCell.VS.RabIncomingRefCell.ReqRabPsStr

• VS.RabIncomingRefCell.VS.RabIncomingRefCell.ReqRabPsHighRateInter

• VS.RabIncomingRefCell.VS.RabIncomingRefCell.ReqRabPsHighRateBgnd

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 199 VS.RabEstabSuccPerReqRabTypRefCell - #682

A-Description

the number of RAB established per requested RAB type reference cell. When requested tosetup an Interactive or a Background service, the RNC will peg the screening Id(corresponding to the bit rate) that most closely matches the requested Rab for setup. The bitrates are selected from those currently available in DCH at the UTRAN level, even if HSDPA isavailable to carry Interactive and Background traffic. Screening 27, 28 are always zero.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP/RAB assignment response message

D-Result














E-Type

• VS.RabEstabSuccPerReqRabTypRefCell.VS.RabEstabSuccPerReqRabTypRefCell.ReqRabOther

• VS.RabEstabSuccPerReqRabTypRefCell.VS.RabEstabSuccPerReqRabTypRefCell.ReqRabCsSpeechConv

• VS.RabEstabSuccPerReqRabTypRefCell.VS.RabEstabSuccPerReqRabTypRefCell.ReqRabCsConv64

• VS.RabEstabSuccPerReqRabTypRefCell.VS.RabEstabSuccPerReqRabTypRefCell.ReqRabCsStr14_4

• VS.RabEstabSuccPerReqRabTypRefCell.VS.RabEstabSuccPerReqRabTypRefCell.ReqRabCsStr57_6

• VS.RabEstabSuccPerReqRabTypRefCell.VS.RabEstabSuccPerReqRabTypRefCell.ReqRabPsLowRateInter

• VS.RabEstabSuccPerReqRabTypRefCell.VS.RabEstabSuccPerReqRabTypRefCell.ReqRabPsLowRateBgnd

• VS.RabEstabSuccPerReqRabTypRefCell.VS.RabEstabSuccPerReqRabTypRefCell.ReqRabPsStr

• VS.RabEstabSuccPerReqRabTypRefCell.VS.RabEstabSuccPerReqRabTypRefCell.ReqRabPsHighRateInter

• VS.RabEstabSuccPerReqRabTypRefCell.VS.RabEstabSuccPerReqRabTypRefCell.ReqRabPsHighRateBgnd

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 200 VS.RabAbnormRelPerReqRabTypRefCel - #683

A-Description

the number of abnormal RAB releases per requested RAB type reference cell. When an Inter-active or a Background service is subject to an abnormal release, the RNC will peg the screen-ing Id (corresponding to the bit rate) that most closely matches the requested Rab for release.The bit rates are selected from those currently available in DCH at the UTRAN level, even ifHSDPA available to carry Interactive and Background traffic. Screenings 27, 28 are alwayszero.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP/RAB assignement request message

D-Result












E-Type

• VS.RabAbnormRelPerReqRabTypRefCel.VS.RabAbnormRelPerReqRabTypRefCel.ReqRabOther

• VS.RabAbnormRelPerReqRabTypRefCel.VS.RabAbnormRelPerReqRabTypRefCel.ReqRabCsSpeechConv

• VS.RabAbnormRelPerReqRabTypRefCel.VS.RabAbnormRelPerReqRabTypRefCel.ReqRabCsConv64

• VS.RabAbnormRelPerReqRabTypRefCel.VS.RabAbnormRelPerReqRabTypRefCel.ReqRabCsStr14_4

• VS.RabAbnormRelPerReqRabTypRefCel.VS.RabAbnormRelPerReqRabTypRefCel.ReqRabCsStr57_6



• VS.RabAbnormRelPerReqRabTypRefCel.VS.RabAbnormRelPerReqRabTypRefCel.ReqRabPsLowRateInter

• VS.RabAbnormRelPerReqRabTypRefCel.VS.RabAbnormRelPerReqRabTypRefCel.ReqRabPsLowRateBgnd

• VS.RabAbnormRelPerReqRabTypRefCel.VS.RabAbnormRelPerReqRabTypRefCel.ReqRabPsStr

• VS.RabAbnormRelPerReqRabTypRefCel.VS.RabAbnormRelPerReqRabTypRefCel.ReqRabPsHighRateInter

• VS.RabAbnormRelPerReqRabTypRefCel.VS.RabAbnormRelPerReqRabTypRefCel.ReqRabPsHighRateBgnd

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 201 VS.RadioBearerReconfigurationSuccess - #684

A-Description

the number of successful radio bearer reconfigurations for each cell controlled by the RNCwhich is the primary cell. During such a procedure, the measurement attached to a given cell isincremented if the cell is the primary cell of the active set of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception by the RNC of a RRC RADIO BEARER RECONFIGURATION COMPLETE mes-



sage following the emission of a RRC RADIO BEARER RECONFIGURATION message. Themeasurement is only incremented when the UE's primary cell is under the control of its SRNC.

D-Result

A set of subcounters screened on: Target type of call for Radio Bearer Reconfiguration , seealso Annex: T16













E-Type

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfOther

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfSignalling

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfCsSpeech

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfCsData

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfCsStr

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfPsStr

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfPsIB

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfCsSpeechPsIB

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfCsDataPsIB

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfPsStrPsIB



• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfCsSpeechPsStr

• VS.RadioBearerReconfigurationSuccess.VS.RadioBearerReconfigurationSuccess.RbReconfCsSpeechPsStrPsIB

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 202 VS.RadioBearerReconfigureRequest - #685

A-Description

the number of Radio bearer reconfiguration decisions by the RNC (leading or not to a RBSETUP or RB RECONFIGURATION, ie. even if Call Admission Control rejects the reconfigura-tion).

B-Collection

CUM

CUMulative

C-Condition (Event)

Decision to reconfigure an existing RB : - Always ON downsize or upsize - (outgoing or incom-ing) Hard-handover 3G to 3G - iRM Scheduling downgrade or upgrade - iRM Pre-emption

D-Result
















E-Type

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfOther

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfSignalling

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfCsSpeech

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfCsData

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfCsStr

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfPsStr

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfPsIB

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfCsSpeechPsIB

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfCsDataPsIB

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfPsStrPsIB

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfCsSpeechPsStr

• VS.RadioBearerReconfigureRequest.VS.RadioBearerReconfigureRequest.RbReconfCsSpeechPsStrPsIB

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 203 VS.RadioBearerReconfigurationSuccessNeighbRnc - #686

A-Description

the number of successful radio bearer reconfigurations for each neighboring RNC. During sucha procedure, the measurement attached to a given neighboring RNC is incremented as manytimes as there are cells in the active set which are controlled by this neighboring RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RRC RADIO BEARER RECONFIGURATION message for whichany subsequent RADIO BEARER RECONFIGURATION COMPLETE message has been re-ceived. The event is only considered when the UE has one or several cells in its active setwhich are outside the control of its SRNC. The counter is incremented as many times as thereare cells of the active set on this neighboring RNC.

D-Result
















E-Type

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfOther

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfSignalling

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfCsSpeech

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfCsData

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfCsStr

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfPsStr

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfPsIB

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfCsSpeechPsIB

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfCsDataPsIB

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfPsStrPsIB

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfCsSpeechPsStr

• VS.RadioBearerReconfigurationSuccessNeighbRnc.VS.RadioBearerReconfigurationSuccessNeighbRnc.RbReconfCsSpeechPsStrPsIB

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 204 VS.RadioBearerSetupSuccess - #687

A-Description

the number of successful radio bearer establishment procedures, for each cell controlled by theRNC which is the reference cell. During such a procedure, the measurement attached to a giv-en cell is incremented if the cell is the primary cell of the active set of the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception by the RNC of a RRC RADIO BEARER SETUP COMPLETE message following theemission of a RRC RADIO BEARER SETUP message. The event is only considered when theUE's primary cell is under the control of its SRNC.

D-Result



















E-Type

• VS.RadioBearerSetupSuccess.VS.RadioBearerSetupSuccess.TgtCallOther

• VS.RadioBearerSetupSuccess.VS.RadioBearerSetupSuccess.TgtCallCsSpeech

• VS.RadioBearerSetupSuccess.VS.RadioBearerSetupSuccess.TgtCallCsData

• VS.RadioBearerSetupSuccess.VS.RadioBearerSetupSuccess.TgtCallCsStr

• VS.RadioBearerSetupSuccess.VS.RadioBearerSetupSuccess.TgtCallPsStr16




• VS.RadioBearerSetupSuccess.VS.RadioBearerSetupSuccess.TgtCallPsIb8






• VS.RadioBearerSetupSuccess.VS.RadioBearerSetupSuccess.TgtCallHsdpa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 205 VS.RadioBearerReleaseSuccess - #688



A-Description

the number of successful radio bearer releases for each cell controlled by the RNC which is theprimary cell. During such a procedure, the measurement attached to a given cell is incremen-ted if the cell is in the primary cell of the active set of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception by the RNC of a RRC RADIO BEARER RELEASE COMPLETE message followingthe emission of a RRC RADIO BEARER RELEASE message. The measurement is only incre-mented when the UE's primary cell is under the control of its SRNC.

D-Result

A set of subcounters screened on: Source Type of call release mapping , see also Annex: T08

















E-Type

• VS.RadioBearerReleaseSuccess.VS.RadioBearerReleaseSuccess.SrcCallOther

• VS.RadioBearerReleaseSuccess.VS.RadioBearerReleaseSuccess.SrcCallCsSpeech

• VS.RadioBearerReleaseSuccess.VS.RadioBearerReleaseSuccess.SrcCallCsData

• VS.RadioBearerReleaseSuccess.VS.RadioBearerReleaseSuccess.SrcCallCsStr

• VS.RadioBearerReleaseSuccess.VS.RadioBearerReleaseSuccess.SrcCallPsStr16






• VS.RadioBearerReleaseSuccess.VS.RadioBearerReleaseSuccess.SrcCallPsIb8






• VS.RadioBearerReleaseSuccess.VS.RadioBearerReleaseSuccess.SrcCallHsdpa

• VS.RadioBearerReleaseSuccess.VS.RadioBearerReleaseSuccess.SrcCallTrbFach

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 206 VS.RadioBearerSetupSuccessNeighbRnc - #689

A-Description

the number of Radio Bearer successfully setup (from serving RNC), with at least a cell of theactive set belonging to a neighbouring RNC. This counter will not be incremented for HSDPADlAsConfId since there is no IUR with HSDPA calls.

B-Collection

CUM

CUMulative



C-Condition (Event)

Reception by the RNC of a RRC RADIO BEARER SETUP COMPLETE message following theemission of a RRC RADIO BEARER SETUP message. The event is only considered when theUE has its reference cell under the control of a DRNS.

D-Result

















E-Type

• VS.RadioBearerSetupSuccessNeighbRnc.VS.RadioBearerSetupSuccessNeighbRnc.TgtCallOther

• VS.RadioBearerSetupSuccessNeighbRnc.VS.RadioBearerSetupSuccessNeighbRnc.TgtCallCsSpeech

• VS.RadioBearerSetupSuccessNeighbRnc.VS.RadioBearerSetupSuccessNeighbRnc.TgtCallCsData

• VS.RadioBearerSetupSuccessNeighbRnc.VS.RadioBearerSetupSuccessNeighbRnc.TgtCallCsStr

• VS.RadioBearerSetupSuccessNeighbRnc.VS.RadioBearerSetupSuccessNeighbRnc.TgtCallPsStr16






• VS.RadioBearerSetupSuccessNeighbRnc.VS.RadioBearerSetupSuccessNeighbRnc.TgtCallPsIb8






• VS.RadioBearerSetupSuccessNeighbRnc.VS.RadioBearerSetupSuccessNeighbRnc.TgtCallHsdpa

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 207 VS.RadioBearerReleaseSuccessNeighbRnc - #690

A-Description

the number of successful radio bearer releases for each neighboring RNC. During such a pro-cedure, the measurement attached to a given neighboring RNC is incremented as many timesas there are cells in the active set which are controlled by this neighboring RNC.

B-Collection



CUM

CUMulative

C-Condition (Event)

Reception by the RNC of a RRC RADIO BEARER RELEASE COMPLETE message followingthe emission of a RRC RADIO BEARER RELEASE message. The event is only consideredwhen the UE has one or several cells in its active set which are outside the control of itsSRNC. The counter is incremented as many times as there are cells of the active set on thisneighboring RNC.

D-Result

A set of subcounters screened on: Source Type of call release mapping , see also Annex: T08

















E-Type

• VS.RadioBearerReleaseSuccessNeighbRnc.VS.RadioBearerReleaseSuccessNeighbRnc.SrcCallOther

• VS.RadioBearerReleaseSuccessNeighbRnc.VS.RadioBearerReleaseSuccessNeighbRnc.SrcCallCsSpeech

• VS.RadioBearerReleaseSuccessNeighbRnc.VS.RadioBearerReleaseSuccessNeighbRnc.SrcCallCsData

• VS.RadioBearerReleaseSuccessNeighbRnc.VS.RadioBearerReleaseSuccessNeighbRnc.SrcCallCsStr

• VS.RadioBearerReleaseSuccessNeighbRnc.VS.RadioBearerReleaseSuccessNeighbRnc.



SrcCallPsStr16

• VS.RadioBearerReleaseSuccessNeighbRnc.VS.RadioBearerReleaseSuccessNeighbRnc.SrcCallPsStr64



• VS.RadioBearerReleaseSuccessNeighbRnc.VS.RadioBearerReleaseSuccessNeighbRnc.SrcCallPsIb8






• VS.RadioBearerReleaseSuccessNeighbRnc.VS.RadioBearerReleaseSuccessNeighbRnc.SrcCallHsdpa

• VS.RadioBearerReleaseSuccessNeighbRnc.VS.RadioBearerReleaseSuccessNeighbRnc.SrcCallTrbFach

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 208 VS.RadioBearerSetupRequest - #691

A-Description

the number of Radio Bearer setup decisions by the RNC, incremented based on reference cell.It counts based on the requested Dowlnlink AsConfID ((DL Access stratum Configuration) . Be-fore CR Q01244717, counters was pegged based on targetDlAsconfId (obtained as output ofIRM algorithm), therefore could not be pegged in case of CAC rejection. Since CR Q01244717,counter is pegged accordingly to the requested Downlink AsConfId, then allowing pegging alsoin case of CAC rejection.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of RAB Assignment request (addition only).

D-Result

















E-Type

• VS.RadioBearerSetupRequest.VS.RadioBearerSetupRequest.TgtCallOther

• VS.RadioBearerSetupRequest.VS.RadioBearerSetupRequest.TgtCallCsSpeech

• VS.RadioBearerSetupRequest.VS.RadioBearerSetupRequest.TgtCallCsData



• VS.RadioBearerSetupRequest.VS.RadioBearerSetupRequest.TgtCallCsStr

• VS.RadioBearerSetupRequest.VS.RadioBearerSetupRequest.TgtCallPsStr16




• VS.RadioBearerSetupRequest.VS.RadioBearerSetupRequest.TgtCallPsIb8






• VS.RadioBearerSetupRequest.VS.RadioBearerSetupRequest.TgtCallHsdpa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 209 VS.DlAsConfIdAvgNbrEstablished - #692

A-Description

indicates an average of the number of DlAsConfIds established per iRNC, based on time aver-age over collection period

B-Collection

LOAD



C-Condition (Event)

Any time an DlAsConfId is established or deleted (even on SRB establishment)

D-Result

A set of subcounters screened on: Derived AsConf Screening for DlAsConfId Avg Nbr Estab ,see also Annex: T11

















E-Type

• VS.DlAsConfIdAvgNbrEstablished.VS.DlAsConfIdAvgNbrEstablished.DlAsCnfSignalling

• VS.DlAsConfIdAvgNbrEstablished.VS.DlAsConfIdAvgNbrEstablished.DlAsCnfCsSpeech

• VS.DlAsConfIdAvgNbrEstablished.VS.DlAsConfIdAvgNbrEstablished.DlAsCnfCsData

• VS.DlAsConfIdAvgNbrEstablished.VS.DlAsConfIdAvgNbrEstablished.DlAsCnfCsStr

• VS.DlAsConfIdAvgNbrEstablished.VS.DlAsConfIdAvgNbrEstablished.DlAsCnfPsStr16




• VS.DlAsConfIdAvgNbrEstablished.VS.DlAsConfIdAvgNbrEstablished.DlAsCnfPsIB8








• VS.DlAsConfIdAvgNbrEstablished.VS.DlAsConfIdAvgNbrEstablished.DlAsCnfHsdpa

• VS.DlAsConfIdAvgNbrEstablished.VS.DlAsConfIdAvgNbrEstablished.DlAsCnfTrbCellFach

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 210 VS.UlAsConfIdAvgNbrEstablished - #693

A-Description

indicates an average of the number of UlAsConfIds established per iRNC, based on time aver-age over collection period

B-Collection

LOAD

C-Condition (Event)

Any time an UlAsConfId is established or deleted (even on SRB establishment)

D-Result

A set of subcounters screened on: Derived AsConf Screening for UlAsConfId Avg Nbr Estab ,see also Annex: T12
















• Sub-Counter #13 : HSUPA

• Sub-Counter #14 : TRB on cell RACH

E-Type

• VS.UlAsConfIdAvgNbrEstablished.VS.UlAsConfIdAvgNbrEstablished.UlAsCnfSig

• VS.UlAsConfIdAvgNbrEstablished.VS.UlAsConfIdAvgNbrEstablished.UlAsCnfCsSpeech

• VS.UlAsConfIdAvgNbrEstablished.VS.UlAsConfIdAvgNbrEstablished.UlAsCnfCsData

• VS.UlAsConfIdAvgNbrEstablished.VS.UlAsConfIdAvgNbrEstablished.UlAsCnfCsStr57_6

• VS.UlAsConfIdAvgNbrEstablished.VS.UlAsConfIdAvgNbrEstablished.UlAsCnfCsStr14_4

• VS.UlAsConfIdAvgNbrEstablished.VS.UlAsConfIdAvgNbrEstablished.UlAsCnfPsStr16



• VS.UlAsConfIdAvgNbrEstablished.VS.UlAsConfIdAvgNbrEstablished.UlAsCnfPsIB8





• VS.UlAsConfIdAvgNbrEstablished.VS.UlAsConfIdAvgNbrEstablished.UlAsCnfHsupa

• VS.UlAsConfIdAvgNbrEstablished.VS.UlAsConfIdAvgNbrEstablished.UlAsCnfTrbCellRach

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 211 VS.SucEdchToDchTrans - #694

A-Description

Number of successful E-DCH to DCH transitions

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful transition upon RAB assignment

D-Result

one measurement

E-Type

VS.SucEdchToDchTrans

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V5.0

L-Aggregation Rule

Rtotal

Table 212 VS.UnsucEdchToDchTrans - #695

A-Description

Number of unsuccessful E-DCH to DCH transition

B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccessful transition upon RAB assignment

D-Result

one measurement

E-Type

VS.UnsucEdchToDchTrans

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 213 VS.SucDchToEdchTrans - #696

A-Description



Number of successful DCH to E-DCH transitions

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful transition upon RAB assignment

D-Result

A set of subcounters screened on: DCH to E-DCH transition trigger.

• Sub-Counter #0 : RAB Setup

• Sub-Counter #1 : RAB Release

E-Type

• VS.SucDchToEdchTrans.VS.SucDchToEdchTrans.RABSetup

• VS.SucDchToEdchTrans.VS.SucDchToEdchTrans.RABRelease

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 214 VS.UnsucDchToEdchTrans - #697

A-Description

Number of unsuccessful DCH to E-DCH transitions

B-Collection

CUM



CUMulative

C-Condition (Event)

Unsuccessful transition upon RAB assignment

D-Result

A set of subcounters screened on: DCH to E-DCH transition trigger.



E-Type

• VS.UnsucDchToEdchTrans.VS.UnsucDchToEdchTrans.RABSetup

• VS.UnsucDchToEdchTrans.VS.UnsucDchToEdchTrans.RABRelease

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 215 VS.SucHspaToDchFallbackCell - #1601

A-Description

Number of calls successfully fallbacked from HSPA to DCH on RAB assignment, mobility or re-configuration event.

B-Collection

CUM

CUMulative

C-Condition (Event)



Successful call reconfiguration attempt to a fallback configuration following failure of initialHSPA target (re)configuration, on RAB assignment, mobility or reconfiguration event.

D-Result

A set of subcounters screened on: Fallback type.

• Sub-Counter #0 : DL:HSDPA/UL:DCH to DL:DCH/UL:DCH

• Sub-Counter #1 : DL:HSDPA/UL:E-DCH to DL:HSDPA/UL:DCH

• Sub-Counter #2 : DL:HSDPA/UL:E-DCH to DL:DCH/UL:DCH

E-Type

• VS.SucHspaToDchFallbackCell.VS.SucHspaToDchFallbackCell.HsdpaDchToDchDch

• VS.SucHspaToDchFallbackCell.VS.SucHspaToDchFallbackCell.HsdpaEdchToHsdpaDch

• VS.SucHspaToDchFallbackCell.VS.SucHspaToDchFallbackCell.HsdpaEdchToDchDch

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 216 VS.SucHspaToDchFallbackNrnc - #1602

A-Description

Number of calls successfully fallbacked from HSPA to DCH on RAB assignment, mobility or re-configuration event.

B-Collection

CUM

CUMulative



C-Condition (Event)

Successful call reconfiguration attempt to a fallback configuration following failure of initialHSPA target (re)configuration, on RAB assignment, mobility or reconfiguration event.

D-Result

A set of subcounters screened on: Fallback type on Iur.

• Sub-Counter #0 : DL:HSDPA/UL:DCH to DL:DCH/UL:DCH

E-Type

• VS.SucHspaToDchFallbackNrnc.VS.SucHspaToDchFallbackNrnc.HsdpaDchToDchDch

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 217 VS.UnsucHspaToDchFallbackCell - #1603

A-Description

Number of calls unsuccessfully fallbacked from HSPA to DCH on RAB assignment, mobility orreconfiguration event.

B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccessful call reconfiguration attempt to a fallback configuration following failure of initialHSPA target (re)configuration, on RAB assignment, mobility or reconfiguration even



D-Result

A set of subcounters screened on: Unsuccessful Fallback type.

• Sub-Counter #0 : DL:HSDPA/UL:DCH fallback

• Sub-Counter #1 : DL:HSDPA/UL:E-DCH fallback

E-Type

• VS.UnsucHspaToDchFallbackCell.VS.UnsucHspaToDchFallbackCell.DlHsdpaUlDch

• VS.UnsucHspaToDchFallbackCell.VS.UnsucHspaToDchFallbackCell.DlHsdpaUlEdch

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 218 VS.UnsucHspaToDchFallbackNrnc - #1604

A-Description

Number of calls unsuccessfully fallbacked from HSPA to DCH on RAB assignment, mobility orreconfiguration event.

B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccessful call reconfiguration attempt to a fallback configuration following failure of initialHSPA target (re)configuration, on RAB assignment, mobility or reconfiguration event

D-Result



A set of subcounters screened on: Unsuccessful Fallback Nrnc type.

• Sub-Counter #0 : DL:HSDPA/UL:DCH fallback

E-Type

• VS.UnsucHspaToDchFallbackNrnc.VS.UnsucHspaToDchFallbackNrnc.DlHsdpaUlDch

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.8 Security

The reference document for security management is 3GPP TS25.331 Radio Resource Control(RRC).


Counter name

#701 VS.SmcSuccess

#702 VS.RejectedSmc

#703 VS.FailedRrcSmc

Table 219 VS.SmcSuccess - #701

A-Description

the number of successful RANAP Security Mode Command procedures screened by Core Net-work domain

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RANAP SECURITY_MODE_COMPLETE message to the Core Net-work.

D-Result

A set of subcounters screened on: Per type of core

• Sub-Counter #0 : With core network CS

• Sub-Counter #1 : With core network PS

E-Type

• VS.SmcSuccess.VS.SmcSuccess.WithCoreNetworkCs

• VS.SmcSuccess.VS.SmcSuccess.WithCoreNetworkPs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 220 VS.RejectedSmc - #702

A-Description

the number of failed RANAP Security Mode Command procedures (before sending the RRCSMC) screened by Core Network domain

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RANAP SECURITY_MODE_REJECT message to the Core Networkbecause this security configuration is not allowed/compatible with current state.

D-Result




E-Type

• VS.RejectedSmc.VS.RejectedSmc.WithCoreNetworkCs

• VS.RejectedSmc.VS.RejectedSmc.WithCoreNetworkPs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V3.0

L-Aggregation Rule

Rtotal

Table 221 VS.FailedRrcSmc - #703

A-Description

the number of failed RRC Security Mode Command procedures screened by Core Network do-main

B-Collection

CUM

CUMulative

C-Condition (Event)

Failure of the RRC Security Mode Command procedure : either reception of an RRC SecurityMode Failure (command not accepted by UE) or no answer at all received from UE.

D-Result




E-Type

• VS.FailedRrcSmc.VS.FailedRrcSmc.WithCoreNetworkCs

• VS.FailedRrcSmc.VS.FailedRrcSmc.WithCoreNetworkPs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

event

K-Available Release

V3.0

L-Aggregation Rule

Rtotal



5.9 Paging

The purpose of the Paging Procedure is to enable the Core Network (CN) to page a UE for a UEterminating service request. The procedure uses connectionless signalling. Type 1 pages are for UEsin RRC states: idle, Cell_PCH and URA_PCH. Type 2 pages are for UEs in RRC states: Cell DCHand Cell_FACH.


Counter name

#801 VS.ReceivedPagingRequest

#802 VS.ReceivedPagingRequestType2CellDch

#803 VS.ReceivedPagingRequestType2CellFach

#805 VS.PagingMessagesSentOnPcch

#807 VS.PagingCancelledRecords

#808 VS.PagingRejectedRequests

#809 VS.PagingDelayedRecords

#810 VS.UnhandledPagingRequestsCs

#811 VS.UnhandledPagingRequestsPs

#812 VS.PagingRecordsSentOnPcchCs

#813 VS.PagingRecordsSentOnPcchPs

#814 VS.PagingRecordsUnscheduledCs

#815 VS.PagingRecordsUnscheduledPs

#816 VS.PagingRecordsType2SentCs

#817 VS.PagingRecordsType2SentPs

#818 VS.PagingRecordsType2PagCauseCs

#819 VS.PagingRequestsIuPagCauseCs

#820 VS.UtranPagingRecSentOnPcch

Table 222 VS.ReceivedPagingRequest - #801

A-Description

the number of received paging requests screened by Core Network domain (type 1 and type2). Type 1 pagings are sent on PCCH and Type 2 are sent on DCCH.

B-Collection

CUM

CUMulative

C-Condition (Event)



Reception by the RNC of a RANAP_PAGING message from the Core Network.

D-Result

A set of subcounters screened on: Paging error cause

• Sub-Counter #0 : From core network CS

• Sub-Counter #1 : From core network PS

• Sub-Counter #2 : From core network CS with invalid LAC

• Sub-Counter #3 : From core network PS with invalid RAC

E-Type

• VS.ReceivedPagingRequest.VS.ReceivedPagingRequest.WithCoreNetworkCs

• VS.ReceivedPagingRequest.VS.ReceivedPagingRequest.WithCoreNetworkPs

• VS.ReceivedPagingRequest.VS.ReceivedPagingRequest.FromCoreNwCsInvalidLac

• VS.ReceivedPagingRequest.VS.ReceivedPagingRequest.WithCoreNwPsInvalidRac

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V1.0

L-Aggregation Rule

Rtotal

Table 223 VS.ReceivedPagingRequestType2CellDch - #802

A-Description

the number of received Type 2 paging requests for UEs in CELL_DCH state, screened by CoreNetwork domain. This paging is sent on DCCH (instead of PCCH).

B-Collection

CUM



CUMulative

C-Condition (Event)

Reception by the RNC of a RANAP_PAGING message from the Core Network for an UE inCELL_DCH state.

D-Result




E-Type

• VS.ReceivedPagingRequestType2CellDch.VS.ReceivedPagingRequestType2CellDch.WithCoreNetworkCs

• VS.ReceivedPagingRequestType2CellDch.VS.ReceivedPagingRequestType2CellDch.WithCoreNetworkPs

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 224 VS.ReceivedPagingRequestType2CellFach - #803

A-Description

the number of received Type 2 paging requests for UEs in CELL_FACH state, screened byCore Network domain. This paging is sent on DCCH (instead of PCCH).

B-Collection

CUM



CUMulative

C-Condition (Event)

Reception by the RNC of a Type 2 RANAP_PAGING message from the Core Network for anUE in CELL_FACH state.

D-Result




E-Type

• VS.ReceivedPagingRequestType2CellFach.VS.ReceivedPagingRequestType2CellFach.WithCoreNetworkCs

• VS.ReceivedPagingRequestType2CellFach.VS.ReceivedPagingRequestType2CellFach.WithCoreNetworkPs

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 225 VS.PagingMessagesSentOnPcch - #805

A-Description

the number of paging messages sent on PCCH (one paging message may contain up to 8 pa-ging records, for different mobiles; fresh pagings have priority on repeated pagings).

B-Collection

CUM



CUMulative

C-Condition (Event)

Emission of a paging message on the PCCH of the cell, taking into account paging repetitions.When paging repetition is not activated, for a given UE the paging record is scheduled once,but can be packed with other paging records in the same paging message. When paging repe-tition is activated, the paging message may contain fresh paging records for different mobilesas well as repeated paging records.

D-Result

one measurement

E-Type

VS.PagingMessagesSentOnPcch

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 226 VS.PagingCancelledRecords - #807

A-Description

Decision to cancel a particular paging record : pre-emption by a higher priority paging (freshpaging vs repeated paging) or Iub timing adjustment leading to a gap in CFN sequence(skipping some paging occasions). In the absence of radio paging repetition, a particular pa-ging record that has been scheduled, could be later cancelled because due to Iub timing ad-justments leading to gap in CFN sequence there were no paging occasion available to transmitit on the PCCH on the appropriate occasion. When radio paging repetition is activated, freshpaging getting higher priority, if there is no room available on the paging occasion, the sched-uled paging records associated to repetitions may be cancelled.



B-Collection

CUM

CUMulative

C-Condition (Event)

Decision to cancel a particular paging record : pre-emption by a higher priority paging (freshpaging vs repeated paging) or Iub timing adjustment leading to a gap in CFN sequence(skipping some paging occasions).

D-Result

one measurement

E-Type

VS.PagingCancelledRecords

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 227 VS.PagingRejectedRequests - #808

A-Description

the number of paging requests that are rejected.

B-Collection

CUM

CUMulative

C-Condition (Event)



Decision to reject a particular paging request. request coming from Core Network due to intern-al reason.

D-Result

one measurement

E-Type

VS.PagingRejectedRequests

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 228 VS.PagingDelayedRecords - #809

A-Description

the number of paging records, that are delayed before being sent.

B-Collection

CUM

CUMulative

C-Condition (Event)

Decision to delay a particular paging record because the first paging occasion was full Afterhaving been successfully scheduled, the paging record was not transmitted in a paging mes-sage at the first paging occasion: there was not enough room available in the paging messagefor this record.

D-Result



one measurement

E-Type

VS.PagingDelayedRecords

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 229 VS.UnhandledPagingRequestsCs - #810

A-Description

the number of CS paging type 1 requests that have been not handled by RNC (meaning notbeen scheduled at all).

B-Collection

CUM

CUMulative

C-Condition (Event)

Decision to not schedule a Cs paging request; due to internal reason

D-Result

A set of subcounters screened on: Cause for message not being sent

• Sub-Counter #0 : Invalid Format

• Sub-Counter #1 : Invalid Information

• Sub-Counter #2 : Reset in Progress

• Sub-Counter #3 : Internal resources not available



• Sub-Counter #4 : Overload Controls


E-Type

• VS.UnhandledPagingRequestsCs.VS.UnhandledPagingRequestsCs.InvalidFormat

• VS.UnhandledPagingRequestsCs.VS.UnhandledPagingRequestsCs.InvalidInformation

• VS.UnhandledPagingRequestsCs.VS.UnhandledPagingRequestsCs.ResetInProgress

• VS.UnhandledPagingRequestsCs.VS.UnhandledPagingRequestsCs.InternalResourcesNotAvailable

• VS.UnhandledPagingRequestsCs.VS.UnhandledPagingRequestsCs.OverloadControls

• VS.UnhandledPagingRequestsCs.VS.UnhandledPagingRequestsCs.OtherCause

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.0

L-Aggregation Rule

Rtotal

Table 230 VS.UnhandledPagingRequestsPs - #811

A-Description

the number of PS paging type 1 requests that have been not handled by RNC (meaning notbeen scheduled at all).

B-Collection

CUM

CUMulative

C-Condition (Event)



Decision to not schedule a Ps paging request; due to internal reason

D-Result

A set of subcounters screened on: Cause for message not being sent

• Sub-Counter #0 : Invalid Format

• Sub-Counter #1 : Invalid Information

• Sub-Counter #2 : Reset in Progress

• Sub-Counter #3 : Internal resources not available

• Sub-Counter #4 : Overload Controls


E-Type

• VS.UnhandledPagingRequestsPs.VS.UnhandledPagingRequestsPs.InvalidFormat

• VS.UnhandledPagingRequestsPs.VS.UnhandledPagingRequestsPs.InvalidInformation

• VS.UnhandledPagingRequestsPs.VS.UnhandledPagingRequestsPs.ResetInProgress

• VS.UnhandledPagingRequestsPs.VS.UnhandledPagingRequestsPs.InternalResourcesNotAvailable

• VS.UnhandledPagingRequestsPs.VS.UnhandledPagingRequestsPs.OverloadControls

• VS.UnhandledPagingRequestsPs.VS.UnhandledPagingRequestsPs.OtherCause

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.0

L-Aggregation Rule

Rtotal

Table 231 VS.PagingRecordsSentOnPcchCs - #812



A-Description

the number of paging records sent on PCCH coming from the CS domain (one paging recordmay be packed with up to 7 other paging records for different mobiles in one paging message,where packing fresh pagings records has priority over packing repeated pagings).

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission on the PCCH of the cell of the last paging message that contains a particular pagingrecord for CS domain. The paging record shall be transmitted at the right paging occasion.When paging repetition is not activated, this counter represents the transmission on the radioof the record, packed in a paging message. When paging repetition is activated, this counterrepresents the total number of transmissions of the record, initial transmission and repetitions.

D-Result

A set of subcounters screened on: Paging Cause (25.331)

• Sub-Counter #0 : terminating conversational call

• Sub-Counter #1 : terminating streaming call

• Sub-Counter #2 : terminating interactive call

• Sub-Counter #3 : terminating background call

• Sub-Counter #4 : terminating high priority signalling

• Sub-Counter #5 : terminating low priority signalling

• Sub-Counter #6 : terminating cause unknown

E-Type

• VS.PagingRecordsSentOnPcchCs.VS.PagingRecordsSentOnPcchCs.TerminatingConversationalCall

• VS.PagingRecordsSentOnPcchCs.VS.PagingRecordsSentOnPcchCs.TerminatingStreamingCall

• VS.PagingRecordsSentOnPcchCs.VS.PagingRecordsSentOnPcchCs.TerminatingInteractiveCall

• VS.PagingRecordsSentOnPcchCs.VS.PagingRecordsSentOnPcchCs.TerminatingBackgroundCall

• VS.PagingRecordsSentOnPcchCs.VS.PagingRecordsSentOnPcchCs.TerminatingHighPrioritySignalling

• VS.PagingRecordsSentOnPcchCs.VS.PagingRecordsSentOnPcchCs.TerminatingLowPrioritySignalling

• VS.PagingRecordsSentOnPcchCs.VS.PagingRecordsSentOnPcchCs.TerminatingCauseUnknown

F-Object Instance



Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.0

L-Aggregation Rule

Rtotal

Table 232 VS.PagingRecordsSentOnPcchPs - #813

A-Description

the number of paging records sent on PCCH coming from the PS domain (one paging recordmay be packed with up to 7 other paging records for different mobiles in one paging message,where packing fresh pagings records has priority over packing repeated pagings).

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission on the PCCH of the cell of the last paging message that contains a particular pagingrecord (PS domain).

D-Result











E-Type

• VS.PagingRecordsSentOnPcchPs.VS.PagingRecordsSentOnPcchPs.TerminatingConversationalCall

• VS.PagingRecordsSentOnPcchPs.VS.PagingRecordsSentOnPcchPs.TerminatingStreamingCall

• VS.PagingRecordsSentOnPcchPs.VS.PagingRecordsSentOnPcchPs.TerminatingInteractiveCall

• VS.PagingRecordsSentOnPcchPs.VS.PagingRecordsSentOnPcchPs.TerminatingBackgroundCall

• VS.PagingRecordsSentOnPcchPs.VS.PagingRecordsSentOnPcchPs.TerminatingHighPrioritySignalling

• VS.PagingRecordsSentOnPcchPs.VS.PagingRecordsSentOnPcchPs.TerminatingLowPrioritySignalling

• VS.PagingRecordsSentOnPcchPs.VS.PagingRecordsSentOnPcchPs.TerminatingCauseUnknown

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 233 VS.PagingRecordsUnscheduledCs - #814

A-Description

the number of unscheduled paging records, i.e. paging records that have invalid format or cannot be scheduled because all paging occasions were full. It only considers paging coming fromthe CS domain.

B-Collection



CUM

CUMulative

C-Condition (Event)

Decision not to schedule a particular CS paging record : paging with an invalid format or all pa-ging occasions were full UTRAN may page several UEs in the same paging occasion by in-cluding one IE "Paging record" for each UE in the PAGING TYPE 1 message and transmittinga PAGING TYPE 1 message on an appropriate paging occasion on the PCCH. If the system isheavily loaded on paging, paging record for an UE could not be scheduled. Scheduling a pa-ging record is the first step. If paging repetition is activated, the number of unscheduled pagingrecords encompasses the missed first transmission of a paging record, as well as the missedrepetitions.

D-Result









E-Type

• VS.PagingRecordsUnscheduledCs.VS.PagingRecordsUnscheduledCs.TerminatingConversationalCall

• VS.PagingRecordsUnscheduledCs.VS.PagingRecordsUnscheduledCs.TerminatingStreamingCall

• VS.PagingRecordsUnscheduledCs.VS.PagingRecordsUnscheduledCs.TerminatingInteractiveCall

• VS.PagingRecordsUnscheduledCs.VS.PagingRecordsUnscheduledCs.TerminatingBackgroundCall

• VS.PagingRecordsUnscheduledCs.VS.PagingRecordsUnscheduledCs.TerminatingHighPrioritySignalling

• VS.PagingRecordsUnscheduledCs.VS.PagingRecordsUnscheduledCs.TerminatingLowPrioritySignalling

• VS.PagingRecordsUnscheduledCs.VS.PagingRecordsUnscheduledCs.TerminatingCauseUnknown

F-Object Instance

Cell



G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.0

L-Aggregation Rule

Rtotal

Table 234 VS.PagingRecordsUnscheduledPs - #815

A-Description

the number of unscheduled paging records, i.e. paging records that have invalid format or cannot be scheduled because all paging occasions were full. It only consider pagings coming fromPS domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Decision not to schedule a particular PS paging record : paging with an invalid format or all pa-ging occasions were full

D-Result









E-Type



• VS.PagingRecordsUnscheduledPs.VS.PagingRecordsUnscheduledPs.TerminatingConversationalCall

• VS.PagingRecordsUnscheduledPs.VS.PagingRecordsUnscheduledPs.TerminatingStreamingCall

• VS.PagingRecordsUnscheduledPs.VS.PagingRecordsUnscheduledPs.TerminatingInteractiveCall

• VS.PagingRecordsUnscheduledPs.VS.PagingRecordsUnscheduledPs.TerminatingBackgroundCall

• VS.PagingRecordsUnscheduledPs.VS.PagingRecordsUnscheduledPs.TerminatingHighPrioritySignalling

• VS.PagingRecordsUnscheduledPs.VS.PagingRecordsUnscheduledPs.TerminatingLowPrioritySignalling

• VS.PagingRecordsUnscheduledPs.VS.PagingRecordsUnscheduledPs.TerminatingCauseUnknown

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.0

L-Aggregation Rule

Rtotal

Table 235 VS.PagingRecordsType2SentCs - #816

A-Description

the number of type 2 pages (UE in connected mode) sent to a UE having this cell as referencecell. It only considers paging coming from CS domain.

B-Collection

CUM

CUMulative



C-Condition (Event)

Sending of a type 2 paging record to a UE for Core Network CS.

D-Result

A set of subcounters screened on: Paging Cause








E-Type

• VS.PagingRecordsType2SentCs.VS.PagingRecordsType2SentCs.TerminatingConversationalCall

• VS.PagingRecordsType2SentCs.VS.PagingRecordsType2SentCs.TerminatingStreamingCall

• VS.PagingRecordsType2SentCs.VS.PagingRecordsType2SentCs.TerminatingInteractiveCall

• VS.PagingRecordsType2SentCs.VS.PagingRecordsType2SentCs.TerminatingBackgroundCall

• VS.PagingRecordsType2SentCs.VS.PagingRecordsType2SentCs.TerminatingHighPrioritySignalling

• VS.PagingRecordsType2SentCs.VS.PagingRecordsType2SentCs.TerminatingLowPrioritySignalling

• VS.PagingRecordsType2SentCs.VS.PagingRecordsType2SentCs.TerminatingCauseUnknown

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V4.0

L-Aggregation Rule

Rtotal

Table 236 VS.PagingRecordsType2SentPs - #817

A-Description

the number of type 2 pagings (UE in connected mode) sent to a UE having this cell as refer-ence cell. It only considers paging coming from PS domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a type 2 paging record to a UE for Core Network PS.

D-Result









E-Type

• VS.PagingRecordsType2SentPs.VS.PagingRecordsType2SentPs.TerminatingConversationalCall

• VS.PagingRecordsType2SentPs.VS.PagingRecordsType2SentPs.TerminatingStreamingCall

• VS.PagingRecordsType2SentPs.VS.PagingRecordsType2SentPs.TerminatingInteractiveCall

• VS.PagingRecordsType2SentPs.VS.PagingRecordsType2SentPs.TerminatingBackgroundCall

• VS.PagingRecordsType2SentPs.VS.PagingRecordsType2SentPs.TerminatingHighPrioritySignalling



• VS.PagingRecordsType2SentPs.VS.PagingRecordsType2SentPs.TerminatingLowPrioritySignalling

• VS.PagingRecordsType2SentPs.VS.PagingRecordsType2SentPs.TerminatingCauseUnknown

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.0

L-Aggregation Rule

Rtotal

Table 237 VS.PagingRecordsType2PagCauseCs - #818

A-Description

Number of paging request messages received on an Iu CS per paging cause.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a RANAP/Paging Request message on an IU CS

D-Result











E-Type

• VS.PagingRecordsType2PagCauseCs.VS.PagingRecordsType2PagCauseCs.TerminatingConversationalCall

• VS.PagingRecordsType2PagCauseCs.VS.PagingRecordsType2PagCauseCs.TerminatingStreamingCall

• VS.PagingRecordsType2PagCauseCs.VS.PagingRecordsType2PagCauseCs.TerminatingInteractiveCall

• VS.PagingRecordsType2PagCauseCs.VS.PagingRecordsType2PagCauseCs.TerminatingBackgroundCall

• VS.PagingRecordsType2PagCauseCs.VS.PagingRecordsType2PagCauseCs.TerminatingHighPrioritySignalling

• VS.PagingRecordsType2PagCauseCs.VS.PagingRecordsType2PagCauseCs.TerminatingLowPrioritySignalling

• VS.PagingRecordsType2PagCauseCs.VS.PagingRecordsType2PagCauseCs.TerminatingCauseUnknown

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 238 VS.PagingRequestsIuPagCauseCs - #819

A-Description



Number of paging request messages received on an Iu CS per paging cause. Screenings forPS shall always be zero for this counter. Not present in last FRS PM27729, thus not implemen-ted.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a RANAP/Paging Request message on an IU CS

D-Result









E-Type

• VS.PagingRequestsIuPagCauseCs.VS.PagingRequestsIuPagCauseCs.TerminatingConversationalCall

• VS.PagingRequestsIuPagCauseCs.VS.PagingRequestsIuPagCauseCs.TerminatingStreamingCall

• VS.PagingRequestsIuPagCauseCs.VS.PagingRequestsIuPagCauseCs.TerminatingInteractiveCall

• VS.PagingRequestsIuPagCauseCs.VS.PagingRequestsIuPagCauseCs.TerminatingBackgroundCall

• VS.PagingRequestsIuPagCauseCs.VS.PagingRequestsIuPagCauseCs.TerminatingHighPrioritySignalling

• VS.PagingRequestsIuPagCauseCs.VS.PagingRequestsIuPagCauseCs.TerminatingLowPrioritySignalling

• VS.PagingRequestsIuPagCauseCs.VS.PagingRequestsIuPagCauseCs.TerminatingCauseUnknown

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 239 VS.UtranPagingRecSentOnPcch - #820

A-Description

Number of UTRAN initiated pagings type 1 sent on the PCCH of the cell

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending the first or last UTRAN paging type 1 message (using URNTI) that contains a particu-lar paging record

D-Result

A set of subcounters screened on: RRC state of mobile paged

• Sub-Counter #0 : CELL_PCH

• Sub-Counter #1 : URA_PCH

E-Type

• VS.UtranPagingRecSentOnPcch.VS.UtranPagingRecSentOnPcch.CellPch

• VS.UtranPagingRecSentOnPcch.VS.UtranPagingRecSentOnPcch.UraPch

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.10 Mobility

The reference documents for location management are 3GPP TS25.413 Iu Interface RANAPSignaling UMT/SYS/DD/0158 Location Services - GPS based UE positioning. UMT/SYS/DD/0160Location services - UE positioning solutions for UMTS Access


Counter name

#901 VS.NbrCellUpdates

#902 VS.NbrCellUpdateRejects

#903 VS.CsLocationReportingControlDefaultLs

#913 VS.CsLocationUebasedAgpsSuccess

#914 VS.CsLocationUebasedAgpsUnsuccess

#915 VS.UeLocationUebasedAgpsSuccess

#916 VS.UeLocationUebasedAgpsSuccessNeighbRnc

#917 VS.UeLocationUebasedAgpsUnsuccess

#918 VS.UeLocationUebasedAgpsUnsuccessNeighbRnc

#919 VS.PsLocationUeBasedAgpsSuccess

#920 VS.PsLocationUebasedAgpsUnsuccess

#921 VS.PsLocationReportingControlGeoLs

#922 VS.PsLocationReportSuccessGeoLsWithinQos

#923 VS.PsLocationReportSuccessGeoLsOutsideQos

#924 VS.PsLocationReportUnsuccessGeoLs

#925 VS.CsLocationReportSuccessGeoLsOutsideQos

#926 VS.CsLocationReportingControlGeoLs

#927 VS.PsLocationReportingControlSaLs

#928 VS.CsLocationReportSuccessSaLs

#929 VS.CsLocationReportUnsuccessSaLs

#930 VS.CsLocationReportSuccessGeoLsWithinQoS

#931 VS.CsLocationReportUnsuccessGeoLs

#932 VS.PsLocationReportSuccessSaLs

#933 VS.PsLocationReportUnsuccessSaLs

#934 VS.RrcAvgNbrCellPch

#935 VS.RrcAvgNbrUraPch

#936 VS.RrcAvgNbrCellFachRnc

#937 VS.NbrUraUpdates

#938 VS.NbrUraUpdatesRej




Counter name

#939 VS.RrcTransCellPchToUraPch

#940 VS.RrcTransDchToPch

#950 VS.HsdpaMobilitySuccess

#951 VS.HsdpaMobilityUnsuccessful

#952 VS.HsdpaCellDeletion

#953 VS.HsdpaDCHToHsdpaTransSucc

#954 VS.HsdpaToDCHSucc

#955 VS.DCHToHsdpaUnsuccessful

#956 VS.HsdpaToDCHUnsuccessful

#957 VS.HsdpaCACSuccess

#958 VS.HsdpaCACUnsuccessful

#959 VS.HsdpaIuRelAbnormal

#960 VS.EdchSucMobility

#961 VS.EdchUnsucMobility

#962 VS.EdchCellDeletion

#963 VS.EdchIuRelAbnormal

Table 240 VS.NbrCellUpdates - #901

A-Description

Number of successful Cell Updates

B-Collection

CUM

CUMulative

C-Condition (Event)

RRC Cell Update

D-Result

A set of subcounters screened on: Cell Update Cause

• Sub-Counter #0 : Cell Reselection

• Sub-Counter #1 : Periodic Cell Update

• Sub-Counter #2 : Uplink Data Transmission

• Sub-Counter #3 : Paging Response

• Sub-Counter #4 : Re-entered Service Area

• Sub-Counter #5 : Radio Link Failure

• Sub-Counter #6 : RLC Unrecoverable Error



E-Type

• VS.NbrCellUpdates.VS.NbrCellUpdates.CellReselection

• VS.NbrCellUpdates.VS.NbrCellUpdates.PeriodicCellUpdate

• VS.NbrCellUpdates.VS.NbrCellUpdates.UplinkDataTransmission

• VS.NbrCellUpdates.VS.NbrCellUpdates.PagingResponse

• VS.NbrCellUpdates.VS.NbrCellUpdates.ReenteredServiceArea

• VS.NbrCellUpdates.VS.NbrCellUpdates.RadioLinkFailure

• VS.NbrCellUpdates.VS.NbrCellUpdates.RlcUnrecoverableError

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 241 VS.NbrCellUpdateRejects - #902

A-Description

Number of rejected Cell Updates

B-Collection

CUM

CUMulative

C-Condition (Event)

RRC Cell Update Failure

D-Result



A set of subcounters screened on: Cell Update Failure Cause

• Sub-Counter #0 : Unknown u-RNTI

• Sub-Counter #1 : Incorrect Message

• Sub-Counter #2 : Aborted by a newer CELL UPDATE


• Sub-Counter #4 : FACH CAC failure

E-Type

• VS.NbrCellUpdateRejects.VS.NbrCellUpdateRejects.UnknownURNTI

• VS.NbrCellUpdateRejects.VS.NbrCellUpdateRejects.IncorrectMessage

• VS.NbrCellUpdateRejects.VS.NbrCellUpdateRejects.AbortedByANewerCellUpdate

• VS.NbrCellUpdateRejects.VS.NbrCellUpdateRejects.Other

• VS.NbrCellUpdateRejects.VS.NbrCellUpdateRejects.FachCacFailure

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 242 VS.CsLocationReportingControlDefaultLs - #903

A-Description

the number of RANAP Location Reporting Control messages received from the CS Core Net-work for geographical purposed and served with a default location service.

B-Collection

CUM



CUMulative

C-Condition (Event)

Reception from the Circuit Core of a valid RANAP Location Reporting Control message withReport Area message parameter set to 'Geographical Area' and selection of Defaut Locationservice.

D-Result

one measurement

E-Type

VS.CsLocationReportingControlDefaultLs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.2

L-Aggregation Rule

Rtotal

Table 243 VS.CsLocationUebasedAgpsSuccess - #913

A-Description

the number of sucessful location estimations performed using UE-based AGPS method, for CSdomain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Succesful position estimate with UE-based AGPS method and sending to the Circuit Core of a



RANAP Location Report.

D-Result

one measurement

E-Type

VS.CsLocationUebasedAgpsSuccess

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.2

L-Aggregation Rule

Rtotal

Table 244 VS.CsLocationUebasedAgpsUnsuccess - #914

A-Description

the number of unsucessful location estimations performed using UE-based AGPS method, forCS domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Failed position estimate with UE-based AGPS method.

D-Result

A set of subcounters screened on: Unsuccess Cause

• Sub-Counter #0 : SAS Services not available

• Sub-Counter #1 : SAS PCAP failure



• Sub-Counter #2 : UE positioning error

• Sub-Counter #3 : AGPS UE-based too long


E-Type

• VS.CsLocationUebasedAgpsUnsuccess.VS.CsLocationUebasedAgpsUnsuccess.SasServicesNotAvailable

• VS.CsLocationUebasedAgpsUnsuccess.VS.CsLocationUebasedAgpsUnsuccess.SasPcapFailure

• VS.CsLocationUebasedAgpsUnsuccess.VS.CsLocationUebasedAgpsUnsuccess.UePositiniongError

• VS.CsLocationUebasedAgpsUnsuccess.VS.CsLocationUebasedAgpsUnsuccess.AgpsUEbasedTooLong

• VS.CsLocationUebasedAgpsUnsuccess.VS.CsLocationUebasedAgpsUnsuccess.Other

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.2

L-Aggregation Rule

Rtotal

Table 245 VS.UeLocationUebasedAgpsSuccess - #915

A-Description

Number of succeeded location of the UE using the UE-based AGPS technology, when the ref-erence cell is located on Serving RNC

B-Collection

CUM



CUMulative

C-Condition (Event)

RRC MEASUREMENT REPORT with UE position estimate

D-Result

A set of subcounters screened on: Accuracy Estimate

• Sub-Counter #0 : UE estimated accuracy better than 50m

• Sub-Counter #1 : UE estimated accuracy between 50m and 150m

• Sub-Counter #2 : UE estimated accurary worse than 150m

E-Type

• VS.UeLocationUebasedAgpsSuccess.VS.UeLocationUebasedAgpsSuccess.UeEstimatedAccuracyBetterThan50m

• VS.UeLocationUebasedAgpsSuccess.VS.UeLocationUebasedAgpsSuccess.UeEstimatedAccuracyBetween50mAnd150m

• VS.UeLocationUebasedAgpsSuccess.VS.UeLocationUebasedAgpsSuccess.UeEstimatedAccuraryWorseThan150m

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.2

L-Aggregation Rule

Rtotal

Table 246 VS.UeLocationUebasedAgpsSuccessNeighbRnc - #916

A-Description

the number of sucessful location estimations performed using UE-based AGPS method, whenthe reference cell is under the control of a drift RNC. In UA03.2, only CS domain is supported



for UE-based AGPS method.

B-Collection

CUM

CUMulative

C-Condition (Event)

Succesful position estimate with UE-based AGPS method and sending to the Core Network ofa RANAP Location Report.

D-Result

A set of subcounters screened on: Accuracy Estimate

• Sub-Counter #0 : UE estimated accuracy better than 50m

• Sub-Counter #1 : UE estimated accuracy between 50m and 150m

• Sub-Counter #2 : UE estimated accurary worse than 150m

E-Type

• VS.UeLocationUebasedAgpsSuccessNeighbRnc.VS.UeLocationUebasedAgpsSuccessNeighbRnc.UeEstimatedAccuracyBetterThan50m

• VS.UeLocationUebasedAgpsSuccessNeighbRnc.VS.UeLocationUebasedAgpsSuccessNeighbRnc.UeEstimatedAccuracyBetween50mAnd150m

• VS.UeLocationUebasedAgpsSuccessNeighbRnc.VS.UeLocationUebasedAgpsSuccessNeighbRnc.UeEstimatedAccuraryWorseThan150m

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.2

L-Aggregation Rule

Rtotal



Table 247 VS.UeLocationUebasedAgpsUnsuccess - #917

A-Description

the number of unsucessful location estimations performed using UE-based AGPS method, andwith the reference cell under the control of the serving RNC. In UA03.2, only CS domain is sup-ported for UE-based AGPS method.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result







E-Type

• VS.UeLocationUebasedAgpsUnsuccess.VS.UeLocationUebasedAgpsUnsuccess.SasServicesNotAvailable

• VS.UeLocationUebasedAgpsUnsuccess.VS.UeLocationUebasedAgpsUnsuccess.SasPcapFailure

• VS.UeLocationUebasedAgpsUnsuccess.VS.UeLocationUebasedAgpsUnsuccess.UePositiniongError

• VS.UeLocationUebasedAgpsUnsuccess.VS.UeLocationUebasedAgpsUnsuccess.AgpsUEbasedTooLong

• VS.UeLocationUebasedAgpsUnsuccess.VS.UeLocationUebasedAgpsUnsuccess.Other

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

event

K-Available Release

V3.2

L-Aggregation Rule

Rtotal

Table 248 VS.UeLocationUebasedAgpsUnsuccessNeighbRnc - #918

A-Description

the number of unsucessful location estimations performed using UE-based AGPS method, andwith the reference cell under the control of a drift RNC. In UA03.2, only CS domain is suppor-ted for UE-based AGPS method.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result







E-Type

• VS.UeLocationUebasedAgpsUnsuccessNeighbRnc.VS.UeLocationUebasedAgpsUnsuccessNeighbRnc.SasServicesNotAvailable

• VS.UeLocationUebasedAgpsUnsuccessNeighbRnc.VS.UeLocationUebasedAgpsUnsuccessNeighbRnc.SasPcapFailure

• VS.UeLocationUebasedAgpsUnsuccessNeighbRnc.VS.UeLocationUebasedAgpsUnsuccessNeighbRnc.UePositiniongError

• VS.UeLocationUebasedAgpsUnsuccessNeighbRnc.VS.UeLocationUebasedAgpsUnsuccessNeighbRnc.AgpsUEbasedTooLong

• VS.UeLocationUebasedAgpsUnsuccessNeighbRnc.VS.UeLocationUebasedAgpsUnsuccessNeighbRnc.Other

F-Object Instance



Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.2

L-Aggregation Rule

Rtotal

Table 249 VS.PsLocationUeBasedAgpsSuccess - #919

A-Description

the number of sucessful location estimations performed using UE-based AGPS method, for PSdomain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Succesful position estimate with UE-based AGPS method and sending to the Circuit Core of aRANAP Location Report.

D-Result

one measurement

E-Type

VS.PsLocationUeBasedAgpsSuccess

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 250 VS.PsLocationUebasedAgpsUnsuccess - #920

A-Description

the number of unsucessful location estimations performed using UE-based AGPS method, forPS domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result







E-Type

• VS.PsLocationUebasedAgpsUnsuccess.VS.PsLocationUebasedAgpsUnsuccess.SasServicesNotAvailable

• VS.PsLocationUebasedAgpsUnsuccess.VS.PsLocationUebasedAgpsUnsuccess.SasPcapFailure

• VS.PsLocationUebasedAgpsUnsuccess.VS.PsLocationUebasedAgpsUnsuccess.UePositiniongError

• VS.PsLocationUebasedAgpsUnsuccess.VS.PsLocationUebasedAgpsUnsuccess.AgpsUEbasedTooLong



• VS.PsLocationUebasedAgpsUnsuccess.VS.PsLocationUebasedAgpsUnsuccess.Other

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 251 VS.PsLocationReportingControlGeoLs - #921

A-Description

the number of RANAP Location Reporting Control messages received from the PS Core Net-work for geographical area purpose and served with a geographical location service.

B-Collection

CUM

CUMulative

C-Condition (Event)

RANAP LOCATION REPORTING CONTROL received from PS domain with report area set togeographical area

D-Result

one measurement

E-Type

VS.PsLocationReportingControlGeoLs

F-Object Instance

RNC

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 252 VS.PsLocationReportSuccessGeoLsWithinQos - #922

A-Description

the number of RANAP Location Report messages for geographical purpose sent to the PS do-main served by Geographical Location Service and which satisfy requested QoS. The counteris screened according to the UE positioning method used to locate the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful position estimate (geographical) and RANAP LOCATION REPORT message sentto Packet Core.

D-Result

A set of subcounters screened on: Location Method

• Sub-Counter #0 : UE_BASED_AGPS

• Sub-Counter #1 : Cell Id

E-Type

• VS.PsLocationReportSuccessGeoLsWithinQos.VS.PsLocationReportSuccessGeoLsWithinQos.UeBasedAgps

• VS.PsLocationReportSuccessGeoLsWithinQos.VS.PsLocationReportSuccessGeoLsWithinQos.CellId

F-Object Instance

RNC



G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 253 VS.PsLocationReportSuccessGeoLsOutsideQos - #923

A-Description

Number of RANAP Location Report messages for geographical purpose sent to the PS domainserved by an Geographical Location Service and which do not satisfy requested QoS. Thecounter is screened according to the UE positioning method used to locate the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful position estimate (geographical) and RANAP LOCATION REPORT message sentto Packet Core

D-Result




E-Type

• VS.PsLocationReportSuccessGeoLsOutsideQos.VS.PsLocationReportSuccessGeoLsOutsideQos.UeBasedAgps

• VS.PsLocationReportSuccessGeoLsOutsideQos.VS.PsLocationReportSuccessGeoLsOutsideQos.CellId

F-Object Instance



RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 254 VS.PsLocationReportUnsuccessGeoLs - #924

A-Description

Number of RANAP Location Report messages for geographical purpose sent to the PS domainfailed and that were supposed to be served by a Geographical Location Service.

B-Collection

CUM

CUMulative

C-Condition (Event)

Conditions applicable to screening 0, 1 & 4: Unsuccessful position estimate (geographical) andRANAP LOCATION REPORT message sent to Packet Core with a failure cause. Condition ap-plicable to screening 2 & 3: Unsuccessful position estimate (geographical).

D-Result


• Sub-Counter #0 : Local Cell Info Not Found

• Sub-Counter #1 : Distant Cell Info Not Found

• Sub-Counter #2 : Relocation_procedure

• Sub-Counter #3 : Abort Procedure

• Sub-Counter #4 : Unknown

E-Type



• VS.PsLocationReportUnsuccessGeoLs.VS.PsLocationReportUnsuccessGeoLs.LocalCellInfoNotFound

• VS.PsLocationReportUnsuccessGeoLs.VS.PsLocationReportUnsuccessGeoLs.DistantCellInfoNotFound

• VS.PsLocationReportUnsuccessGeoLs.VS.PsLocationReportUnsuccessGeoLs.RelocationProcedure

• VS.PsLocationReportUnsuccessGeoLs.VS.PsLocationReportUnsuccessGeoLs.AbortProcedure

• VS.PsLocationReportUnsuccessGeoLs.VS.PsLocationReportUnsuccessGeoLs.Unknown

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 255 VS.CsLocationReportSuccessGeoLsOutsideQos - #925

A-Description

Number of RANAP Location Report messages for geographical purpose sent to the CS domainserved by an Geographical Location Service and which do not satisfy requested QoS. Thecounter is screened according to the UE positioning method used to locate the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful position estimate (geographical) and RANAP LOCATION REPORT message sentto Circuit Core



D-Result




E-Type

• VS.CsLocationReportSuccessGeoLsOutsideQos.VS.CsLocationReportSuccessGeoLsOutsideQos.UeBasedAgps

• VS.CsLocationReportSuccessGeoLsOutsideQos.VS.CsLocationReportSuccessGeoLsOutsideQos.CellId

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 256 VS.CsLocationReportingControlGeoLs - #926

A-Description

the number of CS domain received RANAP Location Reporting Control messages for geo-graphical purpose and served with Geographical Location Service.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception from Circuit Core of a valid RANAP Location Reporting Control message with Re-port Area message parameter set to 'Geographical Area'.



D-Result

one measurement

E-Type

VS.CsLocationReportingControlGeoLs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 257 VS.PsLocationReportingControlSaLs - #927

A-Description

the number of RANAP Location Reporting Control messages received from the PS Core Net-work for geographical purposed and served with a default location service.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception from the Packet Core of a valid RANAP Location Reporting Control message withReport Area message parameter set to 'Geographical Area' and selection of Defaut Locationservice.

D-Result

one measurement

E-Type



VS.PsLocationReportingControlSaLs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 258 VS.CsLocationReportSuccessSaLs - #928

A-Description

This counter provides the number of RANAP Location Report messages for geographical pur-pose to the CS domain served by a Default Location Service (There is no QoS in case of ser-vice area localization. So by default, all these localization are presumed inside QoS).

B-Collection

CUM

CUMulative

C-Condition (Event)

Succesful position estimate and sending to the Circuit Core of a RANAP Location Report mes-sage in response to a request mapped on default LS.

D-Result

one measurement

E-Type

VS.CsLocationReportSuccessSaLs

F-Object Instance

RNC

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 259 VS.CsLocationReportUnsuccessSaLs - #929

A-Description

the number of RANAP failed Location Report messages sent to the CS Core Network for geo-graphical purposed, that were supposed to be served with a default location service.

B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccesful position estimate (geographical) and sending to the Circuit Core of a RANAP Loc-ation Report message with a failure cause in response to a request mapped on default LS.

D-Result





E-Type

• VS.CsLocationReportUnsuccessSaLs.VS.CsLocationReportUnsuccessSaLs.LocalCellInfoNotFound

• VS.CsLocationReportUnsuccessSaLs.VS.CsLocationReportUnsuccessSaLs.DistantCellInfoNotFound

• VS.CsLocationReportUnsuccessSaLs.VS.CsLocationReportUnsuccessSaLs.Unknown

F-Object Instance



RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 260 VS.CsLocationReportSuccessGeoLsWithinQoS - #930

A-Description

the number of RANAP Location Report messages for geographical purpose sent to the CS do-main served by Geographical Location Service and which satisfy requested QoS. The counteris screened according to the UE positioning method used to locate the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful position estimate (geographical) and RANAP LOCATION REPORT message sentto Circuit Core

D-Result




E-Type

• VS.CsLocationReportSuccessGeoLsWithinQoS.VS.CsLocationReportSuccessGeoLsWithinQoS.UeBasedAgps

• VS.CsLocationReportSuccessGeoLsWithinQoS.VS.CsLocationReportSuccessGeoLsWithinQoS.CellId



F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 261 VS.CsLocationReportUnsuccessGeoLs - #931

A-Description

Number of RANAP Location Report messages for geographical purpose sent to the CS domainfailed and that were supposed to be served by a Geographical Location Service.

B-Collection

CUM

CUMulative

C-Condition (Event)

Conditions applicable to screening 0, 1 & 4: Unsuccessful position estimate (geographical) andRANAP LOCATION REPORT message sent to Circuit Core with a failure cause. Condition ap-plicable to screening 2 & 3: Unsuccessful position estimate (geographical).

D-Result




• Sub-Counter #2 : Relocation_procedure

• Sub-Counter #3 : Abort Procedure




E-Type

• VS.CsLocationReportUnsuccessGeoLs.VS.CsLocationReportUnsuccessGeoLs.LocalCellInfoNotFound

• VS.CsLocationReportUnsuccessGeoLs.VS.CsLocationReportUnsuccessGeoLs.DistantCellInfoNotFound

• VS.CsLocationReportUnsuccessGeoLs.VS.CsLocationReportUnsuccessGeoLs.RelocationProcedure

• VS.CsLocationReportUnsuccessGeoLs.VS.CsLocationReportUnsuccessGeoLs.AbortProcedure

• VS.CsLocationReportUnsuccessGeoLs.VS.CsLocationReportUnsuccessGeoLs.Unknown

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 262 VS.PsLocationReportSuccessSaLs - #932

A-Description

the number of RANAP Location Report messages sent to the PS Core Network for geographic-al purposed, served with a default location service (There is no QoS in case of service arealocalization. So by default, all these localization are presumed inside QoS).

B-Collection

CUM

CUMulative

C-Condition (Event)

Succesful position estimate and sending to the Packet Core of a RANAP Location Report mes-



sage in response to a request mapped on default LS.

D-Result

one measurement

E-Type

VS.PsLocationReportSuccessSaLs

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 263 VS.PsLocationReportUnsuccessSaLs - #933

A-Description

the number of RANAP failed Location Report messages sent to the PS Core Network for geo-graphical purposed, that were supposed to be served with a default location service.

B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccesful position estimate (geographical) and sending to the Packet Core of a RANAP Loc-ation Report message with a failure cause in response to a request mapped on default LS.

D-Result







E-Type

• VS.PsLocationReportUnsuccessSaLs.VS.PsLocationReportUnsuccessSaLs.LocalCellInfoNotFound

• VS.PsLocationReportUnsuccessSaLs.VS.PsLocationReportUnsuccessSaLs.DistantCellInfoNotFound

• VS.PsLocationReportUnsuccessSaLs.VS.PsLocationReportUnsuccessSaLs.Unknown

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 264 VS.RrcAvgNbrCellPch - #934

A-Description

Average number of UEs in CELL_PCH RRC state

B-Collection

LOAD

C-Condition (Event)

Various reasons that cause an RRC context to enter or leave the CELL_PCH RRC state.

D-Result

A set of subcounters screened on: CELL_PCH RRC source state

• Sub-Counter #0 : From Cell DCH



• Sub-Counter #1 : From Cell FACH

E-Type

• VS.RrcAvgNbrCellPch.VS.RrcAvgNbrCellPch.FromCellDch

• VS.RrcAvgNbrCellPch.VS.RrcAvgNbrCellPch.FromCellFach

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 265 VS.RrcAvgNbrUraPch - #935

A-Description

Average number of UEs in URA_PCH RRC state

B-Collection

LOAD

C-Condition (Event)

Various reasons that cause an RRC context to enter or leave the URA_PCH RRC state.

D-Result

A set of subcounters screened on: URA_PCH RRC source state


• Sub-Counter #1 : From Cell FACH

• Sub-Counter #2 : From Cell PCH

E-Type



• VS.RrcAvgNbrUraPch.VS.RrcAvgNbrUraPch.FromCellDch

• VS.RrcAvgNbrUraPch.VS.RrcAvgNbrUraPch.FromCellFach

• VS.RrcAvgNbrUraPch.VS.RrcAvgNbrUraPch.FromCellPch

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 266 VS.RrcAvgNbrCellFachRnc - #936

A-Description

Average number of UEs in CELL_FACH RRC state

B-Collection

LOAD

C-Condition (Event)

Various reasons that cause an RRC context to enter or leave the CELL_FACH RRC state.

D-Result

A set of subcounters screened on: CELL_FACH RRC source state


• Sub-Counter #1 : From Cell PCH

• Sub-Counter #2 : From URA PCH

E-Type

• VS.RrcAvgNbrCellFachRnc.VS.RrcAvgNbrCellFachRnc.FromCellDch



• VS.RrcAvgNbrCellFachRnc.VS.RrcAvgNbrCellFachRnc.FromCellPch

• VS.RrcAvgNbrCellFachRnc.VS.RrcAvgNbrCellFachRnc.FromUraPch

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 267 VS.NbrUraUpdates - #937

A-Description

Number of URA Updates received

B-Collection

CUM

CUMulative

C-Condition (Event)

RRC URA Update

D-Result

A set of subcounters screened on: URA Update Cause

• Sub-Counter #0 : Change of URA

• Sub-Counter #1 : Periodic URA Update

E-Type

• VS.NbrUraUpdates.VS.NbrUraUpdates.ChangeUra

• VS.NbrUraUpdates.VS.NbrUraUpdates.PeriodicUraUpdate

F-Object Instance



Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 268 VS.NbrUraUpdatesRej - #938

A-Description

Number of URA Updates rejected

B-Collection

CUM

CUMulative

C-Condition (Event)

RRC Cell Update with invalid parameters

D-Result

A set of subcounters screened on: Cell Update Failure Cause

• Sub-Counter #0 : Unknown u-RNTI

• Sub-Counter #1 : Incorrect Message

• Sub-Counter #2 : FACH CAC failure


E-Type

• VS.NbrUraUpdatesRej.VS.NbrUraUpdatesRej.UnknownURNTI

• VS.NbrUraUpdatesRej.VS.NbrUraUpdatesRej.IncorrectMessage

• VS.NbrUraUpdatesRej.VS.NbrUraUpdatesRej.FachCacFailure

• VS.NbrUraUpdatesRej.VS.NbrUraUpdatesRej.Other



F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 269 VS.RrcTransCellPchToUraPch - #939

A-Description

Number of transitions from CELL_PCH to URA_PCH

B-Collection

CUM

CUMulative

C-Condition (Event)

Transmission of RRC Cell Update Confirm (target RRC state is URA_PCH) to a UE inCELL_PCH RRC state.

D-Result

one measurement

E-Type

VS.RrcTransCellPchToUraPch

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 270 VS.RrcTransDchToPch - #940

A-Description

Number of transitions from CELL_DCH to XXX_PCH

B-Collection

CUM

CUMulative

C-Condition (Event)

Transmission of RRC RB Reconfiguration Request (target RRC state is XXX_PCH) to a UE inCELL_DCH RRC state.

D-Result

one measurement

E-Type

VS.RrcTransDchToPch

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event



K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 271 VS.HsdpaMobilitySuccess - #950

A-Description

Number of successful HSDPA mobility: 1) HSDPA Cell to HSDPA Cell, 2) R99 Cell to HSDPACell, 3) HSDPA Cell to R99 Cell. Reference Cell is new primary cell of call.

B-Collection

CUM

CUMulative

C-Condition (Event)

Change of primary cell for a PS I/B call that is on HSDPA or will be on HSDPA.

D-Result

A set of subcounters screened on: Change of primary cell for a PS I/B call that is on HSDPA orwill be on HSDPA.

• Sub-Counter #0 : HSDPA Cell to HSDPA Cell (intra frequency mobility)

• Sub-Counter #1 : non-HSDPA Cell to HSDPA Cell (intra frequency mobility)

• Sub-Counter #2 : HSDPA Cell to non-HSDPA Cell (intra frequency mobility)

• Sub-Counter #3 : HSDPA Cell to HSDPA Cell (inter frequency mobility)

• Sub-Counter #4 : non-HSDPA Cell to HSDPA Cell (inter frequency mobility)

• Sub-Counter #5 : HSDPA Cell to non-HSDPA Cell (inter frequency mobility)

E-Type

• VS.HsdpaMobilitySuccess.VS.HsdpaMobilitySuccess.HsdpaToHsdpa

• VS.HsdpaMobilitySuccess.VS.HsdpaMobilitySuccess.NonHsdpaToHsdpa

• VS.HsdpaMobilitySuccess.VS.HsdpaMobilitySuccess.HsdpaToNonHsdpa

• VS.HsdpaMobilitySuccess.VS.HsdpaMobilitySuccess.HsdpaToHsdpaInterFreq

• VS.HsdpaMobilitySuccess.VS.HsdpaMobilitySuccess.NonHsdpaToHsdpaInterFreq

• VS.HsdpaMobilitySuccess.VS.HsdpaMobilitySuccess.HsdpaToNonHsdpaInterFreq

F-Object Instance

Cell(Reference)

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 272 VS.HsdpaMobilityUnsuccessful - #951

A-Description

Number of unsuccessful HSDPA mobility: 1) HSDPA Cell to HSDPA Cell, 2) R99 Cell to HS-DPA Cell, 3) HSDPA Cell to R99 Cell. Reference Cell is new primary cell of call.

B-Collection

CUM

CUMulative

C-Condition (Event)

Change of primary cell for a PS I/B call that is on HSDPA or will be on HSDPA.

D-Result

A set of subcounters screened on: Change of primary cell for a PS I/B call that is on HSDPA orwill be on HSDPA.

• Sub-Counter #0 : HSDPA Cell to HSDPA Cell (intra frequency mobility)

• Sub-Counter #1 : non-HSDPA Cell to HSDPA Cell (intra frequency mobility)

• Sub-Counter #2 : HSDPA Cell to non-HSDPA Cell (intra frequency mobility)

• Sub-Counter #3 : HSDPA Cell to HSDPA Cell (inter frequency mobility)

• Sub-Counter #4 : non-HSDPA Cell to HSDPA Cell (inter frequency mobility)

• Sub-Counter #5 : HSDPA Cell to non-HSDPA Cell (inter frequency mobility)

E-Type

• VS.HsdpaMobilityUnsuccessful.VS.HsdpaMobilityUnsuccessful.HsdpaToHsdpa

• VS.HsdpaMobilityUnsuccessful.VS.HsdpaMobilityUnsuccessful.NonHsdpaToHsdpa



• VS.HsdpaMobilityUnsuccessful.VS.HsdpaMobilityUnsuccessful.HsdpaToNonHsdpa

• VS.HsdpaMobilityUnsuccessful.VS.HsdpaMobilityUnsuccessful.HsdpaToHsdpaInterFreq

• VS.HsdpaMobilityUnsuccessful.VS.HsdpaMobilityUnsuccessful.NonHsdpaToHsdpaInterFreq

• VS.HsdpaMobilityUnsuccessful.VS.HsdpaMobilityUnsuccessful.HsdpaToNonHsdpaInterFreq

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 273 VS.HsdpaCellDeletion - #952

A-Description

Number of HSDPA Cell Deletion: the call is then still in a HSDPA state butthere is no more HS-DPA server.

B-Collection

CUM

CUMulative

C-Condition (Event)

SHO algorithm triggering the deletion of the HSDPA Radio Link. Or Radio link failure on theHSDPA RL of an HSDPA call.

D-Result

A set of subcounters screened on: HSDPA Depending on triggering event (1:1 map)

• Sub-Counter #0 : Deletion during Active Set Update



• Sub-Counter #1 : Deletion due to Radio Link failure

E-Type

• VS.HsdpaCellDeletion.VS.HsdpaCellDeletion.ActSetUpd

• VS.HsdpaCellDeletion.VS.HsdpaCellDeletion.RadioLinkFail

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 274 VS.HsdpaDCHToHsdpaTransSucc - #953

A-Description

Number of successful DCH to HSDPA transition

B-Collection

CUM

CUMulative

C-Condition (Event)

Transition happens based on the RAB matching algorithm decision to put the RAB onto HS-DPA. Please note that this counter is also triggered at call establishment when CellDCH isused (that is to say when there is a transition from DCH to HSDPA at call establishment).

D-Result

one measurement

E-Type

VS.HsdpaDCHToHsdpaTransSucc



F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 275 VS.HsdpaToDCHSucc - #954

A-Description

Number of successful HSDPA to DCH transition. This counter is only pegged on RAB estab-lishment or RAB release use cases. Note: - The RAB establishment use case is applicable tomultiservice (i.e PS HSDPA --> PS + (CS or PS)) - The RAB release use case is applicable inmono-service release (i.e. SRB + PS HSDPA --> SRB)

B-Collection

CUM

CUMulative

C-Condition (Event)

Transition happens based on the RAB matching algorithm decision to put the established HS-DPA RAB onto DCH.

D-Result

A set of subcounters screened on: HSDPA-DCH Transition. Depending on triggering event (1:1map)



E-Type

• VS.HsdpaToDCHSucc.VS.HsdpaToDCHSucc.RABSetup



• VS.HsdpaToDCHSucc.VS.HsdpaToDCHSucc.RABRelease

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 276 VS.DCHToHsdpaUnsuccessful - #955

A-Description

Number of unsuccessful DCH to HSDPA transition.This counter is only pegged on RAB estab-lishment or RAB release use cases. Note: - The RAB establishment use case is applicable tomonoservice (i.e SRB --> SRB + PS HSDPA) - The RAB release use case is applicable inmulti-service (i.e.PS + (PS or CS) --> PS)

B-Collection

CUM

CUMulative

C-Condition (Event)

Transition happens based on the RAB matching algorithm decision to put the established RABonto HSDPA.

D-Result




E-Type



• VS.DCHToHsdpaUnsuccessful.VS.DCHToHsdpaUnsuccessful.RABSetup

• VS.DCHToHsdpaUnsuccessful.VS.DCHToHsdpaUnsuccessful.RABRelease

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 277 VS.HsdpaToDCHUnsuccessful - #956

A-Description

Number of unsuccessful HSDPA to DCH transition. This counter is only pegged on RAB estab-lishment or RAB release use cases. Note: - The RAB establishment use case is applicable tomultiservice (i.e PS HSDPA --> PS + (CS or PS)) - The RAB release use case is applicable inmono-service release (i.e. SRB + PS HSDPA --> SRB)

B-Collection

CUM

CUMulative

C-Condition (Event)

Transition happens based on the RAB matching algorithm decision to put the established HS-DPA RAB onto DCH.

D-Result






E-Type

• VS.HsdpaToDCHUnsuccessful.VS.HsdpaToDCHUnsuccessful.RABSetup

• VS.HsdpaToDCHUnsuccessful.VS.HsdpaToDCHUnsuccessful.RABRelease

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 278 VS.HsdpaCACSuccess - #957

A-Description

Number of HSDPA CAC

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful access to the cell for an HSDPA call during mobility, establishment or reconfigura-tion from DCH to HSDPA procedure.

D-Result

one measurement

E-Type

VS.HsdpaCACSuccess

F-Object Instance

Cell(Reference)



G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 279 VS.HsdpaCACUnsuccessful - #958

A-Description

Number of HSDPA CAC

B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccessful access to the cell for an HSDPA call during mobility or establishment procedure.

D-Result

A set of subcounters screened on: Reason for the HSDPA CAC failure

• Sub-Counter #0 : Maximum number of HSDPA users exceeded

• Sub-Counter #1 : Maximum number of Streaming HSDPA users exceeded

• Sub-Counter #2 : Maximum Aggregated GBR exceeded

E-Type

• VS.HsdpaCACUnsuccessful.VS.HsdpaCACUnsuccessful.MaxNumHsdpaUsers

• VS.HsdpaCACUnsuccessful.VS.HsdpaCACUnsuccessful.MaxNumStreamHsdpaUsers

• VS.HsdpaCACUnsuccessful.VS.HsdpaCACUnsuccessful.MaxAggGBR

F-Object Instance

Cell(Reference)

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 280 VS.HsdpaIuRelAbnormal - #959

A-Description

Number of Iu release requested for an HSDPA call. This may happen after a HSDPA credit al-location protocol error, a CAC rejection during a mobility phase or another failure during themobility phase. (NBAP or RRC).

B-Collection

CUM

CUMulative

C-Condition (Event)

Happens on any failure that requests Iu release of call due to failure to access cell in HSDPAstate, or due to failure on flow control.

D-Result

A set of subcounters screened on: HSDPA - abnormal IU release. Depending on triggeringevent (1:1 map)

• Sub-Counter #0 : HSDPA Credit Allocation Protocol Error

• Sub-Counter #1 : CAC reject on the HSDPA cell

• Sub-Counter #2 : Mobility procedure failure (NBAP or RRC)

E-Type

• VS.HsdpaIuRelAbnormal.VS.HsdpaIuRelAbnormal.CreditAllocProtErr

• VS.HsdpaIuRelAbnormal.VS.HsdpaIuRelAbnormal.CACReject

• VS.HsdpaIuRelAbnormal.VS.HsdpaIuRelAbnormal.MobilityFailure

F-Object Instance



Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 281 VS.EdchSucMobility - #960

A-Description

Number of successful E-DCH mobility.

B-Collection

CUM

CUMulative

C-Condition (Event)

Change of primary cell for a PS I/B call that is on E-DCH or will be on E-DCH.

D-Result

A set of subcounters screened on: E-DCH Mobility Reason

• Sub-Counter #0 : E-DCH Cell to E-DCH Cell (intra frequency mobility)

• Sub-Counter #1 : non-E-DCH Cell to E-DCH Cell (intra frequency mobility)

• Sub-Counter #2 : E-DCH Cell to non-E-DCH Cell (intra frequency mobility)

• Sub-Counter #3 : E-DCH Cell to E-DCH Cell (inter frequency mobility)

• Sub-Counter #4 : non-E-DCH Cell to E-DCH Cell (inter frequency mobility)

• Sub-Counter #5 : E-DCH Cell to non-E-DCH Cell (inter frequency mobility)

E-Type

• VS.EdchSucMobility.VS.EdchSucMobility.EdchCellToEdchCellIntraFreqMob

• VS.EdchSucMobility.VS.EdchSucMobility.NonEdchCellToEdchCellIntraFreqMob



• VS.EdchSucMobility.VS.EdchSucMobility.EdchCellToNonEdchCellIntraFreqMob

• VS.EdchSucMobility.VS.EdchSucMobility.EdchCellToEdchCellInterFreqMob

• VS.EdchSucMobility.VS.EdchSucMobility.NonEdchCellToEdchCellInterFreqMob

• VS.EdchSucMobility.VS.EdchSucMobility.EdchCellToNonEdchCellInterFreqMob

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 282 VS.EdchUnsucMobility - #961

A-Description

Number of unsuccessful E-DCH mobility.

B-Collection

CUM

CUMulative

C-Condition (Event)

Change of primary cell for a PS I/B call that is on E-DCH or will be on E-DCH.

D-Result

A set of subcounters screened on: E-DCH Mobility Reason

• Sub-Counter #0 : E-DCH Cell to E-DCH Cell (intra frequency mobility)

• Sub-Counter #1 : non-E-DCH Cell to E-DCH Cell (intra frequency mobility)

• Sub-Counter #2 : E-DCH Cell to non-E-DCH Cell (intra frequency mobility)

• Sub-Counter #3 : E-DCH Cell to E-DCH Cell (inter frequency mobility)



• Sub-Counter #4 : non-E-DCH Cell to E-DCH Cell (inter frequency mobility)

• Sub-Counter #5 : E-DCH Cell to non-E-DCH Cell (inter frequency mobility)

E-Type

• VS.EdchUnsucMobility.VS.EdchUnsucMobility.EdchCellToEdchCellIntraFreqMob

• VS.EdchUnsucMobility.VS.EdchUnsucMobility.NonEdchCellToEdchCellIntraFreqMob

• VS.EdchUnsucMobility.VS.EdchUnsucMobility.EdchCellToNonEdchCellIntraFreqMob

• VS.EdchUnsucMobility.VS.EdchUnsucMobility.EdchCellToEdchCellInterFreqMob

• VS.EdchUnsucMobility.VS.EdchUnsucMobility.NonEdchCellToEdchCellInterFreqMob

• VS.EdchUnsucMobility.VS.EdchUnsucMobility.EdchCellToNonEdchCellInterFreqMob

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 283 VS.EdchCellDeletion - #962

A-Description

Number of E-DCH Cell Deletion

B-Collection

CUM

CUMulative

C-Condition (Event)

SHO algorithm triggering the deletion of the E-DCH Radio Link. Or, Radio link failure on theE_DCH RL of the E_DCH call.



D-Result

A set of subcounters screened on: E-DCH cell deletion

• Sub-Counter #0 : Deletion during Active Set Update

• Sub-Counter #1 : Deletion due to Radio Link failure

E-Type

• VS.EdchCellDeletion.VS.EdchCellDeletion.ActSetUpd

• VS.EdchCellDeletion.VS.EdchCellDeletion.RadioLinkFail

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 284 VS.EdchIuRelAbnormal - #963

A-Description

Number of Iu release requested for E-DCH call.

B-Collection

CUM

CUMulative

C-Condition (Event)

Happens on any failure that requests Iu release of call due to failure to access cell in E-DCHstate, or due to failure on flow control.

D-Result



A set of subcounters screened on: E-DCH - abnormal IU release cause.

• Sub-Counter #0 : CAC reject on the E-DCH cell

• Sub-Counter #1 : Mobility procedure failure (NBAP or RRC)

E-Type

• VS.EdchIuRelAbnormal.VS.EdchIuRelAbnormal.CACReject

• VS.EdchIuRelAbnormal.VS.EdchIuRelAbnormal.MobilityFailure

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.11 Radio Measurement


Counter name

#1002 VS.AvgTxPower

#1003 VS.CmConfigurationFailure

#1004 VS.CmActivationSuccess

#1005 VS.CmActivationFailure

#1006 VS.CmConfigurationSuccess

#1011 VS.IntraFreqMeasAverageOfCallPeriodicModeCell

#1012 VS.IntraFreqMeasAverageOfCallPeriodicModeNeighRnc

#1013 VS.IntraFreqMeasAverageOfCallEventModeCell

#1014 VS.IntraFreqMeasAverageOfCallEventModeNeighRnc

#1016 VS.MeasurementControlCellListSize

#1017 VS.MeasEvent1ACell

#1018 VS.MeasEvent1BCell

#1019 VS.MeasEvent1CCell

#1020 VS.MeasEvent1DCell

#1021 VS.MeasEvent1ECell

#1022 VS.MeasEvent1FCell

#1023 VS.MeasEvent2DCell

#1024 VS.MeasEvent2FCell

#1027 VS.MeasCallFailTraceDetectCell

#1029 VS.MeasEvent1BNeighRNC

#1030 VS.MeasEvent1CNeighRNC

#1031 VS.MeasEvent1DNeighRNC

#1032 VS.MeasEvent1ENeighRNC

#1033 VS.MeasEvent1FNeighRNC

#1034 VS.MeasEvent2DNeighRNC

#1035 VS.MeasEvent2FNeighRNC

#1038 VS.MeasCallFailTraceDetectNeighRNC

#1039 VS.MeasurementControlFailure

#1041 VS.DistPropDelayPerRange

#1042 VS.DistRssi

#1043 VS.IrmcacDistributionEcN0



Table 285 VS.AvgTxPower - #1002

A-Description

Average of Tx Power measurements received from that cell

B-Collection

LOAD

C-Condition (Event)

Common NBAP Measurement Reports from NodeB including Tx Power measurements

D-Result

one measurement

E-Type

VS.AvgTxPower

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

mW

K-Available Release

V3.1

L-Aggregation Rule

Rload

Table 286 VS.CmConfigurationFailure - #1003

A-Description

the number of failed Compressed Mode configuration (by the BTS or by the UE)

B-Collection

CUM

CUMulative



C-Condition (Event)

Failed Compressed Mode configuration due to bad CM parameter setting (by the BTS in NBAPRL Setup/Reconfiguration Failure or by the UE in RRC RB Setup/Reconfiguration Failure).

D-Result

A set of subcounters screened on: Compression Mode Configuration failures reasons

• Sub-Counter #0 : GSM

• Sub-Counter #1 : Inter Frequency

• Sub-Counter #2 : GSM and Inter Frequency

E-Type

• VS.CmConfigurationFailure.VS.CmConfigurationFailure.GSM

• VS.CmConfigurationFailure.VS.CmConfigurationFailure.InterFrequency

• VS.CmConfigurationFailure.VS.CmConfigurationFailure.GsmAndInterFrequency

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 287 VS.CmActivationSuccess - #1004

A-Description

the number of successful Compressed Mode activations. CM is activated on a radio alarm cri-teria (UE is leaving radio coverage) to allow the UE to perform measurements on GSM or an-other UMTS frequency if it needs CM for this.

B-Collection

CUM



CUMulative

C-Condition (Event)

Successful activation of CM measurements (activation is done by RRC Measurement Controlfor the UE and by NBAP Compress Mode Command for the BTS)

D-Result

A set of subcounters screened on: Compression Mode Configuration activation reasons



E-Type

• VS.CmActivationSuccess.VS.CmActivationSuccess.GSM

• VS.CmActivationSuccess.VS.CmActivationSuccess.InterFrequency

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 288 VS.CmActivationFailure - #1005

A-Description

the number of failed Compressed Mode activations.

B-Collection

CUM

CUMulative

C-Condition (Event)



Failed activation of CM measurements (RRC Measurement Control Failure or NBAP RL Fail-ure Indication due to CM : lack of CEM resources).

D-Result

A set of subcounters screened on: Compression Mode Configuration activation reasons



E-Type

• VS.CmActivationFailure.VS.CmActivationFailure.GSM

• VS.CmActivationFailure.VS.CmActivationFailure.InterFrequency

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 289 VS.CmConfigurationSuccess - #1006

A-Description

the number of successful Compressed Mode configuration (CM is configured by NBAP RLSetup/Reconfiguration for the BTS and RRC RB Setup/Reconfiguration for the UE. It may thenbe activated latter if the UE needs to perform radio measurements on another UMTS frequencyor on GSM, according a radio alarm criteria).

B-Collection

CUM

CUMulative

C-Condition (Event)



Successful Compressed Mode configuration (Success on both NBAP RL Reconfiguration Re-sponse and RRC RB Setup/Reconfiguration Response, containing CM configuration).

D-Result

A set of subcounters screened on: Compression Mode Configuration failures reasons



• Sub-Counter #2 : GSM and Inter Frequency

E-Type

• VS.CmConfigurationSuccess.VS.CmConfigurationSuccess.GSM

• VS.CmConfigurationSuccess.VS.CmConfigurationSuccess.InterFrequency

• VS.CmConfigurationSuccess.VS.CmConfigurationSuccess.GsmAndInterFrequency

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 290 VS.IntraFreqMeasAverageOfCallPeriodicModeCell - #1011

A-Description

the average number of mobiles which are in periodic mode and which primary cell is this cell,over the reporting period. Minimum and maximum number of mobiles over the period are alsoprovided.

B-Collection

LOAD

C-Condition (Event)



Incremented : - at call setup (the call starts in periodic mode) - if a call having this cell as itsprimary cell has switched from event to periodic mode - if a call in periodic mode has electedthis cell as its primary cell (soft handover) - Decremented : - if a call having this cell as itsprimary cell has switched from periodic to event mode - if a call in periodic mode has electedanother cell as its primary cell (soft handover) - if a call in periodic mode having cell as primarycell has terminated - This number of mobiles is sampled each 100ms.

D-Result

one measurement

E-Type

VS.IntraFreqMeasAverageOfCallPeriodicModeCell

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rload

Table 291 VS.IntraFreqMeasAverageOfCallPeriodicModeNeighRnc - #1012

A-Description

the average number of mobiles which are in periodic mode and which primary cell is locatedunder this neighboring RNC, over the reporting period. Minimum and maximum number of mo-biles over the period are also provided.

B-Collection

LOAD

C-Condition (Event)

Incremented : - if a call which primary cell is located under this RNC has switched from event



to periodic mode - if a call in periodic mode has elected a primary cell that is located under thisneighbouring RNC (after soft handover) and the former primary cell was under another RNC -Decremented : - if a call which primary cell is under this RNC has switched from periodic toevent mode - if a call in periodic mode has elected a new primary cell which is located underanother RNC (after soft handover) -if a call in periodic mode which primary cell is located underthis RNC has terminated - This number of mobiles is sampled each 100ms.

D-Result

one measurement

E-Type

VS.IntraFreqMeasAverageOfCallPeriodicModeNeighRnc

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rload

Table 292 VS.IntraFreqMeasAverageOfCallEventModeCell - #1013

A-Description

the average number of mobiles which are in event-triggered mode and which primary cell isthis cell, over the reporting period. Minimum and maximum number of mobiles over the periodare also provided.

B-Collection

LOAD

C-Condition (Event)

Incremented : - if a call having this cell as its primary cell has switched from periodic to event



mode - Decremented : - if a call having this cell as its primary cell has switched from event toperiodic mode - if a call in event mode having this cell as primary cell has terminated - Thisnumber of mobiles is sampled each 100ms.

D-Result

one measurement

E-Type

VS.IntraFreqMeasAverageOfCallEventModeCell

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rload

Table 293 VS.IntraFreqMeasAverageOfCallEventModeNeighRnc - #1014

A-Description

the average number of mobiles which are in event-triggered mode and which primary cell is un-der this neighboring RNC, over the reporting period. Minimum and maximum number of mo-biles over the period are also provided.

B-Collection

LOAD

C-Condition (Event)

Incremented : - if a call having its primary cell under this RNC has switched from periodic toevent mode - Decremented : - if a call having its primary cell under this RNC has switched fromevent to periodic mode - if a call in event mode having its primary cell under this RNC has ter-minated - This number of mobiles is sampled each 100ms.



D-Result

one measurement

E-Type

VS.IntraFreqMeasAverageOfCallEventModeNeighRnc

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rload

Table 294 VS.MeasurementControlCellListSize - #1016

A-Description

the size of the compounding cell list (for sho measurements) sent in RRC MEASUREMENTCONTROL messages to mobiles in connected mode. This allows to monitor how many cellsare configured by UTRAN to be measured by mobiles in connected mode for soft handoverpurpose. The average size, minimum and maximum sizes are provided.

B-Collection

VAL

VALue counter

C-Condition (Event)

Each time an RRC Measurement Control with intra-frequency neighbouring configuration issent to a mobile for which the reference cell is this cell. .

D-Result

one measurement

E-Type



VS.MeasurementControlCellListSize

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rval

Table 295 VS.MeasEvent1ACell - #1017

A-Description

the number of RRC Event 1A messages received from the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of an RRC MEASUREMENT REPORT Event 1A

D-Result

one measurement

E-Type

VS.MeasEvent1ACell

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 296 VS.MeasEvent1BCell - #1018

A-Description

the number of RRC Event 1B messages received from the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of an RRC MEASUREMENT REPORT Event 1B

D-Result

one measurement

E-Type

VS.MeasEvent1BCell

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V4.2

L-Aggregation Rule

Rtotal

Table 297 VS.MeasEvent1CCell - #1019

A-Description

the number of RRC Event 1C messages received from the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of an RRC MEASUREMENT REPORT Event 1C

D-Result

one measurement

E-Type

VS.MeasEvent1CCell

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 298 VS.MeasEvent1DCell - #1020

A-Description



the number of RRC Event 1D messages received from the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of an RRC MEASUREMENT REPORT Event 1D

D-Result

one measurement

E-Type

VS.MeasEvent1DCell

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 299 VS.MeasEvent1ECell - #1021

A-Description

the number of RRC Event 1E messages received from the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of an RRC MEASUREMENT REPORT Event 1E



D-Result

one measurement

E-Type

VS.MeasEvent1ECell

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 300 VS.MeasEvent1FCell - #1022

A-Description

the number of RRC Event 1F messages received from the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of an RRC MEASUREMENT REPORT Event 1F

D-Result

one measurement

E-Type

VS.MeasEvent1FCell

F-Object Instance

Cell(Reference)



G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 301 VS.MeasEvent2DCell - #1023

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: Full Event - CPICH triggering

• Sub-Counter #0 : Triggering quantity is CPICH EcNo.

• Sub-Counter #1 : Triggering quantity is CPICH Rscp.

E-Type

• VS.MeasEvent2DCell.VS.MeasEvent2DCell.CpichEcNo

• VS.MeasEvent2DCell.VS.MeasEvent2DCell.CpichRscp

F-Object Instance

Cell(Reference)

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 302 VS.MeasEvent2FCell - #1024

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




E-Type

• VS.MeasEvent2FCell.VS.MeasEvent2FCell.CpichEcNo

• VS.MeasEvent2FCell.VS.MeasEvent2FCell.CpichRscp

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 303 VS.MeasCallFailTraceDetectCell - #1027

A-Description

the number of Indication of at least one available Call Failure Trace due to a Detected Cell notreported via the active measurement method (full event trigger, or other). The Primary RL ofthe UE is on this FddCell.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of at least one RRC MEASUREMENT REPORT Event 1A or 1E with detected cell

D-Result

A set of subcounters screened on: Full Event - Detected Cell triggered

• Sub-Counter #0 : Full Event Mode

• Sub-Counter #1 : Other mode

E-Type

• VS.MeasCallFailTraceDetectCell.VS.MeasCallFailTraceDetectCell.FullEvt

• VS.MeasCallFailTraceDetectCell.VS.MeasCallFailTraceDetectCell.OtherEvt

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 304 VS.MeasEvent1BNeighRNC - #1029

A-Description

the number of RRC Event 1B messages received from the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of an RRC MEASUREMENT REPORT Event 1B

D-Result

one measurement

E-Type

VS.MeasEvent1BNeighRNC

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule



Rtotal

Table 305 VS.MeasEvent1CNeighRNC - #1030

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of an RRC MEASUREMENT REPORT Event 1C

D-Result

one measurement

E-Type

VS.MeasEvent1CNeighRNC

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 306 VS.MeasEvent1DNeighRNC - #1031

A-Description


B-Collection



CUM

CUMulative

C-Condition (Event)


D-Result

one measurement

E-Type

VS.MeasEvent1DNeighRNC

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 307 VS.MeasEvent1ENeighRNC - #1032

A-Description

the number of RRC Event 1E messages received from the UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of an RRC MEASUREMENT REPORT Event 1E

D-Result



one measurement

E-Type

VS.MeasEvent1ENeighRNC

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 308 VS.MeasEvent1FNeighRNC - #1033

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

one measurement

E-Type

VS.MeasEvent1FNeighRNC

F-Object Instance

Neighbouring RNC

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 309 VS.MeasEvent2DNeighRNC - #1034

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




E-Type

• VS.MeasEvent2DNeighRNC.VS.MeasEvent2DNeighRNC.CpichEcNo

• VS.MeasEvent2DNeighRNC.VS.MeasEvent2DNeighRNC.CpichRscp

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 310 VS.MeasEvent2FNeighRNC - #1035

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




E-Type

• VS.MeasEvent2FNeighRNC.VS.MeasEvent2FNeighRNC.CpichEcNo

• VS.MeasEvent2FNeighRNC.VS.MeasEvent2FNeighRNC.CpichRscp

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 311 VS.MeasCallFailTraceDetectNeighRNC - #1038

A-Description

the number of calls that have been reported a detected cell.

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of at least one RRC MEASUREMENT REPORT Event 1A or 1E with detected cell

D-Result

A set of subcounters screened on: Full Event - Detected Cell triggered

• Sub-Counter #0 : Full Event Mode

• Sub-Counter #1 : Other mode

E-Type

• VS.MeasCallFailTraceDetectNeighRNC.VS.MeasCallFailTraceDetectNeighRNC.FullEvt

• VS.MeasCallFailTraceDetectNeighRNC.VS.MeasCallFailTraceDetectNeighRNC.OtherEvt

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 312 VS.MeasurementControlFailure - #1039

A-Description

Number of RRC measurement control failure messages received from the UE

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RRC measurement control failure message from a UE.

D-Result

A set of subcounters screened on: Measurement control to configure Events


• Sub-Counter #1 : due to Measurement Control to configure Events 1A, 1B, 1C, 1D, 1E, 1F

• Sub-Counter #2 : due to Measurement Control to configure Events 2D, 2F on CPICH EcNoquantity

• Sub-Counter #3 : due to Measurement Control to configure Events 2D, 2F on CPICH Rscpquantity

• Sub-Counter #4 : due to Measurement Control to configure Events 2C on CPICH EcNoquantity

• Sub-Counter #5 : due to Measurement Control to configure Events 2C on CPICH Rscpquantity

• Sub-Counter #6 : due to Measurement Control to configure Events 3C

E-Type

• VS.MeasurementControlFailure.VS.MeasurementControlFailure.Other

• VS.MeasurementControlFailure.VS.MeasurementControlFailure.Evt1A1B1C1D1E1F

• VS.MeasurementControlFailure.VS.MeasurementControlFailure.Evt2D2FCpichEcNo

• VS.MeasurementControlFailure.VS.MeasurementControlFailure.Evt2D2FCpichRscp

• VS.MeasurementControlFailure.VS.MeasurementControlFailure.Evt2CCpichEcNo

• VS.MeasurementControlFailure.VS.MeasurementControlFailure.Evt2CCpichRscp

• VS.MeasurementControlFailure.VS.MeasurementControlFailure.Evt3C



F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.2

L-Aggregation Rule

Rtotal

Table 313 VS.DistPropDelayPerRange - #1041

A-Description

Distribution of propagation delays, as expressed in the 3GPP25.433 Nbap Rl Setup Request /Propagation Delay IE when present

B-Collection

CUM

CUMulative

C-Condition (Event)

The RNC is sending a Nbap Rl setup request including the Propagation Delay IE

D-Result

A set of subcounters screened on: Propagation delay reason

• Sub-Counter #0 : Delay < 9 Chips

• Sub-Counter #1 : 9 <= Delay < 15 Chips

• Sub-Counter #2 : 15 <= Delay < 18 Chips

• Sub-Counter #3 : 18 <= Delay <= 765 Chips)

E-Type

• VS.DistPropDelayPerRange.VS.DistPropDelayPerRange.DelayLt9Chips

• VS.DistPropDelayPerRange.VS.DistPropDelayPerRange.9LeDelayLt15Chips



• VS.DistPropDelayPerRange.VS.DistPropDelayPerRange.15LeDelayLt18Chips

• VS.DistPropDelayPerRange.VS.DistPropDelayPerRange.19LeDelayLe765Chips

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 314 VS.DistRssi - #1042

A-Description

Uplink RSSI received from NBAP common measurement per cell. It details the number of com-mon measurements (here, UL RSSI level) according to their respective ranges and during thereporting period.

B-Collection

CUM

CUMulative

C-Condition (Event)

The reception of NBAP COMMON MEASUREMENT from NodeB to RNC

D-Result

A set of subcounters screened on: Power ranges

• Sub-Counter #0 : -97.0dBm <= Measurement

• Sub-Counter #1 : -100.0dBm <= Measurement < -97.0dBm





• Sub-Counter #4 : Measurement < -105dBm

E-Type

• VS.DistRssi.VS.DistRssi.DistRssiN970LeMeas

• VS.DistRssi.VS.DistRssi.DistRssiN1000LeMeasLtN970



• VS.DistRssi.VS.DistRssi.DistRssiMeasLtN1050

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 315 VS.IrmcacDistributionEcN0 - #1043

A-Description

the number of CPICH Ec/N0 measurements received per range from UEs with that referencecell.

B-Collection

CUM

CUMulative

C-Condition (Event)

This measurement is based on measurement reports from UE including Ec/N0 measurements.

D-Result

A set of subcounters screened on: Measurement Report power range



• Sub-Counter #0 : -24 dB <= Measurement < -15 dB




• Sub-Counter #4 : -7 dB <= Measurement < 0 dB

E-Type

• VS.IrmcacDistributionEcN0.VS.IrmcacDistributionEcN0.PwrRngN24LeMeasLtN15




• VS.IrmcacDistributionEcN0.VS.IrmcacDistributionEcN0.PwrRngN7LeMeasLt0

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.12 QOS Performance

For Always-ON, the reference document is UMT/SYS/DD/0034 PS Call Management. For iRM CACand iRM scheduling, the reference document is UMT/SYS/DD/0128 Intelligent RAB Mapping. ForiRM Preemption, the reference document is UMT/SYS/DD/10672 iRM Preemption.


Counter name

#1111 VS.IrmcacMaintainedHighPriority

#1112 VS.IrmcacDowngradedHighPriority

#1113 VS.IrmcacRejectedHighPriority

#1114 VS.IrmcacMaintainedMediumPriority

#1115 VS.IrmcacDowngradedMediumPriority

#1116 VS.IrmcacRejectedMediumPriority

#1117 VS.IrmcacMaintainedLowPriority

#1118 VS.IrmcacDowngradedLowPriority

#1119 VS.IrmcacRejectedLowPriority

#1124 VS.IRMTimeCellRadioColorRed

#1125 VS.IRMTimeCellRadioColorYellow

#1126 VS.IRMTimeFreeDlCodesBySpreadingFactor

#1129 VS.IrmcacRadioLinkColorRed

#1130 VS.IrmcacRadioLinkColorGreen

#1131 VS.IrmUpgradingActivation

#1132 VS.IrmUpgradingActivationDelayed

#1134 VS.IrmUpgradingDeactivation

#1136 VS.IrmPreemptionTimeCellColorCongested

#1137 VS.IrmPreemptionTimeCellColorCongestedBecauseOfOvsfCodes

#1138 VS.IrmPreemptionTimeCellColorCongestedBecauseOfPower

#1139 VS.IrmPreemptionRbHighPriorityDowngraded

#1140 VS.IrmPreemptionRbHighPriorityRejected

#1141 VS.IrmPreemptionRbMediumPriorityDowngraded

#1142 VS.IrmPreemptionRbMediumPriorityRejected

#1143 VS.IrmPreemptionRbLowPriorityDowngraded

#1144 VS.IrmPreemptionRbLowPriorityRejected

#1157 VS.RrcNwkTransPchToFachOrDch

#1158 VS.IrmcacDistributionRscp

#1159 VS.DownsizingStep1Success




Counter name

#1160 VS.DownsizingStep1SuccessNeighbRnc

#1161 VS.DownsizingStep1Unsuccess

#1162 VS.DownsizingStep1UnsuccessNeighbRnc

#1163 VS.DownsizingStep2Success

#1164 VS.DownsizingStep2SuccessNeighbRnc

#1165 VS.UpsizingSuccess

#1166 VS.UpsizingSuccessNeighbRnc

#1167 VS.UpsizingUnsuccess

#1168 VS.UpsizingUnsuccessNeighbRnc

#1169 VS.IRMSchedulingDowngradedSuccess

#1170 VS.IRMSchedulingDowngradedFailure

#1171 VS.IRMSchedulingDowngradedSuccessNeighbRnc

#1172 VS.IRMSchedulingDowngradedFailureNeighbRnc

#1173 VS.IrmUpgradingSuccessful

#1174 VS.IrmUpgradingCommand

#1175 VS.IrmUpgradingCommandNrnc

#1176 VS.IrmUpgradingSuccessfulNrnc

#1177 VS.QosDlCemLdClrYellow

#1178 VS.QosDlCemLdClrRed

#1179 VS.QosDlCemLdCellPreemptClrCngstd

#1180 VS.QosUlCemLdClrYellow

#1181 VS.QosUlCemLdClrRed

#1182 VS.IrmTimeDlIubTransportColorRed

#1183 VS.IrmTimeDlIubTransportColorYellow

#1184 VS.UlIrmcacMaintainedGold

#1185 VS.UlIrmcacMaintainedSilver

#1186 VS.UlIrmcacMaintainedBronze

#1187 VS.UlIrmcacDowngradedGold

#1188 VS.UlIrmcacDowngradedSilver

#1189 VS.UlIrmcacDowngradedBronze

#1190 VS.UlIrmcacRejectedGold

#1191 VS.UlIrmcacRejectedSilver

#1192 VS.UlIrmcacRejectedBronze

#1193 VS.IRMTimeULRadioLoadColorYellow

#1194 VS.IRMTimeULRadioLoadColorRed

#1195 VS.HsPdschDynCodeMgmtStealing




Counter name

#1196 VS.HsPdschDynCodeMgmtRealloc

#1197 VS.NumHsPdschCodes

Table 316 VS.IrmcacMaintainedHighPriority - #1111

A-Description

the number of RAB assignments for high priority users (Allocation/Retention priority= 0) thatare maintained as requested by iRM.

B-Collection

CUM

CUMulative

C-Condition (Event)

RAB Assignment for high priority user.

D-Result

A set of subcounters screened on: DL Radio Bearer Set Id. (MIB Indexes V5.0, V01.07)

• Sub-Counter #0 : DL Radio Bearer Set Id0


• Sub-Counter #2 : NOT USED






























E-Type

• VS.IrmcacMaintainedHighPriority.VS.IrmcacMaintainedHighPriority.DlRbSetId0
































F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 317 VS.IrmcacDowngradedHighPriority - #1112

A-Description

the number of RAB assignments for high priority users (Allocation/Retention priority= 0) thatare downgraded by iRM.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result


































E-Type

• VS.IrmcacDowngradedHighPriority.VS.IrmcacDowngradedHighPriority.DlRbSetId0
































F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 318 VS.IrmcacRejectedHighPriority - #1113

A-Description

the number of RAB assignments for high priority users (Allocation/Retention priority= 0) thatare rejected by iRM.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result


































E-Type

• VS.IrmcacRejectedHighPriority.VS.IrmcacRejectedHighPriority.DlRbSetId0
































F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 319 VS.IrmcacMaintainedMediumPriority - #1114

A-Description

the number of RAB assignments for medium priority users (Allocation/Retention priority= 1)that are maintained as requested by iRM.

B-Collection



CUM

CUMulative

C-Condition (Event)

RAB Assignment for medium priority user.

D-Result


































E-Type

• VS.IrmcacMaintainedMediumPriority.VS.IrmcacMaintainedMediumPriority.DlRbSetId0






























F-Object Instance



RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 320 VS.IrmcacDowngradedMediumPriority - #1115

A-Description

the number of RAB assignments for medium priority users (Allocation/Retention priority= 1)that are downgraded by iRM.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result


































E-Type

• VS.IrmcacDowngradedMediumPriority.VS.IrmcacDowngradedMediumPriority.DlRbSetId0
































F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal



Table 321 VS.IrmcacRejectedMediumPriority - #1116

A-Description

the number of RAB assignments for medium priority users (Allocation/Retention priority= 1)that are rejected by iRM.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result


































E-Type

• VS.IrmcacRejectedMediumPriority.VS.IrmcacRejectedMediumPriority.DlRbSetId0
































F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 322 VS.IrmcacMaintainedLowPriority - #1117

A-Description

the number of RAB assignments for low priority users (Allocation/Retention priority= 2) that aremaintained as requested by iRM.

B-Collection

CUM

CUMulative

C-Condition (Event)

RAB Assignment for low priority user.

D-Result


































E-Type

• VS.IrmcacMaintainedLowPriority.VS.IrmcacMaintainedLowPriority.DlRbSetId0
































F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 323 VS.IrmcacDowngradedLowPriority - #1118

A-Description

the number of RAB assignments for low priority users (Allocation/Retention priority= 2) that aredowngraded by iRM.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result


































E-Type

• VS.IrmcacDowngradedLowPriority.VS.IrmcacDowngradedLowPriority.DlRbSetId0
































F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 324 VS.IrmcacRejectedLowPriority - #1119

A-Description

the number of RAB assignments for low priority users (Allocation/Retention priority= 2) that arerejected by iRM.

B-Collection

CUM

CUMulative

C-Condition (Event)




D-Result
































E-Type



• VS.IrmcacRejectedLowPriority.VS.IrmcacRejectedLowPriority.DlRbSetId0






























F-Object Instance

RNC

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 325 VS.IRMTimeCellRadioColorRed - #1124

A-Description

the ratio of time a cell is considered red by the iRM during a reporting period because of radioressource shortage (Average value). The minimum value allows to know if the cell has neverbeen considered red by the iRM during the reporting period. The maximum value allows toknow if the cell has been considered red, at least once, by the iRM during the reporting period.

B-Collection

LOAD

C-Condition (Event)

Receipt of at least one indication that iRM changes cell colour to or from red because of radioresource shortage.

D-Result

one measurement

E-Type

VS.IRMTimeCellRadioColorRed

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

percent

K-Available Release

V4.2

L-Aggregation Rule

Rload

Table 326 VS.IRMTimeCellRadioColorYellow - #1125

A-Description

the ratio of time a cell is considered yellow by the iRM during a reporting period because of ra-dio ressource shortage (Average value). The minimum value allows to know if the cell has nev-er been considered yellow by the iRM during the reporting period. The maximum value allowsto know if the cell has been considered yellow, at least once, by the iRM during the reportingperiod.

B-Collection

LOAD

C-Condition (Event)

IRM changes cell color to or from yellow because of radio resource shortage.This cell color (1 ifyellow, 0 else) is sampled each 100ms.

D-Result

one measurement

E-Type

VS.IRMTimeCellRadioColorYellow

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

percent

K-Available Release



V4.2

L-Aggregation Rule

Rload

Table 327 VS.IRMTimeFreeDlCodesBySpreadingFactor - #1126

A-Description

the average number of free downlink channelization codes per spreading factor, during a re-porting period. The minimum and maximum number of free codes during the reporting periodare also provided.

B-Collection

LOAD

C-Condition (Event)

DL channelization code reserved or freed up. This number of free codes is sampled each100ms.

D-Result

A set of subcounters screened on: QOS Spreading factor DL codes

• Sub-Counter #0 : 4







E-Type

• VS.IRMTimeFreeDlCodesBySpreadingFactor.VS.IRMTimeFreeDlCodesBySpreadingFactor.4









F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rload

Table 328 VS.IrmcacRadioLinkColorRed - #1129

A-Description

the number of times a radio-link on the cell is a radio-link for a UE reference cell and is red

B-Collection

CUM

CUMulative

C-Condition (Event)

At each iRM CAC activation (CAC, Always ON).

D-Result

one measurement

E-Type

VS.IrmcacRadioLinkColorRed

F-Object Instance

Cell(Reference)

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 329 VS.IrmcacRadioLinkColorGreen - #1130

A-Description

the number of times a radio-link on the cell is a radio-link for a UE reference cell and is green

B-Collection

CUM

CUMulative

C-Condition (Event)

At each iRM CAC activation (CAC, Always ON).

D-Result

one measurement

E-Type

VS.IrmcacRadioLinkColorGreen

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 330 VS.IrmUpgradingActivation - #1131

A-Description

the number of times iRM upgrading monitoring has been triggered for a call which has justbeen downgraded due to iRM Scheduling downgrading (bad radio conditions).

B-Collection

CUM

CUMulative

C-Condition (Event)

Configuration of NBAP Dedicated Measurement on DL transmitted power for a call which hasjust been downgraded (iRM Scheduling downgrading). When the power will go below a giventhreshold (better radio conditions) on its reference cell then the call may be upgraded.

D-Result

one measurement

E-Type

VS.IrmUpgradingActivation

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1



L-Aggregation Rule

Rtotal

Table 331 VS.IrmUpgradingActivationDelayed - #1132

A-Description

the number of times iRM upgrading monitoring has not been triggered immediately after a callhas been downgraded due to iRM Scheduling downgrading (bad radio conditions). The monit-oring may be delayed due to the anti ping-pong timer running (started by previous iRM upgrad-ing). In this case, the monitoring will be performed when this timer expires.

B-Collection

CUM

CUMulative

C-Condition (Event)

iRM Scheduling downgrading of a call but for which the anti ping-pong timer is still running(timer started by latest upgrading)

D-Result

one measurement

E-Type

VS.IrmUpgradingActivationDelayed

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal



Table 332 VS.IrmUpgradingDeactivation - #1134

A-Description

the number of times iRM Scheduling Upgrading (FRS23332) was deactivated while the DLtransmitted power was monitored.

B-Collection

CUM

CUMulative

C-Condition (Event)

All events that stop the monitoring : - Always-ON downsizing - adding of a CS RAB (->CS+PS)or a second PS RAB (PS+PS) as these configurations are not eligible for iRM Scheduling

D-Result

one measurement

E-Type

VS.IrmUpgradingDeactivation

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 333 VS.IrmPreemptionTimeCellColorCongested - #1136

A-Description

the ratio of time a cell is considered to be congested by the iRM during a reporting period(Average value). The minimum value allows to know if the cell has never been considered con-gested by the iRM during the reporting period. The maximum value allows to know if the cell



has been considered congested, at least once, by the iRM during the reporting period. NoteWhen a cell is considered "congested" then iRM pre-emption mechanism (FRS25075) willdowngrade some ongoing PS calls to free resources (OVSF and power). The cell color is theconsequence of all traffic, but the result on downgrading will apply only on the packet compon-ent of the radio configuration.

B-Collection

LOAD

C-Condition (Event)

Cell color transition to "congested". This can be triggered by OVSF code usage or power con-sumptions going over given thresholds.

D-Result

one measurement

E-Type

VS.IrmPreemptionTimeCellColorCongested

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rload

Table 334 VS.IrmPreemptionTimeCellColorCongestedBecauseOfOvsfCodes - #1137

A-Description

the ratio of time a cell is considered to be congested because of OVSF codes by the iRM dur-ing a reporting period (Average value). The minimum value allows to know if the cell has neverbeen considered congested by the iRM during the reporting period. The maximum value allowsto know if the cell has been considered congested, at least once, by the iRM during the report-ing period. The cell color is the consequence of all traffic, but the result on downgrading will ap-



ply only on the packet component of the radio configuration.

B-Collection

LOAD

C-Condition (Event)

Cell color transition to "congested" due to OVSF codes consumption

D-Result

one measurement

E-Type

VS.IrmPreemptionTimeCellColorCongestedBecauseOfOvsfCodes

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rload

Table 335 VS.IrmPreemptionTimeCellColorCongestedBecauseOfPower - #1138

A-Description

the ratio of time a cell is considered to be congested because of power consumption by theiRM during a reporting period (Average value). The minimum value allows to know if the cellhas never been considered congested by the iRM during the reporting period. The maximumvalue allows to know if the cell has been considered congested, at least once, by the iRM dur-ing the reporting period. The cell color is the consequence of all traffic, but the result on con-gestion will apply only on the packet component of the radio configuration.

B-Collection

LOAD

C-Condition (Event)



Cell color transition "congested" because of DL Tx Power consumption

D-Result

one measurement

E-Type

VS.IrmPreemptionTimeCellColorCongestedBecauseOfPower

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rload

Table 336 VS.IrmPreemptionRbHighPriorityDowngraded - #1139

A-Description

the number of times RB with High Priority (gold) is downgraded due to iRM pre-emption (cellcolor is congested).

B-Collection

CUM

CUMulative

C-Condition (Event)

iRM pr-eemption of an high priority user leading to a downgrade of the bitrate during cell con-gestion

D-Result


































E-Type

• VS.IrmPreemptionRbHighPriorityDowngraded.VS.IrmPreemptionRbHighPriorityDowngraded.DlRbSetId0


• VS.IrmPreemptionRbHighPriorityDowngraded.VS.IrmPreemptionRbHighPriorityDowngrade



d.DlRbSetId2






























F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 337 VS.IrmPreemptionRbHighPriorityRejected - #1140

A-Description

the number of times RB with High Priority (gold) is released due to iRM pre-emption (cell coloris congested).

B-Collection

CUM

CUMulative



C-Condition (Event)

iRM pre-emption of an high priority user leading to a release of the RAB during cell congestion

D-Result


































E-Type

• VS.IrmPreemptionRbHighPriorityRejected.VS.IrmPreemptionRbHighPriorityRejected.DlRbSetId0
































F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 338 VS.IrmPreemptionRbMediumPriorityDowngraded - #1141



A-Description

the number of times RB with Medium Priority (silver) is downgraded due to iRM pre-emption(cell color is congested).

B-Collection

CUM

CUMulative

C-Condition (Event)

iRM pre-emption of a medium priority user leading to a downgrade of the bitrate during cellcongestion

D-Result


































E-Type

• VS.IrmPreemptionRbMediumPriorityDowngraded.VS.IrmPreemptionRbMediumPriorityDowngraded.DlRbSetId0
































F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event



K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 339 VS.IrmPreemptionRbMediumPriorityRejected - #1142

A-Description

the number of times RB with Medium Priority (silver) is released due to iRM pre-emption (cellcolor is congested).

B-Collection

CUM

CUMulative

C-Condition (Event)

iRM pre-emption of an medium priority user leading to a release of the RAB during cell conges-tion

D-Result


































E-Type

• VS.IrmPreemptionRbMediumPriorityRejected.VS.IrmPreemptionRbMediumPriorityRejected.DlRbSetId0
































F-Object Instance

RNC

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 340 VS.IrmPreemptionRbLowPriorityDowngraded - #1143

A-Description

the number of times RB with Low Priority (bronze) is downgraded due to iRM pre-emption (cellcolor is congested).

B-Collection

CUM

CUMulative

C-Condition (Event)

iRM pre-emption of an low priority user leading to a downgrade of the bitrate during cell con-gestion

D-Result


































E-Type

• VS.IrmPreemptionRbLowPriorityDowngraded.VS.IrmPreemptionRbLowPriorityDowngraded.DlRbSetId0






























• VS.IrmPreemptionRbLowPriorityDowngraded.VS.IrmPreemptionRbLowPriorityDowngrade



d.DlRbSetId28


F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 341 VS.IrmPreemptionRbLowPriorityRejected - #1144

A-Description

the number of times RB with Low Priority (bronze) is released due to iRM pre-emption (cell col-or is congested).

B-Collection

CUM

CUMulative

C-Condition (Event)

iRM pre-emption of an low priority user leading to a release of the RAB during cell congestion

D-Result


































E-Type

• VS.IrmPreemptionRbLowPriorityRejected.VS.IrmPreemptionRbLowPriorityRejected.DlRbSetId0


























• VS.IrmPreemptionRbLowPriorityRejected.VS.IrmPreemptionRbLowPriorityRejected.DlRbS



etId24






F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 342 VS.RrcNwkTransPchToFachOrDch - #1157

A-Description

Number of network initiated upsizes from XXX_PCH to CELL_FACH or CELL_DCH

B-Collection

CUM

CUMulative

C-Condition (Event)

Upsize to resume DL signalling or data transfer : transmission of a RRC Cell Update Confirmincluding RRC target state = CELL_FACH or CELL_DCH to a mobile initially in CELL_PCH or



URA_PCH state following either a the reception of DL data on Iu-PS interface or a RANAPmessage.

D-Result

A set of subcounters screened on: Target RRC State

• Sub-Counter #0 : Cell FACH

• Sub-Counter #1 : Cell DCH

E-Type

• VS.RrcNwkTransPchToFachOrDch.VS.RrcNwkTransPchToFachOrDch.CellFach

• VS.RrcNwkTransPchToFachOrDch.VS.RrcNwkTransPchToFachOrDch.CellDch

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 343 VS.IrmcacDistributionRscp - #1158

A-Description

the distribution of CPICH RSCP measurements received from UEs with that reference cell oftime

B-Collection

CUM

CUMulative

C-Condition (Event)

Measurement Reports from UE with CPICH RSCP measurement.



D-Result






• Sub-Counter #4 : -80 dB <= Measurement <= -25 dB

E-Type

• VS.IrmcacDistributionRscp.VS.IrmcacDistributionRscp.N120LeMeasLtN110




• VS.IrmcacDistributionRscp.VS.IrmcacDistributionRscp.N80LeMeasLeN25

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 344 VS.DownsizingStep1Success - #1159

A-Description

the number of downsizing step 1 successes, screened by Downlink Access Stratum Configura-tion, for each cell controlled by the RNC. The measurement attached to a given cell is incre-mented if the cell is the reference cell of the involved UE.

B-Collection



CUM

CUMulative

C-Condition (Event)

Successful implementation of an "Always On" algorithm decision to downgrade the UE capabil-ities to the "Always On" radio-configuration. It is started on reception of a RRC RB RECONFIG-URATION COMPLETE message consistent with the required downgraded capabilities. Themeasurement is only incremented when the UE has a reference cell under the control of theRNC in charge of the measurement.

D-Result

A set of subcounters screened on: NT Upsizing or Downsizing Rate Mapping


• Sub-Counter #1 : DCH PS I/B 32





E-Type

• VS.DownsizingStep1Success.VS.DownsizingStep1Success.DchHsdpa

• VS.DownsizingStep1Success.VS.DownsizingStep1Success.DchPsIb32





F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V5.0

L-Aggregation Rule

Rtotal

Table 345 VS.DownsizingStep1SuccessNeighbRnc - #1160

A-Description

the number of downsizing step 1 successes, screened by Downlink Access Stratum Configura-tion, for each neighboring RNC. The measurement attached to a neighboring RNC is incre-mented if the neighboring RNC controls the reference cell of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful implementation of an "Always On" algorithm decision to downgrade the UE capabil-ities to the "Always On" radio-configuration. It is started on reception of a RRC RB RECONFIG-URATION COMPLETE message consistent with the required downgraded capabilities. Themeasurement is only incremented when the UE has a reference cell outside the control of theRNC in charge of the measurement.

D-Result








E-Type

• VS.DownsizingStep1SuccessNeighbRnc.VS.DownsizingStep1SuccessNeighbRnc.DchHsdpa

• VS.DownsizingStep1SuccessNeighbRnc.VS.DownsizingStep1SuccessNeighbRnc.DchPsIb32



• VS.DownsizingStep1SuccessNeighbRnc.VS.DownsizingStep1SuccessNeighbRnc.DchPsI



b256


F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 346 VS.DownsizingStep1Unsuccess - #1161

A-Description

the number of unsuccessful downsizing step 1, screened by Downlink Access Stratum Config-uration, for each cell controlled by the RNC. The measurement attached to a given cell is incre-mented if the cell is the reference cell of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccessful implementation of an "Always On" algorithm decision to downgrade the UE cap-abilities to the "Always On" radio-configuration

D-Result










E-Type

• VS.DownsizingStep1Unsuccess.VS.DownsizingStep1Unsuccess.DchHsdpa

• VS.DownsizingStep1Unsuccess.VS.DownsizingStep1Unsuccess.DchPsIb32





F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 347 VS.DownsizingStep1UnsuccessNeighbRnc - #1162

A-Description

the number of unsuccessful downsizing step 1, screened by Downlink Access Stratum Config-uration, for each neighboring RNC. The measurement attached to a neighboring RNC is incre-mented if the neighboring RNC controls the reference cell of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)



Unsuccessful implementation of an "Always On" algorithm decision to downgrade the UE cap-abilities to the "Always On" radio-configuration

D-Result








E-Type

• VS.DownsizingStep1UnsuccessNeighbRnc.VS.DownsizingStep1UnsuccessNeighbRnc.DchHsdpa

• VS.DownsizingStep1UnsuccessNeighbRnc.VS.DownsizingStep1UnsuccessNeighbRnc.DchPsIb32





F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0



L-Aggregation Rule

Rtotal

Table 348 VS.DownsizingStep2Success - #1163

A-Description

the number of downsizing step 2 successes, screened by Downlink Access Stratum Configura-tion, for each cell controlled by the RNC. The measurement attached to a given cell is incre-mented if the cell is the reference cell of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful implementation of an "Always On" algorithm decision to release an UE call due tothe UE inactivity. It is started on reception of a RRC RRC RELEASE COMPLETE message for"User inactivity" reason. The measurement is only incremented when the UE has a referencecell under the control of the RNC in charge of the measurement.

D-Result

A set of subcounters screened on: Downsizing step 2 Rate Mapping

• Sub-Counter #0 : Other AsConfId


• Sub-Counter #2 : Dch PS I/B 8

E-Type

• VS.DownsizingStep2Success.VS.DownsizingStep2Success.DwnStp2Other

• VS.DownsizingStep2Success.VS.DownsizingStep2Success.DwnStp2CellFach

• VS.DownsizingStep2Success.VS.DownsizingStep2Success.DwnStp2DchPsIb8

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 349 VS.DownsizingStep2SuccessNeighbRnc - #1164

A-Description

the number of downsizing step 2 successes, screened by Downlink Access Stratum Configura-tion, for each neighboring RNC. The measurement attached to a neighboring RNC is incre-mented if the neighboring RNC controls the reference cell of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful implementation of an "Always On" algorithm decision to release an UE call due tothe UE inactivity. It is started on reception of a RRC RRC RELEASE COMPLETE message for"User inactivity" reason. The measurement is only incremented when the UE has a referencecell outside the control of the RNC in charge of the measurement.

D-Result

A set of subcounters screened on: Downsizing step 2 Rate Mapping

• Sub-Counter #0 : Other AsConfId


• Sub-Counter #2 : Dch PS I/B 8

E-Type

• VS.DownsizingStep2SuccessNeighbRnc.VS.DownsizingStep2SuccessNeighbRnc.DwnStp2Other

• VS.DownsizingStep2SuccessNeighbRnc.VS.DownsizingStep2SuccessNeighbRnc.DwnStp2CellFach

• VS.DownsizingStep2SuccessNeighbRnc.VS.DownsizingStep2SuccessNeighbRnc.DwnStp2DchPsIb8

F-Object Instance

Neighbouring RNC

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 350 VS.UpsizingSuccess - #1165

A-Description

the number of successful upsizings, screened by Downlink Access Stratum Configuration, foreach cell controlled by the RNC. The measurement attached to a given cell is incremented ifthe cell is the reference cell of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful implementation of an "Always On" algorithm decision to restore the full UE capabil-ities It is started on reception of a RRC RB RECONFIGURATION COMPLETE message con-sistent with the required upgraded capabilities. The measurement is only incremented whenthe UE has a reference cell under the control of the RNC in charge of the measurement.

D-Result








E-Type

• VS.UpsizingSuccess.VS.UpsizingSuccess.DchHsdpa



• VS.UpsizingSuccess.VS.UpsizingSuccess.DchPsIb32





F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 351 VS.UpsizingSuccessNeighbRnc - #1166

A-Description

the number of successful upsizings, screened by Downlink Access Stratum Configuration, foreach neighboring RNC. The measurement attached to a neighboring RNC is incremented if theneighboring RNC controls the reference cell of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful implementation of an "Always On" algorithm decision to restore the full UE capabil-ities, It is started on reception of a RRC RB RECONFIGURATION COMPLETE message con-sistent with the required upgraded capabilities. The measurement is only incremented whenthe UE has a reference cell outside the control of the RNC in charge of the measurement.

D-Result










E-Type

• VS.UpsizingSuccessNeighbRnc.VS.UpsizingSuccessNeighbRnc.DchHsdpa

• VS.UpsizingSuccessNeighbRnc.VS.UpsizingSuccessNeighbRnc.DchPsIb32





F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 352 VS.UpsizingUnsuccess - #1167

A-Description

the number of unsuccessful upsizings, screened by Downlink Access Stratum Configuration,for each cell controlled by the RNC. The measurement attached to a given cell is incrementedif the cell is the reference cell of the involved UE.



B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccessful implementation of an "Always On" algorithm decision to restore the full UE cap-abilities.

D-Result








E-Type

• VS.UpsizingUnsuccess.VS.UpsizingUnsuccess.DchHsdpa

• VS.UpsizingUnsuccess.VS.UpsizingUnsuccess.DchPsIb32





F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0



L-Aggregation Rule

Rtotal

Table 353 VS.UpsizingUnsuccessNeighbRnc - #1168

A-Description

the number of unsuccessful upsizings, screened by Downlink Access Stratum Configuration,for each neighboring RNC. The measurement attached to a neighboring RNC is incremented ifthe neighboring RNC controls the reference cell of the involved UE.

B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccessful implementation of an "Always On" algorithm decision to restore the full UE cap-abilities

D-Result








E-Type

• VS.UpsizingUnsuccessNeighbRnc.VS.UpsizingUnsuccessNeighbRnc.DchHsdpa

• VS.UpsizingUnsuccessNeighbRnc.VS.UpsizingUnsuccessNeighbRnc.DchPsIb32





F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 354 VS.IRMSchedulingDowngradedSuccess - #1169

A-Description

the number of successful RB throughput downgradings performed by the iRM scheduling fea-ture (FRS #22459), screened by Downlink Access Stratum Configuration, for the current refer-ence cell of the UE. Considered DLASConfigurations are the DLASConfigurations beforethroughput downgrading.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful establishment of the downgraded throughput.

D-Result

A set of subcounters screened on: IRM Scheduling Downgrade Rate Mapping





• Sub-Counter #4 : DCH PS Str 64



E-Type

• VS.IRMSchedulingDowngradedSuccess.VS.IRMSchedulingDowngradedSuccess.DchPsIb64






• VS.IRMSchedulingDowngradedSuccess.VS.IRMSchedulingDowngradedSuccess.DchPsStr64



F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 355 VS.IRMSchedulingDowngradedFailure - #1170

A-Description

the number of failed RB throughput downgradings encountered by the iRM scheduling feature(FRS #22459), screened by Downlink Access Stratum Configuration, for the current referencecell of the UE. Considered DLASConfigurations are the DLASConfigurations before throughputdowngrading

B-Collection

CUM

CUMulative

C-Condition (Event)



Failed establishment of the downgraded throughput.

D-Result









E-Type

• VS.IRMSchedulingDowngradedFailure.VS.IRMSchedulingDowngradedFailure.DchPsIb64




• VS.IRMSchedulingDowngradedFailure.VS.IRMSchedulingDowngradedFailure.DchPsStr64



F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule



Rtotal

Table 356 VS.IRMSchedulingDowngradedSuccessNeighbRnc - #1171

A-Description

the number of successful RB throughput downgradings performed by the iRM scheduling fea-ture (FRS #22459), screened by Downlink Access Stratum Configuration, for each neighboringRNC. The measurement attached to a given neighboring RNC is incremented each time a suc-cess on a RB throughput downgrading is detected on a UE which current reference cell is con-trolled by the neighboring RNC. Considered DL Access Stratum Configurations are the DLAS-Configurations before throughput downgrading

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful establishment of the downgraded throughput.

D-Result









E-Type

• VS.IRMSchedulingDowngradedSuccessNeighbRnc.VS.IRMSchedulingDowngradedSuccessNeighbRnc.DchPsIb64




• VS.IRMSchedulingDowngradedSuccessNeighbRnc.VS.IRMSchedulingDowngradedSuccessNeighbRnc.DchPsStr64





F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 357 VS.IRMSchedulingDowngradedFailureNeighbRnc - #1172

A-Description

the number of failed RB throughput downgradings encountered by the iRM scheduling feature(FRS #22459), screened by Downlink Access Stratum Configuration, for each neighboringRNC. The measurement attached to a given neighboring RNC is incremented each time a fail-ure on a RB throughput downgrading is detected on a UE which current reference cell is con-trolled by the neighboring RNC. Considered DL Access Stratum Configurations are the DLAS-Configurations before throughput downgrading.

B-Collection

CUM

CUMulative

C-Condition (Event)

Failed establishment of the downgraded throughput.

D-Result











E-Type

• VS.IRMSchedulingDowngradedFailureNeighbRnc.VS.IRMSchedulingDowngradedFailureNeighbRnc.DchPsIb64




• VS.IRMSchedulingDowngradedFailureNeighbRnc.VS.IRMSchedulingDowngradedFailureNeighbRnc.DchPsStr64



F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 358 VS.IrmUpgradingSuccessful - #1173



A-Description

the number of times the iRM Upgrading was successfully executed (upgrading to a high or in-termediate bitrate).

B-Collection

CUM

CUMulative

C-Condition (Event)

Reconfiguration of the bearer successfully executed for iRM upgrading (RRC RB Reconfigura-tion Response) .

D-Result

A set of subcounters screened on: BR Category

• Sub-Counter #0 : High BR

• Sub-Counter #1 : Intermediate BR

E-Type

• VS.IrmUpgradingSuccessful.VS.IrmUpgradingSuccessful.HighBitRate

• VS.IrmUpgradingSuccessful.VS.IrmUpgradingSuccessful.LowBitRate

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 359 VS.IrmUpgradingCommand - #1174

A-Description



Number of upgrading commands for the primary cells on SRNC

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful RRM order of eligible RB combined on receipt of EventB (B1 or B2) MeasurementReport for the primary cell on SRNC

D-Result




E-Type

• VS.IrmUpgradingCommand.VS.IrmUpgradingCommand.HighBitRate

• VS.IrmUpgradingCommand.VS.IrmUpgradingCommand.LowBitRate

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 360 VS.IrmUpgradingCommandNrnc - #1175

A-Description

Number of upgrading commands for the primary cells on DRNC

B-Collection



CUM

CUMulative

C-Condition (Event)

Successful RRM order of eligible RB combined on receipt of EventB (B1 or B2) MeasurementReport for the primary cell on DRNC

D-Result




E-Type

• VS.IrmUpgradingCommandNrnc.VS.IrmUpgradingCommandNrnc.HighBitRate

• VS.IrmUpgradingCommandNrnc.VS.IrmUpgradingCommandNrnc.LowBitRate

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 361 VS.IrmUpgradingSuccessfulNrnc - #1176

A-Description

Number of successful upgradings for the primary cells on DRNC

B-Collection

CUM

CUMulative



C-Condition (Event)

A successful Reconf triggered by the DMC function for the primary cells on DRNC

D-Result




E-Type

• VS.IrmUpgradingSuccessfulNrnc.VS.IrmUpgradingSuccessfulNrnc.HighBitRate

• VS.IrmUpgradingSuccessfulNrnc.VS.IrmUpgradingSuccessfulNrnc.LowBitRate

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 362 VS.QosDlCemLdClrYellow - #1177

A-Description

Load counter that tracks the percentage of time during a collection period that a particular cellis considered yellow by CEM load because of CEM radio resource shortage in downlink

B-Collection

LOAD

C-Condition (Event)

CEM load algorithm changes cell color to or from yellow

D-Result



one measurement

E-Type

VS.QosDlCemLdClrYellow

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

0-1

J-Unit

percent

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 363 VS.QosDlCemLdClrRed - #1178

A-Description

Load counter that tracks the percentage of time during a collection period that a particular cellis considered red by CEM load because of CEM radio resource shortage in downlink

B-Collection

LOAD

C-Condition (Event)

CEM load algorithm changes cell color to or from red

D-Result

one measurement

E-Type

VS.QosDlCemLdClrRed

F-Object Instance

Cell

G-Switching



NA

H-3GPP Compliance


I-Range

0-1

J-Unit

percent

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 364 VS.QosDlCemLdCellPreemptClrCngstd - #1179

A-Description

Load counter that tracks the percentage of time during a collection period that a particular cellis considered congested by iRM because CEM shortage in downlink

B-Collection

LOAD

C-Condition (Event)

Cell Preemption Color transitions for CEM load : Normal to Congested; Congested to Normal

D-Result

one measurement

E-Type

VS.QosDlCemLdCellPreemptClrCngstd

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

0-1

J-Unit



percent

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 365 VS.QosUlCemLdClrYellow - #1180

A-Description

Load counter that tracks the percentage of time during a collection period that a particular cellis considered yellow by CEM load because of CEM radio resource shortage in downlink

B-Collection

LOAD

C-Condition (Event)

CEM load algorithm changes cell color to or from yellow

D-Result

one measurement

E-Type

VS.QosUlCemLdClrYellow

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

0-1

J-Unit

percent

K-Available Release

V5.0

L-Aggregation Rule

Rload



Table 366 VS.QosUlCemLdClrRed - #1181

A-Description

Load counter that tracks the percentage of time during a collection period that a particular cellis considered red by CEM load because of CEM radio resource shortage in downlink

B-Collection

LOAD

C-Condition (Event)

CEM load algorithm changes cell color to or from red

D-Result

one measurement

E-Type

VS.QosUlCemLdClrRed

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

0-1

J-Unit

percent

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 367 VS.IrmTimeDlIubTransportColorRed - #1182

A-Description

the ratio of time a cell is considered red for Downlink IubTransport by iRM during a reportingperiod (Average value). The minimum value allows to know if the cell has never been con-sidered green by the iRM during the reporting period. The maximum value allows to know if thecell has been considered green, at least once, by the iRM during the reporting period.

B-Collection



LOAD

C-Condition (Event)

IRM changes cell color to or from Red because of Downlink Iub transport resource shortage

D-Result


• Sub-Counter #0 : Iub Transport Color DL PS IB DCH

• Sub-Counter #1 : Iub Transport Color DL PS STR DCH

• Sub-Counter #2 : Iub Transport Color DL CS

E-Type

• VS.IrmTimeDlIubTransportColorRed.VS.IrmTimeDlIubTransportColorRed.DlPsIbDch

• VS.IrmTimeDlIubTransportColorRed.VS.IrmTimeDlIubTransportColorRed.DlPsStrDch

• VS.IrmTimeDlIubTransportColorRed.VS.IrmTimeDlIubTransportColorRed.DlCs

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

0-100%

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 368 VS.IrmTimeDlIubTransportColorYellow - #1183

A-Description

the ratio of time a cell is considered yellow for Downlink IubTransport by iRM during a reportingperiod (Average value). The minimum value allows to know if the cell has never been con-sidered green by the iRM during the reporting period. The maximum value allows to know if thecell has been considered green, at least once, by the iRM during the reporting period

B-Collection



LOAD

C-Condition (Event)

IRM changes cell color to or from Yellow because of Downlink Iub transport resource shortage

D-Result


• Sub-Counter #0 : Iub Transport Color DL PS IB DCH

• Sub-Counter #1 : Iub Transport Color DL PS STR DCH

• Sub-Counter #2 : Iub Transport Color DL CS

E-Type

• VS.IrmTimeDlIubTransportColorYellow.VS.IrmTimeDlIubTransportColorYellow.DlPsIbDch

• VS.IrmTimeDlIubTransportColorYellow.VS.IrmTimeDlIubTransportColorYellow.DlPsStrDch

• VS.IrmTimeDlIubTransportColorYellow.VS.IrmTimeDlIubTransportColorYellow.DlCs

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

0-100%

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 369 VS.UlIrmcacMaintainedGold - #1184

A-Description

Number of RAB assignments for high priority users (Allocation/Retention Priority of 0) that aremaintained as requested by UL iRM

B-Collection

CUM



CUMulative

C-Condition (Event)

UL iRM table algorithm performance

D-Result

A set of subcounters screened on: UL PS RbSet

• Sub-Counter #0 : PS Other




E-Type

• VS.UlIrmcacMaintainedGold.VS.UlIrmcacMaintainedGold.PsOther

• VS.UlIrmcacMaintainedGold.VS.UlIrmcacMaintainedGold.PsIb64



F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 370 VS.UlIrmcacMaintainedSilver - #1185

A-Description

Number of RAB assignments for medium priority users (Allocation/Retention Priority of 1) thatare maintained as requested by UL iRM



B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result






E-Type

• VS.UlIrmcacMaintainedSilver.VS.UlIrmcacMaintainedSilver.PsOther

• VS.UlIrmcacMaintainedSilver.VS.UlIrmcacMaintainedSilver.PsIb64



F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 371 VS.UlIrmcacMaintainedBronze - #1186

A-Description



Number of RAB assignments for low priority users (Allocation/Retention Priority of 2) that aremaintained as requested by UL iRM

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result






E-Type

• VS.UlIrmcacMaintainedBronze.VS.UlIrmcacMaintainedBronze.PsOther

• VS.UlIrmcacMaintainedBronze.VS.UlIrmcacMaintainedBronze.PsIb64



F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 372 VS.UlIrmcacDowngradedGold - #1187

A-Description

Number of RAB assignments for high priority users (Allocation/Retention Priority of 0) that aredowngraded as requested by UL iRM

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result






E-Type

• VS.UlIrmcacDowngradedGold.VS.UlIrmcacDowngradedGold.PsOther

• VS.UlIrmcacDowngradedGold.VS.UlIrmcacDowngradedGold.PsIb64



F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule



Rtotal

Table 373 VS.UlIrmcacDowngradedSilver - #1188

A-Description

Number of RAB assignments for medium priority users (Allocation/Retention Priority of 1) thatare downgraded as requested by UL iRM

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result






E-Type

• VS.UlIrmcacDowngradedSilver.VS.UlIrmcacDowngradedSilver.PsOther

• VS.UlIrmcacDowngradedSilver.VS.UlIrmcacDowngradedSilver.PsIb64



F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V5.0

L-Aggregation Rule

Rtotal

Table 374 VS.UlIrmcacDowngradedBronze - #1189

A-Description

Number of RAB assignments for low priority users (Allocation/Retention Priority of 2) that aredowngraded as requested by UL iRM

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result






E-Type

• VS.UlIrmcacDowngradedBronze.VS.UlIrmcacDowngradedBronze.PsOther

• VS.UlIrmcacDowngradedBronze.VS.UlIrmcacDowngradedBronze.PsIb64



F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 375 VS.UlIrmcacRejectedGold - #1190

A-Description

Number of RAB assignments for high priority users (Allocation/Retention Priority of 0) that arerejected as requested by UL iRM

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

one measurement

E-Type

VS.UlIrmcacRejectedGold

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 376 VS.UlIrmcacRejectedSilver - #1191

A-Description

Number of RAB assignments for medium priority users (Allocation/Retention Priority of 1) thatare rejected as requested by UL iRM

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

one measurement

E-Type

VS.UlIrmcacRejectedSilver

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 377 VS.UlIrmcacRejectedBronze - #1192

A-Description

Number of RAB assignments for low priority users (Allocation/Retention Priority of 2) that arerejected as requested by UL iRM

B-Collection



CUM

CUMulative

C-Condition (Event)


D-Result

one measurement

E-Type

VS.UlIrmcacRejectedBronze

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 378 VS.IRMTimeULRadioLoadColorYellow - #1193

A-Description

Percentage of time during a collection period that the UL Radio Load color is yellow for the re-lating cell.

B-Collection

LOAD

C-Condition (Event)

Each time that the UL load color becomes yellow or is no longer yellow

D-Result

one measurement



E-Type

VS.IRMTimeULRadioLoadColorYellow

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 379 VS.IRMTimeULRadioLoadColorRed - #1194

A-Description

Percentage of time during a collection period that the UL Radio Load color is red for the relat-ing cell.

B-Collection

LOAD

C-Condition (Event)

Each time that the UL load color becomes red or is no longer red

D-Result

one measurement

E-Type

VS.IRMTimeULRadioLoadColorRed

F-Object Instance

Cell

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload

Table 380 VS.HsPdschDynCodeMgmtStealing - #1195

A-Description

After activation of the feature called HSDPA dynamic downlink code tree management and fora particular cell, this is the number of times the stealing of OVSF SFx codes for DCH is reques-ted and successful

B-Collection

CUM

CUMulative

C-Condition (Event)

The RNC decides to steal codes for DCH. An NBAP procedure called Physical Shared Chan-nel Reconfiguration is initiated. This operation is successful

D-Result

one measurement

E-Type

VS.HsPdschDynCodeMgmtStealing

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 381 VS.HsPdschDynCodeMgmtRealloc - #1196

A-Description

After activation of the feature called HSDPA dynamic downlink code tree management and fora particular cell, this is the number of times the reallocation of OVSF SFx codes for HS-PDSCHis requested and successful

B-Collection

CUM

CUMulative

C-Condition (Event)

The RNC decides to reallocated codes for HS-PDSCH. An NBAP procedure called PhysicalShared Channel Reconfiguration is initiated. This operation is successful

D-Result

one measurement

E-Type

VS.HsPdschDynCodeMgmtRealloc

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V5.0

L-Aggregation Rule

Rtotal

Table 382 VS.NumHsPdschCodes - #1197

A-Description

For a particular cell, this is number of HS-PDSCH codes as required in message PHYSICALSHARED CHANNEL RECONFIGURATION for this feature (see TS 25.433, Section 9.2.2.18F).This counter offers the mean of measuring average, minimum and maximum values for the ob-served quantity NumberOfHsPdschCodes

B-Collection

LOAD

C-Condition (Event)

The RNC decides to steal codes for DCH. Or the RNC decides to reallocated codes for HS-PDSCH. An NBAP procedure called Physical Shared Channel Reconfiguration is initiated.

D-Result

one measurement

E-Type

VS.NumHsPdschCodes

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rload





5.13 User Plane Common Traffic

These counters are computed and sent from the I-Node through a specific stream to the C-Nodewhich writes them on disk in the same file as any other Callp counters computed on C-Node.


Counter name

#1213 VS.CommonMacDownlinkPcchSdu

#1214 VS.CommonMacDownlinkCcchSdu

#1215 VS.CommonMacDownlinkDcchOverFachSdu

#1216 VS.CommonMacDownlinkDtchOverFachSdu

#1217 VS.CommonMacUplinkCcchSdu

#1218 VS.CommonMacUplinkDcchOverRachSdu

#1219 VS.CommonMacUplinkDtchOverRachSdu

#1220 VS.CommonRlcCcchDownlinkKbytes

#1221 VS.CommonRlcCcchDownlinkSdu

#1222 VS.CommonRlcCcchDiscardSdu

#1223 VS.CommonRlcCcchPadding

#1224 VS.CommonUplinkTrafficChnlSyncFrames

#1225 VS.CommonUplinkTimingAdjustmentFrames

Table 383 VS.CommonMacDownlinkPcchSdu - #1213

A-Description

the number of SDUs received by the MAC layer for the PCCH of the cell in the downlink direc-tion

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a SDU at MAC layer for downlink PCCH

D-Result

one measurement

E-Type

VS.CommonMacDownlinkPcchSdu

F-Object Instance



Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 384 VS.CommonMacDownlinkCcchSdu - #1214

A-Description

the number of SDUs received by the MAC layer for the CCCH of the cell in the downlink direc-tion

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a SDU at MAC layer for downlink CCCH

D-Result

one measurement

E-Type

VS.CommonMacDownlinkCcchSdu

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 385 VS.CommonMacDownlinkDcchOverFachSdu - #1215

A-Description

the number of SDUs received by the MAC layer for a DCCH over the FACH of the cell in thedownlink direction

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a SDU at MAC layer for downlink DCCH over FACH

D-Result

one measurement

E-Type

VS.CommonMacDownlinkDcchOverFachSdu

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V3.1

L-Aggregation Rule

Rtotal

Table 386 VS.CommonMacDownlinkDtchOverFachSdu - #1216

A-Description

the number of SDUs received by the MAC layer for a DTCH over the FACH of the cell in thedownlink direction

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a SDU at MAC layer for downlink DTCH over FACH

D-Result

one measurement

E-Type

VS.CommonMacDownlinkDtchOverFachSdu

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 387 VS.CommonMacUplinkCcchSdu - #1217



A-Description

the number of SDUs received by the MAC layer for the CCCH of the cell in the uplink direction

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a SDU at MAC layer for uplink CCCH

D-Result

one measurement

E-Type

VS.CommonMacUplinkCcchSdu

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 388 VS.CommonMacUplinkDcchOverRachSdu - #1218

A-Description

the number of SDUs received by the MAC layer for a DCCH over the RACH of the cell in theuplink direction

B-Collection

CUM

CUMulative



C-Condition (Event)

Receipt of a SDU at MAC layer for uplink DCCH over RACH

D-Result

one measurement

E-Type

VS.CommonMacUplinkDcchOverRachSdu

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 389 VS.CommonMacUplinkDtchOverRachSdu - #1219

A-Description

the number of SDUs received by the MAC layer for a DTCH over the RACH of the cell in theuplink direction

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a SDU at MAC layer for uplink DTCH over RACH

D-Result

one measurement

E-Type



VS.CommonMacUplinkDtchOverRachSdu

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 390 VS.CommonRlcCcchDownlinkKbytes - #1220

A-Description

the total count of downlink RLC payload on CCCH.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RLC SDU the downlink CCCH. On the SDU emission, the counter isincreased with the value of the emitted SDU payload.

D-Result

one measurement

E-Type

VS.CommonRlcCcchDownlinkKbytes

F-Object Instance

Cell

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 391 VS.CommonRlcCcchDownlinkSdu - #1221

A-Description

the number of RLC SDU sent on downlink CCCH.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RLC SDU on the downlink CCCH.

D-Result

one measurement

E-Type

VS.CommonRlcCcchDownlinkSdu

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 392 VS.CommonRlcCcchDiscardSdu - #1222

A-Description

the number of RLC SDU discarded on CCCH.

B-Collection

CUM

CUMulative

C-Condition (Event)

Discard of a RLC SDU for CCCH.

D-Result

one measurement

E-Type

VS.CommonRlcCcchDiscardSdu

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal



Table 393 VS.CommonRlcCcchPadding - #1223

A-Description

the total count of dummy padding added to downlink RLC PDU on CCCH.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RLC PDU on the downlink CCCH. On the PDU emission, thecounter is increased with the value of the emitted PDU dummy padding.

D-Result

one measurement

E-Type

VS.CommonRlcCcchPadding

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 394 VS.CommonUplinkTrafficChnlSyncFrames - #1224

A-Description

the number of uplink traffic channel SYNC frames on the Iub for the cell.

B-Collection

CUM



CUMulative

C-Condition (Event)

Reception of an uplink traffic SYNC frame on the Iub.

D-Result

one measurement

E-Type

VS.CommonUplinkTrafficChnlSyncFrames

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 395 VS.CommonUplinkTimingAdjustmentFrames - #1225

A-Description

the number of timing adjustment frames on the Iub for the cell.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a timing adjustment frame on the Iub.

D-Result

one measurement

E-Type



VS.CommonUplinkTimingAdjustmentFrames

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal



5.14 IUR Interface

The reference document for Iur management is 3GPP TS25.423 Iur Interface RNSAP Signaling.


Counter name

#1302 VS.IurDrncRadioLinkSetupUnsuccess

#1304 VS.IurDrncRadioLinkAdditionUnsuccess

#1306 VS.IurDrncRadioLinkDeletionSuccess

#1308 VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess

#1311 VS.IurSccpCnxSuccess

#1312 VS.IurSccpCnxUnsuccess

#1315 VS.IurAvgNbrInitSccpCnx

#1316 VS.IurAvgNbrTermSccpCnx

#1317 VS.IurEmittedSccpAbnormalDisconnects

#1318 VS.IurReceivedSccpAbnormalDisconnects

#1319 VS.IurDrncRadioLinkReconfigurationCancel

#1320 VS.IurDrncRadioLinkSetupSuccess

#1321 VS.IurDrncRadioLinkAdditionSuccess

#1322 VS.IurDrncRadioLinkReconfigurationPrepareSuccess

#1323 VS.IurDrncRadioLinkReconfigurationCommit

#1324 VS.IurSrncRelocCommit

#1325 VS.IurDrncRelocCommit

Table 396 VS.IurDrncRadioLinkSetupUnsuccess - #1302

A-Description

the number of radio links failed in setup on a RNSAP point of view, screened by set-up failurecause.

B-Collection

CUM

CUMulative

C-Condition (Event)

This measurement is based on two different events: - Emission of a RNSAP RADIO LINKSETUP FAILURE message sent by the Drift RNC to the Serving RNC in response to a RADIOLINK SETUP REQUEST message. - The measurement considers each Radio Link referred asfailed in the RNSAP RADIO LINK SETUP FAILURE message. - Time-out expired without emis-



sion of a RADIO LINK SETUP RESPONSE message or RADIO LINK SETUP FAILURE mes-sage. The measurement considers each Radio Link required to set-up in the RNSAP RADIOLINK SETUP REQUEST message.

D-Result

A set of subcounters screened on: Cause for unsuccess

• Sub-Counter #0 : unspecified

• Sub-Counter #1 : No radio resource

• Sub-Counter #2 : Nbap refusal

• Sub-Counter #3 : requested configuration not support

E-Type

• VS.IurDrncRadioLinkSetupUnsuccess.VS.IurDrncRadioLinkSetupUnsuccess.Unspecified

• VS.IurDrncRadioLinkSetupUnsuccess.VS.IurDrncRadioLinkSetupUnsuccess.NoRadioResource

• VS.IurDrncRadioLinkSetupUnsuccess.VS.IurDrncRadioLinkSetupUnsuccess.NbapRefusal

• VS.IurDrncRadioLinkSetupUnsuccess.VS.IurDrncRadioLinkSetupUnsuccess.RequestedConfigurationNotSupport

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 397 VS.IurDrncRadioLinkAdditionUnsuccess - #1304

A-Description

the number of radio links failed in addition on a RNSAP point of view, screened by addition fail-



ure cause.

B-Collection

CUM

CUMulative

C-Condition (Event)

This measurement is based on two different events: - Emission of a RNSAP RADIO LINK AD-DITION FAILURE message sent by the Drift RNC to the Serving RNC in response to a RADIOLINK ADDITION REQUEST message. - The measurement considers each Radio Link referredas failed in the RNSAP RADIO LINK ADDITION FAILURE message. - Time-out expiredwithout emission of a RADIO LINK ADDITION RESPONSE message or a RADIO LINK ADDI-TION FAILURE message. The measurement considers each Radio Link required to addition inthe RNSAP RADIO LINK ADDITION REQUEST message.

D-Result






E-Type

• VS.IurDrncRadioLinkAdditionUnsuccess.VS.IurDrncRadioLinkAdditionUnsuccess.Unspecified

• VS.IurDrncRadioLinkAdditionUnsuccess.VS.IurDrncRadioLinkAdditionUnsuccess.NoRadioResource

• VS.IurDrncRadioLinkAdditionUnsuccess.VS.IurDrncRadioLinkAdditionUnsuccess.NbapRefusal

• VS.IurDrncRadioLinkAdditionUnsuccess.VS.IurDrncRadioLinkAdditionUnsuccess.RequestedConfigurationNotSupport

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 398 VS.IurDrncRadioLinkDeletionSuccess - #1306

A-Description

the number of radio-links successfully deleted on a RNSAP point of view.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a RNSAP RADIO LINK DELETION RESPONSE message sent by the Drift RNC tothe Serving RNC in response to a RADIO LINK DELETION REQUEST. The measurementconsiders each Radio Link referred in the RNSAP RADIO LINK DELETION RESPONSE mes-sage

D-Result

one measurement

E-Type

VS.IurDrncRadioLinkDeletionSuccess

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1



L-Aggregation Rule

Rtotal

Table 399 VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess - #1308

A-Description

the number of radio links failed in reconfiguration preparation on a RNSAP point of view,screened by cause of reconfiguration preparation failure.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a RNSAP RADIO LINK RECONFIGURATION FAILURE message sent by the DriftRNC to the Serving RNC in response to a RADIO LINK RECONFIGURATION PREPARE mes-sage or no emission of RADIO LINK RECONFIGURATION READY message before a time-out

D-Result






• Sub-Counter #4 : Lack of CID on the Iur




E-Type

• VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.Unspecified

• VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.NoRadioResource

• VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.NbapRefusal

• VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.RequestedConfigurationNotSupport

• VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.LackCidIur

• VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.VS.IurDrncRadioLinkReconfigurati



onPrepareUnsuccess.LackBwthIur

• VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.LackCidIub

• VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess.LackBwthIub

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 400 VS.IurSccpCnxSuccess - #1311

A-Description

the number of successful SCCP connections at Iur interface for each neighboring RNC of aconsidered RNC. The incrementation takes place on the neighboring RNC object, whatever thesource of the request is the local RNC or the distant RNC.

B-Collection

CUM

CUMulative

C-Condition (Event)

Successful SCCP connection establishment (confirm OK)

D-Result

A set of subcounters screened on: Per type of core, per sens of refusal

• Sub-Counter #0 : Established as Serving Rnc

• Sub-Counter #1 : Established as Drift Rnc



E-Type

• VS.IurSccpCnxSuccess.VS.IurSccpCnxSuccess.EstablishedAsServingRnc

• VS.IurSccpCnxSuccess.VS.IurSccpCnxSuccess.EstablishedAsDriftRnc

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 401 VS.IurSccpCnxUnsuccess - #1312

A-Description

the number of failed SCCP connections at Iur interface, for each neighboring RNC of a givenRNC

B-Collection

CUM

CUMulative

C-Condition (Event)

Unsuccessful SCCP connection establishment

D-Result

A set of subcounters screened on: Per type of core, per cause of refusal

• Sub-Counter #0 : Fail connection req by local iRnc on Iur

• Sub-Counter #1 : Fail connection req by neighbouring iRnc on Iur

E-Type

• VS.IurSccpCnxUnsuccess.VS.IurSccpCnxUnsuccess.FailConnectionReqByLocalIRncOnIu



r

• VS.IurSccpCnxUnsuccess.VS.IurSccpCnxUnsuccess.FailConnectionReqByNeighbouringIRncOnIur

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal

Table 402 VS.IurAvgNbrInitSccpCnx - #1315

A-Description

the average number of SCCP connections on Iur initiated toward a neighboring RNC during thereporting period. Minimum and maximum number of initiations over the period are alsoprovided.

B-Collection

LOAD

C-Condition (Event)

SCCP connection on Iur initiated toward that neighboring RNC or torn down. It is not affectedby refused SCCP connections. The number of initiated SCCP connections is sampled each100ms.

D-Result

one measurement

E-Type

VS.IurAvgNbrInitSccpCnx

F-Object Instance



Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rload

Table 403 VS.IurAvgNbrTermSccpCnx - #1316

A-Description

the average number of SCCP connections on Iur terminated from a neighboring RNC duringthe reporting period. Minimum and maximum number of terminations over the period are alsoprovided.

B-Collection

LOAD

C-Condition (Event)

SCCP connection on Iur terminated from that neighboring RNC or torn down. It is not affectedby refused SCCP connections. The number of terminating SCCP connections is sampled each100ms.

D-Result

one measurement

E-Type

VS.IurAvgNbrTermSccpCnx

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rload

Table 404 VS.IurEmittedSccpAbnormalDisconnects - #1317

A-Description

the number of emitted SCCP abnormal disconnections on Iur

B-Collection

CUM

CUMulative

C-Condition (Event)

Emitted SCCP abnormal disconnections on Iur

D-Result





E-Type

• VS.IurEmittedSccpAbnormalDisconnects.VS.IurEmittedSccpAbnormalDisconnects.EndUserOriginated

• VS.IurEmittedSccpAbnormalDisconnects.VS.IurEmittedSccpAbnormalDisconnects.EndUserCongestion

• VS.IurEmittedSccpAbnormalDisconnects.VS.IurEmittedSccpAbnormalDisconnects.EndUserFailure

F-Object Instance

Neighbouring RNC

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 405 VS.IurReceivedSccpAbnormalDisconnects - #1318

A-Description

the number of received SCCP abnormal disconnections on Iur

B-Collection

CUM

CUMulative

C-Condition (Event)

Received SCCP abnormal disconnections on Iur

D-Result

one measurement

E-Type

VS.IurReceivedSccpAbnormalDisconnects

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V3.1

L-Aggregation Rule

Rtotal

Table 406 VS.IurDrncRadioLinkReconfigurationCancel - #1319

A-Description

the number of RNSAP RADIO LINK RECONFIGURATION CANCEL messages.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RNSAP RADIO LINK RECONFIGURATION CANCEL message by the Drift-RNC from the Serving RNC.

D-Result

one measurement

E-Type

VS.IurDrncRadioLinkReconfigurationCancel

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 407 VS.IurDrncRadioLinkSetupSuccess - #1320

A-Description

the number of radio-links successfully setup on a RNSAP point of view, screened by DownlinkAccess Stratum configuration.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a RADIO LINK SETUP RESPONSE or RADIO LINK SETUP FAILURE RNSAPmessage by the Drift RNC to the Serving RNC in response to a RADIO LINK SETUP RE-QUEST message. The measurement considers each Radio Link mentioned as set-up in theRADIO LINK SETUP RESPONSE or RADIO LINK SETUP FAILURE RNSAP message.

D-Result














E-Type

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfOther

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfSig

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfCsSpeech

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfCsData

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfCsStr

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfPsStr



• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfPsIB

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfCsSpeechPsIB

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfCsDataPsIB

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfPsStrPsIB

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfCsSpeechPsStr

• VS.IurDrncRadioLinkSetupSuccess.VS.IurDrncRadioLinkSetupSuccess.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 408 VS.IurDrncRadioLinkAdditionSuccess - #1321

A-Description

the number of radio-links successfully added on a RNSAP point of view, screened by DownlinkAccess Stratum configuration.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of a RADIO LINK ADDITION RESPONSE or RADIO LINK ADDITION FAILURERNSAP message sent by the Drift RNC to the Serving RNC in response to a RADIO LINK AD-



DITION REQUEST message. The measurement considers each Radio Link mentioned as ad-ded in the RADIO LINK ADDITION RESPONSE or RADIO LINK ADDITION FAILURE RNSAPmessage.

D-Result














E-Type

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfOther

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfSig

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfCsSpeech

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfCsData

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfCsStr

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfPsStr

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfPsIB

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfCsSpeechPsIB

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfCsDataPsIB

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfPsStrPsIB

• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfCsSpeechPsStr



• VS.IurDrncRadioLinkAdditionSuccess.VS.IurDrncRadioLinkAdditionSuccess.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 409 VS.IurDrncRadioLinkReconfigurationPrepareSuccess - #1322

A-Description

the number of radio-links successfully prepared for reconfiguration , screened by Downlink Ac-cess Stratum configuration.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission of an RNSAP RADIO LINK RECONFIGURATION READY message. The measure-ment considers each Radio Link referred in the RNSAP RADIO LINK RECONFIGURATIONREADY message.

D-Result
















E-Type

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfOther

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfSig

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfCsSpeech

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfCsData

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfCsStr

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfPsStr

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfPsIB

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfCsSpeechPsIB

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfCsDataPsIB

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfPsStrPsIB

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfCsSpeechPsStr

• VS.IurDrncRadioLinkReconfigurationPrepareSuccess.VS.IurDrncRadioLinkReconfigurationPrepareSuccess.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 410 VS.IurDrncRadioLinkReconfigurationCommit - #1323

A-Description

the number of RNSAP RADIO LINK RECONFIGURATION COMMIT messages.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RNSAP RADIO LINK RECONFIGURATION COMMIT message by the driftRNC from the Serving RNC.

D-Result
















E-Type

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfOther

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfSig

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfCsSpeech

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfCsData

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfCsStr

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfPsStr

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfPsIB

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfCsSpeechPsIB

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfCsDataPsIB

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfPsStrPsIB

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfCsSpeechPsStr

• VS.IurDrncRadioLinkReconfigurationCommit.VS.IurDrncRadioLinkReconfigurationCommit.DlAsCnfCsSpeechPsStrPsIB

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event



K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 411 VS.IurSrncRelocCommit - #1324

A-Description

Number of Relocation Commit messages sent over IuR.

B-Collection

CUM

CUMulative

C-Condition (Event)

RNSAP Relocation Commit sent on the Iur interface.

D-Result

one measurement

E-Type

VS.IurSrncRelocCommit

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 412 VS.IurDrncRelocCommit - #1325



A-Description

Number of Relocation Commit messages received over IuR.

B-Collection

CUM

CUMulative

C-Condition (Event)

RNSAP Relocation Commit received on the Iur interface.

D-Result

one measurement

E-Type

VS.IurDrncRelocCommit

F-Object Instance

Neighbouring RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.15 User Plane Dedicated Traffic


Counter name

#1437 VS.IuCsTimingAdjustmentRequests

#1438 VS.IuCsTimingAdjustmentAcks

#1439 VS.IuCsTimingAdjustmentNacks

#1440 VS.IuCsTimingAdjustmentUnsupported

#1441 VS.IuCsTimingAdjustmentTimeouts

#1470 VS.HsdpaIubFPDiscardedBytes

#1471 VS.DedicatedUplinkBadPdusRlcRefCell

#1472 VS.DedicatedUplinkKbytesRlc

#1473 VS.DedicatedDownlinkKbytesRlc

#1474 VS.DedicatedUplinkPduRlc

#1475 VS.DedicatedDownlinkPduRlc

#1476 VS.DedicatedUplinkSduRlc

#1477 VS.DedicatedDownlinkSduRlc

#1478 VS.DedicatedUplinkMissingPduRlc

#1479 VS.DedicatedDownlinkDiscardSduRlc

#1480 VS.DedicatedDownlinkPaddingSduRlc

#1481 VS.DedicatedUplinkBadPdus

#1484 VS.DedicatedUplinkKbytesRlcActiveCells

#1485 VS.DedicatedDownlinkKbytesRlcActiveCells

#1486 VS.DedicatedUplinkKbytesRlcReferenceCell

#1487 VS.DedicatedDownlinkKbytesRlcReferenceCell

#1488 VS.DedicatedUplinkPdusRlcReferenceCell

#1489 VS.DedicatedDownlinkPdusRlcReferenceCell

#1490 VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell

#1491 VS.RlcUnrecoverableError

#1492 VS.DlDiscardNonConfTraffic

#1493 VS.UlDiscardNonConfTraffic

#1494 VS.EdchIubTnlCongestIndc

#1495 VS.EdchMacTsnReassemblyErr

#1496 VS.EdchFpRetransHarq

#1497 VS.BmcCtchTrafVol




Counter name

#1502 VS.HsdschIubUlXoFrmCnt

#1503 VS.HsdschIubDlTrfcBlkTmCnt

#1504 VS.DchIubDlTrfcBlkTmCnt

#1505 VS.IuDlAmrFrmFqc

#1506 VS.DdUlAmrABtGoodFrm

#1507 VS.DdUlAmrABtBadFrm

#1508 VS.HsdpaIubDlControlFrames

#1509 VS.HsdpaIubNonZeroCapacityAlloc

#1510 VS.HsdpaIubZeroCapacityAlloc

#1511 VS.HsdpaIubCreditsRequested

#1512 VS.HsdpaIubCreditsConsumed

#1513 VS.AmrClDlRt

#1514 VS.AmrClUlRt

#1515 VS.DlAmrRtChg

#1516 VS.IuRcvdAmrRtCtrl

#1521 VS.OvinCnAccLaDscrd

#1522 VS.OvinNiDscrd

#1523 VS.OvinRabRrcConReqDscrd

#1524 VS.DedicatedUplinkSduRlcRefCell

#1525 VS.DedicatedDownlinkSduRlcRefCell

#1526 VS.DedicatedDownlinkActivityRlcRefCell

#1527 VS.DedicatedUplinkActivityRlcRefCell

#1528 VS.IrmcacDistIubLoad

#1529 VS.DedicatedUplinkBadPdusRlcReferenceCell

Table 413 VS.IuCsTimingAdjustmentRequests - #1437

A-Description

Number of Iu CS Timing Adjustment requests sent to the CS Core Network

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending Iu Timing Adjustment request to CS Core Network (part of Iu Frame Protocol)

D-Result



A set of subcounters screened on: Combined Maximum Ul Dl Bit Rate CS Only

• Sub-Counter #0 : Other Dl, Ul combinations

• Sub-Counter #1 : Dl,Ul is 2,2 or 5,5 or 5,2 or 2,5

• Sub-Counter #2 : Dl,Ul is 0,4



E-Type

• VS.IuCsTimingAdjustmentRequests.VS.IuCsTimingAdjustmentRequests.RabCsOther

• VS.IuCsTimingAdjustmentRequests.VS.IuCsTimingAdjustmentRequests.RabCsConv12_2

• VS.IuCsTimingAdjustmentRequests.VS.IuCsTimingAdjustmentRequests.RabCsConv64

• VS.IuCsTimingAdjustmentRequests.VS.IuCsTimingAdjustmentRequests.RabCsStr14_4

• VS.IuCsTimingAdjustmentRequests.VS.IuCsTimingAdjustmentRequests.RabCsStr57_6

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 414 VS.IuCsTimingAdjustmentAcks - #1438

A-Description

Number of Iu CS Timing Adjustment acknowledgements received from the CS Core Network

B-Collection

CUM

CUMulative



C-Condition (Event)

Iu Timing Adjustment ack received from CS Core Network (part of Iu Frame Protocol)

D-Result







E-Type

• VS.IuCsTimingAdjustmentAcks.VS.IuCsTimingAdjustmentAcks.RabCsOther

• VS.IuCsTimingAdjustmentAcks.VS.IuCsTimingAdjustmentAcks.RabCsConv12_2

• VS.IuCsTimingAdjustmentAcks.VS.IuCsTimingAdjustmentAcks.RabCsConv64

• VS.IuCsTimingAdjustmentAcks.VS.IuCsTimingAdjustmentAcks.RabCsStr14_4

• VS.IuCsTimingAdjustmentAcks.VS.IuCsTimingAdjustmentAcks.RabCsStr57_6

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 415 VS.IuCsTimingAdjustmentNacks - #1439

A-Description

Number of Iu CS Timing Adjustment nacks received from the CS Core Network



B-Collection

CUM

CUMulative

C-Condition (Event)

Iu Timing Adjustment nack received from CS Core Network (part of Iu Frame Protocol)

D-Result







E-Type

• VS.IuCsTimingAdjustmentNacks.VS.IuCsTimingAdjustmentNacks.RabCsOther

• VS.IuCsTimingAdjustmentNacks.VS.IuCsTimingAdjustmentNacks.RabCsConv12_2

• VS.IuCsTimingAdjustmentNacks.VS.IuCsTimingAdjustmentNacks.RabCsConv64

• VS.IuCsTimingAdjustmentNacks.VS.IuCsTimingAdjustmentNacks.RabCsStr14_4

• VS.IuCsTimingAdjustmentNacks.VS.IuCsTimingAdjustmentNacks.RabCsStr57_6

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal



Table 416 VS.IuCsTimingAdjustmentUnsupported - #1440

A-Description

Number of Iu CS Timing Adjustment unsupported responses received from the CS Core Net-work.

B-Collection

CUM

CUMulative

C-Condition (Event)

Iu Timing Adjustment unsupported response received from CS Core Network (part of Iu FrameProtocol)

D-Result







E-Type

• VS.IuCsTimingAdjustmentUnsupported.VS.IuCsTimingAdjustmentUnsupported.RabCsOther

• VS.IuCsTimingAdjustmentUnsupported.VS.IuCsTimingAdjustmentUnsupported.RabCsConv12_2

• VS.IuCsTimingAdjustmentUnsupported.VS.IuCsTimingAdjustmentUnsupported.RabCsConv64

• VS.IuCsTimingAdjustmentUnsupported.VS.IuCsTimingAdjustmentUnsupported.RabCsStr14_4

• VS.IuCsTimingAdjustmentUnsupported.VS.IuCsTimingAdjustmentUnsupported.RabCsStr57_6

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 417 VS.IuCsTimingAdjustmentTimeouts - #1441

A-Description

Number of Iu CS Timing Adjustment requests that timed out before receiving esponse from theCS Core Network

B-Collection

CUM

CUMulative

C-Condition (Event)

Iu Timing Adjustment ack request timeout

D-Result







E-Type

• VS.IuCsTimingAdjustmentTimeouts.VS.IuCsTimingAdjustmentTimeouts.RabCsOther

• VS.IuCsTimingAdjustmentTimeouts.VS.IuCsTimingAdjustmentTimeouts.RabCsConv12_2

• VS.IuCsTimingAdjustmentTimeouts.VS.IuCsTimingAdjustmentTimeouts.RabCsConv64

• VS.IuCsTimingAdjustmentTimeouts.VS.IuCsTimingAdjustmentTimeouts.RabCsStr14_4

• VS.IuCsTimingAdjustmentTimeouts.VS.IuCsTimingAdjustmentTimeouts.RabCsStr57_6

F-Object Instance

RNC

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 418 VS.HsdpaIubFPDiscardedBytes - #1470

A-Description

counts the number of bytes discarded on the Iub HS-DSCH FP. The counter precision is afunction of the PC update reporting period.

B-Collection

CUM

CUMulative

C-Condition (Event)

Periodically reported from Pc to RAB. Periodicity will be in the order of seconds or when a giv-en amount of data is reached whichever comes first.

D-Result

one measurement

E-Type

VS.HsdpaIubFPDiscardedBytes

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V4.1

L-Aggregation Rule

Rtotal

Table 419 VS.DedicatedUplinkBadPdusRlcRefCell - #1471

A-Description

Number of bad PDUs sent on Dedicated uplink for the reference cell

B-Collection

CUM

CUMulative

C-Condition (Event)

Bad PDUs sent on Dedicated uplink for the reference cell

D-Result

A set of subcounters screened on: Uplink Traffic Counter Screenings , see also Annex: T01


• Sub-Counter #1 : Any SRB


• Sub-Counter #3 : CS 64 conversational

• Sub-Counter #4 : CS 14.4 streaming


• Sub-Counter #6 : Any PS streaming

• Sub-Counter #7 : PS I/B 8kbps






E-Type

• VS.DedicatedUplinkBadPdusRlcRefCell.VS.DedicatedUplinkBadPdusRlcRefCell.UlRabOth



er

• VS.DedicatedUplinkBadPdusRlcRefCell.VS.DedicatedUplinkBadPdusRlcRefCell.UlRabSRB

• VS.DedicatedUplinkBadPdusRlcRefCell.VS.DedicatedUplinkBadPdusRlcRefCell.UlRabCsSpeech

• VS.DedicatedUplinkBadPdusRlcRefCell.VS.DedicatedUplinkBadPdusRlcRefCell.UlRabCsData64

• VS.DedicatedUplinkBadPdusRlcRefCell.VS.DedicatedUplinkBadPdusRlcRefCell.UlRabCsStr14_4

• VS.DedicatedUplinkBadPdusRlcRefCell.VS.DedicatedUplinkBadPdusRlcRefCell.UlRabCsStr57_6

• VS.DedicatedUplinkBadPdusRlcRefCell.VS.DedicatedUplinkBadPdusRlcRefCell.UlRabPsStr

• VS.DedicatedUplinkBadPdusRlcRefCell.VS.DedicatedUplinkBadPdusRlcRefCell.UlRabPsIb8





• VS.DedicatedUplinkBadPdusRlcRefCell.VS.DedicatedUplinkBadPdusRlcRefCell.UlRabHsupa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0



L-Aggregation Rule

Rtotal

Table 420 VS.DedicatedUplinkKbytesRlc - #1472

A-Description

the total amount of uplink RLC payload (SDU) received on dedicated channels (Traffic RadioBearers and Signalling Radio Bearers). This is incremented for the Current RAB and any RLCSDU payload received (Q01371476).

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception by the RNC of a RLC SDU on an uplink dedicated channel. On the SDU reception,the counter is increased with the value of the received SDU payload.

D-Result















E-Type

• VS.DedicatedUplinkKbytesRlc.VS.DedicatedUplinkKbytesRlc.UlRabOther

• VS.DedicatedUplinkKbytesRlc.VS.DedicatedUplinkKbytesRlc.UlRabSRB

• VS.DedicatedUplinkKbytesRlc.VS.DedicatedUplinkKbytesRlc.UlRabCsSpeech

• VS.DedicatedUplinkKbytesRlc.VS.DedicatedUplinkKbytesRlc.UlRabCsData64

• VS.DedicatedUplinkKbytesRlc.VS.DedicatedUplinkKbytesRlc.UlRabCsStr14_4



• VS.DedicatedUplinkKbytesRlc.VS.DedicatedUplinkKbytesRlc.UlRabCsStr57_6

• VS.DedicatedUplinkKbytesRlc.VS.DedicatedUplinkKbytesRlc.UlRabPsStr

• VS.DedicatedUplinkKbytesRlc.VS.DedicatedUplinkKbytesRlc.UlRabPsIb8





• VS.DedicatedUplinkKbytesRlc.VS.DedicatedUplinkKbytesRlc.UlRabHsupa

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 421 VS.DedicatedDownlinkKbytesRlc - #1473

A-Description

the total count of downlink RLC payload (SDU) sent on dedicated channels (Traffic RadioBearers and Signalling Radio Bearers).

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RLC SDU on a downlink dedicated channel. On the SDU emission,the counter is increased with the value of the emitted SDU payload.



D-Result

A set of subcounters screened on: Downlink Traffic Counter Screenings , see also Annex: T02















E-Type

• VS.DedicatedDownlinkKbytesRlc.VS.DedicatedDownlinkKbytesRlc.DlRabOther

• VS.DedicatedDownlinkKbytesRlc.VS.DedicatedDownlinkKbytesRlc.DlRabSRB

• VS.DedicatedDownlinkKbytesRlc.VS.DedicatedDownlinkKbytesRlc.DlRabCsSpeech

• VS.DedicatedDownlinkKbytesRlc.VS.DedicatedDownlinkKbytesRlc.DlRabCsData64

• VS.DedicatedDownlinkKbytesRlc.VS.DedicatedDownlinkKbytesRlc.DlRabCsStr14_4

• VS.DedicatedDownlinkKbytesRlc.VS.DedicatedDownlinkKbytesRlc.DlRabCsStr57_6

• VS.DedicatedDownlinkKbytesRlc.VS.DedicatedDownlinkKbytesRlc.DlRabHsdpa

• VS.DedicatedDownlinkKbytesRlc.VS.DedicatedDownlinkKbytesRlc.DlRabPsStr

• VS.DedicatedDownlinkKbytesRlc.VS.DedicatedDownlinkKbytesRlc.DlRabPsIb8






F-Object Instance

RNC

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 422 VS.DedicatedUplinkPduRlc - #1474

A-Description

the number of Uplink RLC PDU received on dedicated channels. This is incremented for theCurrent RAB and any RLC PDU received (Q01371476). Notes: in cases where data is trans-mitted on coordinated transport channels, the frames of each subflow are not counted inde-pendently. The PDU and SDU counters are incremented only once for each set of frames re-ceived or sent. An RLC PDU is a frame sent (see TS 25.322) from the RLC to the MAC (or viceversa). For CS voice, counting occurs for data frame, SID frame and empty frame. Emptyframes are being counted for BLER reason (Q01168175). For bearers where RLC is in trans-parent mode, this counter also includes received frames that contain no payload.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception by the RNC of a RLC PDU on an uplink dedicated channel.

D-Result

















E-Type

• VS.DedicatedUplinkPduRlc.VS.DedicatedUplinkPduRlc.UlRabOther

• VS.DedicatedUplinkPduRlc.VS.DedicatedUplinkPduRlc.UlRabSRB

• VS.DedicatedUplinkPduRlc.VS.DedicatedUplinkPduRlc.UlRabCsSpeech

• VS.DedicatedUplinkPduRlc.VS.DedicatedUplinkPduRlc.UlRabCsData64

• VS.DedicatedUplinkPduRlc.VS.DedicatedUplinkPduRlc.UlRabCsStr14_4

• VS.DedicatedUplinkPduRlc.VS.DedicatedUplinkPduRlc.UlRabCsStr57_6

• VS.DedicatedUplinkPduRlc.VS.DedicatedUplinkPduRlc.UlRabPsStr

• VS.DedicatedUplinkPduRlc.VS.DedicatedUplinkPduRlc.UlRabPsIb8





• VS.DedicatedUplinkPduRlc.VS.DedicatedUplinkPduRlc.UlRabHsupa

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0



L-Aggregation Rule

Rtotal

Table 423 VS.DedicatedDownlinkPduRlc - #1475

A-Description

the number of downlink RLC PDU emitted on dedicated channels.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RLC PDU on a downlink dedicated channel.

D-Result
















E-Type

• VS.DedicatedDownlinkPduRlc.VS.DedicatedDownlinkPduRlc.DlRabOther

• VS.DedicatedDownlinkPduRlc.VS.DedicatedDownlinkPduRlc.DlRabSRB

• VS.DedicatedDownlinkPduRlc.VS.DedicatedDownlinkPduRlc.DlRabCsSpeech

• VS.DedicatedDownlinkPduRlc.VS.DedicatedDownlinkPduRlc.DlRabCsData64

• VS.DedicatedDownlinkPduRlc.VS.DedicatedDownlinkPduRlc.DlRabCsStr14_4

• VS.DedicatedDownlinkPduRlc.VS.DedicatedDownlinkPduRlc.DlRabCsStr57_6



• VS.DedicatedDownlinkPduRlc.VS.DedicatedDownlinkPduRlc.DlRabHsdpa

• VS.DedicatedDownlinkPduRlc.VS.DedicatedDownlinkPduRlc.DlRabPsStr

• VS.DedicatedDownlinkPduRlc.VS.DedicatedDownlinkPduRlc.DlRabPsIb8






F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 424 VS.DedicatedUplinkSduRlc - #1476

A-Description

the number of Uplink RLC SDU received on dedicated channels. This is incremented for theCurrent RAB and any RLC SDU received (Q01371476). Notes: in cases where data is trans-mitted on coordinated transport channels, the frames of each subflow are not counted inde-pendently. The PDU and SDU counters are incremented only once for each set of frames re-ceived or sent.

B-Collection

CUM

CUMulative

C-Condition (Event)



Reception by the RNC of an RLC SDU on an uplink dedicated channel.

D-Result















E-Type

• VS.DedicatedUplinkSduRlc.VS.DedicatedUplinkSduRlc.UlRabOther

• VS.DedicatedUplinkSduRlc.VS.DedicatedUplinkSduRlc.UlRabSRB

• VS.DedicatedUplinkSduRlc.VS.DedicatedUplinkSduRlc.UlRabCsSpeech

• VS.DedicatedUplinkSduRlc.VS.DedicatedUplinkSduRlc.UlRabCsData64

• VS.DedicatedUplinkSduRlc.VS.DedicatedUplinkSduRlc.UlRabCsStr14_4

• VS.DedicatedUplinkSduRlc.VS.DedicatedUplinkSduRlc.UlRabCsStr57_6

• VS.DedicatedUplinkSduRlc.VS.DedicatedUplinkSduRlc.UlRabPsStr

• VS.DedicatedUplinkSduRlc.VS.DedicatedUplinkSduRlc.UlRabPsIb8





• VS.DedicatedUplinkSduRlc.VS.DedicatedUplinkSduRlc.UlRabHsupa

F-Object Instance

RNC

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 425 VS.DedicatedDownlinkSduRlc - #1477

A-Description

the number of downlink RLC SDU emitted on dedicated channels.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RLC SDU on a downlink dedicated channel.

D-Result


















E-Type

• VS.DedicatedDownlinkSduRlc.VS.DedicatedDownlinkSduRlc.DlRabOther

• VS.DedicatedDownlinkSduRlc.VS.DedicatedDownlinkSduRlc.DlRabSRB

• VS.DedicatedDownlinkSduRlc.VS.DedicatedDownlinkSduRlc.DlRabCsSpeech

• VS.DedicatedDownlinkSduRlc.VS.DedicatedDownlinkSduRlc.DlRabCsData64

• VS.DedicatedDownlinkSduRlc.VS.DedicatedDownlinkSduRlc.DlRabCsStr14_4

• VS.DedicatedDownlinkSduRlc.VS.DedicatedDownlinkSduRlc.DlRabCsStr57_6

• VS.DedicatedDownlinkSduRlc.VS.DedicatedDownlinkSduRlc.DlRabHsdpa

• VS.DedicatedDownlinkSduRlc.VS.DedicatedDownlinkSduRlc.DlRabPsStr

• VS.DedicatedDownlinkSduRlc.VS.DedicatedDownlinkSduRlc.DlRabPsIb8






F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 426 VS.DedicatedUplinkMissingPduRlc - #1478



A-Description

the number of lost Uplink RLC PDU on dedicated channels (this does not take into account re-transmitted PDUs that are lost). Incremented for the Current RAB and each missing sequencenumber on PDUs received by RLCs (Q01371476). Notes : screenings 1, 2, 3, 4 are alwayszero because RLC cannot provide TM mode (Q01262533).

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception by the RNC of a RLC PDU on an uplink dedicated channel with a sequence numberindicating a "hole" in the reception (ie. "greater" than current VR(H), which corresponds to thenext PDU that we are expecting, excluding retransmissions) . The counter is incremented bythe number of missing PDUs that are detected (sn - VR(H), with the modulus).

D-Result















E-Type

• VS.DedicatedUplinkMissingPduRlc.VS.DedicatedUplinkMissingPduRlc.UlRabOther

• VS.DedicatedUplinkMissingPduRlc.VS.DedicatedUplinkMissingPduRlc.UlRabSRB

• VS.DedicatedUplinkMissingPduRlc.VS.DedicatedUplinkMissingPduRlc.UlRabCsSpeech

• VS.DedicatedUplinkMissingPduRlc.VS.DedicatedUplinkMissingPduRlc.UlRabCsData64

• VS.DedicatedUplinkMissingPduRlc.VS.DedicatedUplinkMissingPduRlc.UlRabCsStr14_4

• VS.DedicatedUplinkMissingPduRlc.VS.DedicatedUplinkMissingPduRlc.UlRabCsStr57_6



• VS.DedicatedUplinkMissingPduRlc.VS.DedicatedUplinkMissingPduRlc.UlRabPsStr

• VS.DedicatedUplinkMissingPduRlc.VS.DedicatedUplinkMissingPduRlc.UlRabPsIb8





• VS.DedicatedUplinkMissingPduRlc.VS.DedicatedUplinkMissingPduRlc.UlRabHsupa

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 427 VS.DedicatedDownlinkDiscardSduRlc - #1479

A-Description

the number of downlink RLC SDU discarded on dedicated channels.

B-Collection

CUM

CUMulative

C-Condition (Event)

Each time a SDU containing Packet Switched RB data is discarded without having been sentsuccessfully on an downlink dedicated channel.

D-Result


















E-Type

• VS.DedicatedDownlinkDiscardSduRlc.VS.DedicatedDownlinkDiscardSduRlc.DlRabOther

• VS.DedicatedDownlinkDiscardSduRlc.VS.DedicatedDownlinkDiscardSduRlc.DlRabSRB

• VS.DedicatedDownlinkDiscardSduRlc.VS.DedicatedDownlinkDiscardSduRlc.DlRabCsSpeech

• VS.DedicatedDownlinkDiscardSduRlc.VS.DedicatedDownlinkDiscardSduRlc.DlRabCsData64

• VS.DedicatedDownlinkDiscardSduRlc.VS.DedicatedDownlinkDiscardSduRlc.DlRabCsStr14_4

• VS.DedicatedDownlinkDiscardSduRlc.VS.DedicatedDownlinkDiscardSduRlc.DlRabCsStr57_6

• VS.DedicatedDownlinkDiscardSduRlc.VS.DedicatedDownlinkDiscardSduRlc.DlRabHsdpa

• VS.DedicatedDownlinkDiscardSduRlc.VS.DedicatedDownlinkDiscardSduRlc.DlRabPsStr

• VS.DedicatedDownlinkDiscardSduRlc.VS.DedicatedDownlinkDiscardSduRlc.DlRabPsIb8






F-Object Instance



RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 428 VS.DedicatedDownlinkPaddingSduRlc - #1480

A-Description

the total count of dummy padding added to downlink RLC PDU on dedicated channels. This isincremented for the Current RAB and any RLC PDU sent (Q01371476). Notes : screenings 1,2, 3, 4 are always zero because RLC cannot provide TM mode (Q01262533).

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RLC PDU on a downlink dedicated channel. On the PDU emission,the counter is increased with the value of the dummy padding in the PDU.

D-Result


















E-Type

• VS.DedicatedDownlinkPaddingSduRlc.VS.DedicatedDownlinkPaddingSduRlc.DlRabOther

• VS.DedicatedDownlinkPaddingSduRlc.VS.DedicatedDownlinkPaddingSduRlc.DlRabSRB

• VS.DedicatedDownlinkPaddingSduRlc.VS.DedicatedDownlinkPaddingSduRlc.DlRabCsSpeech

• VS.DedicatedDownlinkPaddingSduRlc.VS.DedicatedDownlinkPaddingSduRlc.DlRabCsData64

• VS.DedicatedDownlinkPaddingSduRlc.VS.DedicatedDownlinkPaddingSduRlc.DlRabCsStr14_4

• VS.DedicatedDownlinkPaddingSduRlc.VS.DedicatedDownlinkPaddingSduRlc.DlRabCsStr57_6

• VS.DedicatedDownlinkPaddingSduRlc.VS.DedicatedDownlinkPaddingSduRlc.DlRabHsdpa

• VS.DedicatedDownlinkPaddingSduRlc.VS.DedicatedDownlinkPaddingSduRlc.DlRabPsStr

• VS.DedicatedDownlinkPaddingSduRlc.VS.DedicatedDownlinkPaddingSduRlc.DlRabPsIb8






F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 429 VS.DedicatedUplinkBadPdus - #1481

A-Description

the total number of Transport Blocks received with CRCi = 1 (transport block contains errors)on a CS or PS bearer (this does not include SRBs). For voice, CRCi only applies to Class Abits.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of PDU (CRCI=1) on uplink for a CS or PS Traffic Radio Bearer. Basically from thetime the mobile moves to cell FACH, it is not sending anything anymore on the dedicated chan-nel. However the NodeB is not aware of this and it demodulates and decodes the channel any-way, that is its job. Every frame received is then interpreted has an errored frame and an Iubframe is sent to the interface Node with a CRCI that worthes 1. This is necessary on a normalbasis for the interface node to assess the BLER and adjust SIRtarget here it is not the wantedbehavior but the NodeB cannot distinguish the case of an Always On downgrade to cell FACH.

D-Result

















E-Type

• VS.DedicatedUplinkBadPdus.VS.DedicatedUplinkBadPdus.UlRabOther

• VS.DedicatedUplinkBadPdus.VS.DedicatedUplinkBadPdus.UlRabSRB

• VS.DedicatedUplinkBadPdus.VS.DedicatedUplinkBadPdus.UlRabCsSpeech

• VS.DedicatedUplinkBadPdus.VS.DedicatedUplinkBadPdus.UlRabCsData64

• VS.DedicatedUplinkBadPdus.VS.DedicatedUplinkBadPdus.UlRabCsStr14_4

• VS.DedicatedUplinkBadPdus.VS.DedicatedUplinkBadPdus.UlRabCsStr57_6

• VS.DedicatedUplinkBadPdus.VS.DedicatedUplinkBadPdus.UlRabPsStr

• VS.DedicatedUplinkBadPdus.VS.DedicatedUplinkBadPdus.UlRabPsIb8





• VS.DedicatedUplinkBadPdus.VS.DedicatedUplinkBadPdus.UlRabHsupa

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 430 VS.DedicatedUplinkKbytesRlcActiveCells - #1484

A-Description

the total number of Kbytes of RLC SDU received on uplink on dedicated channels for each cellof the active set. This is incremented for the Current RAB and any RLC SDU payload received(Q01371476).

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception by the RNC of a RLC SDU on an uplink dedicated channel. On the SDU reception,the counter is increased with the value of the received SDU payload for all cells in the activeset of the call.

D-Result















E-Type

• VS.DedicatedUplinkKbytesRlcActiveCells.VS.DedicatedUplinkKbytesRlcActiveCells.UlRabOther

• VS.DedicatedUplinkKbytesRlcActiveCells.VS.DedicatedUplinkKbytesRlcActiveCells.UlRabSRB

• VS.DedicatedUplinkKbytesRlcActiveCells.VS.DedicatedUplinkKbytesRlcActiveCells.UlRabCsSpeech

• VS.DedicatedUplinkKbytesRlcActiveCells.VS.DedicatedUplinkKbytesRlcActiveCells.UlRab



CsData64

• VS.DedicatedUplinkKbytesRlcActiveCells.VS.DedicatedUplinkKbytesRlcActiveCells.UlRabCsStr14_4

• VS.DedicatedUplinkKbytesRlcActiveCells.VS.DedicatedUplinkKbytesRlcActiveCells.UlRabCsStr57_6

• VS.DedicatedUplinkKbytesRlcActiveCells.VS.DedicatedUplinkKbytesRlcActiveCells.UlRabPsStr

• VS.DedicatedUplinkKbytesRlcActiveCells.VS.DedicatedUplinkKbytesRlcActiveCells.UlRabPsIb8





• VS.DedicatedUplinkKbytesRlcActiveCells.VS.DedicatedUplinkKbytesRlcActiveCells.UlRabHsupa

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

Kbytes

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 431 VS.DedicatedDownlinkKbytesRlcActiveCells - #1485

A-Description



the total number of Kbytes of RLC SDU sent on downlink on dedicated channels for each cellof the active set

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RLC SDU containing on a downlink dedicated channel. On the SDUemission, the counter is increased with the value of the emitted SDU payload for all cells in theactive set of the call.

D-Result
















E-Type

• VS.DedicatedDownlinkKbytesRlcActiveCells.VS.DedicatedDownlinkKbytesRlcActiveCells.DlRabOther

• VS.DedicatedDownlinkKbytesRlcActiveCells.VS.DedicatedDownlinkKbytesRlcActiveCells.DlRabSRB

• VS.DedicatedDownlinkKbytesRlcActiveCells.VS.DedicatedDownlinkKbytesRlcActiveCells.DlRabCsSpeech

• VS.DedicatedDownlinkKbytesRlcActiveCells.VS.DedicatedDownlinkKbytesRlcActiveCells.DlRabCsData64

• VS.DedicatedDownlinkKbytesRlcActiveCells.VS.DedicatedDownlinkKbytesRlcActiveCells.DlRabCsStr14_4



• VS.DedicatedDownlinkKbytesRlcActiveCells.VS.DedicatedDownlinkKbytesRlcActiveCells.DlRabCsStr57_6

• VS.DedicatedDownlinkKbytesRlcActiveCells.VS.DedicatedDownlinkKbytesRlcActiveCells.DlRabHsdpa

• VS.DedicatedDownlinkKbytesRlcActiveCells.VS.DedicatedDownlinkKbytesRlcActiveCells.DlRabPsStr

• VS.DedicatedDownlinkKbytesRlcActiveCells.VS.DedicatedDownlinkKbytesRlcActiveCells.DlRabPsIb8






F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

Kbytes

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 432 VS.DedicatedUplinkKbytesRlcReferenceCell - #1486

A-Description

the total amount of RLC SDU received on uplink on dedicated channels for the reference cell ofthe active set. This is incremented for the Current RAB and any RLC SDU payload received



(Q01371476).

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception by the RNC of a RLC SDU on an uplink dedicated channel. On the SDU reception,the counter is increased with the value of the received SDU payload on the reference cell ofthe active set of the call.

D-Result















E-Type

• VS.DedicatedUplinkKbytesRlcReferenceCell.VS.DedicatedUplinkKbytesRlcReferenceCell.UlRabOther

• VS.DedicatedUplinkKbytesRlcReferenceCell.VS.DedicatedUplinkKbytesRlcReferenceCell.UlRabSRB

• VS.DedicatedUplinkKbytesRlcReferenceCell.VS.DedicatedUplinkKbytesRlcReferenceCell.UlRabCsSpeech

• VS.DedicatedUplinkKbytesRlcReferenceCell.VS.DedicatedUplinkKbytesRlcReferenceCell.UlRabCsData64

• VS.DedicatedUplinkKbytesRlcReferenceCell.VS.DedicatedUplinkKbytesRlcReferenceCell.UlRabCsStr14_4

• VS.DedicatedUplinkKbytesRlcReferenceCell.VS.DedicatedUplinkKbytesRlcReferenceCell.UlRabCsStr57_6



• VS.DedicatedUplinkKbytesRlcReferenceCell.VS.DedicatedUplinkKbytesRlcReferenceCell.UlRabPsStr

• VS.DedicatedUplinkKbytesRlcReferenceCell.VS.DedicatedUplinkKbytesRlcReferenceCell.UlRabPsIb8





• VS.DedicatedUplinkKbytesRlcReferenceCell.VS.DedicatedUplinkKbytesRlcReferenceCell.UlRabHsupa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

Kbytes

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 433 VS.DedicatedDownlinkKbytesRlcReferenceCell - #1487

A-Description

the total number of Kbytes of RLC SDU sent on downlink on dedicated channels for the refer-ence cell of the active set.

B-Collection

CUM

CUMulative



C-Condition (Event)

Emission by the RNC of a RLC SDU containing on a downlink dedicated channel. On the SDUemission, the counter is increased with the value of the emitted SDU payload on the referencecell of the active set of the call.

D-Result
















E-Type

• VS.DedicatedDownlinkKbytesRlcReferenceCell.VS.DedicatedDownlinkKbytesRlcReferenceCell.DlRabOther

• VS.DedicatedDownlinkKbytesRlcReferenceCell.VS.DedicatedDownlinkKbytesRlcReferenceCell.DlRabSRB

• VS.DedicatedDownlinkKbytesRlcReferenceCell.VS.DedicatedDownlinkKbytesRlcReferenceCell.DlRabCsSpeech

• VS.DedicatedDownlinkKbytesRlcReferenceCell.VS.DedicatedDownlinkKbytesRlcReferenceCell.DlRabCsData64

• VS.DedicatedDownlinkKbytesRlcReferenceCell.VS.DedicatedDownlinkKbytesRlcReferenceCell.DlRabCsStr14_4

• VS.DedicatedDownlinkKbytesRlcReferenceCell.VS.DedicatedDownlinkKbytesRlcReferenceCell.DlRabCsStr57_6

• VS.DedicatedDownlinkKbytesRlcReferenceCell.VS.DedicatedDownlinkKbytesRlcReferenceCell.DlRabHsdpa

• VS.DedicatedDownlinkKbytesRlcReferenceCell.VS.DedicatedDownlinkKbytesRlcReferenceCell.DlRabPsStr



• VS.DedicatedDownlinkKbytesRlcReferenceCell.VS.DedicatedDownlinkKbytesRlcReferenceCell.DlRabPsIb8






F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

Kbytes

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 434 VS.DedicatedUplinkPdusRlcReferenceCell - #1488

A-Description

the number of Uplink RLC PDU received on dedicated channels for the reference cell. This isincremented for the Current RAB and any RLC PDU received (Q01371476). Note: Alternately,number of PDU received on dedicated uplink RLC for the reference cell (Q01168175). An RLCPDU is a frame sent (see TS 25.322) from the RLC to the MAC (or vice versa). For CS voice,counting occurs for data frame, SID frame and empty frame. Empty frames are being countedfor BLER reason (Q01168175).

B-Collection

CUM



CUMulative

C-Condition (Event)

Reception by the RNC of a RLC PDU on an uplink dedicated channel. The counter is only in-cremented on the reference cell of the call.

D-Result















E-Type

• VS.DedicatedUplinkPdusRlcReferenceCell.VS.DedicatedUplinkPdusRlcReferenceCell.UlRabOther

• VS.DedicatedUplinkPdusRlcReferenceCell.VS.DedicatedUplinkPdusRlcReferenceCell.UlRabSRB

• VS.DedicatedUplinkPdusRlcReferenceCell.VS.DedicatedUplinkPdusRlcReferenceCell.UlRabCsSpeech

• VS.DedicatedUplinkPdusRlcReferenceCell.VS.DedicatedUplinkPdusRlcReferenceCell.UlRabCsData64

• VS.DedicatedUplinkPdusRlcReferenceCell.VS.DedicatedUplinkPdusRlcReferenceCell.UlRabCsStr14_4

• VS.DedicatedUplinkPdusRlcReferenceCell.VS.DedicatedUplinkPdusRlcReferenceCell.UlRabCsStr57_6

• VS.DedicatedUplinkPdusRlcReferenceCell.VS.DedicatedUplinkPdusRlcReferenceCell.UlRabPsStr

• VS.DedicatedUplinkPdusRlcReferenceCell.VS.DedicatedUplinkPdusRlcReferenceCell.UlRabPsIb8

• VS.DedicatedUplinkPdusRlcReferenceCell.VS.DedicatedUplinkPdusRlcReferenceCell.UlR



abPsIb32




• VS.DedicatedUplinkPdusRlcReferenceCell.VS.DedicatedUplinkPdusRlcReferenceCell.UlRabHsupa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 435 VS.DedicatedDownlinkPdusRlcReferenceCell - #1489

A-Description

the number of downlink RLC PDU emitted on dedicated channels on the reference cell.

B-Collection

CUM

CUMulative

C-Condition (Event)

Emission by the RNC of a RLC PDU on an downlink dedicated channel. The counter is only in-cremented on the reference cell of the call.

D-Result


















E-Type

• VS.DedicatedDownlinkPdusRlcReferenceCell.VS.DedicatedDownlinkPdusRlcReferenceCell.DlRabOther

• VS.DedicatedDownlinkPdusRlcReferenceCell.VS.DedicatedDownlinkPdusRlcReferenceCell.DlRabSRB

• VS.DedicatedDownlinkPdusRlcReferenceCell.VS.DedicatedDownlinkPdusRlcReferenceCell.DlRabCsSpeech

• VS.DedicatedDownlinkPdusRlcReferenceCell.VS.DedicatedDownlinkPdusRlcReferenceCell.DlRabCsData64

• VS.DedicatedDownlinkPdusRlcReferenceCell.VS.DedicatedDownlinkPdusRlcReferenceCell.DlRabCsStr14_4

• VS.DedicatedDownlinkPdusRlcReferenceCell.VS.DedicatedDownlinkPdusRlcReferenceCell.DlRabCsStr57_6

• VS.DedicatedDownlinkPdusRlcReferenceCell.VS.DedicatedDownlinkPdusRlcReferenceCell.DlRabHsdpa

• VS.DedicatedDownlinkPdusRlcReferenceCell.VS.DedicatedDownlinkPdusRlcReferenceCell.DlRabPsStr

• VS.DedicatedDownlinkPdusRlcReferenceCell.VS.DedicatedDownlinkPdusRlcReferenceCell.DlRabPsIb8








F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 436 VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell - #1490

A-Description

the number of downlink RLC PDU retransmitted on dedicated channels on the reference cell.This counter is only pegged for RLC AM bearer (so only for PS). This is incremented for theCurrent RAB and any RLC PDU (Q01371476). screenings 1, 2, 3, 4 are always zero becauseRLC cannot provide TM mode (Q01262533).

B-Collection

CUM

CUMulative

C-Condition (Event)

Retransmission by the RNC of an RLC PDU on a downlink dedicated channel. The counter isonly incremented on the reference cell of the call.

D-Result


















E-Type

• VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.DlRabOther

• VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.DlRabSRB

• VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.DlRabCsSpeech

• VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.DlRabCsData64

• VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.DlRabCsStr14_4

• VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.DlRabCsStr57_6

• VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.DlRabHsdpa

• VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.DlRabPsStr

• VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.DlRabPsIb8



• VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell.VS.DedicatedDownlinkRetran



smittedPdusRlcReferenceCell.DlRabPsIb128



F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 437 VS.RlcUnrecoverableError - #1491

A-Description

Number of RLC unrecoverable errors detected by the PMC RAB.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of a RLC unrecoverable error notification from the iNode.

D-Result


















E-Type

• VS.RlcUnrecoverableError.VS.RlcUnrecoverableError.DlRabOther

• VS.RlcUnrecoverableError.VS.RlcUnrecoverableError.DlRabSRB

• VS.RlcUnrecoverableError.VS.RlcUnrecoverableError.DlRabCsSpeech

• VS.RlcUnrecoverableError.VS.RlcUnrecoverableError.DlRabCsData64

• VS.RlcUnrecoverableError.VS.RlcUnrecoverableError.DlRabCsStr14_4

• VS.RlcUnrecoverableError.VS.RlcUnrecoverableError.DlRabCsStr57_6

• VS.RlcUnrecoverableError.VS.RlcUnrecoverableError.DlRabHsdpa

• VS.RlcUnrecoverableError.VS.RlcUnrecoverableError.DlRabPsStr

• VS.RlcUnrecoverableError.VS.RlcUnrecoverableError.DlRabPsIb8






F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 438 VS.DlDiscardNonConfTraffic - #1492

A-Description

Counts the number of Kilo Bytes of data discarded by I-Node if the source is non-conformant.INode only discards the data above the agreed maximum data-rate. This counter is onlytriggered for non-conformant sources.

B-Collection

CUM

CUMulative

C-Condition (Event)

Non Conformant Source

D-Result


















E-Type

• VS.DlDiscardNonConfTraffic.VS.DlDiscardNonConfTraffic.DlRabOther

• VS.DlDiscardNonConfTraffic.VS.DlDiscardNonConfTraffic.DlRabSRB

• VS.DlDiscardNonConfTraffic.VS.DlDiscardNonConfTraffic.DlRabCsSpeech

• VS.DlDiscardNonConfTraffic.VS.DlDiscardNonConfTraffic.DlRabCsData64

• VS.DlDiscardNonConfTraffic.VS.DlDiscardNonConfTraffic.DlRabCsStr14_4

• VS.DlDiscardNonConfTraffic.VS.DlDiscardNonConfTraffic.DlRabCsStr57_6

• VS.DlDiscardNonConfTraffic.VS.DlDiscardNonConfTraffic.DlRabHsdpa

• VS.DlDiscardNonConfTraffic.VS.DlDiscardNonConfTraffic.DlRabPsStr

• VS.DlDiscardNonConfTraffic.VS.DlDiscardNonConfTraffic.DlRabPsIb8






F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 439 VS.UlDiscardNonConfTraffic - #1493

A-Description

Counts the number of Kilo Bytes of data discarded by I-Node in UL if the source is non-



conformant. This counter is only triggered for non-conformant sources.

B-Collection

CUM

CUMulative

C-Condition (Event)

Non Conformant Uplink Traffic Source

D-Result















E-Type

• VS.UlDiscardNonConfTraffic.VS.UlDiscardNonConfTraffic.UlRabOther

• VS.UlDiscardNonConfTraffic.VS.UlDiscardNonConfTraffic.UlRabSRB

• VS.UlDiscardNonConfTraffic.VS.UlDiscardNonConfTraffic.UlRabCsSpeech

• VS.UlDiscardNonConfTraffic.VS.UlDiscardNonConfTraffic.UlRabCsData64

• VS.UlDiscardNonConfTraffic.VS.UlDiscardNonConfTraffic.UlRabCsStr14_4

• VS.UlDiscardNonConfTraffic.VS.UlDiscardNonConfTraffic.UlRabCsStr57_6

• VS.UlDiscardNonConfTraffic.VS.UlDiscardNonConfTraffic.UlRabPsStr

• VS.UlDiscardNonConfTraffic.VS.UlDiscardNonConfTraffic.UlRabPsIb8







• VS.UlDiscardNonConfTraffic.VS.UlDiscardNonConfTraffic.UlRabHsupa

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

Kbytes

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 440 VS.EdchIubTnlCongestIndc - #1494

A-Description

Number of E-DCH Congestion Indication sent.

B-Collection

CUM

CUMulative

C-Condition (Event)

Each time an E-DCH Congestion Indication frame is sent to the NodeB.

D-Result

A set of subcounters screened on: E-DCH Congestion Indication cause.

• Sub-Counter #0 : No Congestion

• Sub-Counter #1 : Reserved

• Sub-Counter #2 : Delay build up

• Sub-Counter #3 : Frame loss

E-Type

• VS.EdchIubTnlCongestIndc.VS.EdchIubTnlCongestIndc.NoCongestion



• VS.EdchIubTnlCongestIndc.VS.EdchIubTnlCongestIndc.Reserved

• VS.EdchIubTnlCongestIndc.VS.EdchIubTnlCongestIndc.DelayBuildUp

• VS.EdchIubTnlCongestIndc.VS.EdchIubTnlCongestIndc.FrameLoss

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 441 VS.EdchMacTsnReassemblyErr - #1495

A-Description

Number of Error TSN detected

B-Collection

CUM

CUMulative

C-Condition (Event)

Each time the user-plane detects an error in the TSN Reassembly Function

D-Result

A set of subcounters screened on: TSN reassembly function error cause.

• Sub-Counter #0 : Duplicate TSN due to UE mis-detecting ACK as NAK

• Sub-Counter #1 : Unrecoverable TSN

E-Type

• VS.EdchMacTsnReassemblyErr.VS.EdchMacTsnReassemblyErr.DupTsn



• VS.EdchMacTsnReassemblyErr.VS.EdchMacTsnReassemblyErr.UnrecovTsn

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 442 VS.EdchFpRetransHarq - #1496

A-Description

Number of E-DCH HARQ retransmissions for each sub-frame.

B-Collection

CUM

CUMulative

C-Condition (Event)

Each time the user-plane receives E-DCH FP frame on the serving cell.

D-Result

A set of subcounters screened on: E-DCH FP Frame

• Sub-Counter #0 : Number of sub-frame with N of HARQ = 0 (No retrans).

• Sub-Counter #1 : Number of sub-frame with N of HARQ = 1 (1 retrans).

• Sub-Counter #2 : Number of sub-frame with N of HARQ > 1 (more than 1 retrans).

• Sub-Counter #3 : Number of HARQ Failure Indication

E-Type

• VS.EdchFpRetransHarq.VS.EdchFpRetransHarq.NsubfrmNharqEq0



• VS.EdchFpRetransHarq.VS.EdchFpRetransHarq.NsubfrmNharqEq1

• VS.EdchFpRetransHarq.VS.EdchFpRetransHarq.NsubfrmNharqGt1

• VS.EdchFpRetransHarq.VS.EdchFpRetransHarq.NharqFailInd

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 443 VS.BmcCtchTrafVol - #1497

A-Description

CTCH traffic volume. Count the number of CTCH blocks that are used.

B-Collection

CUM

CUMulative

C-Condition (Event)

CTCH usage during counter period

D-Result

one measurement

E-Type

VS.BmcCtchTrafVol

F-Object Instance

Cell(Reference)

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 444 VS.HsdschIubUlXoFrmCnt - #1502

A-Description

Number of UL Xoff control frames received from the Iub HsDsch link

B-Collection

CUM

CUMulative

C-Condition (Event)

When UL Xoff control frames received from the Iub HsDsch link

D-Result

A set of subcounters screened on: HSDPA type

• Sub-Counter #0 : HSDPA I/B

E-Type

• VS.HsdschIubUlXoFrmCnt.VS.HsdschIubUlXoFrmCnt.RabPsIBHsdpa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 445 VS.HsdschIubDlTrfcBlkTmCnt - #1503

A-Description

Number of milliseconds the Iub DSCH is blocked by Xoff mechanism

B-Collection

CUM

CUMulative

C-Condition (Event)

When Iub DSCH is blocked by Xoff mechanism

D-Result



E-Type

• VS.HsdschIubDlTrfcBlkTmCnt.VS.HsdschIubDlTrfcBlkTmCnt.RabPsIBHsdpa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V5.0

L-Aggregation Rule

Rtotal

Table 446 VS.DchIubDlTrfcBlkTmCnt - #1504

A-Description

Number of milliseconds the Iub DCH is blocked by Xoff mechanism

B-Collection

CUM

CUMulative

C-Condition (Event)

When Iub DSCH is blocked by Xoff mechanism

D-Result
















E-Type

• VS.DchIubDlTrfcBlkTmCnt.VS.DchIubDlTrfcBlkTmCnt.DlRabOther

• VS.DchIubDlTrfcBlkTmCnt.VS.DchIubDlTrfcBlkTmCnt.DlRabSRB

• VS.DchIubDlTrfcBlkTmCnt.VS.DchIubDlTrfcBlkTmCnt.DlRabCsSpeech

• VS.DchIubDlTrfcBlkTmCnt.VS.DchIubDlTrfcBlkTmCnt.DlRabCsData64

• VS.DchIubDlTrfcBlkTmCnt.VS.DchIubDlTrfcBlkTmCnt.DlRabCsStr14_4



• VS.DchIubDlTrfcBlkTmCnt.VS.DchIubDlTrfcBlkTmCnt.DlRabCsStr57_6

• VS.DchIubDlTrfcBlkTmCnt.VS.DchIubDlTrfcBlkTmCnt.DlRabHsdpa

• VS.DchIubDlTrfcBlkTmCnt.VS.DchIubDlTrfcBlkTmCnt.DlRabPsStr

• VS.DchIubDlTrfcBlkTmCnt.VS.DchIubDlTrfcBlkTmCnt.DlRabPsIb8






F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 447 VS.IuDlAmrFrmFqc - #1505

A-Description

Number of AMR frames received on Iu by FQC

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of AMR frames received on Iu UP

D-Result



A set of subcounters screened on: Reception of AMR WB frame on Iu UP

• Sub-Counter #0 : Frame good

• Sub-Counter #1 : Frame bad

• Sub-Counter #2 : Frame bad due to radio

E-Type

• VS.IuDlAmrFrmFqc.VS.IuDlAmrFrmFqc.FrmGood

• VS.IuDlAmrFrmFqc.VS.IuDlAmrFrmFqc.FrmBad

• VS.IuDlAmrFrmFqc.VS.IuDlAmrFrmFqc.FrmBadRadio

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 448 VS.DdUlAmrABtGoodFrm - #1506

A-Description

Number of AMR frames with Class A bits Transport Block received with CRCi = 0

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of AMR frame with Class A bits TB on uplink, where CRCi = 0

D-Result



A set of subcounters screened on: AMR link rate

• Sub-Counter #0 : 12.2








E-Type

• VS.DdUlAmrABtGoodFrm.VS.DdUlAmrABtGoodFrm.AmrRtChgLnkFrm12p2








F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 449 VS.DdUlAmrABtBadFrm - #1507

A-Description

Number of AMR frames with Class A bits Transport Block received with CRCi = 1

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of AMR frame with Class A bits TB on uplink, where CRCi = 1

D-Result










E-Type

• VS.DdUlAmrABtBadFrm.VS.DdUlAmrABtBadFrm.AmrRtChgLnkFrm12p2








F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 450 VS.HsdpaIubDlControlFrames - #1508

A-Description

Counts the total number of downlink control frames sent to NodeB. The trigger is a controlframe to NodeB (i.e., Capacity Request Frame).

B-Collection

CUM

CUMulative

C-Condition (Event)

Capacity Request to NodeB

D-Result



E-Type

• VS.HsdpaIubDlControlFrames.VS.HsdpaIubDlControlFrames.RabPsIBHsdpa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 451 VS.HsdpaIubNonZeroCapacityAlloc - #1509

A-Description

Counts the total number of capacity allocation frames sent by NodeB with non-zero grant.

B-Collection

CUM

CUMulative

C-Condition (Event)

Non-Zero Grant Capacity Allocation by NodeB

D-Result



E-Type

• VS.HsdpaIubNonZeroCapacityAlloc.VS.HsdpaIubNonZeroCapacityAlloc.RabPsIBHsdpa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule



Rtotal

Table 452 VS.HsdpaIubZeroCapacityAlloc - #1510

A-Description

Counts the total number of capacity allocation frames sent by NodeB with zero grant.

B-Collection

CUM

CUMulative

C-Condition (Event)

Zero Grant Capacity Allocation by NodeB

D-Result



E-Type

• VS.HsdpaIubZeroCapacityAlloc.VS.HsdpaIubZeroCapacityAlloc.RabPsIBHsdpa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 453 VS.HsdpaIubCreditsRequested - #1511

A-Description

Counts the total credits requested by the I-Node from NodeB in Kilo Bytes



B-Collection

CUM

CUMulative

C-Condition (Event)

Credit Request for new data (i.e., not repeated request for same data)

D-Result



E-Type

• VS.HsdpaIubCreditsRequested.VS.HsdpaIubCreditsRequested.RabPsIBHsdpa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 454 VS.HsdpaIubCreditsConsumed - #1512

A-Description

Counts the total credits grants by NodeB in Kilo Bytes that are actually consumed by the I-Node.

B-Collection

CUM

CUMulative

C-Condition (Event)



Credit Consumed by I-Node

D-Result



E-Type

• VS.HsdpaIubCreditsConsumed.VS.HsdpaIubCreditsConsumed.RabPsIBHsdpa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 455 VS.AmrClDlRt - #1513

A-Description

Number of AMR calls by DL rate

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of DL AMR frame

D-Result












• Sub-Counter #8 : AMR SID

E-Type

• VS.AmrClDlRt.VS.AmrClDlRt.AmrRtChgLnk12p2








• VS.AmrClDlRt.VS.AmrClDlRt.AmrRtChgLnkSid

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 456 VS.AmrClUlRt - #1514

A-Description

Number of AMR calls by UL rate

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of UL AMR frame

D-Result










• Sub-Counter #8 : AMR SID

E-Type

• VS.AmrClUlRt.VS.AmrClUlRt.AmrRtChgLnk12p2








• VS.AmrClUlRt.VS.AmrClUlRt.AmrRtChgLnkSid

F-Object Instance

Cell(Reference)

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 457 VS.DlAmrRtChg - #1515

A-Description

Number of DL rate change in AMR calls

B-Collection

CUM

CUMulative

C-Condition (Event)

Change of DL rate in AMR

D-Result

one measurement

E-Type

VS.DlAmrRtChg

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 458 VS.IuRcvdAmrRtCtrl - #1516

A-Description

Number of received Iu rate control in AMR calls

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of Iu rate control during AMR calls

D-Result

one measurement

E-Type

VS.IuRcvdAmrRtCtrl

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 459 VS.OvinCnAccLaDscrd - #1521

A-Description

Number of uplink or downlink messages discarded at CN Access La on PMC-RAB

B-Collection

CUM

CUMulative

C-Condition (Event)

Monitored resources in PMC are in overload

D-Result

A set of subcounters screened on: Queue Type

• Sub-Counter #0 : Downlink non-paging messages discarded at TCPLink

• Sub-Counter #1 : Downlink paging messages discarded at TCPLink

• Sub-Counter #2 : Number of uplink trashable messages discarded

E-Type

• VS.OvinCnAccLaDscrd.VS.OvinCnAccLaDscrd.DlNpgMsgDscrdTcplnk

• VS.OvinCnAccLaDscrd.VS.OvinCnAccLaDscrd.DlPgMsgDscrdTcplnk

• VS.OvinCnAccLaDscrd.VS.OvinCnAccLaDscrd.NumUlTrshMsgDscrd

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 460 VS.OvinNiDscrd - #1522

A-Description

Number of Core Network messages received and in NI

B-Collection

CUM

CUMulative

C-Condition (Event)

NI is in overload

D-Result

A set of subcounters screened on: Paging Type

• Sub-Counter #0 : Total trashable paging messages

• Sub-Counter #1 : Total trashable non-paging messages

• Sub-Counter #2 : Trashable paging messages discarded

• Sub-Counter #3 : Trashable non-paging messages discarded

E-Type

• VS.OvinNiDscrd.VS.OvinNiDscrd.TtlTrshPgMsgs

• VS.OvinNiDscrd.VS.OvinNiDscrd.TtlTrshNnPgMsgs

• VS.OvinNiDscrd.VS.OvinNiDscrd.TrshPgMsgsDscrd

• VS.OvinNiDscrd.VS.OvinNiDscrd.TrshNnPgMsgsDscrd

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule



Rtotal

Table 461 VS.OvinRabRrcConReqDscrd - #1523

A-Description

Total RRC connection messages dropped due to panic overload

B-Collection

CUM

CUMulative

C-Condition (Event)

Critical overload on RAB

D-Result

one measurement

E-Type

VS.OvinRabRrcConReqDscrd

F-Object Instance

RNC

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 462 VS.DedicatedUplinkSduRlcRefCell - #1524

A-Description

Number of SDUs received on dedicated uplink RLCs (from RLC counter DCH_UL_SDU)

B-Collection



CUM

CUMulative

C-Condition (Event)

RLC for a dedicated channel receiving a SDU, on uplink

D-Result















E-Type

• VS.DedicatedUplinkSduRlcRefCell.VS.DedicatedUplinkSduRlcRefCell.UlRabOther

• VS.DedicatedUplinkSduRlcRefCell.VS.DedicatedUplinkSduRlcRefCell.UlRabSRB

• VS.DedicatedUplinkSduRlcRefCell.VS.DedicatedUplinkSduRlcRefCell.UlRabCsSpeech

• VS.DedicatedUplinkSduRlcRefCell.VS.DedicatedUplinkSduRlcRefCell.UlRabCsData64

• VS.DedicatedUplinkSduRlcRefCell.VS.DedicatedUplinkSduRlcRefCell.UlRabCsStr14_4

• VS.DedicatedUplinkSduRlcRefCell.VS.DedicatedUplinkSduRlcRefCell.UlRabCsStr57_6

• VS.DedicatedUplinkSduRlcRefCell.VS.DedicatedUplinkSduRlcRefCell.UlRabPsStr

• VS.DedicatedUplinkSduRlcRefCell.VS.DedicatedUplinkSduRlcRefCell.UlRabPsIb8





• VS.DedicatedUplinkSduRlcRefCell.VS.DedicatedUplinkSduRlcRefCell.UlRabHsupa

F-Object Instance



Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 463 VS.DedicatedDownlinkSduRlcRefCell - #1525

A-Description

Number of SDUs sent on dedicated downlink RLCs (from RLC counter DCH_DL_SDU)

B-Collection

CUM

CUMulative

C-Condition (Event)

RLC for a dedicated channel sending a SDU, on downlink

D-Result


















E-Type

• VS.DedicatedDownlinkSduRlcRefCell.VS.DedicatedDownlinkSduRlcRefCell.DlRabOther

• VS.DedicatedDownlinkSduRlcRefCell.VS.DedicatedDownlinkSduRlcRefCell.DlRabSRB

• VS.DedicatedDownlinkSduRlcRefCell.VS.DedicatedDownlinkSduRlcRefCell.DlRabCsSpeech

• VS.DedicatedDownlinkSduRlcRefCell.VS.DedicatedDownlinkSduRlcRefCell.DlRabCsData64

• VS.DedicatedDownlinkSduRlcRefCell.VS.DedicatedDownlinkSduRlcRefCell.DlRabCsStr14_4

• VS.DedicatedDownlinkSduRlcRefCell.VS.DedicatedDownlinkSduRlcRefCell.DlRabCsStr57_6

• VS.DedicatedDownlinkSduRlcRefCell.VS.DedicatedDownlinkSduRlcRefCell.DlRabHsdpa

• VS.DedicatedDownlinkSduRlcRefCell.VS.DedicatedDownlinkSduRlcRefCell.DlRabPsStr

• VS.DedicatedDownlinkSduRlcRefCell.VS.DedicatedDownlinkSduRlcRefCell.DlRabPsIb8






F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V5.0

L-Aggregation Rule

Rtotal

Table 464 VS.DedicatedDownlinkActivityRlcRefCell - #1526

A-Description

Time that RAB is actively transmitting data in the downlink

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of an RLC SDU on downlink for a TRB RLC

D-Result
















E-Type

• VS.DedicatedDownlinkActivityRlcRefCell.VS.DedicatedDownlinkActivityRlcRefCell.DlRabOther

• VS.DedicatedDownlinkActivityRlcRefCell.VS.DedicatedDownlinkActivityRlcRefCell.DlRabSRB

• VS.DedicatedDownlinkActivityRlcRefCell.VS.DedicatedDownlinkActivityRlcRefCell.DlRabCsSpeech



• VS.DedicatedDownlinkActivityRlcRefCell.VS.DedicatedDownlinkActivityRlcRefCell.DlRabCsData64

• VS.DedicatedDownlinkActivityRlcRefCell.VS.DedicatedDownlinkActivityRlcRefCell.DlRabCsStr14_4

• VS.DedicatedDownlinkActivityRlcRefCell.VS.DedicatedDownlinkActivityRlcRefCell.DlRabCsStr57_6

• VS.DedicatedDownlinkActivityRlcRefCell.VS.DedicatedDownlinkActivityRlcRefCell.DlRabHsdpa

• VS.DedicatedDownlinkActivityRlcRefCell.VS.DedicatedDownlinkActivityRlcRefCell.DlRabPsStr

• VS.DedicatedDownlinkActivityRlcRefCell.VS.DedicatedDownlinkActivityRlcRefCell.DlRabPsIb8






F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 465 VS.DedicatedUplinkActivityRlcRefCell - #1527

A-Description

Time that RAB is actively transmitting data in the uplink

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of an RLC SDU on uplink for a TRB RLC

D-Result















E-Type

• VS.DedicatedUplinkActivityRlcRefCell.VS.DedicatedUplinkActivityRlcRefCell.UlRabOther

• VS.DedicatedUplinkActivityRlcRefCell.VS.DedicatedUplinkActivityRlcRefCell.UlRabSRB

• VS.DedicatedUplinkActivityRlcRefCell.VS.DedicatedUplinkActivityRlcRefCell.UlRabCsSpeech

• VS.DedicatedUplinkActivityRlcRefCell.VS.DedicatedUplinkActivityRlcRefCell.UlRabCsData64

• VS.DedicatedUplinkActivityRlcRefCell.VS.DedicatedUplinkActivityRlcRefCell.UlRabCsStr14_4

• VS.DedicatedUplinkActivityRlcRefCell.VS.DedicatedUplinkActivityRlcRefCell.UlRabCsStr57_6

• VS.DedicatedUplinkActivityRlcRefCell.VS.DedicatedUplinkActivityRlcRefCell.UlRabPsStr



• VS.DedicatedUplinkActivityRlcRefCell.VS.DedicatedUplinkActivityRlcRefCell.UlRabPsIb8





• VS.DedicatedUplinkActivityRlcRefCell.VS.DedicatedUplinkActivityRlcRefCell.UlRabHsupa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 466 VS.IrmcacDistIubLoad - #1528

A-Description

Number of seconds per range of IuB load (or VVC tbc) considered by the AAL2 CAC algorithm

B-Collection

CUM

CUMulative

C-Condition (Event)

IuB bandwith measurements by the AAL2 CAC Algorithm

D-Result

A set of subcounters screened on: Power range



• Sub-Counter #0 : 0-20% of total Bandwidth





E-Type

• VS.IrmcacDistIubLoad.VS.IrmcacDistIubLoad.BandWidth0to20





F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 467 VS.DedicatedUplinkBadPdusRlcReferenceCell - #1529

A-Description

Number of PS Transport Block(TB )/PDU received with CRCi = 1

B-Collection

CUM

CUMulative

C-Condition (Event)



PS Transport Block(TB )/PDU received with CRCi = 1

D-Result















E-Type

• VS.DedicatedUplinkBadPdusRlcReferenceCell.VS.DedicatedUplinkBadPdusRlcReferenceCell.UlRabOther

• VS.DedicatedUplinkBadPdusRlcReferenceCell.VS.DedicatedUplinkBadPdusRlcReferenceCell.UlRabSRB

• VS.DedicatedUplinkBadPdusRlcReferenceCell.VS.DedicatedUplinkBadPdusRlcReferenceCell.UlRabCsSpeech

• VS.DedicatedUplinkBadPdusRlcReferenceCell.VS.DedicatedUplinkBadPdusRlcReferenceCell.UlRabCsData64

• VS.DedicatedUplinkBadPdusRlcReferenceCell.VS.DedicatedUplinkBadPdusRlcReferenceCell.UlRabCsStr14_4

• VS.DedicatedUplinkBadPdusRlcReferenceCell.VS.DedicatedUplinkBadPdusRlcReferenceCell.UlRabCsStr57_6

• VS.DedicatedUplinkBadPdusRlcReferenceCell.VS.DedicatedUplinkBadPdusRlcReferenceCell.UlRabPsStr

• VS.DedicatedUplinkBadPdusRlcReferenceCell.VS.DedicatedUplinkBadPdusRlcReferenceCell.UlRabPsIb8







• VS.DedicatedUplinkBadPdusRlcReferenceCell.VS.DedicatedUplinkBadPdusRlcReferenceCell.UlRabHsupa

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.16 Statistic Counter


Counter name

#2001 VS.RRCAtt

#2002 VS.CallAttNorMoCs

#2003 VS.CallAttNorMoPs

#2004 VS.CallAttNorMtCs

#2005 VS.CallAttNorMtPs

#2006 VS.CallAttMulMoCs

#2007 VS.CallAttMulMoPs

#2008 VS.CallAttMulMtCs

#2009 VS.CallAttMulMtPs

#2010 VS.RabAttNorMoCs

#2011 VS.RabAttNorMoPs

#2012 VS.RabAttNorMtCs

#2013 VS.RabAttNorMtPs

#2014 VS.RabAttMulMoCs

#2015 VS.RabAttMulMoPs

#2016 VS.RabAttMulMtCs

#2017 VS.RabAttMulMtPs

#2018 VS.RabRspNorMoCs

#2019 VS.RabRspNorMoPs

#2020 VS.RabRspNorMtCs

#2021 VS.RabRspNorMtPs

#2022 VS.RabRspMulMoCs

#2023 VS.RabRspMulMoPs

#2024 VS.RabRspMulMtCs

#2025 VS.RabRspMulMtPs

#2026 VS.CallAnswNorMoCs

#2027 VS.CallAnswNorMoPs

#2028 VS.CallAnswNorMtCs

#2029 VS.CallAnswNorMtPs

#2030 VS.CallAnswMulMoCs

#2031 VS.CallAnswMulMoPs




Counter name

#2032 VS.CallAnswMulMtCs

#2033 VS.CallAnswMulMtPs

#2034 VS.FailState1NorMo

#2035 VS.FailNotState1NorMoCs

#2036 VS.FailNotState1NorMoPs

#2037 VS.FailState1NorMt

#2038 VS.FailNotState1NorMtCs

#2039 VS.FailNotState1NorMtPs

#2040 VS.FailNotState1MulMoCs

#2041 VS.FailNotState1MulMoPs

#2042 VS.FailNotState1MulMtCs

#2043 VS.FailNotState1MulMtPs

#2044 VS.LocRegRRCAtt

#2045 VS.LocRegCallAtt

#2046 VS.LocRegCallAnsw

#2047 VS.LocRegFail

#2049 VS.PagingRsp

#2050 VS.CsMoState2Failure

#2051 VS.PsMoState2Failure





#2056 VS.CsMtState2Failure

#2057 VS.PsMtState2Failure





#2062 VS.LocalRegState1Failure

#2063 VS.CsLocalRegState2Failure

#2064 VS.PsLocalRegState2Failure

#2065 VS.CsMoCallAvgHoldingTime

#2066 VS.PsMoCallAvgHoldingTime

#2067 VS.CsMtCallAvgHoldingTime

#2068 VS.PsMtCallAvgHoldingTime




Counter name

#2069 VS.CsMoRabCallAvgSetupTime

#2070 VS.PsMoRabCallAvgSetupTime

#2071 VS.CsMtRabCallAvgSetupTime

#2072 VS.PsMtRabCallAvgSetupTime

Table 468 VS.RRCAtt - #2001

A-Description

Number of RRC CONNECTION REQUEST with the establish causes

B-Collection

CUM

CUMulative

C-Condition (Event)

reception RRC CONNECTION REQUEST messages

D-Result

A set of subcounters screened on: Originating Cause for RRC establishment

• Sub-Counter #0 : Originating Conversational Call

• Sub-Counter #1 : Originating StreamingCall



• Sub-Counter #4 : Originating Subscribed Traffic Call(*)

• Sub-Counter #5 : Terminating Conversational Call

• Sub-Counter #6 : Terminating StreamingCall




• Sub-Counter #10 : Inter RAT Cell Reselection(*)

• Sub-Counter #11 : Inter RAT Cell Change Order(*)

• Sub-Counter #12 : Local registration(*)

• Sub-Counter #13 : Local registration detach(*)



• Sub-Counter #16 : Call Reestablishment(*)





• Sub-Counter #19 : Terminating, cause unknown(*)

• Sub-Counter #20 : Originating Preservation call

• Sub-Counter #21 : Terminating Preservation call

E-Type

• VS.RRCAtt.VS.RRCAtt.MoConvCall

• VS.RRCAtt.VS.RRCAtt.MoStrmCall

• VS.RRCAtt.VS.RRCAtt.MoIntactCall

• VS.RRCAtt.VS.RRCAtt.MoBgrdCall

• VS.RRCAtt.VS.RRCAtt.MoSubsTrafCall

• VS.RRCAtt.VS.RRCAtt.MtConvCall

• VS.RRCAtt.VS.RRCAtt.MtStrmCall

• VS.RRCAtt.VS.RRCAtt.MtIntactCall

• VS.RRCAtt.VS.RRCAtt.MtBgrdCall

• VS.RRCAtt.VS.RRCAtt.EmrCall

• VS.RRCAtt.VS.RRCAtt.InterRATCellResel

• VS.RRCAtt.VS.RRCAtt.InterRATCellChgOrd

• VS.RRCAtt.VS.RRCAtt.Reg

• VS.RRCAtt.VS.RRCAtt.Detach

• VS.RRCAtt.VS.RRCAtt.MoHighPSig

• VS.RRCAtt.VS.RRCAtt.MoLowPSig

• VS.RRCAtt.VS.RRCAtt.CallReEstab

• VS.RRCAtt.VS.RRCAtt.MtHighPSig

• VS.RRCAtt.VS.RRCAtt.MtLowPSig

• VS.RRCAtt.VS.RRCAtt.MtCauseUnk

• VS.RRCAtt.VS.RRCAtt.MoPresv

• VS.RRCAtt.VS.RRCAtt.MtPresv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 469 VS.CallAttNorMoCs - #2002

A-Description

Number of INITIAL DIRECT TRANSFER messages received related to the Normal Mobile Ori-ginating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of INITIAL DIRECT TRANSFER message

D-Result

A set of subcounters screened on: CS attempt call

• Sub-Counter #0 : Originating Conversational Call


• Sub-Counter #2 : Originating Low Priority

• Sub-Counter #3 : Originating High Priority

E-Type

• VS.CallAttNorMoCs.VS.CallAttNorMoCs.Conv

• VS.CallAttNorMoCs.VS.CallAttNorMoCs.Emr

• VS.CallAttNorMoCs.VS.CallAttNorMoCs.SMS

• VS.CallAttNorMoCs.VS.CallAttNorMoCs.Suppl

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 470 VS.CallAttNorMoPs - #2003

A-Description

Number of INITIAL DIRECT TRANSFER messages received related to the Normal Mobile Ori-ginating calls in PS core network domain

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: PS attempt call

• Sub-Counter #0 : Originating Conversational Call(*)




• Sub-Counter #4 : Emergency Call(*)

• Sub-Counter #5 : Originating Subscribed traffic Call(*)

• Sub-Counter #6 : Originating Low Priority

• Sub-Counter #7 : Originating Interactive or Background Call

E-Type

• VS.CallAttNorMoPs.VS.CallAttNorMoPs.Conv

• VS.CallAttNorMoPs.VS.CallAttNorMoPs.Strm

• VS.CallAttNorMoPs.VS.CallAttNorMoPs.Intact



• VS.CallAttNorMoPs.VS.CallAttNorMoPs.Bgrd

• VS.CallAttNorMoPs.VS.CallAttNorMoPs.Emr

• VS.CallAttNorMoPs.VS.CallAttNorMoPs.Subs

• VS.CallAttNorMoPs.VS.CallAttNorMoPs.SMS

• VS.CallAttNorMoPs.VS.CallAttNorMoPs.Presv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 471 VS.CallAttNorMtCs - #2004

A-Description

Number of INITIAL DIRECT TRANSFER messages received related to the normal Mobile Ter-minating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result


• Sub-Counter #0 : Terminating Conversational Call





E-Type

• VS.CallAttNorMtCs.VS.CallAttNorMtCs.Conv

• VS.CallAttNorMtCs.VS.CallAttNorMtCs.SMS

• VS.CallAttNorMtCs.VS.CallAttNorMtCs.Suppl

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 472 VS.CallAttNorMtPs - #2005

A-Description

Number of INITIAL DIRECT TRANSFER messages received related to the normal Mobile Ter-minating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result


• Sub-Counter #0 : Terminating Conversational Call(*)






• Sub-Counter #4 : Terminating Low Priority Signalling (SMS)

• Sub-Counter #5 : Terminating Preservation call

E-Type

• VS.CallAttNorMtPs.VS.CallAttNorMtPs.Conv

• VS.CallAttNorMtPs.VS.CallAttNorMtPs.Strm

• VS.CallAttNorMtPs.VS.CallAttNorMtPs.Intact

• VS.CallAttNorMtPs.VS.CallAttNorMtPs.Bgrd

• VS.CallAttNorMtPs.VS.CallAttNorMtPs.SMS

• VS.CallAttNorMtPs.VS.CallAttNorMtPs.Presv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 473 VS.CallAttMulMoCs - #2006

A-Description

Number of INITIAL DIRECT TRANSFER messages received related to the Multi-RAB MobileOriginating calls in CS core network domain.

B-Collection

CUM

CUMulative



C-Condition (Event)


D-Result


• Sub-Counter #0 : Call Attempt

E-Type

• VS.CallAttMulMoCs.VS.CallAttMulMoCs.Att

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 474 VS.CallAttMulMoPs - #2007

A-Description

Number of INITIAL DIRECT TRANSFER messages received related to the Multi-RAB MobileOriginating calls in PS core network domain.(*)

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of INITIAL DIRECT TRANSFER message(*)

D-Result





• Sub-Counter #1 : Preservation Call Attempt

E-Type

• VS.CallAttMulMoPs.VS.CallAttMulMoPs.Att

• VS.CallAttMulMoPs.VS.CallAttMulMoPs.Presv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 475 VS.CallAttMulMtCs - #2008

A-Description

Number of INITIAL DIRECT TRANSFER messages received related to the Multi-RAB MobileTerminating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception INITIAL DIRECT TRANSFER message

D-Result





E-Type

• VS.CallAttMulMtCs.VS.CallAttMulMtCs.Att

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 476 VS.CallAttMulMtPs - #2009

A-Description

Number of INITIAL DIRECT TRANSFER messages received related to the Multi-RAB MobileTerminating calls in PS core network domain.(*)

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of INITIAL DIRECT TRANSFER message(*)

D-Result



• Sub-Counter #1 : Preservation Call Attempt

E-Type

• VS.CallAttMulMtPs.VS.CallAttMulMtPs.Att

• VS.CallAttMulMtPs.VS.CallAttMulMtPs.Presv



F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 477 VS.RabAttNorMoCs - #2010

A-Description

Number of RAB ASSIGNMENT REQUEST messages received related to the normal MobileOriginating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception RAB ASSIGNMENT REQUEST message

D-Result

A set of subcounters screened on: CS Rab

• Sub-Counter #0 : CS Conversational Voice Call Rab

• Sub-Counter #1 : CS Conversational Circuit+Etc Call Rab

• Sub-Counter #2 : CS Emergency Call

E-Type

• VS.RabAttNorMoCs.VS.RabAttNorMoCs.ConvVce

• VS.RabAttNorMoCs.VS.RabAttNorMoCs.ConvCirEtc

• VS.RabAttNorMoCs.VS.RabAttNorMoCs.Emr



F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 478 VS.RabAttNorMoPs - #2011

A-Description

Number of RAB ASSIGNMENT REQUEST messages received related to the normal MobileOriginating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: PS Rab

• Sub-Counter #0 : Conversational Call Rab(*)

• Sub-Counter #1 : HSDPA Conversational Call Rab(*)

• Sub-Counter #2 : Stream Call Rab

• Sub-Counter #3 : HSDPA Stream Call Rab(*)

• Sub-Counter #4 : Interactive Call Rab

• Sub-Counter #5 : HSDPA Interactive CAll Rab

• Sub-Counter #6 : Background Call Rab



• Sub-Counter #7 : HSDPA Background Call Rab


• Sub-Counter #9 : HSDPA Emergency Call(*)

• Sub-Counter #10 : Subscribed Traffic Call(*)

• Sub-Counter #11 : HSDPA Subscribed Traffic Call(*)

• Sub-Counter #12 : Preservation Call

• Sub-Counter #13 : HSDPA Preservation Call

E-Type

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.Conv

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.HSDPAConv

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.Strm

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.HSDPAStrm

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.Intact

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.HSDPAIntact

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.Bgrd

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.HSDPABgrd

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.Emr

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.HSDPAEmr

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.Subs

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.HSDPASubs

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.Presv

• VS.RabAttNorMoPs.VS.RabAttNorMoPs.HSDPAPresv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V5.0

L-Aggregation Rule

Rtotal

Table 479 VS.RabAttNorMtCs - #2012

A-Description

Number of RAB ASSIGNMENT REQUEST messages received related to the normal MobileTerminating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: CS Conversation Rab

• Sub-Counter #0 : Conversational Voice call Rab

• Sub-Counter #1 : Conversational Circuit Etc Rab

E-Type

• VS.RabAttNorMtCs.VS.RabAttNorMtCs.ConvVce

• VS.RabAttNorMtCs.VS.RabAttNorMtCs.ConvCirEtc

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule



Rtotal

Table 480 VS.RabAttNorMtPs - #2013

A-Description

Number of RAB ASSIGNMENT REQUEST messages received related to the normal MobileTerminating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: PS Conversational Call Rab





• Sub-Counter #4 : Interactive CAll Rab






E-Type

• VS.RabAttNorMtPs.VS.RabAttNorMtPs.Conv

• VS.RabAttNorMtPs.VS.RabAttNorMtPs.HSDPAConv

• VS.RabAttNorMtPs.VS.RabAttNorMtPs.Strm

• VS.RabAttNorMtPs.VS.RabAttNorMtPs.HSDPAStrm

• VS.RabAttNorMtPs.VS.RabAttNorMtPs.Intact

• VS.RabAttNorMtPs.VS.RabAttNorMtPs.HSDPAIntact

• VS.RabAttNorMtPs.VS.RabAttNorMtPs.Bgrd

• VS.RabAttNorMtPs.VS.RabAttNorMtPs.HSDPABgrd

• VS.RabAttNorMtPs.VS.RabAttNorMtPs.Presv

• VS.RabAttNorMtPs.VS.RabAttNorMtPs.HSDPAPresv



F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 481 VS.RabAttMulMoCs - #2014

A-Description

Number of RAB ASSIGNMENT REQUEST messages received related to the Multi-RAB MobileOriginating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: CS Rab Attempt

• Sub-Counter #0 : Rab Attempt

E-Type

• VS.RabAttMulMoCs.VS.RabAttMulMoCs.Att

F-Object Instance

Cell

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 482 VS.RabAttMulMoPs - #2015

A-Description

Number of RAB ASSIGNMENT REQUEST messages received related to the Multi-RAB MobileOriginating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: PS Rab Attempt Originating/Terminating


• Sub-Counter #1 : HSDPA Rab Attempt

• Sub-Counter #2 : Preservation Call Rab Attempt

• Sub-Counter #3 : HSDPA Preservation Call Rab Attempt

E-Type

• VS.RabAttMulMoPs.VS.RabAttMulMoPs.Att

• VS.RabAttMulMoPs.VS.RabAttMulMoPs.HSDPAAtt

• VS.RabAttMulMoPs.VS.RabAttMulMoPs.Presv

• VS.RabAttMulMoPs.VS.RabAttMulMoPs.HSDPAPresv

F-Object Instance



Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 483 VS.RabAttMulMtCs - #2016

A-Description

Number of RAB ASSIGNMENT REQUEST messages received related to the Multi-RAB MobileTerminating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: CS Rab Attempt


E-Type

• VS.RabAttMulMtCs.VS.RabAttMulMtCs.Att

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 484 VS.RabAttMulMtPs - #2017

A-Description

Number of RAB ASSIGNMENT REQUEST messages received related to the Multi-RAB MobileTerminating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: PS Rab Attempt Originating/Terminating


• Sub-Counter #1 : HSDPA Rab Attempt

• Sub-Counter #2 : Preservation Call Rab Attempt

• Sub-Counter #3 : HSDPA Preservation Call Rab Attempt

E-Type

• VS.RabAttMulMtPs.VS.RabAttMulMtPs.Att

• VS.RabAttMulMtPs.VS.RabAttMulMtPs.HSDPAAtt

• VS.RabAttMulMtPs.VS.RabAttMulMtPs.Presv

• VS.RabAttMulMtPs.VS.RabAttMulMtPs.HSDPAPresv

F-Object Instance

Cell

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 485 VS.RabRspNorMoCs - #2018

A-Description

Number of RAB ASSIGNMENT RESPONSE messages sent related to the normal Mobile Ori-ginating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending of RAB ASSIGNMENT RESPONSE message

D-Result

A set of subcounters screened on: CS Rab

• Sub-Counter #0 : CS Conversational Voice Call Rab

• Sub-Counter #1 : CS Conversational Circuit+Etc Call Rab

• Sub-Counter #2 : CS Emergency Call

E-Type

• VS.RabRspNorMoCs.VS.RabRspNorMoCs.ConvVce

• VS.RabRspNorMoCs.VS.RabRspNorMoCs.ConvCirEtc

• VS.RabRspNorMoCs.VS.RabRspNorMoCs.Emr

F-Object Instance

Cell

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 486 VS.RabRspNorMoPs - #2019

A-Description

Number of RAB ASSIGNMENT RESPONSE messages sent related to the normal Mobile Ori-ginating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: PS Rab





• Sub-Counter #4 : Interactive Call Rab





• Sub-Counter #9 : HSDPA Emergency Call(*)



• Sub-Counter #10 : Subscribed Traffic Call(*)

• Sub-Counter #11 : HSDPA Subscribed Traffic Call(*)



E-Type

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.Conv

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.HSDPAConv

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.Strm

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.HSDPAStrm

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.Intact

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.HSDPAIntact

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.Bgrd

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.HSDPABgrd

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.Emr

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.HSDPAEmr

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.Subs

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.HSDPASubs

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.Presv

• VS.RabRspNorMoPs.VS.RabRspNorMoPs.HSDPAPresv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 487 VS.RabRspNorMtCs - #2020

A-Description

Number of RAB ASSIGNMENT RESPONSE messages sent related to the normal Mobile Ter-minating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: CS Conversation Rab

• Sub-Counter #0 : Conversational Voice call Rab

• Sub-Counter #1 : Conversational Circuit Etc Rab

E-Type

• VS.RabRspNorMtCs.VS.RabRspNorMtCs.ConvVce

• VS.RabRspNorMtCs.VS.RabRspNorMtCs.ConvCirEtc

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 488 VS.RabRspNorMtPs - #2021



A-Description

Number of RAB ASSIGNMENT RESPONSE messages sent related to the normal Mobile Ter-minating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: PS Conversational Call Rab





• Sub-Counter #4 : Interactive CAll Rab






E-Type

• VS.RabRspNorMtPs.VS.RabRspNorMtPs.Conv

• VS.RabRspNorMtPs.VS.RabRspNorMtPs.HSDPAConv

• VS.RabRspNorMtPs.VS.RabRspNorMtPs.Strm

• VS.RabRspNorMtPs.VS.RabRspNorMtPs.HSDPAStrm

• VS.RabRspNorMtPs.VS.RabRspNorMtPs.Intact

• VS.RabRspNorMtPs.VS.RabRspNorMtPs.HSDPAIntact

• VS.RabRspNorMtPs.VS.RabRspNorMtPs.Bgrd

• VS.RabRspNorMtPs.VS.RabRspNorMtPs.HSDPABgrd

• VS.RabRspNorMtPs.VS.RabRspNorMtPs.Presv

• VS.RabRspNorMtPs.VS.RabRspNorMtPs.HSDPAPresv

F-Object Instance

Cell

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 489 VS.RabRspMulMoCs - #2022

A-Description

Number of RAB ASSIGNMENT RESPONSE messages sent related to the Multi-RAB MobileOriginating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: CS Rab Response

• Sub-Counter #0 : Rab Response

E-Type

• VS.RabRspMulMoCs.VS.RabRspMulMoCs.Resp

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 490 VS.RabRspMulMoPs - #2023

A-Description

Number of RAB ASSIGNMENT RESPONSE messages sent related to the Multi-RAB MobileOriginating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: PS Rab Response


• Sub-Counter #1 : HSDPA Rab Response(*)

• Sub-Counter #2 : Preservation call Rab response

• Sub-Counter #3 : HSDPA Preservationcall Rab response(*)

E-Type

• VS.RabRspMulMoPs.VS.RabRspMulMoPs.Resp

• VS.RabRspMulMoPs.VS.RabRspMulMoPs.HSDPAResp

• VS.RabRspMulMoPs.VS.RabRspMulMoPs.Presv

• VS.RabRspMulMoPs.VS.RabRspMulMoPs.HSDPAPresv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 491 VS.RabRspMulMtCs - #2024

A-Description

Number of RAB ASSIGNMENT RESPONSE messages sent related to the Multi-RAB MobileTerminating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: CS Rab Response


E-Type

• VS.RabRspMulMtCs.VS.RabRspMulMtCs.Resp

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 492 VS.RabRspMulMtPs - #2025

A-Description

Number of RAB ASSIGNMENT RESPONSE messages sent related to the Multi-RAB MobileTerminating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: PS Rab Response


• Sub-Counter #1 : HSDPA Rab Response(*)

• Sub-Counter #2 : Preservation call Rab response

• Sub-Counter #3 : HSDPA Preservationcall Rab response(*)

E-Type

• VS.RabRspMulMtPs.VS.RabRspMulMtPs.Resp

• VS.RabRspMulMtPs.VS.RabRspMulMtPs.HSDPAResp

• VS.RabRspMulMtPs.VS.RabRspMulMtPs.Presv

• VS.RabRspMulMtPs.VS.RabRspMulMtPs.HSDPAPresv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 493 VS.CallAnswNorMoCs - #2026

A-Description

Number of UL_DT (CONNECT ACK), DL_DT (CP ACK) messages received related to the nor-mal Mobile Originating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of UL_DT(CONNECT ACK) or DL_DT(CP ACK) or sending of Location Report(Suppl)

D-Result

A set of subcounters screened on: CS Call Rab Answer

• Sub-Counter #0 : Conversational Voice call Answer

• Sub-Counter #1 : Conversational Circuit Etc call Answer

• Sub-Counter #2 : Emergency Call Answer


• Sub-Counter #4 : Terminating High Priority Signalling Supplementary

E-Type

• VS.CallAnswNorMoCs.VS.CallAnswNorMoCs.ConvVce

• VS.CallAnswNorMoCs.VS.CallAnswNorMoCs.ConvCirEtc

• VS.CallAnswNorMoCs.VS.CallAnswNorMoCs.Emr

• VS.CallAnswNorMoCs.VS.CallAnswNorMoCs.SMS

• VS.CallAnswNorMoCs.VS.CallAnswNorMoCs.Suppl

F-Object Instance

Cell

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 494 VS.CallAnswNorMoPs - #2027

A-Description

Number of DL_DT (ACTIVATE PDP CONTEXT ACCEPT or CP ACK) messages received re-lated to the normal Mobile Originating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of DL_DT (ACTIVATE PDP CONTEXT ACCEPT or CP ACK) message or sendingof RAB Assignment Response (Preservation call)

D-Result

A set of subcounters screened on: PS Call Rab Answer

• Sub-Counter #0 : Originating Conversational Call Answer(*)

• Sub-Counter #1 : HSDPA Originating Conversational Call Answer(*)

• Sub-Counter #2 : Originating Streaming Call Answer

• Sub-Counter #3 : HSDPA Originating Streaming Call Answer(*)

• Sub-Counter #4 : Originating Interactive Call Answer

• Sub-Counter #5 : HSDPA Originating Interactive Call Answer

• Sub-Counter #6 : Originating Background Call Answer

• Sub-Counter #7 : HSDPA Originating Background Call Answer

• Sub-Counter #8 : Emergency Call Answer(*)



• Sub-Counter #9 : HSDPA Emergency Call Answer(*)

• Sub-Counter #10 : Originated Subscribed Traffic Call Answer(*)

• Sub-Counter #11 : HSDPA Originated Subscribed Traffic Call Answer(*)

• Sub-Counter #12 : Originated Low Priority Signalling Answer

• Sub-Counter #13 : Preservation Call Answer

• Sub-Counter #14 : HSDPA Preservation Call Answer

E-Type

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.Conv

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.HSDPAConv

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.Strm

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.HSDPAStrm

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.Intact

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.HSDPAIntact

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.Bgrd

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.HSDPABgrd

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.Emr

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.HSDPAEmr

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.Subs

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.HSDPASubs

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.SMS

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.Presv

• VS.CallAnswNorMoPs.VS.CallAnswNorMoPs.HSDPAPresv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V5.0

L-Aggregation Rule

Rtotal

Table 495 VS.CallAnswNorMtCs - #2028

A-Description

Number of DL_DT (CONNECT ACK), UL_DT (CP ACK) messages received related to the nor-mal Mobile Terminating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of DL_DT(CONNECT ACK) or UL_DT(CP ACK) or sending of Location Report(Suppl)

D-Result

A set of subcounters screened on: CS Call Rab Answer

• Sub-Counter #0 : Terminating Conversational Call Answer

• Sub-Counter #1 : Terminating Conversational Circuit Etc Answer

• Sub-Counter #2 : Terminating Low Priority Signalling Answer

• Sub-Counter #3 : Terminating High Priority Signalling Answer

E-Type

• VS.CallAnswNorMtCs.VS.CallAnswNorMtCs.ConvVce

• VS.CallAnswNorMtCs.VS.CallAnswNorMtCs.ConvCirEtc

• VS.CallAnswNorMtCs.VS.CallAnswNorMtCs.SMS

• VS.CallAnswNorMtCs.VS.CallAnswNorMtCs.Suppl

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 496 VS.CallAnswNorMtPs - #2029

A-Description

Number of DL_DT (ACTIVATE PDP CONTEXT ACCEPT) or UL_DT (CP ACK) messages re-ceived related to the normal Mobile Terminating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of DL_DT (ACTIVATE PDP CONTEXT ACCEPT) or UL_DT (CP ACK) message orsending of RAB Assignment Response (Preservation call)

D-Result

A set of subcounters screened on: PS Call Rab Answer

• Sub-Counter #0 : Terminating Conversational Call Answer(*)

• Sub-Counter #1 : HSDPA Terminating Conversational Call Answer(*)

• Sub-Counter #2 : Terminating Streaming Call Answer

• Sub-Counter #3 : HSDPA Terminating Streaming Call Answer(*)

• Sub-Counter #4 : Terminating Interactive Call Answer

• Sub-Counter #5 : HSDPA Terminating Interactive Call Answer

• Sub-Counter #6 : Terminating Background Call Answer

• Sub-Counter #7 : HSDPA Terminating Background Call Answer

• Sub-Counter #8 : Terminating Low Priority Signalling Answer

• Sub-Counter #9 : Terminating Preservation Call Answer

• Sub-Counter #10 : HSDPA Terminating Preservation Call Answer

E-Type

• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.Conv

• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.HSDPAConv

• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.Strm



• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.HSDPAStrm

• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.Intact

• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.HSDPAIntact

• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.Bgrd

• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.HSDPABgrd

• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.SMS

• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.Presv

• VS.CallAnswNorMtPs.VS.CallAnswNorMtPs.HSDPAPresv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 497 VS.CallAnswMulMoCs - #2030

A-Description

Number of UL_DT (CONNECT ACK) or DL_DT (CP ACK) messages received related to theMulti-RAB Mobile Originating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of UL_DT (CONNECT ACK) or DL_DT (CP ACK) message

D-Result



A set of subcounters screened on: CS Rab Answer

• Sub-Counter #0 : Call Answer

E-Type

• VS.CallAnswMulMoCs.VS.CallAnswMulMoCs.Answer

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 498 VS.CallAnswMulMoPs - #2031

A-Description

Number of DL_DT (ACTIVATE PDP CONTEXT ACCEPT or CP ACK) messages received re-lated to the Multi-RAB Mobile Originating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of DL_DT (ACTIVATE PDP CONTEXT ACCEPT or CP ACK) message or sendingof RAB Assignment Response (Preservation call)

D-Result

A set of subcounters screened on: PS Rab Answer


• Sub-Counter #1 : HSDPA Call Answer(*)




• Sub-Counter #3 : HSDPA Preservation Call Answer(*)

E-Type

• VS.CallAnswMulMoPs.VS.CallAnswMulMoPs.Answer

• VS.CallAnswMulMoPs.VS.CallAnswMulMoPs.HSDPAAnswer

• VS.CallAnswMulMoPs.VS.CallAnswMulMoPs.Presv

• VS.CallAnswMulMoPs.VS.CallAnswMulMoPs.HSDPAPresv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 499 VS.CallAnswMulMtCs - #2032

A-Description

Number of DL_DT (CONNECT ACK) or UL_DT (CP ACK) messages received related to theMulti-RAB Mobile Terminating calls in CS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of DL_DT (CONNECT ACK) or UL_DT (CP ACK) message

D-Result

A set of subcounters screened on: CS Rab Answer




E-Type

• VS.CallAnswMulMtCs.VS.CallAnswMulMtCs.Answer

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 500 VS.CallAnswMulMtPs - #2033

A-Description

Number of DL_DT (ACTIVATE PDP CONTEXT ACCEPT) messages received related to theMulti-RAB Mobile Terminating calls in PS core network domain.

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of DL_DT (ACTIVATE PDP CONTEXT ACCEPT) message or sending of RAB As-signment Response (Preservation call)

D-Result

A set of subcounters screened on: PS Rab Answer


• Sub-Counter #1 : HSDPA Call Answer(*)




• Sub-Counter #3 : HSDPA Preservation Call Answer(*)

E-Type

• VS.CallAnswMulMtPs.VS.CallAnswMulMtPs.Answer

• VS.CallAnswMulMtPs.VS.CallAnswMulMtPs.HSDPAAnswer

• VS.CallAnswMulMtPs.VS.CallAnswMulMtPs.Presv

• VS.CallAnswMulMtPs.VS.CallAnswMulMtPs.HSDPAPresv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 501 VS.FailState1NorMo - #2034

A-Description

Number of call failures with normal originating establishment in state 1

B-Collection

CUM

CUMulative

C-Condition (Event)

Any failure triggered unsuccessful call setup.

D-Result

A set of subcounters screened on: Fail in state 1:RRC connection setup

• Sub-Counter #0 : Etc Failed

E-Type



• VS.FailState1NorMo.VS.FailState1NorMo.Etcfail

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 502 VS.FailNotState1NorMoCs - #2035

A-Description

Number of call failures with normal originating establishment state other than 1 in CS domain

B-Collection

CUM

CUMulative

C-Condition (Event)

Any failure triggered unsuccessful call

D-Result

A set of subcounters screened on: CS Specific Failure State

• Sub-Counter #0 : Failed in State 2 (Call Attempt)

• Sub-Counter #1 : Failed in Other than State 2 (Call Attempt) -Incomplete Call

• Sub-Counter #2 : Circuit Etc Conversational Failed in State 3 (RAB Attempt)

• Sub-Counter #3 : Voice Etc Conversational Failed in State 4 (RAB Response)

• Sub-Counter #4 : Circuit Etc Conversational Failed in State 4 (RAB Response)





• Sub-Counter #7 : Failed in State other than State 4 (RAB Response) -Incomplete Call

• Sub-Counter #8 : Voice Etc Conversational Failed in State 5 (Call Answer)

• Sub-Counter #9 : Circuit Etc Conversational Failed in State 5 (Call Answer)

E-Type

• VS.FailNotState1NorMoCs.VS.FailNotState1NorMoCs.FailState2

• VS.FailNotState1NorMoCs.VS.FailNotState1NorMoCs.FailOtherState2IncompleteCall

• VS.FailNotState1NorMoCs.VS.FailNotState1NorMoCs.VceEtcConvFailInState3

• VS.FailNotState1NorMoCs.VS.FailNotState1NorMoCs.CirEtcConvFailInState3







F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 503 VS.FailNotState1NorMoPs - #2036

A-Description

Number of call failures with normal originating establishment state other than 1 in PS domain

B-Collection



CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: General Failure State

• Sub-Counter #0 : Etc Failed in State 2 (Call Attempt)


• Sub-Counter #2 : Etc Failed in State 3 (RAB Attempt)

• Sub-Counter #3 : Failed in Other State than State 3 (RAB Attempt) -Incomplete Call

• Sub-Counter #4 : Etc Failed in State 4 (RAB Response)


• Sub-Counter #6 : Etc Failed in State 5 (Call Answer)

E-Type

• VS.FailNotState1NorMoPs.VS.FailNotState1NorMoPs.EtcFailInState2

• VS.FailNotState1NorMoPs.VS.FailNotState1NorMoPs.FailOtherState2IncompleteCall






F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0



L-Aggregation Rule

Rtotal

Table 504 VS.FailState1NorMt - #2037

A-Description

Number of call failures with normal terminating establishment in state 1

B-Collection

CUM

CUMulative

C-Condition (Event)

Any failure triggered unsuccessful call setup

D-Result

A set of subcounters screened on: Fail in state 1:RRC connection setup

• Sub-Counter #0 : Etc Failed

E-Type

• VS.FailState1NorMt.VS.FailState1NorMt.Etcfail

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 505 VS.FailNotState1NorMtCs - #2038



A-Description

Number of call failures with normal terminating establishment state other than 1 in CS domain

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: CS Specific Failure State

• Sub-Counter #0 : Failed in State 2 (Call Attempt)


• Sub-Counter #2 : Circuit Etc Conversational Failed in State 3 (RAB Attempt)






• Sub-Counter #8 : Voice Etc Conversational Failed in State 5 (Call Answer)

• Sub-Counter #9 : Circuit Etc Conversational Failed in State 5 (Call Answer)

E-Type

• VS.FailNotState1NorMtCs.VS.FailNotState1NorMtCs.FailState2

• VS.FailNotState1NorMtCs.VS.FailNotState1NorMtCs.FailOtherState2IncompleteCall

• VS.FailNotState1NorMtCs.VS.FailNotState1NorMtCs.VceEtcConvFailInState3

• VS.FailNotState1NorMtCs.VS.FailNotState1NorMtCs.CirEtcConvFailInState3







F-Object Instance

Cell

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 506 VS.FailNotState1NorMtPs - #2039

A-Description

Number of call failures with normal terminating establishment state other than 1 in PS domain

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result









E-Type

• VS.FailNotState1NorMtPs.VS.FailNotState1NorMtPs.EtcFailInState2

• VS.FailNotState1NorMtPs.VS.FailNotState1NorMtPs.FailOtherState2IncompleteCall








F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 507 VS.FailNotState1MulMoCs - #2040

A-Description

Number of call failures with Multi-RAB originating establishment state other than 1 in CS do-main

B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result











E-Type

• VS.FailNotState1MulMoCs.VS.FailNotState1MulMoCs.EtcFailInState2

• VS.FailNotState1MulMoCs.VS.FailNotState1MulMoCs.FailOtherState2IncompleteCall






F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 508 VS.FailNotState1MulMoPs - #2041

A-Description

Number of call failures with Multi-RAB originating establishment state other than 1 in PS do-main

B-Collection

CUM

CUMulative



C-Condition (Event)


D-Result









E-Type

• VS.FailNotState1MulMoPs.VS.FailNotState1MulMoPs.EtcFailInState2

• VS.FailNotState1MulMoPs.VS.FailNotState1MulMoPs.FailOtherState2IncompleteCall






F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



Table 509 VS.FailNotState1MulMtCs - #2042

A-Description

Number of call failures with Multi-RAB terminating establishment and CS domain in state otherthan 1

B-Collection

CUM

CUMulative

C-Condition (Event)

Any failure triggered unsuccessful call.

D-Result









E-Type

• VS.FailNotState1MulMtCs.VS.FailNotState1MulMtCs.EtcFailInState2

• VS.FailNotState1MulMtCs.VS.FailNotState1MulMtCs.FailOtherState2IncompleteCall






F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range



31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 510 VS.FailNotState1MulMtPs - #2043

A-Description

Number of call failures with Multi-RAB terminating establishment and PS domain in state otherthan 1

B-Collection

CUM

CUMulative

C-Condition (Event)

Any failure triggered unsuccessful call.

D-Result









E-Type

• VS.FailNotState1MulMtPs.VS.FailNotState1MulMtPs.EtcFailInState2

• VS.FailNotState1MulMtPs.VS.FailNotState1MulMtPs.FailOtherState2IncompleteCall








F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 511 VS.LocRegRRCAtt - #2044

A-Description

Number of Local Registration message received

B-Collection

CUM

CUMulative

C-Condition (Event)

signal call without firing Rab Setup

D-Result

A set of subcounters screened on: Local registration RRC attempt

• Sub-Counter #0 : RRC registration Attempt

• Sub-Counter #1 : RRC Detach Attempt

E-Type

• VS.LocRegRRCAtt.VS.LocRegRRCAtt.Regist

• VS.LocRegRRCAtt.VS.LocRegRRCAtt.Detach

F-Object Instance



Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 512 VS.LocRegCallAtt - #2045

A-Description

Location Registration

B-Collection

CUM

CUMulative

C-Condition (Event)

The trigger is when INITIAL DIRECT TRANSFER message is received from UE

D-Result

A set of subcounters screened on: Local registration call attempt

• Sub-Counter #0 : Cs Registration Call Attempt

• Sub-Counter #1 : Cs Detach Call Attempt

• Sub-Counter #2 : Ps Registration Call Attempt

• Sub-Counter #3 : Ps Detach Call Attempt

E-Type

• VS.LocRegCallAtt.VS.LocRegCallAtt.CsRegist

• VS.LocRegCallAtt.VS.LocRegCallAtt.CsDetach

• VS.LocRegCallAtt.VS.LocRegCallAtt.PsRegist

• VS.LocRegCallAtt.VS.LocRegCallAtt.PsDetach



F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 513 VS.LocRegCallAnsw - #2046

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)

Registration: when DL_DT (Location Updating Accept or Routing Area Location Accept) is re-ceived. Detach: when Initial UE Message is sent towards Core Network.

D-Result

A set of subcounters screened on: Local registration Call Answer

• Sub-Counter #0 : Cs Registration Call Answer

• Sub-Counter #1 : Cs Detach Call Answer

• Sub-Counter #2 : Ps Registration Call Answer

• Sub-Counter #3 : Ps Detach Call Answer

E-Type

• VS.LocRegCallAnsw.VS.LocRegCallAnsw.CsRegist

• VS.LocRegCallAnsw.VS.LocRegCallAnsw.CsDetach



• VS.LocRegCallAnsw.VS.LocRegCallAnsw.PsRegist

• VS.LocRegCallAnsw.VS.LocRegCallAnsw.PsDetach

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 514 VS.LocRegFail - #2047

A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)

any failure triggering an unsuccessful call in the specified states.

D-Result

A set of subcounters screened on: Local registration failure

• Sub-Counter #0 : Etc Fail in State1

• Sub-Counter #1 : Cs Etc Fail in State2

• Sub-Counter #2 : Ps Etc Fail in State2

E-Type

• VS.LocRegFail.VS.LocRegFail.EtcFailState1



• VS.LocRegFail.VS.LocRegFail.CsEtcFailState2

• VS.LocRegFail.VS.LocRegFail.PsEtcFailState2

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 515 VS.PagingRsp - #2049

A-Description

Paging

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of Paging Response indication in Initial Direct Transfer

D-Result

A set of subcounters screened on: paging screening

• Sub-Counter #0 : Paging response (NAS)

E-Type

• VS.PagingRsp.VS.PagingRsp.Paging

F-Object Instance

RNC



G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 516 VS.CsMoState2Failure - #2050

A-Description

number of CS mobile originating failure at state 2.

B-Collection

CUM

CUMulative

C-Condition (Event)

CS Mobile Originating failure at state 2.

D-Result

A set of subcounters screened on: Per type of CS Mobile Originating call failure at state 2

• Sub-Counter #0 : CnInvalSubS2

• Sub-Counter #1 : CnIncmpPrfS2

• Sub-Counter #2 : CnOrgRelCspS2

• Sub-Counter #3 : CnCallBarS2

• Sub-Counter #4 : CnUserBusyS2

• Sub-Counter #5 : CnTerEtcS2

• Sub-Counter #6 : CnPagNoRspS2

• Sub-Counter #7 : CnWrongNoS2

• Sub-Counter #8 : CnImsiDetS2

• Sub-Counter #9 : CnIncomDialS2



• Sub-Counter #10 : CnWrongFtnS2

• Sub-Counter #11 : CnFwdCntErrS2

• Sub-Counter #12 : CnSysFailS2

• Sub-Counter #13 : CnIsupErrS2

• Sub-Counter #14 : CnMobileErrS2

• Sub-Counter #15 : CnOrgRelMmS2

E-Type

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnInvalSubS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnIncmpPrfS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnOrgRelCspS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnCallBarS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnUserBusyS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnTerEtcS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnPagNoRspS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnWrongNoS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnImsiDetS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnIncomDialS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnWrongFtnS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnFwdCntErrS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnSysFailS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnIsupErrS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnMobileErrS2

• VS.CsMoState2Failure.VS.CsMoState2Failure.CnOrgRelMmS2

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event



K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 517 VS.PsMoState2Failure - #2051

A-Description

number of PS mobile originating failure at state 2.

B-Collection

CUM

CUMulative

C-Condition (Event)

PS Mobile Originating failure at state 2.

D-Result

A set of subcounters screened on: Per type of PS Mobile Originating call failure at state 2

• Sub-Counter #0 : CnOperBarS2

• Sub-Counter #1 : CnMisApnS2

• Sub-Counter #2 : CnUnkPdpS2


• Sub-Counter #4 : CnActRejS2

• Sub-Counter #5 : CnRejUnspeS2

• Sub-Counter #6 : CnNsupSoS2

• Sub-Counter #7 : CnNsubRoS2

• Sub-Counter #8 : CnSoTempS2

• Sub-Counter #9 : CnNcmpMsgS2


• Sub-Counter #11 : CnProtoErrS2

• Sub-Counter #12 : CnRoamRestS2

E-Type

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnOperBarS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnMisApnS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnUnkPdpS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnInvalSubS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnActRejS2



• VS.PsMoState2Failure.VS.PsMoState2Failure.CnRejUnspeS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnNsupSoS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnNsubRoS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnSoTempS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnNcmpMsgS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnOrgRelMmS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnProtoErrS2

• VS.PsMoState2Failure.VS.PsMoState2Failure.CnRoamRestS2

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal


A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result




• Sub-Counter #0 : CnIncmpPrfS3






E-Type

• VS.CsMoState3Failure.VS.CsMoState3Failure.CnIncmpPrfS3






F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal


A-Description


B-Collection

CUM



CUMulative

C-Condition (Event)


D-Result



E-Type


F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal


A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result






• Sub-Counter #2 : CnNoAnsS4





E-Type


• VS.CsMoState4Failure.VS.CsMoState4Failure.CnTerEtcS4

• VS.CsMoState4Failure.VS.CsMoState4Failure.CnNoAnsS4





F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal


A-Description




B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result



E-Type


F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 522 VS.CsMtState2Failure - #2056

A-Description

number of CS mobile terminating failure at state 2.

B-Collection

CUM

CUMulative

C-Condition (Event)



CS Mobile terminating failure at state 2.

D-Result

A set of subcounters screened on: Per type of CS Mobile Terminating call failure at state 2







E-Type

• VS.CsMtState2Failure.VS.CsMtState2Failure.CnInvalSubS2

• VS.CsMtState2Failure.VS.CsMtState2Failure.CnOrgRelCspS2

• VS.CsMtState2Failure.VS.CsMtState2Failure.CnFwdCntErrS2

• VS.CsMtState2Failure.VS.CsMtState2Failure.CnIsupErrS2

• VS.CsMtState2Failure.VS.CsMtState2Failure.CnMobileErrS2

• VS.CsMtState2Failure.VS.CsMtState2Failure.CnOrgRelMmS2

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 523 VS.PsMtState2Failure - #2057

A-Description



number of PS mobile terminating failure at state 2.

B-Collection

CUM

CUMulative

C-Condition (Event)

PS Mobile terminating failure at state 2.

D-Result

A set of subcounters screened on: Per type of PS Mobile Terminating call failure at state 2

• Sub-Counter #0 : CnMisApnS2

• Sub-Counter #1 : CnUnkPdpS2


• Sub-Counter #3 : CnActRejS2


• Sub-Counter #5 : CnNsupSoS2

• Sub-Counter #6 : CnNsubRoS2

• Sub-Counter #7 : CnSoTempS2

• Sub-Counter #8 : CnNcmpMsgS2


• Sub-Counter #10 : CnProtoErrS2

• Sub-Counter #11 : CnRoamRestS2

E-Type

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnMisApnS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnUnkPdpS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnInvalSubS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnActRejS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnRejUnspeS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnNsupSoS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnNsubRoS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnSoTempS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnNcmpMsgS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnOrgRelMmS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnProtoErrS2

• VS.PsMtState2Failure.VS.PsMtState2Failure.CnRoamRestS2

F-Object Instance



Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal


A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: Per type of CS Mobile Terminating call failure at state 3





E-Type







F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal


A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: Per type of PS Mobile Terminating call failure at state 3


E-Type


F-Object Instance

Cell

G-Switching

NA



H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal


A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: Per type of CS Mobile terminating call failure at state 4



• Sub-Counter #2 : CnNoAnsS4




E-Type


• VS.CsMtState4Failure.VS.CsMtState4Failure.CnTerEtcS4

• VS.CsMtState4Failure.VS.CsMtState4Failure.CnNoAnsS4






F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal


A-Description


B-Collection

CUM

CUMulative

C-Condition (Event)


D-Result

A set of subcounters screened on: Per type of PS Mobile terminating call failure at state 4


E-Type


F-Object Instance

Cell

G-Switching



NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 528 VS.LocalRegState1Failure - #2062

A-Description

Local Registration Failure at state 1.

B-Collection

CUM

CUMulative

C-Condition (Event)

Local registration failure

D-Result

A set of subcounters screened on: Per type of Local Registration Failure at state 1

• Sub-Counter #0 : RrcFail

• Sub-Counter #1 : NbapFail

E-Type

• VS.LocalRegState1Failure.VS.LocalRegState1Failure.RrcFail

• VS.LocalRegState1Failure.VS.LocalRegState1Failure.NbapFail

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 529 VS.CsLocalRegState2Failure - #2063

A-Description

CS Local Registration Failure at state 2.

B-Collection

CUM

CUMulative

C-Condition (Event)

CS Local registration failure

D-Result



• Sub-Counter #1 : No7Fail

• Sub-Counter #2 : CnInvalSub

E-Type

• VS.CsLocalRegState2Failure.VS.CsLocalRegState2Failure.RrcFail

• VS.CsLocalRegState2Failure.VS.CsLocalRegState2Failure.No7Fail

• VS.CsLocalRegState2Failure.VS.CsLocalRegState2Failure.CnInvalSub

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 530 VS.PsLocalRegState2Failure - #2064

A-Description

PS Local Registration Failure at state 2.

B-Collection

CUM

CUMulative

C-Condition (Event)

PS Local registration failure

D-Result



• Sub-Counter #1 : No7Fail

• Sub-Counter #2 : CnInvalSub

E-Type

• VS.PsLocalRegState2Failure.VS.PsLocalRegState2Failure.RrcFail

• VS.PsLocalRegState2Failure.VS.PsLocalRegState2Failure.No7Fail

• VS.PsLocalRegState2Failure.VS.PsLocalRegState2Failure.CnInvalSub

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 531 VS.CsMoCallAvgHoldingTime - #2065

A-Description

CS mobile originating call average holding time

B-Collection

VAL

VALue counter

C-Condition (Event)

CS Mobile Originating call holding time, triggered from the beginning of state 5 to the end ofstate5.

D-Result

A set of subcounters screened on: Per type of Mobile Originating CS Call Average HoldingTime

• Sub-Counter #0 : Conv

• Sub-Counter #1 : Emer

E-Type

• VS.CsMoCallAvgHoldingTime.VS.CsMoCallAvgHoldingTime.Conv

• VS.CsMoCallAvgHoldingTime.VS.CsMoCallAvgHoldingTime.Emer

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rval

Table 532 VS.PsMoCallAvgHoldingTime - #2066

A-Description

PS mobile originating call average holding time

B-Collection

VAL

VALue counter

C-Condition (Event)

PS Mobile Originating call holding time, triggered from the beginning of state 5 to the end ofstate5.

D-Result

A set of subcounters screened on: Per type of Mobile Originating PS Call Average HoldingTime


• Sub-Counter #1 : Strm

• Sub-Counter #2 : Intact

• Sub-Counter #3 : Bgrd


• Sub-Counter #5 : Subs

• Sub-Counter #6 : Presv

E-Type

• VS.PsMoCallAvgHoldingTime.VS.PsMoCallAvgHoldingTime.Conv

• VS.PsMoCallAvgHoldingTime.VS.PsMoCallAvgHoldingTime.Strm

• VS.PsMoCallAvgHoldingTime.VS.PsMoCallAvgHoldingTime.Intact

• VS.PsMoCallAvgHoldingTime.VS.PsMoCallAvgHoldingTime.Bgrd



• VS.PsMoCallAvgHoldingTime.VS.PsMoCallAvgHoldingTime.Emer

• VS.PsMoCallAvgHoldingTime.VS.PsMoCallAvgHoldingTime.Subs

• VS.PsMoCallAvgHoldingTime.VS.PsMoCallAvgHoldingTime.Presv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rval

Table 533 VS.CsMtCallAvgHoldingTime - #2067

A-Description

CS mobile terminating call average holding time

B-Collection

VAL

VALue counter

C-Condition (Event)

CS Mobile terminating call holding time, triggered from the beginning of state 5 to the end ofstate5.

D-Result

A set of subcounters screened on: Per type of Mobile Terminating Call CS Average HoldingTime


E-Type

• VS.CsMtCallAvgHoldingTime.VS.CsMtCallAvgHoldingTime.Conv



F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rval

Table 534 VS.PsMtCallAvgHoldingTime - #2068

A-Description

PS mobile terminating call average holding time

B-Collection

VAL

VALue counter

C-Condition (Event)

PS Mobile terminating call holding time, triggered from the beginning of state 5 to the end ofstate5.

D-Result

A set of subcounters screened on: Per type of Mobile terminating PS Call Average HoldingTime






E-Type



• VS.PsMtCallAvgHoldingTime.VS.PsMtCallAvgHoldingTime.Conv

• VS.PsMtCallAvgHoldingTime.VS.PsMtCallAvgHoldingTime.Strm

• VS.PsMtCallAvgHoldingTime.VS.PsMtCallAvgHoldingTime.Intact

• VS.PsMtCallAvgHoldingTime.VS.PsMtCallAvgHoldingTime.Bgrd

• VS.PsMtCallAvgHoldingTime.VS.PsMtCallAvgHoldingTime.Presv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rval

Table 535 VS.CsMoRabCallAvgSetupTime - #2069

A-Description

CS mobile originating RAB call average set up time

B-Collection

VAL

VALue counter

C-Condition (Event)

CS Mobile originating call setup time, triggered from the beginning of state 1 to the beginningof state5.

D-Result

A set of subcounters screened on: Per type of CS Mobile Originating RAB Call Average Set upTime





E-Type

• VS.CsMoRabCallAvgSetupTime.VS.CsMoRabCallAvgSetupTime.Conv

• VS.CsMoRabCallAvgSetupTime.VS.CsMoRabCallAvgSetupTime.Emer

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rval

Table 536 VS.PsMoRabCallAvgSetupTime - #2070

A-Description

PS mobile originating RAB call average set up time

B-Collection

VAL

VALue counter

C-Condition (Event)

PS Mobile originating call setup time, triggered from the beginning of state 1 to the beginning ofstate5.

D-Result

A set of subcounters screened on: Per type of PS Mobile Originating RAB Call Average Set upTime








• Sub-Counter #5 : Subs


E-Type

• VS.PsMoRabCallAvgSetupTime.VS.PsMoRabCallAvgSetupTime.Conv

• VS.PsMoRabCallAvgSetupTime.VS.PsMoRabCallAvgSetupTime.Strm

• VS.PsMoRabCallAvgSetupTime.VS.PsMoRabCallAvgSetupTime.Intact

• VS.PsMoRabCallAvgSetupTime.VS.PsMoRabCallAvgSetupTime.Bgrd

• VS.PsMoRabCallAvgSetupTime.VS.PsMoRabCallAvgSetupTime.Emer

• VS.PsMoRabCallAvgSetupTime.VS.PsMoRabCallAvgSetupTime.Subs

• VS.PsMoRabCallAvgSetupTime.VS.PsMoRabCallAvgSetupTime.Presv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rval

Table 537 VS.CsMtRabCallAvgSetupTime - #2071

A-Description

CS mobile terminating RAB call average set up time

B-Collection

VAL



VALue counter

C-Condition (Event)

CS Mobile terminating call setup time, triggered from the beginning of state 1 to the beginningof state5.

D-Result

A set of subcounters screened on: Per type of CS Mobile Terminating RAB Call Average Setup Time


E-Type

• VS.CsMtRabCallAvgSetupTime.VS.CsMtRabCallAvgSetupTime.Conv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rval

Table 538 VS.PsMtRabCallAvgSetupTime - #2072

A-Description

PS mobile terminating RAB call average set up time

B-Collection

VAL

VALue counter

C-Condition (Event)

PS Mobile terminating call setup time, triggered from the beginning of state 1 to the beginning



of state5.

D-Result

A set of subcounters screened on: Per type of PS Mobile Terminating RAB Call Average Setup Time






E-Type

• VS.PsMtRabCallAvgSetupTime.VS.PsMtRabCallAvgSetupTime.Conv

• VS.PsMtRabCallAvgSetupTime.VS.PsMtRabCallAvgSetupTime.Strm

• VS.PsMtRabCallAvgSetupTime.VS.PsMtRabCallAvgSetupTime.Intact

• VS.PsMtRabCallAvgSetupTime.VS.PsMtRabCallAvgSetupTime.Bgrd

• VS.PsMtRabCallAvgSetupTime.VS.PsMtRabCallAvgSetupTime.Presv

F-Object Instance

Cell

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

ms

K-Available Release

V5.0

L-Aggregation Rule

Rval



5.17 CDMA Handover


Counter name

#2101 VS.RRCCdmaHOFromUtranCmd

#2102 VS.RRCCdmaHOFromUtranFail

#2103 VS.RRCCdmaHOFromUtranComp

#2104 VS.RRCCdmaHOPrepAtt

#2105 VS.RRCCdmaHOPrepFail

#2106 VS.RRCCdmaHOPrePSucc

Table 539 VS.RRCCdmaHOFromUtranCmd - #2101

A-Description

Number of HO FROM UTRAN COMMAND messages transmission from RNC to UE

B-Collection

CUM

CUMulative

C-Condition (Event)

Sending HO FROM UTRAN COMMAND message

D-Result

A set of subcounters screened on: Attempted Outgoing to CDMA 2K HO

• Sub-Counter #0 : Cs HO outgoing to CDMA2000

• Sub-Counter #1 : Ps HO outgoing to CDMA2000

E-Type

• VS.RRCCdmaHOFromUtranCmd.VS.RRCCdmaHOFromUtranCmd.Handover

• VS.RRCCdmaHOFromUtranCmd.VS.RRCCdmaHOFromUtranCmd.HandoverUTRAN

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance




I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 540 VS.RRCCdmaHOFromUtranFail - #2102

A-Description

Number of HANDOVER FROM UTRAN FAILURE messages received by RNC from UE

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception HANDOVER FROM UTRAN FAILURE message

D-Result

A set of subcounters screened on: Failed Outgoing to CDMA 2K HO



E-Type

• VS.RRCCdmaHOFromUtranFail.VS.RRCCdmaHOFromUtranFail.FailHO

• VS.RRCCdmaHOFromUtranFail.VS.RRCCdmaHOFromUtranFail.FailHOUTRAN

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits



J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 541 VS.RRCCdmaHOFromUtranComp - #2103

A-Description

Number of IU RELEASE COMMAND messages received by RNC from CN

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception IU RELEASE COMMAND message

D-Result

A set of subcounters screened on: Successful Outgoing to CDMA 2K HO



E-Type

• VS.RRCCdmaHOFromUtranComp.VS.RRCCdmaHOFromUtranComp.SuccHO

• VS.RRCCdmaHOFromUtranComp.VS.RRCCdmaHOFromUtranComp.SuccHOUTRAN

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release



V5.0

L-Aggregation Rule

Rtotal

Table 542 VS.RRCCdmaHOPrepAtt - #2104

A-Description

Number of RANAP RELOCATION REQUIRED messages send by RNC to CN

B-Collection

CUM

CUMulative

C-Condition (Event)

Transmission RELOCATION REQUIRED message

D-Result

one measurement

E-Type

VS.RRCCdmaHOPrepAtt

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 543 VS.RRCCdmaHOPrepFail - #2105

A-Description



Number of RELOCATION PREPARATION FAILURE message received by RNC from CN

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of RELOCATION PREPARATION FAILURE

D-Result

A set of subcounters screened on: HO Prep Failure

• Sub-Counter #0 : TimeOut on HO Preparation

• Sub-Counter #1 : Failure on HO Preparation

E-Type

• VS.RRCCdmaHOPrepFail.VS.RRCCdmaHOPrepFail.TmoPrepHO

• VS.RRCCdmaHOPrepFail.VS.RRCCdmaHOPrepFail.FailPrepHOUTRAN

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal

Table 544 VS.RRCCdmaHOPrePSucc - #2106

A-Description

Number of RELOCATION COMMAND messages received by RNC from CN

B-Collection

CUM



CUMulative

C-Condition (Event)

Reception of RELOCATION COMMAND message

D-Result

one measurement

E-Type

VS.RRCCdmaHOPrePSucc

F-Object Instance

Cell(Reference)

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit

event

K-Available Release

V5.0

L-Aggregation Rule

Rtotal



5.18 Platform


Counter name

#3002 VS.RncCallCleanup

Table 545 VS.RncCallCleanup - #3002

A-Description

the number of calls that have been cleaned-up by the RNC due to internal problems.

B-Collection

CUM

CUMulative

C-Condition (Event)

Any internal problem detected.

D-Result

A set of subcounters screened on: Callp component at fault

• Sub-Counter #0 : Ue Call

• Sub-Counter #1 : Ue Rrc

• Sub-Counter #2 : Iu Call

E-Type

• VS.RncCallCleanup.VS.RncCallCleanup.UeCall

• VS.RncCallCleanup.VS.RncCallCleanup.UeRrc

• VS.RncCallCleanup.VS.RncCallCleanup.IuCall

F-Object Instance

TMU

G-Switching

NA

H-3GPP Compliance


I-Range

31 Bits

J-Unit



event

K-Available Release

V2.0

L-Aggregation Rule

Rtotal



5.19 Synthetic

The synthetic counters are computed by OAM, combining elemntary counters coming from RNC.


Counter name

#SHO.AttRLAddUTRANSide

SHO.AttRLAddUTRANSide

#SHO.SuccRLAddUTRANSide

SHO.SuccRLAddUTRANSide

#SHO.FailRLAddUTRANSide

FAILED RADIO LINK CREATIONS (UTRAN SIDE)

#SHO.AttRLDelUTRANSide

SHO.AttRLDelUTRANSide

#SHO.SuccRLDelUTRANSide

SHO.SuccRLDelUTRANSide

#IRATHO ATTEMPTED OUTGOING CIRCUIT SWITCHED INTER-RAT HAN-DOVERS

Table 546 SHO.AttRLAddUTRANSide - #SHO.AttRLAddUTRANSide

A-Description

This measurement provides the number of attempted radio link creations (UTRAN side) foreach cell. This measurement shall be increased for each attempted radio link setup or radiolink addition (Softer HO) (UTRAN side).sum(VS.RadioLinkSetupSuccess)+VS.RadioLinkSetupUnsuccess.RadioLinkSetupFailure+VS.RadioLinkSetupUnsuc-cess.Timeout+sum(VS.RadioLinkAdditionSuccess)+VS.RadioLinkAdditionUnsuccess.RadioLinkAdditionFailure+VS.RadioLinkAdditionUnsuccess.Timeout

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RADIO LINK SETUP RESPONSE/FAILURE message or a RADIO LINK ADDI-TION RESPONSE/FAILURE (NBAP) by the RNC from the NodeB or time-out without re-sponse.

D-Result

One integer value.

E-Type



SHO.AttRLAddUTRANSide

F-Object Instance

G-Switching

H-3GPP Compliance

3GPP counter-3GPP counter-#SHO.AttRLAddUTRANSide

I-Range

0-2^31-1

J-Unit

event

K-Available Release

NA

L-Aggregation Rule

Rtotal

Table 547 SHO.SuccRLAddUTRANSide - #SHO.SuccRLAddUTRANSide

A-Description

This measurement provides the number of successful radio link creations (UTRAN side) foreach cell. This measurement shall be increased for each successful radio link setup or radiolink addition (Softer HO) (UTRAN side).sum(VS.RadioLinkSetupSuccess)+sum(VS.RadioLinkAdditionSuccess)

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a RADIO LINK SETUP RESPONSE message or a RADIO LINK ADDITION RE-SPONSE (NBAP) by the RNC from the NodeB. Receipt of a RADIO LINK SETUP FAILUREmessage or a RADIO LINK ADDITION FAILURE (NBAP) by the RNC from the NodeB as oneRADIO LINK SETUP / ADDITION FAILURE message can be related to more than one addedradio link (certain being successful) : each successful added radio link shall be considered sep-arately (see TS 25.433).

D-Result

One integer value.

E-Type

SHO.SuccRLAddUTRANSide

F-Object Instance



G-Switching

Valid for circuit switched and packet switched traffic

H-3GPP Compliance

3GPP counter-3GPP counter-#SHO.SuccRLAddUTRANSide

I-Range

0-2^31-1

J-Unit

event

K-Available Release

NA

L-Aggregation Rule

Rtotal

Table 548 FAILED RADIO LINK CREATIONS (UTRAN SIDE) - #SHO.FailRLAddUTRANSide

A-Description

This measurement provides the number of failed radio link creations (UTRAN side) for eachcell. This measurement shall be increased for each failed radio link setup or radio link addition(Softer HO) (UTRAN side).

B-Collection

CUM

CUMulative

C-Condition (Event)

Receipt of a RADIO LINK SETUP FAILURE message or a RADIO LINK ADDITION FAILURE(NBAP) by the RNC from the NodeB. One RADIO LINK ADDITION/SETUP FAILURE messagecan be related to more than one added radio link : each successful added radio link shall beconsidered separately (see TS 25.433).VS.RadioLinkSetupUnsuccess.RadioLinkSetupFailure+VS.RadioLinkAdditionUnsuccess.RadioLinkAdditionFailureVS.RadioLinkSetupUnsuccess.Timeout+VS.RadioLinkAdditionUnsuccess.Timeout

D-Result

A set of subcounters screened on: failure cause or Time-out

• Sub-Counter #0 : "Failure"

• Sub-Counter #1 : "Time-out"

E-Type



• FAILED RADIO LINK CREATIONS (UTRAN SIDE).SHO.FailRLAddUTRANSide.Failure

• FAILED RADIO LINK CREATIONS (UTRAN SIDE).SHO.FailRLAddUTRANSide.Timeout

F-Object Instance

G-Switching


H-3GPP Compliance

3GPP counter-3GPP counter-#SHO.FailRLAddUTRANSide

I-Range

0-2^31-1

J-Unit

event

K-Available Release

NA

L-Aggregation Rule

Rtotal

Table 549 SHO.AttRLDelUTRANSide - #SHO.AttRLDelUTRANSide

A-Description

This measurement provides the number of attempted radio link deletions (UTRAN side) foreach cell. This measurement shall be increased for each attempted radio link deletion (UTRANside). VS.RadioLinkDeletionSuccess+VS.RadioLinkDeletionUnsuccess

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RADIO LINK DELETION RESPONSE message (NBAP) by the RNC from theNode B.

D-Result

One integer value.

E-Type

SHO.AttRLDelUTRANSide

F-Object Instance

G-Switching




H-3GPP Compliance

3GPP counter-3GPP counter-#SHO.AttRLDelUTRANSide

I-Range

0-2^31-1

J-Unit

event

K-Available Release

NA

L-Aggregation Rule

Rtotal

Table 550 SHO.SuccRLDelUTRANSide - #SHO.SuccRLDelUTRANSide

A-Description

This measurement provides the number of successful radio link deletions (UTRAN side) foreach cell. This measurement shall be increased for each successful radio link deletion (UTRANside). VS.RadioLinkDeletionSuccess

B-Collection

CUM

CUMulative

C-Condition (Event)

Reception of a RADIO LINK DELETION RESPONSE/FAILURE message (NBAP) by the RNCfrom the NodeB or time-out without response.

D-Result

One integer value.

E-Type

SHO.SuccRLDelUTRANSide

F-Object Instance

G-Switching


H-3GPP Compliance

3GPP counter-3GPP counter-#SHO.SuccRLDelUTRANSide

I-Range



0-2^31-1

J-Unit

event

K-Available Release

NA

L-Aggregation Rule

Rtotal

Table 551 ATTEMPTED OUTGOING CIRCUIT SWITCHED INTER-RAT HANDOVERS - #IRATHO

A-Description

This measurement provides the number of attempted outgoing CS inter-RAT hard handovers.VS.RrcHoFromUtranCommand.RescueCs+VS.RrcHoFromUtranCommand.ServiceCs

B-Collection

CUM

CUMulative

C-Condition (Event)

Transmission of a RRC-message INTER RAT HANDOVER COMMAND from serving RNC tothe UE, indicating an attempted outgoing inter-RAT handover.

D-Result

A set of subcounters screened on: Success or Failure of Outgoing Inter-Rat HO

• Sub-Counter #0 : "Attempted Outgoing inter-Rat Handovers Circuit Switched"

• Sub-Counter #1 : "Failed Outgoing Inter-rat Handovers Circuit Switched"

E-Type

• ATTEMPTED OUTGOING CIRCUIT SWITCHED INTER-RAT HAN-DOVERS.IRATHO.AttOutCS

• ATTEMPTED OUTGOING CIRCUIT SWITCHED INTER-RAT HAN-DOVERS.IRATHO.FailOutCs

F-Object Instance

G-Switching

H-3GPP Compliance

3GPP counter-3GPP counter-#IRATHO

I-Range

0-2^31-1



J-Unit

event

K-Available Release

NA

L-Aggregation Rule

Rtotal



6 Screening Appendices

T01-Uplink Traffic Counter Screenings

ID Name Description

0 UlRabOther Other Ul

1 UlRabSRB Any SRB

2 UlRabCsSpeech CS speech

3 UlRabCsData64 CS 64 conversational

4 UlRabCsStr14_4 CS 14.4 streaming

5 UlRabCsStr57_6 CS 57.6 streaming

6 UlRabPsStr Any PS streaming

7 UlRabPsIb8 PS I/B 8kbps





T02-Downlink Traffic Counter Screenings

ID Name Description

0 DlRabOther Other Dl

1 DlRabSRB Any SRB

2 DlRabCsSpeech CS speech

3 DlRabCsData64 CS 64 conversational

4 DlRabCsStr14_4 CS 14.4 streaming

5 DlRabCsStr57_6 CS 57.6 streaming

6 DlRabHsdpa HSDPA

7 DlRabPsStr Any PS streaming

8 DlRabPsIb8 PS I/B 8kbps





T03-DlRbSetId,UlRbSetId,TrafficClass derived screening per requested Rab



ID Name Description

0 ReqRabOther Other Dl, Ul, Traffic Class combinations

1 ReqRabC-sSpeechConv

Dl and Ul are CS Speech, TC is Conversational

2 ReqRabC-sConv64

Dl and Ul are CSD 64, TC is Conversational

3 ReqRabC-sStr14_4

Dl and Ul are CS 14.4, TC is Streaming

4 ReqRabC-sStr57_6


5 ReqR-abPsLowRateInter

Dl is any low rate PS I/B, Ul is any PS I/B, TC is Interative

6 ReqR-abPsLowRate-Bgnd

Dl is any low rate PS I/B, Ul is any PS I/B, TC is Background

7 ReqRabPsStr Dl and Ul are any PS Str, TC is Streaming

8 ReqRabP-sHighRateInter

Dl is any high rate PS I/B, Ul is any PS I/B, TC is Interative

T04-DlRbSetId,UlRbSetId,TrafficClass derived screening per granted Rab

ID Name Description

0 GrntdRabOther Other Dl, Ul, Traffic Class combinations

1 GrntdRabC-SSpeechConv

Dl and Ul are CS Speech, TC is Conversational

2 GrntdRabC-sConv64

Dl and Ul are CSD 64, TC is Conversational

3 GrntdRabC-sStr14_4


4 GrntdRabC-sStr57_6


5 GrntdRabPsInter Dl is any PS I/B, Ul is any PS I/B, TC is Interative

6 GrntdRabPsBgnd Dl is any PS I/B, Ul is any PS I/B, TC is Background

7 GrntdRabPsStr Dl and Ul are any PS Str, TC is Streaming

8 GrntdRabPs2xInter

Dl is any 2x PS I/B, Ul is any 2x PS I/B, TC is Interative

9 GrntdRabPs2xBgnd

Dl is any 2x PS I/B, Ul is any 2x PS I/B, TC is Background

10 GrntdRabHs-dpaPsInter

Dl is HSDPA, Ul is any PS I/B, TC is Interactive

11 GrntdRabHs- Dl is HSDPA, Ul is any PS I/B, TC is Background



ID Name Description

dpaPsBgnd

12 GrntdRabHs-dpaHsupaInter

Dl is HSDPA, Ul is HSUPA, TC is Interactive

13 GrntdRabHs-dpaHsupaBgnd

Dl is HSDPA, Ul is HSUPA, TC is Background

14 GrntdRabHs-dpa2xPsInter

Dl is HSDPA, Ul is any 2x PS I/B, TC is Interactive

15 GrntdRabHs-dpa2xPsBgnd

Dl is HSDPA, Ul is any 2x PS I/B, TC is Background

T05-Target type of call for Radio Link Reconfiguration

ID Name Description

0 DlAsCnfOther Other Type of Call

1 DlAsCnfSig Signalling Only

2 DlAsCnfC-sSpeech

CS speech

3 DlAsCnfCsData CS data

4 DlAsCnfCsStr Any CS Streaming

5 DlAsCnfPsStr Any PS Streaming

6 DlAsCnfPsIB Any PS interactive/background

7 DlAsCnfC-sSpeechPsIB

CS speech and any PS interactive/background

8 DlAsCnfCsData-PsIB

CS data and any PS interactive/background

9 DlAsCn-fPsStrPsIB

PS Streaming and any PS interactive/background

10 DlAsCnfC-sSpeechPsStr

CS speech and any PS streaming

T08-Source Type of call release mapping

ID Name Description

0 SrcCallOther Other combinations

1 SrcCallCsSpeech CS Speech

2 SrcCallCsData CS Data

3 SrcCallCsStr CS Streaming

4 SrcCallPsStr16 PS Streaming 16





ID Name Description


8 SrcCallPsIb8 PS I/B 8






14 SrcCallHsdpa HSDPA

T09-Derived AsConf Screening for PS DlAsConfId

ID Name Description


1 DlAsCnfPsStr16 PS Streaming 16




5 DlAsCnfTrbCell-Fach

TRB on cell FACH

6 DlAsCnfPsIB8 PS I/B 8






12 DlAsCnfHsdpa HSDPA

T10-Derived AsConf Screening for CS DlAsConfId

ID Name Description

0 DlAsCnfOther Other


2 DlAsCnfC-sSpeech

CS speech


4 DlAsCnfC-sStr57_6

CS Streaming 57.6

5 DlAsCnfC- CS Streaming 14.4



ID Name Description

sStr14_4

T11-Derived AsConf Screening for DlAsConfId Avg Nbr Estab

ID Name Description

0 DlAsCnfSignalling Signalling Only

1 DlAsCnfC-sSpeech

CS speech













14 DlAsCnfHsdpa HSDPA

T12-Derived AsConf Screening for UlAsConfId Avg Nbr Estab

ID Name Description

0 UlAsCnfSig Signalling Only

1 UlAsCnfC-sSpeech

CS speech

2 UlAsCnfCsData CS data

3 UlAsCnfC-sStr57_6

CS Streaming 57.6

4 UlAsCnfC-sStr14_4

CS Streaming 14.4

5 UlAsCnfPsStr16 PS Streaming 16



8 UlAsCnfPsIB8 PS I/B 8




ID Name Description




13 UlAsCnfHsupa HSUPA

T13-Type of call for dropped last radio link

ID Name Description

0 DlAsCnfOther Other Type of Call

1 DlAsCnfSig SRB (DCH or cell FACH)

2 DlAsCnfC-sSpeech

CS speech



5 DlAsCn-fPsIbPsStr

Any PS I/B or PS Streaming

T14-Target Type of call setup mapping

ID Name Description

0 TgtCallOther Other combinations

1 TgtCallCsSpeech CS Speech

2 TgtCallCsData CS Data

3 TgtCallCsStr CS Streaming

4 TgtCallPsStr16 PS Streaming 16




8 TgtCallPsIb8 PS I/B 8






T16-Target type of call for Radio Bearer Reconfiguration



ID Name Description

0 RbReconfOther Other Type of Call

1 RbReconfSig-nalling

Signalling Only

2 RbReconfC-sSpeech

CS speech

3 RbReconfCsData CS data

4 RbReconfCsStr Any CS Streaming

5 RbReconfPsStr Any PS Streaming

6 RbReconfPsIB Any PS interactive/background

7 RbReconfC-sSpeechPsIB

CS speech and any PS interactive/background

8 RbReconfC-sDataPsIB

CS data and any PS interactive/background

9 RbRecon-fPsStrPsIB

PS Streaming and any PS interactive/background

10 RbReconfC-sSpeechPsStr

CS speech and any PS streaming



7 MIB Appendices

ID SRB Traffic1 Traffic2 Traffic3

0 SRB 3.4 CSD 64

1 NOT USED

2 SRB 3.4 PS I/B 64

3 SRB 3.4

4 SRB 3.4 PS I/B 8

5 SRB 3.4 CS NB AMR

6 SRB 3.4 PS I/B 128

7 SRB 3.4 PS I/B 384

8 SRB 3.4 CS STR 14.4

9 NOT USED

10 SRB 3.4 CS NB AMR PS I/B 64

11 SRB 3.4 PS I/B 32

12 SRB 3.4 PS I/B 256

13 SRB Fach

14 SRB 3.4 CS STR 57.6

15 NOT USED


17 NOT USED


19 SRB Fach PS I/B Fach

20 SRB 13.6

21 SRB 3.4 CSD 64 PS I/B 64


23 SRB 3.4 PS STR 64

24 SRB 3.4 PS STR 64 PS I/B 8

25 SRB 3.4 PS I/B 64 Mux

26 SRB 3.4 CS NB AMR PS I/B 64 Mux

27 SRB 3.4 PS HS-DSCH PS HS-DSCH(Opt)

28 SRB 3.4 PS STR 128

29 SRB 3.4 CSD 64 PS I/B 8


31 SRB 3.4 CS LR AMR









37 SRB 3.4 PS STR 256



40 SRB 3.4 CS NB AMR PS STR 16




44 SRB 3.4 CS NB AMR PS STR 16 PS I/B 8





49 SRB 3.4 CSD 64 PS I/B 32

50 SRB 3.4 CSD 64 PS I/B 128

51 SRB 3.4 CSD 64 PS HS-DSCH

52 SRB 3.4 CS NB AMR PS HS-DSCH PS HS-DSCH(Opt)

53 SRB 3.4 PS STR 16 PS HS-DSCH




57 SRB 3.4 CS NB AMR PS STR 16 PS HS-DSCH




61 D-SRB 3.4

62 D-SRB 13.6

63 D-SRB 3.4 D-12.2

64 D-SRB 3.4 D-MR

65 SRB Fach PS I/B mux Fach




0 SRB 3.4 PS I/B 64

1 NOT USED

2 SRB 3.4

3 SRB 3.4 PS I/B 32

4 SRB 3.4 CSD 64

5 SRB 3.4 CS NB AMR

6 SRB 3.4 CS STR 14.4

7 NOT USED


9 SRB 3.4 PS I/B 8

10 SRB 3.4 PS I/B 128

11 SRB Rach

12 SRB 3.4 CS STR 57.6

13 NOT USED


15 SRB Rach PS I/B Rach

16 SRB 13.6

17 SRB 3.4 CSD 64 PS I/B 64





22 SRB 3.4 PS I/B 384

23 SRB 3.4 E-DCH

24 SRB 3.4 CSD 64 PS I/B 8

25 SRB 3.4 CS LR AMR







32 SRB 3.4 PS STR 128












41 SRB 3.4 CSD 64 PS I/B 32

42 SRB 3.4 CSD 64 PS I/B 128

43 SRB 3.4 CSD 64 PS I/B 384

44 D-SRB 3.4

45 D-SRB 13.6

46 D-SRB 3.4 D-12.2

47 D-SRB 3.4 D-MR

48 SRB 3.4 CSD 64 E-DCH

49 SRB 3.4 CS NB AMR E-DCH

50 SRB 3.4 PS STR 16 E-DCH



53 SRB 3.4 CS NB AMR PS STR 16 E-DCH



56 SRB Rach PS I/B mux Rach

ID Domain BearerType Rate

0 CS Data 64

1 N/A SRB 3,4

2 NOT USED

3 PS I/B 64

4 PS I/B 8

5 CS Speech NB AMR

6 PS I/B 128

7 PS I/B 384

8 CS Stream 14,4

9 PS I/B 32

10 PS I/B 256

11 N/A SRB FACH

12 CS Stream 57,6




13 PS I/B FACH

14 N/A SRB 13,6

15 PS Stream 64

16 PS I/B Mux 64

17 PS I/B HS-DSCH

18 PS Stream 128

19 CS Speech LR AMR

20 PS I/B Mux HS-DSCH

21 PS Stream 16

22 PS Stream 256

23 PS I/B Mux 128

24 PS I/B Mux 384

25 N/A SRB 0,15

26 N/A SRB D-3.4

27 N/A SRB D-13.6

28 CS Speech D-12.2

29 CS Speech D-MR

30 PS I/B mux FACH


0 PS I/B 64

1 N/A SRB 3,4

2 NOT USED

3 PS I/B 32

4 CS Data 64

5 CS Speech NB AMR

6 CS Stream 14,4

7 PS I/B 8

8 PS I/B 128

9 N/A SRB RACH

10 CS Stream 57,6

11 PS I/B RACH

12 N/A SRB 13,6

13 PS Stream 16

14 PS I/B Mux 64

15 PS I/B 384




16 CS Speech LR AMR

17 PS I/B Mux 128

18 PS Stream 32

19 PS Stream 128

20 PS I/B E-DCH

21 N/A SRB 0

22 N/A SRB D-3.4

23 N/A SRB D-13.6

24 CS Speech D-12.2

25 CS Speech D-MR

26 PS I/B mux RACH



8 CNode Counters Index

• #SHO.AttRLAddUTRANSide SHO.AttRLAddUTRANSide

• #SHO.SuccRLAddUTRANSide SHO.SuccRLAddUTRANSide

• #SHO.FailRLAddUTRANSide FAILED RADIO LINK CREATIONS (UTRAN SIDE)

• #SHO.AttRLDelUTRANSide SHO.AttRLDelUTRANSide

• #SHO.SuccRLDelUTRANSide SHO.SuccRLDelUTRANSide

• #IRATHO ATTEMPTED OUTGOING CIRCUIT SWITCHED INTER-RAT HANDOVERS

• #2 VS.RadioLinkSetupUnsuccess

• #4 VS.RadioLinkAdditionUnsuccess

• #5 VS.RadioLinkDeletionSuccess

• #6 VS.RadioLinkDeletionUnsuccess

• #8 VS.RadioLinkReconfigurationPrepareUnsuccess

• #15 VS.RrcSleepyCellInactivity

• #16 VS.RlSleepyCellInactivity

• #17 VS.PagingSleepyCellInactivity

• #18 VS.RadioLinkFailureIndication

• #20 VS.RadioLinkFirstSetupFailure

• #25 VS.UeWithNRadioLinksEstCellsBts

• #26 VS.RadioLinkReconfigurationCancel

• #27 VS.RadioLinkFirstSetupRequest

• #29 VS.RadioLinkSetupSuccess

• #30 VS.RadioLinkAdditionSuccess

• #31 VS.RadioLinkReconfigurationPrepareSuccess

• #32 VS.RadioLinkReconfigurationCommit

• #33 VS.RadioLinkEstablishedPerCell

• #34 VS.RadioLinkDroppedLastRadioLink

• #35 VS.RadioLinkSetupRequest

• #36 VS.RadioLinkAdditionReq

• #37 VS.RadioLinkReconfPrepReq

• #106 VS.RrcCellChangeOrderNeighbRnc

• #108 VS.RrcCellChangeOrderFailureNeighbRnc

• #122 VS.WithoutIurIncomingHardHoAttempt



• #123 VS.WithoutIurIncomingHardHoFailure

• #124 VS.WithoutIurIncomingHardHoSuccess

• #128 VS.InterPlmnOutgoingHardHoAttempt

• #129 VS.InterPlmnOutgoingHardHoFailure

• #131 VS.InterRncWithoutIurOutgoingHardHoAttempt

• #132 VS.InterRncWithoutIurOutgoingHardHoFailure

• #133 VS.InterRncWithoutIurOutgoingHardHoSuccess

• #135 VS.3g2gOutHoFailure

• #142 VS.WithIurOutgoSrnsRelocAttempt

• #143 VS.WithIurOutgoSrnsRelocFail

• #144 VS.WithIurOutgoSrnsRelocSuccess

• #145 VS.WithIurOutgoSrnsRelocSucPrTc

• #146 VS.WithIurOutgoSrnsRelocFailPrTc

• #147 VS.WithIurIncomSrnsRelocAttempt

• #148 VS.WithIurIncomSrnsRelocFail

• #149 VS.WithIurIncomSrnsRelocSuccess

• #150 VS.WithIurIncomSrnsRelocSucPrTc

• #151 VS.WithIurIncomSrnsRelocFailPrTc

• #154 VS.RrcHoFromUtranCmdTrigByEcNo

• #155 VS.RrcHoFromUtranCmdTrigByEcNoNRnc

• #156 VS.RrcHoFromUtranCmdTrigByRscp

• #157 VS.RrcHoFromUtranCmdTrigByRscpNRnc

• #158 VS.RrcHoFromUtranCmdTrigRnc

• #159 VS.RrcHoFromUtranCmdTrigRncNrnc

• #160 VS.RrcHoFromUtranFailure

• #161 VS.RrcHoFromUtranFailureNeighbRnc

• #162 IRATHO.AttOutPSUTRAN

• #163 IRATHO.FailOutPSUTRAN

• #164 VS.3gto2gHoDetectionFromFddcell

• #165 VS.3gto2gHoDetectionFromFddcellNeighbRnc

• #166 VS.InterPlmnOutgoingHardHoSuccess

• #167 VS.3gto2gOutHoSuccess

• #168 VS.3gto2gOutHoSuccessNrnc

• #169 VS.3g2gOutHoFailureNrnc



• #170 VS.IntraRncOutInterFreqHoAttempt

• #171 VS.IntraRncOutInterFreqHoFail

• #172 VS.IntraRncIncInterFreqHoAttempt

• #173 VS.IntraRncIncInterFreqHoFail

• #174 VS.OutGoInterFreqHoAtt

• #175 VS.OutGoInterFreqHoSuc

• #176 VS.IncomInterFreqHoAtt

• #177 VS.IncomInterFreqHoSuc

• #201 VS.UtranSideSofterHOAtt

• #202 VS.UtranSideSofterHOSucc

• #203 VS.UtranSideSofterHOUnsucc

• #204 VS.UtranSideSoftHOAtt

• #205 VS.UtranSideSoftHOSucc

• #206 VS.UtranSideSoftHOUnsucc

• #207 VS.UtranSideDelHOAtt

• #208 VS.UtranSideDelHOSucc

• #209 VS.UeSideHOAtt

• #210 VS.UeSideHOSucc

• #211 VS.UeSideHOUnsucc

• #212 VS.UtranSideIurSoftHOAtt

• #213 VS.UtranSideIurSoftHOSucc

• #214 VS.UtranSideIurSoftHOUnsucc

• #215 VS.UtranSideIurDelSoftHOAtt

• #216 VS.UtranSideIurDelSoftHOSucc

• #301 VS.AveragePowerUsedForSpeech

• #302 VS.AveragePowerUsedForData

• #303 VS.UplinkRssi

• #304 VS.AveragePowerUsedForSignalling

• #305 VS.AveragePowerUsedForMiscellaneous

• #306 VS.IrmcacPowerDist

• #307 VS.DistDlTtlPwrRatio

• #402 VS.RrcActiveSetUpdateUnsuccess

• #403 RRC.SuccConnEstab

• #404 RRC.FailConnEstab



• #405 VS.RrcConnectionRelease

• #407 VS.RrcActiveSetUpdateUnsuccessNeighbRnc

• #408 VS.RrcConnectionReleaseNeighbRnc

• #409 RRC.AttConnEstab

• #412 VS.RrcTransitionCellFachToCellDch

• #413 VS.RrcTransitionCellDchToCellFach

• #414 VS.RrcAvgNbrCellFach

• #415 VS.RrcActiveSetUpdateCompleteProcedure

• #416 VS.RrcConnectionSetup

• #418 SHO

• #419 VS.FirstRrcConnectionRequest

• #420 VS.RrcRel

• #421 VS.ActiveSetUpdatePerRnc

• #422 VS.RrcActiveSetUpdateSuccessNeighbRnc

• #502 VS.IuSccpCnxUnsuccess

• #505 VS.IuReleaseCommandCs

• #505 IRATHO.SuccOutCS

• #506 VS.IuReleaseCommandPs

• #506 RATHO.SuccOutPSUTRAN

• #516 VS.IuReceivedSccpAbnormalDisconnectsCs

• #517 VS.IuEmittedSccpAbnormalDisconnectsPs

• #518 VS.IuReceivedSccpAbnormalDisconnectsPs

• #532 VS.IuEmittedSccpAbnormalDisconnectsCs

• #535 VS.IuRelocationRequests

• #536 VS.IuRelocationRequestFailuresCs

• #537 VS.IuRelocationRequestFailuresPs

• #548 VS.IuSccpCnxSuccess

• #552 VS.IuReleaseCommandCs

• #552 IRATHO.SuccOutCS

• #553 VS.IuReleaseCommandPs

• #553 IRATHO.SuccOutPS

• #556 VS.IuRelocationRequired

• #557 VS.IuRelocationCommands

• #558 VS.IuRelocationCmdFailuresCs



• #559 VS.IuRelocationCommandFailuresPs

• #560 VS.IuAbnormRelReqCsNrnc

• #561 VS.IuAbnormRelReqPsNrnc

• #562 VS.IuReleaseCompleteCsNrnc

• #564 VS.IuReleaseCmdAfterCcConAck

• #565 VS.IuReleaseReqAfterCcConAck

• #566 VS.IuReleaseCmdBeforeCcConAck

• #567 VS.IuReleaseReqBeforeCcConAck

• #568 VS.IuRelocationCancels

• #569 VS.IuRelocationCompletes

• #570 VS.IuRelocationDetects

• #571 VS.IuReleaseCompleteCs

• #572 VS.IuAbnormalReleaseRequestCs

• #573 VS.IuAbnormalReleaseRequestPs

• #574 VS.IubcSabpMsg

• #575 VS.IubcSabpWrtRplcFail

• #576 VS.IuReleaseReqCs

• #577 VS.IuReleaseReqPs

• #578 VS.IuAvgNbrSccpCnxCs

• #579 VS.IuAvgNbrSccpCnxPs

• #580 VS.IuReleaseRequestCsNrnc

• #581 VS.IuReleaseRequestPsNrnc

• #602 VS.RadioBearerSetupUnsuccess

• #609 VS.RadioBearerReleaseUnsuccess

• #611 VS.RadioBearerSetupUnsuccessNeighbRnc

• #612 VS.RadioBearerEstablishmentUnsuccessNeighbRnc

• #614 VS.RadioBearerReleaseUnsuccessNeighbRnc

• #616 VS.RadioBearerReconfigurationUnsuccess

• #618 VS.RadioBearerReconfigurationUnsuccessNeighbRnc

• #631 VS.RadioBearerEstablishmentUnsuccess

• #635 VS.RabAssignmentRequestUeCapabilitiesCheckFailure

• #636 VS.RabAssignmentRequestUeCapabilitiesCheckAccept

• #638 VS.RabrReconfiCompl3Gto3GReloc

• #639 VS.CallEstablishmentDuration



• #640 VS.UEDlRBRateAdapActiv

• #641 VS.UEDlRBRateAdapDeactiv

• #642 VS.UEUlRBRateAdapActiv

• #643 VS.UEUlRBRateAdapDeactiv

• #644 VS.UEDlRBRateAdapDownReq

• #645 VS.UEDlRBRateAdapUpReq

• #646 VS.UEDlRBRateAdapDownSucc

• #647 VS.UEDlRBRateAdapUpSucc

• #648 VS.UEUlRBRateAdapDownReq

• #649 VS.UEUlRBRateAdapUpReq

• #650 VS.UEUlRBRateAdapDownSucc

• #651 VS.UEUlRBRateAdapUpSucc

• #652 VS.UERBRateAdapDownReqCell

• #653 VS.UERBRateAdapUpReqCell

• #654 VS.UERBRateAdapDownSuccCell

• #655 VS.UERBRateAdapUpSuccCell

• #656 VS.UERBRateAdapDownReqNeighbCell

• #657 VS.UERBRateAdapUpReqNeighbCell

• #658 VS.UERBRateAdapDownSuccNeighbCell

• #659 VS.UERBRateAdapUpSuccNeighbCell

• #666 VS.RabModifReq

• #667 VS.RabModifSucc

• #668 VS.CallAttemptsUeCat

• #669 VS.RbEstabUnsucPerDlRbType

• #670 VS.RadioBearerReconfigFailure

• #671 VS.RabEstablishmentRequestsPerRabType

• #672 VS.RabEstablishmentSuccessPerRequestedRabType

• #673 VS.RabEstablishmentSuccessPerGrantedRabType

• #674 VS.RabReleaseRequest

• #675 VS.NumberOfRabEstablished

• #676 VS.RabNormalRelease

• #677 VS.RabAssignmentSetupUnsuccess

• #678 VS.RabAssignmentReleaseSuccess

• #679 VS.RabAssignmentReleaseUnsuccess



• #680 VS.RabOutgoingRefCell

• #681 VS.RabIncomingRefCell

• #682 VS.RabEstabSuccPerReqRabTypRefCell

• #683 VS.RabAbnormRelPerReqRabTypRefCel

• #684 VS.RadioBearerReconfigurationSuccess

• #685 VS.RadioBearerReconfigureRequest

• #686 VS.RadioBearerReconfigurationSuccessNeighbRnc

• #687 VS.RadioBearerSetupSuccess

• #688 VS.RadioBearerReleaseSuccess

• #689 VS.RadioBearerSetupSuccessNeighbRnc

• #690 VS.RadioBearerReleaseSuccessNeighbRnc

• #691 VS.RadioBearerSetupRequest

• #692 VS.DlAsConfIdAvgNbrEstablished

• #693 VS.UlAsConfIdAvgNbrEstablished

• #694 VS.SucEdchToDchTrans

• #695 VS.UnsucEdchToDchTrans

• #696 VS.SucDchToEdchTrans

• #697 VS.UnsucDchToEdchTrans

• #701 VS.SmcSuccess

• #702 VS.RejectedSmc

• #703 VS.FailedRrcSmc

• #801 VS.ReceivedPagingRequest

• #802 VS.ReceivedPagingRequestType2CellDch

• #803 VS.ReceivedPagingRequestType2CellFach

• #805 VS.PagingMessagesSentOnPcch

• #807 VS.PagingCancelledRecords

• #808 VS.PagingRejectedRequests

• #809 VS.PagingDelayedRecords

• #810 VS.UnhandledPagingRequestsCs

• #811 VS.UnhandledPagingRequestsPs

• #812 VS.PagingRecordsSentOnPcchCs

• #813 VS.PagingRecordsSentOnPcchPs

• #814 VS.PagingRecordsUnscheduledCs

• #815 VS.PagingRecordsUnscheduledPs



• #816 VS.PagingRecordsType2SentCs

• #817 VS.PagingRecordsType2SentPs

• #818 VS.PagingRecordsType2PagCauseCs

• #819 VS.PagingRequestsIuPagCauseCs

• #820 VS.UtranPagingRecSentOnPcch

• #901 VS.NbrCellUpdates

• #902 VS.NbrCellUpdateRejects

• #903 VS.CsLocationReportingControlDefaultLs

• #913 VS.CsLocationUebasedAgpsSuccess

• #914 VS.CsLocationUebasedAgpsUnsuccess

• #915 VS.UeLocationUebasedAgpsSuccess

• #916 VS.UeLocationUebasedAgpsSuccessNeighbRnc

• #917 VS.UeLocationUebasedAgpsUnsuccess

• #918 VS.UeLocationUebasedAgpsUnsuccessNeighbRnc

• #919 VS.PsLocationUeBasedAgpsSuccess

• #920 VS.PsLocationUebasedAgpsUnsuccess

• #921 VS.PsLocationReportingControlGeoLs

• #922 VS.PsLocationReportSuccessGeoLsWithinQos

• #923 VS.PsLocationReportSuccessGeoLsOutsideQos

• #924 VS.PsLocationReportUnsuccessGeoLs

• #925 VS.CsLocationReportSuccessGeoLsOutsideQos

• #926 VS.CsLocationReportingControlGeoLs

• #927 VS.PsLocationReportingControlSaLs

• #928 VS.CsLocationReportSuccessSaLs

• #929 VS.CsLocationReportUnsuccessSaLs

• #930 VS.CsLocationReportSuccessGeoLsWithinQoS

• #931 VS.CsLocationReportUnsuccessGeoLs

• #932 VS.PsLocationReportSuccessSaLs

• #933 VS.PsLocationReportUnsuccessSaLs

• #934 VS.RrcAvgNbrCellPch

• #935 VS.RrcAvgNbrUraPch

• #936 VS.RrcAvgNbrCellFachRnc

• #937 VS.NbrUraUpdates

• #938 VS.NbrUraUpdatesRej



• #939 VS.RrcTransCellPchToUraPch

• #940 VS.RrcTransDchToPch

• #950 VS.HsdpaMobilitySuccess

• #951 VS.HsdpaMobilityUnsuccessful

• #952 VS.HsdpaCellDeletion

• #953 VS.HsdpaDCHToHsdpaTransSucc

• #954 VS.HsdpaToDCHSucc

• #955 VS.DCHToHsdpaUnsuccessful

• #956 VS.HsdpaToDCHUnsuccessful

• #957 VS.HsdpaCACSuccess

• #958 VS.HsdpaCACUnsuccessful

• #959 VS.HsdpaIuRelAbnormal

• #960 VS.EdchSucMobility

• #961 VS.EdchUnsucMobility

• #962 VS.EdchCellDeletion

• #963 VS.EdchIuRelAbnormal

• #1002 VS.AvgTxPower

• #1003 VS.CmConfigurationFailure

• #1004 VS.CmActivationSuccess

• #1005 VS.CmActivationFailure

• #1006 VS.CmConfigurationSuccess

• #1011 VS.IntraFreqMeasAverageOfCallPeriodicModeCell

• #1012 VS.IntraFreqMeasAverageOfCallPeriodicModeNeighRnc

• #1013 VS.IntraFreqMeasAverageOfCallEventModeCell

• #1014 VS.IntraFreqMeasAverageOfCallEventModeNeighRnc

• #1016 VS.MeasurementControlCellListSize

• #1017 VS.MeasEvent1ACell

• #1018 VS.MeasEvent1BCell

• #1019 VS.MeasEvent1CCell

• #1020 VS.MeasEvent1DCell

• #1021 VS.MeasEvent1ECell

• #1022 VS.MeasEvent1FCell

• #1023 VS.MeasEvent2DCell

• #1024 VS.MeasEvent2FCell



• #1027 VS.MeasCallFailTraceDetectCell

• #1029 VS.MeasEvent1BNeighRNC

• #1030 VS.MeasEvent1CNeighRNC

• #1031 VS.MeasEvent1DNeighRNC

• #1032 VS.MeasEvent1ENeighRNC

• #1033 VS.MeasEvent1FNeighRNC

• #1034 VS.MeasEvent2DNeighRNC

• #1035 VS.MeasEvent2FNeighRNC

• #1038 VS.MeasCallFailTraceDetectNeighRNC

• #1039 VS.MeasurementControlFailure

• #1041 VS.DistPropDelayPerRange

• #1042 VS.DistRssi

• #1043 VS.IrmcacDistributionEcN0

• #1111 VS.IrmcacMaintainedHighPriority

• #1112 VS.IrmcacDowngradedHighPriority

• #1113 VS.IrmcacRejectedHighPriority

• #1114 VS.IrmcacMaintainedMediumPriority

• #1115 VS.IrmcacDowngradedMediumPriority

• #1116 VS.IrmcacRejectedMediumPriority

• #1117 VS.IrmcacMaintainedLowPriority

• #1118 VS.IrmcacDowngradedLowPriority

• #1119 VS.IrmcacRejectedLowPriority

• #1124 VS.IRMTimeCellRadioColorRed

• #1125 VS.IRMTimeCellRadioColorYellow

• #1126 VS.IRMTimeFreeDlCodesBySpreadingFactor

• #1129 VS.IrmcacRadioLinkColorRed

• #1130 VS.IrmcacRadioLinkColorGreen

• #1131 VS.IrmUpgradingActivation

• #1132 VS.IrmUpgradingActivationDelayed

• #1134 VS.IrmUpgradingDeactivation

• #1136 VS.IrmPreemptionTimeCellColorCongested

• #1137 VS.IrmPreemptionTimeCellColorCongestedBecauseOfOvsfCodes

• #1138 VS.IrmPreemptionTimeCellColorCongestedBecauseOfPower

• #1139 VS.IrmPreemptionRbHighPriorityDowngraded



• #1140 VS.IrmPreemptionRbHighPriorityRejected

• #1141 VS.IrmPreemptionRbMediumPriorityDowngraded

• #1142 VS.IrmPreemptionRbMediumPriorityRejected

• #1143 VS.IrmPreemptionRbLowPriorityDowngraded

• #1144 VS.IrmPreemptionRbLowPriorityRejected

• #1157 VS.RrcNwkTransPchToFachOrDch

• #1158 VS.IrmcacDistributionRscp

• #1159 VS.DownsizingStep1Success

• #1160 VS.DownsizingStep1SuccessNeighbRnc

• #1161 VS.DownsizingStep1Unsuccess

• #1162 VS.DownsizingStep1UnsuccessNeighbRnc

• #1163 VS.DownsizingStep2Success

• #1164 VS.DownsizingStep2SuccessNeighbRnc

• #1165 VS.UpsizingSuccess

• #1166 VS.UpsizingSuccessNeighbRnc

• #1167 VS.UpsizingUnsuccess

• #1168 VS.UpsizingUnsuccessNeighbRnc

• #1169 VS.IRMSchedulingDowngradedSuccess

• #1170 VS.IRMSchedulingDowngradedFailure

• #1171 VS.IRMSchedulingDowngradedSuccessNeighbRnc

• #1172 VS.IRMSchedulingDowngradedFailureNeighbRnc

• #1173 VS.IrmUpgradingSuccessful

• #1174 VS.IrmUpgradingCommand

• #1175 VS.IrmUpgradingCommandNrnc

• #1176 VS.IrmUpgradingSuccessfulNrnc

• #1177 VS.QosDlCemLdClrYellow

• #1178 VS.QosDlCemLdClrRed

• #1179 VS.QosDlCemLdCellPreemptClrCngstd

• #1180 VS.QosUlCemLdClrYellow

• #1181 VS.QosUlCemLdClrRed

• #1182 VS.IrmTimeDlIubTransportColorRed

• #1183 VS.IrmTimeDlIubTransportColorYellow

• #1184 VS.UlIrmcacMaintainedGold

• #1185 VS.UlIrmcacMaintainedSilver



• #1186 VS.UlIrmcacMaintainedBronze

• #1187 VS.UlIrmcacDowngradedGold

• #1188 VS.UlIrmcacDowngradedSilver

• #1189 VS.UlIrmcacDowngradedBronze

• #1190 VS.UlIrmcacRejectedGold

• #1191 VS.UlIrmcacRejectedSilver

• #1192 VS.UlIrmcacRejectedBronze

• #1193 VS.IRMTimeULRadioLoadColorYellow

• #1194 VS.IRMTimeULRadioLoadColorRed

• #1195 VS.HsPdschDynCodeMgmtStealing

• #1196 VS.HsPdschDynCodeMgmtRealloc

• #1197 VS.NumHsPdschCodes

• #1213 VS.CommonMacDownlinkPcchSdu

• #1214 VS.CommonMacDownlinkCcchSdu

• #1215 VS.CommonMacDownlinkDcchOverFachSdu

• #1216 VS.CommonMacDownlinkDtchOverFachSdu

• #1217 VS.CommonMacUplinkCcchSdu

• #1218 VS.CommonMacUplinkDcchOverRachSdu

• #1219 VS.CommonMacUplinkDtchOverRachSdu

• #1220 VS.CommonRlcCcchDownlinkKbytes

• #1221 VS.CommonRlcCcchDownlinkSdu

• #1222 VS.CommonRlcCcchDiscardSdu

• #1223 VS.CommonRlcCcchPadding

• #1224 VS.CommonUplinkTrafficChnlSyncFrames

• #1225 VS.CommonUplinkTimingAdjustmentFrames

• #1302 VS.IurDrncRadioLinkSetupUnsuccess

• #1304 VS.IurDrncRadioLinkAdditionUnsuccess

• #1306 VS.IurDrncRadioLinkDeletionSuccess

• #1308 VS.IurDrncRadioLinkReconfigurationPrepareUnsuccess

• #1311 VS.IurSccpCnxSuccess

• #1312 VS.IurSccpCnxUnsuccess

• #1315 VS.IurAvgNbrInitSccpCnx

• #1316 VS.IurAvgNbrTermSccpCnx

• #1317 VS.IurEmittedSccpAbnormalDisconnects



• #1318 VS.IurReceivedSccpAbnormalDisconnects

• #1319 VS.IurDrncRadioLinkReconfigurationCancel

• #1320 VS.IurDrncRadioLinkSetupSuccess

• #1321 VS.IurDrncRadioLinkAdditionSuccess

• #1322 VS.IurDrncRadioLinkReconfigurationPrepareSuccess

• #1323 VS.IurDrncRadioLinkReconfigurationCommit

• #1324 VS.IurSrncRelocCommit

• #1325 VS.IurDrncRelocCommit

• #1437 VS.IuCsTimingAdjustmentRequests

• #1438 VS.IuCsTimingAdjustmentAcks

• #1439 VS.IuCsTimingAdjustmentNacks

• #1440 VS.IuCsTimingAdjustmentUnsupported

• #1441 VS.IuCsTimingAdjustmentTimeouts

• #1470 VS.HsdpaIubFPDiscardedBytes

• #1471 VS.DedicatedUplinkBadPdusRlcRefCell

• #1472 VS.DedicatedUplinkKbytesRlc

• #1473 VS.DedicatedDownlinkKbytesRlc

• #1474 VS.DedicatedUplinkPduRlc

• #1475 VS.DedicatedDownlinkPduRlc

• #1476 VS.DedicatedUplinkSduRlc

• #1477 VS.DedicatedDownlinkSduRlc

• #1478 VS.DedicatedUplinkMissingPduRlc

• #1479 VS.DedicatedDownlinkDiscardSduRlc

• #1480 VS.DedicatedDownlinkPaddingSduRlc

• #1481 VS.DedicatedUplinkBadPdus

• #1484 VS.DedicatedUplinkKbytesRlcActiveCells

• #1485 VS.DedicatedDownlinkKbytesRlcActiveCells

• #1486 VS.DedicatedUplinkKbytesRlcReferenceCell

• #1487 VS.DedicatedDownlinkKbytesRlcReferenceCell

• #1488 VS.DedicatedUplinkPdusRlcReferenceCell

• #1489 VS.DedicatedDownlinkPdusRlcReferenceCell

• #1490 VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell

• #1491 VS.RlcUnrecoverableError

• #1492 VS.DlDiscardNonConfTraffic



• #1493 VS.UlDiscardNonConfTraffic

• #1494 VS.EdchIubTnlCongestIndc

• #1495 VS.EdchMacTsnReassemblyErr

• #1496 VS.EdchFpRetransHarq

• #1497 VS.BmcCtchTrafVol

• #1502 VS.HsdschIubUlXoFrmCnt

• #1503 VS.HsdschIubDlTrfcBlkTmCnt

• #1504 VS.DchIubDlTrfcBlkTmCnt

• #1505 VS.IuDlAmrFrmFqc

• #1506 VS.DdUlAmrABtGoodFrm

• #1507 VS.DdUlAmrABtBadFrm

• #1508 VS.HsdpaIubDlControlFrames

• #1509 VS.HsdpaIubNonZeroCapacityAlloc

• #1510 VS.HsdpaIubZeroCapacityAlloc

• #1511 VS.HsdpaIubCreditsRequested

• #1512 VS.HsdpaIubCreditsConsumed

• #1513 VS.AmrClDlRt

• #1514 VS.AmrClUlRt

• #1515 VS.DlAmrRtChg

• #1516 VS.IuRcvdAmrRtCtrl

• #1521 VS.OvinCnAccLaDscrd

• #1522 VS.OvinNiDscrd

• #1523 VS.OvinRabRrcConReqDscrd

• #1524 VS.DedicatedUplinkSduRlcRefCell

• #1525 VS.DedicatedDownlinkSduRlcRefCell

• #1526 VS.DedicatedDownlinkActivityRlcRefCell

• #1527 VS.DedicatedUplinkActivityRlcRefCell

• #1528 VS.IrmcacDistIubLoad

• #1529 VS.DedicatedUplinkBadPdusRlcReferenceCell

• #1601 VS.SucHspaToDchFallbackCell

• #1602 VS.SucHspaToDchFallbackNrnc

• #1603 VS.UnsucHspaToDchFallbackCell

• #1604 VS.UnsucHspaToDchFallbackNrnc

• #2001 VS.RRCAtt



• #2002 VS.CallAttNorMoCs

• #2003 VS.CallAttNorMoPs

• #2004 VS.CallAttNorMtCs

• #2005 VS.CallAttNorMtPs

• #2006 VS.CallAttMulMoCs

• #2007 VS.CallAttMulMoPs

• #2008 VS.CallAttMulMtCs

• #2009 VS.CallAttMulMtPs

• #2010 VS.RabAttNorMoCs

• #2011 VS.RabAttNorMoPs

• #2012 VS.RabAttNorMtCs

• #2013 VS.RabAttNorMtPs

• #2014 VS.RabAttMulMoCs

• #2015 VS.RabAttMulMoPs

• #2016 VS.RabAttMulMtCs

• #2017 VS.RabAttMulMtPs

• #2018 VS.RabRspNorMoCs

• #2019 VS.RabRspNorMoPs

• #2020 VS.RabRspNorMtCs

• #2021 VS.RabRspNorMtPs

• #2022 VS.RabRspMulMoCs

• #2023 VS.RabRspMulMoPs

• #2024 VS.RabRspMulMtCs

• #2025 VS.RabRspMulMtPs

• #2026 VS.CallAnswNorMoCs

• #2027 VS.CallAnswNorMoPs

• #2028 VS.CallAnswNorMtCs

• #2029 VS.CallAnswNorMtPs

• #2030 VS.CallAnswMulMoCs

• #2031 VS.CallAnswMulMoPs

• #2032 VS.CallAnswMulMtCs

• #2033 VS.CallAnswMulMtPs

• #2034 VS.FailState1NorMo

• #2035 VS.FailNotState1NorMoCs



• #2036 VS.FailNotState1NorMoPs

• #2037 VS.FailState1NorMt

• #2038 VS.FailNotState1NorMtCs

• #2039 VS.FailNotState1NorMtPs

• #2040 VS.FailNotState1MulMoCs

• #2041 VS.FailNotState1MulMoPs

• #2042 VS.FailNotState1MulMtCs

• #2043 VS.FailNotState1MulMtPs

• #2044 VS.LocRegRRCAtt

• #2045 VS.LocRegCallAtt

• #2046 VS.LocRegCallAnsw

• #2047 VS.LocRegFail

• #2049 VS.PagingRsp

• #2050 VS.CsMoState2Failure

• #2051 VS.PsMoState2Failure





• #2056 VS.CsMtState2Failure

• #2057 VS.PsMtState2Failure





• #2062 VS.LocalRegState1Failure

• #2063 VS.CsLocalRegState2Failure

• #2064 VS.PsLocalRegState2Failure

• #2065 VS.CsMoCallAvgHoldingTime

• #2066 VS.PsMoCallAvgHoldingTime

• #2067 VS.CsMtCallAvgHoldingTime

• #2068 VS.PsMtCallAvgHoldingTime

• #2069 VS.CsMoRabCallAvgSetupTime

• #2070 VS.PsMoRabCallAvgSetupTime



• #2071 VS.CsMtRabCallAvgSetupTime

• #2072 VS.PsMtRabCallAvgSetupTime

• #2101 VS.RRCCdmaHOFromUtranCmd

• #2102 VS.RRCCdmaHOFromUtranFail

• #2103 VS.RRCCdmaHOFromUtranComp

• #2104 VS.RRCCdmaHOPrepAtt

• #2105 VS.RRCCdmaHOPrepFail

• #2106 VS.RRCCdmaHOPrePSucc

• #3002 VS.RncCallCleanup



Wireless Service Provider SolutionsUMTSPerformance ManagementUMTS Access Network Performance Reference Observation Counters - Volume 1: RNC Counters

Copyright © 2003-2007 Alcatel-Lucent, All Rights Reserved

ALCATEL-LUCENT CONFIDENTIAL

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is "write protected"; it may be alteredonly by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures accessto the current issue. Any hardcopies taken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except asexpressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose theinformation only to its employees with a need to know, and shall protect the information from disclosure and dissemination to thirdparties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information containedherein. If you have received this document in error, please notify the sender and destroy it immediately.

Document number: NN-20500-028Document issue: 07.03Document status: StandardProduct Release: UMTS 5.1Date: July 2007

Design

Counters volume 1 - rnc counters nn-20500-028 p1-07 03_standard_july_2007