BSC Performance Counter Reference

ZXG10 iBSC
Base Station Controller
Performance Counter Reference

Version : 6.20.61
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revison No.
Revision Date
Revision Reason
R1.4
20120113
Add C901130073C901130085
R1.3
20110730
Updated to V6.20.614d
R1.2
20110310
Updated to V6.20.614c
R1.1
20101010
Updated to V6.20.614
R1.0
20100720
First edition
Serial Number: SJ-20100524164252-015
Content
About This Manual............................................. I

PS Basic Measurement (BSC) ............................1
Overview....................................................................... 1
C900030001 Number of bytes received from data link ......... 1
C900030002 Number of bytes sent to data link ................. 1
PS Basic Measurement (Cell).............................3

Overview......................................................................10
C900040001 Number of GPRS DL TBF establishment
success on PACCH .................................................11
C900040002 Number of GPRS DL TBF release due to
N3105 overflow .....................................................12
other reasons........................................................13
C900040004 Number of GPRS DL TBF forcing release by
control plane.........................................................14
instance suspension ...............................................15
inner abnormal......................................................15
C900040007 Number of GPRS DL signaling TBF
establishment .......................................................16
C900040008 Number of GPRS DL data TBF
establishment .......................................................16
C900040009 Number of EGPRS DL TBF establishment
success on PACCH .................................................17
C900040010 Number of EGPRS DL TBF release due to
N3105 overflow .....................................................18
other reasons........................................................19
C900040012 Number of EGPRS DL TBF forcing release by
control plane.........................................................20
Confidential and Proprietary Information of ZTE CORPORATION
ZXG10 iBSC Performance Counter Reference

inner abnormal......................................................21
C900040015 Number of EGPRS DL signaling TBF
establishment .......................................................22
C900040016 Number of EGPRS DL data TBF
establishment .......................................................22
C900040017 Average number of GPRS DL TBF
simultaneous establishment ...................................23
C900040018 Average number of EGPRS DL TBF
C900040019 Number of GPRS UL data TBF establishment
success on PACCH .................................................23
C900040020 Number of GPRS UL TBF release due to
N3101 overflow .....................................................24
N3103 overflow .....................................................25
C900040022 Number of GPRS UL TBF forcing release by
control plane.........................................................25
C900040024 Number of GPRS UL TBF release due to inner
abnormal..............................................................26
C900040025 Number of GPRS UL signaling TBF
establishment .......................................................27
C900040026 Number of GPRS UL data TBF
establishment .......................................................29
C900040027 Number of EGPRS UL TBF establishment
success on PACCH .................................................30
C900040028 Number of EGPRS UL TBF release due to
N3101 overflow .....................................................31
N3103 overflow .....................................................31
C900040030 Number of EGPRS UL TBF forcing release by
control plane.........................................................32
inner abnormal......................................................33
II
C900040033 Number of EGPRS UL signaling TBF

establishment .......................................................33
C900040034 Number of EGPRS UL data TBF
establishment .......................................................33
C900040035 Average number of GPRS UL TBF
C900040036 Average number of EGPRS UL TBF
C900040037 Number of GPRS UL signaling TBF release
due to N3101 overflow ...........................................35
due to N3103 overflow ...........................................35
C900040039 Number of GPRS UL signaling TBF forcing
release by control plane .........................................36
due to instance suspension .....................................36
due to inner abnormal ............................................36
C900040042 Number of EGPRS UL signaling TBF release
due to N3101 overflow ...........................................37
due to N3103 overflow ...........................................37
C900040044 Number of EGPRS UL signaling TBF forcing
release by control plane .........................................38
due to instance suspension .....................................38
due to inner abnormal ............................................38
C900040047 Number of EGPRS DL LLC frames ..................39
C900040048 Number of discarded EGPRS DL LLC frames
due to buffer overflow ............................................39
due to life time expiration .......................................40
due to other reasons .............................................41
C900040051 Number of DL signaling LLC frames ...............41
C900040052 Number of discarded EGPRS DL signaling
LLC frames due to buffer overflow............................42
LLC frames due to life time expiration.......................43
III

LLC frames due to other reasons .............................43
C900040055 Number of data blocks transmitted according
to given Abis bandwidth .........................................44
C900040056 Bytes of effective upper layer protocol data
sent on DL PDCH ..................................................44
C900040057 Bytes of effective upper layer protocol data
received on UL PDCH ............................................45
C900040058 Bytes of LLC frame on GPRS UL data TBF
...........................................................................46
C900040059 Duration of GPRS UL data TBF ......................46
C900040060 Bytes of LLC frame on GPRS DL data TBF
...........................................................................48
C900040061 Duration of GPRS DL data TBF ......................48
C900040062 Number of effective data blocks received on
GPRS UL TBF ........................................................49
C900040063 Number of NACK blocks received on GPRS
UL TBF ................................................................50
C900040064 Number of effective data blocks sent on
GPRS DL TBF .......................................................51
C900040065 Number of NACK blocks sent on GPRS DL
TBF ....................................................................51
C900040066 Bytes of LLC frame on EGPRS UL data TBF
...........................................................................52
C900040067 Duration of EGPRS UL data TBF ....................53
C900040068 Bytes of LLC frame on EGPRS DL data TBF
...........................................................................54
C900040069 Duration of EGPRS DL data TBF ....................55
EGPRS UL TBF.......................................................56
C900040071 Number of NACK blocks received on EGPRS
UL TBF ................................................................57
C900040072 Number of effective data blocks sent on
EGPRS DL TBF ......................................................58
C900040073 Number of NACK blocks sent on EGPRS DL
TBF ....................................................................58
C900040074 Number of GPRS DL LLC frames ....................59
C900040075 Number of discarded GPRS DL LLC frames
due to buffer overflow ............................................60
IV

due to life time expiration .......................................61
due to other reasons ..............................................61
C900040078 Number of DL dummy control blocks on
PACCH .................................................................62
C900040079 Number of UL dummy control blocks on
PACCH .................................................................63
C900040080 Number of DL RLC blocks on PACCH
(excluding dummy block) .......................................63
C900040081 Number of DL RLC pending blocks in CS1 on
PDTCH .................................................................64
PDTCH .................................................................65
PDTCH .................................................................65
PDTCH .................................................................66
C900040085 Number of DL RLC NACK blocks in CS1 on
PDTCH .................................................................67
PDTCH .................................................................67
PDTCH .................................................................68
PDTCH .................................................................69
C900040089 Number of DL RLC new blocks in CS1 on
PDTCH .................................................................70
PDTCH .................................................................70
PDTCH .................................................................71
PDTCH .................................................................72
C900040093 Number of UL RLC blocks excluding dummy
blocks on PACCH ...................................................72
C900040094 Number of UL RLC pending blocks in CS1 on
PDTCH .................................................................73
PDTCH .................................................................74

PDTCH .................................................................74
PDTCH .................................................................75
C900040098 Number of UL RLC NACK blocks in CS1 on
PDTCH .................................................................76
PDTCH .................................................................76
PDTCH .................................................................77
PDTCH .................................................................78
C900040102 Number of UL RLC new blocks in CS1 on
PDTCH .................................................................79
PDTCH .................................................................79
PDTCH .................................................................80
PDTCH .................................................................81
C900040106 Number of UL data blocks received on
PDTCH .................................................................81
C900040107 Number of DL data blocks sent on
PDTCH .................................................................82
requests ..............................................................82
failure due to database allocation failure ...................83
C900040110 Number of GPRS DL TBF resource
reallocation requests due to UL TBF establishment
...........................................................................84
reallocation failure of channel allocation due to UL
TBF establishment ................................................85
reallocation requests due to LLC transmission............86
reallocation failure of channel allocation due to LLC
transmission ........................................................86
VI

requests ..............................................................87
C900040116 Number of EGPRS DL TBF resource
reallocation requests due to UL TBF establishment
...........................................................................89
reallocation failure of channel allocation due to UL
TBF establishment ................................................90
transmission ........................................................91
C900040120 Number of GPRS UL TBF establishment
requests ..............................................................92
C900040122 Number of GPRS UL TBF resource reallocation
requests due to DL TBF establishment ......................94
C900040123 Number of GPRS UL TBF resource
reallocation failure of channel allocation due to DL
TBF establishment .................................................95
transmission .........................................................96
reallocation requests for resource request .................97
reallocation failure due to database allocation failure
for resource request...............................................98
requests...............................................................99
VII
C900040130 Number of EGPRS UL TBF resource

reallocation requests due to DL TBF
establishment ..................................................... 100
reallocation failure of channel allocation due to DL
TBF establishment ............................................... 101
reallocation requests due to LLC transmission.......... 102
transmission ....................................................... 102
reallocation requests for resource request ............... 103
reallocation failure due to database allocation failure
for resource request............................................. 104
C900040136 Average number of available PDCH.............. 105
C900040137 Number of forcing conversation dynamic
from PDCH to TCH by BSC .................................... 105
C900040138 Number of PDCH used by TBF in each
cell .................................................................... 105
C900040139 Maximum number of used PDCH ................. 106
C900040140 Average number of used PDCH ................... 106
requests before T3192 expiration........................... 107
using existing DL TBF resource .............................. 108
requests on PACCH .............................................. 108
requests on CCCH/PCCCH ..................................... 109
requests before T3192 expiration........................... 110
using existing DL TBF resource .............................. 111
VIII
C900040149 Number of GPRS DL signaling TBF release

due to N3105 overflow ......................................... 114
due to other reasons ............................................ 115
C900040151 Number of GPRS DL signaling TBF forcing
release by control plane ....................................... 115
due to instance suspension ................................... 116
due to inner abnormal .......................................... 117
C900040154 Number of EGPRS DL signaling TBF release
due to N3105 overflow ......................................... 118
due to other reasons ............................................ 119
C900040156 Number of EGPRS DL signaling TBF forcing
release by control plane ....................................... 120
due to instance suspension ................................... 120
due to inner abnormal .......................................... 121
C900040159 Number of GPRS UL TBF establishments in
release state ....................................................... 122
C900040160 Number of GPRS UL TBF establishment with
existing UL resource ............................................ 123
establishments on PACCH ..................................... 124
C900040163 Number of EGPRS UL TBF establishments in
release state ....................................................... 125
with existing UL resource...................................... 126
C900040167 Number of dynamic PDCH preemption for
CS service .......................................................... 128
IX

C900040172 Number of DL RLC pending blocks in MCS1
on PDTCH ........................................................... 130
on PDTCH ........................................................... 131
on PDTCH ........................................................... 132
on PDTCH ........................................................... 133
on PDTCH ........................................................... 133
on PDTCH ........................................................... 134
on PDTCH ........................................................... 135
on PDTCH ........................................................... 135
on PDTCH ........................................................... 136
C900040181 Number of DL RLC NACK blocks in MCS1 on
PDTCH ............................................................... 137
PDTCH ............................................................... 138
PDTCH ............................................................... 138
PDTCH ............................................................... 139
PDTCH ............................................................... 140
PDTCH ............................................................... 140
PDTCH ............................................................... 141
PDTCH ............................................................... 142

PDTCH ............................................................... 143
C900040190 Number of DL RLC new blocks in MCS1 on
PDTCH ............................................................... 143
PDTCH ............................................................... 144
PDTCH ............................................................... 145
PDTCH ............................................................... 145
PDTCH ............................................................... 146
PDTCH ............................................................... 147
PDTCH ............................................................... 148
PDTCH ............................................................... 148
PDTCH ............................................................... 149
C900040199 Number of UL RLC pending blocks in MCS1
on PDTCH ........................................................... 150
on PDTCH ........................................................... 150
on PDTCH ........................................................... 151
on PDTCH ........................................................... 152
on PDTCH ........................................................... 153
on PDTCH ........................................................... 153
on PDTCH ........................................................... 154
on PDTCH ........................................................... 155
on PDTCH ........................................................... 155
C900040208 Number of UL RLC NACK blocks in MCS1 on
PDTCH ............................................................... 156
XI

PDTCH ............................................................... 157
PDTCH ............................................................... 158
PDTCH ............................................................... 158
PDTCH ............................................................... 159
PDTCH ............................................................... 160
PDTCH ............................................................... 160
PDTCH ............................................................... 161
PDTCH ............................................................... 162
C900040217 Number of UL RLC new blocks in MCS1 on
PDTCH ............................................................... 163
PDTCH ............................................................... 163
PDTCH ............................................................... 164
PDTCH ............................................................... 165
PDTCH ............................................................... 165
PDTCH ............................................................... 166
PDTCH ............................................................... 167
PDTCH ............................................................... 168
PDTCH ............................................................... 168
C900040232 Accumulated throughput of UL GPRS
TBF ................................................................... 169
C900040233 Accumulated throughput of DL GPRS
TBF ................................................................... 170
C900040234 Accumulated throughput of UL EGPRS
TBF ................................................................... 170
XII
C900040235 Accumulated throughput of DL EGPRS

TBF ................................................................... 171
CPU Load Measurement................................. 173

Overview.................................................................... 173
C900050001 Average load of the processor..................... 173
C900050002 Peak value of the processor load ................. 173
CS Basic Measurement .................................. 175

Overview.................................................................... 182
C900060001 Number of MTC access attempts ................. 183
C900060002 Number of MTC access success ................... 183
C900060003 Number of SDCCH seizure attempts for
assignment......................................................... 184
C900060004 Number of SDCCH seizure success for
assignment......................................................... 185
C900060005 Number of SDCCH seizure failure for
assignment......................................................... 186
C900060006 Number of SDCCH seizure attempts for
handover............................................................ 187
C900060007 Number of SDCCH seizure failure for
handover............................................................ 189
C900060008 Number of SDCCH allocation success for
assignment......................................................... 190
C900060009 Number of SDCCH allocation failure for
assignment......................................................... 191
C900060010 Number of signaling TCH/F seizure attempts
for assignment .................................................... 192
C900060011 Number of signaling TCH/F seizure failure
for assignment .................................................... 193
C900060012 Number of signaling TCH/F seizure attempts
for handover ....................................................... 194
for handover ....................................................... 197
C900060014 Number of signaling TCH/F allocation
success for assignment ........................................ 198
C900060015 Number of signaling TCH/F allocation failure
for assignment .................................................... 198
C900060016 Number of signaling TCH/F allocation failure
for handover ....................................................... 199
C900060017 Number of signaling TCH/F assignment
success for assignment ........................................ 200
XIII

failure for assignment .......................................... 201
C900060019 Number of voice TCH/F seizure attempts for
assignment......................................................... 202
C900060020 Number of voice TCH/F seizure failure for
assignment......................................................... 204
handover............................................................ 205
handover............................................................ 208
C900060023 Number of TCH/F allocation success for
assignment (speech version1) ............................... 209
C900060024 Number of TCH/F allocation failure due to
channel activation failure for assignment (speech
version1)............................................................ 210
version3)............................................................ 214
C900060028 Number of voice TCH/F assignment
success .............................................................. 215
C900060029 Number of voice TCH/F assignment failure
for assignment .................................................... 216
C900060030 Number of data TCH/F seizure attempts for
assignment......................................................... 217
C900060031 Number of data TCH/F seizure failure for
assignment......................................................... 219
C900060032 Number of data TCH/F seizure attempts for
handover............................................................ 220
handover............................................................ 223
C900060034 Number of data TCH/F allocation success for
assignment......................................................... 224
C900060035 Number of data TCH/F allocation failure due
to channel activation failure for assignment............. 225
C900060036 Number of data TCH/F assignment
success .............................................................. 226
XIV

failure ................................................................ 227
C900060038 Number of signaling TCH/H seizure attempts
for assignment .................................................... 228
C900060039 Number of signaling TCH/H seizure failure
for assignment .................................................... 229
C900060040 Number of signaling TCH/H seizure attempts
for handover ....................................................... 230
C900060041 Number of signaling TCH/H seizure failure
for handover ....................................................... 233
C900060042 Number of voice TCH/H seizure attempts for
assignment......................................................... 234
C900060043 Number of voice TCH/H seizure failure for
assignment......................................................... 236
handover............................................................ 237
handover............................................................ 240
C900060046 Number of data TCH/H seizure attempts for
assignment......................................................... 241
C900060047 Number of data TCH/H seizure failure for
assignment......................................................... 243
C900060048 Number of data TCH/H seizure attempts for
handover............................................................ 244
handover............................................................ 247
C900060050 Number of SAPI3 link establishment
requests on SDCCH (MO-SM) ................................ 248
requests on SDCCH (MT-SM)................................. 250
C900060052 Number of SDCCH drops due to handover
failure ................................................................ 251
C900060053 Number of SDCCH drops ............................ 253
C900060054 Number of TCH/F drops ............................. 254
C900060055 Number of TCH/H drops............................. 254
C900060056 Average number of idle TCH/F with
interference band 1 ............................................. 255
XV

C900060061 Average number of idle TCH/H with
C900060066 Number of samples with UL RQ = 0 ............. 259
C900060074 Number of samples with DL RQ = 0............. 262
C900060082 Number of TCH/F handover attempts due to
UL strength ........................................................ 264
DL strength ........................................................ 265
UL quality ........................................................... 266
DL quality........................................................... 266
XVI

UL interference ................................................... 267
DL interference ................................................... 268
good C/I............................................................. 268
bad C/I .............................................................. 269
PBGT ................................................................. 270
large TA ............................................................. 270
other reasons...................................................... 271
C900060093 Number of BSC-controlled inter-cell outgoing
handover............................................................ 272
handover success ................................................ 273
C900060095 Number of MSC-controlled outgoing
handover............................................................ 273
C900060097 Number of BSC-controlled inter-cell
incoming handover .............................................. 275
incoming handover success................................... 276
C900060099 Number of MSC-controlled incoming
handover............................................................ 276
handover due to forced release ............................. 277
handover due to queue ........................................ 278
C900060103 Number of incoming handover
from undefined layer (GSM900) to current
layer(GSM1800) .................................................. 280
C900060104 Number of incoming handover success
from undefined layer(GSM900) to current layer
(GSM1800) ......................................................... 281
XVII
C900060105 Number of incoming handover from

undefined layer (GSM1800) to current layer
(GSM900)........................................................... 282
C900060106 Number of incoming handover success
from undefined layer(GSM1800) to current
layer(GSM900).................................................... 283
C900060107 Number of incoming handover from the
same layer GSM900 to GSM1800 ........................... 284
C900060108 Number of incoming handover success from
the same layer GSM900 to GSM1800 ..................... 284
C900060109 Number of incoming handover from GSM900
to GSM1800 from the upper layer .......................... 285
GSM900 to GSM1800 in the upper layer ................. 286
to GSM1800 in the lower layer .............................. 287
GSM900 to GSM1800 in the lower layer .................. 288
GSM1800 to GSM900 from the same layer .............. 289
GSM1800 to GSM900 from the upper layer ............. 291
GSM1800 to GSM900 from the lower layer .............. 293
C900060119 Number of Intra-cell handover .................... 294
C900060120 Number of Intra-cell handover success ......... 295
C900060121 Maximum number of busy TCH/H ................ 296
C900060122 Average number of available SDCCH............ 297
C900060123 Average number of unavailable SDCCH ......... 297
C900060124 SDCCH busy time ..................................... 298
C900060125 Average number of available radio
channel .............................................................. 299
C900060126 Average number of unavailable radio
channel .............................................................. 300
XVIII
C900060127 TCH/H busy time ...................................... 300

C900060128 Maximum number of busy TCH/F ................ 301
C900060129 TCH/F busy time ....................................... 302
C900060130 Number of healthy TRXs ............................ 303
C900060131 Number of CM service requests of MOC ......... 304
C900060132 Number of SAPI3 link establishment success
on SDCCH (MT-SM) ............................................. 305
C900060133 Number of available defined SDCCH ............ 306
C900060134 Number of available defined TCH/F.............. 306
C900060135 Number of signaling TCH/H assignment
failure ................................................................ 307
C900060136 Number of MOC access attempts................. 308
C900060137 Number of wireless access due to paging
responses........................................................... 309
C900060138 Number of TCH/F allocation failure due
to BTS connection failure for assignment (speech
version1)............................................................ 310
to BIU connection failure for assignment (speech
version1)............................................................ 311
TCU connection failure for assignment (speech
version1)............................................................ 312
version2)............................................................ 313
version2)............................................................ 314
version2)............................................................ 315
version2)............................................................ 316
version3)............................................................ 317
XIX

version3)............................................................ 318
version3)............................................................ 319
to BTS connection failure for assignment) ............... 320
to BIU connection failure for assignment................. 320
to TCU connection failure for assignment ................ 321
C900060151 Number of voice TCH/H drops due to
handover failure .................................................. 322
C900060152 Number of Abis interface paging command
messages ........................................................... 324
C900060153 Number of Abis CS paging messages ........... 325
C900060154 Number of Abis PS paging messages ........... 325
C900060155 Number of available defined TCH/H ............. 326
to channel activation failure for handover(speech
version1)............................................................ 327
to BTS connection failure for handover (speech
version1)............................................................ 328
to BIU connection failure for handover (speech
version1)............................................................ 329
to TCU connection failure for handover (speech
version1)............................................................ 330
to channel activation failure for handover(speech
version2)............................................................ 332
version2)............................................................ 333
version2)............................................................ 334
XX

version2)............................................................ 335
channel activation failure for handover (speech
version3)............................................................ 336
version3)............................................................ 338
version3)............................................................ 339
version3)............................................................ 340
C900060168 Number of Voice TCH/F handover
success .............................................................. 341
to channel activation failure for handover................ 343
to BTS connection failure for handover ................... 344
to BIU connection failure for handover.................... 345
to TCU connection failure for handover ................... 346
C900060173 Number of data TCH/F handover
success .............................................................. 347
C900060174 Number of signaling TCH/H allocation failure
for assignment .................................................... 350
C900060175 Number of TCH/H allocation failure due to
version1)............................................................ 351
C900060176 Number of TCH/H allocation failure due
version1)............................................................ 352
version1)............................................................ 353
XXI

to TCU connection failure for assignment (speech
version1)............................................................ 354
version1)............................................................ 355
version1)............................................................ 356
version1)............................................................ 357
version1)............................................................ 358
version2)............................................................ 360
version2)............................................................ 361
version2)............................................................ 362
version2)............................................................ 363
version2)............................................................ 364
version2)............................................................ 365
version2)............................................................ 366
version2)............................................................ 367
XXII

version3)............................................................ 369
version3)............................................................ 370
version3)............................................................ 371
version3)............................................................ 372
version3)............................................................ 373
version3)............................................................ 374
version3)............................................................ 375
version3)............................................................ 376
C900060199 Number of Voice TCH/H assignment
success .............................................................. 378
failure ................................................................ 379
C900060201 Number of Voice TCH/H handover
success .............................................................. 380
C900060202 Number of data TCH/H allocation failure due
to channel activation failure for assignment............. 383
to BTS connection failure for assignment ................ 384
to BIU connection failure for assignment................. 384
to TCU connection failure for assignment ................ 385
to channel activation failure for handover................ 386
XXIII

to BTS connection failure for handover ................... 387
to BIU connection failure for handover.................... 388
to TCU connection failure for handover ................... 389
C900060210 Number of data TCH/H assignment
success .............................................................. 390
C900060211 Number of data TCH/H assignment
failure ................................................................ 392
C900060212 Number of data TCH/H handover
success .............................................................. 392
C900060213 Number of BSC-controlled incoming
handover due to forced release ............................. 395
handover due to queues ....................................... 396
handover due to forced handover .......................... 397
handover due to forced handover .......................... 398
C900060217 Number of unavailable defined TCH/H.......... 398
C900060218 Number of unavailable defined TCH/F .......... 399
C900060219 Number of signaling TCH/F drops due to
C900060220 Number of voice TCH/F drops due to
C900060221 Number of data TCH/F drops due to
C900060222 Number of signaling TCH/H drops due to
C900060223 Number of data TCH/H drops due to
C900060224 Number of TCH/H handover attempts due to
UL strength ........................................................ 410
DL strength ........................................................ 410
UL quality ........................................................... 411
DL quality........................................................... 412
XXIV

UL interference ................................................... 412
DL interference ................................................... 413
C900060230 Number of TCH/H inter-subcell handover
attempts due to good C/I ..................................... 414
C900060231 Number of TCH/H inter-subcell handover
attempts due to bad C/I ....................................... 414
PBGT ................................................................. 415
large TA ............................................................. 416
other reasons...................................................... 417
success .............................................................. 417
C900060236 Number of MOC access success .................. 418
C900060237 Number of dual band outgoing
handover............................................................ 419
C900060238 Number of dual band outgoing handover
success .............................................................. 420
C900060239 Number of dual band incoming
handover............................................................ 421
C900060240 Number of dual band incoming handover
success .............................................................. 421
C900060241 Number of SDCCH assignment
attempts ............................................................ 422
C900060242 Number of SDCCH assignments
success .............................................................. 423
C900060243 Number of SDCCH assignment failure .......... 424
C900060244 Number of voice TCH/F drops due to radio
link failure .......................................................... 425
C900060245 Number of voice TCH/H drops due to radio
link failure .......................................................... 426
Configuration Management Infomation Basic

Measurement ................................................ 429
Overview.................................................................... 429
C900090001 Cell frequency band .................................. 429
C900090002 Number of TRX ......................................... 430
C900090003 Number of TCH......................................... 430
XXV
C900090004 Number of SDCCH .................................... 430

C900090005 Radio capacity (call loss 1) ......................... 430
C900090006 Radio capacity (call loss 2) ......................... 431
C900090007 Radio capacity (based on TRX).................... 431
C900090008 Number of static PDTCH............................. 431
C900090009 Number of dynamic PDTCH ........................ 431
Downlink Data TBF Measurement .................. 433

Overview.................................................................... 434
C901000001 Number of GPRS DL TBF resumption in delay
state.................................................................. 434
failure on PACCH due to time out ........................... 435
failure on PACCH due to other reasons ................... 436
failure on CCCH/PCCCH due to time out.................. 437
failure on CCCH/PCCCH due to other reasons .......... 438
execution on CCCH/PCCCH ................................... 438
execution failure on CCCH/PCCCH due to polling
failed ................................................................. 440
execution success on CCCH/PCCCH due to polling
succeeded .......................................................... 442
success on CCCH/PCCCH ...................................... 444
C901000015 Number of GPRS DL TBF normal
release............................................................... 446
C901000023 Number of EGPRS DL TBF resumption in
delay state ......................................................... 447
failure on PACCH due to time out ........................... 448
failure on PACCH due to other reasons ................... 449
failure on CCCH/PCCCH due to time out.................. 450
XXVI

execution on CCCH/PCCCH ................................... 451
execution failure on CCCH/PCCCH due to polling
failed ................................................................. 453
execution success on CCCH/PCCCH due to polling
succeeded .......................................................... 455
C901000037 Number of EGPRS DL TBF normal
release............................................................... 459
C901000045 Time of GPRS DL TBF connection ................ 460
C901000046 Time of EGPRS DL TBF connection............... 461
C901000047 Time of DL signaling TBF connection............ 461
C901000048 Max number of GPRS DL TBF simultaneous
establishment ..................................................... 462
C901000050 Max number of EGPRS DL TBF simultaneous
establishment ..................................................... 463
C901000052 Number of GPRS DL signaling TBF normal
release............................................................... 463
C901000058 Number of EGPRS DL signaling TBF normal
release............................................................... 464
Uplink Data TBF Measurement....................... 467

Overview.................................................................... 468
C901010001 Number of GPRS UL TBF resumption in
extend uplink state .............................................. 468
C901010002 Number of GPRS UL TBF resource reassign
in delay uplink state............................................. 469
C901010006 Number of GPRS establishment failure on
PACCH due to time out ......................................... 470
C901010007 Number of GPRS establishment failure on
PACCH due to other reasons ................................. 470
failure on CCCH/PCCCH due to competition solving
failed ................................................................. 471
failure on CCCH/PCCCH due to not receive resource
request .............................................................. 472
XXVII

C901010014 Number of GPRS UL TBF normal
release............................................................... 476
C901010022 Number of EGPRS UL TBF resumption in
extend uplink state .............................................. 477
C901010023 Number of EGPRS UL TBF resource reassign
in delay uplink state............................................. 477
C901010027 Number of EGPRS establishment failure on
PACCH due to time out ......................................... 478
PACCH due to other reasons ................................. 479
failure on CCCH/PCCCH due to competition solving
failed ................................................................. 480
failure on CCCH/PCCCH due to not receive resource
request .............................................................. 481
C901010035 Number of EGPRS UL TBF normal
release............................................................... 484
C901010043 Time of GPRS UL TBF connection................. 485
C901010044 Time of EGPRS UL TBF connection ............... 485
C901010045 Time of UL signaling TBF connection ............ 486
C901010046 Max number of GPRS UL TBF simultaneous
establishment ..................................................... 486
C901010048 Max number of EGPRS UL TBF simultaneous
establishment ..................................................... 487
C901010050 Number of GPRS UL signaling TBF normal
release............................................................... 487
C901010056 Number of EGPRS UL signaling TBF normal
release............................................................... 488
Data Flow Measurement ................................ 491

Overview.................................................................... 491
XXVIII
C901020001 Number of Kbytes of IP packet sent to

BIPB .................................................................. 492
C901020002 Number of packets sent to BIPB.................. 492
C901020003 Number of Kbytes of IP packet received
from BIPB........................................................... 493
C901020004 Number of packets received from BIPB ......... 494
GIPB.................................................................. 494
C901020006 Number of packets sent to GIPB ................. 495
C901020007 Number of Kbytes of IP packet received
from GIPB .......................................................... 496
C901020008 Number of packets received from GIPB ......... 496
C901020009 Number of Kbytes carried by EGPRS DL LLC
frame................................................................. 497
C901020014 Number of Kbytes carried by DL signaling
LLC frame........................................................... 498
C901020019 Number of Kbytes carried by UL LLC
frame................................................................. 498
C901020020 Number of UL LLC frames .......................... 499
C901020021 Number of Bytes of GPRS DL TBF LLC
frame................................................................. 500
C901020022 Number of Bytes of EGPRS DL TBF LLC
frame................................................................. 500
C901020023 Number of Bytes of DL signaling TBF LLC
frame................................................................. 501
C901020024 Number of Bytes of UL GPRS TBF LLC
frame................................................................. 502
C901020025 Number of Bytes of EGPRS UL TBF LLC
frame................................................................. 503
C901020026 Number of Bytes of UL signaling TBF LLC
frame................................................................. 503
C901020031 Number of GPRS UL data TBF
completion ......................................................... 504
C901020034 Number of GPRS DL data TBF
completion ......................................................... 505
completion ......................................................... 506
C901020044 Number of EGPRS DL data TBF
completion ......................................................... 507
XXIX
C901020050 Number of Kbytes carried by GPRS DL LLC

frame................................................................. 508
Uplink-Downlink RLC Statistic Measurement ............................................................. 511

Overview.................................................................... 512
C901030041 Bytes of GPRS DL RLC lost on PDTCH........... 514
C901030042 Bytes of EGPRS DL RLC lost on PDTCH ......... 514
C901030083 Number of UL RLC Blocks lost ..................... 514
C901030084 Bytes of GPRS UL RLC lost on PDTCH........... 515
C901030085 Bytes of EGPRS UL RLC lost on PDTCH ......... 516
C901030086 Number of standstill of GPRS UL TBF
receiving window ................................................. 516
C901030087 Number of standstill of EGPRS UL TBF
receiving window ................................................. 517
C901030088 Number of standstill of GPRS DL TBF sending
window .............................................................. 517
C901030089 Number of standstill of EGPRS DL TBF
sending window................................................... 518
C901030090 Number of increment of DL coding
mode ................................................................. 519
C901030091 Number of decrement of DL coding
mode ................................................................. 520
C901030092 Number of increment of UL coding
mode ................................................................. 522
C901030093 Number of decrement of UL coding
mode ................................................................. 522
C901030094 Number of conversion from GMSK to
8PSK ................................................................. 523
C901030095 Number of conversion from 8PSK to
GMSK ................................................................ 525
C901030153 Number of increment of GPRS DL coding
mode ................................................................. 527
C901030154 Number of decrement of GPRS DL coding
mode ................................................................. 528
C901030155 Number of increment of GPRS UL coding
mode ................................................................. 528
C901030156 Number of decrement of GPRS UL coding
mode ................................................................. 529
C901030157 Number of increment of EGPRS DL coding
mode ................................................................. 530
XXX
C901030158 Number of decrement of EGPRS DL coding

mode ................................................................. 530
C901030159 Number of increment of EGPRS UL coding
mode ................................................................. 531
C901030160 Number of decrement of EGPRS UL coding
mode ................................................................. 532
PS Resource Used Statistic Measurement ............................................................. 533

Overview.................................................................... 534
C901040001 Maximum number of Abis TS used .............. 534
C901040002 Average number of Abis TS used................. 535
C901040004 Average number of unavailable PDCH .......... 535
C901040005 Number of available static PDCH ................. 535
C901040006 Number of unavailable static PDCH.............. 536
C901040009 Time of DL PDCH congestion ...................... 536
C901040010 Time of UL PDCH congestion....................... 537
C901040011 Time of PDCH used at least one UL/DL TBF
exists................................................................. 538
C901040012 Time of PDCH used at least one UL/DL
EGPRS TBF exists ................................................ 538
C901040013 Time of PDCH used at least one DL TBF
exists................................................................. 539
C901040014 Time of PDCH used at least one UL TBF
exists................................................................. 539
C901040018 Number of immediate assignment on
AGCH................................................................. 540
C901040019 Number of paging PS requests on PCH ......... 541
C901040020 Number of paging CS requests on PCH ......... 542
PCH ................................................................... 542
PAGCH ............................................................... 543
C901040023 Number of paging PS requests on
PPCH ................................................................. 544
C901040024 Number of paging CS requests on
PPCH ................................................................. 545
PPCH ................................................................. 546
C901040026 Number of Packet Channel Request on
PRACH ............................................................... 546
XXXI
C901040027 Sum of Abis TS used sampling .................... 547

C901040028 Number of Abis TS used sampling ............... 547
C901040029 Sum of PDCH used sampling ...................... 548
C901040030 Number of PDCH used sampling.................. 548
C901040031 Maximum value of Abis TS used to CS ......... 548
C901040032 Minimum value of Abis TS used to CS .......... 549
C901040033 Total value of the regular sampling used to
CS ..................................................................... 549
C901040034 Number of sampling of CS.......................... 550
C901040035 Maximum value of Abis TS used to PS.......... 550
C901040036 Minimum value of Abis TS used to PS .......... 550
PS ..................................................................... 551
C901040038 Number of sampling of PS .......................... 551
C901040039 MAX CS used number of exclusive
ABIS .................................................................. 551
C901040040 MIN CS used number of exclusive ABIS ......... 552
C901040041 MAX PS used number of exclusive ABIS ......... 552
C901040042 MIN PS used number of exclusive ABIS ......... 552
C901040043 Average Number of GPRS User ................... 553
C901040044 Maximum number of GPRS User ................. 553
C901040045 Average Number of EGPRS User.................. 554
C901040046 Maximum number of EDGE User ................. 554
C901040047 Number of assigned uplink radio
channels ............................................................ 554
C901040048 Number of assigned downlink radio
channels ............................................................ 555
C901040049 Number of requested uplink radio
channels ............................................................ 555
C901040050 Number of requested downlink radio
channels ............................................................ 556
C901040051 Number of PS channel expand .................... 556
C901040052 Number of PS channel expand perform ......... 556
C901040053 Number of PS channel expand success ......... 557
RMM Assignment Measurement..................... 559

Overview.................................................................... 561
C901050001 Number of general assignment executions
for voice channel ................................................. 561
C901050002 Number of assignments attempts for voice
due to forced release ........................................... 562
XXXII
C901050003 Number of assignment executions for voice

channel due to forced release................................ 563
C901050004 Number of handover attempts for voice due
to forced release ................................................. 564
C901050005 Number of handover executions for voice
channel due to forced release................................ 565
C901050006 Number of assignments for voice channel
due to queuing .................................................... 566
C901050007 Number of assignments for execution for
voice channel due to queuing ................................ 567
C901050008 Duration of assignment success voice
channel due to queuing ........................................ 568
C901050009 Number of assignments success for voice
channel due to queuing ........................................ 569
C901050010 Number of assignments for directed retry
attempts for voice channel.................................... 570
voice channel due to directed retry ........................ 571
C901050012 Number of general assignments for
execution for data ............................................... 572
C901050013 Number of assignments attempts for data
C901050014 Number of assignment executions for data
C901050015 Number of handover attempts for data due
C901050016 Number of handover executions for data due
due to queuing .................................................... 577
data due to queuing............................................. 578
C901050019 Total duration of successful assignments for
data due to queuing............................................. 579
C901050020 Number of assignments success for data
due to queuing .................................................... 580
due to directed retry ............................................ 581
due to directed retry ............................................ 582
XXXIII
C901050023 Number of assignment for retry attempts

FDD cell for voice channel..................................... 583
C901050024 Number of assignment executions for
data due to directed retry to FDD cell for voice
channel .............................................................. 584
FDD cell for data ................................................. 585
due to directed retry to FDD cell for data ................ 586
TDD cell for voice channel..................................... 587
C901050028 Number of assignment executions for
data due to directed retry to TDD cell for voice
channel .............................................................. 588
TDD cell for data ................................................. 589
due to directed retry to TDD cell for data ................ 590
C901050031 Assignment unsuccessful due to circuit
obstruction ......................................................... 591
C901050032 Assignment unsuccessful due to circuit
obstruction unmatched......................................... 592
C901050033 Assignment unsuccessful due to no valid
radio resource ..................................................... 593
C901050034 Assignment unsuccessful due to other
causes ............................................................... 594
C901050035 Number of assignments attempts due to
forced release (emergency service)........................ 595
C901050036 Number of assignment executions channel
due to forced release (emergency service) .............. 596
C901050037 Number of assignment attempts due to
forced handover (emergency service)..................... 597
C901050038 Number of assignment executions channel
due to forced handover (emergency service) ........... 598
C901050039 Number of assignments channel due to
queuing (emergency service) ................................ 599
C901050040 Number of assignments for execution
channel due to queuing (emergency service)........... 600
C901050041 Number of forced handover target not found
(assignment forced handover) ............................... 601
XXXIV
C901050042 Number of send forced handover request to

lower PRI user (assignment forced handover).......... 602
C901050043 Number of received failure from lower
PRI user request resource for forced handover
C901050044 Number of lower PRI user handover failure
C901050045 Number of time out for wait resource
C901050046 Number of forced release target not found
(assignment forced release) .................................. 606
C901050047 Number of time out for wait resource
C901050048 Number of get before grab released channel
C901050049 Number of get before grab released
channel(assignment forced release) ....................... 609
C901050050 The count of Assignment using FULL IP
A-Interface ......................................................... 610
C901050051 The count of Assignment using PCM over IP
A-Interface ......................................................... 611
C901050052 The count of Assignment using PCM over
TDM A-Interface ................................................. 612
C901050053 The count of Assignment Failure caused by
"Requested Codec Type or Codec Configuration not
supported" ......................................................... 613
C901050054 The count of Assignment Failure caused
by "Requested Codec Type or Codec Configuration
unavailable"........................................................ 614
"Requested A-Interface Type not supported" ........... 615
"Requested A-Interface Type unavailable" ............... 616
"Call Identifier already allocated" ........................... 617
"Requested Redundancy Level not supported" ......... 618
"Call Access Control" ............................................ 619
XXXV
C901050060 Attempt Number of mode modify for

assignment......................................................... 620
C901050061 Success Number of mode modify for
assignment......................................................... 621
attempts for voice channel because of radio ............ 621
voice channel due to directed retry because of
radio.................................................................. 622
attempts for data channel because of radio ............. 623
data channel due to directed retry because of
radio.................................................................. 624
Handover Cause Measurement ...................... 627

Overview.................................................................... 629
C901060001 Number of handover attempts due to
directed retry ...................................................... 630
C901060002 Number of SDCCH handover attempts due
to UL received strength ....................................... 631
to DL received strength ........................................ 631
C901060004 Number of SDCCH Handover attempt due to
UL quality .......................................................... 632
DL quality........................................................... 633
to UL interference................................................ 633
to DL interference................................................ 634
C901060008 Number of SDCCH inter-subcell handover
attempts due to good C/I ..................................... 635
C901060009 Number of SDCCH inter-subcell handover
attempts due to bad C/I ....................................... 635
C901060010 Number SDCCH of handover attempts due
to PBGT.............................................................. 636
to large TA ......................................................... 637
to quick break up of UL ........................................ 638
XXXVI

to macro-micro switch ......................................... 638
to MSC request .................................................. 639
to traffic ............................................................. 640
to large TA and wastage ....................................... 641
to small TA and wastage ....................................... 642
C901060018 Number of SDCCH Handover attempt due
to a preferable electricity level of 3G adjacent
cell .................................................................... 643
C901060019 Number SDCCH handover attempts due to
forced transfer .................................................... 643
C901060020 Number of SDCCH handover during
assignment due to forced transfer.......................... 644
C901060021 Number of SDCCH handover during
handover due to forced transfer ............................ 645
to increased TA .................................................. 646
to TA decrease .................................................... 647
other factors ...................................................... 648
quick break up of UL ............................................ 649
macro-micro switch ............................................. 649
MSC request ....................................................... 650
traffic................................................................. 651
large TA and wastage ........................................... 652
small TA and wastage........................................... 653
preferable electricity level in 3G adjacent cell ......... 653
XXXVII

forced transfer .................................................... 654
C901060043 Number of TCH/F handover during
C901060044 Number of TCH/F handover attempts during
handover due to forced transfer............................. 656
TA increase......................................................... 657
TA decrease ........................................................ 658
quick break up of UL ............................................ 659
macro-micro switch ............................................. 660
MSC request ....................................................... 660
traffic................................................................. 661
large TA and wastage ........................................... 662
small TA and wastage........................................... 663
C901060064 Number of TCH/H handover attempts due
to a preferable electricity level in 3G adjacent
cell .................................................................... 664
forced transfer .................................................... 665
C901060066 Number of TCH/H handover attempts during
handover due to forced transfer............................. 667
handover due to TA increase ................................. 668
handover due to TA decrease ................................ 669
other reasons...................................................... 669
CS channel transfer ............................................. 670
XXXVIII

CS channel transfer ............................................. 671
Fragment reorganization....................................... 672
energy conservation............................................. 673
energy conservation............................................. 674
CS channel is forced release.................................. 675
CS channel is forced release.................................. 676
FR to HR during cell busy...................................... 677
to downlink rapid drop ......................................... 678
downlink rapid drop ............................................. 678
downlink rapid drop ............................................. 678
C901060082 Attempts of handover on TCH/F caused by
power adjustment ............................................... 679
C901060083 Attempts of handover on TCH/H caused by
power adjustment ............................................... 679
local switch......................................................... 680
local switch......................................................... 680
reducing band resources of IPAbis.......................... 681
C901060087 Attempts of handover on TCH/H because of
MASTERPWR_ALM from TRX.................................. 681
C901060088 Attempts of handover on TCH/F because of
MASTERPWR_ALM from TRX.................................. 682
directed retry for PBGT......................................... 683
to DL quality rapid drop ........................................ 684
DL quality rapid drop............................................ 684
XXXIX

DL quality rapid drop............................................ 685
RMM Call Drop Measurement ......................... 687

Overview.................................................................... 690
C901070001 Number of SDCCH drops due to loss of
contact with RANA ............................................... 690
C901070002 Number of SDCCH drops due to radio link
failure ................................................................ 691
C901070003 Number of SDCCH drops due to LAPD link
failure ................................................................ 692
C901070004 Number of SDCCH drops due to OMC-R
forced release ..................................................... 693
C901070005 Number of SDCCH drops due to forced
release by other calls ........................................... 694
C901070007 Number of SDCCH drops due to other
failure ................................................................ 695
C901070008 Number of signaling TCH/F drops due to loss
of contact with RANA ........................................... 696
radio link failure .................................................. 697
LAPD link failure .................................................. 698
OMC-R forced release........................................... 699
forced release by other calls.................................. 700
other failure........................................................ 701
C901070015 Number of voice TCH/F drops due to loss of
C901070017 Number of voice TCH/F drops due to LAPD
link failure .......................................................... 703
C901070018 Number of voice TCH/F drops due to OMC-R
forced release ..................................................... 704
C901070019 Number of voice TCH/F drops due to forced
C901070021 Number of voice TCH/F drops due to other
failure ................................................................ 707
C901070022 Number of data TCH/F drops due to loss of
XL
C901070023 Number of data TCH/F drops due to radio

link failure .......................................................... 709
C901070024 Number of data TCH/F drops due to LAPD
link failure .......................................................... 710
C901070025 Number of data TCH/F drops due to OMC-R
forced release ..................................................... 711
C901070026 Number of data TCH/F drops due to forced
C901070028 Number of data TCH/F drops due to other
failure ................................................................ 714
loss of contact with RANA ..................................... 715
radio link failure .................................................. 716
LAPD link failure .................................................. 717
OMC-R forced release........................................... 717
forced release by other calls.................................. 718
other failure........................................................ 719
C901070036 Number of voice TCH/H drops due to loss of
C901070038 Number of voice TCH/H drops due to LAPD
link failure .......................................................... 721
C901070039 Number of voice TCH/H drops due to OMC-R
forced release ..................................................... 723
C901070040 Number of voice TCH/H drops due to forced
C901070042 Number of voice TCH/H drops due to other
failure ................................................................ 725
C901070043 Number of data TCH/H drops due to loss of
C901070044 Number of data TCH/H drops due to radio
link failure .......................................................... 728
C901070045 Number of data TCH/H drops due to LAPD
link failure .......................................................... 729
C901070046 Number of data TCH/H drops due to OMC-R
forced release ..................................................... 730
XLI
C901070047 Number of data TCH/H drops due to forced

C901070049 Number of data TCH/H drops due to other
failure ................................................................ 733
C901070053 Number of SDCCH link failures.................... 734
C901070054 Number of TCH/F link failures ..................... 735
C901070055 Number of TCH/H link failures..................... 737
C901070056 Number of RANA link releases due to other
cause on SDCCH ................................................. 738
cause on TCH/F ................................................... 739
cause on TCH/H .................................................. 739
C901070059 Number of SDCCH short messages
drops ................................................................. 740
C901070060 Number of TCH/F short messages
drops ................................................................. 741
C901070061 Number of TCH/H short messages
drops ................................................................. 741
C901070062 Number of TCH/F drops due to CS channel is
forced release by PS ............................................ 742
C901070063 Number of TCH/H drops due to CS channel
is forced release by PS ......................................... 742
C901070064 Number of SDCCH drops due to eMLPP
forced handover .................................................. 743
eMLPP forced handover ........................................ 743
C901070066 Number of voice TCH/F drops due to eMLPP
forced handover .................................................. 744
C901070067 Number of data TCH/F drops due to eMLPP
forced handover .................................................. 745
C901070068 Number of sigaling TCH/H drops due to
eMLPP forced handover ........................................ 746
C901070069 Number of voice TCH/H drops due to eMLPP
forced handover .................................................. 746
C901070070 Number of data TCH/H drops due to eMLPP
forced handover .................................................. 747
C901070071 Bad quality of UL receiving (On
SDCCH) ............................................................. 748
XLII
C901070072 Bad quality of DL receiving (On

SDCCH) ............................................................. 749
C901070073 Lower electrical level of UL (On
SDCCH) ............................................................. 750
C901070074 Lower electrical level of DL (On
SDCCH) ............................................................. 751
C901070075 Number of signaling drops due to TA too far
(On SDCCH) ....................................................... 752
C901070076 Reasons of the other radios (On
SDCCH) ............................................................. 753
C901070077 Bad quality of UL receiving (On TCH/F) ......... 754
C901070078 Bad quality of DL receiving (On TCH/F) ......... 755
C901070079 Lower electrical level of UL (On TCH/F) ......... 756
C901070080 Lower electrical level of DL (On TCH/F) ......... 757
(On TCH/F) ......................................................... 758
C901070082 Reasons of the other radios (On TCH/F) ......... 759
C901070083 Bad quality of UL receiving (On TCH/H) ......... 761
C901070084 Bad quality of DL receiving (On TCH/H) ......... 762
C901070085 Lower electrical level of UL (On TCH/H) ......... 763
C901070086 Lower electrical level of DL (On TCH/H) ......... 764
(On TCH/H) ........................................................ 765
C901070088 Reasons of the other radios (On
TCH/H) .............................................................. 766
C901070089 The Count of Drop Call caused by "IP
Resource Reset" .................................................. 767
C901070090 Number of FR_V1 radio link fail................... 768
C901070093 Number of HR_V1 radio link fail .................. 769
C901070094 Number of HR_V3 radio link fail .................. 769
BIPB Active/Standby Changeover........................... 770
C901070096 Number of voice TCH/F drops due to BIPB
Active/Standby Changeover .................................. 770
C901070097 Number of data TCH/F drops due to BIPB
BIPB Active/Standby Changeover........................... 771
XLIII
C901070099 Number of voice TCH/H drops due to BIPB

C901070100 Number of data TCH/H drops due to BIPB
C901070101 Number of SDCCH drops due to LAPD
C901070102 Number of voice TCH/F drops due to LAPD
C901070103 Number of data TCH/F drops due to LAPD
LAPD Active/Standby Changeover .......................... 773
C901070105 Number of voice TCH/H drops due to LAPD
C901070106 Number of data TCH/H drops due to LAPD
LAPD Active/Standby Changeover .......................... 774
C901070108 Number of voice TCH/F drops due to
handover fail for power adjustment........................ 774
C901070109 Number of voice TCH/H drops due to
handover fail for power adjustment........................ 775
C901070110 Number of SDCCH drops due to BIPB
C901070111 Number of SDCCH drops due to BTS
failure ................................................................ 776
C901070112 Number of signaling TCH/F drops due to BTS
failure ................................................................ 777
C901070113 Number of voice TCH/F drops due to BTS
failure ................................................................ 778
C901070114 Number of data TCH/F drops due to BTS
failure ................................................................ 779
BTS failure.......................................................... 780
C901070116 Number of voice TCH/H drops due to BTS
failure ................................................................ 781
C901070117 Number of data TCH/H drops due to BTS
failure ................................................................ 782
C901070118 Call Drop by Releasing Local Switch............. 783
XLIV
Radio Resource Availability Measurement ............................................................. 785

Overview.................................................................... 785
C901080003 Maximum Number of Busy SDCCHs ............. 785
C901080004 Average processor load.............................. 787
C901080006 SDCCH congestion time ............................. 787
C901080008 Number of unavailable defined SDCCH ......... 788
C901080011 Maximum number of busy radio
channel .............................................................. 789
C901080012 Average number of busy radio channel ......... 790
C901080014 Average number of busy TCH/H .................. 791
C901080016 TCH/H busy time(SpeechVer1).................... 792
C901080017 TCH/H busy time(SpeechVer3).................... 793
C901080018 TCH/H congestion time .............................. 794
C901080022 Average number of busy TCH/F................... 796
C901080024 TCH/F busy time(SpeechVer1) .................... 796
C901080027 TCH/F congestion time............................... 800
C901080030 Number of TRXs ....................................... 801
C901080032 Reserved TCH/F busy time ......................... 802
C901080033 Maximum number of busy TCH/F ................ 803
C901080034 Cell down time ......................................... 804
General Handover Measurement ................... 805

Overview.................................................................... 812
handover attempts .............................................. 813
handover request failures due to unclear
factors ............................................................... 814
handover request failures due to unavailable ground
resource............................................................. 815
handover request failures due to unavailable radio
resource............................................................. 816
handover request failures due to other factors ......... 817
XLV

incoming handover attempts ................................. 818
handover attempts due to forced release ................ 819
handover attempts due to queue ........................... 820
handover attempts due to forced handover ............. 821
C901090020 BSC-controlled incoming handover time due
to queue ............................................................ 822
C901090021 Queue number of BSC-controlled incoming
handover............................................................ 824
C901090022 BSC-controlled incoming handover success
time due to queue ............................................... 826
handover success due to queue ............................. 827
C901090025 Number of incoming handover failure due to
circuit block ........................................................ 828
circuit group mismatch ......................................... 829
unavailable radio resource .................................... 830
other factors ....................................................... 831
handover attempts due to forced release ................ 832
handover attempts due to queue ........................... 833
handover attempts due to forced handover ............. 834
C901090037 MSC-controlled incoming handover time due
to queue ............................................................ 835
C901090038 Queue number of MSC-controlled incoming
handover............................................................ 837
C901090039 MSC-controlled incoming handover success
time due to queue ............................................... 839
handover success due to queue ............................. 840
XLVI
C901090041 Number of incoming handover attempts

from the same layer and frequency ........................ 841
the same layer and frequency ............................... 842
C901090043 Number of outgoing handover attempts to
C901090044 Number of outgoing handover success to
from undefined layer to the same frequency............ 845
undefined layer to the same frequency ................... 846
C901090047 Number of outgoing handover attempts
from undefined layer to the same frequency............ 847
C901090048 Number of outgoing handover success from
undefined layer to the same frequency ................... 848
from undefined layer (GSM900) to current layer
(GSM1800) ......................................................... 849
from current layer (GSM900) to undefined layer
(GSM1800) ......................................................... 850
C901090053 Number of outgoing handover from current
layer (GSM900) to undefined layer (GSM1800) ......... 851
C901090054 Number of outgoing handover success
from current layer (GSM900) to undefined layer
(GSM1800) ......................................................... 852
(GSM900)........................................................... 853
(GSM900)........................................................... 854
C901090059 Number of outgoing handover from
undefined layer (GSM1800) to current layer
(GSM900)........................................................... 855
C901090060 Number of outgoing handover success
(GSM900)........................................................... 856
XLVII

from upper layer to the same frequency ................. 857
upper layer to the same frequency......................... 858
from the same frequency to upper layer ................. 859
the same frequency to upper layer......................... 860
from lower layer to the same frequency.................. 861
lower layer to the same frequency ......................... 862
from the same frequency to lower layer.................. 863
the same frequency to lower layer ......................... 864
from the same layer GSM900 to GSM1800 .............. 865
C901090072 Number of outgoing handover attempts to
C901090073 Number of outgoing handover to the same
layer GSM900 to GSM1800 ................................... 867
C901090074 Number of outgoing handover success to
C901090075 Number of incoming handover attempts from
from GSM900 to GSM1800 to the upper layer.......... 869
C901090079 Number of outgoing handover from GSM900
to GSM1800 to the upper layer.............................. 870
GSM900 to GSM1800 to the upper layer ................. 871
C901090084 Number of outgoing handover attempts from
C901090085 Number of outgoing handover from GSM900
to GSM1800 in the lower layer .............................. 874
GSM900 to GSM1800 in the lower layer .................. 875
XLVIII

from GSM1800 to GSM900 to the upper layer.......... 881
from GSM1800 to GSM900 to the lower layer .......... 885
GSM1800 to GSM900 to the lower layer.................. 886
GSM1800 to GSM900 to the lower layer.................. 887
C901090105 Number of intra-cell handover
attempts ............................................................ 888
C901090108 Number of intra-cell inner-circle-to-outercircle handover attempts ...................................... 889
C901090109 Number of intra-cell inner-circle-to-outercircle handover success ........................................ 889
C901090110 Number of intra-cell outer-circle-to-innercircle handover attempts ...................................... 890
C901090111 Number of intra-cell outer-circle-to-innercircle handover success ........................................ 891
C901090112 Number of intra-cell inner-circle-to-innercircle handover attempts ...................................... 892
C901090113 Number of intra-cell inner-circle-to-innercircle handover success ........................................ 892
C901090114 Number of intra-cell outer-circle-to-outercircle handover attempts ...................................... 893
XLIX
C901090115 Number of intra-cell outer-circle-to-outercircle handover success ........................................ 894

C901090116 Number of handover attempts from 2G to
3G..................................................................... 895
C901090117 Number of handover from 2G to 3G............. 895
C901090118 Number of handover success from 2G to
3G..................................................................... 896
2G..................................................................... 897
C901090120 Number of handover from 3G to 2G............. 898
2G..................................................................... 899
C901090122 Number of intra-cell handover attempts
from TCH/F......................................................... 899
C901090123 Number of intra-cell TCH/F-to-TCH/F
handover............................................................ 900
C901090124 Number of intra-cell TCH/F-to-TCH/F
C901090125 Number of intra-cell TCH/F-to-TCH/H
handover............................................................ 902
C901090126 Number of intra-cell TCH/F-to-TCH/H
C901090127 Number of intra-cell handover attempts
from TCH/H ........................................................ 903
C901090128 Number of intra-cell TCH/H-to-TCH/F
handover............................................................ 904
C901090129 Number of intra-cell TCH/H-to-TCH/F
C901090130 Number of intra-cell TCH/H-to-TCH/H
handover............................................................ 906
C901090131 Number of intra-cell TCH/H-to-TCH/H
C901090132 Number of inter-cell handover attempts
from TCH/F......................................................... 908
C901090133 Number of inter-cell TCH/F-to-TCH/F
handover............................................................ 909
C901090134 Number of inter-cell TCH/F-to-TCH/F
C901090135 Number of inter-cell TCH/F-to-TCH/H
handover............................................................ 910
C901090136 Number of inter-cell TCH/F-to-TCH/H

C901090137 Number of inter-cell handover attempts
from TCH/H ........................................................ 912
C901090138 Number of inter-cell TCH/H-to-TCH/F
handover............................................................ 913
C901090139 Number of inter-cell TCH/H-to-TCH/F
C901090140 Number of inter-cell TCH/H-to-TCH/H
handover............................................................ 915
C901090141 Number of inter-cell TCH/H-to-TCH/H
C901090142 Total dual-band outgoing handover
attempts ............................................................ 917
C901090145 Number of dual band incoming handover
attempts ............................................................ 918
C901090148 Number of intra-cell invalid handovers ......... 919
incoming handover attempts due to forced release
(emergency service) ............................................ 920
incoming handover (forced release) (emergency
service).............................................................. 921
incoming handover attempts due to forced handover
incoming handover (forced handover) (emergency
service).............................................................. 923
C901090153 Number of BSC-controlled inter-cell incoming
handover attempts due to queue (emergency
service).............................................................. 924
handover (queue) (emergency service) .................. 925
handover attempts due to forced release
handover (forced release) (emergency
service).............................................................. 927
LI
C901090157 Number of MSC-controlled inter-cell

incoming handover attempts due to forced handover
handover (forced release) (emergency
service).............................................................. 929
handover attempts due to queue (emergency
service).............................................................. 930
handover (queue) (emergency service) .................. 931
(BSC-controlled inter-cell handover due to forced
handover) .......................................................... 932
lower PRI user (BSC-controlled inter-cell handover
due to forced handover) ....................................... 933
C901090163 Number of recv failure from lower PRI
user request resource for forced handover
handover) .......................................................... 934
handover) .......................................................... 936
C901090165 Number of high PRI user time out for wait
resource (BSC-controlled inter-cell handover due to
forced handover) ................................................. 937
release) ............................................................. 938
resource (BSC-controlled inter-cell handover due to
forced release) .................................................... 939
C901090168 Number of HO Target not found
(MSC-controlled incoming handover due to forced
handover) .......................................................... 940
lower PRI user (MSC-controlled incoming handover
due to forced handover) ....................................... 941
LII
C901090170 Number of failure to lower PRI user request

resource for forced handover (MSC-controlled
incoming handover due to forced handover) ............ 942
handover) .......................................................... 942
resource (MSC-controlled incoming handover due to
forced handover) ................................................. 943
release) ............................................................. 943
resource (MSC-controlled incoming handover due to
forced release) .................................................... 944
C901090177 Number of handover attempts due to eMLPP
forced handover .................................................. 946
C901090178 Number of handover due to eMLPP forced
handover............................................................ 946
C901090179 Number of handover success due to eMLPP
forced handover .................................................. 947
handover attempts between PLMN ......................... 947
handover between PLMN ...................................... 947
handover success between PLMN ........................... 948
handover attempts between PLMN ......................... 948
handover request fail between PLMN due to
unknown reason .................................................. 948
unavailable ground resource ................................ 949
LIII

unavailable radio resource .................................... 950
handover request fail between PLMN due to other
reasons .............................................................. 950
handover success between PLMN ........................... 952
incoming handover attempt between PLMN ............. 953
incoming handover between PLMN ......................... 953
incoming handover force-release attempt between
PLMN ................................................................. 953
incoming handover between PLMN due to force
release............................................................... 954
handover queue attempt between PLMN ................. 954
handover between PLMN due to queue ................... 954
incoming handover force-handover attempt
between PLMN .................................................... 955
incoming handover between PLMN due to force
handover............................................................ 955
incoming handover success between PLMN.............. 955
handover attempt between PLMN .......................... 956
C901090200 A interface incoming handover fail between
PLMN due to circuit block...................................... 957
PLMN due to circuit unmatch ................................. 958
PLMN due to unavailable radio resource .................. 958
LIV

PLMN due to other reason..................................... 959
handover force-release attempt between
PLMN ................................................................. 959
handover between PLMN due to force release .......... 960
handover queue attempt between PLMN ................. 960
handover between PLMN due to queue ................... 961
handover force-handover attempt between
PLMN ................................................................. 962
handover between PLMN due to force handover ......... 962
handover success between PLMN .......................... 963
C901090212 Number of handover due to Fragment
reorganization..................................................... 963
C901090213 Number of handover success due to
Fragment reorganization....................................... 963
C901090214 Number of handover attempt from AMR FR
to AMR HR due to high load .................................. 964
C901090215 Number of handover from AMR FR to AMR
HR due to high load ............................................. 965
C901090216 Number of handover success from AMR FR
to AMR HR due to high load .................................. 966
C901090217 Number of handover attempt from FR to HR
due to high load .................................................. 966
C901090218 Number of handover from FR to HR due to
high load ............................................................ 967
C901090219 Number of handover success from FR to HR
due to high load .................................................. 968
C901090220 Number of handover attempt from AMR HR
to AMR FR due to bad quality ................................ 968
C901090221 Number of handover from AMR HR to AMR
FR due to bad quality ........................................... 969
LV
C901090222 Number of handover success from AMR HR

to AMR FR due to bad quality ................................ 970
C901090223 Number of handover attempt from HR to FR
due to bad quality ............................................... 970
C901090224 Number of handover from HR to FR due to
bad quality ......................................................... 971
C901090225 Number of handover success from HR to FR
due to bad quality ............................................... 972
handover attempts, from GSM900 to GSM900 ......... 972
handover, from GSM900 to GSM900 ....................... 973
handover success, from GSM900 to GSM900 ........... 974
outgoing handover attempts, from GSM1800 to
GSM1800 ........................................................... 975
handover, from GSM1800 to GSM1800 ................... 976
outgoing handover success, from GSM1800 to
GSM1800 ........................................................... 977
GSM1800 ........................................................... 978
handover, from GSM900 to GSM1800 ..................... 979
handover success, from GSM900 to GSM1800 ......... 980
GSM900 ............................................................. 981
handover success, from GSM1800 to GSM900 ......... 983
GSM900 ............................................................. 984
LVI

outgoing handover, from GSM900 to GSM900 .......... 985
GSM900 ............................................................. 986
GSM1800 ........................................................... 987
C901090242 Number of MSC-controlled inter-cell outgoing
handover, from GSM1800 to GSM1800 ................... 988
GSM1800 ........................................................... 989
GSM1800 ........................................................... 990
GSM1800 ........................................................... 991
GSM900 ............................................................. 992
GSM900 ............................................................. 994
Adjacent Cell Handover Measurement ........... 995

Overview.................................................................... 996
C901100001 Number of handover attempts on the
adjacent cell. ...................................................... 996
C901100002 Number of handover success from selected
cell to the adjacent cell......................................... 997
C901100003 Number of handover attempts from adjacent
cell to the selected cell. ........................................ 998
C901100004 Number of handover success from adjacent
cell to the selected cell. ...................................... 1000
LVII
C901100005 Number of handover attempts from

selected cell to the adjacent cell due to better UL
quality.............................................................. 1001
selected cell to the adjacent cell due to better DL
quality.............................................................. 1002
C901100007 Number of handover success from
quality.............................................................. 1003
quality.............................................................. 1005
strength. .......................................................... 1006
strength. .......................................................... 1007
strength. .......................................................... 1009
strength. .......................................................... 1010
C901100013 Number of handover attempts from selected
cell to the adjacent cell due to PBGT .................... 1011
cell to the adjacent cell due to other factors. ......... 1014
C901100016 Number of successful handover from
selected cell to the adjacent cell due to other
factors. ............................................................ 1015
C901100017 Number of pingpong handover (handover to
source cell)....................................................... 1017
C901100018 The max of RTD...................................... 1018
C901100019 The sum of RTD ...................................... 1019
C901100020 The number of RTD ................................. 1020
LVIII

cell to the adjacent cell due to DL quality rapid
drop ................................................................ 1020
cell to the adjacent cell due to DL quality rapid
drop ................................................................ 1022
Radio Access Measurement ......................... 1025

Overview.................................................................. 1026
C901110001 Number of invalid access requests............. 1027
C901110003 Number of MOC access success for
processes ......................................................... 1027
C901110006 Number of MTC access success for
processes ......................................................... 1028
C901110008 Number of call re-establishment access
attempts .......................................................... 1028
success for processes......................................... 1029
success ............................................................ 1029
C901110011 Number of emergency calls access
attempts .......................................................... 1030
C901110012 Number of emergency calls access success
for processes .................................................... 1030
C901110013 Number of emergency calls access
success ............................................................ 1031
C901110014 Number of LOC access attempts ............... 1031
C901110015 Number of LOC access success for
processes ......................................................... 1031
C901110016 Number of LOC access success ................. 1032
C901110017 Number of other causes access
attempts .......................................................... 1032
C901110018 Number of successful random access
processes for other causes.................................. 1033
C901110019 Number of other causes access
success ............................................................ 1033
C901110020 Number of LMU Establishment Access
attempts .......................................................... 1034
C901110021 Number of LMU Establishment access
success for processes......................................... 1034
LIX
C901110022 Number of LMU Establishment access

success ............................................................ 1035
C901110023 Number of accesses due to location
update ............................................................. 1035
C901110024 Number of Access due to CM SERVICE
REQ ................................................................. 1035
C901110026 Number of CM service requests of
Emergency Call ................................................. 1036
SMS................................................................. 1036
Supplement ...................................................... 1037
LCS ................................................................. 1037
C901110031 Number of wireless access due to call
re-establishments .............................................. 1037
C901110032 Number of wireless accesses due to IMSI
detachment ...................................................... 1038
C901110033 Number of wireless accesses due to other
causes ............................................................. 1038
C901110034 Number of access due to Notification
response .......................................................... 1039
C901110035 Number of access due to Immediate
setup ............................................................... 1040
C901110036 Number of access due to Talker
indication ......................................................... 1041
C901110037 Number of access due to DATA
Indication ......................................................... 1042
C901110038 Number of access due to priority uplink
request ............................................................ 1043
C901110039 Number of access of CM service request of
VGCS ............................................................... 1044
VBS ................................................................. 1045
Radio Measurement..................................... 1047

Overview.................................................................. 1050
C901120001 Number of UL signal quality samples in
wireless channels .............................................. 1051
C901120002 Level of worst UL signal quality in wireless
channels .......................................................... 1051
LX
C901120003 Total value of UL quality level values in

C901120004 Number of DL signal quality samples in
C901120005 Level of worst DL signal quality in wireless
channels .......................................................... 1052
C901120006 Total value of DL quality strength values in
C901120007 Number of received UL signal strength
samples in wireless channels............................... 1053
C901120008 Maximum received UL signal strength in
C901120009 Minimum received UL signal strength in
C901120010 Total value of UL signal strength in wireless
channels .......................................................... 1055
C901120011 Number of received DL signal strength
samples in wireless channels............................... 1055
C901120012 Maximum received DL signal strength in
C901120013 Minimum DL received signal strength in
radio channels................................................... 1056
C901120014 Total value of DL signal strength in wireless
channels .......................................................... 1056
C901120015 Number of TA samples in wireless
channels .......................................................... 1057
C901120016 Maximum TA in wireless channels.............. 1057
C901120017 Total number of TAs in wireless
channels .......................................................... 1058
C901120018 Mean number of idle TCH/Fs with
interference band 0 ........................................... 1058
C901120024 Mean number of idle TCH/Hs with
C901120030 Mean number of idle SDCCHs with
LXI

C901120052 Number of TFO initiations......................... 1061
C901120053 Number of using noise suppression ........... 1061
C901120054 Number of mode changes for establishing
TFO ................................................................. 1062
C901120055 Number of mode changes for optimizing
TFO ................................................................. 1062
C901120056 Number of active collection changes for
establishing TFO ................................................ 1062
optimizing TFO .................................................. 1063
C901120058 Number of samples with voice quality is
excellent .......................................................... 1063
good ................................................................ 1063
medium ........................................................... 1064
bad.................................................................. 1064
awfully ............................................................. 1065
C901120063 Number of uplink error frame on
FR_V1.............................................................. 1065
C901120064 Total Number of uplink frame on
FR_V1.............................................................. 1065
FR_V2.............................................................. 1066
FR_V2.............................................................. 1066
FR_V3.............................................................. 1066
FR_V3.............................................................. 1067
HR_V1 ............................................................. 1067
LXII

HR_V1 ............................................................. 1067
HR_V3 ............................................................. 1067
HR_V3 ............................................................. 1068
C901120073 Number of UL signal quality samples in radio
channels on SDCCH ........................................... 1068
C901120074 Level of worst UL signal quality in radio
C901120075 Total value of UL quality level values in radio
C901120076 Number of DL signal quality samples in radio
C901120077 Level of worst DL signal quality in radio
radio channels on SDCCH ................................... 1070
samples in radio channels on SDCCH.................... 1071
C901120082 Total value of UL signal strength in radio
samples in radio channels on SDCCH.................... 1073
C901120086 Total value of DL signal strength in radio
channels on TCH................................................ 1075
C901120088 Level of worst UL signal quality in radio
channels on TCH................................................ 1075
channels on TCH................................................ 1076
LXIII

channels on TCH................................................ 1076
C901120091 Level of worst DL signal quality in radio
channels on TCH................................................ 1076
radio channels on TCH........................................ 1077
samples in radio channels on TCH ........................ 1077
C901120096 Total value of UL signal strength in radio
channels on TCH................................................ 1079
samples in radio channels on TCH ........................ 1079
C901120100 Total value of DL signal strength in radio
channels on TCH................................................ 1081
C901120101 Number of samples with UL RQ = 0 on
SDCCH............................................................. 1081
SDCCH............................................................. 1082
SDCCH............................................................. 1083
SDCCH............................................................. 1083
SDCCH............................................................. 1084
SDCCH............................................................. 1085
SDCCH............................................................. 1085
SDCCH............................................................. 1086
C901120109 Number of samples with DL RQ = 0 on
SDCCH............................................................. 1086
LXIV

SDCCH............................................................. 1087
SDCCH............................................................. 1088
SDCCH............................................................. 1088
SDCCH............................................................. 1089
SDCCH............................................................. 1090
SDCCH............................................................. 1090
SDCCH............................................................. 1091
TCH ................................................................. 1092
TCH ................................................................. 1092
TCH ................................................................. 1093
TCH ................................................................. 1094
TCH ................................................................. 1094
TCH ................................................................. 1095
TCH ................................................................. 1096
TCH ................................................................. 1096
TCH ................................................................. 1097
TCH ................................................................. 1097
TCH ................................................................. 1098
TCH ................................................................. 1099
TCH ................................................................. 1099
LXV

TCH ................................................................. 1100
TCH ................................................................. 1101
TCH ................................................................. 1101
Sub Cell Statistics........................................ 1103

Overview.................................................................. 1106
C901130001 Number of available TCH/Fs in the second
sub cell ............................................................ 1106
C901130002 Number of unavailable TCH/Fs in the second
sub cell ............................................................ 1107
C901130003 Number of available TCH/Hs in the second
sub cell ............................................................ 1107
C901130004 Number of unavailable TCH/Hs in the second
sub cell ............................................................ 1108
C901130005 Number of handover attempts from the first
sub cell to the second sub cell ............................. 1108
C901130006 Number of handover execution from the first
C901130007 Number of handover success from the first
C901130008 Number of handover attempts from the
second sub cell to the first sub cell....................... 1111
C901130009 Number of handover execution from the
C901130010 Number of handover success from the
C901130011 Number of handover attempts in the second
sub cell ............................................................ 1114
C901130012 Number of handover execution in the second
sub cell ............................................................ 1115
C901130013 Number of handover success in the second
sub cell ............................................................ 1116
C901130014 Number of outgoing inter-cell handover
attempts of the second sub cell ........................... 1116
execution of the second sub cell .......................... 1117
success of the second sub cell ............................. 1118
LXVI
C901130017 Handover attempts due to UL receiving

strength of the full rate second sub cell ................ 1119
C901130018 Handover attempts due to DL receiving
strength of the full rate second sub cell ................ 1120
C901130019 Handover attempts due to UL quality of the
full rate second sub cell ...................................... 1121
C901130020 Handover attempts due to DL quality of the
full rate second sub cell ...................................... 1122
C901130021 Handover attempts due to PBGT of the full
rate second sub cell ........................................... 1123
C901130022 Handover attempts due to traffic of the full
C901130023 Handover attempts due to UL interference
of the full rate second sub cell (on TCH/F)............. 1124
C901130024 Handover attempts due to DL interference
of the full rate second sub cell (on TCH/F)............. 1125
C901130025 Handover attempts due to good CI of the
full rate second sub cell (on TCH/F)...................... 1126
C901130026 Handover attempts due to bad CI of the full
rate second sub cell (on TCH/F) ........................... 1127
C901130027 Handover attempts due to path loss and
too large TA of the full rate second sub cell (on
TCH/F) ............................................................. 1128
C901130028 Handover attempts due to path loss and
too small TA of the full rate second sub cell (on
TCH/F) ............................................................. 1129
C901130029 Number of forced transfer handover
attempts of the full rate second sub cell (on
TCH/F) ............................................................. 1130
C901130030 Handover attempts due to other causes of
the full rate second sub cell................................. 1131
C901130031 Handover attempts due to UL receiving
strength of the half rate second sub cell ............... 1132
C901130032 Handover attempts due to DL receiving
strength of the half rate second sub cell ............... 1133
C901130033 Handover attempts due to UL quality of the
half rate second sub cell ..................................... 1134
C901130034 Handover attempts due to DL quality of the
half rate second sub cell ..................................... 1135
LXVII
C901130035 Handover attempts due to PBGT of the half

C901130036 Handover attempts due to traffic of the half
C901130037 Handover attempts due to UL interference
of the half rate second sub cell ............................ 1137
C901130038 Handover attempts due to DL interference
of the half rate second sub cell ............................ 1138
C901130039 Handover attempts due to C/I of the half
C901130040 Handover attempts due to C/I of the half
C901130041 Handover attempts due to path loss and too
large TA of the half rate second sub cell................ 1141
small TA of the half rate second sub cell ............... 1142
C901130043 Number of forced transfer handover
attempts of the half rate second sub cell............... 1143
C901130044 Handover attempts due to other causes of
the half rate second sub cell................................ 1144
C901130045 Number of attempts of TCH/F seizure of the
second sub cell (used for assignment) .................. 1145
C901130046 Number of TCH/F seizure success of the
C901130047 Number of TCH/F seizure failure of the
C901130048 Number of attempts of TCH/F seizure of the
second sub cell (used for handover) ..................... 1147
C901130049 Number of TCH/F seizure success of the
C901130050 Number of TCH/F seizure failure of the
C901130051 Number of TCH/H seizure attempts of the
C901130052 Number of TCH/H seizure success of the
C901130053 Number of TCH/H seizure failure of the
C901130054 Number of TCH/H seizure attempts of the
LXVIII
C901130055 Number of TCH/H seizure success of the

C901130056 Number of TCH/H seizure failure of the
C901130057 Number of TCH/F call drops in the second
sub cell ............................................................ 1153
C901130058 Number of TCH/H call drops in the second
sub cell ............................................................ 1154
C901130059 TCH/F busy time in the second sub
cell .................................................................. 1155
C901130060 TCH/H busy time in the second sub
cell .................................................................. 1155
C901130061 Number of TCH/F assignment attempts of
the second sub cell ............................................ 1156
C901130062 Number of TCH/F assignment success of the
second sub cell.................................................. 1156
C901130063 Number of TCH/F handover attempts of the
second sub cell.................................................. 1157
C901130064 Number of TCH/F handover success of the
second sub cell.................................................. 1158
C901130065 Number of TCH/H assignment attempts of
the second sub cell ............................................ 1159
C901130066 Number of TCH/H assignment success of the
second sub cell.................................................. 1159
C901130067 Number of TCH/H handover attempts of the
second sub cell.................................................. 1160
C901130068 Number of TCH/H handover success of the
second sub cell.................................................. 1161
C901130069 TCH/F of the first sub cell seizure success
when prefer the second sub cell (used for
assignment) ..................................................... 1161
C901130070 TCH/F of the first sub cell seizure success
handover) ........................................................ 1162
C901130071 TCH/H of the first sub cell seizure success
assignment) ..................................................... 1163
C901130072 TCH/H of the first sub cell seizure success
handover) ........................................................ 1163
LXIX
C901130073 Number of Inter-Cell Handover Attempts to

the Second Sub Cell Directly From the Cell in the
Same Site ........................................................ 1164
C901130074 Number of Inter-Cell Handover Execution to
Same Site ........................................................ 1164
C901130075 Number of Inter-Cell Handover Success to
Same Site ........................................................ 1165
C901130076 Number of Inter-Cell Handover Attempts
to the Second Sub Cell Directly From Another
Site ................................................................. 1165
C901130077 Number of Inter-Cell Handover Execution
Site ................................................................. 1166
C901130078 Number of Inter-Cell Handover Success
Site ................................................................. 1166
C901130079 Number of Handover Attempts to the Second
Sub Cell Directly From Another BSC ..................... 1167
C901130080 Number of Handover Execution to the
Second Sub Cell Directly From Another BSC .......... 1167
C901130081 Number of Handover Success to the Second
Sub Cell Directly From Another BSC ..................... 1168
C901130082 Number of Handover to the First Sub Cell
Too Fast After Handover From Another Cell in the
Same Site ........................................................ 1168
C901130083 Number of Handover to the Second Sub Cell
Too Fast After Handover From Another Cell in the
Same Site ........................................................ 1169
Too Fast After Handover From Another Site ........... 1169
Too Fast After Handover From Another Site ........... 1170
MS TA Measurement .................................... 1171

Overview.................................................................. 1171
C901140001 Number of TA=0 ..................................... 1172
C901140002 Number of 0<TA<= 2.............................. 1172
C901140003 Number of 2<TA<=4............................... 1173
C901140004 Number of 4<TA<=6............................... 1173
LXX
C901140005 Number of 6<TA<=8............................... 1174

C901140006 Number of 8<TA<=10 ............................. 1174
C901140007 Number of 10<TA<=12 ........................... 1175
C901140008 Number of 12<TA<=14 ........................... 1176
C901140009 Number of 14<TA<=16 ........................... 1176
C901140010 Number of 16<TA<=18 ........................... 1177
C901140011 Number of 18<TA<=20 ........................... 1177
C901140012 Number of 20<TA<=22 ........................... 1178
C901060013 Number of 22<TA<=24 ........................... 1178
C901140014 Number of 24<TA<=26 ........................... 1179
C901140015 Number of 26<TA<=28 ........................... 1180
C901140016 Number of 28<TA<=30 ........................... 1180
C901140017 Number of 30<TA<=32 ........................... 1181
C901140018 Number of 32<TA<=34 ........................... 1181
C901140019 Number of 34<TA<=36 ........................... 1182
C901140020 Number of 36<TA<=38 ........................... 1183
C901140021 Number of 38<TA<=40 ........................... 1183
C901140022 Number of 40<TA<=42 ........................... 1184
C901140023 Number of 42<TA<=44 ........................... 1184
C901140024 Number 44<TA<=46 ............................... 1185
C901140025 Number of 46<TA<=48 ........................... 1186
C901140026 Number of 48<TA<=50 ........................... 1186
C901140027 Number of 50<TA<=52 ........................... 1187
C901140028 Number of 52<TA<=54 ........................... 1187
C901140029 Number of 54<TA<=56 ........................... 1188
C901140030 Number of 56<TA<=58 ........................... 1189
C901140031 Number of 58<TA<=60 ........................... 1189
C901140032 Number of 60<TA<=63 ........................... 1190
C901140033 Number of TA>63 ................................... 1190
SAPI3 Measurement.................................... 1193

Overview.................................................................. 1194
C901150001 Number of SAPI3 link establishments on
SACCH/F (MO-SM)............................................. 1194
SACCH/H (MO-SM) ............................................ 1195
FACCH/F (MO-SM) ............................................. 1196
FACCH/H (MO-SM)............................................. 1197
LXXI

requests on SACCH/F (MT-SM) ............................ 1197
requests on SACCH/H (MT-SM)............................ 1198
requests on FACCH/F (MT-SM) ............................ 1199
requests on FACCH/H (MT-SM) ............................ 1200
C901150011 Number of successful SAPI3 link
establishments on SACCH/F (MT-SM) ................... 1200
establishments on SACCH/H (MT-SM)................... 1201
establishments on FACCH/F (MT-SM).................... 1202
establishments on FACCH/H (MT-SM) ................... 1203
C901150016 Number of DTAP messages used as SDCCH
UL point-to-point short messages (SMs) ............... 1203
C901150017 Number of DTAP messages used as SDCCH
DL point-to-point short messages (SMs) ............... 1205
C901150018 Number of DTAP messages on FACCH/F UL
for point-to-point short messages ........................ 1207
C901150019 Number of DTAP messages on FACCH/F DL
C901150020 Number of DTAP messages on FACCH/H UL
C901150021 Number of DTAP messages on FACCH/H DL
C901150022 Number of DTAP messages on SACCH/F DL
C901150023 Number of DTAP messages on SACCH/F DL
C901150024 Number of DTAP messages on SACCH/H UL
C901150025 Number of DTAP messages on SACCH/H DL
Uplink and Downlink PACCH Statistics......... 1217

Overview.................................................................. 1218
C901160001 Number of Packet access reject
message .......................................................... 1218
LXXII
C901160002 Number of Packet resource request

message .......................................................... 1219
C901160003 Number of Packet UL Assignment
message .......................................................... 1219
C901160004 Number of Additional MS access capabilities
message .......................................................... 1220
C901160005 Number of Packet DL Assignment
message .......................................................... 1221
C901160006 Number of Packet TBF release
message .......................................................... 1222
C901160007 Number of Packet DL Ack/Nack
message .......................................................... 1223
C901160008 Number of EGPRS Packet DL Ack/Nack
message .......................................................... 1224
C901160009 Number of Packet UL Ack/Nack
message .......................................................... 1225
C901160010 Number of Packet Control Acknowledgement
message .......................................................... 1226
C901160011 Number of Packet Cell Change Continue
message .......................................................... 1227
C901160012 Number of Packet Cell Change Failure
message .......................................................... 1229
C901160013 Number of Packet Cell Change Notification
message .......................................................... 1229
C901160014 Number of Packet Cell Change Order
message .......................................................... 1230
C901160017 Number of packet mobile TBF status
messages ......................................................... 1231
C901160018 Number of packet neighbor cell data
messages ......................................................... 1232
C901160019 Number of packet PDCH release
messages ......................................................... 1233
C901160020 Number of packet polling request
messages ......................................................... 1233
C901160021 Number of packet power control/timing
advance messages............................................. 1234
C901160022 Number of packet PSI status message......... 1235
C901160023 Number of packet serving cell data
messages ......................................................... 1236
C901160024 Number of packet SI status messages......... 1237
LXXIII
C901160025 Number of packet timeslot reconfigure

messages ......................................................... 1238
C901160026 Number of packet paging request
message .......................................................... 1239
C901160027 Number of PSI message........................... 1240
Downlink GPRS Data TBF Statistics ............. 1243

Overview.................................................................. 1245
requests on CCCH/PCCCH ................................... 1245
requests on PACCH ............................................ 1246
failure due to CPU.............................................. 1246
failure due to not support DTM ............................ 1247
failure due to Abis congestion.............................. 1247
failure due to RR congestion................................ 1248
failure due to UPPB-DSP channel congestion.......... 1249
channel allocate success ..................................... 1251
C901170011 Number of allocated PDCH for GPRS DL TBF
establishment ................................................... 1251
failure due to channel activate failed .................... 1252
failure due to BTS connection failed...................... 1253
failure due to BIU connection failed ...................... 1254
C901170015 Number of GPRS DL TBF channel activate
establishment success........................................ 1255
failure on CCCH/PCCCH due to not receive
PIA .................................................................. 1255
failure on CCCH/PCCCH due to UPPB-DSP
congestion........................................................ 1256
LXXIV
C901170018 Number of GPRS DL TBF establishment failure

on PACCH due to UPPB-DSP congestion ................ 1257
success on PCCCH/CCCH .................................... 1257
success on PACCH ............................................. 1258
reallocation failure due to Abis congestion for UL
TBF establishment ............................................. 1258
reallocation failure due to RR congestion for UL TBF
establishment ................................................... 1259
reallocation failure due to UPPB-DSP channel
congestion for UL TBF establishment .................... 1260
reallocation success of channel allocation due to UL
C901170027 Number of allocated PDCH for GPRS
DL TBF resource reallocation due to UL TBF
establishment ................................................... 1262
reallocation failure due to channel activate failure
for UL TBF establishment .................................... 1263
reallocation failure due to BTS connection failure for
UL TBF establishment......................................... 1264
reallocation failure due to BIU connection failure for
reallocation success of channel activate and
connection for UL TBF establishment .................... 1266
C901170032 Number of GPRS DL TBF resource reallocation
failure due to UL TBF establishment ..................... 1267
success due to UL TBF establishment ................... 1267
reallocation failure due to Abis congestion for LLC
transmission ..................................................... 1268
LXXV

reallocation failure due to RR congestion for LLC
transmission ..................................................... 1269
congestion for LLC transmission........................... 1270
reallocation success of channel allocation due to LLC
transmission ..................................................... 1271
C901170040 Number of allocated PDCH for GPRS DL TBF
resource reallocation due to LLC transmission......... 1272
for LLC transmission .......................................... 1273
LLC transmission ............................................... 1274
connection for LLC transmission........................... 1276
reallocation failure due to LLC transmission ........... 1276
reallocation success due to LLC transmission ......... 1277
C901170047 Number of GPRS DL TBF release due to flush
LL.................................................................... 1277
GPRS suspend requests ...................................... 1278
CS ................................................................... 1278
C901170050 Number of GPRS DL TBF normal release due
to user plane requests........................................ 1279
C901170051 Number of GPRS DL TBF abnormal release
due to user plane requests.................................. 1280
NSVC unavailability............................................ 1280
LXXVI
C901170053 Number of GPRS DL TBF release due to BVC

unavailability .................................................... 1281
other reasons.................................................... 1282
C901170055 Number of DL GPRS TBF grab
resources ......................................................... 1282
C901170056 Number of grab instance by DL GPRS
TBF ................................................................. 1283
C901170057 Number of DL GPRS TBF queuing .............. 1284
C901170058 Number of DL GPRS TBF queuing
success ............................................................ 1284
C901170059 Number of DL GPRS TBF release TBF during
queuing............................................................ 1285
Downlink EGPRS Data TBF Statistics ........... 1287

Overview.................................................................. 1289
requests on CCCH/PCCCH ................................... 1289
failure due to CPU.............................................. 1291
failure due to not support DTM ............................ 1291
C901180011 Number of allocated PDCH for EGPRS DL
LXXVII
C901180015 Number of EGPRS DL TBF channel activate

failure on CCCH/PCCCH due to not receive
PIA .................................................................. 1300
failure on CCCH/PCCCH due to UPPB-DSP
congestion........................................................ 1301
C901180018 Number of EGPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion........... 1301
success on PACCH ............................................. 1302
reallocation failure due to Abis congestion for UL
reallocation failure due to RR congestion for UL TBF
establishment ................................................... 1303
congestion for UL TBF establishment .................... 1304
reallocation success of channel allocation due to UL
C901180027 Number of allocated PDCH for EGPRS
DL TBF resource reallocation due to UL TBF
establishment ................................................... 1306
for UL TBF establishment .................................... 1307
LXXVIII

connection for UL TBF establishment .................... 1310
C901180032 Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment ............... 1310
C901180033 Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment ............. 1311
transmission ..................................................... 1311
transmission ..................................................... 1312
transmission ..................................................... 1314
C901180040 Number of allocated PDCH for EGPRS DL TBF
connection for LLC transmission........................... 1319
flush LL ............................................................ 1320
LXXIX

EGPRS suspend requests .................................... 1321
CS ................................................................... 1322
C901180050 Number of EGPRS DL TBF normal release
C901180051 Number of EGPRS DL TBF abnormal release
BVC unavailability .............................................. 1324
other reasons.................................................... 1325
C901180055 Number of DL EGPRS TBF grab
resources ......................................................... 1325
C901180056 Number of grab instance by DL EGPRS
TBF ................................................................. 1326
C901180057 Number of DL EGPRS TBF queuing ............ 1327
C901180058 Number of DL EGPRS TBF queuing
success ............................................................ 1327
C901180059 Number of DL EGPRS TBF release TBF during
queuing............................................................ 1328
Uplink GPRS Data TBF Statistics .................. 1329

Overview.................................................................. 1332
requests on CCCH.............................................. 1332
requests on CCCH.............................................. 1333
requests on PCCCH ............................................ 1333
C901190007 Number of cell attempts for UL assignment
due to ONE PHASE access................................... 1335
due to single block packet access......................... 1336
LXXX

due to response paging ...................................... 1337
due to cell updating ........................................... 1338
due to mobility management............................... 1339
due to TWO PHASE access .................................. 1339
due to short access............................................ 1340
C901190019 Number of cell success for GPRS UL
assignment due to ONE PHASE access .................. 1347
assignment due to single block packet access......... 1349
assignment due to response paging ..................... 1349
assignment due to cell updating .......................... 1350
assignment due to mobility management .............. 1351
assignment due to TWO PHASE access ................. 1352
assignment due to short access ........................... 1353
C901190026 Number of allocated PDCH for GPRS UL TBF
establishment ................................................... 1354
LXXXI
C901190030 Number of GPRS UL TBF channel activate

failure due to not receive PIA .............................. 1359
C901190032 Number of GPRS UL TBF establisment
failure on PCCCH/CCCH due to UPPB-DSP
congestion........................................................ 1360
C901190033 Number of GPRS UL TBF establisment failure
on PACCH due to UPPB-DSP congestion ................ 1361
success on PACCH ............................................. 1362
reallocation failure due to Abis congestion for DL
reallocation failure due to RR congestion for DL TBF
establishment ................................................... 1363
congestion for DL TBF establishment .................... 1364
reallocation success of channel allocation due to DL
C901190042 Number of allocated PDCH for GPRS
UL TBF resource reallocation due to DL TBF
establishment ................................................... 1366
C901190043 Number of GPRS UL TBF resourse
for DL TBF establishment.................................... 1367
DL TBF establishment......................................... 1368
connection for DL TBF establishment .................... 1370
LXXXII
C901190047 Number of GPRS UL TBF resourse reallocation

failure due to DL TBF establishment ..................... 1371
success due to DL TBF establishment ................... 1371
transmission ..................................................... 1371
transmission ..................................................... 1372
transmission ..................................................... 1374
reallocation success of channel activate for LLC
transmission ..................................................... 1379
reallocation requests for resource request ............. 1380
reallocation failure due to Abis congestion for
resource request ............................................... 1380
LXXXIII

reallocation failure due to RR congestion for
congestion for resource request........................... 1382
reallocation success due to resource request ......... 1383
resource reallocation due to resource request......... 1384
for resource request........................................... 1385
connection for resource request........................... 1388
reallocation failure due to resource request ........... 1389
C901190075 Number of GPRS UL TBF release due to flush
LL.................................................................... 1389
CS ................................................................... 1391
C901190078 Number of GPRS UL TBF normal release due
to user plane requests........................................ 1391
C901190079 Number of GPRS UL TBF abnormal release
C901190081 Number of GPRS UL TBF release due to BVC
unavailability .................................................... 1393
LXXXIV

other reasons.................................................... 1394
C901190083 Number of UL GPRS TBF grab
resources ......................................................... 1395
C901190084 Number of grab instance by UL GPRS
TBF ................................................................. 1395
C901190085 Number of UL GPRS TBF queuing .............. 1396
C901190086 Number of UL GPRS TBF queuing
success ............................................................ 1397
C901190087 Number of UL GPRS TBF release TBF during
queuing............................................................ 1397
Uplink EGPRS Data TBF Statistics ................ 1399

Overview.................................................................. 1402
requests on CCCH.............................................. 1402
requests on CCCH.............................................. 1402
due to ONE PHASE access................................... 1405
due to single block packet access......................... 1406
due to response paging ...................................... 1406
due to cell updating ........................................... 1407
due to mobility management............................... 1407
due to TWO PHASE access .................................. 1407
due to short access............................................ 1408
LXXXV

C901200019 Number of cell success for EGPRS UL
assignment due to ONE PHASE access .................. 1414
assignment due to single block packet access......... 1416
assignment due to response paging ..................... 1416
assignment due to cell updating .......................... 1416
assignment due to mobility management .............. 1417
assignment due to TWO PHASE access ................. 1417
assignment due to short access ........................... 1418
C901200026 Number of allocated PDCH for EGPRS UL TBF
establishment ................................................... 1420
failure due to BIU connection failed ..................... 1422
C901200030 Number of EGPRS UL TBF channel activate
failure due to not receive PIA .............................. 1424
failure on PCCCH/CCCH due to UPPB-DSP
congestion........................................................ 1425
C901200033 Number of EGPRS UL TBF establishment failure on PACCH due to UPPB-DSP congestion........... 1426
LXXXVI

success on PACCH ............................................. 1427
reallocation failure due to Abis congestion for DL
reallocation failure due to RR congestion for DL TBF
establishment ................................................... 1429
congestion for DL TBF establishment .................... 1430
reallocation success of channel allocation due to DL
C901200042 Number of allocated PDCH for EGPRS
UL TBF resource reallocation due to DL TBF
establishment ................................................... 1432
for DL TBF establishment.................................... 1433
connection for DL TBF establishment .................... 1436
C901200047 Number of EGPRS UL TBF resource reallocation failure due to DL TBF establishment ............... 1437
C901200048 Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment ............. 1437
transmission ..................................................... 1437
transmission ..................................................... 1438
LXXXVII

transmission ..................................................... 1440
C901200055 Number of allocated PDCH for EGPRS UL
TBF resource reallocation due to LLC transmission
....................................................................... 1441
reallocation success of channel activate for LLC
transmission ..................................................... 1445
reallocation requests for resource request ............. 1447
reallocation failure due to Abis congestion for
reallocation failure due to RR congestion for
congestion for resource request........................... 1449
reallocation success due to database allocation for
LXXXVIII

resource reallocation due to resource request......... 1451
for resource request........................................... 1452
connection for resource request........................... 1455
reallocation failure due to resource request ........... 1456
flush LL ............................................................ 1457
CS ................................................................... 1458
C901200078 Number of EGPRS UL TBF normal release
C901200079 Number of EGPRS UL TBF abnormal release
BVC unavailability .............................................. 1461
other reasons.................................................... 1461
C901200083 Number of UL EGPRS TBF grab
resources ......................................................... 1462
C901200084 Number of grab instance by UL EGPRS
TBF ................................................................. 1463
C901200085 Number of UL EGPRS TBF queuing ............ 1463
LXXXIX
C901200086 Number of UL EGPRS TBF queuing

success ............................................................ 1464
C901200087 Number of UL EGPRS TBF release TBF during
queuing............................................................ 1465
BSSGP Flow Statistic ................................... 1467

Overview.................................................................. 1468
C901210001 Number of paging PS message ................. 1468
C901210002 Number of paging CS message ................. 1468
C901210003 Number of Flush-LL Message received......... 1469
C901210004 Number of Flush-LL-ACK Message
sent................................................................. 1470
C901210005 Number of BVC-BLOCK message sent......... 1470
C901210006 Number of BVC-BLOCK-ACK message
received .......................................................... 1471
C901210007 Number of BVC-UNBLOCK message
sent................................................................. 1472
C901210008 Number of BVC-UNBLOCK-ACK message
received .......................................................... 1472
C901210009 Number of BVC-RESET message sent......... 1473
C901210010 Number of BVC-RESET-ACK message
received .......................................................... 1474
C901210011 Number of BVC-RESET message
received ........................................................... 1474
sent................................................................. 1475
C901210013 Number of PERFORM-LOCATION-REQUEST
message received .............................................. 1476
C901210014 Number of PERFORM-LOCATION-RESPONSE
message sent.................................................... 1477
C901210015 Number of PERFORM-LOCATION-ABORT
C901210016 Number of POSITION-COMMAND message
sent................................................................. 1479
C901210017 Number of POSITION-RESPONSE message
received ........................................................... 1480
C901210018 Number of Flush-LL received if UL/DL TBF
exist ................................................................ 1481
C901210019 Number of Flush-LL received if DL TBF
exist ................................................................ 1482
XC
C901210020 Number of Flush-LL received if UL TBF

exist ................................................................ 1483
C901210021 Number of reroute intra NSE .................... 1483
C901210022 Number of reroute inter NSE intra BSS
cell .................................................................. 1484
C901210023 Number of reroute inter NSE inter BSS
cell .................................................................. 1485
C901210024 LLC transfer bytes................................... 1485
C901210025 LLC transfer frames................................. 1486
C901210026 LLC transfer failed bytes .......................... 1486
C901210027 LLC transfer failed frames ........................ 1486
C901210028 LLC transfer failed num............................ 1487
C901210029 LLC transfer succeeded num..................... 1487
C901210030 LLC transfer via cell reselection................. 1488
C901210031 LLC transfer not via cell reselection ........... 1489
C901210032 LLC transfer fail Num via cell
reselection........................................................ 1489
C901210033 LLC transfer fail Num not via cell
reselection........................................................ 1490
GB Message Statistic ................................... 1491

Overview.................................................................. 1492
C901220001 Sum of UL UNITDATA messages handled at
BSSGP level ...................................................... 1493
C901220002 Sum of DL UNITDATA messages handled at
BSSGP level ...................................................... 1493
C901220003 Number of receiving RA-CAPABILITY
message .......................................................... 1494
C901220004 Number of PTP packet paging received by
BSC ................................................................. 1495
C901220005 Number of PTP circuit paging received by
BSC ................................................................. 1495
C901220006 Number of RA-CAPABILITY-UPDATE message
sent................................................................. 1496
C901220007 Number of RA-CAPABILITY-UPDATE-ACK
C901220008 Number of wireless status PDU messages
sent by BSC...................................................... 1497
C901220009 Number of wireless status messages sent
by BSC due to losing wireless association with
MS .................................................................. 1498
XCI
C901220010 Number of wireless status messages sent by

BSC due to bad link quality ................................. 1499
BSC due to cell reselection command ................... 1499
C901220012 Number of FLOW-CONTROL-BVC messages
sent by BSC...................................................... 1500
C901220013 Number of FLOW-CONTROL-BVC-ACK
messages received by BSC ................................. 1500
C901220014 Number of FLOW-CONTROL-MS messages
sent by BSC...................................................... 1501
C901220015 Number of FLOW-CONTROL-MS-ACK
C901220016 Number of FLOW-CONTROL-PFC messages
sent by BSC...................................................... 1503
C901220017 Number of FLOW-CONTROL-PFC-ACK
C901220018 Number of status messages sent by
BSC ................................................................. 1505
C901220019 Number of status messages received by
BSC ................................................................. 1506
C901220020 Number of status messages sent with BVCI
Unknown .......................................................... 1507
C901220021 Number of Status messages sent with cell
service congestion ............................................. 1507
C901220022 Number of status messages sent with
protocol error.................................................... 1508
Processor overload............................................. 1508
C901220024 Number of status messages received with
BVCI Unknown .................................................. 1508
cell service congestion........................................ 1509
protocol error.................................................... 1509
processor overload ............................................ 1509
C901220028 Number of DOWNLOAD-BSS-PFC messages
sent by BSC...................................................... 1510
C901220029 Number of BVCCREATE-BSS-PFC messages
received by BSC ................................................ 1511
XCII
C901220030 Number of CREATE-BSS-PFC-ACK messages

sent by BSC...................................................... 1511
C901220031 Number of CREATE-BSS-PFC-NACK
messages sent by BSC ....................................... 1512
C901220032 Number of MODIFY-BSS-PFC messages sent
by BSC............................................................. 1513
C901220033 Number of MODIFY-BSS-PFC-ACK messages
received by BSC ................................................ 1514
C901220034 Number of DELETE-BSS-PFC messages
received by BSC ................................................ 1515
C901220035 Number of DELETE-BSS-PFC-ACK messages
sent by BSC...................................................... 1516
C901220036 Number of DELETE-BSS-PFC-REQ messages
received by BSC ................................................ 1517
C901220037 Number of PS-HANDOVER-REQUIRED
C901220038 Number of PS-HANDOVER-REQUIRED-ACK
C901220039 Number of PS-HANDOVER-REQUIRED-NACK
C901220040 Number of PS-HANDOVER-REQUEST
C901220041 Number of PS-HANDOVER-REQUEST-ACK
C901220042 Number of PS-HANDOVER-REQUEST-NACK
C901220043 Number of PS-HANDOVER-COMPLETE
C901220044 Number of PS-HANDOVER-CANCEL
messages with Service UTRAN CCO received by
BSC ................................................................. 1525
C901220046 Number of CREATE-BSS-PFC messages with
Service UTRAN CCO received by BSC ................... 1526
TRX Measurement ....................................... 1529

Overview.................................................................. 1531
C901230001 Number of intra-cell handover in
attempts .......................................................... 1531
XCIII
C901230002 Number of intra-cell handover ins

success ............................................................ 1532
C901230003 Number of Intra-BSC inter-cell handover in
attempts .......................................................... 1532
C901230004 Number of Intra-BSC intra-cell handover ins
success ............................................................ 1533
C901230005 Number of Intra-MSC inter-cell handover in
attempts .......................................................... 1534
C901230006 Number of Intra-MSC inter-cell handover ins
success ............................................................ 1535
C901230007 TCH busy time........................................ 1535
C901230008 Number of TCH seizures (including
handover) ........................................................ 1536
C901230009 Number of call drops due to TCH LAPD
breakage .......................................................... 1536
C901230010 Number of call drops due to TCH radio link
failure .............................................................. 1537
C901230011 Number of TCH handover call drops........... 1537
C901230012 Number of TCH/F activation attempts
(including handover) .......................................... 1538
C901230013 Number of TCH/F activation success
C901230014 Number of TCH/F assignment
attempts .......................................................... 1540
C901230015 Number of TCH/F assignment success......... 1540
C901230016 Number of TCH/H activation attempts
C901230017 Number of TCH/H activation success
C901230018 Number of TCH/H assignment
attempts .......................................................... 1542
C901230019 Number of TCH/H assignment success......... 1543
C901230020 SDCCH busy time ................................... 1544
C901230021 Number of attempts for SDCCH ................ 1545
C901230022 Number of SDCCH call drops .................... 1545
C901230023 Number of SDCCH activation attempts
C901230024 Number of SDCCH activation success
XCIV

attempts .......................................................... 1548
success ............................................................ 1549
C901230027 Number of samples with UL RQ = 0 ........... 1549
C901230035 Number of samples with DL RQ = 0........... 1554
XCV

C901230061 Number of TRX poweroff .......................... 1565
C901230062 Duration of TRX poweroff ......................... 1565
FR_V1.............................................................. 1566
FR_V1.............................................................. 1566
FR_V2.............................................................. 1566
FR_V2.............................................................. 1567
FR_V3.............................................................. 1567
FR_V3.............................................................. 1567
HR_V1 ............................................................. 1568
HR_V1 ............................................................. 1568
HR_V3 ............................................................. 1568
HR_V3 ............................................................. 1569
Timeslot Measurement ................................ 1571

Overview.................................................................. 1572
XCVI
C901240001 Maximum value of UL RQ ......................... 1572

C901240002 Minimum value of UL RQ .......................... 1573
C901240003 Value of UL RQ ....................................... 1573
C901240004 Number of scans of UL RQ........................ 1574
C901240005 Maximum value of DL RQ ......................... 1575
C901240006 Minimum value of DL RQ.......................... 1575
C901240007 Value of DL RQ ....................................... 1576
C901240008 Number of scans of DL RQ ....................... 1576
C901240009 Maximum value of received UL signal
strength ........................................................... 1577
C901240010 Minimum value of received UL signal
strength ........................................................... 1578
C901240011 Total value of received UL signal
strength ........................................................... 1578
samples ........................................................... 1579
C901240013 Maximum value of received DL signal
strength ........................................................... 1580
C901240014 Minimum value of received DL signal
strength ........................................................... 1580
C901240015 Total value of received DL signal
strength ........................................................... 1581
samples ........................................................... 1581
C901240017 Value of power scans of MS transmitting
power .............................................................. 1582
C901240018 Number of power scans of MS transmitting
power .............................................................. 1583
C901240019 Value of power scans of BTS power ........... 1583
C901240020 Number of power scans of BTS power......... 1584
C901240021 Number of immediate assignment
failure .............................................................. 1584
C901240022 Number of assignment failure ................... 1585
C901240023 Number of handovers failure .................... 1586
C901240024 Maximum interference value..................... 1587
C901240025 Minimum interference value ..................... 1587
C901240026 Interference value................................... 1588
C901240027 Number of regular scanning and sampling of
interference value.............................................. 1589
C901240028 Number of call drop................................. 1589
XCVII
C901240029 Maximum value of path balance ................ 1590

C901240030 Minimum value of path balance................. 1590
C901240031 Value of path balance .............................. 1591
path balance ..................................................... 1592
C901240033 Value of UL loss ...................................... 1592
UL loss ............................................................. 1593
C901240035 Total value of DL loss............................... 1593
DL loss............................................................. 1594
C901240037 Number of drops due to the bad quality of
UL receive ........................................................ 1595
C901240038 Number of drops due to the bad quality of
DL receive ........................................................ 1596
C901240039 Number of drops due to the low electric level
of UL ............................................................... 1598
C901240040 Number of drops due to the low electric level
of DL ............................................................... 1600
C901240041 Number of drops due to the TA too far......... 1602
C901240042 Number of drops due to the other radio
reasons ............................................................ 1604
C901240043 The valid time of the used voice
channel ............................................................ 1606
C901240044 Number of activated voice channel ............ 1607
SDCCH Measurement ................................... 1609

Overview.................................................................. 1610
C901250005 Number of SDCCH seizure success for
Handover ......................................................... 1611
C901250007 Number of SDCCH allocation attempts for
Assignment....................................................... 1613
C901250010 Number of SDCCH allocation attempts for
handover.......................................................... 1614
C901250011 Number of SDCCH allocation success for
handover.......................................................... 1616
C901250012 Number of SDCCH allocation failure for
handover.......................................................... 1617
C901250016 Number of SDCCH handover failure ........... 1618
C901250017 Number of SDCCH handover success ......... 1620
XCVIII
C901250018 Number of SDCCH handover failure with

Reconnection .................................................... 1622
C901250019 Number of SDCCH handover failure without
Reconnection .................................................... 1622
C901250020 Number of SDCCH assignment attempts
(MOC).............................................................. 1623
C901250021 Number of successful SDCCH assignments
(MOC).............................................................. 1624
C901250022 Number of unsuccessful SDCCH assignments
(MOC).............................................................. 1625
(MTC) .............................................................. 1626
(MTC) .............................................................. 1627
(MTC) .............................................................. 1628
(call re-establishment) ....................................... 1629
(emergency call) ............................................... 1632
(emergency call) ............................................... 1633
(emergency call) ............................................... 1634
(LOC)............................................................... 1635
(LOC)............................................................... 1636
(LOC)............................................................... 1637
(other cause) .................................................... 1638
(other cause) .................................................... 1639
(other cause) .................................................... 1640
XCIX
C901250038 Count of USSD attempts to connect........... 1641

C901250039 Average dialoge time of USSD
services ........................................................... 1642
C901250040 Dialog counts of USSD services................. 1642
TCH/F Measurement ................................... 1643

Overview.................................................................. 1647
C901260002 Number of signaling TCH/F seizure success
for assignment .................................................. 1650
C901260005 Number of signaling TCH/F seizure success
for handover ..................................................... 1651
attempts for assignment..................................... 1653
attempts for handover........................................ 1654
success for handover ......................................... 1657
attempts for assignment..................................... 1659
C901260016 Number of signaling TCH/F handover
attempt............................................................ 1660
C901260017 Number of signaling TCH/F handover
success ............................................................ 1663
C901260018 Number of signaling TCH/F handover failure
with reconnection .............................................. 1665
without reconnection.......................................... 1667
C901260021 Number of voice TCH/F seizure success for
assignment....................................................... 1668
C901260024 Number of voice TCH/F seizure success for
handover.......................................................... 1669
C901260026 Number of TCH/F allocation attempts for
assignment (speech version 1) ............................ 1672
C901260032 Number of TCH/F allocation attempts by
BSC for handover (speech version 1).................... 1673
C901260033 Number of TCH/F allocation success by BSC
for handover (speech version 1) .......................... 1676
C901260038 Number of TCH/F allocation attempts for

BSC for assignment (speech version 3)................. 1685
C901260062 Number of voice TCH/F assignment attempts
by BSC............................................................. 1691
C901260065 Number of voice TCH/F handover
attempts .......................................................... 1692
C901260067 Number of Voice TCH/F handover
failure .............................................................. 1695
C901260068 Number of Voice TCH/F handover failure
messages do not received by BSC........................ 1697
C901260070 Number of data TCH/F seizure success for
assignment....................................................... 1698
C901260073 Number of data TCH/F seizure success for
handover.......................................................... 1699
C901260075 Number of data TCH/F allocation attempts
for assignment .................................................. 1702
C901260081 Number of data TCH/F allocation attempts
by BSC for handover .......................................... 1703
handover.......................................................... 1706
attempts .......................................................... 1708
attempts .......................................................... 1709
failure .............................................................. 1712
C901260093 Number of data TCH/F handover failure
C901260094 Number of data TCH/F allocation failure for
assignment due to TIPB connection failure (Speech
version 1)......................................................... 1715
assignment due to Resource request to iTC failure
(Speech version 1) ............................................ 1716
CI

handover due to TIPB connection failure (Speech
version 1)......................................................... 1717
handover due to Resource request to iTC failure
(Speech version 1) ............................................ 1718
version 2)......................................................... 1719
(Speech version 2) ............................................ 1720
version 2)......................................................... 1721
(Speech version 2) ............................................ 1723
version 3)......................................................... 1724
(Speech version 3) ............................................ 1725
version 3)......................................................... 1726
(Speech version 3) ............................................ 1728
to request AIPB resource failure for assignment
(speech version 1) ............................................. 1729
request UDP port failure for assignment (speech
version 1)......................................................... 1730
AIPB connection failure for assignment (speech
version 1)......................................................... 1731
CII

request AIPB resource failure for handover (speech
version 1)......................................................... 1732
to request UDP port failure for handover (speech
version 1)......................................................... 1733
to AIPB connection failure for handover (speech
version 1)......................................................... 1734
(speech version 2) ............................................. 1735
version 2)......................................................... 1736
version 2)......................................................... 1737
version 2)......................................................... 1738
version 2)......................................................... 1739
version 2)......................................................... 1740
(speech version 3) ............................................. 1741
version 3)......................................................... 1742
version 3)......................................................... 1743
version 3)......................................................... 1744
CIII

version 3)......................................................... 1745
version 3)......................................................... 1746
(data) .............................................................. 1747
to request UDP port failure for assignment
(data) .............................................................. 1748
C901260126 Number of TCH/F allocation failure
due to AIPB connection failure for assignment
(data) .............................................................. 1748
to request AIPB resource failure for handover
(data) .............................................................. 1749
request UDP port failure for handover (data) ......... 1750
AIPB connection failure for handover (data) .......... 1751
C901260130 Number of assign TCH/F release by forced
handover to forced handover source .................... 1752
handover to queuing user ................................... 1752
C901260132 Number of restore TCH/F release by forced
handover to DBS ............................................... 1753
C901260133 Number of assign TCHF release by forced
release to forced release source .......................... 1753
release to queuing user ...................................... 1754
C901260135 Number of restore TCH/F release by forced
release to DBS .................................................. 1754
for assignment (cause:Abis)................................ 1755
for handover (cause:Abis)................................... 1756
assignment (cause:Abis) .................................... 1756
CIV

handover (cause:Abis ) ...................................... 1757
handover (cause:Abis) ....................................... 1758
for assignment (cause:radio resource).................. 1758
for handover (cause:radio resource)..................... 1759
assignment (cause:radio resource) ...................... 1759
handover (cause:radio resource) ......................... 1760
C901260148 Number of FR_V1 assignment
attempts .......................................................... 1761
C901260149 Number of FR_V1 assignment success......... 1762
attempts .......................................................... 1762
attempts .......................................................... 1763
C901260154 Number of FR_V1 handover...................... 1764
C901260155 Number of FR_V1 handover success .......... 1764
C901260185 Resourse releasing of ordinary users due to
being grabbed (TCH/F) ....................................... 1767
C901260186 Handover of ordinary users due to be
grabbed (TCH/F) ............................................... 1768
C901260187 Number of Channel Request of priority users
(TCH/F)............................................................ 1769
CV
C901260188 Number of Successful Channel seize of

priority users (TCH/F) ........................................ 1771
C901260189 Number of Successful grabbing channel of
priority users (TCH/F) ........................................ 1772
TCH/H Measurement ................................... 1775

Overview.................................................................. 1779
C901270002 Number of signaling TCH/H seizure success
for assignment .................................................. 1782
C901270005 Number of signaling TCH/H seizure success
for handover ..................................................... 1783
C901270007 Number of signaling TCH/H allocation
attempts by BSC for assignment.......................... 1785
success for assignment ...................................... 1786
attempts by BSC due to handover........................ 1787
success due to handover .................................... 1790
C901270012 Number of signaling TCH/H allocation failure
due to handover ................................................ 1792
attempts by BSC ............................................... 1793
C901270016 Number of signaling TCH/H handover
attempts .......................................................... 1794
success ............................................................ 1797
failure .............................................................. 1799
C901270019 Number of signaling TCH/H handover failure
C901270021 Number of voice TCH/H seizure success for
assignment....................................................... 1802
C901270024 Number of voice TCH/H seizure success for
handover.......................................................... 1803
C901270026 Number of TCH/H allocation attempts for
assignment by BSC (speech version 1) ................. 1806
C901270027 Number of TCH/H allocation success for
assignment (speech version1) ............................. 1807
C901270032 Number of TCH/H allocation attempts by
BSC during handover (speech version 1)............... 1809
CVI
C901270033 Number of TCH/H allocation success during

handover (speech version 1) ............................... 1811
BSC for assignment (speech version 2)................. 1813
C901270039 Number of TCH/H allocation success by BSC
for assignment (speech version 2) ....................... 1815
handover by BSC (speech version 2) .................... 1816
attempts by BSC ............................................... 1829
attempts .......................................................... 1831
failure .............................................................. 1833
C901270068 Number of Voice TCH/H handover failure
C901270070 Number of data TCH/H seizure success for
assignment....................................................... 1836
C901270073 Number of data TCH/H seizure success for
handover.......................................................... 1837
C901270075 Number of data TCH/H allocation attempts
for assignment by BSC ....................................... 1840
C901270076 Number of data TCH/H allocation success for
assignment....................................................... 1841
C901270081 Number of data TCH/H allocation attempts
by BSC............................................................. 1843
handover.......................................................... 1845
C901270087 Number of data TCH/H assignment attempts
by BSC............................................................. 1848
CVII

attempts .......................................................... 1849
failure .............................................................. 1852
C901270093 Number of data TCH/H handover failure do
not received by BSC........................................... 1853
C901270094 Number of TCH/H allocation failure for
version 1)......................................................... 1855
(Speech version 1) ............................................ 1856
version 1)......................................................... 1857
(Speech version 1) ............................................ 1858
version 2)......................................................... 1860
(Speech version 2) ............................................ 1861
version 2)......................................................... 1862
(Speech version 2) ............................................ 1863
version 3)......................................................... 1865
(Speech version 3) ............................................ 1866
version 3)......................................................... 1867
CVIII

(Speech version 3) ............................................ 1868
(speech version 1) ............................................. 1869
version 1)......................................................... 1870
version 1)......................................................... 1871
version 1)......................................................... 1872
version 1)......................................................... 1873
version 1)......................................................... 1874
(speech version 2) ............................................. 1875
version 2)......................................................... 1876
version 2)......................................................... 1877
version 2)......................................................... 1878
version 2)......................................................... 1879
version 2)......................................................... 1880
CIX

(speech version 3) ............................................. 1881
version 3)......................................................... 1882
version 3)......................................................... 1883
version 3)......................................................... 1884
version 3)......................................................... 1885
version 3)......................................................... 1886
(data) .............................................................. 1887
C901270125 Number of TCH/H allocation failure
due to request UDP port failure for assignment
(data) .............................................................. 1888
C901270126 Number of TCH/H allocation failure
due to AIPB connection failure for assignment
(data) .............................................................. 1888
to request AIPB resource failure for handover
(data) .............................................................. 1889
request UDP port failure for handover (data) ......... 1890
AIPB connection failure for handover (data) .......... 1891
C901270130 Number of assign TCH/H release by forced
handover to forced handover source .................... 1892
handover to queuing user ................................... 1892
C901270132 Number of restore TCH/H release by forced
handover to DBS ............................................... 1893
CX

release to forced release source .......................... 1893
release to queuing user ...................................... 1894
C901270135 Number of restore TCH/H release by forced
release to DBS .................................................. 1894
C901270136 Number of signaling TCH/H seize failure for
assign due to Abis lack ....................................... 1895
handover due to Abis lack................................... 1895
handover (cause:Abis ) ...................................... 1896
handover (cause:Abis) ....................................... 1897
assign due to radio resource lack ......................... 1898
handover due to radio resource lack..................... 1898
C901270148 Number of HR_V1 assignment
attempts .......................................................... 1901
success ............................................................ 1901
attempts .......................................................... 1901
success ............................................................ 1902
C901270152 Number of HR_V1 handover ..................... 1902
C901270153 Number of HR_V1 handover success.......... 1903
CXI
C901270154 Number of HR_V3 handover ..................... 1903

C901270155 Number of HR_V3 handover success.......... 1904
C901270177 Resource releasing of ordinary users due to
being grabbed (TCH/H) ...................................... 1904
C901270178 Handover of ordinary users due to being
grabbed (TCH/H) ............................................... 1905
(TCH/H) ........................................................... 1907
C901270180 Number of Successful Channel seize of
priority users (TCH/H) ........................................ 1908
C901270181 Number of Successful grabbing channel of
priority users (TCH/H) ........................................ 1909
Abis Interface Message Counter

Measurement .............................................. 1911
Overview.................................................................. 1914
C901280001 Number of DATA REQUEST messages......... 1915
C901280002 Number of DATA INDICATION
messages ......................................................... 1916
C901280003 Number of ERROR INDICATION
messages ......................................................... 1916
C901280004 Number of ESTABLISH REQUEST
messages ......................................................... 1917
C901280005 Number of ESTABLISH CONFIRM
messages ......................................................... 1918
C901280006 Number of ESTABLISH INDICATION
messages ......................................................... 1918
C901280007 Number of RELEASE REQUEST
messages ......................................................... 1919
C901280008 Number of RELEASE CONFIRM
messages ......................................................... 1920
C901280009 Number of RELEASE INDICATION
messages ......................................................... 1920
C901280010 Number of UNIT DATA REQUEST
messages ......................................................... 1921
C901280011 Number of UNIT DATA INDICATION
messages ......................................................... 1922
C901280012 Number of CHANNEL ACTIVATION
messages ......................................................... 1922
C901280013 Number of CHANNEL ACTIVATION ACK
messages ......................................................... 1923
CXII
C901280014 Number of CHANNEL ACTIVATION Negative

ACK messages .................................................. 1924
C901280015 Number of CONNECTION FAILURE
INDICATION messages ....................................... 1924
C901280016 Number of DEACTIVATE SACCH
messages ......................................................... 1925
C901280017 Number of ENCRYPTION COMMAND
messages ......................................................... 1926
C901280018 Number of HANDOVER DETECTION
messages ......................................................... 1926
C901280019 Number of MEASUREMENT RESULT
messages ......................................................... 1927
C901280020 Number of MODE MODIFY REQUEST
messages ......................................................... 1928
C901280021 Number of MODE MODIFY ACK
messages ......................................................... 1929
C901280022 Number of MODE MODIFY NACK
messages ......................................................... 1929
C901280023 Number of PHYSICAL CONTEXT REQUEST
messages ......................................................... 1930
C901280024 Number of PHYSICAL CONTEXT CONFIRM
messages ......................................................... 1931
C901280025 Number of RF CHANNEL RELEASE
messages ......................................................... 1931
C901280026 Number of MS POWER CONTROL
messages ......................................................... 1932
C901280027 Number of BS POWER CONTROL
messages ......................................................... 1933
C901280028 Number of PREPROCESSED CONFIGURE
messages ......................................................... 1933
C901280029 Number of PREPROCESSED MEASUREMENT
RESULT messages ............................................. 1934
C901280030 Number of RF CHANNEL RELEASE ACK
messages ......................................................... 1935
C901280031 Number of SACCH INFO MODIFY
messages ......................................................... 1936
C901280032 Number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages .................................... 1936
C901280033 Number of ABIS_ROUND_TRIP_DELAY_REPORT messages................................................. 1937
CXIII
C901280034 Number of ABIS_PRE_HO_NOTIFY

messages ......................................................... 1938
C901280035 Number of ABIS_BCCH_INFO
messages ......................................................... 1938
C901280036 Number of ABIS_CCCH_LOAD_IND
messages ......................................................... 1939
C901280037 Number of ABIS_CHL_RQD messages......... 1940
C901280038 Number of ABIS_DELETE_IND
messages ......................................................... 1940
C901280039 Number of ABIS_PAGING_CMD
messages ......................................................... 1941
C901280040 Number of ABIS_IMM_ASSIGN_CMD
messages ......................................................... 1942
C901280041 Number of ABIS_SMS_BROADCAST_REQ
messages ......................................................... 1942
C901280042 Number of ABIS_SMS_BROADCAST_CMD
messages ......................................................... 1943
C901280043 Number of ABIS_CBCH_LOAD_IND
messages ......................................................... 1944
C901280044 Number of ABIS_EGPRS_CHL_REQ
messages ......................................................... 1944
C901280045 Number of ABIS_LOAD_CONTROL
messages ......................................................... 1945
C901280046 Number of ABIS_END_LOAD_CONTROL
messages ......................................................... 1946
C901280047 Number of ABIS_END_LOAD_CONTROL_ACK
messages ......................................................... 1946
C901280048 Number of ABIS_PCCCH_LOAD_IND
messages ......................................................... 1947
C901280049 Number of ABIS_RF_RESRC_IND
messages ......................................................... 1948
C901280050 Number of ABIS_SACCH_FILLING
messages ......................................................... 1948
C901280051 Number of ABIS_OVERLOAD
messages ......................................................... 1949
C901280052 Number of ABIS_ERROR_REPORT
messages ......................................................... 1950
C901280053 Number of ABIS_SYSINFO_REQ
messages ......................................................... 1950
CXIV
C901280054 Number of ABIS_SI_BC_END

messages ......................................................... 1951
C901280055 Number of ABIS_SI_NACK messages......... 1952
C901280056 Number of ABIS_PWRCTRL_IND
messages ......................................................... 1952
C901280057 Number of ABIS_SYSINFO_ACK
messages ......................................................... 1953
C901280061 Number of ABIS_PACKET_PBCCH_INF
messages ......................................................... 1954
C901280062 Number of ABIS_PACKET_CCCH_PARA
messages ......................................................... 1954
C901280063 Number of ABIS_PACKET_PBCCH_PARA
messages ......................................................... 1955
C901280064 Number of ABIS_PACKET_CHN_REQ
messages ......................................................... 1956
C901280065 Number of ABIS_PACKET_PAGING_CMD
messages ......................................................... 1956
C901280066 Number of ABIS_PACKET_IMM_ASSIGN_CMD messages......................................... 1957
C901280067 Number of ABIS_PACKET_CONNECT_FAIL_IND messages .................................. 1958
C901280068 Number of ABIS_PACKET_PRACH_OVERLOAD messages ................................................ 1958
C901280069 Number of ABIS_PACKET_PCH_OVERLOAD
messages ......................................................... 1959
C901280070 Number of ABIS_PACKET_TA_REQUEST
messages ......................................................... 1960
C901280071 Number of ABIS_PACKET_TA_REQUEST_ACK
messages ......................................................... 1960
C901280072 Number of ABIS_PACKET_CHN_CONFIG_CHG messages ........................................... 1961
C901280073 Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages .................................. 1962
C901280074 Number of ABIS_PACKET_PIA_DEL_IND
messages ......................................................... 1962
C901280075 Number of ABIS_PACKET_SEND_PIA_IND
messages ......................................................... 1963
C901280076 Number of ABIS_PACKET_CHN_CONFIG_REQ messages............................................ 1964
CXV
C901280077 Number of ABIS_EGPRS_PACKET_CHN_REQ

messages ......................................................... 1964
C901280078 Number of ABIS_PS_CHANNEL_ACTIVE
messages ......................................................... 1965
C901280079 Number of ABIS_PS_CHANNEL_ACTIVE_ACK
messages ......................................................... 1966
C901280080 Number of ABIS_PS_CHANNEL_ACTIVE_NACK messages ........................................ 1966
C901280081 Number of ABIS_PS_CHANNEL_RELEASE
messages ......................................................... 1967
C901280082 Number of ABIS_PS_CHANNEL_RELEASE_ACK messages ........................................ 1968
C901280083 Number of ABIS_PS_CHANNEL_RELEASE_NACK messages...................................... 1968
C901280084 Number of ABIS_PSCONN_CMM_REQ
messages ......................................................... 1969
C901280085 Number of ABIS_PSCONN_CMM_ACK
messages ......................................................... 1970
C901280086 Number of ABIS_PSCONN_CMM_NACK
messages ......................................................... 1970
C901280087 Number of ABIS_GLOBAL_RESET
messages ......................................................... 1971
C901280088 Number of ABIS_GLOBAL_RESET_ACK
messages ......................................................... 1972
C901280089 Number of ABIS_GLOBAL_RESET_NACK
messages ......................................................... 1972
C901280090 Number of ABIS_PACKET_UP_ASSIGN
messages ......................................................... 1973
C901280091 Number of ABIS_PACKET_DOWN_ASSIGN
messages ......................................................... 1974
C901280092 Number of ABIS_CSCONN_CMM_REQ
messages ......................................................... 1974
C901280093 Number of ABIS_CSCONN_CMM_ACK
messages ......................................................... 1975
C901280094 Number of ABIS_CSCONN_CMM_NACK
messages ......................................................... 1976
C901280095 Number of ABIS_CCMCONN_CMM_REQ
messages ......................................................... 1976
C901280096 Number of ABIS_CCMCONN_CMM_ACK
messages ......................................................... 1977
CXVI
C901280097 Number of ABIS_CCMCONN_CMM_NACK

messages ......................................................... 1978
C901280098 Number ABIS_PACKET_ACCESS_REJ
messages ......................................................... 1978
C901280099 Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages ................................ 1979
C901280100 Number of PACKET_DOWNLINK_ASSIGN
messages ......................................................... 1980
C901280101 Number of PACKET_UPLINK_ASSIGN
messages ......................................................... 1980
C901280102 Number of ABIS_PACKET_ACCESS_REJ_NEW messages.................................. 1981
Gb Message Statistics (BVC Cell)................. 1983

Overview.................................................................. 1984
BSSGP level ...................................................... 1984
BSSGP level ...................................................... 1985
C901290003 Number of RA-CAPABILITY message
received ........................................................... 1986
BSC ................................................................. 1986
BSC ................................................................. 1987
sent................................................................. 1987
C901290008 Number of Wireless Status PDU messages
sent by BSC...................................................... 1989
C901290009 Number of Wireless Status messages sent
by BSC due to Losing Wireless Association with
MS .................................................................. 1989
BSC due to Bad Link Quality................................ 1990
C901290011 Number of Wireless status messages sent
by BSC due to Cell reselection command .............. 1990
sent by BSC...................................................... 1991
CXVII

sent by BSC...................................................... 1992
sent by BSC...................................................... 1993
C901290018 Number of Status messages sent by
BSC ................................................................. 1995
C901290019 Number of Status messages received by
BSC ................................................................. 1995
C901290020 Number of Status messages sent with BVCI
Unknown .......................................................... 1996
C901290021 Number of Status messages sent with Cell
C901290022 Number of Status messages sent with
protocol error.................................................... 1997
C901290023 Number of Status messages sent with
C901290024 Number of Status messages received with
BVCI Unknown .................................................. 1997
Cell service congestion ....................................... 1998
protocol error.................................................... 1998
sent by BSC...................................................... 1999
received by BSC ................................................ 1999
sent by BSC...................................................... 2000
by BSC............................................................. 2001
CXVIII

received by BSC ................................................ 2002
received by BSC ................................................ 2003
C901290035 Number of DELETE -BSS-PFC-ACK messages
sent by BSC...................................................... 2003
C901290036 Number of DELETE -BSS-PFC-REQ messages
received by BSC ................................................ 2004
NSVC Statistic Measurement ....................... 2005

Overview.................................................................. 2006
C901300001 Time of PVC unavailable........................... 2006
C901300002 Time of PVC congestion frame relay........... 2007
C901300003 Time of PVC congestion of level 1.............. 2008
C901300004 Number of bytes received from SGSN......... 2008
C901300005 Number of bytes sent to SGSN ................. 2008
C901300006 Number of PDU data sent by NS sub
layer ................................................................ 2009
C901300007 Number of PDU data received by NS sub
layer ................................................................ 2010
C901300008 Number of PDU data discarded by NS sub
layer ................................................................ 2010
C901300009 Number of reset messages send to opposite
end by NS sub layer........................................... 2011
C901300010 Number of received reset messages sent by
opposite end ..................................................... 2012
C901300011 Number of reset confirm messages send to
opposite end by NS sub layer .............................. 2012
C901300012 Number of received reset confirm messages
sent by opposite end.......................................... 2013
C901300013 Number of blocking messages send to
C901300014 Number of received blocking messages sent
by opposite end................................................. 2014
C901300015 Number of blocking confirm messages send
to opposite end by NS sub layer .......................... 2015
C901300016 Number of received blocking confirm
messages sent by opposite end ........................... 2016
C901300017 Number of unblocking messages send to
CXIX
C901300018 Number of received unblocking messages

sent by opposite end.......................................... 2017
C901300019 Number of unblocking confirm messages
send to opposite end by NS sub layer ................... 2018
C901300020 Number of received unblocking acknowledge
messages replied by opposite end........................ 2018
C901300021 Number of abnormal cases in NS
transmission due to network fault ........................ 2019
transmission due to O&M interference .................. 2020
transmission due to equipment fault..................... 2021
transmission due to NSVC block .......................... 2021
transmission due to unknown NSVC ..................... 2022
transmission due to protocol error ....................... 2023
C901300027 Number of test failure (while over
max) ............................................................... 2023
C901300028 Number of blocking procedure failure (after
exceeding the maximum times)........................... 2024
C901300029 Number of unblocking procedure failure
(after exceeding the maximum times) .................. 2025
C901300030 Number of congestion occurrence of level
1 ..................................................................... 2026
C901300031 Number of congestion recovery of level
1 ..................................................................... 2026
2 ..................................................................... 2027
2 ..................................................................... 2027
3 ..................................................................... 2027
3 ..................................................................... 2027
C901300036 Number of BECN..................................... 2028
C901300037 Number of FECN ..................................... 2028
NSE Statistic Measurement ......................... 2031

Overview.................................................................. 2032
CXX
C901310001 Number of CS Paging received by BSS......... 2033

C901310002 Number of PS Paging received by BSS......... 2033
C901310003 Number of SUSPEND message sent ........... 2034
C901310004 Number of SUSPEND-ACK message
received ........................................................... 2034
C901310005 Number of SUSPEND-NACK message
received ........................................................... 2035
C901310006 Number of RESUME message sent ............. 2036
C901310007 Number of RESUME-ACK message
received ........................................................... 2036
C901310008 Number of RESUME-NACK message
received ........................................................... 2037
C901310009 Number of FLUSH-LL message
received ........................................................... 2038
C901310010 Number of FLUSH-LL-ACK message
sent................................................................. 2038
C901310011 Number of LLC-DISCARDED message
sent................................................................. 2039
C901310013 Number of BVC_BLOCK_ACK message
received ........................................................... 2040
sent................................................................. 2041
received ........................................................... 2041
received ........................................................... 2042
sent................................................................. 2043
received ........................................................... 2044
C901310020 Number of PERFORM_LOCATION_REQUEST
C901310021 Number of PERFORM_LOCATION_RESPONSE
message sent.................................................... 2045
C901310022 Number of PERFORM_LOCATION_ABORT
C901310023 Number of POSITION_COMMAND message
sent................................................................. 2046
CXXI
C901310024 Number of POSITION_RESPONSE message

received ........................................................... 2047
C901310025 Number of status messages sent............... 2048
C901310026 Number of status messages received ......... 2048
Unknown .......................................................... 2049
C901310028 Number of status messages sent with cell
protocol error.................................................... 2050
semantically incorrect PDU.................................. 2051
C901310032 Number of status messages sent with invalid
mandatory information element........................... 2051
missing mandatory IE ........................................ 2052
missing conditional IE ........................................ 2052
unexpected conditional IE ................................... 2053
conditional IE error ............................................ 2053
protocol status incompatible error........................ 2054
BVCI unknown .................................................. 2054
protocol error.................................................... 2055
BVC blocking..................................................... 2056
invalid mandatory IE .......................................... 2057
CXXII

SGSN congestion ............................................... 2059
BTS TRX Measurement ................................ 2061

Overview.................................................................. 2062
C901320001 Number of normal increases of MS power
due to UL signal level ......................................... 2063
C901320002 Number of rapid increase in MS power due
to UL signal level ............................................... 2064
C901320003 Number of normal decrease of MS power
due to UL signal level ......................................... 2065
C901320004 Number of rapid decrease in MS power due
to UL signal level ............................................... 2066
C901320005 Number of normal increases of BS power
due to DL signal level ......................................... 2067
C901320006 Number of rapid increase in BS power due
to DL signal level ............................................... 2068
C901320007 Number of normal decrease of BS power
due to DL signal level ......................................... 2069
C901320008 Number of rapid decrease in BS power due
to DL signal level ............................................... 2070
C901320009 Number of normal increases of MS power
due to UL signal quality ...................................... 2071
C901320010 Number of rapid increase in MS power due
to UL signal quality ............................................ 2072
C901320011 Number of normal decrease of MS power
due to UL signal quality ...................................... 2073
C901320012 Number of rapid decrease in MS power due
to UL signal quality ............................................ 2074
C901320013 Number of normal increases of BS power
due to DL signal quality ...................................... 2075
CXXIII
C901320014 Number of rapid increase in BTS power due

to DL signal quality ............................................ 2076
C901320015 Number of normal decrease of BS power
due to DL signal quality ...................................... 2077
C901320016 Number of rapid decrease in BTS power due
to DL signal quality ............................................ 2078
C901320017 Total value of each result of regular scanning
of MS utilization power ....................................... 2079
MS utilization power........................................... 2080
C901320019 Total value of each result of regular scanning
of BS utilization power ....................................... 2081
BS utilization power ........................................... 2082
C901320021 Total value of power scans of DL signal
level ................................................................ 2083
C901320022 Number of power scans of DL signal
level ................................................................ 2084
C901320023 Total value of power scans of UL signal
level ................................................................ 2085
C901320024 Number of power scans of UL signal
level ................................................................ 2086
quality ............................................................. 2087
C901320026 Number of power scans of DL signal
quality ............................................................. 2088
quality ............................................................. 2089
C901320028 Number of power scans of UL signal
quality ............................................................. 2090
C901320029 Maximum value of UL signal level in regular
scan ................................................................ 2091
C901320030 Minimum value of UL signal level in regular
scan ................................................................ 2092
C901320031 Maximum value obtained in regular scan of
DL signal level................................................... 2093
C901320032 Minimum value obtained in regular scan of
DL signal level................................................... 2094
C901320033 Sum of Periodic BS Power (TCH/F) Search
Result .............................................................. 2095
CXXIV
C901320034 Periodic BS Power (TCH/F) Search

Times .............................................................. 2095
C901320035 Sum of Periodic BS Power (TCH/H) Search
Result .............................................................. 2096
C901320036 Number of Periodic BS Power (TCH/H)
Search ............................................................. 2096
C901320037 Sum of Periodic BS Power (SDCCH) Search
Result .............................................................. 2097
C901320038 Number of Periodic BS Power (SDCCH)
Search ............................................................. 2097
C901320039 Sum of Periodic DL Signal Level (TCH/F)
Search Result.................................................... 2097
C901320040 Number of Periodic DL Signal Level (TCH/F)
Search ............................................................. 2098
C901320041 Sum of Periodic DL Signal Level (TCH/H)
Search Result.................................................... 2098
C901320042 Number of Periodic DL Signal Level (TCH/H)
Search ............................................................. 2099
C901320043 Sum of Periodic DL Signal Level (SDCCH)
Search Result.................................................... 2099
C901320044 Number of Periodic DL Signal Level (SDCCH)
Search ............................................................. 2099
NSVC on IPGB HOST Measurement .............. 2101

Overview.................................................................. 2101
C901330001 Time of PVC unavailable........................... 2101
transmission due to network fault ........................ 2102
transmission due to O&M interference .................. 2102
transmission due to equipment fault..................... 2103
transmission due to unknown NSVC ..................... 2103
transmission due to protocol error ....................... 2103
C901330007 Number of unsuccess test due to over
max................................................................. 2104
GB Message on IPGB HOST Measurement ........................................................... 2105

Overview.................................................................. 2106
CXXV
C901340001 Number of RA-CAPABILITY message

recevied ........................................................... 2107
BSC ................................................................. 2107
BSC ................................................................. 2108
sent................................................................. 2108
C901340006 Number of wireless status PDU messages
sent by BSC...................................................... 2110
C901340007 Number of wireless status messages sent
by BSC due to losing wireless association with
MS .................................................................. 2110
BSC due to bad link quality ................................. 2111
BSC due to cell reselection command ................... 2111
sent by BSC...................................................... 2112
sent by BSC...................................................... 2113
sent by BSC...................................................... 2114
C901340016 Number of status messages sent by
BSC ................................................................. 2116
BSC ................................................................. 2116
Unknown .......................................................... 2117
CXXVI

protocol error.................................................... 2118
BVCI Unknown .................................................. 2118
protocol error.................................................... 2119
sent by BSC...................................................... 2120
received by BSC ................................................ 2121
sent by BSC...................................................... 2121
by BSC............................................................. 2123
received by BSC ................................................ 2123
received by BSC ................................................ 2124
sent by BSC...................................................... 2125
C901340034 Number of DELETE-BSS-PFC-REQ messages
received by BSC ................................................ 2125
C901340035 Number of PS-HANDOVER-REQUIRED
C901340039 Number of PS-HANDOVER-REQUEST-ACK
CXXVII

C901340041 Number of PS-HANDOVER-COMPLETE
C901340042 Number of PS-HANDOVER-CANCEL
messages with Service UTRAN CCO received by
BSC ................................................................. 2133
NSE on IPGB HOST Measurement ................ 2137

Overview.................................................................. 2138
C901350001 Number of CS Paging received by BSS......... 2139
C901350002 Number of PS Paging received by BSS......... 2139
received ........................................................... 2140
received ........................................................... 2140
received ........................................................... 2141
received ........................................................... 2141
C901350009 Number of FLUSH-LL message
received ........................................................... 2142
C901350010 Number of FLUSH-LL-ACK message
sent................................................................. 2142
C901350011 Number of LLC-DISCARDED message
sent................................................................. 2143
C901350013 Number of BVC_BLOCK_ACK message
received ........................................................... 2144
sent................................................................. 2144
received ........................................................... 2144
CXXVIII

received ........................................................... 2145
sent................................................................. 2146
received ........................................................... 2146
C901350020 Number of PERFORM LOCATION-REQUEST
message sent.................................................... 2147
C901350022 Number of PERFORM-LOCATION-ABORT
sent................................................................. 2148
C901350024 Number of POSITION-RESPONSE message
received ........................................................... 2149
C901350025 Number of status messages sent............... 2149
C901350026 Number of status messages received ......... 2150
Unknown .......................................................... 2150
protocol error.................................................... 2151
mandatory information element........................... 2153
CXXIX

BVCI unknown .................................................. 2156
protocol error.................................................... 2156
BVC blocking..................................................... 2157
invalid mandatory IE .......................................... 2158
SGSN congestion ............................................... 2161
BSSMAP Message Measurement .................. 2163

Overview.................................................................. 2165
C901360001 Number of ASSIGNMENT REQUEST
messages ......................................................... 2166
C901360002 Number of ASSIGNMENT COMPLETE
messages ......................................................... 2167
C901360003 Number of ASSIGNMENT FAILURE
messages ......................................................... 2168
C901360004 Number of RESOURCE REQUEST
messages ......................................................... 2168
C901360005 Number of RESOURCE INDICATION
messages ......................................................... 2169
C901360006 Number of PAGING messages ................... 2170
CXXX
C901360007 Number of CIPHER MODE COMMAND

messages ......................................................... 2170
C901360008 Number of CIPHER MODE COMPLETE
messages ......................................................... 2171
C901360009 Number of CIPHER MODE REJECT
messages ......................................................... 2172
C901360010 Number of sent CLASSMARK UPDATE
messages ......................................................... 2172
C901360011 Number of received CLASSMARK UPDATE
messages ......................................................... 2173
C901360012 Number of QUEUING INDICATION
messages ......................................................... 2173
C901360013 Number of COMPLETE LAYER 3
INFORMATION messages .................................... 2174
C901360014 Number of CLASSMARK REQUEST
messages ......................................................... 2175
C901360015 Number of uplink LOAD INDICATION
messages ......................................................... 2175
C901360016 Number of downlink LOAD INDICATION
messages ......................................................... 2176
C901360017 Number of HANDOVER REQUEST
messages ......................................................... 2177
C901360018 Number of HANDOVER REQUIRED
messages ......................................................... 2177
C901360019 Number of HANDOVER COMMAND
messages ......................................................... 2178
C901360020 Number of HANDOVER REQUEST ACK
messages ......................................................... 2179
C901360021 Number of HANDOVER COMPLETE
messages ......................................................... 2180
C901360022 Number of HANDOVER SUCCEEDED
messages ......................................................... 2181
C901360023 Number of HANDOVER CANDIDATE ENQUIRE
messages ......................................................... 2182
C901360024 Number of HANDOVER CANDIDATE
RESPONSE messages ......................................... 2183
C901360025 Number of HANDOVER FAILURE
messages ......................................................... 2183
C901360026 Number of HANDOVER PERFORMED
messages ......................................................... 2184
CXXXI
C901360027 Number of HANDOVER REQUIRED REJECT

messages ......................................................... 2185
C901360028 Number of HANDOVER DETECT
messages ......................................................... 2185
C901360029 Number of CLEAR COMMAND
messages ......................................................... 2186
C901360030 Number of CLEAR COMPLETE
messages ......................................................... 2187
C901360031 Number of CLEAR REQUEST messages............................................................... 2187
C901360032 Number of SAPI "N" REJECT
messages ......................................................... 2188
C901360033 Number of UL CONFUSION messages......... 2188
C901360034 Number of DL CONFUSION messages......... 2189
C901360035 Number of UL RESET messages ................ 2190
C901360036 Number of DL RESET messages ................ 2190
C901360037 Number of UL RESET ACKNOWLEDGE
messages ......................................................... 2191
C901360038 Number of DL RESET ACKNOWLEDGE
messages ......................................................... 2192
C901360039 Number of UL OVERLOAD messages .......... 2192
C901360040 Number of DL OVERLOAD messages .......... 2193
C901360041 Number of MSC INVOKE TRACE
messages ......................................................... 2193
C901360042 Number of sent BSS INVOKE TRACE
messages ......................................................... 2194
C901360043 Number of received BSS INVOKE TRACE
messages ......................................................... 2195
C901360044 Number of sent CONNECTIONLESS
C901360045 Number of received CONNECTIONLESS
C901360046 Number of SUSPEND messages ................ 2196
C901360047 Number of RESUME messages .................. 2197
C901360048 Number of Common ID messages ............. 2198
C901360049 Number of LSA INFORMATION
messages ......................................................... 2198
C901360050 Number of PERFORM LOCATION REQUEST
messages ......................................................... 2199
CXXXII
C901360051 Number of PERFORM LOCATION RESPONSE

messages ......................................................... 2199
C901360052 Number of PERFORM LOCATION ABORT
messages ......................................................... 2200
C901360053 Number of sent BLOCK messages.............. 2200
C901360054 Number of received BLOCK ACK
messages ......................................................... 2201
C901360055 Number of sent UNBLOCK messages ......... 2202
C901360056 Number of received UNBLOCK ACK
messages ......................................................... 2203
C901360057 Number of received BLOCK messages......... 2203
C901360058 Number of sent BLOCK ACK messages......... 2204
C901360059 Number of received UNBLOCK
messages ......................................................... 2205
C901360060 Number of sent UNBLOCK ACK
messages ......................................................... 2205
C901360061 Number of UL RESET CIRCUIT
messages ......................................................... 2206
C901360062 Number of DL RESET CIRCUIT
messages ......................................................... 2207
C901360063 Number of UL RESET CIRCUIT ACK
messages ......................................................... 2207
C901360064 Number of DL RESET CIRCUIT ACK
messages ......................................................... 2208
C901360065 Number of UL CIRCUIT GROUP BLOCK
messages ......................................................... 2209
C901360066 Number of DL CIRCUIT GROUP BLOCK
messages ......................................................... 2209
C901360067 Number of UL CIRCUIT GROUP BLOCKING
ACKNOWLEDGE messages .................................. 2210
C901360068 Number of DL CIRCUIT GROUP BLOCKING
C901360069 Number of UL CIRCUIT GROUP UNBLOCK
messages ......................................................... 2211
C901360070 Number of DL CIRCUIT GROUP UNBLOCK
messages ......................................................... 2212
C901360071 Number of UL CIRCUIT GROUP UNBLOCKING
C901360072 Number of DL CIRCUIT GROUP UNBLOCKING
CXXXIII
C901360073 Number of UL UNEQUIPPED CIRCUIT

messages ......................................................... 2214
C901360074 Number of DL UNEQUIPPED CIRCUIT
messages ......................................................... 2215
C901360075 Number of CHANGE CIRCUIT
messages ......................................................... 2216
C901360076 Number of CHANGE CIRCUIT ACK
messages ......................................................... 2216
C901360077 Number of HANDOVER PERFORMED ACK
messages ......................................................... 2217
C901360078 The count of Sending INTERNAL HANDOVER
REQUIRED ........................................................ 2217
C901360079 The count of Receiving INTERNAL
HANDOVER COMMAND ....................................... 2219
C901360080 The count of Receiving INTERNAL
HANDOVER REJECT............................................ 2220
C901360081 Number of INTERNAL HANDOVER ENQUIRY
messages ......................................................... 2220
C901360082 Number of UL RESET IP RESOURCE
messages ......................................................... 2221
C901360083 Number of UL RESET IP RESOURCE
ACKOWNLEDGE messages .................................. 2222
C901360084 Number of DL RESET IP RESOURCE
messages ......................................................... 2222
C901360085 Number of DL RESET IP RESOURCE
A-Interface Message Measurement ............. 2225

Overview.................................................................. 2225
C901370001 Number of UL DTAP messages .................. 2225
C901370002 Number of DL DTAP messages .................. 2226
C901370003 Number of UL BSSMAP messages .............. 2226
C901370004 Number of DL BSSMAP messages.............. 2227
C901370005 Number of DL BSSMAP messages received
with error ......................................................... 2228
C901370006 Number of chosen for MSC Load share by
NULL_NRI......................................................... 2228
the NRI not in the MSC pool ................................ 2229
Terrestrial Resource Availability

Measurement .............................................. 2231
CXXXIV
Overview.................................................................. 2231
C901380001 Mean number of available trunk
circuits ............................................................. 2232
C901380002 Mean number of unavailable trunk
circuits ............................................................. 2232
C901380003 Maximum number of busy trunk
circuits ............................................................. 2232
C901380004 Busy time of trunk circuit ......................... 2233
C901380005 Congestion time of trunk circuit ................ 2233
C901380006 Mean number of available UDP port ........... 2234
C901380007 Mean number of unavailable UDP port......... 2234
C901380008 Number of allocation AIPB board
success ............................................................ 2235
C901380009 Number of allocation AIPB board
failure .............................................................. 2235
C901380010 Maximum number of seizure UDP
port ................................................................. 2236
C901380011 Number of successful one time request UDP
port to AIPB...................................................... 2236
C901380012 Number of successful two time request UDP
port to AIPB...................................................... 2237
C901380013 Number of successful three time request
UDP port to AIPB ............................................... 2238
C901380014 Number of failure request UDP port to
AIPB ................................................................ 2239
C901380015 Seizure duration of UDP port .................... 2240
C901380016 The times of User Plane transport without
RTP multiplexing................................................ 2240
C901380017 The times of RTP multiplexing applied
without RTP header compression ......................... 2241
C901380018 The times of RTP multiplexing applied with
RTP header compression..................................... 2242
C901380019 Mean number of busy trunk circuits........... 2242
C901380020 Mean number of seizure UDP port ............. 2244
Ater Message Measurement ........................ 2245

Overview.................................................................. 2247
C901390001 Number of UL BLOCK Ater single CIRCUIT
messages ......................................................... 2247
C901390002 Number of DL BLOCKING Ater single
CIRCUIT ACKNOWLEDGE messages ..................... 2247
CXXXV
C901390003 Number of UL UNBLOCK Ater single CIRCUIT

messages ......................................................... 2248
C901390004 Number of DL UNBLOCKING Ater single
C901390005 Number of DL BLOCK Ater single CIRCUIT
messages ......................................................... 2248
C901390006 Number of UL BLOCKING Ater single
C901390007 Number of DL UNBLOCK Ater single CIRCUIT
messages ......................................................... 2249
C901390008 Number of UL UNBLOCKING Ater single
C901390009 Number of UL RESET Ater CIRCUIT
messages ......................................................... 2250
C901390010 Number of DL RESET Ater CIRCUIT
messages ......................................................... 2250
C901390011 Number of UL RESET Ater CIRCUIT
C901390012 Number of DL RESET Ater CIRCUIT
C901390013 Number of UL BLOCK Ater GROUP CIRCUIT
messages ......................................................... 2252
C901390014 Number of DL BLOCK Ater GROUP CIRCUIT
messages ......................................................... 2252
C901390015 Number of UL BLOCKING Ater GROUP
C901390016 Number of DL BLOCKING Ater GROUP
C901390017 Number of UL UNBLOCK GROUP CIRCUIT
messages on Ater .............................................. 2253
C901390018 Number of DL UNBLOCK Ater GROUP
CIRCUIT messages ............................................ 2254
C901390019 Number of UL UNBLOCKING Ater GROUP
C901390020 Number of DL UNBLOCKING Ater GROUP
C901390021 Number of UL UNEQUIPPED Ater CIRCUIT
messages ......................................................... 2255
C901390022 Number of DL UNEQUIPPED Ater CIRCUIT
messages ......................................................... 2255
CXXXVI
C901390023 Number of UL BLOCK A CIRCUIT

messages ......................................................... 2256
C901390024 Number of DL BLOCKING A CIRCUIT
C901390025 Number of UL UNBLOCK A CIRCUIT
messages ......................................................... 2256
C901390026 Number of DL UNBLOCKING A CIRCUIT
C901390027 Number of DL BLOCK A CIRCUIT
messages ......................................................... 2257
C901390028 Number of UL BLOCKING A CIRCUIT
C901390029 Number of DL UNBLOCK A CIRCUIT
messages ......................................................... 2258
C901390030 Number of UL UNBLOCKING A CIRCUIT
C901390031 Number of UL BLOCK A CIRCUIT GROUP
messages ......................................................... 2258
C901390032 Number of DL BLOCK A CIRCUIT GROUP
messages ......................................................... 2259
C901390033 Number of UL BLOCKING A CIRCUIT GROUP
C901390034 Number of DL BLOCKING A CIRCUIT GROUP
C901390035 Number of UL UNBLOCK A CIRCUIT GROUP
messages ......................................................... 2260
C901390036 Number of DL UNBLOCK A CIRCUIT GROUP
messages ......................................................... 2260
C901390037 Number of UL UNBLOCKING A CIRCUIT
GROUP ACKNOWLEDGE messages ....................... 2261
C901390038 Number of DL UNBLOCKING A CIRCUIT
GROUP ACKNOWLEDGE messages ....................... 2261
C901390039 Number of UL UNEQUIPPED A CIRCUIT
messages ......................................................... 2261
C901390040 Number of DL UNEQUIPPED A CIRCUIT
messages ......................................................... 2262
C901390041 Number of UL Ater RESET messages.......... 2262
C901390042 Number of DL Ater RESET messages.......... 2262
C901390043 Number of UL Ater RESET ACKNOWLEDGE
messages ......................................................... 2263
CXXXVII
C901390044 Number of DL Ater RESET ACKNOWLEDGE

messages ......................................................... 2263
C901390045 Number of UL Ater CONFUSION
messages ......................................................... 2263
C901390046 Number of DL Ater CONFUSION
messages ......................................................... 2264
C901390047 Number of RESOURCE REQUEST
messages ......................................................... 2264
C901390048 Number of RESOURCE INDICATION
messages ......................................................... 2264
C901390049 Number of RESOURCE NON-INDICATION
messages ......................................................... 2265
C901390050 Number of resource release request
messages ......................................................... 2265
C901390051 Number of resource release acknowledge
messages ......................................................... 2266
C901390052 Number of resource failure messages......... 2266
C901390053 Number of TFO status messages ............... 2266
C901390054 Number of TFO common voice type
messages ......................................................... 2267
C901390055 Number of TFO control messages .............. 2267
MTP2 Signal Link Measurement ................... 2269

Overview.................................................................. 2269
C901400001 Number of error SU due to Abnormal
Flag ................................................................. 2270
C901400002 Number of error SU Length Error .............. 2270
C901400003 Number of Out of Alignment ..................... 2270
C901400004 Number of error SU due not to Octet ......... 2271
C901400005 Number of error SU due to CRC Error......... 2271
C901400006 Number of Other error ............................. 2272
C901400007 Number of Negative Acknowledgement
Received .......................................................... 2272
C901400008 Octets of MSU Retransmitted .................... 2272
C901400009 Number of MSU Resend ........................... 2273
C901400010 Number of Align Error.............................. 2273
C901400011 Number of Error SU................................. 2273
C901400012 Number of MSU discarded due to
congestion........................................................ 2274
C901400013 Number of SL failure due to Abnormal FIBR
BSNR ............................................................... 2274
CXXXVIII
C901400014 Number of SL failure due to Excessive delay

of ack .............................................................. 2274
C901400015 Number of SL failure due to Excessive error
rate ................................................................. 2275
C901400016 Number of SL failure due to Excessive
duration of congestion........................................ 2275
CPU MEM Measurement ............................... 2277

Overview.................................................................. 2277
C901410001 Peak memory usage of the main
processor ......................................................... 2277
C901410002 Mean value of the memory usage.............. 2278
C901410003 Peak load of CPU usage of the main
processor ......................................................... 2278
C901410004 Mean ratio of the CPU usage..................... 2278
C901410005 Duration of the main processor keeping in
peak state ........................................................ 2279
C901410006 The time when peak load CPU usage
occurred........................................................... 2279
C901410007 peak kilo-bytes of the rest UB................... 2280
C901410008 Mean kilo-bytes of the rest UB .................. 2280
SCTP AS Measurement ................................ 2281

Overview.................................................................. 2282
C901420001 Number of IP packets dropped by SCTP due
to some reasons................................................ 2282
C901420002 Number of received SCTP packets ............. 2282
C901420003 Bytes of packets received from ip.............. 2283
C901420004 Number of packets sent to ip .................... 2283
C901420005 Bytes of packets sent to ip ....................... 2283
C901420006 Number of messages sent to ulp ............... 2284
C901420007 Bytes of messages sent to ulp .................. 2284
C901420008 Number of messages received from
ulp .................................................................. 2284
C901420009 Bytes of messages received from .............. 2285
C901420010 Number of Congestion ............................. 2285
C901420011 Duration of congestion............................. 2285
C901420012 Chunk number of fast retransmission......... 2286
C901420013 Chunk number of time-out retransmission ................................................................. 2286
C901420014 RTT is lower than T1................................ 2286
C901420015 RTT is between T1 and T2 ........................ 2287
CXXXIX
C901420016 RTT is higher than T2 .............................. 2287

C901420017 Number of network transmission dropped
packets ............................................................ 2287
C901420018 Maximum delay of network transmission ................................................................. 2288
C901420019 Minimum delay of network transmission ................................................................. 2288
C901420020 Total delay of network transmission(high 4
bytes) .............................................................. 2289
C901420021 Total delay of network transmission(low 4
bytes) .............................................................. 2289
C901420022 Number of delay samples of network
transmission ..................................................... 2289
C901420023 Maximum dithering of network
transmission ..................................................... 2290
C901420024 Minimum dithering of network
transmission ..................................................... 2290
C901420025 Total dithering of network transmission(high
4 bytes) ........................................................... 2291
C901420026 Total dithering of network transmission(low
4 bytes) ........................................................... 2291
C901420027 Number of dithering samples of network
transmission ..................................................... 2292
C901420028 Chunks Lost On Send Dirction................... 2292
C901420029 Chunks Trans On Send Dirction ................. 2292
C901420030 Number of abort from peer....................... 2293
C901420031 Number of association break by
retransmission .................................................. 2293
IP Port Performance Statistics .................... 2295

Overview.................................................................. 2295
C901430001 Packets number received ......................... 2295
C901430002 Packets number transmitted ..................... 2296
C901430003 Packets number discarded at rx end .......... 2296
C901430004 Packets number discarded at tx end .......... 2296
GTRUNK Resource Statistics ........................ 2299

Overview.................................................................. 2299
C901440001 Maximum of used DSP TS ........................ 2299
C901440002 Maximum of the used sampling according to
DSP TS ............................................................ 2300
C901440003 Amount of used DSP TS ........................... 2300
CXL
C901440004 Number of regular scanning and

sampling .......................................................... 2300
Other Process Statistics .............................. 2303

Overview.................................................................. 2304
C901450001 Max time of NACC cell reselection ............. 2305
C901450002 Minimum time of NACC cell reselection ................................................................. 2305
C901450003 Total time of NACC cell reselection ............ 2306
C901450004 Number of NACC cell reselection (PCCN to
flush LL)........................................................... 2307
C901450005 Number of NACC cell reselection without
receiving flush LL............................................... 2308
C901450006 Number of UL packet channel frame
adjustment ....................................................... 2309
C901450007 Number of DL packet channel frame
adjustment ....................................................... 2309
C901450008 Sum of C ............................................... 2310
C901450009 Sum of RxQual ....................................... 2310
C901450010 Sum of GMSK-MEAN-BEP ......................... 2311
C901450011 Sum of GMSK-CV-BEP ............................. 2312
C901450012 Sum of 8PSK-MEAN-BEP .......................... 2313
C901450013 Sum of 8PSK-CV-BEP .............................. 2314
C901450014 Number of sampling of C ......................... 2315
C901450015 Number of sampling of RxQual.................. 2316
C901450016 Number of sampling of GMSK-MEANBEP ................................................................. 2317
C901450017 Number of sampling of GMSK-CV-BEP......... 2318
C901450018 Number of sampling of 8PSK-MEANBEP ................................................................. 2319
C901450019 Number of sampling of 8PSK-CV-BEP......... 2320
C901450020 Number of RLC uplink ACK TBF ................. 2321
C901450021 Number of RLC uplink NACK TBF ............... 2322
C901450022 Number of DL-UNITDATA messages with
C901450023 Total Block Num...................................... 2323
C901450024 UL Idle Block Num .................................. 2323
C901450025 DL Idle Block Num .................................. 2323
C901450026 The max length of packet latency period in
Abis ................................................................. 2323
CXLI
C901450027 The min length of packet latency period in

Abis ................................................................. 2324
C901450028 The average length of packet latency period
in Abis ............................................................. 2324
C901450029 The latest length of packet latency period in
Abis ................................................................. 2325
C901450030 The length of packet latency period between
0 and 20 ms (20 included) in Abis........................ 2325
20 ms and 40 ms (40 included) in Abis ................. 2326
80 ms and 100 ms (100 included) in Abis ............. 2327
100 ms and 120 ms (120 included) in Abis............ 2328
C901450039 The length of packet latency period larger
than 180 ms in Abis ........................................... 2330
C901450040 The max length of downlink packet latency
period in Gb...................................................... 2330
C901450041 The min length of downlink packet latency
period in Gb...................................................... 2330
C901450042 The average length of downlink packet
latency period in Gb ........................................... 2331
C901450043 The length of downlink packet latency period
between 0 and 100 ms (100 included) in Gb ......... 2331
between 100 ms and 200 ms (200 included) in
Gb................................................................... 2332
Gb................................................................... 2332
CXLII

Gb................................................................... 2333
Gb................................................................... 2333
Gb................................................................... 2334
larger than 1000 ms in Gb .................................. 2334
C901450050 The max length of uplink packet latency
period in Gb...................................................... 2335
C901450051 The min length of uplink packet latency
period in Gb...................................................... 2335
C901450052 The average length of uplink packet latency
period in Gb...................................................... 2335
C901450053 LLC Stall Num ........................................ 2336
C901450054 MAC Resource Congestion ........................ 2336
C901450055 BSSGP Resource Congestion..................... 2336
C901450056 Number of Pushing Down Uplink BandWidth
....................................................................... 2337
C901450057 Number of Pushing Down Downlink
BandWidth ....................................................... 2337
C901450058 Number of Pushing Up Uplink
BandWidth........................................................ 2338
C901450059 Number of Pushing Up Downlink
BandWidth........................................................ 2339
FR Carried Links Statistics........................... 2341

Overview.................................................................. 2341
C901460001 Number of Status enquiry Message
sent................................................................. 2341
C901460002 Number of Status ACK Message
received ........................................................... 2342
C901460003 Number of link exception ......................... 2343
C901460004 Number of bytes received on BRCH ........... 2344
C901460005 Number of bytes sent on BRCH ................. 2344
OMP PS Service Statistics ............................ 2345

Overview.................................................................. 2345
CXLIII

received ........................................................... 2346
received ........................................................... 2346
received ........................................................... 2347
received ........................................................... 2347
SNS on OMP Statistics ................................. 2349

Overview.................................................................. 2350
C901480001 Number of SNS-SIZE initiations ................ 2350
C901480002 Number of SNS-SIZE received successful
acknowledgements ............................................ 2350
C901480003 Number of SNS-SIZE failures.................... 2351
C901480004 Number of SNS-SIZE initiated by BSC
without response ............................................... 2351
C901480005 Number of SNS-CONFIG initiated by
BSC ................................................................. 2351
C901480006 Number of SNS-CONFIG initiated by BSC
received successful acknowledgements................. 2352
received failed acknowledgements ....................... 2352
C901480009 Number of SNS-CONFIG initiated by SGSN
C901480010 Number of SNS-CONFIG initiated by SGSN
C901480011 Number of SNS-ADD initiated by BSC......... 2354
C901480012 Number of SNS-ADD initiated by BSC
C901480015 Number of SNS-ADD initiated by SGSN
C901480016 Number of SNS-ADD initiated by SGSN
CXLIV
C901480017 Number of SNS-DELETE initiated by

BSC ................................................................. 2357
C901480018 Number of SNS-DELETE initiated by BSC
C901480021 Number of SNS-DELETE initiated by SGSN
C901480022 Number of SNS-DELETE initiated by SGSN
C901480023 Number of SNS-CHANGEWEIGHT initiated
by BSC............................................................. 2360
C901480024 Number of SNS-CHANGEWEIGHT initiated by
BSC received successful acknowledgements .......... 2361
by BSC received failed acknowledgements ............ 2361
by BSC without response .................................... 2362
SGSN received successful acknowledgements......... 2362
by SGSN received failed acknowledgements .......... 2363
IPGB StrongARM NSVC Statistics................. 2365

Overview.................................................................. 2365
C901490001 Number of bytes received from SGSN......... 2365
C901490002 Number of bytes sent to SGSN ................. 2365
C901490003 Number of PDU data sent by NS sub
layer ................................................................ 2366
layer ................................................................ 2366
layer ................................................................ 2367
IPGB StrongARM Gb Statistics ..................... 2369

Overview.................................................................. 2369
BSSGP level ...................................................... 2369
BSSGP level ...................................................... 2370
CXLV
Queue Measurement ................................... 2371

Overview.................................................................. 2371
C901510001 Average length of queue .......................... 2371
C901510002 Duration of queuing ................................ 2372
C901510003 Number of queuing ................................. 2374
C901510004 Duration of queuing success ..................... 2375
C901510005 Number of queuing success ...................... 2376
HO Synchronization Mode Measurement ........................................................... 2379

Overview.................................................................. 2379
C901520001 Number of synchronous handover
executions ........................................................ 2380
successes ......................................................... 2381
C901520003 Number of pre-synchronous handover
executions ........................................................ 2381
successes ......................................................... 2381
C901520005 Number of pseudo-synchronous handover
executions ........................................................ 2382
C901520006 Number of pseudo-synchronous handover
successes ......................................................... 2382
C901520007 Number of asynchronous handover
executions ........................................................ 2383
successes ......................................................... 2383
Paging Message Measurement .................... 2385

Overview.................................................................. 2385
C901530001 Number of paging messages..................... 2386
C901530002 Number of paging messages from PS of Gb
interface........................................................... 2387
C901530003 Number of paging messages from CS of Gb
interface........................................................... 2387
Reserved Channel Measurement ................. 2389

Overview.................................................................. 2389
C901540001 Number of voice allocations of reserved full
rate channel in assignment ................................. 2389
C901540002 Number of data allocations of reserved full
rate channel in assignment ................................. 2390
CXLVI
C901540003 Number of voice allocations of reserved full

rate channel in handover .................................... 2390
C901540004 Number of data allocations of reserved full
rate channel in handover .................................... 2391
C901540005 Reserved seizure duration of reserved full
rate channel ..................................................... 2391
SCCP Connection Measurement ................... 2393

Overview.................................................................. 2393
C901550001 Number of BSC originated SCCP Connection
attempts .......................................................... 2394
success ............................................................ 2395
failure due to timeout......................................... 2396
C901550004 Number of negative replies for SCCP
connection request ............................................ 2396
C901550005 Number of MSC originated SCCP Connection
Requests .......................................................... 2397
success ............................................................ 2398
DTM Cell Measurement ................................ 2401

Overview.................................................................. 2402
C901560001 Number of voice access in mobile with DTM
ability .............................................................. 2402
C901560002 Number of packet access in mobile with DTM
ability .............................................................. 2403
C901560003 Number of received IMSI when link
establish .......................................................... 2403
C901560004 Number of RANCS module received IMSI
when handover ................................................. 2404
C901560005 Number of mobile sent GTTP message under
DTM mode ........................................................ 2404
C901560006 Number of BSC successfully sent GTTP
message under DTM mode.................................. 2404
C901560007 Number of DTM attempts in mobile ........... 2405
C901560008 Number of DTM uplink attempt failure......... 2405
C901560009 Number of UL DTM database resource
assignment success in dedicated mode ................ 2406
C901560010 Number of UL DTM database resource
assignment failure in dedicated mode .................. 2406
CXLVII
C901560011 Number of handover(intra-cell) attempts

due to UL DTM .................................................. 2407
C901560012 Number of handover(intra-cell) success due
to uplink DTM.................................................... 2407
C901560013 Number of handover(intra-cell) failure due
to uplink DTM.................................................... 2408
C901560014 Number of DTM failure due to
handover.......................................................... 2408
C901560015 Number of UL DTM link establishment
success ............................................................ 2408
C901560016 Attempt number of sending LLC packet on
FACCH in dedicated mode .................................. 2409
C901560017 Number of successfully sent LLC packet on
FACCH in dedicated mode .................................. 2409
C901560018 Attempt Number of DTM established due to
SGSN sent LLC packets ...................................... 2410
C901560019 Number of DTM attempts failure ............... 2410
C901560020 Number of DL DTM resource assignment
success ............................................................ 2411
C901560021 Number of DL DTM resource assignment
failure .............................................................. 2411
C901560022 Number of handover(intra-cell) attempts
due to DL DTM .................................................. 2412
C901560023 Number of successfully handover occurs due
to DL DTM ........................................................ 2412
C901560024 Number of handover failure occurs due to
DL DTM ............................................................ 2413
C901560025 Number of DL DTM failure occurs due to
handover.......................................................... 2413
C901560026 Number of successfully DL DTM
establishment ................................................... 2414
LAPD Measurement ..................................... 2415

Overview.................................................................. 2416
C901570001 Number of Application Data Package from
CMP................................................................. 2416
C901570002 Number of BTS Application Data Package
Sent to MP........................................................ 2416
C901570003 Number of Data Package Ack Sent to
Application ....................................................... 2417
CXLVIII
C901570004 Number of Application Data Package Ack

from BTS .......................................................... 2417
C901570005 Number of Application Nack Data Package
sent to BTS....................................................... 2417
C901570006 Number of BTS Application Nack Data
Package Receive by BTS ..................................... 2418
C901570007 Number of Sending Frame........................ 2418
C901570008 Number of Received Frame ...................... 2418
C901570009 Number of High Priority Queue
overflow ........................................................... 2419
C901570010 Number of Low Priority Queue
overflow ........................................................... 2419
C901570011 Number of Success in High Priority
Queue.............................................................. 2419
C901570012 Number of Success in Low Priority
Queue.............................................................. 2420
C901570013 Number of in Queue Request UB Fail.......... 2420
C901570014 Resend Number ...................................... 2420
C901570015 Resend Request Number .......................... 2421
C901570016 Establish Link Number ............................. 2422
C901570017 Broken Number ...................................... 2422
C901570018 Protocol Error Number ............................. 2423
C901570019 Number of T200 Overtime........................ 2423
C901570023 Number of abnormal hop frame ................ 2425
C901570024 Number of normal hop frame.................... 2425
C901570025 Multi Channel Link Lose Frame.................. 2425
C901570026 No useful channel ................................... 2426
C901570027 Max Up Flow .......................................... 2426
C901570028 Max Down Flow ...................................... 2426
C901570029 Current Up Flow...................................... 2427
C901570030 Current Down Flow.................................. 2427
LCS Measurement........................................ 2429

Overview.................................................................. 2430
C901580001 Number of receiving location request in
CS ................................................................... 2430
C901580002 Number of receiving location abort in
CS ................................................................... 2431
CXLIX
C901580003 Number of TA Request in CS..................... 2431

C901580004 Number of TA Response in CS................... 2432
C901580005 Number of MS Position Command in
CS ................................................................... 2433
C901580006 Number of MS Position Response in
CS ................................................................... 2433
C901580007 Number of location success in CS .............. 2434
C901580008 Number of location failure due to abnormal
status of Lb interface in CS ................................. 2435
C901580009 Number of location failure due to radio Timer
expiration in CS................................................. 2435
C901580010 Number of sending BSSLAP RESET message
due to Intra-BSS handover in CS ......................... 2436
C901580011 Number of location failure due to Intra-BSS
handover expiration in CS................................... 2437
C901580012 Number of location failure due to location
Timer expiration in CS........................................ 2438
C901580013 Number of location failure due to Inter-BSS
handover in CS ................................................. 2439
C901580014 Number of location failure due to call drop in
CS ................................................................... 2439
C901580015 Number of location failure due to other
BSC's cause in CS.............................................. 2440
PS ................................................................... 2440
C901580017 Number of receiving location abort in
PS ................................................................... 2441
C901580018 Number of TA Request in PS ..................... 2442
C901580019 Number of TA Response in PS ................... 2443
C901580020 Number of MS Position Command in
PS ................................................................... 2443
C901580021 Number of MS Position Response in
PS ................................................................... 2444
C901580022 Number of location success in PS .............. 2445
C901580023 Number of location failure due to abnormal
status of Lb interface in PS ................................. 2445
expiration in PS ................................................. 2446
C901580025 Number of location failure due to Inter-CMP
cell reselection in PS .......................................... 2447
CL
C901580026 Number of sending LOCATION INFORMATION

message to SMLC due to Intra-CMP cell reselection
in PS................................................................ 2448
C901580027 Number of location failure due to location
Timer expiration in PS ........................................ 2448
C901580028 Number of location failure due to other
BSC's cause in PS .............................................. 2449
LB Global Msg Measurement........................ 2451

Overview.................................................................. 2451
C901590001 Number of receiving RESET message from
SMLC ............................................................... 2451
C901590002 Number of sending RESET ACK message to
SMLC ............................................................... 2452
C901590003 Number of sending RESET message to
SMLC ............................................................... 2453
C901590004 Number of receiving RESET ACK message
from SMLC........................................................ 2453
Ater Interface Relays Measurement ............ 2455

Overview.................................................................. 2455
C901600001 Number of configured 16 K relay circuits of
Ater interface .................................................... 2456
C901600002 Average of unavailable 16K relay circuits of
Ater interface .................................................... 2456
C901600003 Average of available 16 K relay circuits of
Ater interface .................................................... 2457
C901600004 Maximum of busy 16 K relay circuits of Ater
interface........................................................... 2458
C901600005 Maximum of busy 8 K relay circuits of Ater
interface........................................................... 2459
C901600006 Total busy time of 16 K relay circuits of Ater
interface........................................................... 2461
interface........................................................... 2462
Ater Interface SCCP Connections

Measurement .............................................. 2465
Overview.................................................................. 2465
C901610001 Number of SCCP establishment requests
(BSC to TC) ...................................................... 2465
CLI
C901610002 Number of SCCP establishments success

(BSC to TC) ...................................................... 2466
C901610003 Number of SCCP establishment failure due
to timeout (BSC to TC) ....................................... 2467
C901610004 Number of SCCP establishment refused
(BSC to TC) ...................................................... 2468
Measurement Reprot Serving Cell

Measurement .............................................. 2471
MR Serving Cell Measurement ..................................... 2474
C901620001 Number of samples of UL RQ=0 and receive
level between 0 and 10 ...................................... 2475
level between 11 and 15..................................... 2476
CLII

CLIII

C901620049 Number of samples of DL RQ=0 and receive
CLIV

CLV

CLVI

Measurement Report Adjacent Cell

Measurement .............................................. 2549
MR Adjacent Cell Measurement.................................... 2549
C901630001 Number of samples with C/I < -10db......... 2550
C901630002 Number of samples with C/I between -9db
and -5db .......................................................... 2551
C901630003 Number of samples with C/I between -4db
and 0db ........................................................... 2551
C901630004 Number of samples with C/I between 1db
and 5db ........................................................... 2552
and 10db.......................................................... 2553
and 15db.......................................................... 2553
and 20db.......................................................... 2554
C901630008 Number of samples with C/I > 20db .......... 2555
TRX Paging Measurement............................ 2557

Overview.................................................................. 2557
C901640001 Number of PS paging message discarded
due to full of the queue ...................................... 2558
C901640002 Number of CS paging message discarded
due to full of the queue ...................................... 2558
C901640003 Average length of PCH queue: 9*9............ 2559
C901640004 Average length of PCH queue: 9*64 .......... 2559
C901640005 The percentage of PCH Blocks validly
used ................................................................ 2560
C901640006 Number of paging messages seized by other
hyper-priority messages while transmitting on PCH
blocks .............................................................. 2560
C901640007 Number of paging messages retransmitted
zero times ........................................................ 2560
one times ......................................................... 2561
two times ......................................................... 2561
three times....................................................... 2561
CLVII
C901640011 Numbers of paging messages retransmitted

four times ........................................................ 2562
TRX Temperature Power Measurement ....... 2563

Overview.................................................................. 2563
C901650001 Maximum value of TRX power (db) ............ 2563
C901650002 Minimum value of TRX power (db)............. 2564
C901650003 Mean value of TRX power (db) .................. 2564
C901650004 Maximum of TRX temperature
(Celsius) .......................................................... 2564
C901650005 Minimum of TRX temperature
(Celsius) .......................................................... 2564
C901650006 Mean of TRX temperature (Celsius) ........... 2565
Terminal Ability Statistic ............................. 2567

Terminal Ability Statistics............................................ 2569
C901660001 Number of mobile support single TS DTM
ability .............................................................. 2569
C901660002 Number of mobile support DTM GPRS multi
TS ability 5 ....................................................... 2570
TS ability 9 ....................................................... 2571
TS ability 11 ..................................................... 2572
C901660005 Number of mobile support DTM EGPRS multi
TS ability 5 ....................................................... 2573
TS ability 9 ....................................................... 2574
TS ability 11 ..................................................... 2575
C901660008 Number of mobile support extend DTM GPRS
multi TS ability 5 ............................................... 2576
multi TS ability 6 ............................................... 2577
multi TS ability 9 ............................................... 2578
multi TS ability 10 ............................................. 2579
multi TS ability 11 ............................................. 2580
C901660013 Number of mobile support extend DTM
EGPRS multi TS ability 5 ..................................... 2581
CLVIII

EGPRS multi TS ability 10 ................................... 2584
EGPRS multi TS ability 11 ................................... 2585
C901660018 Number of mobile of GPRS multi TS ability
1 ..................................................................... 2586
2 ..................................................................... 2588
3 ..................................................................... 2589
4 ..................................................................... 2591
5 ..................................................................... 2593
6 ..................................................................... 2594
7 ..................................................................... 2596
8 ..................................................................... 2598
9 ..................................................................... 2599
10 ................................................................... 2601
11 ................................................................... 2603
12 ................................................................... 2604
30 ................................................................... 2606
31 ................................................................... 2608
32 ................................................................... 2609
33 ................................................................... 2611
CLIX

34 ................................................................... 2613
C901660035 Number of mobile of EGPRS multi TS ability
1 ..................................................................... 2614
2 ..................................................................... 2616
3 ..................................................................... 2618
4 ..................................................................... 2619
5 ..................................................................... 2621
6 ..................................................................... 2623
7 ..................................................................... 2624
8 ..................................................................... 2626
9 ..................................................................... 2628
10 ................................................................... 2629
11 ................................................................... 2631
12 ................................................................... 2633
30 ................................................................... 2634
31 ................................................................... 2636
32 ................................................................... 2638
33 ................................................................... 2639
34 ................................................................... 2641
C901660052 Number of mobile support FR ................... 2643
C901660053 Number of mobile support HR................... 2643
C901660054 Number of mobile support EFR ................. 2644
C901660055 Number of mobile support AMRFR ............. 2645
CLX
C901660056 Number of mobile support AMRHR............. 2645

C901660057 Number of mobile support wideband
AMROFR ........................................................... 2646
AMRFR ............................................................. 2647
AMROHR .......................................................... 2648
C901660060 Number of mobile support AMROHR .......... 2649
C901660061 Number of mobile support extend uplink
TBF ................................................................. 2650
C901660062 Number of mobile support NACC ............... 2651
C901660063 Number of mobile support GPRS extend
dynamic allocation ............................................. 2652
C901660064 Number of mobile support EGPRS extend
dynamic allocation ............................................. 2653
C901660065 Number of sampling received
Classmark3....................................................... 2654
C901660066 Number of sampling received radio access
ability .............................................................. 2655
C901660069 Num of MS supporting PS handover........... 2656
C901660070 The Number of MS which Support
SAIC ................................................................ 2657
C901660071 The Number of MS which not Support
SAIC ................................................................ 2658
MTP3 Signaling Link Statistics..................... 2659

Overview.................................................................. 2660
C901670001 Duration of Signaling Link Out of
Service ............................................................ 2660
C901670002 Number of Signaling Link Out of
Service ............................................................ 2661
C901670003 Number of Message Signal Unit Sent ......... 2661
C901670004 Octets of SIF-SIO Sent ............................ 2661
C901670005 Number of Message Signal Unit
Received .......................................................... 2662
C901670006 Octets of SIF-SIO Received ...................... 2662
C901670007 Peak Traffic of Signaling Link .................... 2662
C901670008 Peak Traffic Duration of Signaling Link......... 2663
C901670009 Number of Change Over on OMP ............... 2664
C901670010 Number of TFP Received .......................... 2664
C901670011 Rate of Mtp3 Link Occupy......................... 2664
CLXI
C901670012 Number of SCCP Message Signal Unit

Received .......................................................... 2665
Sent ................................................................ 2665
C901670014 Number of A2SP Message Signal Unit
Received .......................................................... 2665
Sent ................................................................ 2666
C901670016 Number of Stm Message Signal Unit
Received .......................................................... 2666
C901670017 Number of Stm Message Signal Unit
Sent ................................................................ 2666
C901670018 Number of Sltm Message Signal Unit
Received .......................................................... 2666
Sent ................................................................ 2667
C901670020 Octets of SCCP SIF-SIO Received .............. 2667
C901670021 Octets of SCCP SIF-SIO Sent .................... 2667
C901670022 Octets of MTP2 SIF-SIO Received .............. 2667
C901670023 Octets of MTP2 SIF-SIO Sent .................... 2668
C901670024 Octets of Stm SIF-SIO Received................ 2668
C901670025 Octets of Stm SIF-SIO Sent...................... 2668
C901670026 Octets of Sltm SIF-SIO Received ............... 2668
C901670027 Octets of Sltm SIF-SIO Sent ..................... 2669
C901670028 Number of message discarded due to
Congestion ....................................................... 2669
C901670029 Number of restrictions Level 1 .................. 2669
C901670032 Duration of Restrictions Level 1................. 2670
C901670035 Duration of manual prohibition.................. 2671
C901670036 Number of local automatic change
back ................................................................ 2671
C901670037 Number of SL restoration ......................... 2671
C901670038 Number of Local management inhibit......... 2672
C901670039 Duration of SL inhibition due to Local
management actions.......................................... 2672
CLXII
C901670040 Number of remote management

inhibit .............................................................. 2672
C901670041 Duration of SL inhibition due to remote
management actions.......................................... 2673
C901670042 Number of remote processor outage.......... 2673
C901670043 Duration of SL inhibition due to remote
processor outage ............................................... 2673
C901670044 Number of sending unaccess
messages ......................................................... 2674
C901670045 Number of sending flow-control discarded
messages ......................................................... 2674
C901670046 Ten thousand multiple bandwidth occupancy
rate on outgoing signaling link............................. 2674
rate on incoming signaling link ........................... 2675
C901670048 Link type ............................................... 2676
C901670049 Number of TFA sent ................................ 2676
C901670050 Number of TFA received ........................... 2676
C901670051 Number of TFC sent ................................ 2676
C901670052 Number of TFC received........................... 2677
C901670053 Number of RST sent ................................ 2677
C901670054 Number of RST received .......................... 2677
C901670055 Number of TRA sent ................................ 2677
C901670056 Number of TRA received .......................... 2678
C901670057 Number of UPU sent ................................ 2678
C901670058 Number of UPU received .......................... 2678
C901670059 Number of message discard controlled by
license ............................................................. 2678
M3UA Performance Statistics ...................... 2681

Overview.................................................................. 2682
C901680001 Number of data message sent .................. 2682
C901680002 Number of data message received............. 2682
C901680003 Number of ASP Up message sent .............. 2683
C901680004 Number of ASP Up message received......... 2683
C901680005 Number of ASP Up Ack message
received ........................................................... 2683
C901680006 Number of ASP Up Ack message sent......... 2683
C901680007 Number of ASP Down message sent .......... 2684
C901680008 Number of ASP Down message
received ........................................................... 2684
CLXIII
C901680009 Number of ASP Down Ack message

received ........................................................... 2684
C901680010 Number of ASP Down Ack message
sent................................................................. 2684
C901680011 Number of ASP Inactive message
sent................................................................. 2685
C901680012 Number of ASP Inactive message
received ........................................................... 2685
C901680013 Number of ASP Inactive Ack message
received ........................................................... 2685
sent................................................................. 2686
C901680015 Number of ASP Active message sent.......... 2686
C901680016 Number of ASP Active message
received ........................................................... 2686
C901680017 Number of ASP Active Ack message
received ........................................................... 2686
C901680018 Number of ASP Active Ack message
sent................................................................. 2687
C901680019 Number of DAUD message sent ................ 2687
C901680020 Number of SCON message received........... 2687
C901680021 Number of DAVA message received ........... 2688
C901680022 Number of DUNA message received........... 2688
C901680023 Number of invalid message received.......... 2688
C901680024 Number of MGMT message sent ................ 2688
C901680025 Number of MGMT message received .......... 2689
C901680026 Number of Heartbeat message
received ........................................................... 2689
C901680027 Number of HeartBeat Ack message
sent................................................................. 2689
C901680028 Bytes of data message received ................ 2689
C901680029 Bytes of data message transmitted............ 2690
C901680030 Bytes of MGMT message sent ................... 2690
C901680031 Bytes of MGMT message received.............. 2690
C901680032 Counts of discarding messages by Flow
Control............................................................. 2691
license ............................................................. 2691
C901680034 Bytes of all message sent......................... 2691
C901680035 Bytes of all message received ................... 2692
CLXIV
C901680036 Number of ERROR message sent............... 2692

C901680037 Number of ERROR message received ......... 2692
C901680038 Number of NOTIFY message sent .............. 2692
C901680039 Number of NOTIFY message received......... 2693
SCCP Performance Statistics ....................... 2695

Overview.................................................................. 2696
C901690001 Number of UDT Sent ............................... 2696
C901690002 Number of UDT Received ......................... 2697
C901690003 Number of UDTS Sent ............................. 2697
C901690004 Number of UDTS Received........................ 2697
C901690005 Number of ERR Sent................................ 2697
C901690006 Number of ERR Received.......................... 2698
C901690007 Number of SSP Sent................................ 2698
C901690008 Number of SSP Received.......................... 2698
C901690009 Number of RSR Sent ............................... 2698
C901690010 Number of RSR Received ......................... 2699
C901690011 Number of RSC Sent ............................... 2699
C901690012 Number of RSC Received ......................... 2699
C901690013 Number of UnAnswered SST..................... 2699
C901690014 Number of CREF Sent .............................. 2700
C901690015 Number of CREF Received ........................ 2700
C901690016 Number of XUDT Sent ............................. 2700
C901690017 Number of XUDT Received ....................... 2700
C901690018 Number of XUDTS Sent............................ 2701
C901690019 Number of XUDTS Received...................... 2701
C901690020 Number of LUDT Sent.............................. 2701
C901690021 Number of LUDT Received ........................ 2701
C901690022 Number of LUDTS Sent ............................ 2702
C901690023 Number of LUDTS Received ...................... 2702
C901690024 Number of DT1 Received.......................... 2702
C901690025 Number of DT1 Sent................................ 2702
C901690026 Number of DT2 Received.......................... 2703
C901690027 Number of DT2 Sent................................ 2703
C901690028 Number of CONNECTREQ Sent.................. 2703
C901690029 Number of CONNECTCON Received............ 2703
C901690030 Number of CONNECTIND Received ............ 2704
C901690031 Number of CONNECTRES Sent .................. 2704
C901690032 Number of DISCONNECTREQ Sent............. 2704
C901690033 Number of DISCONNECTIND received......... 2704
C901690034 Number of CR Sent ................................. 2705
CLXV
C901690035 Number of CR Received ........................... 2705

C901690036 Number of CC Sent ................................. 2705
C901690037 Number of CC Received ........................... 2705
C901690038 Number of UDT gtt.................................. 2705
C901690039 Number of UDTS gtt ................................ 2706
C901690040 Number of XUDT gtt ................................ 2706
C901690041 Number of XUDTS gtt .............................. 2706
C901690042 Number of LUDT gtt ................................ 2706
C901690043 Number of LUDTS gtt .............................. 2707
C901690044 Number of UDT gtt failure ........................ 2707
C901690045 Number of UDTS gtt failure ...................... 2707
C901690046 Number of XUDT gtt failure ...................... 2707
C901690047 Number of XUDTS gtt failure .................... 2708
C901690048 Number of LUDT gtt failure....................... 2708
C901690049 Number of LUDTS gtt failure..................... 2708
C901690050 Number of CR gtt.................................... 2708
C901690051 Number of CR gtt failure .......................... 2709
C901690052 Number of gtt Count ............................... 2709
C901690053 Number of gtt failure ............................... 2709
C901690054 Number of N_UnitDataReq LongUserData gtt
failure .............................................................. 2709
C901690055 Number of UPU received .......................... 2710
C901690056 Number of SSA received .......................... 2710
C901690057 Number of SSA sent ................................ 2710
C901690058 Number of SST received .......................... 2710
C901690059 Number of SST sent ................................ 2711
MTP3 Signaling Link Set Statistics............... 2713

Overview.................................................................. 2713
C901700001 Duration of Signaling Link Set Out of
Service ............................................................ 2713
C901700002 Times of Signaling Link Set Out of
Service ............................................................ 2714
C901700003 Number of Available Signaling Link ............ 2714
C901700004 Linkset type ........................................... 2714
M3UA Error Statistics .................................. 2715

Overview.................................................................. 2716
C901710001 Invalid Version(T) ................................... 2716
C901710002 Unsupported Message Class(T) ................. 2716
C901710003 Unsupported Message Type(T) .................. 2717
C901710004 Unexpected Message(T)........................... 2717
CLXVI
C901710005 Unsupported Traffic Mode Type(T) ............. 2717

C901710006 Invalid Routing Context(T) ....................... 2717
C901710007 Protocol Error(T)..................................... 2718
C901710008 Invalid Message Type(T) .......................... 2718
C901710009 Number of error message sent.................. 2718
C901710010 Invalid Version(R) ................................... 2718
C901710011 Unsupported Message Class(R) ................. 2719
C901710012 Unsupported Message Type(R).................. 2719
C901710013 Unexpected Message(R)........................... 2719
C901710014 Unsupported Traffic Mode Type(R) ............. 2719
C901710015 Invalid Routing Context(R) ....................... 2720
C901710016 Protocol Error(R)..................................... 2720
C901710017 Invalid Message Type(R) .......................... 2720
C901710018 Number of error message received ............ 2720
C901710019 Unknown Remote User ............................ 2721
C901710020 Unequipped Remote User ......................... 2721
C901710021 Inaccessible Remote User ........................ 2721
C901710022 Number of DUPU message received ........... 2721
C901710023 Invalid Net APPEARANCE(T) ..................... 2722
C901710024 Invalid Net APPEARANCE(R) ..................... 2722
C901710025 Number of DUPU message sent which cause
is unknown ....................................................... 2722
is Unequipped Remote User ................................ 2723
is Inaccessible Remote User ................................ 2723
C901710028 Number of DUPU message sent................. 2723
license ............................................................. 2724
C901710030 Sending invalid stream ID ........................ 2724
C901710031 Sending refuse error, reason is management
blocking ........................................................... 2724
C901710032 Sending required ASP ID.......................... 2725
C901710033 Sending invalid ASP ID ............................ 2725
C901710034 Sending invalid parameter value ............... 2725
C901710035 Sending parameter field error ................... 2725
C901710036 Sending unexpected parameter error......... 2726
C901710037 Sending destination status unknown.......... 2726
C901710038 Sending missing parameter error .............. 2726
C901710039 Sending no configured AS for ASP ............. 2726
CLXVII
C901710040 Receiving invalid stream ID ...................... 2727

C901710041 Receiving refuse error, reason is
management blocking ........................................ 2727
C901710042 Receiving required ASP ID........................ 2727
C901710043 Receiving invalid ASP ID .......................... 2727
C901710044 Receiving invalid parameter value ............. 2728
C901710045 Receiving parameter field error ................. 2728
C901710046 Receiving unexpected parameter
error................................................................ 2728
C901710047 Receiving destination status unknown......... 2728
C901710048 Receiving missing parameter error ............ 2729
C901710049 Receiving no configured AS for ASP ........... 2729
M3UA AS Performance Statistics ................. 2731

Overview.................................................................. 2731
C901720001 Number of service message transmitted .................................................................. 2731
C901720002 Bytes of service message transmitted......... 2732
C901720003 Number of service message received ......... 2732
C901720004 Bytes of service message received ............ 2732
Timer Statistics ........................................... 2733

Overview.................................................................. 2733
C901730001 Number of all timers ............................... 2733
C901730002 Number of available timer ........................ 2734
C901730003 Peak value of timer ................................. 2734
C901730004 Number of success to set timer................. 2734
C901730005 Number of failure to set timer................... 2734
Scheduling Performance Statistics .............. 2735

Overview.................................................................. 2735
C901740001 Number of active process......................... 2735
C901740002 Number of process .................................. 2736
C901740003 Number of process scheduled ................... 2736
UB Memory Performance Statistics ............. 2737

Overview.................................................................. 2737
C901750001 ID of UB Set........................................... 2737
C901750002 Size of UB.............................................. 2738
C901750003 Number of UB ........................................ 2738
C901750004 Number of UB used ................................. 2738
Hard Disk and FLASH Performance

Statistics ..................................................... 2739
CLXVIII
Overview.................................................................. 2739
C901760001 Disk Device ID........................................ 2739
C901760002 Total space............................................. 2739
C901760003 Free space ............................................. 2740
SCTP Protocol Statistics .............................. 2741

Overview.................................................................. 2742
C901770001 Number of Association Accepted ............... 2742
C901770002 Number of Association Initiated ................ 2742
C901770003 Number of Association Shutdown .............. 2742
C901770004 Number of Association Abort .................... 2743
C901770005 Number of Chunk Retransmitted ............... 2743
C901770006 Number of Unordered Chunk Sent ............. 2743
C901770007 Number of Unordered Chunk
Received .......................................................... 2743
C901770008 Number of Chunk Sent ............................ 2743
C901770009 Number of Chunk Received ...................... 2744
C901770010 Number of Init Sent ................................ 2744
C901770011 Number of Init Received .......................... 2744
C901770012 Number of Init Ack Sent .......................... 2744
C901770013 Number of Init Ack Received..................... 2744
C901770014 Number of COOKIE Sent .......................... 2745
C901770015 Number of Cookie Received ...................... 2745
C901770016 Number of Cookie Ack Sent ...................... 2745
C901770017 Number of Cookie Ack Received ................ 2745
C901770018 Number of Heartbeat Sent ....................... 2745
C901770019 Number of Heartbeat Received ................. 2746
C901770020 Number of Heartbeat Ack Sent ................. 2746
C901770021 Number of Heartbeat Ack Received............ 2746
C901770022 Number of Abort Chunk Sent .................... 2746
C901770023 Number of Abort Chunk Received .............. 2747
C901770024 Number of Shutdown Chunk Sent.............. 2747
C901770025 Number of Shutdown Chunk Received......... 2747
C901770026 Number of Shutdown Ack Chunk Sent......... 2747
C901770027 Number of Shutdown Ack Chunk
Received .......................................................... 2748
C901770028 Number of Shutdown Complete Sent ......... 2748
C901770029 Number of Shutdown Complete
Received .......................................................... 2748
C901770030 Number of Error Chunk Sent .................... 2748
C901770031 Number of Error Chunk Received .............. 2749
CLXIX
C901770032 Number of ECNE Chunk Sent .................... 2749

C901770033 Number of ECNE Chunk Received .............. 2749
C901770034 Number of CWR Chunk Sent ..................... 2749
C901770035 Number of CWR Chunk Received ............... 2750
C901770036 Number of Error Packet Received .............. 2750
C901770037 Number of OOTB Chunk Received.............. 2750
C901770038 Number of ULP Sent Chunk Request in
association alive ................................................ 2750
C901770039 Number of ULP Sent Chunk Request to SCTP
OK in association alive ....................................... 2751
C901770040 Number of ULP Sent Chunk Request during
a little time ....................................................... 2751
C901770041 Number of ULP Sent Chunk Request to SCTP
OK during a little time ........................................ 2751
C901770042 Number of SCTP Sent Chunk Request to
ULP ................................................................. 2752
C901770043 Number of Abort Request from ULP ........... 2752
C901770044 Number of Received Abort From Peer ......... 2752
C901770045 Number of Link Break for Retransfer.......... 2752
SCTP Association Statistics ......................... 2753

Overview.................................................................. 2753
C901780001 State of association................................. 2753
C901780002 Send synchronous Msg to ULP fail ............. 2754
C901780003 ULPID from ULP invalid ............................ 2754
C901780004 Number of Association Initiated to
ULP ................................................................. 2754
C901780005 Number of Association Accepted to
ULP ................................................................. 2754
C901780006 Number of Association Restarted to
ULP ................................................................. 2755
C901780007 Number of Association lost to ULP ............. 2755
C901780008 Number of Destroy instance ..................... 2755
C901780009 Number of Shutdown request from
ULP ................................................................. 2755
C901780010 Number of Abort request from ULP ............ 2756
SDTB Fiber Performance Statistics .............. 2757

Overview.................................................................. 2759
C901790001 slot number (no description) .................... 2759
C901790002 master/slave state (no description) ........... 2759
C901790003 SDH Type .............................................. 2759
CLXX
C901790004 Regenerator Section BIP-8 Error ............... 2760

C901790005 Multiplex Section BIP-24 Error .................. 2760
C901790006 VC-4 BIP-8 Error (High-order path 1)......... 2760
C901790009 Multiplex Section Remote Error
Indication ......................................................... 2761
C901790010 VC-4 Remote Error Indication (High-order
path 1) ............................................................ 2761
path 2) ............................................................ 2762
path 3) ............................................................ 2762
C901790013 Multiplex Section Remote Background Block
Error Ratio........................................................ 2762
C901790014 Multiplex Section Remote Errored Second
Ratio................................................................ 2763
C901790015 Multiplex Section Remote Errored
Second............................................................. 2763
C901790016 Multiplex Section Remote Severely Errored
Second............................................................. 2763
C901790017 Multiplex Section Remote Unavailable
Second............................................................. 2764
C901790018 VC-4 Remote Background Block Error Ratio
(High-order path 1) ........................................... 2764
(High-order path 2) ........................................... 2765
(High-order path 3) ........................................... 2765
C901790021 VC-4 Remote Errored Second Ratio
(High-order path 1) ........................................... 2765
(High-order path 2) ........................................... 2766
(High-order path 3) ........................................... 2766
C901790024 VC-4 Remote Errored Second (High-order
path 1) ............................................................ 2766
path 2) ............................................................ 2767
CLXXI

path 3) ............................................................ 2767
C901790027 VC-4 Remote Severely Errored Second
(High-order path 1) ........................................... 2767
(High-order path 2) ........................................... 2768
(High-order path 3) ........................................... 2768
C901790030 VC-4 Remote Unavailable Second
(High-order path 1) ........................................... 2768
(High-order path 2) ........................................... 2769
(High-order path 3) ........................................... 2769
C901790033 B1(Regenerator Section) BIP-8 Background
Block Error Ratio ............................................... 2769
C901790034 B1(Regenerator Section) BIP-8 Errored
Second Ratio..................................................... 2770
C901790035 B1(Regenerator Section) BIP-8 Errored
Second............................................................. 2770
C901790036 B1(Regenerator Section) BIP-8 Severely
Errored Second ................................................. 2771
C901790037 B1(Regenerator Section) BIP-8 Unavailable
Second............................................................. 2771
C901790038 B2(Multiplex Section) BIP-24 Background
Block Error Ratio ............................................... 2771
C901790039 B2(Multiplex Section) BIP-24 Errored Second
Ratio................................................................ 2772
C901790040 B2(Multiplex Section) BIP-24 Errored
Second............................................................. 2772
C901790041 B2(Multiplex Section) BIP-24 Severely
Errored Second ................................................. 2773
C901790042 B2(Multiplex Section) BIP-24 Unavailable
Second............................................................. 2773
C901790043 B3(VC-4) BIP-8 Background Block Error
Ratio (High-order path 1) ................................... 2773
CLXXII
C901790046 B3(VC-4) BIP-8 Errored Second Ratio

(High-order path 1) ........................................... 2775
(High-order path 2) ........................................... 2775
(High-order path 3) ........................................... 2775
C901790049 B3(VC-4) BIP-8 Errored Second (High-order
path 1) ............................................................ 2776
path 2) ............................................................ 2776
path 3) ............................................................ 2776
C901790052 B3(VC-4) BIP-8 Severely Errored Second
(High-order path 1) ........................................... 2777
(High-order path 2) ........................................... 2777
(High-order path 3) ........................................... 2777
C901790055 B3(VC-4) BIP-8 Unavailable Second
(High-order path 1) ........................................... 2778
(High-order path 2) ........................................... 2778
(High-order path 3) ........................................... 2778
C901790058 LOF second ............................................ 2779
PEB22554 E1 Performance Statistics........... 2781

Overview.................................................................. 2781
C901800001 Frame type ............................................ 2782
C901800002 slip Duration ......................................... 2782
C901800003 Near end available Second ....................... 2782
C901800004 Near end unavailable Second.................... 2783
C901800005 Near end Errored Second ......................... 2783
C901800006 Near end Severely Errored Second ............ 2783
C901800007 Near end Background Block Error .............. 2784
C901800008 Frame Alignment Signal error ................... 2784
C901800009 Cyclic Redundancy Check 4 error .............. 2784
C901800010 Bit error rate(PPM) .................................. 2784
C901800011 Near end unavailable Second rate(One
ten-thousandth) ................................................ 2785
CLXXIII
C901800012 Near end Errored Second rate(One

ten-thousandth) ................................................ 2785
C901800013 Near end Severely Errored Second rate(One
ten-thousandth) ................................................ 2785
C901800014 Near end Background Block Error rate......... 2785
C901800015 far end available Second .......................... 2786
C901800016 far end unavailable Second ...................... 2786
C901800017 far end Errored Second ............................ 2786
C901800018 far end Severely Errored Second ............... 2787
C901800019 far end Background Block Error................. 2787
C901800020 E-Bit ERROR........................................... 2787
C901800021 far end unavailable Second rate(One
ten-thousandth) ................................................ 2787
C901800022 far end Errored Second rate(One
ten-thousandth) ................................................ 2788
C901800023 far end Severely Errored Second rate(One
ten-thousandth) ................................................ 2788
C901800024 far end Background Block Error rate(One
ten-thousandth) ................................................ 2788
PEB22554 T1 Performance Statistics........... 2789

Overview.................................................................. 2789
C901810001 Frame type ............................................ 2790
C901810002 slip Duration ......................................... 2790
C901810003 Near end available Second ....................... 2790
C901810004 Near end unavailable Second.................... 2790
C901810005 Near end Errored Second ......................... 2791
C901810006 Near end Severely Errored Second ........... 2791
C901810007 number of Near end Background Block
Error................................................................ 2791
C901810008 number of Frame Alignment Signal
error................................................................ 2792
C901810009 number of Cyclic Redundancy Check 6
error................................................................ 2792
C901810010 Bit error rate (PPM) ................................. 2792
ten-thousandth) ................................................ 2792
C901810012 Near end Errored Second rate (One
ten-thousandth) ................................................ 2793
C901810013 Near end Severely Errored Second rate(One
ten-thousandth) ............................................... 2793
CLXXIV
C901810014 Near end Background Block Error rate......... 2793
MAC Port Flow Statistics.............................. 2795

Overview.................................................................. 2795
C901820001 receive bytes number (high 4 bytes) ......... 2796
C901820002 receive bytes number (low 4 bytes)........... 2796
C901820003 transmit bytes number (high 4 bytes)......... 2796
C901820004 transmit bytes number (low 4 bytes) ......... 2797
C901820005 physical band width................................. 2797
C901820006 mean receiving bit rate ............................ 2797
C901820007 max receiving bit rate.............................. 2798
C901820008 mean transmitting bit rate ....................... 2798
C901820009 max transmitting bit rate ......................... 2798
C901820010 Number of packets discarded at RX side
(high 4 bytes) ................................................... 2799
C901820011 Number of packets discarded at RX side (low
4 bytes) ........................................................... 2799
C901820012 Number of packets discarded at TX side
(high 4 bytes) ................................................... 2799
C901820013 Number of packets discarded at TX side (low
4 bytes) ........................................................... 2800
C901820014 Number of packets received when receiving
bit rate is max during performance period............. 2800
C901820015 Number of packets sent when sending bit
rate is max during performance period ................. 2800
AMR Rate Statistics ..................................... 2801

Overview.................................................................. 2801
C901830001 Total Num of DL AFS12.2k frame............... 2802
C901830009 Total Num of DL AHS7.95k frame .............. 2805
CLXXV
C901830015 Total Num of UL AFS12.2k frame............... 2808

C901830023 Total Num of UL AHS7.95k frame .............. 2811
PPP channel measurement .......................... 2815

C901840001 Received byte count ................................ 2815
C901840002 Received packet count ............................. 2815
C901840003 Received framing aborts .......................... 2816
C901840004 Received FCS errors ................................ 2816
C901840005 Received packets greater than maximum
length .............................................................. 2816
C901840006 Non-octet aligned frames received ............ 2817
C901840007 Received small datagrams discarded byte
count ............................................................... 2817
C901840008 Received jumbo packets byte count ........... 2817
C901840009 Received small datagrams discarded event
count ............................................................... 2817
C901840010 Received jumbo packets count .................. 2818
C901840011 Transmitted byte count ............................ 2818
C901840012 Transmitted packet count ......................... 2818
C901840013 Transmit framing aborts........................... 2818
C901840014 MLPPP ID ............................................... 2819
C901840015 PPP band width ...................................... 2819
UMAC Measurement .................................... 2821

Overview.................................................................. 2823
C901850001 receive discard packets flag...................... 2823
C901850002 receive discard packets low 32bits............. 2824
C901850003 receive discard packets high 32bits ........... 2824
C901850004 receive bytes flag.................................... 2824
C901850005 receive bytes low 32bits........................... 2825
CLXXVI
C901850006 receive bytes high 32bits ......................... 2825

C901850007 receive packets flag ................................ 2825
C901850008 receive packets low 32bits ....................... 2826
C901850009 receive packets high 32bits ...................... 2826
C901850010 receive broadcast packets flag .................. 2826
C901850011 receive broadcast packets low 32bits ......... 2827
C901850012 receive broadcast packets high 32bits......... 2827
C901850013 receive multicast packets flag ................... 2827
C901850014 receive multicast packets low 32bits .......... 2828
C901850015 receive multicast packets high 32bits......... 2828
C901850016 receive CRC or align error packets
flag.................................................................. 2828
C901850017 receive CRC or align error packets low
32bits .............................................................. 2829
C901850018 receive CRC or align error packets high
32bits .............................................................. 2829
C901850019 receive small than 64 bytes packets
flag.................................................................. 2829
C901850020 receive small than 64 bytes packets low
32bits .............................................................. 2830
C901850021 receive small than 64 bytes packets high
32bits .............................................................. 2830
C901850022 receive large than 1518 bytes packets
flag.................................................................. 2830
C901850023 receive large than 1518 bytes packets low
32bits .............................................................. 2831
C901850024 receive large than 1518 bytes packets high
32bits .............................................................. 2831
C901850025 The flag of received fragment packets......... 2831
C901850026 Number of fragment packets received (low
32 bit) ............................................................. 2832
C901850027 Number of received fragment packets (high
32 bit) ............................................................. 2832
C901850028 receive Jabber packets flag ...................... 2832
C901850029 receive Jabber packets low 32bits ............. 2833
C901850030 receive Jabber packets high 32bits ............ 2833
C901850031 receive Collision count flag ....................... 2833
C901850032 receive Collision count low 32bits .............. 2834
C901850033 receive Collision count high 32bits............. 2834
C901850034 receive 64 bytes packets flag.................... 2834
CLXXVII
C901850035 receive 64 bytes packets low 32bits........... 2835

C901850036 receive 64 bytes packets high 32bits ......... 2835
C901850037 receive 65 to 127 bytes packets flag.......... 2835
C901850038 receive 65 to 127 bytes packets low
32bits .............................................................. 2836
C901850039 receive 65 to 127 bytes packets high
32bits .............................................................. 2836
C901850040 receive 128 to 255 bytes packets flag......... 2836
32bits .............................................................. 2837
32bits .............................................................. 2837
32bits .............................................................. 2838
32bits .............................................................. 2838
C901850046 receive 512 to 1023 bytes packets
flag.................................................................. 2838
32bits .............................................................. 2839
32bits .............................................................. 2839
C901850049 receive 1024 to 1518 bytes packets
flag.................................................................. 2839
32bits .............................................................. 2840
32bits .............................................................. 2840
C901850052 send discard packets flag ......................... 2840
C901850053 send discard packets low 32bits ................ 2841
C901850054 send discard packets high 32bits............... 2841
C901850055 send packet bytes flag ............................. 2841
C901850056 send packet bytes low 32bits .................... 2842
C901850057 send packets bytes high 32bits ................. 2842
C901850058 send packets flag .................................... 2842
C901850059 send packets low 32bits ........................... 2843
C901850060 send packets high 32bits.......................... 2843
C901850061 send broadcast packets flag ..................... 2843
C901850062 send broadcast packets low 32bits ............ 2844
CLXXVIII
C901850063 send broadcast packets high 32bits ........... 2844

C901850064 send multicast packets flag ...................... 2844
C901850065 send multicast packets low 32bits ............. 2845
C901850066 send multicast packets high 32bits ............ 2845
C901850067 send CRC or Align error packets flag.......... 2845
C901850068 send CRC or Align error packets low
32bits .............................................................. 2846
C901850069 send CRC or Align error packets high
32bits .............................................................. 2846
C901850070 send small than 64 bytes packets flag......... 2846
C901850071 send small than 64 bytes packets low
32bits .............................................................. 2847
C901850072 send small than 64 bytes packets high
32bits .............................................................. 2847
C901850073 send large than 1518 bytes packets
flag.................................................................. 2847
C901850074 send large than 1518 bytes packets low
32bits .............................................................. 2848
C901850075 send large than 1518 bytes packets high
32bits .............................................................. 2848
C901850076 The flag of sent fragment packets ............. 2848
C901850077 Number of sent fragment packets (low 32
bit) .................................................................. 2849
C901850078 Number of sent fragment packets (high 32
bit) .................................................................. 2849
C901850079 send Jabber packets flag.......................... 2849
C901850080 send Jabber packets low 32bits................. 2850
C901850081 send Jabber packets high 32bits ............... 2850
C901850082 send Collision count flag .......................... 2850
C901850083 send Collision count low 32bits ................. 2851
C901850084 send Collision count high 32bits ................ 2851
C901850085 send 64 bytes packets flag ....................... 2851
C901850086 send 64 bytes packets low 32bits .............. 2852
C901850087 send 64 bytes packets high 32bits............. 2852
C901850088 send 65 to 127 bytes packets flag ............. 2852
C901850089 send 65 to 127 bytes packets low
32bits .............................................................. 2853
C901850090 send 65 to 127 bytes packets high
32bits .............................................................. 2853
C901850091 send 128 to 255 bytes packets flag ........... 2853
CLXXIX

32bits .............................................................. 2854
32bits .............................................................. 2854
C901850094 send 256 to 511 bytes packets flag ........... 2854
32bits .............................................................. 2855
32bits .............................................................. 2855
C901850097 send 512 to 1023 bytes packets flag.......... 2855
32bits .............................................................. 2856
32bits .............................................................. 2856
C901850100 send 1024 to 1518 bytes packets flag......... 2856
32bits .............................................................. 2857
32bits .............................................................. 2857
C901850103 Logic port type ....................................... 2857
PS Handover Cause Measurement ............... 2859

Overview.................................................................. 2859
C901880001 Number of handover attempts due to uplink
received strength .............................................. 2860
downlink received strength ................................. 2860
quality ............................................................. 2861
downlink quality ................................................ 2862
interference ...................................................... 2862
downlink interference ......................................... 2863
PBGT ............................................................... 2864
C901880008 Number of handover attempts due to large
TA ................................................................... 2864
break up quickly................................................ 2865
CLXXX

macro-micro switch ........................................... 2866
C901880011 Number of handover attempts due to high
traffic............................................................... 2866
C901880012 Number of handover attempts due to a good
standard level in FDD adjacent cell ...................... 2867
standard level in TDD adjacent cell ...................... 2868
PCCN ............................................................... 2869
PS General Handover Measurement ............ 2871

Overview.................................................................. 2872
executions ........................................................ 2872
C901890002 Number of successful synchronous
handovers ........................................................ 2873
executions ........................................................ 2874
C901890004 Number of successful pre-synchronous
handovers ........................................................ 2875
executions ........................................................ 2876
C901890006 Number of successful asynchronous
handovers ........................................................ 2877
C901890007 Number of normal handover
executions ........................................................ 2878
C901890008 Number of successful normal
handovers ........................................................ 2879
C901890009 Number of optimised handover
executions ........................................................ 2880
C901890010 Number of successful optimised
handovers ........................................................ 2880
C901890011 Number of Intra-BSC inter-cell handover out
attempts .......................................................... 2881
C901890012 Number of Intra-BSC inter-cell handover out
executions ........................................................ 2882
C901890013 Number of successful Intra-BSC inter-cell
handover out .................................................... 2883
C901890014 Number of Inter-BSC handover out
attempts .......................................................... 2884
CLXXXI
C901890015 Number of Inter-BSC handover out

executions ........................................................ 2885
C901890016 Number of successful Inter-BSC handover
out .................................................................. 2885
C901890017 Number of handover in attempts............... 2886
C901890018 Number of handover in executions ............ 2887
C901890019 Number of successful handover in ............. 2887
C901890020 Number of Intra-cell handover
attempts .......................................................... 2888
C901890021 Number of Intra-Cell handover
executions ........................................................ 2889
C901890022 Number of successful Intra-cell
handovers ........................................................ 2889
C901890023 Number of invalid Intra-cell handovers ............................................................. 2889
C901890024 Number of 2G to FDD handover
attempts .......................................................... 2890
C901890025 Number of 2G to FDD handover
executions ........................................................ 2890
C901890026 Number of successful 2G to FDD
handovers ........................................................ 2891
C901890027 Number of 2G to TDD handover
attempts .......................................................... 2892
C901890028 Number of 2G to TDD handover
executions ........................................................ 2892
C901890029 Number of successful 2G to TDD
handovers ........................................................ 2893
C901890030 Number of 3G to 2G handover
attempts .......................................................... 2894
C901890031 Number of 3G to 2G handover
executions ........................................................ 2894
C901890032 Number of successful 3G to 2G
handovers ........................................................ 2895
C901890033 Number of T12 expiry.............................. 2896
C901890034 Number of PCCF received......................... 2896
messages received with cause Create PFC
Failure ............................................................. 2897
CLXXXII

messages received with cause PS Handover Target
not allowed ...................................................... 2898
messages received with cause PS Handover not
Supported in Target BSS or Target System ............ 2899
messages received with cause other reasons ......... 2899
C901890039 Number of failure in optimised handover due
to failure alloc resource ..................................... 2900
C901890040 Number of failure in optimised handover due
to PS handover not supported in target cell ........... 2901
IURG Measurement ..................................... 2903

Overview.................................................................. 2903
C901900001 Number of relocation requests (on
Iur-g) .............................................................. 2903
C901900002 Number of relocation executions (on
Iur-g) .............................................................. 2904
C901900003 Number of relocation successes (on
Iur-g) .............................................................. 2906
C901900004 Number of relocation failures due to no valid
radio resource (on Iur-g) .................................... 2907
terrestrial circuit resource (on Iur-g) .................... 2907
C901900006 Number of relocation failures due to loss of
UE handover complete message (on Iur-g) ........... 2908
C901900007 Number of relocation failures due to MS
returning to original channel (on Iur-g) ................ 2909
C901900008 Number of relocation failures due to other
causes (on Iur-g) .............................................. 2910
RTCP Measurement ..................................... 2911

Overview.................................................................. 2911
C901910001 local jitter (CS)....................................... 2911
C901910002 distant jitter (CS).................................... 2912
C901910003 average one-way delay (CS)..................... 2913
C901910004 maximal one-way delay (CS) .................... 2915
C901910005 local cumulative fraction lost (CS) ............. 2917
C901910006 distant cumulative fraction lost (CS) .......... 2918
C901910007 local jitter (PS) ....................................... 2919
C901910008 distant jitter (PS) .................................... 2920
CLXXXIII
C901910009 average one-way delay (PS) ..................... 2921

C901910010 maximal one-way delay (PS) .................... 2923
C901910011 local cumulative fraction lost (PS) ............. 2925
C901910012 distant cumulative fraction lost (PS) .......... 2926
DSP Measurement ....................................... 2929

Overview.................................................................. 2929
C901920001 the times of loss of TRAU frame
synchronization in BIPB ...................................... 2929
Access Control Measurement....................... 2931

Overview.................................................................. 2931
C901930001 Number of CS Call Denied for Lack of IPAbis
BandWidth UpLink ............................................. 2932
BandWidth DownLink ......................................... 2932
C901930003 Number of PS Call Denied for Lack of IPAbis
BandWidth UpLink ............................................. 2933
BandWidth DownLink ......................................... 2934
C901930005 Number of Pushing Down Uplink
BandWidth........................................................ 2934
C901930006 Number of Pushing Down Downlink
BandWidth ....................................................... 2935
C901930007 Number of Pushing Up Uplink BandWidth
....................................................................... 2936
C901930008 Number of Pushing Up Downlink
BandWidth........................................................ 2937
C901930034 Number of CS Call Denied for Lack of
IPAbis BandWidth UpLink But Preempt PS IPAbis
Successfully...................................................... 2937
C901930035 Number of CS Call Denied for Lack of
IPAbis BandWidth DownLink But Preempt PS IPAbis
Successfully...................................................... 2938
Power Control Measurement ....................... 2939

Overview.................................................................. 2939
C901940001 The count of iBSC receiving power control
indication from BTS............................................ 2940
C901940002 The count of channel downlink power
exceeding TRX mean downlink power, when iBSC
receives power control indication from BTS ........... 2940
CLXXXIV
C901940003 The count of CS service channel allocation

failure caused by power shortage......................... 2941
C901940004 The count of CS timeslot allocation failure
caused by power shortage .................................. 2943
C901940005 The count of PS service channel allocation
failure caused by power shortage......................... 2944
C901940006 The count of PS timeslot allocation failure
caused by power shortage .................................. 2945
PS Adjacent Cell Handover Measurement ........................................................... 2947

Overview.................................................................. 2948
C901950001 Number of handover attempts on the
adjacent cell ..................................................... 2948
C901950002 Number of successful handovers from
selected cell to the adjacent cell .......................... 2949
C901950003 Number of handover attempts from adjacent
cell to the selected cell ....................................... 2950
adjacent cell to the selected cell .......................... 2951
cell to the adjacent cell due to better uplink
quality ............................................................. 2952
cell to the adjacent cell due to better downlink
quality ............................................................. 2954
selected cell to the adjacent cell due to better uplink
quality ............................................................. 2955
selected cell to the adjacent cell due to better
downlink quality ................................................ 2956
cell to the adjacent cell due to better uplink
strength ........................................................... 2958
cell to the adjacent cell due to better downlink
strength ........................................................... 2959
selected cell to the adjacent cell due to better uplink
strength ........................................................... 2960
CLXXXV

selected cell to the adjacent cell due to better
downlink strength .............................................. 2962
selected cell to the adjacent cell due to PBGT......... 2964
cell to the adjacent cell due to large TA ................ 2965
selected cell to the adjacent cell due to large
TA ................................................................... 2966
cell to the adjacent cell due to high traffic ............. 2968
selected cell to the adjacent cell due to high
traffic............................................................... 2969
LAPDm Measurement .................................. 2971

Overview.................................................................. 2972
C902000001 Number of Error Indications due to T200
expired on SDCCH ............................................. 2973
C902000002 Number of Error Indications due to
unsolicited message on SDCCH............................ 2973
unsolicited DM response on SDCCH ...................... 2974
C902000004 Number of Error Indications due to sequence
error on SDCCH................................................. 2975
C902000005 Number of Error Indications due to frame
content error on SDCCH ..................................... 2975
C902000006 Number of Error Indications due to SABM
command on SDCCH .......................................... 2976
expired on TCH/F............................................... 2977
unsolicited message on TCH/F ............................. 2977
unsolicited DM response on TCH/F ....................... 2978
error on TCH/F .................................................. 2979
CLXXXVI

content error on TCH/F....................................... 2979
command on TCH/F ........................................... 2980
expired on TCH/H .............................................. 2981
unsolicited message on TCH/H ............................ 2981
unsolicited DM response on TCH/H ....................... 2982
error on TCH/H ................................................. 2983
content error on TCH/H ...................................... 2983
command on TCH/H........................................... 2984
C902000019 Number of Release Indications due to T200
expired on SDCCH ............................................. 2985
C902000020 Number of Release Indications due to
unsolicited DM response on SDCCH ...................... 2985
sequence error on SDCCH................................... 2986
expired on TCH/F (signaling) ............................... 2987
unsolicited DM response on TCH/F (signaling)......... 2988
sequence error on TCH/F (signaling) .................... 2988
expired on TCH/F (speech).................................. 2989
unsolicited DM response on TCH/F (speech) .......... 2990
sequence error on TCH/F (speech) ....................... 2991
expired on TCH/F (data) ..................................... 2991
unsolicited DM response on TCH/F (data).............. 2992
sequence error on TCH/F (data) .......................... 2993
CLXXXVII

expired on TCH/H (signaling) .............................. 2994
unsolicited DM response on TCH/H (signaling)......... 2994
sequence error on TCH/H (signaling) .................... 2995
expired on TCH/H (speech) ................................. 2996
unsolicited DM response on TCH/H (speech).......... 2997
error on TCH/H (speech) .................................... 2997
expired on TCH/H (data)..................................... 2998
unsolicited DM response on TCH/H (data) ............. 2999
sequence error on TCH/H (data) .......................... 3000
C902000040 Number of Release Indications without Error
Ind on SDCCH................................................... 3000
Ind on TCH/F (signaling) .................................... 3001
Ind on TCH/F (speech) ....................................... 3001
Ind on TCH/F (data)........................................... 3002
Ind on TCH/H (signaling) .................................... 3002
Ind on TCH/H (speech)....................................... 3002
Ind on TCH/H (data) .......................................... 3003
Access Control Detailed Cause Measurement ........................................................... 3005

Overview.................................................................. 3005
C902010001 Number of PS Uplink BandWidth Allocated
More than Overbooking ...................................... 3006
C902010002 Number of PS Uplink BandWidth Measured
More than C2 ................................................... 3007
CLXXXVIII
C902010003 Number of that Sum of PS Uplink BandWidth

Measured and Current BandWidth Allocated More
than C1............................................................ 3008
C902010004 Number of PS Downlink BandWidth Allocated
C902010005 Number of PS Downlink BandWidth
Measured More than C2...................................... 3010
C902010006 Number of that Sum of PS Downlink
BandWidth Measured and Current BandWidth
Allocated More than C1 ...................................... 3011
C902010007 Number of CS Uplink BandWidth Allocated
More than Overbooking ..................................... 3012
C902010008 Number of CS Uplink BandWidth Measured
More than C2 .................................................... 3012
C902010009 Number of that Sum of CS Uplink BandWidth
Measured and Current BandWidth Allocated More
than C1............................................................ 3013
C902010010 Number of CS Downlink BandWidth Allocated
C902010011 Number of CS Downlink BandWidth
Measured More than C2...................................... 3015
C902010012 Number of that Sum of CS Downlink
BandWidth Measured and Current BandWidth
Allocated More than C1 ...................................... 3016
BSC Group Call Setup Measurement ............ 3019

Overview.................................................................. 3019
C902020001 Number of VGCS setup attempts............... 3019
C902020002 Number of VGCS setup success ................ 3020
C902020003 Number of VGCS setup failure .................. 3021
C902020004 Number of VBS setup attempts ................. 3021
C902020005 Number of VBS setup success................... 3022
C902020006 Number of VBS setup failure..................... 3023
VGCS Measurement ..................................... 3025

Overview.................................................................. 3026
C902030001 Number of VGCS assignment
attempts .......................................................... 3026
C902030002 Number of VGCS assignment success......... 3027
C902030003 Number of VGCS assignment failure .......... 3027
C902030004 Number of VGCS Inter-BSC outgoing
handover attempts of Talker................................ 3028
CLXXXIX

handover execution of Talker............................... 3029
handover success of Talker ................................. 3030
handover failure of Talker ................................... 3031
C902030008 Number of VGCS Inter-BSC incoming
C902030011 Number of VGCS channel request attempts
for NOTIFICATION RESPONSE of Listener .............. 3034
C902030012 Number of VGCS channel request success
C902030013 Number of VGCS channel request failure for
NOTIFICATION RESPONSE of Listener................... 3036
C902030014 Number of VGCS channel release for Listener
detection .......................................................... 3037
C902030015 Number of Talker drops due to radio link
failure .............................................................. 3038
C902030016 Number of Talker quit .............................. 3039
C902030017 Number of attempts for Listener uplink
request ............................................................ 3039
C902030018 Number of VGCS Intra-BSC Inter-cell
outgoing handover attempts of Talker................... 3040
outgoing handover execution of Talker.................. 3041
outgoing handover success of Talker .................... 3042
outgoing handover failure of Talker ...................... 3043
incoming handover attempts of Talker .................. 3044
incoming handover execution of Talker ................. 3045
incoming handover success of Talker .................... 3046
C902030025 Number of NCH overflow of VGCS ............. 3046
CXC
C902030026 Number of successes for Listener uplink

request ............................................................ 3047
C902030027 Number of failures for Listener uplink
request ............................................................ 3048
VBS Measurement ....................................... 3049

Overview.................................................................. 3050
C902040001 Number of VBS assignment attempts......... 3050
C902040002 Number of VBS assignment success .......... 3051
C902040003 Number of VBS assignment failure ............ 3051
C902040004 Number of VBS Inter-BSC outgoing
C902040008 Number of VBS Inter-BSC incoming
C902040011 Number of VBS channel request attempts
C902040012 Number of VBS channel request success for
C902040013 Number of VBS channel request failure for
C902040014 Number of VBS channel release for Listener
detection .......................................................... 3061
C902040015 Number of VBS Intra-BSC Inter-cell outgoing
CXCI
C902040019 Number of VBS Intra-BSC Inter-cell

incoming handover attempts of Talker .................. 3066
incoming handover execution of Talker ................. 3067
incoming handover success of Talker .................... 3068
C902040022 Number of NCH overflow of VBS ............... 3068
C902040023 Number of Talker drops due to radio link
failure .............................................................. 3069
eMLPP Measurement ................................... 3071

Overview.................................................................. 3072
C902050001 Number of Talker is preempted ................. 3072
C902050002 Number of Listener is preempted .............. 3072
C902050003 Number of preempt attempts due to VGCS
setup ............................................................... 3073
C902050004 Number of preempt attempts due to VBS
setup ............................................................... 3074
C902050005 Number of preempt execution due to VGCS
setup ............................................................... 3075
C902050006 Number of preempt execution due to VBS
setup ............................................................... 3076
C902050007 Number of preempt attempts due to
C902050008 Number of preempt execution due to
Inter-BSC handover of Talker .............................. 3079
Inter-BSC handover of Talker .............................. 3080
Intra-BSC Inter-cell handover of Talker................. 3081
C902050013 Number of queuing attempts due to VGCS
setup ............................................................... 3083
C902050014 Number of queuing execution due to VGCS
setup ............................................................... 3084
C902050015 Number of queuing attempts due to VBS
setup ............................................................... 3085
CXCII
C902050016 Number of queuing execution due to VBS

setup ............................................................... 3086
C902050017 Number of queuing attempts due to
C902050018 Number of queuing execution due to
inter-BSC incoming handover of Talker ................. 3089
inter-BSC incoming handover of Talker ................. 3090
Flow Control Measurement.......................... 3093

Overview.................................................................. 3093
C902110001 The number of Channel Requests
overflowing....................................................... 3093
C902110002 The number of Paging Messages
overflowing....................................................... 3094
SDCCH General Handover Measurement ........................................................... 3095

Overview.................................................................. 3096
handover attempts (On SDCCH) .......................... 3097
handover (On SDCCH) ....................................... 3098
handover success (On SDCCH) ............................ 3099
handover request failures due to unclear factors (On
SDCCH) ........................................................... 3101
handover request failures due to unavailable radio
resource (On SDCCH) ........................................ 3102
handover request failures due to other factors (On
SDCCH) ........................................................... 3103
CXCIII

incoming handover attempts (On SDCCH)............. 3106
incoming handover (On SDCCH) .......................... 3107
handover attempts due to forced release (On
SDCCH) ........................................................... 3108
handover due to forced release (On SDCCH) ......... 3109
handover attempts due to queue (On SDCCH)......... 3110
handover due to queue (On SDCCH) .................... 3111
handover attempts due to forced handover (On
SDCCH) ........................................................... 3112
handover due to forced handover (On
SDCCH) ........................................................... 3113
incoming handover success (On SDCCH)............... 3114
C902120019 BSC-controlled incoming handover time due
to queue (On SDCCH) ........................................ 3115
handover queue (On SDCCH) .............................. 3116
C902120021 BSC-controlled incoming handover success
time due to queue (On SDCCH) ........................... 3118
handover success due to queue (On SDCCH)......... 3119
unavailable radio resource (On SDCCH) ................ 3120
other factors (On SDCCH)................................... 3121
CXCIV

handover attempts due to forced release (On
SDCCH) ........................................................... 3123
handover due to forced release (On SDCCH) ......... 3124
handover attempts due to queue (On SDCCH)......... 3125
handover due to queue (On SDCCH) .................... 3126
handover attempts due to forced handover (On
SDCCH) ........................................................... 3127
handover due to forced handover (On
SDCCH) ........................................................... 3128
C902120034 MSC-controlled incoming handover time due
to queue (On SDCCH) ........................................ 3129
handover queue (On SDCCH) .............................. 3131
C902120036 MSC-controlled incoming handover success
time due to queue (On SDCCH) ........................... 3133
handover success due to queue (On SDCCH)......... 3134
Local Switch Measurement .......................... 3135

Overview.................................................................. 3135
C902130001 The Request Number of Local Switch
Establish (Inside BSC)........................................ 3136
Establish (Inside Site) ........................................ 3136
Establish (Inside Site Group)............................... 3137
C902130004 The Request Number of Local Switch Release
(Return Normal Call) .......................................... 3137
C902130005 The Failure Number of Establishing Local
Switch (Inside BSC/Connect Fail) ......................... 3138
CXCV

Switch (Inside BSC/Other Reason Fail) ................. 3139
Switch (Inside Site/Fail Returned by Site) ............. 3139
Switch (Inside Site Group/Fail Returned by
Site) ................................................................ 3140
Switch (Inside Site/No answer from Site).............. 3141
C902130010 The Failure Number of Establishing
Local Switch (Inside Site Group/No answer from
Site) ................................................................ 3142
Switch (Inside Site/Other Reason Fail).................. 3142
Switch (Inside Site Group/Other Reason Fail)......... 3143
C902130013 The Failure Number of Returning Normal Call
(Abis unavailable).............................................. 3143
(Connect Fail) ................................................... 3144
(Ater unavailable) .............................................. 3145
TFO Measurement ....................................... 3147

C902420001 Number of first try to contact distant partner
after TFO being enabled ..................................... 3147
C902420002 Number of retrying to contact distant
partner after being interrupted ............................ 3148
C902420003 Number of TFO contacting with distant
partner after first try.......................................... 3149
C902420004 Number of TFO recontacting with distant
partner after TFO being interrupted...................... 3150
C902420005 Number of TFO establishment after first
try................................................................... 3151
C902420006 Number of TFO reestablishment after being
interrupted ....................................................... 3152
C902420007 Number of synchronization lost at
A-Interface resulting in TFO off............................ 3153
C902420008 Number of codec type mismatch resulting in
TFO off............................................................. 3154
CXCVI
C902420009 Number of rate control failure resulting in

TFO off when using AMR codec type ..................... 3155
TFO ................................................................. 3155
TFO ................................................................. 3156
establishing TFO ................................................ 3156
optimizing TFO .................................................. 3156
IP SLA PD Statistic ...................................... 3157

C902270001 PD Type ................................................. 3157
C902270002 PD SubType ........................................... 3158
C902270003 ULP Pno................................................. 3158
C902270004 ULP TYPE ............................................... 3158
C902270005 ULP ID .................................................. 3158
C902270006 Packet Type............................................ 3159
C902270007 Up Protocol ............................................ 3159
C902270008 Source IP 1 ............................................ 3159
C902270009 Source IP 2 ............................................ 3159
C902270010 Source IP 3 ............................................ 3159
C902270011 Source IP 4 ............................................ 3160
C902270012 Source Port ............................................ 3160
C902270013 Destination IP 1...................................... 3160
C902270014 Destination IP 2...................................... 3160
C902270015 Destination IP 3...................................... 3161
C902270016 Destination IP 4...................................... 3161
C902270017 Destination Port ...................................... 3161
C902270018 Send PD Request .................................... 3162
C902270019 Receive PD Reply .................................... 3162
C902270020 PD Packet Loss Rate ................................ 3162
C902270021 PD Packet statistics by watch time............. 3162
C902270022 PD Packet Loss Rate by watch time ........... 3163
C902270023 PD Packet Out of Sequence ...................... 3163
C902270024 Receive PD Request................................. 3163
C902270025 Send PD Reply........................................ 3164
C902270025 Min Delay .............................................. 3164
C902270027 Max Delay.............................................. 3164
C902270028 Mean Delay ............................................ 3164
C902270029 Max Jitter .............................................. 3165
CXCVII
C902270030 Min Jitter ............................................... 3165

C902270031 Mean Jitter............................................. 3165
C902270032 Jitter Sampling Times .............................. 3165
C902270033 Number of delay sampling........................ 3166
Corresponding Relationship between

Basic Measurement Counters and General
Measurement Counters ............................... 3167
Figures ........................................................ 3185
Tables ......................................................... 3313
Glossary ...................................................... 3315
CXCVIII
About This Manual

Purpose
Intended
Audience
What Is in This
Manual
This manual explains the description, usage, and measurement

point of each performance counter in ZXG10 iBSC Subsystem. It
helps user analyze and locate faults through querying counters.
System Engineer
Testing Engineer
Planning Engineer
This manual contains the following chapters.

Section
Summary
Chapter 1, PS Basic
Measurement (BSC)
Introduces the detailed information about

counters related to PS basic measurement
(BSC).
Chapter 2, PS Basic
Measurement (Cell)

counters related to PS basic measurement
(Cell).
Chapter 3, CPU Load

Measurement

counters related to CPU load measurement.
Chapter 4, CS Basic
Measurement

counters related to CS basic measurement.
Chapter 5, Configuration
Management Information
Basic Measurement

counters related to configuration
management information basic
measurement.
Chapter 6, Downlink
Data TBF Measurement

counters related to downlink data TBF
measurement.
Chapter 7, Uplink Data

TBF Measurement

counters related to uplink data TBF
measurement.
Chapter 8, Data Flow

Measurement

counters related to data flow.
Chapter 9, UplinkDownlink RLC Statistic

Measurement

counters related to uplink/downlink RLC
statistic measurement.
Chapter 10, PS
Resource Used Statistic
Measurement

counters related to PS resource used
statistic measurement.
Chapter 11,
RMM Assignment
Measurement

counters related to RMM assignment
measurement.
II
Section
Summary
Chapter 12, Handover

Cause Measurement

counters related to handover cause
measurement.
Chapter 13, RMM Call

Drop Measurement
Introduces the detailed information

about counters related to RMM call drop
measurement.
Chapter 14, Radio

Resource Availability
Measurement

about counters related to radio resource
availability measurement.
Chapter 15, General

Handover Measurement

counters related to general handover
measurement.
Chapter 16, Adjacent Cell


counters related to adjacent cell handover
measurement.
Chapter 17, Radio Access

Measurement

about counters related to radio access
measurement.
Chapter 18, Radio

Measurement

counters related to radio measurement.
Chapter 19, Sub Cell

Statistics

counters related to sub cell statistics.
Chapter 20, MS TA
Measurement

counters related to MS TA measurement.
Chapter 21, SAPI3

Measurement

counters related to SAPI3 measurement.
Chapter 22, Uplink

and Downlink PACCH
Statistics

counters related to uplink and downlink
PACCH statistics.
Chapter 23, Downlink

GPRS data TBF Statistics

counters related to downlink GPRS data
TBF statistics.
Chapter 24, Downlink

EGPRS data TBF
Statistics

counters related to downlink EGPRS data
TBF statistics.
Chapter 25, Uplink GPRS

data TBF Statistics

counters related to uplink GPRS data TBF
statistics.
Chapter 26, Uplink

EGPRS Data TBF
Statistics

counters related to uplink EGPRS data TBF
statistics.
Chapter 27, BSSGP Flow

Statistics

counters related to BSSGP flow statistics.
Chapter 28, TRX

Measurement

counters related to TRX measurement.
About This Manual
Section
Summary
Chapter 29, Gb Interface

Message Statistics

counters related to Gb interface message
statistics.
Chapter 30, Timeslot

Measurement

counters related to timeslot measurement.
Chapter 31, SDCCH

Measurement

counters related to SDCCH measurement.
Chapter 32, TCH/F

Measurement

counters related to TCH/F measurement.
Chapter 33, TCH/H

Measurement

counters related to TCH/H measurement.
Chapter 34, Abis

Interface Message
Counter Measurement

counters related to Abis interface message
counter measurement.
Chapter 35, Gb Message

Statistics (BVC Cell)

counters related to Gb interface message
statistics (BVC cell).
Chapter 36, NSVC

Statistic Measurement

about counters related to NSVC statistic
measurement.
Chapter 37, NSE Statistic

Measurement

about counters related to NSE statistic
measurement.
Chapter 38, BTS TRX

Measurement

counters related to BTS TRX measurement.
Chapter 39, NSVC on

IPGB HOST Measurement

counters related to NSVC on IPGB HOST
measurement.
Chapter 40, GB
Message on IPGB HOST
Measurement

counters related to GB message on IPGB
HOST measurement.
Chapter 41, NSE on IPGB

HOST Measurement

counters related to NSE on IPGB HOST
measurement.
Chapter 42, BSSMAP

Message Measurement

counters related to BSSMAP message
measurement.
Chapter 43, A-Interface

Message Measurement

counters related to A-Interface message
measurement.
Chapter 44, Terrestrial

Resource Availability
Measurement

counters related to terrestrial resource
availability measurement.
Chapter 45, Ater

Message Measurement

about counters related to Ater message
measurement.
III
IV
Section
Summary
Chapter 46, MTP2

Signaling Link
Measurement

counters related to MTP2 signaling link
measurement.
Chapter 47, CPU/MEM

Measurement

about counters related to CPU/MEM
measurement.
Chapter 48, SCTP AS

Measurement

counters related to SCTP AS measurement.
Chapter 49, IP Port

Performance Statistics

counters related to IP port performance
statistics.
Chapter 50, GTRUNK

Resource Statistics

counters related to GTRUNK resource
statistics.
Chapter 51, Other

Process Statistics

counters related to other process statistics.
Chapter 52, FR Carried

Links Statistics

counters related to FR carried links
statistics.
Chapter 53, OMP PS

Service Statistics

counters related to OMP PS service
statistics.
Chapter 54, SNS on OMP

Statistics

counters related to SNS on OMP statistics.
Chapter 55, IPGB

StrongARM NSVC
Statistics

counters related to IPGB StrongARM NSVC
statistics.
Chapter 56, IPGB

StrongARM Gb Statistics

counters related to IPGB StrongARM Gb
statistics.
Chapter 57, Queue

Measurement

counters related to queue measurement.
Chapter 58, Handover

Synchronization Mode
Measurement

about counters related to handover
synchronization mode measurement.
Chapter 59, Paging

Message Measurement

counters related to paging message
measurement.
Chapter 60, Reserved

Channel Measurement

counters related to reserved channel
measurement.
Chapter 61, SCCP

Connection Measurement

counters related to SCCP connection
measurement.
Chapter 62, DTM Cell

Measurement

counters related to DTM cell measurement.
About This Manual
Section
Summary
Chapter 63, LAPD

Measurement

counters related to LAPD measurement.
Chapter 64, LCS

Measurement

counters related to LCS measurement.
Chapter 65, LB Global

Message Measurement

counters related to LB global message
measurement.
Chapter 66 Ater Interface

Relays Measurement

counters related to Ater interface relays
measurement.
Chapter 67,
Ater Interface
SCCP Connections
Measurement

counters related to Ater interface SCCP
connections measurement.
Chapter 68,
Measurement
Report Serving Cell
Measurement

counters related to measurement report
serving cell measurement.
Chapter 69,
Measurement Report
Adjacent Cell
Measurement

counters related to measurement report
adjacent cell measurement.
Chapter 70, TRX Paging

Measurement

about counters related to TRX paging
measurement.
Chapter 71, TRX

Temperature Power
Measurement

counters related to TRX temperature power
measurement.
Chapter 72, Terminal

Ability Statistics

about counters related to terminal ability
statistics.
Chapter 73, MTP3

Signaling Link Statistics

counters related to MTP3 signaling link
statistics.
Chapter 74, M3UA


counters related to M3UA performance
statistics.
Chapter 75, SCCP


counters related to SCCP performance
statistics.
Chapter 76, MTP3

Signaling Link Set
Statistics

counters related to MTP3 signaling link set
statistics.
Chapter 77, M3UA Error

Statistics

counters related to M3UA error statistics.
VI
Section
Summary
Chapter 78, M3UA AS


counters related to M3UA AS performance
statistics.
Chapter 79, Timer

Statistics

counters related to timer statistics.
Chapter 80, Scheduling


counters related to scheduling performance
statistics.
Chapter 81, UB Memory


about counters related to UB memory
performance statistics.
Chapter 82, Hardware

and FLASH Performance
Statistics

counters related to hardware and FLASH
Chapter 83, SCTP

Protocol Stack Statistics

counters related to SCTP protocol stack
statistics.
Chapter 84, SCTP

Association ULP Statistics

counters related to SCTP association ULP
statistics.
Chapter 85, SDTB Fiber


counters related to SDTB fiber performance
statistics.
Chapter 86, PEB22554

E1 Performance Statistics

about counters related to PEB22554 E1
Chapter 87, PEB22554

T1 Performance Statistics

about counters related to PEB22554 T1
Chapter 88, MAC Port

Flow Statistics

counters related to MAC port flow statistics.
Chapter 89, AMR Rate

Statistics

counters related to AMR rate statistics.
Chapter 90, PPP channel

measurement

about counters related to PPP channel
measurement.
Chapter 91, UMAC

Measurement

counters related to UMAC measurement.
Chapter 92, PS Handover

Cause Measurement

counters related to PS handover cause
measurement.
Chapter 93, PS General


counters related to PS general handover
measurement.
Chapter 94, IURG

Measurement

counters related to IURG measurement.
About This Manual
Section
Summary
Chapter 95, RTCP

Measurement

counters related to RTCP measurement.
Chapter 96, DSP

Measurement

counters related to DSP measurement.
Chapter 97, Access

Control Measurement

about counters related to access control
measurement.
Chapter 98, Power

Control Measurement

about counters related to power control
measurement.
Chapter 99, PS
Adjacent Cell Handover
Measurement

counters related to PS adjacent cell
handover measurement.
Chapter 100, LAPDm

Measurement

counters related to LAPDm measurement.
Chapter 101, Access

Control Detailed Cause
Measurement

counters related to access control detailed
cause measurement.
Chapter 102, BSC Group

Call Setup Measurement

counters related to BSC group call setup
measurement.
Chapter 103, VGCS

Measurement

counters related to VGCS measurement.
Chapter 104, VBS

Measurement

counters related to VBS measurement.
Chapter 105, eMLPP

Measurement

counters related to eMLPP measurement.
Chapter 106, Flow

Control Measurement

about counters related to flow control
measurement.
Chapter 107, SDCCH

General Handover
Measurement

about counters related to SDCCH general
handover measurement.
Chapter 108, Local

Switch Measurement

about counters related to local switch
measurement.
Chapter 109, TFO

Measurement

counters related to TFO Measurement.
Chapter 110, IP SLA PD

Statistic

counters related to IP SLA PD Statistic.
VII
This page is intentionally blank.
VIII
Chapter
PS Basic Measurement
(BSC)
Table of Contents
Overview........................................................................... 1
C900030001 Number of bytes received from data link ............. 1
C900030002 Number of bytes sent to data link ..................... 1
Overview
PS basic measurement (BSC) consists of statistic of the number of
bytes received from data link and bytes sent to data link.
The measurement takes BSC as the statistics unit.
C900030001 Number of
bytes received from data link
Description
This counter counts the total number of bytes received from all
BRCHs on FR sub-layer.
Usage
This counter is used to find out the bytes received from BRCH and
to observe BSC load status.
Measurement
Point
Unit
FR accumulates all the bytes received from Gb interface BRCH.

Byte
bytes sent to data link
Description
This counter counts the total number of bytes sent from all BRCHs
on FR sub-layer.
Usage
Measurement
Point
Unit
This counter is used to find out the bytes sent from BRCH and to
observe BSC load status.
FR accumulates all the bytes sent from Gb interface BRCH.
Byte
Chapter
PS Basic Measurement
(Cell)
Table of Contents
Overview..........................................................................10
C900040001 Number of GPRS DL TBF establishment success
on PACCH.........................................................................11
C900040002 Number of GPRS DL TBF release due to N3105
overflow ...........................................................................12
C900040003 Number of GPRS DL TBF release due to other
reasons............................................................................13
C900040004 Number of GPRS DL TBF forcing release by control plane .........................................................................14
C900040005 Number of GPRS DL TBF release due to instance
suspension .......................................................................15
C900040006 Number of GPRS DL TBF release due to inner
abnormal .........................................................................15
C900040007 Number of GPRS DL signaling TBF establishment ...............................................................................16
C900040008 Number of GPRS DL data TBF establishment ...............................................................................16
C900040009 Number of EGPRS DL TBF establishment success
on PACCH.........................................................................17
C900040010 Number of EGPRS DL TBF release due to N3105
overflow ...........................................................................18
C900040011 Number of EGPRS DL TBF release due to other
reasons............................................................................19
C900040012 Number of EGPRS DL TBF forcing release by control plane .........................................................................20
C900040013 Number of EGPRS DL TBF release due to instance suspension .............................................................21
C900040014 Number of EGPRS DL TBF release due to inner
abnormal .........................................................................21
C900040015 Number of EGPRS DL signaling TBF establishment ...............................................................................22
C900040016 Number of EGPRS DL data TBF establishment ...............................................................................22
C900040017 Average number of GPRS DL TBF simultaneous
establishment ..................................................................23
C900040018 Average number of EGPRS DL TBF simultaneous
establishment ..................................................................23
C900040019 Number of GPRS UL data TBF establishment success on PACCH ..................................................................23
C900040020 Number of GPRS UL TBF release due to N3101
overflow ...........................................................................24
C900040021 Number of GPRS UL TBF release due to N3103
overflow ...........................................................................25
C900040022 Number of GPRS UL TBF forcing release by control plane .........................................................................25

C900040023 Number of GPRS UL TBF release due to instance
suspension .......................................................................26
C900040024 Number of GPRS UL TBF release due to inner
abnormal .........................................................................26
C900040025 Number of GPRS UL signaling TBF establishment ...............................................................................27
C900040026 Number of GPRS UL data TBF establishment ...............................................................................29
C900040027 Number of EGPRS UL TBF establishment success
on PACCH.........................................................................30
C900040028 Number of EGPRS UL TBF release due to N3101
overflow ...........................................................................31
C900040029 Number of EGPRS UL TBF release due to N3103
overflow ...........................................................................31
C900040030 Number of EGPRS UL TBF forcing release by control plane .........................................................................32
C900040031 Number of EGPRS UL TBF release due to instance suspension .............................................................32
C900040032 Number of EGPRS UL TBF release due to inner
abnormal .........................................................................33
C900040033 Number of EGPRS UL signaling TBF establishment ...............................................................................33
C900040034 Number of EGPRS UL data TBF establishment ...............................................................................33
C900040035 Average number of GPRS UL TBF simultaneous
establishment ..................................................................34
C900040036 Average number of EGPRS UL TBF simultaneous
establishment ..................................................................34
C900040037 Number of GPRS UL signaling TBF release due
to N3101 overflow .............................................................35
to N3103 overflow .............................................................35
C900040039 Number of GPRS UL signaling TBF forcing release by control plane ........................................................36
to instance suspension .......................................................36
to inner abnormal..............................................................36
C900040042 Number of EGPRS UL signaling TBF release due
to N3101 overflow .............................................................37
to N3103 overflow .............................................................37
C900040044 Number of EGPRS UL signaling TBF forcing release by control plane ........................................................38
to instance suspension .......................................................38
to inner abnormal..............................................................38
C900040047 Number of EGPRS DL LLC frames ......................39
C900040048 Number of discarded EGPRS DL LLC frames due
to buffer overflow ..............................................................39
to life time expiration .........................................................40
to other reasons ...............................................................41
C900040051 Number of DL signaling LLC frames ...................41
C900040052 Number of discarded EGPRS DL signaling LLC
frames due to buffer overflow .............................................42
Chapter 2 PS Basic Measurement (Cell)

frames due to life time expiration ........................................43
frames due to other reasons ...............................................43
C900040055 Number of data blocks transmitted according to
given Abis bandwidth .........................................................44
C900040056 Bytes of effective upper layer protocol data sent
on DL PDCH .....................................................................44
C900040057 Bytes of effective upper layer protocol data received on UL PDCH ...........................................................45
C900040058 Bytes of LLC frame on GPRS UL data TBF ..........46
C900040059 Duration of GPRS UL data TBF ..........................46
C900040060 Bytes of LLC frame on GPRS DL data TBF ..........48
C900040061 Duration of GPRS DL data TBF ..........................48
GPRS UL TBF ....................................................................49
C900040063 Number of NACK blocks received on GPRS UL
TBF ................................................................................50
C900040064 Number of effective data blocks sent on GPRS
DL TBF ............................................................................51
C900040065 Number of NACK blocks sent on GPRS DL TBF
......................................................................................51
C900040066 Bytes of LLC frame on EGPRS UL data TBF .........52
C900040067 Duration of EGPRS UL data TBF ........................53
C900040068 Bytes of LLC frame on EGPRS DL data TBF .........54
C900040069 Duration of EGPRS DL data TBF ........................55
C900040070 Number of effective data blocks received on EGPRS UL TBF ......................................................................56
C900040071 Number of NACK blocks received on EGPRS UL
TBF ................................................................................57
C900040072 Number of effective data blocks sent on EGPRS
DL TBF ............................................................................58
C900040073 Number of NACK blocks sent on EGPRS DL TBF
......................................................................................58
C900040074 Number of GPRS DL LLC frames........................59
C900040075 Number of discarded GPRS DL LLC frames due
to buffer overflow ..............................................................60
to life time expiration .........................................................61
to other reasons ................................................................61
C900040078 Number of DL dummy control blocks on
PACCH .............................................................................62
C900040079 Number of UL dummy control blocks on
PACCH .............................................................................63
C900040080 Number of DL RLC blocks on PACCH (excluding
dummy block)...................................................................63
PDTCH .............................................................................64
PDTCH .............................................................................65
PDTCH .............................................................................65
PDTCH .............................................................................66
PDTCH .............................................................................67
PDTCH .............................................................................67

PDTCH .............................................................................68
PDTCH .............................................................................69
PDTCH .............................................................................70
PDTCH .............................................................................70
PDTCH .............................................................................71
PDTCH .............................................................................72
C900040093 Number of UL RLC blocks excluding dummy
blocks on PACCH ...............................................................72
PDTCH .............................................................................73
PDTCH .............................................................................74
PDTCH .............................................................................74
PDTCH .............................................................................75
PDTCH .............................................................................76
PDTCH .............................................................................76
PDTCH .............................................................................77
PDTCH .............................................................................78
PDTCH .............................................................................79
PDTCH .............................................................................79
PDTCH .............................................................................80
PDTCH .............................................................................81
C900040106 Number of UL data blocks received on
PDTCH .............................................................................81
C900040107 Number of DL data blocks sent on PDTCH...........82
C900040108 Number of GPRS DL TBF establishment requests
......................................................................................82
due to database allocation failure ........................................83
requests due to UL TBF establishment .................................84
failure of channel allocation due to UL TBF establishment .........85
requests due to LLC transmission.........................................86
failure of channel allocation due to LLC transmission .............86
C900040114 Number of EGPRS DL TBF establishment requests .............................................................................87
C900040115 Number of EGPRS DL TBF establishment failure
C900040116 Number of EGPRS DL TBF resource reallocation
requests due to UL TBF establishment .................................89

failure of channel allocation due to UL TBF establishment .........90
failure of channel allocation due to LLC transmission .............91
C900040120 Number of GPRS UL TBF establishment requests
......................................................................................92
C900040121 Number of GPRS UL TBF establishment failure
requests due to DL TBF establishment ..................................94
failure of channel allocation due to DL TBF establishment .........95
failure of channel allocation due to LLC transmission ..............96
requests for resource request..............................................97
failure due to database allocation failure for resource request ...............................................................................98
C900040128 Number of EGPRS UL TBF establishment requests .............................................................................99
C900040129 Number of EGPRS UL TBF establishment failure
C900040130 Number of EGPRS UL TBF resource reallocation
requests due to DL TBF establishment ................................ 100
C900040131 Number of EGPRS UL TBF resource reallocation failure of channel allocation due to DL TBF establishment ............................................................................. 101
requests due to LLC transmission....................................... 102
failure of channel allocation due to LLC transmission ............ 102
requests for resource request............................................ 103
C900040135 Number of EGPRS UL TBF resource reallocation failure due to database allocation failure for resource request ............................................................................. 104
C900040136 Average number of available PDCH.................. 105
C900040137 Number of forcing conversation dynamic from
PDCH to TCH by BSC ....................................................... 105
C900040138 Number of PDCH used by TBF in each cell ......... 105
C900040139 Maximum number of used PDCH ..................... 106
C900040140 Average number of used PDCH ....................... 106
before T3192 expiration ................................................... 107
C900040142 Number of GPRS DL TBF establishment using
existing DL TBF resource .................................................. 108
on PACCH....................................................................... 108
on CCCH/PCCCH.............................................................. 109
C900040145 Number of EGPRS DL TBF establishment requests before T3192 expiration ......................................... 110
C900040146 Number of EGPRS DL TBF establishment using
existing DL TBF resource .................................................. 111
C900040147 Number of EGPRS DL TBF establishment requests on PACCH............................................................. 112

C900040148 Number of EGPRS DL TBF establishment requests on CCCH/PCCCH.................................................... 113
C900040149 Number of GPRS DL signaling TBF release due
to N3105 overflow ........................................................... 114
to other reasons .............................................................. 115
C900040151 Number of GPRS DL signaling TBF forcing release by control plane ...................................................... 115
to instance suspension ..................................................... 116
to inner abnormal............................................................ 117
C900040154 Number of EGPRS DL signaling TBF release due
to N3105 overflow ........................................................... 118
to other reasons .............................................................. 119
C900040156 Number of EGPRS DL signaling TBF forcing release by control plane ...................................................... 120
to instance suspension ..................................................... 120
to inner abnormal............................................................ 121
C900040159 Number of GPRS UL TBF establishments in release state...................................................................... 122
C900040160 Number of GPRS UL TBF establishment with existing UL resource............................................................ 123
on PACCH....................................................................... 124
C900040162 Number of EGPRS UL data TBF establishments
on PACCH....................................................................... 124
C900040163 Number of EGPRS UL TBF establishments in release state...................................................................... 125
C900040164 Number of EGPRS UL TBF establishment with
existing UL resource ........................................................ 126
C900040165 Number of EGPRS UL TBF establishment requests on PACCH............................................................. 127
C900040166 Number of EGPRS UL TBF establishment requests on CCCH/PCCCH.................................................... 127
C900040167 Number of dynamic PDCH preemption for CS
service ........................................................................... 128
on CCCH/PCCCH.............................................................. 129
on PACCH....................................................................... 129
C900040170 Number of EGPRS DL TBF establishment requests on PACCH............................................................. 130
on PACCH....................................................................... 130
C900040172 Number of DL RLC pending blocks in MCS1 on
PDTCH ........................................................................... 130
PDTCH ........................................................................... 131
PDTCH ........................................................................... 132
PDTCH ........................................................................... 133
PDTCH ........................................................................... 133

PDTCH ........................................................................... 134
PDTCH ........................................................................... 135
PDTCH ........................................................................... 135
PDTCH ........................................................................... 136
PDTCH ........................................................................... 137
PDTCH ........................................................................... 138
PDTCH ........................................................................... 138
PDTCH ........................................................................... 139
PDTCH ........................................................................... 140
PDTCH ........................................................................... 140
PDTCH ........................................................................... 141
PDTCH ........................................................................... 142
PDTCH ........................................................................... 143
PDTCH ........................................................................... 143
PDTCH ........................................................................... 144
PDTCH ........................................................................... 145
PDTCH ........................................................................... 145
PDTCH ........................................................................... 146
PDTCH ........................................................................... 147
PDTCH ........................................................................... 148
PDTCH ........................................................................... 148
PDTCH ........................................................................... 149
C900040199 Number of UL RLC pending blocks in MCS1 on
PDTCH ........................................................................... 150
PDTCH ........................................................................... 150
PDTCH ........................................................................... 151
PDTCH ........................................................................... 152
PDTCH ........................................................................... 153
PDTCH ........................................................................... 153
PDTCH ........................................................................... 154
PDTCH ........................................................................... 155

PDTCH ........................................................................... 155
PDTCH ........................................................................... 156
PDTCH ........................................................................... 157
PDTCH ........................................................................... 158
PDTCH ........................................................................... 158
PDTCH ........................................................................... 159
PDTCH ........................................................................... 160
PDTCH ........................................................................... 160
PDTCH ........................................................................... 161
PDTCH ........................................................................... 162
PDTCH ........................................................................... 163
PDTCH ........................................................................... 163
PDTCH ........................................................................... 164
PDTCH ........................................................................... 165
PDTCH ........................................................................... 165
PDTCH ........................................................................... 166
PDTCH ........................................................................... 167
PDTCH ........................................................................... 168
PDTCH ........................................................................... 168
C900040232 Accumulated throughput of UL GPRS TBF ......... 169
C900040233 Accumulated throughput of DL GPRS TBF ......... 170
C900040234 Accumulated throughput of UL EGPRS TBF ......... 170
C900040235 Accumulated throughput of DL EGPRS TBF ......... 171
Overview
PS basic measurement (Cell) involves the ordinary counters used
to measure the PS service performance and status, such as the
uplink (UL) /downlink (DL) TBF counter, the flow counter, the
UL/DL PACCH counter, the UL/DL RLC counter, the UL/DL GPRS
data counter, the UL/DL EGPRS data counter, and the PS resource
counter.
The measurement takes cell as the statistics unit.
10
C900040001 Number
of GPRS DL TBF
establishment success
on PACCH
Description
This counter counts the number of successful DL GPRS TBF establishments on the UL/DL GPRS TBF PACCH.
Measurement
Point
When the DL GPRS TBF is established on the UL/DL GPRS TBF

PACCH and a message indicating assignment success is sent, this
counter increments. The measurement points are A as shown in
Figure 1 and Figure 2, and A2 as shown in Figure 3.
FIGURE 1 MEASUREMENT POINT OF NUMBER OF REQUESTS FOR
ESTABLISHING GPRS DOWNLINK DATA TBF BEFORE T3192 OVERTIME
FIGURE 2 MEASUREMENT POINT OF NUMBER OF ESTABLISHED GPRS

DOWNLINK DATA TBF USING EXISTING RESOURCES
11

ESTABLISHING GPRS DOWNLINK DATA TBF ON UPLINK GPRS TBF PACCH
Unit
Times
GPRS DL TBF release due
to N3105 overflow
Description
During the DL TBF transmission, the DL block RRBP bit is set to

ask MS to respond with a Packet Downlink Ack/Nack message.
If the specified block of BSC fails to receive response from MS,
then the N3105 counter increments; otherwise, it has a clear. If no
response comes from the MS, then the RRBP bit is set again to ask
MS to respond with a Packet Downlink Ack/Nack message; if the
N3105 counter reaches its maximum value, it is considered that
the radio transmission fails and the DL TBF is released abnormally.
Measurement
Point
12
When the N3105 counter value exceeds N3105Max, this counter

increments. The measurement point is A1, as shown in Figure 4.
FIGURE
DUE TO
Unit
4 MEASUREMENT POINT
N3105 OVERFLOW
OF
NUMBER
OF
GPRS DL TBF RELEASE
Times
to other reasons
Description
When BSC is transmitting the last DL TBF RLC block, set FBI to
1, set RRBP to ask the MS to respond with a Packet Downlink
Ack/Nack message, and at the same time, activate T3191. If the
specified block receives the MS response, then T3191 will stop and
the DL transmission ends normally. If T3191 overflows, then it is
considered that the radio transmission fails and the DL TBF is released abnormally.
13
Measurement
Point
The measurement point is A1, as shown in Figure 5.

FIGURE
DUE TO
Unit
5 MEASUREMENT POINT
OTHER REASONS
OF
NUMBER
OF
GPRS DL TBF RELEASE
Times
GPRS DL TBF forcing
release by control plane
Description
When the user plane is transmitting the DL TBF, if a release request

comes from the control plane, then the DL TBF will stop and be
released abnormally.
Measurement
Point
When the user plane receives the release request from the control
plane, this counter increments. The measurement point is A, as
shown in Figure 6.
FIGURE 6 MEASUREMENT POINT
RELEASE BY CONTROL PLANE
14
OF
NUMBER
OF
GPRS DL TBF FORCING
Unit
Times
to instance suspension
Description
When the user plane is transmitting the DL TBF, at least one block
must be transmitted in every 5 seconds. After a DL TBF block is
transmitted, BSC will start or restart a 5-second DL block assigning
timer. If the timer expires, it is considered that the user plane has
an instance suspension and the DL TBF is released abnormally.
Measurement
Point
When the DL block assigning timer expires, this counter increments. The measurement point is A, as shown in Figure 7.
FIGURE
DUE TO
Unit
7 MEASUREMENT POINT
INSTANCE SUSPENSION
OF
NUMBER
OF
GPRS DL TBF RELEASE
Times
to inner abnormal
Description
When the user plane is transmitting the DL TBF, if the message

fails to be sent at the radio interface, the RLC instance fails to
15
be created, or the resource reassignment fails, the DL TBF will be

Measurement
Point
Unit
During the DL TBF transmission, if the message fails to be sent

at the radio interface, the RLC instance fails to be created, or the
resource reassignment fails, this counter increments.
Times
GPRS DL signaling TBF
establishment
Description
According to the type of the transmitted UL data, TBF has two

categories: signaling TBF and data TBF.
This counter counts the number of establishments of GPRS DL TBF
for UL signaling transmission. The UL signaling involves some UL
processes such as ATTACH, PDP activation, and routing area update.
Measurement
Point
Unit
When the DL TBF is created successfully and the TBF type is GPRS
signaling TBF, the counter increments. The measurement point is
similar to those of C900040001 and C901000014.
Times
C900040008 Number
of GPRS DL data TBF
establishment
Description

This counter counts the number of establishments of GPRS DL TBF
for user data (no-UL-signaling) transmission.
Measurement
Point
Unit
16
When the DL TBF is created successfully and the TBF type is GPRS
data TBF, the counter increments. The measurement point is similar to those of C900040001 and C901000014.
Times
C900040009 Number
of EGPRS DL TBF
on PACCH
Description
This counter counts the number of successful DL EGPRS TBF establishments on the UL/DL EGPRS TBF PACCH.
Measurement
Point
When the DL EGPRS TBF is established on the UL/DL EGPRS TBF

PACCH and a message indicating assignment success is sent, this
counter increments. The measurement points are A as shown in
Figure 8 and Figure 9, and A2 as shown in Figure 10.
ESTABLISHING GPRS DOWNLINK DATA TBF BEFORE T3192 OVERTIME
FIGURE 9 MEASUREMENT POINT OF NUMBER OF ESTABLISHED GPRS

DOWNLINK DATA TBF USING EXISTING RESOURCES
17

ESTABLISHING GPRS DOWNLINK DATA TBF ON UPLINK GPRS TBF PACCH
Unit
Times
EGPRS DL TBF release due
to N3105 overflow
Description
During the DL TBF transmission, the DL block RRBP bit is set to

ask the MS to respond with a Packet Downlink Ack/Nack message.
If the specified block of BSC does not receive the MS response,
then the N3105 counter increments; if it does, then it has a clear;
if no response comes from the MS, then the RRBP bit is set again to
ask the MS to respond with a Packet Downlink Ack/Nack message;
if the N3105 counter reaches its maximum value, it is considered
that the radio transmission fails and the DL TBF is released abnormally.
Measurement
Point
18

increments. The measurement point is A1, as shown in Figure 11.
FIGURE
DUE TO
Unit
11 MEASUREMENT POINT
N3105 OVERFLOW
OF
NUMBER
OF
EGPRS DL TBF RELEASE
Times
to other reasons
Description
When BSC is transmitting the last DL TBF RLC block, set FBI to
1, set RRBP to ask the MS to respond with a Packet Downlink
Ack/Nack message, and at the same time, activate T3191. If the
specified block receives the MS response, then T3191 will stop and
the DL transmission ends normally. If T3191 overflows, then it is
considered that the radio transmission fails and the DL TBF is released abnormally.
19
Measurement
Point

FIGURE
DUE TO
Unit
OTHER REASONS
OF
NUMBER
OF
Times
EGPRS DL TBF forcing
Description
When the user plane is transmitting the DL TBF, if a release request

comes from the control plane, then the DL TBF will stop and be
Measurement
Point
shown in Figure 13.
20
OF
NUMBER
OF
EGPRS DL TBF FORCING
Unit
Times
Description
When the user plane is transmitting the DL TBF, at least one block
must be transmitted in every 5 seconds. After a DL TBF block is
transmitted, BSC will start or restart a 5-second DL block assigning
timer. If the timer expires, it is considered that the user plane has
an instance suspension and the DL TBF is released abnormally.
Measurement
Point
When the DL block assigning timer expires, this counter increments. The measurement point is A1, as shown in Figure 14.
FIGURE
DUE TO
Unit
INSTANCE SUSPENSION
OF
NUMBER
OF
Times
to inner abnormal
Description
When the user plane is transmitting the DL TBF, if the message

21
be created, or the resource reassignment fails, the DL TBF will be

Measurement
Point
Unit
During the DL TBF transmission, if the message fails to be sent

at the radio interface, the RLC instance fails to be created, or the
resource reassignment fails, this counter increments.
Times
EGPRS DL signaling TBF
establishment
Description

This counter counts the number of establishments of EGPRS DL
TBF for UL signaling transmission. The UL signaling involves some
UL processes such as ATTACH, PDP activation, and routing area
update.
Measurement
Point
Unit
When the DL TBF is created successfully and the TBF type is signaling TBF, the counter increments. The measurement point is
similar to those of C900040001 and C901000014.
Times
EGPRS DL data TBF
establishment
Description

This counter counts the number of establishments of EGPRS DL
TBF for user data (no-UL-signaling) transmission.
Measurement
Point
Unit
22
When the DL TBF is created successfully and the TBF type is data
TBF, the counter increments. The measurement point is similar to
those of C900040001 and C901000014.
Times
C900040017 Average
number of GPRS DL TBF
simultaneous establishment
Description
This counter counts the average number of DL GPRS TBF establishments in a cell.
Measurement
Point
The counter acquires the measurement value regularly. The number of GPRS TBFs existing in the cell is considered the average
number.
Unit
Times
C900040018 Average
number of EGPRS DL TBF
Description
This counter counts the average number of DL EGPRS TBF establishments in a cell.
Measurement
Point
The counter acquires the measurement value regularly. The number of EGPRS TBFs existing in the cell is considered the average
number.
Unit
Times
C900040019 Number
of GPRS UL data TBF
establishment success on
PACCH
Description
When MS has a DL TBF and the TBF is being transmitted, if the

UL data need to be transmitted but there is no corresponding UL
TBF, then the Packet Downlink Ack message will carry the UL TBF
establishment request. Usually BSS will assign the resource to MS,
and then an UL TBF is established successfully.
Usage
The counter counts the number of successful GPRS UL TBF establishments on PACCH
23
Measurement
Point
The measurement point is A, as shown in Figure 15.

FIGURE 15 MEASUREMENT POINT OF NUMBER
ESTABLISHMENT SUCCESS ON PACCH
Unit
OF
GPRS UL DATA TBF
Times
GPRS UL TBF release due
to N3101 overflow
Description
After the UL TBF is established, MS will transmit data on the BSSassigned UL block. If the specified block of BSS fails to receive RLC
block from MS, N3101 increments. Otherwise, N3101 will have a
clear. When N3101 exceeds the maximum value, BSS will release
UL TBF.
Usage
The counter counts the number of abnormal releases of GPRS UL

TBF due to N3101 overflow.
Measurement
Point
The measurement point is N3101 overflow, as A shown in Figure

16.
FIGURE
DUE TO
Unit
24
N3101 OVERFLOW
OF
NUMBER
Times
OF
GPRS UL TBF RELEASE
to N3103 overflow
Description
When BSS receives all UL RLC blocks, it will send MS a Packet

Uplink Ack message in which FAI and RRBP are set. MS will report
Packet Control Ack to the corresponding UL block. If BSS fails to
receive it, N3103 increments. When N3103 exceeds the maximum
value, BSS will release UL TBF.
Usage

Measurement
Point
The measurement point is N3103 overflow, as A shown in Figure

17.
FIGURE
DUE TO
Unit
N3103 OVERFLOW
OF
NUMBER
OF
GPRS UL TBF RELEASE
Times
GPRS UL TBF forcing
Description
When an UL TBF establishment is held, the control plane may

forcibly release this UL TBF.
Usage
The counter counts the number of forced releases of GPRS UL TBF

due to release request from the control plane.
Measurement
Point
The measurement point is arrival of the release request, as A

shown in Figure 18.
25

Unit
OF
NUMBER
OF
GPRS UL TBF FORCING
Times
Description
BSS creates an instance for an UL TBF. If the instance is suspended

for some reason, then BSS should release this UL TBF.
Usage

TBF due to suspension of the instance.
Measurement
Point
The measurement point is that UPPB detects suspension of the

instance, as A shown in Figure 19.
FIGURE
DUE TO
Unit
INSTANCE SUSPENSION
OF
NUMBER
OF
GPRS UL TBF RELEASE
Times
to inner abnormal
Description
26
TBF is abnormally released due to UPPB internal error.
Usage

TBF due to internal error.
Measurement
Point
The measurement point is abnormal UPPB suspension, as B shown

in Figure 20.
FIGURE
DUE TO
Unit
INSTANCE SUSPENSION
OF
NUMBER
OF
GPRS UL TBF RELEASE
Times
GPRS UL signaling TBF
establishment
Description
For different purpose, MS may establish two types of TBF: signaling

TBF and data TBF.
Usage
The counter counts the number of GPRS UL signaling TBF link establishments.
Measurement
Point
The measurement point is that UPPB access type is signaling TBF.

For all 1-step accesses, their type is considered signaling TBF, as
A1 shown in Figure 21. For the 2-step accesses, the TBF type is
detected as SIGNAL_TBF, as A1 shown in Figure 22.
27
FIGURE 21 UL TBF FLOW
28
OF
1-STEP ACCESS
Unit
OF
2-STEP ACCESS
Times
C900040026 Number
of GPRS UL data TBF
establishment
Description

TBF and data TBF.
Usage
The counter counts the number of GPRS UL data TBF link establishments.
Measurement
Point
The measurement point is when UPPB access type is data TBF. For
example, the TBF type is detected as DATA_TBF, as A1 shown in
Figure 23.
29
Unit
OF
2-STEP ACCESS
Times
C900040027 Number
of EGPRS UL TBF
on PACCH
Description
30
When MS has a DL TBF and the TBF is being transmitted, if the

UL data need to be transmitted but there is no corresponding UL
TBF, then the Packet Downlink Ack message will carry the UL TBF
establishment request. Usually BSS will assign the resource to MS,
and then an UL TBF is established successfully.
Usage
Measurement
Point
The counter counts the number of successful EGPRS UL TBF establishments on PACCH.
ESTABLISHMENT SUCCESS ON PACCH
Unit
OF
EGPRS UL TBF
Times
EGPRS UL TBF release due
to N3101 overflow
Description
UL TBF.
Usage
The counter counts the number of abnormal releases of EGPRS UL

Measurement
Point
Unit
The measurement point is when N3101 overflow.

Times
to N3103 overflow
Description

31
Usage
Measurement
Point
Unit

The measurement point is when N3103 overflow.
Times
EGPRS UL TBF forcing
Description

Usage
The counter counts the number of forced releases of EGPRS UL

TBF due to release request from the control plane.
Measurement
Point
Unit
The measurement point is arrival of the release request.

Times
Description

Usage

TBF due to suspension of the instance.
Measurement
Point

instance.
Unit
32
Times
to inner abnormal
Description
Usage
Measurement
Point
Unit

TBF due to internal error.
The measurement point is abnormal UPPB suspension.
Times
EGPRS UL signaling TBF
establishment
Description

TBF and data TBF.
Usage
The counter counts the number of EGPRS UL signaling TBF link

establishments.
Measurement
Point
The measurement point is that UPPB access type is signaling TBF.
Unit
Times
EGPRS UL data TBF
establishment
Description

TBF and data TBF.
Usage
The counter counts the number of EGPRS UL data TBF link establishments.
Measurement
Point
Unit
The measurement point is that UPPB access type is data TBF.

Times
33
C900040035 Average
number of GPRS UL TBF
Description
There may be more than one TBF in the system during the sampling period. Average number of uplink GPRS TBF establishing
simultaneously = Number of UL GPRS TBFs established simultaneously in the sampling period / Times of sampling
Usage
This counter counts the average number of UL GPRS TBF establishing simultaneously.
Measurement
Point
When UPPB receives the message informing UL GPRS TBF establishment, the number of TBFs is refreshed and the times of sampling accumulates.
Unit
Times
C900040036 Average
number of EGPRS UL TBF
Description
There may be more than one TBF in the system during the sampling period. Average number of uplink EGPRS TBF establishing
simultaneously = Number of UL EGPRS TBFs established simultaneously in the sampling period / Times of sampling
Usage
This counter counts the average number of UL EGPRS TBF establishing simultaneously.
Measurement
Point
When UPPB receives the message informing UL EGPRS TBF establishment, the number of TBFs is refreshed and the times of
sampling accumulates.
Unit
34
Times
release due to N3101
overflow
Description
UL TBF.
Usage
The counter counts the number of abnormal releases of GPRS signaling UL TBF due to N3101 overflow.
Measurement
Point
Unit
The measurement point is N3101 overflow.

Times
overflow
Description

Usage
The counter counts the number of abnormal releases of GPRS signaling UL TBF due to N3103 overflow.
Measurement
Point
Unit

Times
35
forcing release by control
plane
Description

Usage
The counter counts the number of forced releases of GPRS signaling UL TBF due to release request from the control plane.
Measurement
Point
Unit

Times
release due to instance
suspension
Description

Usage
The counter counts the number of abnormal releases of GPRS signaling UL TBF due to suspension of the instance.
Measurement
Point

instance.
Unit
Times
C900040041 Number
of GPRS UL signaling
TBF release due to inner
abnormal
Description
36
Usage
Measurement
Point
Unit
The counter counts the number of abnormal releases of GPRS signaling UL TBF due to internal error.
Times
overflow
Description
UL TBF.
Usage
The counter counts the number of abnormal releases of EGPRS

signaling UL TBF due to N3101 overflow.
Measurement
Point
Unit

Times
overflow
Description

Usage

signaling UL TBF due to N3103 overflow.
Measurement
Point
Unit

Times
37
plane
Description

Usage
The counter counts the number of forced releases of EGPRS signaling UL TBF due to release request from the control plane.
Measurement
Point
Unit

Times
suspension
Description

Usage

signaling UL TBF due to suspension of the instance.
Measurement
Point

instance.
Unit
Times
C900040046 Number
of EGPRS UL signaling
abnormal
Description
38
Usage
Measurement
Point
Unit

signaling UL TBF due to internal error.
Times
EGPRS DL LLC frames
Description
Usage
Measurement
Point
The DL GIPB sends DL UnitData to UPPB through IP packets.

tQoSProfile Tbit in DL UnitData identifies whether data or signaling
is transmitted. UPPB applies to CMP to establish DL TBF (radio
access capacity to carry MS) and according to the CMP request,
establishes EGPRS/GPRS TBF.
The counter counts the number of EGPRS DL LLC frames.
Unit
OF
NUMBER
OF
EGPRS DL LLC FRAMES
Times
discarded EGPRS DL LLC
frames due to buffer overflow
Description
The DL GIPB sends DL UnitData to UPPB through IP packets. If

UPPB fails to acquire buffer, then it will send the LLC Discard message to SGSN.
Usage
The counter counts the number of discarded EGPRS DL LLC frames

due to buffer overflow.
39
Measurement
Point

LLC FRAMES DUE TO BUFFER OVERFLOW
Unit
OF
DISCARDED EGPRS DL
Times
frames due to life time
expiration
Description

UPPB fails to send them before the LLC frame life time expires,
then it will send the LLC Discard message to SGSN.
Usage
The counter counts the number of discarded EGPRS DL LLC frames

due to life time expiration.
Measurement
Point

LLC FRAMES DUE TO LIFE TIME EXPIRATION
Unit
40
Times
OF
DISCARDED EGPRS DL
frames due to other reasons
Description

UPPB fails to send them for reasons other than the above two in
C900040048 and C900040049, then it will send the LLC Discard
message to SGSN.
Usage
The counter counts the number of discarded EGPRS DL LLC

frames due to other reasons than the above two in C900040048
and C900040049.
Measurement
Point

LLC FRAMES DUE TO OTHER REASONS
Unit
OF
DISCARDED EGPRS DL
Times
C900040051 Number of DL
signaling LLC frames
Description

is transmitted. UPPB applies to the control plane to establish
DL TBF (radio access capacity to carry MS) and according to the
request of the control plane, establishes EGPRS/GPRS TBF.
This counter performs statistics for LLC layer, and the statistic data
contains LLC frame header.
Usage
The counter counts the number of DL signaling LLC frames.
41
Measurement
Point

FRAMES
Unit
OF
NUMBER
OF
DL SIGNALING LLC
Times
discarded EGPRS DL
signaling LLC frames due to
buffer overflow
Description

UPPB fails to acquire buffer, then it will send the LLC Discard message to SGSN.
Usage
The counter counts the number of discarded EGPRS DL signaling

LLC frames due to buffer overflow.
Measurement
Point

FIGURE 30 MEASUREMENT POINT OF NUMBER OF DISCARDED EGPRS DL
SIGNALING LLC FRAMES DUE TO BUFFER OVERFLOW
Unit
42
Times
discarded EGPRS DL
life time expiration
Description

UPPB fails to send them before the LLC frame life time expires,
then it will send the LLC Discard message to SGSN.
Usage
The counter counts the number of discarded EGPRS DL signaling

LLC frames due to life time expiration.
Measurement
Point

SIGNALING LLC FRAMES DUE TO LIFE TIME EXPIRATION
Unit
Times
discarded EGPRS DL
other reasons
Description

UPPB fails to send them for reasons other than the above two in
C900040052 and C900040053, then it will send the LLC Discard
message to SGSN.
Usage
The counter counts the number of discarded EGPRS DL signaling LLC frames due to other reasons than the above two in
C900040052 and C900040053.
43
Measurement
Point

SIGNALING LLC FRAMES DUE TO OTHER REASONS
Unit
Times
C900040055 Number of data

blocks transmitted according
to given Abis bandwidth
Description
Because the bandwidth carrying the Abis-interface (TS) timeslot is

limited, PS may need 1 or more Abis TSs for specific RLC coding
modes. If the number of Abis TSs bond to the channel is definite,
the RLC coding mode is also definite for the channel.
Usage
The counter counts the number of data blocks transmitted according to given Abis bandwidth.
Measurement
Point
During the DL PCU frame transmission, if the number of Abis TSs

required by the coding mode equals that of Abis TSs bond to the
channel, the counter increments.
Unit
Times
C900040056 Bytes of
effective upper layer protocol
data sent on DL PDCH
Description
44
UPPB divides the DL LLC frame into RLC blocks and sends them to
MS. After correctly receiving those RLC blocks, MS will recompose
the LLC frame. UPPB acquires the information about MS reception
by setting RRBP to let MS report the Packet Downlink Ack / EGPRS
Packet Downlink Ack message.
Usage
Measurement
Point
The counter counts the bytes of effective upper layer protocol data
sent on DL PDCH.
FIGURE 33 MEASUREMENT POINT OF TOTAL BYTES
LAYER PROTOCOL DATA SENT ON DL PDCH
Unit
Related Features
OF
EFFECTIVE UPPER
Byte
ZGB-06-01-005 BSC Supervision
C900040057 Bytes of
effective upper layer protocol
data received on UL PDCH
Description
After receiving the RLC blocks reported by MS, UPPB composes

them into the LLC frame and sends it to SGSN. At same time, UPPB
sends the Packet Uplink Ack message to MS by a certain rule.
Usage
Measurement
Point
The counter counts the bytes of effective upper layer protocol data
received on UL PDCH.
FIGURE 34 MEASUREMENT POINT OF TOTAL BYTES
LAYER PROTOCOL DATA RECEIVED ON UL PDCH
Unit
OF
EFFECTIVE UPPER
Byte
45
Related Features
ZGB-06-01-005 BSC Supervision
C900040058 Bytes of LLC

frame on GPRS UL data
TBF
Description

Usage
Measurement
Point
The counter counts the bytes carried by GPRS UL data TBF LLC
frame.
DATA TBF
Unit
OF
BYTES
OF
LLC FRAME
ON
GPRS UL
Byte
C900040059 Duration of
GPRS UL data TBF
Description
Usage
Measurement
Point
46
The duration starts when BSS receives the UL access from MS and
ends when BSS receives the data block (CV=0) and all the other
blocks have arrived. For extended UL TBF, the duration of extended uplink status is subtracted.
The counter counts the duration of GPRS UL data TBF.
The duration lasts from UPPBs reception of UL TBF establishment
request to transmission of Packet Uplink Ack with FAI set. The
measurement point is A, as shown in Figure 36. For extended UL
TBF, the measurement point is A and B, as shown in Figure 37.
OF
DURATION
OF
GPRS UL DATA TBF

(EXTENDED UL TBF)
OF
DURATION
OF
GPRS UL DATA TBF
47
Unit
ms

frame on GPRS DL data
TBF
Description
MS. Besides. UPPB sets RRBP by a certain rule. Then MS reports
Packet Downlink Ack/EGPRS Packet Downlink Ack in the specific
UL block.
Usage
Measurement
Point
The counter counts the bytes of LLC frame on GPRS DL data TBF.
DATA TBF
Unit
OF
BYTES
OF
LLC FRAME
ON
GPRS DL
Byte
GPRS DL data TBF
Description
Usage
Measurement
Point
48
The duration lasts from BSSs reception of the DL TBF establishment request to its reception of Packet Downlink Ack/EGPRS
Packet Downlink Ack (Packet Control Ack in non-reply mode) with
FAI=1 sent from MS, and the duration of downlink delay status
is subtracted.
The counter counts the duration of GPRS DL data TBF.
The counter starts counting when UPPB receives DL TBF establishment request until BSS finishes sending all current data and MS
returns acknowledgement response for all. During the delay, after the new DL data from SGSN is received, data transmission is
initiated again, and the counter restarts counting until the Packet
Downlink Ack/EGPRS Packet Downlink Ack (Packet Control Ack in
non-reply mode) with FAI=1 is received from MS. The measurement point is A and B, as shown in Figure 39.
Unit
OF
DURATION
OF
GPRS DL DATA TBF
ms
C900040062 Number
of effective data blocks
received on GPRS UL TBF
Description
During the TBF transmission, MS divides the UL LLC frame into RLC
blocks and sends them to BSS. Only when BSS receives all these
RLC blocks can it recompose the LLC frame.
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage
The counter counts the number of effective data blocks received

on GPRS UL TBF.
49
Measurement
Point

RECEIVED ON GPRS UL TBF
Unit
Related Features
OF
NUMBER
OF
EFFECTIVE DATA BLOCKS
Times
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode
NACK blocks received on
GPRS UL TBF
Description
blocks and sends them to BSS. Only when BSS correctly receives
all these RLC blocks can it recompose the LLC frame. BBS informs
MS of the RLC block reception through Packet Uplink Ack. For the
reply mode, if any RLC block is lost, MS should transmit again.
Usage
The counter counts the number of NACK blocks received on GPRS

UL TBF
Measurement
Point
Then counter increments when BSS correctly receives a NACK

block. The measurement point is A, as shown in Figure 41.
FIGURE 41 MEASUREMENT
ON GPRS UL TBF
Unit
Related Features
50
POINT
OF
NUMBER
OF
NACK BLOCKS RECEIVED
Times
effective data blocks sent on
GPRS DL TBF
Description
During the TBF transmission, BSS divides the UL LLC frame into
RLC blocks and sends them to MS. Only when MS correctly receives all these RLC blocks can it recompose the LLC frame. MS
informs BSS of the RLC block reception through Packet DownLink
Ack/EGPRS Packet Downlink Ack.
Usage
The counter counts the number of effective data blocks sent on

GPRS DL TBF
Measurement
Point
Then counter increments when Packet DownLink Ack/EGPRS

Packet Downlink Ack indicates that MS have correctly received the
RLC block. The measurement point is A1, as shown in Figure 42.
SENT ON GPRS DL TBF
Unit
Related Features
OF
NUMBER
OF
Times
NACK blocks sent on GPRS
DL TBF
Description
RLC blocks and sends them to MS. Only when MS correctly re-
51
ceives all these RLC blocks can it recompose the LLC frame. MS
Usage
The counter counts the number of NACK blocks sent on GPRS DL

TBF.
Measurement
Point
Then counter increments when Packet DownLink Ack/EGPRS

Packet Downlink Ack indicates that MS fails to receive the RLC
block. The measurement point is A2, as shown in Figure 43.
GPRS DL TBF
Unit
Related Features
OF
NUMBER
OF
NACK BLOCKS SENT
ON
Times

frame on EGPRS UL data
TBF
Description

Usage
52
The counter counts the bytes of LLC frame on EGPRS UL data TBF.
Measurement
Point

UL DATA TBF
Unit
OF
BYTES
OF
LLC FRAME
ON
EGPRS
Byte
EGPRS UL data TBF
Description
Usage
Measurement
Point
The duration starts when BSS receives the UL access from MS and
ends when BSS receives the data block (CV=0) and all the other
blocks have arrived. For extended UL TBF, the duration of extended uplink status is subtracted.
The counter counts the duration of EGPRS UL data TBF.
The duration lasts from UPPBs reception of UL TBF establishment
request to transmission of Packet Uplink Ack with FAI=1. The measurement point is A, as shown in Figure 45. For extended UL TBF,
the measurement point is A and B, as shown in Figure 46.
OF
DURATION
OF
EGPRS UL DATA TBF
53

(EXTENDED UL TBF)
Unit
OF
DURATION
OF
EGPRS UL DATA TBF
ms

frame on EGPRS DL data
TBF
Description
MS. Besides. UPPB sets RRBP by a certain rule. Then MS reports
Packet Downlink Ack/EGPRS Packet Downlink Ack in the specific
UL block.
Usage
54
The counter counts the bytes of LLC frame on EGPRS DL data TBF.
Measurement
Point

DL DATA TBF
Unit
OF
BYTES
OF
LLC FRAME
ON
EGPRS
Byte
EGPRS DL data TBF
Description
Usage
Measurement
Point
The duration lasts from BSSs reception of the DL TBF establishment request to its reception of Packet Downlink Ack/EGPRS
Packet Downlink Ack (Packet Control Ack in non-reply mode) with
FAI=1 sent from MS, and the duration of downlink delay status
is subtracted.
The counter counts the duration of EGPRS DL data TBF.
The counter starts counting when UPPB receives DL TBF establishment request until BSS finishes sending all current data and MS
returns acknowledgement response for all. During the delay, after the new DL data from SGSN is received, data transmission is
initiated again, and the counter restarts counting until the Packet
Downlink Ack/EGPRS Packet Downlink Ack (Packet Control Ack in
non-reply mode) with FAI=1 is received from MS. The measurement point is A and B, as shown in Figure 48.
55
Unit
OF
DURATION
OF
EGPRS DL DATA TBF
ms
C900040070 Number
of effective data blocks
received on EGPRS UL TBF
Description
blocks and sends them to BSS. Only when BSS receives all these
RLC blocks can it recompose the LLC frame.
Usage
56
The counter counts the number of effective data blocks received

on EGPRS UL TBF.
Measurement
Point

RECEIVED ON EGPRS UL TBF
Unit
Related Features
OF
NUMBER
OF
Times
NACK blocks received on
EGPRS UL TBF
Description
blocks and sends them to BSS. Only when BSS correctly receives
all these RLC blocks can it recompose the LLC frame. BBS informs
MS of the RLC block reception through Packet Uplink Ack. For the
reply mode, if any RLC block is lost, MS should transmit again.
Usage
The counter counts the number of NACK blocks received on EGPRS

UL TBF.
Measurement
Point
Then counter increments when BSS correctly receives a NACK

block. The measurement point is A, as shown in Figure 50.
ON EGPRS UL TBF
Unit
Related Features
POINT
OF
NUMBER
OF
NACK BLOCKS RECEIVED
Times
57
effective data blocks sent on
EGPRS DL TBF
Description
RLC blocks and sends them to MS. Only when MS correctly receives all these RLC blocks can it recompose the LLC frame. MS
Usage
The counter counts the number of effective data blocks sent on

EGPRS DL TBF.
Measurement
Point
The counter increments when Packet DownLink Ack/EGPRS Packet

Downlink Ack indicates that MS have correctly received the RLC
block. The measurement point is A1, as shown in Figure 51.
SENT ON EGPRS DL TBF
Unit
Related Features
OF
NUMBER
OF
Times
NACK blocks sent on
EGPRS DL TBF
Description
58
RLC blocks and sends them to MS. Only when MS correctly re-
ceives all these RLC blocks can it recompose the LLC frame. MS
Usage
The counter counts the number of NACK blocks sent on EGPRS DL

TBF.
Measurement
Point
The counter increments when Packet DownLink Ack/EGPRS Packet

Downlink Ack indicates that MS fails to receive the RLC block. The
measurement point is A2, as shown in Figure 52.
EGPRS DL TBF
Unit
Related Features
OF
NUMBER
OF
NACK BLOCKS SENT
ON
Times
GPRS DL LLC frames
Description
This counter counts the times that the UPPB board receives LLC
frames. When the BSSGP module of the UPPB board saves LLC
frames, it judges that the frames are data or signalling according
to the TBit in QoSProfile of DLUnitData. If they are data LLC frames
and the TBF type is GPRS, the counter increases by 1.
Usage
This counter counts the times that downlink LLC frames are sent
in GPRS services.
Measurement
Point
The counter is updated when the BSSGP module saves LLC frames.
59
Unit
OF
DOWNLINK GPRS LLC FRAMES
Times
discarded GPRS DL LLC
frames due to buffer overflow
Description
This counter counts the times that the UPPB board receives LLC
frames but discards them due to buffer overflow. When the BSSGP
module of the UPPB board saves LLC frames, it applies for dynamic
memory. If the application fails or the LLC frames saved in the
BSSGP module exceed the limit set in the network management
system and the TBF type is GPRS, the counter increases by 1.
Usage
This counter counts the failures to apply for dynamic memory for
downlink LLC frames in GPRS services.
Measurement
Point
FIGURE 54 MEASUREMENT POINT OF DISCARDED DOWNLINK GPRS LLC
FRAMES DUE TO BUFFER OVERFLOW
Unit
60
Times
frames due to life time
expiration
Description
The DL GIPB sends DL UnitData to the UPPB board through IP

packets. If the UPPB board fails to send DL UnitData before the
LLC frame life time expires, it will send the LLC Discard message
to the SGSN.
Usage
The counter counts the times that the LLC Discard message is sent
due to life time expiration in downlink GPRS services.
Measurement
Point

FIGURE 55 MEASUREMENT POINT OF DISCARDED DOWNLINK GPRS LLC
FRAMES DUE TO LIFE TIME EXPIRATION
Unit
Times
frames due to other reasons
Description
This counter counts the times that the UPPB board receives
LLC frames but discards them due to reasons other than buffer
overflow. When the BSSGP module of the UPPB board saves LLC
frames, the counter increases by 1 if the module discards an LLC
frame because it fails to insert the frame into queue or transfer
the frame and if the TBF type is GPRS.
Usage
This counter counts the discards of downlink LLC frames in GPRS

services due to reasons other than buffer overflow.
Measurement
Point
61

FRAMES DUE TO OTHER REASONS
Unit
OF
DISCARDED DOWNLINK GPRS LLC
Times
dummy control blocks on
PACCH
Description
If there is no other RLC/MAC block available in the network, BSS

will transmit the DUMMY blocks to MS for UL transmission.
Usage
The counter counts the number of DL dummy control blocks sent

by BSC on PACCH in the packet transmission mode.
Measurement
Point
If the DL control block sent from BTS to MS is a DL Dummy control

block, the counter increments. The measurement point is A, as
shown in Figure 57.
BLOCKS ON PACCH
Unit
62
OF
NUMBER
Times
OF
DL DUMMY CONTROL
C900040079 Number of UL
dummy control blocks on
PACCH
Description
Similar to C900040078, this counter counts the number of UL

dummy control blocks sent by BSC on PACCH in the packet transmission mode.
Measurement
Point
If the DL control block sent from BTS to MS is an UL Dummy control

block, the counter increments. The measurement point is A, as
shown in Figure 58.
BLOCKS ON PACCH
Unit
OF
NUMBER
OF
UL DUMMY CONTROL
Times
DL RLC blocks on PACCH
(excluding dummy block)
Description
This counter counts the number of DL RLC blocks except for

DUMMY blocks sent from BSC to MS through BTS on PACCH.
Usage
The counter counts the number of DL RLC blocks expect DUMMY

blocks sent by BSC on PACCH.
Measurement
Point
When BSC sends a DL control block (except DUMMY block) to MS

through BTS, the counter increments. The measurement point is
A, as shown in Figure 59.
63

PACCH (EXCLUDING DUMMY BLOCK)
Unit
Related Features
OF
DL RLC BLOCKS
ON
Times
ZGB-03-05-001 Coding Scheme #1~#4
RLC pending blocks in CS1
on PDTCH
Description
After BSC receives DownLink Ack message, it decides whether to

send pending RLC block, to resend RLC block or to send new data
blocks. This counter counts the number of DL pending RLC blocks
from BSC to MS, with coding method of CS1.
Usage
This counter counts the number of DL pending RLC blocks sent on

PDTCH, with coding method of CS1.
Measurement
Point
When BSC sends a pending RLC block whose coding method is CS1
to MS, the counter increments. The measurement point is A, as
shown in Figure 60.
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
DL RLC PENDING BLOCKS
Times
64
on PDTCH
Description

Usage

Measurement
Point
to MS via BTS, the counter increments. The measurement point is
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
Times
on PDTCH
Description

Usage

65
Measurement
Point
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
Times
on PDTCH
Description

Usage

Measurement
Point
ON PDTCH
Unit
Related Features
66
POINT
OF
NUMBER
OF
Times
RLC NACK blocks in CS1 on
PDTCH
Description

blocks. This counter counts the number of DL retransmitted RLC
blocks from BSC to MS, with coding method of CS1.
Usage
This counter counts the number of DL retransmitted RLC blocks

sent on PDTCH, with coding method of CS1.
Measurement
Point
When BSC sends retransmitted RLC block whose coding method

is CS1 to MS via BTS, the counter increments. The measurement
point is A, as shown in Figure 64.
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
PDTCH
Description

67
Usage

Measurement
Point

ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
PDTCH
Description

68
Usage

Measurement
Point

ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
PDTCH
Description

Usage

Measurement
Point

ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
69
RLC new blocks in CS1 on
PDTCH
Description

blocks. This counter counts the number of DL first-transmitted
RLC blocks from BSC to MS, with coding method of CS1.
Usage
The counter is used to review the status of DL first-transmitted

RLC blocks sent by BSC on PDTCH, with coding method of CS1.
Measurement
Point
When BSC sends first-transmitted RLC block (with coding method

of CS1) to MS via BTS, the counter increments. The measurement
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
PDTCH
Description

Usage
70

Measurement
Point

ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
PDTCH
Description

Usage

Measurement
Point

ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
71
PDTCH
Description

Usage

Measurement
Point

ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
UL RLC blocks excluding
dummy blocks on PACCH
Description
This counter counts the number of UL RLC blocks except for

DUMMY blocks sent from MS to BSC through BTS on PACCH.
72
Usage
The counter counts the number of uplink RLC blocks expect DUMMY
blocks received by BSC on PACCH.
Measurement
Point
When BSC receives an UL control block (except the DUMMY block)

from MS, the counter increments. The measurement point is A, as
shown in Figure 72.
EXCLUDING DUMMY BLOCKS ON PACCH
Unit
Related Features
OF
UL RLC BLOCKS
Times
on PDTCH
Description
After receiving UL data block, BSC decides whether it is retransmitted RLC block, first-transmitted RLC block or pending RLC block.
This counter counts the number of useful UL CS1-coded pending
RLC blocks received on PDTCH.
Usage

RLC blocks received by BSC on PDTCH.
Measurement
Point
When BSC receives CS1-coded UL pending RLC block, the counter

increments. The measurement point is A, as shown in Figure 73.
ON PDTCH
Unit
POINT
OF
NUMBER
OF
UL RLC PENDING BLOCKS
Times
73
Related Features

on PDTCH
Description
Usage

Measurement
Point

ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
Times
on PDTCH
Description
74
Usage

Measurement
Point

ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
Times
on PDTCH
Description
Usage

Measurement
Point

ON PDTCH
POINT
OF
NUMBER
OF
75
Unit
Related Features
Times
PDTCH
Description
This counter counts the number of useful UL CS1-coded retransmitted RLC blocks received on PDTCH.
Usage
This counter counts the number of useful UL CS1-coded retransmitted RLC blocks received by BSC on PDTCH.
Measurement
Point
When BSC receives CS1-coded UL retransmitted RLC block, the

counter increments. The measurement point is A, as shown in
Figure 77.
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
PDTCH
Description
76
Usage
Measurement
Point

Figure 78.
ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
PDTCH
Description
Usage
Measurement
Point

Figure 79.
77
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
PDTCH
Description
Usage
Measurement
Point

Figure 80.
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
78
PDTCH
Description
This counter counts the number of useful UL CS1-coded first-transmitted RLC blocks received on PDTCH.
Usage
This counter counts the number of useful UL CS1-coded first-transmitted RLC blocks received by BSC on PDTCH.
Measurement
Point
When BSC receives CS1-coded UL first-transmitted RLC block, the

Figure 81.
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
PDTCH
Description
Usage
79
Measurement
Point

Figure 82.
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
PDTCH
Description
Usage
Measurement
Point

Figure 83.
ON PDTCH
Unit
Related Features
80
POINT
OF
NUMBER
Times
OF
UL RLC NEW BLOCKS
PDTCH
Description
Usage
Measurement
Point

Figure 84.
ON PDTCH
Unit
Related Features
POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
UL data blocks received on
PDTCH
Description
When MS transmits UL RLC blocks to BSC through BTS, this counter

counts the number of data blocks received by BSC, including the
retransmitted RLC blocks, blocks to be confirmed and the firsttransmitted blocks.
81
Usage
The counter counts the number of data blocks received by UL

PDTCH.
Measurement
Point
When MS transmits an UL RLC block to BSC through BTS (including

the retransmitted RLC blocks, blocks to be confirmed and the firsttransmitted blocks), this counter increments.
Unit
Related Features
Times
data blocks sent on PDTCH
Description
When BSC transmits DL RLC blocks to BTS, this counter counts

the number of data blocks sent from BSC, including the retransmitted RLC blocks, blocks to be confirmed and the first-transmitted
blocks.
Usage
The counter counts the number of data blocks sent by DL PDTCH.
Measurement
Point
When BSC transmits a DL RLC block to BTS (including the retransmitted RLC blocks, blocks to be confirmed and the first-transmitted
blocks), this counter increments.
Unit
Related Features
Times
C900040108 Number
of GPRS DL TBF
establishment requests
Description
The counter counts the number of GPRS DL TBF establishment

requests received by PS control plane when BSC attempts to establish DL GPRS TBFs. It is the sum of CCCH/PCCCH requests
(C901170002) and PACCH requests (C901170003).
Usage
The counter collects information about the frequency of DL establishment requests received by PS control plane when BSC attempts
to establish DL GPRS TBFs.
Measurement
Point
82
This counter increments in the following two cases:
When PS control plane receives a DL TBF establishment request

from PS user plane, this counter increments.
Unit
When UL GPRS TBF exists and DL GPRS TBF is to be established, if PS control plane receives the DL assignment message
Times
C900040109 Number
of GPRS DL TBF
establishment failure due to
database allocation failure
Description
The counter counts the number of GPRS DL TBF establishment

failure due to database allocation failure. It involves the number
of allocation failures caused by PDCH, Abis, and PCU having no
available resource or in abnormal status.
Usage
The counter collects information about the frequency of channel

allocation failures when BSC attempts to establish GPRS DL TBFs.
Measurement
Point
When PS control plane receives the DL TBF establishment request from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 85.
FIGURE 85 MEASUREMENT POINT OF ALLOCATION FAILURES
RECEIVING DL TBF ESTABLISHMENT REQUEST
AFTER
When MS has already established an UL GPRS TBF and DL GPRS

TBF is to be established, if PS control plane receives the DL
TBF assignment message from PS user plane, it will apply to
database for resources. If it fails to obtain the resources, this
Figure 86.
83

RECEIVING DL TBF ASSIGNMENT MESSAGE
Unit
AFTER
Times
GPRS DL TBF resource
reallocation requests due to
UL TBF establishment
Description
The counter counts the number of GPRS DL TBF resource reallocation requests due to UL TBF establishment.
Usage
The counter collects information about the frequency of GPRS DL

TBF resource reallocation requests.
Measurement
Point
When MS has already established a DL GPRS TBF, if PS control

plane receives an UL TBF assignment message from PS user plane,
this counter increments. The measurement point is A, as shown
in Figure 87.
FIGURE 87 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE
REALLOCATION REQUESTS DUE TO UL TBF ESTABLISHMENT
Unit
84
Times
reallocation failure of
channel allocation due
to UL TBF establishment
Description
If MS has already established a DL GPRS TBF and it needs to establish an UL TBF on PACCH, PS control plane should apply to database for resources. The counter counts the number of DL resource
reallocation failures of channel allocation caused by failed UL TBF
establishment allocation.
Usage
The counter collects information about the frequency of GPRS DL

resource reallocation failures of channel allocation caused by failed
UL TBF establishment allocation.
Measurement
Point

it will apply to database for resources. If it fails to obtain the
resources, this counter increments. The measurement point is A,
as shown in Figure 88.
REALLOCATION FAILURE OF CHANNEL ALLOCATION DUE TO UL TBF
ESTABLISHMENT
Unit
Times
85
LLC transmission
Description
This counter counts the number of resource reallocation requests

that PS control plane receives from PS user plane caused by UL/DL
LLC frame changes during the DL GPRS TBF transmission.
Usage
This counter collects information about the frequency of resource

reallocation requests received by PS control plane during the DL
GPRS TBF transmission.
Measurement
Point
When PS control plane receives a resource reallocation request

from PS user plane, if the current DL GPRS TBF exists, this counter
REALLOCATION REQUESTS DUE TO LLC TRANSMISSION
Unit
Times
to LLC transmission
Description
86
During the DL GPRS TBF transmission, because UL/DL LLC frame

changes, PS user plane sends a resource reallocation request to
PS control plane. After receiving the request, PS control plane
applies to database for resources. This counter counts the number
of failed resource allocations.
Usage
This counter collects information about the frequency of failed resource allocations during the DL GPRS TBF transmission after PS
control plane receives the resource reallocation request and applies to database for resources.
Measurement
Point
After PS control plane receives a resource reallocation request

from PS user plane and applies to database for resources, if it
fails to obtain the resources, this counter increments, as A shown
in Figure 90.
FIGURE 90 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF
RESOURCE REALLOCATION FAILURE OF CHANNEL ALLOCATION DUE TO LLC
TRANSMISSION
Unit
Times
C900040114 Number
of EGPRS DL TBF
Description
The counter counts the number of EGPRS downlink TBF establishment requests received by control plane. It is the sum of CCCH/PCCCH requests (C901180002) and PACCH requests (C901180003).
Usage
The counter collects information about the frequency of DL establishment requests received by the control plane when BSC attempts to establish DL EGPRS TBFs.
Measurement
Point
Unit
When PS control plane receives a DL TBF establishment request

When UL EGPRS TBF exists and DL EGPRS TBF is to be established, if PS control plane receives the DL assignment message
Times
87
C900040115 Number
of EGPRS DL TBF
Description
The counter counts the number of channel allocation failures when

BSC attempts to establish EGPRS DL TBFs and RANPS applies to
database for resources. It involves the number of allocation failures caused by PDCH, Abis, and PCU having no available resource
or in abnormal status.
Usage

allocation failures when BSC attempts to establish EGPRS DL TBFs
and RANPS applies to database for resources.
Measurement
Point
When PS control plane receives the DL TBF establishment request from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 91.
RECEIVING DL TBF ESTABLISHMENT REQUEST
When UL EGPRS TBF exists and DL EGPRS TBF is to be established, if PS control plane receives the DL TBF assignment
message from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 92.
88
AFTER
AFTER
Unit
Times
EGPRS DL TBF resource
Description
The counter counts the number of EGPRS downlink TBF resource

reallocation requests (concurrent PACCH UL TBF establishment request).
Usage
The counter collects information about the frequency of EGPRS

downlink TBF resource reallocation requests.
Measurement
Point
When MS has already established a DL EGPRS TBF, if PS control

in Figure 93.
REALLOCATION REQUESTS DUE TO UL TBF ESTABLISHMENT
Unit
Times
89
to UL TBF establishment
Description
If MS has already established a DL EGPRS TBF and it needs to

establish an UL TBF on PACCH, PS control plane should apply to
database for resources. The counter counts the number of DL
Usage
The counter collects information about the frequency of EGPRS DL

Measurement
Point

REALLOCATION FAILURE OF CHANNEL ALLOCATION DUE TO UL TBF
ESTABLISHMENT
Unit
90
Times
LLC transmission
Description

LLC frame changes during the DL EGPRS TBF transmission.
Usage

reallocation requests received by PS control plane during the DL
EGPRS TBF transmission.
Measurement
Point

from PS user plane, if the current DL EGPRS TBF exists, this
counter increments, as A shown in Figure 95.
REALLOCATION REQUESTS DUE TO LLC TRANSMISSION
Unit
Times
to LLC transmission
Description
During the DL EGPRS TBF transmission, because UL/DL LLC frame

91
Usage
This counter collects information about the frequency of failed resource allocations during the DL EGPRS TBF transmission after PS
Measurement
Point

in Figure 96.
RESOURCE REALLOCATION FAILURE OF CHANNEL ALLOCATION DUE TO LLC
TRANSMISSION
Unit
Times
C900040120 Number
of GPRS UL TBF
Description
The counter counts the number of all channel requests when MS

attempts to establish GPRS UL TBFs. It is the sum of CCCH requests (C901190002), PCCCH requests (C901190004) and PACCH
requests (C901190006).
Usage

requests when MS attempts to establish GPRS services.
Measurement
Point
Unit
92
This counter increments in the following three cases:
When BSC receives a CCCH request originated by MS, this

counter increments.
When BSC receives a PCCCH request originated by MS, this

counter increments.
When BSC receives a PACCH request originated by MS and user

plane sends a resource request to control plane, this counter
increments.
Times
C900040121 Number
of GPRS UL TBF
Description
The counter counts the number of GPRS UL TBF establishment

channel allocation failures. It involves the number of allocation
failures caused by PDCH, Abis, and PCU having no available resource or in abnormal status.
Usage

allocation failures when the system attempts to establish GPRS UL
TBFs.
Measurement
Point
When PS control plane receives a CCCH request from MS, it

will apply to database for resources. If it fails to obtain the
resources, this counter increments. The measurement point is
RECEIVING CCCH REQUEST
ALLOCATION FAILURES
AFTER
When PS control plane receives a PCCCH request from MS, it

will apply to database for resources. If it fails to obtain the
RECEIVING PCCCH REQUEST
OF
OF
ALLOCATION FAILURES
AFTER

plane receives an UL TBF assignment message from PS user
plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement
93

TBF EXISTS)
Unit
OF
ALLOCATION FAILURES (DL GPRS
Times
GPRS UL TBF resource
DL TBF establishment
Description
The counter counts the number of RS UL TBF resource reallocation

requests due to DL TBF establishment.
Usage
The counter collects information about the frequency of GPRS UL

Measurement
Point
When MS has already established an UL GPRS TBF, if PS control

plane receives a DL TBF assignment message from PS user plane,
in Figure 100.
FIGURE 100 MEASUREMENT POINT OF NUMBER OF GPRS UL TBF RESOURCE
REALLOCATION REQUESTS DUE TO DL TBF ESTABLISHMENT
Unit
94
Times
to DL TBF establishment
Description
If MS has already established an UL GPRS TBF and it needs to

establish a DL TBF on PACCH, PS control plane should apply to
database for resources. The counter counts the number of UL resource reallocation failures of channel allocation caused by failed
DL TBF establishment allocation.
Usage
The counter collects information about the frequency of GPRS UL

Measurement
Point
When MS has already established an UL GPRS TBF, if PS control

Unit
AFTER
Times
95
LLC transmission
Description

LLC frame changes during the UL GPRS TBF transmission.
Usage

reallocation requests received by PS control plane during the UL
GPRS TBF transmission.
Measurement
Point

from PS user plane, if the current UL GPRS TBF exists, this counter
RESOURCE REALLOCATION REQUESTS DUE TO LLC TRANSMISSION
Unit
Times
to LLC transmission
Description
96
During the UL GPRS TBF transmission, because UL/DL LLC frame

Usage
This counter collects information about the frequency of failed resource allocations during the UL GPRS TBF transmission after PS
Measurement
Point

in Figure 103.
RESOURCE REALLOCATION FAILURE OF CHANNEL
TRANSMISSION
Unit
OF GPRS DL TBF
ALLOCATION DUE TO
LLC
Times
reallocation requests for
resource request
Description
This counter counts the number of resource allocation requests

that PS control plane receives from MS during the UL GPRS TBF
transmission.
Usage

allocation requests received by PS control plane during the UL
GPRS TBF transmission (including 2-step UL access and UL TBF
transmission).
Measurement
Point
When PS control plane receives a resource allocation request from

PS user plane, this counter increments, as A shown in Figure 104.
97

REALLOCATION REQUESTS FOR RESOURCE REQUEST
Unit
Times
reallocation failure due to
for resource request
Description
During the UL GPRS TBF transmission, after receiving the resource

allocation request from MS, PS control plane applies to database
for resources. This counter counts the number of failed resource
allocations.
Usage
This counter collects information about the frequency of failed resource allocations during the UL GPRS TBF transmission (including
2-step UL access and UL TBF transmission) after PS control plane
receives the resource allocation request from MS and applies to
database for resources.
Measurement
Point

from MS and applies to database for resources, if it fails to obtain the resources, this counter increments, as A shown in Figure
105.
FIGURE 105 FAILING
Unit
98
TO
REQUEST
FOR
Times
RESOURCE
FROM
DATABASE
C900040128 Number
of EGPRS UL TBF
Description
The counter counts the number of all channel requests when MS

attempts to establish EDGE UL TBFs. It is the sum of CCCH requests (C901200003), PCCCH requests (C901200005) and PACCH
requests (C901200006).
Usage

requests when MS attempts to establish EDGE services.
Measurement
Point
Unit
When BSC receives an EDGE CCCH request originated by MS,

this counter increments.
When BSC receives an EDGE PCCCH request originated by MS,

When BSC receives an EDGE PACCH request originated by MS

and user plane sends a resource request to control plane, this
counter increments.
Times
C900040129 Number
of EGPRS UL TBF
Description
The counter counts the number of EGPRS UL TBF establishment

channel allocation failures. It involves the number of allocation
failures caused by PDCH, Abis, and PCU having no available resource or in abnormal status.
Usage

allocation failures when the system attempts to establish EGPRS
UL TBFs.
Measurement
Point
When PS control plane receives an EGPRS channel request on

CCCH or an EGPRS Packet channel request on PCCCH from MS,
99
FIGURE 106 MEASUREMENT POINT OF NUMBER OF EGPRS UPLINK TBF

ESTABLISHMENT CHANNEL ALLOCATION FAILURES

plane receives an UL TBF assignment message from PS user
plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement
GPRS TBF EXISTS)
Unit
OF
ALLOCATION FAILURES (DL
Times
EGPRS UL TBF resource
100
Description
The counter counts the number of EGPRS UL TBF resource reallocation requests due to DL TBF establishment.
Usage
The counter collects information about the frequency of EGPRS UL

Measurement
Point
When MS has already established an UL EGPRS TBF, if PS control

in Figure 108.

REALLOCATION REQUESTS DUE TO DL TBF ESTABLISHMENT
Unit
Times
to DL TBF establishment
Description
If MS has already established an UL EGPRS TBF and it needs to

establish a DL TBF on PACCH, PS control plane should apply to
database for resources. The counter counts the number of UL resource reallocation failures of channel allocation caused by failed
Usage
The counter collects information about the frequency of EGPRS UL

Measurement
Point
When MS has already established an UL EGPRS TBF, if PS control

Unit
AFTER
Times
101
LLC transmission
Description

LLC frame changes during the UL EGPRS TBF transmission.
Usage

reallocation requests received by PS control plane during the UL
EGPRS TBF transmission.
Measurement
Point

from PS user plane, this counter increments, as A shown in Figure
110.
RESOURCE REALLOCATION REQUESTS DUE TO LLC TRANSMISSION
Unit
Times
to LLC transmission
Description
102
During the UL EGPRS TBF transmission, because UL/DL LLC frame

Usage
This counter collects information about the frequency of failed resource allocations during the UL EGPRS TBF transmission after PS
Measurement
Point

in Figure 111.
RESOURCE REALLOCATION FAILURE OF CHANNEL
TRANSMISSION
Unit
OF GPRS DL TBF
ALLOCATION DUE TO
LLC
Times
resource request
Description
This counter counts the number of resource allocation requests

that PS control plane receives from MS during the UL EGPRS TBF
transmission.
Usage

allocation requests received by PS control plane during the UL
EGPRS TBF transmission (including 2-step UL access and UL TBF
transmission).
Measurement
Point
When PS control plane receives a resource allocation request from

PS user plane, this counter increments, as A shown in Figure 112.
103

REALLOCATION REQUESTS FOR RESOURCE REQUEST
Unit
Times
for resource request
Description
During the UL EGPRS TBF transmission, after receiving the resource allocation request from MS, PS control plane applies to
database for resources. This counter counts the number of failed
resource allocations.
Usage
This counter collects information about the frequency of failed resource allocations during the UL EGPRS TBF transmission (including 2-step UL access and UL TBF transmission) after PS control
plane receives the resource allocation request from MS and applies to database for resources.
Measurement
Point

from MS and applies to database for resources, if it fails to obtain the resources, this counter increments, as A shown in Figure
113.
FIGURE 113 FAILING
Unit
104
TO
REQUEST
FOR
RESOURCE
Times
FROM
DATABASE
C900040136 Average
number of available PDCH
Description
This counter counts the number of available PDCH in a cell. The

PDCH that can be assigned include dynamic and static PDCH both
idle and occupied.
Usage
This counter is used to find out the number of available PDCH in

the serving cell.
Measurement
Point
The counter's value can be obtained by querying the database

when periodic measurement data is reported.
Unit
Related Features
Times
ZGO-03-02-003 Full dynamic channel allocation on Um interface
C900040137 Number
of forcing conversation
dynamic from PDCH to TCH
by BSC
Description
iBSC supports dynamic radio channel function. The counter

records number of times of reclaiming dynamic PDCH in idle state
so as to use them as TCH/F.
Usage
This counter is used to find out the busy level and density of PS
service in the serving cell and use it as reference to decide whether
to set static PDCH or not.
Measurement
Point
The counter increments when dynamic PDCH is idle and the database starts reclaiming dynamic PDCH.
Unit
Related Features
Times
ZGO-03-02-002 Enhancement on Channel Allocation
PDCH used by TBF in each
cell
Description
This counter counts the sum of PDCH used by all TBF in the serving
cell.
105
Usage
This counter is used to find out the condition of multi-timeslot allocation in the serving cell.
Measurement
Point
The counter's value can be obtained by querying the database

when periodic measurement data is reported.
Unit
Times
C900040139 Maximum
number of used PDCH
Description
This counter records the maximum number of used PDCH in a cell

within the measurement period. It reflects the occupancy and busy
level of PDCH.
Usage
This counter is used to find out the busy level of the cell TCH/F
channel. It could be used as a reference for whether to increase
PDCH channel configuration.
Measurement
Point
Unit
Request for database
Release database
Report periodic measurement data
Times
C900040140 Average
number of used PDCH
Description
This counter records the average number of used PDCH in a cell

within the measurement period.
Usage
This counter is used to find out the busy level of the cell TCH/F
channel. It could be used as a reference for whether to increase
PDCH channel configuration.
Measurement
Point
Unit
106
Request for database
Release database
Report periodic measurement data
Times
C900040141 Number
of GPRS DL TBF
before T3192 expiration
Description
During the running of T3193 of DL GPRS TBF, BSC receives DL LLC

frame again, then it performs DL assignment on PACCH of the DL
TBF.
Usage
This counter counts the number of times of establishing new DL

TBF.
Measurement
Point
After the DL GPRS TBF transmits all LLC frames and the DL RLC
block with FBI = 1, T3193 is started. During T3193 running,
when BSC receives new LLC frame and sends DL assignment, this
counter increments.
ESTABLISHMENT REQUESTS BEFORE T3192 EXPIRATION
Unit
Times
107
C900040142 Number
of GPRS DL TBF
establishment using existing
DL TBF resource
Description
When establishing EGPRS DL TBF under UL transmission status,

the user plane needs not to request control plane for DL resource
if having saved DL TBF resource of last time. It uses the existing
resource for DL assignment. This counter records the number of
GPRS DL TBF establishment using existing DL TBF resource.
Measurement
Point
During the UL GPRS TBF transmission, when BSC receives the DL

LLC frame, it uses the existing resource to establish DL GPRS TBF.
FIGURE 115 MEASUREMENT POINT OF GPRS DL TBF ESTABLISHMENT
USING EXISTING DL TBF RESOURCE
Unit
Times
C900040143 Number
of GPRS DL TBF
on PACCH
Description
108
Under UL transmission status, it is necessary to establish DL TBF

transmission when user plane receives DL LLC Frame from SGSN.
If user plane has not saved DL TBF resource, then user plane requests control plane for resource.
This counter counts the number of times of requesting control

plane for resource to establish GPRS DL TBF on PACCH.
Note:
Here, user plane refers to the UPPB of iBSC, and control plane
refers to the CMP of iBSC.
Measurement
Point

ESTABLISHMENT REQUESTS ON PACCH
Unit
OF
GPRS DL TBF
Times
C900040144 Number
of GPRS DL TBF
on CCCH/PCCCH
Description
When MS is in packet idle status, after BSC receives DL LLC frame

from SGSN, BSC initiates the process of establishing DL TBF which
is assigned on CCCH or PCCCH. BSC user plane first sends the
request for DL establishment to BSC control plane.
Measurement
Point
Under MSs packet idle status, when BSC sends the request for
DL resource to BSC control plane after receiving LLC frame from
SGSN, the counter increments.
The measurement point is as A1, as shown in Figure 117.
109

ESTABLISHMENT REQUESTS ON CCCH/PCCCH
Unit
OF
GPRS DL TBF
Times
C900040145 Number
of EGPRS DL TBF
before T3192 expiration
Description
During the running of T3193 of DL EGPRS TBF, BSC receives DL

LLC frame again, then it performs DL assignment on PACCH of the
DL TBF.
This counter counts the number of times of establishing new DL
TBF.
Measurement
Point
After the DL EGPRS TBF transmits all LLC frames and the DL RLC
block with FBI = 1, T3193 is started. During T3193 running,
when BSC receives new LLC frame and sends DL assignment, this
counter increments.
110
FIGURE 118 MEASUREMENT POINT OF NUMBER OF EGPRS DL TBF

ESTABLISHMENT REQUESTS BEFORE T3192 EXPIRATION
Unit
Times
C900040146 Number
of EGPRS DL TBF
establishment using existing
DL TBF resource
Description
When establishing EGPRS DL TBF under UL transmission status,

the user plane needs not to request control plane for DL resource
if having saved DL TBF resource of last time. It uses the existing
resource for DL assignment. This counter records the number of
EGPRS DL TBF establishment using existing DL TBF resource.
Measurement
Point
During the UL EGPRS TBF transmission, when BSC receives the DL

LLC frame, it uses the existing resource to establish DL GPRS TBF.
111
FIGURE 119 MEASUREMENT POINT OF NUMBER OF EGPRS DL TBF

ESTABLISHMENT USING EXISTING DL TBF RESOURCE
Unit
Times
C900040147 Number
of EGPRS DL TBF
on PACCH
Description
Under UL transmission status, it is necessary to establish DL TBF

transmission when user plane receives DL LLC Frame from SGSN.
If user plane has not saved DL TBF resource, then user plane requests control plane for resource.
This counter counts the number of times of requesting control
plane for resource to establish EGPRS DL TBF on PACCH.
Measurement
Point

ESTABLISHMENT REQUESTS ON PACCH
Unit
112
Times
OF
GPRS DL TBF
C900040148 Number
of EGPRS DL TBF
on CCCH/PCCCH
Description
When MS is in packet idle status, after BSC receives DL LLC frame

from SGSN, BSC initiates the process of establishing DL TBF which
is assigned on CCCH or PCCCH. BSC user plane first sends the
request for DL establishment to BSC control plane.
Measurement
Point
Under MSs packet idle status, when BSC sends the request for
DL resource to BSC control plane after receiving LLC frame from
SGSN, the counter increments. The measurement point is A1, as
shown in Figure 121.
FIGURE 121 NORMAL CCCH/PCCCH DL TBF ESTABLISHMENT PROCESS
Unit
Times
113
overflow
Description
During the GPRS signaling DL TBF transmission, the DL block RRBP

bit is set to ask MS to respond with a Packet Downlink Ack/Nack
message.
If the specified block of BSC fails to receive response from MS,
then the N3105 counter increments; otherwise, it has a clear. If
no response comes from the MS, then the RRBP bit is set again
to ask MS to respond with a Packet Downlink Ack/Nack message;
that the radio transmission fails and the GPRS signaling DL TBF is
Measurement
Point

increments. The measurement point is A1, as shown in Figure
122.
TBF RELEASE DUE TO N3105 OVERFLOW
Unit
114
Times
OF
GPRS DL SIGNALING
release due to other reasons
Description
Measurement
Point
When BSC is transmitting the last RLC block of GPRS signaling

DL TBF, set FBI to 1, set RRBP to ask the MS to respond with a
Packet Downlink Ack/Nack message, and at the same time, activate T3191. If the specified block receives the MS response, then
T3191 will stop and the DL transmission ends normally. If T3191
overflows, then it is considered that the radio transmission fails
and the GPRS signaling DL TBF is released abnormally.
DUE TO OTHER REASONS
Unit
OF
NUMBER
OF
GPRS DL TBF RELEASE
Times
plane
Description
When the user plane is transmitting the GPRS signaling DL TBF,

if a release request comes from the control plane, then the GPRS
signaling DL TBF will stop and be released abnormally.
115
Measurement
Point
Unit
OF
NUMBER
OF
GPRS DL TBF FORCING
Times
suspension
116
Description
When the user plane is transmitting the GPRS signaling DL TBF, at

least one block must be transmitted in every 5 seconds. After a
DL TBF block is transmitted, BSC will start or restart a 5-second
DL block assigning timer. If the timer expires, it is considered that
the user plane has an instance suspension and the GPRS signaling
DL TBF is released abnormally.
Measurement
Point
When the DL block assigning timer expires, this counter increments. The measurement point is A, as shown in Figure 125.

DUE TO INSTANCE SUSPENSION
Unit
OF
NUMBER
OF
GPRS DL TBF RELEASE
Times
C900040153 Number
of GPRS DL signaling
abnormal
Description
When the user plane is transmitting the GPRS signaling DL TBF, if

the message fails to be sent at the radio interface, the RLC instance
fails to be created, or the resource reassignment fails, the GPRS
signaling DL TBF will be released abnormally.
Measurement
Point
During the transmission of GPRS signaling DL TBF, if the message

be created, or the resource reassignment fails, this counter increments.
Unit
Times
117
overflow
Description
During the transmission of EGPRS signaling DL TBF, the DL block

RRBP bit is set to ask the MS to respond with a Packet Downlink
Ack/Nack message.
If the specified block of BSC does not receive the MS response,
then the N3105 counter increments; if it does, then it has a clear;
if no response comes from the MS, then the RRBP bit is set again to
ask the MS to respond with a Packet Downlink Ack/Nack message;
that the radio transmission fails and the DL TBF is released abnormally.
Measurement
Point

126.
TBF RELEASE DUE TO N3105 OVERFLOW
Unit
118
Times
OF
EGPRS DL SIGNALING
release due to other reasons
Description
When BSC is transmitting the last RLC block of EGPRS signaling

DL TBF, set FBI to 1, set RRBP to ask the MS to respond with a
Packet Downlink Ack/Nack message, and at the same time, activate T3191.
If the specified block receives the MS response, then T3191 will
stop and the DL transmission ends normally. If T3191 overflows,
then it is considered that the radio transmission fails and the EGPRS signaling DL TBF is released abnormally.
Measurement
Point

FIGURE
DUE TO
Unit

OTHER REASONS
OF
NUMBER
OF
Times
119
plane
Description
When the user plane is transmitting the EGPRS signaling DL TBF,

if a release request comes from the control plane, then the EGPRS
signaling DL TBF will stop and be released abnormally.
Measurement
Point
FORCING RELEASE BY CONTROL PLANE
Unit
OF
EGPRS DL TBF
Times
suspension
120
Description
When the user plane is transmitting the EGPRS signaling DL TBF,

at least one block must be transmitted in every 5 seconds. After a
DL TBF block is transmitted, BSC will start or restart a 5-second DL
block assigning timer. If the timer expires, it is considered that the
user plane has an instance suspension and the EGPRS signaling DL
TBF is released abnormally.
Measurement
Point
When the DL block assigning timer expires, this counter increments. The measurement point is A1, as shown in Figure 129.
FIGURE
DUE TO
Unit

INSTANCE SUSPENSION
OF
NUMBER
OF
Times
C900040158 Number
of EGPRS DL signaling
abnormal
Description
When the user plane is transmitting the EGPRS signaling DL TBF, if

the message fails to be sent at the radio interface, the RLC instance
fails to be created, or the resource reassignment fails, the EGPRS
signaling DL TBF will be released abnormally.
Measurement
Point
During the transmission of EGPRS signaling DL TBF, if the message fails to be sent at the radio interface, the RLC instance fails
to be created, or the resource reassignment fails, this counter increments.
Unit
Times
121
C900040159 Number
of GPRS UL TBF
establishments in release
state
Description
If both MS and BSS support reestablishment in released state, BSS

sets RRBP and sends Packet UL Ack message (FAI =1 and TBF Est
= 1) to MS after receiving all RLC blocks from MS.
If MS has no new data to send, MS returns Packet Ctrl Ack message
to BSS.
If MS has new data to send but no DL TBF is available, then TBF
should be reestablished, with the following two cases to be considered:
If system message indicates that Packet Control Ack is of AB

mode, then MS sends Packet Control Ack message (Ctrl Ack
bit is 00) to BSS, and BSS specifies single block resource for
MS by Packet UL Assign message. Subsequent flow is same as
that of TWO STEP access.
If system message indicates that Packet Control Ack is of

RLC/MAC mode, then MS sends Packet Resource Request
message to BSS. Subsequent flow is same as that of TWO
STEP access.
Usage
This counter records the number of reestablishment times of MS

in released state.
Measurement
Point
The measurement point is A, as shown in Figure 130 and Figure

131.
FIGURE 130 MEASUREMENT POINT ON NUMBER
REESTABLISHMENTS IN RELEASED STATE (1)
122
OF
GPRS UL TBF

Unit
OF
GPRS UL TBF
Times
C900040160 Number
of GPRS UL TBF
establishment with existing
UL resource
Description
To accelerate TBF establishment, UPPB caches MSs UL/DL resource within a period of time. When MS attempts to establish
new UL TBF on PACCH, relevant resource is directly assigned to
MS if there is resource as indicated by UPPB; otherwise, MS sends
request for resource to CMP.
Usage
This counter records the number of reestablishing UL GPRS TBF in

released state without having to request for resource.
Measurement
Point

FIGURE 132 MEASUREMENT POINT OF
WITH EXISTING UL RESOURCE
Unit
GPRS UL TBF ESTABLISHMENTS
Times
123
C900040161 Number
of GPRS UL TBF
on PACCH
Description
When MS has DL TBF and the TBF is in transmission status, if MS

has UL data to send but no UL TBF is available, MS sends Packet
DL Ack message together with UL TBF establishment request. This
counter counts the number of resource re-applications after receiving this request.
Usage
This counter records the number of requests for establishing UL

GPRS TBF on PACCH.
Measurement
Point

ESTABLISHING UL GPRS TBF ON PACCH
Unit
OF
REQUESTS
FOR
Times
EGPRS UL data TBF
establishments on PACCH
Description
When there is available DL TBF, MS sends Packet DL Ack message

with UL TBF establishment request. When there is a request to
establish UL TBF on PACCH and the TBF type is EGPRS, the counter
increments.
Usage
This counter records the number of times of establishing EGPRS

UL TBF on PACCH.
Measurement
Point
When Packet DL Ack message with UL TBF establishment request

is received, and the TBF type is EGPRS, the counter increments.
Unit
124
Times
C900040163 Number
of EGPRS UL TBF
establishments in release
state
Description
If both MS and BSS support reestablishment in released state, BSS

sets RRBP and sends Packet UL Ack message (FAI =1 and TBF Est
= 1) to MS after receiving all RLC blocks from MS.
If MS has no new data to send, MS returns Packet Ctrl Ack message
to BSS.
If MS has new data to send but no DL TBF is available, then TBF
should be reestablished, with the following two cases to be considered:
If system message indicates that Packet Control Ack is of AB

mode, then MS sends Packet Control Ack message (Ctrl Ack
bit is 00) to BSS, and BSS specifies single block resource for
MS by Packet UL Assign message. Subsequent flow is same as
that of TWO STEP access.
If system message indicates that Packet Control Ack is of

RLC/MAC mode, then MS sends Packet Resource Request
message to BSS. Subsequent flow is same as that of TWO
STEP access.
Usage
This counter records the number of reestablishment times of MS

in released state.
Measurement
Point
The measurement point is A, as shown in Figure 134 and Figure

135.
OF
EGPRS UL TBF
125

Unit
OF
EGPRS UL TBF
Times
C900040164 Number
of EGPRS UL TBF
establishment with existing
UL resource
Description
To accelerate TBF establishment, UPPB caches MSs UL/DL resource within a period of time. When MS attempts to establish
new UL TBF on PACCH, relevant resource is directly assigned to
MS if there is resource as indicated by UPPB; otherwise, MS sends
request for resource to CMP.
Usage
This counter records the number of reestablishing UL EGPRS TBF

in released state without having to request for resource.
Measurement
Point

WITH EXISTING UL RESOURCE
Unit
126
EGPRS UL TBF ESTABLISHMENTS
Times
C900040165 Number
of EGPRS UL TBF
on PACCH
Description
When MS has DL TBF and the TBF is in transmission status, if MS

has UL data to send but no UL TBF is available, MS sends Packet
DL Ack message together with UL TBF establishment request. This
counter counts the number of resource re-applications after receiving this request.
Usage
This counter records the number of requests for establishing UL

EGPRS TBF on PACCH.
Measurement
Point

ESTABLISHING UL EGPRS TBF ON PACCH
Unit
OF
REQUESTS
FOR
Times
C900040166 Number
of EGPRS UL TBF
on CCCH/PCCCH
Description
When MS has new data to transmit but no corresponding UL/DL

TBF is available, MS initiates UL TBF establishment flow, depending
on whether the cell configures PBCCH on CCCH/PCCCH.
Usage
This counter records the number of requests for establishing EGPRS UL TBF on CCCH/PCCCH.
127
Measurement
Point

Unit
OF
EGPRS UL TBF
Times
dynamic PDCH preemption
for CS service
Description
This counter counts the number of times of PDCH being preempted

when the service instance is performing CS service but fails to
request for the radio channel.
Usage
This counter is used to find out the busy extent of PS service and
CS service in the current cell. It can be used as reference for
expanding radio channel configuration, so as to meet requirements
of both CS and PS services.
Measurement
Point
The counter increments when the following conditions are satisfied:
Unit
Related Features
When the service instance is performing CS service but fails to

request for the radio channel
The database initiates the dynamic PDCH collection
Times
128
C900040168 Number
of GPRS UL TBF
on CCCH/PCCCH
Description
When MS has new data to transmit but no corresponding UL/DL

TBF is available, MS initiates UL TBF establishment flow, depending
on whether the cell configures PBCCH on CCCH/PCCCH.
Usage
This counter records the number of requests for establishing GPRS

UL TBF on CCCH/PCCCH.
Measurement
Point

Unit
OF
GPRS UL TBF
Times
C900040169 Number
of GPRS DL TBF
on PACCH
Description
When UL TBF exists, and there is DL data to be sent through SGSN,

a request will be sent to establish DL TBF on PACCH. This counter
increments upon the request and the TBF type is GPRS.
Usage
This counter counts the number of requests to establish GPRS DL

TBF on PACCH.
Measurement
Point
When a request is sent to establish DL TBF on PACCH and the TBF

type is GPRS, this counter increments.
Unit
Times
129
C900040170 Number
of EGPRS DL TBF
on PACCH
Description
When UL TBF exists, and there is DL data to be sent through SGSN,

a request will be sent to establish DL TBF on PACCH. This counter
increments upon the request and the TBF type is EGPRS.
Usage
This counter counts the number of requests to establish EGPRS DL

TBF on PACCH.
Measurement
Point
When a request is sent to establish DL TBF on PACCH and the TBF

type is EGPRS, this counter increments.
Unit
Times
C900040171 Number
of GPRS UL TBF
on PACCH
Description
When there is available DL TBF, MS sends Packet DL Ack message

with UL TBF establishment request. When there is a request to
establish UL TBF on PACCH and the TBF type is GPRS, the counter
increments.
Usage
This counter records the number of requests to establish GPRS UL

TBF on PACCH.
Measurement
Point
When Packet DL Ack message with UL TBF establishment request

is received, and the TBF type is GPRS, this counter increments.
Unit
Times
DL RLC pending blocks in
MCS1 on PDTCH
Description
130


from BSC to MS, with coding method of MCS1.
Usage

PDTCH, with coding method of MCS1.
Measurement
Point
When BSC sends a pending RLC block whose coding method is

MCS1 to MS, the counter increments. The measurement point is
BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC PENDING
Times
ZGO-03-05-001 Modulation and Coding Scheme #1~#9
MCS2 on PDTCH
Description

Usage

Measurement
Point

MCS2 to MS via BTS, the counter increments. The measurement
131

BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC PENDING
Times
MCS3 on PDTCH
Description

Usage

Measurement
Point

BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC PENDING
Times
132
MCS4 on PDTCH
Description

Usage

Measurement
Point

point is A, as shown inFigure 143.
BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC PENDING
Times
MCS5 on PDTCH
Description

Usage

133
Measurement
Point

BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC PENDING
Times
MCS6 on PDTCH
Description

Usage

Measurement
Point

BLOCKS ON PDTCH
Unit
Related Features
134
OF
NUMBER
OF
DL RLC PENDING
Times
MCS7 on PDTCH
Description

Usage

Measurement
Point

BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC PENDING
Times
MCS8 on PDTCH
Description

135
Usage

Measurement
Point

BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC PENDING
Times
MCS9 on PDTCH
Description

136
Usage

Measurement
Point


BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC PENDING
Times
RLC NACK blocks in MCS1
on PDTCH
Description

blocks from BSC to MS, with coding method of MCS1.
Usage

sent on PDTCH, with coding method of MCS1.
Measurement
Point
When BSC sends retransmitted RLC block whose coding method is

FIGURE 149
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
137
on PDTCH
Description

Usage

Measurement
Point

FIGURE 150
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
on PDTCH
Description

Usage
138

Measurement
Point

FIGURE 151
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
on PDTCH
Description

Usage

Measurement
Point

FIGURE 152
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
139
on PDTCH
Description

Usage

Measurement
Point

FIGURE 153
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
on PDTCH
Description
140

Usage

Measurement
Point

FIGURE 154
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
on PDTCH
Description

Usage

Measurement
Point

141
FIGURE 155
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
on PDTCH
Description

Usage

Measurement
Point

FIGURE 156
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
142
on PDTCH
Description

Usage

Measurement
Point

FIGURE 157
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
DL RLC NACK BLOCKS
Times
RLC new blocks in MCS1 on
PDTCH
Description

RLC blocks from BSC to MS, with coding method of MCS1.
Usage

RLC blocks sent by BSC on PDTCH, with coding method of MCS1.
143
Measurement
Point

of MCS1) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 158.
ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
PDTCH
Description

Usage

Measurement
Point

ON PDTCH
Unit
Related Features
144
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
PDTCH
Description

Usage

Measurement
Point

ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
PDTCH
Description

145
Usage

Measurement
Point

ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
PDTCH
Description

146
Usage

Measurement
Point


ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
PDTCH
Description

Usage

Measurement
Point

ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
147
PDTCH
Description

Usage

Measurement
Point

ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
PDTCH
Description

Usage
148

Measurement
Point

ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
PDTCH
Description

Usage

Measurement
Point

ON PDTCH
Unit
Related Features
OF
NUMBER
OF
DL RLC NEW BLOCKS
Times
149
UL RLC pending blocks in
MCS1 on PDTCH
Description
This counter counts the number of useful UL MCS1-coded pending
Usage

Measurement
Point
When BSC receives MCS1-coded UL pending RLC block, the

Figure 167.
BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC PENDING
Times
MCS2 on PDTCH
Description
150
Usage

Measurement
Point

Figure 168.
BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC PENDING
Times
MCS3 on PDTCH
Description
Usage

Measurement
Point

Figure 169.
151

BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC PENDING
Times
MCS4 on PDTCH
Description
Usage

Measurement
Point

Figure 170.
BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC PENDING
Times
152
MCS5 on PDTCH
Description
Usage

Measurement
Point

Figure 171.
BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC PENDING
Times
MCS6 on PDTCH
Description
Usage

153
Measurement
Point

Figure 172.
BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC PENDING
Times
MCS7 on PDTCH
Description
Usage

Measurement
Point

Figure 173.
BLOCKS ON PDTCH
Unit
Related Features
154
OF
NUMBER
OF
UL RLC PENDING
Times
MCS8 on PDTCH
Description
Usage

Measurement
Point

Figure 174.
BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC PENDING
Times
MCS9 on PDTCH
Description
155
Usage

Measurement
Point

Figure 175.
BLOCKS ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC PENDING
Times
on PDTCH
Description
This counter counts the number of useful UL MCS1-coded retransmitted RLC blocks received on PDTCH.
156
Usage
This counter counts the number of useful UL MCS1-coded retransmitted RLC blocks received by BSC on PDTCH.
Measurement
Point
When BSC receives MCS1-coded UL retransmitted RLC block, the

Figure 176.
FIGURE 176
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
on PDTCH
Description
Usage
Measurement
Point

Figure 177.
FIGURE 177
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
157
on PDTCH
Description
Usage
Measurement
Point

Figure 178.
ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
on PDTCH
Description
Usage
158
Measurement
Point

Figure 179.
FIGURE 179
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
on PDTCH
Description
Usage
Measurement
Point

Figure 180.
FIGURE 180
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
159
on PDTCH
Description
Usage
Measurement
Point

Figure 181.
ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
on PDTCH
Description
160
Usage
Measurement
Point

Figure 182.
FIGURE 182
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
on PDTCH
Description
Usage
Measurement
Point

Figure 183.
161

ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
on PDTCH
Description
Usage
Measurement
Point

Figure 184.
ON PDTCH
Unit
Related Features
OF
NUMBER
OF
UL RLC NACK BLOCKS
Times
162
PDTCH
Description
This counter counts the number of useful UL MCS1-coded firsttransmitted RLC blocks received on PDTCH.
Usage
This counter counts the number of useful UL MCS1-coded firsttransmitted RLC blocks received by BSC on PDTCH.
Measurement
Point
When BSC receives MCS1-coded UL first-transmitted RLC block,

the counter increments. The measurement point is A, as shown in
Figure 185.
FIGURE 185
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
PDTCH
Description
Usage
163
Measurement
Point

Figure 186.
FIGURE 186
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
PDTCH
Description
Usage
Measurement
Point

Figure 187.
FIGURE 187
ON PDTCH
Unit
Related Features
164
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
PDTCH
Description
Usage
Measurement
Point

Figure 188.
FIGURE 188
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
PDTCH
Description
165
Usage
Measurement
Point

Figure 189.
FIGURE 189
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
PDTCH
Description
166
Usage
Measurement
Point

Figure 190.
FIGURE 190
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
PDTCH
Description
Usage
Measurement
Point

Figure 191.
FIGURE 191
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
167
PDTCH
Description
Usage
Measurement
Point

Figure 192.
FIGURE 192
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
PDTCH
Description
Usage
168
Measurement
Point

Figure 193.
FIGURE 193
ON PDTCH
Unit
Related Features
MEASUREMENT POINT
OF
NUMBER
OF
UL RLC NEW BLOCKS
Times
C900040232 Accumulated
throughput of UL GPRS TBF
Description
Usage
Measurement
Point
This counter counts the total uplink GPRS throughput after the
UPPB board receives uplink data blocks. When the URLC module of the UPPB board receives data blocks in extension status or
transmission status changes to extension or delay status and when
the TBF type is GPRS, the counter multiplies the throughput and
transmission bytes of each uplink TBF.
This counter counts the throughput of uplink GPRS TBF.
The counter is updated when the URLC module receives uplink data
blocks. The measurement point is A, as shown in Figure 194.
Unit
OF
UPLINK GPRS TBF THROUGHPUT
kBps * kB
169
throughput of DL GPRS TBF
Description
Usage
Measurement
Point
This counter counts the total downlink GPRS throughput after the
UPPB board receives the Packet DownLink Ack message. After
the DRLC module of the UPPB board receives the message, the
counter multiplies the throughput and transmission bytes of each
downlink TBF if the module changes from transmission status to
delay status and the TBF type is GPRS.
This counter counts the throughput of downlink GPRS TBF.
The counter is updated when the DRLC module receives the Packet
DownLink Ack message. The measurement point is A, as shown
in Figure 195.
Unit
OF
DOWNLINK GPRS TBF THROUGHPUT
kBps * kB
throughput of UL EGPRS
TBF
Description
Usage
Measurement
Point
170
This counter counts the total uplink EGPRS throughput after the
UPPB board receives uplink data blocks. When the URLC module of the UPPB board receives data blocks in extension status or
transmission status changes to extension or delay status and when
the TBF type is EGPRS, the counter multiplies the throughput and
transmission bytes of each uplink TBF.
This counter counts the throughput of uplink EGPRS TBF.
The counter is updated when the URLC module receives uplink data
blocks. The measurement point is A, as shown in Figure 196.
Unit
OF
UPLINK EGPRS TBF THROUGHPUT
kBps * kB
throughput of DL EGPRS
TBF
Description
Usage
Measurement
Point
This counter counts the total downlink EGPRS throughput after the
UPPB board receives the EGPRS Packet DownLink Ack message.
After the DRLC module of the UPPB board receives the message,
the counter multiplies the throughput and transmission bytes of
each downlink TBF if the module changes from transmission status
to delay status and the TBF type is EGPRS.
This counter counts the throughput of downlink EGPRS TBF.
The counter is updated when the DRLC module receives the EGPRS
Packet DownLink Ack message. The measurement point is A, as
FIGURE 197 MEASUREMENT POINT OF DOWNLINK EGPRS TBF THROUGHPUT
Unit
kBps * kB
171
172
Chapter
CPU Load Measurement

Table of Contents
Overview........................................................................ 173
C900050001 Average load of the processor......................... 173
C900050002 Peak value of the processor load ..................... 173
Overview
CPU load measurement consists of statistic of the average value
and peak value of CPU load.
The measurement takes BSC as the statistics unit.
C900050001 Average load

of the processor
Description
This counter counts the average load of the main processor during
measurement period.
Measurement
Point
After a collection period ends, calculation will be executed according to the sampling load of the main processor.
Unit
Percent
C900050002 Peak value of

the processor load
Description
This counter counts the peak value of the main processor load
during measurement period.
Measurement
Point
The measurement point is the peak value of the sampling main

processor load during collection period.
Unit
Percent
173
174
Chapter
CS Basic Measurement
Table of Contents
Overview........................................................................ 182
C900060001 Number of MTC access attempts ..................... 183
C900060002 Number of MTC access success ....................... 183
C900060003 Number of SDCCH seizure attempts for assignment ............................................................................. 184
C900060004 Number of SDCCH seizure success for assignment ............................................................................. 185
C900060005 Number of SDCCH seizure failure for assignment ............................................................................. 186
C900060006 Number of SDCCH seizure attempts for handover............................................................................. 187
C900060007 Number of SDCCH seizure failure for handover............................................................................. 189
C900060008 Number of SDCCH allocation success for assignment ............................................................................. 190
C900060009 Number of SDCCH allocation failure for assignment ............................................................................. 191
C900060010 Number of signaling TCH/F seizure attempts for
assignment..................................................................... 192
C900060011 Number of signaling TCH/F seizure failure for
assignment..................................................................... 193
C900060012 Number of signaling TCH/F seizure attempts for
handover........................................................................ 194
handover........................................................................ 197
C900060014 Number of signaling TCH/F allocation success for
assignment..................................................................... 198
C900060015 Number of signaling TCH/F allocation failure for
assignment..................................................................... 198
C900060016 Number of signaling TCH/F allocation failure for
handover........................................................................ 199
C900060017 Number of signaling TCH/F assignment success
for assignment ................................................................ 200
C900060018 Number of signaling TCH/F assignment failure
for assignment ................................................................ 201
C900060019 Number of voice TCH/F seizure attempts for assignment........................................................................ 202
C900060020 Number of voice TCH/F seizure failure for assignment........................................................................ 204
handover........................................................................ 205
C900060022 Number of voice TCH/F seizure failure for handover............................................................................. 208
C900060023 Number of TCH/F allocation success for assignment (speech version1).................................................... 209
175
C900060024 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version1) ......... 210
C900060028 Number of voice TCH/F assignment success............................................................................... 215
C900060029 Number of voice TCH/F assignment failure for
assignment..................................................................... 216
C900060030 Number of data TCH/F seizure attempts for assignment........................................................................ 217
C900060031 Number of data TCH/F seizure failure for assignment ............................................................................. 219
C900060032 Number of data TCH/F seizure attempts for handover............................................................................. 220
C900060033 Number of data TCH/F seizure failure for handover............................................................................. 223
C900060034 Number of data TCH/F allocation success for assignment........................................................................ 224
C900060035 Number of data TCH/F allocation failure due to
channel activation failure for assignment ............................ 225
C900060036 Number of data TCH/F assignment success............................................................................... 226
C900060037 Number of data TCH/F assignment failure ......... 227
C900060038 Number of signaling TCH/H seizure attempts for
assignment..................................................................... 228
C900060039 Number of signaling TCH/H seizure failure for
assignment..................................................................... 229
C900060040 Number of signaling TCH/H seizure attempts for
handover........................................................................ 230
C900060041 Number of signaling TCH/H seizure failure for
handover........................................................................ 233
C900060042 Number of voice TCH/H seizure attempts for assignment........................................................................ 234
C900060043 Number of voice TCH/H seizure failure for assignment........................................................................ 236
handover........................................................................ 237
C900060045 Number of voice TCH/H seizure failure for handover............................................................................. 240
C900060046 Number of data TCH/H seizure attempts for assignment........................................................................ 241
C900060047 Number of data TCH/H seizure failure for assignment ............................................................................. 243
C900060048 Number of data TCH/H seizure attempts for handover............................................................................. 244
C900060049 Number of data TCH/H seizure failure for handover............................................................................. 247
C900060050 Number of SAPI3 link establishment requests on
SDCCH (MO-SM) ............................................................. 248
SDCCH (MT-SM).............................................................. 250
C900060052 Number of SDCCH drops due to handover failure ................................................................................ 251
C900060053 Number of SDCCH drops................................ 253
C900060054 Number of TCH/F drops ................................. 254
C900060055 Number of TCH/H drops................................. 254
176
Chapter 4 CS Basic Measurement
C900060056 Average number of idle TCH/F with interference

band 1 ........................................................................... 255
band 2 ........................................................................... 255
band 3 ........................................................................... 255
band 4 ........................................................................... 256
band 5 ........................................................................... 256
C900060061 Average number of idle TCH/H with interference
band 1 ........................................................................... 257
band 2 ........................................................................... 257
band 3 ........................................................................... 258
band 4 ........................................................................... 258
band 5 ........................................................................... 259
C900060066 Number of samples with UL RQ = 0 ................. 259
C900060074 Number of samples with DL RQ = 0................. 262
C900060082 Number of TCH/F handover attempts due to UL
strength ......................................................................... 264
C900060083 Number of TCH/F handover attempts due to DL
strength ......................................................................... 265
quality ........................................................................... 266
quality ........................................................................... 266
interference .................................................................... 267
interference .................................................................... 268
good C/I ........................................................................ 268
C900060089 Number of TCH/F handover attempts due to bad
C/I ................................................................................ 269
PBGT ............................................................................. 270
large TA ......................................................................... 270
other reasons.................................................................. 271
handover........................................................................ 272
177

handover success ............................................................ 273
C900060095 Number of MSC-controlled outgoing handover .............................................................................. 273
C900060096 Number of MSC-controlled outgoing handover
success .......................................................................... 274
handover........................................................................ 275
C900060099 Number of MSC-controlled incoming handover............................................................................. 276
C900060100 Number of MSC-controlled incoming handover
due to forced release ....................................................... 277
due to queue .................................................................. 278
success .......................................................................... 279
C900060103 Number of incoming handover from undefined
layer (GSM900) to current layer(GSM1800) ........................ 280
C900060104 Number of incoming handover success from undefined layer(GSM900) to current layer (GSM1800) ............. 281
C900060105 Number of incoming handover from undefined
layer (GSM1800) to current layer (GSM900) ....................... 282
C900060106 Number of incoming handover success from undefined layer(GSM1800) to current layer(GSM900) .............. 283
C900060107 Number of incoming handover from the same
layer GSM900 to GSM1800 ............................................... 284
C900060108 Number of incoming handover success from the
same layer GSM900 to GSM1800 ....................................... 284
C900060109 Number of incoming handover from GSM900 to
GSM1800 from the upper layer.......................................... 285
GSM900 to GSM1800 in the upper layer ............................. 286
C900060111 Number of incoming handover from GSM900 to
GSM1800 in the lower layer .............................................. 287
GSM900 to GSM1800 in the lower layer .............................. 288
to GSM900 from the same layer ........................................ 289
GSM1800 to GSM900 from the same layer .......................... 290
to GSM900 from the upper layer........................................ 291
GSM1800 to GSM900 from the upper layer ......................... 292
to GSM900 from the lower layer ........................................ 293
GSM1800 to GSM900 from the lower layer .......................... 294
C900060119 Number of Intra-cell handover ........................ 294
C900060120 Number of Intra-cell handover success ............ 295
C900060121 Maximum number of busy TCH/H .................... 296
C900060122 Average number of available SDCCH................ 297
C900060123 Average number of unavailable SDCCH ............ 297
C900060124 SDCCH busy time ......................................... 298
C900060125 Average number of available radio channel ................................................................................ 299
C900060126 Average number of unavailable radio channel ................................................................................ 300
178
C900060127 TCH/H busy time .......................................... 300

C900060128 Maximum number of busy TCH/F .................... 301
C900060129 TCH/F busy time ........................................... 302
C900060130 Number of healthy TRXs ................................ 303
C900060131 Number of CM service requests of MOC............ 304
C900060132 Number of SAPI3 link establishment success on
SDCCH (MT-SM).............................................................. 305
C900060133 Number of available defined SDCCH ................ 306
C900060134 Number of available defined TCH/F.................. 306
C900060135 Number of signaling TCH/H assignment failure ................................................................................ 307
C900060136 Number of MOC access attempts..................... 308
C900060137 Number of wireless access due to paging responses ......................................................................... 309
C900060138 Number of TCH/F allocation failure due to BTS
connection failure for assignment (speech version1)............. 310
C900060139 Number of TCH/F allocation failure due to BIU
C900060140 Number of TCH/F allocation failure due to TCU
BTS connection failure for assignment) ............................... 320
BIU connection failure for assignment ................................ 320
TCU connection failure for assignment ................................ 321
C900060151 Number of voice TCH/H drops due to handover
failure ............................................................................ 322
C900060152 Number of Abis interface paging command messages............................................................................. 324
C900060153 Number of Abis CS paging messages ............... 325
C900060154 Number of Abis PS paging messages ............... 325
C900060155 Number of available defined TCH/H ................. 326
C900060156 Number of TCH/F allocation failure due to channel activation failure for handover(speech version1) ............. 327
connection failure for handover (speech version1)................ 328
C900060160 Number of TCH/F allocation failure due to channel activation failure for handover(speech version2) ............. 332
179

C900060164 Number of TCH/F allocation failure due to channel activation failure for handover (speech version3) ............ 336
C900060168 Number of Voice TCH/F handover success ......... 341
channel activation failure for handover ............................... 343
BTS connection failure for handover ................................... 344
BIU connection failure for handover ................................... 345
TCU connection failure for handover ................................... 346
C900060173 Number of data TCH/F handover success ......... 347
C900060174 Number of signaling TCH/H allocation failure for
assignment..................................................................... 350
C900060175 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version1) ......... 351
C900060176 Number of TCH/H allocation failure due to BTS
C900060177 Number of TCH/H allocation failure due to BIU
C900060178 Number of TCH/H allocation failure due to TCU
C900060179 Number of TCH/H allocation failure due to channel activation failure for handover (speech version1) ............ 355
180

C900060199 Number of Voice TCH/H assignment success............................................................................... 378
C900060200 Number of Voice TCH/H assignment failure ................................................................................ 379
C900060201 Number of Voice TCH/H handover success ......... 380
C900060202 Number of data TCH/H allocation failure due to
channel activation failure for assignment ............................ 383
BTS connection failure for assignment ................................ 384
BIU connection failure for assignment ................................ 384
TCU connection failure for assignment ................................ 385
channel activation failure for handover ............................... 386
BTS connection failure for handover ................................... 387
BIU connection failure for handover ................................... 388
TCU connection failure for handover ................................... 389
C900060210 Number of data TCH/H assignment success............................................................................... 390
C900060211 Number of data TCH/H assignment failure ......... 392
C900060212 Number of data TCH/H handover success ......... 392
C900060213 Number of BSC-controlled incoming handover
due to forced release ....................................................... 395
due to queues ................................................................. 396
due to forced handover .................................................... 397
due to forced handover .................................................... 398
C900060217 Number of unavailable defined TCH/H.............. 398
C900060218 Number of unavailable defined TCH/F .............. 399
C900060219 Number of signaling TCH/F drops due to handover failure ................................................................... 400
C900060220 Number of voice TCH/F drops due to handover
failure ............................................................................ 402
C900060221 Number of data TCH/F drops due to handover
failure ............................................................................ 403
C900060222 Number of signaling TCH/H drops due to handover failure ................................................................... 406
C900060223 Number of data TCH/H drops due to handover
failure ............................................................................ 408
C900060224 Number of TCH/H handover attempts due to UL
strength ......................................................................... 410
181
C900060225 Number of TCH/H handover attempts due to DL

strength ......................................................................... 410
quality ........................................................................... 411
quality ........................................................................... 412
interference .................................................................... 412
interference .................................................................... 413
C900060230 Number of TCH/H inter-subcell handover attempts due to good C/I .................................................... 414
C900060231 Number of TCH/H inter-subcell handover attempts due to bad C/I ...................................................... 414
PBGT ............................................................................. 415
large TA ......................................................................... 416
other reasons.................................................................. 417
C900060235 Number of signaling TCH/H assignment success............................................................................... 417
C900060236 Number of MOC access success ...................... 418
C900060237 Number of dual band outgoing handover .......... 419
C900060238 Number of dual band outgoing handover success............................................................................... 420
C900060239 Number of dual band incoming handover ......... 421
C900060240 Number of dual band incoming handover success............................................................................... 421
C900060241 Number of SDCCH assignment attempts .......... 422
C900060242 Number of SDCCH assignments success........... 423
C900060243 Number of SDCCH assignment failure .............. 424
C900060244 Number of voice TCH/F drops due to radio link
failure ............................................................................ 425
C900060245 Number of voice TCH/H drops due to radio link
failure ............................................................................ 426
Overview
CS basic measurement involves counters that are used to evaluate the circuit switching service performance and status. These
counters are often used in measurement related to radio access,
SDCCH, TCH, SAPI3, call drop, handover, Abis interface message
statistics, and radio resource availability.
182
MTC access attempts
Description
This counter counts the number of channel requests due to MTC

random access. When MS sends the CHL_REQ message to BSC
through BTS to request for radio channel, if TA does not exceed the
cell range and the access reason is MTC, the counter increments.
Usage
This counter is used to find out the frequency of channel request

due to MTC.
Measurement
Point
The counter counts when MS requests for channel from BSC and
TA does not exceed the cell range. The measurement point is A1,
FIGURE 198 RADIO ACCESS FLOW
Unit
Times
MTC access success
Description
This counter counts the number of MS successfully accessing the

channel assigned in the immediate assignment message (the access reason is due to MTC). The counter increments when the following two conditions are satisfied:
MS receives the IMM_ASS message from BSC and successfully

accesses the channel.
183
BSC receives the EST_IND message from MS.
Usage
This counter is used to find out the frequency of MS access success

due to MTC.
Measurement
Point
This counter counts when BSC receives the EST_IND message.

Unit
Times
SDCCH seizure attempts for
assignment
Description
Usage
184
SDCCH channel allocation attempt is activated by the MS channel

request message CHL_REQ. After BSC receives this message, it
attempts to allocate channel for the request.
If allocation and occupation succeed,

C900060004 accumulate simultaneously.
If occupation fails and the failure is due to transceiver fault,

C900060003, C900060004, and C900060005 do not change.
For failures in other cases, C900060003 and C900060005 accumulate simultaneously.
C900060003 and
This counter counts the number of SDCCH channel occupation

attempts during assignment, including the number of occupation
success (C900060004) and the number of occupation failure
(C900060005).
Measurement
Point
This counter counts when BSC completes requesting for channel

(due to assignment) (C900060004 + C900060005). The measurement point is A1, as shown in Figure 200.
FIGURE 200 IMMEDIATE ASSIGNMENT FLOW
Unit
Related Features
Times
ZGB-03-02-003 Dynamic Configuration of SDCCH
ZGB-06-01-007 Cell Traffic Statistics
SDCCH seizure success for
assignment
Description

attempts to allocate channel for the request. This counter accumulates when allocation and occupation succeed.
Usage
This counter counts the number of successful SDCCH channel occupations during assignment.
Measurement
Point
This counter counts when BSC requests for channel (due to assignment) and occupies the channel successfully. The measurement
point is A1, as shown in Figure 201.
185
Unit
Related Features
Times
SDCCH seizure failure for
assignment
Description
186

attempts to allocate channel for the request.
If allocation succeeds but occupation fails, this counter accumulates.
If the request returns that the transceiver is faulty, this counter

does not change.
For failures in other cases, this counter accumulates.
Usage
This counter counts the number of SDCCH channel occupation failures during assignment.
Measurement
Point
This counter counts when BSC requests for channel (due to assignment) but fails to occupy the channel. The measurement point is
A1, as shown in Figure 202.
Unit
Related Features
Times
SDCCH seizure attempts for
handover
Description
SDCCH channel allocation attempt is activated by the channel request message RADIO_APPLY from other channel instances. After
BSC receives this message, it attempts to allocate channel for the
request.

If occupation fails, C900060006 and C900060007 accumulate

simultaneously.
If the request returns no channel available but queuing or

forced release is possible, enter the state of waiting for resource.
C900060006 and
If the waiting for resource succeeds, C900060006 and

If the waiting for resource fails and the failure is due
to transceiver fault, C900060006, C901250005, and
C900060007 do not change.
187
Usage
This counter counts the number of SDCCH channel occupation

attempts during handover, including the number of occupation
success (C900060006) and the number of occupation failure
(C900060007).
Measurement
Point
BSC completes requesting for channel (due to handover), or BSC

receives the internal message of waiting for resource successfully
or waiting for resource failed (C901250005 + C900060007). The
measurement point is B1 as shown in Figure 203 and C1 as shown
in Figure 204.
FIGURE 203 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER)
FIGURE 204 EXTERNAL HANDOVER FLOW
Unit
188
Times
Related Features

ZGO-02-02-004 SDCCH/SDCCH Handover
SDCCH seizure failure for
handover
Description
Usage
Measurement
Point
SDCCH channel allocation attempt is activated by the channel request message RADIO_APPLY from other channel instances. After
BSC receives this message, it attempts to allocate channel for the
request.
If occupation fails, this counter accumulates.

forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.

does not change.
This counter counts the number of SDCCH occupation failure.

BSC requests for channel (due to handover) but fails to occupy
the channel, or BSC fails to wait for internal resource. The measurement point is B1 as shown in Figure 205 and C1 as shown in
Figure 206.
FIGURE 205 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER)
189
FIGURE 206 EXTERNAL HANDOVER FLOW
Unit
Related Features
Times
SDCCH allocation success
for assignment
190
Description
After BSC responds the channel request message to allocate and

occupy SDCCH channel successfully, BSC sends the CHL_ACT message to BTS to activate this SDCCH. If the SDCCH is activated successfully (that is, when BSC receives the CHL_ACT_ACK message
from BTS), this counter accumulates.
Usage
This counter counts the number of successful SDCCH channel allocations during assignment.
Measurement
Point
This counter counts when BSC receives the CHL_ACT_ACK message from BTS and the cause is assignment. The measurement
Unit
Related Features
Times
SDCCH allocation failure for
assignment
Description

occupy SDCCH channel successfully, BSC sends the CHL_ACT message to BTS to activate this SDCCH. If channel activation fails due
to receiving channel activation failure message, incorrect channel activation response message, T9103 being timeout, channel
instance being released or channel being forcibly released, this
counter accumulates.
Usage
This counter counts the number of SDCCH channel allocation failure during assignment.
Measurement
Point
BSC activates SDCCH channel due to assignment, but receives

channel activation failure message, incorrect channel activation
response message, T9103 being timeout, channel instance being
released, or channel being forcibly released. The measurement
191
Unit
Related Features
Times
signaling TCH/F seizure
attempts for assignment
Description
This counter counts the number of TCH/F channel occupation attempts during assigning signaling channels, including the number
of occupation success (C901260002) and the number of occupation failure (C900060011).
Usage
After BSC receives the channel request, it attempts to allocate

channel for the request.
Measurement
Point
192

If the request returns that the transceiver is faulty,

For other cases, C900060010 and C900060011 accumulate simultaneously.
C900060010 and

(due to assignment and the channel is used as signaling channel)
(C901260002 + C900060011). The measurement point is A1, as
Unit
Related Features
Times
ZGB-03-01-004 Immediate TCH Assignment
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
failure for assignment
Description
This counter counts the number of TCH/F channel occupation failures during assigning signaling channels.
Measurement
Point

does not change.
BSC requests for channel (due to assignment and the channel is

used as signaling channel) but fails to occupy the channel, or BSC
fails to wait for internal resource. The measurement point is A1,
193
FIGURE 210 IMMEDIATE ASSIGNMENT OCCUPATION FAILURE FLOW 1
Unit
Related Features
Times
attempts for handover
Description
This counter counts the number of TCH/F channel occupation attempts during signaling channel handover, including the number


simultaneously.

Measurement
Point
194
C900060012 and

If the waiting for resource fails, C900060012 and

BSC completes requesting for channel (due to handover and the

channel is used as signaling channel), or BSC receives the internal message of waiting for resource successfully or waiting for resource failed (C901260002 + C900060011). The measurement
point is C1 as shown in Figure 211 and Figure 212, and D1 as

shown in Figure 213 and Figure 214.
FIGURE 211 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, TC IS
INTERNAL)
FIGURE 212 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER,

CHANNEL TYPE CHANGED, TC IS EXTERNAL)
195
FIGURE 213 EXTERNAL HANDOVER FLOW (TC IS INTERNAL)
FIGURE 214 EXTERNAL HANDOVER FLOW (TC IS EXTERNAL)
Unit
Related Features
Times
ZGB-02-02-001 Basic Handover
196
failure for handover
Description
This counter counts the number of TCH/F channel occupation failures during signaling channel handover.
Measurement
Point


does not change.
BSC requests for channel (due to handover and the channel is

fails to wait for internal resource. The measurement point is C1
as shown in Figure 215 and D1 as shown in Figure 216.
FIGURE 215 INTRA-BSC HANDOVER OCCUPATION FAILURE FLOW
FIGURE 216 INTER-BSC HANDOVER OCCUPATION FAILURE FLOW
Unit
Related Features
Times
197
signaling TCH/F allocation
success for assignment
Description
This counter counts the number TCH/F channel being allocated

successfully during signaling channel assignment.
occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F channel. If the activation succeeds (that is, when BSC receives the CHL_ACT_ACK message
from BTS), the counter accumulates.
Measurement
Point
The counter increments when BSC receives the CHL_ACT_ACK

message from BTS, the cause is due to assignment and the
channel is used as signaling channel. The measurement point is
Unit
Related Features
Times
Description
198
This counter counts the number of TCH/F channel allocation failures during signaling channel assignment.
After BSC responds to the channel request message to allocate

and occupy TCH/F channel successfully, BSC sends the CHL_ACT
message to BTS to activate this TCH/F channel.
If the channel activation fails due to receiving channel activation
failure message, incorrect channel activation response message,
T9103 timeout, channel instance being released or channel being
released forcibly, this counter accumulates.
Measurement
Point
BSC activates TCH/F channel due to assignment and uses it as

signaling channel, but receives channel activation failure message,
incorrect channel activation response message, T9103 being timeout, channel instance being released, or channel being forcibly released. The measurement point is A2, as shown in Figure 218.
FIGURE 218 IMMEDIATE ASSIGNMENT ALLOCATION FAILURE FLOW 2
Unit
Related Features
Times
Description
This counter counts the number of TCH/F channel allocation failures during signaling channel handover.
occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F channel.
released forcibly, this counter will accumulate.
Measurement
Point
BSC activates TCH/F channel due to handover and uses it as signaling channel, but receives channel activation failure message,
incorrect channel activation response message, T9103 being timeout, channel instance being released, or channel being forcibly released.
199
The measurement point is C3 as shown in Figure 219 and D3 as

FIGURE 219 INTERNAL HANDOVER FAILURE FLOW 1 (INTRA-CELL
HANDOVER, TC IS INTERNAL)
FIGURE 220 EXTERNAL HANDOVER FAILURE FLOW 2 (TC IS INTERNAL)
Unit
Related Features
Times
signaling TCH/F assignment
Description
This counter counts the number of successful assignments of

TCH/F as signaling channel.
occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. For immediate assignment,
after the TCH/F activation succeeds, BTS finds the MS accessed
and sends the EST_IND message to BSC, this counter accumulates when BSC receives the message correctly.
200
Measurement
Point
For immediate assignment, this counter counts when BSC receives

the EST_IND message correctly. The measurement point is A3, as
Unit
Related Features
Times
Description
This counter counts the number of failing to assign TCH/F channel

as signaling channel.
message to BTS to activate this TCH/F. If BSC does not receive the
MS access notification within a certain time, this assignment fails.
Measurement
Point

incorrect EST_IND message or T3101 is timeout. The measurement point is A3, as shown in Figure 222.
201
FIGURE 222 IMMEDIATE ASSIGNMENT FAILURE FLOW 3
Unit
Related Features
Times
C900060019 Number
of voice TCH/F seizure
Description
This counter counts the number of TCH/F channel being attempted

to be occupied during voice channel assignment, including the
number of occupation success (C901260021) and the number of
occupation failure (C900060020).
After BSC receives the channel request massage, it attempts to
allocate channel for the request.


simultaneously.

202
C900060019 and


Measurement
Point
BSC completes requesting for channel (due to assignment and the

channel is used as voice channel), or BSC receives the internal
message of waiting for resource successfully or waiting for resource failed (C901260021 + C900060020). The measurement
point is B1, as shown in Figure 223 and Figure 224.
.
FIGURE 223 COMMON ASSIGNMENT FLOW (TC IS INTERNAL)
FIGURE 224 COMMON ASSIGNMENT FLOW (TC IS EXTERNAL)
Unit
Related Features
Times
203
voice TCH/F seizure failure
for assignment
Description
This counter counts the number of TCH/F channel occupation failure during voice channel assignment.
After BSC receives the channel request message, it attempts to
Measurement
Point


does not change.

used as voice channel) but fails to occupy the channel, or BSC
fails to wait for internal resource. The measurement point is B1,
FIGURE 225 COMMON ASSIGNMENT FAILURE FLOW 1 (TC IS INTERNAL)
Unit
Related Features
Times
204
C900060021 Number
Description

to be occupied during voice channel handover, including the number of occupation success (C901260024) and the number of occupation failure (C900060022).


simultaneously.

Measurement
Point
C900060021 and



205

INTERNAL)

206
Unit
Related Features
Times
207
for handover
Description
This counter counts the number of TCH/F channel occupation failure during voice channel handover.
Measurement
Point
If allocation or occupation fails, this counter accumulates.


does not change.
BSC requests for channel (due to handover and the channel is used
as voice channel) but fails to occupy the channel, or BSC fails to
wait for internal resource. The measurement point is C1 as shown
in Figure 230 and D1 as shown in Figure 231.
Unit
Related Features
Times
208
TCH/F allocation success
for assignment (speech
version1)
Description
This counter counts the number of TCH/F channel being allocated

successfully during voice channel assignment (speech version 1).
occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If the TCH/F is activated successfully (that is, when BSC receives the CHL_ACT_ACK message
Measurement
Point
This counter counts when BSC receives the CHL_ACT_ACK message from BTS, the cause is assignment and the channel is used
as voice channel (speech version 1). The measurement point is
B3, as shown in Figure 232 and Figure 233.
209
Unit
Related Features
Times
ZGB-01-01-001 Full Rate (FR) Speech Codec
TCH/F allocation failure due
to channel activation failure
version1)
Description
This counter counts the number of TCH/F channel allocation failure

due to channel activation failure during voice channel assignment
(speech version 1).
occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If channel activation fails due
Measurement
Point
210
BSC activates TCH/F channel due to assignment and uses the

channel as voice channel (speech version 1), but receives channel
activation failure message, incorrect channel activation response
message, T9103 being timeout, channel instance being released,
or channel being forcibly released. The measurement point is B3,
Unit
Related Features
Times
version2)
Description

Measurement
Point
211
Unit
Related Features
Times
version3)
Description
212


Measurement
Point
Unit
Related Features
Times
ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
213
version3)
Description

due to channel activation failure during voice channel assignment
(speech version 3).
occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If channel activation fails due
Measurement
Point

channel as voice channel (speech version 3), but receives channel
message, T9103 being timeout, channel instance being released,
or channel being forcibly released. The measurement point is B3,
Unit
Related Features
Times
214
voice TCH/F assignment
success
Description

TCH/F as voice channel.
occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. For assignment from A-interface, after BSC receives the assignment success message, the
Measurement
Point
For assignment from A-interface, the counter accumulates when

BSC receives the assignment success message. The measurement
215
Unit
Related Features
Times
Description

as voice channel.
Measurement
Point
216
This counter counts when BSC receives assignment failure message, abnormal message, channel instance being released, channel instance being released forcibly, or timer timeout message.
The measurement point is B5, as shown in Figure 242.
Unit
Related Features
Times
data TCH/F seizure attempts
for assignment
Description

to be occupied during data channel assignment, including the number of occupation success (C901260070) and the number of occupation failure (C900060031).


simultaneously.

C900060030 and


217
Measurement
Point

channel is used as data channel), or BSC receives the internal message of waiting for resource successfully or waiting for resource
failed (C901260070 + C900060031). The measurement point is
Unit
Related Features
Times
ZGB-01-03-002 Data Traffic Channels
218
data TCH/F seizure failure
for assignment
Description
This counter counts the number of TCH/F channel occupation failure during data channel assignment.
Measurement
Point


does not change.

used as data channel) but fails to occupy the channel, or BSC fails
to wait for internal resource. The measurement point is B1, as
Unit
Related Features
Times
219
data TCH/F seizure attempts
for handover
Description

to be occupied during data channel handover, including the number


simultaneously.

Measurement
Point
220
C900060032 and



C1 as shown in Figure 246 and Figure 247, and D1 as shown in
Figure 248 and Figure 249.

INTERNAL)

221
Unit
Related Features
Times
222
for handover
Description
This counter counts the number of TCH/F channel occupation failure during data channel handover.
Measurement
Point


does not change.
as data channel) but fails to occupy the channel, or BSC fails to
Unit
Related Features
Times
223

TCH/F allocation success for
assignment
Description

successfully during data channel assignment.
Measurement
Point
as data channel. The measurement point is B3, as shown in Figure
252 and Figure 253.
224
Unit
Related Features
Times
data TCH/F allocation failure
due to channel activation
Description

due to channel activation failure during data channel assignment.
occupy TCH/F channel successfully, if connection succeeds, BSC
sends the CHL_ACT message to BTS to activate this TCH/F. If channel activation fails due to receiving channel activation failure message, incorrect channel activation response message, T9103 being
timeout, channel instance being released or channel being forcibly
released, this counter accumulates.
Measurement
Point

channel as data channel, but receives channel activation failure
message, incorrect channel activation response message, T9103
being timeout, channel instance being released, or channel being
forcibly released. The measurement point is B3, as shown in
Figure 254.
225
Unit
Related Features
Times

TCH/F assignment success
Description

TCH/F as data channel.
message to BTS to activate this TCH/F. For assignment from A-interface, after BSC receives the assignment success message, the
Measurement
Point
226

Unit
Related Features
Times

TCH/F assignment failure
Description

as data channel.
227

Measurement
Point
Unit
Related Features
Times
signaling TCH/H seizure
Description
This counter counts the number of TCH/H channel being attempted

to be occupied during signaling channel assignment, including the
228


C900060038 and
Measurement
Point
For other cases, C900060038 and C900060039 accumulate simultaneously.

(due to assignment and the channel is used as signaling channel)
Unit
Related Features
Times
ZGO-01-01-001 Half Rate
ZGO-03-02-005 Dynamic Half Rate Allocation
Description
This counter counts the number of TCH/H channel occupation failure during signaling channel assignment.
Measurement
Point

does not change.

229
fails to wait for internal resource. The measurement point is A1,

FIGURE 259 IMMEDIATE ASSIGNMENT OCCUPATION FAILURE FLOW 1
Unit
Related Features
Times
Description

to be occupied during signaling channel handover, including the


simultaneously.

230
C900060040 and


Measurement
Point

channel is used as signaling channel), or BSC receives the internal message of waiting for resource successfully or waiting for resource failed (C901270005 + C900060041). The measurement
INTERNAL)

231
Unit
Related Features
Times
232
Description
This counter counts the number of TCH/H channel occupation failures during signaling channel handover.
Measurement
Point


does not change.
BSC requests for channel (due to handover and the channel is

fails to wait for internal resource. The measurement point is C1
as shown in Figure 264 and D1 as shown in Figure 265.
Unit
Related Features
Times
233
C900060042 Number
of voice TCH/H seizure
Description

to be occupied during voice channel assignment, including the


simultaneously.

Measurement
Point
234
C900060042 and



Unit
Related Features
Times
235
voice TCH/H seizure failure
for assignment
Description
This counter counts the number of TCH/H channel occupation failure during voice channel assignment.
Measurement
Point


does not change.

used as voice channel) but fails to occupy the channel, or BSC
fails to wait for internal resource. The measurement point is B1,
Unit
Related Features
Times
236
C900060044 Number
Description

to be occupied during voice channel handover, including the number of occupation success (C901270024) and the number of occupation failure (C900060045).


simultaneously.

Measurement
Point
C900060044 and



237

INTERNAL)

238
Unit
Related Features
Times
239
for handover
Description
This counter counts the number of TCH/H channel occupation failure during voice channel handover.
Measurement
Point
If allocation or occupation fails, this counter accumulates.


does not change.
as voice channel) but fails to occupy the channel, or BSC fails to
Unit
Related Features
Times
240

TCH/H seizure attempts for
assignment
Description

to be occupied during data channel assignment, including the number of occupation success (C901270070) and the number of occupation failure (C900060047).


simultaneously.

Measurement
Point
C900060046 and



241
Unit
Related Features
Times
242
data TCH/H seizure failure
for assignment
Description
This counter counts the number of TCH/H channel occupation failure during data channel assignment.
Measurement
Point


does not change.

used as data channel) but fails to occupy the channel, or BSC fails
to wait for internal resource. The measurement point is B1, as
Unit
Related Features
Times
243

TCH/H seizure attempts for
handover
Description

to be occupied during data channel handover, including the number


simultaneously.

Measurement
Point
244
C900060048 and



C1 as shown in Figure 278 and Figure 279, and D1 as shown in

INTERNAL)

245
Unit
Related Features
Times
246
for handover
Description
This counter counts the number of TCH/H channel occupation failure during data channel handover.
Measurement
Point


does not change.
as data channel) but fails to occupy the channel, or BSC fails to
Unit
Related Features
Times
247
SAPI3 link establishment
requests on SDCCH
(MO-SM)
248
Description
This counter counts the number of short message link establishments of mobile originating call on SDCCH. On SDCCH, BSC receives the EST_IND message sent by BTS. If the layer-3 information in this message is SAPI = 3, this counter increments.
Usage
This counter is used to find out the frequency of SAPI 3 link establishment on SDCCH.
Measurement
Point
This counter counts when BSC receives the EST_IND message

(SAPI = 3) from BTS. The measurement point is B1, as shown
in Figure 284.
FIGURE 284 IDLE-STATE MO SHORT MESSAGE FLOW
Unit
Related Features
Times
ZGB-01-03-003 Short Message Service (SMS)
249
requests on SDCCH
(MT-SM)
250
Description
This counter counts the number of short message link establishments of mobile terminating call on SDCCH. On SDCCH, if BSC
receives the DTAP_IND message (SAPI = 3) sent by MSC and the
short message link between BSC and MS is not established, BSC
initiates the link establishment flow, this counter increments.
Usage
This counter is used to find out the frequency of SAPI 3 link establishment request on SDCCH.
Measurement
Point
This counter counts when BSC sends the EST_REQ message (SAPI
= 3) to BTS and the short message link is not established between
BSC and MS. The measurement point is D1, as shown in Figure
285.
FIGURE 285 IDLE-STATE MT SHORT MESSAGE FLOW
Unit
Related Features
Times
SDCCH drops due to
handover failure
Description
This counter counts the number of call drops due to handover failure on SDCCH. Call drop occurs after MS requests for SDCCH successfully. If the problem is due to handover failure, this counter
increments.
Presently, reasons for handover failure include T3107 timeout,
T3103 timeout and external handover timer timeout under the
status of ASSIGNING.
251
T3107 indicates the duration from sending the intra-cell handover

command ASSIGN_CMD to receiving the assignment completion
message ASSIGN_COM. T3103 indicates the duration from sending the inter-cell handover command HOINTER_CMD to receiving
the assignment completion message HOINTER_COM. The external
handover timer indicates the duration from sending the inter-cell
external handover command to receiving the handover completion
message.
Usage
This counter is used to find out the frequency of call drop due to
handover failure on SDCCH.
Measurement
Point
SDCCH is activated after BSC initiates the handover flow. After

that:
If RANCS is in the status of RADIO_APPLY and sends the intracell handover command, then T3107 is started. If RANCS is in
the status of ASSIGN and T3107 is timeout, then the counter
increments. The measurement point is A, as shown in Figure
286.
FIGURE 286 CALL DROP
HANDOVER
252
DUE TO
T3107 TIMEOUT DURING INTRA-CELL
If RANCS is in the status of RADIO_APPLY and sends the intercell handover command, then T3103 is started. If RANCS is in
287.

HANDOVER
Unit
Related Features
DUE TO
T3103 TIMEOUT DURING INTER-CELL
If RANCS is in the status of RADIO_APPLY and sends the external handover command, then the external handover timer is
started. If RANCS is in the status of ASSIGN and the external
handover timer is timeout, then the counter increments.
Times
SDCCH drops
Description
This counter counts the number of call drops on SDCCH channel

due to radio link failure, LAPD link break, or handover failure. Call
drop occurs after MS requests for TCH/H channel successfully. The
counter increments if call drop is due to the above causes.
Usage
This counter is used to find out the frequency of call drop on SDCCH
channel due to radio link failure, LAPD link break, or handover
failure.
Measurement
Point
This counter increments when call drop occurs on SDCCH channel

due to radio link failure, LAPD link failure, or handover failure.
Unit
Related Features
Times
253
TCH/F drops
Description
This counter counts the number of call drops on TCH/F channel

Usage
This counter is used to find out the frequency of call drop on TCH/F
failure.
Measurement
Point
The counter increments when call drop occurs on TCH/F channel

Unit
Related Features
Times
TCH/H drops
Description
This counter counts the number of call drops on TCH/H channel

Usage
This counter is used to find out the frequency of call drop on TCH/H
failure.
Measurement
Point
The counter increments when call drop occurs on TCH/H channel

Unit
Related Features
Times
254
C900060056 Average
number of idle TCH/F with
interference band 1
Description
This counter counts the number of idle TCH/Fs with interference

band 1 in the carrier.
Usage
This counter is used to find out the number of idle TCH/Fs with
interference band 1.
Measurement
Point
Unit
Related Features
This counter counts when querying the database periodically.

Times
ZGO-03-02-001 Idle Channel Measurement
C900060057 Average
interference band 2
Description

Usage
Measurement
Point
Unit
Related Features

Times
C900060058 Average
interference band 3
Description

255
Usage
Measurement
Point
Unit
Related Features
Times
C900060059 Average
interference band 4
Description

Usage
Measurement
Point
Unit
Related Features

Times
C900060060 Average
interference band 5
Description

Usage
Measurement
Point
Unit
Related Features

Times
256
C900060061 Average
number of idle TCH/H with
interference band 1
Description
This counter counts the number of idle TCH/Hs with interference

Usage
This counter is used to find out the number of idle TCH/Hs with
Measurement
Point
Unit
Related Features

Times
C900060062 Average
interference band 2
Description

Usage
Measurement
Point
Unit
Related Features

Times
257
C900060063 Average
interference band 3
Description

Usage
Measurement
Point
Unit
Related Features

Times
C900060064 Average
interference band 4
Description

Usage
Measurement
Point
Unit
Related Features

Times
258
C900060065 Average
interference band 5
Description

Usage
Measurement
Point
Unit
Related Features

Times
samples with UL RQ = 0
Description
This counter counts the number of samples with Uplink (UL) Receiving Quality (RQ) = 0. After BSC receives the measurement
report or preprocessing measurement report, if the UL RQ = 0,
the counter increments.
Usage
This counter is used to count the number of samples with UL RQ

= 0.
Measurement
Point
The counter increments if UL RQ = 0 in the measurement report

or preprocessing measurement report that BSC receives.
Unit
Times
Description
This counter counts the number of samples with UL RQ = 1. After

BSC receives the measurement report or preprocessing measurement report, if the UL RQ = 1, the counter increments.
Usage

= 1.
Measurement
Point

259
Unit
Times
Description

Usage

= 2.
Measurement
Point

Unit
Times
Description

Usage

= 3.
Measurement
Point

Unit
Times
Description

Usage

= 4.
Measurement
Point

Unit
260
Times
Description

Usage

= 5.
Measurement
Point

Unit
Times
Description

Usage

= 6.
Measurement
Point

Unit
Times
Description

Usage

= 7.
Measurement
Point

Unit
Times
261
samples with DL RQ = 0
Description
This counter counts the number of samples with Downlink (DL) RQ

= 0. After BSC receives the measurement report or preprocessing
measurement report, if the DL RQ = 0, the counter increments.
Usage
This counter is used to count the number of samples with DL RQ

= 0.
Measurement
Point
The counter increments if DL RQ = 0 in the measurement report

Unit
Times
Description
This counter counts the number of samples with DL RQ = 1. After

BSC receives the measurement report or preprocessing measurement report, if the DL RQ = 1, the counter increments.
Usage

= 1.
Measurement
Point

Unit
Times
Description

Usage

= 2.
Measurement
Point

Unit
262
Times
Description

Usage

= 3.
Measurement
Point

Unit
Times
Description

Usage

= 4.
Measurement
Point

Unit
Times
Description

Usage

= 5.
Measurement
Point

Unit
Times
263
Description

Usage

= 6.
Measurement
Point

Unit
Times
Description

Usage

= 7.
Measurement
Point

Unit
Times
TCH/F handover attempts
due to UL strength
264
Description
This counter counts the number of handover attempts due to UL

receiving strength too low on TCH/F channel.
Usage
This counter is used to find out the frequency of handover due to

UL receiving strength on TCH/F channel. If the counter's value is
too large, it indicates poor UL level on TCH/F channel.
Measurement
Point
BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the
handover is due to UL strength, this counter increments. The measurement point is A, as shown in Figure 288.
FIGURE 288 HANDOVER DECISION
Unit
Related Features
Times
ZGB-02-02-002 Basic Handover Decision Criteria
due to DL strength
Description
This counter counts the number of times of handover attempts due

to DL receiving strength too low on TCH/F channel.
Usage

DL receiving strength on TCH/F channel. If the counter's value is
too large, it indicates poor DL level on TCH/F channel.
Measurement
Point
handover is due to DL strength, this counter increments. The measurement point is A, as shown in Figure 289.
Unit
Related Features
Times
265
due to UL quality
Description

quality too poor on TCH/F channel.
Usage

UL quality on TCH/F channel. If the counter's value is too large, it
indicates poor UL quality on TCH/F channel.
Measurement
Point
handover is due to UL quality, this counter increments. The measurement point is A, as shown in Figure 290.
Unit
Related Features
Times
due to DL quality
266
Description
This counter counts the number of handover attempts due to DL

quality too poor on TCH/F channel.
Usage

DL quality on TCH/F channel. If the counter's value is too large, it
indicates poor DL quality on TCH/F channel.
Measurement
Point
handover is due to DL quality, this counter increments. The measurement point is A, as shown in Figure 291.
Unit
Related Features
Times
due to UL interference
Description

interference too large on TCH/F channel.
Usage

UL interference on TCH/F channel. If the counter's value is too
large, it indicates large UL interference on TCH/F channel.
Measurement
Point
handover is due to UL interference, this counter increments. The
measurement point is A, as shown in Figure 292.
Unit
Related Features
Times
267
due to DL interference
Description

interference too large on TCH/F channel.
Usage

DL interference on TCH/F channel. If the counter's value is too
large, it indicates large DL interference on TCH/F channel.
Measurement
Point
handover is due to DL interference, this counter increments. The
Unit
Related Features
Times
due to good C/I
268
Description
This counter counts the number of MS handover attempts due to

too large C/I ratio on TCH/F channel. The handover only occurs
during sub-cell configuration; when C/I algorithm is adopted, MS
performs handover from external circle to internal circle.
Usage
This counter is used to find out the frequency of MS handover due

to too large C/I ratio on TCH/F channel. If the counters value is
too large, it indicates that, after MS accesses the external circle,
MS performs handover to the internal circle many times due to
good C/I ratio and the internal circle absorbs the traffic.
Measurement
Point
handover is due to too large C/I ratio, this counter increments.

Unit
Related Features
Times
due to bad C/I
Description

too low C/I ratio on TCH/F channel. The handover only occurs
during sub-cell configuration; when C/I algorithm is adopted, MS
performs handover from internal circle to external circle.
Usage

to too low C/I ratio on TCH/F channel. If the counters value is too
large, it indicates that, when MS calls within the internal circle,
MS performs handover to the external circle many times due to
poor C/I ratio. Interference within the internal circle is big, and
C/I ratio of the internal circle can be improved by adjusting the
carrier power.
Measurement
Point
handover is due to too low C/I ratio, this counter increments. The
Unit
Related Features
Times
269
due to PBGT
Description

PBGT value on TCH/F channel. If PBGT value is larger than zero, it
indicates the adjacent cell has better radio environment than the
current cell. If the number of times that PBGT value is larger than
zero reaches the threshold, PBGT handover occurs.
Usage

to PBGT value on TCH/F channel. If the counter's value is too
large, it indicates that signal on TCH/F channel within the current
cell is poorer than that in the adjacent cell.
Measurement
Point
handover is due to PBGT value, this counter increments. The measurement point is A, as shown in Figure 296.
Unit
Related Features
Times
due to large TA
Description
270

too large TA on TCH/F channel. Increasing TA indicates that MS is
moving away from the current cell. When the distance reaches a
certain value, handover will occur due to too large TA.
Usage

to too large TA on TCH/F channel. The counter's value reflects the
mobility of subscribers in the current cell to a certain extent.
Measurement
Point
handover is due to too large TA, this counter increments. The
Unit
Related Features
Times
due to other reasons
Description
This counter counts the number of handover attempts due to any

other reason beyond the handover reasons mentioned previously.
Usage

any other reason.
Measurement
Point
handover is due to any other reason beyond the handover reasons
mentioned previously, this counter increments. The measurement
271
Unit
Related Features
Times
BSC-controlled inter-cell
outgoing handover
Description
This counter counts the number of intra-BSC inter-cell handoverout executions. The execution here means the radio resource of
target cell has been successfully requested, and system returns
the message of radio resource available.
Usage
This counter is used to find out the frequency of intra-BSC inter-cell

outgoing handover execution. It is one of the parameters that
evaluate radio environment, and it reflects the handover situation.
Measurement
Point
During the handover process, if the target cell requests for channel successfully, it sends the message of radio resource available
back to the source cell. The source cell performs judgment after
receiving the message. If the request is due to intra-BSC inter-cell
handover, this counter increments. The measurement point is A,
FIGURE 299 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
EXECUTION
Unit
Related Features
Times
272
outgoing handover success
Description
This counter counts the number of successful intra-BSC inter-cell

outgoing handovers.
Usage
This counter is used to find out the frequency of successful intraBSC inter-cell outgoing handover. It is one of the parameters that
evaluate the handover situation.
Measurement
Point
During the handover process, when the source cell receives the
handover completion message from the target cell, it indicates that
MS has accessed the target channel and handover succeeds. In
this case, this counter increments. The measurement point is A,
FIGURE 300 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER SUCCESS
Unit
Related Features
Times
MSC-controlled outgoing
handover
Description
This counter counts the number of MSC-controlled inter-BSC outgoing handover executions.
273
Usage
This counter is used to find out the frequency of MSC-controlled

inter-BSC outgoing handover execution, and it reflects the handover situation.
Measurement
Point
BSC performs handover decision after receiving MS measurement

report. If the handover decision indicates inter-cell handover and
the currently attempted cell is a cell under another BSC, the source
BSC sends the handover request message A_HO_RQD to MSC to
trigger inter-BSC handover. If the source BSC receives the handover command returned from MSC, the counter increments. The
FIGURE 301 MSC-CONTROLLED OUTGOING HANDOVER EXECUTION
Unit
Related Features
Times
handover success
274
Description
This counter counts the number of successful MSC-controlled inter-BSC outgoing handovers.
Usage
This counter is used to find out the frequency of successful MSCcontrolled inter-BSC outgoing handover, and it reflects the handover situation.
Measurement
Point
BSC performs handover decision after receiving MS measurement

report. If the handover decision indicates inter-cell handover and
the currently attempted cell is a cell under another BSC, the source
BSC sends the handover request message A_HO_RQD to MSC to
trigger inter-BSC handover. If MS successfully accesses the target
cell, the source cell receives the release command issued by MSC.
In this case, this counter increments. The measurement point is
FIGURE 302 MSC-CONTROLLED OUTGOING HANDOVER SUCCESS
Unit
Related Features
Times
incoming handover
Description
This counter counts the number of BSC-controlled inter-cell incoming handover executions.
Usage
This counter is used to find out the frequency of BSC-controlled

inter-cell incoming handover execution. It is one of the parameters that evaluate radio environment, and it reflects the handover
situation.
Measurement
Point
If channel activation succeeds in the target cell within BSC and the
request is due to inter-cell handover, the counter increments. The
FIGURE 303 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER
EXECUTION
Unit
Related Features
Times
275
incoming handover success
Description
This counter counts the number of successful BSC-controlled intercell incoming handovers.
Usage
This counter shows the frequency of successful BSC-controlled inter-cell incoming handover, and it reflects the handover situation.
Measurement
Point
When the target cell within BSC receives the handover completion
message, if the request is due to BSC-controlled inter-cell handover, the counter increments. The measurement point is A, as
FIGURE 304 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Unit
Related Features
Times
MSC-controlled incoming
handover
276
Description
This counter counts the number of MSC-controlled inter-BSC incoming handover executions.
Usage

inter-BSC incoming handover executions. It is one of the parameters that evaluate radio environment, and it reflects the handover
situation.
Measurement
Point
After the target cell receives the handover request message issued
by MSC, the counter increments if the channel is allocated and
activated successfully. The measurement point is A, as shown in
Figure 305.
FIGURE 305 MSC-CONTROLLED INCOMING HANDOVER EXECUTION
Unit
Related Features
Times
handover due to forced
release
Description
During MSC-controlled inter-BSC incoming handover process, the

counter counts the number of forced release executions due to no
available radio resource in the target cell.
Usage
This counter is used to find out the frequency of forced release

executions during MSC-controlled inter-BSC incoming handover
process. It reflects the handover situation.
Measurement
Point
The target cell receives the radio channel request message. If

the request is due to MSC-controlled inter-BSC incoming handover
and the target cell has no available radio channels, forced release
is attempted. If the target cell receives the message of resource
available returned by the forced release instance, the counter increments. The measurement point is A, as shown in Figure 306.
277
FIGURE 306 FORCED RELEASE EXECUTION
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
handover due to queue
Description

counter counts the number of queuing executions due to no available radio resource in the target cell.
Usage
This counter is used to find out the frequency of queuing executions during MSC-controlled inter-BSC incoming handover process,
and it reflects the handover situation.
Measurement
Point
The target cell receives the radio channel request message. If the
request is due to MSC-controlled inter-BSC incoming handover and
the target cell has no available radio channels, the target instance
is added to the waiting queue. When the target cell receives the
message of resource available, the counter increments. The measurement point is A, as shown in Figure 307.
FIGURE 307 QUEUING EXECUTION
278
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
handover success
Description
This counter counts the number of successful MSC-controlled inter-BSC incoming handovers.
Usage
This counter is used to find out the frequency of successful MSCcontrolled inter-BSC incoming handover, and it reflects the handover situation.
Measurement
Point
When the target cell receives the handover completion message, if

the request is due to MSC-controlled inter-BSC incoming handover,
Figure 308.
FIGURE 308 MSC-CONTROLLED INCOMING HANDOVER SUCCESS
Unit
Related Features
Times
279
incoming handover from
undefined layer (GSM900)
to current layer(GSM1800)
Description
This counter counts the number of incoming handover executions from the undefined layer cell (GSM900) to the target cell
(GSM1800) during BSC-controlled inter-cell handover.
Usage
This counter is used to find out the frequency of incoming handover

executions from the undefined layer cell (GSM900) to target cell
(GSM1800). It reflects the handover situation.
Measurement
Point
When the target cell (GSM1800) within BSC receives the channel
activation response message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM900) is the
undefined layer cell, the counter increments. The measurement
EXECUTION
Unit
Related Features
Times
ZGO-05-02-010 Multi-band Networking
ZGO-05-02-008 Multi-layer Cell Structure
280
C900060104 Number
of incoming handover
success from undefined
layer(GSM900) to current
layer (GSM1800)
Description
This counter counts the number of successful incoming handover from the undefined layer cell (GSM900) to the target cell
Usage
This counter is used to find out the frequency of successful incoming handover from the undefined layer cell (GSM900) to the target
cell (GSM1800). It reflects the handover situation.
Measurement
Point
When the target cell (GSM1800) within BSC receives the handover
completion message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM900) is the undefined
layer cell, the counter increments. The measurement point is A,
Unit
Related Features
Times
281
to current layer (GSM900)
Description
This counter counts the number of incoming handover executions from the undefined layer cell (GSM1800) to the target cell
Usage

executions from the undefined layer cell (GSM1800) to target cell
Measurement
Point
When the target cell (GSM900) within BSC receives the channel
activation response message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is the
undefined layer cell, the counter increments. The measurement
EXECUTION
Unit
Related Features
Times
282
C900060106 Number
layer(GSM1800) to current
layer(GSM900)
Description
This counter counts the number of successful incoming handover from the undefined layer cell (GSM1800) to the target cell
Usage
This counter is used to find out the frequency of successful incoming handover from the undefined layer cell (GSM1800) to the
target cell (GSM900). It reflects the handover situation.
Measurement
Point
When the target cell (GSM900) within BSC receives the handover
completion message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is the undefined
layer cell, the counter increments. The measurement point is A,
Unit
Related Features
Times
283
the same layer GSM900 to
GSM1800
Description
This counter counts the number of incoming handover executions

from the cell (GSM900) to the target cell (GSM1800) in the same
layer during BSC-controlled inter-cell handover.
Usage

executions from the cell (GSM900) to the target cell (GSM1800)
in the same layer. It reflects the handover situation.
Measurement
Point
When the target cell (GSM1800) receives the channel activation

response message, if the request is due to BSC-controlled intercell handover and the source cell (GSM900) is in the same layer,
Figure 313.
EXECUTION
Unit
Related Features
Times
from the same layer GSM900
to GSM1800
Description
284
This counter counts the number of successful incoming handovers

Usage
This counter is used to find out the frequency of successful incoming handover from the cell (GSM900) to the target cell (GSM1800)
Measurement
Point
When the target cell (GSM1800) receives the handover completion message, if the request is due to BSC-controlled inter-cell
handover and the source cell (GSM900) is in the same layer, the
Figure 314.
Unit
Related Features
Times
GSM900 to GSM1800 from
the upper layer
Description

from the upper layer cell (GSM900) to the target cell (GSM1800)
during BSC-controlled inter-cell handover.
Usage

executions from the upper layer cell (GSM900) to the target cell
Measurement
Point

response message, if the request is due to BSC-controlled intercell handover and the source cell (GSM900) is in the upper layer,
Figure 315.
285

EXECUTION
Unit
Related Features
Times
from GSM900 to GSM1800
in the upper layer
Description

Usage
This counter is used to find out the frequency of successful incoming handover from the upper layer cell (GSM900) to the target cell
Measurement
Point
handover and the source cell (GSM900) is in the upper layer, the
Figure 316.
286
Unit
Related Features
Times
GSM900 to GSM1800 in the
lower layer
Description

from the lower layer cell (GSM900) to the target cell (GSM1800)
Usage

executions from the lower layer cell (GSM900) to the target cell
Measurement
Point

response message, if the request is due to BSC-controlled intercell handover and the source cell (GSM900) is in the lower layer,
Figure 317.
EXECUTION
Unit
Related Features
Times
287
in the lower layer
Description

Usage
This counter is used to find out the frequency of successful incoming handover from the lower layer cell (GSM900) to the target cell
Measurement
Point
handover and the source cell (GSM900) is in the lower layer, the
Figure 318.
Unit
Related Features
Times
288
the same layer
Description

Usage

executions from the cell (GSM1800) to the target cell (GSM900)
Measurement
Point
When the target cell (GSM900) receives the channel activation response message, if the request is due to BSC-controlled inter-cell
handover and the source cell (GSM1800) is in the same layer, the
Figure 319.
EXECUTION
Unit
Related Features
Times
289
from the same layer
Description

Usage
This counter is used to find out the frequency of successful incoming handover from the cell (GSM1800) to the target cell (GSM900)
Measurement
Point
When the target cell (GSM900) receives the handover completion

message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is in the same layer, the
Figure 320.
Unit
Related Features
Times
290
the upper layer
Description

Usage

executions from the upper layer cell (GSM1800) to the target cell
Measurement
Point
handover and the source cell (GSM1800) is in the upper layer, the
Figure 321.
EXECUTION
Unit
Related Features
Times
291
from the upper layer
Description

Usage
This counter is used to find out the frequency of successful incoming handover from the upper layer cell (GSM1800) to the target
Measurement
Point

message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is in the upper layer, the
Figure 322.
Unit
Related Features
Times
292
the lower layer
Description

Usage

executions from the lower layer cell (GSM1800) to the target cell
Measurement
Point
handover and the source cell (GSM1800) is in the lower layer, the
Figure 323.
EXECUTION
Unit
Related Features
Times
293
from the lower layer
Description

Usage
This counter is used to find out the frequency of successful incoming handover from the lower layer cell (GSM1800) to the target
Measurement
Point

message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is in the lower layer, the
Figure 324.
Unit
Related Features
Times
Intra-cell handover
Description
294
This counter counts the number of intra-cell handover executions

which is initiated by MS in the source cell. Here, the execution
means that radio resource is requested successfully and the message of resource available is returned.
Usage
This counter is used to find out the frequency of MS-initiated intracell handover execution. It is one of the parameters that evaluate
radio environment. It reflects the handover situation.
Measurement
Point
During the handover process, if the target channel request succeeds, the message of radio resource available is returned to BSC.
BSC then performs judgment after receiving the message. If the
request is due to intra-cell handover, this counter increments. The
FIGURE 325 INTRA-CELL HANDOVER EXECUTION
Unit
Related Features
Times
Intra-cell handover success
Description
This counter counts the number of successful intra-cell handovers

which are initiated by MS in the source cell.
Usage
This counter is used to find out the frequency of successful intracell handover. It is one of the parameters that evaluate handover.
Measurement
Point
During the intra-cell handover process, if the source instance receives the handover completion message returned by the target
instance, it indicates MS accesses the target channel and handover
succeeds. In this case, this counter increments. The measurement
FIGURE 326 INTRA-CELL HANDOVER SUCCESS
Unit
Related Features
Times
295
C900060121 Maximum
number of busy TCH/H
Description
This counter counts the maximum number of occupied TCH/Hs in

a cell during a measurement period.
The system records the TCH/Hs occupied in the cell. If a TCH/H is
successfully occupied, the number of occupied TCH/Hs increases
by 1; if a TCH/H is released, the number of occupied TCH/Hs decreases by 1. After a TCH/H is occupied, before a TCH/H is released, or when the system reports the periodical measurement
data, if this counter's value is less than the number of actual occupied TCH/Hs, this counter's value will be replaced by the actual
number of occupied TCH/Hs.
In consideration of the TCH/H channel occupation situation in the
last measurement period, the number of occupied TCH/Hs is updated before the release of a TCH/H.
Usage
Measurement
Point
This counter is used to find out the maximum number of occupied

TCH/Hs in a cell during a measurement period. The counter's value
reflects the instantaneous occupation and the heaviest traffic of
TCH/H.
The counter counts at the following three time points:
After the TCH/H is occupied successfully, if the maximum number of busy TCH/Hs exceeds the counter's recorded value;
Before the TCH/H is released, if the maximum number of busy

TCH/Hs exceeds the counter's recorded value;
When the system reports the periodical measurement data, if

the maximum number of busy TCH/Hs exceeds the counter's
recorded value.

FIGURE 327 REPORTING MEASUREMENT DATA
Unit
Related Features
Times
296
C900060122 Average
number of available SDCCH
Description
This counter counts the number of SDCCHs which can be assigned

normally, including idle SDCCH and occupied SDCCH.
Usage
This counter is used to find out the number of available SDCCHs

in the current cell.
Measurement
Point
Query the database when periodic measurement data is reported

to get the value of the counter. The measurement point is A, as
Unit
Related Features
Times
C900060123 Average
number of unavailable
SDCCH
Description
This counter counts the number of SDCCHs that can not be assigned normally, including those SDCCHs blocked due to various
reasons.
Usage
This counter is used to find out the number of unavailable SDCCHs

to facilitate troubleshooting.
Measurement
Point

297
Unit
Related Features
Times
C900060124 SDCCH busy

time
Description
This counter counts the busy time of SDCCHs, which reflects the
traffic volume of SDCCH.
Usage
This counter is used to find out the busy level and the average
occupation time of the signaling channel. It can be used as a reference for judging whether to increase the number of SDCCHs.
Measurement
Point
When an SDCCH is acquired successfully, this counter calculates time and accumulates.
When an SDCCH is released, this counter calculates time and

accumulates.
When the system reports the periodical measurement data,

this counter calculates time and accumulates.

The measurement formula is as follows:
298
Measurement value = (Current time Last measurement time

point) Number of MSs that are occupying the channels
Unit
The reported measurement value is accumulated by each measurement value. After each accumulation, the last measurement time point is updated to the current time. If an SDCCH
is acquired successfully, Number of MSs that are occupying
the channels increases by 1; if an SDCCH is released, Number of MSs that are occupying the channels decreases by
1.
Second
C900060125 Average
number of available radio
channel
Description
This counter counts the number of FR radio channel which can

be assigned normally. The radio channels that can be assigned
normally include idle radio channels and occupied radio channels.
Usage
This counter is used to find out the number of available FR radio

channels in the current cell. It helps understand the current resource usage situation of the cell.
Measurement
Point

Unit
Related Features
Times
ZGO-04-04-002 Intelligent TRX Shutdown
299
C900060126 Average
number of unavailable radio
channel
Description
This counter counts the number of radio channels that can not be
assigned normally, including those radio channels blocked due to
various reasons.
Usage
This counter is used to find out the number of unavailable radio

channels in the current cell. It helps understand the current resource usage situation of the cell.
Measurement
Point

Unit
Related Features
Times
C900060127 TCH/H busy

time
Description
This counter counts the busy time of TCH/Hs, which reflects the
traffic volume of TCH/H.
Usage
occupation time of TCH/H. It can be used as a reference for judging
whether to increase the number of TCH/Hs.
Measurement
Point
300
When a TCH/H is acquired successfully, this counter calculates

time and accumulates.
When a TCH/H is released, this counter calculates time and

accumulates.


Unit
Related Features

The reported measurement value is accumulated by each measurement value. After each accumulation, the last measurement time point is updated to the current time. If a TCH/H is
acquired successfully, Number of MSs that are occupying
the channels increases by 1; if a TCH/H is released, Number
of MSs that are occupying the channels decreases by 1.
Second
C900060128 Maximum
number of busy TCH/F
Description
This counter counts the maximum number of occupied TCH/Fs in

a cell during a measurement period.
The system records the TCH/Fs occupied in the cell. If a TCH/F is
successfully occupied, the number of occupied TCH/Fs increases
by 1; if a TCH/F is released, the number of occupied TCH/Hs decreases by 1. After a TCH/F is occupied, before a TCH/F is released, or when the system reports the periodical measurement
data, if this counter's value is less than the number of actual occupied TCH/Fs, this counter's value will be replaced by the actual
number of occupied TCH/Fs.
In consideration of the TCH/F channel occupation situation in the
last measurement period, the number of occupied TCH/Fs is updated before the release of a TCH/F.
Usage
This counter is used to find out the maximum number of occupied

TCH/Fs in a cell during a measurement period. The counter's value
reflects the instantaneous occupation and the heaviest traffic of
TCH/F.
301
Measurement
Point
After the TCH/F is occupied successfully, if the maximum number of busy TCH/Fs exceeds the counters recorded value;
Before the TCH/F is released, if the maximum number of busy

TCH/Hs exceeds the counters recorded value;
When the system reports the periodical measurement data, if

the maximum number of busy TCH/Fs exceeds the counter's
recorded value.

Unit
Related Features
Times
C900060129 TCH/F busy

time
Description
This counter counts the busy time of TCH/Fs, which reflects the
traffic volume of TCH/F.
Usage
occupation time of TCH/F. It can be used as a reference for judging
whether to increase the number of TCH/Fs.
Measurement
Point
When a TCH/F is acquired successfully, this counter calculates

time and accumulates.
When a TCH/F is released, this counter calculates time and

accumulates.

302
Unit
Related Features

The reported measurement value is accumulated by each measurement value. After each accumulation, the last measurement time point is updated to the current time. If a TCH/F is
acquired successfully, Number of MSs that are occupying
the channels increases by 1; if a TCH/F is released, Number
of MSs that are occupying the channels decreases by 1.
Second
healthy TRXs
Description
This counter counts the number of the TRXs that can be used normally.
Usage
This counter is used to find out the number of available TRXs and
resource usage in the current cell to facilitate troubleshooting.
Measurement
Point

303
Unit
Times
C900060131 Number of CM
service requests of MOC
Description
This counter counts the number of accesses due to CM SERVICE

REQ of MOC. After BSC receives the EST_IND message, if the access cause in the layer-3 information in this message is CM SERVICE REQ, this counter increments.
Usage
This counter is used to find out the frequency of the access due to
CM SERVICE REQ of MOC.
Measurement
Point

Unit
304
Times
success on SDCCH
(MT-SM)
Description
This counter counts the number of successful short message link

establishment of mobile terminating call on SDCCH. On SDCCH,
if BSC receives the EST_CONF message sent by BTS after BSC
initiates the short message link establishment flow, it indicates
this link establishment succeeds, and the counter increments.
Usage
This counter is used to find out the frequency of successful SAPI 3

link establishments on SDCCH.
Measurement
Point
This counter counts when BSC receives the EST_CONF message

(SAPI = 3) from BTS. The measurement point is D2, as shown in
Figure 338.
FIGURE 338 IDLE-STATE MT SHORT MESSAGE FLOW
305
Unit
Related Features
Times
available defined SDCCH
Description
iBSC supports dynamic conversion of SDCCH and TCH. This

counter counts the number of available SDCCH configured by
OMCR in the current cell.
Usage
This counter is used to find out the number of available SDCCH in

the current cell to facilitate eliminating fault in the cell.
Measurement
Point

Unit
Related Features
Times
available defined TCH/F
306
Description
iBSC supports the function of full dynamic radio channel. This

counter counts the number of available TCH/F configured by OMCR
in the current cell.
Usage
This counter is used to find out the number of available TCH/F in

the current cell to facilitate eliminating fault in the cell.
Measurement
Point

Unit
Related Features
Times
signaling TCH/H assignment
failure
Description
This counter counts the number of failing to assign TCH/H channel

as a signaling channel.
Usage
After BSC responds to the channel request message to allocate and

occupy TCH/H successfully, BSC sends the CHL_ACT message to
BTS to activate this TCH/H. If BSC does not receive the MS access
notification within a certain time, this assignment fails.
Measurement
Point

incorrect EST_IND message or T3101 is timeout. The measurement point is A3, as shown in Figure 341.
307
Unit
Related Features
Times
MOC access attempts
308
Description
This counter counts the number of channel requests due to Mobile Originated Call (MOC). When MS sends the CHL_REQ message
through BTS to BSC to request for radio channel, if TA does not
exceed the cell range and the access cause is MOC, this counter
increments.
Usage
This counter is used to find out the frequency of channel requests

due to the access cause MOC.
Measurement
Point
This counter counts when MS requests for channel from BSC and
TA does not exceed the cell range. The measurement point is A1,
Unit
Times
wireless access due to
paging responses
Description
This counter counts the number of accesses due to paging responses. After BSC receives the EST_IND message, if the access
cause in the layer-3 information in this message is paging responses, this counter increments.
Usage
This counter is used to find out the frequency of the access due to
paging responses.
Measurement
Point

309
Unit
Related Features
Times
ZGB-02-01-001 Paging
to BTS connection failure
version1)
Description
This counter counts the number of failing to allocate TCH/F channel

due to BTS connection failure when assigning voice channel (using
speech version 1).
occupy TCH/F channel successfully, BSC sends the CMM connection request to BTS. If BTS connection fails due to receiving CMM
connection failure message, incorrect CMM connection response
message, or timer timeout, this counter accumulates.
Measurement
Point
310
BSC uses TCH/F for assignment, but the problem such as receiving
connection failure message, incorrect connection response message, or timer timeout occurs during CMM connection process. The
measurement point is B2, as shown in Figure 344.
FIGURE 344 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Unit
Related Features
Times
to BIU connection failure
version1)
Description

due to BIU connection failure when assigning voice channel (using
speech version 1).
occupy TCH/F channel successfully, BSC sends the BIU connection
request to BIPB. If BIU connection fails due to receiving BIU connection failure message, incorrect BIU connection response message, or timer timeout, this counter accumulates.
Measurement
Point
connection failure message, incorrect connection response message, or timer timeout occurs during BIU connection process. The
311
Unit
Related Features
Times
to TCU connection failure
version1)
Description

due to TCU connection failure when assigning voice channel (using
speech version 1).
occupy TCH/F channel successfully, BSC sends the TCU connection
request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.
Measurement
Point
312
connection failure message, incorrect connection response message, or timer timeout occurs during TCU connection process. The
Unit
Related Features
Times
version2)
Description

due to channel activation failure when assigning speech channel
(using speech version 2).
message to BTS to activate this TCH/F. If the channel activation
fails due to receiving channel activation failure message, incorrect channel activation response message, T9103 timeout, channel instance being released or channel being released forcibly, this
Measurement
Point
BSC activates TCH/F as voice channel (using speech version 2) for

assignment, but the problem such as receiving channel activation
T9103 timeout, channel instance being released, or channel being
forcibly released occurs. The measurement point is B3, as shown
in Figure 347.
313
Unit
Related Features
Times
version2)
Description

speech version 2).
Measurement
Point
314
Unit
Related Features
Times
version2)
Description

speech version 2).
Measurement
Point
315
Unit
Related Features
Times
version2)
Description

speech version 2).
Measurement
Point
Unit
Related Features
316
Times
version3)
Description

speech version 3).
Measurement
Point
Unit
Related Features
Times
317
version3)
Description

speech version 3).
Measurement
Point
Unit
Related Features
Times
318
version3)
Description

speech version 3).
Measurement
Point
Unit
Related Features
Times
319

to BTS connection failure for
assignment)
Description

due to BTS connection failure when assigning data channel.
message or timer timeout, this counter accumulates.
Measurement
Point
connection failure message, incorrect connection response message or timer timeout occurs during CMM connection process. The
Unit
Related Features
Times
due to BIU connection failure
for assignment
Description
320

due to BIU connection failure when assigning data channel.

request to BIPB. If BIU connection fails due to receiving BIU connection failure message, incorrect BIU connection response message or timer timeout, this counter accumulates.
Measurement
Point
BSC uses TCH/F for assignment, but receives connection failure

message, incorrect connection response message or timer timeout
during BIU connection process. The measurement point is B2, as
Unit
Related Features
Times

to TCU connection failure for
assignment
Description

due to TCU connection failure when assigning data channel.
request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message or timer timeout, this counter accumulates.
Measurement
Point
BSC uses TCH/F for assignment, but receiving connection failure

during TCU connection process. The measurement point is B2, as
321
Unit
Related Features
Times
voice TCH/H drops due to
handover failure
Description
This counter counts the number of call drops due to handover failure on TCH/H voice channel. Call drop occurs after MS requests
for TCH/H voice channel successfully. If the problem is due to handover failure, the counter increments.
Usage
handover failure on TCH/H voice channel.
Measurement
Point
TCH/H voice channel is activated after BSC initiates the handover

flow. After that:
322
357.

HANDOVER
358.
HANDOVER
DUE TO
DUE TO
handover timer is timeout, then the counter increments. The
323
Unit
Related Features
DUE TO
INTER-BSC HANDOVER FAILURE
Times
C900060152 Number of Abis

interface paging command
messages
Description
This counter counts the number of paging command messages

from A-interface. These messages are part of Abis interface messages sent from BSC.
Usage
This counter is used to find out the frequency of transmitting paging command messages at Abis interface. These messages are
from A-interface.
Measurement
Point
When BSC sends ABIS_INTER_PAGING_CMD message to BTS, this

Figure 360.
MESSAGES SENT TO BTS FROM BSC
Unit
Related Features
324
Times
OF
ABIS INTERFACE
Abis CS paging messages
Description
This counter counts the number of CS paging command messages

from Gb interface. These messages are part of Abis interface messages sent from BSC.
Usage
This counter is used to find out the frequency of transmitting CS

paging command messages at Abis interface. These messages are
from Gb interface.
Measurement
Point
When BSC sends ABIS_INTER_CSPAGING_CMD message to BTS,

in Figure 361.
Unit
Related Features
OF
ABIS INTERFACE
Times
Abis PS paging messages
Description
This counter counts the number of PS paging command messages

from Gb interface. These messages are part of Abis interface messages sent from BSC.
Usage
This counter is used to find out the frequency of transmitting PS

paging command messages at Abis interface. These messages are
from Gb interface.
Measurement
Point
When BSC sends ABIS_INTER_PSPAGING_CMD message to BTS,

in Figure 362.
325

Unit
Related Features
OF
ABIS INTERFACE
Times
available defined TCH/H
Description

counter counts the number of available TCH/H channel configured
by OMCR in the current cell.
Usage
This counter is used to find out the number of available TCH/H

channel in the current cell to eliminate the fault in the cell.
Measurement
Point

Unit
Related Features
Times
326
TCH/F allocation failure
failure for handover(speech
version1)
Description

due to channel activation failure during voice channel handover
and occupy TCH/F channel successfully, if the connection succeeds,
BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/F. If channel activation fails due to receiving channel
message, T9103 being timeout, channel instance being released
or channel being forcibly released, this counter accumulates.
Measurement
Point
BSC activates TCH/F channel as voice channel due to handover,

but receives channel activation failure message, incorrect channel activation response message, T9103 being timeout, channel
instance being released, or channel being forcibly released. The
measurement point is C3 as shown in Figure 364 and D3 as shown
in Figure 365.
327
Unit
Related Features
Times
handover (speech version1)
Description
This counter counts the number of failing to allocate TCH/F channel due to BTS connection failure during voice channel handover
Measurement
Point
328
BSC uses TCH/F channel for handover, but receives connection

failure message, incorrect connection response message, or timer
timeout during CMM connection process. The measurement point
is C2 as shown in Figure 366 and D2 as shown in Figure 367.

Unit
Related Features
Times
to BIU connection failure for
Description

due to BIU connection failure during voice channel handover (using
speech version 1).
329
Measurement
Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect connection response message, or timer timeout
during BIU connection process. The measurement point is C2 as
shown in Figure 368 and D2 as shown in Figure 369.
Unit
Related Features
Times
Description
This counter counts the number of failing to allocate TCH/F channel due to TCU connection failure during voice channel handover
330
Measurement
Point
during TCU connection process. The measurement point is C2 as
Unit
Related Features
Times
331
failure for handover(speech
version2)
Description

Measurement
Point

in Figure 373.
332
Unit
Related Features
Times
Description
Measurement
Point

333

Unit
Related Features
Times
Description

speech version 2).
Measurement
Point
334

Unit
Related Features
Times
Description
335
Measurement
Point
Unit
Related Features
Times
failure for handover (speech
version3)
Description
336


Measurement
Point

in Figure 381.
Unit
Related Features
Times
337
Description
Measurement
Point

Unit
Related Features
Times
338
Description

speech version 3).
Measurement
Point
Unit
Related Features
Times
339
Description
Measurement
Point
Unit
Related Features
Times
340
Voice TCH/F handover
success
Description
This counter counts the number of successful TCH/F channel handover during voice channel handover.
When BSC detects the successful handover message sent by MS
on newly-allocated TCH/F channel, this counter accumulates. The
ASS_COM message indicates successful intra-cell handover, and
the HO_COM message indicates successful inter-cell handover and
external handover.
For intra-cell handover and inter-cell handover, the counter accumulates on source instances. For external handover, the counter
accumulates on target instances because the source instance is
not under this BSC.
Measurement
Point
The counter counts when BSC receives the ASS_COM/HO_COM

message. The measurement point is C4 as shown in Figure 388
and Figure 389, and D4 as shown in Figure 390 and Figure 391.
INTERNAL)
341

342
Unit
Related Features
Times
Description

due to channel activation failure during data channel handover.
BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/F. If the channel activation fails due to receiving
released, or channel being forcibly released, this counter accumulates.
Measurement
Point
BSC activates TCH/F as data channel for handover, but receives

point is C3 as shown in Figure 392 and D3 as shown in Figure 393.
343

Unit
Related Features
Times

handover
Description

due to BTS connection failure during data channel handover.
344
Measurement
Point

Unit
Related Features
Times
for handover
Description

due to BIU connection failure during data channel handover.
request to BIPB. If BIU connection fails due to receiving BIU con-
345
nection failure message, incorrect BIU connection response message or timer timeout, this counter accumulates.
Measurement
Point
Unit
Related Features
Times

handover
Description
346

due to TCU connection failure during data channel handover.

Measurement
Point
Unit
Related Features
Times

TCH/F handover success
Description
This counter counts the number of successful TCH/F channel handover during data channel handover.
347

external handover.
not under this BSC.
Measurement
Point

INTERNAL)

348
Unit
Related Features
Times
349
signaling TCH/H allocation
Description
This counter counts the number of TCH/H channel allocation failures during signaling channel assignment.
and occupy TCH/H channel successfully, BSC sends the CHL_ACT
message to BTS to activate this TCH/H channel.
released forcibly, this counter accumulates.
Measurement
Point
BSC activates TCH/H channel due to assignment and uses it as

signaling channel, but receives channel activation failure message,
incorrect channel activation response message, T9103 being timeout, channel instance being released, or channel being forcibly released. The measurement point is A2, as shown in Figure 404.
FIGURE 404 IMMEDIATE ASSIGNMENT ALLOCATION FAILURE FLOW 2
Unit
Related Features
Times
350
TCH/H allocation failure due
version1)
Description
This counter counts the number of TCH/H channel allocation failure due to channel activation failure when assigning voice channel
message to BTS to activate this TCH/H. If the channel activation
Measurement
Point
BSC activates TCH/H as voice channel (using speech version 1) for

in Figure 405.
Unit
Related Features
Times
351
version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection failure when assigning voice channel
occupy TCH/H channel successfully, BSC sends the CMM connection request to BTS. If BTS connection fails due to receiving CMM
Measurement
Point
BSC uses TCH/H for assignment, but the problem such as receiving
Unit
Related Features
Times
352
version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to BIU connection failure when assigning voice channel
occupy TCH/H channel successfully, BSC sends the BIU connection
Measurement
Point
Unit
Related Features
Times
353
version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection failure when assigning voice channel
occupy TCH/H channel successfully, BSC sends the TCU connection
Measurement
Point
Unit
Related Features
Times
354
TCH/H allocation failure
version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to channel activation failure during voice channel handover
occupy TCH/H channel successfully, if the connection succeeds,
BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/H. If channel activation fails due to receiving channel
Measurement
Point
BSC activates TCH/H channel as voice channel due to handover,

in Figure 410.
355
Unit
Related Features
Times
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection failure during voice channel handover
Measurement
Point
356
BSC uses TCH/H channel for handover, but receives connection


Unit
Related Features
Times
Description
This counter counts the number of failing to allocate TCH/H channel due to BIU connection failure during voice channel handover
357
Measurement
Point
BSC uses TCH/H for handover, but receives connection failure message, incorrect connection response message, or timer timeout
Unit
Related Features
Times
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection failure during voice channel handover
358
Measurement
Point
Unit
Related Features
Times
359
version2)
Description
Measurement
Point

in Figure 417.
Unit
Related Features
Times
360
version2)
Description
Measurement
Point
Unit
Related Features
Times
361
version2)
Description
Measurement
Point
Unit
Related Features
Times
362
version2)
Description
Measurement
Point
Unit
Related Features
Times
363
version2)
Description
Measurement
Point

in Figure 422.
364
Unit
Related Features
Times
Description
Measurement
Point

365

Unit
Related Features
Times
Description
366
Measurement
Point
Unit
Related Features
Times
Description
367

Measurement
Point
Unit
Related Features
Times
368
version3)
Description
Measurement
Point

in Figure 429.
Unit
Related Features
Times
369
version3)
Description
Measurement
Point
Unit
Related Features
Times
370
version3)
Description
Measurement
Point
Unit
Related Features
Times
371
version3)
Description
Measurement
Point
Unit
Related Features
Times
372
version3)
Description
Measurement
Point

in Figure 434.
373
Unit
Related Features
Times
Description
Measurement
Point
374


Unit
Related Features
Times
Description
375
Measurement
Point
Unit
Related Features
Times
Description
376

Measurement
Point
Unit
Related Features
Times
377
Voice TCH/H assignment
success
Description

TCH/H as voice channel.
occupy TCH/H channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. For assignment from A-interface, after BSC receives the assignment success message, the
Measurement
Point

378
Unit
Related Features
Times
failure
Description

as voice channel.
message to BTS to activate this TCH/H. If BSC does not receive
the MS access notification within a certain time, this assignment
fails.
Measurement
Point
379
Unit
Related Features
Times
Voice TCH/H handover
success
Description
This counter counts the number of successful TCH/H channel handover during voice channel handover.
external handover.
not under this BSC.
Measurement
Point
380


INTERNAL)

381
Unit
Related Features
Times
382
data TCH/H allocation failure
Description
This counter counts the number of TCH/H channel allocation failure

due to channel activation failure during data channel assignment.
occupy TCH/H channel successfully, if connection succeeds, BSC
sends the CHL_ACT message to BTS to activate this TCH/H. If
channel activation fails due to receiving channel activation failure
being timeout, channel instance being released or channel being
forcibly released, this counter accumulates.
Measurement
Point
BSC activates TCH/H channel due to assignment and uses the

channel as data channel, but receives channel activation failure
being timeout, channel instance being released, or channel being forcibly released. The measurement point is B3, as shown in
Figure 448.
Unit
Related Features
Times
383

assignment
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection failure when assigning data channel.
message or timer timeout, this counter accumulates.
Measurement
Point
connection failure message, incorrect connection response message or timer timeout occurs during CMM connection process. The
Unit
Related Features
Times
for assignment
Description
384
This counter counts the number of failing to allocate TCH/H channel due to BIU connection failure when assigning data channel.

Measurement
Point
BSC uses TCH/H for assignment, but receives connection failure

during BIU connection process. The measurement point is B2, as
Unit
Related Features
Times

assignment
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection failure when assigning data channel.
request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message or timer timeout, this counter accumulates.
Measurement
Point
BSC uses TCH/H for assignment, but receiving connection failure

during TCU connection process. The measurement point is B2, as
385
Unit
Related Features
Times
Description
This counter counts the number of failing to allocate TCH/H channel due to channel activation failure during data channel handover.
BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/H. If the channel activation fails due to receiving
released, or channel being forcibly released, this counter accumulates.
Measurement
Point
386
BSC activates TCH/H as data channel for handover, but receives

point is C3 as shown in Figure 452 and D3 as shown in Figure 453.

Unit
Related Features
Times

handover
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection failure during data channel handover.
387
Measurement
Point

Unit
Related Features
Times
for handover
Description
This counter counts the number of failing to allocate TCH/H channel due to BIU connection failure during data channel handover.
request to BIPB. If BIU connection fails due to receiving BIU con-
388
nection failure message, incorrect BIU connection response message or timer timeout, this counter accumulates.
Measurement
Point
Unit
Related Features
Times

handover
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection failure during data channel handover.
389

Measurement
Point
Unit
Related Features
Times

TCH/H assignment success
Description

TCH/H as data channel.
390
message to BTS to activate this TCH/H. For assignment from A-interface, after BSC receives the assignment success message, the
Measurement
Point

Unit
Related Features
Times
391

TCH/H assignment failure
Description

as data channel.
message to BTS to activate this TCH/H. If BSC does not receive
the MS access notification within a certain time, this assignment
fails.
Measurement
Point
Unit
Related Features
Times

TCH/H handover success
Description
This counter counts the number of successful TCH/H channel handover during data channel handover.
on newly-allocated TCH/H channel, this counter accumulates. The
392

external handover.
not under this BSC.
Measurement
Point

INTERNAL)

393
Unit
Related Features
Times
394
BSC-controlled incoming
release
Description
During BSC-controlled inter-cell incoming handover process, the

counter counts the number of forced release executions due to no
available radio resource in the target cell.
Usage
This counter is used to find out the frequency of forced release execution during BSC-controlled inter-cell incoming handover process.
It reflects the status of the handover flow.
Measurement
Point
The target cell within BSC receives the radio channel request message. If the request is due to BSC-controlled inter-cell incoming handover and the target cell has no available radio channels,
forced release is performed. When the target cell receives the
message of resource available returned by the forced release instance, the counter increments. The measurement point is A2, as
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
395
handover due to queues
Description

counter counts the number of queuing executions due to no available radio resource in the target cell.
Usage
This counter is used to find out the frequency of queuing execution during BSC-controlled inter-cell incoming handover process.
It reflects the status of the handover flow.
Measurement
Point
The target cell within BSC receives the radio channel request message. If the request is due to BSC-controlled inter-cell incoming
handover and the target cell has no available radio channels, the
target instance is added to the waiting queue. When the target
cell receives the message of resource available, the counter increments. The measurement point is A2, as shown in Figure 468.
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
396
handover
Description

counter counts the number of forced handover executions due to
no available radio resource in the target cell.
Usage
This counter is used to find out the frequency of forced handover

execution during BSC-controlled inter-cell incoming handover
process. It reflects the status of the handover flow.
Measurement
Point
The target cell within BSC receives the radio channel request message. If the request is due to BSC-controlled inter-cell incoming
handover and the target cell has no available radio channels, the
forced handover message is sent to the forced handover instance
and the target instance is added to the waiting queue. When the
target cell receives the message of resource available, the counter
469.
FIGURE 469 FORCED HANDOVER EXECUTION
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
397
handover
Description

counter counts the number of forced handover executions due to
no available radio resource in the target cell.
Usage

executions during MSC-controlled inter-BSC incoming handover
process. It reflects the status of the handover flow.
Measurement
Point
The target cell receives the radio channel request message. If the
request is due to MSC-controlled inter-BSC incoming handover and
the target cell has no available radio channels, the forced handover
message is sent to the forced handover instance and the target instance is added to the waiting queue. When the target cell receives
the message of resource available, the counter increments. The
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
unavailable defined TCH/H
Description
398

counter counts the number of unavailable TCH/H channel configured by OMCR in the current cell.
Usage
This counter is used to find out the number of unavailable TCH/H

channel in the current cell to facilitate eliminating the fault.
Measurement
Point

Unit
Related Features
Times
unavailable defined TCH/F
Description
iBSC supports the function of full dynamic wireless channel. This

counter counts the number of unavailable TCH/F channel configured by OMCR in the current cell.
Usage
This counter is used to find out the number of unavailable TCH/F

channel in the current cell to facilitate eliminating the fault.
Measurement
Point

399
Unit
Related Features
Times
signaling TCH/F drops due
to handover failure
Description
This counter counts the number of call drops due to handover failure on TCH/F signaling channel. Call drop occurs after MS requests
for TCH/F signaling channel successfully. If the problem is due to
handover failure, the counter increments.
Usage
handover failure on TCH/F signaling channel.
Measurement
Point
TCH/F signaling channel is activated after BSC initiates the handover flow. After that:
473.
HANDOVER
400
DUE TO

474.
HANDOVER
Related Features
Unit
DUE TO
DUE TO
Times
401
voice TCH/F drops due to
handover failure
Description
This counter counts the number of call drops on TCH/F voice channel due to handover failure. Call drop occurs after MS requests for
TCH/F voice channel successfully. The counter increments if call
drop is due to handover failure.
Usage
voice channel due to handover failure.
Measurement
Point
TCH/F voice channel is activated after BSC initiates the handover

flow. After that:
476.
HANDOVER
402
DUE TO
477.

HANDOVER
Related Features
Unit
DUE TO
DUE TO
Times
data TCH/F drops due to
handover failure
Description
This counter counts the number of call drops on TCH/F data channel due to handover failure. Call drop occurs after MS requests for
403
TCH/F data channel successfully. The counter increments if call

drop is due to handover failure.
Usage
data channel due to handover failure.
Measurement
Point
TCH/F data channel is activated after BSC initiates the handover

flow. After that:
479.
HANDOVER
404
DUE TO
480.

HANDOVER
Related Features
Unit
DUE TO
DUE TO
Times
405
signaling TCH/H drops due
to handover failure
Description
This counter counts the number of call drops due to handover failure on TCH/H signaling channel. Call drop occurs after MS requests
for TCH/H signaling channel successfully. If the problem is due to
handover failure, the counter increments.
Usage
handover failure on TCH/H signaling channel.
Measurement
Point
TCH/H signaling channel is activated after BSC initiates the handover flow. After that:
482.
HANDOVER
406
DUE TO
483.

HANDOVER
Related Features
Unit
DUE TO
DUE TO
Times
407
data TCH/H drops due to
handover failure
Description
This counter counts the number of call drops due to handover failure on TCH/H data channel. Call drop occurs after MS requests
for TCH/H data channel successfully. If the problem is due to handover failure, the counter increments.
Usage
handover failure on TCH/H data channel.
Measurement
Point
TCH/H data channel is activated after BSC initiates the handover

flow. After that:
485.
HANDOVER
408
DUE TO
486.

HANDOVER
Related Features
Unit
DUE TO
DUE TO
Times
409
TCH/H handover attempts
due to UL strength
Description

receiving strength too low on TCH/H channel.
Usage

UL receiving strength on TCH/H channel. If the counter's value is
too large, it indicates poor UL level on TCH/H channel.
Measurement
Point
BSC performs handover decision after receiving measurement report on TCH/H channel. If handover decision succeeds and the
handover is due to UL strength, this counter increments. The measurement point is A, as shown in Figure 488.
Unit
Related Features
Times
due to DL strength
410
Description

receiving strength too low on TCH/H channel.
Usage

DL receiving strength on TCH/H channel. If the counter's value is
too large, it indicates poor DL level on TCH/H channel.
Measurement
Point
handover is due to DL strength, this counter increments. The measurement point is A, as shown in Figure 489.
Unit
Related Features
Times
due to UL quality
Description

quality too poor on TCH/H channel.
Usage

UL quality on TCH/H channel. If the counters value is too large, it
indicates poor UL quality on TCH/H channel.
Measurement
Point
handover is due to UL quality, this counter increments. The measurement point is A, as shown in Figure 490.
Unit
Related Features
Times
411
due to DL quality
Description

quality too poor on TCH/H channel.
Usage

DL quality on TCH/H channel. If the counters value is too large,
it indicates poor DL quality on TCH/H channel.
Measurement
Point
handover is due to DL quality, this counter increments. The measurement point is A, as shown in Figure 491.
Unit
Related Features
Times
412
Description

interference too large on TCH/H channel.
Usage

UL interference on TCH/H channel. If the counter's value is too
large, it indicates large UL interference on TCH/H channel.
Measurement
Point
handover is due to UL interference, this counter increments. The
Unit
Related Features
Times
Description

interference too large on TCH/H channel.
Usage

DL interference on TCH/H channel. If the counter's value is too
large, it indicates large DL interference on TCH/H channel.
Measurement
Point
handover is due to DL interference, this counter increments. The
Unit
Related Features
Times
413
C900060230 Number
of TCH/H inter-subcell
handover attempts due to
good C/I
Description

too large C/I ratio on TCH/H channel. The handover only occurs
during sub-cell configuration and when C/I algorithm is adopted;
MS performs handover from external circle to internal circle.
Usage

to too large C/I ratio on TCH/H channel. If the counter's value is
too large, it indicates that, after MS accesses the external circle,
MS performs handover to the internal circle many times due to
good C/I ratio and the internal circle absorbs the traffic.
Measurement
Point
handover is due to too large C/I ratio, this counter increments.
Unit
Related Features
Times
C900060231 Number
of TCH/H inter-subcell
bad C/I
Description
414

too low C/I ratio on TCH/H channel. The handover only occurs
during sub-cell configuration and when C/I algorithm is adopted;

MS performs handover from internal circle to external circle.
Usage

to too low C/I ratio on TCH/H channel. If the counter's value is too
large, it indicates that, when MS calls within the internal circle,
MS performs handover to the external circle many times due to
poor C/I ratio. Interference within the internal circle is big, and
C/I ratio of the internal circle can be improved by adjusting the
carrier power.
Measurement
Point
handover is due to too low C/I ratio, this counter increments. The
Unit
Related Features
Times
due to PBGT
Description

PBGT value on TCH/H channel. If PBGT value is larger than zero, it
indicates the adjacent cell has better radio environment than the
current cell. If the number of times that PBGT value is larger than
zero reaches the threshold, PBGT handover occurs.
Usage

to PBGT value on TCH/H channel. If the counter's value is too
large, it indicates that signal on TCH/H channel within the current
cell is poorer than that in the adjacent cell.
Measurement
Point
handover is due to PBGT value, this counter increments. The measurement point is A, as shown in Figure 496.
415
Unit
Related Features
Times
due to large TA
Description

too large TA on TCH/H channel. Increasing TA indicates that MS is
moving away from the current cell. When the distance reaches a
certain value, handover will occur due to too large TA.
Usage

to too large TA on TCH/F channel. The counter's value reflects the
mobility of subscribers in the current cell to a certain extent.
Measurement
Point
handover is due to too large TA, this counter increments. The
Unit
Related Features
Times
416
Description

other reason beyond the handover reasons mentioned previously.
Usage

any other reason.
Measurement
Point
handover is due to any other reason beyond the handover reasons
mentioned previously, this counter increments. The measurement
Unit
Related Features
Times
success
Description
This counter counts the number of successfully assigning TCH/H

channel as signaling channel.
After BSC responds the channel request and successfully allocates
and occupies the channel, BSC sends channel activation message
CHL_ACT to activate the TCH/H. For immediate assignment, after
the channel activation succeeds, BTS receives the MS access message and sends EST_IND to BSC. The counter increments when
BSC receives the message correctly.
Measurement
Point
For immediate assignment, the counter increments when BSC receives the EST_IND message correctly. The measurement point is
417
Unit
Related Features
Times
MOC access success
418
Description
This counter counts the number of Mobile Originated Call (MOC)

MS successfully accesses the channel allocated in the immediate
assignment message. When MS receives IMM_ASS issued by BSC,
MS accesses the corresponding channel successfully. The counter
increments when BSC receives the EST_IND message from MS.
Usage
This counter is used to find out the frequency of successful MS

access due to MOC.
Measurement
Point
The counter increments when BSC receives the EST_IND message.

Unit
Times
C900060237 Number of dual

band outgoing handover
Description
This counter counts the number of MSC-controlled inter-BSC outgoing handovers that are initiated by MS in the source cell (the
source cell and the target cell are of different frequency bands).
Usage

inter-BSC outgoing handover that is initiated by MS. The source
cell and the target cell are of different frequency bands.
Measurement
Point
BSC performs handover decision after receiving the measurement

report sent by MS. If the decision indicates that inter-cell handover is necessary and if the current cell to which the handover
is attempted is a cell under different BSC, then BSC sends the
handover request A_HO_RQD to MSC to trigger inter-BSC handover. If BSC receives the handover command returned from MSC
and if the source cell and the target cell are of different frequency
bands, then this counter increments. The measurement point is
419
FIGURE 501 MSC-CONTROLLED OUTGOING HANDOVER EXECUTION
Unit
Related Features
Times

band outgoing handover
success
Description
This counter counts the number of successful MSC-controlled inter-BSC outgoing handovers that are initiated by MS in the source
cell (the source cell and the target cell are of different frequency
bands).
Usage
This counter is used to find out the frequency of successful MSCcontrolled inter-BSC outgoing handover that is initiated by MS. The
source cell and the target cell are of different frequency bands.
Measurement
Point
BSC performs handover decision after receiving the measurement

report sent by MS. If the decision indicates that inter-cell handover is necessary and if the current cell to which the handover is
attempted is a cell under different BSC, then BSC sends the handover request A_HO_RQD to MSC to trigger inter-BSC handover.
If MS accesses the target cell successfully, the source cell receives
the release command issued by MSC, if the source cell and the
target cell are of different frequency bands, then this counter increments. The measurement point is A, as shown in Figure 502.
FIGURE 502 MSC-CONTROLLED OUTGOING HANDOVER SUCCESS
Unit
Related Features
420
Times

band incoming handover
Description
This counter counts the number of inter-BSC incoming handovers

to the current cell that are initiated by MSC (the source cell and
the target cell are of different frequency bands).
Usage
This counter is used to find out the frequency of inter-BSC incoming handover that is initiated by MSC. The source cell and the
target cell are of different frequency bands.
Measurement
Point
After the target cell receives the handover request issued by MSC,
if the target cell occupies and activates the channel successfully
Unit
Related Features
Times

success
Description
This counter counts the number of successful MSC-controlled inter-BSC incoming handovers that are initiated by MS (the source
cell and the target cell are of different frequency bands).
Usage

inter-cell handover that is initiated by MS. The source cell and the
target cell are of different frequency bands.
Measurement
Point
After the target cell receives the handover completion message, if

the request is due to MSC-controlled inter-BSC incoming handover
421

Unit
Related Features
Times
C900060241 Number
of SDCCH assignment
attempts
Description
422
After BSC responds to the channel request to allocate and activate

SDCCH channel successfully, BSC sends the IMM_ASS message to
notify MS to use this channel. After MS receives this message, it
sends SABM frame to BTS on SDCCH. BTS then sends the EST_IND
message to BSC after receiving SABM frame.
If BSC receives the correct EST_IND message within specified time, it indicates that the SDCCH channel assignment succeeds, C900060241 and C900060242 accumulate simultaneously.
If BSC receives the incorrect EST_IND message or T3101 is

timeout, it indicates that the SDCCH channel assignment fails,
C900060241 and C900060243 accumulate simultaneously.
Usage
This counter counts the number of SDCCH channel assignment

attempts when BSC sends the IMM_ASS message to notify MS to
use the allocated SDCCH channel. The counter's value includes the
number of assignment success (C900060242) and the number of
assignment failure (C900060243).
Measurement
Point
This counter counts when BSC receives the EST_IND message or

the assignment completion message, or when T3101 is timeout
Unit
Related Features
Times
C900060242 Number
of SDCCH assignments
success
Description

If BSC receives the correct EST_IND message within specified
time, it indicates that the SDCCH channel assignment succeeds,
then this counter increments.
Usage
This counter counts the number of MS successfully accessing SDCCH channel when BSC sends the IMM_ASS message.
Measurement
Point
This counter counts when BSC receives the correct EST_IND message or the assignment completion message. The measurement
423
Unit
Related Features
Times
SDCCH assignment failure
Description

If BSC receives the incorrect EST_IND message or T3101 is timeout, it indicates that the SDCCH channel assignment fails, then
424
Usage
This counter counts the number of MS failing to access SDCCH

channel when BSC sends the IMM_ASS message.
Measurement
Point
This counter counts when BSC receives the incorrect EST_IND

message or when T3101 is timeout. The measurement point is
Unit
Related Features
Times
radio link failure
Description
This counter counts the number of voice TCH/F drops due to radio
link failure. After MS applies for TCH/F voice channel, call drops.
If this problem is caused by radio link failure, then this counter
increments.
Usage
This counter is used to learn the call drop frequency caused by raio
link failure on TCH/F voice channel.
Measurement
Point
On TCH/F voice channel, when BSC receives Connection Failure

Indication message at Abis interface, this counter counts. The
425
FIGURE 508 CALL DROPS CAUSED

ASSIGNMENT
Unit
Related Features
BY
RADIO LINK FAILURE DURING
Times
ZGB-06-01-001 Monitoring Um Interface
radio link failure
Description
426
This counter counts the number of voice TCH/H drops due to radio
link failure. After MS applies for TCH/H voice channel, call drops.
If this problem is caused by radio link failure, then this counter
increments.
Usage
This counter is used to learn the call drop frequency caused by raio
link failure on TCH/H voice channel.
Measurement
Point
On TCH/H voice channel, when BSC receives Connection Failure

Indication message at Abis interface, this counter counts. The
FIGURE 509 CALL DROPS CAUSED
ASSIGNMENT
Unit
Related Features
BY
RADIO LINK FAILURE DURING
Times
427
428
Chapter
Configuration
Management Infomation
Basic Measurement
Table of Contents
Overview........................................................................ 429
C900090001 Cell frequency band ...................................... 429
C900090002 Number of TRX ............................................. 430
C900090003 Number of TCH............................................. 430
C900090004 Number of SDCCH ........................................ 430
C900090005 Radio capacity (call loss 1) ............................. 430
C900090006 Radio capacity (call loss 2) ............................. 431
C900090007 Radio capacity (based on TRX)........................ 431
C900090008 Number of static PDTCH................................. 431
C900090009 Number of dynamic PDTCH ............................ 431
Overview
Configuration management information basic measurement
records the cell's basic configuration information of each measurement period.
Statistic unit in this measurement is cell.
C900090001 Cell frequency

band
Description
This counter records frequency bands set in the cell. Refer to configuration information for frequency band values.
Usage
This counter is used to find out frequency bands set at specific

time segment in the cell.
Unit
None
429
TRX
Description
Usage
Unit
This counter records the number of TRXs in the cell.

This counter is used to find out the number of TRXs in the cell at
specific time segment.
Times
TCH
Description
Usage
Unit
This counter records the number of voice channels in the cell.

This counter is used to find out the number of voice channels in
the cell at specific time segment.
Times
SDCCH
Description
This counter records the number of signaling channels in the cell.
Usage
This counter is used to find out the number of signaling channels

in the cell at specific time segment.
Unit
Times
C900090005 Radio capacity

(call loss 1)
Description
This counter records the cell's maximum traffic capacity in theory,

and it gets the radio capacity (call loss 1) from the Erlang table
according to the number of voice channels.
Usage
This counter is used to find out the cell's maximum traffic capacity
in theory at specific time segment.
Unit
430
Number of Erlangs 10000
Chapter 5 Configuration Management Infomation Basic Measurement

(call loss 2)
Description
This counter records the cell's maximum traffic capacity in theory,

and it gets the radio capacity (call loss 2) from the Erlang table
according to the number of voice channels.
Usage
Unit

(based on TRX)
Description
This counter records the cell's maximum traffic capacity in theory.

The radio capacity is calculated according to the number of carriers: 2.28 for a single carrier, 8.25 for dual carriers, 14.04 for three
carriers, and 21.04 for four carriers.
Usage
Unit
static PDTCH
Description
Usage
Unit
This counter records the number of static PDTCHs in the cell.

This counter is used to find out the number of static PDTCHs in the
cell at specific time segment.
Times
dynamic PDTCH
Description
Usage
This counter records the number of dynamic PDTCHs in the cell.

This counter is used to find out the number of dynamic PDTCHs in
the cell at specific time segment.
431
Unit
432
Times
Chapter
Downlink Data TBF

Measurement
Table of Contents
Overview........................................................................ 434
C901000001 Number of GPRS DL TBF resumption in delay
state.............................................................................. 434
on PACCH due to time out ................................................ 435
on PACCH due to other reasons ......................................... 436
on CCCH/PCCCH due to time out ....................................... 437
on CCCH/PCCCH due to other reasons ................................ 438
C901000011 Number of GPRS DL TBF establishment execution on CCCH/PCCCH ....................................................... 438
C901000012 Number of GPRS DL TBF establishment execution failure on CCCH/PCCCH due to polling failed ................. 440
C901000013 Number of GPRS DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded ......... 442
on CCCH/PCCCH.............................................................. 444
C901000015 Number of GPRS DL TBF normal release........... 446
C901000023 Number of EGPRS DL TBF resumption in delay
state.............................................................................. 447
on PACCH due to time out ................................................ 448
on PACCH due to other reasons ......................................... 449
on CCCH/PCCCH due to time out ....................................... 450
C901000033 Number of EGPRS DL TBF establishment execution on CCCH/PCCCH ....................................................... 451
C901000034 Number of EGPRS DL TBF establishment execution failure on CCCH/PCCCH due to polling failed ................. 453
C901000035 Number of EGPRS DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded ......... 455
on CCCH/PCCCH.............................................................. 457
C901000037 Number of EGPRS DL TBF normal release ......... 459
C901000045 Time of GPRS DL TBF connection .................... 460
C901000046 Time of EGPRS DL TBF connection................... 461
C901000047 Time of DL signaling TBF connection................ 461
433
C901000048 Max number of GPRS DL TBF simultaneous establishment .................................................................... 462

C901000050 Max number of EGPRS DL TBF simultaneous establishment .................................................................... 463
C901000052 Number of GPRS DL signaling TBF normal release ............................................................................. 463
C901000058 Number of EGPRS DL signaling TBF normal release ............................................................................. 464
Overview
DL TBF process comprises establishment, transmission and release
of the DL TBF.
The establishment includes the DL TBF establishment on CCCH,
PCCCH and PACCH.
The release includes normal release and abnormal release of the
DL TBF. Abnormal release is used to judge the running of PS service
so as to make adjustment.
DL transmission measurement mainly focuses on the connecting
time of the DL TBF and the number of co-existing DL TBFs.
GPRS DL TBF resumption
in delay state
Definition
434
Number of GPRS DL TBF resumption in delay state
Description
This counter counts the number of retransmissions after the DL

GPRS TBF finishes LLC frame transmission and receives new LLC
frames.
Measurement
Point
When the DL GPRS TBF transmits all LLC frames and receives new
LLC frames before transmitting the DL RLC block (FBI=1), this
Figure 510.
Chapter 6 Downlink Data TBF Measurement
FIGURE 510 - MEASUREMENT POINT OF NUMBER OF RESUMPTION FOR

GPRS DL TBF IN DELAY STATE
Unit
Related Features
Times
ZGB-03-05-013 Delayed TBF Release in DL
C901000005 Number
of GPRS DL TBF
establishment failure on
PACCH due to time out
Definition
Number of GPRS DL TBF establishment failure on PACCH due to

time out
Description
In the UL transmission state, when SGSN DL LLC frame arrives, the

DL TBF transmission should be established. If there is no reserved
DL resource, the user plane will ask the control plane to allocate
resource. This counter counts the number of non-responses from
the control plane in this case.
435
Measurement
Point
When the BSC sends DL Assign Request, the timer waiting for response is triggered. The counter increments if the timer expires.
FIGURE 511 NUMBER OF REQUEST FAILURES FOR ESTABLISHING GPRS ON
PACCH (NO RESPONSE FROM CONTROL PLANE)
Unit
Times
C901000006 Number
of GPRS DL TBF
PACCH due to other reasons
Definition

other reasons
Description
This counter counts the number of TBF establishment failures

caused by other reasons than non-responses from the control
plane when PACCH of GPRS TBF tries to establish DL TBF. The
other reasons here include failed transmission of assignment
messages and failed creation of DL RLC instances.
Measurement
Point
When PACCH fails to send the assignment messages or fails to

create DL RLC instances, the counter increments.
Unit
436
Times
C901000009 Number
of GPRS DL TBF
CCCH/PCCCH due to time
out
Definition
Number of GPRS DL TBF establishment failure on CCCH/PCCCH

due to time out
Description
When MS is in the idle state, after BSC receives DL LLC frames

from SGSN, BSC should originate DL TBF establishment assigned
on CCCH/PCCCH. The user plane asks the control plane for radio
resources. If the user plane fails to receive the resources within
the specified time or it receives the message of assignment failure,
it indicates that the DL TBF establishment fails.
Measurement
Point
During the DL GPRS TBF establishment on CCCH/PCCCH, if there is

no radio resource assigned by the control plane within the specified
time, this counter increments. The measurement point is A, as
FIGURE 512 FAILURES FOR ESTABLISHING DL GPRS TBF ON
CCCH/PCCCH (1)

CCCH/PCCCH (2)
437
Unit
Times
C901000010 Number
of GPRS DL TBF
CCCH/PCCCH due to other
reasons
Definition

Description
When MS is in the idle state, after BSC receives DL LLC frames from
SGSN, BSC should originate DL TBF establishment assigned on
CCCH/PCCCH. The user plane sends a DL establishment request to
the control plane. If it receives the instance release message from
the control plane or fails to create DL RLC instance after receiving
the resource assignment message, it indicates that the DL TBF
establishment fails.
Measurement
Point
During the DL GPRS TBF establishment on CCCH/PCCCH, after the

user plane sends the request to the control plane, if it receives the
instance release message from the control plane or fails to create
DL RLC instance after receiving the resource assignment message,
Unit
Times
C901000011 Number
of GPRS DL TBF
establishment execution
on CCCH/PCCCH
Definition
Number of GPRS DL TBF establishment execution on CCCH/PCCCH
Description
CCCH/PCCCH. After receiving the request from the user plane, the
control plane assigns the resource, sends the assignment message
on CCCH/PCCCH, and informs the user plane. The initial timing
advance is acquired then and the DL TBF establishment starts.
In the DTM mode, if the control plane has transmitted LLC frames
through the dedicated channel or has transmitted the DTM assign-
438
ment, the user plane is informed too and it believes the DL TBF
establishment has started.
Measurement
Point
During the DL GRPS TBF establishment on CCCH/PCCCH, after the

user plane sends the request to the control plane, receives the
resource assignment message, successfully creates the DL RLC
instance and sends the Packet Polling Request message to MS,
this counter increments. The measurement point is A2, as shown
inFigure 514 .
FIGURE 514 NORMAL ESTABLISHMENT OF DL GPRS TBF ON
CCCH/PCCCH
In the DTM mode, this counter increments when the user plane
receives the DTM sent message (the LLC frame has been sent).
FIGURE 515 LLC FRAME TRANSMITS GTTP MESSAGE IN DTM MODE
receives the DTM assignment message. The measurement
439
FIGURE 516 DTM ASSIGNMENT IN DTM MODE
Unit
Times
C901000012 Number
of GPRS DL TBF
failure on CCCH/PCCCH
due to polling failed
Definition
Number of Number of GPRS DL TBF establishment execution on

CCCH/PCCCH
DL TBF establishment execution failure on CCCH/PCCCH due to
polling failed
Description
Measurement
Point
440
CCCH/PCCCH. After receiving the resource assigned by the control
plane, the user plane sends the packet polling request message
through the assigned channel. When the MS responds with the AB
form of packet control ack message, the MS initial timing advance
is acquired then. If the MS does not respond, it indicates the DL
establishment has failed.
While waiting for MSs responding with the AB form of packet

control ack message, if timeout occurs or messages informing
control block loss exceed the specified number, this counter
517.

control ack message, if the release request is received from
control plane, this counter increments. The measurement
FIGURE 517 MEASUREMENT POINT OF NUMBER OF TIMES FOR

ESTABLISHING GPRS DL TBF WITH POLLING FAILED ON CCCH/PCCCH
FIGURE 518 MEASUREMENT POINT OF NUMBER OF TIMES FOR ESTABLISHING GPRS DL TBF WITH
POLLING FAILED ON CCCH/PCCCH
Unit
Times
441
C901000013 Number
of GPRS DL TBF
success on CCCH/PCCCH
due to polling succeeded
Definition

CCCH/PCCCH
DL TBF establishment execution success on CCCH/PCCCH due to
polling succeeded
Description
Measurement
Point
442

from SGSN, BSC should originate DL TBF establishment assigned on CCCH/PCCCH. After receiving the resource assigned
by the control plane, the user plane sends the packet polling
request message through the assigned channel. When the MS
responds with the AB form of packet control ack message, the
MS initial timing advance is acquired then. If the BSC receives
the packet control ack message and sends the message of timing advance setting, it indicates that the operation is successful.
In the DTM mode, if the user plane receives the DTM assignment message from the control plane, the operation is considered to be successful.
Besides, in the DTM mode, if the user plane receives the DTM
sent message from the control plane, to keep the consistency
of DL TBF establishment attempts and successful establishments, the DL TBF establishment is also considered to be successful.
When BSC receives the packet control ack message from MS after
sending the packet polling request message, or when in the DTM
mode, the user plane receives the DTM sent/assignment message
from the control plane, this counter increments. The measurement
points are A3 as shown in Figure 519, A as shown in Figure 520,
and A as shown in Figure 521.

CCCH/PCCCH
443
Unit
Times
C901000014 Number
of GPRS DL TBF
on CCCH/PCCCH
Definition

CCCH/PCCCH
DL TBF establishment success on CCCH/PCCCH
Description
Measurement
Point
444

MS initial timing advance is acquired then. After receiving the
packet control ack message, BSC sends the message of timing
advance setting. If the assignment is on PCCCH, it indicates
the DL TBF establishment is successful and the DL data will be
transmitted soon; if the assignment is on CCCH, the data will
be transmitted after packet DL assignment message is sent to
MS.
of DL TBF establishment attempts and successful establishments, the GPRS DL TBF establishment is also considered to
be successful.
If the assignment is on PCCCH, after the user plane sends the

packet polling request message and receives the packet control
ack message from MS, the counter increments.
If the assignment is on CCCH, after the user plane receives the

packet control ack message from MS and successfully sends
the DL assignment message, the counter increments.
In the DTM mode, when the user plane receives the DTM
sent/assignment message from the control plane, the counter
increments.
The measurement points are A3 (PCCCH) and A4 (CCCH), as

shown in Figure 522, A as shown in Figure 523, and A as shown
in Figure 524.

CCCH/PCCCH
445
Unit
Times
GPRS DL TBF normal
release
Definition

CCCH/PCCCH
DL TBF normal release
Description
When the DL GPRS TBF sends the last data block, it sets FBI to 1
and sets the RRBP bit to let MS send the DL response message.
After BSC receives the last response message (FAI=1), it is considered that the DL transmission is executed normally. In the DTM
mode, if the user plane receives the data sent message from the
control plane, to keep measurement consistency, it is considered
that the DL TBF is released normally.
Measurement
Point
After the DL GPRS TBF transmits the last data block (FBI=1) and
when BSC receives the last DL response message (FAI=1), this
counter increments. The measurement points are A, as shown in
Figure 525and Figure 526.
FIGURE 525 NORMAL RELEASE OF DL TBF
446
Unit
Times
EGPRS DL TBF resumption
in delay state
Definition
Number of EGPRS DL TBF resumption in delay state
Description
This counter counts the number of retransmissions after the DL

EGPRS TBF finishes LLC frame transmission and receives new LLC
frames.
Measurement
Point
After the DL EGPRS TBF transmits all LLC frames and before the
DL RLC block with FBI = 1 is transmitted, if the DL TBF receives
new LLC frames, this counter increments. The measurement point
is A, as shown in Figure 527.
447
FIGURE 527 - MEASUREMENT POINT OF NUMBER OF RESUMPTION FOR

GPRS DL TBF IN DELAY STATE
Unit
Related Features
Times
ZGB-03-05-013 Delayed TBF Release in DL
C901000027 Number
of EGPRS DL TBF
PACCH due to time out
448
Definition
Number of EGPRS DL TBF establishment failure on PACCH due to

time out
Description
In the UL transmission state, when SGSN DL LLC frame arrives, the

DL TBF transmission should be established. If there is no reserved
DL resource, the user plane will ask the control plane to allocate
resource. This counter counts the number of non-responses from
the control plane in this case.
Measurement
Point
When the BSC sends DL Assignment Request, the timer waiting for
response is triggered. The counter increments if the timer expires.
FIGURE 528 NUMBER OF REQUEST FAILURES FOR ESTABLISHING GPRS ON
PACCH (NO RESPONSE FROM CONTROL PLANE)
Unit
Times
C901000028 Number
of EGPRS DL TBF
PACCH due to other reasons
Definition

other reasons
Description
This counter counts the number of TBF establishment failures

caused by other reasons than non-responses from the control
plane when PACCH of EGPRS TBF tries to establish DL TBF. The
other reasons here include failed transmission of assignment
messages and failed creation of DL RLC instances.
Measurement
Point
When PACCH fails to send the assignment messages or fails to

create DL RLC instances, the counter increments.
Unit
Times
449
C901000031 Number
of EGPRS DL TBF
CCCH/PCCCH due to time
out
Definition
Number of EGPRS DL TBF establishment failure on CCCH/PCCCH

due to time out
Description

from SGSN, BSC should originate DL TBF establishment assigned
on CCCH/PCCCH. The user plane asks the control plane for radio
resources. If the user plane fails to receive the resources within
the specified time or it receives the message of assignment failure,
it indicates that the DL TBF establishment fails.
Measurement
Point
During the DL EGPRS TBF establishment on CCCH/PCCCH, if there

is no radio resource assigned by the control plane within the specified time, this counter increments. The measurement points are
A, as shown in Figure 529 and Figure 530.
CCCH/PCCCH (1)

CCCH/PCCCH (2)
450
Unit
Times
C901000032 Number
of EGPRS DL TBF
reasons
Definition

Description
CCCH/PCCCH. The user plane sends a DL establishment request to
the control plane. If it receives the instance release message from
the control plane or fails to create DL RLC instance after receiving
the resource assignment message, it indicates that the DL TBF
Measurement
Point
During the DL EGRPS TBF establishment on CCCH/PCCCH, after

the user plane sends the request to the control plane, if it receives
the instance release message from the control plane or fails to
create DL RLC instance after receiving the resource assignment
message, this counter increments.
Unit
Times
C901000033 Number
of EGPRS DL TBF
on CCCH/PCCCH
Definition
Number of EGPRS DL TBF establishment execution on CCCH/PCCCH
Description
CCCH/PCCCH. After receiving the request from the user plane, the
control plane assigns the resource, sends the assignment message
on CCCH/PCCCH, and informs the user plane. The initial timing
advance is acquired then and the DL TBF establishment starts.
451
In the DTM mode, if the control plane has transmitted LLC frames
through the dedicated channel or has transmitted the DTM assignment, the user plane is informed too and it believes the DL TBF
establishment has started.
Measurement
Point
During the DL EGRPS TBF establishment on CCCH/PCCCH, after

the user plane sends the request to the control plane, receives
the resource assignment message, successfully creates the DL
RLC instance and sends the Packet Polling Request message to
MS, this counter increments. The measurement point is A2, as
CCCH/PCCCH
receives the DTM sent message (the LLC frame has been sent).
452
receives the DTM assignment message. The measurement
Unit
Times
C901000034 Number
of EGPRS DL TBF
failure on CCCH/PCCCH
due to polling failed
Definition
Number of EGPRS DL TBF establishment execution failure on

CCCH/PCCCH due to polling failed
Description
CCCH/PCCCH. After receiving the resource assigned by the control
plane, the user plane sends the packet polling request message
through the assigned channel. When the MS responds with the AB
form of packet control ack message, the MS initial timing advance
is acquired then. If the MS does not respond, it indicates the DL
Measurement
Point

control ack message, if timeout occurs or messages informing
control block loss exceed the specified number, this counter
534.

control ack message, if the release request is received from
control plane, this counter increments. The measurement
453
FIGURE 534 MEASUREMENT POINT OF NUMBER OF TIMES FOR

ESTABLISHING EGPRS DL TBF WITH POLLING FAILED ON CCCH/PCCCH
FIGURE 535 MEASUREMENT POINT OF NUMBER OF TIMES FOR ESTABLISHING EGPRS DL TBF WITH
POLLING FAILED ON CCCH/PCCCH
Unit
454
Times
C901000035 Number
of EGPRS DL TBF
success on CCCH/PCCCH
due to polling succeeded
Definition
Description
Measurement
Point
Number of EGPRS DL TBF establishment execution success on

CCCH/PCCCH due to polling succeeded

MS initial timing advance is acquired then. If the BSC receives
the packet control ack message and sends the message of timing advance setting, it indicates that the operation is successful.
of DL TBF establishment attempts and successful establishments, the DL TBF establishment is also considered to be successful.
When BSC receives the packet control ack message from MS after
sending the packet polling request message, or when in the DTM
mode, the user plane receives the DTM sent/assignment message
from the control plane, this counter increments. The measurement
points are A3, as shown inFigure 536, A as shown in Figure 537
and A as shown in Figure 538.
455

CCCH/PCCCH
456
Unit
Times
C901000036 Number
of EGPRS DL TBF
on CCCH/PCCCH
Definition
Description
Measurement
Point
Number of EGPRS DL TBF establishment success on CCCH/PCCCH

MS initial timing advance is acquired then. After receiving the
packet control ack message, BSC sends the message of timing
advance setting. If the assignment is on PCCCH, it indicates
the DL TBF establishment is successful and the DL data will be
transmitted soon; if the assignment is on CCCH, the data will
be transmitted after packet DL assignment message is sent to
MS.
of DL TBF establishment attempts and successful establishments, the EGPRS DL TBF establishment is also considered to
be successful.
If the assignment is on PCCCH, after the user plane sends the

packet polling request message and receives the packet control
ack message from MS, the counter increments.
If the assignment is on CCCH, after the user plane receives the

packet control ack message from MS and successfully sends
the DL assignment message, the counter increments.
In the DTM mode, when the user plane receives the DTM
sent/assignment message from the control plane, the counter
increments.
The measurement points are A3 (PCCCH) and A4 (CCCH), as

shown in Figure 539, A as shown in Figure 540, and A as shown
in Figure 541.
457

CCCH/PCCCH
458
Unit
Times
EGPRS DL TBF normal
release
Definition
Number of EGPRS DL TBF normal release
Description
When the DL EGPRS TBF sends the last data block, it sets FBI to
1 and sets the RRBP bit to let MS send the DL response message.
After BSC receives the last response message (FAI=1), it is considered that the DL transmission is executed normally. In the DTM
mode, if the user plane receives the data sent message from the
control plane, to keep measurement consistency, it is considered
that the DL TBF is released normally.
Measurement
Point
After the DL EGPRS TBF transmits the last data block (FBI=1) and
when BSC receives the last DL response message (FAI=1), this
counter increments. The measurement points are A, as shown in
Figure 542andFigure 543.
459
Unit
Times
C901000045 Time of GPRS

DL TBF connection
Definition
Description
Measurement
Point
460
Time of GPRS DL TBF connection

This counter counts the cumulated overall DL connecting time of
GPRS TBF within a cell.
(1) When GPRS TBF RLC transmission starts, this counter accumulates.
(2) When GPRS TBF RLC transmission is released normally

(in the acknowledged mode, BSC receives the response with
FAI=1; or in the non-acknowledged mode, BSC receives the
Packet Control Ack message), this counter accumulates.
(3) When GPRS TBF RLC transmission is released abnormally

(including N3105 overflow and T3191 timeout), this counter
accumulates.
(4) When the measurement value is acquired regularly, this

The measurement value is a cumulated overall measurement

value. After each accumulation, the measurement time point
is updated with the current time. For Measurement Point (1),
after each accumulation, the number of DL GPRS TBFs that
are being transmitted increments by 1; for Measurement Point
(2) and Measurement Point (3), after each accumulation, the
number of DL GPRS TBFs that are being transmitted decreases
by 1. The measurement method is shown in Figure 544.
FIGURE 544 MEASUREMENT OF CUMULATED OVERALL DL CONNECTING

TIME
Unit
Second
C901000046 Time of
EGPRS DL TBF connection
Definition
Time of EGPRS DL TBF connection
Description

EGPRS TBF within a cell.
Measurement
Point
The measurement point and the formulas are as shown in Figure

545. EGPRS TBF is the measurement prerequisite.
FIGURE 545 MEASUREMENT OF CUMULATED OVERALL DL CONNECTING TIME
Unit
Second
C901000047 Time of DL
signaling TBF connection
Definition
Time of DL signaling TBF connection
461
Description

signaling TBF within a cell.
Measurement
Point
The measurement point and the formulas are as shown in Figure

546. Signaling TBF is the measurement prerequisite.
FIGURE 546 MEASUREMENT OF CUMULATED OVERALL DL CONNECTING TIME
Unit
Seconds
C901000048 Max number of

GPRS DL TBF simultaneous
establishment
Definition
Description
Measurement
Point
Max number of GPRS DL TBF simultaneous establishment

The counter counts the maximum number of DL GPRS TBFs that
are established simultaneously within a cell.
When GPRS TBF RLC transmission starts, the GPRS TBFs in the
cell increments by 1 and compares with the saved maximum
value.
When the measurement value is acquired regularly, compare

the number of GPRS TBF in the cell with the saved maximum
value.
For the measurement of number of GPRS TBFs in a cell, refer to

Measurement Point of C901000045.
Unit
462
Times
C901000050 Max number

of EGPRS DL TBF
Definition
Description
Measurement
Point
Max number of EGPRS DL TBF simultaneous establishment

The counter counts the maximum number of DL EGPRS TBFs that
are established simultaneously within a cell.
When EGPRS TBF RLC transmission starts, the EGPRS TBFs in

the cell increments by 1 and compares with the saved maximum value.
When the measurement value is acquired regularly, compare

the number of EGPRS TBF in the cell with the saved maximum
value.
For the measurement of number of EGPRS TBFs in a cell, refer to

Measurement Point of C901000045.
Unit
Times
normal release
Definition
Number of GPRS DL signaling TBF normal release
Description
When the DL GPRS signaling TBF sends the last data block, it sets
FBI to 1 and sets the RRBP bit to let MS send the DL response
message. After BSC receives the last response message (FAI=1),
it is considered that the DL transmission is executed normally. In
the DTM mode, if the user plane receives the data sent message
from the control plane, to keep measurement consistency, it is
considered that the DL TBF is released normally.
Measurement
Point
After the DL GPRS signaling TBF transmits the last data block
(FBI=1) and when BSC receives the last DL response message
(FAI=1), this counter increments. The measurement points are A,
as shown in Figure 547and Figure 548.
463
Unit
Times
normal release
Definition
Description
464
Number of EGPRS DL signaling TBF normal release

When the DL EGPRS signaling TBF sends the last data block, it
sets FBI to 1 and sets the RRBP bit to let MS send the DL response
message. After BSC receives the last response message (FAI=1),
it is considered that the DL transmission is executed normally. In
the DTM mode, if the user plane receives the data sent message
from the control plane, to keep measurement consistency, it is
considered that the DL EGPRS TBF is released normally.
Measurement
Point
After the DL EGPRS signaling TBF transmits the last data block
(FBI=1) and when BSC receives the last DL response message
(FAI=1), this counter increments. The measurement points are A,
as shown in Figure 549 and Figure 550.
Unit
Times
465
466
Chapter
Uplink Data TBF

Measurement
Table of Contents
Overview........................................................................ 468
C901010001 Number of GPRS UL TBF resumption in extend
uplink state .................................................................... 468
C901010002 Number of GPRS UL TBF resource reassign in
delay uplink state ............................................................ 469
C901010006 Number of GPRS establishment failure on PACCH
due to time out ............................................................... 470
C901010007 Number of GPRS establishment failure on PACCH
due to other reasons........................................................ 470
on CCCH/PCCCH due to competition solving failed................ 471
on CCCH/PCCCH due to not receive resource request ........... 472
C901010013 Number of GPRS UL TBF establishment success
on CCCH/PCCCH.............................................................. 474
C901010014 Number of GPRS UL TBF normal release........... 476
C901010022 Number of EGPRS UL TBF resumption in extend
uplink state .................................................................... 477
C901010023 Number of EGPRS UL TBF resource reassign in
delay uplink state ............................................................ 477
PACCH due to time out ..................................................... 478
PACCH due to other reasons ............................................. 479
on CCCH/PCCCH due to competition solving failed................ 480
on CCCH/PCCCH due to not receive resource request ........... 481
on CCCH/PCCCH.............................................................. 482
C901010035 Number of EGPRS UL TBF normal release ......... 484
C901010043 Time of GPRS UL TBF connection..................... 485
C901010044 Time of EGPRS UL TBF connection................... 485
C901010045 Time of UL signaling TBF connection ................ 486
C901010046 Max number of GPRS UL TBF simultaneous establishment .................................................................... 486
C901010048 Max number of EGPRS UL TBF simultaneous establishment .................................................................... 487
467
C901010050 Number of GPRS UL signaling TBF normal release ............................................................................. 487

C901010056 Number of EGPRS UL signaling TBF normal release ............................................................................. 488
Overview
Uplink (UL) data TBF measurement mainly involves processes of
establishing TBF, keeping TBF and releasing TBF on cells.
GPRS UL TBF resumption
in extend uplink state
Definition
468
Number of GPRS UL TBF resumption in extend uplink state
Description
MS notifies BSS whether extended GPRS UL TBF is supported by

reporting its radio access capability. If extended GPRS UL TBF is
supported, BSS will not stop allocating resources within a certain
period of time after receiving RLC block (CV=0) from MS. During
this period, if MS has new data to transmit, the data is transmitted
directly by the block allocated, and after BSS receives a new block,
TBF will be resumed to be in normal transmission state. If MS has
no new data to transmit, the message Packet UL Dummy Control Block
is transmitted by the block allocated.
Usage
This counter is used to record number of resumptions for GPRS UL

TBF in extended UL state.
Measurement
Point
This counter increments when a new data block is received in GPRS

extended UL state. The measurement point is A, as shown in
Figure 551.
Chapter 7 Uplink Data TBF Measurement
FIGURE 551 MEASUREMENT POINT ON RECEIVING NEW DATA BLOCK IN

GPRS EXTENDED UL STATE
Unit
Times
reassign in delay uplink state
Definition
Number of GPRS UL TBF resource reassign in delay uplink state
Description
If either MS or network does not support extended UL, after receiving RLC block (CV = 0) from MS, network will enter in delayed
UL state, and meanwhile stop allocating blocks.
Usage
This counter is used to record number of resource reassignment

for GPRS UL TBF in delayed UL state.
Measurement
Point
This counter increments when UPPB receives UL resource reassign

for GPRS UL TBF in delayed UL state, A, as shown in Figure 552.
FIGURE 552 MEASUREMENT POINT ON RECEIVING RESOURCE
REASSIGNMENT FOR GPRS UL TBF IN DELAYED UL STATE
Unit
Related Features
Times
ZGB-03-05-014 Delayed TBF Release in UL
469
GPRS establishment failure
on PACCH due to time out
Definition
Number of GPRS establishment failure on PACCH due to time out
Description
During TBF transmission of an MS with downlink TBF, if MS has

UL data to transmit but no corresponding TBF is available, UL
TBF establishment request will be sent out by Packet Downlink Ack.
UPPB will request CMP for resources if it does not have UL resource
records, and meanwhile, UPPB starts the timer. The request fails
if the timer gets no response till timeout.
Usage
This counter is used to record number of request failures caused

by timeout for establishing GPRS on PACCH.
Measurement
Point

FIGURE 553 MEASUREMENT POINT ON NUMBER OF REQUEST FAILURES
CAUSED BY TIMEOUT FOR ESTABLISHING GPRS ON PACCH GPRS
Unit
Times
GPRS establishment failure
on PACCH due to other
reasons
470
Definition
Number of GPRS establishment failure on PACCH due to other reasons
Description

UL data to transmit but no corresponding TBF is available, UL TBF
establishment request will be sent out by Packet Downlink Ack. Generally, network will assign resources to MS; However, UL TBF establishment request fails if there is any condition abnormal.
Usage

by other reasons for establishing GPRS on PACCH.
Measurement
Point
This counter increments when the request for establishing GPRS

on PACCH fails because of other reasons except timer is timeout.
Unit
Times
C901010010 Number
of GPRS UL TBF
CCCH/PCCCH due to
competition solving failed
Definition
Number of GPRS UL TBF establishment failure on CCCH/PCCCH

due to competition solving failed
Description
When MS has new data to transmit but no corresponding UL/downlink TBF is available, MS initiates UL TBF establishment flow, depending on whether the cell configures PBCCH on CCCH/PCCCH.
If two-step access is not compulsory at network side, in the case of
request for one-step access, MS sends RLC block with TLLI or Packet
Resource Request/ Additional MS Radio Access Capabilities on the UL
block allocated after receiving assignment message from network
so that solution by competition can be completed. Meanwhile, network sends Packet UL Ack with TLLI as well.
After sending out assignment message, if network does not receive RLC block or Packet Resource Request/ Additional MS Radio Access Capabilities from MS till timeout, solution for one-step access
by competition fails.
Usage
This counter is used to record number of failed GPRS UL TBF establishment on CCCH/PCCCH due to the failure of one-step success
competition solution.
471
Measurement
Point

FIGURE 554 MEASUREMENT POINT ON NUMBER OF ESTABLISHMENT
FAILURES OF GPRS UL TBF CAUSED BY COMPETITION SOLUTION FAILURE
Unit
Related Features
Times
ZGB-03-05-007 One Phase Access
C901010011 Number
of GPRS UL TBF
CCCH/PCCCH due to not
receive resource request
Definition

due to not receive resource request
Description
If two-step access is compulsory at network side, in the case of
request for two-step access, network assigns to MS single block
resource, by which MS then reports Packet Resource Request. After
that, network assigns new resource for MS by Packet UL Assignment according to MSs radio access capability.
After assigning single block resource to MS, if network does not
receive Packet Resource Request from MS, the request to establish
GPRS UL TBF fails.
Usage
472
This counter is used to record number of failed GPRS UL TBF establishment on CCCH/PCCCH caused by not receiving resource request.
Measurement
Point

FAILURES OF GPRS UL TBF CAUSED BY NOT RECEIVING RESOURCE
REQUEST
Unit
Related Features
Times
ZGB-03-05-008 Two Phase Access
C901010012 Number
of GPRS UL TBF
reasons
Definition

Description
so that solution by competion can be completed. Meanwhile, network sends Packet UL Ack with TLLI as well.
that, network assigns new resource for MS by Packet UL Assignment according to MSs wireless radio access capability.
473
Usage
This counter is used to record number of failed GPRS UL TBF establishment on CCCH/PCCCH caused by any other reasons.
Measurement
Point
This counter increments when GPRS UL TBF establishment fails

because of other reasons, except that one-step access competition
solution fails or two-step access does not receive resource request.
Unit
Times
C901010013 Number
of GPRS UL TBF
on CCCH/PCCCH
Definition
Description
Number of GPRS UL TBF establishment success on CCCH/PCCCH

that, network assigns new resource for MS by Packet UL Assignment according to MSs wireless radio access capability.
474
Usage
This counter is used to record number of successful GPRS UL TBF

establishment on CCCH/PCCCH.
Measurement
Point
This counter increments when GPRS UL TBF establishment on

CCCH/PCCCH succeeds in the cases of both one-step access and
two-step access. The measurement points are A, as shown in
FIGURE 556 MEASUREMENT POINT ON NUMBER OF SUCCESSFUL GPRS UL

TBF ESTABLISHMENT ON CCCH/PCCCH (I)
FIGURE 557 MEASUREMENT POINT ON NUMBER OF SUCCESSFUL GPRS UL

TBF ESTABLISHMENT ON CCCH/PCCCH (II)
475
Unit
Times
GPRS UL TBF normal
release
Definition
Number of GPRS UL TBF normal release
Description
If having received all data blocks, BSS sends Packet UL Ack with FAI
to MS and sets RRBP when receiving RLC block (CV = 0). MS then
reports Packet Control Ack on corresponding UL block, notifying BSS
to release TBF normally.
Usage
This counter is used to record number of normal GPRS UL TBF

releases.
Measurement
Point

FIGURE 558 MEASUREMENT POINT ON NUMBER OF NORMAL GPRS UL
TBF RELEASE
Unit
476
Times
EGPRS UL TBF resumption
in extend uplink state
Definition
Number of EGPRS UL TBF resumption in extend uplink state
Description
MS notifies BSS whether extended GPRS UL TBF is supported by

reporting its radio access capability. If extended GPRS UL TBF is
supported, BSS will not stop allocating resources within a certain
period of time after receiving RLC block (CV = 0) from MS. During
this period, if MS has new data to transmit, the data is transmitted
directly by the block allocated, and after the network receives a
new block, TBF will be resumed to be in normal transmission state.
If MS has no new data to transmit, the message Packet UL Dummy
Control Block is transmitted by the block allocated.
Usage
This counter is used to record number of resumptions for EGPRS

UL TBF in extended UL state.
Measurement
Point

FIGURE 559 MEASUREMENT POINT ON NUMBER OF RESUMPTIONS FOR
EGPRS UL TBF IN EXTENDED UL STATE
Unit
Times
reassign in delay uplink state
Definition
Description
Number of EGPRS UL TBF resource reassign in delay uplink state

If either MS or BSS does not support extended UL, after receiving
RLC block (CV = 0) from MS, BSS will enter in delayed UL state,
and meanwhile stop allocating blocks.
477
Usage
Measurement
Point
This counter is used to record number of resource reassignments

for EGPRS UL TBF in delayed UL state.
FIGURE 560 MEASUREMENT POINT ON NUMBER OF RESOURCE
REASSIGNMENTS FOR EGPRS UL TBF IN DELAYED UL STATE
Unit
Related Features
Times
ZGB-03-05-014 Delayed TBF Release in UL
EGPRS establishment
failure on PACCH due to
time out
478
Definition
Number of EGPRS establishment failure on PACCH due to time out
Description
During TBF transmission of an MS with downlink TBF, if MS has UL

data to transmit but no corresponding UL TBF is available, UL TBF
establishment request will be sent out by Packet Downlink Ack. UPPB
will request CMP for resources if having no UL resource records,
and meanwhile, UPPB starts the timer. The request fails if the
timer gets no response till timeout.
Usage

by timeout for establishing EGPRS on PACCH.
Measurement
Point

FIGURE 561 MEASUREMENT POINT ON NUMBER OF REQUEST FAILURES
CAUSED BY TIMEOUT FOR ESTABLISHING EGPRS ON PACCH
Unit
Times
EGPRS establishment
other reasons
Definition
Number of EGPRS establishment failure on PACCH due to other

reasons
Description

UL data to transmit but no corresponding UL TBF is available, UL
TBF establishment request will be sent out by Packet Downlink Ack.
Generally, network will assign resources to MS; However, UL TBF
establishment request fails if there is any condition abnormal.
Usage

by other reasons for establishing GPRS on PACCH.
Measurement
Point
This counter increments when request for establishing EGPRS on

PACCH fails because of other reasons except timer is timeout.
Unit
Times
479
C901010031 Number
of EGPRS UL TBF
CCCH/PCCCH due to
competition solving failed
Definition
Number of EGPRS UL TBF establishment failure on CCCH/PCCCH

due to competition solving failed
Description
After sending out assignment message, if network does not receive
RLC block or Packet Resource Request/ Additional MS Radio Access Capabilities from MS till timer is timeout, solution for one-step access
by competition fails.
Usage
Measurement
Point
This counter is used to record number of failed EGPRS UL TBF establishment on CCCH/PCCCH caused by competition solving failed.
FAILURES OF EGPRS UL TBF CAUSED BY COMPETITION SOLVING FAILED
Unit
Related Features
480
Times
C901010032 Number
of EGPRS UL TBF
receive resource request
Definition

due to not receive resource request
Description
that, network assigns new resource for MS by Packet UL Assignment
according to MSs radio access capability.
After assigning single block resource to MS, if network does not
receive Packet Resource Request from MS, the request to establish
GPRS UL TBF fails.
Usage
Measurement
Point
This counter is used to record number of failed EGPRS UL TBF

establishment on CCCH/PCCCH caused by not receiving resource
request.
FAILURES OF EGPRS UL TBF CAUSED BY NOT RECEIVING RESOURCE
REQUEST
Unit
Related Features
Times
481
C901010033 Number
of EGPRS UL TBF
reasons
Definition

Description
so that solution by competition can be completed. Meanwhile, network sends Packet UL Ack with TLLI as well.
according to MSs wireless radio access capability.
Usage
This counter is used to record number of failed EGPRS UL TBF

establishment on CCCH/PCCCH caused by any other reasons.
Measurement
Point
This counter increments when EGPRS UL TBF establishment fails

because of other reasons except that one-step access competition
solution fails or two-step access does not receive resource request.
Unit
Times
C901010034 Number
of EGPRS UL TBF
on CCCH/PCCCH
482
Definition
Number of EGPRS UL TBF establishment success on CCCH/PCCCH
Description

according to MSs wireless radio access capability.
Usage
This counter is used to record number of successful EGPRS UL TBF

establishment on CCCH/PCCCH.
Measurement
Point
This counter increments when EGPRS UL TBF establishment on

CCCH/PCCCH succeeds in the cases of both one-step access and
two-step access. The measurement points are A, as shown in
FIGURE 564 MEASUREMENT POINT ON NUMBER OF SUCCESSFUL EGPRS
UL TBF ESTABLISHMENT ON CCCH/PCCCH (I)
483
FIGURE 565 MEASUREMENT POINT ON NUMBER OF SUCCESSFUL EGPRS

UL TBF ESTABLISHMENT ON CCCH/PCCCH (II)
Unit
Times
EGPRS UL TBF normal
release
Definition
484
Number of EGPRS UL TBF normal release
Description
If having received all data blocks, BSS sends Packet UL Ack with
FAI to MS and sets RRBP when receiving RLC block (CV = 0). MS
then reports Packet Control Ack on corresponding UL block, notifying BSS to release TBF normally.
Usage
This counter is used to record number of normal EGPRS UL TBF

releases.
Measurement
Point

FIGURE 566 MEASUREMENT POINT ON NUMBER OF NORMAL EGPRS UL
TBF RELEASE
Unit
Times
C901010043 Time of GPRS

UL TBF connection
Definition
Time of GPRS UL TBF connection
Description
MS establishes two types of TBF for different purposes. They are

signaling TBF and data TBF.
Usage
This counter is used to find out cumulated overall UL connecting

time of GPRS TBF.
Measurement
Point
The counter starts to accumulate when UPPB receives the UL GPRS

TBF establishment indication, and stops when UL GPRS TBF on
UPPB ends normally.
Unit
Second
C901010044 Time of
EGPRS UL TBF connection
Definition
Description
Time of EGPRS UL TBF connection

485
Usage

time of EGPRS TBF.
Measurement
Point
The counter starts to accumulate when UPPB receives the UL EGPRS TBF establishment indication, and stops when UL EGPRS TBF
on UPPB ends normally.
Unit
Second
C901010045 Time of UL
signaling TBF connection
Definition
Time of UL signaling TBF connection
Description

Usage

time of signaling TBF.
Measurement
Point
The counter starts to accumulate when UPPB receives the UL signaling TBF establishment indication, and stops when UL signaling
TBF on UPPB ends normally.
Unit
Second
C901010046 Max number of

GPRS UL TBF simultaneous
establishment
Definition
Description
During the measurement period, there might be several TBFs existing simultaneously. This counter is used to find out the maximum number of UL GPRS TBF established simultaneously within
the measurement period.
Usage
This counter is used to find out the maximum number of UL GPRS

TBF established simultaneously within the measurement period.
Measurement
Point
This counter increments when UPPB receives UL GPRS TBF establishment indication, and decrements when the UL GPRS TBF releases.
Unit
486
Max number of GPRS UL TBF simultaneous establishment
Times
C901010048 Max number

of EGPRS UL TBF
Definition
Max number of EGPRS UL TBF simultaneous establishment
Description
During the measurement period, there might be several TBFs existing simultaneously. This counter is used to find out the maximum number of UL EGPRS TBF established simultaneously within
the measurement period
Usage
This counter is used to find out the maximum number of UL EGPRS

TBF established simultaneously within the measurement period.
Measurement
Point
This counter increments when UPPB receives UL EGPRS TBF establishment indication, and decrements when the UL EGPRS TBF
releases.
Unit
Times
normal release
Definition
Number of GPRS UL signaling TBF normal release
Description
Usage
This counter is used to record number of normal GPRS signaling

UL TBF releases.
487
Measurement
Point
The measurement point is A, as shown inFigure 567.

FIGURE 567 MEASUREMENT POINT ON NUMBER OF NORMAL GPRS
SIGNALING UL TBF RELEASE
Unit
Times
normal release
Definition
488
Number of EGPRS UL signaling TBF normal release
Description
Usage
This counter is used to record number of normal EGPRS signaling

UL TBF releases.
Measurement
Point

FIGURE 568 MEASUREMENT POINT ON NUMBER OF NORMAL GPRS
SIGNALING UL TBF RELEASE
Unit
Times
489
490
Chapter
Data Flow Measurement

Table of Contents
Overview........................................................................ 491
BIPB .............................................................................. 492
C901020002 Number of packets sent to BIPB...................... 492
C901020003 Number of Kbytes of IP packet received from
BIPB .............................................................................. 493
C901020004 Number of packets received from BIPB ............ 494
GIPB.............................................................................. 494
C901020006 Number of packets sent to GIPB ..................... 495
C901020007 Number of Kbytes of IP packet received from
GIPB.............................................................................. 496
C901020008 Number of packets received from GIPB ............ 496
C901020009 Number of Kbytes carried by EGPRS DL LLC
frame ............................................................................ 497
C901020014 Number of Kbytes carried by DL signaling LLC
frame ............................................................................ 498
C901020019 Number of Kbytes carried by UL LLC frame ......... 498
C901020020 Number of UL LLC frames .............................. 499
C901020021 Number of Bytes of GPRS DL TBF LLC
frame ............................................................................ 500
C901020022 Number of Bytes of EGPRS DL TBF LLC
frame ............................................................................ 500
C901020023 Number of Bytes of DL signaling TBF LLC
frame ............................................................................ 501
C901020024 Number of Bytes of UL GPRS TBF LLC
frame ............................................................................ 502
C901020025 Number of Bytes of EGPRS UL TBF LLC
frame ............................................................................ 503
C901020026 Number of Bytes of UL signaling TBF LLC
frame ............................................................................ 503
C901020031 Number of GPRS UL data TBF completion ......... 504
C901020034 Number of GPRS DL data TBF completion ......... 505
C901020041 Number of EGPRS UL data TBF completion ......... 506
C901020044 Number of EGPRS DL data TBF completion ......... 507
C901020050 Number of Kbytes carried by GPRS DL LLC
frame ............................................................................ 508
Overview
Data flow measurement focuses on the flow related information,
including the LLC frames, RLC blocks and TBF connecting time.
491
Kbytes of IP packet sent to
BIPB
Definition
Description
Number of Kbytes of IP packet sent to BIPB

DSP on the DL UPPB board encodes RLC/MAC blocks to PCU frames
without sync headers and sends the frames to BIPB through IP
packets. BIPB adds them with sync headers and sends them to
BTS. After the UL BIPB receives the PCU frames with sync headers
(bearing RLC/MAC blocks) from BTS, it removes the headers and
sends them to UPPB through IP packet.
This counter counts the payload sent within iBSC.
Usage
Measurement
Point
The counter counts the size of IP packets sent to BIPB. The measurement unit is Byte.
FIGURE 569 MEASUREMENT POINT OF SIZE OF IP PACKETS SENT TO BIPB
Unit
Byte
packets sent to BIPB
Definition
Description
Usage
492
Number of packets sent to BIPB

The counter counts the number of IP packets sent to BIPB.
Chapter 8 Data Flow Measurement
Measurement
Point

FIGURE 570 MEASUREMENT POINT OF NUMBER OF IP PACKETS SENT TO
BIPB
Unit
Times
Kbytes of IP packet received
from BIPB
Definition
Description
Number of Kbytes of IP packet received from BIPB

This counter counts the payload received within iBSC.
Usage
Measurement
Point
The counter counts the size of IP packets received from BIPB. The
measurement unit is Byte.
FIGURE 571 MEASUREMENT POINT OF SIZE OF IP PACKETS RECEIVED
FROM BIPB
Unit
Byte
493
packets received from BIPB
Definition
Description
Usage
Measurement
Point
Number of packets received from BIPB

The counter counts the number of packets received from BIPB.
FIGURE 572 MEASUREMENT POINT OF NUMBER OF IP PACKETS RECEIVED
FROM BIPB
Unit
Times
Kbytes of IP packet sent to
GIPB
Definition
Description
Number of Kbytes of IP packet sent to GIPB

The DL GIPB sends DL UnitData to UPPB through IP packets. After
caching DL UnitData, UPPB divides it into RLC blocks and sends
them to BTS through PCU frames. The UL UPPB decodes the received RLC blocks, composes UL UnitData, and sends it to GIPB
through IP packet.
This counter performs statistics for BSSGP layer, and the statistic
data contains BSSGP header but does not contain IP header.
Usage
494
The counter counts the size of IP packets sent to GIPB. The measurement unit is Byte.
Measurement
Point

FIGURE 573 MEASUREMENT POINT OF SIZE OF IP PACKETS SENT TO GIPB
Unit
Byte
packets sent to GIPB
Definition
Description
Usage
Measurement
Point
Number of packets sent to GIPB

through IP packet.
The counter counts the number of IP packets sent to GIPB.
FIGURE 574 MEASUREMENT POINT OF NUMBER OF IP PACKETS SENT TO
GIPB
Unit
Times
495
Kbytes of IP packet received
from GIPB
Definition
Description
Number of Kbytes of IP packet received from GIPB

through IP packet.
This counter performs statistics for BSSGP layer, and the statistic
data contains BSSGP header.
Usage
Measurement
Point
The counter counts the size of IP packets received from GIPB. The
measurement unit is Byte.
FIGURE 575 MEASUREMENT POINT OF SIZE OF IP PACKETS RECEIVED
FROM GIPB
Unit
Byte
packets received from GIPB
Definition
496
Number of packets received from GIPB
Description

through IP packet.
Usage
The counter counts the number of IP packets received from GIPB.
Measurement
Point

FIGURE 576 MEASUREMENT POINT OF NUMBER OF IP PACKETS RECEIVED
FROM GIPB
Unit
Times
Kbytes carried by EGPRS
DL LLC frame
Definition
Description
Number of Kbytes carried by EGPRS DL LLC frame

access capacity to carry MS) and according to the CMP command,
Usage
Measurement
Point
The counter counts the number of Kbytes carried by DL EGPRS LLC

frame.
FIGURE 577 MEASUREMENT POINT OF NUMBER OF KBYTES CARRIED BY DL
EGPRS LLC FRAME
Unit
Byte
497
Kbytes carried by DL
signaling LLC frame
Definition
Description
Number of Kbytes carried by DL signaling LLC frame

is transmitted. UPPB applies to the control plane to establish
DL TBF (radio access capacity to carry MS) and according to the
command from the control plane, establishes EGPRS/GPRS TBF.
Usage
Measurement
Point
The counter counts the number of Kbytes carried by DL signaling

LLC frame.
FIGURE 578 MEASUREMENT POINT OF NUMBER OF KBYTES CARRIED BY
DL SIGNALING LLC FRAME
Unit
Byte
Kbytes carried by UL LLC
frame
Definition
Description
Number of Kbytes carried by UL LLC frame

The UL UPPB sends the composed LLC frames to GIPB through IP
packet.
Usage
498
The counter counts the number of Kbytes carried by UL LLC frame.
Measurement
Point

UL LLC FRAME
Unit
Byte
LLC frames
Definition
Description
Number of UL LLC frames

The UL UPPB sends the composed LLC frames to GIPB through IP
packet.
This counter performs statistics for LLC layer, and the statistic result is the number of frames.
Usage
Measurement
Point
The counter counts the number of UL LLC frames.

FIGURE 580 MEASUREMENT POINT OF NUMBER OF UL LLC FRAMES
Unit
Times
499
Bytes of GPRS DL TBF LLC
frame
Definition
Description
Number of Bytes of GPRS DL TBF LLC frame

by setting RRBP to let MS report Packet DL Ack.
Usage
Measurement
Point
The counter counts the number of bytes of DL GPRS TBF LLC frame.
FIGURE 581 MEASUREMENT POINT OF NUMBER OF BYTES OF DL GPRS
TBF LLC FRAME
Unit
Byte
Bytes of EGPRS DL TBF
LLC frame
Definition
Description
500
Number of Bytes of EGPRS DL TBF LLC frame


by setting RRBP to let MS report EGPRS Packet DL Ack.
Usage
Measurement
Point
The counter counts the number of bytes of DL EGPRS TBF LLC

frame.
FIGURE 582 MEASUREMENT POINT OF NUMBER OF BYTES OF DL EGPRS
TBF LLC FRAME
Unit
Byte
Bytes of DL signaling TBF
LLC frame
Definition
Description
Number of Bytes of DL signaling TBF LLC frame

by setting RRBP to let MS report EGPRS Packet DL Ack.
Usage
The counter counts the number of bytes of DL signaling TBF LLC

frame.
501
Measurement
Point

FIGURE 583 MEASUREMENT POINT OF NUMBER OF BYTES OF DL SIGNALING
TBF LLC FRAME
Unit
Byte
Bytes of UL GPRS TBF LLC
frame
Definition
Description
Number of Bytes of UL GPRS TBF LLC frame

them into the LLC frame and sends it to SGSN.
Usage
Measurement
Point
The counter counts the number of bytes of UL GPRS TBF LLC frame.
FIGURE 584 MEASUREMENT POINT OF NUMBER OF BYTES OF UL GPRS
TBF LLC FRAME
Unit
502
Byte
Bytes of EGPRS UL TBF
LLC frame
Definition
Description
Number of Bytes of EGPRS UL TBF LLC frame

Usage
Measurement
Point
The counter counts the number of bytes of UL EGPRS TBF LLC

frame.
FIGURE 585 MEASUREMENT POINT OF NUMBER OF BYTES OF UL EGPRS
TBF LLC FRAME
Unit
Byte
Bytes of UL signaling TBF
LLC frame
Definition
Description
Number of Bytes of UL signaling TBF LLC frame

Usage
The counter counts the number of bytes of UL signaling TBF LLC

frame.
503
Measurement
Point

FIGURE 586 MEASUREMENT POINT OF NUMBER OF BYTES OF UL SIGNALING
TBF LLC FRAME
Unit
Byte
C901020031 Number
of GPRS UL data TBF
completion
Definition
504
Number of GPRS UL data TBF completion
Description
After the network side receives the data blocks (CV=0) from MS
and if all the other blocks have been received successfully, then it
will send the Packet UL Ack message (FAI=1) to MS. By this time,
the UL data transmission is completed.
Usage
The counter counts the number of completion of GPRS UL data

TBF.
Measurement
Point

FIGURE 587 MEASUREMENT POINT OF TOTAL NUMBER OF COMPLETION OF
GPRS UL DATA TBF
Unit
Times
C901020034 Number
of GPRS DL data TBF
completion
Definition
Number of GPRS DL data TBF completion
Description
After MS receives the FBI-set data blocks (RRBP is set at the network side) from the network side and if all the other blocks have
been received successfully, then it will send the Packet DL Ack/EGPRS
Packet DL Ack message (FAI=1) to the network side.
Usage
The counter counts the number of completion of GPRS DL data

TBF.
505
Measurement
Point

FIGURE 588 MEASUREMENT POINT OF TOTAL NUMBER OF COMPLETION OF
GPRS DL DATA TBF
Unit
Times
EGPRS UL data TBF
completion
Definition
506
Number of EGPRS UL data TBF completion
Description
After the network side receives the data blocks (CV=0) from MS
and if all the other blocks have been received successfully, then it
will send the Packet UL Ack message (FAI=1) to MS. By this time,
the UL data transmission is completed.
Usage
The counter counts the number of completion of EGPRS UL data

TBF.
Measurement
Point

FIGURE 589 MEASUREMENT POINT OF TOTAL NUMBER OF COMPLETION
OF EGPRS UL DATA TBF
Unit
Times
EGPRS DL data TBF
completion
Definition
Number of EGPRS DL data TBF completion
Description
After MS receives the FBI-set data blocks (RRBP is set at the network side) from the network side and if all the other blocks have
been received successfully, then it will send the Packet DL Ack/EGPRS
Packet DL Ack message (FAI=1) to the network side.
Usage
The counter counts the number of completion of EGPRS DL data

TBF.
507
Measurement
Point

FIGURE 590 MEASUREMENT POINT OF TOTAL NUMBER OF COMPLETION
OF EGPRS DL DATA TBF
Unit
Times
Kbytes carried by GPRS DL
LLC frame
Definition
Description
Number of Kbytes carried by GPRS DL LLC frame

access capacity to carry MS) and according to the CMP command,
Usage
508
The counter counts the number of Kbytes carried by DL GPRS LLC

frame.
Measurement
Point

DL GPRS LLC FRAME
Unit
Byte
509
510
Chapter
Uplink-Downlink RLC
Table of Contents
Overview........................................................................ 512
C901030041 Bytes of GPRS DL RLC lost on PDTCH............... 514
C901030042 Bytes of EGPRS DL RLC lost on PDTCH ............. 514
C901030083 Number of UL RLC Blocks lost ......................... 514
C901030084 Bytes of GPRS UL RLC lost on PDTCH............... 515
C901030085 Bytes of EGPRS UL RLC lost on PDTCH ............. 516
C901030086 Number of standstill of GPRS UL TBF receiving
window .......................................................................... 516
C901030087 Number of standstill of EGPRS UL TBF receiving
window .......................................................................... 517
C901030088 Number of standstill of GPRS DL TBF sending
window .......................................................................... 517
C901030089 Number of standstill of EGPRS DL TBF sending
window .......................................................................... 518
C901030090 Number of increment of DL coding mode.......... 519
C901030091 Number of decrement of DL coding mode ......... 520
C901030092 Number of increment of UL coding mode.......... 522
C901030093 Number of decrement of UL coding mode ......... 522
C901030094 Number of conversion from GMSK to 8PSK ......... 523
C901030095 Number of conversion from 8PSK to GMSK ......... 525
C901030153 Number of increment of GPRS DL coding
mode ............................................................................. 527
C901030154 Number of decrement of GPRS DL coding
mode ............................................................................. 528
C901030155 Number of increment of GPRS UL coding
mode ............................................................................. 528
C901030156 Number of decrement of GPRS UL coding
mode ............................................................................. 529
C901030157 Number of increment of EGPRS DL coding
mode ............................................................................. 530
C901030158 Number of decrement of EGPRS DL coding
mode ............................................................................. 530
C901030159 Number of increment of EGPRS UL coding
mode ............................................................................. 531
C901030160 Number of decrement of EGPRS UL coding
mode ............................................................................. 532
511
Overview
RLC blocks are classified into control block and data block based
on the content. Data block includes RLC block waiting to be acknowledged (Pending block), retransmitted block (NACK block),
and first-transmitted block (new blocks excluding retransmitted
RLC block and pending RLC blocks).
RLC coding scheme includes CS1 ~ CS4 and MCS1 ~ MCS9. Coding
scheme is set at background and can be adjusted by BSC according to the link quality.
UL /DL RLC statistics is used to find out the number of RLC blocks
with different coding schemes received and sent by BSC as well as
coding scheme adjustment times during transmission process.
Figure 592 shows the measurement point of DL pending RLC block.
FIGURE 592 MEASUREMENT POINT OF DL PENDING RLC BLOCK
Figure 593 shows the measurement point of DL retransmitted RLC

block.
FIGURE 593 MEASUREMENT POINT OF DL RETRANSMITTED RLC BLOCK
Figure 594shows the measurement point of DL first-transmitted

RLC block.
512
Chapter 9 Uplink-Downlink RLC Statistic Measurement
FIGURE 594 MEASUREMENT POINT OF DL FIRST-TRANSMITTED RLC BLOCK
Figure 595 shows the measurement point of UL pending RLC block.

FIGURE 595 MEASUREMENT POINT OF UL PENDING RLC BLOCK
Figure 596 shows the measurement point of UL retransmitted RLC

block.
FIGURE 596 MEASUREMENT POINT OF UL RETRANSMITTED RLC BLOCK
Figure 597 shows the measurement point of UL first-transmitted

RLC block.
513
FIGURE 597 MEASUREMENT POINT OF UL FIRST-TRANSMITTED RLC BLOCK
C901030041 Bytes of GPRS

DL RLC lost on PDTCH
Definition
Description
Bytes of GPRS DL RLC lost on PDTCH

This counter is not used for the time being.
C901030042 Bytes of
EGPRS DL RLC lost on
PDTCH
Definition
Description
Bytes of EGPRS DL RLC lost on PDTCH

RLC Blocks lost
Definition
514
Number of UL RLC Blocks lost
Description
MS sends UL RLC data block to BSC by BTS. The counter keeps

record of the number of data blocks lost during packet transmission.
Usage
This counter is used to find out the number of RLC data blocks lost
on PDTCH.
Measurement
Point
The counter increments when UL RLC data blocks from BTS get
lost. The measurement point is A, as shown in Figure 598.
FIGURE 598 MEASUREMENT POINT OF NUMBER OF UL RLC BLOCKS LOST
Unit
Times
C901030084 Bytes of GPRS

UL RLC lost on PDTCH
Definition
Bytes of GPRS UL RLC lost on PDTCH
Description

record of the number of CS-coded RLC bytes lost on PDTCH in
non-ack mode.
Usage
This counter is used to find out the number of CS-coded RLC bytes
on UL PDTCH in non-ack mode.
Measurement
Point
The counter increments when CS-coded UL RLC block from BTS

gets lost. The measurement point is A, as shown in Figure 599.
Unit
Byte
515
C901030085 Bytes of
EGPRS UL RLC lost on
PDTCH
Definition
Bytes of EGPRS UL RLC lost on PDTCH
Description

record of the number of MCS-coded RLC bytes lost on PDTCH in
non-ack mode.
Usage
This counter is used to find out the number of MCS-coded RLC

bytes on UL PDTCH in non-ack mode.
Measurement
Point
The counter increments when MCS-coded UL RLC block from BTS

gets lost. The measurement point is A, as shown in Figure 600.
Unit
Byte
standstill of GPRS UL TBF
receiving window
Definition
516
Number of standstill of GPRS UL TBF receiving window
Description
This counter counts the number of standstill of UL receiving window after UL GPRS TBF establishment.
Usage
This counter is used to find out the number of standstill of UL GPRS

TBF receiving window.
Measurement
Point
The counter increments when receiving window is found to come

to a standstill in RLC layer after UL GPRS TBF establishment. The
FIGURE 601 MEASUREMENT POINT OF NUMBER OF STANDSTILL OF GPRS

UL TBF RECEIVING WINDOW
Unit
Times
standstill of EGPRS UL TBF
receiving window
Definition
Number of standstill of EGPRS UL TBF receiving window
Description
This counter counts the number of standstill of UL receiving window after UL EGPRS TBF establishment.
Usage
This counter is used to find out the number of standstill of UL EGPRS TBF receiving window.
Measurement
Point
The counter increments when receiving window is found to come

to a standstill in RLC layer after UL EGPRS TBF establishment.
Unit
Times
standstill of GPRS DL TBF
sending window
Definition
Description
Number of standstill of GPRS DL TBF sending window

This counter counts the number of standstill of DL sending window
after DL GPRS TBF establishment.
517
Usage
This counter is used to find out the number of standstill of DL GPRS

TBF sending window.
Measurement
Point
The counter increments when sending window is detected to stagnate during RLC block sending to BTS from BSC. The measurement
DL TBF SENDING WINDOW
Unit
Times
standstill of EGPRS DL TBF
sending window
Definition
518
Number of standstill of EGPRS DL TBF sending window
Description
This counter counts the number of standstill of DL sending window

after DL EGPRS TBF establishment.
Usage
This counter is used to find out the number of standstill of DL

EGPRS TBF sending window.
Measurement
Point
The counter increments when sending window is detected to

standstill during RLC block sending to BTS from BSC. The measurement point is A, as shown in Figure 603.

DL TBF SENDING WINDOW
Unit
Times
increment of DL coding
mode
Definition
Number of increment of DL coding mode
Description
BSC will adjust DL coding scheme based on measurement report

when sending DL RLC blocks to BTS. This counter counts the number of DL coding scheme increase.
Usage
This counter is used to find out the increase of DL RLC block coding
scheme.
Measurement
Point
The counter increments when coding scheme of DL RLC blocks

sending to BTS from BSC is increased. The measurement point is
A as shown in Figure 604 (for EDGE) and Figure 605 (for GPRS).
519
FIGURE 604 MEASUREMENT POINT OF NUMBER OF INCREMENT OF DL

CODING MODE (EDGE RLC BLOCK)

CODING MODE (GPRS RLC BLOCK)
Unit
Related Features
Times
ZGB-03-05-012 GPRS Link Adaptation
ZGO-03-05-002 EGPRS Link Adaptation
decrement of DL coding
mode
Definition
520
Number of decrement of DL coding mode
Description
BSC will adjust DL coding scheme based on measurement report

when sending DL RLC blocks to BTS. This counter counts the number of DL coding scheme decrease.
Usage
This counter is used to find out the decrease of DL RLC block coding
scheme.
Measurement
Point
The counter increments when coding scheme of DL RLC blocks

sending to BTS from BSC is decreased. The measurement point is
A as shown in Figure 606 (for EDGE) and Figure 607 (for GPRS).

Unit
Related Features
Times
521
increment of UL coding
mode
Definition
Number of increment of UL coding mode
Description
BSC will adjust UL coding scheme based on measurement report

when sending UL RLC blocks to BTS. This counter counts the number of UL coding scheme increase.
Usage
This counter is used to find out the increase of UL RLC block coding
scheme.
Measurement
Point
The counter increments when coding scheme of UL RLC blocks is

increased. The measurement point is A, as shown in Figure 608.
FIGURE 608 MEASUREMENT POINT OF NUMBER OF INCREMENT OF UL
CODING MODE
Unit
Related Features
Times
decrement of UL coding
mode
Definition
Description
522
Number of decrement of UL coding mode

BSC will adjust UL coding scheme based on measurement report
when sending UL RLC blocks to BTS. This counter counts the number of UL coding scheme decrease.
Usage
This counter is used to find out the decrease of UL RLC block coding
scheme.
Measurement
Point
The counter increments when coding scheme of UL RLC blocks

sending to BTS from BSC is decreased. The measurement point is
CODING MODE
Unit
Related Features
Times
conversion from GMSK to
8PSK
Definition
Number of conversion from GMSK to 8PSK
Description
This counter counts the number of the handover of modulation

mode from GMSK to 8PSK.
Usage
This counter is used to find out the number of the handover from
GMSK to 8PSK of RLC data block .
Measurement
Point
The counter increments When coding scheme of RLC block is

changed from GMSK to 8PSK (MCS5~MCS9). The measurement
point is A, as shown in Figure 610, Figure 611, and Figure 612.
523


524

CODING MODE
Unit
Related Features
Times
conversion from 8PSK to
GMSK
Definition
Number of conversion from 8PSK to GMSK
Description
This counter counts the number of the handover of modulation

mode from 8PSK to GMSK.
Usage
This counter is used to find out the number of the handover from
8PSK to GMSK of RLC data block.
Measurement
Point
The counter increments when coding scheme of RLC block is

changed from 8PSK to GMSK (from MCS5~MCS9 to other). The
measurement point is A, as shown in Figure 613, Figure 614, and
Figure 615.
525


526

CODING MODE
Unit
Related Features
Times
increment of GPRS DL
coding mode
Description
In GPRS service, when BSC sends the downlink RLC block to BTS,
the downlink coding mode (Cn Xn Nn) is adjusted according to
the receiving condition. In Nn data blocks, if Cn data blocks are
received correctly, then the coding mode is upgraded by one level.
This counter counts the number of times that the downlink GPRS
coding mode is upgraded.
Usage
This counter is used to find out the condition of downlink RLC

block's coding mode being upgraded.
This counter is supported in version V6.20.200a or above.
Measurement
Point
When the coding mode of downlink RLC block sent to BTS from BSC
is upgraded, the counter increments. The measurement point is
527

CODING MODE ADJUSTMENT
Unit
OF
DOWNLINK GPRS RLC BLOCK
Times
decrement of GPRS DL
coding mode
Description
In GPRS service, when BSC sends the downlink RLC block to BTS,
the downlink coding mode (Cn Xn Nn) is adjusted according to
the receiving condition. In Nn data blocks, if Xn data blocks are
lost, then the coding mode is degraded by one level. This counter
counts the number of times that the downlink GPRS coding mode
is degraded.
Usage

block's coding mode being degraded.
Measurement
Point
Unit
When the coding mode of downlink RLC block sent to BTS from
BSC is degraded, the counter increments.
Times
increment of GPRS UL
coding mode
Description
528
When BSC receives the uplink RLC block, it adjusts the coding
mode for RLC block according to the measurement report. This
counter counts the number of times that the uplink coding mode
is upgraded.
Usage
This counter is used to find out the condition of uplink coding mode
being upgraded.
Measurement
Point
When the coding mode of uplink RLC block received by BSC is

upgraded, the counter increments. The measurement point is A,
ADJUSTMENT
Unit
OF
UPLINK RLC BLOCK CODING MODE
Times
decrement of GPRS UL
coding mode
Description
is degraded.
Usage
being degraded.
Measurement
Point
Unit

degraded, the counter increments.
Times
529
increment of EGPRS DL
coding mode
Description
When BSC sends the downlink RLC block to BTS, the downlink
coding mode is adjusted according to the measurement report.
This counter counts the number of times that the downlink coding
mode is upgraded.
Usage

block's coding mode being upgraded.
Measurement
Point
When the coding mode of downlink RLC block sent to BTS from BSC
is upgraded, the counter increments. The measurement point is
CODING MODE ADJUSTMENT
Unit
OF
DOWNLINK EDGE RLC BLOCK
Times
decrement of EGPRS DL
coding mode
Description
530
When BSC sends the downlink RLC block to BTS, the downlink
coding mode is adjusted according to the measurement report.
This counter counts the number of times that the downlink coding
mode is degraded.
Usage

block's coding mode being degraded.
Measurement
Point
Unit
When the coding mode of downlink RLC block sent to BTS from
BSC is degraded, the counter increments.
Times
increment of EGPRS UL
coding mode
Description
is upgraded.
Usage
being upgraded.
Measurement
Point

upgraded, the counter increments. The measurement point is A,
ADJUSTMENT
Unit
OF
UPLINK RLC BLOCK CODING MODE
Times
531
decrement of EGPRS UL
coding mode
Description
is degraded.
Usage
being degraded.
Measurement
Point
Unit
532

degraded, the counter increments.
Times
Chapter
10
PS Resource Used
Table of Contents
Overview........................................................................ 534
C901040001 Maximum number of Abis TS used .................. 534
C901040002 Average number of Abis TS used..................... 535
C901040004 Average number of unavailable PDCH .............. 535
C901040005 Number of available static PDCH ..................... 535
C901040006 Number of unavailable static PDCH.................. 536
C901040009 Time of DL PDCH congestion .......................... 536
C901040010 Time of UL PDCH congestion .......................... 537
C901040011 Time of PDCH used at least one UL/DL TBF exists ................................................................................ 538
C901040012 Time of PDCH used at least one UL/DL EGPRS
TBF exists ...................................................................... 538
C901040013 Time of PDCH used at least one DL TBF exists ................................................................................ 539
C901040014 Time of PDCH used at least one UL TBF exists ................................................................................ 539
AGCH............................................................................. 540
C901040019 Number of paging PS requests on PCH............. 541
C901040020 Number of paging CS requests on PCH............. 542
C901040021 Number of immediate assignment on PCH ......... 542
PAGCH ........................................................................... 543
C901040023 Number of paging PS requests on PPCH ........... 544
C901040024 Number of paging CS requests on PPCH ........... 545
PPCH ............................................................................. 546
C901040026 Number of Packet Channel Request on
PRACH ........................................................................... 546
C901040027 Sum of Abis TS used sampling ........................ 547
C901040028 Number of Abis TS used sampling ................... 547
C901040029 Sum of PDCH used sampling .......................... 548
C901040030 Number of PDCH used sampling...................... 548
C901040031 Maximum value of Abis TS used to CS ............. 548
C901040032 Minimum value of Abis TS used to CS .............. 549
CS................................................................................. 549
C901040034 Number of sampling of CS.............................. 550
C901040035 Maximum value of Abis TS used to PS.............. 550
C901040036 Minimum value of Abis TS used to PS .............. 550
PS ................................................................................. 551
C901040038 Number of sampling of PS .............................. 551
533
C901040039 MAX CS used number of exclusive ABIS ........... 551

C901040040 MIN CS used number of exclusive ABIS............ 552
C901040041 MAX PS used number of exclusive ABIS ........... 552
C901040042 MIN PS used number of exclusive ABIS ............ 552
C901040043 Average Number of GPRS User ....................... 553
C901040044 Maximum number of GPRS User ..................... 553
C901040045 Average Number of EGPRS User...................... 554
C901040046 Maximum number of EDGE User ..................... 554
C901040047 Number of assigned uplink radio channels ......... 554
C901040048 Number of assigned downlink radio channels ............................................................................... 555
C901040049 Number of requested uplink radio channels ............................................................................... 555
C901040050 Number of requested downlink radio channels ............................................................................... 556
C901040051 Number of PS channel expand ........................ 556
C901040052 Number of PS channel expand perform ............ 556
C901040053 Number of PS channel expand success............. 557
Overview
Statistic counters are used to measure the PS resource usage in
each cell, including number of usable PS channels, average and
max number of busy PS channels, total busy time of PS channels,
total time of PS channel congestion and using of PS channels.
C901040001 Maximum
number of Abis TS used
Description
This counter counts the maximum number of Abis TS used under

TDM connection between cell and site during measurement period.
The counter value reflects the instant Abis resource occupation and
maximum busyness.
Usage
This counter is used to find out the current cells requirements for
Abis resource, which helps to adjust or expand Abis resource.
Measurement
Point
Inquire the database when periodic measurement data report to

get the counter value.
Unit
534
Times
Chapter 10 PS Resource Used Statistic Measurement
C901040002 Average
number of Abis TS used
Definition
Average number of Abis TS used
Description
This counter counts the average number of Abis TS used under

TDM connection between cell and site during measurement period.
Usage
This counter is used to find out the Abis resource occupation by

the current cell, which helps to adjust or expand Abis resource.
Measurement
Point

Unit
Times
C901040004 Average
number of unavailable
PDCH
Description
This counter counts the number of PDCHs that are not assigned
normally, including blocked dynamic PDCHs due to various causes
and static PDCHs.
Usage
This counter is used to find out the number of unavailable PDCHs,

which helps to find out the trouble cause and make troubleshooting
in time.
Measurement
Point

Unit
Times
available static PDCH
Definition
Number of available static PDCH
Description
iBSC supports dynamic wireless channels. This counter counts the

number of available PDCHs configured through OMCR in the current cell.
Usage
This counter is used to find out the number of available static PDCHs in the current cell, which helps to make troubleshooting.
Measurement
Point

Unit
Times
535
Related Features
ZGB-03-02-005 GPRS-only (without voice) Timeslots Configurable

ZGO-03-02-010 GPRS and EGPRS Channels Allocated Separately
unavailable static PDCH
Definition
Number of unavailable static PDCH
Description
iBSC supports dynamic wireless channels. This counter counts the

number of unavailable PDCHs configured via OMCR in the current
cell.
Usage
This counter is used to find out the number of unavailable static

PDCHs in the current cell, which helps to make troubleshooting.
Measurement
Point

Unit
Related Features
Times
ZGB-03-02-005 GPRS-only (without voice) Timeslots Configurable
C901040009 Time of DL
PDCH congestion
Definition
Description
Time of DL PDCH congestion

This counter counts the time during which the service instance fails
to apply DL PDCHs (namely the total time of DL PDCH congestion).
If DL PDCH application fails, BSC records the congestion label and
the time when congestion starts. If DL PDCH application succeeds,
BSC clears the congestion label. When applying for DL PDCH, if
the congestion label is set, the current time minus the congestion
time of the previous record leaves the new congestion time.
Before DL PDCH is released, if the congestion label is set, such calculation repeats. When getting the periodic measurement value,
if the congestion label is set, such calculation repeats. The accumulation of these calculations makes the total time of DL PDCH
congestion.
Usage
536
This counter is used to find out the busyness of DL PDCH, which

may be used as a reference for whether more PDCHs should be
configured.
Measurement
Point
Unit
The measurement is taken at three time points listed below:
Before DL PDCH attempts to occupy, if the congestion label is

set, this counter calculates the congestion time and accumulates them.
Before DL PDCH is released, if the congestion label is set, this

counter calculates the congestion time and accumulates them.
When reporting the measurement data periodically, if the congestion label is set, this counter calculates the congestion time
and accumulates them.
Second
C901040010 Time of UL
PDCH congestion
Definition
Description
Time of UL PDCH congestion

This counter counts the time during which the service instance fails
to apply UL PDCHs (namely the total time of UL PDCH congestion).
If UL PDCH application fails, BSC records the congestion label and
the time when congestion starts. If UL PDCH application succeeds,
BSC clears the congestion label. When applying for UL PDCH, if
the congestion label is set, the current time minus the congestion
time of the previous record leaves the new congestion time.
Before UL PDCH is released, if the congestion label is set, such calculation repeats. When getting the periodic measurement value,
if the congestion label is set, such calculation repeats. The accumulation of these calculations makes the total time of UL PDCH
congestion.
Usage
Measurement
Point
Unit
This counter is used to find out the busyness of UL PDCH, which

configured.
Before UL PDCH attempts to occupy, if the congestion label is

set, this counter calculates the congestion time and accumulates them.
Before UL PDCH is released, if the congestion label is set, this

counter calculates the congestion time and accumulates them.
When reporting the measurement data periodically, if the congestion label is set, this counter calculates the congestion time
and accumulates them.
Second
537
C901040011 Time of PDCH

used at least one UL/DL TBF
exists
Definition
Time of PDCH used at least one UL /DL TBF exists
Description
When there is at least one UL TBF or DL TBF in one PDCH, this

PDCH is regarded to be used. This counter counts the time of
PDCH used. The value of the counter reflects the PDCH traffic.
Usage
This counter is used to find out the using of PDCHs, which may be
used as a reference for whether more PDCHs should be configured.
Measurement
Point
Unit
Related Features
When PDCH resource is acquired successfully, this counter calculates and accumulates.
When PDCH resource is released, this counter calculates and

accumulates.
When reporting the measurement data periodically, this

counter calculates and accumulates.
Second

used at least one UL/DL
EGPRS TBF exists
Definition
Description
When there is at least one UL EGPRS TBF or DL EGPRS TBF in one

PDCH, this PDCH is regarded to be used by EGPRS. This counter
counts the time of PDCH used by EGPRS. The value of the counter
reflects the PDCH traffic.
Usage
This counter is used to find out the using of EGPRS in PDCH, which
configured.
Measurement
Point
Unit
538
Time of PDCH used at least one UL /DL EGPRS TBF exists

accumulates.

Second
Related Features

used at least one DL TBF
exists
Definition
Time of PDCH used at least one DL TBF exists
Description
When there is at least one DL TBF in one PDCH, this PDCH is regarded to be used. This counter counts the time of PDCH used by
DL. The value of the counter reflects the PDCH traffic.
Usage
Measurement
Point
Unit
Related Features

accumulates.

Second

used at least one UL TBF
exists
Definition
Time of PDCH used at least one UL TBF exists
Description
When there is at least one UL TBF in one PDCH, this PDCH is regarded to be used. This counter counts the time of PDCH used by
UL. The value of the counter reflects the PDCH traffic.
Usage
Measurement
Point

accumulates.
539
Unit
Related Features

Second
immediate assignment on
AGCH
Definition
Number of immediate assignment on AGCH
Description
This counter counts the number of Imm Assign message sent on

AGCH by BSC.
Usage
This counter is used to find out the frequency of sending Imm Assign
message on AGCH by BSC in the current cell.
Measurement
Point
If BSC starts UL single block or UL TBF channel assignment, when

non-DRX MS assigns DL TBF, the counter increments. The measurement points are A1 and A2 as shown in Figure 620 and Figure
621.
FIGURE 620 SENDING INSTANT ASSIGNMENT MESSAGE BY AGCH CHANNEL
(1)
540

(2)
Unit
Times
paging PS requests on PCH
Definition
Number of paging PS requests on PCH
Description
This counter counts the number of Paging PS message sent on PCH

by BSC.
Usage
This counter is used to find out the frequency of sending Paging

PS message on PCH by BSC in the current cell.
Measurement
Point
When BSC sends Paging PS message on PCH, the counter increments. The measurement point is A as shown in Figure 622.
FIGURE 622 SENDING PS PAGING BY PCH CHANNEL
Unit
Related Features
Times
541
paging CS requests on PCH
Definition
Number of paging CS requests on PCH
Description
This counter counts the number of Paging CS message sent on

PCH by BSC.
Usage

CS message on PCH by BSC in the current cell.
Measurement
Point
When BSC sends Paging CS message on PCH, the counter increments. The measurement point is A as shown in Figure 623.
FIGURE 623 SENDING CS PAGING BY PCH CHANNEL
Unit
Related Features
Times
PCH
Definition
542
Number of immediate assignment on PCH
Description
This counter counts the number of Imm Assign message sent on PCH
by BSC.
Usage
message on PCH by BSC in the current cell.
Measurement
Point
If BSC starts to establish DL TBF, when DRX MS sends Imm Assign

message on PCH, the counter increments. The measurement point
is A2, as shown in Figure 624.
Unit
Times
PAGCH
Definition
Number of immediate assignment on PAGCH
Description

PAGCH by BSC.
Usage
This counter is used to find out the frequency of sendingImm Assign

message on PAGCH by BSC in the current cell.
Measurement
Point
If BSC starts UL single block or UL TBF channel assignment, when

non-DRX MS assigns DL TBF, the counter increments. The measurement points are A1 and A2, as shown in Figure 625and Figure
626.
543
FIGURE 625 SENDING ASSIGNMENT MESSAGE BY PAGCH CHANNEL (1)
FIGURE 626 SENDING ASSIGNMENT MESSAGE BY PAGCH CHANNEL (2)
Unit
Times
paging PS requests on
PPCH
Definition
544
Number of PS paging requests on PPCH
Description
This counter counts the number of Paging PS message sent on

PPCH by BSC.
Usage

PS message on PPCH by BSC in the current cell.
Measurement
Point
When BSC sends Paging PS message on PPCH, the counter increments. The measurement point is A, as shown in Figure 627.
FIGURE 627 SENDING PS PAGING BY PCH CHANNEL
Unit
Related Features
Times
paging CS requests on
PPCH
Definition
Number of CS paging requests on PPCH
Description
This counter counts the number of Paging CS message sent on

PPCH by BSC.
Usage

CS message on PPCH by BSC in the current cell.
Measurement
Point
When BSC sends Paging CS message on PPCH, the counter increments. The measurement point is A, as shown in Figure 628.
FIGURE 628 SENDING CS PAGING BY PCH CHANNEL
545
Unit
Related Features
Times
PPCH
Definition
Number of immediate assignment on PPCH
Description

PPCH by BSC.
Usage
message on PPCH by BSC in the current cell.
Measurement
Point
If BSC starts to establish DL TBF, when DRX MS sends Imm Assign

message on PPCH, the counter increments. The measurement
FIGURE 629 SENDING ASSIGNMENT MESSAGE BY PAGCH CHANNEL
Unit
Times
Packet Channel Request on
PRACH
Description
546
This counter counts the number of EGPRS Packet Channel Request

message or Packet Channel Request message received by BSC on
PRACH.
Usage
This counter is used to find out the load of PRACH in the current
cell, which may be used as a reference for whether more PRACHs
should be configured.
Measurement
Point
When BSC receives EGPRS Packet Channel Request message or

Packet Channel Request message, the counter increments. The
FIGURE 630 NUMBER OF PACKET CHANNEL REQUESTS ON PRACH
Unit
Times
C901040027 Sum of Abis

TS used sampling
Definition
Sum of Abis TS used sampling
Description
This counter counts the total number of used Abis TS under TDM
connection between BSC and BS.
Usage
This counter is used to find out the sum of Abis TS used sampling.
It is one of the parameters to observe the Abis TS using.
Measurement
Point
When the database of BSC starts to assign Abis TS, the counter
accumulates.
Unit
Times
Abis TS used sampling
Definition
Number of Abis TS used sampling
Description
This counter counts the number of Abis TS assignments by database.
Usage
This counter is used to find out the frequency of Abis TS assignment sampling. It is one of the parameters to observe the Abis TS
using.
547
Measurement
Point
Unit
When the database assigns Abis TS, the counter increments.

Times
C901040029 Sum of PDCH

used sampling
Definition
Sum of PDCH used sampling
Description
This counter counts the sum of PDCHs assigned by database when

service processing module starts PS channel request.
Usage
This counter is used to find out the sum of PDCHs assigned by

database when service processing module starts PS channel request. It is one of the parameters to observe multi-TS using when
assigning PS channels in the current cell.
Measurement
Point
When service processing module starts PS channel request and

database assigns PDCH, the counter accumulates.
Unit
Times
PDCH used sampling
Definition
Number of PDCH used sampling
Description
This counter counts the number of PDCH assigning attempts by

database when service processing module starts PS channel request.
Usage
This counter is used to find out the frequency of PDCH assigning

by database when service processing module starts PS channel
request. It is one of the parameters to observe multi-TS using
when assigning PS channels in the current cell.
Measurement
Point
When service processing module starts PS channel request and

database assigns PDCH, the counter increments.
Unit
Times
C901040031 Maximum
value of Abis TS used to CS
Definition
548
Maximum value of Abis TS used to CS
Description
This counter counts the maximum value of Abis timeslot used in

CS service in the cell within the measurement period; for IP-access sites, it counts the maximum bandwidth occupied by CS service. This counter reflects the transcient occupation and the busiest level of Abis resource in the cell's CS service.
Usage
This counter is used to find out the Abis resource occupation in the
cell's CS service, which helps adjust the usage of Abis resource.
Measurement
Point
The counter counts when CS user requests for the Abis resource
successfully.
Unit
Number of (TDM access)/kbps (IP access)
C901040032 Minimum value

of Abis TS used to CS
Definition
Minimum value of Abis TS used to CS
Description
This counter counts the minimum value of Abis timeslot used in CS

service in the cell within the measurement period; for IP-access
sites, it counts the minimum bandwidth occupied by CS service.
Usage
cell's CS service, which helps adjust the usage of Abis resource.
Measurement
Point
The counter counts when CS user requests for the Abis resource
successfully or releases the Abis resource successfully.
Unit
C901040033 Total value of

the regular sampling used to
CS
Definition
Total value of the regular sampling used to CS
Description
The counter accumulates at each measurement point. It counts

the accumulated Abis timeslot used by CS service within the
measurement period; for IP-access sites, it counts the accumulated bandwidth occupied by CS service. With this counter
and C901040034, the system can get the average usage of Abis
resource occupied by CS service within the measurement period.
Usage
This counter reflects the average occupation of Abis resource in

CS service.
Measurement
Point
The counter accumulates when CS user requests for the Abis resource successfully or releases the Abis resource successfully.
Unit
549
sampling of CS
Definition
Number of sampling of CS
Description
The counter increments at the measurement point of C901040033.

This counter and C901040033 reflect the average occupation of
Abis resource in the cell's CS service.
Usage
This counter reflects the average occupation of Abis resource in

CS service.
Measurement
Point
The counter accumulates when CS user requests for the Abis resource successfully or releases the Abis resource successfully.
Unit
C901040035 Maximum
value of Abis TS used to PS
Definition
Maximum value of Abis TS used to PS
Description
This counter counts the maximum value of Abis timeslot used in

PS service in the cell within the measurement period; for IP-access sites, it counts the maximum bandwidth occupied by PS service. This counter reflects the transcient occupation and the busiest level of Abis resource in the cell's PS service.
Usage
cell's PS service, which helps adjust the usage of Abis resource.
Measurement
Point
The counter counts when PS user requests for the Abis resource
successfully.
Unit

of Abis TS used to PS
Definition
550
Minimum value of Abis TS used to PS
Description
This counter counts the minimum value of Abis timeslot used in PS

service in the cell within the measurement period; for IP-access
sites, it counts the minimum bandwidth occupied by PS service.
Usage
cell's PS service, which helps adjust the usage of Abis resource.
Measurement
Point
The counter counts when PS user requests for the Abis resource
successfully or releases the Abis resource successfully.
Unit

the regular sampling used to
PS
Definition
Total value of the regular sampling used to PS
Description
The counter accumulates at each measurement point. It counts

the accumulated Abis timeslot used by PS service within the
measurement period; for IP-access sites, it counts the accumulated bandwidth occupied by PS service. With this counter
and C901040038, the system can get the average usage of Abis
resource occupied by PS service within the measurement period.
Usage
This counter reflects the average occupation of Abis resource in PS

service.
Measurement
Point
The counter accumulates when PS user requests for the Abis resource successfully or releases the Abis resource successfully.
Unit
sampling of PS
Definition
Number of sampling of PS
Description

Abis resource in the cell's PS service.
Usage
This counter reflects the average occupation of Abis resource in PS

service.
Measurement
Point
The counter accumulates when PS user requests for the Abis resource successfully or releases the Abis resource successfully.
Unit
C901040039 MAX CS used

number of exclusive ABIS
Description
This counter counts the maximum number of Abis timeslots occupied by CS service in the cell. Upon the request of releasing CS
551
channel, the system checks the total number of Abis timeslots occupied by CS service in the cell. If the number is larger than the
current value, then update the value.
Usage
This counter is used to find out the usage of Abis timeslots occupied
by CS service in the cell.
Measurement
Point
The counter counts upon channel conversion due to request of

releasing CS channel and refreshing dynamic CS channel.
C901040040 MIN CS used

Description
This counter counts the minimum number of Abis timeslots occupied by CS service in the cell. Upon the request of releasing CS
channel, the system checks the total number of Abis timeslots occupied by CS service in the cell. If the number is less than the
Usage
by CS service in the cell.
Measurement
Point

releasing CS channel and refreshing dynamic CS channel.
C901040041 MAX PS used

Description
This counter counts the maximum number of Abis timeslots occupied by PS service in the cell. Upon the request of releasing PS
channel, the system checks the total number of Abis timeslots occupied by PS service in the cell. If the number is larger than the
Usage
by PS service in the cell.
Measurement
Point

releasing PS channel and refreshing dynamic PS channel.
C901040042 MIN PS used

Description
552
This counter counts the minimum number of Abis timeslots occupied by PS service in the cell. Upon the request of releasing PS
channel, the system checks the total number of Abis timeslots oc-
cupied by PS service in the cell. If the number is less than the

Usage
by PS service in the cell.
Measurement
Point

releasing PS channel and refreshing dynamic PS channel.
C901040043 Average
Number of GPRS User
Description
This counter counts the average number of GPRS users in the cell
and site within the measurement period.
Usage
This counter is used to find out the average number of GPRS users
in current cell.
Measurement
Point
The counter counts in the four following cases.

1. The counter increments after one phase access receives the
indication message.
2. The counter increments after two phase access sends the resource request to user plane.
3. The counter increments after it receives downlink assignment
requests.
4. The counter decrements while RANPS instance is released.
Unit
Times
C901040044 Maximum
number of GPRS User
Description
This counter counts the maximum number of GPRS users in the

cell and site within the measurement period.
Usage
This counter is used to find out the maximum number of GPRS

users in current cell within the measurement period.
Measurement
Point
For the counter C901040043, if the maximum number of users is

less than the average number of users, use the average number
of users to update the maximum number of users. Otherwise, it
is kept unchanged.
Unit
Times
553
C901040045 Average
Number of EGPRS User
Description
This counter counts the average number of EGPRS users in the cell
and site within the measurement period.
Usage
This counter is used to find out the maximum number of EGPRS

Measurement
Point

1. The counter increments after one phase access receives the
indication message.
2. The counter increments after two phase access sends the resource request to user plane.
3. The counter increments after it receives downlink assignment
requests.
4. The counter decrements while RANPS instance is released.
Unit
Times
C901040046 Maximum
number of EDGE User
Description
This counter counts the maximum number of EDGE users in the

cell and site within the measurement period.
Usage
This counter is used to find out the maximum number of EDGE

Measurement
Point
For the counter C901040043, if the maximum number of users is

less than the average number of users, use the average number
of users to update the maximum number of users. Otherwise, it
is kept unchanged.
Unit
Times
C901040047 Number
of assigned uplink radio
channels
554
Description
This counter counts the number of assigned uplink radio channels

in the cell and site within the measurement period.
Usage
This counter counts the number of assigned uplink radio channels

Measurement
Point

1. Counts in single allocated resource block
2. Counts in allocated radio resource
3. Counts in uplink DTM assignment
4. Counts in downlink DTM assignment
Unit
Times
assigned downlink radio
channels
Description
This counter counts the number of assigned downlink radio channels in the cell and site within the measurement period.
Usage
This counter counts the number of assigned downlink radio channels in the cell and site within the measurement period.
Measurement
Point
The counter counts in the following three cases.

1. Counts in allocated radio resource
2. Counts in uplink DTM assignment
3. Counts in downlink DTM assignment
Unit
Times
requested uplink radio
channels
Description
This counter counts the number of requested uplink radio channels

Usage
This counter counts the number of requested uplink radio channels

Measurement
Point
Unit
Consistent with that for C901040047.

Times
555
requested downlink radio
channels
Description
This counter counts the number of requested downlink radio channels in the cell and site within the measurement period.
Usage
This counter counts the number of requested downlink radio channels in the cell and site within the measurement period.
Measurement
Point
Unit
Consistent with that for C901040048.

Times
C901040051 Number of PS
channel expand
Description
This counter counts the number of attempts of channel expansion

in PS service.
Usage
This counter is used to find out the frequency of channel expansion

initiated by database.
Measurement
Point
Unit
The counter counts when the RANUMC module receives the

EV_DBS_PSCHANEXPAND message.
Times
channel expand perform
Description
This counter counts the number of channel expansions in PS service.
Usage
This counter is used to find out the number of channel expansions

executed by RANPS.
Measurement
Point
Unit
556
This counter counts when the RANPS module receives the

EV_RANUMC_PSCHANEXPAND message.
Times
channel expand success
Description
This counter counts the number of successful channel expansions

in PS service.
Usage
This counter is used to find out the number of successful channel

expansions executed by RANPS.
Measurement
Point
Unit
This counter counts when the RANPS module successfully requests

the resource for expansion from database.
Times
557
558
Chapter
11
RMM Assignment
Measurement
Table of Contents
Overview........................................................................ 561
C901050001 Number of general assignment executions for
voice channel.................................................................. 561
C901050002 Number of assignments attempts for voice due
to forced release ............................................................. 562
C901050003 Number of assignment executions for voice
channel due to forced release............................................ 563
C901050004 Number of handover attempts for voice due to
forced release ................................................................. 564
C901050005 Number of handover executions for voice channel due to forced release .................................................. 565
C901050006 Number of assignments for voice channel due to
queuing ......................................................................... 566
C901050007 Number of assignments for execution for voice
channel due to queuing .................................................... 567
C901050008 Duration of assignment success voice channel
due to queuing................................................................ 568
C901050009 Number of assignments success for voice channel due to queuing........................................................... 569
C901050010 Number of assignments for directed retry attempts for voice channel .................................................. 570
channel due to directed retry ............................................ 571
C901050012 Number of general assignments for execution
for data.......................................................................... 572
C901050013 Number of assignments attempts for data due
C901050014 Number of assignment executions for data due
C901050015 Number of handover attempts for data due to
forced release ................................................................. 575
C901050016 Number of handover executions for data due to
forced release ................................................................. 576
to queuing...................................................................... 577
C901050018 Number of assignments for execution for data
due to queuing................................................................ 578
C901050019 Total duration of successful assignments for data
due to queuing................................................................ 579
C901050020 Number of assignments success for data due to
queuing ......................................................................... 580
to directed retry .............................................................. 581
559

to directed retry .............................................................. 582
C901050023 Number of assignment for retry attempts FDD
cell for voice channel ....................................................... 583
to directed retry to FDD cell for voice channel ..................... 584
C901050025 Number of assignment for retry attempts FDD
cell for data .................................................................... 585
to directed retry to FDD cell for data .................................. 586
C901050027 Number of assignment for retry attempts TDD
cell for voice channel ....................................................... 587
to directed retry to TDD cell for voice channel ..................... 588
C901050029 Number of assignment for retry attempts TDD
cell for data .................................................................... 589
to directed retry to TDD cell for data .................................. 590
C901050031 Assignment unsuccessful due to circuit obstruction ............................................................................... 591
C901050032 Assignment unsuccessful due to circuit obstruction unmatched ............................................................... 592
C901050033 Assignment unsuccessful due to no valid radio
resource......................................................................... 593
C901050034 Assignment unsuccessful due to other
causes ........................................................................... 594
C901050035 Number of assignments attempts due to forced
release (emergency service) ............................................. 595
C901050036 Number of assignment executions channel due
to forced release (emergency service) ................................ 596
C901050037 Number of assignment attempts due to forced
handover (emergency service) .......................................... 597
C901050038 Number of assignment executions channel due
to forced handover (emergency service) ............................. 598
C901050039 Number of assignments channel due to queuing
(emergency service) ........................................................ 599
C901050040 Number of assignments for execution channel
due to queuing (emergency service) .................................. 600
(assignment forced handover)........................................... 601
lower PRI user (assignment forced handover)...................... 602
C901050043 Number of received failure from lower PRI user
request resource for forced handover (assignment forced
handover) ...................................................................... 603
C901050044 Number of lower PRI user handover failure (assignment forced handover) ............................................... 604
C901050045 Number of time out for wait resource (assignment forced handover)..................................................... 605
C901050046 Number of forced release target not found (assignment forced release) .................................................. 606
C901050047 Number of time out for wait resource (assignment forced release)........................................................ 607
C901050048 Number of get before grab released channel (assignment forced handover) ............................................... 608
C901050049 Number of get before grab released channel(assignment forced release) .................................................. 609
C901050050 The count of Assignment using FULL IP A-Interface ............................................................................... 610
560
Chapter 11 RMM Assignment Measurement
C901050051 The count of Assignment using PCM over IP

A-Interface ..................................................................... 611
C901050052 The count of Assignment using PCM over TDM
A-Interface .................................................................... 612
"Requested Codec Type or Codec Configuration not supported" .......................................................................... 613
"Requested Codec Type or Codec Configuration unavailable" ............................................................................. 614
C901050055 The count of Assignment Failure caused by "Requested A-Interface Type not supported" ............................ 615
C901050056 The count of Assignment Failure caused by "Requested A-Interface Type unavailable" ................................ 616
C901050057 The count of Assignment Failure caused by "Call
Identifier already allocated" .............................................. 617
C901050058 The count of Assignment Failure caused by "Requested Redundancy Level not supported" .......................... 618
C901050059 The count of Assignment Failure caused by "Call
Access Control" ............................................................... 619
C901050060 Attempt Number of mode modify for assignment ............................................................................. 620
C901050061 Success Number of mode modify for assignment ............................................................................. 621
C901050062 Number of assignments for directed retry attempts for voice channel because of radio........................... 621
channel due to directed retry because of radio..................... 622
C901050064 Number of assignments for directed retry attempts for data channel because of radio............................ 623
C901050065 Number of assignments for execution for data
channel due to directed retry because of radio..................... 624
Overview
RMM assignment counter describers the assignment process. As
many attempts can be made if no channel is available in the first
assignment attempt, it is necessary to make a completed description of the whole assignment process instead of the assignment
processes of TCH/F or TCH/H. These counters are used to analyze
influences of forced release, queuing and directed retry, to assignment success rate from the viewpoint of calling.
C901050001 Number
of general assignment
executions for voice channel
Definition
Number of general assignment executions for voice channel
561
Description
The way for BSC to get TCH in voice channel assignment process
includes normal request, and queuing attempt or forced release
if normal request is failed. This counter counts the number of
general assignment executions for voice channel.
Usage
This counter is used to find out the number of available TCH in

normal request in voice channel assignment flow; this counter can
be used to check whether the cell has enough available radio resource.
Measurement
Point
In voice channel assignment flow, the counter increments when

source cell receives message that resource is available from target
cell after sending channel request, and successfully sends assignment command. The measurement point is A, as shown in Figure
631.
FIGURE 631 MEASUREMENT POINT OF GENERAL ASSIGNMENT EXECUTIONS
Unit
Times
assignments attempts for
voice due to forced release
Definition
Number of assignments attempts for voice due to forced release
Description
BSC attempts to allocate voice channel after receiving Radio App

message in assignment flow; if there is no proper channel available and the system allows forced release, then BSC carries out
forced release to other channels. This counter counts the number
of forced release.
Usage
This counter is used to find out the number of assignments for

forced release attempts in MS accessing process.
Measurement
Point
BSC fails in allocating channel due to no available resource. It

releases other channels forcedly when the system allows.
562
The counter increments when BSC fails in general voice channel

assignment and the system allows forced release and finds a
proper instance of forcing release that sends forced release

message to instance of forced release.
The counter increments when BSC fails in general voice channel

assignment and queuing attempt fails due to overtime and the
system allows forced release and there is a proper instance of
forced release that sends forced release message to instance
of forced release. The measurement point is A, as shown in
Figure 632.
FIGURE 632 MEASUREMENT POINT OF ASSIGNMENTS FOR FORCED RELEASE

ATTEMPTS
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
assignment executions for
voice channel due to forced
release
Definition
Number of assignment executions for voice channel due to forced

release
Description
BSC fails in allocating voice channel due to no available resource

and carries out forced release; if BCS gets required channel in
time, then the forced release succeeds. This counter counts the
number of assignment executions for voice channel due to forced
release.
Usage
This counter is used to find out the number of assignment executions for voice channel due to forced release in MS accessing
process.
563
Measurement
Point
The counter increments if radio resource request fails in voice

channel assignment, forced released can be carried out and instance of forcing release sends forced release message to instance
of forced release, and resource available message is received and
channel is obtained successfully. The measurement point is B, as
POINT OF ASSIGNMENT EXECUTIONS FOR VOICE

CHANNEL DUE TO FORCED RELEASE
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
handover attempts for voice
due to forced release
Definition
564
Number of handover attempts for voice due to forced release
Description
BSC attempts to operate outgoing handover to the cell voice channel for forced release when it fails in voice channel allocation due
to no available resource. The counter counts the number of handover for forced release attempts for voice channel.
Usage
This counter is used to find out the number of handover for forced
release attempts for voice channel in MS accessing process.
Measurement
Point
The counter increments when BSC fails in general voice channel assignment and the system allows forced release and there is
proper instance of forcing release that sends forced release message to instance of forced release. The measurement point is A,
POINT OF HANDOVER FOR FORCED RELEASE
ATTEMPTS
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
handover executions for
voice channel due to forced
release
Definition
Number of handover executions for voice channel due to forced

release
Description
BSC attempts to operate outgoing handover to the cell voice channel for forced release when it fails in voice channel allocation due
to no available resource. The counter counts the number of handover executions for voice channel due to forced release.
Usage
This counter is used to find out the number of handover executions

for voice channel due to forced release in MS accessing process.
Measurement
Point

channel assignment, handover for voice channel due to forced release can be carried out and instance of forcing handover sends
forced handover message to instance of forced handover, and resource available message is received and channel is obtained successfully. The measurement point is B, as shown in Figure 635.
565
FIGURE 635 MEASUREMENT POINT OF HANDOVER EXECUTIONS FOR VOICE

Unit
Related Features
Times
ZGO-01-03-001 eMLPP
assignments for voice
channel due to queuing
Definition
566
Number of assignments for voice channel due to queuing
Description
BSC attempts to assign voice channel after receiving Radio App

message in assignment flow; if there is no proper channel available and the system doesnt allow forced release or cant find
instance of forcing release but allows queuing, then the present
instance queues and waits till other resource releases. This
counter counts the number of assignments for queuing attempts
for voice channel.
Usage

queuing attempts for voice channel in MS accessing process.
Measurement
Point
The counter increments when BSC fails in general voice channel assignment and the system allows queuing and the instance
queues. The measurement point is A, as shown in Figure 636.
FIGURE 636 MEASUREMENT POINT OF ASSIGNMENTS FOR QUEUING

ATTEMPTS
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
assignments for execution
for voice channel due to
queuing
Definition
Number of assignments for execution for voice channel due to

queuing
Description
BSC fails in allocating voice channel due to no available resource

and carries out queuing; if BCS gets required channel in time,
then the queuing succeeds. This counter counts the number of
assignments for execution for voice channel due to queuing.
Measurement
Point

channel assignment, queuing can be carried out and instance of
queuing receives resource available message and obtains channel
successfully. The measurement point is B, as shown in Figure 637.
567
FIGURE 637 MEASUREMENT POINT OF ASSIGNMENTS

VOICE CHANNEL DUE TO QUEUING
Unit
Related Features
FOR
EXECUTION
FOR
Times
ZGO-01-03-001 eMLPP
assignment success voice
Definition
Description
Duration of assignment success voice channel due to queuing

This counter counts the total duration of successful assignment for
queuing voice channel in allocation process.
The duration of successful assignment for queuing for voice channel is the time when channel is obtained minus the time when the
instance began to queue. The counter accumulates the total durations of successful assignment for queuing for voice channel.
568
Usage
This counter is used to check the intra-cell queuing status and represents whether queuing can relieve traffic congestion effectively.
Measurement
Point
The counter accumulates duration of successful assignment for

queuing for voice channel if radio resource request fails in voice
successfully. The measurement points are A and B, as shown in
Figure 638.
FIGURE 638 MEASUREMENT POINT OF ASSIGNMENTS FOR EXECUTION FOR

Unit
Times
C901050009 Number
of assignments success
queuing
Definition
Number of assignments success for voice channel due to queuing
Description
This counter counts the number of successful assignments of queuing for voice channel.
Usage
Measurement
Point

successfully. The measurement point is B, as shown in Figure 639.
569

Unit
Times
assignments for directed
retry attempts for voice
channel
570
Definition
Number of assignments for directed retry attempts for voice channel
Description
If BSC fails in voice channel request, and source cell allows directed retry and target cell that meets the directed retry demand
can be selected from adjacent cells, then BSC carries out directed
retry. This counter counts the number of assignments for directed
retry attempts for voice channel.
Usage

directed retry attempts for voice channel and check whether the
cells radio environment can satisfy the traffic demand.
Measurement
Point
The counter increments when source cell receives no available radio resource message from target cell and source cell supports directed retry and target cell that meets the directed retry demand
can be found and Radio_App message is sent to target cell. The

ATTEMPTS
Unit
Related Features
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Times
ZGB-03-01-002 Directed Retry
ZGO-02-03-003 GERAN/UTRAN Load Sharing
directed retry
Definition
Number of assignments for execution for voice channel due to directed retry
Description
This counter counts the number of assignments for execution for

voice channel due to directed retry
Usage
This counter is used to check the process and result of directed

retry.
Measurement
Point
The counter increments when directed retry is carried out and target cell obtains channel successfully and source cell receives radio
resource available message from target cell in voice channel assignment process. The measurement point is B, as shown in Figure
641.
571

VOICE CHANNEL DUE TO DIRECTED RETRY
Unit
Related Features
FOR
EXECUTION
FOR
Times
general assignments for
execution for data
Definition
572
Number of general assignments for execution for data
Description
The way for BSC to get TCH in data channel assignment process
includes normal request, and queuing attempt or forced release
if normal request is failed. This counter counts the number of
general assignment executions for data channel.
Usage
This counter is used to find out the number of available TCH in

normal request in data channel assignment flow; this counter can
be used to check whether cell has enough available radio resource.
Measurement
Point
In data channel assignment flow, the counter increments when

source cell receives resource is available message from target cell
after sending channel request, and successfully sends assignment
command. The measurement point is A, as shown in Figure 642.
FIGURE 642 MEASUREMENT POINT OF GENERAL ASSIGNMENT EXECUTIONS
Unit
Times
data due to forced release
Definition
Number of assignments attempts for data due to forced release
Description
BSC attempts to allocate data channel after receiving Radio App

message in assignment flow; if there is no proper channel available and the system allows forced release, then BSC carries out
forced release to other channels. This counter counts the number
of forced release.
Usage

forced release attempts in MS accessing process.
Measurement
Point
BSC fails in allocating channel due to no available resource and

releases other channel forcedly when the system allows.
The counter increments when BSC fails in general data channel

assignment and the system allows forced release and there is
a proper instance of forcing release that sends forced release
message to instance of forced release.
The counter increments when BSC fails in general data channel

assignment and queuing attempt fails due to overtime and the
system allows forced release and finds a proper instance of
forcing release that sends forced release message to instance
of forced release. The measurement point is A, as shown in
Figure 643.
573
FIGURE 643 MEASUREMENT POINT OF ASSIGNMENTS FOR FORCED RELEASE

ATTEMPTS
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
Definition
574
Number of assignment executions for data due to forced release
Description
BSC fails in allocating data channel due to no available resource

and carries out forced release; if BCS gets required channel in
time, then the forced release succeeds. This counter counts the
number of assignment executions for data channel due to forced
release.
Usage
This counter is used to find out the number of assignment executions for data channel due to forced release in MS accessing
process.
Measurement
Point
The counter increments if radio resource request fails in data channel assignment, forced released can be carried out and instance of
forcing release sends forced release message to instance of forced
release, and resource available message is received and channel is
obtained successfully. The measurement point is B, as shown in
Figure 644.
FIGURE 644 MEASUREMENT POINT OF ASSIGNMENT EXECUTIONS

Unit
Related Features
FOR
VOICE
Times
ZGO-01-03-001 eMLPP
handover attempts for data
Definition
Number of handover attempts for data due to forced release
Description
BSC attempts to operate outgoing handover to the cell data channel for forced release when it fails in data channel allocation due
to no available resource. The counter counts the number of handover for forced release attempts for data channel.
Usage
This counter is used to find out the number of handover for forced
release attempts for data channel in MS accessing process.
Measurement
Point
The counter increments when BSC fails in general data channel assignment and the system allows forced release and there is proper
instance of forcing release that sends forced release message to instance of forced release. The measurement point is A, as shown
in Figure 645.
575

ATTEMPTS
Unit
Related Features
OF
HANDOVER
FOR
FORCED RELEASE
Times
ZGO-01-03-001 eMLPP
handover executions for
Definition
576
Number of handover executions for data due to forced release
Description
BSC attempts to operate outgoing handover to the cell data channel for forced release when it fails in data channel allocation due
to no available resource. The counter counts the number of handover executions for data channel due to forced release.
Usage
This counter is used to find out the number of handover executions

for data channel due to forced release in MS accessing process.
Measurement
Point
The counter increments if radio resource request fails in data

channel assignment, handover for data channel due to forced
release can be carried out and instance of forcing handover
sends forced handover message to instance of forced handover,
and resource availablemessage is received and channel is obtained
successfully. The measurement point is B, as shown in Figure
646.

Unit
Related Features
Times
ZGO-01-03-001 eMLPP
data due to queuing
Definition
Number of assignments attempts for data due to queuing
Description
BSC attempts to assign data channel after receiving Radio App message in assignment flow; if there is no proper channel available
and the system doesnt allow forced release or cant find instance
of forcing release but allows queuing, then the present instance
queues and waits till other resource releases. This counter counts
the number of assignments for queuing attempts for data channel.
Usage

queuing attempts for data channel in MS accessing process.
Measurement
Point
The counter increments when BSC fails in general data channel assignment and the system allows queuing and the instance queues.
577

ATTEMPTS
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
for data due to queuing
Definition
578
Number of assignments for execution for data due to queuing
Description
BSC fails in allocating data channel due to no available resource

and carries out queuing; if BCS gets required channel in time,
then the queuing succeeds. This counter counts the number of
assignments for execution for data channel due to queuing.
Measurement
Point
The counter increments if radio resource request fails in data channel assignment, queuing can be carried out and instance of queuing receives resource available message and obtains channel successfully. The measurement point is B, as shown in Figure 648.

Unit
Related Features
Times
ZGO-01-03-001 eMLPP
C901050019 Total duration

of successful assignments
for data due to queuing
Definition
Description
Total duration of successful assignments for data due to queuing

This counter counts the total duration of successful assignment for
queuing for data channel in allocation process.
The duration of successful assignment for queuing for data channel is the time when channel is obtained minus the time when the
instance began to queue. The counter accumulates the total durations of successful assignment for queuing for data channel.
Usage
Measurement
Point
The counter accumulates duration of successful assignment for

queuing for data channel if radio resource request fails in data
successfully. The measurement points are A and B, as shown in
Figure 649.
579

Unit
Times
assignments success for
data due to queuing
580
Description
This counter counts the number of successful assignments of queuing for data channel.
Usage
Measurement
Point
The counter increments if radio resource request fails in data channel assignment, queuing can be carried out and instance of queuing receives resource available message and obtains channel successfully. The measurement point is B, as shown in Figure 650.

Unit
Times
data due to directed retry
Definition
Number of assignments attempts for data due to directed retry
Description
If BSC fails in data channel request, and source cell allows directed
retry and target cell that meets the directed retry demand can be
selected from adjacent cells, then BSC carries out directed retry.
This counter counts the number of assignments for directed retry
attempts for data channel.
Usage

directed retry attempts for data channel and check whether the
cells radio environment can satisfy the traffic demand.
Measurement
Point
The counter increments when source cell receives no available radio resource message from target cell and source cell supports directed retry and target cell that meets the directed retry demand
can be found and Radio_App message is sent to target cell. The
581

ATTEMPTS
Unit
Related Features
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Times
data due to directed retry
Definition
582
Number of assignment executions for data due to directed retry
Description
This counter counts the number of assignments for execution for

data channel due to directed retry
Usage
This counter is used to check the process and result of directed

retry.
Measurement
Point
The counter increments when directed retry is carried out and target cell successfully obtains channel and source cell receives radio
resource available message from target cell in data channel assignment process. The measurement point is B, as shown in Figure
652.

Unit
Related Features
FOR
EXECUTION
FOR
Times
C901050023 Number
of assignment for retry
attempts FDD cell for voice
channel
Definition
Number of assignment for retry attempts FDD cell for voice channel
Description
This counter counts the number of assignment for retry attempts

FDD cell for voice channel.
Usage
This counter is used to find out the number of assignment for retry
attempts FDD cell for voice channel and represent FDD cell traffic
sharing status in voice channel assignment.
Measurement
Point
The counter increments in voice channel assignment when source

cell receives no available radio resource message from FDD cell and
source cell supports directed retry and FDD cell that meets the
directed retry demand can be found and Radio_App message is sent
to FDD cell. The measurement point is A, as shown in Figure 653.
583

ATTEMPTS
Unit
Related Features
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Times
ZGO-02-02-014 IMSI Based Handover
ZGO-02-03-002 GSM/WCDMA Interworking
data due to directed retry to
FDD cell for voice channel
584
Definition
Number of assignment executions for data due to directed retry to

FDD cell for voice channel
Description
This counter counts the number of assignment executions due to

directed retry to FDD cell for voice channel.
Usage
This counter is used to find out the number of assignment executions due to directed retry to FDD cell for voice channel and
represent FDD cell directed retry status.
Measurement
Point
The counter increments in voice channel assignment when target

cell in directed retry is FDD cell and successfully obtains channel
and source cell receives resource available message from target
cell. The measurement point is B, as shown in Figure 654.

Unit
Related Features
FOR
EXECUTION
FOR
Times
C901050025 Number
attempts FDD cell for data
Definition
Number of assignment for retry attempts FDD cell for data
Description

FDD cell for data channel.
Usage
attempts FDD cell for data channel and represent FDD cell traffic
sharing status in data channel assignment.
Measurement
Point
The counter increments in data channel assignment when source

cell receives no available radio resource message from FDD cell and
source cell supports directed retry and FDD cell that meets the
to FDD cell. The measurement point is A, as shown inFigure 655.
585

ATTEMPTS
Unit
Related Features
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Times
FDD cell for data
586
Definition

FDD cell for data
Description

directed retry to FDD cell for data channel.
Usage
This counter is used to find out the number of assignment executions due to directed retry to FDD cell for data channel and
represent FDD cell directed retry status.
Measurement
Point
The counter increments in data channel assignment when target

cell in directed retry is FDD cell and successfully obtains channel
and source cell receives radio resource available message from target cell. The measurement point is B, as shown in Figure 656.

Unit
Related Features
FOR
EXECUTION
FOR
Times
C901050027 Number
attempts TDD cell for voice
channel
Definition
Number of assignment for retry attempts TDD cell for voice channel
Description

TDD cell for voice channel.
Usage
attempts TDD cell for voice channel and represent TDD cell traffic
sharing status in voice channel assignment.
Measurement
Point
The counter increments in voice channel assignment when source

cell receives no available radio resource message from TDD cell and
source cell supports directed retry and TDD cell that meets the
to TDD cell. The measurement point is A, as shown in Figure 657.
587

ATTEMPTS
Unit
Related Features
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Times
TDD cell for voice channel
588
Definition

TDD cell for voice channel
Description

directed retry to TDD cell for voice channel.
Usage
This counter is used to find out the number of assignment executions due to directed retry to TDD cell for voice channel and
represent TDD cell directed retry status.
Measurement
Point
The counter increments in voice channel assignment when target

cell in directed retry is TDD cell and successfully obtains channel

Unit
Related Features
FOR
EXECUTION
FOR
Times
C901050029 Number
attempts TDD cell for data
Definition
Number of assignment for retry attempts TDD cell for data
Description

TDD cell for data channel.
Usage
attempts TDD cell for data channel and represent TDD cell traffic
sharing status in data channel assignment.
Measurement
Point
The counter increments in data channel assignment when source

cell receives no available radio resource message from TDD cell and
source cell supports directed retry and TDD cell that meets the
to TDD cell. The measurement point is A, as shown in Figure 659.
589

ATTEMPTS
Unit
Related Features
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Times
TDD cell for data
590
Definition

TDD cell for data
Description

directed retry to TDD cell for data channel.
Usage
This counter is used to find out the number of assignment executions due to directed retry to TDD cell for data channel and
represent TDD cell directed retry status.
Measurement
Point
The counter increments in data channel assignment when target

cell in directed retry is TDD cell and successfully obtains channel

Unit
Related Features
FOR
EXECUTION
FOR
Times
C901050031 Assignment
unsuccessful due to circuit
obstruction
Definition
Assignment unsuccessful due to circuit obstruction
Description
This counter counts the number of the assignment failure due to

circuit obstruction on A-interface.
Usage
This counter is used to find out the number of assignment failure

due to circuit obstruction on A-interface and to check circuit obstruction status on A-interface in assignment flow.
Measurement
Point
Target cell checks circuit after receiving assignment request message

sent by MSC; the counter increments if the circuit is obstructed.
591
FIGURE 661 MEASUREMENT POINT OF ASSIGNMENT FAILURE

CIRCUIT OBSTRUCTION ON A-INTERFACE
Unit
DUE TO
Times
unsuccessful due to circuit
obstruction unmatched
Definition
592
Assignment unsuccessful due to circuit obstruction unmatched
Description
This counter counts the number of assignment failure due to circuit

unmatched on A-interface.
Usage

due to circuit unmatched on A-interface and to check circuit unmatched status on A-interface in assignment flow.
Measurement
Point
Target cell checks circuit after receiving assignment request message

sent by MSC; the counter increments if the circuit is unmatched.

Unit
DUE TO
Times
unsuccessful due to no valid
radio resource
Definition
Assignment unsuccessful due to no valid radio resource
Description
This counter counts the number assignment failure due to no valid

radio resource.
Usage

due to no valid radio resource and to check radio resource assignment status in assignment flow.
Measurement
Point
Source cell sends channel request to target cell after receiving

assignment request message; the counter increments if channel
request fails due to no valid radio resource. The measurement
Source cell sends channel request to target cell after receiving assignment request message; the counter increments if Radio_App is overtime due to no responding message. The measurement point is A, as shown inFigure 663.
593

Unit
DUE TO
Times
unsuccessful due to other
causes
Definition
594
Assignment unsuccessful due to other causes
Description
This counter counts the number assignment failure due to other

causes on A-interface.
Usage

due to other causes and to check A-interface status in assignment
flow.
Measurement
Point
Target cell receives assignment request message sent by MSC; the

counter increments if assignment failure on A-interface is caused
by other causes (instead of the causes mentioned above, such as
circuit obstruction, circuit unmatched and no valid radio resource).

Unit
DUE TO
Times
assignments attempts due to
forced release (emergency
service)
Definition
Number of assignment attempts due to forced release (emergency

service)
Description
In the assignment flow, after BSC receives the RADIO_APPLY message, it attempts to assign the voice channel. If there is no suitable channel and forced release is allowed, then it releases other
channels forcibly, if this call is an emergency call, then this counter
counts the number of forced release attempts.
Usage
This counter is used to find out the number of assignment attempts

due to forced release during the MS access process of an emergency call.
Measurement
Point
BSC fails to assign channel due to no available resource, if forced

release is allowed, BSC will forcibly release other channels.
During an emergency call, BSC fails to assign voice channel. If
forced release is allowed and there is suitable forced release instance, then the counter increments when the forcing release instance sends the forced release message to the forced release
instance. The measurement point is A, as shown in Figure 665.
595
FIGURE 665 MEASUREMENT POINT OF NUMBER OF ASSIGNMENT ATTEMPTS

DUE TO FORCED RELEASE (EMERGENCY SERVICE)
Unit
Times
assignment executions
channel due to forced
release (emergency service)
596
Definition
Number of assignment executions channel due to forced release

(emergency service)
Description
BSC fails to assign voice channel due to no available resource, if

it obtains needed channel within specified time after the forced
release is performed, then the forced release is considered successful. If the call is an emergency call, the counter counts the
number of successful forced releases (emergency service).
Usage
This counter is used to find out the number of successful assignments due to forced release during the MS access process of an
emergency call.
Measurement
Point
During the voice channel assignment process, if the radio resource

request fails and forced release is allowed, the forcing release instance sends the forced release message to the forced release instance. If the message of resource available is received, then the
resource is obtained successfully, and in this case, the counter increments. The measurement point is B, as shown in Figure 666.

Unit
Times
assignment attempts due to
forced handover (emergency
service)
Definition
Number of assignment attempts due to forced handover (emergency service)
Description
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If the
call is an emergency call, the counter counts the number of forced
handover attempts.
Usage

due to forced handover during the MS access process of an emergency call.
Measurement
Point

forced handover is allowed and there is suitable forcing handover
instance, then the counter increments when the forcing handover
instance sends the forced handover message to the forced handover instance. The measurement point is A, as shown in Figure
667.
597

ATTEMPTS
Unit
OF
HANDOVER
FOR
FORCED RELEASE
Times
assignment executions
channel due to forced
handover (emergency
service)
598
Definition
Number of assignment executions channel due to forced handover(emergency service)
Description
call is an emergency call, the counter counts the number of successful forced handover.
Usage
This counter is used to find out the number of successful assignments due to forced handover during the MS access process of an
emergency call.
Measurement
Point
During the voice channel assignment process for emergency call, if

the radio resource request fails and forced handover is allowed, the
forcing handover instance sends the forced handover message to
the forced handover instance. If the message of resource available
is received, then the resource is obtained successfully, and in this
case, the counter increments. The measurement point is B, as

Unit
Times
assignments channel due
to queuing (emergency
service)
Definition
Number of assignments channel due to queuing (emergency service)
Description
In the assignment flow, after BSC receives the RADIO_APPLY message, it attempts to assign the voice channel. If there is no suitable channel and queuing is allowed, then the instance enters the
queuing state and waits for other resource to be released, if this
call is an emergency call, then this counter counts the number of
queuing attempts (emergency service).
Usage

due to queuing during the MS access process of an emergency call.
Measurement
Point

queuing is allowed, then the instance is added to the queue and
Figure 669.
599

ATTEMPTS
Unit
Times
(emergency service)
600
Definition
Number of assignments for execution channel due to queuing

(emergency service)
Description
During an emergency call, BSC fails to assign voice channel due to

no available resource but obtains needed channel within specified
time after the queuing is performed (no forced handover or forced
release is performed). In this case, the queuing is considered successful, the counter counts the number of successful assignments
due to queuing (emergency service).
Usage
This counter is used to find out the number of successful assignments due to queuing during the MS access process of an emergency call.
Measurement
Point

request fails and queuing is allowed, the counter increments when
the queuing instance receives the message of resource available
and obtains resource successfully. The measurement point is B,
FIGURE 670 MEASUREMENT POINT OF ASSIGNMENTS FOR EXECUTION

FOR VOICE CHANNEL DUE TO QUEUING
Unit
Times
forced handover target not
found (assignment forced
handover)
Definition
Number of forced handover target not found (assignment forced

handover)
Description
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If no
forcing handover instance is found in the cell, the counter counts
the number of times that forcing handover target instance is not
found.
Usage
During forced handover for voice channel assignment, this counter

is used to find out the number of times that forced handover target
instance is not found.
Measurement
Point

forced handover is allowed but there is no suitable forced handover
instance, then the counter increments. The measurement point is
601
FIGURE 671 MEASUREMENT POINT OF NUMBER OF FORCED HANDOVER

TARGET NOT FOUND (ASSIGNMENT FORCED HANDOVER)
Unit
Times
send forced handover
request to lower PRI
user (assignment forced
handover)
602
Definition
Number of send forced handover request to lower PRI user (assignment forced handover)
Description
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If forced
handover target instance is found in the cell, the counter counts
the number of forced handover requests sent to low priority users
during the force handover.
Usage
During the voice channel assignment of MS access process, this

counter is used to find out the number of forced handover requests
when the forcing handover instance is found.
Measurement
Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forcing handover instance, then the
counter increments when the forcing handover instance sends the
forced handover message to the forced handover instance. The

ATTEMPTS
Unit
OF
HANDOVER
FOR
FORCED RELEASE
Times
C901050043 Number
of received failure from
lower PRI user request
resource for forced
handover (assignment
forced handover)
Definition
Number of received failure from lower PRI user request resource

for forced handover (assignment forced handover)
Description
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If forcing handover target instance is found in the cell, the forced handover is initiated. Then, if the forced handover fails due to resource request failure, the counter counts the number of receiving
resource request failure message from low priority user during the
forced handover.
Usage
During the forced handover for voice channel assignment in MS

access process, this counter is used to find out the number of
receiving the forced handover failure message due to resource request failure.
Measurement
Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forcing handover instance, then the
603
counter increments in the following case: the forcing handover instance sends the forced handover message to the forced handover
instance and simultaneously receives the forced handover failure
message which is due to resource request failure. The measurement point is B, as shown in Figure 673.
FIGURE 673 MEASUREMENT POINT OF NUMBER OF RECEIVING FORCED
HANDOVER FAILURE MESSAGE FROM LOW PRIORITY USER DURING FORCED
HANDOVER
Unit
Times
lower PRI user handover
failure (assignment forced
handover)
604
Definition
Number of lower PRI user handover failure (assignment forced

handover)
Description
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If forcing handover target instance is found in the cell, the forced handover is initiated. Then, if the forced handover fails due to handover execution failure, the counter counts the number of receiving handover execution failure message from low priority user during the forced handover.
Usage

access process, this counter is used to find out the number of receiving the forced handover failure message due to handover execution failure.
Measurement
Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forced handover target instance, then
the counter increments in the following case: the forcing handover instance sends the forced handover message to the forced
handover target instance and simultaneously receives the forced
handover failure message which is due to handover execution failure. The measurement point is B, as shown in Figure 674.
FIGURE 674 MEASUREMENT POINT OF NUMBER OF RECEIVING FORCED
HANDOVER FAILURE MESSAGE FROM LOW PRIORITY USER DURING FORCED
HANDOVER
Unit
Times
C901050045 Number
of time out for wait
resource (assignment
forced handover)
Definition
Number of time out for wait resource (assignment forced handover)
Description
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If forced
handover target instance is found in the cell, the forced handover is
initiated, and when the waiting for forced handover target instance
resource is timeout, the counter counts the number of timeout due
to waiting for resource during the forced handover.
Usage
During the forced handover for voice channel assignment in MS access process, this counter is used to find out the number of timeout
due to waiting for forced handover target instance resource.
605
Measurement
Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forced handover target instance, then
the counter increments when the waiting for forced handover target instance resource is timeout. The measurement point is B, as
FIGURE 675 MEASUREMENT POINT OF NUMBER OF TIMEOUT FOR WAIT
RESOURCE (ASSIGNMENT FORCED HANDOVER)
Unit
Times
forced release target not
found (assignment forced
release)
606
Definition
Number of forced release target not found (assignment forced release)
Description
channels forcibly, if no forced release target is found in the cell,
then this counter counts the number of times that forced release
target is not found.
Usage
During forced release for voice channel assignment, this counter

is used to find out the number of times that forced release target
is not found.
Measurement
Point

forced release is allowed but there is no suitable forced release
instance, then the counter increments. The measurement point is

FIGURE 676 MEASUREMENT POINT OF NUMBER OF FORCED RELEASE
TARGET NOT FOUND (ASSIGNMENT FORCED RELEASE)
Unit
Times
time out for wait resource
(assignment forced release)
Description
channels forcibly. After the forced release is initiated, if time is
out due to waiting for forced release target to release resource,
then this counter counts the number of timeout due to waiting for
resource during the forced release.
Usage
During the forced release for voice channel assignment in MS access process, this counter is used to find out the number of timeout
due to waiting for forced release target instance resource.
Measurement
Point
When BSC fails to assign voice channel, if forced release is allowed and there is suitable forced release target instance, then
the counter increments when the waiting for forced release target instance resource is timeout. The measurement point is B, as
607
FIGURE 677 MEASUREMENT POINT OF NUMBER OF TIMEOUT FOR WAIT

RESOURCE (ASSIGNMENT FORCED RELEASE
Unit
Times
get before grab released
channel (assignment forced
handover)
608
Definition
Number of get before grab released channel (assignment forced

handover)
Description
handover succeeds in getting the forced handover target resource,
the counter counts the number of preempting the released channel during the forced handover.
Usage

access process, this counter is used to find out the number of preempting the released channel.
Measurement
Point
During the voice channel assignment process for emergency call,

if the radio resource request fails and forced handover is allowed,
the forcing handover instance sends the forced handover message to
the forced handover instance. If the message of resource available
is received, then the resource is obtained successfully, and in this
case, the counter increments. The measurement point is B, as

Unit
Times
channel(assignment forced
release)
Definition

release)
Description
BSC fails to assign voice channel due to no available resource, if

it obtains needed channel within specified time after the forced
release is performed, then the forced release is considered successful, and the counter counts the number of successful forced
releases (emergency service).
Usage
This counter is used to find out the number of successful assignments due to forced release during the MS access process.
Measurement
Point

request fails and forced release is allowed, the forcing release instance sends the forced release message to the forced release instance. If the message of resource available is received, then the
resource is obtained successfully, and in this case, the counter increments. The measurement point is B, as shown in Figure 679.
609

Unit
Times
C901050050 The count of

Assignment using FULL IP
A-Interface
Statistics object
Description
610
CELL
On the premise that the 3GPP IPA function is implemented, when
MSC's assignment request, which is of voice type, data type, or fax
service type, is received, the system selects A-interface transmission mode according to the assignment request's content. After
MS assignment is completed, BSC decides the A-interface transmission mode for the service before sending the assignment completion message. If the A-interface transmission mode is all-IP
A-interface transmission, the counter increments. The measurement point is A, as shown in Figure 680.
Unit
OF THE
COUNT
OF
ASSIGNMENT USING FULL IP A-INTERFACE
Times

Assignment using PCM over
IP A-Interface
Statistics object
Description
CELL
MS assignment is completed, BSC decides the A-interface transmission mode for the service before sending the assignment completion message. If the A-interface transmission mode is PCMoIP
transmission, the counter increments. The measurement point is
611

A-INTERFACE
Unit
OF THE
COUNT
OF
ASSIGNMENT USING PCM
OVER
IP
Times

Assignment using PCM over
TDM A-Interface
Statistics object
Description
612
CELL
MS assignment is completed, BSC decides the A-interface transmission mode for the service before sending the assignment completion message. If the A-interface transmission mode is TDM
transmission, the counter increments. The measurement point is

A-INTERFACE
Unit
OF THE
COUNT
OF
ASSIGNMENT USING PCM
OVER
TDM
Times

Assignment Failure caused
by "Requested Codec Type
or Codec Configuration not
supported"
Statistics object
Description
CELL
MSC's assignment request, which is of voice type, data type, or
fax service type, is received, the system selects the voice version
according to the field Codec List (MSC Preferred) in the assignment request. In the field Codec List (MSC Preferred), if the voice
coding type or combination is not the voice version supported by
BSC, then the assignment failure message is sent to MSC, and the
counter increments. (At present, there is no voice coding type
or combination not supported by BSC. Thus the counter does not
have counting value. ) The measurement point is A, as shown in
Figure 683.
613
FIGURE 683 MEASUREMENT POINT OF THE COUNT OF ASSIGNMENT FAILURE CAUSED

CODEC TYPE OR CODEC CONFIGURATION NOT SUPPORTED"
Unit
BY
"REQUESTED
Times

by "Requested Codec Type
or Codec Configuration
unavailable"
Statistics object
Description
614
CELL
fax service type, is received, the system selects the voice version
according to the field Codec List (MSC Preferred) in the assignment
request. According to the voice coding type or combination in the
field Codec List (MSC Preferred), if it fails to request corresponding
radio channel (i.e. the radio channel type available in the current
cell is not consistent with the requested channel type), then the
assignment failure message is sent to MSC, and the counter increments. The measurement point is B, as shown in Figure 684.
FIGURE 684 MEASUREMENT POINT OF THE COUNT OF ASSIGNMENT FAILURE CAUSED

CODEC TYPE OR CODEC CONFIGURATION UNAVAILABLE"
Unit
BY
"REQUESTED
Times

by "Requested A-Interface
Type not supported"
Statistics object
Description
CELL
fax service type, is received, the system selects voice version as
well as A-interface transmission mode according to the field Codec
List (MSC Preferred) in the assignment request. In the field Codec
List (MSC Preferred), if the A-interface transmission mode is not
consistent with that supported by BSC, then the assignment failure message is sent to MSC, and the counter increments. The
615

A-INTERFACE TYPE NOT SUPPORTED"
Unit
THE
COUNT
OF
ASSIGNMENT FAILURE CAUSED
BY
"REQUESTED
Times

by "Requested A-Interface
Type unavailable"
Statistics object
Description
616
CELL
fax service type, is received, the system selects voice version as
well as A-interface transmission mode according to the field Codec
List (MSC Preferred) in the assignment request. After the system
selects an A-interface transmission mode, if such a transmission
mode can not be used in the current cases (for example, in the case
of IP resource request failure or access failure), then the assignment failure message is sent to MSC, and the counter increments.
The measurement point is C, as shown in Figure 686.

A-INTERFACE TYPE UNAVAILABLE"
Unit
OF THE
COUNT
OF
BY
"REQUESTED
Times

by "Call Identifier already
allocated"
Statistics object
Description
CELL
service type, is received, the system selects voice version as well
as A-interface transmission mode according to the field Codec List
(MSC Preferred) in the assignment request. If the system uses
all-IP A-interface transmission, it is necessary to check whether
there are any same Call IDs of IP calls. If there are, then the
assignment failure message is sent to MSC, and the counter increments. The measurement point is A, as shown in Figure 687.
617

IDENTIFIER ALREADY ALLOCATED"
Unit
OF THE
COUNT
OF
BY
"CALL
Times

by "Requested Redundancy
Level not supported"
Statistics object
Description
618
CELL
MSC's assignment request, which is of data type or fax service
type, is received, the system selects voice version as well as transmission redundancy mode according to the field Codec List (MSC
Preferred) in the assignment request. If the transmission redundancy mode is not supported by BSC, then the assignment failure
message is sent to MSC, and the counter increments. The measurement point is A, as shown in Figure 688.

REDUNDANCY LEVEL NOT SUPPORTED"
Unit
THE
COUNT
OF
BY
"REQUESTED
Times

by "Call Access Control"
Statistics object
Description
CELL
fax service type, is received, the system requests radio channel
according to the assignment request. If the database returns the
message that radio channel request fails due to insufficient Abis
resource, then the assignment failure message is sent to MSC, and
the counter increments. The measurement point is C, as shown in
Figure 689.
619

ACCESS CONTROL"
Unit
OF THE
COUNT
OF
BY
"CALL
Times
C901050060 Attempt
Number of mode modify for
assignment
Description
This counter counts the number of attempts for mode modification.
Usage
This counter counts the number of attempts for mode modification

in the process of assignment.
Measurement
Point
1. The channel type requested by the assignment is same as the

actual channel type, the channel mode is changed, the type of
actual channel is voice channel or the channel type requested
by the assignment is voice channel, and the voice version requested by the assignment is unmatched with that actually
occupied.
2. On re-assignment, the channel type for re-assignment is related to actual channel type, the actual channel type is a voice
channel or the channel type requested by the assignment is a
voice channel, and the voice version requested by the assignment is unmatched with that actually occupied.
Unit
620
Times
C901050061 Success
Number of mode modify for
assignment
Description
This counter counts the number of successes for mode modification.
Usage
This counter counts the number of successes for mode modification in the process of assignment.
Measurement
Point
This counter increments while receiving the response message

about Abis channel mode modified or Um channel mode modified
in the process of modifying the mode.
Unit
Times
retry attempts for voice
channel because of radio
Description
When BSC receives the voice channel assignment request from

MSC, if it finds out a better cell according to the measurement
report on SDCCH and directed retry due to radio cause is allowed,
it attempts to assign TCH of other cells. This counter counts the
number of attempts of directed retry due to radio causes.
This counter counts the number of attempts of directed retry due
to radio causes. It is used to study radio signal condition in the
cell.
During the voice channel assignment, if the source cell supports directed retry due to radio cause and if the source cell finds out a better cell according to the measurement report on SDCCH, it sends
the Radio_App message to the destination cell, and the counter
621

TO RADIO CAUSES
OF
NUMBER
OF
DIRECTED RETRIES
DUE
This counter is supported in version V6.20.614b.

Unit
Statistics Object
Times
Cell
directed retry because of
radio
Description
This counter counts the number of executions of directed retry due

to radio causes.
This counter is used to study the process and the result of directed
retry due to radio cause.
During the voice channel assignment, if directed retry occurs due
to radio cause and if the destination cell successfully requests the
channel, then the counter increments when the source cell receives the message of radio resource available from the destination cell. The measurement point is B, as shown in Figure 691.
622
FIGURE 691 NUMBER OF ASSIGNMENT EXECUTIONS DUE TO DIRECTED RETRY

Unit
Statistics Object
Times
Cell
retry attempts for data
channel because of radio
Description
When BSC receives the data channel assignment request from

MSC, if it finds out a better cell according to the measurement
report on SDCCH and directed retry due to radio cause is allowed,
it attempts to assign TCH of other cells. This counter counts the
number of attempts of directed retry due to radio causes.
This counter counts the number of attempts of directed retry due
to radio causes. It is used to study radio signal condition in the
cell.
During the voice channel assignment, if the source cell supports directed retry due to radio cause and if the source cell finds out a better cell according to the measurement report on SDCCH, it sends
the Radio_App message to the destination cell, and the counter
623

TO RADIO CAUSES
OF
NUMBER
OF
DIRECTED RETRIES
DUE

Unit
Statistics Object
Times
Cell
for data channel due to
directed retry because of
radio
Description
This counter counts the number of executions of directed retry due

to radio causes.
This counter is used to study the process and the result of directed
retry due to radio cause.
During the data channel assignment, if directed retry occurs due
to radio cause and if the destination cell successfully requests the
channel, then the counter increments when the source cell receives the message of radio resource available from the destination cell. The measurement point is B, as shown in Figure 693.
624

Unit
Statistics Object
Times
Cell
625
626
Chapter
12
Handover Cause
Measurement
Table of Contents
Overview........................................................................ 629
C901060001 Number of handover attempts due to directed
retry .............................................................................. 630
C901060002 Number of SDCCH handover attempts due to UL
received strength ........................................................... 631
C901060003 Number of SDCCH handover attempts due to DL
received strength ............................................................ 631
C901060004 Number of SDCCH Handover attempt due to UL
quality .......................................................................... 632
C901060005 Number of SDCCH Handover attempt due to DL
quality ........................................................................... 633
C901060006 Number of SDCCH handover attempts due to UL
interference .................................................................... 633
interference .................................................................... 634
C901060008 Number of SDCCH inter-subcell handover attempts due to good C/I .................................................... 635
C901060009 Number of SDCCH inter-subcell handover attempts due to bad C/I ...................................................... 635
C901060010 Number SDCCH of handover attempts due to
PBGT ............................................................................. 636
C901060011 Number of SDCCH handover attempts due to
large TA ........................................................................ 637
quick break up of UL ........................................................ 638
macro-micro switch ........................................................ 638
MSC request .................................................................. 639
traffic............................................................................. 640
large TA and wastage....................................................... 641
small TA and wastage ...................................................... 642
C901060018 Number of SDCCH Handover attempt due to a
preferable electricity level of 3G adjacent cell ...................... 643
C901060019 Number SDCCH handover attempts due to
forced transfer ................................................................ 643
C901060020 Number of SDCCH handover during assignment
due to forced transfer ...................................................... 644
C901060021 Number of SDCCH handover during handover
due to forced transfer ..................................................... 645
627

increased TA .................................................................. 646
C901060023 Number of SDCCH handover attempts due to TA
decrease ........................................................................ 647
other factors .................................................................. 648
macro-micro switch ......................................................... 649
C901060037 Number of TCH/F handover attempts due to MSC
request .......................................................................... 650
C901060038 Number of TCH/F handover attempts due to traffic ................................................................................. 651
preferable electricity level in 3G adjacent cell ..................... 653
forced transfer ................................................................ 654
C901060043 Number of TCH/F handover during assignment
due to forced transfer ...................................................... 655
C901060044 Number of TCH/F handover attempts during
handover due to forced transfer ........................................ 656
C901060045 Number of TCH/F handover attempts due to TA
increase ......................................................................... 657
C901060046 Number of TCH/F handover attempts due to TA
decrease ........................................................................ 658
macro-micro switch ......................................................... 660
MSC request ................................................................... 660
traffic............................................................................. 661
C901060064 Number of TCH/H handover attempts due to a
preferable electricity level in 3G adjacent cell ...................... 664
forced transfer ................................................................ 665
C901060066 Number of TCH/H handover attempts during assignment due to forced transfer......................................... 665
handover due to forced transfer ........................................ 667
handover due to TA increase ............................................. 668
handover due to TA decrease ............................................ 669
other reasons.................................................................. 669
C901060071 Number of TCH/F handover attempts due to CS
channel transfer .............................................................. 670
C901060072 Number of TCH/H handover attempts due to CS
channel transfer .............................................................. 671
628
Chapter 12 Handover Cause Measurement

Fragment reorganization .................................................. 672
C901060074 Number of TCH/F handover attempts due to energy conservation ............................................................ 673
C901060075 Number of TCH/F handover attempts due to energy conservation ............................................................ 674
C901060076 Number of TCH/F handover attempts due to CS
channel is forced release .................................................. 675
C901060077 Number of TCH/H handover attempts due to CS
channel is forced release .................................................. 676
C901060078 Number of TCH/F handover attempts due to FR
to HR during cell busy ...................................................... 677
downlink rapid drop ......................................................... 678
C901060082 Attempts of handover on TCH/F caused by power
adjustment ..................................................................... 679
power adjustment ........................................................... 679
C901060084 Attempts of handover on TCH/F caused by local
switch ............................................................................ 680
C901060085 Attempts of handover on TCH/H caused by local
switch ............................................................................ 680
C901060086 Attempts of handover on TCH/F caused by reducing band resources of IPAbis ........................................ 681
C901060087 Attempts of handover on TCH/H because of
MASTERPWR_ALM from TRX ............................................. 681
C901060088 Attempts of handover on TCH/F because of MASTERPWR_ALM from TRX.................................................... 682
C901060089 Number of handover attempts due to directed
retry for PBGT................................................................. 683
quality rapid drop ............................................................ 684
Overview
Handover cause counter is used for checking MS handover causes.
According to cell radio environment and BSC settings, handover algorithm judgment module can carry out handover due to several
different handover causes, so as to realize functions such as optimizing resource usage, improving call quality and rescuing calls.
629
directed retry
Definition
Number of handover attempts due to directed retry
Description
During the process of MS requests channel, if radio resource is

congested, then it will attempt to request an available channel
from adjacent cell for this call. This is called direct retry, which is
a kind of handover. This counter counts the number of handover
attempts due to direct retry.
Usage
This counter is used to find out MS access process and to check

cell channel utilizing status. If the statistic number counted by
the counter is relative high, then it means the cell does not have
enough radio resource and capacity expansion shall be taken into
account.
Measurement
Point
In assignment process, the counter increments if source instance

receives message that no available radio resource replied by target
instance, then it chooses cell list successfully and try to attempt
cells in the list. This counter is handover cause counter and used
for finding out cell channel congestion status, so the counter only
counts in the initial judgment. The measurement point is A, as
FIGURE 694 DIRECTED RETRY JUDGMENT
Unit
Related Features
Times
630
SDCCH handover attempts
due to UL received strength
Definition
Number of SDCCH handover attempts due to UL received strength
Description
This counter counts the number of handover attempts due to too

low uplink received strength (on SDCCH).
Usage
This counter is used to find out frequency of handover attempts

due to uplink received strength (on SDCCH); high number means
SDCCH uplink signal strength is low.
Measurement
Point
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes
and handover cause is uplink signal strength. The measurement
Unit
Related Features
Times
due to DL received strength
Definition
Number of SDCCH handover attempts due to DL received strength
Description

low downlink received strength (on SDCCH).
Usage

due to downlink received strength (on SDCCH); high number
means SDCCH downlink signal strength is low.
Measurement
Point
631
and handover cause is downlink signal strength. The measurement point is A, as shown in Figure 696.
Unit
Related Features
Times
SDCCH Handover attempt
due to UL quality
Definition
Number of SDCCH Handover attempt due to UL quality.
Description

bad uplink quality (on SDCCH).
Usage

due to uplink quality (on SDCCH); high number means SDCCH
uplink quality is bad.
Measurement
Point
and handover cause is uplink quality. The measurement point is
Unit
Related Features
632
Times
due to DL quality
Definition
Number of SDCCH Handover attempt due to DL quality.
Description

bad downlink quality (on SDCCH).
Usage

due to downlink quality (on SDCCH); high number means SDCCH
downlink quality is bad.
Measurement
Point
and handover cause is downlink quality. The measurement point
Unit
Related Features
Times
Definition
Number of SDCCH handover attempts due to UL interference.
Description

high uplink interference (on SDCCH).
Usage

due to uplink interference (on SDCCH); high number means SDCCH uplink interference is high.
Measurement
Point
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is
yes and handover cause is uplink interference. The measurement
633
Unit
Related Features
Times
Definition
Number of SDCCH handover attempts due to DL interference.
Description

high downlink interference (on SDCCH).
Usage

due to downlink interference (on SDCCH); high number means
SDCCH downlink interference is high.
Measurement
Point
and handover cause is downlink interference. The measurement
Unit
Related Features
634
Times
C901060008 Number
of SDCCH inter-subcell
good C/I
Definition
Number of SDCCH inter-subcell handover attempts due to good

C/I
Description

high C/I RATIO (on SDCCH). This handover only happens in subcell configuration and C/I algorithm is used; MS is handed over
from first cell to second cell.
Usage

due to too high C/I RATIO (on SDCCH); high number means the
number of MS handover to second cell after MS has been accessed
into first cell due to too high C/I RATIO is high and second cell
absorbs traffic.
Measurement
Point
and handover cause is C/I RATIO (on SDCCH) (Good C/I). The
Unit
Related Features
Times
C901060009 Number
of SDCCH inter-subcell
bad C/I
Definition
Number of SDCCH inter-subcell handover attempts due to bad C/I
635
Description

low C/I RATIO (on SDCCH). This handover only happens in sub-cell
configuration and C/I algorithm is used; MS is handed over from
second cell to first cell.
Usage

due to too low C/I RATIO (on SDCCH); high number means when
MS is on the call in second cell, the number of handover to first
cell is high due to too low C/I RATIO; interference in second cell is
high and some measures like TRX power adjustment shall be done
to improve second cell C/I ratio.
Measurement
Point
and handover cause is C/I RATIO (on SDCCH) (Bad C/I). The measurement point is A, as shown in Figure 702.
Unit
Related Features
Times
C901060010 Number
SDCCH of handover
attempts due to PBGT
Definition
636
Number SDCCH of handover attempts due to PBGT
Description
This counter counts the number of handover attempts due to PBGT

(on SDCCH). If the value of PBGT is higher than 0, then it means
there is an adjacent cell whose radio environment is better than
that of the present cell. If the number that PBGT value is higher
than 0 reaches the threshold, then PBGT handover will be carried
out.
Usage

due to PBGT (on SDCCH); high number means present cells SDCCH signal is worse than that of the adjacent cell.
Measurement
Point
and handover cause is PBGT (on SDCCH). The measurement point
Unit
Related Features
Times
due to large TA
Definition
Number of SDCCH handover attempts due to large TA
Description
This counter counts the number of handover attempts due to large

TA (on SDCCH). Increase of TA means MS is moving far away from
the cell; when the distance between MS and the cell reaches a
certain value, then handover attempts due to large TA may occur.
Usage

due to large TA (on SDCCH); its value can represent mobility of
the subscriber in the cell in a certain extent.
Measurement
Point
and handover cause is large TA (on SDCCH). The measurement
Unit
Related Features
Times
637
due to quick break up of UL
Definition
Number of SDCCH handover attempts due to quick break up of UL
Description
This counter counts the number of handover attempts due to uplink break up quickly (on SDCCH). If SDCCH uplink level decreases
abruptly in several continuous measurement reports, handover attempts due to uplink break up quickly may occur.
Usage

due to uplink break up quickly (on SDCCH); its value can represent
stability of the current radio environment in a certain extent.
Measurement
Point
and handover cause is uplink break up quickly (on SDCCH). The
Unit
Related Features
Times
ZGO-02-02-006 Rapid Level Drop Handover
ZGO-02-02-015 Enhanced Cell Reselection Procedure
due to macro-micro switch
638
Definition
Number of SDCCH handover attempts due to macro-micro switch.
Description
This counter counts the number of handover attempts due to

macro-micro switch (on SDCCH). If adjacent cell level is not lower
than the threshold and the adjacent cell is sub-layer cell, then
handover attempts due to macro-micro switch may occur.
Usage

due to macro-micro switch (on SDCCH); its value can represent
the status of micro cell absorbing traffic.
Measurement
Point
and handover cause is macro-micro switch (on SDCCH). The measurement point is A, as shown in Figure 706.
Unit
Related Features
Times
ZGO-02-02-001 Handover between Macro- and Micro-cells
due to MSC request
Definition
Number of SDCCH handover attempts due to MSC request.
Description
This counter counts the number of handover attempts due to MSC

request (on SDCCH). Handover is originated by MSC, some calls
are handed over from the present cell to target cell for alleviating
the present cell traffic load.
Usage

due to MSC request (on SDCCH); its value can represent the status
that MSC adjusts the present cell traffic.
Measurement
Point
BSC carries out handover judgment after receiving HO_ENQUIRY message sent by MSC; the counter increments if judgment result is
yes. The measurement point is A, as shown inFigure 707.
639
FIGURE 707 HO_ENQUIRY HANDOVER
Unit
Related Features
Times
due to traffic
Definition
640
Number of SDCCH handover attempts due to traffic.
Description
This counter counts the number of handover attempts due to traffic (on SDCCH). Handover is originated by BSC, some calls are
handed over from the present cell to target cell for alleviating the
present cell traffic load.
Usage

due to traffic (on SDCCH); its value can represent the status that
BSC adjusts the present cell traffic.
Measurement
Point
BSC carries out handover judgment after receiving SDCCH traffic alarm, the counter increments if judgment result is yes. The
measurement point is A, as shown in Figure 708. DBS, UMC and
RANCS are all instances of BSC and they take part in handover
due to traffic.
FIGURE 708 TRAFFIC HANDOVER
Unit
Related Features
Times
ZGO-02-02-007 Traffic Based Handover
due to large TA and wastage
Definition
Number of SDCCH handover attempts due to large TA and

wastage.
Description

TA and wastage (on SDCCH). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both
TA and PassLoss are higher than set threshold, MS is handed over
from second cell to first cell.
Usage

due to large TA and wastage (on SDCCH); its value can represent
the mobility of subscriber among sub-cells in the cell.
Measurement
Point
and handover cause is large TA and wastage (on SDCCH). The
641
Unit
Related Features
Times
due to small TA and wastage
Definition
Number of SDCCH handover attempts due to small TA and

wastage.
Description
This counter counts the number of handover attempts due to small

TA and wastage (on SDCCH). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both
TA and PassLoss are lower than set threshold, MS is handed over
Usage

due to small TA and wastage (on SDCCH); its value can represent
Measurement
Point
and handover cause is small TA and wastage (on SDCCH). The
Unit
Related Features
642
Times
due to a preferable electricity
level of 3G adjacent cell
Definition
Number of SDCCH handover attempt due to a preferable electricity

level of FDD adjacent cell.
Description
This counter counts the number of handover attempts due to a

good standard level in FDD adjacent cell (on SDCCH).
Usage

due to a good standard level in FDD adjacent cell (on SDCCH); its
value can represent status that 3G network absorbs traffic.
Measurement
Point
and handover cause is good standard level in FDD adjacent cell (on
SDCCH). The measurement point is A, as shown in Figure 711.
Unit
Related Features
Times
C901060019 Number
due to forced transfer
Definition
Description
Number SDCCH handover attempts due to forced transfer.

This counter counts the number of forced transfer handover attempts (on SDCCH). If the TCH utilizing rate of the present cell
reaches a set percentage of the threshold, BSC will try to handover
643
subscriber whose path loss and TA are small from the present cell
to some set cells. This kind of handover is called forced transfer
handover.
Usage
This counter is used to find out frequency of forced transfer handover attempts (on SDCCH); its value can represent the present
cells channel utilizing status and traffic sharing status.
Measurement
Point
and handover cause is forced transfer handover attempts (on SDCCH). The measurement point is A, as shown in Figure 712.
Unit
Related Features
Times
ZGO-02-02-003 Directed-Shift Handover
SDCCH handover during
assignment due to forced
transfer
644
Definition
Number of SDCCH handover during assignment due to forced

transfer.
Description
This counter counts the number of forced handovers during assignment (on SDCCH). If all TCH of the present cell are occupied
and MS priority is high enough, BSC will try to handover services
whose priority are low from the present cell to adjacent cells. This
kind of handover is called forced handover. Forced handover and
forced release are two forms of occupation.
Usage
This counter is used to find out frequency of forced handovers during assignment (on SDCCH); its value can represent the present
cells TCH utilizing status and traffic sharing status.
Measurement
Point
BSC has no available TCH to allocate during the assignment

process and it carries out forced handover judgment; the counter
increments if judgment result is yes and the channel type of
forced handover instance is SDCCH. The measurement point is A,

FIGURE 713 FORCED HANDOVER JUDGMENT
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
SDCCH handover during
transfer
Definition
Number of SDCCH handover during handover due to forced transfer.
Description
This counter counts the number of forced handovers during handover (on SDCCH).
645
Usage
This counter is used to find out frequency of forced handovers

during handover (on SDCCH); its value can represent the present
Measurement
Point
BSC has no available TCH to allocate during the handover process

and it carries out forced handover judgment; the counter increments if judgment result is yes and the channel type of forced handover instance is SDCCH. The measurement point is A, as shown
in Figure 714.
Unit
Related Features
Times
due to increased TA
Definition
Description
646
Number of SDCCH handover attempts due to increased TA.

This counter counts the number of handover attempts due to increased TA (on SDCCH). This handover only happens in expanding
cell configuration, present BSC version does not use expanded cell
and expanded TRX configuration any more after being introduced

the concept of sub-cell. This counter is equal to the counter that
counts the number of MS handover from second cell to first cell
during sub-cell configuration.
Usage
This counter is used to find out frequency of MS handover from

second cell to first cell in sub-cell.
Measurement
Point
and handover is from second cell to first cell. The measurement
Unit
Related Features
Times
due to TA decrease
Definition
Number of SDCCH handover attempts due to TA decrease.
Description
This counter counts the number of handover attempts due to decreased TA (on SDCCH). This handover only happens in expanding
counts the number of MS handover from first cell to second cell
Usage

first cell to second cell in sub-cell.
Measurement
Point
and handover is from first cell to second cell. The measurement
647
Unit
Related Features
Times
due to other factors
Definition
Number of SDCCH Handover attempt due to other factors.
Description

other reason except reasons mentioned above (on SDCCH).
Usage

due to any other reason (on SDCCH).
Measurement
Point
and handover cause is any other reason. The measurement point
Unit
Related Features
648
Times
Definition
Number of TCH/F handover attempts due to quick break up of UL.
Description
This counter counts the number of handover attempts due to uplink break up quickly (on TCH/F). If TCH/F uplink level decreases
Usage

due to uplink break up quickly (on TCH/F); its value can represent
Measurement
Point
BSC carries out handover judgment after receiving TCH/F measurement report; the counter increments if judgment result is yes
and handover cause is uplink break up quickly (on TCH/F). The
Unit
Related Features
Times
Definition
Number of TCH/F handover attempts due to macro-micro switch.
Description

macro-micro switch (on TCH/F). If adjacent cell level is not lower
649
Usage

due to macro-micro switch (on TCH/F); its value can represent the
status of micro cell absorbing traffic.
Measurement
Point
and handover cause is macro-micro switch (on TCH/F). The measurement point is A, as shown in Figure 719.
Unit
Related Features
Times
due to MSC request
Definition
650
Number of TCH/F handover attempts due to MSC request.
Description

request (on TCH/F). Handover is originated by MSC, some calls
Usage

due to MSC request (on TCH/F); its value can represent the status
Measurement
Point
BSC carries out handover judgment after receiving HO_ENQUIRY

message sent by MSC; the counter increments if judgment result
is yes. The measurement point is A, as shown in Figure 720.
Unit
Related Features
Times
due to traffic
Definition
Number of TCH/F handover attempts due to traffic.
Description
This counter counts the number of handover attempts due to traffic

(on TCH/F). Handover is originated by BSC, some calls are handed
over from the present cell to target cell for alleviating the present
cell traffic load.
Usage

due to traffic (on TCH/F); its value can represent the status that
Measurement
Point
BSC carries out handover judgment after receiving TCH/F traffic

alarm, the counter increments if judgment result is yes. The measurement point is A, as shown in Figure 721.
651
Unit
Related Features
Times
Definition
Number of TCH/F handover attempts due to large TA and wastage.
Description

TA and wastage (on TCH/F). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both
Usage

due to large TA and wastage (on TCH/F); its value can represent
Measurement
Point
and handover cause is large TA and wastage (on TCH/F). The measurement point is A, as shown in Figure 722.
Unit
Related Features
652
Times
Definition
Number of TCH/F handover attempts due to small TA and wastage.
Description

TA and wastage (on TCH/F). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both
Usage

due to small TA and wastage (on TCH/F); its value can represent
Measurement
Point
and handover cause is small TA and wastage (on TCH/F). The measurement point is A, as shown in Figure 723.
Unit
Related Features
Times
due to preferable electricity
level in 3G adjacent cell
Definition
Number of TCH/F handover attempts due to preferable electricity

level in 3G adjacent cell.
Description

good standard level in 3G adjacent cell (on TCH/F).
653
Usage

due to a good standard level in 3G adjacent cell (on TCH/F); its
Measurement
Point
and handover cause is good standard level in 3G adjacent cell (on
TCH/F). The measurement point is A, as shown in Figure 724.
Unit
Related Features
Times
Definition
654
Number of TCH/F handover attempts due to forced transfer.
Description
This counter counts the number of forced transfer handover attempts (on TCH/F). If the TCH utilizing rate of the present cell
handover.
Usage
This counter is used to find out frequency of forced transfer handover attempts (on TCH/F); its value can represent the present
Measurement
Point
BSC carries out handover judgment after receiving TCH/F measurement report; the counter increments if judgment result is
yes and handover cause is forced transfer handover attempts (on
TCH/F). The measurement point is A, as shown in Figure 725.
Unit
Related Features
Times
TCH/F handover during
assignment due to forced
transfer
Definition
Number of TCH/F handover during assignment due to forced transfer.
Description
This counter counts the number of forced handovers during assignment (on TCH/F). If all TCH of the present cell are occupied
kind of handover is called forced handover.
Usage
This counter is used to find out frequency of forced handovers during assignment (on TCH/F); its value can represent the present
Measurement
Point

forced handover instance is TCH/F. The measurement point is A,
655
Unit
Related Features
Times
during handover due to
forced transfer
656
Definition
Number of TCH/F handover attempts during handover due to

forced transfer.
Description
This counter counts the number of forced handovers during handover (on TCH/F).
Usage
This counter is used to find out frequency of forced handovers during handover (on TCH/F); its value can represent the present cells
TCH utilizing status and traffic sharing status.
Measurement
Point

and it carries out forced handover judgment; the counter increments if judgment result is yes and the channel type of forced
handover instance is TCH/F. The measurement point is A, as shown

in Figure 727.
Unit
Related Features
Times
due to TA increase
Definition
Number of TCH/F handover attempts due to TA increase.
Description
This counter counts the number of handover attempts due to increased TA (on TCH/F). This handover only happens in expanding
Usage

657
Measurement
Point
Unit
Related Features
Times
due to TA decrease
Definition
Number of TCH/F handover attempts due to TA decrease.
Description
This counter counts the number of handover attempts due to decreased TA (on TCH/F). This handover only happens in expanding
Usage

Measurement
Point
658
Unit
Related Features
Times
Definition
Number of TCH/H handover attempts due to quick break up of UL.
Description
This counter counts the number of handover attempts due to uplink break up quickly (on TCH/H). If TCH/H uplink level decreases
Usage

due to uplink break up quickly (on TCH/H); its value can represent
Measurement
Point
BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is yes
and handover cause is uplink break up quickly (on TCH/H). The
Unit
Related Features
Times
659
Definition
Number of TCH/H handover attempts due to macro-micro switch.
Description

macro-micro switch (on TCH/H). If adjacent cell level is not lower
Usage

due to macro-micro switch (on TCH/H); its value can represent the
status of micro cell absorbing traffic.
Measurement
Point
and handover cause is macro-micro switch (on TCH/H). The measurement point is A, as shown in Figure 731.
Unit
Related Features
Times
due to MSC request
Definition
Description
660
Number of TCH/H handover attempts due to MSC request.

request (on TCH/H). Handover is originated by MSC, some calls
Usage

due to MSC request (on TCH/H); its value can represent the status
Measurement
Point
BSC carries out handover judgment after receiving HO_ENQUIRY message sent by MSC; the counter increments if judgment result is
yes. The measurement point is A, as shown in Figure 732.
Unit
Related Features
Times
due to traffic
Definition
Number of TCH/H handover attempts due to traffic.
Description
This counter counts the number of handover attempts due to traffic

(on TCH/H). Handover is originated by BSC, some calls are handed
over from the present cell to target cell for alleviating the present
cell traffic load.
Usage

due to traffic (on TCH/H); its value can represent the status that
Measurement
Point
BSC carries out handover judgment after receiving TCH/H traffic

alarm, the counter increments if judgment result is yes. The measurement point is A, as shown in Figure 733.
661
Unit
Related Features
Times
662
Definition
Number of TCH/H handover attempts due to large TA and wastage.
Description

TA and wastage (on TCH/H). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both
Usage

due to large TA and wastage (on TCH/H); its value can represent
Measurement
Point
and handover cause is large TA and wastage (on TCH/H). The measurement point is A, as shown in Figure 734.
Unit
Related Features
Times
Definition
Number of TCH/H handover attempts due to small TA and wastage.
Description

TA and wastage (on TCH/H). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both
Usage

due to small TA and wastage (on TCH/H); its value can represent
Measurement
Point
and handover cause is small TA and wastage (on TCH/H). The measurement point is A, as shown in Figure 735.
Unit
Related Features
Times
663
due to a preferable electricity
level in 3G adjacent cell
Definition
Number of TCH/H handover attempts due to a preferable electricity

level in 3G adjacent cell.
Description

good standard level in 3G adjacent cell (on TCH/H).
Usage

due to a good standard level in 3G adjacent cell (on TCH/H); its
Measurement
Point
and handover cause is good standard level in 3G adjacent cell (on
TCH/H). The measurement point is A, as shown in Figure 736.
Unit
Related Features
Times
664
Definition
Number of TCH/H handover attempts due to forced transfer.
Description
This counter counts the number of forced transfer handover attempts (on TCH/H). If the TCH utilizing rate of the present cell
handover.
Usage
This counter is used to find out frequency of forced transfer handover attempts (on TCH/H); its value can represent the present
Measurement
Point
BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is
yes and handover cause is forced transfer handover attempts (on
TCH/H). The measurement point is A, as shown in Figure 737.
Unit
Related Features
Times
during assignment due to
forced transfer
Definition
Number of TCH/H handover attempts during assignment due to

forced transfer.
665
Description
This counter counts the number of forced handovers during assignment (on TCH/H). If all TCH of the present cell are occupied
kind of handover is called forced handover.
Usage
This counter is used to find out frequency of forced handovers during assignment (on TCH/H); its value can represent the present
Measurement
Point

forced handover instance is TCH/H. The measurement point is A,
Unit
Related Features
Times
666
during handover due to
forced transfer
Definition
Number of TCH/H handover attempts during handover due to

forced transfer.
Description
This counter counts the number of forced handovers during handover (on TCH/H).
Usage
This counter is used to find out frequency of forced handovers during handover (on TCH/H); its value can represent the present cells
TCH utilizing status and traffic sharing status.
Measurement
Point

and it carries out forced handover judgment; the counter increments if judgment result is yes and the channel type of forced handover instance is TCH/H. The measurement point is A, as shown
in Figure 739.
Unit
Related Features
Times
667
during handover due to TA
increase
Definition
Number of TCH/H handover attempts during handover due to TA

increase.
Description
This counter counts the number of handover attempts due to increased TA (on TCH/H). This handover only happens in expanding
Usage

Measurement
Point
Unit
Related Features
Times
668
during handover due to TA
decrease
Definition
Number of TCH/H handover attempts during handover due to TA

decrease.
Description
This counter counts the number of handover attempts due to decreased TA (on TCH/H). This handover only happens in expanding
Usage

Measurement
Point
Unit
Related Features
Times
Definition
Number of TCH/H handover attempts due to other reasons
669
Description
This counter counts the number of handover attempts due to other

reasons except for those reasons mentioned above.
Usage
This counter is used to find out handover frequency due to other

reasons.
Measurement
Point
and handover is caused by other reasons. The measurement point
Unit
Times
due to CS channel transfer
Definition
670
Number of TCH/F handover attempts due to CS channel transfer
Description
This counter counts the number of handover due to CS channel

transfer for continuity of available PS channel on TCH/F. the handover caused by this reason is intra-cell handover.
Usage
This counter is used to find out handover frequency due to CS

channel transfer on TCH/F.
Measurement
Point
During call service, due to other call services released, CS service

channel transfer is issued to do intra-cell handover. The service
occupying middle timeslot can be migrated to edge timeslot, providing available sustainable channels for PS. This counter increments if the channel type of instance is TCH/F. The measurement
FIGURE 743 CS CHANNEL TRANSFER HANDOVER
Unit
Related Features
Times
ZGO-03-02-004 HR Concentration
due to CS channel transfer
Definition
Number of TCH/H handover attempts due to CS channel transfer
Description
This counter counts the number of handover due to CS channel

transfer by BSC, which is useful for continuity of available PS channel on TCH/H. This may lead to intra-cell handover.
Usage

channel handover on TCH/H by BSC.
Measurement
Point
During call service, due to other call service released, CS service

channel transfer is issued to do intra-cell handover. The service
occupying middle timeslot service can be migrated to edge timeslot, providing available continual channel. This counter increments
if channel type for handover instance is TCH/H. The measurement
671
Unit
Related Features
Times
C901060073 Number
of TCH/H handover
attempts due to Fragment
reorganization
672
Definition
Number of TCH/H handover attempts due to Fragment reorganization
Description
BSC carries out fragment reorganization for one of two half-rate

service occupying different timeslot, combining these two half-rate
service into one timeslot by intra-cell handover, so one full-rate
channel can be idle. This couner counts the number of handover
attempts due to fragment reorganization.
Usage
This counter is used to find out handover frequency due to combining two half-rate channel on TCH/H by BSC.
Measurement
Point
New call service instance does not apply for full-rate channel, or
due to other call service released, fragment reorganization is issued to do intra-cell handover. It will combine two half-rate service
into one timeslot. The couner increments while one full-rate channel is idle. The measurement point is A, as shown in Figure 745.
Unit
Related Features
Times
due to energy conservation
Definition
Number of TCH/F handover attempts due to energy conservation
Description
Carrier is powered off intelligently by energy conservation, BSC

migrates the service on the carrier to other carrier by intra-cell
handover. This counter counts the number of handover attempts
due to energy conservation on TCH/F by BSC.
Usage
This counter is used to find out handover frequency due to energy

conservation on TCH/F by BSC.
Measurement
Point
Carrier is intelligently powered off by energy conservation, do intra-cell handover for the call service on the carrier to be powered
off and migrated to other carrier. If channel type of handover instance is TCH/F, this counter increments. The measurement point
673
Unit
Related Features
Times
ZGO-04-04-001 TCH Migration to BCCH TRX
due to energy conservation
Definition
674
Number of TCH/F handover attempts due to energy conservation
Description
Carrier is powered off intelligently by energy conservation, BSC

migrates the service on the carrier to other carrier by intra-cell
handover. This counter counts the number of handover attempts
due to energy conservation on TCH/H by BSC.
Usage
This counter is used to find out handover frequency due to energy

conservation on TCH/H by BSC.
Measurement
Point
Carrier is intelligently powered off by energy conservation, do intra-cell handover for the call service on the carrier to be powered
off and migrated to other carrier. If channel type of handover instance is TCH/H, this counter increments. The measurement point
Unit
Related Features
Times
ZGO-04-04-001 TCH Migration to BCCH TRX
due to CS channel is forced
release
Definition
Number of TCH/F handover attempts due to CS channel is forced

release
Description
Due to unsuccessful PS channel application, BSC does intra-cell

handover transfer for CS instance that occupies PDTCH channel
by BSC, the available PS channel will be used by PS service. This
counter counts the number of handover attempts due to CS channel forcedly released.
Usage

service seizured by PS on TCH/F.
Measurement
Point
After PS service channel application is failed, do intra-cell handover

for CS service that occupies PDTCH channel, available PS channel
is used by PS service. If channel type of CS handover instance is
TCH/F, this counter increments. The measurement point is A, as
675
Unit
Related Features
Times
due to CS channel is forced
release
676
Definition
Number of TCH/H handover attempts due to CS channel is forced

release
Description
Due to unsuccessful PS channel application, BSC does intra-cell

handover transfer for CS instance that occupies PDTCH channel,
the available PS channel will be used by PS service. This counter
counts the number of handover attempts due to CS channel
forcedly released on TCH/H by BSC.
Usage

service seizured by PS on TCH/H.
Measurement
Point
After PS service channel application is failed, do intra-cell handover

for CS service that occupies PDTCH channel, available PS channel
is used by PS service. If channel type of CS handover instance is
TCH/H, this counter increments. The measurement point is A, as
Unit
Related Features
Times
due to FR to HR during cell
busy
Definition
Number of TCH/F handover attempts due to FR to HR during cell

busy
Description
This counter counts the number of handover attempts due to FR

transferred to HR on busy, it can connect more services.
Usage
This counter is used to find out handover frequency due to FR

transferred to HR on busy.
Measurement
Point
Unit
N/A
Times
677
due to downlink rapid drop
Description

high downlink level on SDCCH.
Usage
This counter measures the frequency of handover due to the downlink level on SDCCH. The higher value indicates the higher downlink level on SDCCH.
Measurement
Point
This counter increments if the handover decision is done after receiving the measurement report on SDCCH by BSC and the handover is caused by the rapid downlink drop.
Unit
Times
Description

high downlink level on TCH/F.
Usage
This counter measures the frequency of handover due to the downlink level on TCH/F. The higher value indicates the higher downlink
level on TCH/F.
Measurement
Point
This counter increments if the handover decision is done after receiving the measurement report on TCH/F by BSC and the handover is caused by the rapid downlink drop.
Unit
Times
678
Description

high downlink level on TCH/H.
Usage
This counter measures the frequency of handover due to the downlink level on TCH/H. The higher value indicates the higher downlink
level on TCH/H.
Measurement
Point
Unit
This counter increments if the handover decision is done after receiving the measurement report on TCH/H by BSC and the handover is caused by the rapid downlink drop.
Times
C901060082 Attempts of
handover on TCH/F caused
by power adjustment
Description
After the dynamic power sharing function is enabled, iBSC performs real-time monitoring for the power usage of each RRU's
timeslots. When a channel is allocated, the power it uses is registered; when the channel is released, the power it uses is also
released. When the base station reports downlink dynamic power
control result, the power the channel uses is refreshed.
When iBSC detects the power a RRU's timeslot currently uses
reaches the threshold of power congestion control, it selects
a CS service and performs outgoing handover for it towards
other timeslot of the cell or towards other cell. If the service is
occupying TCH/F, the counter increments.
This counter is supported in version V6.20.61 or later.
Usage
This counter is used to find out the frequency of FR service handover due to RRU power congestion.
Measurement
Point

occupying TCH/F, the counter increments.
handover on TCH/H caused
by power adjustment
Description
After the dynamic power sharing function is enabled, iBSC performs real-time monitoring for the power usage of each RRU's
timeslots. When a channel is allocated, the power it uses is registered; when the channel is released, the power it uses is also
released. When the base station reports downlink dynamic power
control result, the power the channel uses is refreshed.
679

occupying TCH/H, the counter increments.
Usage
This counter is used to find out the frequency of HR service handover due to RRU power congestion.
Measurement
Point

occupying TCH/H, the counter increments.
by local switch
Description
The counter counts when the local switch initiates FR service handover.
This counter is supported in version V6.20.614a.
Unit
Statistics Object
Times
Cell
handover on TCH/H caused
by local switch
Description
The counter counts when the local switch initiates HR service handover.
Unit
680
Times
Statistics Object
Cell
by reducing band resources
of IPAbis
Description
After the service module receives the FR-to-HR handover request

message from the RANUMC module, this counter counts the number of attempts of FR-to-HR handover. As shown in Figure 750,
after the EV_FR_Ho_HR message is received, the system judges
whether the handover condition is satisfied. If handover is allowed, the counter counts.
FIGURE 750 HANDOVER ATTEMPT
IPABIS
DUE TO
REDUCING BAND RESOURCES
OF

Unit
Statistics Object
Times
Cell
handover on TCH/H because
of MASTERPWR_ALM from
TRX
Description
After the service module receives the traffic-migration handover

request message from the DBS module, this counter counts the
number of attempts of FR handover. As shown in Figure 751, after the EV_DBS_CS_MOV message is received, the system judges
681
FIGURE 751
FROM TRX
TRAFFIC-MIGRATION HANDOVER
DUE TO
MASTERPWR_ALM

Unit
Statistics Object
Times
Cell
handover on TCH/F because
of MASTERPWR_ALM from
TRX
Description
After the service module receives the traffic-migration handover

request message from the DBS module, this counter counts the
number of attempts of HR handover. As shown in Figure 752, after the EV_DBS_CS_MOV message is received, the system judges
FIGURE 752
FROM TRX
TRAFFIC-MIGRATION HANDOVER
DUE TO
MASTERPWR_ALM

Unit
682
Times
Statistics Object
Cell
directed retry for PBGT
Description
After MSC assigns the channel, if the measurement report on SDCCH indicates a better cell, then the TCH channel can be assigned
in the better cell. The process is called directed retry due to radio
cause, which is a handover type. This counter counts the number
of attempts of MS's directed retry due to radio causes.
The counter is used to study the cell's coverage and the effects of
cell reselection parameters.
During the assignment, if the measurement report on SDCCH indicates a cell with better signal, then the better cell is selected
for channel assignment attempt, and the counter increments. The

Unit
Times
683
Statistics Object
Cell
due to DL quality rapid drop
Description
This counter counts the number of handover attempts on SDCCH

initiated by MS due to downlink quality fast fading.
This counter is used to find out the frequency of MS's handover on
SDCCH due to downlink quality fast fading. If the counter's value
is large, it indicates that handover on SDCCH often occurs when
the downlink quality becomes worse.
After BSC receives the measurement report on SDCCH, it performs
handover decision. If the handover decision indicates that handover is required and the handover is due to downlink quality fast
fading, the counter increments. The measurement point is A, as

Unit
Statistics Object
Times
Cell
Description
This counter counts the number of handover attempts on TCH/F

TCH/F due to downlink quality fast fading. If the counter's value is
large, it indicates that handover on TCH/F often occurs when the
downlink quality becomes worse.
684
After BSC receives the measurement report on TCH/F, it performs


Unit
Statistics Object
Times
Cell
Description
This counter counts the number of handover attempts on TCH/H

TCH/H due to downlink quality fast fading. If the counter's value
is large, it indicates that handover on TCH/H often occurs when
the downlink quality becomes worse.
After BSC receives the measurement report on TCH/H, it performs

Unit
Statistics Object
Times
Cell
685
686
Chapter
13
RMM Call Drop

Measurement
Table of Contents
Overview........................................................................ 690
C901070001 Number of SDCCH drops due to loss of contact
with RANA ...................................................................... 690
C901070002 Number of SDCCH drops due to radio link failure ................................................................................ 691
C901070003 Number of SDCCH drops due to LAPD link failure ................................................................................ 692
C901070004 Number of SDCCH drops due to OMC-R forced
release........................................................................... 693
C901070005 Number of SDCCH drops due to forced release
by other calls .................................................................. 694
C901070007 Number of SDCCH drops due to other failure ................................................................................ 695
C901070008 Number of signaling TCH/F drops due to loss of
contact with RANA ........................................................... 696
C901070009 Number of signaling TCH/F drops due to radio
link failure ...................................................................... 697
C901070010 Number of signaling TCH/F drops due to LAPD
link failure ...................................................................... 698
C901070011 Number of signaling TCH/F drops due to OMC-R
forced release ................................................................. 699
C901070012 Number of signaling TCH/F drops due to forced
release by other calls ....................................................... 700
C901070014 Number of signaling TCH/F drops due to other
failure ............................................................................ 701
C901070015 Number of voice TCH/F drops due to loss of contact with RANA................................................................ 702
C901070017 Number of voice TCH/F drops due to LAPD link
failure ............................................................................ 703
C901070018 Number of voice TCH/F drops due to OMC-R
forced release ................................................................. 704
C901070019 Number of voice TCH/F drops due to forced release by other calls .......................................................... 706
C901070021 Number of voice TCH/F drops due to other failure ................................................................................ 707
C901070022 Number of data TCH/F drops due to loss of contact with RANA................................................................ 708
C901070023 Number of data TCH/F drops due to radio link
failure ............................................................................ 709
C901070024 Number of data TCH/F drops due to LAPD link
failure ............................................................................ 710
C901070025 Number of data TCH/F drops due to OMC-R
forced release ................................................................. 711
687
C901070026 Number of data TCH/F drops due to forced release by other calls .......................................................... 713
C901070028 Number of data TCH/F drops due to other failure ................................................................................ 714
C901070029 Number of signaling TCH/H drops due to loss of
contact with RANA ........................................................... 715
C901070030 Number of signaling TCH/H drops due to radio
link failure ...................................................................... 716
C901070031 Number of signaling TCH/H drops due to LAPD
link failure ...................................................................... 717
C901070032 Number of signaling TCH/H drops due to OMC-R
forced release ................................................................. 717
C901070033 Number of signaling TCH/H drops due to forced
release by other calls ....................................................... 718
C901070035 Number of signaling TCH/H drops due to other
failure ............................................................................ 719
C901070036 Number of voice TCH/H drops due to loss of contact with RANA................................................................ 720
C901070038 Number of voice TCH/H drops due to LAPD link
failure ............................................................................ 721
C901070039 Number of voice TCH/H drops due to OMC-R
forced release ................................................................. 723
C901070040 Number of voice TCH/H drops due to forced release by other calls .......................................................... 724
C901070042 Number of voice TCH/H drops due to other failure ................................................................................ 725
C901070043 Number of data TCH/H drops due to loss of contact with RANA................................................................ 726
C901070044 Number of data TCH/H drops due to radio link
failure ............................................................................ 728
C901070045 Number of data TCH/H drops due to LAPD link
failure ............................................................................ 729
C901070046 Number of data TCH/H drops due to OMC-R
forced release ................................................................. 730
C901070047 Number of data TCH/H drops due to forced release by other calls .......................................................... 732
C901070049 Number of data TCH/H drops due to other failure ................................................................................ 733
C901070053 Number of SDCCH link failures........................ 734
C901070054 Number of TCH/F link failures ......................... 735
C901070055 Number of TCH/H link failures ........................ 737
C901070056 Number of RANA link releases due to other cause
on SDCCH ...................................................................... 738
on TCH/F........................................................................ 739
on TCH/H ....................................................................... 739
C901070059 Number of SDCCH short messages drops ......... 740
C901070060 Number of TCH/F short messages drops........... 741
C901070061 Number of TCH/H short messages drops .......... 741
C901070062 Number of TCH/F drops due to CS channel is
forced release by PS ........................................................ 742
C901070063 Number of TCH/H drops due to CS channel is
forced release by PS ........................................................ 742
C901070064 Number of SDCCH drops due to eMLPP forced
handover........................................................................ 743
C901070065 Number of signaling TCH/F drops due to eMLPP
forced handover .............................................................. 743
C901070066 Number of voice TCH/F drops due to eMLPP
forced handover .............................................................. 744
688
Chapter 13 RMM Call Drop Measurement
C901070067 Number of data TCH/F drops due to eMLPP

forced handover .............................................................. 745
C901070068 Number of sigaling TCH/H drops due to eMLPP
forced handover .............................................................. 746
C901070069 Number of voice TCH/H drops due to eMLPP
forced handover .............................................................. 746
C901070070 Number of data TCH/H drops due to eMLPP
forced handover .............................................................. 747
C901070071 Bad quality of UL receiving (On SDCCH)........... 748
C901070072 Bad quality of DL receiving (On SDCCH)........... 749
C901070073 Lower electrical level of UL (On SDCCH)........... 750
C901070074 Lower electrical level of DL (On SDCCH)........... 751
C901070075 Number of signaling drops due to TA too far (On
SDCCH) ......................................................................... 752
C901070076 Reasons of the other radios (On SDCCH).......... 753
C901070077 Bad quality of UL receiving (On TCH/F) ............ 754
C901070078 Bad quality of DL receiving (On TCH/F) ............ 755
C901070079 Lower electrical level of UL (On TCH/F) ............ 756
C901070080 Lower electrical level of DL (On TCH/F) ............ 757
TCH/F) ........................................................................... 758
C901070082 Reasons of the other radios (On TCH/F) ........... 759
C901070083 Bad quality of UL receiving (On TCH/H)............ 761
C901070084 Bad quality of DL receiving (On TCH/H) ........... 762
C901070085 Lower electrical level of UL (On TCH/H)............ 763
C901070086 Lower electrical level of DL (On TCH/H)............ 764
TCH/H) .......................................................................... 765
C901070088 Reasons of the other radios (On TCH/H)........... 766
C901070089 The Count of Drop Call caused by "IP Resource
Reset"............................................................................ 767
C901070090 Number of FR_V1 radio link fail....................... 768
C901070093 Number of HR_V1 radio link fail ...................... 769
C901070094 Number of HR_V3 radio link fail ...................... 769
C901070095 Number of signaling TCH/F drops due to BIPB
Active/Standby Changeover .............................................. 770
C901070096 Number of voice TCH/F drops due to BIPB Active/Standby Changeover ................................................. 770
C901070097 Number of data TCH/F drops due to BIPB Active/Standby Changeover ................................................. 770
C901070098 Number of signaling TCH/H drops due to BIPB
C901070099 Number of voice TCH/H drops due to BIPB Active/Standby Changeover ................................................. 771
C901070100 Number of data TCH/H drops due to BIPB Active/Standby Changeover ................................................. 771
C901070101 Number of SDCCH drops due to LAPD Active/Standby Changeover ................................................. 772
C901070102 Number of voice TCH/F drops due to LAPD Active/Standby Changeover ................................................. 772
C901070103 Number of data TCH/F drops due to LAPD Active/Standby Changeover ................................................. 772
C901070104 Number of signaling TCH/F drops due to LAPD
C901070105 Number of voice TCH/H drops due to LAPD Active/Standby Changeover ................................................. 773
C901070106 Number of data TCH/H drops due to LAPD Active/Standby Changeover ................................................. 774
689
C901070107 Number of signaling TCH/H drops due to LAPD

C901070108 Number of voice TCH/F drops due to handover
fail for power adjustment.................................................. 774
C901070109 Number of voice TCH/H drops due to handover
fail for power adjustment.................................................. 775
C901070110 Number of SDCCH drops due to BIPB Active/Standby Changeover ................................................. 775
C901070111 Number of SDCCH drops due to BTS failure ................................................................................ 776
C901070112 Number of signaling TCH/F drops due to BTS
failure ............................................................................ 777
C901070113 Number of voice TCH/F drops due to BTS failure ................................................................................ 778
C901070114 Number of data TCH/F drops due to BTS failure ................................................................................ 779
C901070115 Number of signaling TCH/H drops due to BTS
failure ............................................................................ 780
C901070116 Number of voice TCH/H drops due to BTS failure ................................................................................ 781
C901070117 Number of data TCH/H drops due to BTS failure ................................................................................ 782
C901070118 Call Drop by Releasing Local Switch................. 783
Overview
Channels that take part in the measurement statistic include SDCCH, TCH/F and TCH/H. Service types include signaling, voice and
data. Counted call drop causes include RMM losses contact with
SMM, BTS radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover failure, as well as
other failure.
SDCCH drops due to loss of
contact with RANA
Definition
690
Number of SDCCH drops due to loss of contact with RANA
Description
This counter counts the number of failures due to loss of contact

with SMM. The counter increments if the phenomenon that call
drops after MS has obtained SDCCH is caused by the loss of contact
with SMM.
Usage
This counter is used to find out the frequency of failures due to

loss of contact with SMM.
Measurement
Point
The counter counts the number of failures due to loss of contact

with SMM in the following two cases:
After link between RANCS and RANA has been established on

SDCCH, heartbeat handshake is carried out. If RANCS or RANA
can not receive heartbeat message from each other during 4
unit time, then it is regarded as link failure and the counter
increments; meanwhile, BSC release the channel and instance,
the measurement point is A1, as shown in Figure 757.
FIGURE 757 CALL DROP DUE TO A-INTERFACE FAILURE IN IMMEDIATE
ASSIGNMENT PROCESS
Unit
RANCS forwards EST_IND message to RANA after receiving it on

SDCCH; if no link establishment message on A-interface from
RANA is received, the counter increments; meanwhile, BSC
release the channel and instance, the measurement point is
Times
SDCCH drops due to radio
link failure
Definition
Number of SDCCH drops due to radio link failure
Description
This counter counts the number of call drop due to radio link failures (On SDCCH). The counter increments if the phenomenon that
call drops after MS has obtained SDCCH is caused by radio link failures.
Usage
radio link failures (On SDCCH).
Measurement
Point
The counter increments when BSC receives CONNectiOn FAILure INmessage on Abis interface on SDCCH. The measurement
DicatiOn
691
FIGURE 758 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE

ASSIGNMENT PROCESS
Unit
Related Features
Times
ZGO-04-02-007 AMR Radio Link Timers
SDCCH drops due to LAPD
link failure
Definition
692
Number of SDCCH drops due to LAPD link failure
Description
This counter counts the number of call drop due to LAPD link failures (On SDCCH). The counter increments if the phenomenon that
call drops after MS has obtained SDCCH is caused by LAPD link failures.
Usage
LAPD link failures (On SDCCH).
Measurement
Point
The counter increments when BSC receives DLREL_IND message

from LAPD on SDCCH. The measurement point is A, as shown in
Figure 759.
FIGURE 759 CALL DROP DUE TO LAPD LINK FAILURE IN IMMEDIATE

ASSIGNMENT PROCESS
Unit
Times
SDCCH drops due to
OMC-R forced release
Definition
Number of SDCCH drops due to OMC-R forced release
Description
This counter counts the number of call drop due to OMC-R forced
releases (on SDCCH). The counter increments if the phenomenon
that call drops after MS has obtained SDCCH is caused by OMC-R
forced releases.
Usage
OMC-R forced releases (on SDCCH).
Measurement
Point
The counter increments when BSC receives OMC-R forced release

message from database on SDCCH. The measurement point is A,
693
FIGURE 760 CALL DROP DUE TO OMC-R FORCED RELEASE IN IMMEDIATE

ASSIGNMENT PROCESS
Unit
Times
SDCCH drops due to forced
release by other calls
Definition
694
Number of SDCCH drops due to forced release by other calls
Description
This counter counts the number of call drop due to forced releases
by other calls (On SDCCH). The counter increments if the phenomenon that call drops after MS has obtained SDCCH is caused
by forced releases by other calls.
Usage
forced releases by other calls (On SDCCH).
Measurement
Point
The counter increments when BSC receives forced release message from other calls on SDCCH. The measurement point is A, as
shown inFigure 761.
FIGURE 761 CALL DROP DUE TO FORCED RELEASE BY OTHER CALLS IN

IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
SDCCH drops due to other
failure
Definition
Description
Number of SDCCH drops due to other failure

This counter counts the number of call drop due to other failures
(On SDCCH). The counter increments if the phenomenon that call
drops after MS has obtained SDCCH is caused by other failures
except the causes mentioned above (loss of contact with RANA,
radio link failure, LAPD link failure, OMCR forced release, forced
release by other calls, handover failure).
At present, other failure causes are that T3107 is overtime under
ASSIGN status, timer that waits for access is overtime and forced
release caused by other faults, which include resource fault, BTS
turnover, and AIPB fault.
Usage
other failures (On SDCCH).
Measurement
Point
The counter increments when T3107 is overtime under ASSIGN

status on SDCCH, or when timer that waits for access is overtime
or forced release caused by other faults. The measurement point
695
Unit
OF
TWAITMSACCESS OVERTIME
Times
to loss of contact with RANA
696
Definition
Number of signaling TCH/F drops due to loss of contact with RANA
Description
This counter counts the number of failures due to RANCS losing

contact with RANA (on TCH/F signaling channel). The counter increments if the phenomenon that call drops after MS has obtained
TCH/F signaling channel is caused by failures due to RANCS losing
contact with RANA.
Usage

RANCS losing contact with RANA (on TCH/F signaling channel).
Measurement
Point

with RANA (On TCH/F signaling) in the following two cases:

TCH/F signaling channel, heartbeat handshake is carried out. If
RANCS or RANA can not receive heartbeat message from each
other during 4 unit times, then it is regarded as link failure and
the counter increments; meanwhile, BSC releases the channel
and instance, the measurement point is A1, as shown in Figure
763.

TCH/F signaling; if no link establishment message on A-interface from RANA is received, the counter increments; mean-
while, BSC releases the channel and instance, the measurement point is A2, as shown inFigure 763.
ASSIGNMENT PROCESS
Unit
Related Features
Times
to radio link failure
Definition
Number of signaling TCH/F drops due to radio link failure
Description
This counter counts the number of call drop due to radio link failures (On TCH/F signaling). The counter increments if the phenomenon that call drops after MS has obtained TCH/F signaling channel
is caused by radio link failures.
Usage
radio link failures (On TCH/F signaling).
Measurement
Point
The counter increments when BSC receives CONNectiOn FAILure INmessage on Abis interface on TCH/F signaling channel.
DicatiOn
697

ASSIGNMENT PROCESS
Unit
Related Features
Times
to LAPD link failure
Definition
698
Number of signaling TCH/F drops due to LAPD link failure
Description
This counter counts the number of call drops due to LAPD link failures (on TCH/F signaling channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/F signaling
channel is caused by LAPD link failures.
Usage
LAPD link failures (on TCH/F signaling channel).
Measurement
Point

from LAPD on TCH/F signaling channel. The measurement point

ASSIGNMENT PROCESS
Unit
Related Features
Times
to OMC-R forced release
Definition
Number of signaling TCH/F drops due to OMC-R forced release
Description
releases (on TCH/F signaling channel). The counter increments
if the phenomenon that call drops after MS has obtained TCH/F
signaling channel is caused by OMC-R forced releases.
Usage
OMC-R forced releases (on TCH/F signaling channel).
Measurement
Point

message from database on TCH/F signaling channel. The measurement point is A, as shown in Figure 766.
699

ASSIGNMENT PROCESS
Unit
Related Features
Times
to forced release by other
calls
700
Definition
Number of signaling TCH/F drops due to forced release by other

calls
Description
by other calls (on TCH/F signaling channel). The counter increments if the phenomenon that call drops after MS has obtained
TCH/F signaling channel is caused by forced releases by other calls.
Usage
forced releases by other calls (on TCH/F signaling channel).
Measurement
Point
The counter increments when BSC receives forced release message from other calls on TCH/F signaling channel. The measurement point is A, as shown in Figure 767.

Unit
Related Features
Times
to other failure
Definition
Description
Number of signaling TCH/F drops due to other failure

(on TCH/F signaling channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F signaling
channel is caused by other failures except the causes mentioned
above (loss of contact with RANA, radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover
failure).
Usage
other failures (on TCH/F signaling channel).
Measurement
Point

status on TCH/F, or when timer that waits for access is overtime
701
Unit
Related Features
OF
Times
loss of contact with RANA
Definition
702
Number of voice TCH/F drops due to loss of contact with RANA
Description

contact with RANA (on TCH/F voice channel). The counter increments if the phenomenon that call drops after MS has obtained
TCH/F voice channel is caused by failures due to RANCS losing
contact with RANA (on TCH/F voice channel).
Usage

RANCS losing contact with RANA (on TCH/F voice channel).
Measurement
Point

with RANA (on TCH/F voice channel) in the following two cases:

TCH/F voice channel, heartbeat handshake is carried out. If
and instance.
RANCS forwards EST_IND message to RANA after receiving it

on TCH/F voice channel; if no link establishment message on
A-interface from RANA is received, the counter increments;
meanwhile, BSC releases the channel and instance, the measurement point is A, as shown in Figure 769.
FIGURE 769 CALL DROP DUE TO A-INTERFACE FAILURE IN ASSIGNMENT
PROCESS
Unit
Related Features
Times
LAPD link failure
Definition
Number of voice TCH/F drops due to LAPD link failure
Description
This counter counts the number of call drop due to LAPD link failures (on TCH/F voice channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F voice channel is caused by LAPD link failures.
Usage
LAPD link failures (on TCH/F voice channel).
703
Measurement
Point
The counter increments when BSC receives DLREL_INDmessage from

LAPD on TCH/F voice channel. The measurement point is A, as
FIGURE 770 CALL DROP DUE TO LAPD LINK FAILURE IN ASSIGNMENT
PROCESS
Unit
Related Features
Times
Definition
Description
704
Number of voice TCH/F drops due to OMC-R forced release

releases (on TCH/F voice channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/F voice

channel is caused by OMC-R forced releases.
Usage
OMC-R forced releases (on TCH/F voice channel).
Measurement
Point

message from database on TCH/F voice channel. The measurement point is A, as shown in Figure 771.
FIGURE 771 CALL DROP DUE TO OMC-R FORCED RELEASE IN ASSIGNMENT
PROCESS
Unit
Related Features
Times
705
forced release by other calls
Definition
Number of voice TCH/F drops due to forced release by other calls
Description
by other calls (on TCH/F voice channel). The counter increments
if the phenomenon that call drops after MS has obtained TCH/F
voice channel is caused by forced releases by other calls.
Usage
forced releases by other calls (on TCH/F voice channel).
Measurement
Point
The counter increments when BSC receives forced release message from other calls on TCH/F voice channel. The measurement
ASSIGNMENT PROCESS
Unit
706
Times
Related Features
other failure
Definition
Description
Number of voice TCH/F drops due to other failure

(on TCH/F voice channel). It indicates the call drop case at call
establishment phase due to assignment failure. The counter increments if the phenomenon that call drops after MS has obtained
TCH/F voice channel is caused by other failures except the causes
mentioned above (loss of contact with RANA, radio link failure,
LAPD link failure, OMCR forced release, forced release by other
calls, handover failure).
This counter does not count the call drops due to intra-cell handover failure.
Usage
other failures (on TCH/F voice channel).
Measurement
Point

OF
707
Unit
Related Features
Times
Definition
708
Number of data TCH/F drops due to loss of contact with RANA
Description

contact with RANA (on TCH/F data channel). The counter increments if the phenomenon that call drops after MS has obtained
TCH/F data channel is caused by failures due to RANCS losing contact with RANA (on TCH/F data channel).
Usage

RANCS losing contact with RANA (on TCH/F data channel).
Measurement
Point

with RANA (on TCH/F data channel) in the following two cases:

TCH/F data channel, heartbeat handshake is carried out. If
and instance, the measurement point is A, as shown in Figure
774.

on TCH/F data channel; if no link establishment message on
meanwhile, BSC releases the channel and instance.

PROCESS
Unit
Related Features
Times
radio link failure
Definition
Number of data TCH/F drops due to radio link failure
Description
This counter counts the number of call drop due to radio link failures (on TCH/F data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F data channel
Usage
radio link failures (on TCH/F data channel).
Measurement
Point
The counter increments when BSC receives CONNectiOn FAILure INmessage on Abis interface on TCH/F data channel. The
DicatiOn
709
FIGURE 775 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT

PROCESS
Unit
Related Features
Times
LAPD link failure
Definition
Description
710
Number of data TCH/F drops due to LAPD link failure

This counter counts the number of call drop due to LAPD link failures (on TCH/F data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F data channel
is caused by LAPD link failures.
Usage
LAPD link failures (on TCH/F data channel).
Measurement
Point

from LAPD on TCH/F data channel. The measurement point is A,
PROCESS
Unit
Related Features
Times
Definition
Number of data TCH/F drops due to OMC-R forced release
711
Description
releases (on TCH/F data channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/F data
Usage
OMC-R forced releases (on TCH/F data channel).
Measurement
Point

message from database on TCH/F data channel. The measurement point is A, as shown in Figure 777.
PROCESS
Unit
Related Features
712
Times
Definition
Number of data TCH/F drops due to forced release by other calls
Description
by other calls (on TCH/F data channel). The counter increments if
the phenomenon that call drops after MS has obtained TCH/F data
channel is caused by forced releases by other calls.
Usage
forced releases by other calls (on TCH/F data channel).
Measurement
Point
The counter increments when BSC receives forced release message from other calls on TCH/F data channel. The measurement
ASSIGNMENT PROCESS
Unit
Times
713
Related Features
other failure
Definition
Description
Number of data TCH/F drops due to other failure

(on TCH/F data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F data channel is
caused by other failures except the causes mentioned above (loss
of contact with RANA, radio link failure, LAPD link failure, OMCR
forced release, forced release by other calls, handover failure).
Usage
other failures (on TCH/F data channel).
Measurement
Point

Unit
Related Features
714
OF
Times
to loss of contact with RANA
Definition
Number of signaling TCH/H drops due to loss of contact with RANA
Description

contact with RANA (on TCH/H signaling channel). The counter increments if the phenomenon that call drops after MS has obtained
TCH/H signaling channel is caused by failures due to RANCS losing
contact with RANA (on TCH/H signaling channel).
Usage

RANCS losing contact with RANA (on TCH/H signaling channel).
Measurement
Point
The counter counts the number of failures due to loss of contact with RANA (on TCH/H signaling channel) in the following two
cases:

TCH/H signaling channel, heartbeat handshake is carried out.
If RANCS or RANA can not receive heartbeat message from
each other during 4 unit times, then it is regarded as link failure and the counter increments; meanwhile, BSC releases the
channel and instance, the measurement point is A1, as shown
in Figure 780.

TCH/H signaling; if no link establishment message on A-interface from RANA is received, the counter increments; meanwhile, BSC releases the channel and instance, the measurement point is A2, as shown in Figure 780.

ASSIGNMENT PROCESS
Unit
Related Features
Times
715
to radio link failure
Definition
Number of signaling TCH/H drops due to radio link failure
Description
This counter counts the number of call drop due to radio link failures (on TCH/H signaling channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/H signaling channel is caused by radio link failures.
Usage
radio link failures (on TCH/H signaling channel).
Measurement
Point
The counter increments when BSC receives CONNectiOn FAILure INmessage on Abis interface on TCH/H signaling channel.
DicatiOn

ASSIGNMENT PROCESS
Unit
Related Features
Times
716
to LAPD link failure
Definition
Number of signaling TCH/H drops due to LAPD link failure
Description
This counter counts the number of call drop due to LAPD link failures (on TCH/H signaling channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/H signaling channel is caused by LAPD link failures.
Usage
LAPD link failures (on TCH/H signaling channel).
Measurement
Point

from LAPD on TCH/H signaling channel. The measurement point
ASSIGNMENT PROCESS
Unit
Related Features
Times
to OMC-R forced release
Definition
Number of signaling TCH/H drops due to OMC-R forced release
717
Description
releases (on TCH/H signaling channel). The counter increments
if the phenomenon that call drops after MS has obtained TCH/H
signaling channel is caused by OMC-R forced releases.
Usage
OMC-R forced releases (on TCH/H signaling channel).
Measurement
Point

message from database on TCH/H signaling channel. The measurement point is A, as shown in Figure 783.
ASSIGNMENT PROCESS
Unit
Related Features
Times
to forced release by other
calls
718
Definition
Number of signaling TCH/H drops due to forced release by other

calls
Description
by other calls (on TCH/H signaling channel). The counter increments if the phenomenon that call drops after MS has obtained
TCH/H signaling channel is caused by forced releases by other
calls.
Usage
forced releases by other calls (on TCH/H signaling channel).
Measurement
Point
The counter increments when BSC receives forced release message from other calls on TCH/H signaling channel. The measurement point is A, as shown in Figure 784.
Unit
Related Features
Times
to other failure
Definition
Description
Number of signaling TCH/H drops due to other failure

(on TCH/H signaling channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H signaling
channel is caused by other failures except the causes mentioned
above (loss of contact with RANA, radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover
failure).
Usage
other failures (on TCH/H signaling channel).
Measurement
Point

status on TCH/H, or when timer that waits for access is overtime
719
Unit
Related Features
OF
Times
Definition
Number of voice TCH/H drops due to loss of contact with RANA
Description

contact with RANA (on TCH/H voice channel). The counter increments if the phenomenon that call drops after MS has obtained
TCH/H voice channel is caused by failures due to RANCS losing
contact with RANA (on TCH/H voice channel).
Usage

RANCS losing contact with RANA (on TCH/H voice channel).
Measurement
Point

with RANA (on TCH/H voice channel) in the following two cases:
720

TCH/H voice channel, heartbeat handshake is carried out. If
and instance.
RANCS forwards EST_INDmessage to RANA after receiving it on

TCH/H voice channel; if no link establishment message on A-interface from RANA is received, the counter increments; meanwhile, BSC releases the channel and instance, the measurement point is A, as shown in Figure 786.
PROCESS
Unit
Related Features
Times
LAPD link failure
Definition
Description
Number of voice TCH/H drops due to LAPD link failure

This counter counts the number of call drop due to LAPD link failures (on TCH/H voice channel). The counter increments if the
721
phenomenon that call drops after MS has obtained TCH/H voice

channel is caused by LAPD link failures.
Usage
LAPD link failures (on TCH/H voice channel).
Measurement
Point

from LAPD on TCH/H voice channel. The measurement point is A,
PROCESS
Unit
Related Features
Times
722
Definition
Number of voice TCH/H drops due to OMC-R forced release
Description
releases (on TCH/H voice channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/H voice
Usage
OMC-R forced releases (on TCH/H voice channel).
Measurement
Point

message from database on TCH/H voice channel. The measurement point is A, as shown in Figure 788.
PROCESS
Unit
Times
723
Related Features

724
Definition
Number of voice TCH/H drops due to forced release by other calls
Description
by other calls (on TCH/H voice channel). The counter increments
if the phenomenon that call drops after MS has obtained TCH/H
voice channel is caused by forced releases by other calls.
Usage
forced releases by other calls (on TCH/H voice channel).
Measurement
Point
The counter increments when BSC receives forced release message from other calls on TCH/H voice channel. The measurement

ASSIGNMENT PROCESS
Unit
Related Features
Times
other failure
Definition
Description
Number of voice TCH/H drops due to other failure

(on TCH/H voice channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H voice channel is
725
Usage
other failures (on TCH/H voice channel).
Measurement
Point

Unit
Related Features
OF
Times
Definition
Description
726
Number of data TCH/H drops due to loss of contact with RANA

contact with RANA (on TCH/H data channel). The counter increments if the phenomenon that call drops after MS has obtained
TCH/H data channel is caused by failures due to RANCS losing

contact with RANA (on TCH/H data channel).
Usage

RANCS losing contact with RANA (on TCH/H data channel).
Measurement
Point

with RANA (on TCH/H data channel) in the following two cases:

TCH/H data channel, heartbeat handshake is carried out. If
and instance.

on TCH/H data channel; if no link establishment message on
meanwhile, BSC releases the channel and instance, the measurement point is A, as shown in Figure 791.
PROCESS
Unit
Related Features
Times
727
radio link failure
Definition
Number of data TCH/H drops due to radio link failure
Description
This counter counts the number of call drop due to radio link failures (on TCH/H data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H data channel
Usage
radio link failures (on TCH/H data channel).
Measurement
Point
The counter increments when BSC receives CONNectiOn FAILure INmessage on Abis interface on TCH/H data channel. The
DicatiOn

PROCESS
Unit
728
Times
Related Features

LAPD link failure
Definition
Number of data TCH/H drops due to LAPD link failure
Description
This counter counts the number of call drop due to LAPD link failures (on TCH/H data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H data channel
is caused by LAPD link failures.
Usage
LAPD link failures (on TCH/H data channel).
Measurement
Point

from LAPD on TCH/H data channel. The measurement point is A,
729

PROCESS
Unit
Related Features
Times
Definition
Description
730
Number of data TCH/H drops due to OMC-R forced release

releases (on TCH/H data channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/H data
Usage
OMC-R forced releases (on TCH/H data channel).
Measurement
Point
The counter increments when BSC receives OMCR forced release

message from database on TCH/H data channel. The measurement point is A, as shown in Figure 794.
PROCESS
Unit
Related Features
Times
731
Definition
Number of data TCH/H drops due to forced release by other calls
Description
by other calls (on TCH/H data channel). The counter increments if
the phenomenon that call drops after MS has obtained TCH/H data
channel is caused by forced releases by other calls.
Usage
forced releases by other calls (on TCH/H data channel).
Measurement
Point
The counter increments when BSC receives forced release message from other calls on TCH/H data channel. The measurement
ASSIGNMENT PROCESS
Unit
732
Times
Related Features

other failure
Definition
Description
Number of data TCH/H drops due to other failure

(on TCH/H data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H data channel is
Usage
other failures (on TCH/H data channel).
Measurement
Point

Unit
OF
Times
733
Related Features

SDCCH link failures
Definition
Number of SDCCH link failures
Description
This counter counts the number of SDCCH link failures. The

counter increments when RANA launches abnormal release flow
to RANCS due to SCCP link failure after MS has obtained SDCCH.
Usage
This counter is used to find out the frequency of SDCCH link failures.
Measurement
Point
The counter counts the number of abnormal release flow launched

by RANA to RANCS due to SCCP link failure on SDCCH, including
the following cases:
T9105 is overtime, the measurement point is A2, as shown in

Figure 797.
FIGURE 797 CALL DROP DUE TO SCCP FAILURE IN IMMEDIATE
ASSIGNMENT PROCESS
734
Unit
T9104 is overtime and the number of maximum failure times

is reached, the measurement point is A3, as shown in Figure
797.

Figure 797.
After RANA process has been established, EST_IND message sent

by MS or handover request sent by MSC is not received within
the set time, the measurement point is A1, as shown in Figure
797.
BSC receives MSC reset message.
CONNECT_ID requested by RANA is failed.
BSC receives link release command from MSC.
Times
TCH/F link failures
Definition
Number of TCH/F link failures
Description
This counter counts the number of TCH/F link failures. The counter
increments when RANA launches abnormal release flow to RANCS
due to SCCP link failure after MS has obtained TCH/F.
Usage
This counter is used to find out the frequency of TCH/F link failures.
Measurement
Point

by RANA to RANCS due to SCCP link failure on TCH/F in the following cases:

Figure 798.
735

ASSIGNMENT PROCESS
Unit
Related Features

798.
T9101 is overtime, the measurement point is A4, as shown

inFigure 798.

798.
Times
736
TCH/H link failures
Definition
Number of TCH/H link failures
Description
This counter counts the number of TCH/H link failures. The counter
increments when RANA launches abnormal release flow to RANCS
due to SCCP link failure after MS has obtained TCH/H.
Usage
This counter is used to find out the frequency of TCH/H link failures.
Measurement
Point

by RANA to RANCS due to SCCP link failure on TCH/H in the following cases:

Figure 799.
ASSIGNMENT PROCESS

799.

Figure 799.
737
Unit
Related Features

799.
Times
RANA link releases due to
other cause on SDCCH
Definition
Number of RANA link releases due to other cause on SDCCH
Description
This counter counts the number of RANA link releases by other

cause on SDCCH (except that SCCP link release command message is received). The counter increments if RANA link release
occurs after MS has obtained SDCCH.
Usage
This counter is used to find out the frequency of RANA link releases
by other cause on SDCCH.
Measurement
Point
The counter increments when the content of HO_REQ message is

incorrect. The measurement point is A2, as shown in Figure 800.
FIGURE 800 CALL DROP DUE TO INTER-BSC HANDOVER FAILURE
Unit
738
Times
other cause on TCH/F
Definition
Number of RANA link releases due to other cause on TCH/F
Description

cause on TCH/F (except that SCCP link release command message
is received). The counter increments if RANA link release occurs
after MS has obtained TCH/F.
Usage
by other cause on TCH/F.
Measurement
Point

Unit
Related Features
Times
other cause on TCH/H
Definition
Number of RANA link releases due to other cause on TCH/H
Description

cause on TCH/H (except that SCCP link release command message
is received). The counter increments if RANA link release occurs
after MS has obtained TCH/H.
Usage
by other cause on TCH/H.
739
Measurement
Point

Unit
Related Features
Times
SDCCH short messages
drops
Definition
Description
This counter counts the number of SDCCH short messages drops.

The counter increments when call drops after MS has obtained
SDCCH for short message service.
Usage
This counter is used to find out the frequency of SDCCH short messages drops.
Measurement
Point
The counter increments when call drops due to radio link failure or
LAPD link release or handover failure while doing short message
service.
Unit
740
Number of SDCCH short messages drops
Times
TCH/F short messages
drops
Definition
Number of TCH/F short messages drops
Description
This counter counts the number of TCH/F short messages drops.

TCH/F for short message service.
Usage
This counter is used to find out the frequency of TCH/F short messages drops.
Measurement
Point
service.
Unit
Related Features
Times
TCH/H short messages
drops
Definition
Number of TCH/H short messages drops
Description
This counter counts the number of TCH/H short messages drops.

TCH/H for short message service.
Usage
This counter is used to find out the frequency of TCH/H short messages drops.
Measurement
Point
service.
Unit
Related Features
Times
741
TCH/F drops due to CS
channel is forced release by
PS
Definition
Number of TCH/F drops due to CS channel is forced release by PS
Description
When CS service channel is forcibly released due to PS service,

handover is initiated, and call drop will occur if TCH/F channel request fails. In such a case, the counter increments.
Usage
This counter is used to find out the frequency of call drops due to
TCH/F channel request failure when CS service channel is forcedly
released due to PS service.
Measurement
Point
The counter increments when call drops due to TCH/F channel request failure when CS service is forcedly released due to PS service.
Unit
Related Features
Times
TCH/H drops due to CS
channel is forced release by
PS
Definition
Number of TCH/H drops due to CS channel is forced release by PS
Description
When CS service channel is forcibly released due to PS service,

handover is initiated, and call drop will occur if TCH/H channel
request fails. In such a case, the counter increments.
Usage
This counter is used to find out the frequency of call drops due to
TCH/H channel request failure when CS service channel is forcedly
released due to PS service.
Measurement
Point
The counter increments when call drops due to TCH/H channel

request failure when CS service is forcedly released due to PS service.
Unit
Related Features
742
Times
SDCCH drops due to
eMLPP forced handover
Definition
Number of SDCCH drops due to eMLPP forced handover
Description
This counter counts the number of call drops on SDCCH due to

eMLPP forced handover. After MS obtains SDCCH, call drop occurs.
If the problem is caused by eMLPP forced handover, the counter
increments.
Usage
due to eMLPP forced handover.
Measurement
Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on SDCCH. The measurement point is A, as shown in
Figure 803.
FIGURE
EMLPP
Unit
803 MEASUREMENT POINT OF NUMBER OF SDCCH DROPS DUE TO

FORCED HANDOVER
Times
to eMLPP forced handover
Definition
Number of signaling TCH/F drops due to eMLPP forced handover
Description
This counter counts the number of call drops on signaling TCH/F

due to eMLPP forced handover. After MS obtains signaling TCH/F,
call drop occurs. If the problem is caused by eMLPP forced handover, the counter increments.
Usage
This counter is used to find out the frequency of call drop on signaling TCH/F due to eMLPP forced handover
743
Measurement
Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on signaling TCH/F. The measurement point is A, as
FIGURE
EMLPP
Unit

FORCED HANDOVER
Times
Definition
744
Number of voice TCH/F drops due to eMLPP forced handover
Description
This counter counts the number of call drops on voice TCH/F due
to eMLPP forced handover. After MS obtains voice TCH/F, call drop
occurs. If the problem is caused by eMLPP forced handover, the
counter increments.
Usage
This counter is used to find out the frequency of call drop on voice
TCH/F due to eMLPP forced handover.
Measurement
Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on voice TCH/F. The measurement point is A, as shown
in Figure 805.
FIGURE
EMLPP
Unit

FORCED HANDOVER
Times
Definition
Number of data TCH/F drops due to eMLPP forced handover
Description
This counter counts the number of call drops on data TCH/F due
to eMLPP forced handover. After MS obtains data TCH/F, call drop
counter increments.
Usage
This counter is used to find out the frequency of call drop on data
TCH/F due to eMLPP forced handover.
Measurement
Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on data TCH/F. The measurement point is A, as shown
in Figure 806.
FIGURE
EMLPP

FORCED HANDOVER
745
Unit
Times
sigaling TCH/H drops due to
Definition
Number of signaling TCH/H drops due to eMLPP forced handover
Description
This counter counts the number of call drops on signaling TCH/H

due to eMLPP forced handover. After MS obtains signaling TCH/H,
call drop occurs. If the problem is caused by eMLPP forced handover, the counter increments.
Usage
This counter is used to find out the frequency of call drop on signaling TCH/H due to eMLPP forced handover.
Measurement
Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on signaling TCH/H. The measurement point is A, as
FIGURE
EMLPP
Unit

FORCED HANDOVER
Times
Definition
Description
746
Number of voice TCH/H drops due to eMLPP forced handover

This counter counts the number of call drops on voice TCH/H due
to eMLPP forced handover. After MS obtains voice TCH/H, call drop

counter increments.
Usage
This counter is used to find out the frequency of call drop on voice
TCH/H due to eMLPP forced handover.
Measurement
Point
The counter counts when T3107 and T3103 are timeout under
ASSIGN status on voice TCH/H. The measurement point is A, as
FIGURE
EMLPP
Unit

FORCED HANDOVER
Times
Definition
Number of data TCH/H drops due to eMLPP forced handover
Description
This counter counts the number of call drops on data TCH/H due
to eMLPP forced handover. After MS obtains data TCH/H, call drop
counter increments.
Usage
This counter is used to find out the frequency of call drop on data
TCH/H due to eMLPP forced handover.
Measurement
Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on data TCH/H. The measurement point is A, as shown
in Figure 809.
747
FIGURE
EMLPP
Unit

FORCED HANDOVER
Times
C901070071 Bad quality of

UL receiving (On SDCCH)
Definition
Description

radio link failure. After MS obtains SDCCH, call drop occurs. If
the problem is caused by bad uplink receiving quality, the counter
increments.
Usage
due to radio link failure which is caused by bad uplink receiving
quality.
Measurement
Point
748
Bad quality of UL receiving (On SDCCH)
The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on SDCCH. The measurement
DicatiOn

ASSIGNMENT PROCESS
Unit
Times

DL receiving (On SDCCH)
Definition
Bad quality of DL receiving (On SDCCH)
Description

radio link failure. After MS obtains SDCCH, call drop occurs. If the
problem is caused by bad downlink receiving quality, the counter
increments.
Usage
due to radio link failure which is caused by bad downlink receiving
quality.
Measurement
Point
DicatiOn
749

ASSIGNMENT PROCESS
Unit
Times
C901070073 Lower
electrical level of UL (On
SDCCH)
Definition
Description

the problem is caused by low uplink receiving level, the counter
increments.
Usage
due to radio link failure which is caused by low uplink receiving
level.
Measurement
Point
750
Lower electrical level of UL (On SDCCH)
DicatiOn

ASSIGNMENT PROCESS
Unit
Times
C901070074 Lower
electrical level of DL (On
SDCCH)
Definition
Lower electrical level of DL (On SDCCH)
Description

the problem is caused by low downlink receiving level, the counter
increments.
Usage
due to radio link failure which is caused by low downlink receiving
level.
Measurement
Point
DicatiOn
751

ASSIGNMENT PROCESS
Unit
Times
signaling drops due to TA
too far (On SDCCH)
Definition
Description

radio link failure. After MS obtains SDCCH, call drop occurs. If the
problem is caused by TA being too far, the counter increments.
Usage
due to radio link failure which is caused by TA being too far.
Measurement
Point
752
Number of signaling drops due to TA too far (On SDCCH)
DicatiOn

ASSIGNMENT PROCESS
Unit
Times
C901070076 Reasons of the

other radios (On SDCCH)
Definition
Reasons of the other radios (On SDCCH)
Description

the problem is not due to the above five causes (i.e. bad uplink
receiving quality, bad downlink receiving quality, low uplink receiving level, low downlink receiving level, and TA being too far), the
counter increments.
Usage
due to radio link failure which is caused by other radio problems.
Measurement
Point
DicatiOn
753

ASSIGNMENT PROCESS
Unit
Times

UL receiving (On TCH/F)
Definition
Description
This counter counts the number of call drops on TCH/F due to radio link failure. After MS obtains TCH/F, call drop occurs. If the
problem is caused by bad uplink receiving quality, the counter increments.
Usage
quality.
Measurement
Point
754
Bad quality of UL receiving (On TCH/F)
The counter counts when BSC receives the CONNectiOn FAILure INDimessage at Abis interface on TCH/F. The measurement point
catiOn

ASSIGNMENT PROCESS
Unit
Times

DL receiving (On TCH/F)
Definition
Bad quality of DL receiving (On TCH/F)
Description
increments.
Usage
quality.
Measurement
Point
catiOn
755

PROCESS
Unit
Times
C901070079 Lower
TCH/F)
Definition
756
Lower electrical level of UL (On TCH/F)
Description
problem is caused by low uplink receiving level, the counter increments.
Usage
level.
Measurement
Point
The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/F. The measurement
DicatiOn

PROCESS
Unit
Times
C901070080 Lower
TCH/F)
Definition
Description
Lower electrical level of DL (On TCH/F)

problem is caused by low downlink receiving level, the counter increments.
757
Usage
Measurement
Point
level.
catiOn

PROCESS
Unit
Times
too far (On TCH/F)
Definition
758
Number of signaling drops due to TA too far (On TCH/F)
Description
Usage
Measurement
Point
catiOn

PROCESS
Unit
Times

other radios (On TCH/F)
Definition
Reasons of the other radios (On TCH/F)
759
Description
This counter counts the number of call drops on TCH/F due to radio
link failure. After MS obtains TCH/F, call drop occurs. If the problem is not due to the above five causes (i.e. bad uplink receiving
quality, bad downlink receiving quality, low uplink receiving level,
low downlink receiving level, and TA being too far), the counter
increments.
Usage
Measurement
Point
The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/F. The measurement
DicatiOn

PROCESS
Unit
760
Times

UL receiving (On TCH/H)
Definition
Bad quality of UL receiving (On TCH/H)
Description
This counter counts the number of call drops on TCH/H due to

radio link failure. After MS obtains TCH/H, call drop occurs. If
the problem is caused by bad uplink receiving quality, the counter
increments.
Usage
quality.
Measurement
Point
The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/H. The measurement
DicatiOn

PROCESS
Unit
Times
761

DL receiving (On TCH/H)
Definition
Bad quality of DL receiving (On TCH/H)
Description

radio link failure. After MS obtains TCH/H, call drop occurs. If the
increments.
Usage
quality.
Measurement
Point
DicatiOn

PROCESS
Unit
762
Times
C901070085 Lower
TCH/H)
Definition
Lower electrical level of UL (On TCH/H)
Description

the problem is caused by low uplink receiving level, the counter
increments.
Usage
level.
Measurement
Point
DicatiOn

PROCESS
Unit
Times
763
C901070086 Lower
TCH/H)
Definition
Lower electrical level of DL (On TCH/H)
Description

the problem is caused by low downlink receiving level, the counter
increments.
Usage
level.
Measurement
Point
DicatiOn

PROCESS
Unit
764
Times
too far (On TCH/H)
Definition
Number of signaling drops due to TA too far (On TCH/H)
Description

radio link failure. After MS obtains TCH/H, call drop occurs. If the
Usage
Measurement
Point
DicatiOn

PROCESS
Unit
Times
765

other radios (On TCH/H)
Definition
Reasons of the other radios (On TCH/H)
Description
This counter counts the number of call drops on TCH/H due to radio
link failure. After MS obtains TCH/H, call drop occurs. If the problem is not due to the above five causes (i.e. bad uplink receiving
quality, bad downlink receiving quality, low uplink receiving level,
low downlink receiving level, and TA being too far), the counter
increments.
Usage
Measurement
Point
DicatiOn

PROCESS
Unit
766
Times
C901070089 The Count of

Drop Call caused by "IP
Resource Reset"
Statistics object
Description
CELL
On the premise that the 3GPP IPA function is implemented, during the IP resource resetting process (initiated at MSC or at BSC),
BSC releases relevant calls when it receives the IP resource resetting request or the IP resource resetting response from MSC. The
counter increments upon each released call. The measurement
Unit
OF THE
COUNT
OF
DROP CALL CAUSED
BY
"IP RESOURCE RESET"
Times
767
FR_V1 radio link fail
Description
This counter counts the number of full-rate version 1 radio link

failures on TCH/F. When BSC receives the AbisConnectFailureIndication message from BTS, it judges the voice version. If the voice
version is full-rate version 1, then the counter increments.
Usage
This counter is used to find out the number of call drops due to
full-rate version 1 radio link failures on TCH/F.
Measurement
Point
Unit
When BSC receives the AbisConnectFailureIndication message

from BTS, if the voice version used is full-rate voice version 1,
then the counter counts.
Times
Description

Usage
Measurement
Point
Unit

Times
Description

Usage
768
Measurement
Point
Unit

Times
HR_V1 radio link fail
Description
This counter counts the number of half-rate version 1 radio link

version is half-rate version 1, then the counter increments.
Usage
half-rate version 1 radio link failures on TCH/F.
Measurement
Point
Unit

from BTS, if the voice version used is half-rate voice version 1,
Times
HR_V3 radio link fail
Description
This counter counts the number of half-rate version 3 radio link

version is half-rate version 3, then the counter increments.
Usage
half-rate version 3 radio link failures on TCH/F.
Measurement
Point
Unit

from BTS, if the voice version used is half-rate voice version 3,
Times
769
to BIPB Active/Standby
Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is

received and the cause is FORCE_REL_BIPBEXCH.
Unit
Statistics Object
Times
Cell
voice TCH/F drops due
Changeover
Description

Unit
Statistics Object
Times
Cell

TCH/F drops due to BIPB
Active/Standby Changeover
Description

Unit
770
Times
Statistics Object
Cell
Changeover
Description

Unit
Statistics Object
Times
Cell
voice TCH/H drops due
Changeover
Description

Unit
Statistics Object
Times
Cell

TCH/H drops due to BIPB
Description

771

Unit
Statistics Object
Times
Cell
SDCCH drops due to LAPD
Description

received and the cause is CAUSE_LAPDEXCH.
Unit
Statistics Object
Times
Cell
to LAPD Active/Standby
Changeover
Description

Unit
Statistics Object
Times
Cell

TCH/F drops due to LAPD
Description
772


Unit
Statistics Object
Times
Cell
Changeover
Description

Unit
Statistics Object
Times
Cell
Changeover
Description

Unit
Times
773
Statistics Object
Cell

TCH/H drops due to LAPD
Description

Unit
Statistics Object
Times
Cell
Changeover
Description

Unit
Statistics Object
Times
Cell
to handover fail for power
adjustment
Description
774
After the power sharing function is enabled, if power congestion

occurs, the power congestion control algorithm of CS outgoing
handover is executed. If the handover fails and if the current channel is FR, the counter increments.
This counter is supported in version V6.20.611f.
Unit
Statistics Object
Times
Cell
to handover fail for power
adjustment
Description
After the power sharing function is enabled, if power congestion

occurs, the power congestion control algorithm of CS outgoing
handover is executed. If the handover fails and if the current channel is HR, the counter increments.
This counter is supported in version V6.20.611f.
Unit
Statistics Object
Times
Cell
SDCCH drops due to BIPB
Description

Unit
Times
775
Statistics Object
Cell
SDCCH drops due to BTS
failure
Description
This counter counts the number of call drops on SDCCH due to BTS
fault. The counter has two measurement points:
When BSC receives the ConnectionFailure message and the cause
is "O&M intervention", if the service is on SDCCH, the counter increments. The measurement point is A, as shown in Figure 829.
FAULT
DURING
IMMEDIATE ASSIGNMENT
DUE TO
BTS
When BSC receives the O&M status report message from BTS and
the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on SDCCH, the counter increments.
Unit
776
Times
Statistics Object
Cell
to BTS failure
Description
This counter counts the number of call drops on signaling TCH/F

due to BTS fault. The counter has two measurement points:
is "O&M intervention", if the service is on signaling TCH/F, the
Figure 830.
the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on signaling TCH/F, the counter increments.
FAULT
DURING
IMMEDIATE ASSIGNMENT
DUE TO
BTS

Unit
Times
777
Statistics Object
Cell
BTS failure
Description
This counter counts the number of call drops on voice TCH/F due
to BTS fault. The counter has two measurement points:
is "O&M intervention", if the service is on voice TCH/F, the counter
DURING
ASSIGNMENT
DUE TO
BTS FAULT
the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on voice
TCH/F, the counter increments.
778
Unit
Statistics Object
Times
Cell
BTS failure
Description
This counter counts the number of call drops on data TCH/F due
is "O&M intervention", if the service is on data TCH/F, the counter
the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on data
TCH/F, the counter increments.
DURING
ASSIGNMENT
DUE TO
BTS FAULT
779

Unit
Statistics Object
Times
Cell
to BTS failure
Description
This counter counts the number of call drops on signaling TCH/H

due to BTS fault. The counter has two measurement points:
is "O&M intervention", if the service is on signaling TCH/H, the
Figure 833.
the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on signaling TCH/H, the counter increments.
780
DURING
ASSIGNMENT
DUE TO
BTS FAULT

Unit
Statistics Object
Times
Cell
BTS failure
Description
This counter counts the number of call drops on voice TCH/H due
is "O&M intervention", if the service is on voice TCH/H, the counter
the cause is BTS being blocked due to fault, the service being af-
781
fected should be released. If the service being affected is on voice

TCH/H, the counter increments.
DURING
ASSIGNMENT
DUE TO
BTS FAULT

Unit
Statistics Object
Times
Cell
BTS failure
Description
This counter counts the number of call drops on data TCH/H due
is "O&M intervention", if the service is on data TCH/H, the counter
782
the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on data
TCH/H, the counter increments.
DURING
ASSIGNMENT
DUE TO
BTS FAULT

Unit
Statistics Object
Times
Cell
C901070118 Call Drop by

Releasing Local Switch
Description
This counter counts the number of call drops due to failure in releasing local switch. In normal cases, the call should return to the
normal call status after the local switch is released. However, if
fault occurs during the release, such as failure in requesting TC
resource or connection failure when TC is external, the no-voice
problem will occur. In such cases, the service module will release
783
the call and consider it as a call drop due to failure in releasing

local switch.
This counter is supported in version V6.20.614c.
Unit
Statistics Object
784
Times
Cell
Chapter
14
Radio Resource Availabi

lity Measurement
Table of Contents
Overview........................................................................ 785
C901080003 Maximum Number of Busy SDCCHs ................. 785
C901080004 Average processor load.................................. 787
C901080006 SDCCH congestion time ................................. 787
C901080008 Number of unavailable defined SDCCH............. 788
C901080011 Maximum number of busy radio channel .......... 789
C901080012 Average number of busy radio channel ............ 790
C901080014 Average number of busy TCH/H ...................... 791
C901080016 TCH/H busy time(SpeechVer1)........................ 792
C901080017 TCH/H busy time(SpeechVer3)........................ 793
C901080018 TCH/H congestion time .................................. 794
C901080022 Average number of busy TCH/F....................... 796
C901080024 TCH/F busy time(SpeechVer1) ........................ 796
C901080027 TCH/F congestion time................................... 800
C901080030 Number of TRXs ........................................... 801
C901080032 Reserved TCH/F busy time ............................. 802
C901080033 Maximum number of busy TCH/F .................... 803
C901080034 Cell down time ............................................. 804
Overview
Radio resource available measurement counters count the number,
mean number and the maximum busy number of available SDCCH,
TCH/H and TCH/F, as well as total busy and congestion time of
these channels in the cell.
C901080003 Maximum
Number of Busy SDCCHs
Definition
Maximum Number of Busy SDCCHs
785
Description
This counter counts the maximum number of busy SDCCHs in the

cell within measurement period; its value represents SDDCH instantaneous occupation status and the busiest extent.
System records SDCCH occupation number in cells. The occupation number increments after SDCCH has been occupied successfully; the occupation number decrements before SDCCH has been
released. The counter value updates as occupation number if BSC
judges that the counter value is smaller than the occupation number after SDCCH has been occupied successfully and before SDCCH has been released, as well as when measurement data are
reported periodically.
Update occupation number before SDCCH has been released is
because SDCCH status in the previous measurement period has
been taken into account.
Usage
Measurement
Point
This counter is used to find out the busy extent of SDCCH in cells,
its value can be used as the reference for whether to increase
SDCCH.
The counter counts in the following three cases:
The counter updates if the maximum busy number exceeds the

recorded value after SDCCH has been occupied successfully;

recorded value before SDCCH has been released;

recorded value when measurement data are reported periodically. The measurement point is A, as shown in Figure 836.
Unit
786
Times
Chapter 14 Radio Resource Availability Measurement
C901080004 Average
processor load
Definition
Average processor load.
Description
This counter counts the mean number of busy SDCCHs in the cell
within measurement period. The occupation number in measurement data reported periodically in the system is the mean number
of busy SDCCH.
Usage
SDCCH.
Measurement
Point
The counter counts when measurement data are reported periodically. The measurement point is A, as shown in Figure 837.
Unit
Times
C901080006 SDCCH
congestion time
Definition
Description
SDCCH congestion time

This counter counts the total time of SDCCH congestion.
BSC sets congestion mark when SDCCH request fails, and the start
of congestion time is recorded.
BSC clear congestion mark when SDCCH request succeeds. If
congestion mark is set when requiring SDCCH, then this period
787
of congestion time is to use the present time minus the previous

recorded congestion time.
If congestion mark is set before SDCCH has been released or when
measurement values are reported periodically, the congestion time
is calculated. The sum of each congestion time is the total time of
SDCCH congestion.
Usage
Measurement
Point
SDCCH.
If congestion mark is set before SDCCH has been occupied, the

counter counts congestion time and accumulates.
If congestion mark is set before SDCCH has been released, the

If congestion mark is set when measurement values are reported periodically, the counter counts congestion time and
accumulates. The measurement point is A, as shown in Figure
838.
Unit
Second
unavailable defined SDCCH
Definition
Description
788
Number of unavailable defined SDCCH

iBSC supports dynamic transform between SDCCH and TCH. This
counter counts the number of unavailable static SDCCH configured
by present cell through OMCR.
Usage
This counter is used to find out the unavailability of SDCCH in the

present cell for eliminating cell failures.
Measurement
Point
The counter value is inquired from database when periodical measurement data are reported. The measurement point is A, as
Unit
Related Features
Times
C901080011 Maximum
number of busy radio
channel
Definition
Maximum number of busy radio channel
Description
This counter counts the maximum number of busy radio channel

in the cell within measurement period; its value represents radio
channel instantaneous occupation status and the busiest extent.
Usage
This counter is used to find out the busy extent of radio channel in
cells; its value can be used as the reference for whether to increase
TRXs.
Measurement
Point
789
Unit
Related Features
Times
C901080012 Average
number of busy radio
channel
Definition
790
Average number of busy radio channel
Description
This counter counts the mean number of busy radio channel in

the cell within measurement period. The occupation number in
measurement data reported periodically in the system is the mean
number of busy radio channel.
Usage
This counter is used to find out the busy extent of radio channel in
cells; its value can be used as the reference for whether to increase
TRXs.
Measurement
Point
Unit
Related Features
Times
C901080014 Average
number of busy TCH/H
Definition
Average number of busy TCH/H
Description
This counter counts the mean number of busy TCH/Hs in the cell
of busy TCH/Hs.
Usage
This counter is used to find out the busy extent of TCH/Hs in cells;
TCH/Hs.
Measurement
Point
Occupation number updates after TCH/H has been occupied and

released successfully, the counter value is reported when measurement data are reported periodically. The measurement point
791
Unit
Related Features
Times

time(SpeechVer1)
Definition
Description
This counter counts the total TCH/H busy time (SpeechVer1) in

cells; its value represents traffic on TCH/H (SpeechVer1).
Usage
This counter is used to find out the busy extent and mean occupation time of TCH/H in cells; its value can be used as the reference
for whether to increase TCH/Hs.
Measurement
Point
792
TCH/H busy time (SpeechVer1).
The counter counts time and accumulates when TCH/H is obtained successfully
The counter counts time and accumulates when TCH/H is released
The counter counts time and accumulates when measurement

data are reported periodically. The measurement point is A, as
The measurement formula is:

(Present time previous measurement time) Number of MS
that are occupying channels
The reported measurement value is the accumulation of each
measurement value. After each accumulation, the previous
measurement time is updated as the present time. The number of MS that are occupying channels increments when TCH/H
is obtained successfully after accumulation. The number of MS
that are occupying channels decrements when TCH/H is released after accumulation.
Unit
Related Features
Second

time(SpeechVer3)
Definition
TCH/H busy time(SpeechVer3).
Description
This counter counts the total TCH/H busy time (SpeechVer3) in

cells; its value represents traffic on TCH/H (SpeechVer3).
Usage
This counter is used to find out the busy extent and mean occupation time of TCH/H in cells; its value can be used as the reference
for whether to increase TCH/Hs.
Measurement
Point
The counter counts time and accumulates when TCH/H is obtained successfully
793
The counter counts time and accumulates when TCH/H is released


measurement time is updated as the present time. The number of MS that are occupying channels increments when TCH/H
is obtained successfully after accumulation. The number of MS
that are occupying channels decrements when TCH/H is released after accumulation.
Unit
Related Features
Second
C901080018 TCH/H
congestion time
Definition
Description
794
TCH/H congestion time

This counter counts the total TCH/H congestion time.
BSC sets congestion mark when TCH/H request fails, and the start
BSC clear congestion mark when TCH/H request succeeds. If congestion mark is set when requiring TCH/H, then this period of congestion time is to use the present time minus the previous recorded
congestion time.
If congestion mark is set before TCH/H has been released or when
TCH/H congestion.
Usage
Measurement
Point
This counter is used to find out the busy extent of TCH/H in cells, its
value can be used as the reference for whether to increase TCH/H.
If congestion mark is set before TCH/H has been occupied, the

If congestion mark is set before TCH/H has been released, the

845.
Unit
Related Features
Second
795
C901080022 Average
Definition
Average number of busy TCH/F
Description
This counter counts the mean number of busy TCH/Fs in the cell
of busy TCH/Fs.
Usage
This counter is used to find out the busy extent of TCH/Fs in cells;
TCH/Fs.
Measurement
Point
Occupation number updates after TCH/F has been occupied and

released successfully, the counter value is reported when measurement data are reported periodically. The measurement point
Unit
Related Features
Times

time(SpeechVer1)
Definition
Description
796
TCH/F busy time (SpeechVer1)

This counter counts the total TCH/F busy time (SpeechVer1) in
cells; its value represents traffic on TCH/F (SpeechVer1).
Usage
Measurement
Point
This counter is used to find out the busy extent and mean occupation time of TCH/F in cells; its value can be used as the reference for whether to increase TCH/Fs and the proportion of using
SpeechVer1.
The counter counts time and accumulates when TCH/F is obtained successfully
The counter counts time and accumulates when TCH/F is released


measurement time is updated as the present time. The number of MS that are occupying channels increments when TCH/F
is obtained successfully after accumulation. The number of
MS that are occupying channels decrements when TCH/F is released after accumulation.
Unit
Related Features
Second
797

time(SpeechVer2)
Definition
TCH/F busy time (SpeechVer2)
Description

Usage
SpeechVer2.
Measurement
Point


Unit
798
Second
Related Features


time(SpeechVer3)
Definition
TCH/F busy time(SpeechVer3)
Description

Usage
SpeechVer3.
Measurement
Point


799
Unit
Related Features
Second
C901080027 TCH/F
congestion time
Definition
Description
TCH/F congestion time

This counter counts the total time of TCH/F congestion.
BSC sets congestion mark when TCH/F request fails, and the start
BSC clear congestion mark when TCH/F request succeeds. If congestion mark is set when requiring TCH/F, then this period of congestion time is to use the present time minus the previous recorded
congestion time.
If congestion mark is set before TCH/F has been released or when
TCH/F congestion.
Usage
Measurement
Point
800
This counter is used to find out the busy extent of TCH/F in cells, its
value can be used as the reference for whether to increase TCH/F.
If congestion mark is set before TCH/F has been occupied, the

If congestion mark is set before TCH/F has been released, the

850.
Unit
Related Features
Second
TRXs
Definition
Number of TRX s
Description
This counter counts the total number of TRXs in all status configured in the cell.
Usage
This counter is used to find out the configured TRX number and
resource utilizing status in the present cell.
Measurement
Point
801
Unit
Times
C901080032 Reserved
TCH/F busy time
Definition
Description
Reserved TCH is the channel that can only be occupied by subscribers with high priority. This counter counts the total busy time
for reserved TCH/F; its value represents traffic of reserved TCH/F.
Usage
This counter is used to find out the utilizing status of reserved

TCH/F to facilitate the configuration adjustment of reserved TCH/F.
Measurement
Point
802
Reserved TCH/F busy time
The counter counts when reserved TCH/F is obtained successfully
The counter counts when reserved TCH/F is released;
The counter counts when measurement values are reported

periodically. The measurement point is A, as shown in Figure
852.

Unit
Second
C901080033 Maximum
Description
This counter counts the maximum number of TCHs being occupied

during the measurement period.
The system records the number of TCHs being occupied in the cell.
After a TCH is occupied successfully, the counter increments; after
a TCH is released, the counter decrements. After TCH is successfully occupied or before TCH is released or when the measurement
data is reported periodically, if BSC finds that the counter's value
is smaller than the number of TCHs actually being occupied, then
the counter's value is updated to be the actual number of TCHs
being occupied.
Considering the TCH usage in the last measurement period, the
number of TCH being occupied is updated before TCH is released.
803
Measurement
Point
The counter counts at the following time points.

1. After TCH is occupied successfully, if the maximum number of
busy TCHs exceeds the recorded value, the counter counts.
2. Before TCH is released, if the maximum number of busy TCHs
exceeds the recorded value, the counter counts.
3. When the measurement data is reported periodically, if the
maximum number of busy TCHs exceeds the recorded value,
the counter counts.
Unit
Times
C901080034 Cell down time

Description
This counter counts how long the cell is interrupted on BCCH.

When the confirmation message (tGetCellDownTimeAck.wResult)
of cell's interruption duration obtained from database is true, the
counter records the measurement value.
Usage
This counter is used to find out the duration of cell interruption on

BCCH.
Measurement
Point
Unit
804
When the confirmation message (tGetCellDownTimeAck.wResult)

of cell's interruption duration obtained from database is true, the
counter counts.
Second
Chapter
15
General Handover
Measurement
Table of Contents
Overview........................................................................ 812
handover attempts .......................................................... 813
attempts ........................................................................ 813
request failures due to unclear factors ................................ 814
request failures due to unavailable ground resource ............. 815
request failures due to unavailable radio resource ................ 816
request failures due to other factors................................... 817
attempts due to forced release .......................................... 819
attempts due to queue ..................................................... 820
attempts due to forced handover ....................................... 821
C901090020 BSC-controlled incoming handover time due to
queue ............................................................................ 822
C901090021 Queue number of BSC-controlled incoming handover............................................................................. 824
C901090022 BSC-controlled incoming handover success time
due to queue .................................................................. 826
success due to queue....................................................... 827
attempts ........................................................................ 828
C901090025 Number of incoming handover failure due to circuit block ....................................................................... 828
C901090026 Number of incoming handover failure due to circuit group mismatch ........................................................ 829
C901090027 Number of incoming handover failure due to unavailable radio resource.................................................... 830
other factors ................................................................... 831
attempts due to forced release .......................................... 832
attempts due to queue ..................................................... 833
805

attempts due to forced handover ....................................... 834
C901090037 MSC-controlled incoming handover time due to
queue ............................................................................ 835
C901090038 Queue number of MSC-controlled incoming handover............................................................................. 837
C901090039 MSC-controlled incoming handover success time
due to queue .................................................................. 839
success due to queue....................................................... 840
the same layer and frequency ........................................... 841
C901090042 Number of incoming handover success from the
same layer and frequency................................................. 842
C901090043 Number of outgoing handover attempts to the
C901090044 Number of outgoing handover success to the
undefined layer to the same frequency ............................... 845
C901090046 Number of incoming handover success from undefined layer to the same frequency .................................. 846
undefined layer to the same frequency ............................... 847
C901090048 Number of outgoing handover success from undefined layer to the same frequency .................................. 848
undefined layer (GSM900) to current layer (GSM1800) ......... 849
current layer (GSM900) to undefined layer (GSM1800) ......... 850
C901090053 Number of outgoing handover from current layer
(GSM900) to undefined layer (GSM1800)............................ 851
C901090054 Number of outgoing handover success from current layer (GSM900) to undefined layer (GSM1800) ............. 852
C901090059 Number of outgoing handover from undefined
layer (GSM1800) to current layer (GSM900) ....................... 855
C901090060 Number of outgoing handover success from undefined layer (GSM1800) to current layer (GSM900) ............ 856
upper layer to the same frequency..................................... 857
C901090062 Number of incoming handover success from upper layer to the same frequency ........................................ 858
C901090063 Number of outgoing handover attempts from the
same frequency to upper layer .......................................... 859
C901090064 Number of outgoing handover success from the
same frequency to upper layer .......................................... 860
lower layer to the same frequency ..................................... 861
lower layer to the same frequency ..................................... 862
C901090067 Number of outgoing handover attempts from the
same frequency to lower layer........................................... 863
C901090068 Number of outgoing handover success from the
same frequency to lower layer........................................... 864
the same layer GSM900 to GSM1800 ................................. 865
806
Chapter 15 General Handover Measurement
C901090072 Number of outgoing handover attempts to the

C901090073 Number of outgoing handover to the same layer
GSM900 to GSM1800 ....................................................... 867
C901090074 Number of outgoing handover success to the
GSM900 to GSM1800 to the upper layer ............................. 869
C901090079 Number of outgoing handover from GSM900 to
GSM1800 to the upper layer ............................................. 870
GSM1800 in the lower layer .............................................. 874
GSM900 to GSM1800 in the lower layer .............................. 875
GSM900 from the same layer ............................................ 878
GSM900 to the upper layer ............................................... 882
GSM1800 to GSM900 to the lower layer.............................. 885
GSM900 to the lower layer................................................ 886
GSM1800 to GSM900 to the lower layer.............................. 887
C901090105 Number of intra-cell handover attempts ........... 888
C901090108 Number of intra-cell inner-circle-to-outer-circle
C901090109 Number of intra-cell inner-circle-to-outer-circle
C901090110 Number of intra-cell outer-circle-to-inner-circle
C901090111 Number of intra-cell outer-circle-to-inner-circle
C901090112 Number of intra-cell inner-circle-to-inner-circle
C901090113 Number of intra-cell inner-circle-to-inner-circle
807
C901090114 Number of intra-cell outer-circle-to-outer-circle

C901090115 Number of intra-cell outer-circle-to-outer-circle
3G................................................................................. 895
C901090117 Number of handover from 2G to 3G................. 895
3G................................................................................. 896
2G................................................................................. 897
C901090120 Number of handover from 3G to 2G................. 898
2G................................................................................. 899
C901090122 Number of intra-cell handover attempts from
TCH/F ............................................................................ 899
C901090123 Number of intra-cell TCH/F-to-TCH/F handover............................................................................. 900
C901090124 Number of intra-cell TCH/F-to-TCH/F handover
success .......................................................................... 901
C901090125 Number of intra-cell TCH/F-to-TCH/H handover............................................................................. 902
C901090126 Number of intra-cell TCH/F-to-TCH/H handover
success .......................................................................... 903
C901090127 Number of intra-cell handover attempts from
TCH/H............................................................................ 903
C901090128 Number of intra-cell TCH/H-to-TCH/F handover............................................................................. 904
C901090129 Number of intra-cell TCH/H-to-TCH/F handover
success .......................................................................... 905
C901090130 Number of intra-cell TCH/H-to-TCH/H handover............................................................................. 906
C901090131 Number of intra-cell TCH/H-to-TCH/H handover
success .......................................................................... 907
C901090132 Number of inter-cell handover attempts from
TCH/F ............................................................................ 908
C901090133 Number of inter-cell TCH/F-to-TCH/F handover............................................................................. 909
C901090134 Number of inter-cell TCH/F-to-TCH/F handover
success .......................................................................... 909
C901090135 Number of inter-cell TCH/F-to-TCH/H handover............................................................................. 910
C901090136 Number of inter-cell TCH/F-to-TCH/H handover
success .......................................................................... 911
C901090137 Number of inter-cell handover attempts from
TCH/H............................................................................ 912
C901090138 Number of inter-cell TCH/H-to-TCH/F handover............................................................................. 913
C901090139 Number of inter-cell TCH/H-to-TCH/F handover
success .......................................................................... 914
C901090140 Number of inter-cell TCH/H-to-TCH/H handover............................................................................. 915
C901090141 Number of inter-cell TCH/H-to-TCH/H handover
success .......................................................................... 916
C901090142 Total dual-band outgoing handover attempts ........................................................................... 917
C901090145 Number of dual band incoming handover attempts ........................................................................... 918
C901090148 Number of intra-cell invalid handovers ............. 919
808

handover attempts due to forced release (emergency service) .............................................................................. 920
handover (forced release) (emergency service) ................... 921
handover attempts due to forced handover (emergency service) ............................................................................... 922
handover (forced handover) (emergency service) ................ 923
handover attempts due to queue (emergency service).......... 924
handover (queue) (emergency service) .............................. 925
attempts due to forced release (emergency service)............. 926
(forced release) (emergency service) ................................. 927
C901090157 Number of MSC-controlled inter-cell incoming
handover attempts due to forced handover (emergency service) .............................................................................. 928
(forced release) (emergency service) ................................. 929
attempts due to queue (emergency service)........................ 930
(queue) (emergency service) ............................................ 931
(BSC-controlled inter-cell handover due to forced handover) ........................................................................... 932
lower PRI user (BSC-controlled inter-cell handover due to
forced handover) ............................................................. 933
C901090163 Number of recv failure from lower PRI user request resource for forced handover (BSC-controlled inter-cell
handover due to forced handover) ..................................... 934
(BSC-controlled inter-cell handover due to forced handover) ........................................................................... 936
C901090165 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced handover) ........................................................................... 937
C901090166 Number of forced release target not found (BSCcontrolled inter-cell handover due to forced release) ............ 938
C901090167 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced release) ............................................................................ 939
C901090168 Number of HO Target not found (MSC-controlled
incoming handover due to forced handover)........................ 940
lower PRI user (MSC-controlled incoming handover due to
forced handover) ............................................................. 941
C901090170 Number of failure to lower PRI user request resource for forced handover (MSC-controlled incoming handover due to forced handover) .......................................... 942
(MSC-controlled incoming handover due to forced handover) ........................................................................... 942
809
C901090172 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover) ........................................................................... 943
(MSC-controlled incoming handover due to forced release) ............................................................................ 943
C901090174 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced release) ............................................................................ 944
C901090175 Number of get before grab released channel (assignment forced handover) ............................................... 945
C901090176 Number of get before grab released channel (assignment forced release) .................................................. 945
C901090177 Number of handover attempts due to eMLPP
forced handover .............................................................. 946
C901090178 Number of handover due to eMLPP forced handover............................................................................. 946
C901090179 Number of handover success due to eMLPP
forced handover .............................................................. 947
handover attempts between PLMN ..................................... 947
handover between PLMN .................................................. 947
handover success between PLMN ....................................... 948
attempts between PLMN ................................................... 948
request fail between PLMN due to unknown reason .............. 948
request fail between PLMN due to unavailable ground resource
.................................................................................... 949
request fail between PLMN due to unavailable radio resource ........................................................................... 950
request fail between PLMN due to other reasons .................. 950
between PLMN ................................................................ 951
success between PLMN ..................................................... 952
handover attempt between PLMN....................................... 953
handover between PLMN .................................................. 953
handover force-release attempt between PLMN.................... 953
handover between PLMN due to force release ...................... 954
handover queue attempt between PLMN ............................. 954
handover between PLMN due to queue ............................... 954
handover force-handover attempt between PLMN................. 955
handover between PLMN due to force handover ................... 955
handover success between PLMN ....................................... 955
810

attempt between PLMN ................................................... 956
PLMN due to circuit block.................................................. 957
PLMN due to circuit unmatch ............................................. 958
PLMN due to unavailable radio resource .............................. 958
PLMN due to other reason................................................. 959
between PLMN ................................................................ 959
force-release attempt between PLMN ................................. 959
between PLMN due to force release .................................... 960
queue attempt between PLMN ........................................... 960
between PLMN due to queue ............................................. 961
force-handover attempt between PLMN .............................. 962
between PLMN due to force handover ................................. 962
success between PLMN .................................................... 963
C901090212 Number of handover due to Fragment reorganization ............................................................................ 963
C901090213 Number of handover success due to Fragment
reorganization................................................................. 963
C901090214 Number of handover attempt from AMR FR to
AMR HR due to high load .................................................. 964
C901090215 Number of handover from AMR FR to AMR HR
due to high load .............................................................. 965
C901090216 Number of handover success from AMR FR to
AMR HR due to high load .................................................. 966
C901090217 Number of handover attempt from FR to HR due
to high load .................................................................... 966
C901090218 Number of handover from FR to HR due to high
load............................................................................... 967
C901090219 Number of handover success from FR to HR due
to high load .................................................................... 968
C901090220 Number of handover attempt from AMR HR to
AMR FR due to bad quality ................................................ 968
C901090221 Number of handover from AMR HR to AMR FR
due to bad quality ........................................................... 969
C901090222 Number of handover success from AMR HR to
AMR FR due to bad quality ................................................ 970
C901090223 Number of handover attempt from HR to FR due
to bad quality ................................................................. 970
C901090224 Number of handover from HR to FR due to bad
quality ........................................................................... 971
C901090225 Number of handover success from HR to FR due
to bad quality ................................................................. 972
handover attempts, from GSM900 to GSM900 ..................... 972
handover, from GSM900 to GSM900................................... 973
handover success, from GSM900 to GSM900 ....................... 974
811

handover attempts, from GSM1800 to GSM1800.................. 975
handover, from GSM1800 to GSM1800 ............................... 976
handover success, from GSM1800 to GSM1800 ................... 977
handover attempts, from GSM900 to GSM1800 ................... 978
handover, from GSM900 to GSM1800 ................................. 979
handover success, from GSM900 to GSM1800 ..................... 980
handover attempts, from GSM900 to GSM900 ..................... 984
handover, from GSM900 to GSM900................................... 985
handover success, from GSM900 to GSM900 ....................... 986
handover attempts, from GSM1800 to GSM1800.................. 987
handover, from GSM1800 to GSM1800 ............................... 988
handover success, from GSM1800 to GSM1800 ................... 989
Overview
General handover counter is used to find out MS handover successes, failures, and frequency of abnormal events during handover. After configured with inter-system handover or concentric
circle, general handover counter is also used to find out inter-cell
traffic sharing to improve the wireless planning.
812
outgoing handover attempts
Definition
Number of BSC-controlled inter-cell outgoing handover attempts
Description
This counter counts the Number of BSC-controlled inter-cell outgoing handover attempts originated from the source cell by MS.
Usage

outgoing handover. It is one of the parameters to measure the
wireless environment.
Measurement
Point
BSC starts the handover decision after it receives the measurement report from MS. If inter-cell handover is necessary and the
current attempt cells are intra-BSC, the counter increments. The
FIGURE 853 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Unit
Related Features
Times
handover attempts
Definition
Description
Number of MSC-controlled outgoing handover attempts

This counter counts the number of MSC-controlled inter-BSC outgoing handover attempts originated from the source cell by MS.
813
Usage

inter-BSC outgoing handover attempts. It is one of the parameters
to measure the wireless environment.
Measurement
Point
current attempt cells are governed by different BSCs, the source
BSC will send MSC the handover request A_HO_RQD to trigger inter-BSC handover, and the counter increments. The measurement
FIGURE 854 MSC-CONTROLLED OUTGOING HANDOVER ATTEMPTS
Unit
Related Features
Times
handover request failures
due to unclear factors
814
Definition
Number of MSC-controlled outgoing handover request failures due

to unclear factors
Description
This counter counts the number of MSC-controlled inter-BSC outgoing handover request failures due to unclear factors originated
from the source cell by MS.
Usage

outgoing handover request failures due to unclear reasons, and to
find out the MSC-originated handover status.
Measurement
Point
BSC will send MSC the handover request A_HO_RQD to trigger inter-BSC handover. If BSC fails to receive any feedback from MSC
before the protection timer expires, the counter increments. The

FIGURE 855 MSC-CONTROLLED OUTGOING HANDOVER REQUEST FAILURES
DUE TO UNCLEAR FACTORS
Unit
Related Features
Times
due to unavailable ground
resource
Definition

to unavailable ground resource
Description
This counter counts the number of MSC-controlled inter-BSC

outgoing handover request failures due to unavailable ground
resource originated from the source cell by MS.
Usage

outgoing handover request failures due to unavailable ground resource, and to find out the MSC-originated handover status.
Measurement
Point
BSC will send MSC the handover request A_HO_RQD to trigger
inter-BSC handover. If the source BSC receives the feedback from
MSC that the handover request is rejected due to unavailable
ground resource, the counter increments. The measurement
815
FIGURE 856 MSC-CONTROLLED HANDOVER REQUEST FAILURES
Unit
Related Features
Times
due to unavailable radio
resource
816
Definition
Number of MSC-controlled outgoing request failures due to unavailable radio resource
Description
This counter counts the number of MSC-controlled inter-BSC outgoing handover request failures due to unavailable radio resource
originated from the source cell by MS.
Usage
This counter is used to find out the frequency of MS-originated

MSC-controlled outgoing handover request failures due to unavailable radio resource, and to find out the MSC-originated handover
status.
Measurement
Point
BSC will send MSC the handover request A_HO_RQD to trigger inter-BSC handover. If the source BSC receives the feedback from
MSC that the handover request is rejected due to unavailable radio resource, the counter increments. The measurement point is
Unit
Related Features
Times
Definition

to other factors
Description
This counter counts the number of MSC-controlled inter-BSC outgoing handover request failures due to other factors excluding
unavailable ground resource and unavailable radio resource originated from the source cell by MS.
Usage

MSC-controlled outgoing handover request failures due to other
factors, and to find out the MSC-originated handover status.
Measurement
Point
BSC will send MSC the handover request A_HO_RQD to trigger inter-BSC handover. If the source BSC receives the feedback from
MSC that the handover request is rejected due to other factors,
Figure 858.
817
Unit
Related Features
Times
incoming handover attempts
Definition
Number of BSC-controlled inter-cell incoming handover attempts
Description
This counter counts the Number of BSC-controlled inter-cell incoming handover attempts from MS to target cell.
Usage

incoming handover attempts originated by MS. It is one of the
parameters to measure the wireless environment.
Measurement
Point
When intra-BSC target cell receives the channel request from the
source cell, if the request is due to inter-cell handover, the counter
ATTEMPTS
Unit
Related Features
818
Times
forced release
Definition
Number of BSC-controlled incoming handover attempts due to

forced release
Description
This counter counts the number of forced release attempts originated by target cell due to unavailable radio resource during the
process of MS -originated BSC-controlled inter-cell incoming handover. When target instance fails to allocate the channel, forced
release attempts could be originated referring to the MS priority
and MSC & BSC settings.
Usage

BSC-controlled inter-cell incoming handover attempts due to
forced release, which reflects the handover status.
Measurement
Point
When intra-BSC target cell receives the wireless channel application request, if the application cause is BSC-controlled inter-cell
incoming handover and wireless channel is unavailable to target
cell, forced release attempt decision starts. If forced release attempt is feasible, the counter increments before the target cell
sends forced release message to the instance that is to be released. The measurement point is A, as shown in Figure 860.
FIGURE 860 FORCED RELEASE ATTEMPTS
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
819
queue
Definition

queue
Description
This counter counts the number of queuing attempts originated by

target cell due to unavailable radio resource during the process of
MS-originated BSC-controlled inter-cell incoming handover.
Usage

queue, which reflects the handover status.
Measurement
Point
When intra-BSC target cell receives the wireless channel application request, if the application cause is BSC-controlled inter-cell
incoming handover and wireless channel is unavailable to target
cell, queuing attempt decision starts. If queuing attempt is feasible
and the target cell has the target instance waiting in the queuing,
Figure 861.
FIGURE 861 QUEUING ATTEMPTS
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
820
forced handover
Definition

forced handover
Description
This counter counts the number of forced-handover attempts originated by target cell due to unavailable radio resource during the
process of MS-originated BSC-controlled inter-cell incoming handover.
Usage

forced handover, which reflects the handover status.
Measurement
Point
When intra-BSC target cell receives the wireless channel application request, if the application cause is BSC-controlled intercell incoming handover and wireless channel is unavailable to target cell, forced-handover attempt decision starts. If forced-handover attempt is feasible, the counter increments before the target
cell sends forced-handover message to the instance that is to be
forced. The measurement point is A, as shown inFigure 862.
FIGURE 862 FORCED-HANDOVER ATTEMPTS
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
821
C901090020 BSC-controlled
incoming handover time due
to queue
Definition
BSC-controlled incoming handover time due to queue
Description
This counter counts the total time of call queuing that participate in
BSC-controlled intra-cell incoming handover due to queue. Queuing time refers to a period of an instance from entering to quitting
the queuing.
Usage
This counter is used to find out the total time of BSC-controlled

intra-cell incoming handover due to queue, which helps to understand the traffic status and the situation of the queuing for resource.
Measurement
Point
Under the condition that database acquires resource via dynamic channel conversion or MS releases resource and queuing instance receives usable message, if the application cause
is BSC-controlled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 863.
FIGURE 863 EXECUTION IN QUEUING
822
If the instance queuing timer expires, and the application cause

FIGURE 864 INCOMING HANDOVER QUEUING EXPIRES
During the process of instance queuing, when the instance is

released due to some causes, if the application cause is BSCcontrolled incoming handover, the queuing time accumulates.
FIGURE 865 INSTANCE RELEASE DURING QUEUING
Unit
Related Features
Second
823
C901090021 Queue number

of BSC-controlled incoming
handover
Definition
Queue number of BSC-controlled incoming handover
Description
This counter counts the total queue number of calls that participate
in BSC-controlled intra-cell incoming handover.
Usage
This counter is used to find out the total queue number of calls that
participate in BSC-controlled intra-cell incoming handover, which
helps to understand the traffic status.
Measurement
Point
Under the condition that database acquires resource via dynamic channel conversion or MS releases resource and queuing instance receives usable message, if the application cause
is BSC-controlled incoming handover, the counter increments.
824

is BSC-controlled incoming handover, the counter increments.

released due to certain causes, if the application cause is BSCcontrolled incoming handover, the counter increments. The
Unit
Related Features
Times
825
time due to queue
Definition
BSC-controlled incoming handover success time due to queue
Description
This counter counts the total time of calls that participate in successful BSC-controlled intra-cell incoming handover due to queue
and acquiring resource.
Usage
This counter is used to find out the total queuing time of calls that
participate in successful BSC-controlled intra-cell incoming handover due to queue and acquiring resource, and to find out the
valid queuing time.
Measurement
Point
Under the condition that database acquires resource via dynamic

channel conversion or MS releases resource, when queuing instance receives resource usable message, if the application cause
Unit
Related Features
826
Times
handover success due to
queue
Definition
Number of BSC-controlled incoming handover success due to

queue
Description
This counter counts the total number of calls that participate in

BSC-controlled intra-cell incoming handover due to queue and successfully acquiring resource.
Usage
This counter is used to find out the total number of calls that participate in BSC-controlled intra-cell incoming handover due to queue
and successfully acquiring resource, and to find out the success
ratio of queuing.
Measurement
Point

channel conversion or MS releases resource and queuing instance
receives resource usable message, if the application cause is BSCcontrolled incoming handover, the counter increments. The measurement point is A, as shown in Figure 870.
Unit
Related Features
Times
827
handover attempts
Definition
Number of MSC-controlled incoming handover attempts
Description
This counter counts the number of MSC-originated inter-BSC incoming handover attempts.
Usage
This counter is used to find out the frequency of MSC-originated

inter-BSC incoming handover attempts. It is one of the parameters to measure the wireless environment.
Measurement
Point
When the target cell receives the channel application, if the application cause is external incoming handover, the counter increments. The measurement point is A, as shown in Figure 871.
FIGURE 871 MSC-CONTROLLED INCOMING HANDOVER ATTEMPTS
Unit
Related Features
Times
incoming handover failure
due to circuit block
Definition
Description
828
Number of incoming handover failure due to circuit block

This counter counts the number of unsuccessful MSC-originated
inter-BSC incoming handover due to ground circuit block.
Usage
This counter is used to find out the frequency of unsuccessful

MSC-originated inter-BSC incoming handover due to ground circuit block, and is used to observe the external handover flow.
Measurement
Point
When the target cell receives the handover request from MSC,
it checks the ground circuit. If the requested ground circuit is
blocked, the counter increments. The measurement point is A, as
FIGURE 872 UNSUCCESSFUL MSC-CONTROLLED EXTERNAL INCOMING
HANDOVER
Unit
Related Features
Times
due to circuit group mismatch
Definition
Number of incoming handover failure due to circuit group mismatch
Description
This counter counts the number of unsuccessful MSC-originated inter-BSC incoming handover due to ground circuit group mismatch.
Usage
This counter is used to find out the frequency of unsuccessful

MSC-originated inter-BSC incoming handover due to ground circuit group mismatch, and is used to observe the external handover
flow.
Measurement
Point
When the target cell receives the handover request from MSC, it
checks the ground circuit. If the requested ground circuit does not
match, the counter increments. The measurement point is A, as
829

HANDOVER
Unit
Related Features
Times
resource
830
Definition
Number of incoming handover failure requests due to unavailable

radio resource
Description

inter-BSC incoming handover due to unavailable radio resource.
Usage
This counter is used to find out the frequency of unsuccessful MSCoriginated inter-BSC incoming handover due to unavailable radio
resource, and is used to observe the external handover flow.
Measurement
Point
allocates the wireless channels and attempts to activate and connect. If one link fails and the target cell sends MSC the handover
failure message, the counter increments. The measurement point

HANDOVER
Unit
Related Features
Times
Definition
Number of incoming handover failure due to other factors
Description

inter-BSC incoming handover due to other factors excluding circuit
block, circuit group mismatch and unavailable radio resource.
Usage
This counter is used to find out the frequency of unsuccessful MSCoriginated inter-BSC incoming handover due to other factors, and
is used to observe the external handover flow.
Measurement
Point
sends MSC the handover failure message. If the failure is due to
other factors, the counter increments. The measurement point is
HANDOVER
831
Unit
Related Features
Times
forced release
Definition
Number of MSC-controlled incoming handover attempts due to

forced release
Description
This counter counts the number of forced release attempts originated by target cell due to unavailable radio resource during the
process of MS-originated MSC-controlled inter-BSC incoming handover. When target instance fails to allocate the channel, forced
release attempts could be originated referring to the MS priority
and MSC & BSC settings.
Usage

MSC-controlled inter-BSC incoming handover attempts due to
forced release, which reflects the handover status.
Measurement
Point
When the target cell receives the wireless channel application request, if the application cause is MSC-controlled inter-BSC incoming handover and wireless channel is unavailable to target cell,
forced release attempt decision starts. If forced release attempt is
feasible, the counter increments before the target cell sends forced
release message to the instance that is to be force-released. The
Unit
832
Times
Related Features

ZGO-01-03-001 eMLPP
queue
Definition

queue
Description
This counter counts the number of queuing attempts originated by

target cell due to unavailable radio resource during the process of
MS-originated MSC-controlled inter-BSC incoming handover.
Usage

queue, which reflects the handover status.
Measurement
Point
queuing attempt decision starts. If queuing attempt is feasible,
the target cell has the target instance waiting in the queuing, and
Figure 877.
Unit
Related Features
Times
833
ZGO-01-03-001 eMLPP
forced handover
Definition

forced handovers
Description
This counter counts the number of forced-handover attempts originated by target cell due to unavailable radio resource during the
process of MS-originated MSC-controlled inter-BSC incoming handover.
Usage

forced handover, which reflects the handover status.
Measurement
Point
forced-handover attempt decision starts. If forced-handover attempt is feasible, the counter increments before the target cell
sends forced-handover message to the instance that is to be forced
handover. The measurement point is A, as shown in Figure 878.
Unit
Related Features
Times
ZGO-01-03-001 eMLPP
834
C901090037 MSC-control
led incoming handover time
due to queue
Definition
MSC-controlled incoming handover time due to queue
Description
This counter counts the total time of call queuing that participate
in MSC-controlled intra-cell incoming handover due to queue.
Usage
This counter is used to find out the total time of MSC-controlled

intra-cell incoming handover due to queue, which helps to understand the traffic status and the situation of the queuing for resource.
Measurement
Point
Under the condition that database acquires resource via dynamic channel conversion or MS releases resource, and queuing instance receives usable message, if the application cause
is MSC-controlled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 879.

835

released due to some causes, if the application cause is MSCcontrolled incoming handover, the queuing time accumulates.
Unit
Related Features
836
Second
C901090038 Queue number

of MSC-controlled incoming
handover
Definition
Queue number of MSC-controlled incoming handover
Description
This counter counts the total queue number of calls that participate
in BSC-controlled intra-cell incoming handover.
Usage
This counter is used to find out the total queue number of calls that
participate in MSC-controlled intra-cell incoming handover, which
helps to understand the traffic status.
Measurement
Point
Under the condition that database acquires resource via dynamic channel conversion or MS releases resource, and queuing instance receives usable message, if the application cause
is MSC-controlled incoming handover, the counter increments.

is MSC-controlled incoming handover, the counter increments.
837

released due to some causes, if the application cause is MSCcontrolled incoming handover, the counter increments. The
Unit
Related Features
838
Times
C901090039 MSC-contr
olled incoming handover
success time due to queue
Definition
MSC-controlled incoming handover success time due to queue
Description
This counter counts the total time of calls that participate in successful MSC-controlled intra-cell incoming handover due to queue
and acquiring resource.
Usage
This counter is used to find out the total queuing time of calls
that participate in successful MSC-controlled intra-cell incoming
handover due to queue and acquiring resource, and to find out the
valid queuing time.
Measurement
Point

channel conversion or MS releases resource, when queuing instance receives resource usable message, if the application cause
Unit
Related Features
Second
839
queue
Definition
Number of MSC-controlled incoming handover success due to

queue
Description
This counter counts the total number of calls that participate in

MSC-controlled intra-cell incoming handover due to queue and
successfully acquires resource.
Usage
This counter is used to find out the total number of calls that participate in MSC-controlled intra-cell incoming handover due to queue
and successfully acquires resource, and to find out the success ratio of queuing.
Measurement
Point

channel conversion or MS releases resource, and queuing instance
receives resource usable message, if the application cause is MSCcontrolled incoming handover, the counter increments. The measurement point is A, as shown in Figure 886.
Unit
Related Features
840
Times
from the same layer and
frequency
Definition
Number of incoming handover attempts from the same layer and

frequency
Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from the same layer
and frequency.
Usage

incoming handover attempts from the same layer and frequency,
which helps to make the network planning.
Measurement
Point
When intra-BSC target cell receives the channel application request from the source cell, if the application cause is inter-cell
incoming handover and the source cell is at the same layer and
frequency, the counter increments. The measurement point is A,
ATTEMPTS
Unit
Related Features
Times
841
from the same layer and
frequency
Definition
Number of incoming handover success from the same layer and

frequency
Description
This counter counts the number of successful BSC-controlled intercell incoming handover the target cell receives from the same layer
and frequency.
Usage

incoming handover success from the same layer and frequency,
and is used to observe the handover flow.
Measurement
Point
When intra-BSC target cell receives the handover completed message, if the application cause is BSC-controlled inter-cell handover
and the source cell is at the same layer and frequency, the counter
increments. The measurement point is A, as shown inFigure 888.
FIGURE 888 SUCCESSFUL BSC-CONTROLLED INTER-CELL INCOMING
HANDOVER
Unit
Related Features
842
Times
to the same layer and
frequency
Definition
Number of outgoing handover attempts to the same layer and frequency
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the target cell sends to the same layer
and frequency.
Usage

outgoing handover attempts to the same layer and frequency,
Measurement
Point
BSC starts the handover decision after it receives the measurement report from MS. If inter-cell handover is necessary, and the
current attempt cells are BSC-controlled internal cells at the same
layer and frequency, the counter increments. The measurement
Unit
Related Features
Times
843
to the same layer and
frequency
Definition
Number of outgoing handover success to the same layer and frequency
Description
This counter counts the number of successful BSC-controlled intercell outgoing handover the target cell sends to the same layer and
frequency.
Usage
This counter is used to find out the frequency of successful BSCcontrolled outgoing handover to the same layer and frequency,
Measurement
Point
During the process of BSC-controlled handover, if the source cell

receives the handover completed message from the target cell,
and the target cell is at the same layer and frequency, the counter
FIGURE 890 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING
HANDOVER
Unit
Related Features
844
Times
from undefined layer to the
same frequency
Definition
Number of incoming handover attempts from undefined layer to

the same frequency
Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from undefined
layer to the same frequency.
Usage

incoming handover attempts from undefined layer to the same
frequency, which helps to make the network planning.
Measurement
Point
incoming handover and the source cell is at the undefined layer
and the same frequency, the counter increments. The measurement point is A, as shown in Figure 891.
ATTEMPTS
Unit
Related Features
Times
845
same frequency
Definition
Number of incoming handover success from undefined layer to the

same frequency
Description
This counter counts the number of successful BSC-controlled inter-cell incoming handover the target cell receives from undefined
layer to the same frequency.
Usage

incoming handover success from undefined layer to the same frequency, which helps to observe the handover flow.
Measurement
Point
When intra-BSC target cell receives the handover completed message, if the application cause is BSC-controlled inter-cell handover,
and the source cell is at undefined layer and the same frequency,
Figure 892.
HANDOVER
Unit
Related Features
846
Times
same frequency
Definition
Number of outgoing handover attempts from undefined layer to

the same frequency
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell sends from undefined layer
to the same frequency.
Usage

outgoing handover attempts from undefined layer to the same frequency, which helps to make the network planning.
Measurement
Point
current attempt cells are BSC-controlled internal cells at undefined
layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 893.
Unit
Related Features
Times
847
same frequency
Definition
Number of outgoing handover success from undefined layer to the

same frequency
Description
This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell sends from undefined layer
Usage
This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from undefined layer to the same
frequency, which helps to make the network planning.
Measurement
Point

and the target cell is at undefined layer and the same frequency,
the counter increments. The measurement point is A, as shown
inFigure 894.
HANDOVER
Unit
Related Features
848
Times
C901090049 Number
attempts from undefined
layer (GSM900) to current
layer (GSM1800)
Definition
Number of incoming handover attempts from undefined layer

(GSM900) to current layer (GSM1800)
Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM1800) receives from
undefined layer (GSM900).
Usage

incoming handover attempts from undefined layer (GSM900) to
current layer (GSM1800), which helps to make the network planning.
Measurement
Point
When intra-BSC target cell (GSM1800) receives the channel application request from the source cell (GSM900), if the application
cause is inter-cell incoming handover and the source cell is at undefined layer, the counter increments. The measurement point is
ATTEMPTS
Unit
Related Features
Times
849
C901090052 Number
of outgoing handover
attempts from current layer
(GSM900) to undefined layer
(GSM1800)
Definition
Number of outgoing handover attempts from current layer

(GSM900) to undefined layer (GSM1800)
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to undefined layer (GSM1800).
Usage

outgoing handover attempts from undefined layer (GSM900) to
Measurement
Point
current attempt cells are BSC-controlled internal cells at undefined layer (GSM1800) and the current serving cell is GSM900,
Figure 896.
Unit
Related Features
850
Times
outgoing handover from
current layer (GSM900) to
Definition
Number of outgoing handover from current layer (GSM900) to undefined layer (GSM1800)
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to undefined layer
(GSM1800).
Usage

Measurement
Point

(GSM900) receives the radio resource unavailable message from
the target cell (GSM1800), and the target cell is at undefined layer
EXECUTION FLOW
Unit
Related Features
Times
851
C901090054 Number
success from current layer
(GSM900) to undefined layer
(GSM1800)
Definition
Number of outgoing handover success from current layer

(GSM900) to undefined layer (GSM1800)
Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends from
undefined layer to the same frequency (GSM1800).
Usage
frequency (GSM900) to current layer (GSM1800), which helps to
make the network planning.
Measurement
Point

(GSM900) receives the handover completed message from the target cell (GSM1800), and the target cell is at undefined layer and
the same frequency, the counter increments. The measurement
HANDOVER
Unit
Related Features
852
Times
C901090055 Number
layer (GSM900)
Definition
Number of incoming handover attempts from undefined layer

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from undefined layer (GSM1800).
Usage

incoming handover attempts from undefined layer (GSM1800) to
Measurement
Point
cause is inter-cell incoming handover and the source cell is at undefined layer, the counter increments. The measurement point is
ATTEMPTS
Unit
Related Features
Times
853
C901090058 Number
layer (GSM900)
Definition
Number of outgoing handover attempts from undefined layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to undefined layer (GSM900).
Usage

Measurement
Point
current attempted cell is BSC-controlled internal cell at undefined
layer (GSM900) or lower-layer cell at same frequency (GSM1800),
Figure 900.
Unit
Related Features
854
Times
to current layer (GSM900)
Definition
Number of outgoing handover from undefined layer (GSM1800) to

current layer (GSM900)
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to undefined layer
(GSM900).
Usage

Measurement
Point

the target cell (GSM900), and the target cell is at undefined layer
EXECUTION FLOW
Unit
Related Features
Times
855
C901090060 Number
layer (GSM900)
Definition
Number of outgoing handover success from undefined layer

Description
undefined layer to the same frequency (GSM900).
Usage
frequency (GSM1800) to current layer (GSM900), which helps to
make the network planning.
Measurement
Point

(GSM1800) receives the handover completed message from the
target cell (GSM900), and the target cell is at undefined layer and
HANDOVER
Unit
Related Features
856
Times
from upper layer to the same
frequency
Definition
Number of incoming handover attempts from upper layer to the

same frequency
Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from upper layer to
the same frequency.
Usage

incoming handover attempts from upper layer to the same frequency, which helps to make the network planning.
Measurement
Point
incoming handover and the source cell is at upper layer and the
same frequency, the counter increments. The measurement point
ATTEMPTS
Unit
Related Features
Times
857
from upper layer to the same
frequency
Definition
Number of incoming handover success from upper layer to the

same frequency
Description
This counter counts the number of successful BSC-controlled intercell incoming handover the target cell receives from upper layer to
the same frequency.
Usage
This counter is used to find out the frequency of BSC-controlled incoming handover success from upper layer to the same frequency,
Measurement
Point
When intra-BSC target cell receives the handover completed message, if the application cause is BSC-controlled inter-BSC handover
and the source cell is at upper and the same frequency, the counter
HANDOVER
Unit
Related Features
858
Times
from the same frequency to
upper layer
Definition
Number of outgoing handover attempts from the same frequency

to upper layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell sends from upper layer
Usage

outgoing handover attempts from upper layer to the same frequency, which helps to make the network planning.
Measurement
Point
current attempt cells are BSC-controlled internal cells at upper
Unit
Related Features
Times
859
upper layer
Definition
Number of outgoing handover success from the same frequency

to upper layer
Description
This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell sends from upper layer to
the same frequency.
Usage
This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from upper layer to the same frequency, which helps to make the network planning.
Measurement
Point

it means that MS has accessed the target channel, handover successful. If the target cell is at upper layer and the same frequency,
Figure 906.
HANDOVER
Unit
Related Features
860
Times
from lower layer to the same
frequency
Definition
Number of incoming handover attempts from lower layer to the

same frequency
Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from lower layer to
the same frequency.
Usage

incoming handover attempts from lower layer to the same frequency, which helps to make the network planning.
Measurement
Point
incoming handover and the source cell is at lower layer and the
ATTEMPTS
Unit
Related Features
Times
861
from lower layer to the same
frequency
Definition
Number of incoming handover success from lower layer to the

same frequency
Description
This counter counts the number of successful BSC-controlled intercell incoming handover the target cell receives from lower layer to
the same frequency.
Usage
This counter is used to find out the frequency of BSC-controlled incoming handover success from lower layer to the same frequency,
Measurement
Point
When intra-BSC target cell receives the handover completed message, if the application cause is BSC-controlled inter-BSC handover
and the source cell is at lower and the same frequency, the counter
HANDOVER
Unit
Related Features
862
Times
lower layer
Definition
Number of outgoing handover attempts from the same frequency

to lower layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell sends from the same frequency to lower layer.
Usage

outgoing handover attempts from the same frequency to lower
layer, which helps to make the network planning.
Measurement
Point
current attempt cells are BSC-controlled internal cells at lower
Unit
Related Features
Times
863
lower layer
Definition
Number of outgoing handover success from the same frequency

to lower layer
Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell sends from the same
frequency to lower layer.
Usage
This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from the same frequency to lower
layer, which helps to make the network planning.
Measurement
Point

and the target cell is at lower layer and the same frequency, the
Figure 910.
HANDOVER
Unit
Related Features
864
Times
from the same layer GSM900
to GSM1800
Definition
Number of incoming handover attempts from the same layer

GSM900 to GSM1800
Description
the same layer (GSM900).
Usage

incoming handover attempts from the same layer GSM900 to
GSM1800, which helps to make the network planning.
Measurement
Point
cause is inter-cell handover and the source cell is at the same layer,
Figure 911.
ATTEMPTS
Unit
Related Features
Times
865
to the same layer GSM900
to GSM1800
Definition
Number of outgoing handover attempts to the same layer GSM900

to GSM1800
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to the
same layer (GSM1800).
Usage

outgoing handover attempts to the same layer GSM900 to
Measurement
Point
BSC starts the handover decision after it receives the measurement report from MS. If inter-cell handover is necessary, and
the current attempt cells are BSC-controlled internal cells at the
same layer (GSM1800) and the current serving cell is GSM900,
in Figure 912.
Unit
Related Features
866
Times
outgoing handover to the
same layer GSM900 to
GSM1800
Definition
Number of outgoing handover to the same layer GSM900 to

GSM1800
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to the same layer
(GSM1800).
Usage

outgoing handover attempts to the same layer GSM900 to
Measurement
Point

the target cell (GSM1800), and the target cell is at the same layer
and frequency, the counter increments. The measurement point
EXECUTION FLOW
Unit
Related Features
Times
to the same layer GSM900
to GSM1800
Definition
Number of outgoing handover success to the same layer GSM900

to GSM1800
867
Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to the
same layer and frequency (GSM1800).
Usage
This counter is used to find out the frequency of successful BSCcontrolled outgoing handover to the same layer and frequency
from GSM900 to GSM1800, which helps to make the network planning.
Measurement
Point

(GSM900) receives the handover completed message from the target cell (GSM1800), and the target cell is at the same layer and
HANDOVER
Unit
Related Features
Times
868
Definition
Number of incoming handover attempts from GSM900 to GSM1800

Description
upper layer (GSM900).
Usage

incoming handover attempts at upper layer and from GSM900 to
Measurement
Point
cause is inter-cell handover and the source cell is at upper layer,
Figure 915.
ATTEMPTS
Unit
Related Features
Times
to the upper layer
Definition
Number of outgoing handover attempts from GSM900 to GSM1800

to the upper layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to upper
layer (GSM1800).
Usage

outgoing handover attempts from GSM900 to GSM1800 to the upper layer, which helps to make the network planning.
Measurement
Point
layer (GSM1800) and the current serving cell is GSM900, the
Figure 916.
869
Unit
Related Features
Times
GSM900 to GSM1800 to the
upper layer
870
Definition
Number of outgoing handover from GSM900 to GSM1800 to the

upper layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to upper layer
(GSM1800).
Usage

Measurement
Point

the target cell (GSM1800), and the target cell is at upper layer and

EXECUTION FLOW
Unit
Related Features
Times
to the upper layer
Definition
Number of outgoing handover success from GSM900 to GSM1800

to the upper layer
Description
This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell (GSM900) sends from upper
layer to the same frequency (GSM1800).
Usage
This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from upper layer to the same frequency from GSM900 to GSM1800, which helps to make the network planning.
Measurement
Point

(GSM900) receives the handover completed message from the target cell (GSM1800), and the target cell is at upper layer and the
871

HANDOVER
Unit
Related Features
Times
872
Definition

Description
lower layer (GSM900).
Usage

incoming handover attempts at lower layer and from GSM900 to
Measurement
Point
cause is inter-cell handover and the source cell is at lower layer,
Figure 919.

ATTEMPTS
Unit
Related Features
Times
Definition

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to lower
layer (GSM1800).
Usage

outgoing handover attempts to lower layer and from GSM900 to
Measurement
Point
Figure 920.
873
Unit
Related Features
Times
GSM900 to GSM1800 in the
lower layer
874
Definition
Number of outgoing handover from GSM900 to GSM1800 in the

lower layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to lower layer
(GSM1800).
Usage

outgoing handover attempts to lower layer and from GSM900 to
Measurement
Point

the target cell (GSM1800), and the target cell is at lower layer and

EXECUTION FLOW
Unit
Related Features
Times
in the lower layer
Definition

in the lower layer
Description
This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell (GSM900) sends from the
same frequency to lower layer (GSM1800).
Usage
This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from the same frequency to lower
layer from GSM900 to GSM1800, which helps to make the network
planning.
Measurement
Point

(GSM900) receives the handover completed message from the target cell (GSM1800), and the target cell is at lower layer and the
875

HANDOVER
Unit
Related Features
Times
from the same layer
876
Definition

from the same layer
Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from the
Usage

incoming handover attempts at the same layer and from GSM1800
to GSM900, which helps to make the network planning.
Measurement
Point
cause is inter-cell handover and the source cell is at the same layer,
Figure 923.

ATTEMPTS
Unit
Related Features
Times
from the same layer
Definition

from the same layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to the
Usage

outgoing handover attempts to the same layer and from GSM1800
Measurement
Point
BSC starts the handover decision after it receives the measurement report from MS. If inter-cell handover is necessary, and
the current attempt cells are BSC-controlled internal cells at the
same layer (GSM900) and the current serving cell is GSM1800,
in Figure 924.
877
Unit
Related Features
Times
the same layer
878
Definition
Number of outgoing handover from GSM1800 to GSM900 from the

same layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to the same layer
(GSM900).
Usage

outgoing handover attempts to the same layer and from GSM1800
Measurement
Point

the target cell (GSM900), and the target cell is at the same layer
and frequency, the counter increments. The measurement point

EXECUTION FLOW
Unit
Related Features
Times
from the same layer
Definition

from the same layer
Description
This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell (GSM1800) sends to the
same layer and frequency (GSM900).
Usage
This counter is used to find out the frequency of successful BSCcontrolled outgoing handover to the same layer and frequency and
from GSM1800 to GSM900, which helps to make the network planning.
Measurement
Point

target cell (GSM900), and the target cell is at the same layer and
879

HANDOVER
Unit
Related Features
Times
880
Definition

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from upper layer (GSM1800).
Usage

incoming handover attempts at upper layer and from GSM1800 to
Measurement
Point
cause is inter-cell handover and the source cell is at upper layer,
Figure 927.

ATTEMPTS
Unit
Related Features
Times
to the upper layer
Definition

to the upper layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to upper
layer (GSM900).
Usage

Measurement
Point
Figure 928.
881
Unit
Related Features
Times
upper layer
882
Definition

upper layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to upper layer
(GSM900).
Usage

Measurement
Point

the target cell (GSM900), and the target cell is at upper layer and

EXECUTION FLOW
Unit
Related Features
Times
to the upper layer
Definition

to the upper layer
Description
upper layer to the same frequency (GSM900).
Usage
This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from upper layer to the same frequency and from GSM1800 to GSM900, which helps to make the
network planning.
Measurement
Point

target cell (GSM900), and the target cell is at upper layer and the
883

HANDOVER
Unit
Related Features
Times
884
Definition

Description
lower layer (GSM1800).
Usage

incoming handover attempts from GSM1800 to GSM900 from the
lower layer, which helps to make the network planning.
Measurement
Point
cause is inter-cell handover and the source cell is at lower layer,
Figure 931.

ATTEMPTS
Unit
Related Features
Times
to the lower layer
Definition

to the lower layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to lower
layer (GSM900).
Usage

outgoing handover attempts from GSM1800 to GSM900 to the
Measurement
Point
Figure 932.
885
Unit
Related Features
Times
lower layer
886
Definition

lower layer
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to lower layer
(GSM900).
Usage

outgoing handover attempts from GSM1800 to GSM900 to the
Measurement
Point

the target cell (GSM900), and the target cell is at lower layer and

EXECUTION FLOW
Unit
Related Features
Times
to the lower layer
Definition

to the lower layer
Description
This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell (GSM1800) sends from the
same frequency to lower layer (GSM900).
Usage
This counter is used to find out the frequency of successful

BSC-controlled outgoing handover from the same frequency from
GSM1800 to GSM900 to the lower layer, which helps to make the
network planning.
Measurement
Point

target cell (GSM900), and the target cell is at lower layer and the
887

HANDOVER
Unit
Related Features
Times
intra-cell handover attempts
Definition
Number of intra-cell handover attempts
Description
This counter counts the number of intra-cell handover attempts

originated from the source cell by MS.
Usage
This counter is used to find out the frequency of intra-cell handover

attempts. It is one of the parameters to measure the wireless
environment.
Measurement
Point
BSC starts the handover decision after it receives the measurement report from MS. If intra-cell handover is necessary, the
Figure 935.
FIGURE 935 INTRA-CELL HANDOVER ATTEMPT
Unit
Related Features
888
Times
intra-cell inner-circle-to-oute
r-circle handover attempts
Definition
Number of intra-cell inner-circle-to-outer-circle handover attempts
Description
This counter counts the number of inner-circle-to-outer-circle handover attempts originated by MS when configuring the sub cell.
Usage
This counter is used to find out the frequency of inter-sub cell inner-circle-to-outer-circle handover attempts. It is one of the parameters to measure the sub cell operation status.
Measurement
Point
BSC starts the handover decision after it receives the measurement report from MS. If inner-circle-to-outer-circle handover is
necessary, the counter increments. The measurement point is A,
Unit
Related Features
Times
intra-cell inner-circle-to-oute
r-circle handover success
Definition
Number of intra-cell inner-circle-to-outer-circle handover success
Description
This counter counts the number of successful inner-circle-to-outercircle handovers originated by MS when configuring the sub cell.
Usage
This counter is used to find out the frequency of successful intersub cell inner-circle-to-outer-circle handovers.
Measurement
Point
During handover, if the source instance receives the handover

completed message from the target instance, and the application
889
cause is inner-circle-to-outer-circle handover, the counter increments. The measurement point is A, as shown in Figure 937.
FIGURE 937 SUCCESSFUL INTRA-CELL HANDOVER
Unit
Related Features
Times
intra-cell outer-circle-to-inne
Definition
Number of intra-cell outer-circle-to-inner-circle handover attempts
Description
This counter counts the number of outer-circle-to-inner-circle handover attempts originated by MS when configuring the sub cell.
Usage
This counter is used to find out the frequency of inter-sub cell

outer-circle-to-inner-circle handover attempts. It is one of the parameters to measure the sub cell operation status.
Measurement
Point
BSC starts the handover decision after it receives the measurement report from MS. If outer-circle-to-inner-circle handover is
890
Unit
Related Features
Times
intra-cell outer-circle-to-inne
Definition
Number of intra-cell outer-circle-to-inner-circle handover success
Description
This counter counts the number of successful outer-circle-to-inner-circle handovers originated by MS when configuring the sub
cell.
Usage
This counter is used to find out the frequency of successful intersub cell outer-circle-to-inner-circle handovers, and is to find out
the success ratio of intra-sub cell handovers.
Measurement
Point

cause is outer-circle-to-inner-circle handover, the counter increments. The measurement point is A, as shown in Figure 939.
Unit
Related Features
Times
891
intra-cell inner-circle-to-inner
-circle handover attempts
Definition
Number of intra-cell inner-circle-to-inner-circle handover attempts
Description
This counter counts the number of inner-circle-to-inner-circle handover attempts originated by MS when configuring the sub cell.
Usage

inner-circle-to-inner-circle handover attempts. It is one of the parameters to measure the sub cell operation status.
Measurement
Point
BSC starts the handover decision after it receives the measurement report from MS. If inner-circle-to-inner-circle handover is
Unit
Related Features
Times
intra-cell inner-circle-to-inner
-circle handover success
892
Definition
Number of intra-cell inner-circle-to-inner-circle handover success
Description
This counter counts the number of successful inner-circle-to-innercircle handovers originated by MS when configuring the sub cell.
Usage
This counter is used to find out the frequency of successful intersub cell inner-circle-to-inner-circle handovers.
Measurement
Point

cause is inner-circle-to-inner-circle handover, the counter increments. The measurement point is A, as shown in Figure 941.
Unit
Related Features
Times
intra-cell outer-circle-to-oute
Definition
Number of intra-cell outer-circle-to-outer-circle handover attempts
Description
This counter counts the number of outer-circle-to-outer-circle handover attempts originated by MS when configuring the sub cell.
Usage

outer-circle-to-outer-circle handover attempts. It is one of the
parameters to measure the sub cell operation status.
Measurement
Point
BSC starts the handover decision after it receives the measurement report from MS. If outer-circle-to-outer-circle handover is
893
Unit
Related Features
Times
intra-cell outer-circle-to-oute
Definition
Number of intra-cell outer-circle-to-outer-circle handover success
Description
This counter counts the number of successful outer-circle-to-outer-circle handovers originated by MS when configuring
the sub cell.
Usage
This counter is used to find out the frequency of successful intersub cell outer-circle-to-outer-circle handovers.
Measurement
Point

cause is outer-circle-to-outer-circle handover, the counter increments. The measurement point is A, as shown in Figure 943.
Unit
894
Times
Related Features
handover attempts from 2G
to 3G
Definition
Number of handover attempts from 2G to 3G
Description
This counter counts the number of inter-system 2G to 3G handover

attempts originated by MS.
Usage
This counter is used to find out the frequency of handover attempts

from 2G to 3G. It is one of the parameters to measure the wireless
environment.
Measurement
Point
current attempt cells are 3G cells, BSC sends MSC the handover
request message A_HO_RQD, the counter increments. The measurement point is A, as shown inFigure 944.
Unit
Related Features
Times
handover from 2G to 3G
Definition
Number of handover from 2G to 3G
895
Description

originated by MS.
Usage
This counter is used to find out the frequency of handover from

2G to 3G. It is one of the parameters to measure the wireless
environment.
Measurement
Point
current attempt cells are 3G cells, BSC sends MSC the handover
request message A_HO_RQD to trigger the inter-BSC handover.
If BSC receives the handover command returned from MSC, the
Figure 945.
FIGURE 945 MSC-CONTROLLED OUTGOING HANDOVER
Unit
Related Features
Times
handover success from 2G
to 3G
Definition
896
Number of handover success from 2G to 3G
Description
This counter counts the number of successful inter-system 2G to

3G handovers originated by MS.
Usage
This counter is used to find out the frequency of handover success

environment.
Measurement
Point
current attempt cells are governed by various BSCs, BSC sends
MSC the handover request message A_HO_RQD to trigger the inter-BSC handover. If MS accesses the target 3G cell successfully
and the source 2G cell receives the release command from MSC,
Figure 946.
FIGURE 946 SUCCESSFUL MSC-CONTROLLED OUTGOING HANDOVER
Unit
Related Features
Times
handover attempts from 3G
to 2G
Definition
Number of handover attempts from 3G to 2G
Description

attempts originated by MS.
Usage
This counter is used to find out the frequency of handover attempts

environment.
Measurement
Point
When 2G cell receives the channel application request, if the application cause is external incoming handover and the source cell
is 3G cell, the counter increments. The measurement point is A,
as shown inFigure 947.
897
Unit
Related Features
Times
handover from 3G to 2G
Definition
Number of handover from 3G to 2G
Description
This counter counts the number of inter-system 3G to 2G outgoing

handover originated by MS.
Usage
This counter is used to find out the frequency of handover from

3G to 2G. It is one of the parameters to measure the wireless
environment.
Measurement
Point
When 2G cell receives the channel handover request from MSC, if

the channel is successfully allocated and activated, and the source
cell is 3G cell, the counter increments. The measurement point is
FIGURE 948 MSC-CONTROLLED INCOMING HANDOVER
Unit
898
Times
Related Features
handover success from 3G
to 2G
Definition
Number of handover success from 3G to 2G
Description
This counter counts the number of successful inter-system 3G to

2G incoming handover originated by MS.
Usage
This counter is used to find out the frequency of handover success

environment.
Measurement
Point
When 2G cell receives the handover completed message, if the

application cause is MSC-controlled inter-BSC incoming handover
and the source cell is 3G cell, the counter increments. The measurement point is A, as shown in Figure 949.
Unit
Related Features
Times
from TCH/F
Definition
Number of intra-cell handover attempts from TCH/F
Description
This counter counts the number of intra-cell incoming handover

attempts from TCH/F originated by MS.
Usage
This counter is used to find out the frequency of intra-cell incoming handover attempts from TCH/F. It is one of the parameters to
measure the wireless environment.
899
Measurement
Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/F,
Figure 950.
FIGURE 950 INTRA-CELL INCOMING HANDOVER ATTEMPT
Unit
Related Features
Times
intra-cell TCH/F-to-TCH/F
handover
Definition
900
Number of intra-cell TCH/F-to-TCH/F handover
Description
This counter counts the number of intra-cell TCH/F-to-TCH/F incoming handover originated by MS.
Usage
This counter is used to find out the frequency of intra-cell TCH/Fto-TCH/F incoming handover attempts. It is one of the parameters
Measurement
Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is
TCH/F; if the new channel is successfully applied and activated,
Figure 951.
FIGURE 951 INTRA-CELL INCOMING HANDOVER
Unit
Related Features
Times
intra-cell TCH/F-to-TCH/F
handover success
Definition
Number of intra-cell TCH/F-to-TCH/F handover success
Description
This counter counts the number of successful intra-cell TCH/F-toTCH/F incoming handover originated by MS.
Usage
This counter is used to find out the frequency of successful intra-cell TCH/F-to-TCH/F incoming handover. It is one of the parameters to measure the wireless environment.
Measurement
Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/F;
if MS successfully accesses the new channel and the new channel
is TCH/F, the counter increments. The measurement point is A, as
Unit
Times
901
Related Features

intra-cell TCH/F-to-TCH/H
handover
Definition
Number of intra-cell TCH/F-to-TCH/H handover
Description
This counter counts the number of intra-cell TCH/F-to-TCH/H incoming handover originated by MS.
Usage
This counter is used to find out the frequency of intra-cell TCH/Fto-TCH/H incoming handover attempts. It is one of the parameters
Measurement
Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is
TCH/H; if the new channel is successfully applied and activated,
Figure 953.
Unit
Related Features
Times
902
intra-cell TCH/F-to-TCH/H
handover success
Definition
Number of intra-cell TCH/F-to-TCH/H handover success
Description
This counter counts the number of successful intra-cell TCH/F-toTCH/H incoming handover originated by MS.
Usage
This counter is used to find out the frequency of successful intra-cell TCH/F-to-TCH/H incoming handover. It is one of the parameters to measure the wireless environment.
Measurement
Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/F;
is TCH/H, the counter increments. The measurement point is A,
Unit
Related Features
Times
from TCH/H
Definition
Description
Number of intra-cell handover attempts from TCH/H

This counter counts the number of intra-cell incoming handover
attempts from TCH/H originated by MS.
903
Usage
This counter is used to find out the frequency of intra-cell incoming

handover attempts from TCH/H. It is one of the parameters to
Measurement
Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/H,
Figure 955.
Unit
Related Features
Times
intra-cell TCH/H-to-TCH/F
handover
Definition
904
Number of intra-cell TCH/H-to-TCH/F handover
Description
This counter counts the number of intra-cell TCH/H-to-TCH/F incoming handover originated by MS.
Usage
This counter is used to find out the frequency of intra-cell TCH/Hto-TCH/F incoming handover attempts. It is one of the parameters
Measurement
Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/H;
if the new channel is successfully applied and activated and the
new channel is TCH/F, the counter increments. The measurement
Unit
Related Features
Times
intra-cell TCH/H-to-TCH/F
handover success
Definition
Number of intra-cell TCH/H-to-TCH/F handover success
Description
This counter counts the number of successful intra-cell TCH/H-toTCH/F incoming handover originated by MS.
Usage
This counter is used to find out the frequency of successful intra-cell TCH/H-to-TCH/F incoming handover. It is one of the parameters to measure the wireless environment.
Measurement
Point
is TCH/F, the counter increments. The measurement point is A,
905
Unit
Related Features
Times
intra-cell TCH/H-to-TCH/H
handover
Definition
906
Number of intra-cell TCH/H-to-TCH/H handover
Description
This counter counts the number of intra-cell TCH/H-to-TCH/H incoming handover originated by MS.
Usage
This counter is used to find out the frequency of intra-cell TCH/Hto-TCH/H incoming handover attempts. It is one of the parameters
Measurement
Point
new channel is TCH/H, the counter increments. The measurement
Unit
Related Features
Times
intra-cell TCH/H-to-TCH/H
handover success
Definition
Number of intra-cell TCH/H-to-TCH/H handover success
Description
This counter counts the number of successful intra-cell TCH/H-toTCH/H incoming handover originated by MS.
Usage
This counter is used to find out the frequency of successful intra-cell TCH/H-to-TCH/H incoming handover. It is one of the parameters to measure the wireless environment.
Measurement
Point
907
Unit
Related Features
Times
inter-cell handover attempts
from TCH/F
Definition
Number of inter-cell handover attempts from TCH/F
Description
This counter counts the number of inter-cell incoming handover

attempts from TCH/F originated by MS.
Usage
This counter is used to find out the frequency of inter-cell incoming handover attempts from TCH/F. It is one of the parameters to
Measurement
Point
When BSC receives the channel application request, if the application cause is inter-cell handover, and the source channel is TCH/F,
Figure 960.
ATTEMPTS
Unit
Related Features
Times
908
inter-cell TCH/F-to-TCH/F
handover
Definition
Number of inter-cell TCH/F-to-TCH/F handover
Description
This counter counts the number of inter-cell TCH/F-to-TCH/F incoming handover originated by MS.
Usage
This counter is used to find out the frequency of inter-cell TCH/Fto-TCH/F incoming handover attempts. It is one of the parameters
Measurement
Point
When BSC receives the channel application request, if the application cause is inter-cell handover, and the source channel is
TCH/F; if the new channel is successfully applied and activated,
Figure 961.
ATTEMPTS
Unit
Related Features
Times
inter-cell TCH/F-to-TCH/F
handover success
Definition
Description
Number of inter-cell TCH/F-to-TCH/F handover success

This counter counts the number of successful inter-cell TCH/F-toTCH/F incoming handover originated by MS.
909
Usage
This counter is used to find out the frequency of successful inter-cell TCH/F-to-TCH/F incoming handover. It is one of the parameters to measure the wireless environment.
Measurement
Point
When BSC receives the channel application request, if the application cause is inter-cell handover, and the source channel is TCH/F;
Unit
Related Features
Times
inter-cell TCH/F-to-TCH/H
handover
Definition
910
Number of inter-cell TCH/F-to-TCH/H handover
Description
This counter counts the number of inter-cell TCH/F-to-TCH/H incoming handover originated by MS.
Usage
This counter is used to find out the frequency of inter-cell TCH/Fto-TCH/H incoming handover attempts. It is one of the parameters
Measurement
Point

ATTEMPTS
Unit
Related Features
Times
inter-cell TCH/F-to-TCH/H
handover success
Definition
Number of inter-cell TCH/F-to-TCH/H handover success
Description
This counter counts the number of successful inter-cell TCH/F-toTCH/H incoming handover originated by MS.
Usage
This counter is used to find out the frequency of successful inter-cell TCH/F-to-TCH/H incoming handover. It is one of the parameters to measure the wireless environment.
Measurement
Point
911
Unit
Related Features
Times
inter-cell handover attempts
from TCH/H
Definition
912
Number of inter-cell handover attempts from TCH/H
Description
This counter counts the number of inter-cell incoming handover

attempts from TCH/H originated by MS.
Usage
This counter is used to find out the frequency of inter-cell incoming

handover attempts from TCH/H. It is one of the parameters to
Measurement
Point
When BSC receives the channel application request, if the application cause is inter-cell handover, and the source channel is TCH/H,
Figure 965.

ATTEMPTS
Unit
Related Features
Times
inter-cell TCH/H-to-TCH/F
handover
Definition
Number of inter-cell TCH/H-to-TCH/F handover
Description
This counter counts the number of inter-cell TCH/H-to-TCH/F incoming handover originated by MS.
Usage
This counter is used to find out the frequency of inter-cell TCH/Hto-TCH/F incoming handover attempts. It is one of the parameters
Measurement
Point
When BSC receives the channel application request, if the application cause is inter-cell handover, and the source channel is TCH/H;
new channel is TCH/F, the counter increments. The measurement
913

ATTEMPTS
Unit
Related Features
Times
inter-cell TCH/H-to-TCH/F
handover success
Definition
914
Number of inter-cell TCH/H-to-TCH/F handover success
Description
This counter counts the number of successful inter-cell TCH/H-toTCH/F incoming handover originated by MS.
Usage
This counter is used to find out the frequency of successful inter-cell TCH/H-to-TCH/F incoming handover. It is one of the parameters to measure the wireless environment.
Measurement
Point
Unit
Related Features
Times
inter-cell TCH/H-to-TCH/H
handover
Definition
Number of inter-cell TCH/H-to-TCH/H handover
Description
This counter counts the number of inter-cell TCH/H-to-TCH/H incoming handover originated by MS.
Usage
This counter is used to find out the frequency of inter-cell TCH/Hto-TCH/H incoming handover attempts. It is one of the parameters
Measurement
Point
915

ATTEMPTS
Unit
Related Features
Times
inter-cell TCH/H-to-TCH/H
handover success
Definition
916
Number of inter-cell TCH/H-to-TCH/H handover success
Description
This counter counts the number of successful inter-cell TCH/H-toTCH/H incoming handover originated by MS.
Usage
This counter is used to find out the frequency of successful inter-cell TCH/H-to-TCH/H incoming handover. It is one of the parameters to measure the wireless environment.
Measurement
Point
Unit
Related Features
Times
C901090142 Total
dual-band outgoing
handover attempts
Definition
Total dual band outgoing handover attempts
Description
This counter counts the number of MSC-controlled inter-BSC (the

source cell and the target cell are at different bands) outgoing
handover attempts originated from the source cell by MS.
Usage
This counter is used to find out the frequency of MSC-controlled inter-BSC (the source cell and the target cell are at different bands)
outgoing handover attempts. It is one of the parameters to measure the wireless environment.
Measurement
Point
current attempt cells are governed by different BSCs, BSC will send
MSC the handover request A_HO_RQD to trigger inter-BSC handover. If the source cell and the target cell that are at different
bands, the counter increments. The measurement point is A, as
917
Unit
Times

attempts
Definition
918
Total dual band incoming handover attempts
Description
This counter counts the number of inter-BSC (the source cell and
the target cell are at different bands) incoming handover attempts
originated by MSC.
Usage
This counter is used to find out the frequency of inter-BSC (the

source cell and the target cell are at different bands) incoming
handover attempts. It is one of the parameters to measure the
Measurement
Point
When the target cell receives the channel application request, if the
application cause is external incoming handover, and the source
cell and the target cell that are at different bands, the counter increments. The measurement point is A, as shown in Figure 971.
Unit
Times
intra-cell invalid handovers
Definition
Number of intra-cell invalid handovers
Description
This counter counts the number of intra-cell invalid handovers. Invalid handover refers to that: handovers continue to happen in a
cell where there is UL /DL interference; if the number of the handovers exceeds the pre-set threshold, intra-cell handover punishment will be triggered to stop the continuous handovers; if there
is no new interference handover during sending the measurement
report of pre-set number, then the next handover will be considered valid.
Usage
This counter is used to find out the frequency of intra-cell invalid

handover attempts. It is one of the parameters to measure the
Measurement
Point
When BSC receives the channel application request, if the application cause is intra-cell interference handover, and such interference handover has already occurred in the pre-defined scope of
time, the counter increments. The measurement point is A, as
919
Unit
Related Features
Times
ZGO-02-02-005 Handover Failure Penalty
(emergency service)
920
Definition

due to forced release (emergency service)
Description
This counter counts the number of forced release attempts due to

unavailable radio resource in target cell in the process of BSC-controlled inter-cell incoming handover initiated by a MS on emergency service. Target instance can initiate forced release attempt
based on MS priority and MSC & BSC settings during channel allocation failure.
Usage
This counter counts the frequency of forced release attempts occurred during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover process.
Measurement
Point
Intra-BSC target cell receives radio channel request to determine

whether to do forced release attempt if the request reason is BSCcontrolled inter-cell incoming handover and the target cell has not
available radio channel. This counter increments before target
cell sends forced release message to forced release instance. The
measurement point is A shown in Figure 973.
Unit
Times
incoming handover (forced
release) (emergency
service)
Definition
Number of BSC-controlled inter-cell incoming handover (forced release) (emergency service)
Description
This counter counts the number of forced release due to unavailable radio resource in target cell in the process of BSC-controlled
inter-cell incoming handover initiated by a MS on emergency service.
Usage
This counter counts the frequency of forced release occurred during BSC-controlled inter-cell incoming handover initiated by a MS.
It can reflect the handover process.
Measurement
Point
Intra-BSC target cell receives radio channel request to do forced

release if the request reason is BSC-controlled inter-cell incoming
handover and the target cell has not available radio channel. This
counter increments if target cell receives available resource message sent from forced instance. The measurement point is A2, as
921
FIGURE 974 BSC-CONTROLLED FORCED RELEASE ON INCOMING HANDOVER
Unit
Times
due to forced handover
(emergency service)
922
Definition

due to forced handover (emergency service)
Description
This counter counts the number of forced handover attempts due

to unavailable radio resource in target cell in the process of BSCcontrolled inter-cell incoming handover initiated by a MS on emergency service.
Usage
This counter counts the frequency of forced handover attempts

occurred during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover process.
Measurement
Point

whether to do forced handover attempt if the request reason is
BSC-controlled inter-cell incoming handover and the target cell has
not available radio channel. This counter increments before target
cell sends forced handover message to forced handover instance.
Unit
Times
incoming handover (forced
handover) (emergency
service)
Definition
Number of BSC-controlled inter-cell incoming handover (forced

handover) (emergency service)
Description
This counter counts the number of forced handover due to unavailable radio resource in target cell in the process of BSC-controlled
Usage
This counter counts the frequency of forced handover occurred

during BSC-controlled inter-cell incoming handover initiated by a
MS. It can reflect the handover process.
Measurement
Point
Intra-BSC target cell receives radio channel request and adds it

into a queue after sending forced handover message to forced handover instance if the request reason is BSC-controlled inter-cell incoming handover and the target cell has not available radio channel. This counter increments if target cell receives available resource message. The measurement point is A2, as shown in Figure
976.
923
FIGURE 976 BSC-CONTROLLED FORCED HANDOVER ON INCOMING

HANDOVER
Unit
Times
due to queue (emergency
service)
924
Definition

due to queue (emergency service)
Description
This counter counts the number of queue attempts due to unavailable radio resource in target cell in the process of BSC-controlled
Usage
This counter counts the frequency of queue attempts occurred during BSC-controlled inter-cell incoming handover initiated by a MS.
Measurement
Point

whether to do queue if the request reason is BSC-controlled intercell incoming handover and the target cell has not available radio
channel. This counter increments if target cell adds target instance

into a queue. The measurement point is A, as shown in Figure 977.
Unit
Times
incoming handover (queue)
(emergency service)
Definition
Number of BSC-controlled inter-cell incoming handover (queue)

(emergency service)
Description
This counter counts the number of queue due to unavailable radio

resource in target cell in the process of BSC-controlled inter-cell
incoming handover initiated by a MS on emergency service.
Usage
This counter counts the frequency of queue occurred during BSCcontrolled inter-cell incoming handover initiated by a MS. It can
reflect the handover process.
Measurement
Point
Intra-BSC target cell receives radio channel request and adds target instance into a queue if the request reason is BSC-controlled
inter-cell incoming handover and the target cell has not available
radio channel. Thereafter, this counter increments if target cell receives available resource message. The measurement point is A2,
925
FIGURE 978 BSC-CONTROLLED QUEUE ON INCOMING HANDOVER
Unit
Times
forced release (emergency
service)
926
Definition

forced release (emergency service)
Description
This counter counts the number of forced release attempts due to

unavailable radio resource in target cell in the process of MSC-controlled inter-BSC incoming handover initiated by a MS on emergency service. Target instance can initiate forced release attempt
based on MS priority and MSC & BSC settings during channel allocation failure.
Usage
This counter counts the frequency of forced release attempts occurred during BSC-controlled inter-BSC incoming handover initiated by a MS. It can reflect the handover process.
Measurement
Point
Target cell receives radio channel request to determine whether to

do forced release attempt if the request reason is MSC-controlled
inter-BSC incoming handover and the target cell has not available
radio channel. This counter increments before target cell sends
forced release message to forced release instance. The measurement point is A shown in Figure 979.
FIGURE 979 MSC-CONTROLLED FORCED RELEASE ATTEMPT ON INCOMING
HANDOVER
Unit
Times
handover (forced release)
(emergency service)
Definition
Number of MSC-controlled incoming handover (forced release)

(emergency service)
Description
This counter counts the number of forced handover due to unavailable radio resource in target cell in the process of MSC-controlled
inter-BSC incoming handover initiated by a MS on emergency service.
Usage

during BSC-controlled inter-BSC incoming handover initiated by a
Measurement
Point

into a queue after sending forced handover message to forced handover instance if the request reason is MSC-controlled inter-BSC
incoming handover and the target cell has not available radio channel. This counter increments if target cell receives available resource message. The measurement point is A, as shown in Figure
980.
927
FIGURE 980 MSC-CONTROLLED FORCED RELEASE ON INCOMING HANDOVER
Unit
Times
MSC-controlled inter-cell
due to forced handover
(emergency service)
928
Definition
Number of MSC-controlled inter-cell incoming handover attempts

due to forced handover (emergency service)
Description
This counter counts the number of forced handover attempts due

to unavailable radio resource in target cell in the process of MSCcontrolled inter-BSC incoming handover initiated by a MS on emergency service.
Usage
This counter counts the frequency of forced handover attempt occurred during MSC-controlled inter-BSC incoming handover initiated by a emergent MS. It can reflect the handover process.
Measurement
Point
Target cell receives radio channel request to determine whether

to do forced handover attempt if the request reason is MSC-controlled inter-BSC incoming handover and the target cell has not
available radio channel. This counter increments before target cell
sends forced handover message to forced handover instance. The
FIGURE 981 MSC-CONTROLLED FORCED HANDOVER ATTEMPT ON INCOMING

HANDOVER
Unit
Times
handover (forced release)
(emergency service)
Definition
Number of MSC-controlled incoming handover (forced release)

(emergency service)
Description
This counter counts the number of forced handover due to unavailable radio resource in target cell in the process of MSC-controlled
Usage

during BSC-controlled inter-BSC incoming handover initiated by a
Measurement
Point

into a queue after sending forced handover message to forced handover instance if the request reason is MSC-controlled inter-BSC
incoming handover and the target cell has not available radio channel. This counter increments if target cell receives available resource message. The measurement point is A, as shown in Figure
982.
929
FIGURE 982 MSC-CONTROLLED FORCED HANDOVER ON INCOMING

HANDOVER
Unit
Times
queue (emergency service)
930
Definition

queue (emergency service)
Description
This counter counts the number of queue attempts due to unavailable radio resource in target cell in the process of MSC-controlled
Usage
This counter counts the frequency of queue attempts occurred during BSC-controlled inter-BSC incoming handover initiated by a MS.
Measurement
Point
Target cell receives radio channel request to determine whether to

do a queue if the request reason is MSC-controlled inter-BSC incoming handover and the target cell has not available radio channel. This counter increments if target cell adds target instance into
a queue. The measurement point is A, as shown in Figure 983.
FIGURE 983 MSC-CONTROLLED QUEUE ATTEMPT ON INCOMING HANDOVER
Unit
Times
C901090160 Number
of MSC-controlled
incoming handover (queue)
(emergency service)
Definition
Number of MSC-controlled incoming handover (queue) (emergency service)
Description
This counter counts the number of queue due to unavailable radio

resource in target cell in the process of MSC-controlled inter-BSC
incoming handover initiated by a MS on emergency service.
Usage
This counter counts the frequency of queue occurred during BSCcontrolled inter-BSC incoming handover initiated by a MS. It can
reflect the handover process.
Measurement
Point
Target cell receives radio channel request and adds target instance
into a queue if the request reason is MSC-controlled inter-BSC
incoming handover and the target cell has not available radio
channel. Thereafter, this counter increments if target cell receives
available resource message. The measurement point is A, as
931
FIGURE 984 MSC-CONTROLLED QUEUE ON INCOMING HANDOVER
Unit
Times
forced handover target
not found (BSC-controlled
inter-cell handover due to
forced handover)
932
Definition
Number of forced handover target not found (BSC-controlled intercell handover due to forced handover)
Description
This counter counts the number of forced handover target not

found due to unavailable radio resource in target cell in the process
of BSC-controlled inter-cell incoming handover initiated by a MS.
Usage
This counter counts the frequency of forced handover target not

found during BSC-controlled inter-cell incoming handover initiated
by a MS. It can reflect the handover process.
Measurement
Point
Intra-BSC target cell receives radio channel request if the request

reason is BSC-controlled inter-cell incoming handover and the target cell has not available radio channel. This counter increments if
the forced handover target is not found after initiating forced handover attempt. The measurement point is A, as shown inFigure
985.
FIGURE 985 FORCED HANDOVER TARGET NOT FOUND (BSC-CONTROLLED

INTER-CELL HANDOVER DUE TO FORCED HANDOVER)
Unit
Times
request to lower PRI user
(BSC-controlled inter-cell
handover)
Definition
Number of send forced handover request to lower PRI user

(BSC-controlled inter-cell handover due to forced handover)
Description
This counter counts the number of sending forced handover request to lower priority user on forced handover attempt due to
unavailable radio resource in target cell in the process of BSC-controlled inter-cell incoming handover initiated by a MS.
Usage
This counter counts the frequency of sending forced handover request to a lower priority user during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover
process.
Measurement
Point

reason is BSC-controlled inter-cell incoming handover and the target cell has not available radio channel. This counter increments
if sending forced handover request to a lower priority user after
933
initiating forced handover attempt. The measurement point is A,

FIGURE 986 SEND FORCED HANDOVER REQUEST TO LOWER PRI USER
(BSC-CONTROLLED INTER-CELL HANDOVER DUE TO FORCED HANDOVER)
Unit
Times
C901090163 Number of recv

failure from lower PRI user
request resource for forced
handover (BSC-controlled
forced handover)
934
Definition
Number of recv failure from lower PRI user request resource for
forced handover (BSC-controlled inter-cell handover due to forced
handover)
Description
This counter counts the number of receiving failure from lower priority user due to failure of resource while forced handover attempt
is initiated due to unavailable radio resource in target cell in the
process of BSC-controlled inter-cell incoming handover initiated by

a MS.
Usage
This counter counts the frequency of receiving failure of forced

handover request from a lower priority user during BSC-controlled
inter-cell incoming handover initiated by a MS. It can reflect the
handover process.
Measurement
Point

receiving failure of forced handover request from a lower priority
user after initiating forced handover attempt. The measurement
FIGURE 987 RECV FAILURE FROM LOWER PRI USER REQUEST RESOURCE
FOR FORCED HANDOVER (BSC-CONTROLLED INTER-CELL HANDOVER DUE
TO FORCED HANDOVER)
Unit
Times
935
failure (BSC-controlled
forced handover)
936
Definition
Number of lower PRI user handover failure (BSC-controlled intercell handover due to forced handover)
Description
This counter counts the number of receiving failure from lower priority user due to handover failure while forced handover attempt
is initiated due to unavailable radio resource in target cell in the
a MS.
Usage
This counter counts the frequency of receiving handover failure

from a lower priority user during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover process.
Measurement
Point

if receiving handover failure from a lower priority user after initiating forced handover attempt. The measurement point is A, as
FIGURE 988 RECV FAILURE FROM LOWER PRI USER REQUEST RESOURCE
FOR FORCED HANDOVER (BSC-CONTROLLED INTER-CELL HANDOVER DUE
TO FORCED HANDOVER)
Unit
Times
C901090165 Number of high

PRI user time out for wait
resource (BSC-controlled
forced handover)
Definition
Number of high PRI user time out for wait resource (BSC-controlled
inter-cell handover due to forced handover)
Description
This counter counts the number of timeout for waiting resource

while initiating forced handover due to unavailable radio resource
in target cell in the process of BSC-controlled inter-cell incoming
handover initiated by a MS.
Usage
This counter counts the frequency of timeout for waiting resource

while initiating forced handover during BSC-controlled inter-cell
incoming handover initiated by a MS. It can reflect the handover
process.
937
Measurement
Point

if timeout for waiting resource occurs after initiating forced handover. The measurement point is A, as shown in Figure 989.
FIGURE 989 - HIGH PRI USER TIME OUT FOR WAIT RESOURCE
(BSC-CONTROLLED INTER-CELL HANDOVER DUE TO FORCED HANDOVER)
Unit
Times
found (BSC-controlled
forced release)
938
Definition
Number of forced release target not found (BSC-controlled intercell handover due to forced release)
Description
This counter counts the number of forced release target not found
due to unavailable radio resource in target cell in the process of
BSC-controlled inter-cell incoming handover initiated by a MS.
Usage
This counter counts the frequency of forced release target not

found during BSC-controlled inter-cell incoming handover initiated
by a MS. It can reflect the handover process.
Measurement
Point

the forced release target is not found after initiating forced release
attempt. The measurement point is A, as shown in Figure 990.
FIGURE 990 FORCED RELEASE TARGET NOT FOUND (BSC-CONTROLLED
INTER-CELL HANDOVER DUE TO FORCED RELEASE)
Unit
Times

resource (BSC-controlled
forced release)
Definition
Number of high PRI user time out for wait resource (BSC-controlled
inter-cell handover due to forced release)
Description
This counter counts the number of timeout for waiting resource

while initiating forced release due to unavailable radio resource
in target cell in the process of BSC-controlled inter-cell incoming
handover initiated by a MS.
Usage

while initiating forced release during BSC-controlled inter-cell in-
939
coming handover initiated by a MS. It can reflect the handover

process.
Measurement
Point

timeout for waiting resource occurs after initiating forced release.
FIGURE 991 HIGH PRI USER TIME OUT FOR WAIT RESOURCE
(BSC-CONTROLLED INTER-CELL HANDOVER DUE TO FORCED RELEASE)
Unit
Times
C901090168 Number
of HO Target not found
(MSC-controlled incoming
handover)
940
Definition
Number of HO Target not found (MSC-controlled incoming handover due to forced handover)
Description
This counter counts the number of HO Target not found (MSCcontrolled incoming handover due to forced handover)
Usage
Measurement
Point
Unit
This counter counts the frequency of handover target not found

on MSC-controlled incoming handover due to forced handover. It
is one of parameters to measure radio environment.
This counter increments after BSC receives incoming handover

message and does forced handover attempt due to unavailable
resource.
This counter increments if the interval timer to search for handover target is timeout on handover.
This counter increments if waiting for handover resource and

handover attempt fails.
This counter increments if the timer of waiting for resource is

timeout after initiating forced handover.
Times
request to lower PRI user
(MSC-controlled incoming
handover)
Definition
Number of send forced handover request to lower PRI user

(MSC-controlled incoming handover due to forced handover)
Description
This counter counts the number of sending forced handover request to lower PRI user (MSC-controlled incoming handover due
to forced handover).
Usage
This counter counts the frequency of sending handover request to

a lower priority user on MSC-controlled incoming handover due to
forced handover. It is one of parameters to measure radio environment.
Measurement
Point
Unit
This counter increments after BSC receives incoming handover

message and does forced handover attempt due to unavailable
resource.
This counter increments if the interval timer to search for handover target is timeout on handover.

handover attempt fails.

Times
941
failure to lower PRI user
request resource for forced
handover (MSC-controlled
incoming handover due to
forced handover)
Definition
Number of failure to lower PRI user request resource for forced

handover (MSC-controlled incoming handover due to forced handover)
Description
This counter counts the number of failure to lower PRI user request
resource for forced handover (MSC-controlled incoming handover
due to forced handover).
Usage
This counter counts the frequency of failure request resource for

lower priority user on MSC-controlled incoming handover due to
forced handover. It is one of parameters to measure radio environment.
Measurement
Point
This counter increments if BSC receives forced handover failure

and incoming handover fails due to failure of resource request.
Unit
Times
failure (MSC-controlled
forced handover)
942
Definition
Number of lower PRI user handover failure (MSC-controlled incoming handover due to forced handover)
Description
This counter counts the number of handover failure to lower PRI

user for forced handover (MSC-controlled incoming handover due
to forced handover).
Usage
This counter counts the frequency of handover failure for lower

priority user on MSC-controlled incoming handover due to forced
handover. It is one of parameters to measure radio environment.
Measurement
Point
Unit
This counter increments if BSC receives forced handover failure

and incoming handover fails due to failure of forced handover.
Times

resource (MSC-controlled
forced handover)
Definition
Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover)
Description
This counter counts the number of high PRI user time out for wait
resource (MSC-controlled incoming handover due to forced handover).
Usage

for higher priority user on MSC-controlled incoming handover due
to forced handover. It is one of parameters to measure radio environment.
Measurement
Point
This counter increments if the timer of waiting for resource after

initiating forced handover.
Unit
Times
found (MSC-controlled
forced release)
Definition
Number of forced release target not found (MSC-controlled incoming handover due to forced release)
Description
This counter counts the number of forced release target not found
(MSC-controlled incoming handover due to forced handover).
943
Usage
Measurement
Point
Unit
This counter counts the frequency of forced release target not

found on MSC-controlled incoming handover due to forced handover. It is one of parameters to measure radio environment.
This counter increments after BSC receives incoming forced

release message and does forced release due to unavailable
resource.
This counter increments if the interval timer to search for

forced release target is timeout on handover.

forced release fails.

This counter increments if the timer to initiate forced release

is timeout on handover.

timeout after initiating forced release.
Times

resource (MSC-controlled
forced release)
Definition
Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced release)
Description
This counter counts the number of high PRI user time out for
wait resource (MSC-controlled incoming handover due to forced
release).
Usage

for higher priority user on MSC-controlled incoming handover due
to forced release. It is one of parameters to measure radio environment.
Measurement
Point
This counter increments if the timer of waiting for resource is timeout after initiating forced release.
Unit
944
Times
handover)
Definition

handover)
Description
This counter counts the number of getting previous grab released

channel (assignment forced handover).
Usage
This counter counts the frequency of getting the channel released

by grabbing on forced handover. It is one of parameters to measure radio environment.
Measurement
Point
This counter increments if BSC receives effective messages in resource message on forced handover and the messages hold database resource.
Unit
Times
release)
Definition

release)
Description
This counter counts the number of getting previous grab released

channel (assignment forced release).
Usage
This counter counts the frequency of getting the channel released

by grabbing on forced release. It is one of parameters to measure
radio environment.
Measurement
Point
This counter increments if BSC receives effective messages in resource message on forced release and the messages hold database
resource.
Unit
Times
945
Definition
Number of handover attempts due to eMLPP forced handover
Description

eMLPP forced handover.
Usage
This counter counts the frequency of handover attempts due to

eMLPP forced handover. It is one of parameters to measure radio
environment.
Measurement
Point
This counter increments if it is forced handover on intra-cell handover.

This counter increments if it is forced handover based on hierarchy
and frequency relationship on BSC-controlled inter-cell or MSCcontrolled outgoing handover.
Unit
Times
handover due to eMLPP
forced handover
Definition
Number of handover due to eMLPP forced handover
Description
This counter counts the number of handover due to eMLPP forced

handover.
Usage
This counter counts the frequency of handover due to eMLPP forced

handover. It is one of parameters to measure radio environment.
Measurement
Point
This counter increments if it is forced handover on intra-cell handover.

This counter increments if it is forced handover based on hierarchy and frequency relationship on BSC-controlled inter-cell or
MSC-controlled outgoing handover.
Unit
946
Times
Definition
Number of handover success due to eMLPP forced handover
Description
This counter counts the number of handover success due to eMLPP

forced handover.
Usage
This counter counts the frequency of handover success due to

eMLPP forced handover. It is one of parameters to measure radio environment.
Measurement
Point
This counter increments if it is intra-cell forced handover on handover success.

This counter increments if it is forced handover based on hierarchy and frequency relationship on BSC-controlled inter-cell or
MSC-controlled outgoing handover success.
Unit
Times
between PLMN
outgoing handover between
PLMN
947
between PLMN
handover attempts between
PLMN
handover request fail
between PLMN due to
unknown reason
948
between PLMN due to
unavailable ground resource
Description
This counter counts the number of failures of MSC-controlled inter-PLMN outgoing handover requests due to no available ground
resource. When MSC receives the handover request rejection message from BSC on TCH, it queries the rejection cause. If the rejection cause is CAUSE_REQ_CIC_UNAVAIL, then the counter increments.
Usage
This counter is used to find out the frequency of failure of MSC-controlled inter-PLMN outgoing handover request initiated by MS due
to no available ground resource. It also helps study the condition
of handover initiated by MSC.
Measurement
Point
When MSC receives the handover request rejection message

from BSC, it queries the rejection cause. If the rejection cause
is CAUSE_REQ_CIC_UNAVAIL, then the counter counts. The
FIGURE 992 MSC-CONTROLLED INTER-PLMN HANDOVER FLOW
Unit
Times
949
between PLMN due to
unavailable radio resource
between PLMN due to other
reasons
Description
This counter counts the number of failures of MSC-controlled inter-PLMN outgoing handover requests due to other reasons. When
MSC receives the handover request rejection message from BSC
on TCH, it queries the rejection cause. If the rejection cause
is not CAUSE_REQ_CIC_UNAVAIL or CAUSE_NO_RR_AVAIL, then
Usage
This counter is used to find out the frequency of failure of MSCcontrolled inter-PLMN outgoing handover request initiated by MS
due to other reasons. It also helps study the condition of handover
initiated by MSC.
Measurement
Point
Unit
950
When MSC receives the handover request rejection message from

BSC, it queries the rejection cause. If the rejection cause is not
CAUSE_REQ_CIC_UNAVAIL or CAUSE_NO_RR_AVAIL, then the
counter counts.
Times
handover between PLMN
Description
This counter counts the number of MSC-controlled inter-PLMN

outgoing handovers. When BSC receives the command Clear
Cmd from A-interface on TCH, if the cause in this command is
CAUSE_HO_SUCCESSFUL, then the counter increments.
Usage
This counter is used to study the MSC-controlled inter-PLMN outgoing handover initiated by MS. It also helps study the condition
of handover initiated by MSC.
Measurement
Point
1. When BSC receives the command Clear Cmd from A-interface,

if the cause in this command is CAUSE_HO_SUCCESSFUL, then
the counter counts.
2. The counter counts when BSC fails to wait for the handover
response message returned from MS. The measurement point
is shown in Figure 993.
FIGURE 993 MSC-CONTROLLED INTER-PLMN OUTGOING HANDOVER EXECUTION
3. When the timer THoOutgo is timeout, if there is no abnormal

release, the counter counts. The measurement point is shown
in Figure 994.
951
FIGURE 994 MSC-CONTROLLED INTER-PLMN OUTGOING HANDOVER EXECUTION

RELEASE
Unit
AND
NO ABNORMAL
Times
handover success between
PLMN
Description
This counter counts the number of successful MSC-controlled inter-PLMN outgoing handovers. When BSC receives the command
Clear Cmd from MSC on TCH, the timer THOOUTGO is timeout. If
the cause in the command Clear Cmd is CAUSE_HO_SUCCESSFUL,
then the counter increments.
Usage
This counter is used to find out the number of successful MSCcontrolled inter-PLMN outgoing handovers. It also helps study the
handover initiated by MSC.
Measurement
Point
Unit
952
When BSC receives the command Clear Cmd from MSC, the timer
THOOUTGO is timeout. If the cause in the command Clear Cmd is
CAUSE_HO_SUCCESSFUL, then the counter counts.
Times
incoming handover attempt
between PLMN
incoming handover between
PLMN
incoming handover
force-release attempt
between PLMN
953
PLMN due to force release
incoming handover queue
attempt between PLMN
PLMN due to queue
954
incoming handover
force-handover attempt
between PLMN
PLMN due to force handover
between PLMN
955
handover attempt between
PLMN
Description
This counter counts the number of MSC-controlled inter-PLMN

incoming handover attempts. When BSC receives the RadioApply message from MSC, it queries the cause. If AppCause is
INCOME_HO, then the counter increments.
Usage
This counter is used to find out the number of MSC-controlled inter-PLMN incoming handover attempts. It also helps study the
handover initiated by MSC.
Measurement
Point
When BSC receives the RadioApply message from MSC, it queries

the cause. If AppCause is INCOME_HO, then the counter counts.
FIGURE 995 MSC-CONTROLLED INTER-PLMN INCOMING HANDOVER FLOW
Unit
956
Times
C901090200 A interface
incoming handover fail
between PLMN due to circuit
block
Description
This counter counts the number of A-interface inter-PLMN incoming handover failures due to circuit's being blocked. When MSC receives the Handover Failure message, if the handover fails due to
CAUSE_REQ_CIC_UNAVAIL and the handover is inter-PLMN handover, then the counter increments.
Usage
This counter is used to find out the number of A-interface interPLMN incoming handover failures due to circuit's being blocked. It
also helps study the handover initiated by MSC.
Measurement
Point
When MSC receives the Handover Failure message, if the handover

failiure cause in this message is CAUSE_REQ_CIC_UNAVAIL and
the handover is inter-PLMN handover, then the counter counts.
FIGURE 996 A-INTERFACE INTER-PLMN INCOMING HANDOVER FAILURE
Unit
Times
957
between PLMN due to circuit
unmatch
Description
This counter counts the number of A-interface inter-PLMN incoming handover failures due to circuit mismatching. When MSC receives the Handover Failure message, if the handover fails due
to CAUSE_CIRCUIT_POOL_MISMATCH and the handover is interPLMN handover, then the counter increments.
Usage
This counter is used to find out the number of A-interface interPLMN incoming handover failures due to circuit mismatching. It
also helps study the handover initiated by MSC.
Measurement
Point
Unit
When MSC receives the Handover Failure message, if the handover

failiure cause in this message is CAUSE_CIRCUIT_POOL_MISMATCH and the handover is inter-PLMN handover, then the
counter counts.
Times
between PLMN due to
unavailable radio resource
Description
This counter counts the number of A-interface inter-PLMN incoming handover failures due to no available radio resource. When
MSC receives the Handover Failure message or RanA receives
the Handover Failure message, if the handover failure cause is
CAUSE_NO_RR_AVAI and the handover is inter-PLMN handover,
Usage
This counter is used to find out the number of A-interface inter-PLMN incoming handover failures due to no available radio resource. It also helps study the handover initiated by MSC.
Measurement
Point
1. When MSC receives the Handover Failure message, if the handover failiure cause in this message is CAUSE_NO_RR_AVAI
and the handover is inter-PLMN handover, then the counter
counts.
2. When RanA receives the Handover Failure message, if the handover failiure cause in this message is CAUSE_NO_RR_AVAI
958
and the handover is inter-PLMN handover, then the counter

counts.
Unit
Times
between PLMN due to other
reason
handover force-release
Description
This counter counts the number of attempts of MSC-controlled inter-PLMN incoming handover force-release. After BSC initiates the
forced release, the counter counts the number of force-release
attempts during the assignment (or handover). If the cause of
channel request is INCOME_HO and the handover is inter-PLMN
incoming handover, then the counter increments.
Usage
This counter is used to find out the number of attempts of MSCcontrolled inter-PLMN incoming handover force-release. It also
helps study the inter-PLMN incoming handover force-release initiated by MSC.
959
Measurement
Point
Unit
When BSC receives the command HoReq from MSC, if no radio resource is available and forced release is allowed, then the counter
counts.
Times
due to force release
Description
This counter counts the number of MSC-controlled inter-PLMN incoming handover due to forced release. After BSC initiates the
forced release, the counter counts the number of assignments (or
handovers) due to forced release (or queuing). If the cause of
channel request is INCOME_HO and forced release is allowed and
the handover is inter-PLMN incoming handover, then the counter
increments.
Usage
This counter is used to find out the number of MSC-controlled inter-PLMN incoming handover due to forced release. It also helps
study the inter-PLMN incoming handover initiated by MSC due to
forced release.
Measurement
Point
Unit
When BSC receives the command HoReq from MSC, if the CS instance carries the RADIO_AVAILABLE message and forced release
is allowed, then the counter counts.
Times
handover queue attempt
between PLMN
960
Description
This counter counts the number of attempts of MSC-controlled inter-PLMN incoming handover queuing. When BSC receives the
command Ho Req from MSC, it sends the command Chan Act to
BTS. If channel requests fails but queuing is allowed, the counter
increments.
Usage
This counter is used to find out the number of attempts of

MSC-controlled inter-PLMN incoming handover queuing. It also
helps study the inter-PLMN incoming handover, which is initiated

by MSC, in case of no channel resource.
Measurement
Point
When BSC receives the command Ho Req from MSC, it sends the
command Chan Act to BTS. If no channel request fails but queuing
is allowed, then the counter counts. The measurement point is
FIGURE 997 INTER-MSC HANDOVER
Unit
Times
due to queue
Description
This counter counts the number of MSC-controlled inter-PLMN incoming handover due to queuing. After BSC receives the handover command, it requests for channel resource. If the request
fails, the cause of channel request is INCOME_HO, queuing is allowed, and the handover is inter-PLMN incoming handover, then
Usage
This counter is used to find out the number of MSC-controlled inter-PLMN incoming handover due to queuing. It also helps study
the inter-PLMN incoming handover, which is initiated by MSC, in
case of no channel resource.
Measurement
Point
When BSC receives the command HoReq from MSC, if the CS instance carries the RADIO_AVAILABLE message and queuing is allowed, then the counter counts.
961
Unit
Times
handover force-handover
Description
This counter counts the number of attempts of MSC-controlled inter-PLMN incoming handover force-handover. When BSC receives
the command Ho Req from MSC, it sends the command Chan Act
to BTS. If channel requests fails but forced handover is allowed,
Usage
This counter is used to find out the number of attempts of MSCcontrolled inter-PLMN incoming handover force-handover. It also
helps study the inter-PLMN incoming handover, which is initiated
by MSC, in case of no channel resource.
Measurement
Point
Unit
When BSC receives the command Ho Req from MSC, it sends the
command Chan Act to BTS. If no channel request fails but forced
handover is allowed, then the counter counts.
Times
due to force handover
962
handover success between
PLMN
handover due to Fragment
reorganization
Description
This counter counts the number of handovers due to HR fragment

reorganization in the cell. When Rancs receives the CS service
migration sent from DBS, if byCsMoveCause == HR_DEFRAG, then
Usage
This counter is used to find out the number of handovers due to HR

fragment reorganization in the cell. It helps study the CS service
migration.
Measurement
Point
Unit
When Rancs receives the CS service migration sent from DBS, if

byCsMoveCause == HR_DEFRAG, then the counter counts.
Times
Fragment reorganization
Description
This counter counts the number of successful handovers due to

HR fragment reorganization in the cell. When BSC receives the
CS service migration command from DBS, it sends the command
Chan Act to BTS. After the command Chan Act Ack is received, if
byCsMoveCause == HR_DEFRAG, then the counter increments.
Usage
This counter is used to find out the number of successful handovers

due to HR fragment reorganization in the cell. It helps study the
CS service migration.
963
Measurement
Point
When BSC receives the CS service migration command from DBS,

it sends the command Chan Act to BTS. After the command Chan
Act Ack is received, if the assignment at Um interface succeeds
and byCsMoveCause == HR_DEFRAG, then the counter counts.
FIGURE 998 HANDOVER SUCCESS
Unit
DUE TO
CS SERVICE MIGRATION
Times
handover attempt from AMR
FR to AMR HR due to high
load
Description
964
When the cell's traffic load increases and reaches the threshold of
handover from AMR FR to AMR HR, it will trigger the process of
finding an existed AMR FR call in the cell. If the appropriate call
is found, the intra-cell handover attempt from AMR FR to AMR HR
will be initiated, and the counter increments. The measurement
FIGURE 999 INTRA-CELL HANDOVER FLOW

Unit
Statistics Object
Times
Cell
handover from AMR FR to
AMR HR due to high load
Description
handover from AMR FR to AMR HR,if the radio resource is available
and the channel activation succeeds, the counter increments. The

Unit
Times
965
Statistics Object
Cell
handover success from AMR
FR to AMR HR due to high
load
Description
handover from AMR FR to AMR HR,if the MS successfully performs
handover to the new channel and the handover completion message is sent, the counter increments. The measurement point is

Unit
Statistics Object
Times
Cell
handover attempt from FR to
HR due to high load
Description
966
handover from FR to HR, it will trigger the process of finding an existed AMR FR call or FR call in the cell. It finds the AMR FR call first,
and then finds the FR call if no appropriate AMR FR call is found.
If an appropriate FR call is found, the intra-cell handover attempt
from FR to HR will be initiated, and the counter increments. The

Unit
Statistics Object
Times
Cell
handover from FR to HR due
to high load
Description
handover from FR to HR,if the radio resource is available and the
channel activation succeeds, the counter increments. The measurement point is A2, as shown in Figure 1003.

Unit
Times
967
Statistics Object
Cell
handover success from FR
to HR due to high load
Description
handover from FR to HR,if the MS successfully performs handover
to the new channel and the handover completion message is sent,
the counter increments. The measurement point is A3, as shown
in Figure 1004.

Unit
Statistics Object
Times
Cell
handover attempt from AMR
HR to AMR FR due to bad
quality
Description
968
Suppose the voice quality of an AMR HR call is poor. If all other

handover conditions are not satisfied but the threshold of intracell handover from AMR HR to AMR FR is reached, the intra-cell
handover attempt from AMR HR to AMR FR is initiated, and the
counter increments. The measurement point is A1, as shown in
Figure 1005.

Unit
Statistics Object
Times
Cell
handover from AMR HR to
AMR FR due to bad quality
Description
When the intra-cell handover from AMR HR to AMR FR is caused

due to bad quality, if the radio resource is available and the channel
activation succeeds, the counter increments. The measurement

Unit
Times
969
Statistics Object
Cell
handover success from AMR
HR to AMR FR due to bad
quality
Description
When the intra-cell handover from AMR HR to AMR FR is caused

due to bad quality, if the MS successfully performs handover to
the new channel and the handover completion message is sent,
in Figure 1007.

Unit
Statistics Object
Times
Cell
handover attempt from HR
to FR due to bad quality
Description
970
Suppose the voice quality of an HR call is poor. If all other handover conditions are not satisfied but the threshold of intra-cell
handover from HR to FR is reached, the intra-cell handover attempt from HR to FR is initiated, and the counter increments. The

Unit
Statistics Object
Times
Cell
handover from HR to FR due
to bad quality
Description
When the intra-cell handover from HR to FR is caused due to bad

quality, if the radio resource is available and the channel activation
succeeds, the counter increments. The measurement point is A2,

Unit
Times
971
Statistics Object
Cell
handover success from HR
to FR due to bad quality
Description
When the intra-cell handover from HR to FR is caused due to bad

quality, if the MS successfully performs handover to the new channel and the handover completion message is sent, the counter increments. The measurement point is A3, as shown in Figure 1010.

Unit
Statistics Object
Times
Cell
outgoing handover attempts,
Description
972
During the process of intra-BSC inter-cell handover, after BSC receives the measurement report from MS, it performs handover decision. If it decides intra-BSC inter-cell handover is required and
if the source cell's frequency band is 900 MHz and the destination
cell's frequency band is 900 MHz, the counter increments. The
FIGURE 1011 INTRA-BSC INTER-CELL HANDOVER FLOW

Unit
Statistics Object
Times
Cell
outgoing handover, from
GSM900 to GSM900
Description
During the process of intra-BSC inter-cell handover, after BSC successfully activates channel for BTS in the destination cell, it sends
the HANDOVER COMMAND message to MS in the source cell. If
the source cell's frequency band is 900 MHz and the destination
973

Unit
Statistics Object
Times
Cell
outgoing handover success,
Description
974
During the process of intra-BSC inter-cell handover, after BSC

sends the HANDOVER COMMAND message to MS in the source
cell, MS successfully accesses the destination channel, and BSC
receives the HANDOVER COMPLETE message from the destination
cell. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 900 MHz, the counter increments.

Unit
Statistics Object
Times
Cell
Description
During the process of intra-BSC inter-cell handover, after BSC receives the measurement report from MS, it performs handover decision. If it decides intra-BSC inter-cell handover is required and if
975

Unit
Statistics Object
Times
Cell
GSM1800 to GSM1800
Description
976

Unit
Statistics Object
Times
Cell
Description

cell. If the source cell's frequency band is 1800 MHz and the
destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A3, as shown in Figure 1016.
977

Unit
Statistics Object
Times
Cell
Description
978
During the process of intra-BSC inter-cell handover, after BSC receives the measurement report from MS, it performs handover decision. If it decides intra-BSC inter-cell handover is required and
if the source cell's frequency band is 900 MHz and the destination

Unit
Statistics Object
Times
Cell
GSM900 to GSM1800
Description
979

Unit
Statistics Object
Times
Cell
Description
980


Unit
Statistics Object
Times
Cell
Description
During the process of intra-BSC inter-cell handover, after BSC receives the measurement report from MS, it performs handover decision. If it decides intra-BSC inter-cell handover is required and if
981

Unit
Statistics Object
Times
Cell
GSM1800 to GSM900
Description
982

Unit
Statistics Object
Times
Cell
Description

983

Unit
Statistics Object
Times
Cell
Description
984
During the process of inter-BSC inter-cell handover, the source

BSC sends the HANDOVER REQUIRED message to MSC. If the
source cell's frequency band is 900 MHz and the destination cell's
frequency band is 900 MHz, the counter increments. The measurement point is A4, as shown in Figure 1023.
FIGURE 1023 INTER-BSC INTER-CELL HANDOVER FLOW

Unit
Statistics Object
Times
Cell
GSM900 to GSM900
Description

BSC receives the HANDOVER COMMAND message from MSC. If
985

Unit
Statistics Object
Times
Cell
Description
During the process of inter-BSC inter-cell handover, MS successfully performs handover to the destination BSC, and the source
BSC receives the CLEAR COMMAND message from MSC and the
cause is handover success. If the source cell's frequency band is
900 MHz and the destination cell's frequency band is 900 MHz, the
Figure 1025.

Unit
986
Times
Statistics Object
Cell
Description


Unit
Times
987
Statistics Object
Cell
GSM1800 to GSM1800
Description


Unit
988
Times
Statistics Object
Cell
Description
1800 MHz and the destination cell's frequency band is 1800 MHz,
in Figure 1028.

Unit
Times
989
Statistics Object
Cell
Description


Unit
Statistics Object
Times
Cell
GSM900 to GSM1800
Description
990


Unit
Statistics Object
Times
Cell
Description
in Figure 1031.
991

Unit
Statistics Object
Times
Cell
Description

992
Unit
Statistics Object
Times
Cell
GSM1800 to GSM900
Description


Unit
Times
993
Statistics Object
Cell
Description
in Figure 1034.

Unit
Statistics Object
994
Times
Cell
Chapter
16
Adjacent Cell Handover

Measurement
Table of Contents
Overview........................................................................ 996
C901100001 Number of handover attempts on the adjacent
cell. ............................................................................... 996
C901100002 Number of handover success from selected cell
to the adjacent cell. ......................................................... 997
C901100003 Number of handover attempts from adjacent cell
to the selected cell. ......................................................... 998
C901100004 Number of handover success from adjacent cell
to the selected cell. ....................................................... 1000
C901100005 Number of handover attempts from selected cell
to the adjacent cell due to better UL quality. ..................... 1001
to the adjacent cell due to better DL quality. ..................... 1002
to the adjacent cell due to better UL quality. ..................... 1003
to the adjacent cell due to better DL quality. ..................... 1005
to the adjacent cell due to better UL strength. ................... 1006
to the adjacent cell due to better DL strength.................... 1007
to the adjacent cell due to better UL strength. ................... 1009
to the adjacent cell due to better DL strength.................... 1010
to the adjacent cell due to PBGT ...................................... 1011
to the adjacent cell due to other factors............................ 1014
C901100016 Number of successful handover from selected
cell to the adjacent cell due to other factors. ..................... 1015
C901100017 Number of pingpong handover (handover to
source cell)................................................................... 1017
C901100018 The max of RTD.......................................... 1018
C901100019 The sum of RTD .......................................... 1019
C901100020 The number of RTD ..................................... 1020
to the adjacent cell due to DL quality rapid drop ................ 1020
to the adjacent cell due to DL quality rapid drop ................ 1022
995
Overview
Adjacent cell handover counter is used to record the number of
outgoing handover or incoming handover so as to find out the
handover between the cell and its adjacent cell which lays a basis
for configuration of adjacent cell and improves service quality of
the cell through handover.
handover attempts on the
adjacent cell.
Definition
Number of handover attempts on the adjacent cell.
Description
This counter counts the number of attempts of handover from the

selected cell to the adjacent cell.
Usage
This counter is used to find out the number of attempts of handover from the selected cell to the adjacent cell so as to know the
handover situation.
Measurement
Point
When handover happens between cells inside one BSC, and

source cell sends radio channel request message to target cell,
in Figure 1035.
ATTEMPT
996
When external handover happens inside one MSC, and source

cell sends handover request message to MSC, the counter increments. The measurement point is A, as shown in Figure
1036.
Chapter 16 Adjacent Cell Handover Measurement
Unit
Related Features
Times
handover success from
selected cell to the adjacent
cell.
Definition
This counter counts the number of success of handover from the

selected cell to the adjacent cell.
Usage
This counter is used to find out the number of success of handover

from the selected cell to the adjacent cell so as to know the handover situation.
Measurement
Point

source cell receives handover completion message from target
cell, the counter increments. The measurement point is A, as
997

HANDOVER
When external handover happens inside one MSC, source cell

receives release command from MSC and the release is due to
handover success, the counter increments. The measurement
Unit
Related Features
Times
handover attempts from
adjacent cell to the selected
cell.
Definition
998
Number of handover attempts from adjacent cell to the selected

cell.
Usage
Measurement
Point
This counter is used to find out the number of attempts of handover from adjacent cell to the selected cell so as to know the
handover situation.
When handover happens between cells inside one BSC, target

cell receives radio channel request message from source cell,
in Figure 1039.
ATTEMPTS
When external handover happens inside one MSC, and target

cell receives handover request message from MSC, the counter
1040.
Unit
Related Features
Times
999
cell.
Definition
This counter counts the number of successful handover from the

adjacent cell to the selected cell.
Usage
This counter is used to find out the number of success of handover

from the adjacent cell to the selected cell due to better quality so
as to know the handover situation.
Measurement
Point

target cell receives handover completion message from MS, the
Figure 1041.
HANDOVER
When external handover happens inside one MSC, and target cell receives handover completion message from MS, the
Figure 1042.
Unit
Related Features
1000
Times
cell due to better UL quality.
Definition
Number of handover attempts from selected cell to the adjacent

cell due to better UL quality
Usage
This counter is used to find out the number of attempts of handover from a selected cell to the adjacent cell so as to know the
handover situation.
Measurement
Point

target cell receives radio channel request message from source
cell due to better UL quality, the counter increments. The measurement point is A, as shown inFigure 1043.
ATTEMPTS
When external handover happens inside one MSC, target cell

receives handover request message from MSC due to better
UL quality, the counter increments. The measurement point is
1001
Unit
Related Features
Times
cell due to better DL quality.
Definition

cell due to better DL quality
Usage
This counter is used to find out the number of attempts of handover from selected cell to the adjacent cell so as to know the
handover situation.
Measurement
Point
1002

cell due to better DL quality, the counter increments. The measurement point is A, as shown in Figure 1045.

ATTEMPTS

cell receives handover request message from MSC due to better DL quality, the counter increments. The measurement point
Unit
Related Features
Times
cell due to better UL quality.
Definition
Number of successful handover from the selected cell to the adjacent cell due to better UL quality.
1003
Usage
Measurement
Point
This counter is used to find out the number of successful handover

from a selected cell to the adjacent cell due to better UL quality so

source cell receives handover completion message from target cell due to better UL quality, the counter increments. The
HANDOVER

cell receives release command from MSC due to better UL quality, the counter increments. The measurement point is A, as
Unit
Related Features
1004
Times
cell due to better DL quality.
Definition
Number of handover success from selected cell to the adjacent cell

due to better DL quality
Usage

from a selected cell to the adjacent cell due to better DL quality so
Measurement
Point

source cell receives handover completion message from target cell due to better DL quality, the counter increments. The
HANDOVER
When external handover happens inside one MSC, source cell

receives release command from MSC due to better DL quality,
in Figure 1050.
1005
Unit
Related Features
Times
cell due to better UL strength.
Definition

Usage
This counter is used to find out the number of attempts of handover from a selected cell to the adjacent cell due to better UL
strength so as to know the handover situation.
Measurement
Point
1006

cell due to better UL strength, the counter increments. The

ATTEMPTS

cell receives handover request message from MSC due to better UL strength, the counter increments. The measurement
point is A, as shown in Figure 1052
Unit
Related Features
Times
cell due to better DL strength.
Definition

1007
Usage
Measurement
Point
This counter is used to find out the number of attempts of handover from a selected cell to the adjacent cell due to better DL
strength so as to know the handover situation.

cell due to better DL strength, the counter increments. The
ATTEMPTS

cell receives handover request message from MSC due to better DL strength, the counter increments. The measurement
Unit
Related Features
1008
Times
Definition
Number of successful handover from selected cell to the adjacent

cell due to better UL strength
Usage

from a selected cell to the adjacent cell due to better UL strength
so as to know the handover situation.
Measurement
Point

cell due to better UL strength, the counter increments. The
HANDOVER

cell receives release command from MSC due to better UL
strength, the counter increments. The measurement point is
1009
Unit
Related Features
Times
Definition
Number of successful handover from the selected cell to the adjacent cell due to better DL strength
Usage

from a selected cell to the adjacent cell due to better DL strength
Measurement
Point
1010

cell due to better DL strength, the counter increments. The

HANDOVER

cell receives release command from MSC due to better UL
strength, the counter increments, as shown in Figure 1058.
Unit
Related Features
Times
cell due to PBGT
Definition
Number of handover attempts from the selected cell to the adjacent cell due to better PBGT
1011
Usage
Measurement
Point
This counter is used to find out the number of attempts of handover from a selected cell to the adjacent cell due to PBGT, so as
to know the handover situation.

cell due to better PBGT, the counter increments. The measurement point is A, as shown inFigure 1059.
ATTEMPTS

cell receives handover request message from MSC due to better PBGT, the counter increments. The measurement point is
Unit
Related Features
1012
Times
cell due to PBGT
Definition
Number of handover success from selected cell to the adjacent cell

due to better PBGT
Usage
This counter is used to find out the number of handover success

from a selected cell to the adjacent cell due to better PBGT, so as
Measurement
Point

cell due to better PBGT, the counter increments. The measurement point is A, as shown in Figure 1061.
HANDOVER

cell receives release command from MSC due to better PBGT,
in Figure 1062.
1013
Unit
Related Features
Times
cell due to other factors.
Definition
Number of handover attempts from the selected cell to the adjacent cell due to other factors.
Usage
This counter is used to find out the number of attempts of handover from a selected cell to the adjacent cell due to other factors,
Measurement
Point
1014

cell due to other factors, the counter increments, as shown in
Figure 1063.

ATTEMPTS

cell receives handover request message from MSC due to other
factors, the counter increments, as shown in Figure 1064.
Unit
Times
successful handover from
cell due to other factors.
Definition
Number of successful handover from the selected cell to the adjacent cell due to other factors
1015
Usage
Measurement
Point
This counter is used to find out the number of handover success

from a selected cell to the adjacent cell due to other factors, so as

cell due to other factors, the counter increments, as shown in
Figure 1065.
HANDOVER

cell receives release command from MSC due to other factors,
the counter increments, as shown in Figure 1066.
Unit
1016
Times
C901100017 Number
of pingpong handover
(handover to source cell)
Definition
Number of pingpong handover (handover to source cell)
Description
MS performs handover from cell 1 to cell 2, this counter counts

the number of MS's attempting handover back from cell 2 to cell
1 within specified time.
Usage
This counter is used to find out the number of MS's attempting

pingpong handover due to network coverage problems or inappropriate parameter setting.
Measurement
Point
For BSC-controlled inter-cell handover, the counter increments

when the source cell sends the radio channel request message
to the destination cell. The measurement point is A, as shown
in Figure 1067.
ATTEMPT
For MSC-controlled external handover, the counter increments

when the souce cell sends the handover request message to
MSC. The measurement point is A, as shown in Figure 1068.
1017
Unit
Times
C901100018 The max of

RTD
Description
This counter counts the maximum reference time difference between two cells. When BSC receives the Assign Complete message
from MS, if it contains the mobile time difference and dwRTDMa
is smaller than the temporary variable dwRTD, then update dwRTDMa.
Usage
This counter is used to find out the maximum reference time difference between two cells.
Measurement
Point
1018
When BSC receives the Assign Complete message, if it contains

the mobile time difference, then the counter counts. The measurement point is A1, as shown in Figure 1069.
FIGURE 1069 HANDOVER FLOW
Unit
Second
C901100019 The sum of

RTD
Description
This counter counts the sum of sampled reference time differences

between two cells. When BSC receives the Assign Complete message from MS, if it contains the mobile time difference, then update
dwRTDSum.
Usage
This counter is used to find out the sum of sampled reference time
differences between two cells.
Measurement
Point
Unit
When BSC receives the Assign Complete message from MS, if it

contains the mobile time difference, then the counter counts.
Times
1019
C901100020 The number of

RTD
Description
This counter counts the number of sampled reference time differences between two cells. When BSC receives the Assign Complete
message from MS, if it contains the mobile time difference, then
Usage
This counter is used to find out the number of sampled reference

time differences between two cells.
Measurement
Point
Unit
When BSC receives the Assign Complete message from MS, if it

contains the mobile time difference, then the counter counts.
Times
cell due to DL quality rapid
drop
Description
This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to fast fading of
downlink quality.
This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell. It helps check
the direction of handover between cells.
1020

when the source cell sends the radio channel request message
to the destination cell. The measurement point is A, as shown
in Figure 1070.
For MSC-controlled external handover, the counter increments

when the source cell sends the handover request message to
MSC. The measurement point is A, as shown in Figure 1071.

ATTEMPT
FIGURE 1071 MSC-CONTROLLED INTER-CELL OUTGOING HANDOVER

ATTEMPT

Unit
Times
1021
Statistics Object
Cell
cell due to DL quality rapid
drop
Description
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to fast fading of
downlink quality.
This counter is used to find out the number of MS's successful
outgoing handovers from the local cell to a specific cell. It helps
check the direction of handover between cells.
1022

when the source cell receives the handover completion message from the destination cell. The measurement point is A,
For MSC-controlled external handover, when the source cell

receives the release command issued by MSC and if the release
is due to handover success, then the counter increments. The
FIGURE 1072 NUMBER

SUCCESSES
OF
BSC-CONTROLLED OUTGOING HANDOVER
FIGURE 1073 NUMBER

SUCCESSES
OF
MSC-CONTROLLED OUTGOING HANDOVER

Unit
Statistics Object
Times
Cell
1023
1024
Chapter
17
Radio Access
Measurement
Table of Contents
Overview...................................................................... 1026
C901110001 Number of invalid access requests................. 1027
C901110003 Number of MOC access success for processes.......................................................................... 1027
C901110006 Number of MTC access success for processes.......................................................................... 1028
C901110008 Number of call re-establishment access attempts ......................................................................... 1028
C901110009 Number of call re-establishment access success
for processes ................................................................ 1029
C901110010 Number of call re-establishment access success............................................................................. 1029
C901110011 Number of emergency calls access attempts ......................................................................... 1030
C901110012 Number of emergency calls access success for
processes ..................................................................... 1030
C901110013 Number of emergency calls access success............................................................................. 1031
C901110014 Number of LOC access attempts ................... 1031
C901110015 Number of LOC access success for processes.......................................................................... 1031
C901110016 Number of LOC access success ..................... 1032
C901110017 Number of other causes access attempts......... 1032
C901110018 Number of successful random access processes
for other causes ............................................................ 1033
C901110019 Number of other causes access success ......... 1033
C901110020 Number of LMU Establishment Access attempts ......................................................................... 1034
C901110021 Number of LMU Establishment access success
for processes ................................................................ 1034
C901110022 Number of LMU Establishment access success............................................................................. 1035
C901110023 Number of accesses due to location update ............................................................................ 1035
C901110024 Number of Access due to CM SERVICE
REQ............................................................................. 1035
C901110026 Number of CM service requests of Emergency
Call ............................................................................. 1036
C901110027 Number of CM service requests of SMS .......... 1036
C901110028 Number of CM service requests of Supplement ........................................................................... 1037
C901110029 Number of CM service requests of LCS........... 1037
1025
C901110031 Number of wireless access due to call re-establishments ..................................................................... 1037

C901110032 Number of wireless accesses due to IMSI detachment ..................................................................... 1038
C901110033 Number of wireless accesses due to other
causes ......................................................................... 1038
C901110034 Number of access due to Notification response ......................................................................... 1039
C901110035 Number of access due to Immediate
setup ........................................................................... 1040
C901110036 Number of access due to Talker indication ............................................................................. 1041
C901110037 Number of access due to DATA Indication......... 1042
C901110038 Number of access due to priority uplink request ........................................................................... 1043
VGCS........................................................................... 1044
VBS ............................................................................. 1045
Overview
Radio access counter is mainly used to observe MS radio random
access process as the reference of radio access parameter adjustment, signaling channel allocation strategy, etc. Several possible
causes of radio access are listed here. Access statistics related to
GPRS is not listed here but in the category of other access request
temporarily.
The number of access request is that of receiving Channel Required
message; the number of successful access process is that of sending Immediate Assignment message.
The slot-aloha protocol used in radio access allows many access
requests in one access. We can use the percentage of the number of successful access process to the number of access request
to describe access success rate. This value represents signaling
channel congestion extent. The percentage of the number of successful access to the number of access request represents the collision status in radio access request. If this value is low, we shall
consider factors such as the interval between access requests, and
check whether it is reasonable.
Radio access flow and related counters locations are shown in
Figure 1074.
1026
Chapter 17 Radio Access Measurement
FIGURE 1074 RADIO ACCESS PROCESS
invalid access requests
Definition
Number of invalid access requests
Description
This counter counts the number of invalid access requests. The

counter increments when MS sends CHL_REQ message through BTS
to BSC for requiring radio channel and TA exceeds cell scope, and
then BSC regards the access request as interference and abandons
the request.
Usage
This counter is used to find out the frequency of invalid access

request.
Measurement
Point
The counter increments when MS fails in requiring radio channel

from BSC because TA exceeds cell scope. The measurement point
is A2, as shown in Figure Radio Access Process .
Unit
Times
MOC access success for
processes
Definition
Number of MOC access success for processes
1027
Description
This counter counts the Number of MOC access success for processes. The counter increments when BSC allows MS to be accessed into the network due to MOC attempts and accepts channel
request sent by MS and allocates and activates channel successfully. Meanwhile, BSC sends message IMM_ASS to MS.
Usage
This counter is used to find out the frequency of successful random

access processes due to MOC attempts.
Measurement
Point
The counter increments when channel is activated successfully.

The measurement point is A3, as shown in Figure Radio Access
Process .
Unit
Times
MTC access success for
processes
Definition
Number of MTC access success for processes
Description
This counter counts the Number of MTC access success for processes. The counter increments when BSC allows MS to be accessed into the network due to MTC attempts and accepts channel
request sent by MS and allocates and activates channel successfully. Meanwhile, BSC sends IMM_ASS message to MS.
Usage
This counter is used to find out the frequency of successful random

access processes due to MTC attempts.
Measurement
Point

Process.
Unit
Times
C901110008 Number of call

re-establishment access
attempts
Definition
1028
Number of call re-establishment access attempts
Description
This counter counts the Number of call re-establishment access attempts. The counter increments when MS sends CHL_REQ message
through BTS to BSC for requiring radio channel, if TA does not exceed cell scope and the access cause is call re-establishment.
Usage
This counter is used to find out the frequency of random access

attempts due to call re-establishment.
Measurement
Point
Unit
The counter increments when MS requires channel from BSC and

TA does not exceed the scope. The measurement point is A1, as
shown in Figure Radio Access Process.
Times

success for processes
Definition
Number of call re-establishment access success for processes
Description
This counter counts the Number of call re-establishment access

success for processes. The counter increments when BSC allows
MS to be accessed into the network due to call re-establishment
and accepts channel request sent by MS and allocates and activates channel successfully. Meanwhile, BSC sends IMM_ASS message to MS.
Usage

processes due to call re-establishment.
Measurement
Point

Process.
Unit
Times

success
Definition
Number of call re-establishment access success.
Description
This counter counts the Number of call re-establishment access

success. The counter increments when MS receives IMM_ASS message sent by BSC and successfully accesses corresponding channel
and BSC receives EST_IND message sent by MS.
Usage
This counter is used to find out the frequency of successful access

of call re-establishment.
Measurement
Point
The counter increments when BSC receives EST_IND message. The

measurement point is A4, as shown in Figure Radio Access Process.
Unit
Times
1029
emergency calls access
attempts
Definition
Number of emergency calls access attempts
Description
This counter counts the Number of emergency calls access attempts. The counter increments when MS sends CHL_REQ message
through BTS to BSC for requiring radio channel, if TA does not exceed cell scope and the access cause is emergency calls.
Usage

attempts due to emergency calls.
Measurement
Point

Unit
Related Features
Times
ZGB-01-03-001 Emergency Call Handling
Definition
Description
This counter counts the Number of emergency calls access success

for processes. The counter increments when BSC allows MS to
be accessed into the network due to emergency calls and accepts
channel request sent by MS and allocates and activates channel
successfully. Meanwhile, BSC sends IMM_ASS message to MS.
Usage

processes due to emergency calls.
Measurement
Point

Process.
Unit
Related Features
1030
Number of emergency calls access success for processes
Times
success
Definition
Number of emergency calls access success
Description
This counter counts the Number of emergency calls access success. The counter increments when MS receives IMM_ASS message
sent by BSC and successfully accesses corresponding channel and
BSC receives EST_IND message sent by MS.
Usage
This counter is used to find out the frequency of successful access

of emergency calls.
Measurement
Point

Unit
Related Features
Times
LOC access attempts
Definition
Number of LOC access attempts
Description
This counter counts the Number of LOC access attempts. The

counter increments when MS sends CHL_REQ message through BTS
to BSC for requiring radio channel, if TA does not exceed cell scope
and the access cause is LOC.
Usage

attempts due to LOC.
Measurement
Point

Unit
Times
LOC access success for
processes
Definition
Number of LOC access success for processes
1031
Description
This counter counts the number of successful random access processes due to LOC. The counter increments when BSC allows MS to
be accessed into the network due to emergency calls and accepts
channel request sent by MS and allocates and activates channel
successfully. Meanwhile, BSC sends IMM_ASS message to MS.
Usage

processes due to LOC.
Measurement
Point

Process.
Unit
Times
LOC access success
Definition
Number of LOC access success
Description
This counter counts the number of access success. The counter increments when MS receives IMM_ASS message sent by BSC and successfully accesses corresponding channel and BSC receives EST_IND
message sent by MS.
Usage
This counter is used to find out the frequency of LOC access success.
Measurement
Point

Unit
Times
C901110017 Number
of other causes access
attempts
Definition
1032
Number of other causes access attempts
Description
This counter counts the Number of other causes access attempts

(except MOC, MTC, call re-establishment, LOC and emergency
calls). The counter increments when MS sends CHL_REQ message
through BTS to BSC for requiring radio channel, if TA does not
exceed cell scope and the access cause is other causes.
Usage

attempts due to other causes.
Measurement
Point

Unit
Times
successful random access
processes for other causes
Definition
Number of successful random access processes for other causes
Description
This counter counts the number of successful random access processes for other causes. The counter increments when BSC allows MS to be accessed into the network due to other causes and
accepts channel request sent by MS and allocates and activates
channel successfully. Meanwhile, BSC sends IMM_ASS message to
MS.
Usage

processes due to other causes.
Measurement
Point

Process.
Unit
Times
C901110019 Number
of other causes access
success
Definition
Number of other causes access success
Description
This counter counts the Number of other causes access success.

The counter increments when MS receives IMM_ASS message sent
by BSC and successfully accesses corresponding channel and BSC
receives EST_IND message sent by MS.
Usage
This counter is used to find out the frequency of other successful

access requests.
Measurement
Point

Unit
Times
1033
LMU Establishment Access
attempts
Definition
Number of LMU Establishment Access attempts
Description
This counter counts the Number of LMU Establishment Access attempts. The counter increments when MS sends CHL_REQ message
through BTS to BSC for requiring radio channel, if TA does not exceed cell scope and the access cause is LMU establishment.
Usage
This counter is used to find out the frequency of LMU establishment

access request.
Measurement
Point

Unit
Times
LMU Establishment access
Definition
Description
This counter counts the Number of LMU Establishment access success for processes. The counter increments when MS sends CHL_REQ
message through BTS to BSC for requiring radio channel, if TA does
not exceed cell scope and the access cause is LMU establishment.
Usage

access request successfully.
Measurement
Point

Process.
Unit
1034
Number of LMU Establishment access success for processes
Times
LMU Establishment access
success
Definition
Number of LMU Establishment access success
Description
This counter counts the Number of LMU Establishment access success. The counter increments when MS sends CHL_REQ message
through BTS to BSC for requiring radio channel, if TA does not exceed cell scope and the access cause is LMU establishment.
Usage

access successfully.
Measurement
Point

Unit
Times
accesses due to location
update
Definition
Number of wireless accesses due to location update
Description
This counter counts the Number of wireless accesses due to location update. The counter increments when the access cause in
Layer3 information carried in EST_IND message received by BSC is
location update.
Usage
This counter is used to find out the frequency of radio channel

accesses due to location update.
Measurement
Point

Unit
Times
Access due to CM SERVICE
REQ
Definition
Number of Access due to CM SERVICE REQ
1035
Description
This counter counts the Number of Access due to CM SERVICE REQ.

The counter increments when the access cause in Layer3 information carried in EST_IND message received by BSC is CM SERVICE
REQ.
Usage
This counter is used to find out the frequency of access caused by

CM SERVICE REQ.
Measurement
Point

Unit
Times
CM service requests of
Emergency Call
Definition
Number of access of CM SERVICE REQ's emergency call
Description
This counter counts the number of access of CM SERVICE REQ's

emergency call. The counter increments when it is emergency
call and the access cause in Layer3 information carried in EST_IND
message received by BSC is CM SERVICE REQ.
Usage
This counter is used to find out the frequency of access of CM

SERVICE REQ's emergency call.
Measurement
Point

Unit
Related Features
Times
service requests of SMS
Definition
Description
This counter counts the number of access of SMS's CM SERVICE

REQ. The counter increments when it is SMS access among other
accesses and the access cause in Layer3 information carried in
EST_IND message received by BSC is CM SERVICE REQ.
Usage
This counter is used to find out the frequency of access of SMS's

CM SERVICE REQ.
Measurement
Point

Unit
1036
Number of access of SMS's CM SERVICE REQ
Times
CM service requests of
Supplement
Definition
Number of access of supplement's CM SERVICE REQ
Description
This counter counts the number of access of supplement's CM SERVICE REQ. The counter increments when it is supplement access
among other accesses and the access cause in Layer3 information
carried in EST_IND message received by BSC is CM SERVICE REQ.
Usage
This counter is used to find out the frequency of access of supplement's CM SERVICE REQ.
Measurement
Point

Unit
Times
service requests of LCS
Definition
Number of access of LCS's CM SERVICE REQ
Description
This counter counts the number of access of supplement's CM SERVICE REQ. The counter increments when it is LCS access among
other accesses and the access cause in Layer3 information carried
in EST_IND. message received by BSC is CM SERVICE REQ.
Usage
This counter is used to find out the frequency of access of LCS's

CM SERVICE REQ.
Measurement
Point

Unit
Times
wireless access due to call
re-establishments
Definition
Description
Number of wireless accesses due to call re-establishments

This counter counts the Number of wireless accesses due to call
re-establishments. The counter increments when the access cause
1037
in Layer3 information carried in EST_IND message received by BSC

is call re-establishments.
Usage

accesses due to call re-establishments.
Measurement
Point

Unit
Times
wireless accesses due to
IMSI detachment
Definition
Number of wireless accesses due to IMSI detachment
Description
This counter counts the Number of wireless accesses due to IMSI

detachment. The counter increments when the access cause in
Layer3 information carried in EST_IND message received by BSC is
IMSI detachment.
Usage

accesses due to IMSI detachment.
Measurement
Point

Unit
Times
wireless accesses due to
other causes
Definition
Description
This counter counts the Number of wireless accesses due to

other causes (except location update, call establishment, paging
response, call re-establishment and IMSI detachment).
The
counter increments when the access cause in Layer3 information
carried in EST_IND message received by BSC is other causes.
Usage

accesses due to other causes.
Measurement
Point

Unit
1038
Number of wireless accesses due to other causes
Times
access due to Notification
response
Description
This counter counts the number of accesses due to notification response in the group call service. After BSC receives the EST_IND
message, if the layer-3 information carried in this message indicates that the access is due to MS's response to notification, then
in Figure 1075.

Unit
Times
1039
Statistics Object
Cell
access due to Immediate
setup
Description
This counter counts the number of accesses due to immediate

setup in the group call service. After BSC receives the EST_IND
message, if the layer-3 information carried in this message indicates that the access is due to immediate setup, then the counter
1076.

Unit
1040
Times
Statistics Object
Cell
C901110036 Number
of access due to Talker
indication
Description
This counter counts the number of accesses due to Talker indication in the group call service. After BSC receives the EST_IND
message, if the layer-3 information carried in this message indicates that the access is due to Talker indication, then the counter
1077.

Unit
Times
1041
Statistics Object
Cell
C901110037 Number
of access due to DATA
Indication
Description
This counter counts the number of accesses due to DATA indication in the group call service. After BSC receives the EST_IND
message, if the layer-3 information carried in this message indicates that the access is due to DATA indication, then the counter
1078.

Unit
1042
Times
Statistics Object
Cell
access due to priority uplink
request
Description
This counter counts the number of accesses due to priority uplink

request in the group call service. After BSC receives the EST_IND
message, if the layer-3 information carried in this message indicates that the access is due to priority uplink request, then the
Figure 1079.

Unit
Times
1043
Statistics Object
Cell
access of CM service
request of VGCS
Description
This counter counts the number of accesses of CM service request

of VGCS. After BSC receives the EST_IND message, if the layer-3
information carried in this message indicates that the access is
due to CM service request and the service type is VGCS, then the
Figure 1080.

Unit
1044
Times
Statistics Object
Cell
access of CM service
request of VBS
Description
This counter counts the number of accesses of CM service request

of VBS. After BSC receives the EST_IND message, if the layer-3
information carried in this message indicates that the access is
due to CM service request and the service type is VBS, then the
Figure 1081.

Unit
Statistics Object
Times
Cell
1045
1046
Chapter
18
Radio Measurement
Table of Contents
Overview...................................................................... 1050
C901120001 Number of UL signal quality samples in wireless
channels ...................................................................... 1051
C901120002 Level of worst UL signal quality in wireless channels ............................................................................. 1051
C901120003 Total value of UL quality level values in wireless
channels ...................................................................... 1052
C901120004 Number of DL signal quality samples in wireless
channels ...................................................................... 1052
C901120005 Level of worst DL signal quality in wireless channels ............................................................................. 1052
C901120006 Total value of DL quality strength values in wireless channels ................................................................ 1053
C901120007 Number of received UL signal strength samples
in wireless channels ....................................................... 1053
C901120008 Maximum received UL signal strength in wireless
channels ...................................................................... 1054
C901120009 Minimum received UL signal strength in wireless
channels ...................................................................... 1054
C901120010 Total value of UL signal strength in wireless
channels ...................................................................... 1055
C901120011 Number of received DL signal strength samples
in wireless channels ....................................................... 1055
C901120012 Maximum received DL signal strength in wireless
channels ...................................................................... 1055
C901120013 Minimum DL received signal strength in radio
channels ...................................................................... 1056
C901120014 Total value of DL signal strength in wireless
channels ...................................................................... 1056
C901120015 Number of TA samples in wireless channels ............................................................................. 1057
C901120016 Maximum TA in wireless channels.................. 1057
C901120017 Total number of TAs in wireless channels......... 1058
C901120018 Mean number of idle TCH/Fs with interference
band 0 ......................................................................... 1058
C901120024 Mean number of idle TCH/Hs with interference
band 0 ......................................................................... 1058
C901120030 Mean number of idle SDCCHs with interference
band 0 ......................................................................... 1059
band 1 ......................................................................... 1059
band 2 ......................................................................... 1060
band 3 ......................................................................... 1060
1047

band 4 ......................................................................... 1060
band 5 ......................................................................... 1061
C901120052 Number of TFO initiations............................. 1061
C901120053 Number of using noise suppression ............... 1061
TFO ............................................................................. 1062
TFO ............................................................................. 1062
C901120056 Number of active collection changes for establishing TFO ................................................................... 1062
C901120057 Number of active collection changes for optimizing TFO ........................................................................ 1063
C901120058 Number of samples with voice quality is excellent ............................................................................. 1063
good............................................................................ 1063
medium ....................................................................... 1064
bad ............................................................................. 1064
C901120062 Number of samples with voice quality is awfully............................................................................. 1065
C901120063 Number of uplink error frame on FR_V1 ......... 1065
C901120064 Total Number of uplink frame on FR_V1 ......... 1065
C901120069 Number of uplink error frame on HR_V1......... 1067
C901120070 Total Number of uplink frame on HR_V1 ......... 1067
channels on SDCCH ....................................................... 1068
C901120074 Level of worst UL signal quality in radio channels
on SDCCH .................................................................... 1068
C901120077 Level of worst DL signal quality in radio channels
on SDCCH .................................................................... 1070
C901120078 Total value of DL quality strength values in radio
in radio channels on SDCCH ............................................ 1071
C901120080 Maximum received UL signal strength in radio
C901120081 Minimum received UL signal strength in radio
C901120082 Total value of UL signal strength in radio channels on SDCCH.............................................................. 1072
in radio channels on SDCCH ............................................ 1073
C901120084 Maximum received DL signal strength in radio
1048
Chapter 18 Radio Measurement
C901120086 Total value of DL signal strength in radio channels on SDCCH.............................................................. 1074

channels on TCH ........................................................... 1075
C901120088 Level of worst UL signal quality in radio channels
on TCH......................................................................... 1075
channels on TCH ........................................................... 1076
channels on TCH ........................................................... 1076
C901120091 Level of worst DL signal quality in radio channels
on TCH......................................................................... 1076
C901120092 Total value of DL quality strength values in radio
channels on TCH ........................................................... 1077
in radio channels on TCH ................................................ 1077
C901120094 Maximum received UL signal strength in radio
channels on TCH ........................................................... 1078
C901120095 Minimum received UL signal strength in radio
channels on TCH ........................................................... 1078
C901120096 Total value of UL signal strength in radio channels on TCH .................................................................. 1079
in radio channels on TCH ................................................ 1079
C901120098 Maximum received DL signal strength in radio
channels on TCH ........................................................... 1080
channels on TCH ........................................................... 1080
C901120100 Total value of DL signal strength in radio channels on TCH .................................................................. 1081
C901120101 Number of samples with UL RQ = 0 on SDCCH............................................................................. 1081
C901120109 Number of samples with DL RQ = 0 on SDCCH............................................................................. 1086
1049

TCH ............................................................................. 1092
TCH ............................................................................. 1092
TCH ............................................................................. 1093
TCH ............................................................................. 1094
TCH ............................................................................. 1094
TCH ............................................................................. 1095
TCH ............................................................................. 1096
TCH ............................................................................. 1096
TCH ............................................................................. 1097
TCH ............................................................................. 1097
TCH ............................................................................. 1098
TCH ............................................................................. 1099
TCH ............................................................................. 1099
TCH ............................................................................. 1100
TCH ............................................................................. 1101
TCH ............................................................................. 1101
Overview
Cell radio measurement items mainly include UL/DL quality, signal
strength, TA, interference band and RQ value of radio channels.
The UL/DL quality, signal strength, TA and RQ value are counted
after measurement report or pre-processing measurement report
sent by BTS is received; BSC updates interference band status
in database after receiving measurement report or pre-processing
measurement report. The value of interference band can be inquired in database when periodical measurement is reported.
1050
signal quality samples in
wireless channels
Definition
Number of UL signal quality samples in radio channels
Description
This counter counts the number of received UL radio measurement report or pre-processing measurement report. The counter
increments when BSC receives UL radio measurement report or
pre-processing measurement report.
Usage
This counter is used to find out the frequency of UL signal quality

samples in radio channels.
Measurement
Point
The counter increments when BSC receives UL measurement report or pre-processing measurement report.
Unit
Times
C901120002 Level of worst

UL signal quality in wireless
channels
Definition
Level of worst UL signal quality in radio channels
Description
This counter counts the number of radio channels with the worst UL
signal quality in UL measurement report or pre-processing measurement report. If the level of UL signal quality in radio channel
in UL measurement report or pre-processing measurement report
received by BSC is worse than the recorded worst level of UL signal quality, then the new worst level of UL signal quality will be
recorded.
Usage
This counter is used to find out status of the level of the worst UL
signal quality in radio channels.
Measurement
Point
The counter counts when BSC receives UL measurement report or

Unit
None
1051

UL quality level values in
wireless channels
Definition
Total value of UL quality level values in radio channels
Description
This counter counts the number of total value of UL quality level

values in radio channels in radio measurement reports. The
counter accumulates UL quality level values in radio channels in
UL measurement report or pre-processing measurement report
received by BSC.
Usage
This counter is used to find out status of total value of UL quality

level values in radio channels.
Measurement
Point

Unit
None
wireless channels
Definition
Number of DL signal quality samples in radio channels
Description
This counter counts the number of received DL radio measurement report or pre-processing measurement report. The counter
increments when BSC receives DL radio measurement report or
Usage
This counter is used to find out the frequency of DL signal quality

samples in radio channels.
Measurement
Point
The counter increments when BSC receives DL measurement report or pre-processing measurement report.
Unit
Times

DL signal quality in wireless
channels
Definition
1052
Level of worst DL signal quality in radio channels
Description
This counter counts the number of radio channels with the worst DL
signal quality in DL measurement report or pre-processing measurement report. If the level of DL signal quality in radio channel
in DL measurement report or pre-processing measurement report
received by BSC is worse than the recorded worst level of DL signal quality, then the new worst level of DL signal quality will be
recorded.
Usage
This counter is used to find out status of the level of the worst DL
signal quality in radio channels.
Measurement
Point
The counter counts when BSC receives DL measurement report or

Unit
None

DL quality strength values in
wireless channels
Definition
Total value of DL quality level values in radio channels
Description
This counter counts the number of total value of DL quality level

values in radio channels in radio measurement reports. The
counter accumulates DL quality level values in radio channels in
DL measurement report or pre-processing measurement report
received by BSC.
Usage
This counter is used to find out status of total value of DL quality

level values in radio channels.
Measurement
Point

Unit
None
received UL signal strength
samples in wireless channels
Definition
Number of received UL signal strength samples in radio channels
Description
This counter counts the number of received UL signal strength

samples in radio channels in UL measurement report. The counter
increments when BSC receives UL measurement report or pre-processing measurement report.
Usage
This counter is used to find out frequency of received UL signal

strength samples in radio channels.
1053
Measurement
Point
Unit
Times
C901120008 Maximum
in wireless channels
Definition
Maximum received UL signal strength in radio channels
Description
This counter counts the maximum received UL signal strength in

radio channels in UL measurement report. If the UL signal strength
in radio channel in UL measurement report or pre-processing measurement report received by BSC is higher than the recorded highest UL signal strength, then the new highest UL signal strength will
be recorded.
Usage
This counter is used to find out status of maximum received UL

signal strength in radio channels.
Measurement
Point

Unit
None
C901120009 Minimum
Definition
Description
This counter counts the minimum received UL signal strength in

radio channels in UL measurement report. If the UL signal strength
in radio channel in UL measurement report or pre-processing measurement report received by BSC is lower than the recorded lowest
UL signal strength, then the new lowest UL signal strength will be
recorded.
Usage
This counter is used to find out status of minimum received UL

Measurement
Point

Unit
1054
Minimum received UL signal strength in radio channels
None
C901120010 Total value

of UL signal strength in
wireless channels
Definition
Total value of UL signal strength in radio channels
Description
This counter counts the number of total value of UL signal strength

in radio channels in radio measurement reports. The counter accumulates values of UL signal strength in radio channels in UL measurement report or pre-processing measurement report received
by BSC.
Usage
This counter is used to find out status of total value of UL signal

strength in radio channels.
Measurement
Point

Unit
None
received DL signal strength
samples in wireless channels
Definition
Number of received DL signal strength samples in radio channels
Description
This counter counts the number of received DL signal strength

samples in radio channels in DL measurement report. The counter
increments when BSC receives DL measurement report or pre-processing measurement report.
Usage
This counter is used to find out frequency of received DL signal

strength samples in radio channels.
Measurement
Point
Unit
Times
C901120012 Maximum
Definition
Maximum received DL signal strength in radio channels
1055
Description
This counter counts the maximum received DL signal strength in

radio channels in DL measurement report. If the DL signal strength
in radio channel in DL measurement report or pre-processing measurement report received by BSC is higher than the recorded highest DL signal strength, then the new highest DL signal strength will
be recorded.
Usage
This counter is used to find out status of maximum received DL

Measurement
Point

Unit
None
C901120013 Minimum DL
received signal strength in
radio channels
Definition
Minimum DL received signal strength in radio channels
Description
This counter counts the minimum received DL signal strength in

radio channels in DL measurement report. If the DL signal strength
in radio channel in DL measurement report or pre-processing measurement report received by BSC is lower than the recorded lowest
DL signal strength, then the new lowest DL signal strength will be
recorded.
Usage
This counter is used to find out status of minimum received DL

Measurement
Point

Unit
None

of DL signal strength in
wireless channels
Definition
1056
Total value of DL signal strength in radio channels
Description
This counter counts the number of total value of DL signal strength

in radio channels in radio measurement reports. The counter accumulates values of DL signal strength in radio channels in DL measurement report or pre-processing measurement report received
by BSC.
Usage
This counter is used to find out status of total value of DL signal

strength in radio channels.
Measurement
Point
Unit

None
TA samples in wireless
channels
Definition
Number of TA samples in radio channels
Description
This counter counts the number of TA samples in radio channels

in radio measurement reports. The counter increments when BSC
receives measurement report or pre-processing measurement report.
Usage
This counter is used to find out frequency of TA samples in radio

channels.
Measurement
Point
The counter increments when BSC receives measurement report

or pre-processing measurement report.
Unit
Times
C901120016 Maximum TA
Definition
Maximum TA in radio channels
Description
This counter counts the maximum TA in radio measurement reports. If the value of TA in radio channels in measurement report
or pre-processing measurement report received by BSC is larger
than the recorded highest value of TA, then the new largest value
of TA will be recorded.
Usage
This counter is used to find out status of maximum TA in radio

channels.
Measurement
Point
The counter counts when BSC receives measurement report or

Unit
Second
1057
C901120017 Total number

of TAs in wireless channels
Definition
Total number of TAs in radio channels
Description
This counter counts the number of TAs in radio channels in radio measurement reports. The counter accumulates values of TA
in radio channels in measurement report or pre-processing measurement report received by BSC.
Usage
This counter is used to find out status of total value of TA in radio

channels.
Measurement
Point
The counter counts when BSC receives measurement report or

Unit
Second
C901120018 Mean number

of idle TCH/Fs with
interference band 0
Definition
Mean number of idle TCH/Fs with interference band 0
Description
This counter counts the mean number of idle TCH/Fs with interference band 0.
Usage
This counter is used to find out number of idle TCH/Fs with interference band 0.
Measurement
Point
The counter increments when timed database inquiry is carried

out.
Unit
Related Features
Times

of idle TCH/Hs with
interference band 0
Definition
Description
1058
Mean number of idle TCH/Hs with interference band 0.

This counter counts the mean number of idle TCH/Hs with interference band 0.
Usage
This counter is used to find out number of idle TCH/Hs with interference band 0.
Measurement
Point

out.
Unit
Related Features
Times

of idle SDCCHs with
interference band 0
Definition
Mean number of idle SDCCHs with interference band 0
Description
This counter counts the mean number of idle SDCCHs with interference band 0.
Usage
This counter is used to find out number of idle SDCCHs with interference band 0.
Measurement
Point

out.
Unit
Related Features
Times

of idle SDCCHs with
interference band 1
Definition
Description
Usage
Measurement
Point

out.
Unit
Related Features
Times
1059

of idle SDCCHs with
interference band 2
Definition
Description
Usage
Measurement
Point

out.
Unit
Related Features
Times

of idle SDCCHs with
interference band 3
Definition
Description
Usage
Measurement
Point

out.
Unit
Related Features
Times

of idle SDCCHs with
interference band 4
Definition
Description
1060
Mean number of idle SDCCHs with interference band 4.

Usage
Measurement
Point

out.
Unit
Related Features
Times

of idle SDCCHs with
interference band 5
Definition
Description
Usage
Measurement
Point

out.
Unit
Related Features
Times
TFO initiations
Definition
Description
Measurement
Point
Unit
Related Features
Number of TFO initiations

This counter counts the number of TFOs established by BSC.
When the RANCS service process of BSC receives TFO status message and TFO has been established, the counter increments.
Times
ZGO-04-02-006 TFO
using noise suppression
Definition
Number of using noise suppression
1061
Description
This counter does not count for the time being.
C901120054 Number
of mode changes for
establishing TFO
Definition
Description
Related Features
Number of mode changes for establishing TFO

ZGO-04-02-006 TFO
mode changes for optimizing
TFO
Definition
Description
Related Features
Number of mode changes for optimizing TFO

ZGO-04-02-006 TFO
active collection changes for
establishing TFO
Definition
Description
Related Features
1062
Number of active collection changes for establishing TFO

ZGO-04-02-006 TFO
optimizing TFO
Definition
Description
Related Features
Number of active collection changes for optimizing TFO

ZGO-04-02-006 TFO
samples with voice quality is
excellent
Definition
Number of samples with voice quality is excellent
Description
This counter counts the number of voice quality being excellent.

When the UL measurement report, preprocessing measurement
report, or enhanced preprocessing measurement report is received, if the voice quality is excellent, the counter increments.
Usage
This counter is used to find out the UL voice quality on the radio
channel.
Measurement
Point
When BSCreceives the UL measurement report, preprocessing

measurement report, or enhanced preprocessing measurement
report, if the voice quality is excellent, the counter increments.
Unit
Times
good
Definition
Number of samples with voice quality is good
Description
This counter counts the number of voice quality being good. When
the UL measurement report, preprocessing measurement report,
or enhanced preprocessing measurement report is received, if the
voice quality is good, the counter increments.
Usage
channel.
1063
Measurement
Point
Unit
When BSC receives the UL measurement report, preprocessing

report, if the voice quality is good, the counter increments.
Times
medium
Definition
Number of samples with voice quality is medium
Description
This counter counts the number of voice quality being medium.

When the UL measurement report, preprocessing measurement
report, or enhanced preprocessing measurement report is received, if the voice quality is medium, the counter increments.
Usage
channel.
Measurement
Point

report, if the voice quality is medium, the counter increments.
Unit
Times
bad
Definition
Description
This counter counts the number of voice quality being bad. When
voice quality is bad, the counter increments.
Usage
channel.
Measurement
Point

report, if the voice quality is bad, the counter increments.
Unit
1064
Number of samples with voice quality is bad
Times
awfully
Definition
Number of samples with voice quality is awfully
Description
This counter counts the number of voice quality being awful. When
voice quality is awful, the counter increments.
Usage
channel.
Measurement
Point

report, if the voice quality is awful, the counter increments.
Unit
Times
uplink error frame on FR_V1
Description
This counter counts the number of uplink error frames of full-rate

version 1.
Usage
This counter is used to find out the number of incorrect uplink voice
frames of full-rate version 1. The counter increments when uplink
decoding error occurs.
Measurement
Point
The counter's value is obtained from the periodic measurement

report.
C901120064 Total Number

of uplink frame on FR_V1
Description
This counter counts the number of uplink frames of full-rate version 1.
Usage
This counter is used to find out the number of uplink voice frames
of full-rate version 1. The counter increments every 20 ms.
Measurement
Point

report.
1065
Description

version 2.
Usage
Measurement
Point

report.

Description
This counter counts the number of uplink voice frames of full-rate

version 2.
Usage
Measurement
Point

report.
1066
Description

version 3.
Usage
Measurement
Point

report.

Description
This counter counts the number of uplink voice frames of full-rate

version 3.
Usage
Measurement
Point

report.
uplink error frame on HR_V1
Description
This counter counts the number of uplink error frames of half-rate

version 1.
Usage
This counter is used to find out the number of incorrect uplink

voice frames of half-rate version 1. The counter increments when
uplink decoding error occurs.
Measurement
Point

report.

of uplink frame on HR_V1
Description
This counter counts the number of uplink voice frames of half-rate

version 1.
Usage
of half-rate version 1. The counter increments every 20 ms.
Measurement
Point

report.
Description
This counter counts the number of uplink error frames of half-rate

version 3.
1067
Usage
This counter is used to find out the number of incorrect uplink

voice frames of half-rate version 3. The counter increments when
uplink decoding error occurs.
Measurement
Point

report.

Description
This counter counts the number of uplink voice frames of half-rate

version 3.
Usage
of half-rate version 3. The counter increments every 20 ms.
Measurement
Point

report.
radio channels on SDCCH
Definition
Number of UL signal quality samples in radio channels on SDCCH
Description
Usage

samples in radio channels on SDCCH.
Measurement
Point
Unit
Times

UL signal quality in radio
channels on SDCCH
Definition
1068
Level of worst UL signal quality in radio channels on SDCCH
Description
recorded.
Usage
signal quality in radio channels on SDCCH.
Measurement
Point

Unit
None

Definition
Total value of UL quality level values in radio channels on SDCCH
Description

values in radio channels on SDCCH in radio measurement reports.
The counter accumulates UL quality level values in radio channels
on SDCCH in UL measurement report or pre-processing measurement report received by BSC.
Usage

level values in radio channels on SDCCH.
Measurement
Point

Unit
None
Definition
Number of DL signal quality samples in radio channels on SDCCH
Description
Usage

samples in radio channels on SDCCH.
1069
Measurement
Point
Unit
Times

DL signal quality in radio
channels on SDCCH
Definition
Level of worst DL signal quality in radio channels on SDCCH
Description
recorded.
Usage
signal quality in radio channels on SDCCH.
Measurement
Point

Unit
None

Definition
Total value of DL quality level values in radio channels on SDCCH
Description

values in radio channels on SDCCH in radio measurement reports.
The counter accumulates DL quality level values in radio channels
on SDCCH in DL measurement report or pre-processing measurement report received by BSC.
Usage

level values in radio channels on SDCCH.
Measurement
Point

Unit
1070
None
samples in radio channels
on SDCCH
Definition

on SDCCH
Description

samples in radio channels on SDCCH in UL measurement report.
Usage

strength samples in radio channels on SDCCH.
Measurement
Point
Unit
Times
C901120080 Maximum
in radio channels on SDCCH
Definition
Maximum received UL signal strength in radio channels on SDCCH
Description

radio channels on SDCCH in UL measurement report. If the UL
signal strength in radio channel in UL measurement report or preprocessing measurement report received by BSC is higher than
the recorded highest UL signal strength, then the new highest UL
signal strength will be recorded.
Usage

signal strength in radio channels on SDCCH.
Measurement
Point

Unit
None
1071
C901120081 Minimum
Definition
Minimum received UL signal strength in radio channels on SDCCH
Description

radio channels on SDCCH in UL measurement report. If the UL
signal strength in radio channel in UL measurement report or preprocessing measurement report received by BSC is lower than the
recorded lowest UL signal strength, then the new lowest UL signal
strength will be recorded.
Usage

Measurement
Point

Unit
None

UL signal strength in radio
channels on SDCCH
Definition
Description
This counter counts the number of total value of UL signal strength

in radio channels on SDCCH in radio measurement reports. The
counter accumulates values of UL signal strength in radio channels
on SDCCH in UL measurement report or pre-processing measurement report received by BSC.
Usage

strength in radio channels on SDCCH.
Measurement
Point

Unit
1072
Total value of UL signal strength in radio channels on SDCCH
None
on SDCCH
Definition

on SDCCH
Description

samples in radio channels on SDCCH in DL measurement report.
Usage

strength samples in radio channels on SDCCH.
Measurement
Point
Unit
Times
C901120084 Maximum
Definition
Maximum received DL signal strength in radio channels on SDCCH
Description

radio channels on SDCCH in DL measurement report. If the DL
signal strength in radio channel in DL measurement report or preprocessing measurement report received by BSC is higher than
the recorded highest DL signal strength, then the new highest DL
signal strength will be recorded.
Usage

Measurement
Point

Unit
None
1073
Definition
Minimum DL received signal strength in radio channels on SDCCH
Description

radio channels on SDCCH in DL measurement report. If the DL
signal strength in radio channel in DL measurement report or preprocessing measurement report received by BSC is lower than the
recorded lowest DL signal strength, then the new lowest DL signal
Usage

Measurement
Point

Unit
None

DL signal strength in radio
channels on SDCCH
Definition
Description
This counter counts the number of total value of DL signal strength

in radio channels on SDCCH in radio measurement reports. The
counter accumulates values of DL signal strength in radio channels
on SDCCH in DL measurement report or pre-processing measurement report received by BSC.
Usage

strength in radio channels on SDCCH.
Measurement
Point

Unit
1074
Total value of DL signal strength in radio channels on SDCCH
None
radio channels on TCH
Definition
Number of UL signal quality samples in radio channels on TCH
Description
Usage

samples in radio channels on TCH.
Measurement
Point
Unit
Times

UL signal quality in radio
channels on TCH
Definition
Level of worst UL signal quality in radio channels on TCH
Description
recorded.
Usage
signal quality in radio channels on TCH.
Measurement
Point

Unit
None
1075

Definition
Total value of UL quality level values in radio channels on TCH
Description

values in radio channels on TCH in radio measurement reports.
The counter accumulates UL quality level values in radio channels
on TCH in UL measurement report or pre-processing measurement
report received by BSC.
Usage

level values in radio channels on TCH.
Measurement
Point

Unit
None
Definition
Number of DL signal quality samples in radio channels on TCH
Description
Usage

samples in radio channels on TCH.
Measurement
Point
Unit
Times

DL signal quality in radio
channels on TCH
Definition
1076
Level of worst DL signal quality in radio channels on TCH
Description
recorded.
Usage
signal quality in radio channels on TCH.
Measurement
Point

Unit
None

Definition
Total value of DL quality level values in radio channels on TCH
Description

values in radio channels on TCH in radio measurement reports.
The counter accumulates DL quality level values in radio channels
on TCH in DL measurement report or pre-processing measurement
report received by BSC.
Usage

level values in radio channels on TCH.
Measurement
Point

Unit
None
on TCH
Definition

on TCH
Description

samples in radio channels on TCH in UL measurement report. The
counter increments when BSC receives UL measurement report or
1077
Usage

strength samples in radio channels on TCH.
Measurement
Point
Unit
Times
C901120094 Maximum
in radio channels on TCH
Definition
Maximum received UL signal strength in radio channels on TCH
Description

radio channels on TCH in UL measurement report. If the UL signal
strength in radio channel in UL measurement report or pre-processing measurement report received by BSC is higher than the
recorded highest UL signal strength, then the new highest UL signal strength will be recorded.
Usage

signal strength in radio channels on TCH.
Measurement
Point

Unit
None
C901120095 Minimum
Definition
Description

radio channels on TCH in UL measurement report. If the UL signal
strength in radio channel in UL measurement report or pre-processing measurement report received by BSC is lower than the
recorded lowest UL signal strength, then the new lowest UL signal
Usage

Measurement
Point

Unit
1078
Minimum received UL signal strength in radio channels on TCH
None

UL signal strength in radio
channels on TCH
Definition
Total value of UL signal strength in radio channels on TCH
Description
This counter counts the number of total value of UL signal

strength in radio channels on TCH in radio measurement reports.
The counter accumulates values of UL signal strength in radio
channels on TCH in UL measurement report or pre-processing
measurement report received by BSC.
Usage

strength in radio channels on TCH.
Measurement
Point

Unit
None
on TCH
Definition

on TCH
Description

samples in radio channels on TCH in DL measurement report. The
counter increments when BSC receives DL measurement report or
Usage

strength samples in radio channels on TCH.
Measurement
Point
Unit
Times
1079
C901120098 Maximum
Definition
Maximum received DL signal strength in radio channels on TCH
Description

radio channels on TCH in DL measurement report. If the DL signal
strength in radio channel in DL measurement report or pre-processing measurement report received by BSC is higher than the
recorded highest DL signal strength, then the new highest DL signal strength will be recorded.
Usage

Measurement
Point

Unit
None
Definition
Description

radio channels on TCH in DL measurement report. If the DL signal
strength in radio channel in DL measurement report or pre-processing measurement report received by BSC is lower than the
recorded lowest DL signal strength, then the new lowest DL signal
Usage

Measurement
Point

Unit
1080
Minimum DL received signal strength in radio channels on TCH
None

DL signal strength in radio
channels on TCH
Definition
Total value of DL signal strength in radio channels on TCH
Description
This counter counts the number of total value of DL signal

strength in radio channels on TCH in radio measurement reports.
The counter accumulates values of DL signal strength in radio
channels on TCH in DL measurement report or pre-processing
measurement report received by BSC.
Usage

strength in radio channels on TCH.
Measurement
Point

Unit
None
samples with UL RQ = 0 on
SDCCH
Definition
Description
Number of samples with UL RQ = 0 on SDCCH

BTS measures the level, quality, and interference of UL signal received in channel, and reports it to BSC, in combination with measurement report of DL signal reported by MS.
Interval between BTS measurement and report is consistent with
that of MS, that is, one measurement report is reported to BSC
per 480 ms.
Measurement mechanism of following counter C901120101 ~
C901120116 is same as that of this measurement value.
This measurement value is the sample number with UL RQ = 0 in
measurement report.
Measurement
Point
BSC receives the measurement report submitted by BTS, if UL

RQ=0 in measurement report, this counter increments. The measurement point is A, as shown in Figure 1082.
1081
FIGURE 1082 - BSC RECEIVES

BY BTS
Unit
THE
MEASUREMENT REPORT SUBMITTED
Times
SDCCH
Definition
Description
This measurement value is the sample number with UL RQ=1 in

measurement report.
Measurement
Point

BY BTS
Unit
1082
THE
Times
SDCCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
SDCCH
Definition
Description

measurement report.
Measurement
Point

RQ=3 in measurement report, this counter increments. The measurement point is A, as shown inFigure 1085.
1083

BY BTS
Unit
THE
Times
SDCCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
1084
THE
Times
SDCCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
SDCCH
Definition
Description

measurement report.
Measurement
Point

1085

BY BTS
Unit
THE
Times
SDCCH
Description

measurement report.
Measurement
Point

FIGURE 1089 BSC RECEIVES
BTS
Unit
THE
BY
Times
samples with DL RQ = 0 on
SDCCH
Definition
1086
Number of samples with DL RQ = 0 on SDCCH
Description
This measurement value is the sample number with DL RQ=1 in

measurement report.
Measurement
Point
BSC receives the measurement report submitted by BTS, if DL

BY BTS
Unit
THE
Times
SDCCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
1087
SDCCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
SDCCH
Definition
1088
Description

measurement report.
Measurement
Point


BY BTS
Unit
THE
Times
SDCCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
1089
SDCCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
SDCCH
Definition
1090
Description

measurement report.
Measurement
Point


BY BTS
Unit
THE
Times
SDCCH
Definition
Description

measurement report.
Measurement
Point
BSC receives the measurement report submitted by BTS, if DL RQ

= 7 in measurement report, this counter increments. The measurement point is A, as shown in Figure 1097.
BY BTS
Unit
THE
Times
1091
TCH
Definition
Description
Number of samples with UL RQ = 0 on TCH

per 480 ms.
measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
TCH
Definition
1092
Description

measurement report.
Measurement
Point


BY BTS
Unit
THE
Times
TCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
1093
TCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
TCH
Definition
1094
Description

measurement report.
Measurement
Point


BY BTS
Unit
THE
Times
TCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
1095
TCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
TCH
Description

measurement report.
Measurement
Point

BTS
1096
THE
BY
Unit
Times
TCH
Definition
Number of samples with DL RQ = 0 on TCH
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
TCH
Definition
Description

measurement report.
Measurement
Point

1097

BY BTS
Unit
THE
Times
TCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
1098
THE
Times
TCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
TCH
Definition
Description

measurement report.
Measurement
Point

1099

BY BTS
Unit
THE
Times
TCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
1100
THE
Times
TCH
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
TCH
Definition
Description

measurement report.
Measurement
Point
BSC receives the measurement report submitted by BTS, if DL RQ

= 7 on TCH in measurement report, this counter increments. The
1101

BY BTS
Unit
1102
THE
Times
Chapter
19
Sub Cell Statistics

Table of Contents
Overview...................................................................... 1106
C901130001 Number of available TCH/Fs in the second sub
cell .............................................................................. 1106
C901130002 Number of unavailable TCH/Fs in the second sub
cell .............................................................................. 1107
C901130003 Number of available TCH/Hs in the second sub
cell .............................................................................. 1107
C901130004 Number of unavailable TCH/Hs in the second sub
cell .............................................................................. 1108
C901130005 Number of handover attempts from the first sub
cell to the second sub cell ............................................... 1108
C901130006 Number of handover execution from the first sub
C901130007 Number of handover success from the first sub
C901130008 Number of handover attempts from the second
sub cell to the first sub cell ............................................. 1111
C901130009 Number of handover execution from the second
C901130010 Number of handover success from the second
C901130011 Number of handover attempts in the second sub
cell .............................................................................. 1114
C901130012 Number of handover execution in the second sub
cell .............................................................................. 1115
C901130013 Number of handover success in the second sub
cell .............................................................................. 1116
C901130014 Number of outgoing inter-cell handover attempts of the second sub cell .......................................... 1116
C901130015 Number of outgoing inter-cell handover execution of the second sub cell .............................................. 1117
C901130016 Number of outgoing inter-cell handover success
of the second sub cell .................................................... 1118
C901130017 Handover attempts due to UL receiving strength
of the full rate second sub cell ......................................... 1119
C901130018 Handover attempts due to DL receiving strength
of the full rate second sub cell ......................................... 1120
C901130019 Handover attempts due to UL quality of the full
rate second sub cell ....................................................... 1121
C901130020 Handover attempts due to DL quality of the full
C901130021 Handover attempts due to PBGT of the full rate
second sub cell ............................................................. 1123
C901130022 Handover attempts due to traffic of the full rate
second sub cell ............................................................. 1123
1103
C901130023 Handover attempts due to UL interference of the

full rate second sub cell (on TCH/F).................................. 1124
C901130024 Handover attempts due to DL interference of the
full rate second sub cell (on TCH/F).................................. 1125
C901130025 Handover attempts due to good CI of the full
rate second sub cell (on TCH/F)....................................... 1126
C901130026 Handover attempts due to bad CI of the full rate
second sub cell (on TCH/F) ............................................. 1127
large TA of the full rate second sub cell (on TCH/F) ............ 1128
small TA of the full rate second sub cell (on TCH/F) ............ 1129
C901130029 Number of forced transfer handover attempts of
the full rate second sub cell (on TCH/F) ............................ 1130
C901130030 Handover attempts due to other causes of the
full rate second sub cell .................................................. 1131
C901130031 Handover attempts due to UL receiving strength
of the half rate second sub cell ........................................ 1132
C901130032 Handover attempts due to DL receiving strength
of the half rate second sub cell ........................................ 1133
C901130033 Handover attempts due to UL quality of the half
C901130034 Handover attempts due to DL quality of the half
C901130035 Handover attempts due to PBGT of the half rate
second sub cell ............................................................. 1136
C901130036 Handover attempts due to traffic of the half rate
second sub cell ............................................................. 1136
C901130037 Handover attempts due to UL interference of the
half rate second sub cell ................................................. 1137
C901130038 Handover attempts due to DL interference of the
C901130039 Handover attempts due to C/I of the half rate
second sub cell ............................................................. 1139
C901130040 Handover attempts due to C/I of the half rate
second sub cell ............................................................. 1140
large TA of the half rate second sub cell............................ 1141
small TA of the half rate second sub cell ........................... 1142
C901130043 Number of forced transfer handover attempts of
the half rate second sub cell............................................ 1143
C901130044 Handover attempts due to other causes of the
C901130045 Number of attempts of TCH/F seizure of the second sub cell (used for assignment) .................................. 1145
C901130046 Number of TCH/F seizure success of the second
sub cell (used for assignment)......................................... 1146
C901130047 Number of TCH/F seizure failure of the second
C901130048 Number of attempts of TCH/F seizure of the second sub cell (used for handover) ..................................... 1147
C901130049 Number of TCH/F seizure success of the second
sub cell (used for handover) ........................................... 1148
C901130050 Number of TCH/F seizure failure of the second
C901130051 Number of TCH/H seizure attempts of the second sub cell (used for assignment) .................................. 1149
C901130052 Number of TCH/H seizure success of the second
1104
Chapter 19 Sub Cell Statistics
C901130053 Number of TCH/H seizure failure of the second

C901130054 Number of TCH/H seizure attempts of the second sub cell (used for handover) ..................................... 1151
C901130055 Number of TCH/H seizure success of the second
C901130056 Number of TCH/H seizure failure of the second
C901130057 Number of TCH/F call drops in the second sub
cell .............................................................................. 1153
C901130058 Number of TCH/H call drops in the second sub
cell .............................................................................. 1154
C901130059 TCH/F busy time in the second sub cell .......... 1155
C901130060 TCH/H busy time in the second sub cell.......... 1155
C901130061 Number of TCH/F assignment attempts of the
second sub cell ............................................................. 1156
C901130062 Number of TCH/F assignment success of the second sub cell .................................................................. 1156
C901130063 Number of TCH/F handover attempts of the second sub cell .................................................................. 1157
C901130064 Number of TCH/F handover success of the second sub cell .................................................................. 1158
C901130065 Number of TCH/H assignment attempts of the
second sub cell ............................................................. 1159
C901130066 Number of TCH/H assignment success of the
second sub cell ............................................................. 1159
C901130067 Number of TCH/H handover attempts of the second sub cell .................................................................. 1160
C901130068 Number of TCH/H handover success of the second sub cell .................................................................. 1161
C901130069 TCH/F of the first sub cell seizure success when
prefer the second sub cell (used for assignment) ............... 1161
C901130070 TCH/F of the first sub cell seizure success when
prefer the second sub cell (used for handover) .................. 1162
C901130071 TCH/H of the first sub cell seizure success when
prefer the second sub cell (used for assignment) ............... 1163
C901130072 TCH/H of the first sub cell seizure success when
prefer the second sub cell (used for handover) .................. 1163
C901130073 Number of Inter-Cell Handover Attempts to
the Second Sub Cell Directly From the Cell in the Same
Site ............................................................................. 1164
C901130074 Number of Inter-Cell Handover Execution to
Site ............................................................................. 1164
C901130075 Number of Inter-Cell Handover Success to
Site ............................................................................. 1165
C901130076 Number of Inter-Cell Handover Attempts to the
Second Sub Cell Directly From Another Site ...................... 1165
C901130077 Number of Inter-Cell Handover Execution to the
C901130078 Number of Inter-Cell Handover Success to the
C901130079 Number of Handover Attempts to the Second
Sub Cell Directly From Another BSC ................................. 1167
C901130080 Number of Handover Execution to the Second
Sub Cell Directly From Another BSC ................................. 1167
C901130081 Number of Handover Success to the Second Sub
Cell Directly From Another BSC ....................................... 1168
1105

Too Fast After Handover From Another Cell in the Same
Site ............................................................................. 1168
Too Fast After Handover From Another Cell in the Same
Site ............................................................................. 1169
C901130084 Number of Handover to the First Sub Cell Too
Fast After Handover From Another Site............................. 1169
C901130085 Number of Handover to the Second Sub Cell Too
Fast After Handover From Another Site............................. 1170
Overview
Sub cell statistics counter is used to find out operation status of
the sub cell in radio environment. It focuses on inter-sub-cell handover and relevant counting at the second sub cell so as to check
traffic absorption condition by the second sub cell.
The measurement takes sub cell as the statistics unit.
available TCH/Fs in the
second sub cell
Definition
Number of available TCH/Fs in the second sub cell
Description
This counter counts the number of available TCH/F channels in the

second sub cell.
Usage
This counter is used to find out the number of available TCH/F

channels in the second sub cell, to learn the traffic of the second
sub cell.
Measurement
Point
Unit
Related Features
Call database interface to count promptly.

Times
ZGO-05-02-009 Concentric Circle Technology
1106
unavailable TCH/Fs in the
second sub cell
Definition
Number of unavailable TCH/Fs in the second sub cell
Description
This counter counts the number of unavailable TCH/F channels in

the second sub cell.
Usage
This counter is used to find out the number of available TCH/F

sub cell.
Measurement
Point
Unit
Related Features

Times
available TCH/Hs in the
second sub cell
Definition
Number of available TCH/Hs in the second sub cell
Description
This counter counts the number of available TCH/H channels in the

second sub cell.
Usage

sub cell.
Measurement
Point
Unit
Related Features

Times
1107
unavailable TCH/Hs in the
second sub cell
Definition
Number of unavailable TCH/Hs in the second sub cell
Description
This counter counts the number of unavailable TCH/H channels in

Usage

sub cell.
Measurement
Point
Unit
Related Features

Times
handover attempts from the
first sub cell to the second
sub cell
1108
Definition
Number of handover attempts from the first sub cell to the second
sub cell
Description

from the first sub cell to the second sub cell.
Usage

attempts from the first sub cell to the second sub cell, as one of
the parameters to measure radio environment.
Measurement
Point
When BSC receives measurement reports from MS, it makes handover decision. If it is decided to do intra-cell handover, and current sub cell is the first sub cell, and if handover reason is 'too
small Ta&PassLoss' or 'too large C/I', this counter increments. The
measurement point is A, as shown inFigure 1114 .
FIGURE 1114 - INTRA-CELL HANDOVER ATTEMPT
Unit
Related Features
Times
ZGO-04-02-005 Co-BCCH
handover execution from the
sub cell
Definition
Number of handover execution from the first sub cell to the second
sub cell
Description
This counter counts the number of intra-cell handover execution

Usage

execution from the first sub cell to the second sub cell, as one of
Measurement
Point
During inter-sub-cell handover within a cell, this counter increments when following conditions are met:
The channel of target sub cell is successfully activated
Current channel is in the second sub cell
Source channel is in the first sub cell
1109
FIGURE 1115 - INTRA-CELL INCOMING HANDOVER
Unit
Related Features
Times
handover success from the
sub cell
1110
Definition
Number of handover success from the first sub cell to the second
sub cell
Description
This counter counts the number of intra-cell handover success

Usage

success from the first sub cell to the second sub cell, as one of the
parameters to measure radio environment.
Measurement
Point
During inter-sub-cell handover within a cell, target sub cell will receive handover completion message, indicating that MS successfully accesses to new channel. If target channel is in the second
sub cell, and source channel is in the first sub cell, this counter
increments. The measurement point is A, as shownFigure 1116 .
FIGURE 1116 - SUCCESSFUL INTRA-CELL HANDOVER
Unit
Related Features
Times
handover attempts from the
second sub cell to the first
sub cell
Definition
Number of handover attempts from the second sub cell to the first
sub cell
Description

from the second sub cell to the first sub cell.
Usage

attempts from the second sub cell to the first sub cell, as one of
Measurement
Point
When BSC receives measurement reports from MS, it makes handover decision. If it is decided to do intra-cell handover, and current sub cell is the second sub cell, and if handover reason is 'too
small Ta&PassLoss' or 'too large C/I', this counter increments. The
1111
Unit
Related Features
Times
handover execution from the
sub cell
Definition
Number of handover execution from the second sub cell to the first
sub cell
Description

Usage

execution from the second sub cell to the first sub cell, as one of
Measurement
Point
Current channel is in the second sub cell
Source channel is in the first sub cell
1112
Unit
Related Features
Times
handover success from the
sub cell
Definition
Number of handover success from the second sub cell to the first
sub cell
Description
This counter counts the number of intra-cell successful handover

Usage

ins success from the second sub cell to the first sub cell, as one of
Measurement
Point
Target sub cell receives handover completion message
Target channel is in the first sub cell
Source channel is in the second sub cell
1113
Unit
Related Features
Times
handover attempts in the
second sub cell
Definition
Number of handover attempts in the second sub cell
Description

within the second sub cell.
Usage

attempts within the second sub cell, as one of the parameters to
measure radio environment.
Measurement
Point
When BSC receives measurement reports from MS, it makes handover decision. If it is decided to do intra-cell handover, and current sub cell is the second sub cell, and if handover reason is interference handover, this counter increments. The measurement
Unit
1114
Times
Related Features
handover execution in the
second sub cell
Definition
Number of handover execution in the second sub cell
Description

Usage

execution within the second sub cell, as one of the parameters to
measure radio environment.
Measurement
Point
Current channel is in the first sub cell
Source channel is in the second sub cell

Unit
Related Features
Times
1115
handover success in the
second sub cell
Definition
Number of handover success in the second sub cell
Description
This counter counts the number of intra-cell handover success

Usage
This counter is used to find out the frequency of successful handover from the second sub cell to the second sub cell, as one of
Measurement
Point
Target sub cell receives handover completion message
Target channel is in the second sub cell
Source channel is in the first sub cells

Unit
Related Features
Times
outgoing inter-cell handover
attempts of the second sub
cell
Definition
1116
Number of outgoing inter-cell handover attempts of the second

sub cell
Description
This counter counts the number of inter-cell handover attempts

originated from the second sub cell.
Usage
This counter is used to find out the frequency of inter-cell handover attempts originated from the second sub cell, as one of the
parameters to measure radio environment.
Measurement
Point
When BSC receives measurement reports from MS, it makes handover decision. If it is decided to do inter-cell handover, and source
cell is the second sub cell, this counter increments. The measurement point is A, as shown in Figure 1123.
Unit
Related Features
Times
execution of the second sub
cell
Definition
Number of outgoing inter-cell handover success of the second sub

cell
Description
This counter counts the Number of handover success inter-cell

Usage
This counter is used to find out the frequency of inter-cell successful handover originated from the second sub cell, as one of
Measurement
Point
During inter-sub-cell handover within a cell, source instance receives the handover completion message returned from target instance, indicating the MS has accessed to target channel. If source
sub cell is the second sub cell, this counter increments. The measurement point is A, as shown in Figure 1124.
1117
FIGURE 1124 - INTER-CELL HANDOVER EXECUTION
Unit
Related Features
Times
success of the second sub
cell
1118
Definition
Number of outgoing inter-cell handover success of the second sub

cell
Description
This counter counts the number of handover success inter-cell

Usage
This counter is used to find out the frequency of inter-cell successful handover originated from the second sub cell, as one of
Measurement
Point
During inter-sub-cell handover within a cell, source instance receives the handover completion message returned from target instance, indicating the MS has accessed to target channel. If source
sub cell is the second sub cell, this counter increments. The measurement point is A, as shown in Figure 1125.
Usage
Related Features
Times
C901130017 Handover
attempts due to UL receiving
strength of the full rate
second sub cell
Definition
Handover attempts due to UL receiving strength of the full rate

second sub cell
Description
This counter counts the number of handover attempts, caused by

too low UL receiving strength and originated from full rate channel
in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by UL receiving strength and originated from full
rate channel in the second sub cell, as one of the references for
radio environment in the second sub cell.
Measurement
Point
Make handover decision after BSC receives measurement reports.

This counter increments when following conditions are met:
Decision is made
Source sub cell is the second sub cell
Handover is caused by UL strength
Current channel is full rate one
The measurement point is A, as shown in .
1119
FIGURE 1126 - HANDOVER DECISION
Unit
Related Features
Times
C901130018 Handover
attempts due to DL receiving
strength of the full rate
second sub cell
Definition
Handover attempts due to DL receiving strength of the full rate

second sub cell
Description

too low DL receiving strength and originated from full rate channel
Usage
This counter is used to find out the frequency of handover attempts, caused by DL receiving strength and originated from full
Measurement
Point

Decision is made
Handover is caused by DL strength
1120
Usage
Related Features
Times
C901130019 Handover
attempts due to UL quality of
the full rate second sub cell
Definition
Handover attempts due to UL quality of the full rate second sub

cell
Description

too poor UL quality and originated from full rate channel in the
second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by UL quality and originated from full rate channel
in the second sub cell, as one of the references for radio environment in the second sub cell.
Measurement
Point

Decision is made
Handover is caused by UL quality
The measurement point is A, as shown inFigure 1128 .

1121
Unit
Related Features
Times
C901130020 Handover
attempts due to DL quality of
Definition
Handover attempts due to DL quality of the full rate second sub

cell
Description

too poor DL quality and originated from full rate channel in the
second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by DL quality and originated from full rate channel
Measurement
Point

Decision is made
Handover is caused by DL quality

Unit
Related Features
1122
Times
C901130021 Handover
attempts due to PBGT of the
full rate second sub cell
Definition
Handover attempts due to PBGT of the full rate second sub cell
Description

PBGT and originated from full rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by PBGT and originated from full rate channel in
the second sub cell, as one of the references for radio environment
Measurement
Point

Decision is made
Handover is caused by PBGT

Unit
Related Features
Times
C901130022 Handover
attempts due to traffic of the
full rate second sub cell
Definition
Description
Handover attempts due to traffic of the full rate second sub cell
traffic and originated from full rate channel in the second sub cell.
1123
Usage
This counter is used to find out the frequency of handover attempts, caused by traffic and originated from full rate channel in
Measurement
Point

Decision is made
Handover is caused by traffic
Current channel is full rate one, this counter increments

Units
Related Features
Times
C901130023 Handover
attempts due to UL
interference of the full
rate second sub cell (on
TCH/F)
1124
Definition
Handover attempts due to UL interference of the full rate second

sub cell (on TCH/F)
Description

UL interference and originated from full rate channel in the second
sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by UL interference and originated from full rate
channel in the second sub cell, as one of the references for radio
environment in the second sub cell.
Measurement
Point

Decision is made

Unit
Related Features
Times
C901130024 Handover
attempts due to DL
interference of the full
TCH/F)
Definition
Handover attempts due to DL interference of the full rate second

sub cell (on TCH/F)
Description

DL interference and originated from full rate channel in the second
sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by DL interference and originated from full rate
Measurement
Point

1125
Decision is made
Handover is caused by DL interference

Unit
Related Features
Times
C901130025 Handover
attempts due to good CI of
(on TCH/F)
Definition
Handover attempts due to good CI of the full rate second sub cell
(on TCH/F)
Description

too good C/I and originated from full rate channel in the second
sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by too good C/I and originated from full rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.
Measurement
Point

Decision is made
Handover is caused by too good C/I
1126
Unit
Related Features
Times
C901130026 Handover
attempts due to bad CI of the
full rate second sub cell (on
TCH/F)
Definition
Handover attempts due to bad C/I of the full rate second sub cell
(on TCH/F)
Description

too bad C/I and originated from full rate channel in the second sub
cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by too bad C/I and originated from full rate channel
Measurement
Point

Decision is made
Handover is caused by too bad C/I
1127
Unit
Related Features
Times
C901130027 Handover
attempts due to path loss
and too large TA of the full
TCH/F)
Definition
Handover attempts due to path loss and too large GSMBSS-TA of

the full rate second sub cell (on TCH/F)
Description

too large path loss and TA and originated from full rate channel in
Usage
This counter is used to find out the frequency of handover attempts, caused by too large path loss and TA and originated from
full rate channel in the second sub cell, as one of the references
for radio environment in the second sub cell.
Measurement
Point

Decision is made
Handover is caused by too large path loss and TA
1128
Unit
Related Features
Times
C901130028 Handover
and too small TA of the full
TCH/F)
Definition
Handover attempts due to path loss and too small GSMBSS-TA of

the full rate second sub cell (on TCH/F)
Description

too small path loss and TA and originated from full rate channel in
Usage
This counter is used to find out the frequency of handover attempts, caused by too small path loss and TA and originated from
Measurement
Point

Decision is made
Handover is caused by too small path loss and TA
1129
Unit
Related Features
Times
forced transfer handover
attempts of the full rate
second sub cell (on TCH/F)
Definition
Number of forced transfer handover attempts of the full rate second sub cell (on TCH/F)
Description

forced transfer handover and originated from full rate channel in
the second sub cell
Usage
This counter is used to find out the frequency of handover attempts, caused by forced transfer handover and originated from
Measurement
Point

Decision is made
Handover is caused by forced transfer
1130
Unit
Related Features
Times
C901130030 Handover
attempts due to other causes
of the full rate second sub
cell
Definition
Handover attempts due to other causes of the full rate second sub
cell
Description
This counter is used to find out the frequency of handover attempts, caused by other causes and originated from full rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.
Usage
Measurement
Point

Decision is made
Handover is caused by other reasons
1131
Unit
Related Features
Times
C901130031 Handover
attempts due to UL receiving
strength of the half rate
second sub cell
Definition
Handover attempts due to UL receiving strength of the half rate

second sub cell
Description

too low UL receiving strength and originated from half rate channel
Usage
Measurement
Point

Decision is made
Handover is caused by UL strength
Current channel is half rate one
1132
Unit
Related Features
Times
C901130032 Handover
attempts due to DL receiving
strength of the half rate
second sub cell
Definition
Handover attempts due to DL receiving strength of the half rate

second sub cell
Description

too low DL receiving strength and originated from half rate channel
Usage
This counter is used to find out the frequency of handover attempts, caused by DL receiving strength and originated from half
Measurement
Point

Decision is made
Handover is caused by DL strength
1133
Unit
Related Features
Times
C901130033 Handover
attempts due to UL quality of
the half rate second sub cell
Definition
Handover attempts due to UL quality of the half rate second sub

cell
Description

too poor UL quality and originated from half full rate channel in
Usage
This counter is used to find out the frequency of handover attempts, caused by UL quality and originated from half rate channel
Measurement
Point

Decision is made
Handover is caused by UL quality

1134
Unit
Related Features
Times
C901130034 Handover
attempts due to DL quality of
Definition
Handover attempts due to DL quality of the half rate second sub

cell
Description

too poor DL quality and originated from half rate channel in the
second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by DL quality and originated from full rate channel
Measurement
Point

Decision is made
Handover is caused by DL quality

Unit
Related Features
Times
1135
C901130035 Handover
attempts due to PBGT of the
half rate second sub cell
Definition
Handover attempts due to PBGT of the half rate second sub cell
Description

PBGT and originated from half rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by PBGT and originated from half rate channel in
Measurement
Point

Decision is made
Handover is caused by PBGT

Unit
Related Features
Times
C901130036 Handover
attempts due to traffic of the
Definition
Description
1136
Handover attempts due to traffic of the half rate second sub cell
traffic and originated from half rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by traffic and originated from half rate channel in
Measurement
Point

Decision is made

Unit
Related Features
Times
C901130037 Handover
attempts due to UL
interference of the half
rate second sub cell
Definition
Handover attempts due to UL interference of the half rate second

sub cell
Description

UL interference and originated from half rate channel in the second
sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by UL interference and originated from half rate
1137
Measurement
Point

Decision is made
Handover is caused by UL interference

Unit
Related Features
Times
C901130038 Handover
attempts due to DL
interference of the half
1138
Definition
Handover attempts due to DL interference of the half rate second

sub cell (on TCH/F)
Description

DL interference and originated from half rate channel in the second
sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by DL interference and originated from half rate
Measurement
Point

Decision is made
Handover is caused by DL interference

Unit
Related Features
Times
C901130039 Handover
attempts due to C/I of the
Definition
Handover attempts due to C/I of the half rate second sub cell
Description

too good C/I and originated from half rate channel in the second
sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by too good C/I and originated from half rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.
Measurement
Point

Decision is made
Handover is caused by too good C/I
The measurement point is A, as shown in Figure 1148
1139
Unit
Related Features
Times
C901130040 Handover
attempts due to C/I of the
Definition
Handover attempts due to C/I of the half rate second sub cell
Description

too bad C/I and originated from half rate channel in the second
sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by too bad C/I and originated from half rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.
Measurement
Point

Decision is made
Handover is caused by too bad C/I

1140
Unit
Related Features
Times
C901130041 Handover
and too large TA of the half
Definition
Handover attempts due to path loss and too large GSMBSS-TA of

Description

too large path loss and TA and originated from half rate channel
Usage
This counter is used to find out the frequency of handover attempts, caused by too large path loss and TA and originated from
half rate channel in the second sub cell, as one of the references
Measurement
Point

Decision is made
Handover is caused by too large path loss and TA

Unit
Related Features
Times
1141
C901130042 Handover
and too small TA of the half
Definition
Handover attempts due to path loss and too small GSMBSS-TA of

the half rate second sub cell (on TCH/F)
Description

too small path loss and TA and originated from half rate channel
Usage
This counter is used to find out the frequency of handover attempts, caused by too small path loss and TA and originated from
Measurement
Point

Decision is made
Handover is caused by too small path loss and TA

Unit
Related Features
Times
1142
forced transfer handover
attempts of the half rate
second sub cell
Definition
Number of forced transfer handover attempts of the half rate second sub cell (on TCH/F)
Description

forced transfer handover and originated from half rate channel in
Usage
This counter is used to find out the frequency of handover attempts, caused by forced transfer handover and originated from
Measurement
Point

Decision is made
Handover is caused by forced transfer

Unit
Related Features
Times
1143
C901130044 Handover
attempts due to other causes
of the half rate second sub
cell
Definition
Handover attempts due to other causes of the half rate second sub
cell
Description

other causes and originated from half rate channel in the second
sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by other causes and originated from half rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.
Measurement
Point

Decision is made
Handover is caused by other reasons

Unit
Related Features
Times
1144
attempts of TCH/F seizure
of the second sub cell (used
for assignment)
Definition
Number of attempts of TCH/F seizure of the second sub cell (used

for assignment).
Description
This counter counts the number of seizure attempts in TCH/F channel in the second sub cell.
Usage
This counter is used to find out the frequency of seizure attempts

in TCH/F channel in the second sub cell, as one of the references
Measurement
Point
Measurement points of this counter include two types.
When successfully applying for channel, if channel type is

TCH/F, and application reason is assignment, this counter
increments. Successful application includes:
Receive release command while waiting for resource state
Failed to configure instance number while seizing channel
Related Features
Resource acquisition by queuing, seizure, or dynamic channel conversion
When channel application is failed, if channel type is TCH/F,

and application reason is assignment, this counter increments.
Failure reasons of application channel include:
Unit
Successful resource application
Timeout while queuing or seizure, or waiting for resource

timer
No available radio resource
Times
1145
TCH/F seizure success of
the second sub cell (used for
assignment)
Definition
Number of TCH/F seizure success of the second sub cell (used for
assignment)
Description
This counter counts the number of successful seizure in TCH/F

channel in the second sub cell.
Usage
This counter is used to find out the frequency of successful seizure

Measurement
Point
Successfully applying for channel
Channel type is TCH/F
Application reason is assignment
Successful application includes: successful resource application;

resource acquisition by queuing, seizure, or dynamic channel conversion.
Unit
Related Features
Times
TCH/F seizure failure of the
second sub cell (used for
assignment)
1146
Definition
Number of TCH/F seizure failure of the second sub cell (used for
assignment)
Description
This counter counts the number of seizure failure in TCH/F channel

Usage
This counter is used to find out the frequency of seizure failure in

TCH/F channel in the second sub cell, as one of the references for
Measurement
Point
Unit
Related Features
When channel application is failed, if channel type is TCH/F, and

application reason is assignment, this counter increments. Failure
reasons of application channel include:
Timeout while queuing or seizure, or waiting for resource timer
Times
attempts of TCH/F seizure
of the second sub cell (used
for handover)
Description
This counter counts the number of seizure attempts in TCH/F channel in the second sub cell.
Usage

Measurement
Point
Measurement points of this counter include two types.
When channel is successfully applied, if channel type is TCH/F,

and application reason is handover, this counter increments.
Successful application includes: successful resource application; resource acquisition by queuing, seizure, or dynamic
channel conversion.
When channel application is failed, if channel type is TCH/F,

Receive release command while waiting for resource state;
Failed to configure instance number while seizing channel;
Unit
Related Features

timer;
No available radio resource.
Times
1147
TCH/F seizure success of
handover)
Definition
Number of TCH/F seizure success of the second sub cell (used for
handover)
Description
This counter counts the number of successful seizure in TCH/F

Usage

Measurement
Point
Channel is successfully applied
Channel type is TCH/F
Application reason is handover

Unit
Related Features
Times
TCH/F seizure failure of the
handover)
Definition
1148
Number of TCH/F seizure failure of the second sub cell (used for
handover)
Description

Usage

TCH/F channel in the second sub cell, as one of the references for
Measurement
Point
When channel application is failed, if channel type is TCH/F, and

application reason is handover, this counter increments. Failure

Unit
Related Features
Times
TCH/H seizure attempts of
assignment)
Definition
Number of TCH/H seizure attempts of the second sub cell (used

for assignment)
Description
This counter counts the number of seizure attempts in TCH/H

Usage

in TCH/H channel in the second sub cell, as one of the references
Measurement
Point
Measurement points of this counter include two types:
When channel is successfully applied, if channel type is TCH/H,

channel conversion.
When channel application is failed, if channel type is TCH/H,

1149
Unit
Related Features

timer
Times
TCH/H seizure success of
assignment)
Definition
Number of TCH/H seizure success of the second sub cell (used for
assignment)
Description
This counter counts the number of successful seizure in TCH/H

Usage

Measurement
Point
When successfully applying for channel, if channel type is TCH/H,

Unit
Related Features
Times
1150
TCH/H seizure failure of the
assignment)
Definition
Number of TCH/H seizure failure of the second sub cell (used for
assignment)
Description

Usage

TCH/H channel in the second sub cell, as one of the references for
Measurement
Point
When channel application is failed, if channel type is TCH/H, and

application reason is assignment, this counter increments. Failure
Unit
Related Features
Times
TCH/H seizure attempts of
handover)
Definition
Number of TCH/H seizure attempts of the second sub cell (used

for handover)
Description
This counter counts the number of seizure attempts in TCH/H

Usage

1151
Measurement
Point
Measurement points of this counter include two types:
When channel is successfully applied, if channel type is TCH/H,

channel conversion.
When channel application is failed, if channel type is TCH/H,

Unit
Related Features

timer
Times
TCH/H seizure success of
handover)
Definition
Number of TCH/H seizure success of the second sub cell (used for
handover)
Description
This counter counts the number of successful seizure in TCH/H

Usage

Measurement
Point
When channel is successfully applied, if channel type is TCH/H, and

application reason is handover, this counter increments. Successful application includes: successful resource application; resource
acquisition by queuing, seizure, or dynamic channel conversion.
Unit
Related Features
Times
1152
TCH/H seizure failure of the
handover)
Definition
Number of TCH/H seizure failure of the second sub cell (used for
handover)
Description
This counter counts the number of seizure failure in TCH/H channel

Usage

TCH/H channel in the second sub cell, as one of the references for
Measurement
Point
When channel application is failed, if channel type is TCH/H and

application reason is handover, this counter increments. Failure
Unit
Related Features
Times
TCH/F call drops in the
second sub cell
Definition
Description
Number of TCH/F call drops in the second sub cell

This counter counts the number of call drops in TCH/F channel in
1153
Usage
This counter is used to find out the frequency of call drops in TCH/F
Measurement
Point
During call drops, if current channel is TCH/F, this counter increments. Call drops include following cases:
Unit
Related Features
After handover and deliver assignment command in cell, call

drops occur due to 3107 timer timeout
After inter-cell handover delivers handover command, call

After handover and deliver external handover command, call

drops occur due to outgoing protection timer timeout
BSC receives radio link failure message
Times
TCH/H call drops in the
second sub cell
Definition
Number of TCH/H call drops in the second sub cell
Description
This counter counts the number of call drops in TCH/H channel in

Usage
This counter is used to find out the frequency of call drops in TCH/H
Measurement
Point
During call drops, if current channel is TCH/H, this counter increments. Call drops include following cases:
Unit
Related Features
After handover and deliver assignment command in cell, call

After inter-cell handover delivers handover command, call

After handover and deliver external handover command, call

drops occur due to outgoing protection timer timeout
BSC receives radio link failure message
Times
1154

time in the second sub cell
Definition
TCH/F busy time in the second sub cell
Description
This counter counts the seizure time in TCH/F channel in the second sub cell.
Usage
This counter is used to find out the seizure time in TCH/F channel
in the second sub cell, as one of the references for traffic condition
Measurement
Point
Unit
Related Features
This counter will count at following two cases:
When seize or release TCH/F channel within a cell. Seizure

channel means successful application of radio resource for
database. Channel release means two cases: instance release
caused by different reasons and release while waiting resource
timer timeout.
When promptly report measurement data.
Times

time in the second sub cell
Definition
TCH/H busy time in the second sub cell
Description
This counter counts the seizure time in TCH/H channel in the second sub cell.
Usage
This counter is used to find out the seizure time in TCH/H channel
in the second sub cell, as one of the references for traffic condition
Measurement
Point
Unit
Related Features
This counter will count at following two cases:
When seize or release TCH/F channel within a cell. Seizure

channel means successful application of radio resource for
database. Channel release means two cases: instance release
caused by different reasons and release while waiting resource
timer timeout.
When promptly report measurement data.
Times
1155
TCH/F assignment attempts
of the second sub cell
Description
This counter counts the number of attempts of TCH/F assignment

for the second sub cell. When BSC receives the release command,
the Um interface assignment completion message or handover
completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is full-rate channel,
and the channel request is due to assignment, then the counter
increments.
Usage
This counter is used to find out the number of attempts of TCH/F

assignment for the second sub cell. It helps study the access condition of the second sub cell.
This counter is supported in version V6.20.200f or above.
Measurement
Point
1. When BSC receives the release command in the WaitAccess

status, if the sub cell ID is 2, the channel is full-rate channel,
counts.
2. When BSC receives the Um interface assignment completion
message in the WaitAccess status, if the sub cell ID is 2, the
channel is full-rate channel, and the channel request is due to
assignment, then the counter counts.
3. When BSC receives the handover completion message in the
WaitAccess status, if the sub cell ID is 2, the channel is full-rate
channel, and the channel request is due to assignment, then
the counter counts.
4. When BSC receives the TWaitMSAccessOut message in the
the counter counts.
Unit
Times
Description
1156
This counter counts the number of successful TCH/F assignments

completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is full-rate channel,
increments.
Usage
This counter is used to find out the number of successful TCH/F

assignments for the second sub cell. It helps study the access
condition of the second sub cell.
Measurement
Point

channel is full-rate channel, and the channel request is due to
2. When the handover completion message is processed in the
the counter counts.
Unit
Times
TCH/F handover attempts of
the second sub cell
Description
This counter counts the number of attempts of TCH/F handover

of the second sub cell. In the WaitAccess status, when BSC receives the release command, the Um interface assignment completion message or handover completion message, or the message
of waiting for MS access being timeout, if the sub cell ID is 2, the
channel is full-rate channel, and the channel request is due to intra-cell handover, inter-cell handover, external incoming handover,
or internal directed retry, then the counter increments.
Usage
This counter is used to find out the number of attempts of TCH/F

handover of the second sub cell. It helps study the access condition of the second sub cell.
Measurement
Point

status, if the sub cell ID is 2, the channel is full-rate channel,
and the channel request is due to intra-cell handover, intercell handover, external incoming handover, or internal directed
retry, then the counter counts.
channel is full-rate channel, and the channel request is due
to intra-cell handover, inter-cell handover, external incoming
handover, or internal directed retry, then the counter counts.
channel, and the channel request is due to intra-cell handover,
1157
inter-cell handover, external incoming handover, or internal directed retry, then the counter counts.
WaitAccess status, if the sub cell ID is 2, the channel is
full-rate channel, and the channel request is due to intra-cell
handover, inter-cell handover, external incoming handover, or
internal directed retry, then the counter counts.
Unit
Times
TCH/F handover success of
the second sub cell
Description
This counter counts the number of successful TCH/F handovers of

the second sub cell. When BSC receives the release command, the
Um interface assignment completion message or handover completion message, or the message of waiting for MS access being
timeout, if the sub cell ID is 2, the channel is full-rate channel, and
the channel request is due to intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then
Usage
This counter is used to find out the number of successful TCH/F

handovers of the second sub cell. It helps study the access condition of the second sub cell.
Measurement
Point

channel is full-rate channel, and the channel request is due
Unit
1158
Times
TCH/H assignment attempts
Description
This counter counts the number of attempts of TCH/H assignment

completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is half-rate channel,
increments.
Usage
This counter is used to find out the number of attempts of TCH/H

assignment for the second sub cell. It helps study the access condition of the second sub cell.
Measurement
Point

status, if the sub cell ID is 2, the channel is half-rate channel,
counts.
channel is half-rate channel, and the channel request is due to
WaitAccess status, if the sub cell ID is 2, the channel is half-rate
the counter counts.
half-rate channel, and the channel request is due to assignment, then the counter counts.
Unit
Times
Description
This counter counts the number of successful TCH/H assignments

completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is half-rate channel,
increments.
1159
Usage
This counter is used to find out the number of successful TCH/H

assignments for the second sub cell. It helps study the access
condition of the second sub cell.
Measurement
Point

channel is half-rate channel, and the channel request is due to
the counter counts.
Unit
Times
TCH/H handover attempts of
the second sub cell
Description
This counter counts the number of attempts of TCH/H handover

of the second sub cell. In the WaitAccess status, when BSC receives the release command, the Um interface assignment completion message or handover completion message, or the message
of waiting for MS access being timeout, if the sub cell ID is 2, the
channel is half-rate channel, and the channel request is due to intra-cell handover, inter-cell handover, external incoming handover,
or internal directed retry, then the counter increments.
Usage
This counter is used to find out the number of attempts of TCH/H

handover of the second sub cell. It helps study the access condition of the second sub cell.
Measurement
Point

status, if the sub cell ID is 2, the channel is half-rate channel,
and the channel request is due to intra-cell handover, intercell handover, external incoming handover, or internal directed
retry, then the counter counts.
channel is half-rate channel, and the channel request is due
1160
half-rate channel, and the channel request is due to intra-cell

handover, inter-cell handover, external incoming handover, or
internal directed retry, then the counter counts.
Unit
Times
TCH/H handover success of
the second sub cell
Description
This counter counts the number of successful TCH/H handovers of

the second sub cell. When BSC receives the release command, the
Um interface assignment completion message or handover completion message, or the message of waiting for MS access being
timeout, if the sub cell ID is 2, the channel is half-rate channel,
and the channel request is due to intra-cell handover, inter-cell
handover, external incoming handover, or internal directed retry,
Usage
This counter is used to find out the number of successful TCH/H

handovers of the second sub cell. It helps study the access condition of the second sub cell.
Measurement
Point

channel is half-rate channel, and the channel request is due
Unit
Times
C901130069 TCH/F of the

first sub cell seizure success
when prefer the second sub
cell (used for assignment)
Description
This counter counts the number of assigning TCH/F to the first

sub cell when the second sub cell has higher priority (used for assignment). When BSC requests radio resource from DBS, if the
1161
request succeeds and the following conditions are satisfied, the

counter increments: the sub cell selection mode is the second cell
being preferred, the sub cell ID is 1, the channel is full-rate channel, and the channel request is due to assignment.
Usage
This counter is used to find out the number of assigning TCH/F

to the first sub cell when the second sub cell has higher priority
(used for assignment). It helps study the access condition of the
first sub cell when the second sub cell has higher priority.
Measurement
Point
Unit
In the RadioApply status, when BSC requests radio resource from

DBS, if the request succeeds and the following conditions are satisfied, the counter counts: the sub cell selection mode is the second
cell being preferred, the sub cell ID is 1, the channel is full-rate
channel, and the channel request is due to assignment.
Times
C901130070 TCH/F of the

cell (used for handover)
Description
This counter counts the number of assigning TCH/F to the first

sub cell when the second sub cell has higher priority (used for
handover). When BSC requests radio resource from DBS, if the
being preferred, the sub cell ID is 1, the channel is full-rate channel, and the channel request is due to handover.
Usage
This counter is used to find out the number of assigning TCH/F to

the first sub cell when the second sub cell has higher priority (used
for handover). It helps study the access condition of the first sub
cell when the second sub cell has higher priority.
Measurement
Point
Unit
1162

cell being preferred, the sub cell ID is 1, the channel is full-rate
channel, and the channel request is due to handover.
Times
C901130071 TCH/H of the

cell (used for assignment)
Description
This counter counts the number of assigning TCH/H to the first

sub cell when the second sub cell has higher priority (used for assignment). When BSC requests radio resource from DBS, if the
being preferred, the sub cell ID is 1, the channel is half-rate channel, and the channel request is due to assignment.
Usage
This counter is used to find out the number of assigning TCH/H

to the first sub cell when the second sub cell has higher priority
(used for assignment). It helps study the access condition of the
first sub cell when the second sub cell has higher priority.
Measurement
Point
Unit

cell being preferred, the sub cell ID is 1, the channel is half-rate
channel, and the channel request is due to assignment.
Times
C901130072 TCH/H of the

cell (used for handover)
Description
This counter counts the number of assigning TCH/H to the first

sub cell when the second sub cell has higher priority (used for
handover). When BSC requests radio resource from DBS, if the
being preferred, the sub cell ID is 1, the channel is half-rate channel, and the channel request is due to handover.
Usage
This counter is used to find out the number of assigning TCH/H to

the first sub cell when the second sub cell has higher priority (used
for handover). It helps study the access condition of the first sub
cell when the second sub cell has higher priority.
1163
Measurement
Point
Unit

cell being preferred, the sub cell ID is 1, the channel is half-rate
channel, and the channel request is due to handover.
Times
C901130073 Number
of Inter-Cell Handover
Attempts to the Second Sub
Cell Directly From the Cell in
the Same Site
Description
This counter counts the inter-cell handover attempts that occur to

hand over an MS to subcell 2 of the cell from another cell in the
same site.
Usage
This counter indicates the number of inter-cell handover attempts

that occur to hand over an MS to subcell 2 of the cell from another
cell in the same site.
Measurement
Point
This counter is incremented when channel assignment in subcell 2

of the cell is determined.
Unit
Times
C901130074 Number
Execution to the Second
Sub Cell Directly From the
Cell in the Same Site
1164
Description
This counter counts the times that an inter-cell handover is performed to hand over an MS to subcell 2 of the cell from another
cell in the same site.
Usage
This counter indicates the number of times that an inter-cell handover is performed to hand over an MS to subcell 2 of the cell from
another cell in the same site.
Measurement
Point
Unit
This counter is incremented when the assigned channel in subcell

2 of the cell is activated.
Times
Inter-Cell Handover Success
to the Second Sub Cell
Directly From the Cell in the
Same Site
Description
This counter counts successful inter-cell handovers from a cell in

the same site to subcell 2 of the cell.
Usage
This counter indicates the number of successful inter-cell handovers from a cell in the same site to subcell 2 of the cell.
Measurement
Point
This counter is incremented when a HANDOVER COMPLETE message is received through the assigned channel in subcell 2 of the
cell.
Unit
Times
C901130076 Number
Attempts to the Second Sub
Cell Directly From Another
Site
Description

hand over an MS to subcell 2 of the cell from a cell in another site
controlled by the same BSC.
Usage

that occur to hand over an MS to subcell 2 of the cell from a cell
in another site controlled by the same BSC.
Measurement
Point

Unit
Times
1165
C901130077 Number
Execution to the Second
Sub Cell Directly From
Another Site
Description
This counter counts the times that an inter-cell handover is performed to hand over an MS from a cell in another site (controlled
by the same BSC) to subcell 2 of the cell.
Usage
This counter indicates the number of inter-cell handovers that

hand over an MS to subcell 2 of the cell from a cell in another site
controlled by the same BSC.
Measurement
Point

Unit
Times
Inter-Cell Handover Success
to the Second Sub Cell
Directly From Another Site
Description
This counter counts successful inter-cell handovers that hand over

an MS to subcell 2 of the cell from a cell in another site controlled
by the same BSC.
Usage
This counter indicates the number of successful inter-cell handovers that hand over an MS to subcell 2 of the cell from a cell
in another site controlled by the same BSC.
Measurement
Point
cell.
Unit
1166
Times
Handover Attempts to the
Second Sub Cell Directly
From Another BSC
Description

hand over an MS to subcell 2 of the cell from a cell controlled by
another BSC.
Usage

that occur to hand over an MS to subcell 2 of the cell from a cell
controlled by another BSC.
Measurement
Point

Unit
Times
Handover Execution to the
From Another BSC
Description
This counter counts the times that an inter-cell handover is performed to hand over an MS from a cell controlled by another BSC
to subcell 2 of the cell.
Usage
This counter indicates the number of inter-cell handovers that

hand over an MS to subcell 2 of the cell from a cell controlled by
another BSC.
Measurement
Point

Unit
Times
1167
Handover Success to the
From Another BSC
Description
This counter counts successful inter-cell handovers that hand over

an MS to subcell 2 of the cell from a cell controlled by another BSC.
Usage
This counter indicates the number of successful inter-cell handovers that hand over an MS to subcell 2 of the cell from a cell
controlled by another BSC.
Measurement
Point
cell.
Unit
Times
Handover to the First Sub
Cell Too Fast After Handover
From Another Cell in the
Same Site
Description
This counter indicates the number of times that an MS is handed

over to subcell 1 soon after being handed over to subcell 2 of the
cell from another cell in the same site.
Usage
This counter indicates the number of inter-subcell handovers that

are carried out to hand over an MS from subcell 2 to subcell 1
soon after the MS is handed over to subcell 2 of the cell from
another cell in the same site. It is a reference for revising handover
parameters.
Measurement
Point
This counter is incremented when an inter-subcell handover is decided.
Unit
1168
Times
Handover to the Second
Sub Cell Too Fast After
Handover From Another Cell
in the Same Site
Description

cell from another cell in the same site.
Usage

soon after the MS is handed over to subcell 1 of the cell from
another cell in the same site. It is a reference for revising handover
parameters.
Measurement
Point
Unit
Times
Handover to the First Sub
From Another Site
Description

cell from a cell in another site.
Usage

soon after the MS is handed over to subcell 2 of the cell from a
cell in another site controlled by the same BSC. It is a reference
for revising handover parameters.
Measurement
Point
Unit
Times
1169
Handover to the Second Sub
From Another Site
Description

cell from a cell in another site.
Usage

soon after the MS is handed over to subcell 1 of the cell from a
cell in another site controlled by the same BSC. It is a reference
for revising handover parameters.
Measurement
Point
Unit
1170
Times
Chapter
20
MS TA Measurement
Table of Contents
Overview...................................................................... 1171
C901140001 Number of TA=0 ......................................... 1172
C901140002 Number of 0<TA<= 2.................................. 1172
C901140003 Number of 2<TA<=4................................... 1173
C901140004 Number of 4<TA<=6................................... 1173
C901140005 Number of 6<TA<=8................................... 1174
C901140006 Number of 8<TA<=10 ................................. 1174
C901140007 Number of 10<TA<=12 ............................... 1175
C901140008 Number of 12<TA<=14 ............................... 1176
C901140009 Number of 14<TA<=16 ............................... 1176
C901140010 Number of 16<TA<=18 ............................... 1177
C901140011 Number of 18<TA<=20 ............................... 1177
C901140012 Number of 20<TA<=22 ............................... 1178
C901060013 Number of 22<TA<=24 ............................... 1178
C901140014 Number of 24<TA<=26 ............................... 1179
C901140015 Number of 26<TA<=28 ............................... 1180
C901140016 Number of 28<TA<=30 ............................... 1180
C901140017 Number of 30<TA<=32 ............................... 1181
C901140018 Number of 32<TA<=34 ............................... 1181
C901140019 Number of 34<TA<=36 ............................... 1182
C901140020 Number of 36<TA<=38 ............................... 1183
C901140021 Number of 38<TA<=40 ............................... 1183
C901140022 Number of 40<TA<=42 ............................... 1184
C901140023 Number of 42<TA<=44 ............................... 1184
C901140024 Number 44<TA<=46 ................................... 1185
C901140025 Number of 46<TA<=48 ............................... 1186
C901140026 Number of 48<TA<=50 ............................... 1186
C901140027 Number of 50<TA<=52 ............................... 1187
C901140028 Number of 52<TA<=54 ............................... 1187
C901140029 Number of 54<TA<=56 ............................... 1188
C901140030 Number of 56<TA<=58 ............................... 1189
C901140031 Number of 58<TA<=60 ............................... 1189
C901140032 Number of 60<TA<=63 ............................... 1190
C901140033 Number of TA>63 ....................................... 1190
Overview
MS TA counters are used to check the value of TA in MS measurement reports. TA can reflect the relative location of MS in the cell.
If most of the TAs are in very high level, network planning should
be remade, such as, increasing the site density.
1171
TA=0
Description
This counter counts the number of times of TA=0 in the MS measurement reports.
Usage
This counter is used to find out the frequency of TA=0 in the MS

measurement reports. It can be one of the parameters that are
used to evaluate the cell radio environment.
Measurement
Point
This counter increments when BSC receives the MS measurement

report with TA=0. The measurement point is A, as shown in Figure
1154.
FIGURE 1154 MS MEASUREMENT REPORT
Unit
Times
0<TA<= 2
Definition
Description
Number of 0<TA<= 2
This counter counts the number of times of 0<TA<=2.
Usage
This counter is used to find out the frequency of 0<TA<=2 in the

MS measurement reports. It can be one of the parameters that
are used to evaluate the cell radio environment.
Measurement
Point

report with 0<TA<=2. The measurement point is A, as shown in
Figure 1155.
1172
Chapter 20 MS TA Measurement
Unit
Times
2<TA<=4
Definition
Number of 2<TA<=4.
Description
This counter counts the number of times of 2<TA<=4 in the MS

measurement reports.
Usage

Measurement
Point

report with 2<TA<=4. The measurement point is A, as shown
inFigure 1156.
FIGURE 1156 - MS MEASUREMENT REPORT
Unit
Times
4<TA<=6
Definition
Number of 4<TA<=6.
Description

Usage

Measurement
Point

Figure 1157.
1173
Unit
Times
6<TA<=8
Definition
Number of 6<TA<=8.
Description

Usage

Measurement
Point

Figure 1158.
Unit
Times
8<TA<=10
Definition
Description
1174
Number of 8<TA<=10.
Usage

Measurement
Point

Figure 1159.
Unit
Times
10<TA<=12
Definition
Number of 10<TA<=12.
Description

Usage
This counter is used to find out the frequency of 10<TA<=12 in

the MS measurement reports. It can be one of the parameters
that are used to evaluate the cell radio environment.
Measurement
Point

in Figure 1160.
Unit
Times
1175
12<TA<=14
Description

Usage

Measurement
Point

in Figure 1161.
Unit
Times
14<TA<=16
Description

Usage

Measurement
Point

in Figure 1162.
Unit
1176
Times
16<TA<=18
Definition
Description

Usage

Measurement
Point

in Figure 1163.
Unit
Times
18<TA<=20
Definition
Description

Usage

Measurement
Point

in Figure 1164.
1177
Unit
Times
20<TA<=22
Definition
Description

Usage

Measurement
Point

in Figure 1165.
Unit
Times
22<TA<=24
Definition
Description
1178
Usage

Measurement
Point

in Figure 1166.
Unit
Times
24<TA<=26
Definition
Description

Usage

Measurement
Point

in Figure 1167.
Unit
Times
1179
26<TA<=28
Definition
Description

Usage

Measurement
Point

in Figure 1168.
Unit
Times
28<TA<=30
Definition
1180
Description

Usage

Measurement
Point

in Figure 1169.
Unit
Times
30<TA<=32
Definition
Description

Usage

Measurement
Point

in Figure 1170.
Unit
Times
32<TA<=34
Definition
Description
1181
Usage

Measurement
Point

in Figure 1171.
Unit
Times
34<TA<=36
Definition
Description

Usage

Measurement
Point

in Figure 1172.
Unit
1182
Times
36<TA<=38
Definition
Description

Usage

Measurement
Point

in Figure 1173.
Unit
Times
38<TA<=40
Definition
Number of 38<TA<=40
Description

Usage

Measurement
Point

in Figure 1174.
1183
Unit
Times
40<TA<=42
Definition
Description

Usage

Measurement
Point

in Figure 1175.
Unit
Times
42<TA<=44
Definition
Description
1184
Usage

Measurement
Point

in Figure 1176.
Unit
Times
C901140024 Number
44<TA<=46
Definition
Description

Usage

Measurement
Point

in Figure 1177.
Unit
Times
1185
46<TA<=48
Definition
Description

Usage

Measurement
Point

in Figure 1178.
Unit
Times
48<TA<=50
Definition
1186
Description

Usage

Measurement
Point

in Figure 1179.
Unit
Times
50<TA<=52
Definition
Description

Usage

Measurement
Point

in Figure 1180.
Unit
Times
52<TA<=54
Definition
Description
1187
Usage

Measurement
Point

in Figure 1181.
Unit
Times
54<TA<=56
Definition
Description

Usage

Measurement
Point

in Figure 1182.
Unit
1188
Times
56<TA<=58
Definition
Description

Usage

Measurement
Point

in Figure 1183.
Unit
Times
58<TA<=60
Definition
Number of 58<TA<=60
Description

Usage

Measurement
Point

in Figure 1184.
1189
Unit
Times
60<TA<=63
Definition
Description

Usage

Measurement
Point

in Figure 1185.
Unit
Times
TA>63
Definition
Description
1190
Number of TA > 63
This counter counts the number of times of TA>63 in the MS measurement reports.
Usage
This counter is used to find out the frequency of TA>63 in the MS

measurement reports. It can be one of the parameters that are
used to evaluate the cell radio environment.
Measurement
Point

report with TA>63. The measurement point is A, as shown in
Figure 1186.
Unit
Times
1191
1192
Chapter
21
SAPI3 Measurement
Table of Contents
Overview...................................................................... 1194
SACCH/F (MO-SM)......................................................... 1194
SACCH/H (MO-SM) ........................................................ 1195
FACCH/F (MO-SM) ......................................................... 1196
FACCH/H (MO-SM)......................................................... 1197
SACCH/F (MT-SM) ......................................................... 1197
SACCH/H (MT-SM)......................................................... 1198
FACCH/F (MT-SM).......................................................... 1199
FACCH/H (MT-SM) ......................................................... 1200
C901150011 Number of successful SAPI3 link establishments
on SACCH/F (MT-SM)..................................................... 1200
on SACCH/H (MT-SM) .................................................... 1201
on FACCH/F (MT-SM) ..................................................... 1202
on FACCH/H (MT-SM)..................................................... 1203
C901150016 Number of DTAP messages used as SDCCH UL
point-to-point short messages (SMs)................................ 1203
C901150017 Number of DTAP messages used as SDCCH DL
point-to-point short messages (SMs)................................ 1205
C901150018 Number of DTAP messages on FACCH/F UL for
point-to-point short messages......................................... 1207
C901150019 Number of DTAP messages on FACCH/F DL for
C901150020 Number of DTAP messages on FACCH/H UL for
C901150021 Number of DTAP messages on FACCH/H DL for
C901150022 Number of DTAP messages on SACCH/F DL for
C901150023 Number of DTAP messages on SACCH/F DL for
C901150024 Number of DTAP messages on SACCH/H UL for
C901150025 Number of DTAP messages on SACCH/H DL for
1193
Overview
MO-SM is short message of mobile originating call; MT-SM is short
messages of mobile terminating call. In conversation status, the
MS can receive point-to-point message so the mobile caller maybe
the other side of receiving short message at one time. On the
wireless side, short message could be transmitted by the following
five channels: SACCH/F, SACCH/H, SDCCH, FACCHF, and FACCHH.
So far the statistics counting has been realized by the channel of
SACCH/F, SACCH/H and SDCCH.
SAPI3 link establishments
on SACCH/F (MO-SM)
Definition
1194
Number of SAPI3 link establishments on SACCH/F (MO-SM)
Description
This counter counts the number of short message link establishment of mobile originating call through SACCH/F. On SDCCH/F,
BSC receives EST_IND message sent by BTS. If the layer 3 information in this message is SAPI=3, the counter increments.
Usage
This counter is used to find out the frequency of SAPI3 link establishments on SACCH/F.
Measurement
Point
This counter counts the number of BSC receiving EST_IND message

sent by BTS with SAPI=3. The measurement point is A, as shown
inFigure 1187.
Chapter 21 SAPI3 Measurement
FIGURE 1187 - FLOW
Unit
Related Features
OF
MO SHORT MESSAGES
DURING
CONVERSATION
Times
on SACCH/H (MO-SM)
Definition
Number of SAPI3 link establishments on SACCH/H (MO-SM)
Description
This counter counts the number of short message link establishment of mobile originating call through SACCH/H. On SDCCH/H,
Usage
This counter is used to find out the frequency of SAPI3 link establishments on SACCH/H.
Measurement
Point
This counter counts the number of BSC receiving EST_IND message sent by BTS with SAPI=3. The measurement point is A1, as
1195
FIGURE 1188 - FLOW
Unit
Related Features
OF
MO SHORT MESSAGES
DURING
CONVERSATION
Times
on FACCH/F (MO-SM)
Definition
Description
This counter counts the number of short message link establishment of mobile originating call through FACCH/F. On FACCH/F, BSC
receives EST_IND message sent by BTS. If the layer 3 information
in this message is SAPI=3, the counter increments.
Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/F.
Measurement
Point
Unit
Related Features
1196
Number of SAPI3 link establishments on FACCH/F (MO-SM)
This counter is not realized at present in the system.

Times
on FACCH/H (MO-SM)
Definition
Number of SAPI3 link establishments on FACCH/H (MO-SM)
Description
This counter counts the number of short message link establishment of mobile originating call through FACCH/H. On FACCH/H,
Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/H.
Measurement
Point
Unit
Related Features

Times
requests on SACCH/F
(MT-SM)
Definition
Number of SAPI3 link establishments on SACCH/F (MT-SM)
Description
This counter counts the number of short message link establishment of mobile originating call through SACCH/F. On SDCCH/F, if
BSC receives DTAP_IND message sent by MSC with SAPI=3 while the
initiates link establishment flow and the counter increments.
Usage
This counter is used to find out the frequency of SAPI3 link establishment requests on SACCH/F.
Measurement
Point
This counter counts the number of BSC sending EST_REQ message

to BTS with SAPI=3 while the short message link between BSC and
MS is not established. The measurement point is C1, as shown in
Figure 1189.
1197
FIGURE 1189 - FLOW
Unit
Related Features
OF
MT SHORT MESSAGE
DURING
CONVERSATION
Times
requests on SACCH/H
(MT-SM)
Definition
1198
Number of SAPI3 link establishments on SACCH/H (MT-SM)
Description
This counter counts the number of short message link establishment of mobile originating call through SACCH/H. On SACCH/H, if
Usage
This counter is used to find out the frequency of SAPI3 link establishment requests on SACCH/H.
Measurement
Point
This counter counts the number of BSC sending EST_REQ message

to BTS with SAPI=3 while the short message link between BSC and
MS is not established. The measurement point is C1, as shown in
Figure 1190.
FIGURE 1190 - FLOW
Unit
Related Features
OF
MT SHORT MESSAGE
DURING
CONVERSATION
Times
requests on FACCH/F
(MT-SM)
Definition
Number of SAPI3 link establishments on FACCH/F (MT-SM)
Description
This counter counts the number of short message link establishment of mobile terminating call through FACCH/F. On FACCH/F,
BSC receives DTAP_IND message sent by MSC with SAPI=3 while
the short message link between BSC and MS is not established,
BSC initiates link establishment flow and the counter increments.
Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/F.
Measurement
Point
Unit

Times
1199
Related Features
requests on FACCH/H
(MT-SM)
Definition
Number of SAPI3 link establishments on FACCH/H (MT-SM)
Description
This counter counts the number of short message link establishment of mobile terminating call through FACCH/H. On FACCH/H,
Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/H.
Measurement
Point
Unit
Related Features

Times
successful SAPI3 link
establishments on SACCH/F
(MT-SM)
1200
Definition
Number of successful SAPI3 link establishments on SACCH/F (MTSM)
Description
This counter counts the number of successful short message

link establishment of mobile terminating call through SACCH/F.
On SACCH/F, if BSC receives EST_CONF message sent by BTS
after it initiates short message link establishment flow, this link
establishment succeeds, and the counter increments.
Usage
This counter is used to find out the frequency of successful SAPI3

link establishments on SACCH/F.
Measurement
Point
This counter counts the number of BSC receiving EST_IND message

send by BTS with SAPI=3. The measurement point is C2, as shown
in Figure 1191.
FIGURE 1191 - FLOW
Unit
Related Features
OF
MT SHORT MESSAGE
DURING
CONVERSATION
Times
establishments on SACCH/H
(MT-SM)
Definition
Number of SAPI3 link establishments on SACCH/H (MT-SM)
Description
This counter counts the number of short message link establishment of mobile terminating call through SACCH/H. On SDCCH/H,
if BSC receives EST_CONF message sent by BTS after it initiates short
message link establishment flow, this link establishment succeeds,
and the counter increments.
Usage
This counter is used to find out the frequency of SAPI3 link establishment requests on SACCH/H.
Measurement
Point
This counter counts the number of BSC sending EST_CONF message

send by BTS with SAPI=3 while the short message link between
BSC and MS is not established. The measurement point is C2, as
shown inFigure 1192 .
1201
FIGURE 1192 - FLOW
Unit
Related Features
OF
MT SHORT MESSAGE
DURING
CONVERSATION
Times
establishments on FACCH/F
(MT-SM)
Definition
Number of successful SAPI3 link establishments on FACCH/F (MTSM)
Description

establishment of mobile terminating call through FACCH/F. On
FACCH/F, if BSC receives EST_CONF message sent by BTS after it
initiates short message link establishment flow, this link establishment succeeds, and the counter increments.
Usage
This counter is used to find out the frequency of SAPI3 link establishment requests on SACCH/F.
Measurement
Point
Unit
1202

Times
Related Features
establishments on FACCH/H
(MT-SM)
Definition
Number of successful SAPI3 link establishments on FACCH/H (MTSM)
Description

establishment of mobile terminating call through FACCH/H. On
FACCH/H, if BSC receives EST_CONF message sent by BTS after it
initiates short message link establishment flow, this link establishment succeeds, and the counter increments.
Usage
This counter is used to find out the frequency of successful SAPI3

link establishments on FACCH/H.
Measurement
Point
Unit
Related Features

Times
DTAP messages used as
SDCCH UL point-to-point
short messages (SMs)
Definition
Number of DTAP messages used as SDCCH UL point-to-point short

messages (SMs)
Description
This counter counts the number of DTAP packet sent by MS to the

network side through SDCCH.
Usage
This counter is used to find out the frequency of DTAP message of

point-to-point message on SDCCH UL.
Measurement
Point
This counter counts the number of BSC receiving DTAP packet sent
by BTS on SDCCH with SAPI=3. The measurement points are D4
and D5 as shown inFigure 1193 , and B2 and B5 as shown inFigure
1194 .
1203
FIGURE 1193 - FLOW
1204
OF
MT SHORT MESSAGE
IN
IDLE STATUS
FIGURE 1194 - FLOW
Unit
Related Features
OF
MO SHORT MESSAGE
IN
IDLE STATUS
Times
DTAP messages used as
SDCCH DL point-to-point
short messages (SMs)
Definition
Number of DTAP messages used as SDCCH DL point-to-point short

messages (SMs)
Description
This counter counts the number of DTAP packet sent by network

to MS through SDCCH .
Usage

point-to-point message on SDCCH DL.
1205
Measurement
Point
This counter counts the number of BSC receiving DTAP packet

toBTS on SDCCH with SAPI=3. The measurement points are D3
and D6 as shown inFigure 1195 , and B3 and B4 as shown in Figure
1196.
FIGURE 1195 - FLOW
1206
OF
MT SHORT MESSAGE
IN
IDLE STATUS
FIGURE 1196 - FLOW
Unit
Related Features
OF
MO SHORT MESSAGE
IN
IDLE STATUS
Times
C901150018 Number
of DTAP messages
on FACCH/F UL for
point-to-point short
messages
Definition
Number of DTAP messages on FACCH/F UL for point-to-point short

messages
Description
This counter counts the number of DTAP packet sent by MS to

network side through FACCH/F.
1207
Usage
Measurement
Point
Unit
Related Features

point-to-point short messages on FACCH/F UL.
Times
C901150019 Number
of DTAP messages
on FACCH/F DL for
messages
Definition
Number of DTAP messages on FACCH/F DL for point-to-point short

messages.
Description
This counter counts the number of DTAP packet of short messages

sent by network side to MS through FACCH/F.
Usage

point-to-point short messages on FACCH/F UL.
Measurement
Point
Unit
Related Features

Times
C901150020 Number
of DTAP messages
on FACCH/H UL for
messages
1208
Definition
Number of DTAP messages on FACCH/H UL for point-to-point short

messages.
Description

sent by MS to network side through FACCH/H.
Usage
Measurement
Point
Unit
Related Features

point-to-point short messages on FACCH/H UL.
Times
C901150021 Number
of DTAP messages
on FACCH/H DL for
messages
Definition
Number of DTAP messages on FACCH/H DL for point-to-point short

messages.
Description

sent by network side to MS through FACCH/H.
Usage

point-to-point short messages on FACCH/H DL.
Measurement
Point
Unit
Related Features

Times
C901150022 Number
of DTAP messages
on SACCH/F DL for
messages
Definition
Number of DTAP messages on SACCH/F UL for point-to-point short

messages.
Description

sent by network side to MS through SACCH/F.
1209
Usage
This counter is used to find out the frequency of point-to-point

DTAP message of point-to-point short messages on SACCH/F UL.
Measurement
Point
by BTS on SDCCH with SAPI=3. The measurement points are C4
and C5 as shown in Figure 1197, and A2 and A5 as shown inFigure
1198 .
FIGURE 1197 - FLOW
1210
OF
MT SHORT MESSAGE
DURING
CONVERSATION
FIGURE 1198 - FLOW
Unit
Related Features
OF
MO SHORT MESSAGES
DURING
CONVERSATION
Times
C901150023 Number
of DTAP messages
on SACCH/F DL for
messages
Definition
Number of DTAP messages on SACCH/F DL for point-to-point short

messages.
Description

sent by network side to MS through SACCH/F.
Usage

point-to-point short messages on SACCH/F DL.
1211
Measurement
Point
Unit
Related Features

Times
C901150024 Number
of DTAP messages
on SACCH/H UL for
messages
1212
Definition
Number of DTAP messages on SACCH/H UL for point-to-point short

messages
Description
This counter counts the number of DTAP packet sent by MS to

network side through SACCH/H.
Usage

point-to-point short messages on SACCH/H UL.
Measurement
Point
by BTS on SDCCH with SAPI=3. The measurement points are C4
and C5 as shown inFigure 1199 , and A2 and A5 as shown in Figure
1200.
FIGURE 1199 - FLOW OF MT SHORT MESSAGE DURING CONVERSATION
FIGURE 1200 - FLOW OF MO SHORT MESSAGES DURING CONVERSATION
1213
Unit
Related Features
Times
C901150025 Number
of DTAP messages
on SACCH/H DL for
messages
Definition
Number of DTAP messages on SACCH/H DL for point-to-point short

messages.
Description

sent by network side to MS through SACCH/H.
Usage

point-to-point short messages on SACCH/H DL.
Measurement
Point
This counter counts the number of BSC sending DTAP packet to

BTS on SACCH/H withSAPI=3. The measurement points are C3
and C6 as shown in Figure 1201, and A3 and A4 as shown inFigure
1202.
FIGURE 1201 - FLOW
1214
OF
MT SHORT MESSAGE
DURING
CONVERSATION
FIGURE 1202 - FLOW
Unit
Related Features
OF
MO SHORT MESSAGES
DURING
CONVERSATION
Times
1215
1216
Chapter
22
Uplink and Downlink

PACCH Statistics
Table of Contents
Overview...................................................................... 1218
C901160001 Number of Packet access reject message......... 1218
C901160002 Number of Packet resource request message ............................................................................ 1219
C901160003 Number of Packet UL Assignment message ............................................................................ 1219
C901160004 Number of Additional MS access capabilities
message ...................................................................... 1220
C901160005 Number of Packet DL Assignment message ............................................................................ 1221
C901160006 Number of Packet TBF release message ......... 1222
C901160007 Number of Packet DL Ack/Nack message......... 1223
C901160008 Number of EGPRS Packet DL Ack/Nack message ............................................................................ 1224
C901160009 Number of Packet UL Ack/Nack message......... 1225
C901160010 Number of Packet Control Acknowledgement
message ...................................................................... 1226
C901160011 Number of Packet Cell Change Continue message ............................................................................ 1227
C901160012 Number of Packet Cell Change Failure message ............................................................................ 1229
C901160013 Number of Packet Cell Change Notification message ............................................................................ 1229
C901160014 Number of Packet Cell Change Order message ............................................................................ 1230
C901160017 Number of packet mobile TBF status messages........................................................................... 1231
C901160018 Number of packet neighbor cell data messages........................................................................... 1232
C901160019 Number of packet PDCH release messages........................................................................... 1233
C901160020 Number of packet polling request messages........................................................................... 1233
C901160021 Number of packet power control/timing advance
messages ..................................................................... 1234
C901160022 Number of packet PSI status message ........... 1235
C901160023 Number of packet serving cell data messages........................................................................... 1236
C901160024 Number of packet SI status messages ........... 1237
C901160025 Number of packet timeslot reconfigure messages........................................................................... 1238
C901160026 Number of packet paging request message ............................................................................ 1239
1217
C901160027 Number of PSI message............................... 1240
Overview
In transmitting GPRS data service, UL and DL PACCH statistics is
used to count the number of receiving and sending controlled messages on PACCH, including packet access reject, packet resource
request, packet UL assignment, and so on.
C901160001 Number
of Packet access reject
message
Definition
Description
Number of Packet access reject message

When MS sends packet resource request to BSC through BTS, BSC
will return packet UL assignment to MS or packet access reject on
PACCH.
This counter counts the number of BSC sending the packet access
reject messages on PACCH.
Usage
This counter is used to check the packet access reject messages

sent by BSC in packet transmission mode.
Measurement
Point
When the UPPB of BSC sends packet access reject messages to

MS, the counter increments. The measurement point is A2, as
FIGURE 1203 - MEASUREMENT POINT
PACKET ACCESS REJECT
Unit
1218
OF
Times
PACKET RESOURCE REQUEST
AND
Chapter 22 Uplink and Downlink PACCH Statistics
Packet resource request
message
Definition
Description
Number of Packet access reject message

When MS sends packet resource request to BSC through BTS, BSC
will return packet UL assignment to MS or packet access reject on
PACCH.
This counter counts the number of BSC sending the packet access
reject messages on PACCH.
Usage

Measurement
Point
When the UPPB of BSC receives packet resource request messages, the counter increments. The measurement point is A1, as
PACKET ACCESS REJECT
Unit
OF
PACKET RESOURCE REQUEST
AND
Times
Packet UL Assignment
message
Definition
Description
Number of Packet UL Assignment message

Packet UL assignment can be sent on both PCCCH and PACCH.
When established for TBF double steps, the first packet UL assignment needs to be sent on PCCH, other packet UL assignments such
as DL TBF or resource redistribution initiated by MS will be sent on
PACCH by BSC.
1219
This counter counts the number of packet UL assignment messages sent by BSC on PACCH.
Measurement
Point
When the type of DL control block sent by BSC is packet UL assignment, the counter increments. The measurement point is A,
FIGURE 1205 - MEASUREMENT
Unit
OF
PACKET UL ASSIGNMENT MESSAGE
Times
Additional MS access
capabilities message
Definition
1220
Number of Additional MS access capabilities messages.
Description
This counter counts the number of additional MS access capabilities messages received by BSC on PACCH in packet transmission
mode.
Usage

Measurement
Point
When the type of UL control block received by BSC is additional

MS access capabilities, the counter increments. The measurement
FIGURE 1206 - MEASUREMENT POINT OF ADDITIONAL MS ACCESS

CAPABILITIES MESSAGE
Unit
Times
Packet DL Assignment
message
Definition
Number of packet DL assignment messages.
Description
This counter counts the number of packet DL assignment messages sent by BSC on PACCH in packet transmission mode.
Measurement
Point
When the type of DL control block sent by BSC is packet DL assignment, the counter increments. The measurement point is A,
as shown inFigure 1207 .
1221
FIGURE 1207 - DL SENT
Unit
ON
PACCH
IN
PACKET TRANSMISSION MODE
Times
C901160006 Number
of Packet TBF release
message
Definition
1222
Number of packet TBF release messages
Description
This counter counts the number of packet TBF release messages

on PACCH sent by BSC.
Measurement
Point
When the type of DL control block sent by BSC is packet TBF release, the counter increments. The measurement point is A, as
shown inFigure 1208.
Unit
ON
PACCH
IN
Times
C901160007 Number
of Packet DL Ack/Nack
message
Definition
Description
Number of packet DL Ack/Nack messages.

After TBF is established and DL RLC set RRBP on sending data
block, MS sends packet DL Ack/Nack messages on PACCH.
This counter counts the number of packet DL Ack/Nack messages
received by BSC on PACCH in packet transmission mode.
Measurement
Point
When the type of UL control block sent by BSC is packet DL

Ack/Nack, the counter increments. The measurement points are
A, A1, as shown inFigure 1209 .
1223
Unit
ON
PACCH IN PACKET TRANSMISSION MODE
Times
EGPRS Packet DL Ack/Nack
message
Definition
Description
Number of EGPRS Packet DL Ack/Nack messages.

After TBF is established and DL RLC set RRBP on sending data
block, MS sends packet DL Ack/Nack messages on PACCH.
This counter counts the number of EGPRS packet DL Ack/Nack
messages received by BSC on PACCH in EGPRS packet transmission mode.
Measurement
Point
1224
When the type of UL control block sent by BSC is EGPRS packet DL

Ack/Nack, the counter increments. The measurement points are
A and A1, as shown inFigure 1210.
Unit
ON
PACCH
IN
Times
C901160009 Number
of Packet UL Ack/Nack
message
Definition
Number of Packet UL Ack/Nack message
Description
This counter counts the number of packet UL Ack/Nack messages

sent by BSC on PACCH in packet transmission mode.
Measurement
Point
When the type of DL control block sent by BSC is packet UL

Ack/Nack, the counter increments. The measurement point is A,
1225
FIGURE 1211 - SIGNALING TRANSMISSION
Unit
ON
PACCH
Times
C901160010 Number
of Packet Control
Acknowledgement message
Definition
1226
Number of Packet Control Acknowledgement message
Description
This counter counts the number of packet control acknowledgement messages received by BSC on PACCH in packet transmission
mode.
Measurement
Point
When the type of UL control block received by BSC is packet control acknowledgement, the counter increments. The measurement
point is B, as shown inFigure 1212.
FIGURE 1212 - SIGNALING TRANSMISSION
Unit
ON
PACCH
Times
C901160011 Number
of Packet Cell Change
Continue message
Definition
Description
Number of Packet Cell Change Continue message

If MS intends to handoff from service cell to destination cell, it will
initiate packet cell change notification to BSC to request the system message of destination under the condition that the network
and MS support NACC.
After BSC receives packet cell change messages, it will send
packet cell change continues messages to MS on PACCH or packet
cell changes command to inform MS to switch to the new cell.
This counter counts the number of packet cell change continues
messages sent by BSC on PACCH.
Measurement
Point
BSC initiates timer after receiving PACKET NEIGHBOR CELL CHANGE NOTIIf it receives the packet system message of destination
cell in the defined time, BSC send PACK NEIGHBOR CELL DATA, then
send PACKET CELL CHANGE CONTINUES, the counter increments. The
measurement point is A3, as shown inFigure 1213.
FICATION.
1227

COUNTER (I)
OF
PACKET-CELL-CHANGE-RELATED
BSC initiates timer after receiving the PACKET NEIGHBOR CELL CHANGE
NOTIFICATION message. If timer times out and doesnt receive the
packet system message of destination cell, BSC sends the PACK
CELL CHANGE CONTINUE message directly, the counter increments. The
measurement point is A1, as shown inFigure 1214 .
COUNTER (II)
Unit
1228
OF
Times
Packet Cell Change Failure
message
Definition
Description
Number of Packet Cell Change Failure message

After BSC sends packet cell change command to MS, BTS initiates
packet cell change failure to BSC to indicate that the cell fails to
change command.
This counter counts the number of packet cell change failure messages received by BSC on PACCH in packet transmission mode.
Measurement
Point
When the type of UL control block sent by BSC is packet cell change
failure, the counter increments. The measurement point is A3, as
FIGURE 1215 - MEASUREMENT POINT OF
AND PACKET CELL CHANGE FAILURE
Unit
PACKET CELL CHANGE ORDER
Times
C901160013 Number
of Packet Cell Change
Notification message
Definition
Number of Packet Cell Change Notification messages.
1229
Description
If MS intends to handoff from service cell to destination cell, it will

initiate packet cell change notification to BSC to request the system message of destination under the condition that the network
and MS support NACC.
This counter counts the number of packet cell change notification
messages received by BSC on PACCH in packet transmission mode.
Measurement
Point
When the type of UL control block received by BSC is packet cell

change notification, the counter increments. The measurement
point is A1, as shown inFigure 1216.
COUNTER (I)
Unit
OF
Times
Packet Cell Change Order
message
Definition
1230
Number of Packet Cell Change Order message
Description
When the MS initiates the packet cell change notification, this

counter counts the number of packet cell change order messages
Measurement
Point
When BSC sends packet cell change order messages, the counter
increments. The measurement point is A2, as shown inFigure
1217.
FIGURE 1217 - MEASUREMENT POINT OF

AND PACKET CELL CHANGE FAILURE
Unit
PACKET CELL CHANGE ORDER
Times
packet mobile TBF status
messages
Definition
Number of packet mobile TBF status messages
Description
This counter counts the number of packet mobile TBF status messages sent by BSC on PACCH in packet service.
Measurement
Point
When the type of UL control block received by BSC is packet mobile TBF, the counter increments. The measurement point is A, as
1231
FIGURE 1218
ON PACCH
Unit
- MEASUREMENT POINT
OF
PACKET MOBILE STATUS MESSAGE
Times
packet neighbor cell data
messages
Definition
Description
Number of packet neighbor cell data messages.

If MS sends change notification to neighboring cell in support of
NACC, BSC will send packet neighboring cell data to MS through
BTS.
This counter counts the number of packet neighboring cell data
Measurement
Point
1232
When the type of DL control block sent by BSC is packet neighboring cell data, the counter increments. The measurement point is
A2, as shown inFigure 1219.

COUNTER
Unit
OF
Times
packet PDCH release
messages
Definition
Number of packet PDCH release messages.
Description
This counter counts the number of packet PDCH release messages

sent by BSC on PACCH.
Measurement
Point
When the type of DL control block sent by BSC is packet PDCH

release, the counter increments.
Unit
Times
packet polling request
messages
Definition
Number of packet polling request messages.
1233
Description
This counter counts the number of packet polling request messages sent by BSC on PACCH in packet transmission mode.
Measurement
Point
When the type of DL control block sent by BSC is packet polling request, counter increments. The measurement point is A, as shown
inFigure 1220 .
POLLING
Unit
OF
DL TBF ESTABLISHES EXECUTION
Times
packet power control/timing
advance messages
Definition
1234
Number of packet power control/timing advance messages.
Description
This counter counts the number of packet power control/timing

advance messages sent by BSC on PACCH.
Measurement
Point
When the type of DL control block sent by BSC is packet power

control/timing advance message, counter increments. The measurement point is A, as shown inFigure 1221.

ADVANCE MESSAGE SENT ON PACCH
Unit
OF
PACKET POWER CONTROL/TIMING
Times
packet PSI status message
Definition
Description
Number of packet PSI status messages.

In order to obtain the packet system messages of serving cell,
MS initiates packet PSI status messages to BSC through BTS to
indicate that MS has been received the packet system messages.
This counter counts the number of packet PSI status messages
received by BSC on PACCH.
Measurement
Point
When the type of UL control block sent by BSC is packet PSI Status
message, counter increments. The measurement point is A1, as
1235

RELATED COUNTER
Unit
OF
PACKET-SERVICE-CELL-DATA-
Times
packet serving cell data
messages
Definition
1236
Number of packet serving cell data messages.
Description
Network uses packet serving cell data to send the system messages and packet messages of serving cell to MS, this counter
counts the number of packet serving cell data messages received
by BSC on PACCH.
Usage
This counter is used to check packet serving cell data messages

sent by BSC on PACCH.
Measurement
Point
When the type of DL control block sent by BSC is packet serving

cell data messages, the counter increments. The measurement
point is A2, as shown inFigure 1223 .

RELATED COUNTER
Unit
OF
Times
packet SI status messages
Definition
Description
Number of packet SI status messages.

In order to obtain the system messages of serving cell, MS initiates
packet SI status message to BSC through BTS to indicate that MS
has been received the packet system messages.
This counter counts the number of packet SI status messages received by BSC on PACCH.
Measurement
Point
When the type of UL control block sent by BSC is packet SI status

message, counter increments. The measurement point is A1, as
1237

RELATED COUNTER
Unit
OF
Times
packet timeslot reconfigure
messages
Definition
Description
Number of packet timeslot reconfigure messages.

Packet timeslot reconfigure is used to assign UL and DL resource
link.
This counter counts the number of packet timeslot reconfigure
messages sent by BSC on PACCH.
Measurement
Point
1238
When the type of DL control block sent by BSC is packet timeslot reconfigure messages, counter increments. The measurement
point is A, as shown inFigure 1225 andFigure 1226 .
Unit
FIGURE 1225 - FLOW OF ESTABLISHING UL

TRANSMISSION STATUS
ON
PACCH
UNDER
DL
FIGURE 1226 - FLOW OF ESTABLISHING DL

TRANSMISSION STATUS
ON
PACCH
UNDER
UL
Times
packet paging request
message
Definition
Number of packet paging request message.
1239
Description
If MS is in packet transmission status or attached by GPRS, BSC

will send packet paging request messages.
This counter counts the number of packet paging request messages sent by BSC on PACCH.
Measurement
Point
When the type of DL control block sent by BSC to MS through BTS

is packet paging request messages, the counter increments. The
REQUEST MESSAGE
Unit
Related Features
OF
BSC ISSUING PACKET PAGING
Times
C901160027 Number of PSI

message
Definition
1240
Number of packet PSI message.
Description
This counter counts the number of PSI messages sent by BSC on

PACCH in packet service.
Measurement
Point
When the type of DL control block sent by BSC to MS through BTS

is packet system message, the counter increments. The measurement point is A, as shown inFigure 1228.

MESSAGE
Unit
OF
BSC ISSUING PACKET SYSTEM
Times
1241
1242
Chapter
23
Downlink GPRS Data

TBF Statistics
Table of Contents
Overview...................................................................... 1245
on CCCH/PCCCH............................................................ 1245
on PACCH..................................................................... 1246
due to CPU ................................................................... 1246
due to not support DTM.................................................. 1247
due to Abis congestion ................................................... 1247
due to RR congestion ..................................................... 1248
due to UPPB-DSP channel congestion ............................... 1249
C901170010 Number of GPRS DL TBF establishment channel
allocate success ............................................................ 1251
C901170011 Number of allocated PDCH for GPRS DL TBF establishment .................................................................. 1251
due to channel activate failed.......................................... 1252
due to BTS connection failed ........................................... 1253
due to BIU connection failed ........................................... 1254
C901170015 Number of GPRS DL TBF channel activate establishment success ........................................................... 1255
on CCCH/PCCCH due to not receive PIA ............................ 1255
on CCCH/PCCCH due to UPPB-DSP congestion ................... 1256
on PACCH due to UPPB-DSP congestion ............................ 1257
on PCCCH/CCCH............................................................ 1257
on PACCH..................................................................... 1258
C901170023 Number of GPRS DL TBF resource reallocation failure due to Abis congestion for UL TBF establishment ........................................................................... 1258
failure due to RR congestion for UL TBF establishment......... 1259
1243

failure due to UPPB-DSP channel congestion for UL TBF establishment .................................................................. 1260
success of channel allocation due to UL TBF establishment ........................................................................... 1261
C901170027 Number of allocated PDCH for GPRS DL TBF resource reallocation due to UL TBF establishment ................ 1262
failure due to channel activate failure for UL TBF establishment ........................................................................... 1263
failure due to BTS connection failure for UL TBF establishment ........................................................................... 1264
failure due to BIU connection failure for UL TBF establishment ........................................................................... 1265
success of channel activate and connection for UL TBF establishment....................................................................... 1266
failure due to UL TBF establishment ................................. 1267
success due to UL TBF establishment ............................... 1267
failure due to Abis congestion for LLC transmission ............ 1268
failure due to RR congestion for LLC transmission .............. 1269
failure due to UPPB-DSP channel congestion for LLC transmission ........................................................................ 1270
success of channel allocation due to LLC transmission......... 1271
C901170040 Number of allocated PDCH for GPRS DL TBF resource reallocation due to LLC transmission ...................... 1272
failure due to channel activate failure for LLC transmission ............................................................................. 1273
failure due to BTS connection failure for LLC transmission ............................................................................. 1274
failure due to BIU connection failure for LLC transmission ............................................................................. 1275
success of channel activate and connection for LLC transmission ............................................................................. 1276
failure due to LLC transmission........................................ 1276
success due to LLC transmission ...................................... 1277
C901170047 Number of GPRS DL TBF release due to flush
LL ............................................................................... 1277
C901170048 Number of GPRS DL TBF release due to GPRS
suspend requests .......................................................... 1278
CS............................................................................... 1278
C901170050 Number of GPRS DL TBF normal release due to
user plane requests ....................................................... 1279
1244
Chapter 23 Downlink GPRS Data TBF Statistics
C901170051 Number of GPRS DL TBF abnormal release due

to user plane requests.................................................... 1280
C901170052 Number of GPRS DL TBF release due to NSVC
unavailability ................................................................ 1280
C901170053 Number of GPRS DL TBF release due to BVC
unavailability ................................................................ 1281
C901170054 Number of GPRS DL TBF release due to other
reasons........................................................................ 1282
C901170055 Number of DL GPRS TBF grab resources......... 1282
C901170056 Number of grab instance by DL GPRS TBF......... 1283
C901170057 Number of DL GPRS TBF queuing .................. 1284
C901170058 Number of DL GPRS TBF queuing success......... 1284
C901170059 Number of DL GPRS TBF release TBF during
queuing ....................................................................... 1285
Overview
DL GPRS data TBF statistics is used to observe the process of GPRS
DL TBF establishment, maintenance and release.
C901170002 Number
of GPRS DL TBF
on CCCH/PCCCH
Definition
Number of GPRS DL TBF establishment requests on CCCH/PCCCH.
Description
This counter counts the number of DL establishment requests received by control plane when BSC initially attempts to establish
GPRS DL TBF.
Usage
This counter is used to find out the frequency of DL establishment

requests sent from CCCH/PCCCH and received by control plane
when BSC establishes GPRS DL TBF.
Measurement
Point
When RANPS module receives the DL request (EV_RANUMC_DLASS_REQ)

sent from RANUMC module, the counter increments. The measurement point is A, as shown in Figure 1229.
FIGURE 1229 - DL REQUEST
1245
Unit
Times
C901170003 Number
of GPRS DL TBF
on PACCH
Definition
Number of GPRS DL TBF establishment requests on PACCH.
Description
This counter counts the number of establishing GPRS DL TBF on

PACCH by MS.
Usage
This counter is used to find out the frequency of establishing DL

TBF in PACCH after MS has established GPRS UL TBF.
Measurement
Point
After MS has established GPRS UL TBF, RANPS module receives

message sent from RANU module, the counter
EV_MAC_DL_ASSIGN_REQ
FIGURE 1230 - DL ASSIGNMENT REQUEST
Unit
Times
C901170004 Number
of GPRS DL TBF
CPU
Description
1246
No statistics temporarily.
C901170005 Number
of GPRS DL TBF
not support DTM
Description
C901170007 Number
of GPRS DL TBF
Abis congestion
Definition
Number of GPRS DL TBF establishment failure due to Abis congestion.
Description
This counter counts the number of failures that RANPS applies to

database for resource and the cause of failures is Abis congestion
when BSC attempts to establish GPRS DL TBF.
Usage
This counter is used to find out the frequency of failures that RANPS
applies to database for resource and the cause of failures is Abis
congestion when BSC attempts to establish GPRS DL TBF.
Measurement
Point
The measurement is taken at two time points listed below:
After RANPS module receives DL request message

(EV_RANUMC_DLASS_REQ) sent from RANUMC module, if resource
application fails and the cause of failure is Abis congestion,
the counter increments. The measurement point is A, as
FIGURE 1231 - DATABASE APPLICATION FAILURE
CONGESTION (I)
DUE TO
ABIS
1247
After MS establishes GPRS UL TBF, RANPS module receives

message sent from RANU module, if resource application fails and the cause of failure is Abis congestion, the counter increments. The measurement point is A, as

CONGESTION (II)
Unit
Related Features
DUE TO
ABIS
Times
C901170008 Number
of GPRS DL TBF
RR congestion
Definition
Number of GPRS DL TBF establishment failure due to RR congestion.
Description

database for resource and the cause of failures is RR congestion
when BSC attempts to establish GPRS DL TBF. There are three
causes for RR congestion: MS per channel (number of MS reaches
the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH
(no PS channel).
Usage
applies to database for resource and the cause of failures is RR
Measurement
Point
1248

application fails and the cause of failure is RR congestion, the
counter increments. The measurement point is A, as shown
inFigure 1233.
FIGURE 1233 - DATABASE APPLICATION FAILURE DUE TO RR

CONGESTION (I)

EV_MAC_DL_ASSIGN_REQ message sent from RANU module, if resource application fails and the cause of failure is RR congestion, the counter increments. The measurement point is A, as
CONGESTION (II)
Unit
Related Features
Times
C901170009 Number
of GPRS DL TBF
establishment failure due
to UPPB-DSP channel
congestion
Definition
Number of GPRS DL TBF establishment failure due to UPPB-DSP

channel congestion.
1249
Description

database for resource and the cause of failures is UPPB-DSP channel congestion when BSC attempts to establish GPRS DL TBF.
Usage
applies to database for resource and the cause of failures is UPPBDSP channel congestion when BSC attempts to establish GPRS DL
TBF.
Measurement
Point
After
RANPS
module receives DL request message

sent from RANUMC module, if resource
application fails and the cause of failure is UPPB-DSP channel
congestion, the counter increments. The measurement point
is A, as shown inFigure 1235.
EV_RANUMC_DLASS_REQ

CHANNEL CONGESTION (I)
Related Features
1250
UPPB-DSP

EV_MAC_DL_ASSIGN_REQ message sent from RANU module, if resource application fails and the cause of failure is UPPB-DSP
channel congestion, the counter increments. The measurement point is A, as shown inFigure 1236.
CHANNEL CONGESTION (II)
Unit
DUE TO
DUE TO
Times
UPPB-DSP
C901170010 Number
of GPRS DL TBF
establishment channel
allocate success
Definition
Number of GPRS DL TBF establishment channel allocate success
Description
This counter counts the number of channel allocate success applied

by RANPS when BSC attempts to establish GPRS DL TBF.
Usage
This counter is used to find out the frequency of successful resource application that RANPS sends when BSC attempts to establish GPRS DL TBF.
Measurement
Point
After
RANPS
module
receives
DL
request
message
(EV_RANUMC_DLASS_REQ) sent from RANUMC module, when resource
application succeeds, the counter increments. The measurement
FIGURE 1237 - SUCCESSFUL RESOURCE APPLICATION
Unit
Related Features
Times
allocated PDCH for GPRS
Definition
Number of allocated PDCH for GPRS DL TBF establishment.
Description
This counter counts the number of successful allocated PDCH when

BSC attempts to establish GPRS DL TBF.
Usage
This counter is used to find out the number of successful allocated

PDCH when BSC attempts to establish GPRS DL TBF.
1251
Measurement
Point
After
RANPS
module
receives
DL
request
message
application succeeds, the counter accumulates the PDCH number.
Unit
Times
C901170012 Number
of GPRS DL TBF
channel activate failed
Definition
Number of GPRS DL TBF establishment failure due to channel activate failed
Description
This counter counts the number of PDCH activate failure when BSC
establishes GPRS DL TBF.
Usage
This counter is used to find out the frequency of PDCH activate failure when BSC establishes GPRS DL TBF (including establishing DL
TBF initially and establishing DL TBF while UL TBF already exists).
Measurement
Point
1252
When BSC receives PDCH activation failure message reported

by BTS, the counter increments. The measurement point is A,
FIGURE 1239 - PDCH ACTIVATION FAILURE
Unit
If 'wait for PDCH activate & connection response' timer expires,

and BSC has not received PDCH activate response message
reported by BTS, the counter increments.
Times
C901170013 Number
of GPRS DL TBF
BTS connection failed
Definition
Number of GPRS DL TBF establishment failure due to BTS connection failed.
Description
This counter counts the number of connection failure due to BTS

connection failed when BSC establishes GPRS DL TBF.
Usage
This counter is used to find out the frequency of connection failure due to BTS connection failed when BSC establishes GPRS DL
TBF (including establishing DL TBF initially and establishing DL TBF
while UL TBF already exists).
Measurement
Point
If RANPS module receives connection failed message reported

by connection module, and the cause of failure is BTS connection failed, the counter increments. The measurement point is
A, as shown inFigure 1240.
FIGURE 1240 - CONNECTION FAILED DUE TO BTS CONNECTION FAILURE
1253
Unit

and BSC has not received connection success response message reported by connection module, the counter increments.
Times
C901170014 Number
of GPRS DL TBF
BIU connection failed
Definition
Number of GPRS DL TBF establishment failed due to BIU connection failure.
Description
This counter counts the number of connection failure due to BIU

connection failed when BSC establishes GPRS DL TBF.
Usage
This counter is used to find out the frequency of connection failure due to BIU connection failed when BSC establishes GPRS DL
Measurement
Point
If RANPS module receives connection failed message reported by

connection module, and the cause of failure is BIU connection
failed, the counter increments. The measurement point is A, as
FIGURE 1241 - CONNECTION FAILED DUE TO BIU CONNECTION FAILURE
Unit
1254
Times
GPRS DL TBF channel
activate establishment
success
Definition
Number of GPRS DL TBF channel activate establishment success.
Description
This counter counts the number of channel activate establishment

success when BSC establishes GPRS DL TBF.
Usage
This counter is used to find out the frequency of channel activate

establishment success when BSC establishes GPRS DL TBF.
Measurement
Point
When RANPS module receives channel activate response message

reported by BTS and connection success response message reported by connection module, the counter increments. The measurement point is A as shown inFigure 1242.
FIGURE 1242 - DL GPRS TBF ESTABLISHES CHANNEL ACTIVATION AND
ACCESS SUCCESS
Unit
Times
C901170016 Number
of GPRS DL TBF
receive PIA
Definition

due to not receive PIA
Description
This counter counts the number of DL immediate assignment message sending failures when BSC establishes GPRS DL TBF.
1255
Usage
Measurement
Point
This counter is used to find out the frequency of DL immediate

assignment message sending failures when BSC establishes GPRS
DL TBF.
When RANPS module receives immediate assignment sending

failure message (EV_PACKET_PIA_DEL_IND) reported by BTS, the
inFigure 1243.
FIGURE 1243 - IMMEDIATE ASSIGNMENT SENDING FAILURE
Unit
If 'wait for immediate assignment sending indication' timer expires, and BSC has not received immediate assignment sending message, the counter increments.
Times
C901170017 Number
of GPRS DL TBF
CCCH/PCCCH due to
UPPB-DSP congestion
Definition
Description
Related Features
1256

due to UPPB-DSP congestion.
No statistics for this counter is meaningless to GPRS DL TBF.
C901170018 Number
of GPRS DL TBF
PACCH due to UPPB-DSP
congestion
Definition
Description
Related Features

UPPB-DSP congestion.
C901170019 Number
of GPRS DL TBF
on PCCCH/CCCH
Definition
Number of GPRS DL TBF establishment success on PCCCH/CCCH.
Description
This counter counts the number of successful DL immediate assignment message sending when BSC establishes GPRS DL TBF.
Usage
This counter is used to find out the frequency of GPRS DL TBF

establishment success.
Measurement
Point
When RANPS module receives successful immediate assignment

sending message (SPS_ABIS_PACKET_SEND_PIA_IND) reported by BTS,
Figure 1244.
FIGURE 1244 - SUCCESSFUL IMMEDIATE ASSIGNMENT SENDING
Unit
Times
1257
C901170020 Number
of GPRS DL TBF
on PACCH
Definition
Description
Number of GPRS DL TBF establishment success on PACCH.

Abis congestion for UL TBF
establishment
1258
Definition
Number of GPRS DL TBF resource reallocation failure due to Abis

congestion for UL TBF establishment.
Description
After MS establishes GPRS DL TBF, it shall establish UL TBF on

PACCH. But resource application failure leads to DL resource reallocation failure. This counter counts the number of DL resource
reallocation failure due to Abis congestion.
Usage

resource reallocation failure due to Abis congestion.
Measurement
Point
MS has established GPRS DL TBF, and after RANPS module receives

message sent from RANU module, if resource
application fails due to Abis congestion, the counter increments.
EV_MAC_UL_ASSIGN_REQ
FIGURE 1245 - RESOURCE APPLICATION FAILURE DUE TO ABIS

CONGESTION (ASSIGNED BY UL)
Unit
Related Features
Times
RR congestion for UL TBF
establishment
Description
Number of GPRS DL TBF resource reallocation failure due to RR

Definition
After MS establishes GPRS DL TBF, it shall establish UL TBF on

reallocation failure due to RR congestion.
There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or
TFI) and no PDCH (no PS channel).
Usage

resource reallocation failure due to RR congestion.
Measurement
Point

application fails due to RR congestion, the counter increments.
1259
FIGURE 1246 - RESOURCE APPLICATION FAILURE DUE TO RR CONGESTION

(ASSIGNED BY UL)
Unit
Related Features
Times
reallocation failure due
to UPPB-DSP channel
congestion for UL TBF
establishment
Definition
Number of GPRS DL TBF resource reallocation failure due to UPPBDSP channel congestion for UL TBF establishment
Description
After MS establishes GPRS DL TBF, it shall establish UL TBF in

reallocation failures due to UPPB-DSP channel congestion.
Usage

resource reallocation failure due to UPPB-DSP channel congestion.
Measurement
Point
1260

application fails due to UPPB-DSP channel congestion, the counter
FIGURE 1247 - RESOURCE APPLICATION FAILURE DUE TO UPPB-DSP

CHANNEL CONGESTION (ASSIGNED BY UL)
Unit
Related Features
Times
reallocation success of
channel allocation due to UL
TBF establishment
Definition
Number of GPRS DL TBF resource reallocation success of channel

allocation due to UL TBF establishment.
Description
After MS establishes GPRS DL TBF, it shall establish UL TBF in

PACCH. This counter counts the number of DL resource application success.
Usage

resource reallocation success.
Measurement
Point

1261
FIGURE 1248 SUCCESSFUL RESOURCE APPLICATION (ASSIGNED BY UL)
Unit
Related Features
Times
C901170027 Number
of allocated PDCH for
reallocation due to UL TBF
establishment
1262
Definition
Number of allocated PDCH for GPRS DL TBF resource reallocation

due to UL TBF establishment.
Description
This counter counts the number of successfully allocated PDCH

when GPRS DL TBF resource is reallocated.
Usage
This counter is used to find out the number of successfully allocated PDCH when GPRS DL TBF resource is reallocated.
Measurement
Point

message sent from RANU module, when resource application succeeds, the counter accumulates the PDTCH
number. The measurement point is A, as shown inFigure 1249.
FIGURE 1249 - SUCCESSFUL RESOURCE APPLICATION (ASSIGNED BY UL)
Unit
Related Features
Times
channel activate failure for
Definition
Number of GPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment
Description
This counter counts the number of PDCH activate failure during

the process of GPRS DL TBF resource reallocation.
Usage
This counter is used to find out the frequency of PDCH activate

failure during the process of GPRS DL TBF resource reallocation.
Measurement
Point
When BSC receives PDCH activate failure message reported by

BTS, the counter increments. The measurement point is A, as
1263
Unit

Times
BTS connection failure for
Definition
Number of GPRS DL TBF resource reallocation failure due to BTS

connection failure for UL TBF establishment
Description

connection failure during the process of GPRS DL TBF resource
reallocation.
Usage
This counter is used to find out the frequency of connection failure

due to BTS connection failure during the process of GPRS DL TBF
resource reallocation.
Measurement
Point
1264
If RANPS module receives connection failure message reported

by connection module, and the cause of failure is BTS connection failure, the counter increments. The measurement point
FIGURE 1251 - CONNECTION FAILURE DUE TO BTS CONNECTION

FAILURE
Unit
If 'wait for PDCH activation & connection response' timer expires, and BSC has not received connection success response
message reported by connection module, the counter increments.
Times
BIU connection failure for UL
TBF establishment
Definition
Number of GPRS DL TBF resource reallocation failure due to BIU

Description

connection failure during the process of GPRS DL TBF resource
reallocation.
Usage

due to BIU connection failure during the process of GPRS DL TBF
Measurement
Point

by connection module, and the cause of failure is BIU connection
failure, the counter increments. The measurement point is A, as
1265
Unit
Times
channel activate and
connection for UL TBF
establishment
1266
Definition

activate and connection for UL TBF establishment
Description
This counter counts the number of channel activate success during

the process of GPRS DL TBF resource reallocation.
Usage

success during the process of GPRS DL TBF resource reallocation.
Measurement
Point

reported by BTS and connection success response message reported by connection module, the counter increments. The measurement point is A, as shown inFigure 1253.
FIGURE 1253 - SUCCESSFUL ACTIVATION AND CONNECTION
Unit
Times
reallocation failure due to UL
TBF establishment
Definition
Description
Number of GPRS DL TBF resource reallocation failure due to UL

TBF establishment.
reallocation success due to
Definition
Description
Number of GPRS DL TBF resource reallocation success due to UL

TBF establishment.
1267
Abis congestion for LLC
transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to Abis

congestion for LLC transmission.
Description
During GPRS DL TBF transmission, MAC sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to RANPS due to UL/DL
LLC changes. RANPS applies for resource after it receives the
message. This counter counts the number of resource application
failures after RANPS receives resource adjustment request during
GPRS DL TBF transmission (the cause of database application failure is Abis congestion).
Usage
This counter is used to find out the frequency of resource application failures after RANPS receives resource adjustment request
during GPRS DL TBF transmission (the cause of database application failure is Abis congestion).
Measurement
Point
After RANPS module receives EV_MAC_RESOURCE_ADJU_REQ message

sent from MAC, if resource application fails due to Abis congestion,
inFigure 1254.
CONGESTION (RESOURCE ADJUSTMENT)
Unit
Related Features
1268
Times
RR congestion for LLC
transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to RR

Description
failures after RANPS receives resource adjustment request during
GPRS DL TBF transmission (the cause of database application failure is RR congestion).
Usage
Measurement
Point

sent from MAC, if resource application fails due to RR congestion,
in Figure 1255.
(RESOURCE ADJUSTMENT)
Unit
Related Features
Times
1269
to UPPB-DSP channel
congestion for LLC
transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to UPPBDSP channel congestion for LLC transmission.
Description
message. This counter counts the number of resource reallocation
failure after RANPS receives resource adjustment request during
GPRS DL TBF transmission (the cause of database application failure is UPPB-DSP channel congestion).
Usage
This counter is used to find out the frequency of resource reallocation failure after RANPS receives resource adjustment request
during GPRS DL TBF transmission (the cause of database application failure is UPPB-DSP channel congestion).
Measurement
Point

sent from MAC, if resource application fails due to UPPB-DSP
channel congestion, the counter increments. The measurement
CHANNEL CONGESTION (RESOURCE ADJUSTMENT)
Unit
Related Features
1270
Times
channel allocation due to
LLC transmission
Definition

allocation due to LLC transmission.
Description
message. This counter counts the number of resource reallocation success after RANPS receives resource adjustment request
during GPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of resource reallocation success after RANPS receives resource adjustment request
Measurement
Point

sent from MAC, if resource application succeeds, the counter
1257.
FIGURE 1257 SUCCESSFUL RESOURCE APPLICATION (RESOURCE
ADJUSTMENT)
Unit
Related Features
Times
1271
C901170040 Number
reallocation due to LLC
transmission
Definition
Number of allocated PDCH for GPRS DL TBF resource reallocation

due to LLC transmission.
Description
LLC changes. RANPS applies for resource after it receives the message. This counter counts the number of successfully allocated
PDCH after RANPS receives resource adjustment request during
GPRS DL TBF transmission.
Usage
This counter is used to find out the number of successfully allocated PDCH after RANPS receives resource adjustment request
Measurement
Point

accumulates the PDTCH number. The measurement point is A, as
FIGURE 1258 - SUCCESSFUL RESOURCE APPLICATION (RESOURCE
ADJUSTMENT)
Unit
Related Features
1272
Times
LLC transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission.
Description
This counter counts the number of PDCH activate failure after BSC
receives resource adjustment request during GPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of PDCH activate failure after BSC receives resource adjustment request during GPRS
DL TBF transmission.
Measurement
Point

Unit

Times
1273
LLC transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to BTS

connection failure for LLC transmission.
Description

connection failure after BSC receives resource adjustment request
Usage

due to BTS connection failure after BSC receives resource adjustment request during GPRS DL TBF transmission.
Measurement
Point
measurement is taken at two time points listed below:

FIGURE 1260 - CONNECTION FAILED DUE TO BTS CONNECTION
FAILURE
Unit
1274

Times
BIU connection failure for
LLC transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to BIU

Description

Usage

due to BIU connection failure after BSC receives resource adjustment request during GPRS DL TBF transmission.
Measurement
Point

Unit
Times
1275
connection for LLC
transmission
Definition

activate and connection for LLC transmission
Description
This counter counts the number of channel activate success after

BSC receives resource adjustment request during GPRS DL TBF
transmission.
Usage

success after BSC receives resource adjustment request during
GPRS DL TBF transmission.
Measurement
Point

reported by BTS and connection success response message reported by connection module, the counter increments. The measurement point is A, as shown in Figure 1262.
Unit
Times
LLC transmission
Definition
1276
Number of GPRS DL TBF resource reallocation failure due to LLC

transmission.
Description
LLC transmission
Definition
Description
Number of GPRS DL TBF resource reallocation success due to LLC

transmission.
to flush LL
Definition
Number of GPRS DL TBF release due to flush LL.
Description
This counter counts the number of GPRS DL TBF release due to

flush LL.
Usage

forcing Release Requests due to flush LL received by RANPS.
Measurement
Point
When RANPS module receives Release Request message

(EV_RANUMC_REL_CMD) reported by RANUMC, if the cause of release is
flush LL, and GPRS DL TBF exists, the counter increments. The
FIGURE 1263 - RELEASE REQUEST DUE TO FLUSH LL
Unit
Times
1277
to GPRS suspend requests
Definition
Number of GPRS DL TBF release due to GPRS suspend requests.
Description

GPRS suspend requests.
Usage
This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to suspend requests received by RANPS.
Measurement
Point

SUSPEND, and GPRS DL TBF exists, the counter increments. The
FIGURE 1264 - RELEASE REQUEST DUE TO SUSPEND REQUEST
Unit
Times
GPRS DL TBF forcing
release by CS
Definition
1278
Number of GPRS DL TBF forcing release by CS.
Description
This counter counts the number of GPRS DL TBF forcing release

by CS due to PDCH REL.
Usage

forcing Release Requests (EV_RANCCM_PDCH_REL) received by RANPS.
Measurement
Point

(EV_RANCCM_PDCH_REL) reported by RANCCM module, if GPRS DL TBF
exists, the counter increments. The measurement point is A, as
FIGURE 1265 - RELEASE REQUEST DUE TO PDCH REL
Unit
Times
GPRS DL TBF normal
release due to user plane
requests
Definition
Number of GPRS DL TBF normal release due to user plane requests.
Description
This counter counts the number of GPRS DL TBF normal release

due to normal Release Request by MAC.
Usage

forcing Release Requests due to normal Release Request by MAC
received by RANPS.
Measurement
Point

(EV_MAC_REL_IND) reported by MAC, if the cause of release is normal
Release Request by MAC, and GPRS DL TBF exists, the counter
1266.
FIGURE 1266 - RELEASE REQUEST DUE TO NORMAL RELEASE REQUEST
BY MAC
Unit
Times
1279
GPRS DL TBF abnormal
requests
Definition
Number of GPRS DL TBF abnormal release due to user plane requests.
Description
This counter counts the number of GPRS DL TBF abnormal release

due to abnormal Release Request by MAC.
Usage

forcing Release Requests due to abnormal Release Request by MAC
received by RANPS.
Measurement
Point

(EV_MAC_REL_IND) reported by MAC, if the cause of release is abnormal Release Request by MAC, and GPRS DL TBF exists, the
inFigure 1267.
FIGURE 1267 - RELEASE REQUEST DUE TO ABNORMAL RELEASE REQUEST
BY MAC
Unit
Times
to NSVC unavailability
Definition
1280
Number of GPRS DL TBF release due to NSVC unavailability.
Description

NSVC unavailability.
Usage

forcing Release Requests due to NSVC unavailability received by
RANPS.
Measurement
Point

(EV_RANUMC_REL_CMD) reported by RANUMC, if the cause of release
is NSVC unavailability, and GPRS DL TBF exists, the counter
1268.
FIGURE 1268 - RELEASE REQUEST DUE TO NSVC UNAVAILABILITY
Unit
Times
to BVC unavailability
Definition
Number of GPRS DL TBF release due to BVC unavailability.
Description

BVC unavailability.
Usage
This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to BVC unavailability received by RANPS.
Measurement
Point

is BVC unavailability, and GPRS DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 1269 .
FIGURE 1269 - RELEASE REQUEST DUE TO BVC UNAVAILABILITY
Unit
Times
1281
to other reasons
Definition
Number of GPRS DL TBF release due to other reasons.
Description

other reasons.
Usage

forcing Release Requests due to other reasons received by RANPS.
Measurement
Point

(EV_RANUMC_REL_CMD) reported by RANUMC, if the reason of release
is others, and GPRS DL TBF exists, the counter increments. The
measurement point is A, as shown inFigure 1270.
FIGURE 1270 - RELEASE REQUEST DUE TO OTHER REASONS
Unit
Times
GPRS TBF grab resources
Definition
Description
1282
Number of DL GPRS TBF grab resources.

This counter counts the number of DL GPRS TBF grab resources.
Usage
This counter is used to find out the frequency for DL GPRS TBF
grabbing other TBF resource.
Measurement
Point
This counter increments while DL GPRS TBF is established during

resource adjustment, resource request is successful, and other
TBF resource is grabbed. Measurement point is A as shown in
Figure 1271.
FIGURE 1271 - DL GPRS RESOURCE REQUEST SUCCESS
Unit
Related Features
Times
ZGO-01-02-003 Service Based QoS
ZGO-01-02-004 Streaming Service Policies
grab instance by DL GPRS
TBF
Definition
Number of grab instance by DL GPRS TBF
Description
This counter counts the number of grab instance by DL GPRS TBF.
Usage
Measurement
Point

TBF resource is grabbed. Measurement point is A as shown
inFigure 1272.
Unit
Related Features
Times
1283
GPRS TBF queuing
Definition
Description
Number of DL GPRS TBF queuing.

This counter counts the number of DL GPRS TBF queuing.
Usage
queuing.
Measurement
Point

resource adjustment, resource request is successful but queuing
is required due to incompliant to QoS rate. Measurement point is
A as shown inFigure 1273.
Unit
Related Features
Times
GPRS TBF queuing success
Definition
1284
Number of DL GPRS TBF queuing success.
Description
This counter counts the number of DL GPRS TBF queuing success.
Usage
queuing success.
Measurement
Point
This counter increments while DL GPRS TBF is established during resource adjustment, the instance to be queued successfully
assigns resource for user plane, and database is successfully registered. Measurement point is A as shown in Figure 1274.
FIGURE 1274 - RESOURCE ASSIGNMENT SUCCESS
Unit
Related Features
Times
GPRS TBF release TBF
during queuing
Definition
Number of DL GPRS TBF release TBF during queuing.
Description
This counter counts the number of DL GPRS TBF release during

queuing.
Usage
release during queuing.
Measurement
Point
This counter increments while DL GPRS TBF is released and instance still in queuing state. The measurement point is A as shown
inFigure 1275.
FIGURE 1275 - RELEASE DL GPRS TBF
Unit
Related Features
Times
1285
1286
Chapter
24
Downlink EGPRS Data

TBF Statistics
Table of Contents
Overview...................................................................... 1289
C901180002 Number of EGPRS DL TBF establishment requests on CCCH/PCCCH.................................................. 1289
C901180003 Number of EGPRS DL TBF establishment requests on PACCH........................................................... 1290
due to CPU ................................................................... 1291
due to not support DTM.................................................. 1291
C901180010 Number of EGPRS DL TBF establishment channel
establishment ............................................................... 1296
C901180015 Number of EGPRS DL TBF channel activate establishment success....................................................... 1299
on CCCH/PCCCH due to not receive PIA ............................ 1300
on CCCH/PCCCH due to UPPB-DSP congestion ................... 1301
on PCCCH/CCCH............................................................ 1301
on PACCH..................................................................... 1302
C901180023 Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for UL TBF establishment ........................................................................... 1302
failure due to RR congestion for UL TBF establishment......... 1303
1287

failure due to UPPB-DSP channel congestion for UL TBF establishment .................................................................. 1304
C901180026 Number of EGPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment ........................................................................... 1305
resource reallocation due to UL TBF establishment ............. 1306
failure due to channel activate failure for UL TBF establishment ........................................................................... 1307
failure due to BTS connection failure for UL TBF establishment ........................................................................... 1308
failure due to BIU connection failure for UL TBF establishment ........................................................................... 1309
success of channel activate and connection for UL TBF establishment....................................................................... 1310
failure due to UL TBF establishment ................................. 1310
success due to UL TBF establishment ............................... 1311
failure due to UPPB-DSP channel congestion for LLC transmission ............................................................................. 1313
resource reallocation due to LLC transmission.................... 1315
C901180041 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission ............................................................................. 1316
C901180042 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission ............................................................................. 1317
C901180043 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission ............................................................................. 1318
success of channel activate and connection for LLC transmission ............................................................................. 1319
C901180047 Number of EGPRS DL TBF release due to flush
LL ............................................................................... 1320
C901180048 Number of EGPRS DL TBF release due to EGPRS
CS............................................................................... 1322
C901180050 Number of EGPRS DL TBF normal release due to
1288
Chapter 24 Downlink EGPRS Data TBF Statistics
C901180051 Number of EGPRS DL TBF abnormal release due

C901180052 Number of EGPRS DL TBF release due to NSVC
unavailability ................................................................ 1324
C901180053 Number of EGPRS DL TBF release due to BVC
unavailability ................................................................ 1324
C901180054 Number of EGPRS DL TBF release due to other
reasons........................................................................ 1325
C901180055 Number of DL EGPRS TBF grab resources......... 1325
C901180056 Number of grab instance by DL EGPRS
TBF ............................................................................. 1326
C901180057 Number of DL EGPRS TBF queuing ................ 1327
C901180058 Number of DL EGPRS TBF queuing success............................................................................. 1327
C901180059 Number of DL EGPRS TBF release TBF during
queuing ....................................................................... 1328
Overview
DL (DL) EGPRS data TBF statistics aims to measure the process of
cell-level EGPRS DL TBF establishment and release. This chapter
describes the definition, usage and measurement point of various
counters.
C901180002 Number
of EGPRS DL TBF
on CCCH/PCCCH
Definition
Number of EGPRS DL TBF establishment requests on CCCH/PCCCH.
Description
This counter counts the number of DL establishment requests received by control plane when BSC initially attempts to establish
EGPRS DL TBF.
Usage
This counter is used to find out the frequency of DL establishment

requests sent from CCCH/PCCCH and received by control plane
when BSC establishes EGPRS DL TBF.
Measurement
Point
When RANPS module receives the DL request (EV_RANUMC_DLASS_REQ)

sent from RANUMC module, the counter increments. This measurement point is A, as shown in Figure 1276.
1289
FIGURE 1276 - DL REQUEST
Unit
Times
C901180003 Number
of EGPRS DL TBF
on PACCH
Definition
Number of EGPRS DL TBF establishment requests on PACCH.
Description
This counter counts the number of establishing EGPRS DL TBF on

PACCH by MS.
Usage
This counter is used to find out the frequency of establishing DL

TBF in PACCH after MS has established EGPRS UL TBF.
Measurement
Point
After MS has established EGPRS UL TBF, RANPS module receives

message sent from RANU module, the counter
increments. This measurement point is A, as shown inFigure 1277.
FIGURE 1277 - DL ASSIGNMENT REQUEST
Unit
1290
Times
C901180004 Number
of EGPRS DL TBF
CPU
Definition
Description
Number of EGPRS DL TBF establishment failure due to CPU.

C901180005 Number
of EGPRS DL TBF
not support DTM
Definition
Description
Number of EGPRS DL TBF establishment failure due to not support

DTM.
C901180007 Number
of EGPRS DL TBF
Abis congestion
Definition
Number of EGPRS DL TBF establishment failure due to Abis congestion.
Description

database for resource and the cause of failures is Abis congestion
when BSC attempts to establish EGPRS DL TBF.
Usage
applies to database for resource and the cause of failures is Abis
congestion when BSC attempts to establish EGPRS DL TBF.
Measurement
Point

1291
application fails and the cause of failure is Abis congestion,

the counter increments. The measurement point is A, as
FIGURE 1278 - DATABASE APPLICATION FAILURE DUE TO ABIS
CONGESTION (I)
After MS establishes EGPRS UL TBF, RANPS module receives

message sent from RANU module, if resource application fails and the cause of failure is Abis congestion, the counter increments. The measurement point is A, as

CONGESTION (II)
Unit
Related Features
Times
C901180008 Number
of EGPRS DL TBF
RR congestion
Definition
1292
Number of EGPRS DL TBF establishment failure due to RR congestion.
Description

database for resource and the cause of failures is RR congestion
when BSC attempts to establish GPRS DL TBF. There are three
causes for RR congestion: MS per channel (number of MS reaches
the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH
(no PS channel).
Usage
Measurement
Point

application fails and the cause of failure is RR congestion, the
inFigure 1280.
CONGESTION (I)

EV_MAC_DL_ASSIGN_REQ message sent from RANU module, if resource application fails and the cause of failure is RR congestion, the counter increments. The measurement point is A, as
CONGESTION (II)
Unit
Related Features
Times
1293
C901180009 Number
of EGPRS DL TBF
to UPPB-DSP channel
congestion
Definition
Number of EGPRS DL TBF establishment failure due to UPPB-DSP

channel congestion.
Description

database for resource and the cause of failures is UPPB-DSP channel congestion when BSC attempts to establish EGPRS DL TBF.
Usage
applies to database for resource and the cause of failures is UPPBDSP channel congestion when BSC attempts to establish EGPRS
DL TBF.
Measurement
Point

application fails and the cause of failure is UPPB-DSP channel
CHANNEL CONGESTION (I)
UPPB-DSP
After MS establishes EGPRS UL TBF, RANPS module receives

message sent from RANU module, if resource application fails and the cause of failure is UPPB-DSP
channel congestion, the counter increments. The measurement point is A, as shown inFigure 1283.
1294
DUE TO

CHANNEL CONGESTION (II)
Unit
Related Features
DUE TO
UPPB-DSP
Times
C901180010 Number
of EGPRS DL TBF
allocate success
Definition
Number of EGPRS DL TBF establishment channel allocate success.
Description
This counter counts the number of channel allocate success applied

by RANPS when BSC attempts to establish EGPRS DL TBF.
Usage
This counter is used to find out the frequency of successful resource application that RANPS sends when BSC attempts to establish EGPRS DL TBF.
Measurement
Point
After
RANPS
module
receives
DL
request
message
Unit
Times
1295
Related Features
allocated PDCH for EGPRS
Definition
Number of allocated PDCH for EGPRS DL TBF establishment.
Description
This counter counts the number of successful allocated PDCH when

BSC attempts to establish EGPRS DL TBF.
Usage

PDCH when BSC attempts to establish EGPRS DL TBF.
Measurement
Point
After
RANPS
module
receives
DL
request
message
sent from RANUMC module, when resource
application succeeds, the counter accumulates the PDCH number.
EV_RANUMC_DLASS_REQ
Unit
Related Features
Times
C901180012 Number
of EGPRS DL TBF
1296
Definition
Number of EGPRS DL TBF establishment failure due to channel

activate failed.
Description
This counter counts the number of PDCH activate failure when BSC
establishes EGPRS DL TBF.
Usage
Measurement
Point

failure when BSC establishes EGPRS DL TBF (including establishing DL TBF initially and establishing DL TBF while UL TBF already
exists).
When BSC receives PDCH activation failure message reported

by BTS, the counter increments. The measurement point is A,
Unit

Times
C901180013 Number
of EGPRS DL TBF
Definition
Number of EGPRS DL TBF establishment failed due to BTS connection failure.
Description

connection failed when BSC establishes EGPRS DL TBF.
Usage
This counter is used to find out the frequency of connection failure due to BTS connection failed when BSC establishes EGPRS DL
Measurement
Point

1297

FAILURE
Unit
Times
C901180014 Number
of EGPRS DL TBF
1298
Definition
Number of EGPRS DL TBF establishment failed due to BIU connection failure.
Description

connection failed when BSC establishes EGPRS DL TBF.
Usage
This counter is used to find out the frequency of connection failure due to BIU connection failed when BSC establishes EGPRS DL
Measurement
Point
If RANPS module receives connection failed message reported by

connection module, and the cause of failure is BIU connection
failed, the counter increments. The measurement point is A, as
Unit
Times
EGPRS DL TBF channel
success
Definition
Number of EGPRS DL TBF channel activate establishment success.
Description
This counter counts the number of channel activate establishment

success when BSC establishes EGPRS DL TBF.
Usage

establishment success when BSC establishes EGPRS DL TBF.
Measurement
Point

FIGURE 1289 - IMMEDIATE ASSIGNMENT SENDING FAILURE
Unit
Times
1299
C901180016 Number
of EGPRS DL TBF
receive PIA
Definition

due to not receive PIA
Description
This counter counts the number of DL immediate assignment message sending failures when BSC establishes EGPRS DL TBF.
Usage
This counter is used to find out the frequency of DL immediate assignment message sending failures when BSC establishes EGPRS
DL TBF.
Measurement
Point
When RANPS module receives immediate assignment sending failure message EV_PACKET_PIA_DEL_IND reported by BTS, the
inFigure 1290.
Unit
1300
If 'wait for immediate assignment sending indication' timer expires, and BSC has not received immediate assignment sending message, the counter increments.
Times
C901180017 Number
of EGPRS DL TBF
CCCH/PCCCH due to
UPPB-DSP congestion
Definition
Description

No statistics for this counter is meaningless to EGPRS DL TBF.
C901180018 Number
of EGPRS DL TBF
congestion
Definition
Description

C901180019 Number
of EGPRS DL TBF
on PCCCH/CCCH
Definition
Number of EGPRS DL TBF establishment success on PCCCH/CCCH.
Description
This counter counts the number of successful DL immediate assignment message sendings when BSC establishes EGPRS DL TBF.
Usage
This counter is used to find out the frequency of EGPRS DL TBF

1301
Measurement
Point
When RANPS module receives successful immediate assignment

sending message (SPS_ABIS_PACKET_SEND_PIA_IND) reported by BTS,
inFigure 1291.
Unit
Times
C901180020 Number
of EGPRS DL TBF
on PACCH
Definition
Description
Number of EGPRS DL TBF establishment success on PACCH.

Abis congestion for UL TBF
establishment
Definition
1302
Number of EGPRS DL TBF establishment success on PCCCH/CCCH.
Description
After MS establishes EGPRS DL TBF, it shall establish UL TBF on

reallocation failure due to Abis congestion.
Usage

Measurement
Point
MS has established EGPRS DL TBF, and after RANPS module receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if resource application fails due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 1292.
Unit
Related Features
Times
RR congestion for UL TBF
establishment
Definition
Number of EGPRS DL TBF resource reallocation failure due to RR

Description
After MS establishes EGPRS DL TBF, it shall establish UL TBF on

reallocation failure due to RR congestion.
1303
Usage

resource reallocation failure due to RR congestion.
Measurement
Point
MS has established EGPRS DL TBF, and after RANPS module receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if resource application fails due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 1293.
(ASSIGNED BY UL)
Unit
Related Features
Times
to UPPB-DSP channel
congestion for UL TBF
establishment
1304
Definition
Number of EGPRS DL TBF resource reallocation failure due to

UPPB-DSP channel congestion for UL TBF establishment
Description
After MS establishes EGPRS DL TBF, it shall establish UL TBF in

reallocation failures due to UPPB-DSP channel congestion.
Usage

resource reallocation failure due to UPPB-DSP channel congestion.
Measurement
Point
MS has established EGPRS DL TBF, and after RANPS module receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if
resource application fails due to UPPB-DSP channel congestion,
inFigure 1294.
Unit
Related Features
Times
channel allocation due to UL
TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation success of channel

allocation due to UL TBF establishment
Description
After MS establishes EGPRS DL TBF, it shall establish UL TBF in

PACCH. This counter counts the number of DL resource application
success.
Usage

resource reallocation success.
Measurement
Point
MS has established EGPRS DL TBF, and after RANPS module receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if resource application succeeds, the counter increments. The measurement point is A, as shown in Figure 1295.
1305
FIGURE 1295 SUCCESSFUL RESOURCE APPLICATION (ASSIGNED BY UL)
Unit
Related Features
Times
C901180027 Number
reallocation due to UL TBF
establishment
1306
Definition
Number of allocated PDCH for EGPRS DL TBF resource reallocation

due to UL TBF establishment.
Description
This counter counts the number of successfully allocated PDCH

when EGPRS DL TBF resource is reallocated.
Usage
This counter is used to find out the number of successfully allocated PDCH when EGPRS DL TBF resource is reallocated.
Measurement
Point
MS has established EGPRS DL TBF, and after RANPS module

receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module,
when resource application succeeds, the counter accumulates the
PDTCH number. The measurement point is A, as shown inFigure
1296.
FIGURE 1296 - SUCCESSFUL RESOURCE APPLICATION (ASSIGNED BY UL)
Unit
Related Features
Times
Definition
Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment
Description
This counter counts the number of PDCH activate failure during

the process of EGPRS DL TBF resource reallocation.
Usage

failure during the process of EGPRS DL TBF resource reallocation.
Measurement
Point

shown in

1307
Unit
Times
Definition
Number of EGPRS DL TBF resource reallocation failure due to BTS

Description

connection failure during the process of EGPRS DL TBF resource
reallocation.
Usage

due to BTS connection failure during the process of EGPRS DL TBF
Measurement
Point

FAILURE
1308
Unit
Times
BIU connection failure for UL
TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation failure due to BIU

connection failure for UL TBF establishment.
Description

connection failure during the process of EGPRS DL TBF resource
reallocation.
Usage

due to BIU connection failure during the process of EGPRS DL TBF
Measurement
Point

Unit
Times
1309
connection for UL TBF
establishment
Definition

activate and connection for UL TBF establishment
Description
This counter counts the number of channel activate success during

the process of EGPRS DL TBF resource reallocation.
Usage

success during the process of EGPRS DL TBF resource reallocation.
Measurement
Point

Unit
Times
reallocation failure due to UL
TBF establishment
Definition
Description
1310
Number of EGPRS DL TBF resource reallocation failure due to UL

TBF establishment.
Related Features
Definition
Description
Related Features
Number of EGPRS DL TBF resource reallocation success due to UL

TBF establishment.
transmission
Definition
Number of EGPRS DL TBF resource reallocation failure due to Abis

Description
During EGPRS DL TBF transmission, MAC sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to RANPS due to UL/DL
failures after RANPS receives resource adjustment request during EGPRS DL TBF transmission (the cause of database application
failure is Abis congestion).
Usage
during EGPRS DL TBF transmission (the cause of database application failure is Abis congestion).
Measurement
Point

sent from MAC, if resource application fails due to Abis congestion,
inFigure 1301 .
1311

Unit
Related Features
Times
transmission
Definition
Number of EGPRS DL TBF resource reallocation failure due to RR

Description
failures after RANPS receives resource adjustment request during EGPRS DL TBF transmission (the cause of database application
failure is RR congestion).
1312
Usage
during EGPRS DL TBF transmission (the cause of database application failure is RR congestion).
Measurement
Point

sent from MAC, if resource application fails due to RR congestion,
inFigure 1302 .

Unit
Related Features
Times
to UPPB-DSP channel
congestion for LLC
transmission
Definition
Number of EGPRS DL TBF resource reallocation failure due to

UPPB-DSP channel congestion for LLC transmission.
Description
message. This counter counts the number of resource reallocation
failure after RANPS receives resource adjustment request during
EGPRS DL TBF transmission (the cause of database application failure is UPPB-DSP channel congestion).
Usage
This counter is used to find out the frequency of resource reallocation failure after RANPS receives resource adjustment request
during EGPRS DL TBF transmission (the cause of database application failure is UPPB-DSP channel congestion).
Measurement
Point

sent from MAC, if resource application fails due to UPPB-DSP
channel congestion, the counter increments. The measurement
1313

Unit
Related Features
Times
LLC transmission
1314
Definition

Description
LLC changes. RANPS applies for resource after receiving the message. This counter counts the number of resource reallocation
success after RANPS receives resource adjustment request during
EGPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of resource reallocation success after RANPS receives resource adjustment request
during EGPRS DL TBF transmission.
Measurement
Point

1304.

ADJUSTMENT)
Unit
Related Features
Times
C901180040 Number
transmission
Definition
Number of allocated PDCH for EGPRS DL TBF resource reallocation

Description
LLC changes. RANPS applies for resource after it receives the message. This counter counts the number of successfully allocated
PDCH after RANPS receives resource adjustment request during
Usage
This counter is used to find out the number of successfully allocated PDCH after RANPS receives resource adjustment request
Measurement
Point

accumulates the PDTCH number. The measurement point is A, as
1315

ADJUSTMENT)
Unit
Related Features
Times
LLC transmission
Definition
Number of Number of EGPRS DL TBF resource reallocation failure

due to channel activate failure for LLC transmission.
Description
This counter counts the number of PDCH activate failure after BSC
receives resource adjustment request during EGPRS DL TBF transmission.
Usage

failure after BSC receives resource adjustment request during EGPRS DL TBF transmission.
Measurement
Point
1316

Unit
Related Features

Times
LLC transmission
Definition
Number of EGPRS DL TBF resource reallocation failure due to BTS

Description

Usage

due to BTS connection failure after BSC receives resource adjustment request during EGPRS DL TBF transmission.
Measurement
Point

1317

FAILURE
Unit

Times
LLC transmission
1318
Definition
Number of EGPRS DL TBF resource reallocation failure due to BIU

Description

Usage

due to BIU connection failure after BSC receives resource adjustment request during EGPRS DL TBF transmission.
Measurement
Point

Unit
Times
connection for LLC
transmission
Definition

activate and connection for LLC transmission
Description
This counter counts the number of channel activate success after

BSC receives resource adjustment request during EGPRS DL TBF
transmission.
Usage

success after BSC receives resource adjustment request during
Measurement
Point

reported by BTS and connection success response message reported by connection module, the counter increments. The measurement point is A, as shown in Figure 1309.
1319
Unit
Times
LLC transmission
Definition
Description
Related Features
Number of EGPRS DL TBF resource reallocation failure due to LLC

transmission.
LLC transmission
Definition
Description
Related Features
Number of EGPRS DL TBF resource reallocation success due to LLC

transmission.
to flush LL
Definition
1320
Number of EGPRS DL TBF release due to flush LL.
Description
This counter counts the number of EGPRS DL TBF release due to

flush LL.
Usage

forcing Release Requests due to flush LL received by RANPS.
Measurement
Point

flush LL, and EGPRS DL TBF exists, the counter increments. The
Unit
Times
to EGPRS suspend requests
Definition
Number of EGPRS DL TBF release due to EGPRS suspend requests.
Description

EGPRS suspend requests.
Usage

forcing Release Requests due to suspend requests received by
RANPS.
Measurement
Point

is SUSPEND, and EGPRS DL TBF exists, the counter increments.
FIGURE 1311 - RELEASE REQUEST DUE TO SUSPEND REQUEST
Unit
Times
1321
EGPRS DL TBF forcing
release by CS
Definition
Number of EGPRS DL TBF forcing release by CS.
Description
This counter counts the number of EGPRS DL TBF forcing release

by CS due to PDCH REL.
Usage

forcing Release Requests (EV_RANCCM_PDCH_REL) received by RANPS.
Measurement
Point

(EV_RANCCM_PDCH_REL) reported by RANCCM module, if EGPRS DL
TBF exists, the counter increments. The measurement point is A,
FIGURE 1312 - RELEASE REQUEST DUE TO PDCH REL
Unit
Times
EGPRS DL TBF normal
requests
1322
Definition
Number of EGPRS DL TBF normal release due to user plane requests.
Description
This counter counts the number of EGPRS DL TBF abnormal release

Usage

received by RANPS.
Measurement
Point

(EV_MAC_REL_IND) reported by MAC, if the cause of release is
abnormal Release Request by MAC, and EGPRS DL TBF exists,

inFigure 1313.
FIGURE 1313 - RELEASE REQUEST
MAC
Unit
DUE TO
NORMAL RELEASE REQUEST
BY
Times
EGPRS DL TBF abnormal
requests
Definition
Number of EGPRS DL TBF abnormal release due to user plane requests
Description
This counter counts the number of EGPRS DL TBF abnormal release

Usage

received by RANPS.
Measurement
Point

(EV_MAC_REL_IND) reported by MAC, if the cause of release is
abnormal Release Request by MAC, and EGPRS DL TBF exists,
inFigure 1314.
BY MAC
Unit
DUE TO
ABNORMAL RELEASE REQUEST
Times
1323
Definition
Number of EGPRS DL TBF release due to NSVC unavailability.
Description

Usage

forcing Release Requests due to NSVC unavailability received by
RANPS.
Measurement
Point

is NSVC unavailability, and EGPRS DL TBF exists, the counter
increments. The measurement point is A, as shown inFigure
1315.
Unit
DUE TO
NVSC UNAVAILABILITY
Times
Definition
1324
Number of EGPRS DL TBF release due to BVC unavailability.
Description

BVC unavailability.
Usage

forcing Release Requests due to BVC unavailability received by
RANPS.
Measurement
Point

is BVC unavailability, and EGPRS DL TBF exists, the counter
1316.
Unit
Times
to other reasons
Definition
Number of EGPRS DL TBF release due to other reasons.
Description

other reasons.
Usage

forcing Release Requests due to other reasons received by RANPS.
Measurement
Point

(EV_RANUMC_REL_CMD) reported by RANUMC, if the reason of release
is others, and EGPRS DL TBF exists, the counter increments. The
Unit
Times
EGPRS TBF grab resources
Description
This counter counts the number of downlink EGRPS TBF's grabbing

resources.
1325
Usage
The counter is used to find out the frequency of downlink EGPRS

TBF grabbing other TBF resources.
Measurement
Point
During the downlink EGPRS TBF establishment and resource adjustment process, if the resource request succeeds and the other
TBF resources is grabbed, the counter increments. The measurement point is A, as shown in Figure 1318.
FIGURE 1318 DOWNLINK EGPRS REQUESTING RESOURCE SUCCESSFULLY
Unit
Related Features
Times
grab instance by DL EGPRS
TBF
Description
This counter counts the number of instances grabbed by downlink

EGRPS TBF.
Usage

TBF grabbing other TBF resources.
Measurement
Point
During the downlink EGPRS TBF establishment and resource

adjustment process, if the resource request succeeds and the
other TBF resources is grabbed, the counter counts the number
of grabbed instances. The measurement point is A, as shown in
Figure 1319.
1326
Unit
Related Features
Times
EGPRS TBF queuing
Description
This counter counts the number of downlink EGRPS TBF's queuing.
Usage

TBF's queuing.
Measurement
Point
During the downlink EGPRS TBF establishment and resource adjustment process, if the resource request succeeds but it can not
guarantee queuing at the QoS rate, the counter increments. The
Unit
Related Features
Times
DL EGPRS TBF queuing
success
Description
This counter counts the number of downlink EGRPS TBF's queuing

success.
Usage

TBF's queuing success.
Measurement
Point
During the downlink EGPRS TBF establishment and resource adjustment process, when the queuing instance assigns resource to
the user plane successfully and registers in database successfully,
1327

Figure 1321.
FIGURE 1321 ASSIGNING RESOURCE SUCCESSFULLY
Unit
Related Features
Times
EGPRS TBF release TBF
during queuing
Description
This counter counts the number of downlink EGRPS TBF's releasing

TBF during queuing.
Usage

TBF's releasing TBF during queuing.
Measurement
Point
When the downlink EGPRS TBF releases TBF, if the instance is

still in queuing status, the counter increments. The measurement
FIGURE 1322 RELEASING DOWNLINK EGPRS TBF
Unit
Related Features
1328
Times
Chapter
25
Uplink GPRS Data TBF

Statistics
Table of Contents
Overview...................................................................... 1332
on CCCH ...................................................................... 1332
C901190003 Number of EGPRS UL TBF establishment requests on CCCH ............................................................ 1333
on PCCCH..................................................................... 1333
C901190005 Number of EGPRS UL TBF establishment requests on PCCCH........................................................... 1334
on PACCH..................................................................... 1334
C901190007 Number of cell attempts for UL assignment due
to ONE PHASE access..................................................... 1335
to single block packet access........................................... 1336
to response paging ........................................................ 1337
to cell updating ............................................................. 1338
to mobility management................................................. 1339
to TWO PHASE access .................................................... 1339
to short access.............................................................. 1340
C901190018 Number of GPRS UL TBF establishment channel
C901190019 Number of cell success for GPRS UL assignment
due to ONE PHASE access............................................... 1347
due to single block packet access .................................... 1349
due to response paging .................................................. 1349
due to cell updating ....................................................... 1350
due to mobility management........................................... 1351
1329

due to TWO PHASE access .............................................. 1352
due to short access........................................................ 1353
C901190026 Number of allocated PDCH for GPRS UL TBF establishment .................................................................. 1354
C901190030 Number of GPRS UL TBF channel activate establishment success ........................................................... 1358
due to not receive PIA.................................................... 1359
C901190032 Number of GPRS UL TBF establisment failure on
PCCCH/CCCH due to UPPB-DSP congestion ....................... 1360
C901190033 Number of GPRS UL TBF establisment failure on
PACCH due to UPPB-DSP congestion ................................ 1361
on PCCCH/CCCH............................................................ 1361
on PACCH..................................................................... 1362
C901190038 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for DL TBF establishment ........................................................................... 1362
failure due to RR congestion for DL TBF establishment......... 1363
failure due to UPPB-DSP channel congestion for DL TBF establishment .................................................................. 1364
success of channel allocation due to DL TBF establishment ........................................................................... 1365
C901190042 Number of allocated PDCH for GPRS UL TBF resource reallocation due to DL TBF establishment................ 1366
failure due to channel activate failure for DL TBF establishment ........................................................................... 1367
failure due to BTS connection failure for DL TBF establishment ........................................................................... 1368
failure due to BIU connection failure for DL TBF establishment ........................................................................... 1369
success of channel activate and connection for DL TBF establishment....................................................................... 1370
failure due to DL TBF establishment ................................. 1371
success due to DL TBF establishment ............................... 1371
failure due to UPPB-DSP channel congestion for LLC transmission ........................................................................ 1373
1330
Chapter 25 Uplink GPRS Data TBF Statistics

C901190055 Number of allocated PDCH for GPRS UL TBF resource reallocation due to LLC transmission ...................... 1375
failure due to channel activate failure for LLC transmission ............................................................................. 1376
failure due to BTS connection failure for LLC transmission ............................................................................. 1377
failure due to BIU connection failure for LLC transmission ............................................................................. 1378
success of channel activate for LLC transmission................ 1379
requests for resource request.......................................... 1380
failure due to Abis congestion for resource request ............ 1380
failure due to RR congestion for resource request .............. 1381
failure due to UPPB-DSP channel congestion for resource request ........................................................................... 1382
success due to resource request ...................................... 1383
C901190068 Number of allocated PDCH for GPRS UL TBF resource reallocation due to resource request ...................... 1384
C901190069 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for resource
request ........................................................................ 1385
C901190070 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for resource
request ........................................................................ 1386
C901190071 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for resource
request ........................................................................ 1387
success of channel activate and connection for resource request ........................................................................... 1388
failure due to resource request ........................................ 1389
C901190075 Number of GPRS UL TBF release due to flush
LL ............................................................................... 1389
C901190076 Number of GPRS UL TBF release due to GPRS
CS............................................................................... 1391
C901190078 Number of GPRS UL TBF normal release due to
C901190079 Number of GPRS UL TBF abnormal release due
C901190080 Number of GPRS UL TBF release due to NSVC
unavailability ................................................................ 1393
1331
C901190081 Number of GPRS UL TBF release due to BVC unavailability .................................................................... 1393
C901190082 Number of GPRS UL TBF release due to other
reasons........................................................................ 1394
C901190083 Number of UL GPRS TBF grab resources......... 1395
C901190084 Number of grab instance by UL GPRS TBF......... 1395
C901190085 Number of UL GPRS TBF queuing .................. 1396
C901190086 Number of UL GPRS TBF queuing success......... 1397
C901190087 Number of UL GPRS TBF release TBF during
queuing ....................................................................... 1397
Overview
UL GPRS data TBF statistics collects the information about the establishment, maintain and release of UL GPRS TBF. The statistic
unit is cell.
C901190002 Number
of GPRS UL TBF
on CCCH
Definition
1332
Number of GPRS UL TBF establishment requests on CCCH.
Description
This counter counts the number of channel requests on CCCH when

MS using GPRS service.
Usage

on CCCH when MS attempts using GPRS service.
Measurement
Point
When BSC receives channel requests on CCCH from MS, the

inFigure 1323.
FIGURE 1323 - CHANNEL REQUEST
Usage
Times
C901190003 Number
of EGPRS UL TBF
on CCCH
Definition
Description
Number of EGPRS UL TBF establishment requests on CCCH.

This counter is not meaningful in UL GPRS TBF and is not used.
C901190004 Number
of GPRS UL TBF
on PCCCH
Definition
Number of GPRS UL TBF establishment requests on PCCCH.
Description
This counter counts the number of packet channel requests on

PCCCH when MS attempts using GPRS service.
Usage

on PCCCH when MS attempts using GPRS service.
Measurement
Point
When BSC receives channel requests on PCCCH from MS, the

inFigure 1324.
1333
FIGURE 1324 - PACKET CHANNEL REQUEST
Unit
Times
C901190005 Number
of EGPRS UL TBF
on PCCCH
Definition
Description
Number of EGPRS UL TBF establishment requests on PCCCH.

This counter is not meaningful in UL GPRS TBF statistic, and is not
used.
C901190006 Number
of GPRS UL TBF
on PACCH
Definition
1334
Number of GPRS UL TBF establishment requests on PACCH.
Description
The counter counts the number of UL GPRS TBF establishment

attempts on PACCH.
Usage
This counter is used to find out the number of UL GPRS TBF establishment attempts on PACCH under the situation when DL GPRS
TBF is already established.
Measurement
Point
In the situation when DL GPRS TBF is established, PS control

plane receives UL assignment request message from PS user
plane, the counter increments. The measurement point is A, as
FIGURE 1325 - PACKET CHANNEL REQUEST
Unit
Times
C901190007 Number of cell

attempts for UL assignment
due to ONE PHASE access
Definition
Number of cell attempts for UL assignment due to ONE PHASE

access
Description
This counter counts the number of channel requests on CCCH

when MS attempting UL GPRS TBF establishment or the number
of packet channel requests on PCCCH due to one phase access.
Usage
This counter is used to find out the number of UL GPRS TBF establishment attempts due to one phase access.
Measurement
Point
The counter accumulates at the following two time points:
If BSC receives channel requests from MS on CCCH due to one

phase access, the counter increments. The measurement point
1335
FIGURE 1326 - CHANNEL REQUESTS

ACCESS
ON
CCCH
Related Features
ONE PHASE

FIGURE 1327 - PACKET CHANNEL REQUESTS
PHASE ACCESS
Unit
DUE TO
ON
CCCH
DUE TO
ONE
Times

due to single block packet
access
Definition
1336
Number of cell attempts for UL assignment due to single block

packet access.
Description
This counter counts the number of packet channel requests on PCCCH when MS attempts UL GPRS TBF establishment due to single
block packet access.
Usage
This counter is used to find out the number of packet channel requests when MS attempting UL GPRS TBF establishment due to
single block packet access.
Measurement
Point
If BSC receives channel requests on PCCCH from MS due to single block packet access. The measurement point is A, as shown
inFigure 1328.
Unit
DUE TO
SINGLE BLOCK PACKET ACCESS
Times

due to response paging
Definition
Number of cell attempts for UL assignment due to response paging.
Description
This counter counts the number of packet channel requests when

MS attempting UL GPRS TBF establishment due to response paging.
Usage
response paging.
Measurement
Point
When BSC receives channel requests on PCCCH from MS due to

response paging, the counter increments. The measurement point
1337
FIGURE 1329 - CHANNEL REQUEST DUE TO RESPONSE PAGING
Unit
Times

due to cell updating
Definition
Number of cell attempts for UL assignment due to cell updating.
Description
This counter counts the number of packet channel requests when

MS attempting UL GPRS TBF establishment due to cell update.
Usage
cell update.
Measurement
Point
When BSC receives channel requests on PCCCH from MS duet to

cell update, the counter increments. The measurement point is A,
FIGURE 1330 - CHANNEL REQUESTS
Unit
1338
DUE TO
Times
CELL UPDATE

due to mobility management
Definition
Number of cell attempts for UL assignment due to mobility management
Description
The counter counts the number of packet channel requests on PCCCH when MS attempting UL GPRS TBF establishment due to mobile management.
Usage
mobile management.
Measurement
Point
If BSC receives channel requests on PCCCH from MS due to mobile

management, the counter increments. The measurement point is
FIGURE 1331 - CHANNEL REQUEST DUE TO MOBILE MANAGEMENT
Unit

due to TWO PHASE access
Definition
Number of cell attempts for UL assignment due to TWO PHASE

access
Description
This counter counts the number of channel requests on CCCH

when MS attempting UL GPRS TBF establishment or the number
of packet channel requests on PCCCH due to two phase access.
Usage
This counter is used to find out the number of UL GPRS TBF establishment attempts due to two phase access.
1339
Measurement
Point
If BSC receives channel requests from MS on CCCH due to two

FIGURE 1332 - CHANNEL REQUESTS ON PCCCH DUE TO TWO PHASE
ACCESS

FIGURE 1333 - PACKET CHANNEL REQUESTS ON PCCCH DUE TO TWO
PHASE ACCESS
Unit
Related Features
Times
GB-03-05-008 Two Phase Access

due to short access
Definition
1340
Number of cell attempts for UL assignment due to short access.
Description

PCCCH when MS attempting UL GPRS TBF establishment due to
short access.
Usage
This counter is used to find out the number of UL GPRS TBF establishment attempts due to short access.
Measurement
Point
If BSC receives packet channel requests on PCCCH from MS on

PCCCH due to short access, the counter increments. The measurement point is A, as shown inFigure 1334.
FIGURE 1334 - PACKET CHANNEL REQUESTS ON PCCCH DUE TO SHORT
ACCESS
Unit
Times
C901190015 Number
of GPRS UL TBF
Abis congestion
Definition
Number of GPRS UL TBF establishment failure due to Abis congestion.
Description
The counter records the number of DB resource application failure

when attempting UL GPRS TBF establishment due to Abis congestion.
Usage
This counter is used to find out the number of DB resource application failure when attempting UL GPRS TBF establishment due to
Abis congestion.
Measurement
Point
The counter accumulates at the following three time points:
If PS control plane receives channel requests from MS on CCCH

and fails to apply for DB resource due to Abis congestion, the
inFigure 1335.
1341
FIGURE 1335 - DB RESOURCE REQUESTS FAILURE DUE TO ABIS

CONGESTION (CCCH)
If PS control panel receives channel requests from MS on CCCH

and fails to apply for DB resource due to Abis congestion, the
inFigure 1336.
CONGESTION (PCCCH)
If PS control panel receives UL assignment request messages

from PS user plane on CCCH and fails to apply for DB resource
due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 1337.
CONGESTION (DL GPRS TBF ALREADY ESTABLISHED)
Unit
Related Features
1342
Times
C901190016 Number
of GPRS UL TBF
RR congestion
Definition
Number of GPRS UL TBF establishment failure due to RR congestion.
Description
The counter records the number of DB resource request failure

when attempting UL GPRS TBF establishment due to radio resource
congestion. There are three causes that lead to radio resource
congestion: MS per channel (MS number on each channel reaches
its maximum), no TAI/TFI, and no PDCH.
Usage
RR congestion.
Measurement
Point

and fails to apply for DB resource due to RR congestion, the
inFigure 1338.
FIGURE 1338 - DB RESOURCE REQUESTS FAILURE DUE TO RR
CONGESTION (CCCH)
If PS control panel receives channel requests from MS on CCCH

and fails to apply for DB resource due to RR congestion, the
inFigure 1339.
1343

CONGESTION (PCCCH)

from PS user plane on CCCH and fails to apply for DB resource
due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 1340.
Unit
Related Features
Times
C901190017 Number
of GPRS UL TBF
to UPPB-DSP channel
congestion
Definition
1344
Number of GPRS UL TBF establishment failure due to UPPB-DSP

channel congestion.
Description

when attempting UL GPRS TBF establishment due to UPPB-DSP
channel congestion.
Usage
UPPB-DSP channel congestion.
Measurement
Point

and fails to apply for DB resource due to UPPB-DSP channel
FIGURE 1341 DB RESOURCE REQUESTS FAILURE DUE TO UPPB-DSP
CHANNEL CONGESTION (CCCH)
If PS control panel receives channel requests from MS on PCCCH and fails to apply for DB resource due to UPPB-DSP channel congestion, the counter increments. The measurement
CONGESTION (PCCCH)

from PS user plane on CCCH (DL GPRS TBF already established) and fails to apply for DB resource due to UPPB-DSP
1345
FIGURE 1343 - DB RESOURCE REQUESTS FAILURE DUE TO DPPB-DSP

Unit
Related Features
Times
C901190018 Number
of GPRS UL TBF
allocate success
Definition
Description
This counter counts the number of DB resource request successes

when attempting UL GPRS TBF establishment.
Usage
This counter is used to find out the number of DB resource request

successes when attempting UL GPRS TBF establishment.
Measurement
Point
1346
Number of GPRS UL TBF establishment channel allocate success.

and succeeds in applying for DB resource, the counter increments. The measurement point is A, as shown inFigure 1344.
FIGURE 1344 - DB RESOURCE REQUEST SUCCESSES (CCCH)
If PS control panel receives channel requests from MS on PCCCH and succeed in applying for DB resource, the counter increments. The measurement point is A, as shown inFigure
1345.
FIGURE 1345 - DB RESOURCE REQUEST SUCCESSES (PCCCH)
Unit
Related Features
If only GPRS is supported in the network, PS control plane receives EGPRS channel request on CCCH or on PCCCH from MS,
and DB resource request succeeds, the counter increments.
Times
cell success for GPRS UL
assignment due to ONE
PHASE access
Definition
Number of cell success for GPRS UL assignment due to ONE PHASE

access.
1347
Description
This counter counts the number of successful UL GPRS TBF establishment due to one phase access.
Usage
This counter is used to find out the number of UL GPRS TBF establishment successes due to one phase access.
Measurement
Point

due to one phase access and DB resource requests succeeds,
in Figure 1346.
FIGURE 1346 - CHANNEL REQUEST SUCCESSES ON CCCH DUE TO ONE
PHASE ACCESS

FIGURE 1347 - PACKET CHANNEL REQUEST SUCCESSES ON CCCH DUE
TO ONE PHASE ACCESS
Unit
Related Features
1348
Times
ZGB-03-05-007One Phase Access
assignment due to single
block packet access
Definition
Number of cell success for GPRS UL assignment due to single block

packet access.
Description
The counter counts the number of successful UL GPRS TBF establishment due to single block packet access.
Usage
This counter is used to find out the number of successful UL GPRS

TBF establishment due to single block packet access.
Measurement
Point
If PS control plane receives channel requests on PCCCH from MS

due to single block packet access and DB resource request succeeds, the counter increments. The measurement point is A, as
FIGURE 1348 - CHANNEL REQUESTS SUCCESSES DUE TO SINGLE BLOCK
PACKET ACCESS
Unit
Times
assignment due to response
paging
Definition
Number of cell success for GPRS UL assignment due to response

paging.
1349
Description
The counter counts the number of successful UL GPRS TBF establishment due to response paging.
Usage

TBF establishment due to response paging.
Measurement
Point
When PS control plane receives channel requests on PCCCH from

MS due to response paging and DB resource request succeeds,
inFigure 1349.
FIGURE 1349 - DB RESOURCE REQUEST SUCCESSES DUE TO RESPONSE
PAGING
Unit
Times
cell success for GPRS
UL assignment due to cell
updating
1350
Definition
Number of cell success for GPRS UL assignment due to cell updation.
Description
The counter counts the number of successful UL GPRS TBF establishment due to cell update
Usage

TBF establishment due to cell update.
Measurement
Point
When PS control plane receives channel requests on PCCCH from

MS due to cell update and DB resource request succeeds, the
inFigure 1350.
FIGURE 1350 - DB RESOURCE REQUEST SUCCESSES DUE TO CELL UPDATE
Unit
Times
assignment due to mobility
management
Definition
Number of cell success for GPRS UL assignment due to mobility

management.
Description
The counter counts the number of successful UL GPRS TBF establishment due to mobile management.
Usage

TBF establishment due to mobile management.
Measurement
Point
If PS control plane receives channel requests on PCCCH from MS

due to mobile management and DB resource request succeeds,
inFigure 1351.
FIGURE 1351 - DB RESOURCE REQUEST SUCCESSES DUE TO MOBILE
MANAGEMENT (PCCCH)
1351
Unit
Times
assignment due to TWO
PHASE access
Definition
Number of cell success for GPRS UL assignment due to TWO PHASE

access.
Description
This counter counts the number of successful UL GPRS TBF establishment due to two phase access.
Usage

TBF establishment due to two phase access.
Measurement
Point
If BSC receives channel requests from MS on CCCH due to two

phase access and DB resource request succeeds, the counter
1352.
FIGURE 1352 - DB RESOURCE REQUEST SUCCESSES DUE TO TWO
PHASE ACCESS (CCCH)
1352
If BSC receives channel requests from MS on PCCCH due to two

phase access and DB resource request succeeds, the counter
1353.
FIGURE 1353 - DB RESOURCE REQUEST SUCCESSES ON PCCCH DUE

TO TWO PHASE ACCESS
Unit
Related Features
Times
ZGB-03-05-008Two Phase Access
assignment due to short
access
Definition
Number of cell success for GPRS UL assignment due to short access.
Description
This counter counts the number of successful UL GPRS TBF establishment due to short access.
Usage

TBF establishment due to short access.
Measurement
Point
If BSC receives channel requests from MS on CCCH due to

short access and DB resource request succeeds, the counter
1354.
1353
FIGURE 1354 - DB RESOURCE REQUEST SUCCESSES DUE TO SHORT

ACCESS (PCCCH)
Unit
If only GPRS is supported in the network, PS control plane

receives GPRS channel request on CCCH or on PCCCH from MS,
Times
allocated PDCH for GPRS
Definition
Description
This counter counts the number of successfully assigned PDTCH

when UL GPRS TBF successfully established.
Usage
This counter is used to find out the number of successfully assigned

PDTCH when UL GPRS TBF successfully established.
Measurement
Point
1354
Number of allocated PDCH for GPRS UL TBF establishment.
When PS control plane receives channel requests on CCCH from

MS and DB resource requests succeed, the counter increments.
FIGURE 1355 - DB RESOURCE REQUEST SUCCESSES DUE TO SHORT

ACCESS (PCCCH)
When PS control plane receives packet channel requests on

PCCCH from MS, the counter increments. The measurement
FIGURE 1356 - UL GPRS TBF ESTABLISHMENT ON PCCCH/CCCH
Unit
Related Features
Times
1355
C901190027 Number
of GPRS UL TBF
Definition
Number of GPRS UL TBF establishment failure due to channel activate failed.
Description
This counter counts the number of PDTCH activate failure when

establishing UL GPRS TBF.
Usage
This counter is used to find out the number of PDTCH activate

failure when establishing UL GPRS TBF (including initially establish
UL TBF and establish UL TBF when DL TBF exists).
Measurement
Point
When BSC receives PDTCH channel activate failure message

reported by BTS, the counter increments. The measurement
Unit
1356
When 'wait for PDTCH channel activation and connection response' counter times out and BSC fails to receive PDTCH activate response message reported by BTS, this counter increments.
Times
C901190028 Number
of GPRS UL TBF
Definition
Number of GPRS UL TBF establishment failure due to BTS connection failed.
Description
This counter counts the number of failure to establish UL GPRS

TBF due to BTS connection failure.
Usage
This counter is used to find out the number of UL GPRS TBF establishment failure (including initially establish UL TBF and establish
UL TBF when DL TBF exists) due to BTS connection failure.
Measurement
Point
When PS control plane receives connection failure message reported by connection module due to BTS connection failure, the
Figure 1358.
Unit
When 'wait for PDTCH channel activate and connection response' counter times out and BSC fails to receive connection
success response message reported by connection module,
Times
1357
C901190029 Number
of GPRS UL TBF
Definition
Number of GPRS UL TBF establishment failure due to BIU connection failed.
Description

TBF due to BIU connection failure.
Usage
This counter is used to find out the number of UL GPRS TBF establishment failure (including initially establish UL TBF and establish
UL TBF when DL TBF exists) due to BIU connection failure.
Measurement
Point
When PS control plane receives connection failure message

reported by connection modules due to BIU connection failure,
inFigure 1359.
Usage
Times
GPRS UL TBF channel
success
Definition
1358
Number of GPRS UL TBF channel activate establishment success.
Description
This counter counts the number of channel activate and connection

successes when establishing UL GPRS TBF.
Usage
This counter is used to find out the number of channel activate and
connection successes when establishing UL GPRS TBF.
Measurement
Point
When PS control plane receives channel activate response message reported by BTS and connection successes acknowledgement
Unit
Times
C901190031 Number
of GPRS UL TBF
not receive PIA
Definition
Number of GPRS UL TBF establishment failure due to not receive

PIA.
Description
This counter counts the number of failure to send immediate assignment message to MS when establishing UL GPRS TBF.
Usage
This counter is used to find out the number of failure to send immediate assignment message to MS when establishing UL GPRS
TBF.
Measurement
Point
When PS control plane receives immediate assignment failure

message reported by BTS, the counter increments.
When 'wait for immediate assignment and sending indication'

counter times out and BSC fails to receive immediate assignment and sending indication message, the counter increments.
1359
Usage
Times
GPRS UL TBF establisment
failure on PCCCH/CCCH
due to UPPB-DSP
congestion
Definition
Number of GPRS UL TBF establishment failure on PCCCH/CCCH

Description

TBF.
Usage
This counter is used to find out the number of failure to establish

UL GPRS TBF.
Measurement
Point
When PS control plane assigns single block through two phase access from PS user plane, or gets access to PS user plane through
one phase access and starts assignment timer. If the timer times
out, resource request from PS user plane (two phase access) is
not received or indication (one phase access) is not established,
inFigure 1361 .
Unit
1360
Times
GPRS UL TBF establisment
UPPB-DSP congestion
Definition
Description
Number of GPRS UL TBF establishment failure on PACCH due to

This counter is not used currently.
C901190034 Number
of GPRS UL TBF
on PCCCH/CCCH
Definition
Number of GPRS UL TBF establishment success on PCCCH/CCCH
Description
This counter counts the number of successful UL GPRS TBF establishment and receiving MS TLL1.
Usage

TBF establishment and receiving MS TLL1.
Measurement
Point
When PS control plane receives MS TLL1 'MAC establishment

indication' message reported by PS user plane in the premise of
one phase access, the counter increments. The measurement
FIGURE 1362 - UL ONE-PHASE-ACCESS RESOURCE ASSIGNMENT
SUCCESSES
1361
PS control plane receives resource request message from PS

user plane in the premise of two phase access, the counter
1363 .
FIGURE 1363 - UL TWO-PHASE-ACCESS SINGLE BLOCK ASSIGNMENT
SUCCESSES
Unit
Times
C901190035 Number
of GPRS UL TBF
on PACCH
Definition
Description
Number of GPRS UL TBF establishment success on PACCH.

Abis congestion for DL TBF
establishment
Definition
1362
Number of GPRS UL TBF resource reallocation failure due to Abis

congestion for DL TBF establishment.
Description
In the situation when UL GPRS TBF is already established, DL

TBF is needed to be established on PACCH; DB resource request
fails which leads to UL resource reallocation failure. The counter
records the number of UL resource reallocation failure due to Abis
resource congestion.
Usage
This counter is used to find out the number of UL GPRS TBF reallocation failure due to Abis congestion.
Measurement
Point
In the situation when UL GPRS TBF is established, PS control plane

receives DL assignment request message from PS user plane, and
DB resource request fails due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 1364 .
CONGESTION
Unit
Related Features
Times
RR congestion for DL TBF
establishment
Definition
Number of GPRS UL TBF resource reallocation failure due to RR

Description

records the number of UL resource reallocation failure due to Abis
There are three causes which lead to radio resource congestion:
MS per channel (MS number per channel reaches its maximum),
TAI/TFI (no TAI or TFI available) and no PDCH available.
1363
Usage
This counter is used to find out the number of UL GPRS TBF reallocation failure due to RR congestion.
Measurement
Point

DB resource request fails due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 1365.
Unit
Related Features
DUE TO
RR CONGESTION
Times
to UPPB-DSP channel
congestion for DL TBF
establishment
1364
Definition
Number of GPRS UL TBF resource reallocation failure due to UPPB

-DSP channel congestion for DL TBF establishment.
Description

records the number of UL resource reallocation failure due to
UPPB-DSP channel resource congestion.
Usage
This counter is used to find out the number of UL GPRS TBF reallocation failure due to UPPB-DSP channel congestion.
Measurement
Point

DB resource request fails due to UPPB-DSP channel congestion,
inFigure 1366.

CHANNEL CONGESTION
Unit
Related Features
DUE TO
UPPB-DSP
Times
channel allocation due to DL
TBF establishment
Definition
Number of GPRS UL TBF resource reallocation success of channel

allocation due to DL TBF establishment.
Description
The counter records the number of successful DL TBF establishment on PACCH when UL GPRS TBF is already established.
Usage
This counter is used to find out the number of DL GPRS TBF reallocation successes.
Measurement
Point

DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 1367.
FIGURE 1367 SUCCESSFUL RESOURCE APPLICATION
1365
Unit
Related Features
Times
C901190042 Number
reallocation due to DL TBF
establishment
Definition
Number of allocated PDCH for GPRS UL TBF resource reallocation

success due to DL TBF establishment.
Description
The counter records the number of successful allocated PDTCH

when UL GPRS TBF is successfully reallocated.
Usage

PDTCH when UL GPRS TBF is successfully reallocated.
Measurement
Point

DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 1368.
Unit
Related Features
1366
Times
GPRS UL TBF resourse
Definition
Number of GPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment.
Description
The counter records the number of PDTCH activate failure during

UL GPRS TBF resource reallocation.
Usage

failure during UL GPRS TBF resource reallocation.
Measurement
Point

from BTS, the counter increments. The measurement point is
A, as shown inFigure 1369 .
FIGURE 1369 - PDTCH ACTIVATION FAILURE
Unit
When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive PDTCH channel activate response message from BTS, the counter increments.
Times
1367
Definition
Number of GPRS UL TBF resourse reallocation failure due to BTS

connection failure for DL TBF establishment.
Description
The counter records the number of BTS connection failure during

Usage
This counter is used to find out the number of BTS connection

Measurement
Point

from connection module due to BTS connection failure, the
inFigure 1370 .
Unit
1368
When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive connection
success message from connection module, the counter increments.
Times
BIU connection failure for DL
TBF establishment
Definition
Number of GPRS UL TBF resourse reallocation failure due to BIU

Description
The counter records the number of BIU connection failure during

Usage
This counter is used to find out the number of BIU connection failure during UL GPRS TBF resource reallocation.
Measurement
Point
When PS control plane receives connection failure message from

connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown inFigure 1371.
Unit
Times
1369
connection for DL TBF
establishment
Definition

activate and connection for DL TBF establishment
Description
The counter records the number of channel activate and connection successes during UL GPRS TBF resource reallocation.
Usage
connection successes during UL GPRS TBF resource reallocation.
Measurement
Point
When PS control plane receives channel activate ack message and

connection success ack message from connection module due to
BIU connection failure, the counter increments. The measurement
Unit
1370
Times
reallocation failure due to DL
TBF establishment
Definition
Description
Related Features
Number of GPRS UL TBF resource reallocation failure due to DL

TBF establishment.
Definition
Description
Related Features
Number of GPRS UL TBF resource reallocation success due to DL

TBF establishment.
transmission
Definition

congestion for LLC transmission
Description
During UL GPRS TBF transmission process, PS user plane sends resource reallocation message to PS control plane due to LLC frame
change; PS control plane requests DB resource after receiving the
message. The counter records the number of DB resource request
1371
failure due to Abis resource congestion after PS control plane receiving resource reallocation request during UL GPRS TBF transmission process.
Usage
This counter is used to find out DB resource request failure due to

Abis resource congestion after PS control plane receiving resource
reallocation request during UL GPRS TBF transmission process.
Measurement
Point
When PS control plane receives resource reallocation message

from PS user plane, and DB resource request fails due to Abis
congestion, the counter increments. The measurement point is
CONGESTION
Unit
Related Features
Times
transmission
Definition

congestion for LLC transmission
Description
During UL GPRS TBF transmission process, PS user plane sends resource reallocation message to PS control plane due to LLC frame
failure due to radio resource congestion after PS control plane receiving resource reallocation request during UL EGPRS TBF transmission process.
There are three causes leading to RR congestion: MS per channel
(reaches its maximum), TAI/TFI (not available), and no PDTCH.
1372
Usage

RR congestion after PS control plane receiving resource reallocation request during UL EGPRS TBF transmission process.
Measurement
Point

from PS user plane, and DB resource request fails due to RR
congestion, the counter increments. The measurement point is A,
Unit
Related Features
Times
to UPPB-DSP channel
congestion for LLC
transmission
Definition
Number of GPRS UL TBF resource reallocation failure due to UPPBDSP channel congestion for LLC transmission.
Description
During UL EGPRS TBF transmission process, PS user plane sends

resource reallocation message to PS control plane due to LLC frame
change; PS control plane requests DBresource after receiving the
failure due to UPPB-DSP channel congestion after PS control plane
receiving resource reallocation request during UL GPRS TBF transmission process.
Usage
This counter is used to find out DB resource request failure due

to UPPB-DSP channel congestion after PS control plane receiving
1373
resource reallocation request during UL GPRS TBF transmission

process.
Measurement
Point

from PS user plane, and DB resource request fails due to
UPPB-DSP channel congestion, the counter increments. The
FIGURE 1375 - RESOURCE APPLICATION FAILURE DUE TO UPPPB-DSP
Unit
Related Features
Times
LLC transmission
1374
Definition

allocation due to LLC transmission
Description

successes after PS control plane receiving resource reallocation request during UL EGPRS TBF transmission process.
Usage
This counter is used to find out DB resource request success due

after PS control plane receiving resource reallocation request during UL EGPRS TBF transmission process.
Measurement
Point

from PS user plane, and DB resource request succeeds, the
inFigure 1376.
FIGURE 1376 RELEASE REQUEST DUE TO FLUSH LL
Unit
Related Features
Times
C901190055 Number
transmission
Definition
Number of allocated PDTCH for GPRS UL TBF resource reallocation

Description

message. The counter records the number of successfully allocated PDTCH after PS control plane receiving resource reallocation
requests during UL GPRS TBF.
Usage

PDTCH when UL GPRS TBF is successfully reallocated.
Measurement
Point

inFigure 1377.
Unit
Times
1375
Related Features
LLC transmission
Definition
Number of GPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment
Description
The counter records the number of PDTCH activate failure after

BSC receiving resource reallocation request during UL GPRS TBF
Usage

Measurement
Point

Unit
1376
Times
LLC transmission
Definition
Number of GPRS UL TBF resource reallocation failure due to BTS

connection failure for LLC transmission
Description
The counter records the number of connection failure due to BTS

connection failure after BSC receiving resource reallocation request during UL GPRS TBF transmission.
Usage

failure during UL GPRS TBF resource transmission.
Measurement
Point

inFigure 1379.
FAILURE
Unit
Times
1377
LLC transmission
Definition
Number of GPRS UL TBF resource reallocation failure due to BIU

Description

UL GPRS TBF transmission.
Usage
This counter is used to find out the number of BIU connection failure during UL GPRS TBF transmission.
Measurement
Point

FIGURE 1380 - CONNECTION FAILED
Unit
1378
DUE TO
Times
BIU CONNECTION FAILURE
channel activate for LLC
transmission
Definition

activate for LLC transmission.
Description
The counter records the number of channel activate and connection successes during UL GPRS TBF transmission.
Usage
connection successes during UL GPRS TBF tranmission.
Measurement
Point

Unit
Times
LLC transmission
Definition
Description
Related Features
Number of GPRS UL TBF resource reallocation failure due to LLC

transmission.
1379
LLC transmission
Definition
Description
Related Features
Number of GPRS UL TBF resource reallocation success due to LLC

transmission.
resource request
Definition
Description
Number of GPRS UL TBF resource reallocation requests for resource request.

Abis congestion for resource
request
1380
Definition

congestion for resource request
Description
The counter records the number of DB resource request failure due

to Abis congestion after PS control plane resource request from MS
during UL GPRS TBF.
Usage

failure after PS control plane receives resource request from MS
during UL GPRS TBF process (including UL two-phase access and

UL TBF transmission).
Measurement
Point
PS control plane receives resource request message from PS user

plane, and DB resource request fails due to Abis congestion, the
Figure 1382.
CONGESTION (RESOURCE REQUEST)
Unit
Related Features
Times
RR congestion for resource
request
Definition

congestion for resource request.
Description

after PS control plane receives resource request from MS due to
RR congestion during UL GPRS TBF.
There are three cause leading to radio resource congestion: MS
per channel (MS number per channel reaches its maximum),
TAI/TFI (no TAI/TFI available), no PDCH (no PS service channel
available)
Usage

due to RR congestion during UL GPRS TBF process (including UL
two-phase access and UL TBF transmission).
1381
Measurement
Point

plane, and DB resource request fails due to RR congestion, the
Figure 1383.
FIGURE 1383 - DB RESOURCE REQUESTS FAILURE DUE TO RR CONGESTION
Unit
Related Features
Times
to UPPB-DSP channel
congestion for resource
request
1382
Description

UPPB-DSP channel congestion during UL GPRS TBF.
Usage

due to UPPB-DSP channel congestion during UL GPRS TBF process
(including UL two-phase access and UL TBF transmission).
Measurement
Point

Figure 1384.
FIGURE 1384 DB RESOURCE REQUESTS FAILURE

CHANNEL CONGESTION (RESOURCE REQUEST)
Unit
Related Features
DUE TO
UPPB-DSP
Times
resource request
Description
The counter records the number of successful DB resource request

after PS control plane receives resource request message from MS
during UL GPRS TBF process.
Usage

successes after PS control plane receives resource request from
MS during UL GPRS TBF process (including UL two-phase access
and UL TBF transmission).
Measurement
Point

plane, and DB resource request succeeds, the counter increments.
FIGURE 1385 DB RESOURCE REQUESTS SUCCESSES (RESOURCE REQUEST)
1383
Unit
Related Features
Times
C901190068 Number
reallocation due to resource
request
Description
The counter records the number of successful allocated PDTCH after PS control plane receives resource request message from MS
during UL GPRS TBF process.
Usage

PDTCH after PS control plane receives resource request from MS
during UL GPRS TBF process (including UL two-phase access and
Measurement
Point

FIGURE 1386 DB RESOURCE REQUESTS SUCCESSES (RESOURCE REQUEST)
Unit
Related Features
1384
Times
resource request
Definition
Number of GPRS UL TBF resource reallocation failure due to channel activate failure for resource request.
Description

UL GPRS TBF resource reallocation after PS control plane receives
resource request message.
Usage

UL GPRS TBF resource reallocation after PS control plane receives
resource request message in UL GPRS TBF process (including UL
two-phase access and one-phase TBF transmission).
Measurement
Point

Unit
Times
1385
resource request
Definition
Number of GPRS UL TBF resource reallocation failure due to BTS

connection failure for resource request.
Description

connection failure during UL GPRS TBF resource reallocation after
PS control plane receives resource request message.
Usage

PS control plane receives resource request message in UL GPRS
TBF process (including UL two-phase access and one-phase TBF
transmission).
Measurement
Point

inFigure 1388 .
Unit
1386
Times
resource request
Definition
Number of GPRS UL TBF resource reallocation failure due to BIU

connection failure for resource request
Description
The counter records the number of connection failure due to BIU

Usage

transmission).
Measurement
Point

Unit
Times
1387
connection for resource
request
Definition

activate and connection for resource request
Description
The counter records the number of channel activate and connection successes during UL GPRS TBF resource reallocation after PS
control plane receives resource request message.
Usage
The counter records the number of channel activate and connection failure during UL GPRS TBF resource reallocation after PS
control plane receives resource request message in UL GPRS TBF
process (including UL two-phase access and one-phase TBF transmission).
Measurement
Point

Unit
1388
Times
resource request
Definition
Description
Related Features
Number of GPRS UL TBF resource reallocation failure due to resource request.

resource request
Definition
Description
Related Features
Number of GPRS UL TBF resource reallocation failure due to reallocation success due to resource request.
to flush LL
Definition
Number of GPRS UL TBF release due to flush LL.
Description
This counter counts the number of UL GPRS TBF release after PS

control plane receiving request due to flush LL.
Usage
This counter is used to find out the number of UL GPRS TBF release
after PS control plane receiving request due to flush LL.
Measurement
Point
When PS control plane of BSC receives FLUSH message from SGSN

and release is executed when UL GPRS TBF is established, the
Figure 1391.
1389
Unit
Times
Definition
Number of GPRS UL TBF release due to GPRS suspend requests.
Description
This counter counts the number of UL GPRS TBF release after PS

control plane receiving request due to GPRS suspend requests.
Usage
due to GPRS suspend requests.
Measurement
Point
When PS control plane of BSC receives SUSPEND message from

SGSN and release is executed when UL GPRS TBF is established,
inFigure 1392.
Unit
1390
DUE TO
Times
SUSPEND REQUEST
GPRS UL TBF forcing
release by CS
Definition
Number of GPRS UL TBF forcing release by CS.
Description
This counter counts the number of UL GPRS TBF forcing release

by CS.
Usage
This counter is used to find out the number of UL GPRS TBF forcing
release by CS.
Measurement
Point
When PS control plane of BSC receives PDCH RELEASE message from

CS control plane when UL GPRS TBF is established, the counter
Unit
DUE TO
PDCH REL
Times
GPRS UL TBF normal
requests
Definition
Number of GPRS UL TBF normal release due to user plane requests.
Description
This counter counts the number of UL GPRS TBF normal release

due to user plane requests.
Usage
This counter is used to find out the number of UL GPRS TBF normal
release due to user plane requests.
Measurement
Point
When PS control plane of BSC receives NORMAL RELEASE REQUEST message from PS user plane when UL GPRS TBF exists, the counter
1391
FIGURE 1394 - NORMAL RELEASE REQUEST
Unit
Times
GPRS UL TBF abnormal
requests
Definition
Number of GPRS UL TBF abnormal release due to user plane requests.
Description
This counter counts the number of UL GPRS TBF abnormal release

Usage
This counter is used to find out the number of UL GPRS TBF abnormal release due to user plane requests.
Measurement
Point
When PS control plane receives ABNORMAL RELEASE REQUEST message

from PS user plane when UL GPRS TBF exists, the counter increments. The measurement point is A, as shown inFigure 1395.
BY MAC
Unit
1392
DUE TO
Times
Definition
Number of GPRS UL TBF release due to NSVC unavailability.
Description
This counter counts the number of UL GPRS TBF release due to

Usage
after receiving forcing release request due to NSVC unavailability.
Measurement
Point
When PS control plane receives NSVC unavailability command to

release PS control plane module from DB when UL GPRS TBF exists, the counter increments. The measurement point is A, as
Unit
DUE TO
NVSC UNAVAILABILITY
Times
Definition
Number of GPRS UL TBF release due to BVC unavailability.
Description
This counter counts the number of UL GPRS TBF release due to

BVC unavailability.
Usage
after receiving forcing release request due to BVC unavailability.
Measurement
Point
When PS control plane receives BVC unavailability command to release PS control plane module from DB when UL GPRS TBF exists,
inFigure 1397.
1393
Unit
Times
to other reasons
Definition
Number of GPRS UL TBF release due to other reasons.
Description
This counter counts the number of UL GPRS TBF forcing release

due to other reasons.
Usage
after receiving forcing release request due to other reasons.
Measurement
Point
When PS control plane receives release message due to other reasons when UL GPRS TBF exists, the counter increments. The measurement point is A, as shown inFigure 1398.
Unit
1394
Times
GPRS TBF grab resources
Definition
Description
Number of UL GPRS TBF grab resources.

This counter counts the number of UL GPRS TBF grab resources.
Usage
This counter is used to find out the frequency for UL GPRS TBF
grabbing other TBF.
Measurement
Point
This counter increments while UL GPRS TBF is established during

TBF resource is grabbed. Measurement point is A, as shown
inFigure 1399.
FIGURE 1399 - UL GPRS RESOURCE REQUEST SUCCESS
Unit
Related Features
Times
grab instance by UL GPRS
TBF
Definition
Number of grab instance by UL GPRS TBF.
Description
This counter counts the number of grab instance by UL GPRS TBF.
Usage
Measurement
Point

TBF resource is grabbed. Measurement point is A, as shown
inFigure 1400.
1395
Unit
Related Features
Times
GPRS TBF queuing
Definition
Description
Number of UL GPRS TBF queuing.

This counter counts the number of UL GPRS TBF queuing.
Usage
Measurement
Point

A as shown inFigure 1401.
Unit
Related Features
1396
Times
GPRS TBF queuing success
Definition
Number of UL GPRS TBF queuing success.
Description
This counter counts the number of UL GPRS TBF queuing success.
Usage
queuing success.
Measurement
Point
This counter increments while UL GPRS TBF is established during resource adjustment, the instance to be queued successfully
assigns resource for user plane, and database is successfully registered. Measurement point is A as shown inFigure 1402.
FIGURE 1402 - RESOURCE ASSIGNMENT SUCCESS
Unit
Related Features
Times
GPRS TBF release TBF
during queuing
Definition
Number of UL GPRS TBF release TBF during queuing.
Description
This counter counts the number of UL GPRS TBF release during

queuing.
Usage
Measurement
Point
This counter increments while UL GPRS TBF is released and instance still in queuing state. The measurement point is A as shown
inFigure 1403.
1397
FIGURE 1403 - RELEASE UL GPRS TBF
Unit
Related Features
1398
Times
Chapter
26
Uplink EGPRS Data TBF

Statistics
Table of Contents
Overview...................................................................... 1402
on CCCH ...................................................................... 1402
C901200003 Number of EGPRS UL TBF establishment requests on CCCH ............................................................ 1402
on PCCCH..................................................................... 1403
C901200005 Number of EGPRS UL TBF establishment requests on PCCCH........................................................... 1403
on PACCH..................................................................... 1404
to ONE PHASE access..................................................... 1405
to single block packet access........................................... 1406
to response paging ........................................................ 1406
to cell updating ............................................................. 1407
to mobility management................................................. 1407
to TWO PHASE access .................................................... 1407
to short access.............................................................. 1408
C901200018 Number of EGPRS UL TBF establishment channel
C901200019 Number of cell success for EGPRS UL assignment
due to ONE PHASE access............................................... 1414
due to single block packet access .................................... 1416
due to response paging .................................................. 1416
due to cell updating ....................................................... 1416
due to mobility management........................................... 1417
1399

due to TWO PHASE access .............................................. 1417
due to short access........................................................ 1418
establishment ............................................................... 1420
due to BIU connection failed .......................................... 1422
C901200030 Number of EGPRS UL TBF channel activate establishment success....................................................... 1423
due to not receive PIA.................................................... 1424
on PCCCH/CCCH due to UPPB-DSP congestion ................... 1425
on PCCCH/CCCH............................................................ 1426
on PACCH..................................................................... 1427
C901200038 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for DL TBF establishment ........................................................................... 1428
failure due to RR congestion for DL TBF establishment......... 1429
failure due to UPPB-DSP channel congestion for DL TBF establishment .................................................................. 1430
C901200041 Number of EGPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment ........................................................................... 1431
resource reallocation due to DL TBF establishment ............. 1432
failure due to channel activate failure for DL TBF establishment ........................................................................... 1433
failure due to BTS connection failure for DL TBF establishment ........................................................................... 1434
failure due to BIU connection failure for DL TBF establishment ........................................................................... 1435
success of channel activate and connection for DL TBF establishment....................................................................... 1436
failure due to DL TBF establishment ................................. 1437
success due to DL TBF establishment ............................... 1437
failure due to UPPB-DSP channel congestion for LLC transmission ............................................................................. 1439
1400
Chapter 26 Uplink EGPRS Data TBF Statistics

resource reallocation due to LLC transmission ................... 1441
C901200056 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for LLC transmission ............................................................................. 1442
C901200057 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for LLC transmission ............................................................................. 1443
C901200058 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for LLC transmission ............................................................................. 1444
success of channel activate for LLC transmission................ 1445
requests for resource request.......................................... 1447
failure due to Abis congestion for resource request ............ 1447
failure due to RR congestion for resource request .............. 1448
failure due to UPPB-DSP channel congestion for resource request ........................................................................... 1449
C901200067 Number of EGPRS UL TBF resource reallocation success due to database allocation for resource
request ........................................................................ 1450
resource reallocation due to resource request.................... 1451
C901200069 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for resource request ........................................................................... 1452
C901200070 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for resource request ........................................................................... 1453
C901200071 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for resource request ........................................................................... 1454
success of channel activate and connection for resource request ........................................................................... 1455
failure due to resource request ........................................ 1456
C901200075 Number of EGPRS UL TBF release due to flush
LL ............................................................................... 1457
C901200076 Number of EGPRS UL TBF release due to GPRS
CS............................................................................... 1458
C901200078 Number of EGPRS UL TBF normal release due to
C901200079 Number of EGPRS UL TBF abnormal release due
1401
C901200080 Number of EGPRS UL TBF release due to NSVC

unavailability ................................................................ 1460
C901200081 Number of EGPRS UL TBF release due to BVC
unavailability ................................................................ 1461
C901200082 Number of EGPRS UL TBF release due to other
reasons........................................................................ 1461
C901200083 Number of UL EGPRS TBF grab resources......... 1462
C901200084 Number of grab instance by UL EGPRS
TBF ............................................................................. 1463
C901200085 Number of UL EGPRS TBF queuing ................ 1463
C901200086 Number of UL EGPRS TBF queuing success............................................................................. 1464
C901200087 Number of UL EGPRS TBF release TBF during
queuing ....................................................................... 1465
Overview
UL EGPRS data TBF statistics collects the information about the
establishment, maintain and release of UL EGPRS TBF. The statistic
unit is cell.
C901200002 Number
of GPRS UL TBF
on CCCH
Definition
Description
Number of GPRS UL TBF establishment requests on CCCH

C901200003 Number
of EGPRS UL TBF
on CCCH
Definition
Description
1402
Number of EGPRS UL TBF establishment requests on CCCH.

This counter counts the number of EGPRS channel requests on
CCCH when MS using EGPRS service.
Usage

on CCCH when MS attempts using EGPRS service.
Measurement
Point
When BSC receives channel requests on CCCH from MS, the

inFigure 1404.
FIGURE 1404 - EGPRS CHANNEL REQUEST
Unit
Related Features
Times
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
C901200004 Number
of GPRS UL TBF
on PCCCH
Definition
Description
Number of GPRS UL TBF establishment requests on PCCCH.

The counter is not used.
C901200005 Number
of EGPRS UL TBF
on PCCCH
Definition
Description
Number of EGPRS UL TBF establishment requests on PCCCH.

PCCCH when MS attempts using EGPRS service.
1403
Usage

on PCCCH when MS attempts using EGPRS service.
Measurement
Point
When BSC receives channel requests on PCCCH from MS, the

Figure 1405.
FIGURE 1405 - EGPRS PACKET CHANNEL REQUEST
Unit
Times
C901200006 Number
of GPRS UL TBF
on PACCH
Definition
1404
Number of GPRS UL TBF establishment requests on PACCH.
Description
The counter counts the number of UL EGPRS TBF establishment

attempts on PACCH.
Usage
This counter is used to find out the number of UL EGPRS TBF establishment attempts on PACCH under the situation when DL GPRS
TBF is already established.
Measurement
Point
In the situation when DL EGPRS TBF is established, PS control

plane receives UL assignment request message from PS user
plane, the counter increments. The measurement point is A, as
FIGURE 1406 - UL ASSIGNMENT REQUEST (DL GPRS TBF ALREADY

ESTABLISHED)
Unit
Times

due to ONE PHASE access
Definition
Number of cell attempts for UL assignment due to ONE PHASE

access.
Description

MS attempting UL EGPRS TBF establishment or the number of
packet channel requests on PCCCH due to one phase access.
Usage
This counter is used to find out the number of UL EGPRS TBF establishment attempts due to one phase access.
Measurement
Point

is A, as shown inFigure 1407 .
FIGURE 1407 - EGPRS CHANNEL REQUESTS ON CCCH DUE TO ONE
PHASE ACCESS
If BSC receives EGPRS Packet channel request from MS on PCCCH due to one phase access, the counter increments. The
1405
FIGURE 1408 - EGPRS PACKET CHANNEL REQUESTS ON CCCH DUE

TO ONE PHASE ACCESS
Unit
Related Features
Times

due to single block packet
access
Definition
Description
Related Features
Number of cell attempts for UL assignment due to single block

packet access

due to response paging
Definition
Description
Related Features
1406
Number of cell attempts for UL assignment due to response paging.


due to cell updating
Definition
Description
Related Features
Number of cell attempts for UL assignment due to cell updating.


due to mobility management
Definition
Description
Related Features
Number of cell attempts for UL assignment due to mobility management

The counter is not used currently.

due to TWO PHASE access
Definition
Number of cell attempts for UL assignment due to TWO PHASE

access.
Description

MS attempting UL EGPRS TBF establishment or the number of
packet channel requests on PCCCH due to two phase access.
Usage
This counter is used to find out the number of UL EGPRS TBF establishment attempts due to two phase access.
Measurement
Point
If BSC receives EGPRS channel requests from MS on CCCH due

to two phase access, the counter increments. The measurement point is A, as shown in Figure 1409.
1407
FIGURE 1409 - EGPRS CHANNEL REQUESTS ON CCCH DUE TO TWO

PHASE ACCESS
If BSC receives EGPRS Packet channel request from MS on

CCCH due to one phase access, the counter increments. The
FIGURE 1410 - EGPRS PACKET CHANNEL REQUESTS ON PCCCH DUE
TO TWO PHASE ACCESS
Unit
Related Features
Times

due to short access
Definition
Description
This counter counts the number of EGPRS channel request on

CCCH or EGPRS Packet channel request on PCCCH when MS
attempting UL EGPRS TBF establishment due to short access.
Usage
This counter is used to find out the number of UL EGPRS TBF establishment attempts due to short access.
Measurement
Point
1408
Number of cell attempts for UL assignment due to short access.

to short access, the counter increments. The measurement
FIGURE 1411 - EGPRS CHANNEL REQUESTS ON CCCH DUE TO SHORT

ACCESS
If BSC receives EGPRS Packet channel request from MS on PCCCH due to short access, the counter increments. The measurement point is A, as shown in Figure 1412.
FIGURE 1412 - EGPRS PACKET CHANNEL REQUESTS ON PCCCH DUE
TO SHORT ACCESS
Unit
Related Features
Times
C901200015 Number
of EGPRS UL TBF
Abis congestion
Definition
Number of EGPRS UL TBF establishment failure due to Abis congestion.
Description

when attempting UL EGPRS TBF establishment due to Abis congestion.
Usage
This counter is used to find out the number of DB resource application failure when attempting UL EGPRS TBF establishment due
to Abis congestion.
1409
Measurement
Point
If PS control plane receives EGPRS channel requests from MS

on CCCH or EGPRS Packet channel requests on PCCCH and fails
to apply for DB resource due to Abis congestion, the counter
1413.
CONGESTION (EGPRS)
If PS control panel receives UL channel requests from PS user

plane when DL EGPRS TBF exists and fails to apply for DB resource due to Abis congestion, the counter increments. The
Unit
Related Features
Times
C901200016 Number
of EGPRS UL TBF
RR congestion
Definition
1410
Number of EGPRS UL TBF establishment failure due to RR congestion.
Description

when attempting UL EGPRS TBF establishment due to radio resource congestion. There are three causes that lead to radio resource congestion: MS per channel (MS number on each channel
reaches its maximum), no TAI/TFI and no PDCH.
Usage
to RR congestion.
Measurement
Point
If PS control plane receives EGPRS channel request from MS

on CCCH or EGPRS Packet channel request on PCCCH and fails
to apply for DB resource due to RR congestion, the counter
increments. The measurement point is A, as shown Figure
1415.
CONGESTION (EGPRS)
If PS control panel receives UL channel requests from PS user

plane when DL EGPRS TBF exists and fails to apply for DB resource due to RR congestion, the counter increments. The
Unit
Related Features
Times
1411
C901200017 Number
of EGPRS UL TBF
to UPPB-DSP channel
congestion
Definition
Number of EGPRS UL TBF establishment failure due to UPPB-DSP

channel congestion
Description

when attempting UL EGPRS TBF establishment due to UPPB-DSP
channel congestion.
Usage
to UPPB-DSP channel congestion.
Measurement
Point

to apply for DB resource due to UPPB-DSP channel congestion,
in Figure 1417.
FIGURE 1417 - DB RESOURCE REQUESTS FAILURE DUE TO UPPB-DSP
CHANNEL CONGESTION (EGPRS)
1412


Unit
Related Features
Times
C901200018 Number
of EGPRS UL TBF
allocate success
Definition
Number of EGPRS UL TBF establishment channel allocate success.
Description
This counter counts the number of DB resource request successes

when attempting UL EGPRS TBF establishment.
Usage

successes when attempting UL GPRS TBF establishment.
Measurement
Point
If PS control plane receives EGPRS channel requests from MS on

CCCH or EGPRS Packet channel request on PCCCH and succeeds in
applying for DB resource, the counter increments. The measurement point is A, as shown in Figure 1419.
1413
FIGURE 1419 - DB RESOURCE REQUEST SUCCESSES (EGPRS)
Unit
Related Features
Times
cell success for EGPRS
UL assignment due to ONE
PHASE access
Definition
Number of EGPRS UL TBF establishment failure due to UPPB-DSP

channel congestion.
Description

when attempting UL EGPRS TBF establishment due to UPPB-DSP
channel congestion.
Usage
to UPPB-DSP channel congestion.
Measurement
Point
1414

to apply for DB resource due to UPPB-DSP channel congestion,
inFigure 1420

CHANNEL CONGESTION (EGPRS)

is A, as shown inFigure 1421
FIGURE 1421 - DB RESOURCE REQUESTS FAILURE DUE TO DPPB-DSP
Unit
Related Features
Times
1415
cell success for EGPRS UL
assignment due to single
block packet access
Definition
Description
Related Features
Number of cell success for EGPRS UL assignment due to single

block packet access
This counter is not used.
assignment due to response
paging
Definition
Description
Related Features
Number of cell success for EGPRS UL assignment due to response

paging
cell success for EGPRS
UL assignment due to cell
updating
Definition
Description
Related Features
1416
Number of cell success for EGPRS UL assignment due to cell updating.

assignment due to mobility
management
Definition
Description
Related Features
Number of cell success for EGPRS UL assignment due to mobility

management.
assignment due to TWO
PHASE access
Definition
Number of cell success for EGPRS UL assignment due to TWO

PHASE access.
Description
This counter counts the number of successful UL EGPRS TBF establishment due to two phase access.
Usage
This counter is used to find out the number of successful UL EGPRS

TBF establishment due to two phase access.
Measurement
Point

to two phase access and DB resource request succeeds, the
Figure 1422.
1417
FIGURE 1422 - EGPRS DB RESOURCE REQUEST SUCCESSES DUE TO

TWO PHASE ACCESS (CCCH)
If BSC receives EGPRS packet channel requests from MS on

PCCCH due to two phase access and DB resource request succeeds, the counter increments. The measurement point is A,
FIGURE 1423 - DB RESOURCE REQUEST SUCCESSES ON PCCCH DUE
TO TWO PHASE ACCESS
Unit
Related Features
Times
assignment due to short
access
Definition
1418
Number of cell success for EGPRS UL assignment due to short access.
Description
This counter counts the number of successful UL EGPRS TBF establishment due to short access.
Usage

TBF establishment due to short access.
Measurement
Point

to short access and DB resource request succeeds, the counter
1424.
SHORT ACCESS (CCCH)
If BSC receives EGPRS packet channel requests from MS on

PCCCH due to short access and DB resource request succeeds,
in Figure 1425.
SHORT ACCESS (PCCCH)
Unit
Related Features
Times
1419
allocated PDCH for EGPRS
Definition
Number of allocated PDTCH for EGPRS UL TBF establishment.
Description
This counter counts the number of successfully assigned PDTCH

when UL EGPRS TBF successfully established.
Usage
This counter is used to find out the number of successfully assigned

PDTCH when UL EGPRS TBF successfully established.
Measurement
Point
When PS control plane receives EGPRS channel requests on CCCH

from MS or EGPRS Packet channel request on PCCCH and DB resource requests succeed, the counter increments. The measurement point is A, as shown in Figure 1426.
FIGURE 1426 - DB RESOURCE REQUEST SUCCESSES (EGPRS)
Unit
Related Features
Times
C901200027 Number
of EGPRS UL TBF
1420
Definition
Number of EGPRS UL TBF establishment failure due to channel

activate failed.
Description
This counter counts the number of PDTCH activate failure when

establishing UL EGPRS TBF.
Usage
Measurement
Point
This counter is used to find out the number of PDTCH activate failure when establishing UL EGPRS TBF (including initially establish
UL TBF and establish UL TBF when DL TBF exists).

reported by BTS, the counter increments. The measurement
Unit
Related Features
When 'wait for PDTCH channel activation and connection response' counter times out and BSC fails to receive PDTCH activate response message reported by BTS, this counter increments.
Times
C901200028 Number
of EGPRS UL TBF
Definition
Number of EGPRS UL TBF establishment failure due to BTS connection failed.
Description
This counter counts the number of failure to establish UL EGPRS

TBF due to BTS connection failure.
Usage
This counter is used to find out the number of UL EGPRS TBF establishment failure (including initially establish UL TBF and establish
UL TBF when DL TBF exists) due to BTS connection failure.
Measurement
Point
When PS control plane receives connection failure message reported by connection module due to BTS connection failure, the
Figure 1428.
1421

FAILURE
Unit
Related Features
When 'wait for PDTCH channel activate and connection response' counter times out and BSC fails to receive connection
success response message reported by connection module,
Times
C901200029 Number
of EGPRS UL TBF
1422
Definition
Number of EGPRS UL TBF establishment failure due to BIU connection failed.
Description

TBF due to BIU connection failure.
Usage
This counter is used to find out the number of UL EGPRS TBF establishment failure (including initially establish UL TBF and establish
UL TBF when DL TBF exists) due to BIU connection failure.
Measurement
Point
When PS control plane receives connection failure message reported by connection modules due to BIU connection failure, the
Figure 1429.
Unit
Related Features
Times
EGPRS UL TBF channel
success
Definition
Number of EGPRS UL TBF channel activate establishment success.
Description
This counter counts the number of channel activate and connection

successes when establishing UL EGPRS TBF.
Usage
connection successes when establishing UL EGPRS TBF.
Measurement
Point
When PS control plane receives channel activate response message reported by BTS and connection successes acknowledgement
FIGURE 1430 - UL EGPRS TBF ESTABLISHES CHANNEL ACTIVATION AND
ACCESS SUCCESS
1423
Unit
Related Features
Times
C901200031 Number
of EGPRS UL TBF
not receive PIA
Definition
Number of EGPRS UL TBF establishment failure due to not receive

PIA.
Description
This counter counts the number of failure to send immediate assignment message to MS when establishing UL EGPRS TBF.
Usage
This counter is used to find out the number of failure to send immediate assignment message to MS when establishing UL EGPRS
TBF.
Measurement
Point
When PS control plane receives immediate assignment failure

message reported by BTS, the counter increments. The measurement point is A, as shown in Figure 1431.
Unit
Related Features
1424
When 'wait for immediate assignment and sending indication'

counter times out and BSC fails to receive immediate assignment and sending indication message, the counter increments.
Times
C901200032 Number
of EGPRS UL TBF
PCCCH/CCCH due to
UPPB-DSP congestion
Definition
Number of EGPRS UL TBF establishment failure on PCCCH/CCCH

due to UPPB-DSP.
Description

TBF.
Usage
This counter is used to find out the number of failure to establish

UL EGPRS TBF.
Measurement
Point
When PS control plane assigns single block through two phase access from PS user plane, or gets access to PS user plane through
one phase access and starts assignment timer. If the timer times
out, resource request from PS user plane (two phase access) is
not received or indication (one phase access) is not established,
Figure 1432.
Unit
Related Features
Times
1425
C901200033 Number
of EGPRS UL TBF
congestion
Definition
Description
Number of EGPRS UL TBF establishment failure on PACCH due to

C901200034 Number
of EGPRS UL TBF
on PCCCH/CCCH
Definition
Number of EGPRS UL TBF establishment success on PCCCH/CCCH.
Description
This counter counts the number of successful UL EGPRS TBF establishment and receiving MS TLL1.
Usage
This counter is used to find out the number of successful UL EGPRS

TBF establishment and receiving MS TLL1.
Measurement
Point
When PS control plane receives MS TLL1 MAC establishment inmessage reported by PS user plane in the premise of
one phase access, the counter increments. The measurement
dication
1426
FIGURE 1433 - UL ONE-PHASE-ACCESS RESOURCE ASSIGNMENT

SUCCESSES
PS control plane receives resource request message from PS

user plane in the premise of two phase access, the counter
1434.
FIGURE 1434 - UL TWO-PHASE-ACCESS SINGLE BLOCK ASSIGNMENT
SUCCESSES
Unit
Related Features
Times
C901200035 Number
of EGPRS UL TBF
on PACCH
Definition
Description
Number of EGPRS UL TBF establishment success on PACCH.

1427
Abis congestion for DL TBF
establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to Abis

Description
In the situation when UL EGPRS TBF is already established, DL

records the number of UL EGPRS TBF reallocation failure due to
Abis resource congestion.
Usage
This counter is used to find out the number of UL GPRS TBF reallocation failure due to Abis congestion.
Measurement
Point
In the situation when UL EGPRS TBF is established, PS control

plane receives DL assignment request message from PS user
plane, and DB resource request fails due to Abis congestion,
inFigure 1435.
CONGESTION
Unit
Related Features
1428
Times
RR congestion for DL TBF
establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to RR

Description

records the number of UL resource reallocation failure due to RR
There are three causes which lead to radio resource congestion:
MS per channel (MS number per channel reaches its maximum),
TAI/TFI (no TAI or TFI available) and no PDCH available.
Usage
This counter is used to find out the number of UL EGPRS TBF reallocation failure due to RR congestion.
Measurement
Point

inFigure 1436.
Unit
Related Features
DUE TO
RR CONGESTION
Times
1429
to UPPB-DSP channel
establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to

UPPB-DSP channel congestion.
Description
In the situation when UL EGPRS TBF is already established, DL

records the number of EGPRS UL resource reallocation failure due
to UPPB-DSP channel resource congestion.
Usage
This counter is used to find out the number of UL EGPRS TBF reallocation failure due to UPPB-DSP channel congestion.
Measurement
Point

plane, and DB resource request fails due to UPPB-DSP channel
CHANNEL CONGESTION
Unit
Related Features
1430
DUE TO
UPPB-DSP
Times
channel allocation due to DL
TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation success of channel

allocation due to DL TBF establishment.
Description
The counter records the number of successful DL TBF establishment on PACCH when UL EGPRS TBF is already established.
Usage
This counter is used to find out the number of DL EGPRS TBF reallocation successes.
Measurement
Point

FIGURE 1438 SUCCESSFUL RESOURCE APPLICATION
Unit
Related Features
Times
1431
C901200042 Number
reallocation due to DL TBF
establishment
Definition
Number of allocated PDTCH for EGPRS UL TBF resource reallocation due to DL TBF establishment.
Description
The counter records the number of successful allocated PDTCH

when UL EGPRS TBF is successfully reallocated.
Usage

PDTCH when UL EGPRS TBF is successfully reallocated.
Measurement
Point

plane, and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 1439.
Unit
Related Features
1432
Times
Definition
Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment.
Description

Usage

failure during UL EGPRS TBF resource reallocation.
Measurement
Point

Unit
Times
1433
Definition
Number of EGPRS UL TBF resource reallocation failure due to BTS

Description
The counter records the number of BTS connection failure during

UL EGPRS TBF resource reallocation.
Usage

Measurement
Point

in Figure 1441.
FAILURE
Unit
1434
Times
BIU connection failure for DL
TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to BIU

Description

UL EGPRS TBF resource reallocation.
Usage
This counter is used to find out the number of BIU connection failure during UL EGPRS TBF resource reallocation.
Measurement
Point

connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown in Figure 1442.
Unit
Times
1435
connection for DL TBF
establishment
Definition

activate and connection for DL TBF establishment
Description
The counter records the number of channel activate and connection successes during UL EGPRS TBF resource reallocation.
Usage
connection successes during UL EGPRS TBF resource reallocation.
Measurement
Point

Unit
1436
Times
reallocation failure due to DL
TBF establishment
Definition
Description
Related Features
Number of EGPRS UL TBF resource reallocation failure due to DL

TBF establishment.
Definition
Description
Related Features
Number of EGPRS UL TBF resource reallocation success due to DL

TBF establishment.
transmission
Definition

Description

1437
failure due to Abis resource congestion after PS control plane receiving resource reallocation request during UL EGPRS TBF transmission process.
Usage

Abis resource congestion after PS control plane receiving resource
reallocation request during UL EGPRS TBF transmission process.
Measurement
Point

from PS user plane, and DB resource request fails due to Abis
Unit
Related Features
Times
transmission
Definition

Description

failure due to radio resource congestion after PS control plane receiving resource reallocation request during UL EGPRS TBF transmission process.
There are three causes leading to RR congestion: MS per channel
(reaches its maximum), TAI/TFI (not available), and no PDTCH.
1438
Usage

RR congestion after PS control plane receiving resource reallocation request during UL EGPRS TBF transmission process.
Measurement
Point

from PS user plane, and DB resource request fails due to RR
Unit
Related Features
Times
to UPPB-DSP channel
congestion for LLC
transmission
Definition

UPPB-DSP channel congestion for LLC transmission.
Description

message. The counter records the number of DB resource request failure due to UPPB-DSP channel congestion after PS control
plane receiving resource reallocation request during UL EGPRS TBF
transmission process.
Usage
This counter is used to find out DB resource request failure due

to UPPB-DSP channel congestion after PS control plane receiving
1439
resource reallocation request during UL EGPRS TBF transmission

process.
Measurement
Point

from PS user plane, and DB resource request fails due to
UPPB-DSP channel congestion, the counter increments. The
Unit
Related Features
Times
LLC transmission
1440
Definition

Description

successes after PS control plane receiving resource reallocation request during UL EGPRS TBF transmission process.
Usage
This counter is used to find out DB resource request success due

after PS control plane receiving resource reallocation request during UL EGPRS TBF transmission process.
Measurement
Point

Figure 1447.

ADJUSTMENT)
Unit
Related Features
Times
C901200055 Number
transmission
Definition
Number of allocated PDTCH for EGPRS UL TBF resource reallocation due to LLC transmission.
Description

message. The counter records the number of successfully allocated PDTCH after PS control plane receiving resource reallocation
requests during UL EGPRS TBF.
Usage

PDTCH when UL EGPRS TBF is successfully reallocated.
Measurement
Point

inFigure 1448.
1441

ADJUSTMENT)
Unit
Related Features
Tines
LLC transmission
Definition
Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for LLC transmission.
Description
This counter counts the number of PDTCH activate failure after

BSC receiving resource reallocation request during UL EGPRS TBF
Usage

Measurement
Point
1442

Unit
Times
LLC transmission
Definition

Description

connection failure after BSC receiving resource reallocation request during UL EGPRS TBF transmission.
Usage

failure during UL EGPRS TBF resource transmission.
Measurement
Point

in
1443

FAILURE
Unit
Times
LLC transmission
1444
Definition

Description

UL EGPRS TBF transmission.
Usage
This counter is used to find out the number of BIU connection failure during UL EGPRS TBF transmission.
Measurement
Point

connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown in Figure 1451.
Unit
Times
channel activate for LLC
transmission
Definition

activate for LLC transmission
Description
The counter records the number of channel activate and connection successes during UL EGPRS TBF transmission.
Usage
connection successes during UL EGPRS TBF tranmission.
Measurement
Point

point is A, as shown in .
1445
FIGURE 1452
Unit
Times
LLC transmission
Definition
Description
Related Features
Number of EGPRS UL TBF resource reallocation failure due to LLC

transmission.
LLC transmission
Definition
Description
Related Features
1446
Number of EGPRS UL TBF resource reallocation success due to LLC

transmission.
resource request
Definition
Description
Number of EGPRS UL TBF resource reallocation requests for resource request.

Abis congestion for resource
request
Definition

Description
The counter records the number of DB resource request failure due

to Abis congestion after PS control plane resource request from MS
during UL EGPRS TBF.
Usage

during UL EGPRS TBF process (including UL two-phase access and
Measurement
Point

plane, and DB resource request fails due to Abis congestion, the
Figure 1453.
1447

CONGESTION (RESOURCE REQUEST)
Unit
Related Features
Times
RR congestion for resource
request
Definition

Description

RR congestion during UL EGPRS TBF.
There are three cause leading to radio resource congestion: MS
per channel (MS number per channel reaches its maximum),
TAI/TFI (no TAI/TFI available), no PDCH (no PS service channel
available).
1448
Usage

due to RR congestion during UL EGPRS TBF process (including UL
two-phase access and UL TBF transmission).
Measurement
Point
PS control plane receives resource request message from MS, and

DB resource request fails due to RR congestion, the counter increments. The measurement point is A, as shown in Figure 1454.
FIGURE 1454 - DB RESOURCE REQUESTS FAILURE DUE TO RR CONGESTION
Unit
Related Features
Times
to UPPB-DSP channel
congestion for resource
request
Definition

UPPB-DSP channel congestion for resource request.
Description

UPPB-DSP channel congestion during UL EGPRS TBF.
Usage

due to UPPB-DSP channel congestion during UL EGPRS TBF process
(including UL two-phase access and UL TBF transmission).
Measurement
Point

Figure 1455.
1449

CHANNEL CONGESTION (RESOURCE REQUEST)
Unit
Related Features
Times
reallocation success due
to database allocation for
resource request
1450
Definition
Number of EGPRS UL TBF resource reallocation success due to

database allocation for resource request
Description
The counter records the number of successful DB resource request

after PS control plane receives resource request message from MS
during UL EGPRS TBF process.
Usage

successes after PS control plane receives resource request from
MS during UL EGPRS TBF process (including UL two-phase access
and UL TBF transmission).
Measurement
Point

FIGURE 1456 - DB RESOURCE REQUESTS SUCCESSES (RESOURCE REQUEST)
Unit
Related Features
Times
C901200068 Number
reallocation due to resource
request
Definition
Number of allocated PDTCH for EGPRS UL TBF resource reallocation due to resource request.
Description
The counter records the number of successful allocated PDTCH after PS control plane receives resource request message from MS
during UL EGPRS TBF process.
Usage

PDTCH after PS control plane receives resource request from MS
during UL EGPRS TBF process (including UL two-phase access and
Measurement
Point

1451
FIGURE 1457 - DB RESOURCE REQUESTS SUCCESSES (RESOURCE REQUEST)
Unit
Related Features
Times
resource request
Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for resource request.
UL EGPRS TBF resource reallocation after PS control plane receives
resource request message.
UL EGPRS TBF resource reallocation after PS control plane receives
resource request message in UL EGPRS TBF process (including UL
two-phase access and one-phase TBF transmission).
1452

A, as shown in .
Unit
Times
resource request
Definition

Description

connection failure during UL EGPRS TBF resource reallocation after
Usage

transmission).
Measurement
Point

in Figure 1459.
1453

FAILURE
Unit
Times
resource request
1454
Definition

Description

Usage

PS control plane receives resource request message in UL EGPRS
transmission).
Measurement
Point

Unit
Times
connection for resource
request
Definition

activate and connection for resource request
Description
The counter records the number of channel activate and connection successes during UL EGPRS TBF resource reallocation after PS
control plane receives resource request message.
Usage
The counter records the number of channel activate and connection failure during UL EGPRS TBF resource reallocation after PS
control plane receives resource request message in UL EGPRS TBF
process (including UL two-phase access and one-phase TBF transmission).
Measurement
Point

1455

Unit
Times
resource request
Description
Related Features

resource request
Description
Related Features
1456

to flush LL
Description
This counter counts the number of UL EGPRS TBF release after PS

control plane receiving request due to flush LL.
Usage
This counter is used to find out the number of UL EGPRS TBF release after PS control plane receiving request due to flush LL.
Measurement
Point
When PS control plane of BSC receives FLUSH message from SGSN

and release is executed when UL EGPRS TBF is established, the
Figure 1462.
FIGURE 1462 RELEASE REQUEST
Unit
DUE TO
SUSPEND REQUEST
Times
Description
This counter counts the number of UL EGPRS TBF release after PS

control plane receiving request due to GPRS suspend requests.
Usage
This counter is used to find out the number of UL EGPRS TBF release due to GPRS suspend requests.
Measurement
Point
When PS control plane of BSC receives SUSPEND message from

SGSN and release is executed when UL EGPRS TBF is established,
Figure 1463.
1457
Unit
DUE TO
SUSPEND REQUEST
Times
EGPRS UL TBF forcing
release by CS
Description
This counter counts the number of UL EGPRS TBF forcing release

by CS.
Usage
This counter is used to find out the number of UL EGPRS TBF forcing release by CS.
Measurement
Point
When PS control plane of BSC receives PDCH RELEASE message

from CS control plane when UL EGPRS TBF is established, the
Figure 1464.
Unit
1458
DUE TO
Times
PDCH REL
EGPRS UL TBF normal
requests
Description
This counter counts the number of UL EGPRS TBF normal release

Usage
This counter is used to find out the number of UL EGPRS TBF normal release due to user plane requests.
Measurement
Point
When PS control plane of BSC receives NORMAL RELEASE REQUEST message from PS user plane when UL EGPRS TBF exists,
Figure 1465.
MAC
Unit
DUE TO
NORMAL RELEASE REQUEST
BY
Times
EGPRS UL TBF abnormal
requests
Description
This counter counts the number of UL EGPRS TBF abnormal release

Usage
This counter is used to find out the number of UL EGPRS TBF abnormal release due to user plane requests.
Measurement
Point
When PS control plane receives ABNORMAL RELEASE REQUEST

message from PS user plane when UL EGPRS TBF exists, the
Figure 1466.
1459

BY MAC
Unit
DUE TO
Times
Definition
Number of EGPRS UL TBF release due to NSVC unavailability.
Description
This counter counts the number of UL EGPRS TBF release due to

Usage
This counter is used to find out the number of UL EGPRS TBF release after receiving forcing release request due to NSVC unavailability.
Measurement
Point
When PS control plane receives NSVC unavailability command to

release PS control plane module from DB when UL EGPRS TBF
FIGURE 1467 - RELEASE REQUEST DUE TO NSVC UNAVAILABILITY
Unit
1460
Times
Definition
Number of EGPRS UL TBF release due to BVC unavailability.
Description
This counter counts the number of UL EGPRS TBF release due to

BVC unavailability.
Usage
This counter is used to find out the number of UL EGPRS TBF release after receiving forcing release request due to BVC unavailability.
Measurement
Point
When PS control plane receives BVC unavailability command to

release PS control plane module from DB when UL EGPRS TBF
Unit
Times
to other reasons
Definition
Number of EGPRS UL TBF release due to other reasons.
Description
This counter counts the number of UL EGPRS TBF forcing release

due to other reasons.
Usage
This counter is used to find out the number of UL EGPRS TBF release after receiving forcing release request due to other reasons.
Measurement
Point
When PS control plane receives release message due to other reasons when UL EGPRS TBF exists, the counter increments. The
1461
Unit
Times
EGPRS TBF grab resources
Definition
Number of UL EGPRS TBF grab resources.
Description
This counter counts the number of UL EGPRS TBF grab resources.
Usage
This counter is used to find out the frequency for UL EGPRS TBF
Measurement
Point
This counter increments while UL EGPRS TBF is established during

TBF resource is grabbed. Measurement point is A as shown
inFigure 1470.
FIGURE 1470 - UL EGPRS RESOURCE REQUEST SUCCESS
Unit
Related Features
1462
Times
grab instance by UL EGPRS
TBF
Definition
Number of grab instance by UL EGPRS TBF.
Description
This counter counts the number of grab instance by UL EGPRS TBF.
Usage
Measurement
Point

TBF resource is grabbed. Measurement point is A as shown in
Figure 1471.
Unit
Related Features
Times
EGPRS TBF queuing
Definition
Description
Number of UL EGPRS TBF queuing.

This counter counts the number of UL EGPRS TBF queuing.
Usage
queuing.
Measurement
Point

A as shown in Figure 1472.
1463
Unit
Related Features
Times
UL EGPRS TBF queuing
success
Definition
Number of UL EGPRS TBF queuing success.
Description
This counter counts the number of UL EGPRS TBF queuing success.
Usage
queuing success.
Measurement
Point
This counter increments while UL EGPRS TBF is established during resource adjustment, the instance to be queued successfully
assigns resource for user, and database is successfully registered.
Measurement point is A as shown inFigure 1473.
1464
Unit
Related Features
Times
EGPRS TBF release TBF
during queuing
Definition
Number of UL EGPRS TBF release TBF during queuing.
Description
This counter counts the number of UL EGPRS TBF release during

queuing.
Usage
Measurement
Point
This counter increments while UL EGPRS TBF is released and instance still in queuing state. The measurement point is A as shown
in Figure 1474.
FIGURE 1474 - RELEASE UL EGPRS TBF
Unit
Related Features
Times
1465
1466
Chapter
27
BSSGP Flow Statistic

Table of Contents
Overview...................................................................... 1468
C901210001 Number of paging PS message ..................... 1468
C901210002 Number of paging CS message ..................... 1468
C901210003 Number of Flush-LL Message received ........... 1469
C901210004 Number of Flush-LL-ACK Message sent .......... 1470
C901210005 Number of BVC-BLOCK message sent ............ 1470
C901210006 Number of BVC-BLOCK-ACK message received
.................................................................................. 1471
C901210007 Number of BVC-UNBLOCK message sent......... 1472
C901210008 Number of BVC-UNBLOCK-ACK message received ......................................................................... 1472
C901210009 Number of BVC-RESET message sent ............ 1473
C901210010 Number of BVC-RESET-ACK message received
.................................................................................. 1474
C901210011
Number
of
BVC-RESET
message
received.......................................................................... 1474
C901210012
Number
of
BVC-RESET-ACK
message
sent............................................................................. 1475
C901210013 Number of PERFORM-LOCATION-REQUEST message received................................................................ 1476
message sent ............................................................... 1477
C901210015 Number of PERFORM-LOCATION-ABORT message received................................................................ 1478
sent............................................................................. 1479
C901210017 Number of POSITION-RESPONSE message received.......................................................................... 1480
C901210018 Number of Flush-LL received if UL/DL TBF exist ............................................................................... 1481
C901210019 Number of Flush-LL received if DL TBF exist ............................................................................... 1482
C901210020 Number of Flush-LL received if UL TBF exist ............................................................................... 1483
C901210021 Number of reroute intra NSE ........................ 1483
C901210022 Number of reroute inter NSE intra BSS
cell .............................................................................. 1484
C901210023 Number of reroute inter NSE inter BSS
cell .............................................................................. 1485
C901210024 LLC transfer bytes....................................... 1485
C901210025 LLC transfer frames..................................... 1486
C901210026 LLC transfer failed bytes .............................. 1486
C901210027 LLC transfer failed frames ............................ 1486
C901210028 LLC transfer failed num................................ 1487
C901210029 LLC transfer succeeded num......................... 1487
C901210030 LLC transfer via cell reselection..................... 1488
1467
C901210031 LLC transfer not via cell reselection ............... 1489

C901210032 LLC transfer fail Num via cell reselection......... 1489
C901210033 LLC transfer fail Num not via cell reselection ............................................................................. 1490
Overview
TRX measurement is to measure the success or failure condition
of channel activation, assignment, and handover in the unit of carrier. It also can measure carrier interference band, maximum and
minimum UL & DL level condition, to learn the status of different
carriers, providing evidence for adjustment and maintenance.
paging PS message
Description
SGSN sending packet paging message indicates that BSC originates packet paging for MS in designated cell. This counter counts
the number of receiving this message.
Measurement
Point
When BSC receives a PAGING PS message, this counter increments. The measurement point is A, as shown in Figure 1475.
FIGURE 1475 PAGING PS PROCESS
Unit
Related Features
Times
paging CS message
Definition
Description
1468
Number of paging CS message

SGSN sending circuit paging message indicates that BSC originates
packet paging for MS in designated cell. This counter counts the
number of received messages.
Chapter 27 BSSGP Flow Statistic
Measurement
Point
When BSC receives a PAGING CS message, this counter increments.

FIGURE 1476 - PAGING CS PROCESS
Unit
Related Features
Times
Flush-LL Message received
Definition
Number of Flush-LL Message received
Description
SGSN sends FLUSH-LL message to notify of BSS MS to do inter-cell

handover, and this counter counts the number of receiving this
message by BSC.
Usage
By viewing the number of receiving this message by BSC, to check

the MS handover condition.
Measurement
Point
When BSC receives a FLUSH-LL message, this counter increments.

FIGURE 1477 - FLUSH-LL MESSAGE
Unit
Times
1469
Flush-LL-ACK Message sent
Definition
Number of Flush-LL Message sent
Description
BSC sends FLUSH-LL-ACK message to notify SGSN: LLC PDU buffered

for this MS by pervious cell has been removed or transferred to new
cell under same routing area. This counter counts the number of
sending this message by BSC.
Measurement
Point
When BSC receives a FLUSH-LL-ACK message, this counter increments. The measurement point is A2, as shown in Figure 1478.
Unit
Times
BVC-BLOCK message sent
Definition
1470
Number of BVC-BLOCK message sent
Description
BSC sending BVC block message indicates BVC designated by

SGSN blocking. This counter counts the number of blocking
designated BVC by BSC.
Measurement
Point
When BSC sends a BVC-BLOCK message, this counter increments.

The measurement point is A1, as shown inFigure 1479.
FIGURE 1479 - BVC BLOCKING PROCESS
Unit
Times
BVC-BLOCK-ACK message
received
Definition
Number of BVC-BLOCK-ACK message received
Description
SGSN sends BVC blocking confirmation message to notify of designated BVC blocked by BSC, and this counter counts the number
of receiving this message by BSC.
Measurement
Point
When BSC receives a BVC-BLOCK-ACK message, this counter increments. The measurement point is A2, as shown inFigure 1480 .
FIGURE 1480 - BVC BLOCKING PROCESS
Unit
Times
1471
BVC-UNBLOCK message
sent
Definition
Number of BVC-UNBLOCK message sent
Description
BSC sends BVC unblocking message indicates BVC designated by

SGSN unblocking, and this counter counts the number of unblocking designated BVC by BSC.
Measurement
Point
When BSC sends a BVC-UNBLOCK message, this counter increments.

The measurement point is A1, as shown inFigure 1481 .
FIGURE 1481 - BVC UNBLOCKING PROCESS
Unit
Times
C901210008 Number
of BVC-UNBLOCK-ACK
message received
Definition
1472
Number of BVC-UNBLOCK-ACK message received.
Description
SGSN sends BVC unblocking confirmation message to notify of

designated BVC unblocked by BSC, and this counter counts the
number of receiving this message by BSC.
Measurement
Point
When BSC receives a BVC-UNBLOCK-ACK message, this counter increments. The measurement point is A2, as shown inFigure 1482.
FIGURE 1482 - BVC UNBLOCKING PROCESS
Unit
Times
BVC-RESET message sent
Definition
Number of BVC-RESET message sent
Description
BSC sends BVC reset message indicates SGSN resets designated

BVC, and this counter counts the number of resetting designated
BVC by BSC actively.
Measurement
Point
When BSC sends a BVC-RESET message, this counter increments.

FIGURE 1483 - BVC RESET PROCESS
1473
Unit
Times
BVC-RESET-ACK message
received
Definition
Number of BVC-RESET-ACK message received.
Description
SGSN sends BVC reset confirmation message to notify of designated BVC reset by BSC, and this counter counts the number of
receiving this message by BSC.
Measurement
Point
When BSC receives a BVC-RESET-ACK essage, this counter increments. The measurement point is A2, as shown in Figure 1484.
Unit
Times
BVC-RESET message
received
Definition
1474
Number of BVC-RESET message received
Description
SGSN sends BVC reset message indicates BSC resets designated

BVC, and this counter will count the number of resetting BVC by
SGSN actively.
Description
When BSC receives a BVC-RESET message, this counter increments.

Unit
Times
sent
Definition
Number of BVC-RESET-ACK message sent.
Description
BSC sends BVC reset confirmation message to notify of designated

BVC reset by SGSN, and this counter counts the number of sending
this message by BSC.
Measurement
Point
When BSC sends a BVC-RESET-ACK message, this counter increments.

1475
Unit
Times
PERFORM-LOCATION-RE
QUEST message received
Definition
1476
Number of PERFORM-LOCATION-REQUEST message received.
Description
SGSN sends location request message to request BSC to do a locating process for MS. This counter counts the number of receiving
Usage
By viewing the number of receiving locating request message by

BSC, you can view the frequency of locating service.
Measurement
Point
When BSC receives a PERFORM-LOCATION-REQUEST message, this

counter increments. The measurement point is A1, as shown
inFigure 1487 .
FIGURE 1487 - PERFORM LOCATION PROCESS
Unit
Times
PERFORM-LOCATION-RE
SPONSE message sent
Definition
Number of PERFORM-LOCATION-RESPONSE message sent
Description
After BSC finishes locating process, send locating response message to notify SGSN of locating result for MS. This counter counts
the number of sending this message by BSC.
Usage
By viewing the number of sending this message by BSC, you can

view the frequency of locating service.
Measurement
Point
When BSC sends a PERFORM-LOCATION- RESPONSE message, this counter

1488.
1477
Unit
Times
PERFORM-LOCATION-AB
ORT message received
Definition
1478
Number of PERFORM-LOCATION-ABORT message received.
Description
SGSN sends abort locating message to request BSC abort current

locating process. This counter counts the number of receiving this
message by BSC.
Measurement
Point
When BSC receives a PERFORM-LOCATION-ABORT message, this counter

1489.
Unit
Times
POSITION-COMMAND
message sent
Definition
Number of POSITION-COMMAND message sent.
Description
BSC sends locating command message to request SGSN perform

locating command process. This counter counts the number of
Measurement
Point
BSC sends a POSITION-COMMAND message, this counter increments.

1479
Unit
Times
POSITION-RESPONSE
message received
Definition
1480
Number of POSITION-RESPONSE message received.
Description
SGSN sends POSITION-RESPONSE message to notify BSC of response

result for locating command result. This counter counts the number of receiving this message by BSC.
Measurement
Point
When BSC receives a POSITION-RESPONSE message, this counter increments. The measurement point is A3, as shown inFigure 1491.
Unit
Times
Flush-LL received if UL/DL
TBF exist
Definition
Number of Flush-LL received if UL/DL TBF exist
Description
SGSN sends FLUSH-LL message to notify of BSC MS passed inter-cell

handover. This counter counts the number of receiving FLUSH-LL
message during data service made by MS.
Measurement
Point
Each time BSC receives a FLUSH-LL message and MS is conducting

DL data service, this counter increments. The measurement point
1481
FIGURE 1492 - RECEIVE FLUSH-LL FOR UL & DL TBF
Unit
Times
Flush-LL received if DL TBF
exist
Definition
Number of Flush-LL received if DL TBF exist
Description

message during DL data service made by MS.
Measurement
Point
When BSC receives a FLUSH-LL message and MS is conducting UL

data service, this counter increments. The measurement point is
FIGURE 1493 - RECEIVE FLUSH-LL FOR DL TBF
1482
Unit
Times
Flush-LL received if UL TBF
exist
Definition
Number of Flush-LL received if UL TBF exist
Description

message during UL data service made by MS.
Measurement
Point
When BSC receives a FLUSH-LL message and MS is conducting UL

data service, this counter increments. The measurement point is
FIGURE 1494 - RECEIVE FLUSH-LL FOR UL TBF
Unit
Times
reroute intra NSE
Definition
Number of reroute intra NSE.
Description
SGSN sends FLUSH-LL message to notify of BSS MS passed inter-cell

handover. This counter counts the number of receiving this message by BSC, and the number of same NSE for new and previous
cells.
Measurement
Point
When BSC receives a FLUSH-LL message and new and previous cells
are same NSE, this counter increments. The measurement point
is A1, as shown inFigure 1495.
1483
Unit
Times
reroute inter NSE intra BSS
cell
Definition
Number of reroute inter NSE intra BSS cell.
Description
SGSN sends FLUSH-LL message to notify of BSS MS passed intercell handover. This counter counts the number of receiving this
message by BSC, and the number of same BSS and different NSEs
for new and previous cells.
Measurement
Point
When BSC receives a FLUSH-LL message and new and previous cells
are same BSS or different NSEs, this counter increments. The
Unit
1484
Times
reroute inter NSE inter BSS
cell
Definition
Number of reroute inter NSE inter BSS cell.
Description
SGSN sends FLUSH-LL message to notify of BSS MS passed intercell handover. This counter counts the number of receiving this
message by BSC, and the number of different BSSs and NSEs for
new and previous cells.
Measurement
Point
When BSC receives a FLUSH-LL message, and new and previous

cells are different BSSs or NSEs, this counter increments. The
Unit
Times
C901210024 LLC transfer

bytes
Description
If LLC frame transferring is supported, then this counter counts

the number of bytes of LLC frames successfully transferred within
BSC when cell reselection or LLC frame transferring due to uplink
and downlink TBFs being established simultaneously occurs.
Usage
This counter is used to find out the number of bytes of LLC frames
successfully transferred after LLC frame transferring is initiated.
Measurement
Point
Unit
When PS control plane receives the indication of LLC frame transferring success or failure from PS user plane, the number of bytes
of LLC frames successfully transferred is accumulated.
Byte
1485

frames
Description
If LLC frame transferring is supported, then this counter counts the

number of LLC frames successfully transferred within BSC when
cell reselection or LLC frame transferring due to uplink and downlink TBFs being established simultaneously occurs.
Usage
This counter is used to find out the number of LLC frames successfully transferred after LLC frame transferring is initiated.
Measurement
Point
Unit
When PS control plane receives the indication of LLC frame transferring success or failure from PS user plane, the number of LLC
frames successfully transferred is accumulated.
Times

failed bytes
Description

the number of bytes of LLC frames failed to be transferred within
BSC when cell reselection or LLC frame transferring due to uplink
and downlink TBFs being established simultaneously occurs.
Usage
This counter is used to find out the number of bytes of LLC frames
failed to be transferred after LLC frame transferring is initiated.
Measurement
Point
Unit
When PS control plane receives the indication of LLC frame transferring failure from PS user plane, the number of bytes of LLC
frames failed to be transferred is accumulated.
Byte

failed frames
Description
If LLC frame transferring is supported, then this counter counts the

number of LLC frames failed to be transferred within BSC when cell
reselection or LLC frame transferring due to uplink and downlink
TBFs being established simultaneously occurs.
Usage
This counter is used to find out the number of LLC frames failed to
be transferred after LLC frame transferring is initiated.
1486
Measurement
Point
Unit
When PS control plane receives the indication of LLC frame transferring failure from PS user plane, the number of LLC frames failed
to be transferred is accumulated.
Times

failed num
1. V6.20.200a ~ V6.20.200e
2. V6.20.200f
i. Description
If LLC frame transferring is supported, then this counter
counts the number of LLC frames failed to be transferred
within BSC when cell reselection or LLC frame transferring
due to uplink and downlink TBFs being established simultaneously occurs.
ii. Usage
This counter is used to find out the number of LLC frames
failed to be transferred after LLC frame transferring is initiated.
iii. Measurement Point
When PS control plane receives the indication of LLC frame
transferring completion from PS user plane, if the transferring fails, then the counter increments.
iv. Unit
Times

succeeded num
1. V6.20.200a ~ V6.20.200e
2. V6.20.200f
i. Description
counts the number of LLC frames successfully transferred
within BSC when cell reselection or LLC frame transferring
due to uplink and downlink TBFs being established simultaneously occurs.
1487
ii. Usage
successfully transferred after LLC frame transferring is initiated.
transferring completion from PS user plane, if the transferring succeeds, then the counter increments.
iv. Unit
Times

via cell reselection
Description
1. V6.20.200a ~ V6.20.200e
the number of LLC frames successfully transferred within BSC
when cell reselection occurs.
2. V6.20.200f
the number of attempts of self-recovered TBF link reestablishment in downlink within BSC.
Usage
1. V6.20.200a ~ V6.20.200e
This counter is used to find out the number of LLC frames successfully transferred after LLC frame transferring is initiated
due to cell reselection.
2. V6.20.200f
If LLC frame transferring is supported, then this counter is used
to find out the number of attempts of self-recovered TBF link
reestablishment in downlink within BSC.
Measurement
Point
1. V6.20.200a ~ V6.20.200e
transferring success from PS user plane, if the LLC frame transferring is due to cell reselection, then the counter increments.
2. V6.20.200f
When PS control plane processes the downlink TBF link establishment request sent from PS user plane, if the link establishment request is due to self-recovery in downlink, then the
counter increments.
Unit
1488
Times

not via cell reselection
Description
1. V6.20.200a ~ V6.20.200e
the number of LLC frames successfully transferred within BSC
when no cell reselection occurs (such as when uplink and downlink TBFs are established simultaneously).
2. V6.20.200f
the number of successful self-recovered TBF link reestablishments in downlink within BSC.
Usage
1. V6.20.200a ~ V6.20.200e
This counter is used to find out the number of LLC frames successfully transferred after LLC frame transferring is initiated
not due to cell reselection.
2. V6.20.200f
If LLC frame transferring is supported, then this counter is used
to find out the number of successful self-recovered TBF link
reestablishments in downlink within BSC.
Measurement
Point
1. V6.20.200a ~ V6.20.200e
transferring success from PS user plane, if the LLC frame transferring is not due to cell reselection, then the counter increments.
2. V6.20.200f
When BSC receives the PIA_SEND_IND message from BTS, if
the downlink TBF establishment is due to downlink self-recovered reestablishment, then the counter increments.
Unit
Times

fail Num via cell reselection
1. V6.20.200a ~ V6.20.200e
i. Description
within BSC when cell reselection occurs.
ii. Usage
1489

failed to be transferred after LLC frame transferring is initiated due to cell reselection.
transferring failure from PS user plane, if the LLC frame
transferring is due to cell reselection, then the counter increments.
iv. Unit
Times
2. V6.20.200f

fail Num not via cell
reselection
1. V6.20.200a ~ V6.20.200e
i. Description
within BSC when no cell reselection occurs (such as when
uplink and downlink TBFs are established simultaneously).
ii. Usage
failed to be transferred after LLC frame transferring is initiated not due to cell reselection.
transferring failure from PS user plane, if the LLC frame
transferring is not due to cell reselection, then the counter
increments.
iv. Unit
Times
2. V6.20.200f
1490
Chapter
28
GB Message Statistic
Table of Contents
Overview...................................................................... 1492
BSSGP level.................................................................. 1493
BSSGP level.................................................................. 1493
C901220003 Number of receiving RA-CAPABILITY message ............................................................................ 1494
BSC ............................................................................. 1495
BSC ............................................................................. 1495
sent............................................................................. 1496
C901220007 Number of RA-CAPABILITY-UPDATE-ACK message received................................................................ 1497
C901220008 Number of wireless status PDU messages sent
by BSC......................................................................... 1497
BSC due to losing wireless association with MS .................. 1498
BSC due to bad link quality ............................................. 1499
BSC due to cell reselection command ............................... 1499
C901220012 Number of FLOW-CONTROL-BVC messages sent
by BSC......................................................................... 1500
C901220013 Number of FLOW-CONTROL-BVC-ACK messages
received by BSC ............................................................ 1500
C901220014 Number of FLOW-CONTROL-MS messages sent
by BSC......................................................................... 1501
C901220015 Number of FLOW-CONTROL-MS-ACK messages
received by BSC ............................................................ 1502
C901220016 Number of FLOW-CONTROL-PFC messages sent
by BSC......................................................................... 1503
C901220017 Number of FLOW-CONTROL-PFC-ACK messages
received by BSC ............................................................ 1504
C901220018 Number of status messages sent by BSC......... 1505
BSC ............................................................................. 1506
C901220020 Number of status messages sent with BVCI Unknown ......................................................................... 1507
C901220021 Number of Status messages sent with cell service congestion ............................................................. 1507
C901220022 Number of status messages sent with protocol
error............................................................................ 1508
C901220023 Number of status messages sent with Processor
overload....................................................................... 1508
1491
C901220024 Number of status messages received with BVCI

Unknown...................................................................... 1508
C901220025 Number of status messages received with cell
service congestion ......................................................... 1509
C901220026 Number of status messages received with protocol error .................................................................... 1509
C901220027 Number of status messages received with processor overload ............................................................. 1509
C901220028 Number of DOWNLOAD-BSS-PFC messages sent
by BSC......................................................................... 1510
C901220029 Number of BVCCREATE-BSS-PFC messages received by BSC............................................................... 1511
sent by BSC.................................................................. 1511
C901220031 Number of CREATE-BSS-PFC-NACK messages
sent by BSC.................................................................. 1512
C901220032 Number of MODIFY-BSS-PFC messages sent by
BSC ............................................................................. 1513
C901220033 Number of MODIFY-BSS-PFC-ACK messages received by BSC............................................................... 1514
C901220034 Number of DELETE-BSS-PFC messages received
by BSC......................................................................... 1515
sent by BSC.................................................................. 1516
C901220036 Number of DELETE-BSS-PFC-REQ messages received by BSC............................................................... 1517
C901220037 Number of PS-HANDOVER-REQUIRED messages
sent by BSC.................................................................. 1517
messages received by BSC ............................................. 1518
C901220040 Number of PS-HANDOVER-REQUEST messages
received by BSC ............................................................ 1520
C901220041 Number of PS-HANDOVER-REQUEST-ACK messages sent by BSC ......................................................... 1521
messages sent by BSC ................................................... 1522
C901220043 Number of PS-HANDOVER-COMPLETE messages
sent by BSC.................................................................. 1523
C901220044 Number of PS-HANDOVER-CANCEL messages
sent by BSC.................................................................. 1524
with Service UTRAN CCO received by BSC......................... 1525
Service UTRAN CCO received by BSC ............................... 1526
Overview
Gb interface message statistics mainly measures transmission number of different PTP messages at Gb BSSGP level in
GPRS service (such as RA-CAPABILITY, RADIO-STATUS, DOWNLOAD-BSS-PFC).
1492
Chapter 28 GB Message Statistic
C901220001 Sum of UL
UNITDATA messages
handled at BSSGP level
Description
This counter counts the number of sending UL-UNITDATA PDU to

SGSN by BSC.
Measurement
Point
This counter increments each time BSC sends a UL-UNITDATA

message. The measurement point is A, as shown in Figure 1498.
HANDLED AT BSSGP LEVEL
Unit
OF SUM OF
UL UNITDATA
MESSAGE
Times
C901220002 Sum of DL
UNITDATA messages
Description
SGSN sends DL-UNITDATA PDU to BSC, and this counter counts

the number of receiving this message by BSC.
Measurement
Point
This counter increments each time BSC receives a DL-UNITDATA

1493

Unit
POINT OF SUM OF
DL UNITDATA
MESSAGE
Times
receiving RA-CAPABILITY
message
Description
SGSN sends RA-CAPABILITY message to BSC, to indicate wireless

capability of MS. This counter counts the number of receiving this
message.
Measurement
Point
When BSC receives a RA-CAPABILITY message, this counter increments. The measurement point is A, as shown in Figure 1500.
MESSAGE RECEVIED
Unit
1494
POINT
OF
NUMBER
Times
OF
RA-CAPABILITY
PTP packet paging received
by BSC
Description
SGSN sends PTP packet paging message, to indicate BSC originate

PTP packet paging for MS. This counter counts the number of receiving this message by BSC.
Measurement
Point
FIGURE 1501 PTP PACKET PAGING PROCESS
Unit
Times
PTP circuit paging received
by BSC
Description
SGSN sends the PTP circuit paging message to indicate BSC to

initiate PTP circuit paging for MS. This counter counts the number
of BSC's receiving this message.
Measurement
Point
When BSC receives a PAGING CS message, this counter increments. The measurement point is A, as shown in Figure 1502.
1495
FIGURE 1502 PTP CIRCUIT PAGING PROCESS
Unit
Times
RA-CAPABILITY-UPDATE
message sent
Description
BSC sends the RA-CAPABILITY-UPDATE message to SGSN to request for the current wireless capability of MS. This counter counts
the number of BSC's sending this message.
Measurement
Point
When BSC sends a RA-CAPABILITY-UPDATE message to SGSN,

in Figure 1503.
FIGURE 1503 RA-CAPABILITY-UPDATE PROCESS
Unit
1496
Times
RA-CAPABILITY-UPDATEACK message received
Description
SGSN sends RA-CAPABILITY-UPDATE-ACK message to BSC, to indicate current wireless capability of MS. This counter counts the
Measurement
Point
When BSC receives a RA-CAPABILITY-UPDATE-ACK message

from SGSN, this counter increments. The measurement point is
Unit
Times
C901220008 Number
of wireless status PDU
messages sent by BSC
Description
BSC sends the wireless status PDU message to indicate SGSN that
abnormality occurs at radio interface. This counter counts the
number of BSC's sending this message.
Usage
The radio interface status can be checked by counting this message.
Measurement
Point
When BSC sends a RADIO-STATUS message to SGSN, this

Figure 1505.
1497
FIGURE 1505 RADIO-STATUS PROCESS
Unit
Times
wireless status messages
sent by BSC due to losing
wireless association with MS
Description
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio interface. This counter counts the number of BSC's sending this message due to Losing wireless association with MS.
Usage
Measurement
Point
When BSC sends a RADIO-STATUS message to SGSN due to Losing wireless association with MS, this counter increments.
Unit
1498
Times
sent by BSC due to bad link
quality
Description
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio interface. This counter counts the number of BSC's sending this message due to bad link quality.
Usage
Measurement
Point
When BSC sends a RADIO-STATUS message to SGSN due to bad

link quality, this counter increments.
Unit
Times
sent by BSC due to cell
reselection command
Description
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio interface. This counter counts the number of BSC's sending this message due to cell reselection command.
Usage
Measurement
Point
When BSC sends a RADIO-STATUS message to SGSN due to cell

reselection command, this counter increments.
Unit
Times
1499
FLOW-CONTROL-BVC
Description
BSC sends the FLOW-CONTROL-BVC message to notify SGSN of

the current BVC flow control policy. This counter counts the number of BSC's sending this message.
Measurement
Point
When BSC sends a FLOW-CONTROL-BVC message, this counter

1506.
FIGURE 1506 FLOW-CONTROL-BVC PROCESS
Unit
Times
FLOW-CONTROL-BVCACK messages received by
BSC
Description
1500
SGSN sends the FLOW-CONTROL-BVC-ACK message to notify BSC

that the current BVC flow control policy is accepted. This counter
counts the number of BSC's receiving this message.
Measurement
Point
When BSC receives a FLOW-CONTROL-BVC-ACK message, this

Figure 1507.
Unit
Times
FLOW-CONTROL-MS
Description
BSC sends the FLOW-CONTROL-MS message to notify SGSN of the

current MS flow control policy. This counter counts the number of
BSC's sending this message.
Measurement
Point
When BSC sends the FLOW-CONTROL-MS message, this counter

1508.
1501
FIGURE 1508 FLOW-CONTROL-MS PROCESS
Unit
Times
FLOW-CONTROL-MS-ACK
messages received by BSC
1502
Description
SGSN sends the FLOW-CONTROL-MS-ACK message to notify BSC

that the current MS flow control policy is accepted. This counter
Measurement
Point
When BSC receives a FLOW-CONTROL-MS-ACK message, this

Figure 1509.
Unit
Times
FLOW-CONTROL-PFC
Description
BSC sends the FLOW-CONTROL-PFC message to notify SGSN of

the flow control policy for one or multiple PFCs of designated MS.
This counter counts the number of BSC's sending this message.
Measurement
Point
When BSC sends the FLOW-CONTROL-PFC message, this counter

1510.
1503
FIGURE 1510 FLOW-CONTROL-PFC PROCESS
Unit
Times
FLOW-CONTROL-PFCACK messages received by
BSC
1504
Description
SGSN sends the FLOW-CONTROL-PFC-ACK message to notify BSC

that the PFC flow control policy for designated MS is accepted. This
counter counts the number of BSC's receiving this message.
Measurement
Point
When BSC receives a FLOW-CONTROL-PFC-ACK message, this

Figure 1511.
Unit
Times
status messages sent by
BSC
Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter counts the number of BSC's sending this
message.
Measurement
Point
When BSC sends the STATUS message, this counter increments.

1505
FIGURE 1512 STATUS PROCESS
Unit
Times
status messages received
by BSC
1506
Description
SGSN sends the status message to BSC to indicate that abnormality occurs. This counter counts the number of BSC's receiving this
message.
Measurement
Point
When BSC receives the STATUS message, this counter increments.

Unit
Times
status messages sent with
BVCI Unknown
Description
message due to BVCI Unknown.
Measurement
Point
When BSC sends a "STATUS" message due to BVCI Unknown,

Unit
Times
Status messages sent with
cell service congestion
Description
message due to cell service congestion.
Measurement
Point
When BSC sends a STATUS message due to cell service congestion, this counter increments.
1507
Unit
Times
protocol error
Description
message due to protocol error.
Measurement
Point
When BSC sends a STATUS message due to protocol error, this

counter increments.
Unit
Times
Processor overload
Description
BSC sends status message to SGSN, to indicate exception occurred. This counter counts the number of sending this message
by BSC due to processor overload.
Measurement
Point
When BSC sends a STATUS message due to processor overload,

Unit
Times
with BVCI Unknown
Description
SGSN sends status message to BSC, to indicate exception occurred. This counter counts the number of receiving this message
by BSC due to BVCI Unknown.
Measurement
Point
When BSC receives a STATUS message due to BVCI Unknown,

Unit
1508
Times
with cell service congestion
Description
by BSC due to cell service congestion.
Measurement
Point
When BSC receives a STATUS message due to cell service congestion, this counter increments.
Unit
Times
with protocol error
Description
by BSC due to protocol error.
Measurement
Point
When BSC receives a STATUS message due to protocol error, this

counter increments.
Unit
Times
with processor overload
Description
Measurement
Point
When BSC receives a STATUS message due to processor overload, this counter increments.
Unit
Times
1509
DOWNLOAD-BSS-PFC
Description
BSC sends the DOWNLOAD-BSS-PFC message to request SGSN

to initiate the CREATE-BSS-PFC process. This counter counts the
Measurement
Point
When BSC sends the DOWNLOAD-BSS-PFC message, this

Figure 1514.
FIGURE 1514 CREATE-BSS-PFC PROCESS
Unit
1510
Times
BVCCREATE-BSS-PFC
Description
SGSN sends the CREATE-BSS-PFC message to request BSC to create or modify a packet flow control context. This counter counts
the number of BSC's receiving this message.
Measurement
Point
When BSC receives a CREATE-BSS-PFC message, this counter

1515.
Unit
Times
CREATE-BSS-PFC-ACK
Description
BSC sends the CREATE-BSS-PFC-ACK message to acknowledge the

request of SGSN creating or modifying a packet flow control con-
1511
text. This counter counts the number of BSC's sending this message.
Measurement
Point
When BSC sends a CREATE-BSS-PFC-ACK message, this counter

1516.
Unit
Times
CREATE-BSS-PFC-NACK
1512
Description
BSC sends the CREATE-BSS-PFC-NACK message to deny the request of SGSN creating or modifying a packet flow control context.
Measurement
Point
When BSC sends a CREATE-BSS-PFC-NACK message, this counter

1517.
Unit
Times
C901220032 Number
of MODIFY-BSS-PFC
Description
BSC sends the MODIFY-BSS-PFC message to SGSN to request for

modifying the packet flow control context. This counter counts the
Measurement
Point
When BSC sends the MODIFY-BSS-PFC message, this counter increments. The measurement point is A1, as shown in Figure 1518.
1513
FIGURE 1518 MODIFY-BSS-PFC PROCESS
Unit
Times
MODIFY-BSS-PFC-ACK
1514
Description
SGSN sends the MODIFY-BSS-PFC-ACK message to BSC to confirm the modification of packet flow control context. This counter
Measurement
Point
When BSC receives a MODIFY-BSS-PFC-ACK message, this

Figure 1519.
Unit
Times
C901220034 Number
of DELETE-BSS-PFC
Description
SGSN sends the DELETE-BSS-PFC message to request BSC to

delete a packet flow control context. This counter counts the
number of BSC's receiving this message.
Measurement
Point
When BSC receives a DELETE-BSS-PFC message, this counter increments. The measurement point is A1, as shown in Figure 1520.
1515
FIGURE 1520 DELETE-BSS-PFC PROCESS
Unit
Times
DELETE-BSS-PFC-ACK
1516
Description
BSC sends the DELETE-BSS-PFC-ACK message to SGSN to confirm

the deletion of specified packet flow control context. This counter
counts the number of BSC's sending this message.
Measurement
Point
When BSC sends a DELETE-BSS-PFC-ACK message, this counter

1521.
Unit
Times
DELETE-BSS-PFC-REQ
Description
PS-HANDOVER-REQUI
RED messages sent by BSC
Statistics object
Description
BSC
This counter counts the number of PS-HANDOVER-REQUIRED
messages sent to SGSN from BSC. The counter increments when
BSC sends a PS-HANDOVER-REQUIRED message. The measurement point is A, as shown in Figure 1522.
1517

REQUIRED MESSAGES SENT BY BSC
Unit
OF
PS-HANDOVER-
Times
PS-HANDOVER-REQUIRE
D-ACK messages received
by BSC
Statistics object
Description
1518
BSC
After a PS handover request is acknowledged, SGSN sends the
PS-HANDOVER-REQUIRED-ACK message to BSC. This counter
counts the number of PS-HANDOVER-REQUIRED-ACK messages
received by BSC from SGSN. The counter increments when
BSC receives the PS-HANDOVER-REQUIRED-ACK message. The

REQUIRED-ACK MESSAGES RECEIVED BY BSC
Unit
OF
PS-HANDOVER-
Times
PS-HANDOVER-REQUIRE
D-NACK messages received
by BSC
Statistics object
Description
BSC
If SGSN receives the non-acknowledgement message for PS
handover request from BSC, then SGSN sends the PS-HANDOVER-REQUIRED-NACK message back to BSC. This counter
counts the number of PS-HANDOVER-REQUIRED-NACK messages
received by BSC from SGSN. The counter increments when BSC
receives the PS-HANDOVER-REQUIRED-NACK message.
The
1519
FIGURE 1524 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUIRED-NACK MESSAGES RECEIVED BY BSC
Unit
Times
PS-HANDOVER-REQUEST
Statistics object
Description
1520
BSC
This counter counts the number of PS-HANDOVER-REQUEST messages received by BSC from SGSN. The counter increments when
BSC receives the PS-HANDOVER-REQUEST message. The measurement point is A2, as shown in Figure 1525.

REQUEST MESSAGES RECEIVED BY BSC
Unit
OF
PS-HANDOVER-
Times
PS-HANDOVER-REQUES
T-ACK messages sent by
BSC
Statistics object
Description
BSC
This counter counts the number of PS-HANDOVER-REQUEST-ACK
messages sent by BSC. The counter increments when BSC sends
the PS-HANDOVER-REQUEST-ACK message. The measurement
1521

REQUEST-ACK MESSAGES SENT BY BSC
Unit
OF
PS-HANDOVER-
Times
PS-HANDOVER-REQUES
T-NACK messages sent by
BSC
Statistics object
Description
1522
BSC
During the handover, if the channel request fails or the cell does
not support PS handover, then creating MS or PS instance will fail.
This counter counts the number of messages, which indicate failure of creating MS or PS instance, sent by BSC. The counter incre-
ments when BSC sends the PS-HANDOVER-REQUEST-NACK message. The measurement point is A3, as shown in Figure 1527.
REQUEST-NACK MESSAGES SENT BY BSC
Unit
OF
PS-HANDOVER-
Times
PS-HANDOVER-COMPL
ETE messages sent by BSC
Statistics object
Description
BSC
When the destination cell receives the first RLC/MAC block sent
from MS, it indicates that the handover is completed. This counter
counts the number of PS-HANDOVER-COMPLETE messages sent
1523
to SGSN from BSC. The counter increments when BSC sends the
PS-HANDOVER-REQUEST-COMPLETE message.
COMPLETE MESSAGES SENT BY BSC
Unit
OF
PS-HANDOVER-
Times
PS-HANDOVER-CANCEL
Statistics object
Description
1524
BSC
If PS handover fails or waiting for handover is timeout, BSC sends
the PS-HANDOVER-CANCEL message to SGSN. This counter
counts the number of PS-HANDOVER-CANCEL messages sent
by BSC. The counter increments when BSC sends the PS-HANDOVER-CANCEL message. The measurement point is A, as shown
in Figure 1529.

CANCEL MESSAGES SENT BY BSC
Unit
OF
NUMBER
OF
PS-HANDOVER-
Times
PS-HANDOVER-REQUEST
messages with Service
UTRAN CCO received by
BSC
Statistics object
Description
BSC
After BSC receives the PS-HANDOVER-REQUEST message from
SGSN, the message might contains the field Service UTRAN CCO,
which indicates that 2G/3G handover is preferred. This counter
counts the number of PS-HANDOVER-REQUEST messages, which
contains the field Service UTRAN CCO, received by BSC. After BSC
receives the PS-HANDOVER-REQUEST message from SGSN, it decodes the message to decide whether the message contains the
field Service UTRAN CCO. If the message contains the field, the
Figure 1530.
1525
FIGURE 1530 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUEST MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Unit
Times
C901220046 Number
of CREATE-BSS-PFC
BSC
Statistics object
Description
1526
BSC
When BSC receives the CREATE-BSS-PFC message from SGSN, the
message might contain the field Service UTRAN CCO. This counter
counts the number of CREATE-BSS-PFC messages, which contains
the field Service UTRAN CCO, received by BSC. After BSC receives
the CREATE-BSS-PFC message from SGSN, it decodes the message to decide whether the message contains the field Service
UTRAN CCO. If the message contains the field, the counter increments. The measurement point is A, as shown in Figure 1531.
FIGURE 1531 MEASUREMENT POINT OF NUMBER OF CREATE-BSS-PFC

MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Unit
Times
1527
1528
Chapter
29
TRX Measurement
Table of Contents
Overview...................................................................... 1531
C901230001 Number of intra-cell handover in attempts ......................................................................... 1531
C901230002 Number of intra-cell handover ins success............................................................................. 1532
C901230003 Number of Intra-BSC inter-cell handover in attempts ......................................................................... 1532
C901230004 Number of Intra-BSC intra-cell handover ins
success ........................................................................ 1533
C901230005 Number of Intra-MSC inter-cell handover in attempts ......................................................................... 1534
C901230006 Number of Intra-MSC inter-cell handover ins
success ........................................................................ 1535
C901230007 TCH busy time............................................ 1535
C901230008 Number of TCH seizures (including handover) ......................................................................... 1536
C901230009 Number of call drops due to TCH LAPD breakage.............................................................................. 1536
C901230010 Number of call drops due to TCH radio link failure .............................................................................. 1537
C901230011 Number of TCH handover call drops............... 1537
C901230012 Number of TCH/F activation attempts (including
handover) .................................................................... 1538
C901230013 Number of TCH/F activation success (including
handover) .................................................................... 1539
C901230014 Number of TCH/F assignment attempts.......... 1540
C901230015 Number of TCH/F assignment success............ 1540
C901230016 Number of TCH/H activation attempts (including
handover) .................................................................... 1541
C901230017 Number of TCH/H activation success (including
handover) .................................................................... 1542
C901230018 Number of TCH/H assignment attempts ......... 1542
C901230019 Number of TCH/H assignment success ........... 1543
C901230020 SDCCH busy time ....................................... 1544
C901230021 Number of attempts for SDCCH .................... 1545
C901230022 Number of SDCCH call drops ........................ 1545
C901230023 Number of SDCCH activation attempts (including handover) ............................................................... 1547
C901230024 Number of SDCCH activation success (including
handover) .................................................................... 1547
C901230025 Number of SDCCH assignment attempts......... 1548
C901230026 Number of SDCCH assignment success .......... 1549
C901230027 Number of samples with UL RQ = 0 ............... 1549
1529

C901230035 Number of samples with DL RQ = 0............... 1554
band 0 ......................................................................... 1558
band 1 ......................................................................... 1559
band 2 ......................................................................... 1559
band 3 ......................................................................... 1560
band 4 ......................................................................... 1560
band 5 ......................................................................... 1560
band 0 ......................................................................... 1561
band 1 ......................................................................... 1561
band 2 ......................................................................... 1561
band 3 ......................................................................... 1562
band 4 ......................................................................... 1562
band 5 ......................................................................... 1563
band 0 ......................................................................... 1563
band 1 ......................................................................... 1563
band 2 ......................................................................... 1564
band 3 ......................................................................... 1564
band 4 ......................................................................... 1564
band 5 ......................................................................... 1565
C901230061 Number of TRX poweroff .............................. 1565
C901230062 Duration of TRX poweroff ............................. 1565
1530
Chapter 29 TRX Measurement
Overview
TRX measurement is to measure the success or failure condition
of channel activation, assignment, and handover in the unit of carrier. It also can measure carrier interference band, maximum and
minimum UL & DL level condition, to learn the status of different
carriers, providing evidence for adjustment and maintenance.
C901230001 Number
of intra-cell handover in
attempts
Definition
Number of intra-cell handover in attempts.
Description
Normally, intra-cell handover is triggered by receiving level, receiving quality, interference, and concentric circle, its source cell
is same as target cell. During intra-cell handover, first send CHANNEL ACTIVATE message to target channel, and BTS responds CHANNEL
ACTIVATE ACK message.
Measurement
Point
During intra-cell handover, measurement point will be counted after BSC receives CHANNEL ACTIVATE ACK. The measurement point is A,
FIGURE 1532 - INTRA-CELL HANDOVER
Unit
Related Features
Times
1531
intra-cell handover ins
success
Definition
Number of intra-cell handover ins success.
Description
During intra-cell handover, after target channel is successfully activated, BSC will send ASSIGNMENT COMMAND message to MS through
source channel. After BSC receives ASSIGNMENT COMPLETE of MS from
target channel, intra-cell handover is successfully completed.
Measurement
Point
During intra-cell handover, the measurement point will be counted

after receive ASSIGNMENT COMPLETE. The measurement point is A2, as
FIGURE 1533 - INTRA-CELL HANDOVER
Unit
Related Features
Times
C901230003 Number
of Intra-BSC inter-cell
handover in attempts
Definition
Description
1532
Number of Intra-BSC inter-cell handover in attempts

During inter-cell handover controlled by BSC, source and target
cells are different cells under same BSC. During inter-cell handover, first send CHANNEL ACTIVATE message to target channel.
Measurement
Point
During inter-cell handover controlled by BSC, measurement point

will be counted after BSC receives CHANNEL ACTIVATE ACK message.
FIGURE 1534 - INTER-CELL HANDOVER CONTROLLED BY BSC
Unit
Related Features
Times
C901230004 Number
of Intra-BSC intra-cell
handover ins success
Definition
Number of Intra-BSC intra-cell handover ins success.
Description
During inter-cell handover controlled by BSC, after target channel

is successfully activated, BSC will send handover command to MS
through source channel. After BSC receives HANDOVER COMPLETE message of MS from target channel, inter-cell handover is successfully
completed.
Measurement
Point
During inter-cell handover controlled by BSC, measurement point

will be counted after BSC receives HANDOVER COMPLETE message. The
1533
Unit
Related Features
Times
C901230005 Number
of Intra-MSC inter-cell
Definition
Number of Intra-MSC inter-cell handover in attempts
Description
Inter-cell handover controlled by MSC is conducted after BSC receives HANDOVER REQUEST message from MSC. After BSC receives handover request message, first send CHANNEL ACTIVATE to acquisition
target channel.
Measurement
Point
During inter-cell handover (incoming) controlled by MSC, measurement point will be counted after BSC receives CHANNEL ACTIVATE
ACK. The measurement point is A1, as shown in Figure 1536.
Unit
1534
Times
Related Features
C901230006 Number
of Intra-MSC inter-cell
handover ins success
Definition
Number of Intra-MSC inter-cell handover ins success.
Description
During inter-cell handover controlled by MSC, after target channel

is successfully activated and target channel receives HANDOVER COMPLETE message sent by MS, handover is successfully done.
Measurement
Point
During inter-cell handover controlled by MSC, measurement point

will be counted after BSC receives HANDOVER COMPLETE message from
MS. The measurement point is A2, as shown in Figure 1537.
Unit
Related Features
Times
C901230007 TCH busy time

Definition
Description
TCH busy time

To count used time in voice channel on carrier, including TCH/F and
TCH/H. This can reflect carrier traffic.
Measurement formula is: (current time last measured time) *
the number of MS seizing channel. Reported measurement value
shall be gotten by accumulation of each measurement value. After
each accumulation, previous measured time will be changed to
current time; at measurement point A, the number of MS seizing
channel will increment after accumulation; at measurement point
1535
B, the number of MS seizing channel will be decremented after

accumulation.
Measurement
Point
Unit
There are 3 measurement points:
Accumulate while successfully acquire voice channel resource
Accumulate while release voice channel resource
Accumulate by regular measurement and acquisition
Second
TCH seizures (including
handover)
Definition
Description
Measurement
Point
Unit
Number of TCH seizures (including handover)

The number of seizure voice channel on carrier, including TCH/F
and TCH/H. This can reflect the traffic busy degree of carrier.
Count while successfully acquire voice channel service.
Times

drops due to TCH LAPD
breakage
Definition
Description
Measurement
Point
Unit
1536
Number of call drops due to TCH LAPD breakage.

When LAPD link is disconnected, the call on carrier will be interrupted, and this counter will record call interruption condition
caused by disconnected LAPD.
Count while receive LAPD Disconnected message.
Times

drops due to TCH radio link
failure
Definition
Number of call drops due to TCH radio link failure.
Description
When radio link quality is poor or level is low, and unable to change
to other cells, the call on carrier will be interrupted. This counter
records the call interruption condition caused by radio link failure.
Measurement
Point
Count while receiving radio link failure message. The measurement point is A, as shown in Figure 1538.
FIGURE 1538 - BSC RECEIVES RADIO LINK FAILURE MESSAGE REPORTED
BY BTS
Unit
Times
TCH handover call drops
Definition
Description
Measurement
Point
Number of TCH handover call drops.

During handover, if HANDOVER COMMAND or ASSIGNMENT COMMAND (intra-cell
handover) has been sent, but BSC doesnt receive HANDOVER COMPLETE
message or ASSIGNMENT COMPLETE message during guard time, the
handover is failed and intra-cell handover and BSC controlled intercell handover will be interrupted. This counter records the call
interruption condition caused by handover failure.
This counter will count at following cases:
When receiving T3013 timer timeout message. The measurement point is A2, as shown in Figure 1539.
1537
FIGURE 1539 - INTER-CELL HANDOVER FAILURE
When receiving T3107 timer timeout message. The measurement point is A2, as shown in .Figure 1540.
FIGURE 1540 - INTRA-CELL HANDOVER FAILURE
Unit
Times
TCH/F activation attempts
(including handover)
Definition
1538
Number of TCH/F activation attempts (including handover)
Description
Count the number of originating CHANNEL ACTIVATE messages from

carrier TCH/F channel.
Measurement
Point
Count after BSC sends CHANNEL ACTIVATE message to BTS. The measurement point is A1, as shown inFigure 1541.
FIGURE 1541 - CHANNEL ACTIVATION MEASUREMENT POINT
Unit
Related Features
Times
TCH/F activation success
Definition
Number of TCH/F activation success (including handover)
Description
Count the number of successful activation from carrier TCH/F

channel.
Measurement
Point
Count after BSC receives CHANNEL ACTIVATE ACK message. The measurement point is A2, as shown inFigure 1542 .
1539
Unit
Related Features
Times
Definition
Number of TCH/F assignment attempts.
Description
Count the number of sending ASSIGNMENT COMMAND by BSC while assigning TCH/F channel.
Measurement
Point
Count after BSC sends ASSIGNMENT COMMAND message to BTS. The

measurement point is A1, as shownFigure 1543.
FIGURE 1543 - TCH/F CHANNEL ASSIGNMENT MEASUREMENT POINT
Unit
Related Features
Times
Definition
1540
Number of TCH/F assignment success
Description
When assign TCH/F channel, BSC sends ASSIGNMENT COMMAND message to assignment channel, after BSC receives EST IND or ASSIGNMENT COMPLETE message, channel assignment is successful.
Measurement
Point
Count after BSC receives EST IND or ASSIGNMENT COMPLETE message.

Unit
Related Features
Times
TCH/H activation attempts
Definition
Number of TCH/H activation attempts (including handover).
Description
Count the number of originating channel activation from carrier

TCH/H channel.
Measurement
Point
Count after BSC sends CHANNEL ACTIVATE message to BTS. The measurement point is A1, as shown inFigure 1545.
1541
Unit
Related Features
Times
TCH/H activation success
Definition
Number of TCH/H activation success (including handover).
Description
Count the number of successful activation from carrier TCH/H

channel.
Measurement
Point
Unit
Related Features
Times
TCH/H assignment attempts
Definition
Description
1542
Number of TCH/H assignment attempts

Count the number of sending ASSIGNMENT COMMAND by BSC while assigning TCH/H channel.
Measurement
Point
Count after BSC sends ASSIGNMENT COMMAND message to BTS. The

measurement point is A1, as shown inFigure 1547 .
Unit
Related Features
Times
Definition
Number of TCH/H assignment success
Description
When assign TCH/H channel, BSC sends ASSIGNMENT COMMAND message to assignment channel, after BSC receives EST IND or ASSIGNMENT COMPLETE message, channel assignment is successful.
Measurement
Point
Count after BSC receives EST IND or ASSIGNMENT COMPLETE message.

1543
Unit
Related Features
C901230020 SDCCH busy

time
Definition
Description
SDCCH busy time

Time used by SDCCH channel on carrier, including assignment and
handover. This can reflect traffic of carrier SDCCH channel.
Measurement formula is: (current time last measured time) *
the number of MS seizing channel.
Reported measurement value shall be gotten by accumulation of
each measurement value. After each accumulation, previous measured time will be changed to current time; when SDCCH channel
is seized, the number of MS seizing channel will be incremented
after accumulation; when SDCCH channel is released, the number
of MS seizing channel will be decremented after accumulation.
Measurement
Point
Unit
1544
There are 3 measurement points as follows.
Accumulate while successfully acquire SDCCH channel resource
Accumulate while release SDCCH channel resource
Accumulate by regular measurement and acquisition
Times
attempts for SDCCH
Definition
Description
Measurement
Point
Unit
Number of attempts for SDCCH

Count the number of successful and failed SDCCH application during assignment and handover.
Count after BSC applying for SDCCH is successful or failed.
Times
SDCCH call drops
Definition
Description
Number of SDCCH call drops

During assignment and handover, ASSIGNMENT COMPLETE or HANDOVER
send ASSIGNMENT COMMAND or HANDOVER
or T3107 timer times out, it is considered as SDCCH failure, see Figure 1549 andFigure 1550.
COMPLETE is not received after
COMMAND message. After T3103
FIGURE 1549 - INTER-CELL HANDOVER FAILURE
1545
FIGURE 1550 - INTRA-CELL HANDOVER FAILURE
If handover to external cell, when HANDOVER COMMAND is delivered,

start THoOutGo, CLEAR COMMAND of MSC is not received before
THoOutGo times out, it is considered as SDCCH failure, as shown
inFigure 1551 .
FIGURE 1551 - THOOUTGO TIMEOUT
In addition, when LAPD is broken or disconnected, if channel is

SDCCH, it will be recorded as SDCCH call drops.
Measurement
Point
Unit
1546
This counter will count at following cases:
When BSC receives LAPD breakage message and channel is

SDCCH.
When BSC connection faults and channel is SDCCH.
After THoOutGo timer times out.
After T3103 timer times out.
After T3107 timer times out.
Times
SDCCH activation attempts
Definition
Number of SDCCH activation attempts (including handover)
Description
Count the number of originating CHANNEL ACTIVATE messages from

carrier SDCCH channel.
Measurement
Point
Count after BSC sends CHANNEL ACTIVATE message to BTS. The measurement point is A1, as shown inFigure 1552 .
Unit
Times
SDCCH activation success
Definition
Number of SDCCH activation success (including handover)
Description
Count the number of successful activation from carrier SDCCH

channel.
Measurement
Point
1547
Unit
Times
C901230025 Number
of SDCCH assignment
attempts
Definition
Number of SDCCH assignment attempts
Description
When assign SDCCH channel, BSC assigns SDCCH channels

by sending IMMEDIATE ASSIGNMENT message or ASSIGNMENT COMMAND
message. This counter counts the number of SDCCH assignment
attempts.
Measurement
Point
Count after BSC sends IMMEDIATE ASSIGNMENT message or ASSIGNMENT

COMMAND to BTS. The measurement point is A1, as shown in Figure
1554.
FIGURE 1554 - CHANNEL ASSIGNMENT MEASUREMENT POINT
1548
Unit
Times
SDCCH assignment success
Definition
Number of SDCCH assignment success
Description
When assign SDCCH channel, BSC sends IMMEDIATE ASSIGNMENT message or ASSIGNMENT COMMAND message to assignment channel, after
BSC receives EST IND (CM SERV REQ), channel assignment is successful.
Measurement
Point
Count after BSC receives EST IND (CM SERV REQ) message. The measurement point is A2, as shown in Figure 1555.
FIGURE 1555 - CHANNEL ASSIGNMENT MEASUREMENT POINT
Unit
Times
Definition
Description
Number of samples with UL RQ = 0

per 480 ms.
1549

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
1550
THE
Times
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
Definition
Description

measurement report.
Measurement
Point

BY BTS
THE
1551
Unit
Times
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
Definition
1552
Description

measurement report.
Measurement
Point


BY BTS
Unit
THE
Times
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
Description

measurement report.
1553
Measurement
Point

BTS
Unit
THE
BY
Times
Definition
Number of samples with DL RQ = 0
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
Definition
1554
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
1555
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
Definition
Description

measurement report.
Measurement
Point

BY BTS
1556
THE
Unit
Times
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times
Definition
Description

measurement report.
Measurement
Point

1557

BY BTS
Unit
THE
Times
Definition
Description

measurement report.
Measurement
Point

BY BTS
Unit
THE
Times

of idle TCH/Fs with
interference band 0
Definition
1558
Description
Measurement
Point
Unit
Related Features
Regularly query database, acquire idle TCH/F number at different

interference level on carrier, to represent average with queried
value. Interference level for different TCH/F channel in database
will be updated after BSC receives radio resource sent by BTS.
C901230060 is same as that of this measurement value. This
measurement value is idle TCH/F number when interference band
is 0 in carrier.
Count when regularly query database.
Times

of idle TCH/Fs with
interference band 1
Definition
Description
Measurement
Point
Unit
Related Features

This measurement value is idle TCH/F number when interference
band is 1 in carrier.
Times

of idle TCH/Fs with
interference band 2
Definition
Description
Measurement
Point
Unit
Related Features

Times
1559

of idle TCH/Fs with
interference band 3
Definition
Description
Measurement
Point
Unit
Related Features

Times

of idle TCH/Fs with
interference band 4
Definition
Description
Measurement
Point
Unit
Related Features

Times

of idle TCH/Fs with
interference band 5
Definition
Description
Measurement
Point
Unit
Related Features
1560

Times

of idle TCH/Hs with
interference band 0
Definition
Description
Measurement
Point
Unit
Related Features
Mean number of idle TCH/Hs with interference band 0

This measurement value is idle TCH/H number when interference
Times

of idle TCH/Hs with
interference band 1
Definition
Description
Measurement
Point
Unit
Related Features

Times

of idle TCH/Hs with
interference band 2
Definition
Description
Measurement
Point

1561
Unit
Related Features
Times

of idle TCH/Hs with
interference band 3
Definition
Description
Measurement
Point
Unit
Related Features

Times

of idle TCH/Hs with
interference band 4
Definition
Description
Measurement
Point
Unit
Related Features
1562

Times

of idle TCH/Hs with
interference band 5
Definition
Description
Measurement
Point
Unit
Related Features

Times

of idle SDCCHs with
interference band 0
Definition
Description
Measurement
Point
Unit

This measurement value is idle SDCCH number when interference
Times

of idle SDCCHs with
interference band 1
Definition
Description
Measurement
Point
Unit

Times
1563

of idle SDCCHs with
interference band 2
Definition
Description
Measurement
Point
Unit

Times

of idle SDCCHs with
interference band 3
Definition
Description
Measurement
Point
Unit

Times

of idle SDCCHs with
interference band 4
Definition
Description
Measurement
Point
Unit
1564

Times

of idle SDCCHs with
interference band 5
Definition
Description
Measurement
Point
Unit

Times
TRX poweroff
Definition
Description
Measurement
Point
Unit
Related Features
Number of TRX power off.

This counter counts the number of TRX smart power off, excluding
normal POWER OFF.
This counter increments during smart power on.
Times
TRX poweroff
Definition
Description
Measurement
Point
Unit
Related Features
Duration of TRX power off.

This counter counts the duration of TRX power off.
This counter increments during smart power on.
Times
1565
Description
Enable the function of reporting voice quality information, and

count the number of error frames of voice version 1 in the measurement report received on the FR channel.
Measurement
Point
The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received.
Unit
Times

Description

count the number of voice frames of voice version 1 in the measurement report received on the FR channel.
Measurement
Point
Unit
Times
Description

Measurement
Point
Unit
1566
Times

Description

Measurement
Point
Unit
Times
Description

Measurement
Point
Unit
Times

Description

Measurement
Point
Unit
Times
1567
Description

count the number of error frames of voice version 1 in the measurement report received on the HR channel.
Measurement
Point
Unit
Times

Description

count the number of voice frames of voice version 1 in the measurement report received on the HR channel.
Measurement
Point
Unit
Times
Description

count the number of error frames of voice version 3 in the measurement report received on the HR channel.
Measurement
Point
Unit
1568
Times

Description

count the number of voice frames of voice version 3 in the measurement report received on the HR channel.
Measurement
Point
Unit
Times
1569
1570
Chapter
30
Timeslot Measurement
Table of Contents
Overview...................................................................... 1572
C901240001 Maximum value of UL RQ ............................. 1572
C901240002 Minimum value of UL RQ .............................. 1573
C901240003 Value of UL RQ ........................................... 1573
C901240004 Number of scans of UL RQ............................ 1574
C901240005 Maximum value of DL RQ ............................. 1575
C901240006 Minimum value of DL RQ.............................. 1575
C901240007 Value of DL RQ ........................................... 1576
C901240008 Number of scans of DL RQ ........................... 1576
C901240009 Maximum value of received UL signal
strength ....................................................................... 1577
C901240010 Minimum value of received UL signal
strength ....................................................................... 1578
C901240011 Total value of received UL signal strength......... 1578
C901240012 Number of received UL signal strength samples ............................................................................. 1579
C901240013 Maximum value of received DL signal
strength ....................................................................... 1580
C901240014 Minimum value of received DL signal
strength ....................................................................... 1580
C901240015 Total value of received DL signal strength......... 1581
C901240016 Number of received DL signal strength samples ............................................................................. 1581
C901240017 Value of power scans of MS transmitting
power .......................................................................... 1582
C901240018 Number of power scans of MS transmitting
power .......................................................................... 1583
C901240019 Value of power scans of BTS power ............... 1583
C901240020 Number of power scans of BTS power ............ 1584
C901240021 Number of immediate assignment failure......... 1584
C901240022 Number of assignment failure ....................... 1585
C901240023 Number of handovers failure ........................ 1586
C901240024 Maximum interference value......................... 1587
C901240025 Minimum interference value ......................... 1587
C901240026 Interference value....................................... 1588
C901240027 Number of regular scanning and sampling of interference value ............................................................ 1589
C901240028 Number of call drop..................................... 1589
C901240029 Maximum value of path balance .................... 1590
C901240030 Minimum value of path balance..................... 1590
C901240031 Value of path balance .................................. 1591
path balance................................................................. 1592
C901240033 Value of UL loss .......................................... 1592
C901240034 Number of regular scanning and sampling of UL
loss ............................................................................. 1593
1571
C901240035 Total value of DL loss................................... 1593

C901240036 Number of regular scanning and sampling of DL
loss ............................................................................. 1594
C901240037 Number of drops due to the bad quality of UL
receive......................................................................... 1595
C901240038 Number of drops due to the bad quality of DL
receive......................................................................... 1596
C901240039 Number of drops due to the low electric level of
UL ............................................................................... 1598
C901240040 Number of drops due to the low electric level of
DL ............................................................................... 1600
C901240041 Number of drops due to the TA too far ........... 1602
C901240042 Number of drops due to the other radio reasons ............................................................................ 1604
C901240043 The valid time of the used voice channel......... 1606
C901240044 Number of activated voice channel ................ 1607
Overview
Timeslot counters are used to view the radio transceiver environment of a MS in a particular timeslot, including the link quality
and strength in the timeslot. These data is sent to Network side
through measurement report. If signal strength in some timeslots
is weak, then it can be improved by changing send and receive
power.
The measurement takes cell as statistics unit.
C901240001 Maximum
value of UL RQ
Definition
1572
Maximum UL RQ
Description
This counter counts Maximum UL RQ in the measurement report

of a timeslot in a cell.
Usage
This counter is used to find out the Maximum UL RQ in a timeslot

of a cell. It is one of the parameters that evaluate timeslot radio
environment.
Measurement
Point
After BSC receives the measurement report from BTS, if UL RQ in

the report is bigger than the value in the counter, the UL RQ in
the counter is replaced. The measurement point is A, as shown in
Figure 1572.
Chapter 30 Timeslot Measurement
FIGURE 1572 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Unit
NA

of UL RQ
Definition
Minimum UL RQ
Description
This counter counts Minimum UL RQ in the measurement report of

a timeslot in a cell.
Usage
This counter is used to find out the Minimum UL RQ in a timeslot

environment.
Measurement
Point
After BSC receives the measurement report from BTS, if UL RQ

in the report is less than the value in the counter, the UL RQ in
Figure 1573.
Unit
NA
C901240003 Value of UL
RQ
Definition
Description
Total value of UL RQ
This counter counts the total value of UL RQ of a timeslot of a cell
in the measurement report.
1573
Usage
This counter is used to find out the Total value of UL RQ in a timeslot of a cell. It is one of the parameters that evaluate timeslot radio
environment.
Measurement
Point
After BSC receives the measurement report from BTS, the counter
accumulates UL RQ value for relevant timeslot. The measurement
Unit
NA
scans of UL RQ
Definition
Number of scans of UL RQ
Description
This counter counts the number of times of sampling UL RQ of a

timeslot in a cell.
Usage
This counter shows the frequency of sampling UL RQ of a timeslot

in a cell. It is one of the parameters that evaluate timeslot radio
environment.
Measurement
Point
The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure
1575.
Unit
1574
Times
C901240005 Maximum
value of DL RQ
Definition
Maximum value of DL RQ
Description
This counter counts Maximum DL RQ in the measurement report

Usage
This counter is used to find out the Maximum DL RQ in a timeslot

environment.
Measurement
Point
After BSC receives the measurement report from BTS, if DL RQ in

the report is bigger than the value in the counter, the DL RQ is in
the counter replaced. The measurement point is A, as shown in
Figure 1576
Unit
NA

of DL RQ
Definition
Minimum DL RQ
Description
This counter counts Minimum DL RQ in the measurement report

Usage
This counter is used to find out the Minimum DL RQ in a timeslot

environment.
Measurement
Point
After BSC receives the measurement report from BTS, if DL RQ

in the report is less than the value in the counter, the DL RQ in
Figure 1577.
1575
Unit
NA
C901240007 Value of DL
RQ
Definition
Total value of DL RQ
Description
This counter counts the total value of DL RQ of a timeslot of a cell

in the measurement report.
Usage
This counter is used to find out the Total value of DL RQ in a timeslot of a cell. It is one of the parameters that evaluate timeslot radio
environment.
Measurement
Point
accumulates DL RQ value for relevant timeslot. The measurement
Unit
NA
scans of DL RQ
Definition
Description
1576
Number of scans of DL RQ
This counter counts the number of times of sampling DL RQ of a
timeslot in a cell.
Usage
This counter shows the frequency of sampling DL RQ of a timeslot

environment.
Measurement
Point
1579.
Unit
Times
C901240009 Maximum
value of received UL signal
strength
Definition
Maximum value of received UL signal strength
Description
This counter counts Maximum value of received UL signal strength

in the measurement report of a timeslot in a cell.
Usage
This counter is used to find out the Maximum value of received UL

signal strength in a timeslot of a cell. It is one of the parameters
that evaluate timeslot radio environment.
Measurement
Point
After BSC receives the measurement report from BTS, if received

UL signal strength in the report is bigger than the value in the
counter, the received UL signal strength in the counter is replaced.
Unit
dBm
1577
C901240010 Minimum
value of received UL signal
strength
Definition
Minimum value of received UL signal strength
Description
This counter counts Minimum value of received UL signal strength

Usage
This counter is used to find out the Minimum value of received UL

signal strength in a timeslot in a cell. It is one of the parameters
Measurement
Point
After BSC receives the measurement report from BTS, if the value
of received UL signal strength in the report is less than the value
in the counter, the received UL signal strength in the counter is
replaced. The measurement point is A, as shown in Figure 1581.
Unit
dBm

Definition
1578
Total value of received UL signal strength
Description
This counter counts the total value of received UL signal strength

of a timeslot of a cell in the measurement report.
Usage
This counter is used to find out the total value of received UL signal
strength in a timeslot in a cell. It is one of the parameters that
evaluate timeslot radio environment.
Measurement
Point
accumulates UL reception strength value for relevant timeslot. The
Unit
dBm
samples
Definition
Number of received UL signal strength samples
Description
This counter counts the number of times of sampling UL signal

strength in a timeslot in a cell.
Usage
This counter shows the frequency of sampling UL signal strength

in a timeslot in a cell. It is one of the parameters that evaluate
timeslot radio environment.
Measurement
Point
1583.
Unit
Times
1579
C901240013 Maximum
value of received DL signal
strength
Definition
Maximum value of received DL signal strength
Description
This counter counts Maximum value of received DL signal strength

Usage
This counter is used to find out the Maximum value of received DL

signal strength in a timeslot of a cell. It is one of the parameters
Measurement
Point
After BSC receives the measurement report from BTS, if DL reception strength in the report is bigger than the value in the counter,
the DL reception strength in the counter is replaced. The measurement point is A, as shown in Figure 1584.
Unit
dBm
C901240014 Minimum
value of received DL signal
strength
Definition
1580
Minimum value of received DL signal strength
Description
This counter counts Minimum value of received DL signal strength

Usage
This counter is used to find out the Minimum value of received DL

signal strength in a timeslot in a cell. It is one of the parameters
Measurement
Point
After BSC receives the measurement report from BTS, if DL reception strength in the report is less than the value in the counter, the
DL reception strength in the counter is replaced. The measurement point is A, as shown in Figure 1585.
Unit
dBm

Definition
Total value of received DL signal strength
Description
This counter counts the total value of received DL signal strength

in a timeslot in a cell in the measurement report.
Usage
This counter is used to find out the total value of received DL signal
Measurement
Point
accumulates DL reception strength value for relevant timeslot. The
Unit
dBm
samples
Definition
Number of received DL signal strength samples
1581
Description
This counter counts the number of times of sampling received DL

signal strength in a timeslot in a cell.
Usage
This counter shows the frequency of sampling received DL signal

Measurement
Point
1587.
Unit
Times
C901240017 Value of power

scans of MS transmitting
power
Definition
Total value of power scans of MS transmitting power
Description
This counter counts the total value of MS transmitting power in a

timeslot in a cell in the measurement report.
Usage
This counter is used to find out the total value of MS transmitting

power in a timeslot in a cell. It is one of the parameters that
Measurement
Point
accumulates MS power value for relevant timeslot. The measurement point is A, as shown in Figure 1588.
Unit
1582
dBm
C901240018 Number
of power scans of MS
transmitting power
Definition
Number of power scans of MS transmitting power
Description
This counter counts the number of times of sampling MS transmitting power in a timeslot in a cell.
Usage
This counter shows the frequency of sampling MS transmitting

power in a timeslot in a cell. It is one of the parameters that
Measurement
Point
1589.
Unit
Times
C901240019 Value of power

scans of BTS power
Definition
Total value of power scans of BTS power
Description
This counter counts the total value of BTS power in a timeslot in a

cell in the measurement report.
Usage
This counter is used to find out the total value of BTS power in a
timeslot in a cell. It is one of the parameters that evaluate timeslot
radio environment.
Measurement
Point
accumulates BTS power value for relevant timeslot. The measurement point is A, as shown in Figure 1590.
1583
Unit
dBm
power scans of BTS power
Definition
Number of power scans of BTS power
Description
This counter counts the number of times of sampling BTS power

in a timeslot in a cell.
Usage
This counter shows the frequency of power scans of BTS power

Measurement
Point
1591.
Unit
dBm
immediate assignment
failure
Definition
1584
Number of immediate assignment failure
Description
This counter counts the number of times of immediate assignment

failure in a timeslot in a cell.
Usage
This counter shows the frequency of immediate assignment failure

Measurement
Point
After BSC sent immediate assignment to MS, if access Timer overtimes, the counter increments in relevant timeslot. The measurement point is A2, as shown in Figure 1592.
In the waiting state, case release caused by any reason, leads
immediate assignment failure, then the counter increments in relevant timeslot. The measurement point is A1, as shown in Figure
1592.
FIGURE 1592 IMMEDIATE ASSIGNMENT FAILURE MEASUREMENT POINT
Unit
Times
assignment failure
Definition
Number of assignment failure
Description
This counter counts the number of times of assignment failure in

a timeslot in a cell.
Usage
This counter shows the frequency of assignment failure in a timeslot in a cell. It is one of the parameters that evaluate timeslot radio
environment.
Measurement
Point
After BSC sent assignment to MS, if access Timer overtimes, the

counter increments in relevant timeslot. The measurement point
In the waiting state, case release caused by any reason, leads assignment failure, then the counter increments in relevant timeslot.
1585
FIGURE 1593 ASSIGNMENT FAILURE MEASUREMENT POINT
Unit
Times
handovers failure
Definition
Number of handovers failure
Description
This counter counts the number of times of handover failure in a

timeslot in a cell.
Usage
This counter shows the frequency of handover failure in a timeslot

environment.
Measurement
Point
After BSC sent handover to MS, if access Timer overtimes, the

counter increments in relevant timeslot. The measurement point
In the waiting state, case release caused by any reason, leads
handover failure, then the counter increments in relevant timeslot.
FIGURE 1594 HANDOVERS FAILURE MEASUREMENT POINT
Unit
1586
Times
C901240024 Maximum
interference value
Definition
Maximum interference value
Description
This counter counts the Maximum interference band value in a

timeslot in a cell.
Usage
This counter shows the Maximum interference band value in a

timeslot in a cell. It is one of the parameters that evaluate timeslot radio environment.
Measurement
Point
When BSC received resource indication from BTS updating interference band, if interference band reported is bigger than the value
in the counter, the value in the counter is replaced. The measurement point is A, as shown in Figure 1595.
FIGURE 1595 RESOURCE INDICATION MEASUREMENT POINT
Unit
NA
C901240025 Minimum
interference value
Definition
Minimum interference value
Description
This counter counts the Minimum interference band value in a

timeslot in a cell.
Usage
This counter shows the Minimum interference band value in a

timeslot in a cell. It is one of the parameters that evaluate
Measurement
Point
When BSC received resource indication from BTS updating interference band, if interference band reported is less than the value
in the counter, the value in the counter is replaced. The measurement point is A, as shown in Figure 1596.
1587
Unit
NA
C901240026 Interference
value
Definition
Total value of interference
Description
This counter counts the total value of interference band in a timeslot in a cell.
Usage
This counter is used to find out the total value of interference band
Measurement
Point
When BSC received resource indication from BTS updating interference band, the counter accumulates interference value for relevant timeslot. The measurement point is A, as shown in Figure
1597.
Unit
1588
NA
C901240027 Number
of regular scanning and
sampling of interference
value
Definition
Number of regular scanning and sampling of interference value
Description
This counter counts the number of times of interference band value

report in a timeslot in a cell.
Usage
This counter is used to find out the frequency of interference band

value sampling in a timeslot in a cell. It is one of the parameters
Measurement
Point
The counter increments in relevant timeslot after BSC receives resource indication from BTS updating interference band. The measurement point is A, as shown in Figure 1598.
Unit
Times

drop
Definition
Number of call drop
Description
This counter counts the number of call drop caused by radio link
failure in a timeslot in a cell.
Usage
This counter is used to find out the frequency of call drop caused by
radio link failure in a timeslot in a cell. It is one of the parameters
Measurement
Point
The counter increments in relevant timeslot after BSC receives radio link failure from BTS. The measurement point is A, as shown
in Figure 1599.
1589
Unit
Times
C901240029 Maximum
value of path balance
Definition
Maximum value of path balance
Description
This counter counts the Maximum value of path balance in a timeslot in a cell. Path balance is the path loss margin of UL and DL path.
Usage
This counter shows the Maximum value of path balance in a timeslot in a cell. It is one of the parameters that evaluate timeslot radio
environment.
Measurement
Point
When BSC receives measurement report from BTS, calculate the

current path loss. Then path balance is calculated according UL
and DL path loss. If the path balance calculated is more than the
value in the counter, then the value in the counter is replaced. The
Unit
dBm

of path balance
Definition
1590
Minimum value of path balance
Description
This counter counts the Minimum value of path balance in a timeslot in a cell. Path balance is the path loss margin of UL and DL path.
Usage
This counter shows the Minimum value of path balance in a timeslot in a cell. It is one of the parameters that evaluate timeslot
radio environment.
Measurement
Point

and DL path loss. If the path balance calculated is less than the
value in the counter, then the value in the counter is replaced. The
Unit
dBm
C901240031 Value of path

balance
Definition
Total value of path balance
Description
This counter counts the total value of path balance in a timeslot in

a cell.
Usage
This counter is used to find out the total value of path balance in a
radio environment.
Measurement
Point

and DL path loss. The counter accumulates the path balance for
relevant timeslot. The measurement point is A, as shown in Figure
1602.
Unit
dBm
1591
C901240032 Number
sampling of path balance
Definition
Number of path balance sampling
Description
This counter counts the number of path balance sampling in a

timeslot in a cell.
Usage
This counter is used to find out the frequency of path balance sampling in a timeslot in a cell. It is one of the parameters that evaluate timeslot radio environment.
Measurement
Point
The counter increments in relevant timeslot when BSC receives

measurement point from BTS and calculates path balance. The
Unit
Times
C901240033 Value of UL
loss
Definition
1592
Total value of UL loss
Description
This counter counts the total value of UL loss in a timeslot in a cell.
Usage
This counter is used to find out the total value of UL loss in a

radio environment.
Measurement
Point

and DL path loss. The counter accumulates the path balance for
relevant timeslot. The measurement point is A, as shown in Figure
1604.
Unit
dBm
C901240034 Number
sampling of UL loss
Definition
Description
Number of regular scanning and sampling of UL loss

This counter counts the number of UL loss in a timeslot in a cell.
Usage
This counter is used to find out the frequency of sampling in UL

path in a timeslot in a cell. It is one of the parameters that evaluate
radio environment.
Measurement
Point

current UL path loss. The counter increments if UL path loss is
valid. The measurement point is A, as shown in Figure 1605.
Unit
Times

DL loss
Definition
Description
Total value of DL loss

This counter counts the maximum of DL loss in a timeslot in a cell.
1593
Usage
This counter is used to find out the maximum of UL path loss in a

timeslot in a cell. It is one of the parameters that evaluate radio
environment.
Measurement
Point

current DL path loss. The counter increments if DL path loss is
valid. The measurement point is A, as shown in Figure 1606.
Unit
dB
C901240036 Number
sampling of DL loss
Definition
Description
Number of regular scanning and sampling of DL loss

This counter counts the number of DL loss in a timeslot in a cell.
Usage
This counter is used to find out the frequency of sampling in DL

path in a timeslot in a cell. It is one of the parameters that evaluate
radio environment.
Measurement
Point

current UL path loss. The counter increments if DL path loss is
valide. The measurement point is A, as shown in Figure 1607.
Unit
1594
Times
drops due to the bad quality
of UL receive
Definition
Number of drops due to the bad quality of UL receive
Description
This counter counts the number of call drops on some timeslot in

the cell due to radio link failure. After MS obtains SDCCH or TCH,
call drop occurs. If the problem is caused by bad uplink receiving
quality, the counter increments.
Usage
This counter is used to find out the frequency of call drop on some
timeslot due to radio link failure which is caused by bad uplink
receiving quality. It is one of the radio parameters that evaluate
the timeslot.
Measurement
Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on SDCCH. The measurement point is A, as shown in Figure 1608.
FIGURE 1608 CALL DROP DUE TO RADIO LINK FAILURE
DURING
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 1609.
1595

ASSIGNMENT PROCESS
Unit
DUE TO
RADIO LINK FAILURE
DURING
Times
drops due to the bad quality
of DL receive
Definition
1596
Number of drops due to the bad quality of DL receive
Description
This counter counts the number of call drops on some timeslot

in the cell due to radio link failure. After MS obtains SDCCH or
TCH, call drop occurs. If the problem is caused by bad downlink
receiving quality, the counter increments.
Usage
timeslot due to radio link failure which is caused by bad downlink
receiving quality. It is one of the radio parameters that evaluate

the timeslot.
Measurement
Point
DURING
1597

ASSIGNMENT PROCESS
Unit
DUE TO
RADIO LINK FAILURE
DURING
Times
drops due to the low electric
level of UL
Definition
1598
Number of drops due to the low electric level of UL
Description

call drop occurs. If the problem is caused by low uplink receiving
level, the counter increments.
Usage
timeslot due to radio link failure which is caused by low uplink
receiving level. It is one of the radio parameters that evaluate the

timeslot.
Measurement
Point
DURING
1599

ASSIGNMENT PROCESS
Unit
DUE TO
RADIO LINK FAILURE
DURING
Times
drops due to the low electric
level of DL
Definition
1600
Number of drops due to the low electric level of DL
Description
This counter counts the number of call drops on some timeslot

in the cell due to radio link failure. After MS obtains SDCCH or
TCH, call drop occurs. If the problem is caused by low downlink
receiving level, the counter increments.
Usage
timeslot due to radio link failure which is caused by low downlink
receiving level. It is one of the radio parameters that evaluate the

timeslot.
Measurement
Point
DURING
1601

ASSIGNMENT PROCESS
Unit
DUE TO
RADIO LINK FAILURE
DURING
Times
drops due to the TA too far
Definition
1602
Number of drops due to the TA too far
Description

call drop occurs. If the problem is caused by TA being too far, the
counter increments.
Usage
timeslot due to radio link failure which is caused by TA being too
far. It is one of the radio parameters that evaluate the timeslot.
Measurement
Point
DURING
1603

ASSIGNMENT PROCESS
Unit
DUE TO
RADIO LINK FAILURE
DURING
Times
drops due to the other radio
reasons
Definition
Description
1604
Number of drops due to the other radio reasons

call drop occurs. If the problem is not due to the above five causes
(i.e. bad uplink receiving quality, bad downlink receiving quality,
low uplink receiving level, low downlink receiving level, and TA
being too far), the counter increments.
Usage
Measurement
Point
timeslot due to radio link failure which is caused by other radio
problems. It is one of the radio parameters that evaluate the
timeslot.
DURING
counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement
1605

ASSIGNMENT PROCESS
Unit
DUE TO
RADIO LINK FAILURE
DURING
Times
C901240043 The valid time

of the used voice channel
Definition
1606
The valid time of the used voice channel
Description
This counter counts the valid occupation time of a timeslot's voice

channel in the cell.
Usage
This counter is used to find out the sum of valid occupation time
of a timeslot's voice channel in the cell. It is one of the radio
parameters that evaluate the timeslot.
Measurement
Point
When BSC receives the measurement report from BTS, the counter
is accumulated with a time value. Different measurement report
type corresponds to different value, for common measurement re-
port, the time value is 480 ms. The measurement point is A, as

FIGURE 1620 BSC RECEIVES MEASUREMENT REPORT
Unit
FROM
BTS
ms
activated voice channel
Definition
Number of activated voice channel
Description
This counter counts the number of a timeslot's voice channel being

activated in the cell.
Usage
This counter is used to find out the frequency of a timeslot's voice

channel being activated in the cell. It is one of the radio parameters that evaluate the timeslot.
Measurement
Point
When BSC receives the CHANNEL ACTIVATE ACK message, the

Figure 1621.
Unit
WHEN
CHANNEL IS ACTIVATED
Times
1607
1608
Chapter
31
SDCCH Measurement
Table of Contents
Overview...................................................................... 1610
C901250005 Number of SDCCH seizure success for Handover........................................................................... 1611
C901250007 Number of SDCCH allocation attempts for Assignment...................................................................... 1613
C901250010 Number of SDCCH allocation attempts for handover........................................................................... 1614
C901250011 Number of SDCCH allocation success for handover........................................................................... 1616
C901250012 Number of SDCCH allocation failure for handover........................................................................... 1617
C901250016 Number of SDCCH handover failure ............... 1618
C901250017 Number of SDCCH handover success ............. 1620
C901250018 Number of SDCCH handover failure with Reconnection ........................................................................ 1622
C901250019 Number of SDCCH handover failure without Reconnection.................................................................... 1622
(MOC).......................................................................... 1623
(MOC).......................................................................... 1624
(MOC).......................................................................... 1625
(MTC) .......................................................................... 1626
(MTC) .......................................................................... 1627
(MTC) .......................................................................... 1628
C901250026 Number of SDCCH assignment attempts (call
re-establishment) .......................................................... 1629
C901250027 Number of successful SDCCH assignments (call
re-establishment) .......................................................... 1630
(call re-establishment) ................................................... 1631
C901250029 Number of SDCCH assignment attempts (emergency call).................................................................... 1632
(emergency call) ........................................................... 1633
(emergency call) ........................................................... 1634
(LOC) .......................................................................... 1635
(LOC) .......................................................................... 1636
1609

(LOC) .......................................................................... 1637
C901250035 Number of SDCCH assignment attempts (other
cause) ......................................................................... 1638
(other cause) ................................................................ 1639
(other cause) ................................................................ 1640
C901250038 Count of USSD attempts to connect............... 1641
C901250039 Average dialoge time of USSD services .......... 1642
C901250040 Dialog counts of USSD services..................... 1642
Overview
SDCCH counters describe allocation, occupation, assignment, use
of resources related to SDCCH, which as SDCCH configuration and
parameters adjustment basis. Allocation of SDCCH is mainly in
the process of immediate assignment and handover. Handover
includes internal and external handover. The statistic unit in this
measurement is cell.
The Measurement point Of SDCCH counters in the process of immediate assignment is shown in Figure 1622.
FIGURE 1622 THE PROCESS OF IMMEDIATE ASSIGNMENT
The Measurement point Of SDCCH counters in the process of internal handover (like intra-cell handover) is shown in Figure 1623.
1610
Chapter 31 SDCCH Measurement
FIGURE 1623
HANDOVER)
THE PROCESS OF INTERNAL HANDOVER (LIKE
INTRA-CELL
The Measurement point Of SDCCH counters in the process of external handover is shown in Figure 1624.
FIGURE 1624 THE PROCESS OF EXTERNAL HANDOVER
SDCCH seizure success for
Handover
Definition
Number of SDCCH seizure success for Handover
1611
Description
SDCCH allocation attempt is triggered by the channel request message RADIO_APPLY from other channel instances. BSC attempts
to allocate SDCCH after receiving the message. If SDCCH allocation and seizure succeed, the counter increments. If application
response shows no SDCCH available but queuing or forced release
is possible, enter the state of waiting for resource. If SDCCH is
available after waiting, then the counter increments. If application response shows transceiver is faulty, the three counters do
not change.
Usage
This counter records the number of SDCCH seizure success for

handover.
Measurement
Point
When BSC requesting for SDCCH (due to handover) is completed

and SDCCH seizure succeeds, or BSC gets valid response of waiting
resource. The measurement point is B1 as shown in Figure 1625,
and C1 as shown in Figure 1626.
FIGURE 1625
HANDOVER)
1612
INTRA-CELL
Unit
Related Features
Times
SDCCH allocation attempts
for Assignment
Definition
Number of SDCCH allocations attempts for assignment
Description
This counter records the number of SDCCH allocations attempts

for assignment, including successful allocations (C900060008) and
unsuccessful allocations (C900060009).
Usage

occupy SDCCH channel successfully, BSC sends the CHL_ACT message to BTS to activate this SDCCH channel. If the activation succeeds (that is, when BSC receives the CHL_ACT_ACK message
from BTS), this counter and C900060008 increment simultaneously. Otherwise, if the channel could not be activated due to
receiving channel activation failure message, incorrect channel activation response message, T9103 timeout, channel instance being released or channel being released forcibly, this counter and
C900060009 increment simultaneously.
Measurement
Point
BSC activates SDCCH due to assignment (C900060008+C900060

009). The measurement point is A2 as shown in Figure 1627.
1613
FIGURE 1627 THE PROCESS OF IMMEDIATE ASSIGNMENT
Unit
Related Features
Times
SDCCH allocation attempts
for handover
Definition
1614
Number of SDCCH allocation attempts for handover
Description

from BTS), this counter and C901250011 increment simultaneously. Otherwise, if the channel could not be activated due to
receiving channel activation failure message, incorrect channel activation response message, T9103 timeout, channel instance being released or channel being released forcibly, this counter and
C901250012 increment simultaneously.
Usage
This counter records the number of SDCCH allocations attempts

for handover, including successful allocations (C901250011) and
unsuccessful allocations (C901250012).
Measurement
Point
BSC activates SDCCH due to handover (C901250011+C90125001

2). The measurement point is B2 as shown in Figure 1628and C2
FIGURE 1628
HANDOVER)
INTRA-CELL
Unit
Related Features
Times
1615
SDCCH allocation success
for handover
Definition
Number of SDCCH allocation success for handover
Description

from BTS), it means SDCCH allocation succeeds completely and
Usage
This counter records the number of SDCCH allocations success for

handover.
Measurement
Point
When BSC receives the CHL_ACT_ACK message from BTS due to

handover. The measurement point is B2 as shown in Figure 1630,
and C2 as shown in Figure 1631.
FIGURE 1630
HANDOVER)
1616
INTRA-CELL
Unit
Related Features
Times
SDCCH allocation failure for
handover
Definition
Number of SDCCH allocation failure for handover
Description

occupy SDCCH channel successfully, BSC sends the CHL_ACT message to BTS to activate this SDCCH channel. If the channel could
not be activated due to receiving channel activation failure message, incorrect channel activation response message, T9103 timeout, channel instance being released or channel being released
forcibly, this counter increments.
Usage
This counter records the number of SDCCH allocations failure for

handover.
Measurement
Point
BSC activates SDCCH for handover, but encounters the following

situation: receives channel activation failed message, channel activation response message is incorrect, T9103 is time-out, channel
instance is released, or channel is released forcibly. The measurement point is B2 as shown in Figure 1632 and C2 as shown in
Figure 1633.
1617
FIGURE 1632
HANDOVER)
INTRA-CELL
Unit
Related Features
Times
SDCCH handover failure
Definition
1618
Number of SDCCH handover attempts
Description
In the process of handover, when MS accesses successfully in

the new channel, BSC will receive assignment complete message
ASS_COM (intra-cell handover) or HO_COM (inter-cell handover).
If BSC receives successfully above message within assigned time,
which means handover succeeds. This counter and C901250017
increment simultaneously. If BSC receives HO_FAILURE message,
this counter and C901250018 increment simultaneously. Otherwise, handover fails and same time BSC has not received any failure message, this counter and C901250019 increment simultaneously.
Usage
This counter records the attempts number of MS accesses

SDCCH newly allocated in the process of handover, including
successful handover times (C901250017), failed handover times
(C901250018) with HO_FAILURE message and failed handover
times (C901250019) without HO_FAILURE message.
Measurement
Point
When BSC receives ASS_COM message (intra-cell handover),

HO_COM message (inter-cell handover), HO_FAILURE message or
HO_FAILURE abnormally, time-out message, channel instance is
released, or channel is released forcibly. The measurement point
is B3 as shown in Figure 1634and C3 as shown in Figure 1635.
FIGURE 1634
HANDOVER)
INTRA-CELL
1619
Unit
Related Features
Times
SDCCH handover success
Definition
1620
Number of SDCCH handover success
Description
In the process of handover, when MS accesses successfully in

the new channel, BSC will receive assignment complete message
ASS_COM (intra-cell handover) or HO_COM (inter-cell handover).
If BSC receives successfully above message within assigned time,
which means handover succeeds, this counter increments.
Usage
This counter records the number of MS accesses successfully SDCCH newly allocated in the process of handover.
Measurement
Point
BSC receives ASS_COM message (intra-cell handover) or HO_COM

message (inter-cell handover). The measurement point is B3 as
shown in Figure 1636and C3 as shown in Figure 1637.
FIGURE 1636
HANDOVER)
INTRA-CELL
Unit
Related Features
Times
1621
with Reconnection
Definition
Number of SDCCH handover failure with Reconnection
Description
In the process of handover, when BSC receives ASSIGN_FAIL message or HO_FAIL message, this counter increments.
Usage
This counter records the number of MS accesses unsuccessfully

SDCCH newly allocated in the process of handover and BSC receives handover failure message.
Measurement
Point
Unit
Related Features
BSC receives HO_FAILURE message.

Times
without Reconnection
Definition
Description
If handover fails and at same time BSC has not received any
HO_FAILURE message, this counter increments.
Usage
This counter records the number of MS accesses unsuccessfully

SDCCH newly allocated in the process of handover and BSC has
not received any HO_FAILURE message.
Measurement
Point
When BSC has not received any HO_FAILURE message, time-out

message, channel instance is released, or channel is released
forcibly.
Unit
Related Features
1622
Number of SDCCH handover failure without Reconnection
Times
C901250020 Number
of SDCCH assignment
attempts (MOC)
Description
After BSC responds to the channel request due to MOC and successfully allocates and activates SDCCH, BSC sends the immediate
assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame
to BTS via SDCCH. After BTS receives the frame, it sends the
EST_IND message to BSC.
If BSC receives the EST_IND message correctly within specified
time, it indicates that SDCCH assignment succeeds, this counter
and C901250021 accumulate simultaneously. Otherwise, if BSC
receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, this counter and
Usage
When the channel access is due to MOC, this counter is used to

find out the number of BSC's attempts of making MS use allocated
SDCCH by sending the IMM_ASS message to MS, including the
number of assignment successes (C901250021) and the number
of assignment failures (C901250022).
Measurement
Point
The counter counts when BSC receives the EST_IND message

or the assignment completion message, or T3101 is timeout
(C901250021+C901250022). The measurement point is A3, as
Unit
Times
1623
C901250021 Number
of successful SDCCH
assignments (MOC)
Description
time, it indicates that SDCCH assignment succeeds, and this
Usage
When the channel access is due to MOC, this counter is used to find
out the number of MS's successfully accessing the corresponding
SDCCH after BSC sends the IMM_ASS message. The measurement point is A3, as shown in Figure 1639.
FIGURE 1639 NUMBER
Measurement
Point
Unit
1624
OF SUCCESSFUL
SDCCH
ASSIGNMENTS
(MOC)
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message.
Times
unsuccessful SDCCH
assignments (MOC)
Description
If BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, and this counter accumulates.
Usage
When the channel access is due to MOC, this counter is used to find
out the number of MS's failing in accessing the allocated SDCCH
after BSC sends the IMM_ASS message.
Measurement
Point
The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as
FIGURE 1640 NUMBER
Unit
OF UNSUCCESSFUL
SDCCH
ASSIGNMENTS
(MOC)
Times
1625
C901250023 Number
of SDCCH assignment
attempts (MTC)
Description
After BSC responds to the channel request due to MTC and successfully allocates and activates SDCCH, BSC sends the immediate
Usage
When the channel access is due to MTC, this counter is used to

Measurement
Point

FIGURE 1641 NUMBER
Unit
1626
OF
SDCCH
ASSIGNMENT ATTEMPTS
Times
(MTC)
C901250024 Number
of successful SDCCH
assignments (MTC)
Description
Usage
When the channel access is due to MTC, this counter is used to find
FIGURE 1642 NUMBER
OF SUCCESSFUL
SDCCH
ASSIGNMENTS
(MTC)

Measurement
Point
Unit
Times
1627
unsuccessful SDCCH
assignments (MTC)
Description
Usage
When the channel access is due to MTC, this counter is used to find
Measurement
Point
FIGURE 1643 NUMBER
Unit
1628
OF UNSUCCESSFUL
Times
SDCCH
ASSIGNMENTS
(MTC)
SDCCH assignment attem
pts (call re-establishment)
Description
After BSC responds to the channel request due to call reestablishment and successfully allocates and activates SDCCH, BSC sends
the immediate assignment message IMM_ASS to MS to notify it
to use the channel. After MS receives the message, it sends the
SABM frame to BTS via SDCCH. After BTS receives the frame, it
sends the EST_IND message to BSC.
Usage
When the channel access is due to call reestablishment, this

counter is used to find out the number of BSC's attempts of making MS use allocated SDCCH by sending the IMM_ASS message to
MS, including the number of assignment successes (C901250027)
and the number of assignment failures (C901250028).
Measurement
Point

FIGURE 1644 NUMBER OF
RE-ESTABLISHMENT)
SDCCH
ASSIGNMENT ATTEMPTS
(CALL
1629
Unit
Times
C901250027 Number
of successful SDCCH
assignments (call
re-establishment)
Description
Usage

counter is used to find out the number of MS's successfully accessing the corresponding SDCCH after BSC sends the IMM_ASS
message. The measurement point is A3, as shown in Figure 1645.
FIGURE 1645 NUMBER OF SUCCESSFUL
RE-ESTABLISHMENT)
SDCCH
ASSIGNMENTS
1630
(CALL
Measurement
Point
Unit
Times
unsuccessful SDCCH
assignments (call
re-establishment)
Description
Usage

counter is used to find out the number of MS's failing in accessing
the allocated SDCCH after BSC sends the IMM_ASS message.
Measurement
Point
1631
FIGURE 1646 NUMBER OF UNSUCCESSFUL

RE-ESTABLISHMENT)
Unit
SDCCH
ASSIGNMENTS
(CALL
Times
C901250029 Number
of SDCCH assignment
attempts (emergency call)
Description
After BSC responds to the channel request due to emergency call

and successfully allocates and activates SDCCH, BSC sends the
immediate assignment message IMM_ASS to MS to notify it to use
the channel. After MS receives the message, it sends the SABM
frame to BTS via SDCCH. After BTS receives the frame, it sends
the EST_IND message to BSC.
Usage
When the channel access is due to emergency call, this counter

is used to find out the number of BSC's attempts of making MS
use allocated SDCCH by sending the IMM_ASS message to MS,
including the number of assignment successes (C901250030) and
the number of assignment failures (C901250031).
1632
Measurement
Point

FIGURE
CALL)
Unit
1647 NUMBER
OF
SDCCH
ASSIGNMENT ATTEMPTS
(EMERGENCY
Times
C901250030 Number
of successful SDCCH
assignments (emergency
call)
Description

Usage
When the channel access is due to emergency call, this counter is

used to find out the number of MS's successfully accessing the cor-
1633
responding SDCCH after BSC sends the IMM_ASS message. The

FIGURE 1648 NUMBER
CALL)
OF SUCCESSFUL
SDCCH
ASSIGNMENTS
(EMERGENCY

Measurement
Point
Unit
Times
unsuccessful SDCCH
assignments (emergency
call)
Description

1634
Usage
When the channel access is due to emergency call, this counter

is used to find out the number of MS's failing in accessing the
allocated SDCCH after BSC sends the IMM_ASS message.
Measurement
Point
FIGURE 1649 NUMBER
(EMERGENCY CALL)
Unit
OF UNSUCCESSFUL
SDCCH
ASSIGNMENTS
Times
C901250032 Number
of SDCCH assignment
attempts (LOC)
Description
After BSC responds to the channel request due to LOC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel.
After MS receives the message, it sends the SABM frame to BTS
via SDCCH. After BTS receives the frame, it sends the EST_IND
message to BSC.
receives the EST_IND message incorrectly or T3101 is time-
1635
out, it indicates that SDCCH assignment fails, this counter and

Usage
When the channel access is due to LOC, this counter is used to

Measurement
Point

FIGURE 1650 NUMBER
Unit
OF
SDCCH
ASSIGNMENT ATTEMPTS
(LOC)
Times
C901250033 Number
of successful SDCCH
assignments (LOC)
Description
1636
message to BSC.

Usage
When the channel access is due to LOC, this counter is used to find
FIGURE 1651 NUMBER
OF SUCCESSFUL
SDCCH
ASSIGNMENTS
(LOC)

Measurement
Point
Unit
Times
unsuccessful SDCCH
assignments (LOC)
Description
message to BSC.
1637
Usage
When the channel access is due to LOC, this counter is used to find
Measurement
Point
FIGURE 1652 NUMBER
Unit
OF UNSUCCESSFUL
SDCCH
ASSIGNMENTS
(LOC)
Times
C901250035 Number
of SDCCH assignment
attempts (other cause)
Description
1638
After BSC responds to the channel request due to causes beyond

what have been mentioned previously and successfully allocates
and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS
receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message
to BSC.

Usage
When the channel access is due to causes beyond what have been
mentioned previously, this counter is used to find out the number
of BSC's attempts of making MS use allocated SDCCH by sending
the IMM_ASS message to MS, including the number of assignment
successes (C901250036) and the number of assignment failures
(C901250037).
Measurement
Point

FIGURE 1653 NUMBER
Unit
OF
SDCCH
ASSIGNMENT ATTEMPTS
(OTHER
CAUSE)
Times
C901250036 Number
of successful SDCCH
assignments (other cause)
Description

1639
to BSC.
Usage
of MS's successfully accessing the corresponding SDCCH after BSC
sends the IMM_ASS message. The measurement point is A3, as
FIGURE
CAUSE)
1654 NUMBER
OF SUCCESSFUL
SDCCH
ASSIGNMENTS
(OTHER

Measurement
Point
Unit
Times
unsuccessful SDCCH
assignments (other cause)
Description
1640

to BSC.
Usage
of MS's failing in accessing the allocated SDCCH after BSC sends
the IMM_ASS message.
Measurement
Point
FIGURE 1655 NUMBER
CAUSE)
Unit
OF UNSUCCESSFUL
SDCCH
ASSIGNMENTS
(OTHER
Times
C901250038 Count of USSD

attempts to connect
Description
This counter counts the number of attempts of connecting USSD

service.
1641
Unit
Statistics Object
Times
Cell
C901250039 Average
dialoge time of USSD
services
Description
This counter counts the average conversation time of USSD service.

Unit
Statistics Object
Second
Cell
C901250040 Dialog counts

of USSD services
Description
This counter counts the number of conversations of USSD service.

Unit
Statistics Object
1642
Times
Cell
Chapter
32
TCH/F Measurement
Table of Contents
Overview...................................................................... 1647
C901260002 Number of signaling TCH/F seizure success for
assignment................................................................... 1650
C901260005 Number of signaling TCH/F seizure success for
handover...................................................................... 1651
C901260007 Number of signaling TCH/F allocation attempts
for assignment .............................................................. 1653
C901260010 Number of signaling TCH/F allocation attempts
for handover ................................................................. 1654
C901260011 Number of signaling TCH/F allocation success for
handover...................................................................... 1657
C901260013 Number of signaling TCH/F assignment attempts
for assignment .............................................................. 1659
C901260016 Number of signaling TCH/F handover attempt .......................................................................... 1660
C901260017 Number of signaling TCH/F handover success............................................................................. 1663
C901260018 Number of signaling TCH/F handover failure with
reconnection ................................................................. 1665
without reconnection...................................................... 1667
C901260021 Number of voice TCH/F seizure success for assignment...................................................................... 1668
C901260024 Number of voice TCH/F seizure success for handover........................................................................... 1669
C901260026 Number of TCH/F allocation attempts for assignment (speech version 1)................................................. 1672
C901260032 Number of TCH/F allocation attempts by BSC for
handover (speech version 1) ........................................... 1673
C901260033 Number of TCH/F allocation success by BSC for
C901260038 Number of TCH/F allocation attempts for assignment (speech version 2)................................................. 1678
assignment (speech version 3) ........................................ 1685
C901260062 Number of voice TCH/F assignment attempts by
BSC ............................................................................. 1691
1643
C901260065 Number of voice TCH/F handover attempts ......................................................................... 1692

C901260067 Number of Voice TCH/F handover failure......... 1695
C901260068 Number of Voice TCH/F handover failure messages do not received by BSC ......................................... 1697
C901260070 Number of data TCH/F seizure success for assignment...................................................................... 1698
C901260073 Number of data TCH/F seizure success for handover........................................................................... 1699
C901260075 Number of data TCH/F allocation attempts for
assignment................................................................... 1702
C901260081 Number of data TCH/F allocation attempts by
BSC for handover .......................................................... 1703
handover...................................................................... 1706
C901260087 Number of data TCH/F assignment attempts ......................................................................... 1708
C901260090 Number of data TCH/F handover attempts ......................................................................... 1709
C901260092 Number of data TCH/F handover failure ......... 1712
C901260093 Number of data TCH/F handover failure messages do not received by BSC ......................................... 1714
assignment due to TIPB connection failure (Speech version
1)................................................................................ 1715
C901260095 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 1) ......................................................................... 1716
handover due to TIPB connection failure (Speech version
1)................................................................................ 1717
C901260097 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version
1)................................................................................ 1718
2)................................................................................ 1719
2)................................................................................ 1721
2)................................................................................ 1723
3)................................................................................ 1724
3)................................................................................ 1726
3)................................................................................ 1728
1644
Chapter 32 TCH/F Measurement
C901260106 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version
1)................................................................................ 1729
request UDP port failure for assignment (speech version
1)................................................................................ 1730
C901260108 Number of TCH/F allocation failure due to AIPB
connection failure for assignment (speech version 1).......... 1731
request AIPB resource failure for handover (speech version
1)................................................................................ 1732
C901260110 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 1)......... 1733
connection failure for handover (speech version 1)............. 1734
2)................................................................................ 1735
2)................................................................................ 1736
2)................................................................................ 1738
3)................................................................................ 1741
3)................................................................................ 1742
3)................................................................................ 1744
C901260124 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (data).............. 1747
C901260125 Number of TCH/F allocation failure due to request UDP port failure for assignment (data)..................... 1748
connection failure for assignment (data) ........................... 1748
C901260127 Number of TCH/F allocation failure due to request AIPB resource failure for handover (data)................. 1749
C901260128 Number of TCH/F allocation failure due to request UDP port failure for handover (data)........................ 1750
connection failure for handover (data).............................. 1751
C901260130 Number of assign TCH/F release by forced handover to forced handover source...................................... 1752
1645
C901260131 Number of assign TCH/F release by forced handover to queuing user .................................................... 1752
C901260132 Number of restore TCH/F release by forced handover to DBS ................................................................ 1753
C901260133 Number of assign TCHF release by forced release
to forced release source ................................................. 1753
C901260134 Number of assign TCH/F release by forced release to queuing user..................................................... 1754
C901260135 Number of restore TCH/F release by forced release to DBS ................................................................. 1754
assignment (cause:Abis) ................................................ 1755
handover (cause:Abis) ................................................... 1756
C901260138 Number of voice TCH/F seizure failure for assignment (cause:Abis) ................................................... 1756
C901260139 Number of voice TCH/F seizure failure for handover (cause:Abis ) ....................................................... 1757
C901260140 Number of data TCH/F seizure failure for assignment (cause:Abis) ......................................................... 1757
C901260141 Number of data TCH/F seizure failure for handover (cause:Abis) ........................................................ 1758
assignment (cause:radio resource) .................................. 1758
handover (cause:radio resource) ..................................... 1759
C901260144 Number of voice TCH/F seizure failure for assignment (cause:radio resource) ..................................... 1759
C901260145 Number of voice TCH/F seizure failure for handover (cause:radio resource) .......................................... 1760
C901260146 Number of data TCH/F seizure failure for assignment (cause:radio resource) ........................................... 1760
C901260147 Number of data TCH/F seizure failure for handover (cause:radio resource) .......................................... 1761
C901260148 Number of FR_V1 assignment attempts ......... 1761
C901260149 Number of FR_V1 assignment success ........... 1762
C901260154 Number of FR_V1 handover.......................... 1764
C901260155 Number of FR_V1 handover success .............. 1764
C901260185 Resourse releasing of ordinary users due to being grabbed (TCH/F) ...................................................... 1767
C901260186 Handover of ordinary users due to be grabbed
(TCH/F)........................................................................ 1768
(TCH/F)........................................................................ 1769
C901260188 Number of Successful Channel seize of priority
users (TCH/F) ............................................................... 1771
C901260189 Number of Successful grabbing channel of priority users (TCH/F) ........................................................ 1772
1646
Overview
In GSM BSC signaling system, allocation and usage of TCH/F channel mainly exist in assignment and handover flow, where assignment flow includes immediate assignment and common assignment; handover flow includes internal and external handover.
For the measurement positions of TCH/F counter in immediate assignment flow, see Figure 1656.
FIGURE 1656 IMMEDIATE
ASSIGNMENT FLOW
During internal and external TC, for the measurement positions of

TCH/F counter in common assignment flow, see Figure 1657and
Figure 1658.
FIGURE 1657 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1647
FIGURE 1658 COMMON
ASSIGNMENT FLOW
(EXTERNAL TC)
During internal and external TC, for the measurement positions of

TCH/F counter in internal handover flow (like intra-cell handover),
see Figure 1659and Figure 1660.
FIGURE 1659 INTERNAL
(INTERNAL TC)
1648
HANDOVER
(LIKE
INTRA-CELL HANDOVER) FLOW
FIGURE 1660 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND

CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
During internal and external TC, for the measurement positions

of TCH/F counter in external handover flow, see Figure 1661and
Figure 1662
FIGURE 1661 EXTERNAL
HANDOVER FLOW
(INTERNAL TC)
1649
HANDOVER FLOW
(EXTERNAL TC)
Definition
Description
Number of signaling TCH/F seizure success for assignment

This counter counts the number of signaling TCH/F seizure success
during assignment of signaling channel.
After BSC receives channel request message, it will try to allocate
channel for this request. If allocation and seizure succeed, this
Measurement
Point
BSC successfully applies for channel (due to assignment, used for

signaling channel) and does successful assignment. The measurement point is A1, as shown in Figure 1663
1650
ASSIGNMENT FLOW
Unit
Related Features
Times
success for handover
Definition
Description
Number of signaling TCH/F seizure success for handover

This counter counts the number of signaling TCH/F seizure success
during handover of signaling channel.
counter accumulates. If no channel is returned after application
but queuing or force release can be conducted, it will enter into
the state to wait for resource, this counter accumulates when corresponding resource occurs.
Measurement
Point
BSC successfully applies for channel (due to handover, used for

signaling channel) and does successful seizure, or BSC receives
internal waiting resource effective message. The measurement
points are C1 and D1, as shown in Figure 1664, Figure 1665, Figure
1666, and Figure 1667.
(INTERNAL TC)
HANDOVER
(LIKE
1651

1652
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
ZGO-03-02-011 Channel Repacking
Definition
Description
Number of signaling TCH/F allocation attempts for assignment

This counter counts the number of signaling TCH/F allocation attempts when assigning signaling channel, including the number of
allocation success (C900060014) and failure (C900060014).
After BSC responds channel request message allocation and
successfully seizes TCH/F channel, BSC sends channel activation
message CHL_ACT to activate this TCH/F. if activation success,
CHL_ACT_ACK message sent by BTS will be received, indicating
TCH/F allocation success, this counter and C900060014 accumulate simultaneously; reversely, if channel activation failure due to
receive channel activation failure message, incorrect channel activation response message, timer T9103 timeout, channel instance
released, channel force-released, this counter and C900060015
accumulate simultaneously.
Measurement
Point
After BSC activates TCH/F (due to assignment, used for signaling

channel), this counter accumulates when CHL_ACT_ACK message
sent by BTS is received correctly, channel activation failure message is received, channel activation response message is not correct, timer T9103 times out, channel instance is released, or channel is forcibly released. (C900060014+C900060015) The measurement point is A2, as shown in Figure 1668.
1653
Unit
Related Features
ASSIGNMENT FLOW
Times
Definition
Description
Number of signaling TCH/F allocation attempts for handover

This counter counts the number of signaling TCH/F allocation attempts during handover of signaling channel, including the number
of allocation success (C901260011) and failure (C900060016).
After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation success,
TCH/F allocation success, this counter and C901260011 accumulate simultaneously; reversely, if channel activation failure due to
receive channel activation failure message, incorrect channel activation response message, timer T9103 timeout, channel instance
released, channel force-released, this counter and C900060016
Measurement
Point
1654
After BSC activates TCH/F (due to handover, used for signaling

channel), this counter accumulates when CHL_ACT_ACK message
sent by BTS is received correctly, channel activation failure message is received, channel activation response message is not correct, timer T9103 times out, channel instance is released, or channel is forcibly released. (C901260011+C900060016) The measurement points are C3 and D3, as shown in Figure 1669, Figure
1670,Figure 1671 and Figure 1672.

(INTERNAL TC)
HANDOVER
(LIKE

1655
Unit
Related Features
1656
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
Definition
Description
Number of signaling TCH/F allocation success for handover

This counter counts the number of signaling TCH/F allocation success during handover of signaling channel.
After BSC responds channel request message allocation and successfully seizes channel, BSC sends channel activation message
CHL_ACT to BTS to activate this TCH/F. if activation success,
TCH/F allocation success, this counter accumulates.
Measurement
Point
This counter accumulates when CHL_ACT_ACK correctly receives

CHL_ACT_ACK message sent by BTS due to handover and used
for signaling channel. The measurement points are C3 and D3, as
shown in Figure 1673, Figure 1674, Figure 1675, and Figure 1676.
(INTERNAL TC)
HANDOVER
(LIKE
1657

1658
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
Definition
Description
Number of signaling TCH/F assignment attempts for assignment

This counter counts the number of signaling TCH/F assignment
success during assignment of TCH/F channel.
CHL_ACT to BTS to activate this TCH/F. For immediate assignment, after activation success, BTS receives MS access and sends
EST_IND message to BSC, this counter accumulates while BSC
correctly receives this message; if MS access cant be received
within specified duration, this assignment is failed.
Measurement
Point
For immediate assignment, this counter accumulates when BSC

correctly receives EST_IND message or T3101 times out (that is,
MS access notice cant be received within specified duration). The
1659
Unit
Related Features
ASSIGNMENT FLOW
Times
signaling TCH/F handover
attempt
Definition
Description
Number of signaling TCH/F handover attempt

This counter counts the number of signaling TCH/F handover
attempts, including the number of TCH/F handover success
(C901260017), the number of TCH/F handover failure with return
(C901260018), and the number of TCH/F handover failure without
return (C901260019).
This counter and C901260017 accumulate when BSC detects the
handover success message sent by MS on reallocated TCH/F channel; this counter and C901260018 accumulate when handover failure message is received; this counter and C901260019 accumulate when it receives the message of exception, released instance,
force-released instance, or timer timeout.
For intra-cell handover, handover success symbolic message is
ASS_COM; for inter-cell handover and external handover, handover success symbolic message is HO_COM. For intra-cell and inter-cell handover, this counter accumulates on the basis of source
instance; for external handover, this counter accumulates on target instance because source instance doesnt at this BSC side.
Measurement
Point
1660
This counter accumulates when BSC detects handover success

message, ASS_COM/HO_COM, sent from reallocated TCH/F channel, or receives failure message, ASS_FAIL/HO_FAIL,, or receives
message of exception, released instance, force-released instance,
or timer timeout. The measurement points are C4 and D4, as

(INTERNAL TC)
HANDOVER
(LIKE

1661
Unit
Related Features
1662
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
success
Definition
Description
Number of signaling TCH/F handover success

his counter counts the number of signaling TCH/F handover success during handover of signaling channel.
This counter accumulates when handover success message sent
from MS is detected on reallocated TCH/F channel.
For intra-cell handover, handover success symbolic message is
ASS_COM; for inter-cell handover and external handover, handover success symbolic message is HO_COM. For intra-cell and inter-cell handover, this counter accumulates on the basis of source
instance; for external handover, this counter accumulates on target instance because source instance doesnt at this BSC side.
Measurement
Point
BSC receives ASS_COM or HO_COM message. The measurement

points are C4 and D4, as shown in Figure 1682, Figure 1683, Figure
1684, and Figure 1685.
(INTERNAL TC)
HANDOVER
(LIKE
1663

1664
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
failure with reconnection
Definition
Description
Number of signaling TCH/F handover failure with reconnection

This counter counts the number of signaling TCH/F handover failure during handover of signaling channel.
This counter accumulates when MS conducts handover on TCH/F
channel, returns to previous channel after failed to access to new
channel, receives assignment failure or handover failure from previous channel.
Measurement
Point
BSC receives ASS_FAIL or HO_FAIL message. The measurement

points are C4 and D4, as shown in Figure 1686, Figure 1687.
1665
Unit
Related Features
1666

FAILURE FLOW 1
HANDOVER
(INTERNAL TC
HANDOVER FAILURE FLOW
INTRA-CELL HANDOVER)
(INTERNAL TC)
Times
failure without reconnection
Definition
Number of signaling TCH/F handover failure without reconnection
Description
This counter counts the number of signaling TCH/F handover failure without reconnection during handover of signaling channel.
This counter accumulates when MS handover fails or it cant return to previous channel after BSC sends assignment command or
handover command to MS.
Measurement
Point
Unit
Related Features
This counter accumulates when BSC receives messages of exception, released instance, force-released instance, or timer timeout.
The measurement point is C4, as shown in Figure 1688, Figure
1689.
FIGURE 1688 INTERNAL HANDOVER
FAILURE FLOW 2
(INTERNAL TC

FAILURE FLOW 3
(INTERNAL TC
Times
1667
C901260021 Number
Definition
Description
Number of voice TCH/F seizure success for assignment

This counter counts the number of voice TCH/F seizure success
during assignment of signaling channel.
Measurement
Point

voice channel) and does successful seizure, or BSC receives internal waiting resource effective message. The measurement point
is B1, as shown in Figure 1690, Figure 1691.
FIGURE 1690 COMMON
1668
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1691 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
C901260024 Number
Definition
Description
Number of voice TCH/F seizure success for handover

This counter counts the number of voice TCH/F seizure success
Measurement
Point

voice channel) and does successful seizure, or BSC receives internal waiting resource effective message. The measurement points
are C1 and D1, as shown in Figure 1692, Figure 1693, Figure 1694,
and Figure 1695.
1669

(INTERNAL TC)
HANDOVER
(LIKE

1670
Unit
Related Features
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
1671
TCH/F allocation attempts
version 1)
Definition
Number of TCH/F allocation attempts for assignment (speech version 1)
Description
This counter counts the number of TCH/F allocation attempts

when assigning voice channel (for speech version 1), including
the number of allocation success (C900060023) and failure
(C900060024+C900060138+ C900060139+ C900060140).
After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC firstly finishes connection,
then sends channel activation message CHL_ACT to BTS to activate
this TCH/F. if activation succeeds, BSC will receive CHL_ACT_ACK
message sent by BTS, indicating TCH/F allocation success, this
counter and C900060023 accumulate simultaneously; reversely,
if failed, this counter and the counter that corresponds to failure
will accumulate simultaneously.
Measurement
Point
This counter accumulates when allocation succeeds or fails (due

to assignment, used for voice channel, using speech version 1).
The measurement points are B2 and B3, as shown in Figure 1696,
Figure 1697.
FIGURE 1696 COMMON
1672
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1697 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
by BSC for handover
(speech version 1)
Definition
Number of TCH/F allocation attempts by BSC for handover (speech

version 1)
Description

during handover of voice channel (for speech version 1), including the number of allocation success (C901260033) and failure
(C900060156+C900060157+C900060158+C900060159).
Measurement
Point

to handover, used for voice channel, using speech version 1). The
measurement points are C3 and D3, as shown in Figure 1698,
Figure 1699, Figure 1700, and Figure 1701.
1673

(INTERNAL TC)
HANDOVER
(LIKE

1674
Unit
Related Features
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
1675
TCH/F allocation success by
BSC for handover (speech
version 1)
Definition
Number of TCH/F allocation success by BSC for handover(speech

version 1)
Description
This counter counts the number of TCH/F allocation success during

handover of voice channel (for speech version 1).
Measurement
Point
This counter accumulates when BSC correctly receives

for voice channel (for speech version 1). The measurement
points are C3 and D3, as shown in Figure 1702, Figure 1703,
Figure 1704, and Figure 1705.
(INTERNAL TC)
1676
HANDOVER
(LIKE

HANDOVER FLOW
(INTERNAL TC)
1677
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
version 2)
Definition
Description

(C900060141+C900060142+C900060143+C900060144).
Measurement
Point
1678


Figure 1707.
Unit
Related Features
FIGURE 1706 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1707 COMMON
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
1679
by BSC for handover
(speech version 2)
Definition

version 2)
Description

(C900060160+C900060161+C900060162+C900060163).
Measurement
Point

(INTERNAL TC)
1680
HANDOVER
(LIKE

HANDOVER FLOW
(INTERNAL TC)
1681
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
version 2)
Definition
Number of TCH/F allocation success by BSC for handover (speech

version 2)
Description

Measurement
Point
1682


(INTERNAL TC)
HANDOVER
(LIKE

1683
Unit
Related Features
1684
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
by BSC for assignment
(speech version 3)
Definition
Description

(C900060027+C900060145+C900060146+C900060147).
Measurement
Point

Figure 1717.
FIGURE 1716 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1685
FIGURE 1717 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
by BSC for handover
(speech version 3)
Definition

version 3)
Description

(C900060164+C900060165+C900060166+C900060167).
Measurement
Point
1686


(INTERNAL TC)
HANDOVER
(LIKE

1687
Unit
Related Features
1688
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
version 3)
Definition
Number of TCH/F allocation success by BSC for handover (speech

version 3)
Description

Measurement
Point

(INTERNAL TC)
HANDOVER
(LIKE
1689

1690
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
attempts by BSC
Definition
Description
Number of voice TCH/F assignment attempts by BSC

This counter counts the number of voice TCH/F assignment attempts when assigning TCH/F channel as voice channel, including the number of assignment success (C900060028) and failure
(C900060029).
CHL_ACT to BTS to activate this TCH/F. For the assignment form
port A, this counter and C900060028 accumulate simultaneously
after receiving assignment success message. This counter and
C900060029 accumulate simultaneously if MS access notice cant
be received within specified duration, that is, this assignment
failed at this time.
Measurement
Point
For the assignment from port A, BSC receives the messages of

assignment success, assignment failure, timer timeout, exception,
released instance, or force-released instance. The measurement
point is B5, as shown in Figure 1726, Figure 1727.
1691
Unit
Related Features
FIGURE 1726 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1727 COMMON
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
voice TCH/F handover
attempts
Definition
Description
1692
Number of voice TCH/F handover attempts

This counter counts the number of voice TCH/F handover
attempts, including the number of TCH/F handover success
(C900060168), the number of TCH/F handover failure with return
(C901260067), and the number of TCH/F handover failure without

return (C901260068).
During handover, after MS is successfully accessed from new
channel, BSC will receive assignment completion message
ASS_COM (intra-cell handover) or HO_COM message (inter-cell
handover and external handover).
If BSC receives above mentioned messages within specified duration, it indicates handover success, this counter and C900060168
accumulate simultaneously; if BSC receives HO_FAILURE, it is
handover failure with response, this counter and C901260067
accumulate; if handover is failed and BSC cant receive HO_FAILURE, it is handover failure without response, this counter and
For intra-cell and inter-cell handover, this counter accumulates on
the basis of source instance; for external handover, this counter
accumulates on target instance because source instance doesnt
at this BSC side.
Measurement
Point
This counter accumulates when BSC receives ASS_COM/HO_COM

message, ASS_FAIL/HO_FAIL message, or messages of exception,
released instance, force-released instance, or timer timeout. The
(INTERNAL TC)
HANDOVER
(LIKE
1693

1694
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
failure
Definition
Description
Number of Voice TCH/F handover failure

This counter counts the number of voice TCH/F handover failure
during handover of voice channel.
channel, fails to access to new channel and returns to previous
Measurement
Point

1695
Unit
Related Features
1696

FAILURE FLOW 1
HANDOVER
(INTERNAL TC
(INTERNAL TC)
Times
failure messages do not
received by BSC
Definition
Number of Voice TCH/F handover failure messages do not received

by BSC
Description
This counter counts the number of voice TCH/F handover failure

without response during handover of voice channel.
This counter accumulates when handover fails or it cant return to
source channel after BSC sends assignment / handover command
to MS.
Measurement
Point
This counter accumulates when BSC receives messages of exception, timer timeout, released instance, or force-released instance.
The measurement points are C4 and D4, as shown in Figure 1734,
Figure 1735.
FAILURE FLOW 2
(INTERNAL TC

FAILURE FLOW 3
(INTERNAL TC
1697
Unit
Related Features
Times
data TCH/F seizure success
for assignment
Definition
Description
Number of data TCH/F seizure success for assignment

This counter counts the number of data TCH/F seizure success during assignment of signaling channel.
Measurement
Point

data channel) and does successful seizure, or BSC receives internal
waiting resource effective message. The measurement point is B1,
as shown in Figure 1736, Figure 1737.
FIGURE 1736 COMMON
1698
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1737 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
data TCH/F seizure success
for handover
Definition
Description
Number of data TCH/F seizure success for handover

This counter counts the number of data TCH/F seizure success during handover of signaling channel.
Measurement
Point

data channel) and does successful seizure, or BSC receives internal
waiting resource effective message. The measurement points are
C1 and D1, as shown in Figure 1738, Figure 1739, Figure 1740,
and Figure 1741.
1699

(INTERNAL TC)
HANDOVER
(LIKE

1700
Unit
Related Features
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
1701

for assignment
Definition
Number of data TCH/F allocation attempts for assignment
Description
This counter counts the number of data TCH/F allocation

attempts when assigning signaling channel, including the
number of allocation success (C900060034) and failure
(C900060035+C900060148+C900060149+C900060150).
Usage
Measurement
Point

to assignment, used for data channel). The measurement points
are B2 and B3, as shown in Figure 1742, Figure 1743.
FIGURE 1742 COMMON
1702
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1743 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times

by BSC for handover
Definition
Description
Number of data TCH/F allocation attempts by BSC for handover

This counter counts the number of data TCH/F allocation
attempts during handover of data channel, including the
number of allocation success (C901260082) and failure
(C900060169+C900060170+C900060171+C900060172).
Measurement
Point

to handover, used for data channel). The measurement points are
C3 and D3, as shown in Figure 1744, Figure 1745, Figure 1746,
and Figure 1747.
1703

(INTERNAL TC)
HANDOVER
(LIKE

1704
Unit
Related Features
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
1705

TCH/F allocation success for
handover
Definition
Description
Number of data TCH/F allocation success for handover

This counter counts the number of data TCH/F allocation success
Measurement
Point
This counter accumulates when CHL_ACT_ACK correctly receives

CHL_ACT_ACK message sent by BTS due to handover and used for
data channel. The measurement points are C3 and D3, as shown
in Figure 1748, Figure 1749, Figure 1750, and Figure 1751.
(INTERNAL TC)
1706
HANDOVER
(LIKE

HANDOVER FLOW
(INTERNAL TC)
1707
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times

Definition
Description
Number of data TCH/F assignment attempts

This counter counts the number of voice TCH/F assignment attempts when assigning TCH/F channel as data channel, including the number of assignment success (C900060036) and failure
(C900060037).
CHL_ACT to BTS to activate this TCH/F. For the assignment form
port A, this counter and C900060036 accumulate simultaneously
after receiving assignment success message. This counter and
C900060037 accumulate simultaneously if MS access notice cant
be received within specified duration, that is, this assignment
failed at this time.
Measurement
Point
1708
For the assignment from port A, BSC receives the messages of

assignment success, assignment failure, timer timeout, exception,
released instance, or force-released instance. The measurement
point is B5, as shown in Figure 1752, Figure 1753.
Unit
Related Features
FIGURE 1752 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1753 COMMON
ASSIGNMENT FLOW
(EXTERNAL TC)
Times

Definition
Description
Number of data TCH/F handover attempts

This counter counts the number of data TCH/F handover attempts,
including the number of TCH/F handover success (C901260091),
TCH/F response handover failure (C901260092), and TCH/F response-less handover failure (C901260093).
1709
During handover, after MS is successfully accessed from new

channel, BSC will receive assignment completion message
ASS_COM (intra-cell handover) or HO_COM message (inter-cell
handover and external handover).
If BSC receives above mentioned messages within specified duration, it indicates handover success, this counter and C901260091
accumulate simultaneously; if BSC receives HO_FAILURE, it is
handover failure with response, this counter and C901260092
accumulate; if handover is failed and BSC cant receive HO_FAILURE, it is handover failure without response, this counter and
For intra-cell and inter-cell handover, this counter accumulates on
the basis of source instance; for external handover, this counter
accumulates on target instance because source instance doesnt
at this BSC side.
Measurement
Point
This counter accumulates when BSC receives ASS_COM/HO_COM

message, ASS_FAIL/HO_FAIL message, or messages of exception,
released instance, force-released instance, or timer timeout. The
(INTERNAL TC)
1710
HANDOVER
(LIKE

HANDOVER FLOW
(INTERNAL TC)
1711
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
data TCH/F handover failure
Definition
Description
Number of data TCH/F handover failure

his counter counts the number of data TCH/F handover failure during handover of data channel.
channel, fails to access to new channel and returns to previous
Measurement
Point
1712


FAILURE FLOW 1
Unit
Related Features
(INTERNAL TC
(INTERNAL TC)
Times
1713
data TCH/F handover failure
messages do not received
by BSC
Definition
Number of data TCH/F handover failure messages do not received

by BSC
Description
This counter counts the number of data TCH/F handover failure

without response during handover of data channel.
This counter accumulates when handover fails or it cant return to
source channel after BSC sends assignment / handover command
to MS.
Measurement
Point
1714
This counter accumulates when BSC receives messages of exception, released instance, force-released instance, or timer timeout.
The measurement point is C4, as shown in Figure 1760and Figure
1761.
FAILURE FLOW 2
HANDOVER
(INTERNAL TC

FAILURE FLOW 3
HANDOVER
(INTERNAL TC
Unit
Related Features
Times
for assignment due to TIPB
connection failure (Speech
version 1)
Definition
Number of data TCH/F allocation failure for assignment due to TIPB

connection failure (Speech version 1)
Description
This counter counts the number of data TCH/F allocation failure

for assignment due to TIPB connection failure (speech version 1)
when assigning voice channel.
After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC sends TIU connection requests
to TIPB. This counter accumulates when it receives the messages
of TIU connection failure, incorrect TIU connection response message, or timer timeout.
Measurement
Point
BSC uses TCH/F due to assignment; this counter accumulates

when it receives connection failure message, incorrect connection
response message, or timer timeout during TIU connection. The
FIGURE 1762 GENERAL ASSIGNMENT FAILURE FLOW 1 (EXTERNAL TC)
Unit
Related Features
Times
1715
for assignment due to
Resource request to iTC
failure (Speech version 1)
Definition
Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 1)
Description
This counter counts the number of data TCH/F allocation failure for
assignment due to resource request to iTC failure (speech version
1) when assigning voice channel.
After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC requests resource from iTC.
If application of iTC resource fails due to receive the messages
of unavailable iTC resource, incorrect response message, or timer
timeout, this leads to TCH/F assignment failure, and this counter
accumulates.
Measurement
Point

when it receives the messages of unavailable iTC, incorrect response message, or timer timeout during iTC resource application.
Unit
Related Features
1716
Times
for handover due to TIPB
version 1)
Definition
Number of data TCH/F allocation failure for handover due to TIPB

Description
handover due to TIPB connection failure (speech version 1) during
handover.
Measurement
Point

when it receives messages of connection failure, incorrect connection response, or timer timeout during TIU connection. The
measurement points are C2 and D2, as shown in Figure 1764and
Figure 1765.
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER,

AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 1
1717
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
data TCH/F allocation
failure for handover due to
Definition
Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 1)
Description
handover due to resource request to iTC failure (speech version 1)
After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC requests TC resource after
determining channel types are changed. If application of iTC resource fails due to receive the messages of unavailable iTC resource, incorrect response, or timer timeout, this leads to TCH/F
assignment failure, and this counter accumulates.
Measurement
Point
1718
BSC uses TCH/F due to handover; this counter accumulates when

it receives the messages of unavailable iTC, incorrect response, or
timer timeout during iTC resource application. The measurement
points are C1 and D1, as shown in Figure 1766and Figure 1767.

Unit
Related Features
2 (EXTERNAL TC)
Times
version 2)
Definition

Description

1719
Measurement
Point

Unit
Related Features
Times
Definition
Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 2)
Description
accumulates.
1720
Measurement
Point

when it receives the messages of unavailable iTC, incorrect response message, or timer timeout during iTC resource application.
Unit
Related Features
Times
version 2)
Definition

Description
handover.
Measurement
Point

Figure 1771.
1721

Unit
Related Features
1722
HANDOVER FLOW
(EXTERNAL TC)
Times
Definition
Description
Measurement
Point

it receives the messages of unavailable iTC resource, incorrect response message, or timer timeout during iTC resource application. The measurement points are C1 and D1, as shown in Figure
1772and Figure 1773.

1723
Unit
Related Features
2 (EXTERNAL TC)
Times
version 3)
Definition

Description

Measurement
Point
1724

Unit
Related Features
Times
Definition
Number of data TCH/F allocation failure for assignment due to resource request to iTC failure (Speech version 3)
Description
accumulates.
Measurement
Point

when it receives the messages of unavailable iTC resource,
incorrect response message, or timer timeout during iTC resource
application. The measurement point is B1, as shown in Figure
1775.
1725
Unit
Related Features
Times
version 3)
Definition

Description
handover.
Measurement
Point
1726

Figure 1777.

Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
1727
Definition
Description
Measurement
Point

it receives the messages of unavailable iTC resource, incorrect response message, or timer timeout during iTC resource application. The measurement points are C1 and D1, as shown in Figure

1728
Unit
Related Features
2 (EXTERNAL TC)
Times
to request AIPB resource
(speech version 1)
Definition
Number of TCH/F allocation failure due to request AIPB resource

failure for assignment (speech version 1)
Description
This counter counts the number of TCH/F allocation failure due to

request AIPB resource failure for assignment.
This counter increments while BSC receives assignment requests
(speech version 1) to apply for AIPB board resource from database, failed request (including database return failure or no AIPB
board resource) indicates TCH/F allocation failure.
Usage
This counter is used to find out the frequency of TCH/F allocation

failure due to request AIPB resource failure for assignment.
Measurement
Point
This counter increments while BSC correctly receives database return failure or no AIPB board resource, and the reason to apply
for channel is assignment and purpose is voice channel. The measurement point is A as shown in Figure 1780.
1729
FIGURE 1780 REQUEST RESOURCE FAILURE
Unit
Related Features
Times
ZGO-05-04-003 A over IP
to request UDP port failure
version 1)
Definition
Number of TCH/F allocation failure due to request UDP port failure

for assignment (speech version 1)
Description

due to UDP port failure during assigning voice channel.
(speech version 1), access request is sent to access module, if access module returns access failure due to UDP port request failure.
1730
Usage

failure due to request UDP port failure.
Measurement
Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and
the reason is request UDP port failure for assignment. The measurement point is A as shown in Figure 1781.
FIGURE 1781 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
to AIPB connection failure
version 1)
Definition
Number of TCH/F allocation failure due to AIPB connection failure

Description

Usage

failure due to AIPB access failure.
Measurement
Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the
reason is AIPB access failure) or TwaitConn timer timeout for assignment. The measurement point is A as shown in Figure 1782.
FIGURE 1782 CHANNEL
Unit
ALLOCATION FAILURE
Times
1731
Related Features
version 1)
Definition

failure for handover (speech version 1)
Description

When BSC receives EV_RANUMC_RADIO_APPLY message (speech
version 1), the reason to request channel is handover, to request
AIPB resource from database. This counter increments if failed
to request AIPB (including database returning failure or no AIPB
resource), indicating TCH/F allocation failure.
Usage

Measurement
Point
This counter increments while BSC correctly receives database return failure or no AIPB board resource, and the reason to apply for
channel is handover and purpose is voice channel. The measurement point is A as shown in Figure 1783.
Unit
Related Features
1732
Times
due to request UDP port
version 1)
Definition

for handover (speech version 1)
Description

due to UDP port failure during handover.
access request for access module. This counter increments while
access module returns failure and the reason is failed to request
UDP port.
Usage

Measurement
Point
the reason is request UDP port failure for handover. The measurement point is A as shown in Figure 1784.
FIGURE 1784 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
1733
to AIPB connection failure for
handover (speech version 1)
Definition

Description

due to AIPB access failure during handover.
access module returns failure and the reason is failed to access
AIPB.
Usage

Measurement
Point
reason is AIPB access failure) or TwaitConn timer timeout for handover. The measurement point is A as shown in Figure 1785.
FIGURE 1785 CHANNEL
Unit
Related Features
1734
ALLOCATION FAILURE
Times
(speech version 2)
Definition

Description

Usage

Measurement
Point
Unit
Related Features
Times
1735
version 2)
Definition

Description

Usage

Measurement
Point
FIGURE 1787 CHANNEL
Unit
Related Features
1736
ALLOCATION FAILURE
Times
version 2)
Definition

Description

Usage

Measurement
Point
FIGURE 1788 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
1737
version 2)
Definition

Description

Usage

Measurement
Point
Unit
Related Features
1738
Times
version 2)
Definition

Description

This counter increments while BSC receives EV_RANUMC_RADIO_APPLY message (speech version 2) to request channel due
to handover, access request is sent to access module, if access
module returns access failure due to UDP port request failure.
Usage

Measurement
Point
FIGURE 1790 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
1739
Definition

Description

AIPB.
Usage

Measurement
Point
FIGURE 1791 CHANNEL
Unit
Related Features
1740
ALLOCATION FAILURE
Times
(speech version 3)
Definition

Description

Usage

Measurement
Point
Unit
Related Features
Times
1741
version 3)
Definition

Description

Usage

Measurement
Point
FIGURE 1793 CHANNEL
Unit
Related Features
1742
ALLOCATION FAILURE
Times
version 3)
Definition

Description

Usage

Measurement
Point
FIGURE 1794 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
1743
version 3)
Definition

Description

This counter increments while BSC receives EV_RANUMC_RADIO_APPLY message (speech version 3), the reason to request
channel is handover and request AIPB resource from database, if
request AIPB fails (including database return failure or no AIPB
Usage

Measurement
Point
Unit
Related Features
1744
Times
version 3)
Definition

Description

UDP port.
Usage

Measurement
Point
FIGURE 1796 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
1745
Definition

Description

AIPB.
Usage

Measurement
Point
FIGURE 1797 CHANNEL
Unit
Related Features
1746
ALLOCATION FAILURE
Times
failure for assignment (data)
Definition

Description

(data) to apply for AIPB board resource from database, failed request (including database return failure or no AIPB resource) indicates TCH/F allocation failure.
Usage

Measurement
Point
Unit
Related Features
Times
1747
for assignment (data)
Definition

Description

(data), access request is sent to access module, if access module
returns access failure due to UDP port request failure.
Usage

Measurement
Point
FIGURE 1799 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
Definition
1748

Description

Usage

Measurement
Point
FIGURE 1800 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
failure for handover (data)
Definition

Description

When BSC receives EV_RANUMC_RADIO_APPLY message (data),
the reason to request channel is handover, to request AIPB resource from database. This counter increments if failed to request
AIPB (including database returning failure or no AIPB resource),
indicating TCH/F allocation failure.
Usage

Measurement
Point
1749
Unit
Related Features
Times
for handover (data)
Definition

for handover (data)
Description

the reason to request channel is handover, to request access request for access module. This counter increments while access
module returns failure and the reason is failed to request UDP
port.
1750
Usage

Measurement
Point
FIGURE 1802 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
for handover (data)
Definition

for handover (data)
Description

module returns failure and the reason is failed to access AIPB.
Usage

Measurement
Point
FIGURE 1803 CHANNEL
Unit
ALLOCATION FAILURE
Times
1751
Related Features
assign TCH/F release by
forced handover to forced
handover source
Definition
Number of assign TCH/F release by forced handover to forced handover source
Description
When the BSC CS service instance is forcibly handover, this counter

counts the number of times that the released TCH/F resource is assigned to the forced handover source.
The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is assigned to the forced
handover source, the counter accumulates.
Usage
This counter is used to find out the frequency of the TCH/F released
by forced handover being assigned to the forced handover source.
Measurement
Point
The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is assigned to the forced
Unit
Times
forced handover to queuing
user
Definition
Number of assign TCH/F release by forced handover to queuing

user
Description

counts the number of times that the released TCH/F resource is assigned to the queuing user.
The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is assigned to the queuing
user, the counter accumulates.
1752
Usage
by forced handover being assigned to the queuing user.
Measurement
Point
Unit
Times
restore TCH/F release by
forced handover to DBS
Definition
Description
Number of restore TCH/F release by forced handover to DBS

counts the number of times that the released TCH/F resource is assigned to the queuing user.
Usage
by forced handover being restored to DBS.
Measurement
Point
The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is just released instead of
being assigned to other users, the counter accumulates.
Unit
Times
assign TCHF release by
forced release to forced
release source
Definition
Number of assign TCH/F release by forced release to forced release

source
Description
When the BSC CS service instance is forcibly released, this counter

counts the number of times that the released TCH/F resource is
assigned to the forced release source.
The BSC CS service instance is forcibly released to release resource, if the released TCH/F resource is assigned to the forced
release source, the counter accumulates.
1753
Usage
by forced release being assigned to the forced release source.
Measurement
Point
The BSC CS service instance is forcibly released to release resource, if the released TCH/F resource is assigned to the forced
Unit
Times
forced release to queuing
user
Definition
Number of assign TCH/F release by forced release to queuing user
Description

assigned to the queuing user.
The BSC CS service instance is forcibly released to release resource, if the released TCH/F resource is assigned to the queuing
Usage
by forced release being assigned to the queuing user.
Measurement
Point
The BSC CS service instance is forcibly released to release resource, if the released TCH/F resource is assigned to the queuing
Unit
Times
restore TCH/F release by
forced release to DBS
Definition
Description
Number of restore TCH/F release by forced release to DBS

restored to the database instead of being assigned to other users.
The BSC CS service instance is forcibly released to release resource, if the released TCH/F resource is just released instead of
1754
Usage
by forced release being restored to DBS.
Measurement
Point
The BSC CS service instance is forcibly released to release resource, if the released TCH/F resource is just released instead of
FIGURE 1804 CHANNEL
Unit
ALLOCATION FAILURE
Times
(cause:Abis)
Description
This counter counts the number of failed signaling TCH/F seizure

attempts during the process of signaling channel assignment.
When BSC receives the channel request, it attempts to allocate
channel for the request. If the channel occupation fails due to no
available Abis resource, the counter accumulates. If the request
is responded with the message that the transceiver is faulty, the
counter does not count.
Measurement
Point
The counter counts when the request for channel is sent to BSC
(due to assignment, used for signaling channel) and the channel
is occupied successfully.
Unit
Times
1755
(cause:Abis)
Description

attempts during the process of signaling channel handover. When
BSC receives the channel request, it attempts to allocate channel
for the request. If the channel occupation fails due to no available Abis resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing
or forced release is possible, then the instance enters the queuing
state. If the queuing fails, the counter accumulates. If the request
counter does not count. For channel occupation failures in other
cases, the counter accumulates.
Measurement
Point
(due to handover, used for signaling channel) but the channel occupation fails or waiting for resource inside BSC fails.
Unit
Times
for assignment (cause:Abis)
Description
This counter counts the number of failed voice TCH/F seizure attempts during the process of voice channel assignment. When
Measurement
Point
(due to assignment, used for voice channel) but the channel occupation fails or waiting for resource inside BSC fails.
Unit
1756
Times
for handover (cause:Abis )
Description
This counter counts the number of failed voice TCH/F seizure attempts during the process of voice channel handover. When BSC
receives the channel request, it attempts to allocate channel for
the request. If the channel occupation fails due to no available Abis
resource, the counter accumulates. If the request is responded
with the message that no channel is available but queuing or forced
release is possible, then the instance enters the queuing state.
If the queuing fails, the counter accumulates. If the request is
responded with the message that the transceiver is faulty, the
Measurement
Point
(due to handover, used for voice channel) but the channel occupation fails or waiting for resource inside BSC fails.
Unit
Times
Description
This counter counts the number of failed data TCH/F seizure attempts during the process of data channel assignment. When
Measurement
Point
(due to assignment, used for data channel) but the channel occupation fails or waiting for resource inside BSC fails.
Unit
Times
1757
for handover (cause:Abis)
Description
This counter counts the number of failed data TCH/F seizure attempts during the process of data channel handover. When BSC
Measurement
Point
(due to handover, used for data channel) but the channel occupation fails or waiting for resource inside BSC fails.
Unit
Times
(cause:radio resource)
Description

available radio resource, the counter accumulates. If the request
Measurement
Point
Unit
1758
Times
(cause:radio resource)
Description

for the request. If the channel occupation fails due to no available radio resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing
Measurement
Point
Unit
Times
for assignment (cause:radio
resource)
Description
This counter counts the number of failed voice TCH/F seizure attempts during the process of voice channel assignment. When
Measurement
Point
Unit
Times
1759
for handover (cause:radio
resource)
Description
This counter counts the number of failed voice TCH/F seizure attempts during the process of voice channel handover. When BSC
the request. If the channel occupation fails due to no available
radio resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing
Measurement
Point
Unit
Times
resource)
Description
This counter counts the number of failed data TCH/F seizure attempts during the process of data channel assignment. When BSC
Measurement
Point
Unit
1760
Times
resource)
Description
This counter counts the number of failed data TCH/F seizure attempts during the process of data channel handover. When BSC
Measurement
Point
Unit
Times
FR_V1 assignment attempts
Description
This counter counts the number of attempts of assigning TCH/F

of voice version 1 as the voice channel. After BSC responds the
channel request message, allocates channel, and the channel is
occupied successfully, BSC sends the channel activation message
CHL_ACT to BTS to activate the TCH/F. For the assignment from
A-interface, this counter and C901260149 accumulate simultaneously after the assignment success message is received. If the
MS access message can not be received within specified time, the
assignment fails, and the counter accumulates.
Measurement
Point
For the assignment from A-interface, the counter accumulates in

the following cases: BSC receives the message of assignment success, assignment failure, timer timeout, or exception, instance being released, or instance being forcibly released.
Unit
Times
1761
FR_V1 assignment success
Description
This counter counts the number of successes of assigning TCH/F

A-interface, this counter accumulates after the assignment success message is received.
Measurement
Point
For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message.
Unit
Times
Description

Measurement
Point

Unit
Times
Description
1762

Measurement
Point
Unit
Times
Description

Measurement
Point

Unit
Times
Description

Measurement
Point
Unit
Times
1763
FR_V1 handover
Description
This counter counts the number of handover attempts that the destination voice channel is of full-rate voice version 1. During handover, after MS is successfully accessed on the new channel, BSC
will receive the assignment completion message ASS_COM (intra-cell handover) or HO_COM message (inter-cell handover and
external handover). If BSC correctly receives the above messages within specified time, the handover succeeds, this counter
and C901260155 accumulate simultaneously. If BSC receives the
HO_FAILURE message, then it is considered as handover failure
with return, the counter accumulates. If handover fails but BSC
does not receives the HO_FAILURE message, then it is considered as handover failure without return, the counter accumulates.
For intra-cell handover and inter-cell handover, the counter accumulates on the basis of source instances. For external handover,
because the source instance is not at the BSC, the counter accumulates on the basis of destination instances.
Measurement
Point
This
counter
accumulates
when
BSC
receives
the
ASS_COM/HO_COM message, the ASS_FAIL/HO_FAIL message,
or message of exception, instance being released, instance being
forcibly released, or timer timeout.
Unit
Times
FR_V1 handover success
Description
This counter counts the number of successful handovers that

the destination voice channel is of full-rate voice version 1. This
counter accumulates when BSC detects the handover success
message sent from MS on the newly allocated TCH/F channel. For intra-cell handover, the handover success message is
ASS_COM; for inter-cell handover and external handover, the
handover success message is HO_COM. For intra-cell handover
and inter-cell handover, the counter accumulates on the basis
of source instances. For external handover, because the source
instance is not at the BSC, the counter accumulates on the basis
of destination instances.
Measurement
Point
The counter counts when BSC receives the ASS_COM message or

the HO_COM message.
Unit
1764
Times
FR_V2 handover
Description
Measurement
Point
This
counter
accumulates
when
BSC
receives
the
Unit
Times
Description

Measurement
Point

the HO_COM message.
Unit
Times
1765
FR_V3 handover
Description
Measurement
Point
This
counter
accumulates
when
BSC
receives
the
Unit
Times
Description

Measurement
Point

the HO_COM message.
Unit
1766
Times
C901260185 Resourse
releasing of ordinary users
due to being grabbed
(TCH/F)
Description
This counter counts the number of ordinary user's call on TCH/F being released due to resource being preempted. After the ordinary
user obtains TCH/F, call drop occurs. If the problem is caused by
high-priority user's preempting resource, the counter increments.
Usage
This counter is used to find out the number of ordinary user's call
on TCH/F being released due to high-priority user's preempting
resource.
Measurement
Point
After the ordinary user obtains TCH/F, if the forced release message from other call is received, the counter counts. The measurement point is A, as shown in Figure 1805.
1767
FIGURE 1805 FLOW OF ORDINARY USER'S CALL BEING RELEASED

RESOURCE BEING PREEMPTED
Unit
DUE TO
Times
C901260186 Handover of
ordinary users due to be
grabbed (TCH/F)
1768
Description
This counter counts the number of handovers performed for ordinary user's call on TCH/F due to resource being preempted. After
the ordinary user obtains TCH/F, handover is performed due to
no available resource under the BSC. If the problem is caused by
Usage
This counter is used to find out the number of handovers performed for ordinary user's call on TCH/F due to high-priority user's
preempting resource.

Measurement
Point
After the ordinary user obtains TCH/F, if the forced handover message is received, the counter counts. The measurement point is
FIGURE 1806 FLOW OF HANDOVER
RESOURCE BEING PREEMPTED
Unit
FOR
ORDINARY USER'S CALL
DUE TO
Times
Channel Request of priority
users (TCH/F)
Description
This counter counts the number of requesting for TCH/F by highpriority users.
1769

channel for the request. If the channel request is initiated by highpriority user, the counter increments.
Usage
This counter is used to find out the number of requesting for TCH/F
by high-priority users.
Measurement
Point
Unit
1770
When the high-priority user requests for TCH/F, the counter

counts. The measurement point is A, as shown in Figure 1807,
FIGURE 1807 FLOW
OF
OCCUPYING TCH/F
DURING
ASSIGNMENT
FIGURE 1808 FLOW
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
FIGURE 1809 FLOW
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Times
Successful Channel seize of
priority users (TCH/F)
Description
This counter counts the number of high-priority users' requesting

for TCH/F successfully.
channel for the request. If the channel request is initiated by highpriority user and the channel is obtained successfully, the counter
increments.
Usage
This counter is used to find out the number of high-priority users'

requesting for TCH/F successfully.
Measurement
Point
Unit
When the high-priority user requests for TCH/F, if the channel is

obtained successfully, the counter counts. The measurement point
is A, as shown in Figure 1810, Figure 1811, and Figure 1812.
FIGURE 1810 FLOW
OF
OCCUPYING TCH/F
DURING
ASSIGNMENT
FIGURE 1811 FLOW
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
FIGURE 1812 FLOW
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Times
1771
Successful grabbing channel
of priority users (TCH/F)
Description
When the high-priority user requests for TCH/F, this counter

counts the number of high-priority user's successfully preempting
resource from the ordinary user due to no available resource in
the system.
channel for the request. If the request is initiated by high-priority
user but there is no available resource, the system initiates the
flow of preempting resource from ordinary user. If the resource is
preempted successfully, the counter increments.
Usage
This counter is used to find out the number of high-priority user's

preempting resource from ordinary user successfully.
Measurement
Point
1772
When high-priority user requests for TCH/F but there is no available resource, if high-priority user preempts resource from ordinary user successfully, the counter counts. The measurement
FIGURE 1813 FLOW
OF
OCCUPYING TCH/F
DURING
ASSIGNMENT
FIGURE 1814 FLOW
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
FIGURE 1815 FLOW
Unit
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Times
1773
1774
Chapter
33
TCH/H Measurement
Table of Contents
Overview...................................................................... 1779
C901270002 Number of signaling TCH/H seizure success for
assignment................................................................... 1782
C901270005 Number of signaling TCH/H seizure success for
handover...................................................................... 1783
C901270007 Number of signaling TCH/H allocation attempts
by BSC for assignment ................................................... 1785
C901270008 Number of signaling TCH/H allocation success
for assignment .............................................................. 1786
C901270010 Number of signaling TCH/H allocation attempts
by BSC due to handover ................................................. 1787
C901270011 Number of signaling TCH/H allocation success
due to handover ............................................................ 1790
C901270012 Number of signaling TCH/H allocation failure due
to handover .................................................................. 1792
C901270013 Number of signaling TCH/H assignment attempts by BSC .............................................................. 1793
C901270016 Number of signaling TCH/H handover attempts ......................................................................... 1794
C901270017 Number of signaling TCH/H handover success............................................................................. 1797
C901270018 Number of signaling TCH/H handover failure .............................................................................. 1799
C901270019 Number of signaling TCH/H handover failure
messages do not received by BSC.................................... 1801
C901270021 Number of voice TCH/H seizure success for assignment...................................................................... 1802
C901270024 Number of voice TCH/H seizure success for handover........................................................................... 1803
C901270026 Number of TCH/H allocation attempts for assignment by BSC (speech version 1)...................................... 1806
C901270027 Number of TCH/H allocation success for assignment (speech version1).................................................. 1807
C901270032 Number of TCH/H allocation attempts by BSC
during handover (speech version 1) ................................. 1809
C901270033 Number of TCH/H allocation success during handover (speech version 1) ................................................ 1811
for assignment (speech version 2) ................................... 1813
C901270039 Number of TCH/H allocation success by BSC for
assignment (speech version 2) ........................................ 1815
C901270044 Number of TCH/H allocation attempts for handover by BSC (speech version 2) ..................................... 1816
C901270045 Number of TCH/H allocation success for handover (speech version 2) ................................................ 1819
1775
C901270050 Number of TCH/H allocation attempts for assignment (speech version 3)................................................. 1821
C901270051 Number of TCH/H allocation success for assignment (speech version 3)................................................. 1823
for handover (speech version 3) ...................................... 1824
C901270057 Number of TCH/H allocation success for handover (speech version 3) ................................................ 1827
C901270062 Number of Voice TCH/H assignment attempts by
BSC ............................................................................. 1829
C901270065 Number of Voice TCH/H handover attempts ......................................................................... 1831
C901270067 Number of Voice TCH/H handover failure......... 1833
C901270068 Number of Voice TCH/H handover failure messages do not received by BSC ......................................... 1835
C901270070 Number of data TCH/H seizure success for assignment...................................................................... 1836
C901270073 Number of data TCH/H seizure success for handover........................................................................... 1837
C901270075 Number of data TCH/H allocation attempts for
assignment by BSC........................................................ 1840
C901270076 Number of data TCH/H allocation success for assignment...................................................................... 1841
C901270081 Number of data TCH/H allocation attempts by
BSC ............................................................................. 1843
handover...................................................................... 1845
C901270087 Number of data TCH/H assignment attempts by
BSC ............................................................................. 1848
C901270090 Number of data TCH/H handover attempts ......................................................................... 1849
C901270092 Number of data TCH/H handover failure ......... 1852
C901270093 Number of data TCH/H handover failure do not
received by BSC ............................................................ 1853
C901270094 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version
1)................................................................................ 1855
C901270095 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version
1)................................................................................ 1856
C901270096 Number of TCH/H allocation failure for handover
due to TIPB connection failure (Speech version 1).............. 1857
C901270097 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version
1)................................................................................ 1858
2)................................................................................ 1860
2)................................................................................ 1861
2)................................................................................ 1863
3)................................................................................ 1865
1776
Chapter 33 TCH/H Measurement
3)................................................................................ 1866
3)................................................................................ 1868
C901270106 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version
1)................................................................................ 1869
1)................................................................................ 1870
C901270108 Number of TCH/H allocation failure due to AIPB
1)................................................................................ 1872
C901270110 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 1)......... 1873
2)................................................................................ 1875
2)................................................................................ 1876
2)................................................................................ 1878
3)................................................................................ 1881
3)................................................................................ 1882
3)................................................................................ 1884
C901270124 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (data).............. 1887
C901270125 Number of TCH/H allocation failure due to request UDP port failure for assignment (data)..................... 1888
connection failure for assignment (data) ........................... 1888
1777
C901270127 Number of TCH/H allocation failure due to request AIPB resource failure for handover (data)................. 1889
C901270128 Number of TCH/H allocation failure due to request UDP port failure for handover (data)........................ 1890
connection failure for handover (data).............................. 1891
C901270130 Number of assign TCH/H release by forced handover to forced handover source...................................... 1892
C901270131 Number of assign TCH/H release by forced handover to queuing user .................................................... 1892
C901270132 Number of restore TCH/H release by forced handover to DBS ................................................................ 1893
C901270133 Number of assign TCH/H release by forced release to forced release source ......................................... 1893
C901270134 Number of assign TCH/H release by forced release to queuing user..................................................... 1894
C901270135 Number of restore TCH/H release by forced release to DBS ................................................................. 1894
C901270136 Number of signaling TCH/H seize failure for assign due to Abis lack ...................................................... 1895
C901270137 Number of signaling TCH/H seize failure for handover due to Abis lack .................................................... 1895
C901270138 Number of voice TCH/H seizure failure for assignment (cause:Abis) ................................................... 1896
C901270139 Number of voice TCH/H seizure failure for handover (cause:Abis ) ....................................................... 1896
C901270140 Number of data TCH/H seizure failure for assignment (cause:Abis) ......................................................... 1897
C901270141 Number of data TCH/H seizure failure for handover (cause:Abis) ........................................................ 1897
C901270142 Number of signaling TCH/H seize failure for assign due to radio resource lack ........................................ 1898
C901270143 Number of signaling TCH/H seize failure for handover due to radio resource lack ...................................... 1898
C901270144 Number of voice TCH/H seizure failure for assignment (cause:radio resource) ..................................... 1899
C901270145 Number of voice TCH/H seizure failure for handover (cause:radio resource) .......................................... 1899
C901270146 Number of data TCH/H seizure failure for assignment (cause:radio resource) ........................................... 1900
C901270147 Number of data TCH/H seizure failure for handover (cause:radio resource) .......................................... 1900
C901270148 Number of HR_V1 assignment attempts ......... 1901
C901270149 Number of HR_V1 assignment success........... 1901
C901270150 Number of HR_V3 assignment attempts ......... 1901
C901270151 Number of HR_V3 assignment success........... 1902
C901270152 Number of HR_V1 handover ......................... 1902
C901270153 Number of HR_V1 handover success.............. 1903
C901270154 Number of HR_V3 handover ......................... 1903
C901270155 Number of HR_V3 handover success.............. 1904
C901270177 Resource releasing of ordinary users due to being grabbed (TCH/H)...................................................... 1904
C901270178 Handover of ordinary users due to being
grabbed (TCH/H) ........................................................... 1905
(TCH/H) ....................................................................... 1907
C901270180 Number of Successful Channel seize of priority
users (TCH/H)............................................................... 1908
C901270181 Number of Successful grabbing channel of priority users (TCH/H) ....................................................... 1909
1778
Overview
During GSM BSC signaling system, the allocation uses of TCH/H
channel mainly exist in assignment and handover processes. The
assignment processes include immediate assignment, general assignment; handover processes include inner handover and outer
handover.
The measurement point of TCH/H counters in immediate assignment process is shown in Figure 1816.
ASSIGNMENT FLOW
When TC is internal and external, the measurement point of

TCH/H counter in general assignment processes is shown in Figure
FIGURE 1817 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1779
FIGURE 1818 COMMON
ASSIGNMENT FLOW
(EXTERNAL TC)
When TC is internal and external, the measurement point of TCH/H

counter in inner handover process is shown in Figure 1819 and
Figure 1820.
(INTERNAL TC)
1780
HANDOVER
(LIKE

When TC is internal and external, the measurement point of TCH/H

counter in outer handover process is shown in Figure 1821 and
Figure 1822.
HANDOVER FLOW
(INTERNAL TC)
1781
HANDOVER FLOW
(EXTERNAL TC)
Definition
Description
Number of signaling TCH/H seizure success for assignment

This counter counts the number of TCH/H channel being seized
when assigning signaling channel.
After BSC receives request message, it tries to assign channel for
the request. This counter increments when allocation and seizure
succeed.
Measurement
Point
BSC applies for channel (due to assignment, it is used for signaling

channels) and seizure succeeds. The measurement point is A1, as
1782
ASSIGNMENT FLOW
Unit
Related Features
Times
Definition
Description
Number of signaling TCH/H seizure success for handover.

This counter counts the number of TCH/H seizure success in signaling channel handover.
After BSC receives channel request message, it tries to assign
channel for the request. This counter will accumulate if assignment and seizure succeed; if application returns no signaling but
it is possible to queue or being forced to disconnect, it will enter
the state of waiting for resource. This counter will accumulate if
waiting succeeds.
Measurement
Point
BSC applies for channel (because handover, usage are signaling

channels) and seizure succeeds, or it receives inner waiting resource valid message. The measurement points are C1, D1, as
(INTERNAL TC)
HANDOVER
(LIKE
1783

1784
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
attempts by BSC for
assignment
Definition
Number of signaling TCH/H assignment attempts by BSC for assignment
Description
This counter counts the number of TCH/H channel attempts being assigned on allocating signaling channel, including the number of assignment success (C901270008) and assignment failure
(900060174).
After BSC responds channel request message assignment and successfully seizes TCH/H channel, BSC send channel activation message CHL_ACT to BTS to activate the TCH/H. If activation succeeds,
it will receive the CHL_ACT_ACK message sent by BTS, it indicates
TCH/H assignment succeeds, this counter and C901270008 will
accumulate simultaneously. On the contrary, if channel activation
fails due to receiving channel activation failure message, wrong
channel activation response message, timer T9103 timeout, channel instance being released, channel being forced to disconnect
etc, this counter and C900060174 will accumulate simultaneously.
1785
Measurement
Point
After BSC activates TCH/H (because allocation, usage are signaling channels), it receives the CHL_ACK message sent by BTS,
or receives channel activation failure message, wrong channel
activation response message, timer T9013 timeout, channel
instance being released, channel being forced to disconnect etc.
Unit
Related Features
ASSIGNMENT FLOW
Times
Definition
Description
Number of signaling TCH/H allocation success for assignment

This counter counts the number of TCH/H channel success assignment on allocating signaling channel.
After BSC responds channel request messages assignment and
successfully seizures channel, BSC sends channel activation message CHL_ACT to activate the TCH/H. If activated successfully, it
will receive CHL_ACT_ACK message sent by BTS, it indicates that
TCH/H assigns successfully and the counter accumulates.
Measurement
Point
1786
BSC receives correctly CHL_ACT_ACK message sent by BTS and

the reason is that allocation and usage are signaling channel. The
Unit
Related Features
ASSIGNMENT FLOW
Times
attempts by BSC due to
handover
Definition
Number of signaling TCH/H allocation attempts by BSC due to handover
Description
This counter counts the number of TCH/H channel attempt

being allocated in signaling channel handover, including successful allocation times (C901270011) and failed allocation times
(C901270012).
After BSC responds channel request message assignment and
successfully occupies TCH/H channel, BSC send channel activation
message CHL_ACT to BTS to activate the TCH/H. If activation
is successful, it will receive the CHL_ACT_ACK message sent by
BTS, it indicates TCH/H assignment is successful, this counter and
C901270011 will accumulate simultaneously. On the contrary, if
channel activation fails due to receiving channel activation failure
message, wrong channel activation response message, timer
T9103 timeout, channel instance being released, channel being
forced to disconnection etc, this counter and C901270012 will
1787
Measurement
Point
After BSC activates TCH/H (because allocation, usage are signaling

channel), receives correctly the CHL_ACK_ACK message sent by
BTS, or receives channel activation failure message, wrong channel activation response message, timer T9013 timeout, channel
instance being released, channel being forced to disconnection
etc. (C901270011+C901270012). The measurement points are
C3, C4, as shown in Figure 1830, Figure 1831, Figure 1832, and
Figure 1833.
(INTERNAL TC)
HANDOVER
(LIKE

1788
Unit
Related Features
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
1789
success due to handover
Definition
Description
Number of signaling TCH/H allocation success due to handover

This counter counts the number of successful TCH/H channel assignment in signaling channel handover.
After BSC responds channel request messages assignment and
successfully occupies channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/H. If activated successfully, it will receive CHL_ACT_ACK message sent by BTS, it indicates that TCH/H assigns successfully and the counter accumulates.
Measurement
Point
BSC receives correctly CHL_ACT_ACK message sent by BTS and

the reason is that allocation and usage are signaling channel. The
measurement points are C3, D3, as shown in Figure 1834, Figure
1835, Figure 1836, and Figure 1837.
(INTERNAL TC)
1790
HANDOVER
(LIKE

HANDOVER FLOW
(INTERNAL TC)
1791
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
failure due to handover
Definition
Description
Number of signaling TCH/H allocation failure due to handover

This counter counts the number of TCH/H channel assignment failure.
After BSC responds channel request message assignment and successfully occupies TCH/H channel, BSC send channel activation
message CHL_ACT to BTS to activate the TCH/H. If channel activation fails due to receiving channel activation failure message,
wrong channel activation response message, timer T9103 timeout,
channel instance being released, channel being forced to disconnection etc, this counter will increment.
Measurement
Point
1792
BSC activates TCH/H to be used as signaling channel because of

handover, but receiving channel activation failure message, wrong
channel activation response message, timer T9103 timeout, channel instance being released, channel being forced to disconnection
etc. The measurement points are C3, D3, as shown in Figure 1838,
Figure 1839.

FAILURE FLOW 1
Unit
Related Features
(INTERNAL TC
2 (INTERNAL TC)
Times
attempts by BSC
Definition
Description
Number of signaling TCH/H assignment attempts by BSC

This counter counts the number of attempt allocating TCH/H channel to be signaling channel.
After BSC responds channel request message assignment and successfully occupies channel, BSC sends channel activation message
CHL_ACT to BTS to activate the TCH/H. To immediate allocation,
after activated successfully BTS receives MS and send EST_IND
message to BSC, BSC receives the messages and this counter ac-
1793
cumulates; if it is impossible to receive the MS access notification

in the certain time, this allocation fails.
Measurement
Point
For immediate allocation, this counter counts the number when

BSC receives EST_IND message correctly or T31.3 timeout (not
receive the MS access notification in the certain time). The measurement point is A3, as shown in Figure 1840.
Unit
Related Features
ASSIGNMENT FLOW
Times
signaling TCH/H handover
attempts
Definition
Description
Number of signaling TCH/H handover attempts

This counter counts the number of TCH/H channel attempt in
signaling channel handover, including the number of successful
TCH/H handover (C901270017), the number of TCH/H handover
failure with return (C901270018), and the number of TCH/H
handover failure without return (C901270019).
When BSC check the handover success message from MS in the
newly assigned TCH/H channel, this counter and C901270017 will
accumulate; if receiving the failure message, this counter and
C901270018 will accumulate; if receiving abnormal message, or
instance being released, instance being forced to disconnection,
timer timeout, this counter and C901270019 will accumulate.
For handover in cell, the symbol message of handover success is
ASS_COM. For handover between cells and outer handover, the
symbol message of handover success is HO_COM. For handover
1794
in cell and between cells, the counter accumulates based on the

resource instance; for the outer handover, because the resource
instance is not in present BSC, the counter accumulates based on
the object instance.
Measurement
Point
On newly assigned TCH/H channel, BSC check the handover

success ASS_COM/HO_FAIL message sent by MS, or receives
handover failure ASS_FAIL/HO_FAIL message, receives abnormal
message, instance being released, instance being forced to
disconnection, timer timeout, this counter will accumulate. The
measurement points are C4, D4, as shown in Figure 1841, Figure
1842, Figure 1843, and Figure 1844.
(INTERNAL TC)
HANDOVER
(LIKE

1795
Unit
Related Features
1796
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
success
Definition
Description
Number of signaling TCH/H handover success

This counter counts the number of TCH/H channel success in signaling channel handover.
When BSC check the handover success message sent by MS in
newly assigned TCH/H channel, this counter will accumulate.
For handover in cell, the symbol message of handover success is
ASS_COM. For handover between cells and outer handover, the
symbol message of handover success is HO_COM. For handover
in cell and between cells, the counter accumulates based on the
resource instance; for the outer handover, because the resource
instance is not in present BSC, the counter accumulates based on
the object instance.
Measurement
Point
BSC receives ASS_COM or HO_COM message. The measurement

points are C4, D4, as shown in Figure 1845, Figure 1846, Figure
1847 and Figure 1848.
(INTERNAL TC)
HANDOVER
(LIKE
1797

1798
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
failure
Definition
Description
Number of signaling TCH/H handover failure

This counter counts the number of TCH/H channel return handover
failure.
This counter accumulates when MS on the TCH/H channel are in
handover, accesses new channel failure and returns original channel, receives allocation failure on original channel or handover failure.
Measurement
Point

points are C4, D4, as shown in Figure 1849, Figure 1850.
1799
Unit
Related Features
1800

FAILURE FLOW 1
HANDOVER
(INTERNAL TC
(INTERNAL TC)
Times
received by BSC
Definition
Number of signaling TCH/H handover failure messages do not received by BSC
Description
This counter counts the number of TCH/H channel return no handover failure.
This counter accumulates when BSC sends allocation request to
MS or handover request, MS does not handover successfully and
does not return original channel.
Measurement
Point
BSC receives abnormal message, or instance being released, instance being forced to disconnection, timer timeout message. The
measurement point is C4, as shown in Figure 1851, Figure 1852.
FAILURE FLOW 2
(INTERNAL TC

FAILURE FLOW 3
(INTERNAL TC
1801
Unit
Related Features
Times
C901270021 Number
Definition
Description
Number of voice TCH/H seizure success for assignment

This counter counts the number of TCH/H channel being occupied
successfully on allocation voice channel.
After BSC receives channel request message, it attempts to assign
channel for the request. This counter will accumulate if assignment
and occupation succeed. If application returns no channel but possible to queue or force to disconnect, it enters the state of waiting
for resource. This counter accumulates if waiting succeeds.
Measurement
Point
BSC applies for channel (because allocation, usage are voice channel) and occupation succeeds or BSC receives inner waiting resource valid message. The measurement point is B1, as shown in
Figure 1853, Figure 1854.
FAILURE FLOW 1
1802
HANDOVER
(INTERNAL TC
Unit
Related Features
(INTERNAL TC)
Times
C901270024 Number
Definition
Description
Number of voice TCH/H seizure success for handover

on voice channel handover.
channel for the request. This counter will accumulate if assignment
and occupation succeed. If application returns no channel but possible to queue or force to disconnect, it enters the state of waiting
for resource. This counter accumulates if waiting succeeds.
Measurement
Point
BSC applies for channel (because handover, usage are voice channel) and occupation succeeds or BSC receives inner waiting resource valid message. The measurement points are C1, D1, as
1803

(INTERNAL TC)
HANDOVER
(LIKE

1804
Unit
Related Features
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
1805
TCH/H allocation attempts
for assignment by BSC
(speech version 1)
Definition
Number of TCH/H allocation attempts for assignment by BSC

(speech version 1)
Description
This counter counts the number of TCH/H channel being attempt

to assign on allocation voice channel (used for voice version 1),
including assignment success (C901270027) and assignment failure (C900060175+C900060176+900060177+C900060178)
After BSC respond channel request message assignment and successfully occupied TCH/H channel, BSC first finishes connection,
then sends channel activation message CHL_ACT to BTS to activate the the TCH/H. If activation succeeds, BSC will receive the
CHL_ACT_ACK message sent by BTS. It indicated that assignment
succeeds, this counter and C901270027 accumulate simultaneously; on the contrary, if failed, this counter and another counter
related the failure reason accumulate siulataneously.
Measurement
Point
Assignment succeeds or fails (because allocation and usage are

voice channel, use voice version 1). The measurement points are
B2, B3, as shown in Figure 1859, Figure 1860.
FIGURE 1859 COMMON
1806
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1860 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
TCH/H allocation success
version1)
Definition
Number of TCH/H allocation success for assignment (speech version1)
Description

to assign on allocation voice channel (used for voice version 1).
After BSC respond channel request message assignment and successfully occupied channel, BSC sends channel activation message
CHL_ACT to BTS to activate the TCH/F. If activation succeeds, BSC
will receive the CHL_ACT_ACK message sent by BTS. It indicated
that TCH/H assignment succeeds, this counter accumulate.
Measurement
Point
BSC correctly receives the CHL_ACT_ACK message sent by BTS,

and because allocation and usage are voice channel (use voice
version 1). The measurement point is B3, as shown in Figure 1861,
Figure 1862.
1807
Unit
Related Features
1808
FIGURE 1861 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1862 COMMON
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
by BSC during handover
(speech version 1)
Definition
Number of TCH/H allocation attempts by BSC during handover

(speech version 1)
Description

to assign on voice channel (use voice version 1) handover, including assignment success (C901270033) and assignment failure
(C900060179+C900060180+900060181+C900060182)
then sends channel activation message CHL_ACT to BTS to activate the the TCH/H. If activation succeeds, BSC will receive the
CHL_ACT_ACK message sent by BTS. It indicated that assignment
succeeds, this counter and related C901270033 accumulate simultaneously; on the contrary, if failed, this counter and another
counter related the failure reason accumulate simultaneously.
Measurement
Point
Assignment succeeds or fails (because handover, usage are voice

channel, use voice version 1). The measurement points are C3,
D3, as shown in Figure 1863, Figure 1864, and Figure 1865.
(INTERNAL TC)
HANDOVER
(LIKE
1809

Unit
Related Features
1810
HANDOVER FLOW
(INTERNAL TC)
Times
during handover (speech
version 1)
Definition
Number of TCH/H allocation success during handover (speech version 1)
Description
This counter counts the number of TCH/H channel success assignment on voice channel (use voice version 1).
After BSC respond channel request message assignment and successfully occupied channel, BSC sends channel activation message
CHL_ACT to BTS to activate the TCH/F. If activation succeeds, it
will receive CHL_ACT_ACK message sent by BTS. It indicated that
TCH/H assignment succeeds, this counter accumulate.
Measurement
Point

and because handover and usage are voice channel (use voice version 1). The measurement points are C3, D3, as shown in Figure
1866, Figure 1867, Figure 1868, and Figure 1869.
(INTERNAL TC)
HANDOVER
(LIKE
1811

1812
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
by BSC for assignment
(speech version 2)
Definition
Number of TCH/H allocation attempts by BSC for assignment

(speech version 2)
Description

to assign on allocation voice channel (use voice version 2), including assignment success (C901270039) and assignment failure
(C900060183+C900060184+900060185+C900060186)
the TCH/H. If activation succeeds, it will receive the CHL_ACT_ACK
message sent by BTS. It indicated that TCH/H assignment succeeds, this counter and C901270039 accumulate simultaneously;
on the contrary, if failed, this counter and another counter related
the failure reason accumulate simultaneously.
1813
Measurement
Point
Unit
Related Features
1814
Assignment succeeds or fails (because allocation, usage are voice

channel, use voice version 2). The measurement points are B2,
B3, as shown in Figure 1870, Figure 1871.
FIGURE 1870 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1871 COMMON
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
TCH/H allocation success by
BSC for assignment (speech
version 2)
Definition
Number of TCH/H allocation success by BSC for assignment

(speech version 2)
Description
This counter counts the number of TCH/H channel success assignment on allocation voice channel (use voice version 2).
After BSC responds channel request message assignment and successfully occupied channel, BSC sends channel activation message
Measurement
Point

version 2). The measurement point is B3, as shown in Figure 1872,
Figure 1873.
FIGURE 1872 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1815
FIGURE 1873 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
for handover by BSC
(speech version 2)
Definition
Number of TCH/H allocation attempts for handover by BSC (speech

version 2)
Description

to assign on voice channel (use voice version 2) handover, including assignment success (C901270045) and assignment failure
(C900060187+C900060188+900060189+C900060190)
After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC first finishes connection,
1816
Measurement
Point

D3, as shown in Figure 1874, Figure 1875, Figure 1876, and Figure
1877.
(INTERNAL TC)
HANDOVER
(LIKE

1817
Unit
Related Features
1818
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
for handover (speech version
2)
Definition
Number of TCH/H allocation success for handover (speech version

2)
Description
Measurement
Point

(INTERNAL TC)
HANDOVER
(LIKE
1819

1820
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
version 3)
Definition
Number of TCH/H allocation attempts for assignment (speech version 3)
Description

to assign on allocation voice channel (use voice version 3), including assignment success (C901270051) and assignment failure
(C900060191+C900060192+900060193+C900060194)
1821
Measurement
Point
Unit
Related Features
1822
Assignment succeeds or fails (because allocation, usage are voice

channel, use voice version 3). The measurement points are B2,
B3, as shown in Figure 1882and Figure 1883.
FIGURE 1882 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1883 COMMON
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
version 3)
Definition
Number of TCH/H allocation success for assignment (speech version 3)
Description
This counter counts the number of TCH/H channel success assignment on allocation voice channel (use voice version 3).
Measurement
Point

version 3). The measurement point is B3, as shown in Figure 1884
and Figure 1885.
FIGURE 1884 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1823
FIGURE 1885 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
by BSC for handover
(speech version 3)
Definition
Number of TCH/H allocation attempts by BSC for handover (speech

version 3)
Description

to assign on voice channel (use voice version 3), including
assignment success (C901270057) and assignment failure
(C900060195+C900060196+900060197+C900060198)
1824
Measurement
Point

D3, as shown in Figure 1886, Figure 1887, Figure 1888, and Figure
1889.
(INTERNAL TC)
HANDOVER
(LIKE

1825
Unit
Related Features
1826
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
for handover (speech version
3)
Definition
Number of TCH/H allocation success for handover (speech version

3)
Description
CHL_ACT to BTS to activate the TCH/H. If activation succeeds, it
Measurement
Point

(INTERNAL TC)
HANDOVER
(LIKE
1827

1828
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
attempts by BSC
Definition
Description
Number of Voice TCH/H assignment attempts by BSC

This counter counts the number of attempting TCH/H channel to be
voice channel, including assignment success (C900060199) and
allocation failure (C900060200).
CHL_ACT to BTS to activate the TCH/H. For allocation from A-interface, after receiving allocation success message, this counter
and C900060199 accumulate simultaneously. If it is impossible to
receive MS access notification in the certain time, the assignment
fails, this counter and C900060200 accumulate simultaneously.
Measurement
Point
For allocation from A-interface, BSC correctly receives the allocation success message, allocation failure message, timer timeout
message, or abnormal message, the instance being released, the
instance being forced to disconnection, this counter accumulates.
1829
The measurement point is B5, as shown in Figure 1894and Figure

1895.
Unit
Related Features
1830
FIGURE 1894 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1895 COMMON
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
attempts
Definition
Description
Number of Voice TCH/H handover attempts

This counter counts the number of TCH/H channel attempt in
voice channel handover, including the number of TCH/H handover success (C900060201), TCH/H handover failure with
return (C901270067) and TCH/H handover failure without return
(C901270068).
During handover, when MS is accessed successfully on the new
channel, BSC will receive allocation finishing message ASS_COM
(handover in cell) or HO_COM message (handover between cells
and outer handover).
If BSC correctly receives the message above in the certain
time, it indicated that handover succeed, the related counter
and C900060201 will accumulate simultaneously; if BSC receives HO_FAILURE, it returns handover failure, this counter and
C901270067 will accumulate simultaneously; if handover fails,
BSC does not receive HO_FAILURE, then no return handover fails.
This counter and C901270068 will accumulate simultaneously.
For handover in cell and between cells, this counter accumulates
based on the resource instance; for outer handover, because the
resource instance is not in local BSC, the object instance accumulates.
Measurement
Point
BSC receives ASS_COM/HO_COM message, ASS_FAIL/HO_FAIL

message or receive abnormal message, the instance being released, the instance being forced to disconnection, timer timeout.
The measurement points are C4, D4, as shown in Figure 1896,
(INTERNAL TC)
HANDOVER
(LIKE
1831

1832
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
failure
Definition
Description
Number of Voice TCH/H handover failure

This counter counts the number of TCH/H channel returning handover failure on voice channel handover.
MS is in handover on TCH/H channel, accesses new channel failure and returns original channel. This counter accumulates when
receiving allocation failure/handover failure on original channel.
Measurement
Point
BSC receives the ASS_FAIL/HO_FAIL message. The measurement

points are C4, D4, as shown in Figure 1900and Figure 1901.
1833
Unit
Related Features
1834

FAILURE FLOW 1
HANDOVER
(INTERNAL TC
(INTERNAL TC)
Times
received by BSC
Definition
Number of Voice TCH/H handover failure messages do not received

by BSC
Description
This counter counts the number of TCH/H channel returning no

handover failure on voice channel handover.
BSC sends allocation request/handover request to MS, MS does
not handover successfully, not return resource channel, and then
accumulates.
Measurement
Point
BSC receives abnormal message, timer timeout message or the instance being released, the instance being forced to disconnection.
The measurement points are C4, D4, as shown in Figure 1902and
Figure 1903.
FAILURE FLOW 2
(INTERNAL TC

FAILURE FLOW 3
(INTERNAL TC
1835
Unit
Related Features
Times
data TCH/H seizure success
for assignment
Definition
Description
Number of data TCH/H seizure success for assignment

successfully on allocation data channel.
channel for the request. If assignments and occupation succeed,
this counter will accumulate; If application returns no channel but
possible to queue or force to disconnect, it enters the status of
waiting resource. This counter will also accumulate until waiting
succeeds.
Measurement
Point
BSC applies for channel (because allocation, usage are data channels) and occupies successfully, or BSC receives inner waiting resource valid message. The measurement points is B1, as shown
in Figure 1904and Figure 1905.
FIGURE 1904 COMMON
1836
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1905 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times
data TCH/H seizure success
for handover
Definition
Description
Number of data TCH/H seizure success for handover

successfully on data channel handover.
channel for the request. If assignments and occupation succeed,
this counter will accumulate; If application returns no channel but
possible to queue or force to disconnect, it enters the status of
waiting resource. This counter will also accumulate until waiting
succeeds.
Measurement
Point
BSC applies for channel (because handover, usage are data channels) and occupies successfully, or BSC receives inner waiting resource valid message. The measurement points are C1, D1, as
1837

(INTERNAL TC)
HANDOVER
(LIKE

1838
Unit
Related Features
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
1839

for assignment by BSC
Definition
Number of data TCH/H allocation attempts for assignment by BSC
Description
This counter counts the number of TCH/H channel being

assigned on allocation data channel, including assignment success (C901270076) and assignment failure (C900060202 +
C900060203 + C900060204 + C900060205).
Usage
message sent by BTS. It indicated that TCH/H assignment succeeds, this related counter and C901270076 accumulate simultaneously; on the contrary, if fails, this counter and another counter
related the failure reason accumulate simultaneously.
Measurement
Point
Assignment succeeds or fails (because allocation, usage are data

channel). The measurement points are B2, B5, as shown in Figure
FIGURE 1910 COMMON
1840
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1911 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times

for assignment
Definition
Description
Number of data TCH/H allocation success for assignment

This counter counts the number of TCH/H channel being assigned
successfully.
will receive the CHL_ACT_ACK message sent by BTS. It indicated
that TCH/H assignment succeeds, This counter accumulates.
Measurement
Point

and because allocation and usage are data channel. The measurement points is B3, as shown in Figure 1912and Figure 1913.
1841
Unit
Related Features
1842
FIGURE 1912 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1913 COMMON
ASSIGNMENT FLOW
(EXTERNAL TC)
Times

by BSC
Definition
Description
Number of data TCH/H allocation attempts by BSC

This counter counts the number of TCH/H channel being attempted to assign on data channel handover, including assignment
success (C901270082) and assignment failure (C900060206 +
C900060207 + C900060208 + C900060209).
message sent by BTS. It indicated that TCH/H assignment succeeds, this related counter and C901270082 accumulate simultaneously; on the contrary, if fails, this counter and another counter
related the failure reason accumulate simultaneously.
Measurement
Point
Assignment succeeds or fails (because handover, usage are data

channels). The measurement points are C3, D3, as shown in
Figure 1914, Figure 1915, Figure 1916, and Figure 1917.
(INTERNAL TC)
HANDOVER
(LIKE
1843

1844
HANDOVER FLOW
(INTERNAL TC)
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times

for handover
Definition
Description
Number of data TCH/H allocation success for handover

This counter counts the number of TCH/H channel assignment successfully on data channel handover.
will receive the CHL_ACT_ACK message sent by BTS and indicate
that TCH/H assignment succeeds. This counter accumulates.
Measurement
Point

and because handover and usage are data channel. The measurement points are C3, D3, as shown in Figure 1918, Figure 1919,
1845

(INTERNAL TC)
HANDOVER
(LIKE

1846
Unit
Related Features
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
1847
data TCH/H assignment
attempts by BSC
Definition
Description
Number of data TCH/H assignment attempts by BSC

This counter counts the number of attempting TCH/H channel to
be data channel, including assignment success (C900060210) and
allocation failure (C900060211).
CHL_ACT to BTS to activate the TCH/H. For allocation from A-interface, after receiving allocation success message, this counter
and C900060210 accumulate simultaneously. If it is impossible to
receive MS access notification in the certain time, the assignment
fails, this counter and C900060211 accumulate simultaneously.
Measurement
Point
For allocation from A-interface, BSC correctly receives the allocation success message, allocation failure message, timer timeout message, or abnormal message, the instance being released,
the instance being forced to disconnect, this counter accumulates.
The measurement point is B5, as shown in Figure 1922and Figure
1923.
FIGURE 1922 COMMON
1848
ASSIGNMENT FLOW
(INTERNAL TC)
FIGURE 1923 COMMON
Unit
Related Features
ASSIGNMENT FLOW
(EXTERNAL TC)
Times

Definition
Description
Number of data TCH/H handover attempts

This counter counts the number of TCH/H channel attempt
on data channel handover, including TCH/H handover success
(C900060212), TCH/H returning handover failure (C901270092)
and TCH/H returning no handover failure (C901270093).
During handover, when MS is accessed successfully on the new
channel, BSC will receive allocation finishing message ASS_COM
(handover in cell) or HO_COM message (handover between cells
and outer handover).
If BSC correctly receives the message above in the certain
time, it indicated that handover succeed, this related counter
and C900060212 will accumulate simultaneously; if BSC receives HO_FAILURE, it returns handover failure, this counter and
C901270092 will accumulate simultaneously; if handover fails,
BSC does not receive HO_FAILURE, then no returning handover
fails. This counter and C901270093 will accumulate simultaneously.
For handover in cell and between cells, this counter accumulates
based on the resource instance; for outer handover, because the
resource instance is not in local BSC, the object instance accumulates.
1849
Measurement
Point
BSC receives ASS_COM/HO_COM message, ASS_FAIL/HO_FAIL

message or receive abnormal message, the instance being released, the instance being forced to disconnection, timer timeout.
The measurement points are C4, D4, as shown in Figure 1924,
(INTERNAL TC)
HANDOVER
(LIKE

1850
Unit
Related Features
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times
1851
data TCH/H handover failure
Definition
Description
Number of data TCH/H handover failure

This counter counts the number of TCH/H channel returning handover failure on data channel handover.
MS is under handover on TCH/H channel, access new channel fails
then returns original channel. This counter accumulates when receiving allocation failure/handover failure on original channel.
Measurement
Point
BSC receives the ASS_FAIL/HO_FAIL message. The measurement

points are C4, D4, as shown in Figure 1928and Figure 1929.
FAILURE FLOW 1
1852
HANDOVER
(INTERNAL TC
Unit
Related Features
(INTERNAL TC)
Times
data TCH/H handover failure
do not received by BSC
Definition
Description
Number of data TCH/H handover failure do not received by BSC

This counter counts the number of TCH/H channel returning no
handover failure on data channel handover.
After BSC sends allocation request/handover request to MS, MS
does not handover successfully, not go back to the original channel, then accumulate.
Measurement
Point
BSC receives abnormal message, the instance being released, the

instance being forced to disconnect or timer timeout message.
The measurement point is C4, as shown in Figure 1930and Figure
1931.
1853
Unit
Related Features
1854

FAILURE FLOW 2
HANDOVER
(INTERNAL TC

FAILURE FLOW 3
HANDOVER
(INTERNAL TC
Times
TCH/H allocation failure for
assignment due to TIPB
version 1)
Definition
Number of TCH/H allocation failure for assignment due to TIPB

Description
This counter counts the number of TCH/H channel assignment failure due to TIPB connection failure when allocating voice channel
(use voice version 1).
After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC sends TIU connection request to TIPB. If TIU connection fails due to receiving TIU connection failure, or wrong TIU connection respond message, timer
timeout, then this counter will accumulate.
Measurement
Point
Due to allocation BSC uses TCH/H. Receive connection failure message, wrong connection respond message, or timer timeout when
in TIU connection. The measurement point is B2, as shown in
Figure 1932.
Unit
Related Features
Times
1855
Definition
Number of TCH/H allocation failure for assignment due to Resource

request to iTC failure (Speech version 1)
Description
This counter counts the number of TCH/H channel assignment failure due to iTC application resource failure when allocating voice
channel (use voice version 1).
After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC apply for resource to iTC.
If iTC application resource fails due to receiving iTC resource unavailability, or wrong response message, or timer timeout, then it
contributes to TCH/H assignment failure and this counter will accumulate.
Measurement
Point
Due to allocation BSC uses TCH/H. Receive iTC resource unabailability, wrong respond message, or timer timeout when in iTC application resource. The measurement point is B1, as shown in
Figure 1933.
Unit
Related Features
1856
Times
version 1)
Definition
Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 1)
Description
This counter counts the number of TCH/H channel assignment failure due to TIU connection failure when in voice channel handover
After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC sends TIU connection request to TIPB. If TIU connection fails due to receiving TIU connection failure, or wrong TIU connection response message, timer
Measurement
Point
Due to handover BSC uses TCH/H. Receive connection failure message, wrong connection response message, or timer timeout when
in TIU connection. The measurement points are C2, D2, as shown

1857
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
handover due to Resource
request to iTC failure
(Speech version 1)
Definition
Number of TCH/H allocation failure for handover due to Resource

Description
This counter counts the number of TCH/H channel assignment failure due to iTC application resource failure when voice channel handover (use voice version 1).
successfully occupied TCH/H channel, the type of BSC judgement
channel changes. Need to reapply TC resource, then BSC apply for
resource to iTC. If iTC application resource fails due to receiving
iTC resource unavailability, or wrong response message, or timer
timeout, then it contributes to TCH/H assignment failure and this
counter will accumulate.
1858
Measurement
Point
Due to allocation BSC uses TCH/H. Receive iTC resource unabailability, wrong response message, or timer timeout when in iTC application resource. The measurement points are C1, D1, as shown

Unit
Related Features
2 (EXTERNAL TC)
Times
1859
version 2)
Definition

Description
This counter counts the number of TCH/H channel assignment failure due to TIPB connection failure when allocating voice channel
Measurement
Point
Due to allocation BSC uses TCH/H. Receive connection failure message, wrong connection response message, or timer timeout when
Figure 1938.
Unit
Related Features
1860
Times
Definition

Description
After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC apply for resource to iTC.
Measurement
Point
Due to allocation BSC uses TCH/H. Receive iTC resource unabailability, wrong response message, or timer timeout when in iTC
application resource. The measurement point is B1, as shown in
Figure 1939.
Unit
Related Features
Times
1861
version 2)
Definition
Description
This counter counts the number of TCH/H channel assignment failure due to TIU connection failure when voice channel handover
Measurement
Point

1862
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
(Speech version 2)
Definition

Description
This counter counts the number of TCH/H channel assignment failure due to iTC application resource failure when voice channel (use
voice version 2).
successfully occupied TCH/H channel, the type of BSC judgement
channel changes. Need to reapply TC resource, then BSC apply for
resource to iTC. If iTC application resource fails due to receiving
iTC resource unavailability, or wrong response message, or timer
timeout, then it contributes to TCH/H assignment failure and this
counter will accumulate.
1863
Measurement
Point
Due to handover BSC uses TCH/H. Receive iTC resource un availability, wrong response message, or timer timeout when in iTC application resource. The measurement points are C1, D1, as shown

Unit
Related Features
1864
2 (EXTERNAL TC)
Times
version 3)
Definition

Description
This counter counts the number of TCH/H channel assignment failure due to TIU connection failure when allocating voice channel
Measurement
Point
Due to allocation BSC uses TCH/H. Receive connection failure message, wrong connection response message, or timer timeout when
Figure 1944.
Unit
Related Features
Times
1865
Definition

Description
After BSC responds channel request message assignment and successfully occupies TCH/H channel, BSC apply for resource to iTC.
Measurement
Point
Due to allocation BSC uses TCH/H. Receive iTC resource unavailability, wrong response message, or timer timeout when in iTC
application resource. The measurement point is B1, as shown in
Figure 1945.
Unit
Related Features
1866
Times
version 3)
Definition
Description
This counter counts the number of TCH/H channel assignment failure due to TIU connection failure when voice channel (use voice
version 3) handover.
After BSC responds channel request message assignment and successfully occupies TCH/H channel, BSC sends TIU connection request to TIPB. If TIU connection fails due to receiving TIU connection failure, or wrong TIU connection response message, timer
Measurement
Point

1867
Unit
Related Features
HANDOVER FLOW
(EXTERNAL TC)
Times
(Speech version 3)
Definition

Description
This counter counts the number of TCH/H channel assignment failure due to iTC application resource failure when voice channel (use
voice version 3) handover.
After BSC responds channel request message assignment and successfully occupies TCH/H channel, BSC applies for resource to iTC.
Measurement
Point
1868
Due to allocation BSC uses TCH/H. Receive iTC resource unavailability, wrong response message, or timer timeout when in iTC ap-
plication resource. The measurement points are C1, D1, as shown

in Figure 1948 and Figure 1949.

Unit
Related Features
2 (EXTERNAL TC)
Times
(speech version 1)
Definition
Number of TCH/H allocation failure due to request AIPB resource

1869
Description
This counter counts the number of TCH/H allocation failure due to

board resource) indicates TCH/H allocation failure.
Usage
This counter is used to find out the frequency of TCH/H allocation

Measurement
Point
Unit
Times
version 1)
Definition
Number of TCH/H allocation failure due to request UDP port failure

Description

Usage
1870

Measurement
Point
FIGURE 1951 CHANNEL
Unit
ALLOCATION FAILURE
Times
version 1)
Definition
Number of TCH/H allocation failure due to AIPB connection failure

Description

Usage

Measurement
Point
1871
FIGURE 1952 CHANNEL
Unit
ALLOCATION FAILURE
Times
version 1)
Definition

Description

resource), indicating TCH/H allocation failure.
1872
Usage

Measurement
Point
Unit
Related Features
Times
version 1)
Definition

Description

UDP port.
Usage

Measurement
Point
1873
FIGURE 1954 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
Definition

Description

AIPB.
Usage

Measurement
Point
FIGURE 1955 CHANNEL
Unit
1874
ALLOCATION FAILURE
Times
Related Features
(speech version 2)
Definition

Description

Usage

Measurement
Point
Unit
Times
1875
version 2)
Definition

Description

Usage

Measurement
Point
FIGURE 1957 CHANNEL
Unit
1876
ALLOCATION FAILURE
Times
version 2)
Definition

Description

Usage

Measurement
Point
FIGURE 1958 CHANNEL
Unit
ALLOCATION FAILURE
Times
1877
version 2)
Definition

Description

Usage

Measurement
Point
Unit
Related Features
1878
Times
version 2)
Definition

Description

This counter increments while BSC receives EV_RANUMC_RADIO_APPLY message (speech version 2) to request channel due
to handover, access request is sent to access module, if access
module returns access failure due to UDP port request failure.
Usage

Measurement
Point
FIGURE 1960 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
1879
Definition

Description

AIPB.
Usage

Measurement
Point
FIGURE 1961 CHANNEL
Unit
Related Features
1880
ALLOCATION FAILURE
Times
(speech version 3)
Definition

Description

Usage

Measurement
Point
Unit
Related Features
Times
1881
version 3)
Definition

Description

Usage

Measurement
Point
FIGURE 1963 CHANNEL
Unit
Related Features
1882
ALLOCATION FAILURE
Times
version 3)
Definition

Description

Usage

Measurement
Point
FIGURE 1964 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
1883
version 3)
Definition

Description

This counter increments while BSC receives EV_RANUMC_RADIO_APPLY message (speech version 3), the reason to request
channel is handover and request AIPB resource from database, if
request AIPB fails (including database return failure or no AIPB
Usage

Measurement
Point
Unit
Related Features
1884
Times
version 3)
Definition

Description

UDP port.
Usage

Measurement
Point
FIGURE 1966 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
1885
Definition

Description

AIPB.
Usage

Measurement
Point
FIGURE 1967 CHANNEL
Unit
Related Features
1886
ALLOCATION FAILURE
Times
Definition

Description

(data) to apply for AIPB board resource from database, failed request (including database return failure or no AIPB resource) indicates TCH/H allocation failure.
Usage

Measurement
Point
Unit
Times
1887
Definition

Description

Usage

Measurement
Point
FIGURE 1969 CHANNEL
Unit
ALLOCATION FAILURE
Times
1888
Definition

Description


Usage

Measurement
Point
FIGURE 1970 CHANNEL
Unit
ALLOCATION FAILURE
Times
Definition

Description

the reason to request channel is handover, to request AIPB resource from database. This counter increments if failed to request
AIPB (including database returning failure or no AIPB resource),
indicating TCH/H allocation failure.
Usage

Measurement
Point
1889
Unit
Related Features
Times
for handover (data)
Definition

for handover (data)
Description

module returns failure and the reason is failed to request UDP
port.
Usage

Measurement
Point
FIGURE 1972 CHANNEL
1890
ALLOCATION FAILURE
Unit
Related Features
Times
for handover (data)
Definition

for handover (data)
Description

module returns failure and the reason is failed to access AIPB.
Usage

Measurement
Point
FIGURE 1973 CHANNEL
Unit
Related Features
ALLOCATION FAILURE
Times
1891
assign TCH/H release by
forced handover to forced
handover source
Definition
Number of assign TCH/H release by forced handover to forced handover source
Description

counts the number of times that the released TCH/H resource is
assigned to the forced handover source.
The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is assigned to the forced
Usage
This counter is used to find out the frequency of the TCH/H released by forced handover being assigned to the forced handover
source.
Measurement
Point
The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is assigned to the forced
Unit
Times
forced handover to queuing
user
Definition
Number of assign TCH/H release by forced handover to queuing

user
Description

The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is assigned to the queuing
Usage
This counter is used to find out the frequency of the TCH/H released by forced handover being assigned to the queuing user.
Measurement
Point
The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is assigned to the queuing
Unit
1892
Times
restore TCH/H release by
forced handover to DBS
Definition
Description
Number of restore TCH/H release by forced handover to DBS

The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is just released instead of
Usage
This counter is used to find out the frequency of the TCH/H released by forced handover being restored to DBS.
Measurement
Point
The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is just released instead of
Unit
Times
forced release to forced
release source
Definition
Number of assign TCH/H release by forced release to forced release source
Description

assigned to the forced release source.
The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is assigned to the forced
Usage
This counter is used to find out the frequency of the TCH/H released
by forced release being assigned to the forced release source.
Measurement
Point
The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is assigned to the forced
Unit
Times
1893
forced release to queuing
user
Definition
Number of assign TCH/H release by forced release to queuing user
Description

The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is assigned to the queuing
Usage
This counter is used to find out the frequency of the TCH/H released by forced release being assigned to the queuing user.
Measurement
Point
The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is assigned to the queuing
Unit
Times
restore TCH/H release by
forced release to DBS
Definition
Description
Number of restore TCH/H release by forced release to DBS

The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is just released instead of
Usage
This counter is used to find out the frequency of the TCH/H released by forced release being restored to DBS.
Measurement
Point
The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is just released instead of
Unit
1894
Times
signaling TCH/H seize
failure for assign due to Abis
lack
Description
This counter counts the number of failed signaling TCH/H seizure

available Abis resource, the counter accumulates. If the request
Measurement
Point
Unit
Times
Abis lack
Description

Measurement
Point
Unit
Times
1895
Description
This counter counts the number of failed voice TCH/H seizure attempts during the process of voice channel assignment. When
Measurement
Point
Unit
Times
for handover (cause:Abis )
Description
This counter counts the number of failed voice TCH/H seizure attempts during the process of voice channel handover. When BSC
Measurement
Point
Unit
1896
Times
Description
This counter counts the number of failed data TCH/H seizure attempts during the process of data channel assignment. When
Measurement
Point
Unit
Times
for handover (cause:Abis)
Description
This counter counts the number of failed data TCH/H seizure attempts during the process of data channel handover. When BSC
Measurement
Point
Unit
Times
1897
failure for assign due to radio
resource lack
Description

available radio resource, the counter accumulates. If the request
Measurement
Point
Unit
Times
radio resource lack
Description

Measurement
Point
Unit
1898
Times
resource)
Description
This counter counts the number of failed voice TCH/H seizure attempts during the process of voice channel assignment. When
Measurement
Point
Unit
Times
resource)
Description
This counter counts the number of failed voice TCH/H seizure attempts during the process of voice channel handover. When BSC
Measurement
Point
Unit
Times
1899
resource)
Description
This counter counts the number of failed data TCH/H seizure attempts during the process of data channel assignment. When BSC
Measurement
Point
Unit
Times
resource)
Description
This counter counts the number of failed data TCH/H seizure attempts during the process of data channel handover. When BSC
Measurement
Point
Unit
1900
Times
HR_V1 assignment attempts
Description
This counter counts the number of attempts of assigning TCH/H

CHL_ACT to BTS to activate the TCH/H. For the assignment from
Measurement
Point

Unit
Times
HR_V1 assignment success
Description
This counter counts the number of successes of assigning TCH/H

Measurement
Point
Unit
Times
HR_V3 assignment attempts
Description
This counter counts the number of attempts of assigning TCH/H

1901

Measurement
Point
Unit

Times
HR_V3 assignment success
Description
This counter counts the number of successes of assigning TCH/H

Measurement
Point
Unit
Times
HR_V1 handover
1902
Description
This counter counts the number of handover attempts that the destination voice channel is of half-rate voice version 1. During handover, after MS is successfully accessed on the new channel, BSC
Measurement
Point
This
counter
accumulates
when
BSC
receives
the
Unit
Times
HR_V1 handover success
Description
This counter counts the number of successful handovers that the

destination voice channel is of half-rate voice version 1. This
message sent from MS on the newly allocated TCH/H channel. For intra-cell handover, the handover success message is
Measurement
Point

the HO_COM message.
Unit
Times
HR_V3 handover
Description
This counter counts the number of handover attempts that the destination voice channel is of half-rate voice version 3. During handover, after MS is successfully accessed on the new channel, BSC
Measurement
Point
This
counter
accumulates
when
BSC
receives
the
Unit
Times
1903
HR_V3 handover success
Description
This counter counts the number of successful handovers that the

destination voice channel is of half-rate voice version 3. This
message sent from MS on the newly allocated TCH/H channel. For intra-cell handover, the handover success message is
Measurement
Point

the HO_COM message.
Unit
Times
C901270177 Resource
releasing of ordinary users
due to being grabbed
(TCH/H)
Description
This counter counts the number of ordinary user's call on TCH/H

being released due to resource being preempted. After the ordinary user obtains TCH/H, call drop occurs. If the problem is
caused by high-priority user's preempting resource, the counter
increments.
Usage
This counter is used to find out the number of ordinary user's call
on TCH/H being released due to high-priority user's preempting
resource.
Measurement
Point
1904
After the ordinary user obtains TCH/H, if the forced release message from other call is received, the counter counts. The measurement point is A, as shown in Figure 1974.
FIGURE 1974 RESOURCE

GRABBED (TCH/H)
Unit
RELEASING OF ORDINARY USERS DUE TO BEING
Times
C901270178 Handover of
ordinary users due to being
grabbed (TCH/H)
Description
This counter counts the number of handovers performed for ordinary user's call on TCH/H due to resource being preempted. After
the ordinary user obtains TCH/H, handover is performed due to
no available resource under the BSC. If the problem is caused by
1905
Usage
This counter is used to find out the number of handovers performed for ordinary user's call on TCH/H due to high-priority user's
preempting resource.
Measurement
Point
After the ordinary user obtains TCH/H, if the forced handover message is received, the counter counts. The measurement point is
FIGURE 1975 HANDOVER
(TCH/H)
Unit
1906
OF ORDINARY USERS DUE TO BEING GRABBED
Times
Channel Request of priority
users (TCH/H)
Description
This counter counts the number of requesting for TCH/H by highpriority users.
channel for the request. If the channel request is initiated by highpriority user, the counter increments.
Usage
This counter is used to find out the number of requesting for TCH/H
by high-priority users.
Measurement
Point
Unit
When the high-priority user requests for TCH/H, the counter

counts. The measurement point is A, as shown in Figure 1976,
FIGURE 1976 FLOW
OF
OCCUPYING TCH/F
DURING
ASSIGNMENT
FIGURE 1977 FLOW
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
FIGURE 1978 FLOW
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Times
1907
Successful Channel seize of
priority users (TCH/H)
Description
This counter counts the number of high-priority users' requesting

for TCH/H successfully.
channel for the request. If the channel request is initiated by highpriority user and the channel is obtained successfully, the counter
increments.
Usage
This counter is used to find out the number of high-priority users'

requesting for TCH/H successfully.
Measurement
Point
Unit
1908
When the high-priority user requests for TCH/H, if the channel is

obtained successfully, the counter counts. The measurement point
is A, as shown in Figure 1979, Figure 1980, and Figure 1981.
FIGURE 1979 FLOW
OF
OCCUPYING TCH/F
DURING
ASSIGNMENT
FIGURE 1980 FLOW
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
FIGURE 1981 FLOW
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Times
Successful grabbing channel
of priority users (TCH/H)
Description
When the high-priority user requests for TCH/H, this counter

counts the number of high-priority user's successfully preempting
resource from the ordinary user due to no available resource in
the system.
channel for the request. If the request is initiated by high-priority
user but there is no available resource, the system initiates the
flow of preempting resource from ordinary user. If the resource is
preempted successfully, the counter increments.
Usage
This counter is used to find out the number of high-priority user's

preempting resource from ordinary user successfully.
Measurement
Point
When high-priority user requests for TCH/H but there is no available resource, if high-priority user preempts resource from ordinary user successfully, the counter counts. The measurement
FIGURE 1982 FLOW
OF
OCCUPYING TCH/F
DURING
ASSIGNMENT
FIGURE 1983 FLOW
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
1909
FIGURE 1984 FLOW
Unit
1910
OF
OCCUPYING TCH/F
Times
DURING
INTRA-BSC HANDOVER
Chapter
34
Abis Interface Message

Counter Measurement
Table of Contents
Overview...................................................................... 1914
C901280001 Number of DATA REQUEST messages ............ 1915
C901280002 Number of DATA INDICATION messages......... 1916
C901280003 Number of ERROR INDICATION messages........................................................................... 1916
C901280004 Number of ESTABLISH REQUEST messages........................................................................... 1917
C901280005 Number of ESTABLISH CONFIRM messages........................................................................... 1918
C901280006 Number of ESTABLISH INDICATION messages........................................................................... 1918
C901280007 Number of RELEASE REQUEST messages......... 1919
C901280008 Number of RELEASE CONFIRM messages......... 1920
C901280009 Number of RELEASE INDICATION messages........................................................................... 1920
C901280010 Number of UNIT DATA REQUEST messages........................................................................... 1921
C901280011 Number of UNIT DATA INDICATION messages........................................................................... 1922
C901280012 Number of CHANNEL ACTIVATION messages........................................................................... 1922
C901280013 Number of CHANNEL ACTIVATION ACK messages........................................................................... 1923
C901280014 Number of CHANNEL ACTIVATION Negative ACK
messages ..................................................................... 1924
C901280015 Number of CONNECTION FAILURE INDICATION
messages ..................................................................... 1924
C901280016 Number of DEACTIVATE SACCH messages........................................................................... 1925
C901280017 Number of ENCRYPTION COMMAND messages........................................................................... 1926
C901280018 Number of HANDOVER DETECTION messages........................................................................... 1926
C901280019 Number of MEASUREMENT RESULT messages........................................................................... 1927
C901280020 Number of MODE MODIFY REQUEST messages........................................................................... 1928
C901280021 Number of MODE MODIFY ACK messages......... 1929
C901280022 Number of MODE MODIFY NACK messages........................................................................... 1929
C901280023 Number of PHYSICAL CONTEXT REQUEST messages........................................................................... 1930
1911
C901280024 Number of PHYSICAL CONTEXT CONFIRM messages........................................................................... 1931

C901280025 Number of RF CHANNEL RELEASE messages........................................................................... 1931
C901280026 Number of MS POWER CONTROL messages........................................................................... 1932
C901280027 Number of BS POWER CONTROL messages........................................................................... 1933
C901280028 Number of PREPROCESSED CONFIGURE messages........................................................................... 1933
C901280029 Number of PREPROCESSED MEASUREMENT RESULT messages ............................................................. 1934
C901280030 Number of RF CHANNEL RELEASE ACK messages........................................................................... 1935
C901280031 Number of SACCH INFO MODIFY messages........................................................................... 1936
C901280032
Number
of
ABIS_PREPROC_ENHANCEMEAS_RESULT messages ................................................ 1936
C901280033 Number of ABIS_ROUND_TRIP_DELAY_REPORT
messages ..................................................................... 1937
C901280034 Number of ABIS_PRE_HO_NOTIFY messages........................................................................... 1938
C901280035 Number of ABIS_BCCH_INFO messages......... 1938
C901280036 Number of ABIS_CCCH_LOAD_IND messages........................................................................... 1939
C901280037 Number of ABIS_CHL_RQD messages............ 1940
C901280038 Number of ABIS_DELETE_IND messages......... 1940
C901280039
Number
of
ABIS_PAGING_CMD
messages........................................................................... 1941
C901280040 Number of ABIS_IMM_ASSIGN_CMD messages........................................................................... 1942
C901280041 Number of ABIS_SMS_BROADCAST_REQ messages........................................................................... 1942
C901280042 Number of ABIS_SMS_BROADCAST_CMD messages........................................................................... 1943
C901280043 Number of ABIS_CBCH_LOAD_IND messages........................................................................... 1944
C901280044 Number of ABIS_EGPRS_CHL_REQ messages........................................................................... 1944
C901280045 Number of ABIS_LOAD_CONTROL messages........................................................................... 1945
C901280046 Number of ABIS_END_LOAD_CONTROL messages........................................................................... 1946
C901280047 Number of ABIS_END_LOAD_CONTROL_ACK
messages ..................................................................... 1946
C901280048 Number of ABIS_PCCCH_LOAD_IND messages........................................................................... 1947
C901280049 Number of ABIS_RF_RESRC_IND messages........................................................................... 1948
C901280050 Number of ABIS_SACCH_FILLING messages........................................................................... 1948
C901280051 Number of ABIS_OVERLOAD messages .......... 1949
C901280052 Number of ABIS_ERROR_REPORT messages........................................................................... 1950
C901280053
Number
of
ABIS_SYSINFO_REQ
messages........................................................................... 1950
C901280054 Number of ABIS_SI_BC_END messages ......... 1951
C901280055 Number of ABIS_SI_NACK messages............. 1952
C901280056
Number
of
ABIS_PWRCTRL_IND
messages........................................................................... 1952
1912
Chapter 34 Abis Interface Message Counter Measurement
C901280057
Number
of
ABIS_SYSINFO_ACK
messages........................................................................... 1953
C901280061 Number of ABIS_PACKET_PBCCH_INF messages........................................................................... 1954
C901280062 Number of ABIS_PACKET_CCCH_PARA messages........................................................................... 1954
C901280063 Number of ABIS_PACKET_PBCCH_PARA messages........................................................................... 1955
C901280064 Number of ABIS_PACKET_CHN_REQ messages........................................................................... 1956
C901280065 Number of ABIS_PACKET_PAGING_CMD messages........................................................................... 1956
C901280066 Number of ABIS_PACKET_IMM_ASSIGN_CMD
messages ..................................................................... 1957
C901280067 Number of ABIS_PACKET_CONNECT_FAIL_IND
messages ..................................................................... 1958
C901280068 Number of ABIS_PACKET_PRACH_OVERLOAD
messages ..................................................................... 1958
C901280069 Number of ABIS_PACKET_PCH_OVERLOAD
messages ..................................................................... 1959
C901280070 Number of ABIS_PACKET_TA_REQUEST messages........................................................................... 1960
C901280071 Number of ABIS_PACKET_TA_REQUEST_ACK
messages ..................................................................... 1960
C901280072 Number of ABIS_PACKET_CHN_CONFIG_CHG
messages ..................................................................... 1961
C901280073
Number
of
ABIS_PACKET_CHN_CONFIG_CHG_RESP messages .............................................. 1962
C901280074 Number of ABIS_PACKET_PIA_DEL_IND messages........................................................................... 1962
C901280075 Number of ABIS_PACKET_SEND_PIA_IND messages........................................................................... 1963
C901280076 Number of ABIS_PACKET_CHN_CONFIG_REQ
messages ..................................................................... 1964
C901280077 Number of ABIS_EGPRS_PACKET_CHN_REQ
messages ..................................................................... 1964
C901280078 Number of ABIS_PS_CHANNEL_ACTIVE messages........................................................................... 1965
C901280079 Number of ABIS_PS_CHANNEL_ACTIVE_ACK
messages ..................................................................... 1966
C901280080 Number of ABIS_PS_CHANNEL_ACTIVE_NACK
messages ..................................................................... 1966
C901280081 Number of ABIS_PS_CHANNEL_RELEASE messages........................................................................... 1967
C901280082 Number of ABIS_PS_CHANNEL_RELEASE_ACK
messages ..................................................................... 1968
C901280083 Number of ABIS_PS_CHANNEL_RELEASE_NACK
messages ..................................................................... 1968
C901280084 Number of ABIS_PSCONN_CMM_REQ messages........................................................................... 1969
C901280085 Number of ABIS_PSCONN_CMM_ACK messages........................................................................... 1970
C901280086 Number of ABIS_PSCONN_CMM_NACK messages........................................................................... 1970
C901280087 Number of ABIS_GLOBAL_RESET messages........................................................................... 1971
C901280088 Number of ABIS_GLOBAL_RESET_ACK messages........................................................................... 1972
C901280089 Number of ABIS_GLOBAL_RESET_NACK messages........................................................................... 1972
1913
C901280090 Number of ABIS_PACKET_UP_ASSIGN messages........................................................................... 1973

C901280091 Number of ABIS_PACKET_DOWN_ASSIGN messages........................................................................... 1974
C901280092 Number of ABIS_CSCONN_CMM_REQ messages........................................................................... 1974
C901280093 Number of ABIS_CSCONN_CMM_ACK messages........................................................................... 1975
C901280094 Number of ABIS_CSCONN_CMM_NACK messages........................................................................... 1976
C901280095 Number of ABIS_CCMCONN_CMM_REQ messages........................................................................... 1976
C901280096 Number of ABIS_CCMCONN_CMM_ACK messages........................................................................... 1977
C901280097 Number of ABIS_CCMCONN_CMM_NACK messages........................................................................... 1978
C901280098 Number ABIS_PACKET_ACCESS_REJ messages........................................................................... 1978
C901280099
Number
of
ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages ............................................ 1979
C901280100 Number of PACKET_DOWNLINK_ASSIGN messages........................................................................... 1980
C901280101 Number of PACKET_UPLINK_ASSIGN messages........................................................................... 1980
C901280102 Number of ABIS_PACKET_ACCESS_REJ_NEW
messages ..................................................................... 1981
Overview
Abis interface message measurement is mainly for all kinds of
messages of Abis interface to count. It is convenient to find out
the frequency of all kinds of messages transmitting on Abis interface. When BSC receives the messages sent by BTS, the counter
begin to count. The measurement point is A, as shown in Figure
1985.
FIGURE 1985 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
This counter accumulates before sending the message sent to BTS

by BSC. The measurement point is A, as shown in Figure 1986.
1914

TO BTS
WHEN
BSC SENDS ABIS MESSAGE
DATA REQUEST messages
Definition
Number of DATA REQUEST messages
Description
This counter counts the number of data request messages to be

confirmed sent by BSC to LAPD.
Usage
This counter is used to find out the frequency of data request message to be confirmed transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends DATA REQuest message

to BTS. The measurement point is A, as shown in Figure 1987.
TO BTS
Unit
WHEN
Times
1915
C901280002 Number
of DATA INDICATION
messages
Definition
Number of DATA INDICATION messages
Description
This counter counts the number of data indication messages received by BSC on Abis interface.
Usage
This counter is used to find out the frequency of data indication

messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives DATA INDication message. The measurement point is A, as shown in Figure 1988.
FIGURE 1988 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ERROR INDICATION
messages
Definition
1916
Number of ERROR INDICATION messages
Description
When radio channel generates errors (for example radio link fault),
BTS sends ERROR INDication message to notify BSC. This counter
counts the number of ERROR INDication messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of error indication

Measurement
Point
This counter increments when BSC receives ERROR INDication

FIGURE 1989 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ESTABLISH REQUEST
messages
Definition
Number of ESTABLISH REQUEST messages
Description
When BSC delivers short messages need received by A-interface to

MS, it will send Establish Request messages to establish process.
This counter counts the number of Establish Request messages
sent by BSC to BTS.
Usage
This counter is used to find out the frequency of Establish Request

Measurement
Point
This counter increments when BSC sends Establish Request message to BTS. The measurement point is A, as shown in Figure 1990.
TO BTS
Unit
WHEN
Times
1917
ESTABLISH CONFIRM
messages
Definition
Number of ESTABLISH CONFIRM messages
Description
When BSC receives Establish Confirm messages, it indicates that

establishing link succeeds. BSC can deliver short messages to MS.
This counter counts the number of Establish Confirm messages of
Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of Establish Confirm

Measurement
Point
This counter increments when BSC receives Establish Confirm

FIGURE 1991 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ESTABLISH INDICATION
messages
Definition
1918
Number of ESTABLISH INDICATION messages
Description
When MS receives assignment command (including immediate assignment) of BSC or handover command, it sends SABM frame to
network, BTS will send Establish Indication messages to BSC after
receiving. This counter counts the number of Establish Indication
messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of Establish Indication messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives Establish Indication

FIGURE 1992 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
RELEASE REQUEST
messages
Definition
Number of RELEASE REQUEST messages
Description
When BSC releases one channel due to other reasons, it will send
Release Request messages to initiate channel release flow. This
counter counts the number of Release Request messages sent by
BSC to BTS.
Usage
This counter is used to find out the frequency of Release Request

Measurement
Point
This counter increments when BSC sends Release Request message to BTS. The measurement point is A, as shown in Figure 1993.
TO BTS
Unit
WHEN
Times
1919
RELEASE CONFIRM
messages
Definition
Number of RELEASE CONFIRM messages
Description
When BSC sends Release Confirm messages, MS releases channel,

BTS sends BSC Release Confirm messages as reply. This counter
counts the number of Release Confirm messages of Abis interface
messages received by BSC.
Usage
This counter is used to find out the frequency of Release Confirm

Measurement
Point
This counter increments when BSC receives Release Confirm messages. The measurement point is A, as shown in Figure 1994.
FIGURE 1994 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
RELEASE INDICATION
messages
Definition
1920
Number of RELEASE INDICATION messages
Description
When BTS receives one DISC frame sent by MS through one link
layer of multi-frame layer, BTS sends one Release Indication message to notify that link layer connection of BSC radio interface is
released. This counter counts the number of Release Indication
Usage
This counter is used to find out the frequency of Release Indication

Measurement
Point
This counter increments when BSC receives Release Indication

messages. The measurement point is A, as shown in Figure 1995.
FIGURE 1995 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
UNIT DATA REQUEST
messages
Definition
Number of UNIT DATA REQUEST messages
Description
BTS sends a UNIT DATA REQUEST message to BTS. The message

includes complete L3 message needed to send in uncertain mode.
This counter counts the number of UNIT DATA REQUEST messages
sent by BSC to BTS.
Usage
This counter is used to find out the frequency of UNIT DATA REQUEST messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends UNIT DATA REQUEST

messages to BTS. The measurement point is A, as shown in Figure
1996.
TO BTS
Unit
WHEN
Times
1921
UNIT DATA INDICATION
messages
Definition
Number of UNIT DATA INDICATION messages
Description
BTS sends a UNIT DATA INDICATION message to BTS. The message includes complete L3 message needed to send in uncertain
mode. This counter counts the number of UNIT DATA INDICATION
Usage
This counter is used to find out the frequency of UNIT DATA INDICATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives UNIT DATA INDICATION messages. The measurement point is A, as shown in Figure
1997.
FIGURE 1997 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
CHANNEL ACTIVATION
messages
Definition
1922
Number of CHANNEL ACTIVATION messages
Description
When BSC want to activate one channel due to other reasons, it

sends CHANNEL ACTIVATION message to BTS to initiate channel
activation flow. This counter counts the number of CHANNEL ACTIVATION messages sent by BSC to BTS.
Usage
This counter is used to find out the frequency of CHANNEL ACTIVATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends CHANNEL ACTIVATION


TO BTS
Unit
WHEN
Times
CHANNEL ACTIVATION
ACK messages
Definition
Number of CHANNEL ACTIVATION ACK messages
Description
After BSC finishes activating channel, it sends CHANNEL ACTIVATION ACK message to BSC as the response of channel activation
message. This counter counts the number of CHANNEL ACTIVATION ACK messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of CHANNEL ACTIVATION ACK messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives CHANNEL ACTIVATION

ACK messages. The measurement point is A, as shown in Figure
1999.
FIGURE 1999 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1923
CHANNEL ACTIVATION
Negative ACK messages
Definition
Number of CHANNEL ACTIVATION Negative ACK messages
Description
After BSC receives channel activation command, if it is impossible

to finish channel activation due to other reasons (for example TRX
fault etc.), it sends CHANNEL ACTIVATION Negative ACK message
to BSC to notify that BSC channel activation fail. This counter
counts the number of CHANNEL ACTIVATION Negative ACK messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of CHANNEL ACTIVATION Negative ACK messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives CHANNEL ACTIVATION

Negative ACK messages. The measurement point is A, as shown
in Figure 2000.
FIGURE 2000 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
CONNECTION FAILURE
INDICATION messages
Definition
1924
Number of CONNECTION FAILURE INDICATION messages
Description
When connection fails due to certain reason (for example TRX

fault), BTS sends CONNECTION FAILURE INDICATION message to
notify BSC. This counter counts the number of CONNECTION FAILURE INDICATION messages of Abis interface messages received
by BSC.
Usage
This counter is used to find out the frequency of CONNECTION

FAILURE INDICATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives CONNECTION FAILURE INDICATION messages. The measurement point is A, as
FIGURE 2001 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
DEACTIVATE SACCH
messages
Definition
Number of DEACTIVATE SACCH messages
Description
When BSC activate SACCH due to certain reason (releasing radio

channel), it sends DEACTIVATE SACCH message to initiate to activate flow. This counter counts the number of DEACTIVATE SACCH
messages sent by BSC to LAPD.
Usage
This counter is used to find out the frequency of DEACTIVATE

SACCH messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives DEACTIVATE SACCH

TO BTS
Unit
WHEN
Times
1925
ENCRYPTION COMMAND
messages
Definition
Number of ENCRYPTION COMMAND messages
Description
BSC initiate ENCRYPTION COMMAND message to require encryption. This counter counts the number of ENCRYPTION COMMAND
messages sent by BSC to LAPD.
Usage
This counter is used to find out the frequency of ENCRYPTION COMMAND messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ENCRYPTION COMMAND

2003.
TO BTS
Unit
WHEN
Times
HANDOVER DETECTION
messages
Definition
1926
Number of HANDOVER DETECTION messages
Description
During the outer incoming handover process controlled by MSC,

after MS receives handover command, then sends SABM frame to
BTS to initiate incoming handover. After receiving BTS sends HANDOVER DETCTION messages to notify BSC. This counter counts
the number of HANDOVER DETCTION messages of Abis interface
Usage
This counter is used to find out the frequency of HANDOVER DETCTION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives HANDOVER DETCTION

FIGURE 2004 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
MEASUREMENT RESULT
messages
Definition
Description
Number of MEASUREMENT RESULT messages

In general, MS reports a measurement report ( Um interface message MEASUREMENT messages) to BTS per 102/104 multi-frame
through SACCH channel, including DL measurement information
from 102/104 multi-frame. During the period BTS are also under
DL measurement. Therefore every 102/104 multi-frame, BTS will
combine these two information together, send to BSC through Abis
message MEASUREMENT RESULT.
For some reasons, BTS does not receive the MS measurement
report on time, only put its UL measurement results into this
MEASUREMENT RESULTS messages to send to BSC. This counter
counts the number of MEASUREMENT RESULTS messages of Abis
interface messages received by BSC.
Usage
This counter is used to find out the frequency of MEASUREMENT

RESULTS messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives MEASUREMENT RESULTS messages. The measurement point is A, as shown in Figure
2005.
1927
FIGURE 2005 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
MODE MODIFY REQUEST
messages
Definition
Number of MODE MODIFY REQUEST messages
Description
During the allocation or inner handover process, when the channel type of allocation and current type are in agreement but the
channel modes are different, BSC sends MODE MODIFY REQUEST
messages to BTS to notify to change channel mode. This counter
counts the number of MODE MODIFY REQUEST messages of Abis
interface messages sent by BSC.
Usage
This counter is used to find out the frequency of MODE MODIFY

REQUEST messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends MODE MODIFY REQUEST

2006.
TO BTS
Unit
1928
WHEN
Times
MODE MODIFY ACK
messages
Definition
Number of MODE MODIFY ACK messages
Description
After BTS receives MODE MODIFY ACK messages, finish channel

mode change. Then BTS sends MODE MODIFY ACK messages to
BSC as reply. This counter counts the number of MODE MODIFY
ACK messages of Abis interface messages received by BSC.
Usage

ACK messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives MODE MODIFY ACK

FIGURE 2007 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
MODE MODIFY NACK
messages
Definition
Number of MODE MODIFY NACK messages
Description
After BTS receives MODE MODIFY REQUEST messages, it is impossible to finish channel mode change due to certain reason, it
will send MODE MODIFY NACK messages to BSC as reply. This
counter counts the number of MODE MODIFY NACK messages of
Usage

NACK messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives MODE MODIFY NACK

1929
FIGURE 2008 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
PHYSICAL CONTEXT
REQUEST messages
Definition
Number of PHYSICAL CONTEXT REQUEST messages
Description
When BSC needs to know the current channel of MS (physical context), it sends PHYSICAL CONTEXT REQUEST messages to BTS to
apply. This counter counts the number of PHYSICAL CONTEXT REQUEST messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of PHYSICAL CONTEXT REQUEST messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends PHYSICAL CONTEXT REQUEST messages to BTS. The measurement point is A, as shown
in Figure 2009.
TO BTS
Unit
1930
WHEN
Times
PHYSICAL CONTEXT
CONFIRM messages
Definition
Number of PHYSICAL CONTEXT CONFIRM messages
Description
After BTS receives PHYSICAL CONTEXT REQUEST messages, report to BSC about related physical context through PHYSICAL CONTEXT COMFIRM messages. This counter counts the number of
PHYSICAL CONTEXT COMFIRM messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of PHYSICAL CONTEXT COMFIRM messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives PHYSICAL CONTEXT

COMFIRM messages to BTS. The measurement point is A, as shown
in Figure 2010.
FIGURE 2010 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
RF CHANNEL RELEASE
messages
Definition
Number of RF CHANNEL RELEASE messages
Description
When the certain logical channel is not used, BSC needs to notify BTS to release the channel. Therefore it sends RF CHANNEL
RELEASE messages to BTS. This counter counts the number of RF
CHANNEL RELEASE messages of Abis interface messages received
by BSC.
Usage
This counter is used to find out the frequency of RF CHANNEL RELEASE messages transmitting on Abis interface.
1931
Measurement
Point
This counter increments when BSC sends RF CHANNEL RELEASE

2011.
TO BTS
Unit
WHEN
Times
MS POWER CONTROL
messages
Definition
Number of MS POWER CONTROL messages
Description
BSC can calculate the proper transmitting power used by MS according to measurement data result. Therefore it notify control
parameters to BTS through MS POWER CONTROL messages. BTS
sends the information to MS through L1 frame header of SACCH,
then finish MS POWER CONTROL ultimately. This counter counts
the number of MS POWER CONTROL messages of Abis interface
messages sent by BSC.
Usage
This counter is used to find out the frequency of MS POWER CONTROL messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends MS POWER CONTROL

2012.
TO BTS
1932
WHEN
Unit
Times
BS POWER CONTROL
messages
Definition
Number of BS POWER CONTROL messages
Description
BSC can calculate the proper transmitting power used by BTS side
according to measurement data result. Therefore it notifies control parameters to BTS through BS POWER CONTROL messages.
BTS conducts the corresponding transmission power adjustment
work immediately. This counter counts the number of BS POWER
CONTROL messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of BS POWER CONTROL messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends BS POWER CONTROL

2013.
TO BTS
Unit
WHEN
Times
C901280028 Number
of PREPROCESSED
CONFIGURE messages
Definition
Description
Number of PREPROCESSED CONFIGURE messages

In order to reduce the load of processed measurement report of
BSC and the messages flux of Abis interface, the process of preprocessed measurement report can be used. First BTS processes the
1933
102/104 multi-frame measurement data (average), then sends

the processed result to BSC at lower frequency.
To make BTS conduct preprocessed measurement report, first
BSC sends PREPROCESSED CONFIGURE messages to BTS. The
message includes some basic control parameters being processed.
This counter counts the number of PREPROCESSED CONFIGURE
messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of PREPROCESSED

CONFIGURE messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends PREPROCESSED CONFIGURE messages to BTS. The measurement point is A, as shown
in Figure 2014.
TO BTS
Unit
WHEN
Times
C901280029 Number
of PREPROCESSED
MEASUREMENT RESULT
messages
Definition
1934
Number of PREPROCESSED MEASUREMENT RESULT messages
Description
After BTS receives PREPROCESSED CONFIGURE messages, it

begins to preprocess the measurement report, sends the preprocessed result to BSC through PREPROCESSED MEASUREMENT
RESULT messages. This counter counts the number of PREPROCESSED MEASUREMENT RESULT messages of Abis interface
Usage
This counter is used to find out the frequency of PREPROCESSED

MEASUREMENT RESULT messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives PREPROCESSED MEASUREMENT RESULT messages to BTS. The measurement point is
FIGURE 2015 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
C901280030 Number of RF
CHANNEL RELEASE ACK
messages
Definition
Number of RF CHANNEL RELEASE ACK messages
Description
After BTS receives RF CHANNEL RELEASE messages and releases

this channel, returns one RF CHANNEL RELEASE ACK messages
to BSC. This counter counts the number of RF CHANNEL RELEASE
ACK messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of RF CHANNEL RELEASE ACK messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives RF CHANNEL RELEASE

ACK messages to BTS. The measurement point is A, as shown in
Figure 2016.
FIGURE 2016 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1935
SACCH INFO MODIFY
messages
Definition
Number of SACCH INFO MODIFY messages
Description
On the DL direction of SACCH, BTS will send RR message

SI5/5bis/5ter/6 of Um interface to MS repeatedly, besides informing power control parameters and the latest time advance of L1
frame header to MS. When BSC want to modify related message
on one SACCH, send one SACCH INFO MODIFY messages to
BTS. The message includes RR message SI5/5bis/5ter/6 of new
Um interface. This counter counts the number of SACCH INFO
MODIFY messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of SACCH INFO MODIFY messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends SACCH INFO MODIFY

2017.
TO BTS
Unit
WHEN
Times
ABIS_PREPROC_ENH
ANCEMEAS_RESULT
messages
Definition
Description
1936
Number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages

This counter counts the number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages received by BSC.
Usage
This counter is used to find out the frequency of enhanced preprocessed measurement report message transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PREPROC_ENHANCEMEAS_RESULT messages. The measurement point is A, as
FIGURE 2018 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_ROUND_TRIP_DELA
Y_REPORT messages
Definition
Number of ABIS_ROUND_TRIP_DELAY_REPORT messages
Description
This counter counts the number of ABIS_ROUND_TRIP_DELAY_REPORT messages received by BSC.
Usage
This counter is used to find out the frequency of ROUND TRIP DELAY REPORT messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ROUND TRIP DELAY

REPORT messages. The measurement point is A, as shown in
Figure 2019.
FIGURE 2019 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1937
ABIS_PRE_HO_NOTIFY
messages
Definition
Number of ABIS_PRE_HO_NOTIFY messages
Description
This counter counts the number of ABIS_PRE_HO_NOTIFY messages received by BSC.
Usage
This counter is used to find out the frequency of PRE_HO_NOTIFY

Measurement
Point
This counter increments when BSC sends PRE-HANDOVER NOFICATION messages. The measurement point is A, as shown in
Figure 2020.
TO BTS
Unit
WHEN
Times
C901280035 Number
of ABIS_BCCH_INFO
messages
Definition
1938
Number of ABIS_BCCH_INFO messages
Description
When BSC want to messages sent on BCCH, it sends one BCCH

INFORMATION messages to BTS. The message includes complete
SI messages of RR lay of Um interface needed to be modified. This
counter counts the number of ABIS_BCCH_INFO messages sent by
BSC.
Usage
This counter is used to find out the frequency of BCCH changing

Measurement
Point
This counter increments when BSC sends BCCH INFOMATION messages. The measurement point is A, as shown in Figure 2021.

TO BTS
Unit
WHEN
Times
ABIS_CCCH_LOAD_IND
messages
Definition
Number of ABIS_CCCH_LOAD_IND messages
Description
When BSC checks one CCCH overload, it needs to send one CCCH
LOAD INDICATION message to BSC periodically to notify BSC. This
counter counts the number of ABIS_CCCH_LOAD_IND messages
received by BSC.
Usage
This counter is used to find out the frequency of CCCH load indication messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives CCCH LOAD INDICATION messages. The measurement point is A, as shown in Figure
2022.
FIGURE 2022 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1939
ABIS_CHL_RQD messages
Definition
Number of ABIS_CHL_RQD messages
Description
When BTS checks one random access of MS on RACH (CHANNEL

REQUEST of MS), it sends one CHANNEL REQUIRED message to
BSC, including valid messages of CHANNEL REQUEST. This counter
counts the number of ABIS_CHL_RDQ messages received by BSC.
Usage
This counter is used to find out the frequency of data indication

Measurement
Point
This counter increments when BSC receives CHANNEL REQUIRED

FIGURE 2023 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
C901280038 Number
of ABIS_DELETE_IND
messages
Definition
1940
Number of ABIS_DELETE_IND messages
Description
When BTS finds to delete one IMMEDIATE ASSIGN COMMAND

message due to DL congestion, it sends one DELETE INDICATION message to notify BSC. This counter counts the number of
ABIS_DELETE_IND messages received by BSC.
Usage
This counter is used to find out the frequency of DELETE INDICATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives DELETE INDICATION

FIGURE 2024 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
C901280039 Number
of ABIS_PAGING_CMD
messages
Definition
Number of ABIS_PAGING_CMD messages
Description
When BSC receives PADING message of BSSMAP protocol sent by

MSC from A-interface, it sends one PAGING COMMAND message
to BTS, including MS identity (TMSI or IMSI). BTS sends to MS
on PCH of radio interface through PAGING REQUEST. This counter
counts the number of ABIS_PAGING_CMD messages sent by BSC.
Usage
This counter is used to find out the frequency of PAGING COMMAND messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends PAGING COMMAND messages to BTS. The measurement point is A, as shown in Figure
2025.
TO BTS
Unit
Related Features
WHEN
Times
1941
ABIS_IMM_ASSIGN_CMD
messages
Definition
Description
Number of ABIS_IMM_ASSIGN_CMD messages

After BSC receives MS channel request, it tries for assigning one
channel accordingly and activates the channel, then sends one IMMEDIATE ASSIGN COMMAND message to BTS.
This message includes one complete Um interface RR layer IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED or
IMMEDIATE ASSIGNMENT REJECT (if there is no channel) to notify
MS.
After BTS receives this message, it is in charge of assigning Um
interface RR layer message of the message on CCCH to MS. This
counter counts the number of ABIS_IMM_ASSIGN_CMD messages
sent by BSC.
Usage
This counter is used to find out the frequency of IMMEDIATE ASSIGN COMMAND messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends IMMEDIATE ASSIGN

COMMAND messages to BTS. The measurement point is A, as
TO BTS
Unit
WHEN
Times
ABIS_SMS_BROADCAST_
REQ messages
Definition
Description
1942
Number of ABIS_SMS_BROADCAST_REQ messages

This counter counts the number of ABIS_SMS_BROADCAST_REQ
Usage
This counter is used to find out the frequency of SMS BROADCAST

Measurement
Point
This counter increments when BSC sends SMS BROADCAST REQUEST messages to BTS. The measurement point is A, as shown
in Figure 2027.
TO BTS
Unit
Related Features
WHEN
Times
ZGO-01-03-004 Cell Broadcast SMS
ABIS_SMS_BROADCAST_
CMD messages
Definition
Number of ABIS_SMS_BROADCAST_CMD messages
Description
This counter counts the number of ABIS_SMS_BROADCAST_CMD

Usage
This counter is used to find out the frequency of SMS BROADCAST

COMMAND messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends MS BROADCAST COMMAND messages to BTS. The measurement point is A, as shown
in Figure 2028.
TO BTS
WHEN
1943
Unit
Related Features
Times
ZGO-01-03-004 Cell Broadcast SMS
ABIS_CBCH_LOAD_IND
messages
Definition
Number of ABIS_CBCH_LOAD_IND messages
Description
When BTS checks CBCH over load or less than load, it sends CBCH
LOAD INDICATION message to notify BSC. This counter counts the
number of ABIS_CBCH_LOAD_IND messages sent by BSC.
Usage
This counter is used to find out the frequency of CBCH LOAD INDICATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives CBCH LOAD INDICATION messages to BTS. The measurement point is A, as shown in
Figure 2029.
FIGURE 2029 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_EGPRS_CHL_REQ
messages
Definition
1944
Number of ABIS_EGPRS_CHL_REQ messages
Description
This counter counts the number of ABIS_EGPRS_CHL_REQ messages sent by BSC.
Usage
This counter is used to find out the frequency of EGPRS_CHL_REQ

Measurement
Point
This counter increments when BSC receives ABIS_EGPRS_CHL_REQ messages. The measurement point is A, as shown
in Figure 2030.
FIGURE 2030 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_LOAD_CONTROL
messages
Definition
Number of ABIS_LOAD_CONTROL messages
Description
When BTS checks one CCCH overload, it needs to send CCCHLOAD

INDICATION message periodically to inform BSC. This counter
counts the number of ABIS_LOAD_CONTROL messages receives
by BSC.
Usage
This counter is used to find out the frequency of CCCHLOAD INDICATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives CCCHLOAD INDICATION messages. The measurement point is A, as shown in Figure
2031.
FIGURE 2031 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1945
ABIS_END_LOAD_CONT
ROL messages
Definition
Number of ABIS_END_LOAD_CONTROL messages
Description
This counter counts the number of ABIS_END_LOAD_CONTROL

Usage
This counter is used to find out the frequency of END LOAD CONTROL messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_END_LOAD_CONTROL messages to BTS. The measurement point is A, as shown in
Figure 2032.
TO BTS
Unit
WHEN
Times
ABIS_END_LOAD_CONTR
OL_ACK messages
Definition
1946
Number of ABIS_END_LOAD_CONTROL_ACK messages
Description
This counter counts the number of ABIS_END_LOAD_CONTROL_ACK messages received by BSC.
Usage
This counter is used to find out the frequency of END LOAD CONTROL RETURN messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_END_LOAD_CONTROL_ACK messages to BTS. The measurement point is A, as
FIGURE 2033 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PCCCH_LOAD_IND
messages
Definition
Number of ABIS_PCCCH_LOAD_IND messages
Description
This counter counts the number of PCCH flow control control command messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of PCCH flow control
control command messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PCCCH_LOAD_CONTROL_IND messages to BTS. The measurement
FIGURE 2034 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1947
ABIS_RF_RESRC_IND
messages
Definition
Number of ABIS_RF_RESRC_IND messages
Description
BTS sends RF RESOURCE INDICATION messages periodically to

inform BSC of interference on idle channel belonging to one TRX.
This counter counts the number of ABIS_RF_RESRC_ IND messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of RF RESOURCE

INDICATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives RF RESOURCE INDICATION messages. The measurement point is A, as shown in
Figure 2035.
FIGURE 2035 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_SACCH_FILLING
messages
Definition
1948
Number of ABIS_SACCH_FILLING messages
Description
When BSC modifies SI1/5bis/6/EXTENDED MEASUREMENT ORDER

message sent on SACCH, it sends one SACCH FILLING message to
BTS. This counter counts the number of SACCH FILLING INFORMATION CHANGE messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of SACCH FILLING

INFORMATION CHANGE messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends SACCH FILLING messages. The measurement point is A, as shown in Figure 2036.

TO BTS
Unit
WHEN
Times
C901280051 Number
of ABIS_OVERLOAD
messages
Definition
Number of ABIS_OVERLOAD messages
Description
This counter counts the number of flow control messages of Abis

interface messages received by BSC.
Usage
This counter is used to find out the frequency of flow control messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives overload messages.

FIGURE 2037 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1949
ABIS_ERROR_REPORT
messages
Definition
Number of ABIS_ERROR_REPORT messages
Description
When BTS check some errors but it is impossible to report to BSC

through other processes, it sends one ERROR REPORT message
to BSC. This counter counts the number of ABIS_ERROR_REPORT
Usage
This counter is used to find out the frequency of error report messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives error report messages. The measurement point is A, as shown in Figure 2038.
FIGURE 2038 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_SYSINFO_REQ
messages
Definition
1950
Number of ABIS_SYSINFO_REQ messages
Description
This counter counts the number of ABIS_SYSINFO_REQ messages

received by BSC.
Usage
This counter is used to find out the frequency of systems information requirement messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_SYSINFO_REQ

FIGURE 2039 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
C901280054 Number
of ABIS_SI_BC_END
messages
Definition
Number of ABIS_SI_BC_END messages
Description
This counter counts the number of ABIS_SI_BC_END indication

Usage
This counter is used to find out the frequency of systems information broadcast end indication messages transmitting on Abis
interface.
Measurement
Point
This counter increments when BSC sends ABIS_SI_BC_END messages to BTS. The measurement point is A, as shown in Figure
2040.
TO BTS
Unit
WHEN
Times
1951
ABIS_SI_NACK messages
Definition
Number of ABIS_SI_NACK messages
Description
This counter counts the number of ABIS_SI_NACK messages received by BSC.
Usage
This counter is used to find out the frequency of SI_NACK messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_SI_NACK messages to BTS. The measurement point is A, as shown in Figure
2041.
FIGURE 2041 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PWRCTRL_IND
messages
Definition
1952
Number of ABIS_PWRCTRL_IND messages
Description
This counter counts the number of ABIS_PWRCTRL_IND messages

received by BSC.
Usage
This counter is used to find out the frequency of POWER CONTROL

INDICATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PWRCTRL_IND

FIGURE 2042 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_SYSINFO_ACK
messages
Definition
Number of ABIS_SYSINFO_ACK messages
Description
This counter counts the number of ABIS_SYSINFO_ACK messages

received by BSC.
Usage
This counter is used to find out the frequency of SYSTEM INFORMATION ACKNOWLEDGE messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_SYSINFO_ACK

FIGURE 2043 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1953
ABIS_PACKET_PBCCH_
INF messages
Definition
Number of ABIS_PACKET_PBCCH_INF messages
Description
This counter counts the number of ABIS_PACKET_PBCCH_INF

Usage
This counter is used to find out the frequency of PACKET PBCCH

INFORMATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_PACKET_PBCCH_INF messages. The measurement point is A, as shown in Figure
2044.
TO BTS
Unit
WHEN
Times
ABIS_PACKET_CCCH_P
ARA messages
Definition
1954
Number of ABIS_PACKET_CCCH_PARA messages
Description
This counter counts the number of ABIS_PACKET_CCCH_PARA

Usage
This counter is used to find out the frequency of CCCH INFORMATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_PACKET_CCCH_PARA messages. The measurement point is A, as shown in Figure
2045.

TO BTS
Unit
WHEN
Times
ABIS_PACKET_PBCCH_P
ARA messages
Definition
Number of ABIS_PACKET_PBCCH_PARA messages
Description
This counter counts the number of ABIS_PACKET_PBCCH_PARA

Usage
This counter is used to find out the frequency of PBCCH PATAMETER messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_PACKET_PBCCH_

PARA messages to BTS. The measurement point is A, as shown in
Figure 2046.
TO BTS
Unit
WHEN
Times
1955
ABIS_PACKET_CHN_REQ
messages
Definition
Number of ABIS_PACKET_CHN_REQ messages
Description
This counter counts the number of ABIS_PACKET_CHN_REQ messages received by BSC.
Usage
This counter is used to find out the frequency of UL PACKET CHANNEL REQUIREMENT messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PACKET_CHN_

REQ messages to BTS. The measurement point is A, as shown in
Figure 2047.
FIGURE 2047 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PACKET_PAGING_
CMD messages
Definition
1956
Number of ABIS_PACKET_PAGING_CMD messages
Description
This counter counts the number of ABIS_PACKET_PAGING_CMD

Usage
This counter is used to find out the frequency of PACKET PAGING

Measurement
Point
This counter increments when BSC sends ABIS_PACKET_PAGING_CMD messages to BTS. The measurement point is A, as

TO BTS
Unit
Related Features
WHEN
Times
ABIS_PACKET_IMM_ASSI
GN_CMD messages
Definition
Number of ABIS_PACKET_IMM_ASSIGN_CMD messages
Description
This counter counts the number of PACKET IMMEDIATE ASSIGNMENT messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of PACKET IMMEDIATE ASSIGNMENT messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_PACKET_IMM_ASSIGN_CMD messages to BTS. The measurement point is A, as
TO BTS
Unit
WHEN
Times
1957
ABIS_PACKET_CONNECT
_FAIL_IND messages
Definition
Number of ABIS_PACKET_CONNECT_FAIL_IND messages
Description
This counter counts the number of PACKET CONNECT FAILURE INDICATION messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of PACKET CONNECT

FAILURE INDICATION messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PACKET_CONNECT_FAIL_IND messages to BTS. The measurement point is A,
FIGURE 2050 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PACKET_PRACH_O
VERLOAD messages
Definition
1958
Number of ABIS_PACKET_PRACH_OVERLOAD messages
Description
This counter counts the number of PRACH OVERLOAD messages

of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of PRACH OVERLOAD

Measurement
Point
This counter increments when BSC receives ABIS_PACKET_PRACH_OVERLOAD messages. The measurement point is A, as shown
in Figure 2051.
FIGURE 2051 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PACKET_PCH_OVE
RLOAD messages
Definition
Number of ABIS_PACKET_PCH_OVERLOAD messages
Description
This counter counts the number of PCH OVERLOAD messages of

Usage
This counter is used to find out the frequency of PCH OVERLOAD

Measurement
Point
This counter increments when BSC receives ABIS_PACKET_PCH_

OVERLOAD messages. The measurement point is A, as shown in
Figure 2052.
FIGURE 2052 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1959
ABIS_PACKET_TA_REQU
EST messages
Definition
Number of ABIS_PACKET_TA_REQUEST messages
Description
This counter counts the number of TIME ADVANCE REQUEST messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of TIME ADVANCE

Measurement
Point
This counter increments when BSC sends ABIS_PACKET_TA_REQUEST messages. The measurement point is A, as shown in Figure
2053.
TO BTS
Unit
WHEN
Times
ABIS_PACKET_TA_REQU
EST_ACK messages
Definition
1960
Number of ABIS_PACKET_TA_REQUEST_ACK messages
Description
This counter counts the number of TIME ADVANCE REQUEST ACKNOWLEDGE messages of Abis interface messages received by
BSC.
Usage
This counter is used to find out the frequency of TIME ADVANCE

REQUEST ACKNOWLEDGE messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PACKET_TA_REQUEST_ACK messages. The measurement point is A, as shown in
Figure 2054.
FIGURE 2054 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PACKET_CHN_CON
FIG_CHG messages
Definition
Number of ABIS_PACKET_CHN_CONFIG_CHG messages
Description
This counter counts the number of CHANNEL CONFIGURATION

CHANGE messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of CHANNEL CONFIGURATION CHANGE messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_PACKET_CHG_CONFIG_CHG messages. The measurement point is A, as shown in
Figure 2055.
TO BTS
Unit
WHEN
Times
1961
ABIS_PACKET_CHN_CON
FIG_CHG_RESP messages
Definition
Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages
Description
This counter counts the number of CHANNEL CONFIGURATION

CHANGE RESPONSE messages of Abis interface messages received
by BSC.
Usage
This counter is used to find out the frequency of CHANNEL CONFIGURATION CHANGE RESPONSE messages transmitting on Abis
interface.
Measurement
Point
This counter increments when BSC receives ABIS_PACKET_CHG_CONFIG_CHG_RESP messages. The measurement point is A, as
FIGURE 2056 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PACKET_PIA_DEL_
IND messages
Definition
1962
Number of ABIS_PACKET_PIA_DEL_IND messages
Description
This counter counts the number of IMMEDIATE ASSIGNMENT

TRANSMISSION FAILURE INDICATION messages of Abis interface
Usage
This counter is used to find out the frequency of IMMEDIATE

ASSIGNMENT TRANSMISSION FAILURE INDICATION messages
transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PACKET_PIA_DEL_IND messages. The measurement point is A, as shown in
Figure 2057.
FIGURE 2057 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PACKET_SEND_PIA
_IND messages
Definition
Number of ABIS_PACKET_SEND_PIA_IND messages
Description
This counter counts the number of IMMEDIATE ASSIGNMENT

TRANSMISSION SUCCESS INDICATION messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of IMMEDIATE

ASSIGNMENT TRANSMISSION SUCCESS INDICATION messages
transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PACKET_SEND_PIA_IND messages. The measurement point is A, as shown in
Figure 2058.
FIGURE 2058 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1963
ABIS_PACKET_CHN_CON
FIG_REQ messages
Definition
Number of ABIS_PACKET_CHN_CONFIG_REQ messages
Description
This counter counts the number of PS PARAMETER CONFIGURATION REQUEST messages of Abis interface messages received by
BSC.
Usage
This counter is used to find out the frequency of PS PARAMETER

CONFIGURATION REQUEST messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PACKET_CHN_

CONFIG_REQ messages. The measurement point is A, as shown
in Figure 2059.
FIGURE 2059 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_EGPRS_PACKET_C
HN_REQ messages
Definition
1964
Number of ABIS_EGPRS_PACKET_CHN_REQ messages
Description
This counter counts the number of UL EGPRS PACKET REQUEST

Usage
This counter is used to find out the frequency of UL EGPRS PACKET

Measurement
Point
This counter increments when BSC receives ABIS_EGPRS_PACKET

_CHN_REQ messages. The measurement point is A, as shown in
Figure 2060.
FIGURE 2060 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PS_CHANNEL_ACT
IVE messages
Definition
Number of ABIS_PS_CHANNEL_ACTIVE messages
Description
This counter counts the number of PS CHANNEL ACTIVE COMMAND

Usage
This counter is used to find out the frequency of PS CHANNEL ACTIVE COMMAND messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_PS_CHANNEL _ACTIVE messages. The measurement point is A, as shown in Figure
2061.
TO BTS
Unit
WHEN
Times
1965
ABIS_PS_CHANNEL_ACTI
VE_ACK messages
Definition
Number of ABIS_PS_CHANNEL_ACTIVE_ACK messages
Description
This counter counts the number of PS CHANNEL ACTIVE ACKNOWLEDGEMENT COMMAND messages of Abis interface
Usage
This counter is used to find out the frequency of PS CHANNEL ACTIVE ACKNOWLEDGEMENT COMMAND messages transmitting on
Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PS_CHANNEL

_ACTIVE_ACK messages. The measurement point is A, as shown
in Figure 2062.
FIGURE 2062 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PS_CHANNEL_ACTI
VE_NACK messages
Definition
1966
Number of ABIS_PS_CHANNEL_ACTIVE_NACK messages
Description
This counter counts the number of PS CHANNEL ACTIVE UNACKNOWLEDGEMENT COMMAND messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of PS CHANNEL ACTIVE UNACKNOWLEDGEMENT COMMAND messages transmitting
on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PS_CHANNEL

_ACTIVE_NACK messages. The measurement point is A, as shown
in Figure 2063.
FIGURE 2063 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PS_CHANNEL_RELE
ASE messages
Definition
Number of ABIS_PS_CHANNEL_RELEASE messages
Description
This counter counts the number of PS CHANNEL RELEASE COMMAND messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of PS CHANNEL RELEASE COMMAND messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_PS_CHANNEL_RELEASE messages to BTS. The measurement point is A, as shown
in Figure 2064.
TO BTS
Unit
WHEN
Times
1967
ASE_ACK messages
Definition
Number of ABIS_PS_CHANNEL_RELEASE_ACK messages
Description
This counter counts the number of PS CHANNEL RELEASE ACKNOWLEDGEMENT COMMAND messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of PS CHANNEL RELEASE ACKNOWLEDGEMENT COMMAND messages transmitting on
Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PS_CHANNEL_RELEASE_ACK messages. The measurement point is A, as
FIGURE 2065 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ASE_NACK messages
Definition
1968
Number of ABIS_PS_CHANNEL_RELEASE_NACK messages
Description
This counter counts the number of PS CHANNEL RELEASE UNACKNOWLEDGEMENT COMMAND messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of PS CHANNEL RELEASE UNACKNOWLEDGEMENT COMMAND messages transmitting
on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PS_CHANNEL_RELEASE_NACK messages. The measurement point is A, as
FIGURE 2066 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PSCONN_CMM_
REQ messages
Definition
Number of ABIS_PSCONN_CMM_REQ messages
Description
This counter counts the number of PS CONNECTION COMMAND

Usage
This counter is used to find out the frequency of PS CONNECTION

Measurement
Point
This counter increments when BSC sends ABIS_PSCONN_CMM_

Figure 2067.
TO BTS
Unit
WHEN
Times
1969
ABIS_PSCONN_CMM_ACK
messages
Definition
Number of ABIS_PSCONN_CMM_ACK messages
Description
This counter counts the number of PS CONNECTION SUCCESS

COMMAND ACKNOWLEDGEMENT messages of Abis interface messages sent by BSC.
Usage

SUCCESS COMMAND ACKNOWLEDGEMENT messages transmitting
on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PSCONN_CMM_ACK messages. The measurement point is A, as shown in Figure
2068.
FIGURE 2068 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PSCONN_CMM_N
ACK messages
Definition
1970
Number of ABIS_PSCONN_CMM_NACK messages
Description
This counter counts the number of PS CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages of Abis interface messages
sent by BSC.
Usage

FAILURE COMMAND ACKNOWLEDGEMENT messages transmitting
on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_PSCONN_CMM_

NACK messages. The measurement point is A, as shown in Figure
2069.
FIGURE 2069 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_GLOBAL_RESET
messages
Definition
Number of ABIS_GLOBAL_RESET messages
Description
This counter counts the number of GLOBAL RESET COMMAND messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of GLOBAL RESET

Measurement
Point
This counter increments when BSC sends ABIS_GLOBAL_RESET

2070.
TO BTS
Unit
WHEN
Times
1971
ABIS_GLOBAL_RESET_
ACK messages
Definition
Number of ABIS_GLOBAL_RESET_ACK messages
Description
This counter counts the number of GLOBAL RESET ACKNOWLEDGEMENT COMMAND messages of Abis interface messages sent
by BSC.
Usage

ACKNOWLEDGEMENT COMMAND messages transmitting on Abis
interface.
Measurement
Point
This counter increments when BSC receives ABIS_GLOBAL_RESET_ACK messages. The measurement point is A, as shown in
Figure 2071.
FIGURE 2071 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_GLOBAL_RESET_N
ACK messages
Definition
1972
Number of ABIS_GLOBAL_RESET_NACK messages
Description
This counter counts the number of GLOBAL RESET UNACKNOWLEDGEMENT COMMAND messages of Abis interface messages sent
by BSC.
Usage

UNACKNOWLEDGEMENT COMMAND messages transmitting on
Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_GLOBAL_RESET_NACK messages. The measurement point is A, as shown in
Figure 2072.
FIGURE 2072 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_PACKET_UP_ASS
IGN messages
Definition
Number of ABIS_PACKET_UP_ASSIGN messages
Description
This counter counts the number of PS UL ASSIGNMENT COMMAND

Usage
This counter is used to find out the frequency of PS UL ASSIGNMENT COMMAND messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_PACKET_UP_ASSIGN messages to BTS. The measurement point is A, as shown in
Figure 2073.
TO BTS
Unit
WHEN
Times
1973
ABIS_PACKET_DOWN_AS
SIGN messages
Definition
Number of ABIS_PACKET_DOWN_ASSIGN messages
Description
This counter counts the number of PS DL ASSIGNMENT COMMAND

Usage
This counter is used to find out the frequency of PS DL ASSIGNMENT COMMAND messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_PACKET_DOWN_

ASSIGN messages to BTS. The measurement point is A, as shown
in Figure 2074.
TO BTS
Unit
WHEN
Times
ABIS_CSCONN_CMM_
REQ messages
Definition
1974
Number of ABIS_CSCONN_CMM_REQ messages
Description
This counter counts the number of CS CONNECTION COMMAND

Usage
This counter is used to find out the frequency of CS CONNECTION

Measurement
Point
This counter increments when BSC sends ABIS_CSCONN_CMM_

Figure 2075.

TO BTS
Unit
WHEN
Times
ABIS_CSCONN_CMM_
ACK messages
Definition
Number of ABIS_CSCONN_CMM_ACK messages
Description
This counter counts the number of CS CONNECTION SUCCESS

COMMAND ACKNOWLEDGEMENT messages of Abis interface messages received by BSC.
Usage

on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_CSCONN_CMM_ACK messages. The measurement point is A, as shown in Figure
2076.
FIGURE 2076 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1975
ABIS_CSCONN_CMM_N
ACK messages
Definition
Number of ABIS_CSCONN_CMM_NACK messages
Description
This counter counts the number of CS CONNECTION FAILURE

COMMAND ACKNOWLEDGEMENT messages of Abis interface
Usage

on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_CSCONN_CMM_

NACK messages. The measurement point is A, as shown in Figure
2077.
FIGURE 2077 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
ABIS_CCMCONN_CMM_
REQ messages
Definition
1976
Number of ABIS_CCMCONN_CMM_REQ messages
Description
This counter counts the number of CCM CONNECTION COMMAND

Usage
This counter is used to find out the frequency of CCM CONNECTION

Measurement
Point
This counter increments when BSC sends ABIS_CCMCONN_CMM_REQ messages to BTS. The measurement point is A,

TO BTS
Unit
WHEN
Times
ABIS_CCMCONN_CMM_
ACK messages
Definition
Number of ABIS_CCMCONN_CMM_ACK messages
Description
This counter counts the number of CCM CONNECTION SUCCESS

Usage

on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_CCMCONN_CMM_ACK messages. The measurement point is A, as
FIGURE 2079 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
1977
ABIS_CCMCONN_CMM_N
ACK messages
Definition
Number of ABIS_CCMCONN_CMM_NACK messages
Description
This counter counts the number of CCM CONNECTION FAILURE

Usage

on Abis interface.
Measurement
Point
This counter increments when BSC receives ABIS_CCMCONN_CMM_NACK messages. The measurement point is A, as
FIGURE 2080 BTS
Unit
ABIS
MESSAGE TO
BSC
Times
C901280098 Number ABIS

_PACKET_ACCESS_REJ
messages
Definition
1978
Number ABIS_PACKET_ACCESS_REJ messages
Description
This counter counts the number of PS ACCESS REJECT messages

of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of PS ACCESS REJECT messages transmitting on Abis interface.
Measurement
Point
This counter increments when BSC sends ABIS_PACKET_ACCESS_REJ messages to BSC. The measurement point is A, as

TO BTS
Unit
WHEN
Times
ABIS_PACKET_IMM_ASSI
GN_CMD_NEW messages
Definition
Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages
Description
This counter counts the number of new packet immediate assignment messages in the Abis interface messages sent by BSC.
Usage
The counter is used to find out the frequency of new packet immediate assignment messages transmitted at Abis interface.
Measurement
Point
When BSC sends the ABIS_PACKET_IMM_ASSIGN_CMD_NEW

message to BTS, the counter increments. The measurement point
TO BTS
Unit
WHEN
Times
1979
PACKET_DOWNLINK_ASS
IGN messages
Definition
Number of PACKET_DOWNLINK_ASSIGN messages
Description
This counter counts the number of packet downlink assignment

messages in the Abis interface messages sent by BSC.
Usage
The counter is used to find out the frequency of packet downlink

assignment messages transmitted at Abis interface.
Measurement
Point
When BSC sends the PACKET_DOWNLINK_ASSIGN message to

TO BTS
Unit
WHEN
Times
PACKET_UPLINK_ASSIGN
messages
Definition
1980
Number of PACKET_UPLINK_ASSIGN messages
Description
This counter counts the number of packet uplink assignment messages in the Abis interface messages sent by BSC.
Usage
The counter is used to find out the frequency of packet uplink assignment messages transmitted at Abis interface.
Measurement
Point
When BSC sends the PACKET_UPLINK_ASSIGN message to BTS,

Figure 2084.

TO BTS
Unit
WHEN
Times
ABIS_PACKET_ACCESS_
REJ_NEW messages
Definition
Number of ABIS_PACKET_ACCESS_REJ_NEW messages
Description
This counter counts the number of new PS access reject messages

in the Abis interface messages sent by BSC.
Usage
The counter is used to find out the frequency of new PS access

reject messages transmitted at Abis interface.
Measurement
Point
When BSC sends the ABIS_PACKET_ACCESS_REJ_NEW message

to BTS, the counter increments. The measurement point is A, as
TO BTS
Unit
WHEN
Times
1981
1982
Chapter
35
Gb Message Statistics
(BVC Cell)
Table of Contents
Overview...................................................................... 1984
BSSGP level.................................................................. 1984
BSSGP level.................................................................. 1985
C901290003 Number of RA-CAPABILITY message received.......................................................................... 1986
BSC ............................................................................. 1986
BSC ............................................................................. 1987
sent............................................................................. 1987
C901290008 Number of Wireless Status PDU messages sent
by BSC......................................................................... 1989
C901290009 Number of Wireless Status messages sent by
BSC due to Losing Wireless Association with MS ................ 1989
BSC due to Bad Link Quality ........................................... 1990
C901290011 Number of Wireless status messages sent by
BSC due to Cell reselection command............................... 1990
by BSC......................................................................... 1991
received by BSC ............................................................ 1991
by BSC......................................................................... 1992
received by BSC ............................................................ 1993
by BSC......................................................................... 1993
received by BSC ............................................................ 1994
C901290018 Number of Status messages sent by BSC......... 1995
C901290019 Number of Status messages received by
BSC ............................................................................. 1995
C901290020 Number of Status messages sent with BVCI Unknown ......................................................................... 1996
C901290021 Number of Status messages sent with Cell service congestion ............................................................. 1996
1983
C901290022 Number of Status messages sent with protocol

error............................................................................ 1997
C901290023 Number of Status messages sent with Processor
overload....................................................................... 1997
C901290024 Number of Status messages received with BVCI
Unknown...................................................................... 1997
C901290025 Number of Status messages received with Cell
C901290026 Number of Status messages received with protocol error .................................................................... 1998
C901290027 Number of Status messages received with Processor overload ............................................................. 1998
by BSC......................................................................... 1999
sent by BSC.................................................................. 2000
sent by BSC.................................................................. 2001
BSC ............................................................................. 2001
by BSC......................................................................... 2003
C901290035 Number of DELETE -BSS-PFC-ACK messages
sent by BSC.................................................................. 2003
C901290036 Number of DELETE -BSS-PFC-REQ messages received by BSC............................................................... 2004
Overview
Gb message statistics mainly measures transmission number of
different PTP messages at Gb BSSGP level in GPRS service (such
as RA-CAPABILITY, RADIO-STATUS, DOWNLOAD-BSS-PFC).
The measurement takes BVC cell as the statistics unit.
UNITDATA messages
Definition
1984
Sum of UL UNITDATA messages handled at BSSGP level
Description
This counter counts the number of sending UL-UNITDATA PDU to

SGSN by BSC.
Measurement
Point
When BSC sends a UL-UNITDATA message, this counter increments. The measurement point is A, as shown in Figure 2086.
Chapter 35 Gb Message Statistics (BVC Cell)
FIGURE 2086 MEASUREMENT POINT OF SUM OF

Unit
UL UNITDATA
MESSAGE
Times
UNITDATA messages
Definition
Sum of DL UNITDATA messages handled at BSSGP level
Description
SGSN sends DL-UNITDATA PDU to BSC, and this counter counts

Measurement
Point
When BSC receives a DL-UNITDATA message, this counter increments. The measurement point is A, as shown in Figure 2087.
Unit
POINT OF SUM OF
DL UNITDATA
MESSAGE
Times
1985
RA-CAPABILITY message
received
Definition
Number of RA-CAPABILITY message received
Description
SGSN sends RA-CAPABILITY message to BSC, to indicate wireless

capability of MS. This counter counts the number of receiving this
message.
Measurement
Point
When BSC receives a RA-CAPABILITY message, this counter increments. The measurement point is A, as shown in Figure 2088.
POINT OF THE NUMBER OF
RA-CAPABILITY
MESSAGE RECEIVED
Unit
Times
by BSC
Definition
1986
Number of PTP packet paging received by BSC
Description
SGSN sends PTP packet paging message, to indicate BSC originate

PTP packet paging for MS. This counter counts the number of receiving this message by BSC.
Measurement
Point
Unit
Times
by BSC
Definition
Number of PTP circuit paging received by BSC
Description
SGSN sends PTP circuit paging message, to indicate BSC originate

PTP circuit paging for MS. This counter counts the number of receiving this message by BSC.
Measurement
Point
When BSC receives a PAGING CS message, this counter increments. The measurement point is A, as shown in Figure 2090.
Unit
Times
message sent
Definition
Number of RA-CAPABILITY-UPDATE message sent
1987
Description
SGSN sends RA-CAPABILITY-UPDATE message to SGSN, to indicate current wireless capability of MS. This counter counts the
number of sending this message by BSC.
Measurement
Point

in Figure 2091.
Unit
Times
Definition
Number of RA-CAPABILITY-UPDATE-ACK message received
Description
SGSN sends RA-CAPABILITY-UPDATE-ACK message to BSC, to indicate current wireless capability of MS. This counter counts the
Measurement
Point
When BSC sends a RA-CAPABILITY-UPDATE-ACK message from

SGSN, this counter increments. The measurement point is A2, as
Unit
1988
Times
C901290008 Number
of Wireless Status PDU
Definition
Description
Usage
Measurement
Point
Number of Wireless Status PDU messages sent by BSC

BSC sends wireless status PDU message, to indicate exception at
SGSN radio interface. This counter counts the number of sending
View the status at radio interface by counting this message.
Figure 2093.
Unit
Times
Wireless Status messages
sent by BSC due to Losing
Wireless Association with
MS
Definition
Number of Wireless Status messages sent by BSC due to Losing

Wireless Association with MS
Description
BSC sends wireless status message, to indicate exception occurred

at SGSN radio interface. This counter counts the number of sending this message by BSC due to Losing wireless association with
MS.
Usage
Measurement
Point

When BSC sends a RADIO-STATUS message due to Losing wireless association with MS, this counter increments.
1989
Unit
Times
sent by BSC due to Bad Link
Quality
Definition
Number of wireless status messages sent by BSC due to Bad Link

Quality
Description

at SGSN radio interface. This counter counts the number of sending this message by BSC due to bad link quality.
Usage
Measurement
Point
Unit

Times
Wireless status messages
sent by BSC due to Cell
reselection command
Definition
Number of Wireless status messages sent by BSC due to Cell reselection command
Description

at SGSN radio interface. This counter counts the number of sending this message by BSC due to cell reselection command.
Usage
Measurement
Point
Unit
1990

Times
FLOW-CONTROL-BVC
Definition
Number of FLOW-CONTROL-BVC messages sent by BSC
Description
BSC sends FLOW-CONTROL-BVC message to notify SGSN of flow

control policy for current BVC. This counter counts the number of
Measurement
Point

increments, as A1 measurement position shown in Figure 2094.
Unit
Times
BSC
Definition
Number of FLOW-CONTROL-BVC-ACK messages received by BSC
Description
BSC sends FLOW-CONTROL-BVC-ACK message to notify BSC of

accepted flow control policy for current BVC. This counter counts
Measurement
Point

Figure 2095.
1991
Unit
Times
FLOW-CONTROL-MS
Definition
Number of FLOW-CONTROL-MS messages sent by BSC
Description
BSC sends FLOW-CONTROL- MS message to notify SGSN of flow

control policy for current MS. This counter counts the number of
Measurement
Point
When BSC sends a FLOW-CONTROL-MS message, this counter

2096.
Unit
1992
Times
FLOW-CONTROL-MS-ACK
Definition
Number of FLOW-CONTROL-MS-ACK messages received by BSC
Description
BSC sends FLOW-CONTROL-MS-ACK message to notify BSC of accepted flow control policy for current MS. This counter counts the
Measurement
Point

Figure 2097.
Unit
Times
FLOW-CONTROL-PFC
Definition
Number of FLOW-CONTROL- PFC messages sent by BSC
Description
BSC sends FLOW-CONTROL-PFC message to notify SGSN of flow

control policy for one or more PFC for designated MS. This counter
counts the number of sending this message by BSC.
Measurement
Point
When BSC sends a FLOW-CONTROL-PFC message, this counter

2098.
1993
Unit
Times
BSC
Definition
Number of FLOW-CONTROL-PFC-ACK messages received by BSC
Description
BSC sends FLOW-CONTROL-PFC-ACK message to notify BSC of

accepted PFC flow control policy for designated MS. This counter
counts the number of receiving this message by BSC.
Measurement
Point

Figure 2099.
Unit
1994
Times
Status messages sent by
BSC
Definition
Number of Status messages sent by BSC
Description
by BSC.
Measurement
Point
When BSC sends a STATUS message, this counter increments.

Unit
Times
Status messages received
by BSC
Definition
Number of Status messages received by BSC
Description
by BSC.
Measurement
Point
When BSC receives a STATUS message, this counter increments.

1995
Unit
Times
BVCI Unknown
Definition
Number of Status messages sent with BVCI Unknown
Description
Measurement
Point
When BSC sends a STATUS message due to BVCI Unknown, this

counter increments.
Unit
Times
Cell service congestion
Definition
Description
Measurement
Point
When BSC sends a STATUS message due to cell service congestion, this counter increments.
Unit
1996
Number of Status messages sent with Cell service congestion
Times
protocol error
Definition
Number of Status messages sent with protocol error
Description
Measurement
Point
When BSC sends a STATUS message due to protocol error, this

counter increments.
Unit
Times
Processor overload
Definition
Number of Status messages sent with Processor overload
Description
Measurement
Point
When BSC sends a STATUS message due to processor overload,

Unit
Times
with BVCI Unknown
Definition
Number of Status messages received with BVCI Unknown
Description
Measurement
Point
When BSC receives a STATUS message due to BVCI Unknown,

Unit
Times
1997
with Cell service congestion
Definition
Number of Status messages received with Cell service congestion
Description
Measurement
Point
When BSC receives a STATUS message due to cell service congestion, this counter increments.
Unit
Times
with protocol error
Definition
Number of Status messages received with protocol error
Description
Measurement
Point
When BSC receives a STATUS message due to protocol error, this

counter increments.
Unit
Times
with Processor overload
Definition
Number of Status messages received with cause Processor overload
Description
Measurement
Point
When BSC receives a STATUS message due to processor overload, this counter increments.
Unit
1998
Times
DOWNLOAD-BSS-PFC
Definition
Number of DOWNLOAD-BSS-PFC messages sent by BSC
Description
BSC sends DOWNLOAD-BSS-PFC message, to request SGSN originate CREATE-BSS-PFC process. This counter counts the number
of sending this message by BSC.
Measurement
Point
When BSC sends a DOWNLOAD-BSS-PFC message, this counter

2102.
Unit
Times
BVCCREATE-BSS-PFC
Definition
Number of BVCCREATE-BSS-PFC messages received by BSC
Description
SGSN sends CREATE-BSS-PFC message to request BSC create or

modify a packet flow control context. This counter counts the number of receiving this message by BSC.
Measurement
Point

2103.
1999
Unit
Times
CREATE-BSS-PFC-ACK
Definition
Number of CREATE-BSS-PFC-ACK messages sent by BSC
Description
BSC sends CREATE-BSS-PFC-ACK message to affirm SGSN create

or modify a request of packet flow control context. This counter
Measurement
Point

2104.
2000
Unit
Times
CREATE-BSS-PFC-NACK
Definition
Number of CREATE-BSS-PFC-NACK messages sent by BSC
Description
BSC sends CREATE-BSS-PFC-NACK message to deny SGSN create

or modify a request of packet flow control context. This counter
Measurement
Point
When BSC sends a CREATE-BSS-PFC-NACK message, this

Figure 2105.
Unit
Times
C901290032 Number
of MODIFY-BSS-PFC
Definition
Description
Number of MODIFY-BSS-PFC messages sent by BSC

BSC sends MODIFY-BSS-PFC message to SGSN to request modify
packet flow control context. This counter counts the number of
2001
Measurement
Point
When BSC sends a MODIFY-BSS-PFC message, this counter increments. The measurement point is A1, as shown in Figure 2106.
Unit
Times
MODIFY-BSS-PFC-ACK
Definition
Number of MODIFY-BSS-PFC-ACK messages received by BSC
Description
SGSN sends MODIFY-BSS-PFC-ACK message to BSC to confirm the

modification of packet flow control context. This counter counts
Measurement
Point
When BSC receives a MODIFY-BSS-PFC-ACK message, this

Figure 2107.
Unit
2002
Times
C901290034 Number
of DELETE-BSS-PFC
Definition
Number of DELETE-BSS-PFC messages received by BSC
Description
SGSN sends DELETE-BSS-PFC message to request BSC delete a

packet flow control context. This counter counts the number of
receiving this message by BSC.
Measurement
Point
When BSC receives a DELETE-BSS-PFC message, this counter

2108.
Unit
Times
DELETE -BSS-PFC-ACK
Definition
Number of DELETE -BSS-PFC-ACK messages sent by BSC
Description
BSC sends DELETE-BSS-PFC-ACK message to SGSN to confirm the

deletion of packet flow control context. This counter counts the
number of sending this message by BSC.
Measurement
Point

2109.
2003
Unit
Times
DELETE -BSS-PFC-REQ
Definition
Description
2004
Number of DELETE-BSS-PFC-REQ messages received by BSC

Chapter
36
NSVC Statistic
Measurement
Table of Contents
Overview...................................................................... 2006
C901300001 Time of PVC unavailable............................... 2006
C901300002 Time of PVC congestion frame relay .............. 2007
C901300003 Time of PVC congestion of level 1.................. 2008
C901300004 Number of bytes received from SGSN ............ 2008
C901300005 Number of bytes sent to SGSN ..................... 2008
C901300006 Number of PDU data sent by NS sub layer......... 2009
layer............................................................................ 2010
layer............................................................................ 2010
C901300009 Number of reset messages send to opposite end
by NS sub layer............................................................. 2011
C901300010 Number of received reset messages sent by opposite end .................................................................... 2012
C901300011 Number of reset confirm messages send to opposite end by NS sub layer ............................................. 2012
C901300012 Number of received reset confirm messages
sent by opposite end...................................................... 2013
C901300013 Number of blocking messages send to opposite
end by NS sub layer....................................................... 2014
C901300014 Number of received blocking messages sent by
opposite end ................................................................. 2014
C901300015 Number of blocking confirm messages send to
opposite end by NS sub layer .......................................... 2015
C901300016 Number of received blocking confirm messages
sent by opposite end...................................................... 2016
C901300017 Number of unblocking messages send to opposite end by NS sub layer................................................. 2016
C901300018 Number of received unblocking messages sent
by opposite end ............................................................ 2017
C901300019 Number of unblocking confirm messages send
to opposite end by NS sub layer ...................................... 2018
C901300020 Number of received unblocking acknowledge
messages replied by opposite end.................................... 2018
C901300021 Number of abnormal cases in NS transmission
due to network fault ...................................................... 2019
due to O&M interference................................................. 2020
due to equipment fault ................................................... 2021
due to NSVC block ......................................................... 2021
2005

due to unknown NSVC.................................................... 2022
due to protocol error ...................................................... 2023
C901300027 Number of test failure (while over max) ......... 2023
C901300028 Number of blocking procedure failure (after exceeding the maximum times) .......................................... 2024
C901300029 Number of unblocking procedure failure (after
exceeding the maximum times)....................................... 2025
1................................................................................. 2026
C901300031 Number of congestion recovery of level 1......... 2026
2................................................................................. 2027
3................................................................................. 2027
C901300036 Number of BECN......................................... 2028
C901300037 Number of FECN ......................................... 2028
Overview
The NSVC statistic measurement is used to measure signaling interaction and data transmission at NS layer of Gb interface for
GPRS service. It counts the number of various messages, such as
blocking, unblocking, resetting, and ALIVE.
Statistic unit in this measurement is NSVC.
C901300001 Time of PVC

unavailable
Definition
2006
Time of PVC unavailable
Description
This counter counts the time during which NSVC can not be used
for data transmission.
Measurement
Point
The counter starts counting when NSVC link becomes abnormal

and stops counting when NSVC link becomes normal. The duration
between the two time points is the time during which NSVC is
unavailable.
Chapter 36 NSVC Statistic Measurement
FIGURE 2110 TIME OF PVC UNAVAILABLE
Unit
Second

congestion frame relay
Definition
Time of PVC congestion frame relay
Description
The time during which BECN in the data sent by SGSN is set is the
total time of PVC congestion bit being set. The counter counts the
total time of PVC congestion bit being set.
Measurement
Point
The counter starts counting when SGSN receives data in which

BECN is set and stops counting when BECN is not set. The duration
between the two time points is the total time of PVC congestion
bit being set.
FIGURE 2111 TIME OF PVC CONGESTION FRAME RELAY
Unit
Second
2007

congestion of level 1
Definition
Description
Time of PVC congestion of level 1

bytes received from SGSN
Definition
Description
Number of bytes received from SGSN

This counter counts the number of bytes received by NS sublayer
from SGSN.
This counter performs statistics for FR layer, and the statistic data
contains FR header.
Usage
Measurement
Point
The NSVC load can be checked through this counter.

FR accumulates the number of bytes received from Gb interface.
The measurement point is A1.
FIGURE 2112 UPLINK/DOWNLINK NS DATA
Unit
Byte
bytes sent to SGSN
Definition
Description
2008
Number of bytes sent to SGSN

This counter counts the number of bytes sent to SGSN from NS
sublayer.
contains FR header.
Usage
Measurement
Point

FR accumulates the number of bytes sent each time. The measurement point is A2.
FIGURE 2113 UPLINK/DOWNLINK NS DATA
Unit
Byte
PDU data sent by NS sub
layer
Definition
Description
Usage
Number of PDU data sent by NS sub layer

This counter counts the number of PDU data sent to SGSN from
NS sub layer.
The NSVC service load can be checked through this counter.
'
Measurement
Point
The counter increments each time BSC's FR sends a PDU data to

SGSN. The measurement point is A1.
FIGURE 2114 SENDING AND RECEIVING PDU DATA
Unit
Times
2009
PDU data received by NS
sub layer
Definition
Description
Usage
Number of PDU data received by NS sub layer

This counter counts the number of PDU data received by NS sub
layer from SGSN.
'
Measurement
Point
The counter increments each time BSC's FR receives a PDU data

from SGSN. The measurement point is A2.
FIGURE 2115 SENDING AND RECEIVING PDU DATA
Unit
Times
PDU data discarded by NS
sub layer
Definition
Description
Usage
Number of PDU data discarded by NS sub layer

The amount of PDU data discarded by NS sub layer is the sum of
incorrect PDU data received by NS sub layer from SGSN and PDU
data that FR fails to send.
'
Measurement
Point
2010
The counter increments when NS sub layer receives an illegal

PDU data.
The counter increments when FR fails to send a PDU data.
FIGURE 2116 PDU DATA DISCARDED BY NS SUB LAYER
Unit
Times
reset messages send to
opposite end by NS sub
layer
Definition
Description
Usage
Number of reset messages send to opposite end by NS sub layer

NS sub layer sends the NSVC resetting message to indicate SGSN
to reset specified NSVC. This counter counts the number of resetting messages sent to opposite end by NS sub layer.
The counter counts the number of BSC resetting specified NSVC.
'
Measurement
Point
Each time BSC sends the NS-RESET message, this counter increments. The measurement point is A1.
FIGURE 2117 NSVC RESETTING PROCESS
Unit
Times
2011
received reset messages
sent by opposite end
Definition
Number of received reset messages sent by opposite end
Description
SGSN sends the NSVC resetting message to indicate BSC to reset

specified NSVC. This counter counts the number of resetting messages received by BSC from the opposite end.
Usage
The counter counts the number of SGSN resetting specified NSVC.

'
Measurement
Point
Each time BSC receives the NS-RESET message, this counter

increments. The measurement point is A3.
Unit
Times
reset confirm messages
send to opposite end by NS
sub layer
2012
Definition
Number of reset confirm messages send to opposite end by NS

sub layer
Description
NS sub layer sends NSVC reset confirmation message to notify

SGSN that specified NSVC is reset. This counter counts the number of sending this message by BSC.
Measurement
Point
Each time BSC sends the NS-RESET-ACK message, this counter

Unit
Times
received reset confirm
messages sent by opposite
end
Definition
Number of received reset confirm messages sent by opposite end
Description
SGSN sends NSVC reset confirmation message to notify BSC that

specified NSVC is reset. This counter counts the number of BSC's
receiving this message.
Measurement
Point
Each time BSC receives the NS-RESET-ACK message, this

counter increments. The measurement point is A2.
Unit
Times
2013
blocking messages send
to opposite end by NS sub
layer
Definition
Number of blocking messages send to opposite end by NS sub

layer
Description
BSC's NS sub layer sends the NSVC blocking message to indicate

SGSN to block specified NSVC. This counter counts the number of
BSC's blocking specified NSVC.
Measurement
Point
Each time BSC sends the NS-BLOCK message, this counter increments. The measurement point is A1.
FIGURE 2121 NSVC BLOCKING PROCESS
Unit
Times
received blocking messages
sent by opposite end
Definition
2014
Number of received blocking messages sent by opposite end
Description
SGSN sends the NSVC blocking message to indicate BSC to block

specified NSVC. This counter counts the number of SGSN's blocking specified NSVC.
Measurement
Point
Each time BSC receives the NS-BLOCK message, this counter

Unit
Times
blocking confirm messages
send to opposite end by NS
sub layer
Definition
Number of blocking confirm messages send to opposite end by NS

sub layer
Description
BSC's NS sub layer sends NSVC blocking confirmation message to

notify SGSN that specified NSVC is blocked. This counter counts
Measurement
Point
Each time BSC sends the NS-BLOCK-ACK message, this counter

Unit
Times
2015
received blocking confirm
end
Definition
Number of received blocking confirm messages sent by opposite

end
Description
SGSN sends NSVC blocking confirmation message to notify BSC

that specified NSVC is reset. This counter counts the number of
BSC's receiving this message.
Measurement
Point
Each time BSC receives the NS-BLOCK-ACK message, this

Unit
Times
unblocking messages send
to opposite end by NS sub
layer
2016
Definition
Number of unblocking messages send to opposite end by NS sub

layer
Description
BSC's NS sub layer sends the NSVC unblocking message to indicate SGSN to unblock specified NSVC. This counter counts the
number of BSC's unblocking specified NSVC.
Measurement
Point
Each time BSC sends the NS-UNBLOCK message, this counter

FIGURE 2125 NSVC UNBLOCKING PROCESS
Unit
Times
C901300018 Number
of received unblocking
end
Definition
Number of received unblocking messages sent by opposite end
Description
SGSN sends the NSVC unblocking message to indicate BSC to unblock specified NSVC. This counter counts the number of SGSN's
unblocking specified NSVC.
Measurement
Point
Each time BSC receives the NS-UNBLOCK message, this counter

2017
Unit
Times
C901300019 Number
of unblocking confirm
messages send to opposite
end by NS sub layer
Definition
Number of unblocking confirm messages send to opposite end by

NS sub layer
Description
NS sub layer sends NSVC unblocking confirmation message to notify SGSN that specified NSVC is unblocked. This counter counts
Measurement
Point
Each time BSC sends the NS-UNBLOCK-ACK message, this

Unit
Times
C901300020 Number
of received unblocking
acknowledge messages
replied by opposite end
Definition
2018
Number of received unblocking acknowledge messages replied by

opposite end
Description
SGSN sends NSVC unblocking confirmation message to notify BSC

that specified NSVC is unblocked. This counter counts the number
Measurement
Point
Each time BSC receives the NS-UNBLOCK-ACK message, this

Unit
Times
abnormal cases in NS
transmission due to network
fault
Definition
Number of abnormal cases in NS transmission due to network fault
Description
This counter counts the number of abnormal cases in NS sub layer

transmission due to transmission network fault.
Measurement
Point
When NS sub layer receives reported fault from frame relay and
the fault is due to transmission network fault, the counter increments. The measurement point is A1.
2019
FIGURE 2129 FR REPORTING TRANSMISSION NETWORK FAULT
Unit
Times
transmission due to O&M
interference
Definition
Number of abnormal cases in NS transmission due to O&M interference
Description

transmission due to O interference.
Measurement
Point
When NS sub layer receives the blocking request from background,

the counter increments. The measurement point is A1.
FIGURE 2130 BLOCKING NSVC BY BACKGROUND
Unit
2020
Times
C901300023 Number
of abnormal cases in
NS transmission due to
equipment fault
Definition
Number of abnormal cases in NS transmission due to equipment

fault
Description

transmission due to equipment fault.
Measurement
Point
When NS sub layer receives reported fault from frame relay and
the fault is due to equipment fault, the counter increments. The
measurement point is A1.
FIGURE 2131 FR REPORTING EQUIPMENT FAULT
Unit
Times
transmission due to NSVC
block
Definition
Number of abnormal cases in NS transmission due to NSVC block
Description

transmission due to NSVC block.
Measurement
Point
When NS sub layer sends the status message which is due to NSVC
BLOCKED, the counter increments. The measurement point is A1.
2021
FIGURE 2132 NSVC BLOCKED
Unit
Times
C901300025 Number
of abnormal cases in NS
transmission due to unknown
NSVC
Definition
Number of abnormal cases in NS transmission due to unknown

NSVC
Description

transmission due to unknown NSVC.
Measurement
Point
When NS sub layer sends the status message which is due to unknown NSVC, the counter increments. The measurement point is
A1.
FIGURE 2133 NSVC UNKNOWN
Unit
2022
Times
transmission due to protocol
error
Definition
Number of abnormal cases in NS transmission due to protocol error
Description

transmission due to protocol error.
Measurement
Point
When NS sub layer sends the status message which is due to protocol error, including PDU semantic error, PDU being incompatible
with protocol, protocol error, invalid necessary IE, and missing necessary IE, the counter increments. The measurement point is A1.
FIGURE 2134 NS PROTOCOL ERROR
Unit
Times
C901300027 Number of test

failure (while over max)
Definition
Number of test failure (while over max)
Description
This counters counts the number of test failure due to the maximum retransmission times being exceeded during the NS sub layer
test procedure.
Measurement
Point
When the number of NS sub layer's sending NS-ALIVE PDU exceeds the maximum retransmission times NS-ALIVE-RETRIES and
there is no response, the counter increments. The measurement
point is A1.
2023
FIGURE 2135 TEST PROCEDURE BEING ABNORMAL
Unit
Times
C901300028 Number
of blocking procedure
failure (after exceeding the
maximum times)
2024
Definition
Number of blocking procedure failure (after exceeding the maximum times)
Description
blocking procedure.
Measurement
Point
When the number of NS sub layer's sending NS-BLOCK PDU

exceeds the maximum retransmission times NS-BLOCK-RETRIES
and there is no response, the counter increments. The measurement point is A1.
FIGURE 2136 BLOCKING PROCEDURE BEING ABNORMAL
Unit
Times
unblocking procedure
failure (after exceeding the
maximum times)
Definition
Number of unblocking procedure failure (after exceeding the maximum times)
Description
unblocking procedure.
Measurement
Point
When the number of NS sub layer's sending NS-UNBLOCK PDU exceeds the maximum retransmission times NS-UNBLOCK-RETRIES
and there is no response, the counter increments. The measurement point is A1.
2025
FIGURE 2137 UNBLOCKING PROCEDURE BEING ABNORMAL
Unit
Times
congestion occurrence of
level 1
Definition
Description
Number of congestion occurrence of level 1

congestion recovery of level
1
Definition
2026
Number of congestion recovery of level 1
Description
level 2
Definition
Description

2
Definition
Description

level 3
Definition
Description

3
Definition
2027
Description
BECN
Definition
Description
Usage
Measurement
Point
Number of BECN
This counter counts the number of setting BECN in the data sent
by SGSN.
The counter counts the number of NSVC backward congestions.
When BECN in the data received by FR from SGSN is set, the
counter accumulates. The measurement point is A1.
FIGURE 2138 UPLINK/DOWNLINK DATA BECN BEING SET
Unit
Times
FECN
Definition
Description
Usage
Measurement
Point
2028
Number of FECN
This counter counts the number of setting FECN in the data sent
by SGSN.
The counter counts the number of NSVC forward congestions.
When FECN in the data received by FR from SGSN is set, the
counter accumulates. The measurement point is A2.
FIGURE 2139 UPLINK/DOWNLINK DATA BECN BEING SET
Unit
Times
2029
2030
Chapter
37
NSE Statistic
Measurement
Table of Contents
Overview...................................................................... 2032
C901310001 Number of CS Paging received by BSS ........... 2033
C901310002 Number of PS Paging received by BSS ........... 2033
C901310003 Number of SUSPEND message sent ............... 2034
C901310004 Number of SUSPEND-ACK message received.......................................................................... 2034
C901310005 Number of SUSPEND-NACK message received.......................................................................... 2035
C901310006 Number of RESUME message sent................. 2036
C901310007 Number of RESUME-ACK message received.......................................................................... 2036
C901310008 Number of RESUME-NACK message received.......................................................................... 2037
C901310009 Number of FLUSH-LL message received ......... 2038
C901310010 Number of FLUSH-LL-ACK message sent......... 2038
C901310011
Number
of
LLC-DISCARDED
message
sent............................................................................. 2039
C901310013 Number of BVC_BLOCK_ACK message received.......................................................................... 2040
C901310015 Number of BVC-UNBLOCK-ACK message received.......................................................................... 2041
C901310017
Number
of
BVC-RESET
message
received.......................................................................... 2042
C901310018
Number
of
BVC-RESET-ACK
message
sent............................................................................. 2043
C901310019 Number of BVC-RESET-ACK message received.......................................................................... 2044
C901310020 Number of PERFORM_LOCATION_REQUEST
message received.......................................................... 2044
C901310021 Number of PERFORM_LOCATION_RESPONSE
message sent ............................................................... 2045
C901310022 Number of PERFORM_LOCATION_ABORT message received................................................................ 2046
C901310023 Number of POSITION_COMMAND message
sent............................................................................. 2046
C901310024 Number of POSITION_RESPONSE message received.......................................................................... 2047
C901310025 Number of status messages sent .................. 2048
C901310026 Number of status messages received ............. 2048
2031
C901310028 Number of status messages sent with cell service congestion ............................................................. 2049
error............................................................................ 2050
C901310030 Number of status messages sent with processor
overload....................................................................... 2050
C901310031 Number of status messages sent with semantically incorrect PDU ........................................................ 2051
mandatory information element....................................... 2051
C901310033 Number of status messages sent with missing
mandatory IE................................................................ 2052
conditional IE................................................................ 2052
C901310035 Number of status messages sent with unexpected conditional IE...................................................... 2053
C901310036 Number of status messages sent with conditional IE error ............................................................... 2053
status incompatible error................................................ 2054
unknown ...................................................................... 2054
C901310042 Number of status messages received with BVC
blocking ....................................................................... 2056
C901310043 Number of status messages received with semantically incorrect PDU................................................. 2056
C901310044 Number of status messages received with invalid
mandatory IE................................................................ 2057
C901310045 Number of status messages received with missing mandatory IE .......................................................... 2057
C901310046 Number of status messages received with missing conditional IE........................................................... 2057
C901310047 Number of status messages received with unexpected conditional IE...................................................... 2058
C901310048 Number of status messages received with conditional IE error............................................................. 2058
C901310049 Number of status messages received with protocol status incompatible error ........................................ 2059
C901310050 Number of status messages received with SGSN
congestion.................................................................... 2059
Overview
The NSE statistic measurement takes a single NSE as the measurement entity. It performs statistics for paging message, status
indication message, and signaling BVC resetting message received
by NSE at BSS.
2032
Chapter 37 NSE Statistic Measurement
Statistic unit in this measurement is the single NSE.
C901310001 Number of CS
Paging received by BSS
Definition
Number of CS Paging received by BSS
Description
This counter counts the number of PAGING CS messages received

by NSE at BSC from SGSN.
Usage
The counter is used to find out the frequency of SGSN's CS paging

to MS.
Measurement
Point
When BSS receives a message of which the type is GB_PAGING_CS, the counter increments. The measurement point is A.
FIGURE 2140 MEASUREMENT POINT OF BSS RECEIVING CS
PAGING MESSAGE
Unit
Times
Definition
Number of PS Paging received by BSS
Description
This counter counts the number of PAGING PS messages received

Usage
The counter is used to find out the frequency of SGSN's PS paging

to MS.
Measurement
Point
When BSS receives a message of which the type is GB_PAGING_PS, the counter increments. The measurement point is A.
FIGURE 2141 MEASUREMENT POINT OF BSS RECEIVING PS
PAGING MESSAGE
2033
Unit
Times
SUSPEND message sent
Definition
Number of SUSPEND message sent
Description
When BSS receives the suspending GPRS service message from

MS, BSS will send the SUSPEND message to SGSN. This counter
counts the number of sending SUSPEND message from NSE.
Usage
The counter is used to find out the frequency of MS's terminating

GPRS service.
Measurement
Point
When BSS sends the SUSPEND message, the counter increments.

FIGURE 2142 SUSPEND PROCESS
Unit
Times
SUSPEND-ACK message
received
Definition
2034
Number of SUSPEND-ACK message received
Description
When SGSN receives the SUSPEND message from BSS, SGSN will
send the SUSPEND_ACK message to BSS. This counter counts the
number of SUSPEND_ACK messages received by NSE.
Usage
The counter is used to find out cases in which SGSN has response
when MS requests for terminating GPRS service.
Measurement
Point
When BSS receives the SUSPEND_ACK message, the counter increments. The measurement point is A2.
FIGURE 2143 SUSPEND PROCESS
Unit
Times
SUSPEND-NACK message
received
Definition
Number of SUSPEND-NACK message received
Description
When SGSN receives the SUSPEND message from BSS, it checks

the SUSPEND message content.
If the message content is
incorrect or fault occurs at SGSN, SGSN will send the SUSPEND_NACK message to BSS. This counter counts the number of
SUSPEND_NACK messages received by NSE.
Usage
The counter is used to find out cases in which SGSN has no response when MS requests for terminating GPRS service.
Measurement
Point
When BSS receives the SUSPEND_NACK message, the counter increments. The measurement point is A2.
FIGURE 2144 MEASUREMENT POINT OF BSS RECEIVING
SUSPEND_NACK MESSAGE
Unit
Times
2035
RESUME message sent
Definition
Number of RESUME message sent
Description
When problems that cause MS to suspend disappear, BSS might

send the RESUME message to SGSN to notify it to resume GPRS
service of MS. This counter counts the number of sending RESUME
message by BSS.
Usage
The counter is used to find out the frequency of MS's resuming

GPRS service.
Measurement
Point
When BSS sends the RESUME message, the counter increments.

FIGURE 2145 RESUME PROCESS
Unit
Times
RESUME-ACK message
received
Definition
2036
Number of RESUME-ACK message received
Description
When SGSN receives the RESUME message from BSS, SGSN will
send the RESUME_ACK message to BSS. This counter counts the
number of RESUME_ACK messages received by NSE.
Usage
The counter is used to find out causes due to which SGSN has no
response when MS requests for resuming GPRS service.
Measurement
Point
When BSS receives the RESUME_ACK message, the counter increments. The measurement point is A2.
FIGURE 2146 RESUME PROCESS
Unit
Times
RESUME-NACK message
received
Definition
Number of RESUME-NACK message received
Description
If the MS in the RESUME PDU message sent from BSS is not found
at SGSN, SGSN willl send the RESUME_NACK message to BSS.
This message contains the failure cause, that is, unknown MS.
At this moment, BSS will terminate the RESUME process and ask
MS to update routing area. This counter counts the number of
RESUME_NACK messages received by NSE.
Usage
The counter is used to find out cases in which SGSN has no response when MS requests for resuming GPRS service.
Measurement
Point
When BSS receives the RESUME_NACK message, the counter increments. The measurement point is A2.
RESUME_NACK MESSAGE
Unit
Times
2037
C901310009 Number
of FLUSH-LL message
received
Definition
Number of FLUSH-LL message received
Description
When SGSN detects that a MS changes cell through cell update

or routing area update, SGSN will send the FLUSH_LL message to
the old BVC to initiate the cell update process on NSE. This counter
counts the number of FLUSH_LL messages received by NSE.
Usage
The counter is used to find out the frequency of MS's changing cell.
Measurement
Point
When BSS receives the FLUSH_LL message, the counter increments. The measurement point is A1.
FIGURE 2148 FLUSH_LL PROCESS
Unit
Times
FLUSH-LL-ACK message
sent
Definition
2038
Number of FLUSH-LL-ACK message sent
Description
When BSS receives the FLUSH_LL message from SGSN, BSS will
send the FLUSH_LL_ACK message to SGSN. This counter counts
the number of sending FLUSH_LL_ACK message from NSE.
Usage
The counter is used to find out that, after MS changes cell, whether
the MS's LLC PDU buffer is deleted in the old cell or moved to the
new cell in the routing area.
Measurement
Point
When BSS sends the FLUSH_LL_ACK message, the counter increments. The measurement point is A2.
FIGURE 2149 FLUSH_LL PROCESS
Unit
Times
LLC-DISCARDED message
sent
Definition
Description
Usage
Measurement
Point
Number of LLC-DISCARDED message sent

When the LLC PDU stored in BSS is deleted, the LLC_DISCARDED
message is sent to SGSN. This counter counts the number of sending LLC_DISCARDED message from NSE.
The counter is used to find out the storage of LLC PDU in BSS.
When BSS sends the LLC_DISCARDED message, the counter increments. The measurement point is A.
FIGURE 2150 MEASUREMENT POINT OF BSS SENDING
LLC_DISCARDED MESSAGE
Unit
Times
Definition
Description

When BSS blocks a BVC, it will send the BVC_BLOCK message to
SGSN to start the timer T1. BSS will identify the blocked BVC and
stop sending uplink data of the BVC. Meanwhile, cells associated
2039
with the BVC do not receive downlink data any more. This counter
counts the number of sending BVC_BLOCK message from NSE.
Usage
The counter is used to find out the frequency of BSS's requesting

to block BVC.
Measurement
Point
When BSS sends the BVC_BLOCK message, the counter increments. The measurement point is A1.
FIGURE 2151 BVC_BLOCK PROCESS
Unit
Times
C901310013 Number
of BVC_BLOCK_ACK
message received
Definition
Description
Usage
Measurement
Point
Number of BVC_BLOCK_ACK message received

When SGSN receives the BVC_BLOCK message from BSS, it identifies the BVC to be blocked and stops sending data to the BVC, and
replies the BVC_BLOCK_ACK message to BSS. This counter counts
the number of BVC_BLOCK_ACK messages received by NSE.
The counter is used to find out cases when BVC is blocked.
When BSS receives the BVC_BLOCK_ACK message, the counter
FIGURE 2152 BVC_BLOCK PROCESS
Unit
2040
Times
BVC-UNBLOCK message
sent
Definition
Description
When BSS unblocks the blocked BVC, it will send the BVC_UNBLOCK message to SGSN. This counter counts the number of sending BVC_UNBLOCK message from NSE.
Usage

to unblock BVC.
Measurement
Point
When BSS sends the BVC_UNBLOCK message, the counter increments. The measurement point is A1.
FIGURE 2153 BVC_UNBLOCK PROCESS
Unit
Times
C901310015 Number
of BVC-UNBLOCK-ACK
message received
Definition
Description
Usage
Measurement
Point
Number of BVC-UNBLOCK-ACK message received

When SGSN receives the BVC_UNBLOCK message from BSS,
it identifies the BVC to be unblocked and replies the BVC_UNBLOCK_ACK message to BSS. This counter counts the number of
BVC_UNBLOCK_ACK messages received by NSE.
The counter is used to find out cases when BVC is unblocked.
When BSS receives the BVC_UNBLOCK_ACK message, the counter
2041
FIGURE 2154 BVC_UNBLOCK PROCESS
Unit
Times
Definition
Description
This counter counts the number of PCU sending signaling BVC resetting message through Gb interface.
Usage
The counter is used to find out the frequency of requesting to

restart BVC due to BVC failure.
Measurement
Point
When NSE at BSC sends message of which the type is BVC_RESET

and BVCI is zero, the counter increments. The measurement point
is A1.
FIGURE 2155 PROCESS OF SENDING BVC_RESET
Unit
Times
BVC-RESET message
received
Definition
2042
Description
Usage
Measurement
Point
This counter counts the number of PCU's receiving the signaling

BVC resetting message.
The counter is used to find out cases when BVC is restarted.
When NSE at BSC receives message of which the type is BVC_RESET and BVCI is zero, the counter increments. The measurement
point is A1.
FIGURE 2156 PROCESS OF RECEIVING BVC_RESET
Unit
Times
sent
Definition
Description
Usage
Measurement
Point
Number of BVC-RESET-ACK message sent

When PCU receives the signaling BVC resetting message from Gb
interface, it replies the signaling BVC resetting acknowledge message. This counter counts the number of NSE's sending signaling
BVC resetting acknowledge message.
The counter is used to find out cases of SGSN initializing BVC.
When NSE at BSC sends message of which the type is BVC_RESET_ACK and BVCI is zero, the counter increments. The measurement point is A2.
FIGURE 2157 PROCESS OF RECEIVING BVC_RESET
Unit
Times
2043
received
Definition
Description
Usage
Measurement
Point
Number of BVC_RESET_ACK message received

Number of PCU's receiving the signaling BVC resetting acknowledge message. This counter counts the number of NSE's receiving
signaling BVC resetting acknowledge message.
The counter is used to find out cases of BVC initialization.
When NSE at BSC receives message of which the type is BVC_RESET_ACK and BVCI is zero, the counter increments. The measurement point is A2.
FIGURE 2158 PROCESS OF SENDING BVC_RESET
Unit
Times
PERFORM_LOCATION_RE
QUEST message received
Definition
2044
Number of PERFORM_LOCATION_REQUEST message received
Description
When SGSN receives the location request and BSS supports LCS,
SGSN will start the locating process and send PERFORM_LOCATION_REQUEST message to BSS. This counter counts the number
of BSS's receiving the location request message.
Usage
The counter is used to find out the frequency of SGSN's sending

location request to BSS.
Measurement
Point
When BSS receives the PERFORM_LOCATION_REQUEST message,

FIGURE 2159 PERFORM_LOCATION_REQUEST PROCESS
Unit
Times
PERFORM_LOCATION_RE
SPONSE message sent
Definition
Number of PERFORM_LOCATION_RESPONSE message sent
Description
After BSS receives the PERFORM_LOCATION_REQUEST message,

it will send the location request to SMLC and wait for SMLC's response, and then send the result in the PERFORM_LOCATION_RESPONSE message to SGSN. This counter counts the number of
BSS's sending the location request response message.
Usage
The counter is used to find out BSS's response to the location request from SGSN.
Measurement
Point
When BSS sends the PERFORM_LOCATION_RESPONSE message,

FIGURE 2160 PERFORM_LOCATION_REQUEST PROCESS
Unit
Times
2045
PERFORM_LOCATION_AB
Definition
Number of PERFORM_LOCATION_ABORT message received
Description
When SGSN initiates the location request before interruption

occurs, it sends the PERFORM_LOCATION_ABORT message to
BSS. This counter counts the number of BSS's receiving the
PERFORM_LOCATION_ABORT message.
Usage
The counter is used to find out the frequency of SGSN's terminating location towards BSS.
Measurement
Point
When BSS receives the PERFORM_LOCATION_ABORT message,

the counter increments. The measurement point is A.
PERFORM_LOCATION_ABORT MESSAGE
Unit
Times
POSITION_COMMAND
message sent
Definition
2046
Number of POSITION_COMMAND message sent
Description
BSS triggers the positioning command process by sending POSITION_COMMAND message to SGSN. This process is valid only
when positioning a MS. This counter counts the number of BSS's
sending POSITION_COMMAND message.
Usage

to implement positioning command to SGSN.
Measurement
Point
When BSS sends the POSITION_COMMAND message, the counter

FIGURE 2162 POSITION_COMMAND PROCESS
Unit
Times
POSITION_RESPONSE
message received
Definition
Number of POSITION_RESPONSE message received
Description
When SGSN receives the TOM message, SGSN will send the POSITION_RESPONSE message to BSS to trigger the position response
process. The TOM message is contained in LLC PDU, and the
LLC PDU contains the RRLP message of a MS. This position response process is valid only when positioning a MS. This counter
counts the number of BSS's receiving the POSITION_RESPONSE
message.
Usage
The counter is used to find out the frequency of SGSN's requesting

to implement positioning command to BSS.
Measurement
Point
When BSS receives the POSITION_RESPONSE message, the

FIGURE 2163 POSITION_COMMAND PROCESS
Unit
Times
2047
status messages sent
Definition
Number of status messages sent
Description
When NSE receives downlink BSSGP PDU, if there is any abnormality, NSE will send the STATUS message to the opposite end entity.
The STATUS message sent indicates causes of the abnormality:
BVCI unknown, cell traffic congestion, Protocol error, Processor
overload, Semantically incorrect PDU, Invalid mandatory information, Missing mandatory IE, or Missing conditional IE. This counter
counts the number of abnormality that occurs.
Usage
The counter is used to find out abnormality occurring when NSE

receives downlink BSSGP PDU.
Measurement
Point
When NSE at BSC sends message of which the type is STATUS to

opposite end entity, the counter increments. The measurement
point is A1.
Unit
Times
Definition
2048
Number of status messages received
Description
If the BSSGP PDU sent by NSE to SGSN is abnormal, NSE will receive the STATUS message returned from the opposite end. The
STATUS message returned indicates causes of the abnormality:
counts teh number of STATUS messages returned from SGSN.
Usage
The counter is used to find out abnormality occurring when SGSN

Measurement
Point
When NSE receives the STATUS message, the counter increments.

Unit
Times
BVCI Unknown
Definition
Number of status messages sent with BVCI Unknown
Description
This counter counts the number of NSE's sending STATUS message

to opposite end entity, the message indicating "BVCI unknown".
Usage
The counter is used to find out the frequency of abnormality due

to "BVCI unknown" occurring when NSE receives downlink BSSGP
PDU.
Measurement
Point
When NSE sends the STATUS message to opposite end entity and
the message indicates that the abnormality is due to "BVCI unknown", the counter increments.
Unit
Times
Definition
Number of status messages sent with cell service congestion
Description

to opposite end entity, the message indicating "cell traffic congestion".
Usage

to "cell traffic congestion" occurring when NSE receives downlink
BSSGP PDU.
2049
Measurement
Point
Unit
the message indicates that the abnormality is due to "cell traffic
congestion", the counter increments.
Times
protocol error
Definition
Number of status messages sent with protocol error
Description

to opposite end entity, the message indicating "Protocol error".
Usage

to "Protocol error" occurring when NSE receives downlink BSSGP
PDU.
Measurement
Point
the message indicates that the abnormality is due to "Protocol error", the counter increments.
Unit
Times
processor overload
Definition
Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Processor
overload".
Usage

to "Processor overload" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Processor
overload", the counter increments.
Unit
2050
Number of status messages sent with processor overload
Times
semantically incorrect PDU
Definition
Number of status messages sent with semantically incorrect PDU
Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Semantically
incorrect PDU".
Usage
The counter is used to find out the frequency of abnormality due to

"Semantically incorrect PDU" occurring when NSE receives downlink BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Semantically
incorrect PDU", the counter increments.
Unit
Times
with invalid mandatory
information element
Definition
Number of status messages sent with invalid mandatory information element
Description

to opposite end entity, the message indicating "Invalid mandatory
information".
Usage

to "Invalid mandatory information" occurring when NSE receives
downlink BSSGP PDU.
Measurement
Point
When NSE sends the STATUS message to opposite end entity

and the message indicates that the abnormality is due to "Invalid
mandatory information", the counter increments.
Unit
Times
2051
missing mandatory IE
Definition
Number of status messages sent with missing mandatory IE
Description

to opposite end entity, the message indicating "Missing mandatory
IE".
Usage

to "Missing mandatory IE" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Missing
mandatory IE", the counter increments.
Unit
Times
missing conditional IE
Definition
Description

to opposite end entity, the message indicating "Missing conditional
IE".
Usage

to "Missing conditional IE" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Missing conditional IE", the counter increments.
Unit
2052
Number of status messages sent with missing conditional IE
Times
unexpected conditional IE
Definition
Number of status messages sent with unexpected conditional IE
Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Unexpected
conditional IE".
Usage

"Unexpected conditional IE" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Unexpected
conditional IE", the counter increments.
Unit
Times
conditional IE error
Definition
Number of status messages sent with conditional IE error
Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Conditional
IE error".
Usage

to "Conditional IE error" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Conditional
IE error", the counter increments.
Unit
Times
2053
protocol status incompatible
error
Definition
Number of status messages sent with protocol status incompatible

error
Description

to opposite end entity, the message indicating "PDU not compatible
with the protocol state".
Usage

to "PDU not compatible with the protocol state" occurring when
NSE receives downlink BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "PDU not
compatible with the protocol state", the counter increments.
Unit
Times
with BVCI unknown
Definition
Description
This counter counts the number of received STATUS messages

which indicate "BVCI unknown".
Usage

"BVCI unknown" occurring when SGSN receives downlink BSSGP
PDU.
Measurement
Point
When PCU receives STATUS message which indicates "BVCI unknown", the counter increments.
Unit
2054
Number of status messages received with BVCI unknown
Times
Definition
Number of status messages received with cell service congestion
Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "cell traffic congestion".
Usage

to "cell traffic congestion" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "cell traffic

Unit
Times
with protocol error
Definition
Number of status messages received with protocol error
Description

which indicate "Protocol error".
Usage

to "Protocol error" occurring when SGSN receives downlink BSSGP
PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Protocol error", the counter increments.
Unit
Times
Definition
Description
Number of status messages received with processor overload

This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "Processor overload".
2055
Usage

to "Processor overload" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Processor

Unit
Times
with BVC blocking
Definition
Number of status messages received with BVC blocking
Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "BVCI-blocked".
Usage

to "BVCI-blocked" occurring when SGSN receives downlink BSSGP
PDU.
Measurement
Point
When PCU receives STATUS message which indicates "BVCIblocked", the counter increments.
Unit
Times
with semantically incorrect
PDU
Definition
Number of status messages received with semantically incorrect

PDU
Description

which indicate "Semantically incorrect PDU".
Usage

"Semantically incorrect PDU" occurring when SGSN receives downlink BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Semantically incorrect PDU", the counter increments.
Unit
2056
Times
with invalid mandatory IE
Definition
Number of status messages received with invalid mandatory IE
Description

which indicate "Invalid mandatory information".
Usage

to "Invalid mandatory information" occurring when SGSN receives
downlink BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Invalid

Unit
Times
with missing mandatory IE
Definition
Number of status messages received with missing mandatory IE
Description

which indicate "Missing mandatory IE".
Usage

to "Missing mandatory IE" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Missing

Unit
Times
with missing conditional IE
Definition
Description
Number of status messages received with missing conditional IE

which indicate "Missing conditional IE".
2057
Usage

to "Missing conditional IE" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Missing conditional IE", the counter increments.
Unit
Times
with unexpected conditional
IE
Definition
Number of status messages received with unexpected conditional

IE
Description

which indicate "Unexpected conditional IE".
Usage

"Unexpected conditional IE" occurring when SGSN receives downlink BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Unexpected

Unit
Times
with conditional IE error
Definition
Description

which indicate "Conditional IE error".
Usage

to "Conditional IE error" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Conditional

Unit
2058
Number of status messages received with conditional IE error
Times
C901310049 Number
of status messages
received with protocol
status incompatible error
Definition
Number of status messages received with protocol status incompatible error
Description

which indicate "PDU not compatible with the protocol state".
Usage

SGSN receives downlink BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "PDU not

Unit
Times
with SGSN congestion
Definition
Number of status messages received with SGSN congestion
Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "SGSN congestion".
Usage

to "SGSN congestion" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "SGSN congestion", the counter increments.
Unit
Times
2059
2060
Chapter
38
BTS TRX Measurement

Table of Contents
Overview...................................................................... 2062
C901320001 Number of normal increases of MS power due to
UL signal level............................................................... 2063
C901320002 Number of rapid increase in MS power due to UL
signal level ................................................................... 2064
C901320003 Number of normal decrease of MS power due to
UL signal level............................................................... 2065
C901320004 Number of rapid decrease in MS power due to
UL signal level............................................................... 2066
C901320005 Number of normal increases of BS power due to
DL signal level .............................................................. 2067
C901320006 Number of rapid increase in BS power due to DL
signal level ................................................................... 2068
C901320007 Number of normal decrease of BS power due to
DL signal level .............................................................. 2069
C901320008 Number of rapid decrease in BS power due to
DL signal level .............................................................. 2070
C901320009 Number of normal increases of MS power due to
UL signal quality............................................................ 2071
C901320010 Number of rapid increase in MS power due to UL
signal quality ................................................................ 2072
C901320011 Number of normal decrease of MS power due to
C901320012 Number of rapid decrease in MS power due to
C901320013 Number of normal increases of BS power due to
DL signal quality............................................................ 2075
C901320014 Number of rapid increase in BTS power due to
C901320015 Number of normal decrease of BS power due to
C901320016 Number of rapid decrease in BTS power due to
C901320017 Total value of each result of regular scanning of
MS utilization power....................................................... 2079
C901320018 Number of regular scanning and sampling of MS
utilization power............................................................ 2080
C901320019 Total value of each result of regular scanning of
BS utilization power ....................................................... 2081
C901320020 Number of regular scanning and sampling of BS
utilization power............................................................ 2082
level ............................................................................ 2083
C901320022 Number of power scans of DL signal level......... 2084
level ............................................................................ 2085
2061
C901320024 Number of power scans of UL signal level......... 2086

C901320025 Total value of power scans of DL signal quality ............................................................................... 2087
C901320026 Number of power scans of DL signal quality ............................................................................... 2088
C901320027 Total value of power scans of UL signal quality ............................................................................... 2089
C901320028 Number of power scans of UL signal quality ............................................................................... 2090
C901320029 Maximum value of UL signal level in regular
scan ............................................................................ 2091
C901320030 Minimum value of UL signal level in regular
scan ............................................................................ 2092
C901320031 Maximum value obtained in regular scan of DL
signal level ................................................................... 2093
C901320032 Minimum value obtained in regular scan of DL
signal level ................................................................... 2094
C901320033 Sum of Periodic BS Power (TCH/F) Search Result ............................................................................. 2095
C901320034 Periodic BS Power (TCH/F) Search Times......... 2095
C901320035 Sum of Periodic BS Power (TCH/H) Search Result ............................................................................. 2096
C901320036 Number of Periodic BS Power (TCH/H)
Search ......................................................................... 2096
C901320037 Sum of Periodic BS Power (SDCCH) Search Result ............................................................................. 2097
C901320038 Number of Periodic BS Power (SDCCH)
Search ......................................................................... 2097
C901320039 Sum of Periodic DL Signal Level (TCH/F) Search
Result .......................................................................... 2097
C901320040 Number of Periodic DL Signal Level (TCH/F)
Search ......................................................................... 2098
C901320041 Sum of Periodic DL Signal Level (TCH/H) Search
Result .......................................................................... 2098
C901320042 Number of Periodic DL Signal Level (TCH/H)
Search ......................................................................... 2099
C901320043 Sum of Periodic DL Signal Level (SDCCH) Search
Result .......................................................................... 2099
C901320044 Number of Periodic DL Signal Level (SDCCH)
Search ......................................................................... 2099
Overview
According to the receiving level and receiving quality in MS measurement report and the receiving level and receiving quality in
BTS measurement, BTS decides whether to perform power control
for MS or BTS. BTS also performs statistics according to different
reasons for power control.
There are two ways for power control: common control and rapid
control. The power control amplitude in rapid control is larger than
that in common control. Besides, BTS periodically samples the
power of MS and BTS to get the average power.
After the power control measurement task is customized, BTS periodically reports the power control statistic result to BSC through
the PC TEST RPT message. The power control measurement result
2062
Chapter 38 BTS TRX Measurement
can be used to analyze coverage quality and power control effect

and frequency.
The power control measurement mechanism is shown as below.
The measurement point for MS power control is A1, which is after
BTS sending the power control message to MS. The measurement
point for BTS power control is A2, which is after BTS sending the
power control message to itself. The measurement point for periodical power sampling is A3. BSC collects the power control measurement counter information after it receives the PC TEST RPT
message, which is at B1 as shown in below.
FIGURE 2166 POWER CONTROL MEASUREMENT
Statistic unit in this measurement is TRX.
normal increases of MS
power due to UL signal level
Definition
Number of normal increases of MS power due to UL signal level
Description
In common power control, after BTS measures the uplink level and
quality of MS, it compares the MS's uplink level with the configured uplink receiving level threshold according to the power control algorithm and makes decision. If BTS decides to increase MS's
transmission power, it sends the message of increasing transmission power to MS, and the counter increments.
Measurement
Point
The counter counts when BTS sends the message of increasing

transmission power to MS. The measurement point is A1
2063
Unit
Related Features
Times
ZGO-04-02-002 Dynamic MS Power Control
rapid increase in MS power
due to UL signal level
Definition
2064
Number of rapid increase in MS power due to UL signal level
Description
In rapid power control, after BTS measures the uplink level and
quality of MS, it compares the MS's uplink level with the configured uplink receiving level threshold according to the power control algorithm and makes decision. If BTS decides to increase MS's
transmission power, it sends the message of increasing transmission power to MS, and the counter increments.
Measurement
Point

transmission power to MS. The measurement point is A1.
Unit
Related Features
Times
normal decrease of MS
power due to UL signal level
Definition
Number of normal decrease of MS power due to UL signal level
Description
quality of MS, it compares the MS's uplink level with the configured uplink receiving level threshold according to the power control algorithm and makes decision. If BTS decides to decrease MS's
transmission power, it sends the message of decreasing transmission power to MS, and the counter increments.
Measurement
Point
The counter counts when BTS sends the message of decreasing

2065
Unit
Related Features
Times
rapid decrease in MS power
due to UL signal level
Definition
2066
Number of rapid decrease in MS power due to UL signal level
Description
quality of MS, it compares the MS's uplink level with the configured uplink receiving level threshold according to the power control algorithm and makes decision. If BTS decides to decrease MS's
Measurement
Point

Unit
Related Features
Times
normal increases of BS
power due to DL signal level
Definition
Number of normal increases of BS power due to DL signal level
Description
In common power control, after BTS receives the MS measurement report, it compares the MS's downlink receiving level with
the configured downlink receiving level threshold according to the
power control algorithm and makes decision. If BTS decides to
increase BTS's transmission power, it sends the message of increasing transmission power to BTS, and the counter increments.
Measurement
Point

transmission power to itself. The measurement point is A2.
2067
Unit
Related Features
Times
ZGO-04-02-001 Dynamic BTS Power Control
rapid increase in BS power
due to DL signal level
Definition
2068
Number of rapid increase in BS power due to DL signal level
Description
In rapid power control, after BTS receives the MS measurement report, it compares the MS's downlink receiving level and quality with
the configured downlink receiving level threshold and downlink receiving quality threshold according to the power control algorithm
and makes decision. If BTS decides to increase BTS's transmission
power, it sends the message of increasing transmission power to
BTS, and the counter increments.
Measurement
Point

Unit
Related Features
Times
normal decrease of BS
power due to DL signal level
Definition
Number of normal decrease of BS power due to DL signal level
Description
In common power control, after BTS receives the MS measurement report, it compares the MS's downlink receiving level with
the configured downlink receiving level threshold according to the
decrease BTS's transmission power, it sends the message of decreasing transmission power to BTS, and the counter increments.
Measurement
Point

2069
Unit
Related Features
Times
rapid decrease in BS power
due to DL signal level
Definition
2070
Number of rapid decrease in BS power due to DL signal level
Description
In rapid power control, after BTS receives the MS measurement

report, it compares the MS's downlink receiving level with the
configured downlink receiving level threshold according to the
Measurement
Point

Unit
Related Features
Times
normal increases of MS
power due to UL signal
quality
Definition
Number of normal increases of MS power due to UL signal quality
Description
quality of MS, it compares the MS's uplink quality with the configured uplink receiving quality threshold according to the power
control algorithm and makes decision. If BTS decides to increase
MS's transmission power, it sends the message of increasing transmission power to MS, and the counter increments.
Measurement
Point

2071
Unit
Related Features
Times
rapid increase in MS power
due to UL signal quality
Definition
2072
Number of rapid increase in MS power due to UL signal quality
Description
quality of MS, it compares the MS's uplink quality with the configured uplink receiving quality threshold according to the power
control algorithm and makes decision. If BTS decides to increase
MS's transmission power, it sends the message of increasing transmission power to MS, and the counter increments.
Measurement
Point

Unit
Related Features
Times
normal decrease of MS
power due to UL signal
quality
Definition
Number of normal decrease of MS power due to UL signal quality
Description
quality of MS, it compares the MS's uplink quality with the configured uplink receiving quality threshold according to the power control algorithm and makes decision. If BTS decides to decrease MS's
Measurement
Point

2073
Unit
Related Features
Times
rapid decrease in MS power
due to UL signal quality
Definition
2074
Number of rapid decrease in MS power due to UL signal quality
Description
quality of MS, it compares the MS's uplink quality with the configured uplink receiving quality threshold according to the power control algorithm and makes decision. If BTS decides to decrease MS's
Measurement
Point

Unit
Related Features
Times
normal increases of BS
power due to DL signal
quality
Definition
Number of normal increases of BS power due to DL signal quality
Description
In common power control, after BTS receives the MS measurement report, it compares the MS's downlink receiving quality with
the configured downlink receiving quality threshold according to
the power control algorithm and makes decision. If BTS decides
to increase BTS's transmission power, it sends the message of increasing transmission power to BTS, and the counter increments.
Measurement
Point

2075
Unit
Related Features
Times
rapid increase in BTS power
due to DL signal quality
Definition
2076
Number of rapid increase in BTS power due to DL signal quality
Description

report, it compares the MS's downlink receiving quality with the
configured downlink receiving quality threshold according to the
increase BTS's transmission power, it sends the message of increasing transmission power to BTS, and the counter increments.
Measurement
Point

Unit
Related Features
Times
normal decrease of BS
quality
Definition
Number of normal decrease of BS power due to DL signal quality
Description
In common power control, after BTS receives the MS measurement report, it compares the MS's downlink receiving quality with
the configured downlink receiving quality threshold according to
the power control algorithm and makes decision. If BTS decides
to decrease BTS's transmission power, it sends the message of decreasing transmission power to BTS, and the counter increments.
Measurement
Point

2077
Unit
Related Features
Times
rapid decrease in BTS
quality
Definition
2078
Number of rapid decrease in BTS power due to DL signal quality
Description

report, it compares the MS's downlink receiving quality with the
configured downlink receiving quality threshold according to the
Measurement
Point

Unit
Related Features
Times

of each result of regular
scanning of MS utilization
power
Definition
Total value of each result of regular scanning of MS utilization

power
Description
To get the average MS utilization power on TRX, BTS periodically

scans the MS utilization power on channels of TRX and accumulates
the value. During the period of reporting measurement result to
BSC, BTS may perform multiple periodical scannings. This counter
accumulates the MS utilization power value of each scanning.
Measurement
Point
The counter accumulates when BTS performs periodical scanning.

2079
Unit
Related Features
Grade
C901320018 Number
sampling of MS utilization
power
2080
Definition
Number of regular scanning and sampling of MS utilization power
Description
To get the average MS utilization power on TRX, BTS periodically

scans the MS utilization power on channels of TRX and accumulates the value. Each time a MS utilization power value is accumulated, the counter increments. During the period of reporting
measurement result to BSC, BTS may perform multiple periodical scannings. This counter accumulates the number of periodical
scannings.
Measurement
Point
The counter counts when BTS performs periodical scanning. The

Unit
Related Features
Times

of each result of regular
scanning of BS utilization
power
Definition
Total value of each result of regular scanning of BS utilization

power
Description
To get the average utilization power on TRX, BTS periodically

scans the utilization power on channels of TRX and accumulates
the value. During the period of reporting measurement result to
accumulates the BTS utilization power value of each scanning.
Measurement
Point
The counter accumulates when BTS performs periodical scanning.

2081
Unit
Related Features
Grade
C901320020 Number
sampling of BS utilization
power
2082
Definition
Number of regular scanning and sampling of BS utilization power
Description
To get the average utilization power on TRX, BTS periodically

scans the utilization power on channels of TRX and accumulates
the value. Each time a channel utilization power value is accumulated, the counter increments. During the period of reporting
measurement result to BSC, BTS may perform multiple periodical
scannings. This counter accumulates the number of periodical
scannings.
Measurement
Point

Unit
Related Features
Times

power scans of DL signal
level
Definition
Total value of power scans of DL signal level
Description
To get the average downlink signal level received by MS on TRX,

BTS periodically scans the downlink signal level reported by MS on
channels of TRX and accmulates. During the period of reporting
scannings. This counter accumulates the MS downlink signal level
value of each scanning.
Measurement
Point

2083
Unit
Related Features
Grade
level
Definition
2084
Number of power scans of DL signal level
Description
To get the average downlink signal level received by MS on TRX,

BTS periodically scans the downlink signal level reported by MS on
channels of TRX and accmulates. Each time a measured downlink
signal level is accumulated, the counter increments. During the
period of reporting measurement result to BSC, BTS may perform
multiple periodical scannings. This counter accumulates the number of periodical scannings.
Measurement
Point

Unit
Related Features
Times

power scans of UL signal
level
Definition
Total value of power scans of UL signal level
Description
To get the average uplink signal level received by TRX, BTS periodically scans the uplink signal level on channels of TRX and accmulates. During the period of reporting measurement result to
accumulates the uplink signal level value of each scanning.
Measurement
Point

2085
Unit
Related Features
Grade
level
Definition
2086
Number of power scans of UL signal level
Description
To get the average uplink signal level received by TRX, BTS periodically scans the uplink signal level on channels of TRX and accmulates. Each time a uplink signal level is accumulated, the counter
increments. During the period of reporting measurement result to
accumulates the number of periodical scannings.
Measurement
Point

Unit
Related Features
Times

quality
Definition
Total value of power scans of DL signal quality
Description
To get the average downlink signal quality received by MS on TRX,

BTS periodically scans the downlink signal quality reported by MS
on channels of TRX and accmulates. During the period of reporting
scannings. This counter accumulates the MS downlink signal quality value of each scanning.
Measurement
Point

2087
Unit
Related Features
Grade
quality
Definition
2088
Number of power scans of DL signal quality
Description
To get the average downlink signal quality received by MS on TRX,

BTS periodically scans the downlink signal quality reported by MS
on channels of TRX and accmulates. Each time a measured downlink signal quality is accumulated, the counter increments. During
the period of reporting measurement result to BSC, BTS may perform multiple periodical scannings. This counter accumulates the
number of periodical scannings.
Measurement
Point

Unit
Related Features
Times

quality
Definition
Total value of power scans of UL signal quality
Description
To get the average uplink signal quality received by TRX, BTS periodically scans the uplink signal quality on channels of TRX and
accmulates. During the period of reporting measurement result to
accumulates the uplink signal quality value of each scanning.
Measurement
Point

2089
Unit
Related Features
Grade
quality
Definition
2090
Number of power scans of UL signal quality
Description
To get the average uplink signal quality received by TRX, BTS periodically scans the uplink signal quality on channels of TRX and
accmulates. Each time a uplink signal quality is accumulated, the
counter increments. During the period of reporting measurement
result to BSC, BTS may perform multiple periodical scannings. This
counter accumulates the number of periodical scannings.
Measurement
Point

Unit
Related Features
Times
C901320029 Maximum
value of UL signal level in
regular scan
Definition
Maximum value of UL signal level in regular scan
Description
When BSC collects information of power control measurement

counters, this counter records the maximum uplink signal level
value.
Measurement
Point
The counter counts when BSC receives the reported power control
measurement message PC TEST RPT. The measurement point is
B1.
2091
Unit
Related Features
Grade

of UL signal level in regular
scan
Definition
2092
Minimum value of UL signal level in regular scan
Description

counters, this counter records the minimum uplink signal level
value.
Measurement
Point
B1.
Unit
Related Features
Grade
C901320031 Maximum
value obtained in regular
scan of DL signal level
Definition
Maximum value obtained in regular scan of DL signal level
Description

counters, this counter records the maximum downlink signal level
value.
Measurement
Point
B1.
2093
Unit
Related Features
Grade

obtained in regular scan of
DL signal level
Definition
2094
Minimum value obtained in regular scan of DL signal level
Description

counters, this counter records the minimum downlink signal level
value.
Measurement
Point
B1.
Unit
Related Features
Grade
C901320033 Sum of
Periodic BS Power (TCH/F)
Search Result
Definition
Sum of Periodic BS Power (TCH/F) Search Result
Description
This counter records the total value of BS power (TCH/F) of periodical scannings.
Measurement
Point
When the power control message is received and if the channel is

TCH/F, then obtain the BS power in the message and accumulate.
Unit
Related Features
Grade
C901320034 Periodic BS
Power (TCH/F) Search
Times
Definition
Periodic BS Power (TCH/F) Search Times
2095
Description
This counter counts the number of periodical scanning of BS power

(TCH/F).
Measurement
Point
When the power control message is received, if the channel is

TCH/F and the message contains BS power information, then the
counter increments.
Unit
Related Features
Times
C901320035 Sum of
Periodic BS Power (TCH/H)
Search Result
Definition
Sum of Periodic BS Power (TCH/H) Search Result
Description
This counter records the total value of BS power (TCH/H) of periodical scannings.
Measurement
Point

TCH/H, then obtain the BS power in the message and accumulate.
Unit
Related Features
Grade
Periodic BS Power (TCH/H)
Search
Definition
Description

(TCH/H).
Measurement
Point

TCH/H and the message contains BS power information, then the
counter increments.
Unit
Related Features
2096
Number of Periodic BS Power (TCH/H) Search
Times
C901320037 Sum of
Periodic BS Power (SDCCH)
Search Result
Definition
Sum of Periodic BS Power (SDCCH) Search Result
Description
This counter records the total value of BS power (SDCCH) of periodical scannings.
Measurement
Point

SDCCH, then obtain the BS power in the message and accumulate.
Unit
Related Features
Grade
Periodic BS Power (SDCCH)
Search
Definition
Number of Periodic BS Power (SDCCH) Search
Description

(SDCCH).
Measurement
Point
When the power control message is received, if the channel is SDCCH and the message contains BS power information, then the
counter increments.
Unit
Related Features
Times
C901320039 Sum of
Periodic DL Signal Level
(TCH/F) Search Result
Definition
Sum of Periodic DL Signal Level (TCH/F) Search Result
Description
This counter records the total value of downlink signal level

(TCH/F) of periodical scannings.
Measurement
Point

TCH/F, then obtain the downlink signal level in the message and
accumulate.
2097
Unit
Related Features
Grade
(TCH/F) Search
Definition
This counter counts the number of periodical scanning of downlink

signal level (TCH/F).
Description

(TCH/F) of periodical scannings.
Measurement
Point

TCH/F and the message contains downlink signal level information, then the counter increments.
Unit
Related Features
Times
C901320041 Sum of
(TCH/H) Search Result
Definition
Description

(TCH/H) of periodical scannings.
Measurement
Point

TCH/H, then obtain the downlink signal level in the message and
accumulate.
Unit
Related Features
2098
Sum of Periodic DL Signal Level (TCH/H) Search Result
Grade
(TCH/H) Search
Definition
Number of Periodic DL Signal Level (TCH/H) Search
Description

signal level (TCH/H).
Measurement
Point

TCH/H and the message contains downlink signal level information, then the counter increments.
Unit
Related Features
Times
C901320043 Sum of
(SDCCH) Search Result
Definition
Sum of Periodic DL Signal Level (SDCCH) Search Result
Description
This counter records the total value of downlink signal level (SDCCH) of periodical scannings.
Measurement
Point

SDCCH, then obtain the downlink signal level in the message and
accumulate.
Unit
Related Features
Grade
(SDCCH) Search
Definition
Description
Number of Periodic DL Signal Level (SDCCH) Search

signal level (SDCCH).
2099
Measurement
Point
Unit
Related Features
2100
When the power control message is received, if the channel is SDCCH and the message contains downlink signal level information,
Times
Chapter
39
NSVC on IPGB HOST

Measurement
Table of Contents
Overview...................................................................... 2101
C901330001 Time of PVC unavailable............................... 2101
due to network fault ...................................................... 2102
due to O&M interference................................................. 2102
due to equipment fault ................................................... 2103
due to unknown NSVC.................................................... 2103
due to protocol error ...................................................... 2103
C901330007 Number of unsuccess test due to over
max............................................................................. 2104
Overview
The NSVC statistic measurement on IPGB HOST is used to measure signaling interaction and data transmission at NS layer of Gb
interface in GPRS service. It also performs statistics for abnormalities in various flows.

unavailable
Definition
Time of PVC unavailable
Description
This counter counts the time during which NSVC can not be used
for data transmission.
Measurement
Point
The counter starts counting when NSVC link becomes abnormal

and stops counting when NSVC link becomes normal. The duration
2101
between the two time points is the time during which NSVC is
unavailable.
Unit
Related Features
Second
ZGO-05-04-002 Gb over IP
transmission due to network
fault
Definition
Description
Related Features
Number of abnormal cases in NS transmission due to network fault

transmission due to O&M
interference
Definition
Description
Related Features
2102
Number of abnormal cases in NS transmission due to O&M interference

Chapter 39 NSVC on IPGB HOST Measurement
C901330004 Number
of abnormal cases in
NS transmission due to
equipment fault
Definition
Description
Related Features
Number of abnormal cases in NS transmission due to equipment

fault
C901330005 Number
of abnormal cases in NS
transmission due to unknown
NSVC
Definition
Number of abnormal cases in NS transmission due to unknown

NSVC
Description

transmission due to unknown NSVC.
Measurement
Point
During the NS sub layer signaling interaction, the counter accumulates the number of signaling transmitted by unknown NSVC.
Unit
Related Features
Times
transmission due to protocol
error
Definition
Number of abnormal cases in NS transmission due to protocol error
Description

transmission due to protocol error.
2103
Measurement
Point
Unit
Related Features
When the field in NS signaling is inconsistent with that defined in

protocol, the counter accumulates.
Times
unsuccess test due to over
max
Definition
Number of unsuccess test due to over max
Description
test procedure.
Measurement
Point
When the number of NS sub layer's sending NS-ALIVE PDU exceeds the maximum retransmission times NS-ALIVE-RETRIES and
there is no response, the counter increments. The measurement
point is A1.
FIGURE 2199 TEST PROCEDURE BEING ABNORMAL
Unit
Related Features
2104
Times
Chapter
40
GB Message on IPGB
HOST Measurement
Table of Contents
Overview...................................................................... 2106
C901340001 Number of RA-CAPABILITY message recevied............................................................................. 2107
BSC ............................................................................. 2107
BSC ............................................................................. 2108
sent............................................................................. 2108
C901340006 Number of wireless status PDU messages sent
by BSC......................................................................... 2110
BSC due to losing wireless association with MS .................. 2110
BSC due to bad link quality ............................................. 2111
BSC due to cell reselection command ............................... 2111
by BSC......................................................................... 2112
received by BSC ............................................................ 2112
by BSC......................................................................... 2113
received by BSC ............................................................ 2114
by BSC......................................................................... 2114
received by BSC ............................................................ 2115
C901340016 Number of status messages sent by BSC......... 2116
BSC ............................................................................. 2116
error............................................................................ 2118
C901340021 Number of status messages sent with Processor
overload....................................................................... 2118
2105

Unknown...................................................................... 2118
by BSC......................................................................... 2120
sent by BSC.................................................................. 2121
sent by BSC.................................................................. 2122
BSC ............................................................................. 2123
by BSC......................................................................... 2124
sent by BSC.................................................................. 2125
C901340034 Number of DELETE-BSS-PFC-REQ messages received by BSC............................................................... 2125
C901340035 Number of PS-HANDOVER-REQUIRED messages
sent by BSC.................................................................. 2126
received by BSC ............................................................ 2128
C901340039 Number of PS-HANDOVER-REQUEST-ACK messages sent by BSC ......................................................... 2129
messages sent by BSC ................................................... 2130
C901340041 Number of PS-HANDOVER-COMPLETE messages
sent by BSC.................................................................. 2131
C901340042 Number of PS-HANDOVER-CANCEL messages
sent by BSC.................................................................. 2132
with Service UTRAN CCO received by BSC......................... 2133
Service UTRAN CCO received by BSC ............................... 2134
Overview
The Gb interface message measurement on IPGB HOST measures
the number of transceiving various PTP messages at BSSGP layer
of Gb interface in GPRS service, such as RA-CAPABILITY, RADIOSTATUS, and DOWNLOAD-BSS-PFC.
2106
Chapter 40 GB Message on IPGB HOST Measurement
RA-CAPABILITY message
recevied
Definition
Number of RA-CAPABILITY message received
Description
SGSN sends the RA-CAPABILITY message to BSC to indicate the

wireless capability of MS. This counter counts the number of BSC's
receiving this message.
Measurement
Point
When BSC receives a RA-CAPABILITY message, this counter increments. The measurement point is A.
FIGURE 2200 MEASUREMENT POINT OF THE NUMBER OF
RECEIVING RA-CAPABILITY MESSAGE
Unit
Related Features
Times
by BSC
Definition
Number of PTP packet paging received by BSC
Description
SGSN sends the PTP packet paging message to indicate BSC to

initiate PTP packet paging for MS. This counter counts the number
Measurement
Point
When BSC receives a PAGING PS message, this counter increments. The measurement point is A.
Unit
Times
2107
Related Features
by BSC
Definition
Number of PTP circuit paging recevied by BSC
Description
SGSN sends the PTP circuit paging message to indicate BSC to

initiate PTP circuit paging for MS. This counter counts the number
Measurement
Point
When BSC receives a PAGING CS message, this counter increments. The measurement point is A.
Unit
Related Features
Times
message sent
Definition
2108
Number of RA-CAPABILITY-UPDATE message sent
Description
BSC sends the RA-CAPABILITY-UPDATE message to SGSN to request for the current wireless capability of MS. This counter counts
the number of BSC's sending this message.
Measurement
Point

this counter increments. The measurement point is A1.
Unit
Related Features
Times
Definition
Number of RA-CAPABILITY-UPDATE-ACK message received
Description
SGSN sends the RA-CAPABILITY-UPDATE-ACK message to BSC to

indicate the current wireless capability of MS. This counter counts
Measurement
Point
When BSC receives a RA-CAPABILITY-UPDATE-ACK message

from SGSN, this counter increments. The measurement point is
A2.
Unit
Related Features
Times
2109
C901340006 Number
of wireless status PDU
Definition
Number of wireless status PDU messages sent by BSC
Description
BSC sends the wireless status PDU message to indicate SGSN that
abnormality occurs at radio interface. This counter counts the
Usage
Measurement
Point

counter increments. The measurement point is A.
Unit
Related Features
Times
sent by BSC due to losing
Definition
Number of wireless status messages sent by BSC due to losing

Description
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio interface. This counter counts the number of BSC's sending this message due to Losing wireless association with MS.
Usage
Measurement
Point
When BSC sends a RADIO-STATUS message to SGSN due to Losing wireless association with MS, this counter increments.
Unit
2110
Times
Related Features
sent by BSC due to bad link
quality
Definition
Number of wireless status messages sent by BSC due to bad link

quality
Description
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio interface. This counter counts the number of BSC's sending this message due to bad link quality.
Usage
Measurement
Point

Unit
Related Features
Times
sent by BSC due to cell
reselection command
Definition
Number of wireless status messages sent by BSC due to cell reselection command
Description
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio interface. This counter counts the number of BSC's sending this message due to cell reselection command.
Usage
Measurement
Point

Unit
Related Features
Times
2111
FLOW-CONTROL-BVC
Definition
Number of FLOW-CONTROL-BVC messages sent by BSC
Description
BSC sends the FLOW-CONTROL-BVC message to notify SGSN of

the current BVC flow control policy. This counter counts the number of BSC's sending this message.
Measurement
Point

increments. The measuremnt point is A1.
Unit
Related Features
Times
BSC
2112
Definition
Number of FLOW-CONTROL-BVC-ACK messages received by BSC
Description
SGSN sends the FLOW-CONTROL-BVC-ACK message to notify BSC

that the current BVC flow control policy is accepted. This counter
Measurement
Point

Unit
Related Features
Times
FLOW-CONTROL-MS
Definition
Number of FLOW-CONTROL-MS messages sent by BSC
Description
BSC sends the FLOW-CONTROL-MS message to notify SGSN of the

current MS flow control policy. This counter counts the number of
BSC's sending this message.
Measurement
Point
When BSC sends the FLOW-CONTROL-MS message, this counter

Unit
Related Features
Times
2113
FLOW-CONTROL-MS-ACK
Definition
Number of FLOW-CONTROL-MS-ACK messages received by BSC
Description
SGSN sends the FLOW-CONTROL-MS-ACK message to notify BSC

that the current MS flow control policy is accepted. This counter
Measurement
Point

Unit
Related Features
Times
FLOW-CONTROL-PFC
Definition
2114
Number of FLOW-CONTROL-PFC messages sent by BSC
Description
BSC sends the FLOW-CONTROL-PFC message to notify SGSN of

the flow control policy for one or multiple PFCs of designated MS.
Measurement
Point
When BSC sends the FLOW-CONTROL-PFC message, this counter

Unit
Related Features
Times
BSC
Definition
Number of FLOW-CONTROL-PFC-ACK messages received by BSC
Description
SGSN sends the FLOW-CONTROL-PFC-ACK message to notify BSC

that the PFC flow control policy for designated MS is accepted. This
counter counts the number of BSC's receiving this message.
Measurement
Point

Unit
Related Features
Times
2115
status messages sent by
BSC
Definition
Number of status messages sent by BSC
Description
message.
Measurement
Point
When BSC sends the STATUS message, this counter increments.

Unit
Related Features
Times
by BSC
Definition
2116
Number of status messages received by BSC
Description
message.
Measurement
Point
When BSC receives the STATUS message, this counter increments. The measurement point is A2.
Unit
Related Features
Times
BVCI Unknown
Definition
Description
Measurement
Point
When BSC sends a "STATUS" message due to BVCI Unknown,

Unit
Related Features
Times
Definition
Description
Measurement
Point
When BSC sends a "STATUS" message due to cell service congestion, this counter increments.
Unit
Related Features
Times
2117
protocol error
Definition
Description
Measurement
Point
When BSC sends a "STATUS" message due to protocol error, this

counter increments.
Unit
Related Features
Times
Processor overload
Definition
Number of status messages sent with Processor overload
Description
message due to processor overload.
Measurement
Point
When BSC sends a "STATUS" message due to processor overload,

Unit
Related Features
Times
with BVCI Unknown
Definition
Description
2118
Number of status messages received with BVCI Unknown

BSC sends the status message to SGSN to indicate that abnormality occurs. This counter counts the number of BSC's receiving this
Measurement
Point
Unit
Related Features
When BSC receives a "STATUS" message due to BVCI Unknown,

Times
Definition
Description
Measurement
Point
When BSC receives a "STATUS" message due to cell service congestion, this counter increments.
Unit
Related Features
Times
with protocol error
Definition
Description
Measurement
Point
When BSC receives a "STATUS" message due to protocol error,

Unit
Related Features
Times
2119
Definition
Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter counts the number of BSC's receiving this
message due to processor overload.
Measurement
Point
When BSC receives a "STATUS" message due to processor overload, this counter increments.
Unit
Related Features
Times
DOWNLOAD-BSS-PFC
Definition
Number of DOWNLOAD-BSS-PFC messages sent by BSC
Description
BSC sends the DOWNLOAD-BSS-PFC message to request SGSN

to initiate the CREATE-BSS-PFC process. This counter counts the
Measurement
Point
When BSC sends the DOWNLOAD-BSS-PFC message, this

Unit
Related Features
2120
Times
BVCCREATE-BSS-PFC
Definition
Number of BVCCREATE-BSS-PFC messages received by BSC
Description
SGSN sends the CREATE-BSS-PFC message to request BSC to create or modify a packet flow control context. This counter counts
Measurement
Point

Unit
Related Features
Times
CREATE-BSS-PFC-ACK
Definition
Number of CREATE-BSS-PFC-ACK messages sent by BSC
Description
BSC sends the CREATE-BSS-PFC-ACK message to acknowledge the

request of SGSN creating or modifying a packet flow control context. This counter counts the number of BSC's sending this message.
Measurement
Point

2121
Unit
Related Features
Times
CREATE-BSS-PFC-NACK
Definition
Number of CREATE-BSS-PFC-NACK messages sent by BSC
Description
BSC sends the CREATE-BSS-PFC-NACK message to deny the request of SGSN creating or modifying a packet flow control context.
Measurement
Point
When BSC sends a CREATE-BSS-PFC-NACK message, this counter

Unit
Related Features
2122
Times
C901340030 Number
of MODIFY-BSS-PFC
Definition
Number of MODIFY-BSS-PFC messages sent by BSC
Description
BSC sends the MODIFY-BSS-PFC message to SGSN to request for

modifying the packet flow control context. This counter counts the
Measurement
Point
When BSC sends the MODIFY-BSS-PFC message, this counter

Unit
Related Features
Times
MODIFY-BSS-PFC-ACK
Definition
Description
Measurement
Point
Number of MODIFY-BSS-PFC-ACK messages received by BSC

SGSN sends the MODIFY-BSS-PFC-ACK message to BSC to confirm the modification of packet flow control context. This counter
When BSC receives a MODIFY-BSS-PFC-ACK message,
this
2123
Unit
Related Features
Times
C901340032 Number
of DELETE-BSS-PFC
Definition
Number of DELETE-BSS-PFC messages received by BSC
Description
SGSN sends the DELETE-BSS-PFC message to request BSC to

delete a packet flow control context. This counter counts the
number of BSC's receiving this message.
Measurement
Point
When BSC receives a DELETE-BSS-PFC message, this counter increments. The measurement point is A1.
Unit
Related Features
2124
Times
DELETE-BSS-PFC-ACK
Definition
Number of DELETE-BSS-PFC-ACK messages sent by BSC
Description
BSC sends the DELETE-BSS-PFC-ACK message to SGSN to confirm

the deletion of specified packet flow control context. This counter
counts the number of BSC's sending this message.
Measurement
Point

Unit
Related Features
Times
DELETE-BSS-PFC-REQ
Definition
Description
Related Features
Number of DELETE-BSS-PFC-REQ messages received by BSC

2125
PS-HANDOVER-REQUI
RED messages sent by BSC
Statistics object
Description
BSC
This counter counts the number of PS-HANDOVER-REQUIRED
messages sent to SGSN from BSC in IP transmission mode. The
counter increments when BSC sends a PS-HANDOVER-REQUIRED
REQUIRED MESSAGES SENT BY BSC
OF
PS-HANDOVER-
Times
PS-HANDOVER-REQUIRE
D-ACK messages received
by BSC
Statistics object
Description
2126
BSC
After a PS handover request is acknowledged, SGSN sends the
PS-HANDOVER-REQUIRED-ACK message to BSC. This counter
counts the number of PS-HANDOVER-REQUIRED-ACK messages
received by BSC in IP transmission mode. The counter increments
when BSC receives the PS-HANDOVER-REQUIRED-ACK message.

REQUIRED-ACK MESSAGES RECEIVED BY BSC
OF
PS-HANDOVER-
Times
PS-HANDOVER-REQUIRE
by BSC
Statistics object
Description
BSC
If SGSN receives the non-acknowledgement message for PS handover request from BSC, then SGSN sends the PS-HANDOVERREQUIRED-NACK message back to BSC. This counter counts the
number of PS-HANDOVER-REQUIRED-NACK messages received by
BSC in IP transmission mode. The counter increments when BSC
receives the PS-HANDOVER-REQUIRED-NACK message. The measurement point is A, as shown in Figure 2224.
2127
FIGURE 2224 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUIRED-NACK MESSAGES RECEIVED BY BSC
Times
PS-HANDOVER-REQUEST
Statistics object
Description
2128
BSC
When SGSN receives the PS-HANDOVER-REQUIRED message from
BSC, it sends the PS-HANDOVER-REQUEST message back to BSC.
This counter counts the number of PS-HANDOVER-REQUEST messages received by BSC from SGSN. The counter increments when
BSC receives the PS-HANDOVER-REQUEST message. The measurement point is A2, as shown in Figure 2225.

REQUEST MESSAGES RECEIVED BY BSC
OF
PS-HANDOVER-
Times
PS-HANDOVER-REQUES
T-ACK messages sent by
BSC
Statistics object
Description
BSC
SGSN, it implements PS handover flow and sends the PS-HANDOVER-REQUEST message back to SGSN. This counter counts the
number of PS-HANDOVER-REQUEST messages sent by BSC in IP
transmission mode. The counter increments when BSC sends the
PS-HANDOVER-REQUEST-ACK message. The measurement point
2129

REQUEST-ACK MESSAGES SENT BY BSC
OF
PS-HANDOVER-
Times
PS-HANDOVER-REQUES
T-NACK messages sent by
BSC
Statistics object
Description
2130
BSC
SGSN, it implements PS handover flow. During the handover, if
the channel request fails or the cell does not support PS handover,
then creating MS or PS instance will fail. This counter counts the
number of messages, which indicate failure of creating MS or PS

instance, sent by BSC in IP transmission mode. The counter increments when BSC sends the PS-HANDOVER-REQUEST-NACK message. The measurement point is A3, as shown in Figure 2227.
REQUEST-NACK MESSAGES SENT BY BSC
OF
PS-HANDOVER-
Times
PS-HANDOVER-COMPL
ETE messages sent by BSC
Statistics object
BSC
2131
Description
When the destination cell receives the first RLC/MAC block sent
from MS, it indicates that the handover is completed. This counter
counts the number of PS-HANDOVER-COMPLETE messages sent
to SGSN from BSC in IP transmission mode. The counter increments when BSC sends the PS-HANDOVER-REQUEST-COMPLETE
COMPLETE MESSAGES SENT BY BSC
OF
PS-HANDOVER-
Times
PS-HANDOVER-CANCEL
Statistics object
Description
2132
BSC
If PS handover fails or waiting for handover is timeout, BSC sends
the PS-HANDOVER-CANCEL message to SGSN. This counter
counts the number of PS-HANDOVER-CANCEL messages sent by
BSC in IP transmission mode. The counter increments when BSC
sends the PS-HANDOVER-CANCEL message. The measurement

CANCEL MESSAGES SENT BY BSC
OF
NUMBER
OF
PS-HANDOVER-
Times
PS-HANDOVER-REQUEST
BSC
Statistics object
Description
BSC
SGSN, the message might contains the field Service UTRAN CCO,
which indicates that 2G/3G handover is preferred. This counter
counts the number of PS-HANDOVER-REQUEST messages, which
contains the field Service UTRAN CCO, received by BSC in IP transmission mode. After BSC receives the PS-HANDOVER-REQUEST
message from SGSN, it decodes the message to decide whether
the message contains the field Service UTRAN CCO. If the message contains the field, the counter increments. The measurement
2133
FIGURE 2230 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUEST MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Times
C901340044 Number
of CREATE-BSS-PFC
BSC
Statistics object
Description
2134
BSC
When BSC receives the CREATE-BSS-PFC message from SGSN, the
message might contain the field Service UTRAN CCO. This counter
counts the number of CREATE-BSS-PFC messages, which contains
the field Service UTRAN CCO, received by BSC in IP transmission
mode. After BSC receives the CREATE-BSS-PFC message from
SGSN, it decodes the message to decide whether the message
contains the field Service UTRAN CCO. If the message contains
the field, the counter increments. The measurement point is A, as
FIGURE 2231 MEASUREMENT POINT OF NUMBER OF CREATE-BSS-PFC

MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Times
2135
2136
Chapter
41
NSE on IPGB HOST

Measurement
Table of Contents
Overview...................................................................... 2138
C901350001 Number of CS Paging received by BSS ........... 2139
C901350002 Number of PS Paging received by BSS ........... 2139
C901350009 Number of FLUSH-LL message received ......... 2142
C901350010 Number of FLUSH-LL-ACK message sent......... 2142
C901350011
Number
of
LLC-DISCARDED
message
sent............................................................................. 2143
C901350013 Number of BVC_BLOCK_ACK message received.......................................................................... 2144
C901350015 Number of BVC-UNBLOCK-ACK message received.......................................................................... 2144
C901350017
Number
of
BVC-RESET
message
received.......................................................................... 2145
C901350018
Number
of
BVC-RESET-ACK
message
sent............................................................................. 2146
C901350019 Number of BVC-RESET-ACK message received.......................................................................... 2146
C901350020 Number of PERFORM LOCATION-REQUEST
message received.......................................................... 2147
message sent ............................................................... 2147
C901350022 Number of PERFORM-LOCATION-ABORT message received................................................................ 2148
sent............................................................................. 2148
C901350024 Number of POSITION-RESPONSE message received.......................................................................... 2149
C901350025 Number of status messages sent .................. 2149
C901350026 Number of status messages received ............. 2150
2137
error............................................................................ 2151
C901350030 Number of status messages sent with processor
overload....................................................................... 2152
C901350031 Number of status messages sent with semantically incorrect PDU ........................................................ 2152
mandatory information element....................................... 2153
mandatory IE................................................................ 2153
conditional IE................................................................ 2154
C901350035 Number of status messages sent with unexpected conditional IE...................................................... 2154
C901350036 Number of status messages sent with conditional IE error ............................................................... 2155
status incompatible error................................................ 2155
unknown ...................................................................... 2156
C901350042 Number of status messages received with BVC
blocking ....................................................................... 2157
C901350043 Number of status messages received with semantically incorrect PDU................................................. 2158
C901350044 Number of status messages received with invalid
mandatory IE................................................................ 2158
C901350045 Number of status messages received with missing mandatory IE .......................................................... 2159
C901350046 Number of status messages received with missing conditional IE........................................................... 2159
C901350047 Number of status messages received with unexpected conditional IE...................................................... 2160
C901350048 Number of status messages received with conditional IE error............................................................. 2160
C901350049 Number of status messages received with protocol status incompatible error ........................................ 2161
C901350050 Number of status messages received with SGSN
congestion.................................................................... 2161
Overview
The NSE measurement on IPGB HOST takes a single NSE as the
measurement entity. It performs statistics for paging message,
status indication message, and signaling BVC resetting message
received by NSE at BSS.
2138
Chapter 41 NSE on IPGB HOST Measurement
Statistic unit in this measurement is the single NSE.
Definition
Number of CS Paging received by BSS
Description
This counter counts the number of PAGING CS messages received

Usage
The counter is used to find out the frequency of SGSN's CS paging

to MS.
Measurement
Point
When BSS receives a message of which the type is GB_PAGING_CS, the counter increments.
Unit
Related Features
Times
Definition
Number of PS Paging received by BSS
Description
This counter counts the number of PAGING PS messages received

Usage
The counter is used to find out the frequency of SGSN's PS paging

to MS.
Measurement
Point
When BSS receives a message of which the type is GB_PAGING_PS, the counter increments.
Unit
Related Features
Times
Definition
Description
Number of SUSPEND message sent

When BSS receives the suspending GPRS service message from
MS, BSS will send the SUSPEND message to SGSN. This counter
counts the number of sending SUSPEND message from NSE.
2139
Usage
The counter is used to find out the frequency of MS's terminating

GPRS service.
Measurement
Point
When BSS sends the SUSPEND message, the counter increments.
Unit
Related Features
Times
SUSPEND-ACK message
received
Definition
Number of SUSPEND-ACK message received
Description
When SGSN receives the SUSPEND message from BSS, SGSN will
send the SUSPEND_ACK message to BSS. This counter counts the
number of SUSPEND_ACK messages received by NSE.
Usage
The counter is used to find out cases in which SGSN has response
when MS requests for terminating GPRS service.
Measurement
Point
When BSS sends the SUSPEND_ACK message, the counter increments.
Unit
Related Features
Times
received
Definition
Description
When SGSN receives the SUSPEND message from BSS, it checks

the SUSPEND message content.
If the message content is
incorrect or fault occurs at SGSN, SGSN will send the SUSPEND_NACK message to BSS. This counter counts the number of
SUSPEND_NACK messages received by NSE.
Usage
The counter is used to find out cases in which SGSN has no response when MS requests for terminating GPRS service.
Measurement
Point
When BSS sends the SUSPEND_NACK message, the counter increments.
Unit
Related Features
2140
Number of SUSPEND-NACK message received
Times
RESUME message sent
Definition
Number of RESUME message sent
Description
When problems that cause MS to suspend disappear, BSS might

send the RESUME message to SGSN to notify it to resume GPRS
service of MS. This counter counts the number of sending RESUME
message by BSS.
Usage
The counter is used to find out the frequency of MS's resuming

GPRS service.
Measurement
Point
Unit
Related Features
When BSS sends the RESUME message, the counter increments.

Times
RESUME-ACK message
received
Definition
Number of RESUME-ACK message received
Description
When SGSN receives the RESUME message from BSS, SGSN will
send the RESUME_ACK message to BSS. This counter counts the
number of RESUME_ACK messages received by NSE.
Usage
The counter is used to find out causes due to which SGSN has no
response when MS requests for resuming GPRS service.
Measurement
Point
When BSS sends the RESUME_ACK message, the counter increments.
Unit
Related Features
Times
RESUME-NACK message
received
Definition
Description
Number of RESUME-NACK message received

If the MS in the RESUME PDU message sent from BSS is not found
at SGSN, SGSN willl send the RESUME_NACK message to BSS.
2141
This message contains the failure cause, that is, unknown MS.
At this moment, BSS will terminate the RESUME process and ask
MS to update routing area. This counter counts the number of
RESUME_NACK messages received by NSE.
Usage
The counter is used to find out cases in which SGSN has no response when MS requests for resuming GPRS service.
Measurement
Point
When BSS receives the RESUME_NACK message, the counter increments.
Unit
Related Features
Times
C901350009 Number
of FLUSH-LL message
received
Definition
Number of FLUSH-LL message received
Description
When SGSN detects that a MS changes cell through cell update

or routing area update, SGSN will send the FLUSH_LL message to
the old BVC to initiate the cell update process on NSE. This counter
counts the number of FLUSH_LL messages received by NSE.
Usage
The counter is used to find out the frequency of MS's changing cell.
Measurement
Point
When BSS receives the FLUSH_LL message, the counter increments.
Unit
Related Features
Times
FLUSH-LL-ACK message
sent
Definition
2142
Number of FLUSH-LL-ACK message sent
Description
When BSS receives the FLUSH_LL message from SGSN, BSS will
send the FLUSH_LL_ACK message to SGSN. This counter counts
the number of sending FLUSH_LL_ACK message from NSE.
Usage
The counter is used to find out that, after MS changes cell, whether
the MS's LLC PDU buffer is deleted in the old cell or moved to the
new cell in the routing area.
Measurement
Point
When BSS sends the FLUSH_LL_ACK message, the counter increments.
Unit
Related Features
Times
LLC-DISCARDED message
sent
Definition
Description
Usage
Measurement
Point
Unit
Related Features
Number of LLC-DISCARDED message sent

When the LLC PDU stored in BSS is deleted, the LLC_DISCARDED
message is sent to SGSN. This counter counts the number of sending LLC_DISCARDED message from NSE.
The counter is used to find out the storage of LLC PDU in BSS.
When BSS sends the LLC_DISCARDED message, the counter increments.
Times
Definition
Description
When BSS blocks a BVC, it will send the BVC_BLOCK message to

SGSN to start the timer T1. BSS will identify the blocked BVC and
stop sending uplink data of the BVC. Meanwhile, cells associated
with the BVC do not receive downlink data any more. This counter
counts the number of sending BVC_BLOCK message from NSE.
Usage

to block BVC.
Measurement
Point
When BSS sends the BVC_BLOCK message, the counter increments.
Unit
Related Features
Times
2143
C901350013 Number
of BVC_BLOCK_ACK
message received
Definition
Description
Usage
Measurement
Point
Unit
Related Features
Number of BVC-BLOCK-ACK message received

When SGSN receives the BVC_BLOCK message from BSS, it identifies the BVC to be blocked and stops sending data to the BVC, and
replies the BVC_BLOCK_ACK message to BSS. This counter counts
the number of BVC_BLOCK_ACK messages received by NSE.
The counter is used to find out cases when BVC is blocked.
increments.
Times
BVC-UNBLOCK message
sent
Definition
Description
When BSS unblocks the blocked BVC, it will send the BVC_UNBLOCK message to SGSN. This counter counts the number of sending BVC_UNBLOCK message from NSE.
Usage

to unblock BVC.
Measurement
Point
When BSS sends the BVC_UNBLOCK message, the counter increments.
Unit
Related Features
Times
C901350015 Number
of BVC-UNBLOCK-ACK
message received
Definition
2144
Number of BVC-UNBLOCK-ACK message received
Description
Usage
Measurement
Point
Unit
Related Features
When SGSN receives the BVC_UNBLOCK message from BSS,

it identifies the BVC to be unblocked and replies the BVC_UNBLOCK_ACK message to BSS. This counter counts the number of
BVC_UNBLOCK_ACK messages received by NSE.
The counter is used to find out cases when BVC is unblocked.
increments.
Times
Definition
Description
This counter counts the number of PCU sending signaling BVC resetting message through Gb interface.
Usage
The counter is used to find out the frequency of requesting to

restart BVC due to BVC failure.
Measurement
Point
When NSE at BSC sends message of which the type is BVC_RESET

and BVCI is zero, the counter increments.
Unit
Related Features
Times
BVC-RESET message
received
Definition
Description
Usage
Measurement
Point
Unit
Related Features

This counter counts the number of PCU's receiving the signaling
BVC resetting message.
The counter is used to find out cases when BVC is restarted.
When NSE at BSC receives message of which the type is BVC_RESET and BVCI is zero, the counter increments.
Times
2145
sent
Definition
Description
Usage
Measurement
Point
Unit
Related Features
Number of BVC-RESET-ACK message sent

When PCU receives the signaling BVC resetting message from Gb
interface, it replies the signaling BVC resetting acknowledgement
message. This counter counts the number of NSE's sending signaling BVC resetting acknowledgement message.
The counter is used to find out cases of SGSN initializing BVC.
When NSE at BSC sends message of which the type is BVC_RESET_ACK and BVCI is zero, the counter increments.
Times
received
Definition
Description
Usage
Measurement
Point
Unit
Related Features
2146
Number of BVC-RESET-ACK message received

Number of PCU's receiving the signaling BVC resetting acknowledgement message. This counter counts the number of NSE's receiving signaling BVC resetting acknowledgement message.
The counter is used to find out cases of BVC initialization.
When NSE at BSC receives message of which the type is BVC_RESET_ACK and BVCI is zero, the counter increments.
Times
C901350020 Number
of PERFORM
LOCATION-REQUEST
message received
Definition
Number of PERFORMLOCATION-REQUEST message received
Description
When SGSN receives the location request and BSS supports LCS,
SGSN will start the locating process and send PERFORM_LOCATION_REQUEST message to BSS. This counter counts the number
of BSS's receiving the location request message.
Usage
The counter is used to find out the frequency of SGSN's sending

location request to BSS.
Measurement
Point

Unit
Related Features
Times
PERFORM-LOCATION-RE
SPONSE message sent
Definition
Number of PERFORM_LOCATION_RESPONSE message sent
Description
After BSS receives the PERFORM_LOCATION_REQUEST message,

it will send the location request to SMLC and wait for SMLC's response, and then send the result in the PERFORM_LOCATION_RESPONSE message to SGSN. This counter counts the number of
BSS's sending the location request response message.
Usage
The counter is used to find out BSS's response to the location request from SGSN.
Measurement
Point

Unit
Related Features
Times
2147
PERFORM-LOCATION-AB
Definition
Number of PERFORM_LOCATION_ABORT message received
Description
When SGSN initiates the location request before interruption

occurs, it sends the PERFORM_LOCATION_ABORT message to
BSS. This counter counts the number of BSS's receiving the
PERFORM_LOCATION_ABORT message.
Usage
The counter is used to find out the frequency of SGSN's terminating location towards BSS.
Measurement
Point

Unit
Related Features
Times
POSITION-COMMAND
message sent
Definition
Description
BSS triggers the positioning command process by sending POSITION_COMMAND message to SGSN. This process is valid only
when positioning a MS. This counter counts the number of BSS's
sending POSITION_COMMAND message.
Usage

to implement positioning command to SGSN.
Measurement
Point
When BSS sends the POSITION_COMMAND message, the counter

increments.
Unit
Related Features
2148
Number of POSITION_COMMAND message sent
Times
POSITION-RESPONSE
message received
Definition
Number of POSITION_RESPONSE message received
Description
When SGSN receives the TOM message, SGSN will send the POSITION_RESPONSE message to BSS to trigger the position response
process. The TOM message is contained in LLC PDU, and the
LLC PDU contains the RRLP message of a MS. This position response process is valid only when positioning a MS. This counter
counts the number of BSS's receiving the POSITION_RESPONSE
message.
Usage
The counter is used to find out the frequency of SGSN's requesting

to implement positioning command to BSS.
Measurement
Point
When BSS receives the POSITION_RESPONSE message, the

counter increments.
Unit
Related Features
Times
Definition
Number of status messages sent
Description
When NSE receives downlink BSSGP PDU, if there is any abnormality, NSE will send the STATUS message to the opposite end entity.
The STATUS message sent indicates causes of the abnormality:
counts the number of abnormality that occurs.
Usage
The counter is used to find out abnormality occurring when NSE

Measurement
Point
When NSE at BSC sends message of which the type is STATUS to

the opposite end entity, the counter increments.
Unit
Related Features
Times
2149
Definition
Number of status messages received
Description
If the BSSGP PDU sent by NSE to SGSN is abnormal, NSE will receive the STATUS message returned from the opposite end. The
STATUS message returned indicates causes of the abnormality:
counts the number of STATUS messages returned from SGSN.
Usage
The counter is used to find out abnormality occurring when SGSN

Measurement
Point
When NSE receives the STATUS message, the counter increments.
Unit
Related Features
Times
BVCI Unknown
Definition
Description

to opposite end entity, the message indicating "BVCI unknown".
Usage

to "BVCI unknown" occurring when NSE receives downlink BSSGP
PDU.
Measurement
Point
the message indicates that the abnormality is due to "BVCI unknown", the counter increments.
Unit
Related Features
2150
Times
Definition
Description

to opposite end entity, the message indicating "cell traffic congestion".
Usage

to "cell traffic congestion" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "cell traffic
Unit
Related Features
Times
protocol error
Definition
Description

to opposite end entity, the message indicating "Protocol error".
Usage

to "Protocol error" occurring when NSE receives downlink BSSGP
PDU.
Measurement
Point
the message indicates that the abnormality is due to "Protocol error", the counter increments.
Unit
Related Features
Times
2151
processor overload
Definition
Number of status messages sent with processor overload
Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Processor
overload".
Usage

to "Processor overload" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Processor
Unit
Related Features
Times
semantically incorrect PDU
Definition
Number of status messages sent with semantically incorrect PDU
Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Semantically
incorrect PDU".
Usage

"Semantically incorrect PDU" occurring when NSE receives downlink BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Semantically
incorrect PDU", the counter increments.
Unit
Related Features
2152
Times
with invalid mandatory
information element
Definition
Number of status messages sent with invalid mandatory information element
Description

to opposite end entity, the message indicating "Invalid mandatory
information".
Usage

to "Invalid mandatory information" occurring when NSE receives
downlink BSSGP PDU.
Measurement
Point
When NSE sends the STATUS message to opposite end entity

and the message indicates that the abnormality is due to "Invalid
Unit
Related Features
Times
missing mandatory IE
Definition
Number of status messages sent with missing mandatory IE
Description

to opposite end entity, the message indicating "Missing mandatory
IE".
Usage

to "Missing mandatory IE" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Missing
Unit
Related Features
Times
2153
missing conditional IE
Definition
Number of status messages sent with missing conditional IE
Description

to opposite end entity, the message indicating "Missing conditional
IE".
Usage

to "Missing conditional IE" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Missing conditional IE", the counter increments.
Unit
Related Features
Times
unexpected conditional IE
Definition
Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Unexpected
conditional IE".
Usage

"Unexpected conditional IE" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Unexpected
Unit
Related Features
2154
Number of status messages sent with unexpected conditional IE
Times
conditional IE error
Definition
Number of status messages sent with conditional IE error
Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Conditional
IE error".
Usage

to "Conditional IE error" occurring when NSE receives downlink
BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "Conditional
Unit
Related Features
Times
protocol status incompatible
error
Definition
Number of status messages sent with protocol status incompatible

error
Description

to opposite end entity, the message indicating "PDU not compatible
with the protocol state".
Usage

NSE receives downlink BSSGP PDU.
Measurement
Point
the message indicates that the abnormality is due to "PDU not
Unit
Related Features
Times
2155
with BVCI unknown
Definition
Number of status messages received with BVCI unknown
Description

which indicate "BVCI unknown".
Usage

"BVCI unknown" occurring when SGSN receives downlink BSSGP
PDU.
Measurement
Point
When PCU receives STATUS message which indicates "BVCI unknown", the counter increments.
Unit
Related Features
Times
Definition
Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "cell traffic congestion".
Usage

to "cell traffic congestion" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "cell traffic

Unit
Related Features
Times
with protocol error
Definition
2156
Description

which indicate "Protocol error".
Usage

to "Protocol error" occurring when SGSN receives downlink BSSGP
PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Protocol error", the counter increments.
Unit
Related Features
Times
Definition
Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "Processor overload".
Usage

to "Processor overload" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Processor

Unit
Related Features
Times
with BVC blocking
Definition
Number of status messages received with BVC blocking
Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "BVCI-blocked".
Usage

to "BVCI-blocked" occurring when SGSN receives downlink BSSGP
PDU.
Measurement
Point
When PCU receives STATUS message which indicates "BVCIblocked", the counter increments.
Unit
Times
2157
Related Features
with semantically incorrect
PDU
Definition
Number of status messages received with semantically incorrect

PDU
Description

which indicate "Semantically incorrect PDU".
Usage

"Semantically incorrect PDU" occurring when SGSN receives downlink BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Semantically incorrect PDU", the counter increments.
Unit
Related Features
Times
with invalid mandatory IE
Definition
Description

which indicate "Invalid mandatory information".
Usage

to "Invalid mandatory information" occurring when SGSN receives
downlink BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Invalid

Unit
Related Features
2158
Number of status messages received with invalid mandatory IE
Times
with missing mandatory IE
Definition
Number of status messages received with missing mandatory IE
Description

which indicate "Missing mandatory IE".
Usage

to "Missing mandatory IE" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Missing

Unit
Related Features
Times
with missing conditional IE
Definition
Number of status messages received with missing conditional IE
Description

which indicate "Missing conditional IE".
Usage

to "Missing conditional IE" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Missing conditional IE", the counter increments.
Unit
Related Features
Times
2159
with unexpected conditional
IE
Definition
Number of status messages received with unexpected conditional

IE
Description

which indicate "Unexpected conditional IE".
Usage

"Unexpected conditional IE" occurring when SGSN receives downlink BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Unexpected

Unit
Related Features
Times
with conditional IE error
Definition
Description

which indicate "Conditional IE error".
Usage

to "Conditional IE error" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "Conditional

Unit
Related Features
2160
Number of status messages received with conditional IE error
Times
C901350049 Number
of status messages
received with protocol
status incompatible error
Definition
Number of status messages received with protocol status incompatible error
Description

which indicate "PDU not compatible with the protocol state".
Usage

SGSN receives downlink BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "PDU not

Unit
Related Features
Times
with SGSN congestion
Definition
Number of status messages received with SGSN congestion
Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "SGSN congestion".
Usage

to "SGSN congestion" occurring when SGSN receives downlink
BSSGP PDU.
Measurement
Point
When PCU receives STATUS message which indicates "SGSN congestion", the counter increments.
Unit
Related Features
Times
2161
2162
Chapter
42
BSSMAP Message
Measurement
Table of Contents
Overview...................................................................... 2165
C901360001 Number of ASSIGNMENT REQUEST messages........................................................................... 2166
C901360002 Number of ASSIGNMENT COMPLETE messages........................................................................... 2167
C901360003 Number of ASSIGNMENT FAILURE messages........................................................................... 2168
C901360004 Number of RESOURCE REQUEST messages........................................................................... 2168
C901360005 Number of RESOURCE INDICATION messages........................................................................... 2169
C901360006 Number of PAGING messages ....................... 2170
C901360007 Number of CIPHER MODE COMMAND messages........................................................................... 2170
C901360008 Number of CIPHER MODE COMPLETE messages........................................................................... 2171
C901360009 Number of CIPHER MODE REJECT messages........................................................................... 2172
C901360010 Number of sent CLASSMARK UPDATE messages........................................................................... 2172
C901360011 Number of received CLASSMARK UPDATE messages........................................................................... 2173
C901360012 Number of QUEUING INDICATION messages........................................................................... 2173
C901360013 Number of COMPLETE LAYER 3 INFORMATION
messages ..................................................................... 2174
C901360014 Number of CLASSMARK REQUEST messages........................................................................... 2175
C901360015 Number of uplink LOAD INDICATION messages........................................................................... 2175
C901360016 Number of downlink LOAD INDICATION messages........................................................................... 2176
C901360017 Number of HANDOVER REQUEST messages........................................................................... 2177
C901360018 Number of HANDOVER REQUIRED messages........................................................................... 2177
C901360019 Number of HANDOVER COMMAND messages........................................................................... 2178
C901360020 Number of HANDOVER REQUEST ACK messages........................................................................... 2179
C901360021 Number of HANDOVER COMPLETE messages........................................................................... 2180
2163
C901360022 Number of HANDOVER SUCCEEDED messages........................................................................... 2181

C901360023 Number of HANDOVER CANDIDATE ENQUIRE
messages ..................................................................... 2182
C901360024 Number of HANDOVER CANDIDATE RESPONSE
messages ..................................................................... 2183
C901360025 Number of HANDOVER FAILURE messages........................................................................... 2183
C901360026 Number of HANDOVER PERFORMED messages........................................................................... 2184
C901360027 Number of HANDOVER REQUIRED REJECT messages........................................................................... 2185
C901360028 Number of HANDOVER DETECT messages........................................................................... 2185
C901360029 Number of CLEAR COMMAND messages ......... 2186
C901360030 Number of CLEAR COMPLETE messages ......... 2187
C901360031 Number of CLEAR REQUEST messages........... 2187
C901360032 Number of SAPI "N" REJECT messages .......... 2188
C901360033 Number of UL CONFUSION messages ............ 2188
C901360034 Number of DL CONFUSION messages ............ 2189
C901360035 Number of UL RESET messages .................... 2190
C901360036 Number of DL RESET messages .................... 2190
C901360037 Number of UL RESET ACKNOWLEDGE messages........................................................................... 2191
C901360038 Number of DL RESET ACKNOWLEDGE messages........................................................................... 2192
C901360039 Number of UL OVERLOAD messages .............. 2192
C901360040 Number of DL OVERLOAD messages .............. 2193
C901360041 Number of MSC INVOKE TRACE messages........................................................................... 2193
C901360042 Number of sent BSS INVOKE TRACE messages........................................................................... 2194
C901360043 Number of received BSS INVOKE TRACE messages........................................................................... 2195
C901360044 Number of sent CONNECTIONLESS INFORMATION messages ............................................................. 2195
C901360045 Number of received CONNECTIONLESS INFORMATION messages ......................................................... 2196
C901360046 Number of SUSPEND messages .................... 2196
C901360047 Number of RESUME messages ...................... 2197
C901360048 Number of Common ID messages ................. 2198
C901360049 Number of LSA INFORMATION messages......... 2198
C901360050 Number of PERFORM LOCATION REQUEST messages........................................................................... 2199
C901360051 Number of PERFORM LOCATION RESPONSE
messages ..................................................................... 2199
C901360052 Number of PERFORM LOCATION ABORT messages........................................................................... 2200
C901360053 Number of sent BLOCK messages.................. 2200
C901360054 Number of received BLOCK ACK messages........................................................................... 2201
C901360055 Number of sent UNBLOCK messages ............. 2202
C901360056 Number of received UNBLOCK ACK messages........................................................................... 2203
C901360057 Number of received BLOCK messages ............ 2203
C901360058 Number of sent BLOCK ACK messages ........... 2204
C901360059 Number of received UNBLOCK messages......... 2205
C901360060 Number of sent UNBLOCK ACK messages......... 2205
C901360061 Number of UL RESET CIRCUIT messages......... 2206
C901360062 Number of DL RESET CIRCUIT messages......... 2207
2164
Chapter 42 BSSMAP Message Measurement
C901360063 Number of UL RESET CIRCUIT ACK messages........................................................................... 2207

C901360064 Number of DL RESET CIRCUIT ACK messages........................................................................... 2208
C901360065 Number of UL CIRCUIT GROUP BLOCK messages........................................................................... 2209
C901360066 Number of DL CIRCUIT GROUP BLOCK messages........................................................................... 2209
C901360067 Number of UL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages .................................................. 2210
C901360068 Number of DL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages .................................................. 2211
C901360069 Number of UL CIRCUIT GROUP UNBLOCK messages........................................................................... 2211
C901360070 Number of DL CIRCUIT GROUP UNBLOCK messages........................................................................... 2212
C901360071 Number of UL CIRCUIT GROUP UNBLOCKING
ACKNOWLEDGE messages .............................................. 2213
C901360072 Number of DL CIRCUIT GROUP UNBLOCKING
C901360073 Number of UL UNEQUIPPED CIRCUIT messages........................................................................... 2214
C901360074 Number of DL UNEQUIPPED CIRCUIT messages........................................................................... 2215
C901360075 Number of CHANGE CIRCUIT messages ......... 2216
C901360076 Number of CHANGE CIRCUIT ACK messages........................................................................... 2216
C901360077 Number of HANDOVER PERFORMED ACK messages........................................................................... 2217
C901360078 The count of Sending INTERNAL HANDOVER REQUIRED ....................................................................... 2217
C901360079 The count of Receiving INTERNAL HANDOVER
COMMAND.................................................................... 2219
C901360080 The count of Receiving INTERNAL HANDOVER
REJECT ........................................................................ 2220
C901360081 Number of INTERNAL HANDOVER ENQUIRY
messages ..................................................................... 2220
C901360082 Number of UL RESET IP RESOURCE messages........................................................................... 2221
C901360083 Number of UL RESET IP RESOURCE ACKOWNLEDGE messages........................................................... 2222
C901360084 Number of DL RESET IP RESOURCE messages........................................................................... 2222
C901360085 Number of DL RESET IP RESOURCE ACKNOWLEDGE messages ............................................................ 2223
Overview
The BSSMAP message measurement performs statistics for various
BSSMAP messages at A-interface. It is used to find out the frequency of various BSSMAP messages transmitted at A-interface.
When BSC receives the correct BSSMAP message from MSC, the
counter counts. The measurement point is A
2165
FIGURE 2232 MEASUREMENT POINT OF MSC SENDING BSSMAP

MESSAGE TO BSC
Before BSC sends the BSSMAP message to MSC, the counter

counts. The measurement point is A
FIGURE 2233 MEASUREMENT POINT OF BSC SENDING BSSMAP
MESSAGE TO MSC
Statistic unit in this measurement is Control Main Processor (CMP).
ASSIGNMENT REQUEST
messages
Definition
2166
Number of ASSIGNMENT REQUEST messages
Description
For one paging, MSC sends a ASSIGNMENT REQUEST message to

BSS, requesting BSC to change the current channel to a TCH. During the paging process, MSC can also change mode at radio interface through the ASSIGNMENT REQUEST message. This counter
counts the number of assignment request messages in A-interface
BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of assignment request messages transmitted at A-interface.
Measurement
Point
When BSC receives the ASSIGNMENT REQUEST message, the

FIGURE 2234 MEASUREMENT POINT OF BSC RECEIVING

ASSIGNMENT REQUEST MESSAGE FROM MSC
Unit
Times
ASSIGNMENT COMPLETE
messages
Definition
Number of ASSIGNMENT COMPLETE messages
Description
During the mode modification (assignment) flow, after BSC receives the RR message ASSIGNMENT COMPLETE from Um interface, it sends an ASSIGNMENT COMPLETE message of A-interface
BSSMAP protocol to MSC. This counter counts the number of assignment completion messages in A-interface BSSMAP messages
sent to MSC from BSC.
Usage
The counter is used to find out the frequency of assignment completion messages transmitted at A-interface.
Measurement
Point
When BSC sends the ASSIGNMENT COMPLETE message to MSC,

FIGURE 2235 MEASUREMENT POINT OF BSC SENDING
ASSIGNMENT COMPLETE MESSAGE TO MSC
Unit
Times
2167
ASSIGNMENT FAILURE
messages
Definition
Number of ASSIGNMENT FAILURE messages
Description
This counter counts the number of assignment failure messages

in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of assignment failure

messages transmitted at A-interface.
Measurement
Point
When BSC sends the ASSIGNMENT FAILURE message to MSC, the

counter increments. The measurement point is A
ASSIGNMENT FAILURE MESSAGE TO MSC
Unit
Times
RESOURCE REQUEST
messages
Definition
2168
Number of RESOURCE REQUEST messages
Description
MSC sends the RESOURCE REQUEST message to BSC, the message indicating the mode of reporting resource condition to BSC
and relevant cell IDs. This counter counts the number of resource
request messages in A-interface BSSMAP messages received by
BSC.
Usage
The counter is used to find out the frequency of resource request

Measurement
Point
When BSC receives the RESOURCE REQUEST message, the

FIGURE 2237 MEASUREMENT POINT OF MSC SENDING RESOURCE

REQUEST MESSAGE TO BSC
Unit
Times
RESOURCE INDICATION
messages
Definition
Number of RESOURCE INDICATION messages
Description
After BSC receives the RESOURCE REQUEST message from MSC, it

sends the RESOURCE INDICATION message to MSC according to
MSC's requirement. The message contains the current resource
usage of relevant cells. This counter counts the number of resource indication messages in A-interface BSSMAP messages sent
to MSC from BSC.
Usage
The counter is used to find out the frequency of resource indication

Measurement
Point
When BSC sends the RESOURCE INDICATION message to MSC,

FIGURE 2238 MEASUREMENT POINT OF BSC SENDING RESOURCE
INDICATION MESSAGE TO MSC
Unit
Times
2169
PAGING messages
Definition
Number of PAGING messages
Description
When MSC needs to page a MS, it sends a PAGING message to BSC

through A-interface. This counter counts the number of paging
messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of paging messages

transmitted at A-interface.
Measurement
Point
When BSC receives the PAGING message, the counter increments.

The measurement point is A.
FIGURE 2239 MEASUREMENT POINT OF MSC SENDING PAGING
MESSAGE TO BSC
Unit
Times
CIPHER MODE COMMAND
messages
Definition
2170
Number of CIPHER MODE COMMAND messages
Description
When MSC decides to modify the cipher mode of channel, it sends

a CIPHER MODE COMMAND message to BSC through A-interface.
This counter counts the number of CIPHER MODE COMMAND messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of CIPHER MODE

COMMAND messages transmitted at A-interface.
Measurement
Point
When BSC receives the CIPHER MODE COMMAND message, the

FIGURE 2240 MEASUREMENT POINT OF MSC SENDING CIPHER

MODE COMMAND MESSAGE TO BSC
Unit
Times
CIPHER MODE COMPLETE
messages
Definition
Number of CIPHER MODE COMPLETE messages
Description
After BSC receives the CIPHERing MODE COMPLETE message (RR

message at Um interface) from MS , it sends the CIPHER MODE
COMPLETE message at A-interface to MSC as response. This
counter counts the number of CIPHER MODE COMPLETE messages
Usage

COMPLETE messages transmitted at A-interface.
Measurement
Point
When BSC sends the CIPHER MODE COMPLETE message to MSC,

FIGURE 2241 MEASUREMENT POINT OF BSC SENDING CIPHER
MODE COMPLETE MESSAGE TO MSC
Unit
Times
2171
CIPHER MODE REJECT
messages
Definition
Number of CIPHER MODE REJECT messages
Description
After BSC receives the CIPHERing MODE REJECT message (RR

message at Um interface) from MS , it sends the CIPHER MODE
REJECT message at A-interface to MSC as response. This counter
counts the number of CIPHER MODE REJECT messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage

REJECT messages transmitted at A-interface.
Measurement
Point
When BSC sends the CIPHER MODE REJECT message to MSC, the
FIGURE 2242 MEASUREMENT POINT OF BSC SENDING CIPHER
MODE REJECT MESSAGE TO MSC
Unit
Times
sent CLASSMARK UPDATE
messages
Definition
2172
Number of sent CLASSMARK UPDATE messages
Description
MS notifies the network of its classmark through the RR message

CLASSMARK CHANGE. After BSC receives the message, it sends
the CLASSMARK UPDATE message to MSC, the message containing
relevant information in the CLASSMARK CHANGE message. This
counter counts the number of CLASSMARK UPDATE messages in
A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the sending frequency of CLASSMARK UPDATE messages transmitted at A-interface.
Measurement
Point
When BSC sends the CLASSMARK UPDATE message to MSC, the

FIGURE 2243 MEASUREMENT POINT OF BSC SENDING CLASSMARK

UPDATE MESSAGE TO MSC
Unit
Times
received CLASSMARK
UPDATE messages
Definition
Number of received CLASSMARK UPDATE messages
Description
This counter counts the number of CLASSMARK UPDATE messages

in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of receiving CLASSMARK UPDATE messages transmitted at A-interface.
Measurement
Point
When BSC receives the CLASSMARK UPDATE message, the counter

increments. The measurement point is A.
FIGURE 2244 MEASUREMENT POINT OF MSC SENDING CLASSMARK
UPDATE MESSAGE TO BSC
Unit
Times
QUEUING INDICATION
messages
Definition
Number of QUEUING INDICATION messages
2173
Description
During the assignment process or handover resource allocation

process, if BSS fails to be allocated with radio channel, the queuing
mechanism is adopted. With this mechanism, the channel request
can be delayed and BSS waits for idle radio channels. In this case,
BSS needs to send a QUEUING INDICAITON message to MSC. This
counter counts the number of QUEUING INDICATION messages in
Usage
The counter is used to find out the frequency of QUEUING INDICATION messages transmitted at A-interface.
Measurement
Point
When BSC sends the QUEUING INDICATION message to MSC, the

FIGURE 2245 MEASUREMENT POINT OF BSC SENDING QUEUING
Unit
Times
COMPLETE LAYER 3
INFORMATION messages
Definition
Number of COMPLETE LAYER 3 INFORMATION messages
Description
This counter counts the number of COMPLETE LAYER 3 INFORMATION messages in A-interface BSSMAP messages sent to MSC from
BSC.
Usage
The counter is used to find out the frequency of COMPLETE LAYER

3 INFORMATION messages transmitted at A-interface.
Measurement
Point
When BSC sends the COMPLETE LAYER 3 INFORMATION message

to MSC, the counter increments. The measurement point is A.
FIGURE 2246 MEASUREMENT POINT OF BSC SENDING COMPLETE
LAYER 3 INFORMATION MESSAGE TO MSC
2174
Unit
Times
CLASSMARK REQUEST
messages
Definition
Number of CLASSMARK REQUEST messages
Description
When MSC wants MS classmark information, it sends a CLASSMARK REQUEST message to BSC. This counter counts the number
of CLASSMARK REQUEST messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of CLASSMARK REQUEST messages transmitted at A-interface.
Measurement
Point
When BSC receives the CLASSMARK REQUEST message, the

FIGURE 2247 MEASUREMENT POINT OF MSC SENDING CLASSMARK
Unit
Times
uplink LOAD INDICATION
messages
Definition
Number of uplink LOAD INDICATION messages
Description
According to certain principle, such as reporting periodically or reporting when triggered by threshold being exceeded, BSC reports
the current load of cells under it to MSC. After MSC receives the
message, it forwards the message to other relevant BSCs. This
counter counts the number of load indication messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of uplink load indication messages transmitted at A-interface.
2175
Measurement
Point
When BSC sends the LOAD INDICATION message to MSC, the

FIGURE 2248 MEASUREMENT POINT OF BSC SENDING LOAD
Unit
Times
C901360016 Number
of downlink LOAD
INDICATION messages
Definition
Number of downlink LOAD INDICATION messages
Description
This counter counts the number of load indication messages in

A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of downlink load

indication messages transmitted at A-interface.
Measurement
Point
When BSC receives the LOAD INDICATION message, the counter

FIGURE 2249 MEASUREMENT POINT OF MSC SENDING LOAD
INDICATION MESSAGE TO BSC
Unit
2176
Times
HANDOVER REQUEST
messages
Definition
Number of HANDOVER REQUEST messages
Description
MSC sends a HANDOVER REQUEST message to the target BSS

to request channel resource for handover. This counter counts
the number of handover request messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of handover request

Measurement
Point
When BSC receives the HANDOVER REQUEST message, the

FIGURE 2250 MEASUREMENT POINT OF MSC SENDING HANDOVER
Unit
Times
HANDOVER REQUIRED
messages
Definition
Number of HANDOVER REQUIRED messages
Description
When BSC decides to initiate an inter-BSC handover, it sends a

HANDOVER REQUIRED message to the MSC to which it belongs,
the message containing information of the target cell of handover.
This counter counts the number of HANDOVER REQUIRED messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of HANDOVER REQUIRED messages transmitted at A-interface.
Measurement
Point
When BSC sends the HANDOVER REQUIRED message to MSC, the

2177
FIGURE 2251 INTER-BSC HANDOVER PROCESS INITIATED BY BSC
Unit
Times
HANDOVER COMMAND
messages
Definition
2178
Number of HANDOVER COMMAND messages
Description
When BSC decides to initiate an inter-BSC handover, it sends a

HANDOVER REQUIRED message to the MSC to which it belongs,
the message containing information of the target cell of handover.
If MSC decides to perform handover and successfully establishes
channel at the target BSC, it sends the HANDOVER COMMAND
message as response. This counter counts the number of HANDOVER COMMAND messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of HANDOVER COMMAND messages transmitted at A-interface.
Measurement
Point
When BSC receives the HANDOVER COMMAND message, the

Unit
Times
HANDOVER REQUEST
ACK messages
Definition
Number of HANDOVER REQUEST ACK messages
Description
MSC sends a HANDOVER REQUEST message to the target BSS to

request channel resource for handover. If the target BSS successfully allocates and activates channel, then BSC puts a Um
interface RR message HANDOVER COMMAND in the HANDOVER
REQUEST ACK message and returns the message to MSC. This
counter counts the number of HANDOVER REQUEST ACK messages
Usage
The counter is used to find out the frequency of HANDOVER REQUEST ACK messages transmitted at A-interface.
Measurement
Point
When BSC sends the HANDOVER REQUEST ACK message to MSC,

2179
Unit
Times
HANDOVER COMPLETE
messages
Definition
2180
Number of HANDOVER COMPLETE messages
Description
When MS successfully performs handover to the target BSC, it

sends a Um interface RR message HANDOVER COMPLETE to BSC.
BSC then sends a HANDOVER COMPLETE message to MSC. This
counter counts the number of HANDOVER COMPLETE messages in
Usage
The counter is used to find out the frequency of HANDOVER COMPLETE messages transmitted at A-interface.
Measurement
Point
When BSC sends the HANDOVER COMPLETE message to MSC, the

Unit
Times
HANDOVER SUCCEEDED
messages
Definition
Number of HANDOVER SUCCEEDED messages
Description
If the inter-BSC handover succeeds, MSC sends the HANDOVER

SUCCEEDED message to the old BSC. This counter counts the
number of HANDOVER SUCCEEDED messages in A-interface
Usage
The counter is used to find out the frequency of HANDOVER SUCCEEDED messages transmitted at A-interface.
Measurement
Point
When BSC receives the HANDOVER SUCCEEDED message, the

2181
Unit
Times
HANDOVER CANDIDATE
ENQUIRE messages
Definition
Number of HANDOVER CANDIDATE ENQUIRE messages
Description
MSC sends a HANDOVER CANDIDATE ENQUIRY message to the

BSC to which the cell belongs. The message contains the maximum number of handover requests that can be triggered and candidate cells that can be used for handover. This counter counts the
number of HANDOVER CANDIDATE ENQUIRE messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of HANDOVER CANDIDATE ENQUIRE messages transmitted at A-interface.
Measurement
Point
When BSC receives the HANDOVER CANDIDATE ENQUIRE message, the counter increments. The measurement point is A1.
FIGURE 2256 PROCESS OF MSC SENDING HANDOVER CANDIDATE
ENQUIRE MESSAGE TO BSC
2182
Unit
Times
HANDOVER CANDIDATE
RESPONSE messages
Definition
Description
Number of HANDOVER CANDIDATE RESPONSE messages

After BSC receives the HANDOVER CANDIDATE ENQUIRE message, it initiates handover process for specified calls of the cell,
that is, BSC sends corresponding HANDOVER REQUIRED messages
to MSC. After all HANDOVER REQUIRED messages are sent, BSC
notifies MSC of the number of triggered handover through the
HANDOVER CANDIDATE RESPONSE message.
This counter counts the number of HANDOVER CANDIDATE RESPONSE messages in A-interface BSSMAP messages sent to MSC
from BSC.
Usage
The counter is used to find out the frequency of HANDOVER CANDIDATE RESPONSE messages transmitted at A-interface.
Measurement
Point
When BSC sends the HANDOVER CANDIDATE RESPONSE message

to MSC, the counter increments. The measurement point is A2.
FIGURE 2257 PROCESS OF MSC SENDING HANDOVER CANDIDATE
ENQUIRE MESSAGE TO BSC
Unit
Times
HANDOVER FAILURE
messages
Definition
Number of HANDOVER FAILURE messages
2183
Description
This counter counts the number of HANDOVER FAILURE messages

Usage
The counter is used to find out the frequency of HANDOVER FAILURE messages transmitted at A-interface.
Measurement
Point
When BSC sends the HANDOVER FAILURE message to MSC, the

FIGURE 2258 MEASUREMENT POINT OF BSC SENDING HANDOVER
FAILURE MESSAGE TO MSC
Unit
Times
HANDOVER PERFORMED
messages
Definition
Number of HANDOVER PERFORMED messages
Description
After BSC performs a handover (intra-cell or inter-cell) within itself,

it sends a HANDOVER PERFORMED messge to MSC. This counter
counts the number of HANDOVER PERFORMED messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of HANDOVER PERFORMED messages transmitted at A-interface.
Measurement
Point
When BSC sends the HANDOVER PERFORMED message to MSC,

PERFORMED MESSAGE TO MSC
Unit
2184
Times
HANDOVER REQUIRED
REJECT messages
Definition
Number of HANDOVER REQUIRED REJECT messages
Description
This counter counts the number of HANDOVER REQUIRED REJECT

Usage
The counter is used to find out the frequency of HANDOVER REQUIRED REJECT messages transmitted at A-interface.
Measurement
Point
When BSC receives the HANDOVER REQUIRED REJECT message,

FIGURE 2260 MEASUREMENT POINT OF MSC SENDING HANDOVER
REQUIRED REJECT MESSAGE TO BSC
Unit
Times
HANDOVER DETECT
messages
Definition
Number of HANDOVER DETECT messages
Description
This counter counts the number of HANDOVER DETECT messages

Usage
The counter is used to find out the frequency of HANDOVER DETECT messages transmitted at A-interface.
Measurement
Point
When BSC sends the HANDOVER DETECT message to MSC, the

2185

DETECT MESSAGE TO MSC
Unit
Times
C901360029 Number
of CLEAR COMMAND
messages
Definition
Number of CLEAR COMMAND messages
Description
MSC sends the CLEAR COMMAND message to BSC, asking BSC to

release the conneciton. This counter counts the number of CLEAR
COMMAND messages in A-interface BSSMAP messages received
by BSC.
Usage
The counter is used to find out the frequency of CLEAR COMMAND

Measurement
Point
When BSC receives the CLEAR COMMAND message, the counter

FIGURE 2262 CLEAR PROCESS
Unit
2186
Times
C901360030 Number
of CLEAR COMPLETE
messages
Definition
Number of CLEAR COMPLETE messages
Description
After BSC receives the CLEAR COMMAND message, it starts corresponding release process and returns the CLEAR COMPLETE message to MSC. This counter counts the number of CLEAR COMPLETE
messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of CLEAR COMPLETE

Measurement
Point
When BSC sends the CLEAR COMPLETE message to MSC, the

FIGURE 2263 CLEAR PROCESS
Unit
Times
C901360031 Number
of CLEAR REQUEST
messages
Definition
Number of CLEAR REQUEST messages
Description
BSC sends the CLEAR REQUEST message to MSC, asking MSC to

release the conneciton. This counter counts the number of CLEAR
REQUEST messages in A-interface BSSMAP messages sent to MSC
from BSC.
Usage
The counter is used to find out the frequency of CLEAR REQUEST

Measurement
Point
When BSC sends the CLEAR REQUEST message to MSC, the

2187
FIGURE 2264 MEASUREMENT POINT OF BSC SENDING CLEAR

REQUEST MESSAGE TO MSC
Unit
Times
C901360032 Number
of SAPI "N" REJECT
messages
Definition
Number of SAPI "N" REJECT messages
Description
This counter counts the number of SAPI "N" REJECT messages in

Usage
The counter is used to find out the frequency of SAPI "N" REJECT
Measurement
Point
When BSC sends the SAPI "N" REJECT message to MSC, the
FIGURE 2265 MEASUREMENT POINT OF BSC SENDING SAPI "N"
REJECT MESSAGE TO MSC
Unit
Times
CONFUSION messages
Definition
Description
2188
Number of UL CONFUSION messages

When BSC receives the incorrect BSSMAP message from MSC, it
sends the CONFUSION message to MSC. This counter counts the
number of CONFUSION messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of uplink CONFUSION

Measurement
Point
When BSC sends the CONFUSION message to MSC, the counter

FIGURE 2266 MEASUREMENT POINT OF BSC SENDING CONFUSION
MESSAGE TO MSC
Unit
Times
CONFUSION messages
Definition
Number of DL CONFUSION messages
Description
When MSC receives the incorrect BSSMAP message from BSC, it

sends the CONFUSION message to BSC. This counter counts the
number of CONFUSION messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of downlink CONFUSION messages transmitted at A-interface.
Measurement
Point
When BSC receives the CONFUSION message, the counter increments. The measurement point is A.
FIGURE 2267 MEASUREMENT POINT OF MSC SENDING CONFUSION
MESSAGE TO BSC
Unit
Times
2189
RESET messages
Definition
Number of UL RESET messages
Description
When BSC detects that it has serious global fault, it will send a
RESET message to MSC. This counter counts the number of RESET
Usage
The counter is used to find out the frequency of uplink RESET messages transmitted at A-interface.
Measurement
Point
When BSC sends the RESET message to MSC, the counter increments. The measurement point is A1.
FIGURE 2268 UPLINK RESET PROCESS
Unit
Times
RESET messages
Definition
2190
Number of DL RESET messages
Description
When MSC detects that it has serious global fault, it will send a
RESET message to BSC. This counter counts the number of RESET
Usage
The counter is used to find out the frequency of downlink RESET

Measurement
Point
When BSC receives the RESET message, the counter increments.

FIGURE 2269 DOWNLINK RESET PROCESS
Unit
Times
RESET ACKNOWLEDGE
messages
Definition
Number of UL RESET ACKNOWLEDGE messages
Description
When MSC detects that it has serious global fault, it will send a RESET message to BSC. After BSC receives the message, it releases
all calls and relevant information, and after a period of time, it
returns the RESET ACKNOWLEDGE message as response. This
counter counts the number of RESET ACKNOWLEDGE messages in
Usage
The counter is used to find out the frequency of uplink RESET ACKNOWLEDGE messages transmitted at A-interface.
Measurement
Point
When BSC sends the RESET ACKNOWLEDGE message to MSC, the

FIGURE 2270 DOWNLINK RESET PROCESS
Unit
Times
2191
RESET ACKNOWLEDGE
messages
Definition
Number of DL RESET ACKNOWLEDGE messages
Description
When BSC detects that it has serious global fault, it will send a
RESET message to MSC. After MSC receives the message, it releases all calls and relevant information, and after a period of time,
it returns the RESET ACKNOWLEDGE message as response. This
counter counts the number of RESET ACKNOWLEDGE messages in
Usage

ACKNOWLEDGE messages transmitted at A-interface.
Measurement
Point
When BSC receives the RESET ACKNOWLEDGE message, the

FIGURE 2271 UPLINK RESET PROCESS
Unit
Times
OVERLOAD messages
Definition
2192
Number of UL OVERLOAD messages
Description
When BSC detects that its processor is overloaded or CCCH (which

is PCH actually) is overloaded, it will send the OVERLOAD message
to the MSC to which it belongs. If the overload problem persists,
BSC will send the OVERLOAD message to MSC periodically. This
counter counts the number of OVERLOAD messages in A-interface
BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of uplink OVERLOAD

Measurement
Point
When BSC sends the OVERLOAD message to MSC, the counter

FIGURE 2272 MEASUREMENT POINT OF BSC SENDING OVERLOAD

MESSAGE TO MSC
Unit
Times
OVERLOAD messages
Definition
Number of DL OVERLOAD messages
Description
When MSC detects that its processor is overloaded, it will send the
OVERLOAD message to the BSC under it. If the overload problem
persists, MSC will send the OVERLOAD message to BSC periodically. This counter counts the number of OVERLOAD messages in
Usage
The counter is used to find out the frequency of downlink OVERLOAD messages transmitted at A-interface.
Measurement
Point
When BSC receives the OVERLOAD message, the counter increments. The measurement point is A.
FIGURE 2273 MEASUREMENT POINT OF MSC SENDING OVERLOAD
MESSAGE TO BSC
Unit
Times
MSC INVOKE TRACE
messages
Definition
Number of MSC INVOKE TRACE messages
2193
Description
When MSC needs to generate tracing records of specified calls for

BSC, it will send a MSC INVOKE TRACE message to the corresponding BSC to trigger tracing actions. This counter counts the
number of MSC INVOKE TRACE messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of MSC INVOKE

TRACE messages transmitted at A-interface.
Measurement
Point
When BSC receives the MSC INVOKE TRACE message, the counter
FIGURE 2274 MEASUREMENT POINT OF MSC SENDING MSC
INVOKE TRACE MESSAGE TO BSC
Unit
Times
sent BSS INVOKE TRACE
messages
Definition
Number of sent BSS INVOKE TRACE messages
Description
When BSC needs to generate tracing records of specified calls for

MSC, it will send a BSS INVOKE TRACE message to the corresponding MSC to trigger tracing actions. This counter counts the
number of BSS INVOKE TRACE messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of sending BSS INVOKE TRACE messages transmitted at A-interface.
Measurement
Point
When BSC sends the BSS INVOKE TRACE message to MSC, the
FIGURE 2275 MEASUREMENT POINT OF BSC SENDING BSS INVOKE
TRACE MESSAGE TO MSC
2194
Unit
Times
received BSS INVOKE
TRACE messages
Definition
Number of received BSS INVOKE TRACE messages
Description
This counter counts the number of BSS INVOKE TRACE messages

Usage
The counter is used to find out the frequency of receiving BSS

INVOKE TRACE messages transmitted at A-interface.
Measurement
Point
When BSC receives the BSS INVOKE TRACE message, the counter
FIGURE 2276 MEASUREMENT POINT OF MSC SENDING BSS
INVOKE TRACE MESSAGE TO BSC
Unit
Times
sent CONNECTIONLESS
Definition
Number of sent CONNECTIONLESS INFORMATION messages
Description
This counter counts the number of CONNECTIONLESS INFORMATION messages in A-interface BSSMAP messages sent by BSC.
Usage
The counter is used to find out the frequency of sending CONNECTIONLESS INFORMATION messages transmitted at A-interface.
Measurement
Point
When BSC sends the CONNECTIONLESS INFORMATION message

to MSC, the counter increments. The measurement point is A.
2195

CONNECTIONLESS INFORMATION MESSAGE TO MSC
Unit
Times
C901360045 Number of rece

ived CONNECTIONLESS
Definition
Number of received CONNECTIONLESS INFORMATION messages
Description
This counter counts the number of CONNECTIONLESS INFORMATION messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of receiving CONNECTIONLESS INFORMATION messages transmitted at A-interface.
Measurement
Point
When BSC receives the CONNECTIONLESS INFORMATION message, the counter increments. The measurement point is A.
FIGURE 2278 MEASUREMENT POINT OF MSC SENDING
CONNECTIONLESS INFORMATION MESSAGE TO BSC
Unit
Times
SUSPEND messages
Definition
Description
2196
Number of SUSPEND messages

When BSC detects that congestion occurs at radio interface, it
sends a SUSPEND message to MSC, asking MSC to stop sending
DTAP message that contains PDSS1 protocol layer 3. This counter

counts the number of SUSPEND messages in A-interface BSSMAP
messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of SUSPEND messages transmitted at A-interface.
Measurement
Point
When BSC sends the SUSPEND message to MSC, the counter increments. The measurement point is A.
FIGURE 2279 MEASUREMENT POINT OF BSC SENDING SUSPEND
MESSAGE TO MSC
Unit
Times
RESUME messages
Definition
Number of RESUME messages
Description
When BSC detects that congestion occurs at radio interface, it

sends a RESUME message to MSC, asking MSC to resume sending
DTAP message that contains PDSS1 protocol layer 3. This counter
counts the number of RESUME messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of RESUME messages

Measurement
Point
When BSC sends the RESUME message to MSC, the counter increments. The measurement point is A.
FIGURE 2280 MEASUREMENT POINT OF BSC SENDING RESUME
MESSAGE TO MSC
Unit
Times
2197
Common ID messages
Definition
Number of Common ID messages
Description
This counter counts the number of Common ID messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of Common ID messages transmitted at A-interface.
Measurement
Point
When BSC receives the Common ID message, the counter increments. The measurement point is A.
FIGURE 2281 MEASUREMENT POINT OF MSC SENDING COMMON
ID MESSAGE TO BSC
Unit
Times
C901360049 Number of LSA

Definition
Number of LSA INFORMATION messages
Description
MSC may send a LSA INFORMATION message to BSC for a certain

call. This message contains a Localised Service Area (LSA) list and
relevant properties of each LSA, such as the priority. This counter
counts the number of LSA INFORMATION messages in A-interface
Usage
The counter is used to find out the frequency of LSA INFORMATION

Measurement
Point
When BSC receives the LSA INFORMATION message, the counter

FIGURE 2282 MEASUREMENT POINT OF MSC SENDING LSA
INFORMATION MESSAGE TO BSC
2198
Unit
Times
PERFORM LOCATION
REQUEST messages
Definition
Number of PERFORM LOCATION REQUEST messages
Description
This counter counts the number of PERFORM LOCATION REQUEST

Usage
The counter is used to find out the frequency of PERFORM LOCATION REQUEST messages transmitted at A-interface.
Measurement
Point
When BSC receives the PERFORM LOCATION REQUEST message,

FIGURE 2283 PROCESS OF MSC SENDING PERFORM LOCATION
Unit
Times
PERFORM LOCATION
RESPONSE messages
Definition
Number of PERFORM LOCATION RESPONSE messages
Description
This counter counts the number of PERFORM LOCATION RESPONSE messages in A-interface BSSMAP messages sent to MSC
from BSC.
Usage
The counter is used to find out the frequency of PERFORM LOCATION RESPONSE messages transmitted at A-interface.
Measurement
Point
When BSC sends the PERFORM LOCATION RESPONSE message to

MSC, the counter increments. The measurement point is A2.
2199
FIGURE 2284 PROCESS OF MSC SENDING PERFORM LOCATION

Unit
Times
PERFORM LOCATION
ABORT messages
Definition
Number of PERFORM LOCATION ABORT messages
Description
This counter counts the number of PERFORM LOCATION ABORT

Usage
The counter is used to find out the frequency of PERFORM LOCATION ABORT messages transmitted at A-interface.
Measurement
Point
When BSC receives the PERFORM LOCATION ABORT message, the

FIGURE 2285 MEASUREMENT POINT OF MSC SENDING PERFORM
LOCATION ABORT MESSAGE TO BSC
Unit
Times
C901360053 Number of sent

BLOCK messages
Definition
2200
Number of sent BLOCK messages
Description
When BSC decides to block a terrestrial circuit of A-interface, it

sends a BLOCK message to MSC. This counter counts the number
of BLOCK messages in A-interface BSSMAP messages sent to MSC
from BSC.
Usage
The counter is used to find out the frequency of sending BLOCK

Measurement
Point
When BSC sends the BLOCK message to MSC, the counter increments. The measurement point is A1.
FIGURE 2286 PROCESS OF BSC SENDING BLOCK MESSAGE TO MSC
Unit
Times
received BLOCK ACK
messages
Definition
Number of received BLOCK ACK messages
Description
When BSC decides to block a terrestrial circuit of A-interface, it

sends a BLOCK message to MSC. MSC performs appropriate handling and returns a BLOCK ACK message as response. This counter
counts the number of BLOCK ACK messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of receiving BLOCK

ACK messages transmitted at A-interface.
Measurement
Point
When BSC receives the BLOCK ACK message, the counter increments. The measurement point is A2.
2201
FIGURE 2287 PROCESS OF BSC SENDING BLOCK MESSAGE TO MSC
Unit
Times

UNBLOCK messages
Definition
Number of sent UNBLOCK messages
Description
When BSC decides to unblock a terrestrial circuit of A-interface,

it sends an UNBLOCK message to MSC. This counter counts the
number of UNBLOCK messages in A-interface BSSMAP messages
sent to MSC from BSC.
Usage
The counter is used to find out the frequency of sending UNBLOCK

Measurement
Point
When BSC sends the UNBLOCK message to MSC, the counter increments. The measurement point is A1.
FIGURE 2288 PROCESS OF BSC SENDING UNBLOCK MESSAGE TO
MSC
Unit
2202
Times
received UNBLOCK ACK
messages
Definition
Number of received UNBLOCK ACK messages
Description
When BSC decides to unblock a terrestrial circuit of A-interface, it

sends an UNBLOCK message to MSC. MSC performs appropriate
handling and returns an UNBLOCK ACK message as response. This
counter counts the number of UNBLOCK ACK messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of receiving UNBLOCK

Measurement
Point
When BSC receives the UNBLOCK ACK message, the counter increments. The measurement point is A2.
FIGURE 2289 PROCESS OF BSC SENDING UNBLOCK MESSAGE TO
MSC
Unit
Times
received BLOCK messages
Definition
Number of received BLOCK messages
Description
When MSC decides to block a terrestrial circuit of A-interface, it

sends a BLOCK message to BSC. This counter counts the number
of BLOCK messages in A-interface BSSMAP messages received by
BSC.
Usage
The counter is used to find out the frequency of receiving BLOCK

Measurement
Point
When BSC receives the BLOCK message, the counter increments.

2203
FIGURE 2290 PROCESS OF MSC SENDING BLOCK MESSAGE TO BSC
Unit
Times

BLOCK ACK messages
Definition
Number of sent BLOCK ACK messages
Description
When MSC decides to block a terrestrial circuit of A-interface, it

sends a BLOCK message to BSC. BSC performs appropriate handling and returns a BLOCK ACK message as response. This counter
counts the number of BLOCK ACK messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of sending BLOCK

Measurement
Point
When BSC sends the BLOCK ACK message to MSC, the counter
FIGURE 2291 PROCESS OF MSC SENDING BLOCK MESSAGE TO BSC
Unit
2204
Times
C901360059 Number
of received UNBLOCK
messages
Definition
Number of received UNBLOCK messages
Description
When MSC decides to unblock a terrestrial circuit of A-interface, it

sends a UNBLOCK message to BSC. This counter counts the number of UNBLOCK messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of receiving UNBLOCK

Measurement
Point
When BSC receives the UNBLOCK message, the counter increments. The measurement point is A1.
FIGURE 2292 PROCESS OF MSC SENDING UNBLOCK MESSAGE TO
BSC
Unit
Times

UNBLOCK ACK messages
Definition
Number of sent UNBLOCK ACK messages
Description
When MSC decides to unblock a terrestrial circuit of A-interface,

it sends a UNBLOCK message to BSC. BSC performs appropriate
handling and returns an UNBLOCK ACK message as response. This
counter counts the number of UNBLOCK ACK messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of sending UNBLOCK

Measurement
Point
When BSC sends the UNBLOCK ACK message to MSC, the counter
2205
FIGURE 2293 PROCESS OF MSC SENDING UNBLOCK MESSAGE TO

BSC
Unit
Times
RESET CIRCUIT messages
Definition
Number of UL RESET CIRCUIT messages
Description
When BSC detects that an abnormal SCCP connection release

causes a circuit to become idle, it sends a RESET CIRCUIT message to MSC. This counter counts the number of RESET CIRCUIT
messages in A-interface BSSMAP messages sent to MSC from
BSC.
Usage
The counter is used to find out the frequency of uplink RESET CIRCUIT messages transmitted at A-interface.
Measurement
Point
When BSC sends the RESET CIRCUIT message to MSC, the counter
FIGURE 2294 PROCESS OF BSC SENDING RESET CIRCUIT MESSAGE
TO MSC
Unit
2206
Times
RESET CIRCUIT messages
Definition
Number of DL RESET CIRCUIT messages
Description
When MSC detects that an abnormal SCCP connection release

causes a circuit to become idle, it sends a RESET CIRCUIT message to BSC. This counter counts the number of RESET CIRCUIT
Usage

CIRCUIT messages transmitted at A-interface.
Measurement
Point
When BSC receives the RESET CIRCUIT message, the counter increments. The measurement point is A1.
FIGURE 2295 PROCESS OF MSC SENDING RESET CIRCUIT
MESSAGE TO BSC
Unit
Times
UL RESET CIRCUIT ACK
messages
Definition
Number of UL RESET CIRCUIT ACK messages
Description
When MSC detects that an abnormal SCCP connection release

causes a circuit to become idle, it sends a RESET CIRCUIT message to BSC. After BSC receives the message, it clears relevant
calls and makes corresponding circuits to become idle, and sends
a RESET CIRCUIT ACK message to MSC. This counter counts the
number of RESET CIRCUIT ACK messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of uplink RESET CIRCUIT ACK messages transmitted at A-interface.
Measurement
Point
When BSC sends the RESET CIRCUIT ACK message to MSC, the
2207
FIGURE 2296 PROCESS OF MSC SENDING RESET CIRCUIT

MESSAGE TO BSC
Unit
Times
DL RESET CIRCUIT ACK
messages
Definition
Number of DL RESET CIRCUIT ACK messages
Description
When BSC detects that an abnormal SCCP connection release

causes a circuit to become idle, it sends a RESET CIRCUIT message to MSC. After MSC receives the message, it clears relevant
calls and makes corresponding circuits to become idle, and sends
a RESET CIRCUIT ACK message to BSC. This counter counts the
number of RESET CIRCUIT ACK messages in A-interface BSSMAP
Usage

CIRCUIT ACK messages transmitted at A-interface.
Measurement
Point
When BSC receives the RESET CIRCUIT ACK message, the counter
FIGURE 2297 PROCESS OF BSC SENDING RESET CIRCUIT MESSAGE
TO MSC
Unit
2208
Times
CIRCUIT GROUP BLOCK
messages
Definition
Number of UL CIRCUIT GROUP BLOCK messages
Description
When BSC decides to block some terrestrial circuits of A-interface

and these terrestrial circuits can be described in one message,
BSC will send a CIRCUIT GROUP BLOCK message to MSC. This
counter counts the number of CIRCUIT GROUP BLOCK messages
Usage
The counter is used to find out the frequency of uplink CIRCUIT

GROUP BLOCK messages transmitted at A-interface.
Measurement
Point
When BSC sends the CIRCUIT GROUP BLOCK message to MSC,

FIGURE 2298 PROCESS OF BSC SENDING CIRCUIT GROUP BLOCK
MESSAGE TO MSC
Unit
Times
CIRCUIT GROUP BLOCK
messages
Definition
Number of DL CIRCUIT GROUP BLOCK messages
Description
When MSC decides to block some terrestrial circuits of A-interface

MSC will send a CIRCUIT GROUP BLOCK message to BSC. This
counter counts the number of CIRCUIT GROUP BLOCK messages
Usage
The counter is used to find out the frequency of downlink CIRCUIT

GROUP BLOCK messages transmitted at A-interface.
Measurement
Point
When BSC receives the CIRCUIT GROUP BLOCK message, the

2209
FIGURE 2299 PROCESS OF MSC SENDING CIRCUIT GROUP BLOCK

MESSAGE TO BSC
Unit
Times
C901360067 Number
of UL CIRCUIT
GROUP BLOCKING
ACKNOWLEDGE messages
Definition
Number of UL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages
Description
When MSC decides to block some terrestrial circuits of A-interface

MSC will send a CIRCUIT GROUP BLOCK message to BSC. After
BSC performs appropriate handlings, it returns a CIRCUIT GROUP
BLOCKING ACKNOWLEDGE message as response. This counter
counts the number of CIRCUIT GROUP BLOCKING ACKNOWLEDGE
Usage

GROUP BLOCKING ACKNOWLEDGE messages transmitted at A-interface.
Measurement
Point
When BSC sends the CIRCUIT GROUP BLOCKING ACKNOWLEDGE

message to MSC, the counter increments. The measurement point
is A2.
FIGURE 2300 PROCESS OF MSC SENDING CIRCUIT GROUP BLOCK
MESSAGE TO BSC
Unit
2210
Times
C901360068 Number
of DL CIRCUIT
GROUP BLOCKING
Definition
Number of DL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages
Description
When BSC decides to block some terrestrial circuits of A-interface

BSC will send a CIRCUIT GROUP BLOCK message to MSC. After
MSC performs appropriate handlings, it returns a CIRCUIT GROUP
BLOCKING ACKNOWLEDGE message as response. This counter
counts the number of CIRCUIT GROUP BLOCKING ACKNOWLEDGE
Usage

GROUP BLOCKING ACKNOWLEDGE messages transmitted at A-interface.
Measurement
Point
When BSC receives the CIRCUIT GROUP BLOCKING ACKNOWLEDGE message, the counter increments. The measurement point
is A2.
FIGURE 2301 PROCESS OF BSC SENDING CIRCUIT GROUP BLOCK
MESSAGE TO MSC
Unit
Times
UL CIRCUIT GROUP
UNBLOCK messages
Definition
Description
Number of UL CIRCUIT GROUP UNBLOCK messages

When BSC decides to unblock some terrestrial circuit of A-interface, it sends a CIRCUIT GROUP UNBLOCK message to MSC. This
2211
counter counts the number of CIRCUIT GROUP UNBLOCK messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage

GROUP UNBLOCK messages transmitted at A-interface.
Measurement
Point
When BSC sends the CIRCUIT GROUP UNBLOCK message to MSC,

FIGURE 2302 PROCESS OF BSC SENDING CIRCUIT GROUP
UNBLOCK MESSAGE TO MSC
Unit
Times
DL CIRCUIT GROUP
UNBLOCK messages
Definition
Number of DL CIRCUIT GROUP UNBLOCK messages
Description
When MSC decides to unblock some terrestrial circuit of A-interface, it sends a CIRCUIT GROUP UNBLOCK message to BSC. This
counter counts the number of CIRCUIT GROUP UNBLOCK messages in A-interface BSSMAP messages received by BSC.
Usage

GROUP UNBLOCK messages transmitted at A-interface.
Measurement
Point
When BSC receives the CIRCUIT GROUP UNBLOCK message, the

FIGURE 2303 PROCESS OF MSC SENDING CIRCUIT GROUP
UNBLOCK MESSAGE TO BSC
2212
Unit
Times
C901360071 Number
of UL CIRCUIT
GROUP UNBLOCKING
Definition
Number of UL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE

messages
Description
When MSC decides to unblock some terrestrial circuit of A-interface, it sends a CIRCUIT GROUP UNBLOCK message to BSC. After
BSC performs appropriate handlings, it returns a CIRCUIT GROUP
UNBLOCKING ACKNOWLEDGE message as response. This counter
counts the number of CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages in A-interface BSSMAP messages sent to MSC
from BSC.
Usage

GROUP UNBLOCKING ACKNOWLEDGE messages transmitted at
A-interface.
Measurement
Point
When BSC sends the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message to MSC, the counter increments. The measurement point is A2.
FIGURE 2304 PROCESS OF MSC SENDING CIRCUIT GROUP
UNBLOCK MESSAGE TO BSC
Unit
Times
2213
C901360072 Number
of DL CIRCUIT
GROUP UNBLOCKING
Definition
Number of DL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE

messages
Description
When BSC decides to unblock some terrestrial circuit of A-interface, it sends a CIRCUIT GROUP UNBLOCK message to MSC.
After MSC performs appropriate handlings, it returns a CIRCUIT
GROUP UNBLOCKING ACKNOWLEDGE message as response. This
counter counts the number of CIRCUIT GROUP UNBLOCKING
ACKNOWLEDGE messages in A-interface BSSMAP messages
received by BSC.
Usage
The counter is used to find out the frequency of downlink CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages transmitted
at A-interface.
Measurement
Point
When BSC receives the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message, the counter increments. The measurement point
is A2.
FIGURE 2305 PROCESS OF BSC SENDING CIRCUIT GROUP
UNBLOCK MESSAGE TO MSC
Unit
Times
UNEQUIPPED CIRCUIT
messages
Definition
Description
2214
Number of UL UNEQUIPPED CIRCUIT messages

During circuit maintenance process, if BSC can not find the circuit
in the message, it returns the UNEQUIPPED CIRCUIT message to
MSC. This counter counts the number of UNEQUIPPED CIRCUIT

Usage
The counter is used to find out the frequency of uplink UNEQUIPPED CIRCUIT messages transmitted at A-interface.
Measurement
Point
When BSC sends the UNEQUIPPED CIRCUIT message to MSC, the

UNEQUIPPED CIRCUIT MESSAGE TO MSC
Unit
Times
UNEQUIPPED CIRCUIT
messages
Definition
Number of DL UNEQUIPPED CIRCUIT messages
Description
During circuit maintenance process, if MSC can not find the circuit
in the message, it returns the UNEQUIPPED CIRCUIT message to
BSC. This counter counts the number of UNEQUIPPED CIRCUIT
Usage
The counter is used to find out the frequency of downlink UNEQUIPPED CIRCUIT messages transmitted at A-interface.
Measurement
Point
When BSC receives the UNEQUIPPED CIRCUIT message, the

UNEQUIPPED CIRCUIT MESSAGE TO BSC
Unit
Times
2215
C901360075 Number
of CHANGE CIRCUIT
messages
Definition
Number of CHANGE CIRCUIT messages
Description
When A-interface terrestrial circuits are allocated only by BSC, if

MSC wants to perform circuit handover for a call connection, MSC
will send a CHANGE CIRCUIT message to BSC and release the circuit at the same time. This counter counts the number of CHANGE
CIRCUIT messages in A-interface BSSMAP messages received by
BSC.
Usage
The counter is used to find out the frequency of CHANGE CIRCUIT

Measurement
Point
When BSC receives the CHANGE CIRCUIT message, the counter

FIGURE 2308 PROCESS OF MSC SENDING CHANGE CIRCUIT
MESSAGE TO BSC
Unit
Times
CHANGE CIRCUIT ACK
messages
Definition
Description
Number of CHANGE CIRCUIT ACK messages

When A-interface terrestrial circuits are allocated only by BSC, if
MSC wants to perform circuit handover for a call connection, MSC
will send a CHANGE CIRCUIT message to BSC and release the circuit at the same time. After BSC receives the message, it selects
a new circuit being occupied that satisfies requirement, sends the
circuit information in the CHANGE CIRCUIT ACK message to MSC,
and releases the circuit.
This counter counts the number of CHANGE CIRCUIT ACK messages in A-interface BSSMAP messages received by BSC.
2216
Usage
The counter is used to find out the frequency of CHANGE CIRCUIT

Measurement
Point
When BSC sends the CHANGE CIRCUIT ACK message to MSC, the
FIGURE 2309 PROCESS OF MSC SENDING CHANGE CIRCUIT
MESSAGE TO BSC
Unit
Times
HANDOVER PERFORMED
ACK messages
Definition
Description
Number of HANDOVER PERFORMED ACK messages

This counter counts the number of HANDOVER PERFORMED ACK
messages received by BSC from MSC.
This counter counts the number of CHANGE CIRCUIT ACK messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out cases of BSC receiving the HANDOVER PERFORMED ACK message from MSC.
Measurement
Point
When BSC receives the HANDOVER PERFORMED ACK message

from MSC, the counter increments.
Unit
Times
C901360078 The count

of Sending INTERNAL
HANDOVER REQUIRED
Statistics object
CELL
2217
Description
This counter counts the number of internal handover requests sent

to MSC from BSC. The measurement point is A1, as shown in Figure
2310.
Times
FIGURE 2310 MEASUREMENT POINT OF THE COUNT OF SENDING INTERNAL
HANDOVER REQUIRED
Reference
2218
3GPP TS 48008

of Receiving INTERNAL
HANDOVER COMMAND
Statistics object
Description
CELL
This counter counts the number of internal handover commands
sent to BSC from MSC. The measurement point is A2, as shown in
Figure 2311.
Times
INTERNAL HANDOVER COMMAND
Reference
THE
COUNT
OF
RECEIVING
3GPP TS 48008
2219

of Receiving INTERNAL
HANDOVER REJECT
Statistics object
Description
CELL
This counter counts the number of internal handover rejections
sent to BSC from MSC. The measurement point is A1, as shown in
Figure 2312.
Times
INTERNAL HANDOVER REJECT
Reference
OF THE
COUNT
OF
RECEIVING
3GPP TS 48008
INTERNAL HANDOVER
ENQUIRY messages
Statistics object
Description
2220
CELL
This counter counts the number of INTERNAL HANDOVER ENQUIRY messages sent by MSC. On TCH/F or TCH/H, when BSC
receives the INTERNAL HANDOVER ENQUIRY message from MSC,
in Figure 2313.
FIGURE 2313 OMCR INITIATING IP RESOURCE RESETTING FLOW
Unit
Times
UL RESET IP RESOURCE
messages
Statistics object
Description
CELL
This counter counts the number of IP resource resettings initiated
by BSC towards MSC. OMCR initiates the IP resource resetting request, and the IPRSCRST module initiates the IP resource resetting request towards MSC through the ADispatch module. When
the ADispatch module receives the IP resource resetting request
from the IPRSCRST module, the counter increments. The measurement point is A, as shown in Figure 2314.
Unit
Times
2221
UL RESET IP RESOURCE
ACKOWNLEDGE messages
Statistics object
Description
CELL
This counter counts the number of IP resource resetting response
messages sent to MSC from BSC. MSC initiates IP resource resetting towards BSC, and the IPRSCRST module at OMP sends IP
resource resetting response to MSC through the ADispatch module. When the ADispatch module receives the IP resource resetting
response, the counter increments. The measurement point is A,
FIGURE 2315 MSC INITIATING IP RESOURCE RESETTING FLOW
Unit
Times
DL RESET IP RESOURCE
messages
Statistics object
Description
2222
CELL
This counter counts the number of IP resource resetting requests
initiated by MSC towards BSC. MSC initiates the IP resource resetting requests towards the IPRSCRST module through the ADispatch module. When the ADispatch module receives the IP resource resetting request from MSC, the counter increments. The
FIGURE 2316 MSC INITIATING IP RESOURCE RESETTING FLOW
Unit
Reference
Times
3GPP TS 48008
DL RESET IP RESOURCE
Statistics object
Description
CELL
This counter counts the number of IP resource resetting response
messages sent to BSC from MSC. OMCR initiates the IP resource
resetting request, the IPRSCRST module initiates the IP resource
resetting request towards MSC and waits for MSC to send back
the IP resource resetting response. When the ADispatch module
receives the IP resource resetting response from MSC, the counter
increments. The measurement point is A, as shown in .
Unit
Times
2223
2224
Chapter
43
A-Interface Message
Measurement
Table of Contents
Overview...................................................................... 2225
C901370001 Number of UL DTAP messages ...................... 2225
C901370002 Number of DL DTAP messages ...................... 2226
C901370003 Number of UL BSSMAP messages .................. 2226
C901370004 Number of DL BSSMAP messages.................. 2227
C901370005 Number of DL BSSMAP messages received with
error............................................................................ 2228
NULL_NRI..................................................................... 2228
C901370007 Number of chosen for MSC Load share by the
NRI not in the MSC pool ................................................. 2229
Overview
The A-interface message measurement performs statistics for uplink/downlink DTAP message, BSSMAP message, and received incorrect BSSMAP message. Statistic unit in this measurement is
CMP.
DTAP messages
Definition
Description
Number of UL DTAP messages

This counter counts the number of A-interface DTAP messages sent
to MSC from BSC.
This counter counts the number of HANDOVER CANDIDATE RESPONSE messages in A-interface BSSMAP messages sent to MSC
from BSC.
Usage
The counter analyzes the frequency of uplink DTAP messages

2225
Measurement
Point
The counter counts when BSC sends the DTAP message to MSC.
A-INTERFACE DTAP MESSAGE TO MSC
Unit
Times
DTAP messages
Definition
Number of DL DTAP messages
Description
This counter counts the number of DTAP messages received by

BSC from MSC. MSC can carry the DTAP message in the Connection
Indication message, Connection Confirm message, Disconnection
Indication message, and Data Indication message.
Usage
The counter analyzes the frequency of downlink DTAP messages

Measurement
Point
The counter counts when BSC receives the Connection Indication

message, Connection Confirm message, Disconnection Indication
message, or Data Indication message, these messages containing
DTAP message. The measurement point is A.
A-INTERFACE DTAP MESSAGE TO BSC
Unit
Times
BSSMAP messages
Definition
2226
Number of UL BSSMAP messages
Chapter 43 A-Interface Message Measurement
Description
This counter counts the number of messages containing BSSMAP

message sent to MSC from BSC. BSC can carry the uplink BSSMAP
message in the Connection Request message, Data Request message, or UnitData Request message.
Usage
The counter analyzes the frequency of uplink BSSMAP messages

Measurement
Point
The counter counts when BSC sends the Connection Request message, Data Request message, or UnitData Request message to
MSC, these messages containing BSSMAP message. The measurement point is A.
A-INTERFACE BSSMAP MESSAGE TO MSC
Unit
Times
BSSMAP messages
Definition
Number of DL BSSMAP messages
Description
This counter counts the number of BSSMAP messages received by

BSC from MSC. MSC can carry the BSSMAP message in the Connection Indication message, Connection Confirm message, Data
Indication message, and UnitData Indication message.
Usage
The counter analyzes the frequency of downlink BSSMAP messages

Measurement
Point
The counter counts when BSC receives the Connection Indication message, Connection Confirm message, Data Indication message, or UnitData Indication message, these messages containing
BSSMAP message. The measurement point is A.
FIGURE 2321 MEASUREMENT POINT OF BSC RECEIVING
A-INTERFACE BSSMAP MESSAGE FROM MSC
Unit
Times
2227
DL BSSMAP messages
received with error
Definition
Number of DL BSSMAP messages received with error
Description
This counter counts the number of incorrect BSSMAP messages

received by BSC from MSC. Such incorrect BSSMAP messages include L3 message with zero length, BSSMAP message of which the
length does not match the length of its contained L3 message, decoding error, or messge type error.
Usage
The counter analyzes the frequency of received incorrect BSSMAP

Measurement
Point
The counter counts when BSC receives incorrect BSSMAP message.
Unit
Times
chosen for MSC Load share
by NULL_NRI
Definition
Description
This counter counts the number of a MSC being chosen for load
sharing by NULL_NRI within the measurement period.
Usage
This counter is used to find out the frequency that the original
serving MSC in the pool allocates NULL_NRI to MS to make a MSC
actively shares the load.
Measurement
Point
The counter counts when iBSC chooses an appropriate MSC route

for MS access.
Unit
2228
Number of chosen for MSC Load share by NULL_NRI
Times
Chapter 43 A-Interface Message Measurement
chosen for MSC Load share
by the NRI not in the MSC
pool
Definition
Number of chosen for MSC Load share by the NRI not in the MSC
pool
Description
This counter counts the number of a MSC being chosen for load
sharing by non-NULL_NRI within the measurement period.
Usage
This counter is used to find out the frequency of a MSC's sharing

load due to MS accessing the network through NRI which is not of
the MSC.
Measurement
Point
The counter counts when iBSC chooses an appropriate MSC route

for MS access.
Unit
Times
2229
2230
Chapter
44
Terrestrial Resource
Availability Measurem
ent
Table of Contents
Overview...................................................................... 2231
C901380001 Mean number of available trunk circuits ......... 2232
C901380002 Mean number of unavailable trunk circuits ............................................................................ 2232
C901380003 Maximum number of busy trunk circuits......... 2232
C901380004 Busy time of trunk circuit ............................. 2233
C901380005 Congestion time of trunk circuit .................... 2233
C901380006 Mean number of available UDP port ............... 2234
C901380007 Mean number of unavailable UDP port ........... 2234
C901380008 Number of allocation AIPB board success......... 2235
C901380009 Number of allocation AIPB board failure ......... 2235
C901380010 Maximum number of seizure UDP port ........... 2236
C901380011 Number of successful one time request UDP port
to AIPB ........................................................................ 2236
C901380012 Number of successful two time request UDP port
to AIPB ........................................................................ 2237
C901380013 Number of successful three time request UDP
port to AIPB.................................................................. 2238
C901380014 Number of failure request UDP port to
AIPB ............................................................................ 2239
C901380015 Seizure duration of UDP port ........................ 2240
C901380016 The times of User Plane transport without RTP
multiplexing.................................................................. 2240
C901380017 The times of RTP multiplexing applied without
RTP header compression................................................. 2241
C901380018 The times of RTP multiplexing applied with RTP
header compression....................................................... 2242
C901380019 Mean number of busy trunk circuits............... 2242
C901380020 Mean number of seizure UDP port ................. 2244
Overview
The terrestrial resource availability measurement performs statistics for the availability of terrestrial resource at A-interface, including the average number of available BSC trunk circuits, the
average number of unavailable BSC trunk circuits, the maximum
number of busy trunk circuits, the total busy time of BSC trunk cir-
2231
cuits, and the total congestion time of BSC trunk circuits. All these
information reflects the A-interface trunk circuit resource usage.
Statistic unit in this measurement is BSC.

of available trunk circuits
Definition
Description
Usage
Measurement
Point
Unit
Mean number of available trunk circuits

This counter counts the average number of trunk circuits that can
be used normally.
The counter reflects the current trunk circuit usage.
The counter counts when system periodically queries database for
circuit information.
Times

of unavailable trunk circuits
Definition
Description
Usage
Measurement
Point
Unit
Mean number of unavailable trunk circuits

This counter counts the average number of trunk circuits that can
not be used normally, including the number of circuits being occupied and the number of circuits being blocked.
The counter reflects the current trunk circuit usage.
Times
C901380003 Maximum
number of busy trunk circuits
Definition
2232
Maximum number of busy trunk circuits
Description
This counter counts the maximum number of trunk circuits being

occupied during the measurement period.
Usage
The counter reflects the transient occupation condition of trunk

circuits.
Measurement
Point
There are three measurement points for the maximum number of

busy trunk circuits.
Chapter 44 Terrestrial Resource Availability Measurement
Unit
After the trunk circuit is occupied successfully, if the maximum

number of busy trunk circuits exceeds the recorded value, then
the counter's value is updated.
Before the trunk circuit is released, if the maximum number

of busy trunk circuits exceeds the recorded value, then the
counter's value is updated.
During periodical measurement, if the maximum number

of busy trunk circuits exceeds the recorded value, then the
counter's value is updated.
Times
C901380004 Busy time of

trunk circuit
Definition
Description
Usage
Measurement
Point
Unit
Busy time of trunk circuit

This counter counts the total time of all trunk circuits being occupied during the measurement period.
The counter reflects the busy condition of trunk circuits.
There are three measurement points for the busy time of trunk
circuits.
Before the trunk circuit is occupied successfully, the counter

calculates the occupation time and accumulates.
Before the trunk circuit is released, the counter calculates the

occupation time and accumulates.
During periodical measurement, the counter calculates the occupation time and accumulates.
Second
C901380005 Congestion
time of trunk circuit
Definition
Description
Usage
Measurement
Point
Congestion time of trunk circuit

This counter counts the total time of failing to request trunk circuit
The counter reflects the congestion condition of trunk circuits.
There are three measurement points for the congestion time of
trunk circuits.
Before the trunk circuit is attempted to be occupied, if the congestion identifier is set, then the counter calculates the congestion time and accumulates.
2233
Unit
Before the trunk circuit is released, if the congestion identifier

is set, then the counter calculates the congestion time and
accumulates.
During periodical measurement, if the congestion identifier is

set, then the counter calculates the congestion time and accumulates.
Second

of available UDP port
Definition
Description
Mean number of available UDP port

This counter counts the average number of available UDP ports.
Usage
The counter is used to find out the average number of available

UDP ports.
Measurement
Point

Unit
Related Features
Times

of unavailable UDP port
Definition
Description
This counter counts the average number of unavailable UDP ports.
Usage
The counter is used to find out the average number of unavailable

UDP ports.
Measurement
Point

Unit
Related Features
2234
Mean number of unavailable UDP port
Times
allocation AIPB board
success
Definition
Number of allocation AIPB board success
Description
This counter counts the number of allocating AIPB board successfully. The RANCS module receives the EV_RANUMC_RADIO_APPLY message and requests AIPB resource from database. If the
request succeeds, the counter accumulates.
Usage
The counter is used to find out the frequency of allocating AIPB

board successfully.
Measurement
Point
When the request of AIPB board from database is returned successfully, the counter accumulates. The measurement point is A.
FIGURE 2322 REQUESTING RESOURCE FROM DATABASE
SUCCESSFULLY
Unit
Related Features
Times
allocation AIPB board failure
Definition
Number of allocation AIPB board failure
Description
This counter counts the number of AIPB board allocation failure.

The RANCS module receives the EV_RANUMC_RADIO_APPLY
messge and requests AIPB resource from database. If the request
fails, the counter accumulates.
Usage
The counter is used to find out the frequency of AIPB board allocation failure.
Measurement
Point
When the request of AIPB board from database fails, the counter
accumulates. The measurement point is A.
2235
FIGURE 2323 REQUESTING RESOURCE FROM DATABASE FAILURE
Unit
Related Features
Times
C901380010 Maximum
number of seizure UDP port
Definition
Maximum number of seizure UDP port
Description
This counter counts the maximum number of UDP ports being occupied.
Usage
The counter is used to find out the maximum number of UDP ports
being occupied.
Measurement
Point
Unit
Related Features
After the UDP port is occupied successfully, if the maximum

number of busy UDP ports exceeds the recorded value, then
the counter's value is updated.
Before the UDP port is released, if the maximum number of

busy UDP ports exceeds the recorded value, then the counter's
value is updated.
During periodical measurement, if the maximum number of

busy UDP ports exceeds the recorded value, then the counter's
value is updated.
Times
successful one time request
UDP port to AIPB
Definition
2236
Number of successful one time request UDP port to AIPB
Description
This counter counts the number of successfully requesting AIPB

board for UDP port through only one request.
The RANCS module receives the EV_RANUMC_RADIO_APPLY message, and after requesting database for AIPB resource successfully, it sends the connection request to the connection module.
When BSC receives the correct EV_RANCONN_IPA_CONN_ACK
message from the connection module, if the number of times of
requesting UDP port is only one, then the counter accumulates.
Usage
The counter is used to find out the frequency of successfully requesting AIPB board for UDP port through only one request.
Measurement
Point
When the connection succeeds and the requesting AIPB board for
UDP port succeeds through only one request, the counter accumulates. The measurement point is A
SUCCESSFULLY
Unit
Related Features
Times
successful two time request
UDP port to AIPB
Definition
Description
Number of successful two time request UDP port to AIPB

board for UDP port through two requests.
requesting UDP port is two, then the counter accumulates.
Usage
The counter is used to find out the frequency of successfully requesting AIPB board for UDP port through two requests.
2237
Measurement
Point
UDP port succeeds after two requests, the counter accumulates.
SUCCESSFULLY
Unit
Related Features
Times
C901380013 Number
of successful three time
request UDP port to AIPB
Definition
Description
Number of successful three time request UDP port to AIPB

board for UDP port through three requests.
requesting UDP port is three, then the counter accumulates.
2238
Usage
The counter is used to find out the frequency of successfully requesting AIPB board for UDP port through three requests.
Measurement
Point
UDP port succeeds after three requests, the counter accumulates.

SUCCESSFULLY
Unit
Related Features
Times
failure request UDP port to
AIPB
Definition
Description
Number of failure request UDP port to AIPB

This counter counts the number of failing to request AIPB board
for UDP port.
When BSC receives the correct EV_RANCONN_IPA_CONN_NACK
message from the connection module, if the failure is due to requesting UDP port failure, the counter accumulates.
Usage
The counter is used to find out the frequency of failing to request

AIPB board for UDP port.
Measurement
Point
When the connection failure message is returned, the counter accumulates. The measurement point is A.
FIGURE 2327 REQUESTING RESOURCE FROM DATABASE FAILURE
Unit
Times
2239
Related Features
C901380015 Seizure
duration of UDP port
Definition
Description
Usage
Measurement
Point
Unit
Related Features
Seizure duration of UDP port

This counter counts the total time of UDPPort being occupied.
The counter is used to find out the total time of UDPPort being
occupied.
Before UDPPort is occupied successfully, the counter calculates

the occupation time and accumulates.
Before UDPPort is released, the counter calculates the occupation time and accumulates.
During periodical measurement, the counter calculates the occupation time and accumulates.
Second
C901380016 The times of

User Plane transport without
RTP multiplexing
Description
When IP A mode is adopted, BSC and MGW negotiate the RTP

transmission mode of user plane at A-interface. If BSC or MGW
does not enable the RTP multiplexing mode for transmission, or if
the RTP multiplexing modes used at BSC and MGW are not consistent, then the message at UDP port of A-interface will not be
transmitted in RTP multiplexing mode.
Usage
This counter counts the number of user plane not applying RTP
multiplexing mode in AoIP call at BSC side.
Measurement
Point
2240
After the call is established, BSC and MGW negotiate the RTP transmission mode. When control plane receives the RTP_MUX_RPT
message from user plane, if the RTP multiplexing mode is not applied, the counter counts. The measurement point is A, as shown
in Figure 2328.
FIGURE 2328
MULTIPLEXING
Unit
THE
TIMES OF
USER PLANE
TRANSPORT WITHOUT
RTP
Times
C901380017 The times

of RTP multiplexing
applied without RTP header
compression
Description

transmission mode of user plane at A-interface. If both BSC and
MGW support RTP multiplexing and the negotiation succeeds, then
the message at UDP port of A-interface will be transmitted in RTP
multiplexing mode.
Usage
This counter counts the number of user plane applying RTP multiplexing mode in AoIP call at BSC side.
Measurement
Point
message from user plane, if the RTP multiplexing mode is applied,
the counter counts. The measurement point is A, as shown in
Figure 2329.
FIGURE 2329 THE TIMES OF
HEADER COMPRESSION
Unit
RTP
MULTIPLEXING APPLIED WITHOUT
RTP
Times
2241
C901380018 The times

of RTP multiplexing
applied with RTP header
compression
Description

transmission mode of user plane at A-interface. If both BSC and
MGW support compressed RTP multiplexing and the negotiation
succeeds, then the message at UDP port of A-interface will be
transmitted in compressed RTP multiplexing mode.
Usage
This counter counts the number of user plane applying compressed

RTP multiplexing mode in AoIP call at BSC side.
Measurement
Point
message from user plane, if the compressed RTP multiplexing
mode is applied, the counter counts. The measurement point is
FIGURE 2330 THE TIMES OF
HEADER COMPRESSION
Unit
RTP
MULTIPLEXING APPLIED WITH
RTP
Times

of busy trunk circuits
Description
Usage
This counter counts the average number of busy trunk circuits.

If the flow becomes abnormal or is to be released normally, the
common processing function of release flow is called. Also, in active-standby changeover, the ranumc process calls the function
to release the standby umc database. In the above two cases,
if obtaining the instance occupying circuit fails, then the counter
decrements.
This counter is used to find out the occupation of trunk circuits.
2242
Measurement
Point
1. When BSC receives the release command and releases the

terrestrial circuit, it attempts to obtain the instance currently
occupying circuit. If the instance obtaining fails, the counter
counts. The measurement point is shown in Figure 2331.
FIGURE 2331 COMMON RELEASE FLOW
2. When the standby umc releases database and A-interface terrestrial circuit, the counter counts. The measurement point is
FIGURE 2332 STANDBY
Unit
UMC
DATABASE BEING RELEASED
Times
2243

of seizure UDP port
Description
Usage
This counter counts the average number of occupied UDP ports.

The counter is used to find out the average number of occupied
UDP ports.
Measurement
Point
IPA performance statistics is implemented when Oms reports data.

If the time when UDP port becomes busy is the current system
time, then the average number of occupied UDP ports is counted.
FIGURE 2333 OMS REPORTING DATA
Unit
2244
TO
Times
DATABASE
Chapter
45
Ater Message
Measurement
Table of Contents
Overview...................................................................... 2247
C901390001 Number of UL BLOCK Ater single CIRCUIT messages........................................................................... 2247
C901390002 Number of DL BLOCKING Ater single CIRCUIT
C901390003 Number of UL UNBLOCK Ater single CIRCUIT
messages ..................................................................... 2248
C901390004 Number of DL UNBLOCKING Ater single CIRCUIT
C901390005 Number of DL BLOCK Ater single CIRCUIT messages........................................................................... 2248
C901390006 Number of UL BLOCKING Ater single CIRCUIT
C901390007 Number of DL UNBLOCK Ater single CIRCUIT
messages ..................................................................... 2249
C901390008 Number of UL UNBLOCKING Ater single CIRCUIT
C901390009 Number of UL RESET Ater CIRCUIT messages........................................................................... 2250
C901390010 Number of DL RESET Ater CIRCUIT messages........................................................................... 2250
C901390011 Number of UL RESET Ater CIRCUIT ACKNOWLEDGE messages ............................................................ 2251
C901390012 Number of DL RESET Ater CIRCUIT ACKNOWLEDGE messages ............................................................ 2251
C901390013 Number of UL BLOCK Ater GROUP CIRCUIT messages........................................................................... 2252
C901390014 Number of DL BLOCK Ater GROUP CIRCUIT messages........................................................................... 2252
C901390015 Number of UL BLOCKING Ater GROUP CIRCUIT
C901390016 Number of DL BLOCKING Ater GROUP CIRCUIT
C901390017 Number of UL UNBLOCK GROUP CIRCUIT messages on Ater................................................................ 2253
C901390018 Number of DL UNBLOCK Ater GROUP CIRCUIT
messages ..................................................................... 2254
C901390019 Number of UL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages ...................................... 2254
C901390020 Number of DL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages ...................................... 2254
C901390021 Number of UL UNEQUIPPED Ater CIRCUIT messages........................................................................... 2255
2245
C901390022 Number of DL UNEQUIPPED Ater CIRCUIT messages........................................................................... 2255

C901390023 Number of UL BLOCK A CIRCUIT messages........................................................................... 2256
C901390024 Number of DL BLOCKING A CIRCUIT ACKNOWLEDGE messages ............................................................ 2256
C901390025 Number of UL UNBLOCK A CIRCUIT messages........................................................................... 2256
C901390026 Number of DL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages .................................................. 2257
C901390027 Number of DL BLOCK A CIRCUIT messages........................................................................... 2257
C901390028 Number of UL BLOCKING A CIRCUIT ACKNOWLEDGE messages ............................................................ 2257
C901390029 Number of DL UNBLOCK A CIRCUIT messages........................................................................... 2258
C901390030 Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages .................................................. 2258
C901390031 Number of UL BLOCK A CIRCUIT GROUP messages........................................................................... 2258
C901390032 Number of DL BLOCK A CIRCUIT GROUP messages........................................................................... 2259
C901390033 Number of UL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages .................................................. 2259
C901390034 Number of DL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages .................................................. 2259
C901390035 Number of UL UNBLOCK A CIRCUIT GROUP messages........................................................................... 2260
C901390036 Number of DL UNBLOCK A CIRCUIT GROUP messages........................................................................... 2260
C901390037 Number of UL UNBLOCKING A CIRCUIT GROUP
C901390038 Number of DL UNBLOCKING A CIRCUIT GROUP
C901390039 Number of UL UNEQUIPPED A CIRCUIT messages........................................................................... 2261
C901390040 Number of DL UNEQUIPPED A CIRCUIT messages........................................................................... 2262
C901390041 Number of UL Ater RESET messages.............. 2262
C901390042 Number of DL Ater RESET messages ............. 2262
C901390043 Number of UL Ater RESET ACKNOWLEDGE messages........................................................................... 2263
C901390044 Number of DL Ater RESET ACKNOWLEDGE messages........................................................................... 2263
C901390045 Number of UL Ater CONFUSION messages........................................................................... 2263
C901390046 Number of DL Ater CONFUSION messages........................................................................... 2264
C901390047 Number of RESOURCE REQUEST messages........................................................................... 2264
C901390048 Number of RESOURCE INDICATION messages........................................................................... 2264
C901390049 Number of RESOURCE NON-INDICATION messages........................................................................... 2265
C901390050 Number of resource release request messages........................................................................... 2265
C901390051 Number of resource release acknowledge messages........................................................................... 2266
C901390052 Number of resource failure messages ............ 2266
C901390053 Number of TFO status messages ................... 2266
2246
Chapter 45 Ater Message Measurement
C901390054 Number of TFO common voice type messages........................................................................... 2267

C901390055 Number of TFO control messages .................. 2267
Overview
Ater interface message counters are used to collect statistics on
messages transceived on Ater interface. It is counted by AterDispatch according to iTC office.
BLOCK Ater single CIRCUIT
messages
Definition
Description
Measurement
Point
Unit
Related Features
Number of UL BLOCK Ater single CIRCUIT messages

This counter counts the number of BLOCK messages sent by BSC
to iTC.
When BSC sends a BLOCK message, this counter increments.
Times
ZGO-05-02-005 Flex Ater
DL BLOCKING Ater single
CIRCUIT ACKNOWLEDGE
messages
Definition
Number of DL BLOCKING Ater single CIRCUIT ACKNOWLEDGE

messages
Description
This counter counts the number of BLOCKING ACKNOWLEDGE

messages received by BSC from iTC.
Measurement
Point
When BSC receives a BLOCKING ACKNOWLEDGE message, this

counter increments.
Unit
Related Features
Times
2247
UL UNBLOCK Ater single
CIRCUIT messages
Definition
Number of UL UNBLOCK Ater single CIRCUIT messages
Description
This counter counts the number of UNBLOCK messages sent by

BSC to iTC.
Measurement
Point
When BSC sends an UNBLOCK message, this counter increments.
Unit
Related Features
Times
UNBLOCKING Ater single
CIRCUIT ACKNOWLEDGE
messages
Definition
Number of DL UNBLOCKING Ater single CIRCUIT ACKNOWLEDGE

messages
Description
This counter counts the number of UNBLOCKING ACKNOWLEDGE

Measurement
Point
When BSC receives an UNBLOCKING ACKNOWLEDGE message,

Unit
Related Features
Times
BLOCK Ater single CIRCUIT
messages
Definition
Description
2248
Number of DL BLOCK Ater single CIRCUIT messages

This counter counts the number of BLOCK messages received by
BSC from iTC.
Measurement
Point
Unit
Related Features
When BSC receives a BLOCK message, this counter increments.

Times
UL BLOCKING Ater single
CIRCUIT ACKNOWLEDGE
messages
Definition
Number of UL BLOCKING Ater single CIRCUIT ACKNOWLEDGE

messages
Description
This counter counts the number of BLOCKING ACKNOWLEDGE

messages sent by BSC to iTC.
Measurement
Point
When BSC sends a BLOCKING ACKNOWLEDGE message, this

counter increments.
Unit
Related Features
Times
DL UNBLOCK Ater single
CIRCUIT messages
Definition
Number of DL UNBLOCK Ater single CIRCUIT messages
Description
This counter counts the number of UNBLOCK messages received

by BSC from iTC.
Measurement
Point
When BSC receives an UNBLOCK message, this counter increments.
Unit
Related Features
Times
2249
UNBLOCKING Ater single
CIRCUIT ACKNOWLEDGE
messages
Definition
Number of UL UNBLOCKING Ater single CIRCUIT ACKNOWLEDGE

messages
Description
This counter counts the number of UNBLOCKING ACKNOWLEDGE

Measurement
Point
When BSC sends an UNBLOCKING ACKNOWLEDGE message,

Unit
Related Features
Times
UL RESET Ater CIRCUIT
messages
Definition
Number of UL RESET Ater CIRCUIT messages
Description
This counter counts the number of RESET CIRCUIT messages

sent by BSC to iTC.
Measurement
Point
When BSC sends a RESET CIRCUIT message, this counter increments.
Unit
Related Features
Times
DL RESET Ater CIRCUIT
messages
Definition
Description
2250
Number of DL RESET Ater CIRCUIT messages

This counter counts the number of RESET CIRCUIT messages
received by BSC from iTC.
Measurement
Point
Unit
Related Features
When BSC receives a RESET CIRCUIT message, this counter increments.

Times
UL RESET Ater CIRCUIT
Definition
Number of UL RESET Ater CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of RESET CIRCUIT ACKNOWLEDGE messages sent by BSC to iTC.
Measurement
Point
When BSC sends a RESET CIRCUIT ACKNOWLEDGE message,

Unit
Related Features
Times
DL RESET Ater CIRCUIT
Definition
Number of DL RESET Ater CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of RESET CIRCUIT ACKNOWLEDGE messages received by BSC from iTC.
Measurement
Point
When BSC receives a RESET CIRCUIT ACKNOWLEDGE message,

Unit
Related Features
Times
2251
UL BLOCK Ater GROUP
CIRCUIT messages
Definition
Number of UL BLOCK Ater GROUP CIRCUIT messages
Description
This counter counts the number of BLOCK CIRCUIT GROUP messages sent by BSC to iTC.
Measurement
Point
When BSC sends a BLOCK CIRCUIT GROUP message, this

counter increments.
Unit
Related Features
Times
DL BLOCK Ater GROUP
CIRCUIT messages
Definition
Number of DL BLOCK Ater GROUP CIRCUIT messages
Description
This counter counts the number of BLOCK CIRCUIT GROUP messages received by BSC from iTC.
Measurement
Point
When BSC receives a BLOCK CIRCUIT GROUP message, this

counter increments.
Unit
Related Features
Times
BLOCKING Ater GROUP
CIRCUIT ACKNOWLEDGE
messages
2252
Definition
Number of UL BLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE

messages
Description
This counter counts the number of BLOCKING CIRCUIT GROUP

ACKNOWLEDGE messages sent by BSC to iTC.
Measurement
Point
Unit
Related Features
When BSC sends a BLOCKING CIRCUIT GROUP ACKNOWLEDGE

Times
BLOCKING Ater GROUP
CIRCUIT ACKNOWLEDGE
messages
Definition
Number of DL BLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE

messages
Description
This counter counts the number of BLOCKING CIRCUIT GROUP

ACKNOWLEDGE messages received by BSC from iTC.
Measurement
Point
When BSC receives a BLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.
Unit
Related Features
Times
UL UNBLOCK GROUP
CIRCUIT messages on Ater
Definition
Number of UL UNBLOCK GROUP CIRCUIT messages on Ater
Description
This counter counts the number of UL UNBLOCK GROUP CIRCUIT

messages on Ater sent by BSC to iTC.
Measurement
Point
When BSC sends an UL UNBLOCK GROUP CIRCUIT messages on

Ater, this counter increments.
Unit
Related Features
Times
2253
UNBLOCK Ater GROUP
CIRCUIT messages
Definition
Number of DL UNBLOCK Ater GROUP CIRCUIT messages
Description
This counter counts the number of UNBLOCK CIRCUIT GROUP

Measurement
Point
When BSC receives an UNBLOCK CIRCUIT GROUP message, this

counter increments.
Unit
Related Features
Times
UNBLOCKING Ater GROUP
CIRCUIT ACKNOWLEDGE
messages
Definition
Number of UL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE

messages
Description
This counter counts the number of UNBLOCKING CIRCUIT GROUP

Measurement
Point
When BSC sends an UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.
Unit
Related Features
Times
UNBLOCKING Ater GROUP
CIRCUIT ACKNOWLEDGE
messages
Definition
2254
Number of DL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE

messages
Description
This counter counts the number of UNBLOCKING CIRCUIT GROUP

Measurement
Point
When BSC receives an UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.
Unit
Related Features
Times
UL UNEQUIPPED Ater
CIRCUIT messages
Definition
Number of UL UNEQUIPPED Ater CIRCUIT messages
Description
This counter counts the number of UNEQUIPPED CIRCUIT messages sent by BSC to iTC.
Measurement
Point
When BSC sends an UNEQUIPPED CIRCUIT message, this

counter increments.
Unit
Related Features
Times
DL UNEQUIPPED Ater
CIRCUIT messages
Definition
Number of DL UNEQUIPPED Ater CIRCUIT messages
Description
This counter counts the number of UNEQUIPPED CIRCUIT messages received by BSC from iTC.
Measurement
Point
When BSC receives an UNEQUIPPED CIRCUIT message, this

counter increments.
Unit
Related Features
Times
2255
UL BLOCK A CIRCUIT
messages
Definition
Number of UL BLOCK A CIRCUIT messages
Description
This counter counts the number of BLOCK A CIRCUIT messages

sent by BSC to iTC.
Measurement
Point
When BSC sends a BLOCK A CIRCUIT message, this counter increments.
Unit
Times
DL BLOCKING A CIRCUIT
Definition
Number of DL BLOCKING A CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING A CIRCUIT ACKNOWLEDGE messages received by BSC from iTC.
Measurement
Point
When BSC receives a BLOCKING A CIRCUIT ACKNOWLEDGE message, this counter increments.
Unit
Times
UL UNBLOCK A CIRCUIT
messages
Definition
Description
This counter counts the number of UNBLOCK A CIRCUIT messages sent by BSC to iTC.
Measurement
Point
When BSC sends an UNBLOCK A CIRCUIT message, this counter

increments.
Unit
2256
Number of UL UNBLOCK A CIRCUIT messages
Times
UNBLOCKING A CIRCUIT
Definition
Number of DL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of UNBLOCKING A CIRCUIT ACKNOWLEDGE messages received by BSC from iTC.
Measurement
Point
When BSC receives an UNBLOCKING A CIRCUIT ACKNOWLEDGE

Unit
Times
DL BLOCK A CIRCUIT
messages
Definition
Number of DL BLOCK A CIRCUIT messages
Description
This counter counts the number of BLOCK A CIRCUIT messages

received by BSC from iTC.
Measurement
Point
When BSC receives a BLOCK A CIRCUIT message, this counter

increments.
Unit
Times
UL BLOCKING A CIRCUIT
Definition
Number of UL BLOCKING A CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING A CIRCUIT ACKNOWLEDGE messages sent by BSC to iTC.
Measurement
Point
When BSC sends a BLOCKING A CIRCUIT ACKNOWLEDGE message, this counter increments.
Unit
Times
2257
DL UNBLOCK A CIRCUIT
messages
Definition
Number of DL UNBLOCK A CIRCUIT messages
Description
This counter counts the number of UNBLOCK A CIRCUIT messages received by BSC from iTC.
Measurement
Point
When BSC receives an UNBLOCK A CIRCUIT message, this

counter increments.
Unit
Times
Definition
Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of UNBLOCKING A CIRCUIT ACKNOWLEDGE messages sent by BSC to iTC.
Measurement
Point
When BSC sends an UNBLOCKING A CIRCUIT ACKNOWLEDGE

Unit
Times
BLOCK A CIRCUIT GROUP
messages
Definition
Description
This counter counts the number of BLOCK A CIRCUIT GROUP

Measurement
Point
When BSC sends a BLOCK A CIRCUIT GROUP message, this

counter increments.
Unit
2258
Number of UL BLOCK A CIRCUIT GROUP messages
Times
BLOCK A CIRCUIT GROUP
messages
Definition
Number of DL BLOCK A CIRCUIT GROUP messages
Description
This counter counts the number of BLOCK A CIRCUIT GROUP

Measurement
Point
When BSC receives a BLOCK A CIRCUIT GROUP message, this

counter increments.
Unit
Times
UL BLOCKING A CIRCUIT
GROUP ACKNOWLEDGE
messages
Definition
Number of UL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING A CIRCUIT GROUP

Measurement
Point
When BSC sends a BLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.
Unit
Times
DL BLOCKING A CIRCUIT
GROUP ACKNOWLEDGE
messages
Definition
Number of DL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING A CIRCUIT GROUP

2259
Measurement
Point
Unit
When BSC receives a BLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.
Times
UL UNBLOCK A CIRCUIT
GROUP messages
Definition
Number of UL UNBLOCK A CIRCUIT GROUP messages
Description
This counter counts the number of UNBLOCK A CIRCUIT GROUP

Measurement
Point
When BSC sends an UNBLOCK A CIRCUIT GROUP message, this

counter increments.
Unit
Times
DL UNBLOCK A CIRCUIT
GROUP messages
Definition
Description
This counter counts the number of UNBLOCK A CIRCUIT GROUP

Measurement
Point
When BSC receives an UNBLOCK A CIRCUIT GROUP message,

Unit
2260
Number of DL UNBLOCK A CIRCUIT GROUP messages
Times
GROUP ACKNOWLEDGE
messages
Definition
Number of UL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE

messages
Description
This counter counts the number of UNBLOCKING A CIRCUIT

GROUP ACKNOWLEDGE messages sent by BSC to iTC.
Measurement
Point
When BSC sends an UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.
Unit
Times
GROUP ACKNOWLEDGE
messages
Definition
Number of DL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE

messages
Description
This counter counts the number of UNBLOCKING A CIRCUIT

GROUP ACKNOWLEDGE messages received by BSC from iTC.
Measurement
Point
When BSC receives an UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.
Unit
Times
UNEQUIPPED A CIRCUIT
messages
Definition
Description
Number of UL UNEQUIPPED A CIRCUIT messages

This counter counts the number of UNEQUIPPED A CIRCUIT messages sent by BSC to iTC.
2261
Measurement
Point
Unit
When BSC sends an UNEQUIPPED A CIRCUIT message, this

counter increments.
Times
UNEQUIPPED A CIRCUIT
messages
Definition
Number of DL UNEQUIPPED A CIRCUIT messages
Description
This counter counts the number of UNEQUIPPED A CIRCUIT messages received by BSC from iTC.
Measurement
Point
When BSC receives an UNEQUIPPED A CIRCUIT message, this

counter increments.
Unit
Times
Ater RESET messages
Definition
Description
Measurement
Point
Unit
Related Features
Number of UL Ater RESET messages

This counter counts the number of RESET messages sent by BSC
to iTC.
When BSC sends a RESET message, this counter increments.
Times
Ater RESET messages
Definition
Description
This counter counts the number of RESET messages received by

BSC from iTC.
Measurement
Point
When BSC receives a RESET message, this counter increments.
Unit
2262
Number of DL Ater RESET messages
Times
Related Features
C901390043 Number
of UL Ater RESET
Definition
Number of UL Ater RESET ACKNOWLEDGE messages
Description
This counter counts the number of RESET ACKNOWLEDGE messages sent by BSC to iTC.
Measurement
Point
When BSC sends a RESET ACKNOWLEDGE message, this counter

increments.
Unit
Related Features
Times
C901390044 Number
of DL Ater RESET
Definition
Number of DL Ater RESET ACKNOWLEDGE messages
Description
This counter counts the number of RESET ACKNOWLEDGE messages received by BSC from iTC.
Measurement
Point
When BSC receives a RESET ACKNOWLEDGE message, this

counter increments.
Unit
Related Features
Times
UL Ater CONFUSION
messages
Definition
Description
Number of UL Ater CONFUSION messages

This counter counts the number of CONFUSION messages sent
by BSC to iTC.
2263
Measurement
Point
Unit
Related Features
When BSC sends a CONFUSION message, this counter increments.

Times
DL Ater CONFUSION
messages
Definition
Number of DL Ater CONFUSION messages
Description
This counter counts the number of CONFUSION messages received by BSC from iTC.
Measurement
Point
When BSC receives a CONFUSION message, this counter increments.
Unit
Related Features
Times
RESOURCE REQUEST
messages
Definition
Number of RESOURCE REQUEST messages
Description
This counter counts the number of RESOURCE REQUEST messages sent by BSC to iTC.
Measurement
Point
When BSC sends a RESOURCE REQUEST message, this counter

increments.
Unit
Times
RESOURCE INDICATION
messages
Definition
2264
Number of RESOURCE INDICATION messages
Description
This counter counts the number of RESOURCE REQUEST ACKNOWLEDGE messages received by BSC from iTC.
Measurement
Point
When BSC receives a RESOURCE REQUEST ACKNOWLEDGE

Unit
Times
C901390049 Number
of RESOURCE
NON-INDICATION
messages
Definition
Number of RESOURCE NON-INDICATION messages
Description
This counter counts the number of RESOURCE REQUEST NEGTIVE

Measurement
Point
When BSC receives a RESOURCE REQUEST NEGTIVE ACKNOWLEDGE message, this counter increments.
Unit
Times
resource release request
messages
Definition
Number of resource release request messages
Description
This counter counts the number of RESOURCE RELEASE REQUEST messages sent by BSC to iTC.
Measurement
Point
When BSC sends a RESOURCE RELEASE REQUEST message, this

counter increments.
Unit
Times
2265
C901390051 Number
of resource release
acknowledge messages
Definition
Number of resource release acknowledge messages
Description
This counter counts the number of RESOURCE RELEASE ACKNOWLEDGE messages received by BSC from iTC.
Measurement
Point
When BSC receives a RESOURCE RELEASE ACKNOWLEDGE message, this counter increments.
Unit
Times
resource failure messages
Definition
Number of resource failure messages
Description
This counter counts the number of RESOURCE FAILURE messages received by BSC from iTC.
Measurement
Point
When BSC receives a RESOURCE FAILURE message, this counter

increments.
Unit
Times
TFO status messages
Definition
Description
This counter counts the number of TFO STATE messages received

by BSC from iTC.
Measurement
Point
When BSC receives a TFO STATE message, this counter increments
Unit
2266
Number of TFO status messages
Times
TFO common voice type
messages
Definition
Number of TFO common voice type messages
Description
This counter counts the number of TFO CONMMONTYPE messages received by BSC from iTC.
Measurement
Point
When BSC receives a TFO CONMMONTYPE message, this counter

increments.
Unit
Times
TFO control messages
Definition
Number of TFO control messages
Description
This counter counts the number of TFO CONTROL INFORMATION

Measurement
Point
When BSC sends a TFO CONTROL INFORMATION message, this

counter increments.
Unit
Times
2267
2268
Chapter
46
MTP2 Signal Link

Measurement
Table of Contents
Overview...................................................................... 2269
C901400001 Number of error SU due to Abnormal
Flag ............................................................................. 2270
C901400002 Number of error SU Length Error .................. 2270
C901400003 Number of Out of Alignment ......................... 2270
C901400004 Number of error SU due not to Octet ............. 2271
C901400005 Number of error SU due to CRC Error ............ 2271
C901400006 Number of Other error................................. 2272
C901400007 Number of Negative Acknowledgement Received.......................................................................... 2272
C901400008 Octets of MSU Retransmitted ........................ 2272
C901400009 Number of MSU Resend ............................... 2273
C901400010 Number of Align Error.................................. 2273
C901400011 Number of Error SU..................................... 2273
C901400012 Number of MSU discarded due to congestion ............................................................................. 2274
C901400013 Number of SL failure due to Abnormal FIBR
BSNR........................................................................... 2274
C901400014 Number of SL failure due to Excessive delay of
ack .............................................................................. 2274
C901400015 Number of SL failure due to Excessive error
rate ............................................................................. 2275
C901400016 Number of SL failure due to Excessive duration
of congestion ................................................................ 2275
Overview
Platform signaling defines a MTP2 performance statistic structure:
T_PM_SIG_MTP2_Link and defines a structure array according to
the maximum number of links, ie, 128. In this way, error codes,
frame loss, faults, and congestion can be counted according to link
number.
2269
error SU due to Abnormal
Flag
Definition
Number of error SU due to Abnormal Flag
Description
This counter counts the number of SUs with seven consecutive

1s in message code stream received by an MTP2 link. According
to the protocol, the valid flag is 01111110 and a flag with seven
consecutive 1s is invalid. If this message carries 1111111, this
counter increments.
Usage
This counter is used to find out the occurrence of SUs carrying

seven consecutive 1s in message code stream received by an MTP2
link.
Measurement
Point
When an MTP2 link receives a message code stream carrying

1111111, this counter increments.
Unit
Times
error SU Length Error
Definition
Number of error SU Length Error
Description
This counter counts the number of SUs with overlong or too short
messages received by an MTP2 link. According to the protocol,
a signal unit (SU) contains at least six octets and at most 279
octets. If the number of octets is smaller than 6 or bigger than
279, the length of the signal unit is wrong. and this counter increments.(Note: an octet is equal to a byte, that is 8 bits.)
Usage
This counter is used to find out the occurrence of SUs carrying

overlong or too short messages received by an MTP2 link.
Measurement
Point
When a message octet is shorter than 6 or longer than 127, this

counter increments.
Unit
Times
C901400003 Number of Out

of Alignment
Definition
Description
2270
Number of Out of Alignment

This counter counts the number of message code streams out of
alignment received by an MTP2 link. According to the protocol,
Chapter 46 MTP2 Signal Link Measurement
there is an eight-bit flag each at the head and tail of a signal unit
to identify the signal unit. When the flag is invalid or the length
of the signal unit exceeds the maximum value, location is lost. In
this case, this counter increments.
Usage
This counter is used to find out the occurrence of message code

streams out of alignment received by an MTP2 link.
Measurement
Point
When the flag is invalid or the length of the signal unit exceeds
the maximum value, this counter increments.
Unit
Times
error SU due not to Octet
Definition
Number of error SU due not to Octet
Description
This counter counts the times of message code streams with nonoctet received by an MTP2 link. According to the protocol, the
composition of the signal unit is a multiple of 8 bits. When an
octet composed of non-8 bits occurs, this counter increments.
Usage
This counter is used to find out the occurrence of message code

streams with non-octet received by an MTP2 link.
Measurement
Point
When an octet composed of non-8 bits occurs, this counter increments.
Unit
Times
error SU due to CRC Error
Definition
Number of error SU due to CRC Error
Description
This counter counts the number of CRC errors received by an MTP2

link. According to the protocol, a signal unit has a 16-bit check
code at its tail, which is generated when the signal unit is sent.
The check code is checked at the receiving end. When a CRC error
occurs, this counter increments.
Usage
This counter is used to find out the occurrence of CRC errors received by an MTP2 link.
Measurement
Point
Unit
When a CRC error occurs, this counter increments.

Times
2271
Other error
Definition
Number of Other error
Description
This counter counts the number of other message errors received

by an MTP2 link. When errors other than the above four types
occur, this counter increments.
Usage
This counter is used to find out the occurrence of message errors

other than the above four types received by an MTP2 link.
Measurement
Point
When errors other than the above four types occur, this counter
increments.
Unit
Times
Negative Acknowledgement
Received
Definition
Number of Negative Acknowledgement Received
Description
This counter counts the number of negative acknowledgements

received by an MTP2 link.
Usage
This counter is used to find out the occurrence of negative acknowledgements received by an MTP2 link.
Measurement
Point
When an MTP2 link receives a negative acknowledgement, this

counter increments.
Unit
Times
C901400008 Octets of MSU

Retransmitted
Definition
Description
This counter counts the number of octets retransmitted by an MTP2

link.
Usage
This counter is used to find out the frequency of retransmission of

an MTP2 link.
Measurement
Point
When an MTP2 link is retransmitted, this counter increments by

the corresponding octet.
Unit
2272
Octets of MSU Retransmitted
octet
MSU Resend
Definition
Number of MSU Resend
Description
This counter counts the number of MSU packets resent by MTP2.
Usage
This counter is used to find out the frequency of MTP2 resending.
Measurement
Point
When an MTP2 link is resent, this counter increments by the corresponding number of resent packets.
Unit
Packet
Align Error
Definition
Number of Align Error
Description
This counter counts the number of alignment or check error of an

MTP2 link.
Usage
This counter is used to find out the frequency of alignment failures

of an MTP2 link.
Measurement
Point
When an MTP2 link receives AlignNtpsbl during alignment, this

counter increments.
Unit
Times
Error SU
Definition
Number of Error SU
Description
This counter counts the number of error SUs received by an MTP2

link.
Usage
This counter is used to find out the frequency of receiving error

SUs received by an MTP2 link.
Measurement
Point
When an MTP2 link receives an error SU, this counter increments.
Unit
Times
2273
MSU discarded due to
congestion
Definition
Number of MSU discarded due to congestion
Description
This counter counts the number of MSUs discarded due to congestion resulted from full buffer on an MTP2 link.
Usage
This counter is used to find out the frequency discarding MSUs due
to congestion resulted from full buffer on an MTP2 link.
Measurement
Point
When an MTP2 link discards MSU due to congestion, this counter

increments.
Unit
Times
C901400013 Number of SL
failure due to Abnormal FIBR
BSNR
Definition
Number of SL failure due to Abnormal FIBR/BSNR
Description
This counter counts the number of SL failures due to abnormal

FIBR/BSNR.
Usage
This counter is used to find out the occurrence of SL failures due

to abnormal FIBR/BSNR.
Measurement
Point
When an MTP2 link is broken due to abnormal FIBBSN, this counter

increments.
Unit
Times
SL failure due to Excessive
delay of ack
Definition
2274
Number of SL failure due to Excessive delay of ack
Description
This counter counts the number of SL failures due to excessive

delay of acknowledgement.
Usage

to excessive delay of acknowledgement.
Measurement
Point
Unit
When an MTP2 link is broken due to excessive delay of acknowledgement, this counter increments.
Times
error rate
Definition
Number of SL failure due to Excessive error rate
Description

error rate.
Usage

to excessive error rate.
Measurement
Point
When an MTP2 link is broken due to excessive error rate, this

counter increments.
Unit
Times
duration of congestion
Definition
Number of SL failure due to Excessive duration of congestion
Description

duration of congestion.
Usage

to excessive duration of congestion.
Measurement
Point
When an MTP2 link is broken due to congestion, this counter increments.
Unit
Times
2275
2276
Chapter
47
CPU MEM Measurement

Table of Contents
Overview...................................................................... 2277
C901410001 Peak memory usage of the main processor .............................................................................. 2277
C901410002 Mean value of the memory usage.................. 2278
C901410003 Peak load of CPU usage of the main processor .............................................................................. 2278
C901410004 Mean ratio of the CPU usage......................... 2278
C901410005 Duration of the main processor keeping in peak
state............................................................................ 2279
C901410006 The time when peak load CPU usage occurred.......................................................................... 2279
C901410007 peak kilo-bytes of the rest UB....................... 2280
C901410008 Mean kilo-bytes of the rest UB ...................... 2280
Overview
To explicate CPU and memory usages during platform running
procedure and provide reference for future upgrade and maintenance, the system enables users to view peak CPU usage,
remaining memory, and peak of the rest UB in the specified
period. Eight counters are provided, as shown in the following
sections.
C901410001 Peak memory

usage of the main processor
Definition
Peak memory usage of the main processor
Description
This counter compares the memory usages of all measurement

points measured at an interval of 2 seconds in the measurement
period and specifies the maximum measurement point as the peak
load.
Usage
This counter is used to view the peak memory usage of the main
processor in measurement period.
Measurement
Point
In the sampling period, sample a memory usage every 2 seconds.
2277
Unit
Percent
C901410002 Mean value of

the memory usage
Definition
Mean value of the memory usage
Description
This counter averages the memory usages of all measurement

points at an interval of 2 seconds in the measurement period and
outputs the mean value.
Usage
This counter is used to find out the mean memory usage of the
system.
Measurement
Point
In the sampling period, sample a memory usage every 2 seconds.
Unit
Percent
C901410003 Peak load of

CPU usage of the main
processor
Definition
Peak load of CPU usage of the main processor
Description
This counter samples CPU usage at an interval of 2 seconds and

specifies the maximum memory usage in the measurement period
as the peak load of CPU usage of the main processor.
Usage
This counter is used to view the peak load of CPU usage in the
specified measurement period.
Measurement
Point
In the sampling period, sample a CPU usage every 2 seconds and

use the peak value as the maximum value of the measurement
point.
Unit
Percent
C901410004 Mean ratio of

the CPU usage
Definition
2278
Mean ratio of the CPU usage
Chapter 47 CPU MEM Measurement
Description
This counter samples CPU usage at an interval of 2 seconds, averages the CPU usages of all measurement points, and outputs the
mean value.
Usage
This counter is used to find out the mean CPU usage in the specified
period.
Measurement
Point
In the sampling period, sample a CPU usage every 2 seconds. Divide the sum of the values of all measurement points by the number of measurement points.
Unit
Percent
C901410005 Duration of the

main processor keeping in
peak state
Definition
Duration of the main processor keeping in peak state
Description
This counter counts the duration of the main processor in peak

state.
Usage
This counter is used to find out the duration of CPU peak status,
which can serve as a reference for knowing system operating conditions.
Measurement
Point
In the sampling period, count and record the maximum values of

main processor peak at all measurement points, and accumulate
the duration of the maximum measurement point.
Unit
Second
C901410006 The time

when peak load CPU usage
occurred
Definition
The time when peak load CPU usage occurred
Description
This counter records the time when peak load of main processor
occurred for the first time in the measurement period. The time is
the number of seconds relative to 00:00:00 January 1, 2000.
Usage
This counter is used to find out the time when CPU peak occurred,
which provides a basis for system performance analysis.
Measurement
Point
In the sampling period, trace the time when the load of main processor reaches peak. At the end of collection period, output the
traced time point.
Unit
Second
2279
C901410007 peak kilo-bytes

of the rest UB
Definition
peak kilo-bytes of the rest UB
Description
In the measurement period, sample bytes of the rest UB at an

interval of 2 seconds, collect statistics in the sampling period, and
output the peak value of measurement point.
Usage
This counter is used to find out the peak kilo-bytes of the rest UB.
Measurement
Point
In the sampling period, do sampling at an interval of 2 seconds

and get the maximum kilo-bytes of the rest UB.
Unit
Byte
C901410008 Mean
kilo-bytes of the rest UB
Definition
Description
Usage
Measurement
Point
Unit
2280
Mean kilo-bytes of the rest UB

In the sampling period, do sampling at an interval of 2 seconds.
Divide the sum of the values of all measurement points by the
number of measurement points.
This counter is used to find out the condition of the rest UB.
At the end of a collection period, average the bytes of the rest UB
sampled every 2 seconds.
Byte
Chapter
48
SCTP AS Measurement
Table of Contents
Overview...................................................................... 2282
C901420001 Number of IP packets dropped by SCTP due to
some reasons ............................................................... 2282
C901420002 Number of received SCTP packets ................. 2282
C901420003 Bytes of packets received from ip.................. 2283
C901420004 Number of packets sent to ip ........................ 2283
C901420005 Bytes of packets sent to ip ........................... 2283
C901420006 Number of messages sent to ulp ................... 2284
C901420007 Bytes of messages sent to ulp ...................... 2284
C901420008 Number of messages received from ulp.......... 2284
C901420009 Bytes of messages received from .................. 2285
C901420010 Number of Congestion ................................. 2285
C901420011 Duration of congestion................................. 2285
C901420012 Chunk number of fast retransmission............. 2286
C901420013 Chunk number of time-out retransmission ............................................................................. 2286
C901420014 RTT is lower than T1.................................... 2286
C901420015 RTT is between T1 and T2 ............................ 2287
C901420016 RTT is higher than T2 .................................. 2287
C901420017 Number of network transmission dropped packets .............................................................................. 2287
C901420018 Maximum delay of network transmission......... 2288
C901420019 Minimum delay of network transmission......... 2288
C901420020 Total delay of network transmission(high 4
bytes).......................................................................... 2289
C901420021 Total delay of network transmission(low 4
bytes).......................................................................... 2289
C901420022 Number of delay samples of network transmission ............................................................................. 2289
C901420023 Maximum dithering of network transmission ............................................................................. 2290
C901420024 Minimum dithering of network transmission ............................................................................. 2290
C901420025 Total dithering of network transmission(high 4
bytes).......................................................................... 2291
C901420026 Total dithering of network transmission(low 4
bytes).......................................................................... 2291
C901420027 Number of dithering samples of network transmission ........................................................................ 2292
C901420028 Chunks Lost On Send Dirction....................... 2292
C901420029 Chunks Trans On Send Dirction ..................... 2292
C901420030 Number of abort from peer .......................... 2293
C901420031 Number of association break by retransmission ............................................................................. 2293
2281
Overview
SCTP AS measurement mainly collects statistics on values related
to SCTP, such as data receiving and sending and associated items
(congestion, delay, and dithering).
C901420001 Number of IP
packets dropped by SCTP
due to some reasons
Definition
Number of IP packets dropped by SCTP due to some reasons
Description
This counter counts the number of IP packets dropped by the SCTP,

including heartbeat and SHUTDOWN. When SCTP drops packets,
Usage
This counter is used to find out the number of packets dropped by

SCTP.
Measurement
Point
Unit
When SCTP drops packets, this counter will count.

Times
received SCTP packets
Definition
Description
This counter counts the number of IP packets received by the SCTP,

including heartbeat and SHUTDOWN. When SCTP receives packets, this counter increments.
Usage
This counter is used to find out the number of packets received by

SCTP.
Measurement
Point
Unit
2282
Number of received SCTP packets
When SCTP receives packets, this counter will count.

Times
Chapter 48 SCTP AS Measurement
C901420003 Bytes of
packets received from ip
Definition
Bytes of packets received from ip
Description
This counter counts the number of packet bytes received by the

SCTP. The length of only valid data in DATA CHUNK is counted.
When SCTP receives DATA packets, this counter accumulates.
Usage
This counter is used to find out the number of DATA packet bytes
received by SCTP.
Measurement
Point
Unit
When SCTP receives DATA packets, this counter will count.

Times
packets sent to ip
Definition
Number of packets sent to ip
Description
This counter counts the number of IP packets sent by the SCTP,

including heartbeat and SHUTDOWN. When SCTP sends packets,
Usage
This counter is used to find out the number of packets sent by

SCTP.
Measurement
Point
Unit
When SCTP sends packets, this counter will count.

Times
C901420005 Bytes of
packets sent to ip
Definition
Bytes of packets sent to ip
Description
This counter counts the number of packet bytes sent by the SCTP.
The length of only valid data in DATA CHUNK is counted. When
SCTP sends DATA packets, this counter accumulates.
Usage
This counter is used to find out the number of DATA packet bytes
sent by SCTP.
Measurement
Point
Unit
When SCTP sends DATA packets, this counter will count.

Times
2283
messages sent to ulp
Definition
Number of messages sent to ulp
Description
This counter counts the number of messages sent by the SCTP to

ULP. When SCTP sends messages to ULP, this counter increments.
Usage
This counter is used to find out the number of messages sent by

SCTP to ULP.
Measurement
Point
Unit
When SCTP sends messages to ULP, this counter will count.

Times
C901420007 Bytes of
messages sent to ulp
Definition
Bytes of messages sent to ulp
Description
This counter counts the number of message bytes sent by the SCTP
to ULP. When SCTP sends messages to ULP, this counter accumulates.
Usage
This counter is used to find out the number of message bytes sent
by SCTP to ULP.
Measurement
Point
Unit
When SCTP sends messages to ULP, this counter will count.

Times
messages received from ulp
Definition
Description
This counter counts the number of message bytes received by

the SCTP from ULP. When SCTP receives messages from ULP, this
Usage
This counter is used to find out the number of messages received

by SCTP from ULP.
Measurement
Point
Unit
2284
Number of messages received from ulp
When SCTP receives ULP messages, this counter will count.

Times
C901420009 Bytes of
messages received from
Definition
Bytes of messages received from ulp
Description
This counter counts the number of message bytes received by

the SCTP from ULP. When SCTP receives messages from ULP, this
Usage
This counter is used to find out the number of message bytes received by SCTP from ULP.
Measurement
Point
Unit
When SCTP receives ULP messages, this counter will count.

Times
Congestion
Definition
Number of Congestion
Description
This counter counts the number of congestion control module

zooming out congestion windows.
When congestion control
module zooms out congestion windows, this counter accumulates.
Usage
This counter is used to find out the number of SCTP congestions.
Measurement
Point
When congestion control module zooms out congestion windows,

this counter will count.
Unit
Times
congestion
Definition
Description
Usage
Measurement
Point
Duration of congestion
This counter counts the congestion duration.
This counter is used to find out the duration of SCTP congestion.
SCTP congestion control.
2285
Unit
ms
C901420012 Chunk number

of fast retransmission
Definition
Chunk number of fast retransmission
Description
This counter counts the number of chunks fast transmitted by the

SCTP. If the data sending end receives three SACKs indicating loss
of a DATA chunk, SCTP fast transmits chunks and this counter
increments.
Usage
This counter is used to find out the number of chunks fast transmitted by SCTP.
Measurement
Point
Unit
When SCTP fast transmits chunks, this counter will count.

Times
C901420013 Chunk number

of time-out retransmission
Definition
Chunk number of time-out retransmission
Description
This counter counts the number of chunks retransmitted by the

SCTP due to timeout. If the timeout retransmission timer times
out, SCTP fast retransmits chunks and this counter increments.
Usage
This counter is used to find out the number of chunks fast transmitted by SCTP.
Measurement
Point
When SCTP retransmits chunks due to timeout, this counter will

count.
Unit
Times
C901420014 RTT is lower

than T1
Definition
2286
RTT is lower than T1
Description
This counter counts the statistics of RTT lower than T1. When RTT
is lower than T1, this counter accumulates.
Usage
This counter is used to find out the statistics of RTT lower than T1.
Measurement
Point
When the sampled RTT is lower than T1, this counter will counts.
Unit
None
C901420015 RTT is
between T1 and T2
Definition
RTT is between T1 and T2
Description
This counter counts the statistics of RTT between T1 and T2. When
RTT is between T1 and T2, this counter accumulates.
Usage
This counter is used to find out the statistics of RTT between T1

and T2.
Measurement
Point
When the sampled RTT is between T1 and T2, this counter will
count.
Unit
None
C901420016 RTT is higher

than T2
Definition
RTT is higher than T2
Description
This counter counts the statistics of RTT higher than T2. When RTT
is higher than T2, this counter accumulates.
Usage
This counter is used to find out the statistics of RTT higher than
T2.
Measurement
Point
Unit
When the sampled RTT is higher than T2, this counter will count.
None
C901420017 Number
of network transmission
dropped packets
Definition
Description
Number of network transmission dropped packets

This counter counts the number of dropped packets during network
transmission and chunks re-transmitted. When SCTP receives no
response after sending packets, this counter counts during retransmission.
2287
Usage
This counter is used to find out the statistics of packets dropped

during network transmission.
Measurement
Point
If SCTP receives no response after sending packets, this counter

will count during retransmission.
Unit
Related Features
Times
ZGO-05-04-005 IP SLA Monitoring
C901420018 Maximum
delay of network
transmission
Definition
Maximum delay of network transmission
Description
This counter counts the maximum delay of network transmission of

SCTP packets in an interval. When the actual network transmission
delay is greater than maximum delay of network transmission, the
actual one prevails.
Usage
This counter is used to find out the maximum delay of network

transmission.
Measurement
Point
When RTT is calculated based on RTO sampling, determine the

maximum delay of network transmission.
Unit
Related Features
ms
C901420019 Minimum delay

of network transmission
Definition
Description
This counter counts the minimum delay of network transmission of

SCTP packets in an interval. When the actual network transmission
delay is smaller than maximum delay of network transmission, it
replaces the minimum delay of network transmission.
Usage
This counter is used to find out the minimum delay of network

transmission.
Measurement
Point

minimum delay of network transmission.
Unit
Related Features
2288
Minimum delay of network transmission
ms
C901420020 Total delay of

network transmission(high 4
bytes)
Definition
Total delay of network transmission (high 4 bytes)
Description
This counter counts the high 4 bytes of total delay of network

transmission for processing SCTP packets.
Usage
This counter is used to find out the total delay of network transmission for processing SCTP packets.
Measurement
Point
When RTT is calculated based on RTO sampling, delay of network

transmission is accumulated.
Unit
Related Features
ms
C901420021 Total delay of

network transmission(low 4
bytes)
Definition
Total delay of network transmission(low 4 bytes)
Description
This counter counts the low 4 bytes of total delay of network transmission for processing SCTP packets.
Usage
This counter is used to find out the total delay of network transmission for processing SCTP packets.
Measurement
Point
When RTT is calculated based on RTO sampling, delay of network

transmission is accumulated.
Unit
Related Features
ms
delay samples of network
transmission
Definition
Number of delay samples of network transmission
2289
Description
This counter counts the number of delay samples of network transmission. In measurement internal, each time delay is sampled,
this counter accumulates.
Usage
This counter is used to find out the number of delay samples in

measurement interval.
Measurement
Point
When a delay sampling is done in measurement interval, this

counter will count.
Unit
Related Features
Times
C901420023 Maximum
dithering of network
transmission
Definition
Maximum dithering of network transmission
Description
This counter counts the maximum dithering of network transmission of SCTP packets in an interval. When the actual network
transmission dithering is greater than maximum dithering of network transmission, the actual one prevails.
Usage
This counter is used to find out the maximum dithering of network

transmission.
Measurement
Point

maximum dithering of network transmission.
Unit
Related Features
ms
C901420024 Minimum
dithering of network
transmission
Definition
2290
Minimum dithering of network transmission
Description
This counter counts the minimum dithering of network transmission of SCTP packets in an interval. When the actual network
transmission dithering is smaller than maximum dithering of network transmission, it replaces the minimum dithering of network
transmission.
Usage
This counter is used to find out the minimum dithering of network

transmission.
Measurement
Point
Unit
Related Features

minimum dithering of network transmission.
ms
C901420025 Total dithering

of network transmission(high
4 bytes)
Definition
Total dithering of network transmission(high 4 bytes)
Description
This counter counts the high 4 bytes of total dithering of network

Usage
This counter is used to find out the total dithering of network transmission for processing SCTP packets.
Measurement
Point
When RTT is calculated based on RTO sampling, dithering of network transmission is accumulated.
Unit
Related Features
ms
C901420026 Total dithering

of network transmission(low
4 bytes)
Definition
Total dithering of network transmission(low 4 bytes)
Description
This counter counts the low 4 bytes of total dithering of network

Usage
This counter is used to find out the total dithering of network transmission for processing SCTP packets.
Measurement
Point
When RTT is calculated based on RTO sampling, dithering of network transmission is accumulated.
Unit
Related Features
ms
2291
dithering samples of network
transmission
Definition
Number of dithering samples of network transmission
Description
This counter counts the number of delay samples of network transmission. In measurement internal, each time dithering is sampled,
this counter accumulates.
Usage
This counter is used to find out the number of dithering samples

in measurement interval.
Measurement
Point
When a dithering sampling is done in measurement interval, this

counter will count.
Unit
Related Features
Times
C901420028 Chunks Lost

On Send Dirction
Description
This counter counts the number of data blocks retransmitted by

SCTP.
Usage
This counter is used to study the link quality and whether the two
parties of the communication are normal. If the counter's value
keeps increasing, it might be due to lost packets or large network
delay.
Measurement
Point
Unit
The counter counts when the data block marked as lost by SCTP
(due to retransmission timer being timeout or determined by rapid
retransmission algorithm) is sent.
Number of data blocks
C901420029 Chunks Trans

On Send Dirction
2292
Description
This counter counts the number of data blocks transmitted by

SCTP.
Usage
This counter is used to study the data transceiving of SCTP. Usually,

the counter's value is studied together with C901420028's value
and the number of data blocks received at the opposite end, or
with the data sending condition at upper level.

Measurement
Point
Unit
The counter counts when the data block is sent. Here, the data
block is the one sent for the first time.
Number of data blocks
abort from peer
Description
Usage
Measurement
Point
Unit
This counter counts the number of link breaks due to abort initiated
from the peer end.
When the abort message is received from the peer end, the
counter increments.
Times
C901420031 Number
of association break by
retransmission
Description
Usage
Measurement
Point
Unit
This counter counts the number of link breaks due to retransmission.

When the link breaks due to retransmission, the counter increments.
Times
2293
2294
Chapter
49
IP Port Performance
Statistics
Table of Contents
Overview...................................................................... 2295
C901430001 Packets number received ............................. 2295
C901430002 Packets number transmitted ......................... 2296
C901430003 Packets number discarded at rx end .............. 2296
C901430004 Packets number discarded at tx end .............. 2296
Overview
IP port performance statistics performs measurement for the number of messages received, transmitted, and discarded at the external physical port of IP interface board.
IP port performance statistics involves debugging performance
data and performance data that are useful for module debugging
and commissioning. Periodical statistics of IP port performance
data can reflect the characteristic of the port's history flow, such
as the average number of messages transmitted/received per
second at the port, flow burst, and bidirectional flow symmetry,
etc. At present, physical boards it supports include BIPI and GIPI.
Statistic unit in this measurement is times that the message is
counted. The measurement obtains the average number of received/transmitted messages per second (PPS) at the port by controlling the period of sampling IP port performance data.
C901430001 Packets
number received
Definition
Packets number received
Description
This counter counts the number of messages received at IP port.

The counter increments when a message is received.
Usage
This counter is used to observe the number of messages received

at IP port.
2295
Measurement
Point
Unit
The counter accumulates when there is message received at IP

port.
Times
C901430002 Packets
number transmitted
Definition
Packets number transmitted
Description
This counter counts the number of messages sent at IP port. The

counter increments when a message is sent.
Usage
This counter is used to observe the number of messages sent at

IP port.
Measurement
Point
Unit
The counter accumulates when there is message sent at IP port.

Times
C901430003 Packets
number discarded at rx end
Definition
Packets number discarded at rx end
Description
This counter counts the number of messages discarded at the receiving end of IP port. The counter increments when an incorrect
message is discarded at the receiving end.
Usage
This counter is used to observe the number of messages discarded

at the receiving end of IP port.
Measurement
Point
The counter accumulates when there is incorrect message discarded at the receiving end of IP port.
Unit
Times
C901430004 Packets
number discarded at tx end
Definition
Description
2296
Packets number discarded at tx end

This counter counts the number of messages discarded at the
transmitting end of IP port. The counter increments when an incorrect message is discarded at the transmitting end.
Chapter 49 IP Port Performance Statistics
Usage
This counter is used to observe the number of messages discarded

at the transmitting end of IP port.
Measurement
Point
The counter accumulates when there is incorrect message discarded at the transmitting end of IP port.
Unit
Times
2297
2298
Chapter
50
GTRUNK Resource
Statistics
Table of Contents
Overview...................................................................... 2299
C901440001 Maximum of used DSP TS ............................ 2299
C901440002 Maximum of the used sampling according to DSP
TS ............................................................................... 2300
C901440003 Amount of used DSP TS ............................... 2300
C901440004 Number of regular scanning and sampling ............................................................................ 2300
Overview
GTRUNK refers to the timeslot resource on UPU DSP. GTRUNK resource statistics is used to monitor the GTRUNK resource usage,
which helps implement Gb interface capacity expansion.
Statistic unit in this measurement is UPU DSP.
C901440001 Maximum of
used DSP TS
Definition
Maximum of used DSP TS
Description
This counter counts the maximum number of each UPU DSP timeslot resource being occupied within the measurement period.
Usage
This counter is used to find out the occupation of UPU DSP timeslot resource by PS service, which helps optimize the UPU DSP resource.
Measurement
Point
The counter counts when PS user requests for the UPU DSP timeslot resource successfully.
Unit
Times
2299
the used sampling according
to DSP TS
Description
This counter counts the number of available UPU DSP timeslot resource at the measurement point of C901440001, which is the
sum of the number of occupied timeslots and the number of idle
timeslots.
Usage
This counter is used to find out the availability of UPU DSP timeslot
resource when PS service occupies the UPU DSP timeslot resource
the most.
Measurement
Point
Unit
Times
C901440003 Amount of
used DSP TS
Definition
Amount of used DSP TS
Description
This counter accumulates at each measurement point to get the

sum of UPU DSP timeslot resource used by PS service within the
measurement period.
Usage
This counter reflects the average occupation of UPU DSP resource

in PS service.
Measurement
Point
Unit
Times
C901440004 Number
sampling
Definition
Description
2300
Number of regular scanning and sampling

UPU DSP resource in PS service.
Chapter 50 GTRUNK Resource Statistics
Usage
This counter reflects the average occupation of UPU DSP resource

in PS service.
Measurement
Point
Unit
Times
2301
2302
Chapter
51
Other Process Statistics

Table of Contents
Overview...................................................................... 2304
C901450001 Max time of NACC cell reselection ................. 2305
C901450002 Minimum time of NACC cell reselection .......... 2305
C901450003 Total time of NACC cell reselection ................ 2306
C901450004 Number of NACC cell reselection (PCCN to flush
LL) .............................................................................. 2307
C901450005 Number of NACC cell reselection without receiving flush LL................................................................... 2308
C901450006 Number of UL packet channel frame adjustment ........................................................................... 2309
C901450007 Number of DL packet channel frame adjustment ........................................................................... 2309
C901450008 Sum of C ................................................... 2310
C901450009 Sum of RxQual ........................................... 2310
C901450010 Sum of GMSK-MEAN-BEP ............................. 2311
C901450011 Sum of GMSK-CV-BEP ................................. 2312
C901450012 Sum of 8PSK-MEAN-BEP .............................. 2313
C901450013 Sum of 8PSK-CV-BEP .................................. 2314
C901450014 Number of sampling of C ............................. 2315
C901450015 Number of sampling of RxQual...................... 2316
C901450016 Number of sampling of GMSK-MEAN-BEP......... 2317
C901450017 Number of sampling of GMSK-CV-BEP............ 2318
C901450018 Number of sampling of 8PSK-MEAN-BEP......... 2319
C901450019 Number of sampling of 8PSK-CV-BEP............. 2320
C901450020 Number of RLC uplink ACK TBF ..................... 2321
C901450021 Number of RLC uplink NACK TBF ................... 2322
C901450022 Number of DL-UNITDATA messages with Service
UTRAN CCO received by BSC .......................................... 2322
C901450023 Total Block Num.......................................... 2323
C901450024 UL Idle Block Num ...................................... 2323
C901450025 DL Idle Block Num ...................................... 2323
C901450026 The max length of packet latency period in
Abis............................................................................. 2323
C901450027 The min length of packet latency period in
Abis............................................................................. 2324
C901450028 The average length of packet latency period in
Abis............................................................................. 2324
C901450029 The latest length of packet latency period in
Abis............................................................................. 2325
C901450030 The length of packet latency period between 0
and 20 ms (20 included) in Abis ...................................... 2325
ms and 40 ms (40 included) in Abis ................................. 2326
2303

ms and 100 ms (100 included) in Abis.............................. 2327
C901450039 The length of packet latency period larger than
180 ms in Abis .............................................................. 2330
C901450040 The max length of downlink packet latency period in Gb ..................................................................... 2330
C901450041 The min length of downlink packet latency period in Gb ..................................................................... 2330
C901450042 The average length of downlink packet latency
period in Gb.................................................................. 2331
C901450043 The length of downlink packet latency period between 0 and 100 ms (100 included) in Gb......................... 2331
C901450044 The length of downlink packet latency period between 100 ms and 200 ms (200 included) in Gb ................ 2332
C901450048 The length of downlink packet latency period between 600 ms and 1000 ms (1000 included) in Gb............. 2334
larger than 1000 ms in Gb .............................................. 2334
C901450050 The max length of uplink packet latency period
in Gb ........................................................................... 2335
C901450051 The min length of uplink packet latency period
in Gb ........................................................................... 2335
C901450052 The average length of uplink packet latency period in Gb ..................................................................... 2335
C901450053 LLC Stall Num ............................................ 2336
C901450054 MAC Resource Congestion ............................ 2336
C901450055 BSSGP Resource Congestion......................... 2336
C901450056 Number of Pushing Down Uplink BandWidth
.................................................................................. 2337
C901450057 Number of Pushing Down Downlink BandWidth
.................................................................................. 2337
C901450058 Number of Pushing Up Uplink BandWidth......... 2338
C901450059 Number of Pushing Up Downlink BandWidth .......................................................................... 2339
Overview
Other process measurements contain the measurement on adjustments of frame number and NACC processes.
2304
Chapter 51 Other Process Statistics
C901450001 Max time of

NACC cell reselection
Description
Usage
Measurement
Point
Do NACC after receiving the Packet Cell Change Notification message sent by MS at network side. SGSN sends Flush LL to BSS
after receiving the uplink frame sent by the MS in reselection cell,
to notify cell reselection has been successfully done by the BSS
MS.
It is used to measure the max duration of NACC.
The NACC duration is a sampling period, starting with BSS receiving the Packet Cell Change Notification message sent by MS and
ending with BSS receiving the Flush LL message sent by SGSN.
FIGURE 2334 NACC DURATION
C901450002 Minimum time

of NACC cell reselection
Description
Usage
MS.
It is used to measure the minimum duration of NACC.
2305
Measurement
Point
Minimum time of this NACC is the minimum of all NACC periods in

a sampling period.
C901450003 Total time of

Description
MS.
Usage
It is used to measure the total time of all successful NACCs in this

cell.
Measurement
Point
2306
Total time of this NACC is the sum of all NACC periods in a sampling
period.
(PCCN to flush LL)
Description
Usage
Measurement
Point
MS.
It is used to measure the number of NACC success.
2307
POINT OF NUMBER OF
NACC
SUCCESS
without receiving flush LL
Description
Do NACC after receiving the Packet Cell Change Notification message sent by MS at network side. The MS decides whether to do
cell reselection after the MS gets the system message about adjacent cell at network side.
Usage
It is used to measure the number of NACC without receiving flush

LL.
Measurement
Point
2308
POINT OF NUMBER OF
NACCS
UL packet channel frame
adjustment
Description
This counter increments every 20 ms while recording a uplink

frame number on packet channel to locate the received MAC
block. BTS maintains an absolute frame number and reports it
through PCU frame. Adjust the frame number in uplink channel
if these two values are different.
Usage
It is used to measure the number of UL packet channel frame adjustment.
Measurement
Point
Do the measurement while the uplink frame number carried in

uplink PCU frame is inconsistent with the uplink frame number
recorded on the channel.
DL packet channel frame
adjustment
Description
This counter increments every 20 ms while recording a downlink

frame number on the packet channel to locate the received MAC
block. BTS maintains an absolute frame number and reports the
2309
adjustment degree of downlink frame number through PCU frame.

Adjust the downlink frame number on the channel if the adjustment value is not 0.
Usage
It is used to measure the number of DL packet channel frame adjustment.
Measurement
Point
Do the measurement while the adjustment value of downlink frame

number carried in uplink PCU frame is not 0 and not located in the
protection period.
C901450008 Sum of C
Description
Usage
Measurement
Point
This counter counts the C value in channel quality report while

DRLC receives GPRS PACKET DOWNLINK ACK or EGPRS PACKET
DOWNLINK ACK.
This counter measures the C value about the channel quality.
For GPRS or EGPRS, this counter increments while receiving
PACKET DOWNLINK ACK. The measurement point is A, as shown
in Figure 2339.
Unit
POINT FOR THE SUM OF
None
C901450009 Sum of RxQual
2310
Description
This counter counts the RxQual value in channel quality report

while DRLC receives GPRS PACKET DOWNLINK ACK.
Usage
This counter measures the RxQual value about the channel quality.
Measurement
Point
This counter increments while GPRS receives PACKET DOWNLINK

ACK. The measurement point is A, as shown in Figure 2340.
Unit
None
C901450010 Sum of
GMSK-MEAN-BEP
Description
This counter counts the GMSK-MEAN-BEP value in channel quality

report while DRLC receives EGPRS PACKET DOWNLINK ACK.
Usage
This counter measures the GMSK-MEAN-BEP value about the channel quality.
Measurement
Point
This counter increments when EGPRS receives PACKET DOWNLINK

ACK and the GMSK_MEAN_BEP indication bit is 1 in the channel
quality report. The measurement point is A, as shown in Figure
2341.
2311
Unit
None
C901450011 Sum of
GMSK-CV-BEP
2312
Description
This counter counts the GMSK-CV-BEP value in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK.
Usage
This counter measures the GMSK-CV-BEP value about the channel

quality.
Measurement
Point

2342.
Unit
None
C901450012 Sum of
8PSK-MEAN-BEP
Description
This counter counts the 8PSK-MEAN-BEP value in channel quality

report while DRLC receives EGPRS PACKET DOWNLINK ACK.
Usage
This counter measures the 8PSK-MEAN-BEP value about the channel quality.
Measurement
Point

ACK and the 8PSK_MEAN_BEP indication bit is 1 in the channel
2343.
2313
Unit
None
C901450013 Sum of
8PSK-CV-BEP
2314
Description
This counter counts the 8PSK-CV-BEP value in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK.
Usage
This counter measures the 8PSK-CV-BEP value about the channel

quality.
Measurement
Point

2344.
Unit
None
sampling of C
Description
This counter counts the number of C sampling points in channel

quality report while DRLC receives GPRS PACKET DOWNLINK ACK
or EGPRS PACKET DOWNLINK ACK.
Usage
This counter measures the number of C sampling points about the

channel quality.
Measurement
Point
For GPRS or EGPRS, this counter increments while receiving

PACKET DOWNLINK ACK. The measurement point is A, as shown
in Figure 2345.
2315
Unit
Times
sampling of RxQual
2316
Description
This counter counts the number of RxQual sampling points in channel quality report while DRLC receives GPRS PACKET DOWNLINK
ACK.
Usage
This counter measures the number of RxQual sampling points

about the channel quality.
Measurement
Point
This counter increments while GPRS receives PACKET DOWNLINK

ACK. The measurement point is A, as shown in Figure 2346.
Unit
Times
C901450016 Number
of sampling of
GMSK-MEAN-BEP
Description
This counter counts the number of GMSK-MEAN-BEP sampling

points in channel quality report when DRLC receives EGPRS
PACKET DOWNLINK ACK.
Usage
This counter measures the number of GMSK-MEAN-BEP sampling

points about the channel quality.
Measurement
Point

2347.
2317
Unit
None
sampling of GMSK-CV-BEP
2318
Description
This counter counts the number of GMSK-CV-BEP sampling points

in channel quality report while DRLC receives EGPRS PACKET
DOWNLINK ACK.
Usage
This counter measures the number of GMSK-CV-BEP sampling

Measurement
Point

2348.
Unit
Times
C901450018 Number
of sampling of
8PSK-MEAN-BEP
Description
This counter counts the number of 8PSK-MEAN-BEP sampling

points in channel quality report while DRLC receives EGPRS
PACKET DOWNLINK ACK.
Usage
This counter measures the number of 8PSK-MEAN-BEP sampling

Measurement
Point

2349.
2319
Unit
None
sampling of 8PSK-CV-BEP
2320
Description
This counter counts the number of 8PSK-CV-BEP sampling points

in channel quality report while DRLC receives EGPRS PACKET
DOWNLINK ACK.
Usage
This counter measures the number of 8PSK-CV-BEP sampling

Measurement
Point

2350.
Unit
Times
RLC uplink ACK TBF
Description
This counter counts the number of TBFs while URLC receives the
uplink assginment or DTM assignment and the resource assignment message shall be recorded under the acknowledgement
mode.
Usage
This counter measures the number of uplink TBFs under the acknowledgement mode.
Measurement
Point
This counter measures the number of TBFs when URLC receives

the uplink assginment or DTM assignment and the resource assignment message shall be recorded under the acknowledgement
mode. The measurement point is A, as shown in Figure 2351.
Unit
POINT OF
NUMBER
OF
RLC
UPLINK
ACK TBF
Times
2321
RLC uplink NACK TBF
Description
This counter counts the number of TBFs while URLC receives the
uplink assginment or DTM assignment and the resource assignment message shall be recorded under the unacknowledgement
mode.
Usage
This counter measures the number of uplink TBFs under the unacknowledgement mode.
Measurement
Point
This counter measures the number of TBFs when URLC receives the
uplink assginment or DTM assignment and the resource assignment message shall be recorded under the unacknowledgement
mode. The measurement point is A, as shown in Figure 2352.
Unit
POINT OF
NUMBER
OF
RLC
UPLINK
ACK TBF
Times
DL-UNITDATA messages
with Service UTRAN CCO
received by BSC
2322
C901450023 Total Block

Num
C901450024 UL Idle Block

Num
C901450025 DL Idle Block

Num
C901450026 The max length

of packet latency period in
Abis
Statistics object
Description
Cell
This counter counts the maximum delay of the cell's PS service
at Abis interface within the measurement period. When the uplink frame number and downlink frame number of PS service at
BSC are synchronized, the counter gets the difference between
the uplink frame number and downlink frame number, thus to get
the delay of PS service at Abis interface. After comparison, the
counter records the maximum delay.
2323
Unit
ms
C901450027 The min length

of packet latency period in
Abis
Statistics object
Description
Unit
Cell
This counter counts the minimum delay of the cell's PS service
at Abis interface within the measurement period. When the uplink frame number and downlink frame number of PS service at
BSC are synchronized, the counter gets the difference between
the uplink frame number and downlink frame number, thus to get
the delay of PS service at Abis interface. After comparison, the
counter records the minimum delay.
ms
C901450028 The average

length of packet latency
period in Abis
Statistics object
Description
2324
Cell
This counter counts the average delay of the cell's PS service at
Abis interface within the measurement period. When the uplink
frame number and downlink frame number of PS service at BSC
are synchronized, the counter gets the difference between the uplink frame number and downlink frame number, thus to get the
delay of PS service at Abis interface. After adding all delays and
dividing the sum by the number of measurements, the counter
records the average delay.
Unit
ms
C901450029 The latest

length of packet latency
period in Abis
Statistics object
Description
Unit
Cell
This counter counts the latest delay of the cell's PS service at
Abis interface within the measurement period. When the uplink
delay of PS service at Abis interface. The counter records the latest delay.
ms
C901450030 The length

of packet latency period
between 0 and 20 ms (20
included) in Abis
Statistics object
Description
Unit
Cell
This counter counts the number of samples of which the delay of
the cell's PS service at Abis interface is in the range of (0, 20 ms]
within the measurement period. When the uplink frame number
and downlink frame number of PS service at BSC are synchronized,
the counter gets the difference between the uplink frame number
and downlink frame number, thus to get the delay of PS service
at Abis interface. If the delay is in the range, then the counter
increments.
Times
2325

between 20 ms and 40 ms
(40 included) in Abis
Statistics object
Description
Unit
Cell
the cell's PS service at Abis interface is in the range of (20 ms, 40
ms] within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame
number and downlink frame number, thus to get the delay of PS
service at Abis interface. If the delay is in the range, then the
counter increments.
Times

Statistics object
Description
Unit
2326
Cell
counter increments.
Times

Statistics object
Description
Unit
Cell
counter increments.
Times

Statistics object
Description
Unit
Cell
counter increments.
Times
2327

Statistics object
Description
Unit
Cell
This counter counts the number of samples of which the delay
of the cell's PS service at Abis interface is in the range of (100
ms, 120 ms] within the measurement period. When the uplink
delay of PS service at Abis interface. If the delay is in the range,
Times

Statistics object
Description
Unit
2328
Cell
Times

Statistics object
Description
Unit
Cell
Times

Statistics object
Description
Unit
Cell
Times
2329
C901450039 The length of

packet latency period larger
than 180 ms in Abis
Statistics object
Description
Unit
Cell
the cell's PS service at Abis interface is in the range of (180 ms,
+] within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame
counter increments.
Times
C901450040 The max length

of downlink packet latency
period in Gb
Statistics object
Description
Unit
Cell
This counter counts the maximum delay of the cell's PS service
in downlink transmission at Gb interface within the measurement
period. At BSC, when IP packet is received at Gb interface, the
downlink received time is recorded; when IP packet is sent at Gb
interface, the downlink sent time is recorded. Subtract the downlink received time from the downlink sent time to get the downlink
delay at Gb interface. After comparison, the counter records the
maximum delay.
ms

period in Gb
Statistics object
Description
2330
Cell
This counter counts the minimum delay of the cell's PS service
in downlink transmission at Gb interface within the measurement

delay at Gb interface. After comparison, the counter records the
minimum delay.
Unit
ms

length of downlink packet
latency period in Gb
Statistics object
Description
Unit
Cell
This counter counts the average delay of the cell's PS service in
downlink transmission at Gb interface within the measurement
delay at Gb interface. Add the subtraction result with all downlink
delays at Gb interface to get the total delay. Divide the sum by
the number of measurements, and the counter records the average delay.
ms

period between 0 and 100
ms (100 included) in Gb
Statistics object
Description
Unit
Cell
the cell's PS service in downlink transmission at Gb interface is
in the range of (0 ms, 100 ms] within the measurement period.
At BSC, when IP packet is received at Gb interface, the downlink
received time is recorded; when IP packet is sent at Gb interface,
the downlink sent time is recorded. Subtract the downlink received
time from the downlink sent time to get the downlink delay at Gb
interface. If the delay is in the range, then the counter increments.
Times
2331

period between 100 ms and
200 ms (200 included) in Gb
Statistics object
Description
Unit
Cell
the cell's PS service in downlink transmission at Gb interface is in
the range of (100 ms, 200 ms] within the measurement period.
Times

Statistics object
Description
Unit
2332
Cell
Times

Statistics object
Description
Unit
Cell
Times

Statistics object
Description
Unit
Cell
Times
2333

1000 ms (1000 included) in
Gb
Statistics object
Description
Unit
Cell
Times

period larger than 1000 ms
in Gb
Statistics object
Description
Unit
2334
Cell
the cell's PS service in downlink transmission at Gb interface is
in the range of (1000 ms, +) within the measurement period.
Times
C901450050 The max

length of uplink packet
Statistics object
Description
Unit
Cell
This counter counts the maximum delay of the cell's PS service in
uplink transmission at Gb interface within the measurement period. At BSC, when IP packet is sent at Gb interface, the uplink
sent time is recorded; when IP packet is received at Gb interface,
the uplink received time is recorded. Subtract the uplink sent time
from the uplink received time to get the uplink delay at Gb interface. After comparison, the counter records the maximum delay.
ms

of uplink packet latency
period in Gb
Statistics object
Description
Unit
Cell
This counter counts the minimum delay of the cell's PS service in
uplink transmission at Gb interface within the measurement period. At BSC, when IP packet is sent at Gb interface, the uplink
sent time is recorded; when IP packet is received at Gb interface,
the uplink received time is recorded. Subtract the uplink sent time
from the uplink received time to get the uplink delay at Gb interface. After comparison, the counter records the minimum delay.
ms

length of uplink packet
Statistics object
Description
Cell
This counter counts the average delay of the cell's PS service in uplink transmission at Gb interface within the measurement period.
At BSC, when IP packet is sent at Gb interface, the uplink sent time
is recorded; when IP packet is received at Gb interface, the uplink
2335
received time is recorded. Subtract the uplink sent time from the
uplink received time to get the uplink delay at Gb interface. Add
the subtraction result with all uplink delays at Gb interface to get
the total delay. Divide the sum by the number of measurements,
and the counter records the average delay.
Unit
ms
C901450053 LLC Stall Num

C901450054 MAC Resource

Congestion
Description
This counter counts the number of failures in requesting for MAC

instance resource. If obtaining MAC instance fails in requesting for
MAC instance resource, the counter increments.
Usage
This counter is used to find out the number of failures in creating

MAC instance.
Measurement
Point
1. When BSC receives the Channel Request message from MS, if

BSC fails to create the MAC instance, then the counter counts.
2. When BSC receives the downlink data from SGSN, if BSC fails
to create the MAC instance, then the counter counts.
Unit
Times
C901450055 BSSGP
Resource Congestion
Description
This counter counts the number of failures in requesting for BSSGP

instance resource. If obtaining BSSGP instance fails in requesting
for BSSGP instance resource, the counter increments.
Usage
This counter is used to find out the number of failures in creating

BSSGP instance.
Measurement
Point
Unit
2336
When BSC receives the downlink data from SGSN, if BSC fails to
create the BSSGP instance, then the counter counts.
Times
Pushing Down Uplink
BandWidth
Description
This counter counts the number of pushing down uplink bandwidth

in the cell. When BSC control plane judges that the actual uplink bandwidth exceeds C1, which is the safe allocation upper limit
about bandwidth at the resource pool, if the current theoretically
allocated uplink bandwidth of resource pool is larger than available
uplink bandwidth, BSC control plane sends the message of pushing down uplink bandwidth to BSC user plane. When BSC user
plane receives the message, the counter increments.
Usage
The counter is used to find out the frequency of pushing down

uplink bandwidth in the cell.
Measurement
Point
The counter counts when BSC user plane receives the message of
pushing down uplink bandwidth. The measurement point is A, as
FIGURE 2353 FLOW
Unit
OF
PUSHING DOWN UPLINK BANDWIDTH
Times
Pushing Down Downlink
BandWidth
Description
This counter counts the number of pushing down downlink bandwidth in the cell. When BSC control plane judges that the actual
downlink bandwidth exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, if the current theoretically allocated downlink bandwidth of resource pool is larger
than available downlink bandwidth, BSC control plane sends the
message of pushing down downlink bandwidth to BSC user plane.
2337
When BSC user plane receives the message, the counter increments.
Usage

downlink bandwidth in the cell.
Measurement
Point
pushing down downlink bandwidth. The measurement point is A,
FIGURE 2354 FLOW
Unit
OF
PUSHING DOWN DOWNLINK BANDWIDTH
Times
C901450058 Number
of Pushing Up Uplink
BandWidth
Description
This counter counts the number of pushing up uplink bandwidth

in the cell. When BSC control plane judges that the actual uplink
bandwidth is lower than C3, which is the congestion pushing up
limit, BSC control plane sends the message of pushing up uplink
bandwidth to BSC user plane. When BSC user plane receives the
message, the counter increments.
Usage
The counter is used to find out the frequency of pushing up uplink

bandwidth in the cell.
Measurement
Point
2338
The counter counts when BSC user plane receives the message
of pushing up uplink bandwidth. The measurement point is A, as
FIGURE 2355 FLOW
Unit
OF
PUSHING UP UPLINK BANDWIDTH
Times
Pushing Up Downlink
BandWidth
Description
This counter counts the number of pushing up downlink bandwidth

in the cell. When BSC control plane judges that the actual downlink
bandwidth is lower than C3, which is the congestion pushing up
limit, BSC control plane sends the message of pushing up downlink
bandwidth to BSC user plane. When BSC user plane receives the
message, the counter increments.
Usage
The counter is used to find out the frequency of pushing up downlink bandwidth in the cell.
Measurement
Point
pushing up downlink bandwidth. The measurement point is A, as
FIGURE 2356 FLOW
Unit
OF
PUSHING UP DOWNLINK BANDWIDTH
Times
2339
2340
Chapter
52
FR Carried Links
Statistics
Table of Contents
Overview...................................................................... 2341
C901460001 Number of Status enquiry Message sent......... 2341
C901460002 Number of Status ACK Message received......... 2342
C901460003 Number of link exception ............................. 2343
C901460004 Number of bytes received on BRCH ............... 2344
C901460005 Number of bytes sent on BRCH ..................... 2344
Overview
FR carrier links statistics measures the message transceiving information at FR sublayer of NS layer at Gb interface in GPRS service, including the number of status queries, the number of status
responses, the number of bytes sent/received on BRCH, and the
number of abnormalities on BRCH. It helps check the running status and load of BRCH.
Statistic unit in this measurement is BRCH.
Status enquiry Message
sent
Description
BSC sends the "Status Enquiry" message to query BRCH's status.

This counter counts the number of "Status Enquiry" messages sent
by BSC.
Measurement
Point
When BSC sends the "Status Enquiry" message, this counter increments. The measurement point is A1, as shown in Figure 2357.
2341
FIGURE 2357 STATUS QUERY PROCESS
Status ACK Message
received
2342
Description
When SGSN receives the "Status Enquiry" message from BSC,

it sends the "Status" message to indicate BRCH's status. This
counter counts the number of "Status" messages received by BSC.
Measurement
Point
When BSC receives the "Status" message, this counter increments. The measurement point is A2, as shown in Figure 2358.
Chapter 52 FR Carried Links Statistics
C901460003 Number of link

exception
Description
During the process of querying BRCH's status between BSC and

SGSN, this counter counts the number of errors occurred at N392
every N393.
Usage
Check the counter's value to observe the running status of BRCH.
Measurement
Point
During the process of querying BRCH's status, this counter increments when error occurs at N392 every N393. The measurement
2343
bytes received on BRCH
Description
This counter counts the number of bytes received on BRCH of FR

sublayer.
contains FR header.
Usage
Check the number of bytes received on BRCH to observe the load

of BRCH.
Measurement
Point
FR accumulates the number of bytes received on BRCH from Gb

interface.
bytes sent on BRCH
Description
This counter counts the number of bytes sent on BRCH of FR sublayer.

contains FR header.
2344
Usage
Check the number of bytes sent on BRCH to observe the load of

BRCH.
Measurement
Point
FR accumulates the number of bytes sent on BRCH from Gb interface.
Chapter
53
OMP PS Service
Statistics
Table of Contents
Overview...................................................................... 2345
Overview
Counters of OMP-PS service statistics counts messages related to
PS service on OMP, including messages of suspension and resuming. These counters are used to observe the frequency of MS's
requesting for terminating GPRS service and resuming GPRS service.
Description
This counter counts the number of SUSPEND messages sent to an

SGSN from site or cell within the measurement period.
Usage
This counter counts the number of SUSPEND messages sent to an

SGSN from site or cell in downlink within the measurement period.
Measurement
Point
Unit
The counter counts when the GB_SUSPEND message is sent.

Times
2345
SUSPEND-ACK message
received
Description
This counter counts the number of SUSPEND-ACK messages received by site or cell from an SGSN within the measurement period.
Usage
This counter counts the number of SUSPEND-ACK messages received by site or cell from an SGSN within the measurement period.
Measurement
Point
The counter counts when the GB_SUSPEND_ACK message is received from SGSN.
Unit
Times
received
Description
This counter counts the number of SUSPEND-NACK messages received by site or cell from an SGSN within the measurement period.
Usage
This counter counts the number of SUSPEND-NACK messages received by site or cell from an SGSN within the measurement period.
Measurement
Point
The counter counts when the GB_SUSPEND_NACK message is received from SGSN.
Unit
Times
RESUME message sent
Description
This counter counts the number of RESUME messages sent to an

SGSN from site or cell within the measurement period.
Usage
This counter counts the number of RESUME messages sent to an

SGSN from site or cell in downlink within the measurement period.
Measurement
Point
Unit
2346
The counter counts when the GB_RESUME message is sent.

Times
Chapter 53 OMP PS Service Statistics
RESUME-ACK message
received
Description
This counter counts the number of RESUME-ACK messages received by site or cell from an SGSN within the measurement period.
Usage
This counter counts the number of RESUME-ACK messages received by site or cell from an SGSN within the measurement period.
Measurement
Point
The counter counts when the GB_RESUME_ACK message is received from SGSN.
Unit
Times
RESUME-NACK message
received
Description
This counter counts the number of RESUME-NACK messages received by site or cell from an SGSN within the measurement period.
Usage
This counter counts the number of RESUME-NACK messages received by site or cell from an SGSN within the measurement period.
Measurement
Point
The counter counts when the GB_RESUME_NACK message is received from SGSN.
Unit
Times
2347
2348
Chapter
54
SNS on OMP Statistics

Table of Contents
Overview...................................................................... 2350
C901480001 Number of SNS-SIZE initiations .................... 2350
C901480002 Number of SNS-SIZE received successful acknowledgements ........................................................... 2350
C901480003 Number of SNS-SIZE failures........................ 2351
C901480004 Number of SNS-SIZE initiated by BSC without
response ...................................................................... 2351
C901480005 Number of SNS-CONFIG initiated by BSC......... 2351
C901480006 Number of SNS-CONFIG initiated by BSC received successful acknowledgements ............................... 2352
C901480007 Number of SNS-CONFIG initiated by BSC received failed acknowledgements ...................................... 2352
C901480008 Number of SNS-CONFIG initiated by BSC without response................................................................. 2353
C901480009 Number of SNS-CONFIG initiated by SGSN received successful acknowledgements ............................... 2353
C901480010 Number of SNS-CONFIG initiated by SGSN received failed acknowledgements ...................................... 2354
C901480011 Number of SNS-ADD initiated by BSC ............ 2354
C901480012 Number of SNS-ADD initiated by BSC received
successful acknowledgements ......................................... 2355
C901480013 Number of SNS-ADD initiated by BSC received
failed acknowledgements................................................ 2355
C901480014 Number of SNS-ADD initiated by BSC without
response ...................................................................... 2356
C901480015 Number of SNS-ADD initiated by SGSN received
successful acknowledgements ......................................... 2356
C901480016 Number of SNS-ADD initiated by SGSN received
failed acknowledgements................................................ 2357
C901480017 Number of SNS-DELETE initiated by BSC......... 2357
C901480018 Number of SNS-DELETE initiated by BSC received successful acknowledgements ............................... 2358
C901480019 Number of SNS-DELETE initiated by BSC received failed acknowledgements ...................................... 2358
C901480020 Number of SNS-DELETE initiated by BSC without
response ...................................................................... 2359
C901480021 Number of SNS-DELETE initiated by SGSN received successful acknowledgements ............................... 2359
C901480022 Number of SNS-DELETE initiated by SGSN received failed acknowledgements ...................................... 2360
BSC ............................................................................. 2360
BSC received successful acknowledgements ...................... 2361
BSC received failed acknowledgements ............................ 2361
2349

BSC without response .................................................... 2362
SGSN received successful acknowledgements.................... 2362
SGSN received failed acknowledgements .......................... 2363
Overview
These counters are used when Gb interface adopts IP transmission
mode and the transmission link's IP address and PORT are configured dynamically. They count messages involved in the flow of
port negotiation and port's weight negotiation between iBSC and
sgsnce. Statistic unit in this measurement is NSE.
SNS-SIZE initiations
Description
This counter counts the number of SNS-SIZE messages sent by

NSE within the measurement period.
Usage
This counter counts the number of SNS-SIZE messages sent by

Measurement
Point
The counter counts in the following two cases:

1. The configuration at background is modified, and the database
triggers the counting.
2. The SNS process timer expires, triggering the counting.
Unit
Related Features
Times
SNS-SIZE received success
ful acknowledgements
2350
Description
This counter counts the number of acknowledged responses from

NSE after NSE receives the SNS-SIZE message within the measurement period.
Usage

NSE after NSE receives SNS-SIZE within the measurement period.
Chapter 54 SNS on OMP Statistics
Measurement
Point
Unit
Related Features
The counter counts when the EV_NSCTRL_SIZE_ACK message

from SGSN is received.
Times
SNS-SIZE failures
Description
This counter counts the number of unacknowledged responses

from NSE after NSE receives the SNS-SIZE message within the
measurement period.
Usage

from NSE after NSE receives SNS-SIZE within the measurement
period.
Measurement
Point
After the SNS-SIZE message is received, this counter counts when

NSE sends response message with the cause of unavailable NSVC
or unavailable IPV4.
Unit
Related Features
Times
SNS-SIZE initiated by BSC
without response
Related Features
SNS-CONFIG initiated by
BSC
Description
This counter counts the number of SNS-CONFIG messages sent by

Usage
This counter counts the number of SNS-CONFIG messages sent by

2351
Measurement
Point
Unit
Related Features
The counter counts after NSE sends the SNS-CONFIG message.

Times
BSC received successful
acknowledgements
Description

NSE after NSE receives the SNS-CONFIG message within the measurement period.
Usage

NSE after NSE receives the SNS-CONFIG message successfully
Measurement
Point
The counter counts when NSE returns the acknowledged response

after receiving the SNS-CONFIG message.
Unit
Related Features
Times
SNS-CONFIG initiated
by BSC received failed
acknowledgements
Description

from NSE after NSE receives the SNS-CONFIG message within
Usage

from NSE after NSE receives the SNS-CONFIG message within
Measurement
Point
The counter counts when NSE returns the unacknowledged response after receiving the SNS-CONFIG message.
Unit
Related Features
2352
Times
BSC without response
Description
This counter counts the number of SNS-CONFIG messages initiated by BSC but without any response within the measurement
period.
Usage
This counter counts the number of SNS-CONFIG messages initiated by BSC but without any response within the measurement
period.
Measurement
Point
The counter counts when it is timeout during the process of waiting

for NSE's response for the SNS-CONFIG message.
Unit
Related Features
Times
SGSN received successful
acknowledgements
Description
This counter counts the number of acknowledged responses of

SNS-CONFIG messages initiated by SGSN within the measurement
period.
Usage

SNS-CONFIG messages initiated by SGSN within the measurement
period.
Measurement
Point
The counter counts when the EV_NSCTRL_CONFIG_IND message

is received which indicates that the IP endpoint at SGSN is
recorded successfully.
Unit
Related Features
Times
2353
SNS-CONFIG initiated
by SGSN received failed
acknowledgements
Description
This counter counts the number of failures of the SNS-CONFIG

message initiated by SGSN within the measurement period.
Usage
This counter counts the number of failures of the SNS-CONFIG

message initiated by SGSN within the measurement period.
Measurement
Point
The counter counts when the EV_NSCTRL_CONFIG_IND message

is received which indicates that the IP endpoint at SGSN fails to
be recorded.
Unit
Related Features
Times
SNS-ADD initiated by BSC
Description
This counter counts the number of SNS-ADD messages initiated

by BSC within the measurement period.
Usage

Measurement
Point
The counter counts when BSC sends the EV_NSOAM_ADD_REQ

message.
Unit
Related Features
2354
Times
SNS-ADD initiated by
acknowledgements
Description
This counter counts the number of acknowledged responses of the

SNS-ADD message initiated by BSC within the measurement period.
Usage

SNS-ADD message initiated by BSC within the measurement period.
Measurement
Point
When BSC receives the EV_NSCTRL_SNSACK_IND message with

acknowledgement, the counter increments.
Unit
Related Features
Times
C901480013 Number
of SNS-ADD initiated
acknowledgements
Description
This counter counts the number of unacknowledged responses of

the SNS-ADD message initiated by BSC within the measurement
period.
Usage

the SNS-ADD message initiated by BSC within the measurement
period.
Measurement
Point

unacknowledgement, the counter increments.
Unit
Related Features
Times
2355
SNS-ADD initiated by BSC
without response
Description

by BSC but without any response within the measurement period.
Usage

Measurement
Point
The counter counts when it is timeout during the process of BSC's

waiting for the response for the SNS-ADD message.
Unit
Related Features
Times
acknowledgements
Description

SNS-ADD messages initiated by SGSN within the measurement
period.
Usage

period.
Measurement
Point
The counter counts when the EV_NSCTRL_ADD_IND message is

received which indicates that the IP endpoint at SGSN is recorded
successfully.
Unit
Related Features
2356
Times
SGSN received failed
acknowledgements
Description

period.
Usage

period.
Measurement
Point
The counter counts when the EV_NSCTRL_ADD_IND message is

received which indicates that the IP endpoint at SGSN fails to be
recorded.
Unit
Related Features
Times
SNS-DELETE initiated by
BSC
Description
This counter counts the number of SNS-DELETE messages initiated

Usage

Measurement
Point
The counter counts when the EV_NSOAM_DELETE_REQ message

is sent.
Unit
Related Features
Times
2357
acknowledgements
Description

SNS-DELETE message initiated by BSC within the measurement
period.
Usage

SNS-DELETE message initiated by BSC within the measurement
period.
Measurement
Point
The counter counts when BSC receives the SNS-ACK message with
acknowledgement.
Unit
Related Features
Times
SNS-DELETE initiated
acknowledgements
Description

the SNS-DELETE message initiated by BSC within the measurement period.
Usage

the SNS-DELETE message initiated by BSC within the measurement period.
Measurement
Point
The counter counts when BSC receives the SNS-ACK message with
unacknowledgement.
Unit
Related Features
2358
Times
BSC without response
Description

Usage

Measurement
Point

waiting for the response of SNS-DELETE message.
Unit
Related Features
Times
acknowledgements
Description

SNS-DELETE messages initiated by SGSN within the measurement
period.
Usage

period.
Measurement
Point
The counter counts when the EV_NSCTRL_DELETE_IND message

is received which indicates that the IP endpoint at SGSN is
recorded successfully.
Unit
Related Features
Times
2359
SNS-DELETE initiated
by SGSN received failed
acknowledgements
Description

period.
Usage

period.
Measurement
Point
The counter counts when the EV_NSCTRL_DELETE_IND message

is received which indicates that the IP endpoint at SGSN fails to
be recorded.
Unit
Related Features
Times
SNS-CHANGEWEIGHT
initiated by BSC
Description
This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC within the measurement period.
Usage
This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC within the measurement period.
Measurement
Point
The counter counts when BSC receives the EV_NSOAM_CHANGEWEIGHT_REQ message.
Unit
Related Features
2360
Times
SNS-CHANGEWEIGHT
initiated by BSC
received successful
acknowledgements
Description

SNS-CHANGEWEIGHT message initiated by BSC within the measurement period.
Usage

SNS-CHANGEWEIGHT message initiated by BSC within the measurement period.
Measurement
Point

acknowledgement, the counter increments.
Unit
Related Features
Times
SNS-CHANGEWEIGHT
initiated by BSC received
failed acknowledgements
Description

the SNS-CHANGEWEIGHT message initiated by BSC within the
measurement period.
Usage

the SNS-CHANGEWEIGHT message initiated by BSC within the
measurement period.
Measurement
Point

unacknowledgement, the counter increments.
Unit
Related Features
Times
2361
SNS-CHANGEWEIGHT
initiated by BSC without
response
Description
This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC but without any response within the measurement period.
Usage
This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC but without any response within the measurement period.
Measurement
Point

waiting for the response for the SNS-CHANGEWEIGHT message.
Unit
Related Features
Times
SNS-CHANGEWEIGHT
initiated by SGSN
received successful
acknowledgements
Description

SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period.
Usage

SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period.
Measurement
Point
The counter counts when the EV_NSCTRL_CHANGEWEIGHT_IND

message is received which indicates that the IP endpoint at SGSN
is recorded successfully.
Unit
Related Features
2362
Times
SNS-CHANGEWEIGHT
initiated by SGSN received
failed acknowledgements
Description

the SNS-CHANGEWEIGHT message initiated by SGSN within the
measurement period.
Usage

the SNS-CHANGEWEIGHT message initiated by SGSN within the
measurement period.
Measurement
Point
The counter counts when the EV_NSCTRL_CHANGEWEIGHT_IND

message is received which indicates that the IP endpoint at SGSN
fails to be recorded.
Unit
Related Features
Times
2363
2364
Chapter
55
IPGB StrongARM NSVC

Statistics
Table of Contents
Overview...................................................................... 2365
C901490001 Number of bytes received from SGSN ............ 2365
C901490002 Number of bytes sent to SGSN ..................... 2365
C901490003 Number of PDU data sent by NS sub layer......... 2366
layer............................................................................ 2366
layer............................................................................ 2367
Overview
IPGB StrongARM NSVC statistics measures the signaling interaction and data transmission at NS layer of Gb interface in GPRS
service.
bytes received from SGSN
Related Features
bytes sent to SGSN
Description
This counter counts the number of bytes sent to SGSN from NS

sub layer.
2365
Usage

Measurement
Point
IP accumulates the number of bytes sent each time. The measurement point is A1, as shown in Figure 2360.
FIGURE 2360 UPLINK NS DATA
Unit
Related Features
Byte
PDU data sent by NS sub
layer
Related Features
PDU data received by NS
sub layer
Related Features
2366
Chapter 55 IPGB StrongARM NSVC Statistics
PDU data discarded by NS
sub layer
Related Features
2367
2368
Chapter
56
IPGB StrongARM Gb
Statistics
Table of Contents
Overview...................................................................... 2369
BSSGP level.................................................................. 2369
BSSGP level.................................................................. 2370
Overview
IPGB StrongARM Gb message statistics measures the number of
transceiving uplink/downlink data at BSSGP layer of Gb interface
in GPRS service.
UNITDATA messages
Related Features
2369
UNITDATA messages
Related Features
2370
Chapter
57
Queue Measurement
Table of Contents
Overview...................................................................... 2371
C901510001 Average length of queue .............................. 2371
C901510002 Duration of queuing .................................... 2372
C901510003 Number of queuing ..................................... 2374
C901510004 Duration of queuing success ......................... 2375
C901510005 Number of queuing success .......................... 2376
Overview
Queue measurement counters reflect the following information:
the number of queuing users in a cell, the total queuing time, the
number of queuing successes, and the duration of queuing success. These counters are used to find out how busy the channels
are in a cell.
The measurement unit is cell.
C901510001 Average length

of queue
Description
This counter counts the average queue length that a user has to
wait for after entering the queue during the assignment or handover process.
Usage
The counter's value is calculated by dividing the total queue length

by the number of queues.
Measurement
Point
When the measurement period expires, divide the total queue

length by the number of queues to calculate the counter's value.
The measurement point is shown in Figure 2361.
2371
Unit
OF
AVERAGE
LENGTH OF QUEUE
Times
queuing
2372
Description
This counter counts the total queuing time after a user enters the
queue during the assignment or handover process. When the user
enters the queue, the start queuing time is recorded; when the
user exits the queue, the total queuing time is calculated by subtracting the start queuing time from the current time.
Usage
The counter is used to find out how busy the channels are in a cell.
Measurement
Point
This counter counts the total queuing time of a user in the

cell. When the user enters the queue, the start queuing time
is recorded; when the user exits the queue, the total queuing
Chapter 57 Queue Measurement
time is calculated by subtracting the start queuing time from the

current time. The measurement point is B2, as shown in Figure
2362 and Figure 2363.
Unit

QUEUING FAILS
OF
QUEUING DURATION
WHEN

QUEUING SUCCEEDS
OF
QUEUING DURATION
WHEN
Times
2373
queuing
Description
This counter counts the number of users entering the queue during the assignment or handover process. The counter increments
every time a user exits the queue.
Usage
This counter is used to find out how many queuing users there are
in a cell.
Measurement
Point
This counter counts the number of queuing users in a cell. The

counter increments every time a user exits the queue. The measurement point is B2, as shown in Figure 2364 and Figure 2365.
QUEUING FAILS
2374
OF
QUEUING DURATION
WHEN

QUEUING SUCCEEDS
Unit
OF
QUEUING DURATION
WHEN
Times
queuing success
Description
This counter counts the total queuing time of a user from entering
the queue to acquiring the resource. When the user enters the
queue, the start queuing time is recorded; when the user exits
the queue and acquires the resource, the total queuing time is
calculated by subtracting the start queuing time from the current
time.
Usage
This counter is used to find out how long it takes a user to queue
in the cell before acquiring the resource.
Measurement
Point
This counter counts the total queuing time of a user in the cell
before acquiring the resource. When the user enters the queue,
the start queuing time is recorded; when the user exits the queue
and acquires the resource, the total queuing time is calculated
by subtracting the start queuing time from the current time. The
2375

QUEUING SUCCEEDS
Unit
OF
QUEUING DURATION
WHEN
Second
queuing success
2376
Description
This counter counts the number of users entering the queue and
acquiring the resource during the assignment or handover process.
The counter increments every time a user exits the queue and
acquires the resource.
Usage
This counter is used to find out how many users successfully acquiring resource after queuing in a cell.
Measurement
Point
This counter counts the number of users acquiring resource after

queuing in a cell. The counter increments every time a user exits
the queue and acquires resource. The measurement point is B2,

QUEUING SUCCEEDS
Unit
OF
QUEUING DURATION
WHEN
Times
2377
2378
Chapter
58
HO Synchronization
Mode Measurement
Table of Contents
Overview...................................................................... 2379
C901520001 Number of synchronous handover executions ............................................................................ 2380
C901520002 Number of synchronous handover successes.......................................................................... 2381
C901520003 Number of pre-synchronous handover executions ............................................................................ 2381
C901520004 Number of pre-synchronous handover successes.......................................................................... 2381
C901520005 Number of pseudo-synchronous handover executions......................................................................... 2382
C901520006 Number of pseudo-synchronous handover successes.......................................................................... 2382
C901520007 Number of asynchronous handover executions ............................................................................ 2383
C901520008 Number of asynchronous handover successes.......................................................................... 2383
Overview
Counters of handover synchronization mode measurement count
in the following two cases: execution of different handover modes
and successes of different handover modes. If the uplink channel
activation is completed, the counter counts the number of handover executions. If the uplink handover (assignment) is completed, the counter counts the number of handover successes. The
measurement point of counting handover executions is A, and the
measurement point of counting handover successes is B.
2379
FIGURE 2368 MEASUREMENT POINT OF BTS SENDING CHANNEL

ACTIVATION COMPLETION MESSAGE TO BSC
FIGURE 2369 MEASUREMENT POINT OF MS SENDING

ASSIGNMENT/HANDOVER COMPLETION MESSAGE TO BSC
synchronous handover
executions
Description
This counter counts the number of synchronous handover executions after the uplink channel activation completion message is
received.
Usage
This counter is used to find out the number of synchronous handover executions in the cell.
Measurement
Point
After BSC receives the channel activation completion message

from BTS, if the handover is synchronous handover, the counter
increments.
Unit
2380
Times
Chapter 58 HO Synchronization Mode Measurement
successes
Description
This counter counts the number of successful synchronous handovers after the uplink handover(assignment) completion message is received.
Usage
This counter is used to find out the number of successful synchronous handovers in the cell.
Measurement
Point
After BSC receives the uplink handover (assignment) completion

message from BTS, if the handover is synchronous handover, the
counter increments.
Unit
Times
pre-synchronous handover
executions
Description
This counter counts the number of pre-synchronous handover executions after the uplink channel activation completion message is
received.
Usage
This counter is used to find out the number of pre-synchronous

handover executions in the cell.
Measurement
Point

from BTS, if the handover is pre-synchronous handover, the
counter increments.
Unit
Times
successes
Description
This counter counts the number of successful pre-synchronous

handovers after the uplink handover(assignment) completion
message is received.
Usage
This counter is used to find out the number of successful pre-synchronous handovers in the cell.
2381
Measurement
Point
Unit

message from BTS, if the handover is pre-synchronous handover,
Times
C901520005 Number
of pseudo-synchronous
handover executions
Description
This counter counts the number of pseudo-synchronous handover

executions after the uplink channel activation completion message
is received.
Usage
This counter is used to find out the number of pseudo-synchronous

handover executions in the cell.
Measurement
Point

from BTS, if the handover is pseudo-synchronous handover, the
counter increments.
Unit
Times
C901520006 Number
of pseudo-synchronous
handover successes
Description
This counter counts the number of successful pseudo-synchronous

handovers after the uplink handover(assignment) completion
message is received.
Usage
This counter is used to find out the number of successful pseudosynchronous handovers in the cell.
Measurement
Point

message from BTS, if the handover is pseudo-synchronous handover, the counter increments.
Unit
2382
Times
Chapter 58 HO Synchronization Mode Measurement
asynchronous handover
executions
Description
This counter counts the number of asynchronous handover executions after the uplink channel activation completion message is
received.
Usage
This counter is used to find out the number of asynchronous handover executions in the cell.
Measurement
Point

from BTS, if the handover is asynchronous handover, the counter
increments.
Unit
Times
successes
Description
This counter counts the number of successful asynchronous handovers after the uplink handover(assignment) completion message is received.
Usage
This counter is used to find out the number of successful asynchronous handovers in the cell.
Measurement
Point

message from BTS, if the handover is asynchronous handover, the
counter increments.
Unit
Times
2383
2384
Chapter
59
Paging Message
Measurement
Table of Contents
Overview...................................................................... 2385
C901530001 Number of paging messages ........................ 2386
C901530002 Number of paging messages from PS of Gb interface ......................................................................... 2387
C901530003 Number of paging messages from CS of Gb interface ......................................................................... 2387
Overview
Counters of paging message measurement count the number of
paging messages from A-interface and the number of PS paging
messages and CS paging messages from Gb interface. Measurement points of paging message measurement counters are A, as
FROM A-INTERFACE
OF
BSC RECEIVING PAGING MESSAGE
2385

MESSAGE FROM GB INTERFACE
OF
BSC RECEIVING PS/CS PAGING
paging messages
Description
This counter counts the number of paging messages received by

BSC from A-interface.
Usage
This counter is used to find out the number of paging messages

received by BSC from A-interface.
Measurement
Point
When BSC receives the paging message from A-interface, the

Figure 2372.
FROM A-INTERFACE
Unit
2386
POINT
OF
BSC RECEIVING PAGING MESSAGE
Times
Chapter 59 Paging Message Measurement
paging messages from PS
of Gb interface
Description
This counter counts the number of PS paging messages received

by BSC from Gb interface.
Usage
When BSC receives the PS paging message from Gb interface, the

Figure 2373.
Measurement
Point
Unit
OF
When BSC receives the PS paging message from Gb interface, the

Figure 2373.
Times
paging messages from CS
of Gb interface
Description
This counter counts the number of CS paging messages received

by BSC from Gb interface.
Usage
When BSC receives the CS paging message from Gb interface, the

Figure 2374.
2387

Measurement
Point
Unit
2388
OF
When BSC receives the CS paging message from Gb interface, the

Figure 2374.
Times
Chapter
60
Reserved Channel
Measurement
Table of Contents
Overview...................................................................... 2389
C901540001 Number of voice allocations of reserved full rate
channel in assignment.................................................... 2389
C901540002 Number of data allocations of reserved full rate
channel in assignment.................................................... 2390
C901540003 Number of voice allocations of reserved full rate
channel in handover ...................................................... 2390
C901540004 Number of data allocations of reserved full rate
channel in handover ...................................................... 2391
C901540005 Reserved seizure duration of reserved full rate
channel ........................................................................ 2391
Overview
Counters of reserved channel measurement describe the occupation condition of reserved channels in the cell. If the channel
resource request to the database succeeds and the acquired resource is reserved channel, then the counter counts.
C901540001 Number
of voice allocations of
reserved full rate channel in
assignment
Description
During the channel assignment process, when the voice channel

resource request to the database succeeds and the acquired resource is reserved channel, the counter counts.
2389
Usage
This counter is used to find out the occupation condition of reserved channels.
Measurement
Point
During the channel assignment process, when the voice channel

resource request to the database succeeds and the acquired resource is reserved channel, the counter increments.
Unit
Times

allocations of reserved full
rate channel in assignment
Description
During the channel assignment process, when the data channel

Usage
Measurement
Point
During the channel assignment process, when the data channel

Unit
Times
voice allocations of reserved
full rate channel in handover
Description
During the channel handover process, when the voice channel

Usage
Measurement
Point
During the channel handover process, when the voice channel

Unit
2390
Times
Chapter 60 Reserved Channel Measurement
data allocations of reserved
full rate channel in handover
Description
During the channel handover process, when the data channel resource request to the database succeeds and the acquired resource is reserved channel, the counter counts.
Usage
Measurement
Point
During the channel handover process, when the data channel resource request to the database succeeds and the acquired resource is reserved channel, the counter increments.
Unit
Times
C901540005 Reserved
seizure duration of reserved
full rate channel
Description
This counter counts the total duration of reserved channels being

occupied in the cell.
Usage
This counter is used to find out the occupation condition of reserved channels in the cell.
Measurement
Point
Unit
BSC performs statistics every 15 minutes.

Second
2391
2392
Chapter
61
SCCP Connection
Measurement
Table of Contents
Overview...................................................................... 2393
C901550001 Number of BSC originated SCCP Connection attempts ......................................................................... 2394
C901550002 Number of BSC originated SCCP Connection success............................................................................. 2395
C901550003 Number of BSC originated SCCP Connection failure due to timeout......................................................... 2396
C901550004 Number of negative replies for SCCP connection
request ........................................................................ 2396
C901550005 Number of MSC originated SCCP Connection Requests ......................................................................... 2397
success ........................................................................ 2398
Overview
Counters of SCCP connection measurement count the following
information: the number of SCCP link establishment requests initiated by BSC, the number of successful SCCP link establishments
initiated by BSC, the number of link establishment failure due to
timeout, the number of link esablishment being rejected, the number of SCCP link establishment requests initiated by MSC, and the
number of successful SCCP link establishments initiated by MSC.
Statistic unit in this measurement is office.
2393
BSC originated SCCP
Connection attempts
Description
This counter counts the number of SCCP link establishment requests initiated by BSC towards MSC, that is, the number of BSC's
sending the ConnectRequest message to MSC.
Usage
This counter is used to find out the number of BSC's sending the
SCCP link establishment requests to MSC.
Measurement
Point
When BSC sends the Connect Req message to MSC, the counter
SCCP CONNECTION ATTEMPTS
Unit
2394
OF
NUMBER
Times
OF
BSC
ORIGINATED
Chapter 61 SCCP Connection Measurement
BSC originated SCCP
Connection success
Description
This counter counts the number of successful SCCP link establishments initiated by BSC towards MSC.
Usage
This counter is used to find out the number of successful SCCP link
establishments initiated by BSC towards MSC.
Measurement
Point
When BSC receives the SCCP connection confirmation message

from MSC, the counter increments. The measurement point is A,
SCCP CONNECTION ATTEMPTS
Unit
OF
NUMBER
OF
BSC
ORIGINATED
Times
2395
BSC originated SCCP
Connection failure due to
timeout
Description
This counter counts the number of SCCP link establishment failures

due to timeout, and the SCCP link establishment is initiated by BSC
towards MSC.
Usage
This counter is used to find out the number of SCCP link establishment failures due to timeout, and the SCCP link establishment is
initiated by BSC towards MSC.
Measurement
Point
Unit
When the timer T9105 expires, the counter increments.

Times
negative replies for SCCP
connection request
2396
Description
This counter counts the number of SCCP link establishment requests being rejected, and the SCCP link establishment is initiated
by BSC towards MSC.
Usage
This counter is used to find out the number of SCCP link establishment requests being rejected, and the SCCP link establishment is
initiated by BSC towards MSC.
Measurement
Point
When the Rana process receives the DISCONNECT IND message

from the ADispatch process, the counter increments. The measurement point is A, as shown in Figure 2377.

SCCP CONNECTION REQUEST
Unit
OF
NUMBER
OF NEGATIVE REPLIES FOR
Times
MSC originated SCCP
Connection Requests
Description
This counter counts the number of SCCP link establishment requests initiated by MSC.
Usage
This counter is used to find out the number of SCCP link establishment requests initiated by MSC.
Measurement
Point
When BSC receives the Connect Indication message from MSC,

Figure 2378.
2397

SCCP CONNECTION REQUESTS
Unit
OF
NUMBER
OF
MSC
ORIGINATED
Times
MSC originated SCCP
Connection success
2398
Description
This counter counts the number of successful SCCP link establishments initiated by MSC.
Usage
This counter is used to find out the number of successful SCCP link
establishments initiated by MSC.
Measurement
Point
When BSC sends the Connect Response message to MSC, the

Figure 2379.

SCCP CONNECTION SUCCESS
Unit
OF
NUMBER
OF
MSC
ORIGINATED
Times
2399
2400
Chapter
62
DTM Cell Measurement

Table of Contents
Overview...................................................................... 2402
C901560001 Number of voice access in mobile with DTM ability ............................................................................... 2402
C901560002 Number of packet access in mobile with DTM
ability .......................................................................... 2403
C901560003 Number of received IMSI when link establish .............................................................................. 2403
C901560004 Number of RANCS module received IMSI when
handover...................................................................... 2404
C901560005 Number of mobile sent GTTP message under
DTM mode .................................................................... 2404
C901560006 Number of BSC successfully sent GTTP message
under DTM mode ........................................................... 2404
C901560007 Number of DTM attempts in mobile ............... 2405
C901560008 Number of DTM uplink attempt failure ........... 2405
C901560009 Number of UL DTM database resource assignment success in dedicated mode .................................... 2406
C901560010 Number of UL DTM database resource assignment failure in dedicated mode ...................................... 2406
C901560011 Number of handover(intra-cell) attempts due to
UL DTM ........................................................................ 2407
C901560012 Number of handover(intra-cell) success due to
uplink DTM ................................................................... 2407
C901560013 Number of handover(intra-cell) failure due to
uplink DTM ................................................................... 2408
C901560014 Number of DTM failure due to handover ......... 2408
C901560015 Number of UL DTM link establishment success............................................................................. 2408
C901560016 Attempt number of sending LLC packet on
FACCH in dedicated mode .............................................. 2409
C901560017 Number of successfully sent LLC packet on
FACCH in dedicated mode .............................................. 2409
C901560018 Attempt Number of DTM established due to
SGSN sent LLC packets .................................................. 2410
C901560019 Number of DTM attempts failure ................... 2410
C901560020 Number of DL DTM resource assignment success............................................................................. 2411
C901560021 Number of DL DTM resource assignment failure .............................................................................. 2411
C901560022 Number of handover(intra-cell) attempts due to
DL DTM ........................................................................ 2412
C901560023 Number of successfully handover occurs due to
DL DTM ........................................................................ 2412
C901560024 Number of handover failure occurs due to DL
DTM ............................................................................ 2413
2401
C901560025 Number of DL DTM failure occurs due to handover........................................................................... 2413

C901560026 Number of successfully DL DTM establishment ........................................................................... 2414
Overview
DTM cell measurement studies the DTM service condition of mobile phones that have DTM capability, including resource request
for DTM service, intra-cell handover due to DTM service, and DTM
service establishment. The measurement unit is cell.
voice access in mobile with
DTM ability
Description
This counter counts the number of accessing voice service by mobile phone that has the DTM capability in the cell within the measurement period.
Usage
This counter is used to find out the number of accessing voice

service by mobile phone that has the DTM capability in the cell.
Measurement
Point

1. When BSC receives the Classmark Change message from MS, if
Classmark3 carries the information that the MS has DTM multitimeslot capability, the counter increments.
2. When BSC receives the Classmark Update message from MSC,
if Classmark3 carries the information that the MS has DTM
multi-timeslot capability, the counter increments.
3. During inter-cell handover or external handover, when the destination cell receives the Radio Apply message, if Classmark3
carries the information that the MS has DTM multi-timeslot capability, the counter increments.
Unit
Related Features
2402
Times
Chapter 62 DTM Cell Measurement
packet access in mobile with
DTM ability
Description
This counter counts the number of accessing packet service by

mobile phone that has the DTM capability in the cell within the
measurement period.
Usage
This counter is used to find out the number of accessing packet

service by mobile phone that has the DTM capability in the cell.
Measurement
Point

1. During uplink two-step access, when BSC receives the resource
request which indicates that MS has DTM multi-timeslot capability, the counter increments.
2. During downlink access, when BSC receives the downlink assignment request which indicates that MS has DTM
multi-timeslot capability, the counter increments.
Unit
Related Features
Times
received IMSI when link
establish
Description
This counter counts the number of IMSIs received during link establishment in the cell within the measurement period.
Usage
This counter is used to find out the number of IMSIs received during link establishment in the cell.
Measurement
Point
When BSC receives the COMMON ID message from MSC, if no IMSI

information is saved originally, then the IMSI information carried
in the COMMON ID message is saved, and the counter increments.
Unit
Related Features
Times
2403
RANCS module received
IMSI when handover
Description
This counter counts the number of IMSIs received by the RANCS

module during intra-cell handover within the measurement period.
Usage
This counter is used to find out the number of IMSIs received by

the RANCS module during intra-cell handover.
Measurement
Point
During inter-cell handover or external handover, when the destination cell receives the Radio Apply message which carries the
IMSI information, the counter increments.
Unit
Related Features
Times
mobile sent GTTP message
under DTM mode
Description
This counter counts the number of GTTP messages sent by MS in

dedicated mode in the cell within the measurement period.
Usage
This counter is used to find out the number of GTTP messages sent
by MS in dedicated mode in the cell.
Measurement
Point
During BSC's voice service process, the counter increments when

the GTTP message (GPRS information) is received from MS.
Unit
Related Features
Times
BSC successfully sent GTTP
message under DTM mode
2404
Description
This counter counts the number of GTTP messages successfully

sent by BSC in dedicated mode in the cell within the measurement
period.
Usage
This counter is used to find out the number of GTTP messages

successfully sent by BSC in dedicated mode in the cell.
Measurement
Point
Unit
Related Features
During BSC's voice service process, when the GTTP message is received from MS and then is successfully sent to SGSN, the counter
increments.
Times
DTM attempts in mobile
Description
This counter counts the number of attempts of uplink DTM service

initiated by MS in dedicated mode in the cell within the measurement period.
Usage
This counter is used to find out the number of attempts of uplink

DTM service initiated by MS in dedicated mode in the cell.
Measurement
Point
During BSC's voice service process, the counter increments when

the DTM request message is received from MS.
Unit
Related Features
Times
DTM uplink attempt failure
Description
This counter counts the number of failed attempts of uplink DTM

service in the cell within the measurement period.
Usage
This counter is used to find out the number of failed attempts of

uplink DTM service in the cell.
Measurement
Point
1. When BSC receives the DTM request from MS but does not
process due to MS not on SDCCH, the counter increments.
process because there is no Classmark3 information of the MS,
3. When BSC receives the DTM request from MS but finds out that
the cell where MS is located does not support DTM service, the
counter increments.
process due to the DTM request being repeated, the counter
increments.
Unit
Related Features
Times
2405
DTM database resource
assignment success in
dedicated mode
Description
This counter counts the number of uplink DTM service requesting

for database resource successfully in dedicated mode in the cell
Usage
This counter is used to find out the number of uplink DTM service
requesting for database resource successfully in dedicated mode
in the cell.
Measurement
Point
During BSC's voice service process, when the DTM request is

received from MS and the resource is acquired successfully, the
counter increments.
Unit
Related Features
Times
C901560010 Number
of UL DTM database
resource assignment failure
in dedicated mode
Description
This counter counts the number of failed uplink DTM service requesting for database resource in dedicated mode in the cell within
Usage
This counter is used to find out the number of failed uplink DTM
service requesting for database resource in dedicated mode in the
cell.
Measurement
Point
During BSC's voice service process, when the DTM request is received from MS and the resource request fails, the counter increments.
Unit
Related Features
2406
Times
handover(intra-cell) attempts
due to UL DTM
Description
This counter counts the number of attempts of intra-cell handover

due to uplink DTM service in dedicated mode in the cell within the
measurement period.
Usage
This counter is used to find out the number of attempts of intra-cell

handover due to uplink DTM service in dedicated mode in the cell.
Measurement
Point
During BSC's voice service process, when the DTM request is received from MS, the voice channel is reallocated for the resource
request, if intra-cell handover is required and the DTM resource
assignment is in uplink, the counter increments.
Unit
Related Features
Times
handover(intra-cell) success
due to uplink DTM
Description

due to uplink DTM service in dedicated mode in the cell within the
measurement period.
Usage
This counter is used to find out the number of successful intra-cell

handovers due to uplink DTM service in dedicated mode in the cell.
Measurement
Point
After the intra-cell handover is completed, if BSC judges that the

MS is implementing DTM service, the counter increments.
Unit
Related Features
Times
2407
handover(intra-cell) failure
due to uplink DTM
Description
This counter counts the number of failed intra-cell handovers due

to uplink DTM service in dedicated mode in the cell within the measurement period.
Usage
This counter is used to find out the number of failed intra-cell handovers due to uplink DTM service in dedicated mode in the cell.
Measurement
Point
During intra-cell handover, when the handover fails due to BSC

assignment failure or T3107 timeout, if BSC judges that the MS is
implementing DTM service, the counter increments.
Unit
Related Features
Times
DTM failure due to handover
Description
This counter counts the number of failed uplink DTM service due
to handover in dedicated mode in the cell within the measurement
period.
Usage
This counter is used to find out the number of failed uplink DTM
service due to handover in dedicated mode in the cell within the
measurement period.
Measurement
Point
During BSC's voice service process, when the DTM request is received and the DTM service fails due to MS being in the handover
status, the counter increments.
Unit
Related Features
Times
UL DTM link establishment
success
Description
2408
This counter counts the number of successful uplink DTM service

establishments in dedicated mode in the cell within the measurement period.
Usage
This counter is used to find out the number of successful uplink

DTM service establishments in dedicated mode in the cell.
Measurement
Point
During the uplink establishment process, the ranps module on CMP

inside BSC receives the establishment indication message from the
MAC module on UPPB, if it is judged that MS is implementing DTM
service, the counter increments.
Unit
Related Features
Times
C901560016 Attempt
number of sending LLC
packet on FACCH in
dedicated mode
Description
This counter counts the number of attempts of sending LLC frame

on FACCH in dedicated mode in the cell within the measurement
period.
Usage
This counter is used to find out the number of attempts of sending

LLC frame on FACCH in dedicated mode in the cell.
Measurement
Point
During BSC's voice service process, when the downlink LLC data
frame is received in GTTP mode, the counter increments.
Unit
Related Features
Times
successfully sent LLC
packet on FACCH in
dedicated mode
Description
This counter counts the number of successfully sending LLC frame

on FACCH in dedicated mode in the cell within the measurement
period.
Usage
This counter is used to find out the number of successfully sending

LLC frame on FACCH in dedicated mode in the cell.
Measurement
Point
During BSC's voice service process, when the LLC frame is sent on
FACCH in GTTP mode, the counter increments.
Unit
Times
2409
Related Features
C901560018 Attempt
Number of DTM established
due to SGSN sent LLC
packets
Description
This counter counts the number of attempts of SGSN's sending LLC

frame to trigger DTM service establishment in dedicated mode in
the cell within the measurement period.
Usage
This counter is used to find out the number of attempts of SGSN's

sending LLC frame to trigger DTM service establishment in dedicated mode in the cell within the measurement period.
Measurement
Point
During BSC's voice service process, when DTM service is intiated

due to receiving LLC data frame sent by SGSN, the counter increments.
Unit
Related Features
Times
DTM attempts failure
Description
This counter counts the number of failed attempts of downlink DTM

service in the cell within the measurement period.
Usage
This counter is used to find out the number of failed attempts of

downlink DTM service in the cell.
Measurement
Point
During BSC's voice service process, when DTM service is initiated

due to receiving LLC data frame sent by SGSN, if the system judges
that the rancs module on CMP is not in stable service status, then
the following messages are not processed: DTM assignment message, PS assignment message, and LLC frame sending message.
In this case, the counter increments.
Unit
Related Features
2410
Times
DTM resource assignment
success
Description
This counter counts the number of downlink DTM service requesting for database resource successfully in dedicated mode in the
cell within the measurement period.
Usage
This counter is used to find out the number of downlink DTM service
requesting for database resource successfully in dedicated mode
in the cell.
Measurement
Point

due to receiving LLC data frame sent by SGSN and the resource is
acquired successfully, the counter increments.
Unit
Related Features
Times
DTM resource assignment
failure
Description
This counter counts the number of failed downlink DTM service

requesting for database resource in dedicated mode in the cell
Usage
This counter is used to find out the number of failed downlink DTM
service requesting for database resource in dedicated mode in the
cell.
Measurement
Point

due to receiving LLC data frame sent by SGSN and the resource
request fails, the counter increments.
Unit
Related Features
Times
2411
handover(intra-cell) attempts
due to DL DTM
Description
This counter counts the number of attempts of intra-cell handover

due to downlink DTM service in dedicated mode in the cell within
Usage
This counter is used to find out the number of attempts of intra-cell

handover due to downlink DTM service in dedicated mode in the
cell.
Measurement
Point
During BSC's voice service process, when the DTM request is received from MS, the voice channel is reallocated for the resource
request, if intra-cell handover is required and the DTM resource
assignment is in downlink, the counter increments.
Unit
Related Features
Times
successfully handover
occurs due to DL DTM
Description

due to downlink DTM service in dedicated mode in the cell within
Usage
This counter is used to find out the number of successful intra-cell

handovers due to downlink DTM service in dedicated mode in the
cell.
Measurement
Point
After the intra-cell handover is completed, if BSC judges that the

MS is implementing DTM service and the DTM resource assignment
is in downlink, the counter increments.
Unit
Related Features
2412
Times
handover failure occurs due
to DL DTM
Description
This counter counts the number of failed intra-cell handovers due

to downlink DTM service in dedicated mode in the cell within the
measurement period.
Usage
This counter is used to find out the number of failed intra-cell handovers due to downlink DTM service in dedicated mode in the cell.
Measurement
Point
During intra-cell handover, when the handover fails due to BSC

assignment failure or T3107 timeout, if BSC judges that the MS is
implementing DTM service and the DTM resource assignment is in
downlink, the counter increments.
Unit
Related Features
Times
DTM failure occurs due to
handover
Description
This counter counts the number of failed downlink DTM service due
to handover in dedicated mode in the cell within the measurement
period.
Usage
This counter is used to find out the number of failed downlink DTM
service due to handover in dedicated mode in the cell within the
measurement period.
Measurement
Point
During BSC's voice service process, when the DTM request is received, if DTM service fails due to MS being in the handover status
and if DTM service is in downlink, the counter increments.
Unit
Related Features
Times
2413
C901560026 Number
of successfully DL DTM
establishment
Description
This counter counts the number of successful downlink DTM service establishments in dedicated mode in the cell within the measurement period.
Usage
This counter is used to find out the number of successful downlink

DTM service establishments in dedicated mode in the cell.
Measurement
Point
During downlink DTM service process, when the RANPS module

on CMP inside BSC receives the instance establishment indication
message from the MAC module on UPPB, the counter increments.
Unit
Related Features
2414
Times
Chapter
63
LAPD Measurement
Table of Contents
Overview...................................................................... 2416
C901570001 Number of Application Data Package from
CMP............................................................................. 2416
C901570002 Number of BTS Application Data Package Sent
to MP ........................................................................... 2416
C901570003 Number of Data Package Ack Sent to Application ............................................................................. 2417
C901570004 Number of Application Data Package Ack from
BTS ............................................................................. 2417
C901570005 Number of Application Nack Data Package sent
to BTS ......................................................................... 2417
C901570006 Number of BTS Application Nack Data Package
Receive by BTS ............................................................. 2418
C901570007 Number of Sending Frame............................ 2418
C901570008 Number of Received Frame .......................... 2418
C901570009 Number of High Priority Queue overflow......... 2419
C901570010 Number of Low Priority Queue overflow ......... 2419
C901570011 Number of Success in High Priority
Queue.......................................................................... 2419
C901570012 Number of Success in Low Priority Queue......... 2420
C901570013 Number of in Queue Request UB Fail ............. 2420
C901570014 Resend Number .......................................... 2420
C901570015 Resend Request Number .............................. 2421
C901570016 Establish Link Number ................................. 2422
C901570017 Broken Number .......................................... 2422
C901570018 Protocol Error Number ................................. 2423
C901570019 Number of T200 Overtime............................ 2423
C901570023 Number of abnormal hop frame .................... 2425
C901570024 Number of normal hop frame........................ 2425
C901570025 Multi Channel Link Lose Frame...................... 2425
C901570026 No useful channel ....................................... 2426
C901570027 Max Up Flow .............................................. 2426
C901570028 Max Down Flow .......................................... 2426
C901570029 Current Up Flow.......................................... 2427
C901570030 Current Down Flow ..................................... 2427
2415
Overview
LAPD measurement counters reflect the message transceiving
condition at Abis interface between BSC and BTS. The measurement takes each LAPD link (channel cluster) as the statistics unit.
It measures the transmitted data volume on LAPD link and message transceiving condition on the link, and records exceptions in
LAPD protocol processing.
Application Data Package
from CMP
Description
This counter counts the number of downlink data messages received from CMP on LAPD link.
Usage
This counter is used to find out the number of service and O&M
messages received from CMP on LAPD link.
Measurement
Point
The counter counts when SPB receives the EV_DLDATA_REQ message from CMP.
C901570002 Number of BTS

Sent to MP
2416
Description
This counter counts the number of uplink data messages sent to

CMP on LAPD link.
Usage
This counter is used to find out the number of service and O&M
messages sent to CMP on LAPD link.
Measurement
Point
The counter counts when CMP receives the EV_DLDATA_IND message from SPB.
Chapter 63 LAPD Measurement
Data Package Ack Sent to
Application
Description
This counter counts the number of downlink I frames sent to BTS

on LAPD link.
Usage
This counter is used to find out the number of LAPD information

frames sent to BTS on LAPD link.
Measurement
Point
The counter counts when BTS receives the I frame from SPB.
Ack from BTS
Description
This counter counts the number of uplink I frames received from

BTS on LAPD link.
Usage
This counter is used to find out the number of LAPD information

frames received from BTS on LAPD link.
Measurement
Point
The counter counts when SPB receives the I frame from BTS.
Application Nack Data
Package sent to BTS
Description
This counter counts the number of downlink UI frames sent to BTS

on LAPD link.
Usage
This counter is used to find out the number of LAPD unnumbered

2417
Measurement
Point
The counter counts when BTS receives the UI frame from SPB.
BTS Application Nack Data
Package Receive by BTS
Description
This counter counts the number of uplink UI frames received from

BTS on LAPD link.
Usage
This counter is used to find out the number of LAPD unnumbered

Measurement
Point
The counter counts when SPB receives the UI frame from BTS.
Sending Frame
Description
This counter counts the total number of message frames sent to

BTS on LAPD link, including all LAPD protocol frame types.
Usage
This counter is used to find out the total number of LAPD message
Measurement
Point
The counter counts when BTS receives the LAPD message from
SPB.
Received Frame
2418
Description
This counter counts the total number of message frames received

from BTS on LAPD link, including all LAPD protocol frame types.
Usage
This counter is used to find out the total number of LAPD message
Measurement
Point
The counter counts when SPB receives the LAPD message from
BTS.
High Priority Queue overflow
Description
This counter counts the number of overflows of high-priority LAPD

message entering the queue.
Each LAPD link has a high-priority message-sending queue, which
saves high-priority messages to be sent. If there are too many
messages to be sent, the queue is full, causing that subsequent
messages to be sent are discarded. This counter counts the number of discarded messages due to the queue being full.
Usage
This counter is used to find out exceptions in receiving high-priority

LAPD messages from CMP on LAPD link.
Measurement
Point
The counter counts when a message is discarded due to the highpriority LAPD message queue being full.
C901570010 Number of Low

Priority Queue overflow
Description
This counter counts the number of overflows of low-priority LAPD

message entering the queue.
Each LAPD link has a low-priority message-sending queue, which
saves low-priority messages to be sent. If there are too many
messages to be sent, the queue is full, causing that subsequent
messages to be sent are discarded. This counter counts the number of discarded messages due to the queue being full.
Usage
This counter is used to find out exceptions in receiving low-priority

LAPD messages from CMP on LAPD link.
Measurement
Point
The counter counts when a message is discarded due to the lowpriority LAPD message queue being full.
Success in High Priority
Queue
Description
This counter counts the number of high-priority LAPD message

entering the queue successfully.
Usage
This counter is used to find out the number of successfully receiving high-priority LAPD messages from CMP on LAPD link.
2419
Measurement
Point
The counter counts when SPB receives the high-priority message

from CMP.
Success in Low Priority
Queue
Description
This counter counts the number of low-priority LAPD message entering the queue successfully.
Usage
This counter is used to find out the number of successfully receiving low-priority LAPD messages from CMP on LAPD link.
Measurement
Point
The counter counts when SPB receives the low-priority message

from CMP.
C901570013 Number of in
Queue Request UB Fail
Description
This counter counts the number of failed UB requests when receiving the high/low-priority message on LAPD link.
Usage
This counter is used to find out memory request failure when receiving the high/low-priority LAPD message from CMP on LAPD
link.
Measurement
Point
The counter counts when UB request fails during the process of

receiving the high/low-priority message on LAPD link.
C901570014 Resend
Number
2420
Description
This counter counts the number of resending I frame on LAPD link

due to T200 timeout.
Usage
In the case that LAPD link does not receive unacknowledgement

from the opposite end, this counter is used to find out the number
of resending frame and waiting for the acknowledgement frame.
Measurement
Point
The counter counts when I frame is resent on LAPD link due to

T200 timeout. The measurement point is A, as shown in Figure
2380.

LINK DUE TO T200 TIMEOUT
OF
RESENDING I FRAME
ON
LAPD
C901570015 Resend
Request Number
Description
This counter counts the number of resending frame on LAPD link

according to the opposite end's response.
In acknowledgement transmission mode, if the opposite end returns the unacknowledgement frame after a data frame is sent,
it indicates that the data frame is not correctly received. In this
case, the I frame requested by the opposite end is resent on LAPD
link to the opposite end.
Usage
Measurement
Point
This counter is used to find out the number of resending frame on

LAPD link due to receiving the unacknowledgement frame returned
from the opposite end.
2421

UPON REQUEST
POINT
OF
NUMBER
OF
RESENDING FRAME
C901570016 Establish Link

Number
Description
This counter counts the number of LAPD link establishments.

Before transmitting data on LAPD link, it is necessary to establish
the transmission link through negotiation. Refer to LAPD protocol
specification for the link establishment.
Usage
This counter is used to find out the number of LAPD link establishments.
Measurement
Point
LAPD link establishment negotiation is completed, and the system

enters multi-frame establishment status.
C901570017 Broken
Number
Description
Usage
Measurement
Point
2422
This counter counts the number of LAPD link breaks.

This counter is used to find out the number of LAPD link breaks.
The LAPD link is released, and the system enters the status of
waiting for link establishment.
C901570018 Protocol Error

Number
Description
Usage
Measurement
Point
When protocol error occurs on LAPD link, the multi-frame link protocol reports the protocol error to the layer management entity.
This counter counts the number of protocol error messages received by the layer management entity.
This counter is used to find out protocol errors on LAPD link.
OF
NUMBER
OF
PROTOCOL ERRORS
T200 Overtime
Description
T200 defines the time limit for the opposite end's acknowledging
the information frame. This counter counts the number of T200
timeout on LAPD link.
Usage
This counter is used to find out the number of T200 timeout on

LAPD link. It studies whether the opposite end acknowledges the
information frame. If T200 is timeout, it indicates that the opposite
end does not acknowledge the information frame in time.
Measurement
Point
The counter counts when the LAPD process receives the T200 timeout message.
2423
T201 Overtime
Description
T201 defines the time limit of response for LAPD identification authentication. This counter counts the number of T201 timeout on
LAPD link.
Usage
his counter is used to find out the number of T201 timeout on LAPD
link. It studies whether the LAPD identification authentication request is acknowledged.
Measurement
Point
T203 Overtime
Description
T203 defines the maximum time allowed for no frame interaction.

This counter counts the number of T203 timeout on LAPD link.
Usage

LAPD link. It studies whether there is no frame interaction on
LAPD link, if the counter's value is large, it indicates that the LAPD
link is idle.
Measurement
Point
T204 Overtime
2424
Description
T204 defines the time limit of sending unacknowledgement due to

hop frame in the slide window. This counter counts the number of
T204 timeout on LAPD link.
Usage

LAPD link. It studies the transmission delay difference between
channels in the LAPD channel cluster. The larger the counter's
value is, the more unacknowledgements there are sent to the opposite end due to hop frame in the slide window, indicating that the
transmission delay difference between different channels is large.
Measurement
Point
abnormal hop frame
Description
This counter counts the number of I frames outside of the slide

window received by the slide window of LAPD link during the message receiving process.
Usage
This counter is used to observe abnormal hop frames on LAPD link.

It reflects the LAPD transmission quality, if the counter's value is
large, it indicates that the link quality is poor.
Measurement
Point
When an I frame outside of the slide window is received by the

slide window of LAPD link during the message receiving process,
normal hop frame
Description
This counter counts the number of unexpected frames in the slide

window received by the slide window of LAPD link during the message receiving process.
Usage
This counter is used to observe the case that a frame sent later is
received earlier on LAPD link due to different channel and different
path.
Measurement
Point
When an unexpected frames in the slide window is received by the

slide window of LAPD link during the message receiving process,
C901570025 Multi Channel

Link Lose Frame
Description
During the message receiving process of slide window of LAPD

link, if the last frame number received on each channel exceeds
the expected frame number, it indicates that frame loss occurs at
multiple channels.
This counter counts the number of frame numbers received on all
channels exceeding the expected frame number.
Usage
This counter is used to observe the frame loss condition on LAPD

link. If the counter's value is large, it indicates that there are many
frames lost on the link.
Measurement
Point
During the message receiving process of slide window of LAPD

link, the counter counts when the frame numbers received on all
channels exceed the expected frame number.
2425
C901570026 No useful
channel
Description
When the message is tranmitted on LAPD link, if all channels of the

channel cluster are blocked, then there are no available channels
to transmit the LAPD frame.
This counter counts the number of message transmission failure
due to no available channel.
Usage
This counter is used to observe the case that all channels of the
channel cluster of LAPD link are blocked. If the counter's value is
large, it indicates that the transmission quality is poor.
Measurement
Point
The counter counts when message transmission on LAPD link fails

due to no available channel.
C901570027 Max Up Flow

Description
This counter counts the maximum flow of uplink messages on LAPD

link. The uplink flow on LAPD link is counted every 5 minutes, and
the maximum flow is recorded.
Usage
This counter is used to find out the maximum flow of LAPD frames
received from BTS on LAPD link within the meaurement period.
Such frames include all types of frames in the LAPD protocol.
Measurement
Point
The uplink flow on LAPD link is counted every 5 minutes, and the
maximum flow is recorded.
C901570028 Max Down

Flow
2426
Description
This counter counts the maximum flow of downlink messages on

LAPD link. The downlink flow on LAPD link is counted every 5
minutes, and the maximum flow is recorded.
Usage
This counter is used to find out the maximum flow of LAPD frames
sent to BTS on LAPD link within the meaurement period. Such
frames include all types of frames in the LAPD protocol.
Measurement
Point
The downlink flow on LAPD link is counted every 5 minutes, and

the maximum flow is recorded.
C901570029 Current Up
Flow
Description
This counter counts the current flow of uplink messages on LAPD

link. The uplink flow on LAPD link is counted every 5 minutes.
Usage
This counter is used to find out the current flow of LAPD frames received from BTS on LAPD link during the performance measuremnt
report process. Such frames include all types of frames in the LAPD
protocol.
Measurement
Point
The current flow of uplink messages on LAPD link is recorded every

5 minutes.
C901570030 Current Down

Flow
Description
This counter counts the current flow of downlink messages on

LAPD link. The downlink flow on LAPD link is counted every 5
minutes.
Usage
This counter is used to find out the current flow of LAPD frames
sent to BTS on LAPD link during the performance measuremnt report process. Such frames include all types of frames in the LAPD
protocol.
Measurement
Point
The current flow of downlink messages on LAPD link is recorded

every 5 minutes.
2427
2428
Chapter
64
LCS Measurement
Table of Contents
Overview...................................................................... 2430
CS............................................................................... 2430
C901580002 Number of receiving location abort in CS......... 2431
C901580003 Number of TA Request in CS......................... 2431
C901580004 Number of TA Response in CS....................... 2432
C901580005 Number of MS Position Command in CS ......... 2433
C901580006 Number of MS Position Response in CS .......... 2433
C901580007 Number of location success in CS .................. 2434
C901580008 Number of location failure due to abnormal status of Lb interface in CS ................................................. 2435
expiration in CS............................................................. 2435
C901580010 Number of sending BSSLAP RESET message due
to Intra-BSS handover in CS ........................................... 2436
C901580011 Number of location failure due to Intra-BSS handover expiration in CS .................................................... 2437
C901580012 Number of location failure due to location Timer
expiration in CS............................................................. 2438
C901580013 Number of location failure due to Inter-BSS handover in CS................................................................... 2439
C901580014 Number of location failure due to call drop in
CS............................................................................... 2439
C901580015 Number of location failure due to other BSC's
cause in CS .................................................................. 2440
PS ............................................................................... 2440
C901580017 Number of receiving location abort in PS......... 2441
C901580018 Number of TA Request in PS ......................... 2442
C901580019 Number of TA Response in PS ....................... 2443
C901580020 Number of MS Position Command in PS.......... 2443
C901580021 Number of MS Position Response in PS .......... 2444
C901580022 Number of location success in PS .................. 2445
C901580023 Number of location failure due to abnormal status of Lb interface in PS ................................................. 2445
expiration in PS ............................................................. 2446
C901580025 Number of location failure due to Inter-CMP cell
reselection in PS............................................................ 2447
C901580026 Number of sending LOCATION INFORMATION
message to SMLC due to Intra-CMP cell reselection in
PS ............................................................................... 2448
C901580027 Number of location failure due to location Timer
expiration in PS ............................................................. 2448
C901580028 Number of location failure due to other BSC's
cause in PS................................................................... 2449
2429
Overview
LCS measurement involves counters used for evaluating performance and status of location services, such as the number of location requests in CS domain and the number of location requests
in PS domain.
receiving location request in
CS
Description
This counter counts the number of location requests received by

CS domain from the core network.
Measurement
Point
The counter counts when CS domain receives the location request

from the core network. The measurement point is A, as shown in
Figure 2383.
REQUEST IN CS
Unit
Related Features
2430
OF
NUMBER
Times
ZGO-01-03-002 LCS with CGI+TA
ZGO-01-03-003 LCS with AGPS
OF RECEIVING LOCATION
Chapter 64 LCS Measurement
receiving location abort in
CS
Description
This counter counts the number of location terminations received

by CS domain from the core network.
Measurement
Point
The counter counts when CS domain receives the location termination from the core network. The measurement point is A, as
TERMINATIONS RECEIVED IN CS DOMAIN
Unit
Related Features
OF
LOCATION
Times
C901580003 Number of TA
Request in CS
Description
When SMLC receives the location request from iBSC, if the location
request does not contain TA value, SMLC will send the TA request
to iBSC. After iBSC receives the message, the number of TA requests is counted.
Measurement
Point
The counter counts the number of TA requests when iBSC receives

the location request from SMLC. The measurement point is A, as
2431
Unit
Related Features
OF
NUMBER
OF
TA REQUEST
IN
CS
Times
Response in CS
Description
After iBSC receives the TA request correctly from SMLC, iBSC sends
the TA response message to SMLC. In this case, the counter counts
the number of TA responses.
Measurement
Point
The counter counts when iBSC sends TA response to SMLC after

receiving TA request correctly from SMLC. The measurement point
CS DOMAIN
Unit
Related Features
2432
OF
NUMBER
Times
OF
TA RESPONSES
IN
C901580005 Number of MS
Position Command in CS
Description
iBSC receives the MS position command from SMLC, then the

counter counts the number of MS location requests in CS domain.
Measurement
Point
The counter counts when the MS position command in CS domain

is received. The measurement point is A, as shown in Figure 2387.
COMMANDS IN CS DOMAIN
Unit
Related Features
OF
NUMBER
OF
MS POSITION
Times
Position Response in CS
Description
iBSC sends the position request to MS. After the position response
from MS is received, the counter counts the number of position
responses from MS.
Measurement
Point
The counter counts when iBSC receives the position response from
MS. The measurement point is A, as shown in Figure 2388.
2433

RESPONSE IN CS DOMAIN
Unit
Related Features
OF
NUMBER
OF
MS POSITION
Times
location success in CS
Description
This counter counts the number of location successes in CS domain.
Measurement
Point
The counter counts when iBSC receives the position result from
SMLC. The measurement point is A, as shown in Figure 2389.
IN CS DOMAIN
Unit
Related Features
2434
POINT
OF
NUMBER
Times
OF
LOCATION SUCCESSES
location failure due to
abnormal status of Lb
interface in CS
Description
When the location request from the core network is received, if the
Lb interface link from iBSC to SMLC is broken, the location will fail.
In this case, the counter counts the number of location failures.
Measurement
Point
When the location request from the core network is received, if

the Lb interface link is broken, the counter counts the number of
location failures in CS domain due to abnormal Lb interface status.
FIGURE 2390 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURE DUE
TO ABNORMAL STATUS OF LB INTERFACE IN CS
Unit
Related Features
Times
location failure due to radio
Timer expiration in CS
Description
After iBSC sends the location command to MS, the radio timer
starts. If no response is received from MS before the timer is
timeout, the counter counts the number of location failures in CS
domain due to radio timer timeout.
Measurement
Point
After iBSC sends the location command to MS, the radio timer
starts. When the timer is timeout, the counter counts the number
2435
of location failures in CS domain due to radio timer timeout. The

TO RADIO TIMER EXPIRATION IN CS
Unit
Related Features
NUMBER
OF LOCATION FAILURE DUE
Times
sending BSSLAP RESET
message due to Intra-BSS
handover in CS
2436
Description
During the MS position process, when intra-BSC handover occurs,

the counter counts the number of location delays.
Measurement
Point
During the MS position process, intra-BSC handover occurs, the

counter counts the number of location delays when the handover
completion message is received from MS. The measurement point

CS DOMAIN DUE TO INTRA-BSC HANDOVER
Unit
Related Features
OF
LOCATION DELAYS
IN
Times
C901580011 Number
of location failure due
to Intra-BSS handover
expiration in CS
Description
When iBSC receives the MS position command from SMLC, if iBSC

is initiating intra-BSC inter-cell handover at the moment, the timer
starts. This counter counts the number of location failures due to
timer timout.
Measurement
Point
The counter counts when the intra-BSC handover timer is timeout

in CS domain. The measurement point is A, as shown in Figure
2393.
FIGURE 2393 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURES
DUE TO INTRA-BSS HANDOVER TIMER TIMEOUT IN CS DOMAIN
Unit
Times
2437
Related Features
location Timer expiration in
CS
Description
When the location request from the core network is received,

the location monitoring timer starts. If the timer is timeout, this
counter counts the number of location failures due to the timer
timout.
Measurement
Point
The counter counts when the location monitoring timer is timeout.

FIGURE 2394 MEASUREMENT POINT OF NUMBER OF LOCATION
TO LOCATION MONITORING TIMER TIMEOUT IN CS DOMAIN
Unit
Related Features
2438
Times
FAILURE
DUE
Inter-BSS handover in CS
Description
When the MS position command is received from SMLC, if the external handover flow is initiated, the location will fail.
Measurement
Point
When the MS position command is received, if the external handover flow is initiated, the counter counts. The measurement point
TO INTER-BSS HANDOVER IN CS DOMAIN
Unit
Related Features
OF
LOCATION FAILURE
DUE
Times
location failure due to call
drop in CS
Description
During the location process, iBSC receives the clear command from
the core network.
Measurement
Point
During the location process, the counter counts when iBSC receives the clear command from the core network. The measurement point is A, as shown in Figure 2396.
2439
FIGURE
DUE TO
Unit
Related Features

CALL DROP IN CS DOMAIN
OF
NUMBER
OF
LOCATION FAILURE
Times
location failure due to other
BSC's cause in CS
Description
Location fails due to other causes inside iBSC, such as message

sending failure between modules, requesting SCCP connection failure, and timer setting failure.
Measurement
Point
The counter counts when the following problems occur: message

Unit
Related Features
Times
receiving location request in
PS
Description
2440
This counter counts the number of location requests received by

PS domain from the core network.
Measurement
Point
The counter counts when PS domain receives the location request

from the core network. The measurement point is A, as shown in
Figure 2397.
IN PS DOMAIN
Unit
Related Features
OF
NUMBER
OF
LOCATION REQUESTS
Times
receiving location abort in
PS
Description
This counter counts the number of location terminations received

by PS domain from the core network.
Measurement
Point
The counter counts when PS domain receives the location termination from the core network. The measurement point is A, as
2441

TERMINATIONS RECEIVED IN PS DOMAIN
Unit
Related Features
OF
LOCATION
Times
Request in PS
Description
When SMLC receives the location request from iBSC, if the location
request does not contain TA value, SMLC will send the TA request
to iBSC. After iBSC receives the message, the number of TA requests is counted.
Measurement
Point
The counter counts the number of TA requests when iBSC receives

the location request from SMLC. The measurement point is A, as
DOMAIN
Unit
Related Features
2442
OF
NUMBER
Times
OF
TA REQUESTS
IN
PS
Response in PS
Description
After iBSC receives the TA request correctly from SMLC, iBSC sends
the TA response message to SMLC. In this case, the counter counts
the number of TA responses.
Measurement
Point
The counter counts when iBSC sends TA response to SMLC after

receiving TA request correctly from SMLC. The measurement point
PS DOMAIN
Unit
Related Features
OF
NUMBER
OF
TA RESPONSES
IN
Times
Position Command in PS
Description
iBSC receives the MS position command from SMLC, then the

counter counts the number of MS location requests in PS domain.
Measurement
Point
The counter counts when BSC receives the MS position command

in PS domain. The measurement point is A, as shown in Figure
2401.
2443

COMMANDS IN PS DOMAIN
Unit
Related Features
OF
NUMBER
OF
MS POSITION
Times
Position Response in PS
Description
iBSC sends the position request to the core network. After the
position response from the core network is received, the counter
counts the number of MS position responses.
Measurement
Point
The counter counts when iBSC receives the position response from
the core network. The measurement point is A, as shown in Figure
2402.
RESPONSE IN PS DOMAIN
Unit
Related Features
2444
OF
NUMBER
Times
OF
MS POSITION
location success in PS
Description
This counter counts the number of location successes in PS domain.
Measurement
Point
The counter counts when iBSC receives the position result from
SMLC. The measurement point is A, as shown in Figure 2403.
IN PS DOMAIN
Unit
Related Features
POINT
OF
NUMBER
OF
LOCATION SUCCESSES
Times
abnormal status of Lb
interface in PS
Description
When the location request from the core network is received, if the
Lb interface link from iBSC to SMLC is broken, the location will fail.
In this case, the counter counts the number of location failures.
Measurement
Point
When the location request from the core network is received, if

the Lb interface link is broken, the counter counts the number of
location failures in PS domain due to abnormal Lb interface status.
2445
FIGURE 2404 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURE DUE

TO ABNORMAL STATUS OF LB INTERFACE IN PS
Unit
Related Features
Times
location failure due to radio
Timer expiration in PS
Description
After iBSC sends the location command to the core network, the
radio timer starts. If no response is received from MS before the
timer is timeout, the counter counts the number of location failures
in PS domain due to radio timer timeout.
Measurement
Point
After iBSC sends the location command to the core network, the
radio timer starts. When the timer is timeout, the counter counts
the number of location failures in PS domain due to radio timer
timeout. The measurement point is A, as shown in Figure 2405.
FIGURE 2405 NUMBER OF LOCATION FAILURES
RADIO TIMER TIMEOUT
Unit
2446
Times
IN
PS
DOMAIN DUE TO
Related Features
Inter-CMP cell reselection in
PS
Description
During the positioning process in PS domain, if inter-module cell

reselection occurs, the FLUSH LL message is received from the
core network, then the location fails.
Measurement
Point
During the positioning process in PS domain, if inter-module cell

reselection occurs, the counter counts when the FLUSH LL message is received from the core network. The measurement point
FIGURE 2406 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURE
TO INTER-MODULE CELL RESELECTION IN PS DOMAIN
Unit
Related Features
DUE
Times
2447
C901580026 Number
of sending LOCATION
INFORMATION message to
SMLC due to Intra-CMP cell
reselection in PS
Description
During the positioning process in PS domain, if intra-module cell

reselection occurs, then the counter counts when the FLUSH LL
message is received from the core network.
Measurement
Point
During the positioning process in PS domain, if intra-module cell

reselection occurs, the counter counts when the FLUSH LL message is received from the core network. The measurement point
FIGURE 2407 MEASUREMENT POINT OF NUMBER OF SENDING LOCATION
INFORMATION MESSAGES TO LCS DUE TO INTRA-MODULE CELL RESELECTION
IN PS DOMAIN
Unit
Related Features
Times
location Timer expiration in
PS
Description
2448
When the location request from the core network is received,

the location monitoring timer starts. If the timer is timeout, this
counter counts the number of location failures due to the timer

timout.
Measurement
Point
The counter counts when the location monitoring timer is timeout.

FIGURE 2408 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURE
TO LOCATION MONITORING TIMER TIMEOUT IN PS DOMAIN
Unit
Related Features
DUE
Times
location failure due to other
BSC's cause in PS
Description
Location fails due to other causes inside iBSC, such as message

Measurement
Point
The counter counts when the following problems occur: message

Unit
Related Features
Times
2449
2450
Chapter
65
LB Global Msg
Measurement
Table of Contents
Overview...................................................................... 2451
C901590001 Number of receiving RESET message from
SMLC ........................................................................... 2451
C901590002 Number of sending RESET ACK message to
SMLC ........................................................................... 2452
C901590003 Number of sending RESET message to
SMLC ........................................................................... 2453
C901590004 Number of receiving RESET ACK message from
SMLC ........................................................................... 2453
Overview
LB interface global message measurement involve counters used
for evaluating the global performance and status of LB interface.
receiving RESET message
from SMLC
Description
Measurement
Point
The RESET message is received at BSC from SMLC.

The counter counts when the RESET message is received at BSC
from SMLC. The measurement point is A, as shown in Figure 2409.
2451

RECEIVED FROM SMLC
Unit
OF
NUMBER
OF
RESET MESSAGES
Times
sending RESET ACK
message to SMLC
Description
BSC receives the RESET message from SMLC. This counter counts
the number of the RESET ACK messages sent to SMLC from BSC.
Measurement
Point
The counter counts when the RESET ACK message is sent to SMLC
from BSC. The measurement point is A, as shown in Figure 2410.
SENT TO SMLC
2452
OF
NUMBER
OF
RESET ACK MESSAGES
Chapter 65 LB Global Msg Measurement
Unit
Times
sending RESET message to
SMLC
Description
This counter counts the number of RESET messages sent to SMLC

from BSC.
Measurement
Point
The counter counts when the RESET message is sent to SMLC from
BSC. The measurement point is A, as shown in Figure 2411.
SENT TO SMLC
Unit
OF
NUMBER
OF
RESET MESSAGES
Times
receiving RESET ACK
message from SMLC
Description
This counter counts the number of RESET ACK messages received

at BSC from SMLC.
Measurement
Point
The counter counts when the RESET ACK message is received at

BSC from SMLC. The measurement point is A, as shown in Figure
2412.
2453

RECEIVED FROM SMLC
Unit
2454
OF
NUMBER
Times
OF
RESET ACK MESSAGES
Chapter
66
Ater Interface Relays

Measurement
Table of Contents
Overview...................................................................... 2455
C901600001 Number of configured 16 K relay circuits of Ater
interface ...................................................................... 2456
C901600002 Average of unavailable 16K relay circuits of Ater
interface ...................................................................... 2456
C901600003 Average of available 16 K relay circuits of Ater
interface ...................................................................... 2457
C901600004 Maximum of busy 16 K relay circuits of Ater interface ......................................................................... 2458
C901600005 Maximum of busy 8 K relay circuits of Ater interface ......................................................................... 2459
interface ...................................................................... 2461
C901600007 Total busy time of 8 K relay circuits of Ater interface ......................................................................... 2462
Overview
Ater interface relay measurement (office) involves measurement
of the following information: the number of 16 K relay circuits configured at Ater interface, the average number of unavailable 16 K
relay circuits (blocked) configured at Ater interface, the average
number of available 16 K relay circuits (unblocked) configured at
Ater interface, the maximum number of busy 16 K relay circuits
at Ater interface, the maximum number of busy 8 K relay circuits
at Ater interface, the total busy time of 16 K relay circuits at Ater
interface, and the total busy time of 8 K relay circuits at Ater interface.
2455
configured 16 K relay circuits
of Ater interface
Description
This counter counts the number of 16 K relay circuits configured

at Ater interface.
Usage
This counter is used to find out the number of 16 K relay circuits

configured at Ater interface.
Measurement
Point
iBSC queries the database periodically, and saves the value obtained from the database in this counter. The measurement point
RELAY CIRCUITS OF ATER INTERFACE
Unit
NUMBER
OF CONFIGURED
16 K
16 K
C901600002 Average
of unavailable 16K relay
circuits of Ater interface
2456
Description
This counter counts the average number of unavailable 16 K relay

circuits at Ater interface.
Usage
This counter is used to find out the average number of unavailable

16 K relay circuits at Ater interface.
Chapter 66 Ater Interface Relays Measurement
Measurement
Point
RELAY CIRCUITS OF ATER INTERFACE
Unit
OF
AVERAGE
OF UNAVAILABLE
16K
16 K
C901600003 Average of
available 16 K relay circuits
of Ater interface
Description
This counter counts the average number of available 16 K relay

Usage
This counter is used to find out the average number of available

16 K relay circuits at Ater interface.
Measurement
Point
2457

CIRCUITS OF ATER INTERFACE
Unit
OF
AVERAGE
OF AVAILABLE
16 K
RELAY
16 K
busy 16 K relay circuits of
Ater interface
2458
Description
This counter counts the maximum number of busy 16 K relay circuits at Ater interface.
Usage
This counter is used to find out the maximum number of busy 16

K relay circuits at Ater interface.
Measurement
Point
iBSC queries the database periodically and saves the value obtained from the database in this counter, or the counter counts
when Ater interface terrestrial circuit is released. The measurement point is A in Figure 2416 and B in Figure 2417. (Note: Figure
2417 only gives one case of Ater interface terrestrial circuit being
released.)
Unit

CIRCUITS OF ATER INTERFACE - (1)
MAXIMUM
OF BUSY
16 K
RELAY

MAXIMUM
OF BUSY
16 K
RELAY
Times
busy 8 K relay circuits of Ater
interface
Description
This counter counts the maximum number of busy 8 K relay circuits at Ater interface.
Usage
This counter is used to find out the maximum number of busy 8 K

relay circuits at Ater interface.
2459
Measurement
Point
Unit
2460
released.)
POINT
- (1)
OF
MAXIMUM
OF BUSY
8K
RELAY

POINT
- (2)
OF
MAXIMUM
OF BUSY
8K
RELAY
Times
C901600006 Total busy time

of 16 K relay circuits of Ater
interface
Description
This counter counts the total busy time of 16 K relay circuits at

Ater interface.
Usage
This counter is used to find out the total busy time of 16 K relay
Measurement
Point
released.)
OF
TOTAL
BUSY TIME OF
16 K
RELAY
2461

Unit
OF
TOTAL
BUSY TIME OF
16 K
RELAY
Second
C901600007 Total busy time

of 8 K relay circuits of Ater
interface
2462
Description
This counter counts the total busy time of 8 K relay circuits at Ater
interface.
Usage
This counter is used to find out the total busy time of 8 K relay
Measurement
Point
released.)
Unit

TOTAL
BUSY TIME OF
8K
RELAY

TOTAL
BUSY TIME OF
8K
RELAY
Second
2463
2464
Chapter
67
Ater Interface
SCCP Connections
Measurement
Table of Contents
Overview...................................................................... 2465
C901610001 Number of SCCP establishment requests (BSC
to TC) .......................................................................... 2465
C901610002 Number of SCCP establishments success (BSC
to TC) .......................................................................... 2466
C901610003 Number of SCCP establishment failure due to
timeout (BSC to TC) ...................................................... 2467
C901610004 Number of SCCP establishment refused (BSC to
TC).............................................................................. 2468
Overview
Ater interface SCCP connection measurement (office) is used to
measure the following information of link establishment from BSC
to TC: the number of link establishment requests, the number of
link establishment successes, the number of link establishment
failures due to timer timeout, and the number of link establishment
being rejected.
C901610001 Number
of SCCP establishment
requests (BSC to TC)
Description
This counter counts the number of link establishment requests initiated by BSC towards TC.
Usage
This counter is used to find out the number of link establishment

requests initiated by BSC towards TC.
2465
Measurement
Point
Rancs sends the TC resource request to Ater interface. The counter

increments when Ater interface sends the SCCP link establishment
request to iTC. The measurement point is A, as shown in Figure
2424.
REQUESTS (BSC TO TC)
Unit
OF
NUMBER
OF
SCCP
ESTABLISHMENT
Times
SCCP establishments
success (BSC to TC)
2466
Description
This counter counts the number of successful link establishments

initiated by BSC towards TC.
Usage
This counter is used to find out the number of successful link establishments initiated by BSC towards TC. The BSC-to-TC link establishment success rate can be calculated according to this counter's
value and the number of link establishment requests.
Measurement
Point
When the Ater process receives the Connect Conf message from
iTC, the counter increments. The measurement point is A, as
Chapter 67 Ater Interface SCCP Connections Measurement

SUCCESSES
Unit
OF
NUMBER
OF
SCCP CONNECTION
Times
SCCP establishment failure
due to timeout (BSC to TC)
Description
This counter counts the number of failed link establishments,

which is due to timer timeout, initiated by BSC towards TC.
Measurement
Point
When the Ater process expires at the timer TAterWaitConn, the

Figure 2426.
2467

FAILURE DUE TO TIMEOUT
Unit
OF
NUMBER
OF
SCCP CONNECTION
Times
C901610004 Number
of SCCP establishment
refused (BSC to TC)
2468
Description
This counter counts the number of rejected link establishment requests initiated by BSC towards TC.
Measurement
Point
When the Ater process receives the Disconnect Ind message from
the AterDispatch process, the counter increments. The measurement point is A, as shown in Figure 2427.
Chapter 67 Ater Interface SCCP Connections Measurement

REQUEST BEING REJECTED
Unit
OF
NUMBER
OF
SCCP CONNECTION
Times
2469
2470
Chapter
68
Measurement
Reprot Serving Cell
Measurement
Table of Contents
MR Serving Cell Measurement ......................................... 2474
C901620001 Number of samples of UL RQ=0 and receive level
between 0 and 10.......................................................... 2475
between 11 and 15 ........................................................ 2476
between 16 and 20 ........................................................ 2476
between 21 and 30 ........................................................ 2477
between 31 and 40 ........................................................ 2478
between 41 and 63 ........................................................ 2479
between 0 and 10.......................................................... 2480
between 11 and 15 ........................................................ 2480
between 16 and 20 ........................................................ 2481
between 21 and 30 ........................................................ 2482
between 31 and 40 ........................................................ 2483
between 41 and 63 ........................................................ 2483
between 0 and 10.......................................................... 2484
between 11 and 15 ........................................................ 2485
between 16 and 20 ........................................................ 2486
between 21 and 30 ........................................................ 2486
between 31 and 40 ........................................................ 2487
between 41 and 63 ........................................................ 2488
between 0 and 10.......................................................... 2489
between 11 and 15 ........................................................ 2489
2471

between 16 and 20 ........................................................ 2490
between 21 and 30 ........................................................ 2491
between 31 and 40 ........................................................ 2492
between 41 and 63 ........................................................ 2492
between 0 and 10.......................................................... 2493
between 11 and 15 ........................................................ 2494
between 16 and 20 ........................................................ 2495
between 21 and 30 ........................................................ 2495
between 31 and 40 ........................................................ 2496
between 41 and 63 ........................................................ 2497
between 0 and 10.......................................................... 2498
between 11 and 15 ........................................................ 2498
between 16 and 20 ........................................................ 2499
between 21 and 30 ........................................................ 2500
between 31 and 40 ........................................................ 2501
between 41 and 63 ........................................................ 2501
between 0 and 10.......................................................... 2502
between 11 and 15 ........................................................ 2503
between 16 and 20 ........................................................ 2504
between 21 and 30 ........................................................ 2504
between 31 and 40 ........................................................ 2505
between 41 and 63 ........................................................ 2506
between 0 and 10.......................................................... 2507
between 11 and 15 ........................................................ 2507
between 16 and 20 ........................................................ 2508
between 21 and 30 ........................................................ 2509
between 31 and 40 ........................................................ 2510
between 41 and 63 ........................................................ 2510
C901620049 Number of samples of DL RQ=0 and receive level
between 0 and 10.......................................................... 2511
between 11 and 15 ........................................................ 2512
2472
Chapter 68 Measurement Reprot Serving Cell Measurement

between 16 and 20 ........................................................ 2513
between 21 and 30 ........................................................ 2513
between 31 and 40 ........................................................ 2514
between 41 and 63 ........................................................ 2515
between 0 and 10.......................................................... 2516
between 11 and 15 ........................................................ 2516
between 16 and 20 ........................................................ 2517
between 21 and 30 ........................................................ 2518
between 31 and 40 ........................................................ 2519
between 41 and 63 ........................................................ 2519
between 0 and 10.......................................................... 2520
between 11 and 15 ........................................................ 2521
between 16 and 20 ........................................................ 2522
between 21 and 30 ........................................................ 2522
between 31 and 40 ........................................................ 2523
between 41 and 63 ........................................................ 2524
between 0 and 10.......................................................... 2525
between 11 and 15 ........................................................ 2525
between 16 and 20 ........................................................ 2526
between 21 and 30 ........................................................ 2527
between 31 and 40 ........................................................ 2528
between 41 and 63 ........................................................ 2528
between 0 and 10.......................................................... 2529
between 11 and 15 ........................................................ 2530
between 16 and 20 ........................................................ 2531
between 21 and 30 ........................................................ 2531
between 31 and 40 ........................................................ 2532
between 41 and 63 ........................................................ 2533
between 0 and 10.......................................................... 2534
between 11 and 15 ........................................................ 2534
2473

between 16 and 20 ........................................................ 2535
between 21 and 30 ........................................................ 2536
between 31 and 40 ........................................................ 2537
between 41 and 63 ........................................................ 2537
between 0 and 10.......................................................... 2538
between 11 and 15 ........................................................ 2539
between 16 and 20 ........................................................ 2540
between 21 and 30 ........................................................ 2540
between 31 and 40 ........................................................ 2541
between 41 and 63 ........................................................ 2542
between 0 and 10.......................................................... 2543
between 11 and 15 ........................................................ 2543
between 16 and 20 ........................................................ 2544
between 21 and 30 ........................................................ 2545
between 31 and 40 ........................................................ 2546
between 41 and 63 ........................................................ 2546
MR Serving Cell
Measurement
Values of MR serving cell measurement counters involve uplink/downlink quality and receiving level in the measurement
report. The measurement point of all counters in this measurement task is A, as shown in Figure 2428.
REPORT TO BSC
2474
OF
BTS SENDING MEAUREMENT
Statistic unit in this measurement is TRX.
samples of UL RQ=0 and
receive level between 0 and
10
Description
This counter counts the number of samples of UL RQ=0 and receive

level between 0 and 10 in UL radio measurement report (preprocessing report or enhanced preprocessing measurement report).
This counter increments when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing
measurement report) in which UL RQ=0 and receive level is between 0 and 10.
Usage
This counter is used to find out radio channel's UL quality and receive level.
Measurement
Point
This counter counts when BSC receives the UL radio measurement

report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=0 and receive level is between 0 and
10. The measurement point is A, as shown in Figure 2429.
REPORT TO BSC
Unit
OF
Times
2475
receive level between 11
and 15
Description

Usage
Measurement
Point

report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=0 and receive level is between 11
and 15. The measurement point is A, as shown in Figure 2430.
REPORT TO BSC
Unit
OF
Times
and 20
Description
2476

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 30
Description

Usage
Measurement
Point

2477

REPORT TO BSC
Unit
OF
Times
and 40
Description

Usage
Measurement
Point

REPORT TO BSC
2478
OF
Unit
Times
and 63
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2479
10
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 15
Description
2480

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 20
Description

Usage
Measurement
Point

2481

REPORT TO BSC
Unit
OF
Times
and 30
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
2482
OF
Times
and 40
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 63
Description

2483
Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
10
2484
Description

Usage
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 15
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2485
and 20
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 30
Description
2486

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 40
Description

Usage
Measurement
Point

2487

REPORT TO BSC
Unit
OF
Times
and 63
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
2488
OF
Times
10
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 15
Description

2489
Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 20
2490
Description

Usage
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 30
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2491
and 40
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 63
Description
2492

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
10
Description

Usage
Measurement
Point

2493

REPORT TO BSC
Unit
OF
Times
and 15
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
2494
OF
Times
and 20
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 30
Description

2495
Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 40
2496
Description

Usage
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 63
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2497
10
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 15
Description
2498

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 20
Description

Usage
Measurement
Point

2499

REPORT TO BSC
Unit
OF
Times
and 30
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
2500
OF
Times
and 40
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 63
Description

2501
Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
10
2502
Description

Usage
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 15
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2503
and 20
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 30
Description
2504

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 40
Description

Usage
Measurement
Point

2505

REPORT TO BSC
Unit
OF
Times
and 63
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
2506
OF
Times
10
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 15
Description

2507
Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 20
2508
Description

Usage
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 30
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2509
and 40
Description

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 63
Description
2510

Usage
Measurement
Point

REPORT TO BSC
Unit
OF
Times
samples of DL RQ=0 and
10
Description
This counter counts the number of samples of DL RQ=0 and receive

level between 0 and 10 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report).
This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing
measurement report) in which DL RQ=0 and receive level is between 0 and 10.
Usage
This counter is used to find out radio channel's DL quality and

receive level.
Measurement
Point
This counter counts when BSC receives the DL radio measurement

report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 0 and
2511

REPORT TO BSC
Unit
OF
Times
and 15
Description

Usage

receive level.
Measurement
Point

report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level between 11 and
REPORT TO BSC
Unit
2512
OF
Times
and 20
Description

Usage

receive level.
Measurement
Point

report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 16
REPORT TO BSC
Unit
OF
Times
and 30
Description

2513
Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 40
2514
Description

Usage

receive level.
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 63
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2515
10
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 15
Description
2516

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 20
Description

Usage

receive level.
Measurement
Point

2517

REPORT TO BSC
Unit
OF
Times
and 30
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
2518
OF
Times
and 40
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 63
Description

2519
Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
10
2520
Description

Usage

receive level.
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 15
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2521
and 20
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 30
Description
2522

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 40
Description

Usage

receive level.
Measurement
Point

2523

REPORT TO BSC
Unit
OF
Times
and 63
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
2524
OF
Times
10
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 15
Description

2525
Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 20
2526
Description

Usage

receive level.
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 30
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2527
and 40
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 63
Description
2528

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
10
Description

Usage

receive level.
Measurement
Point

2529

REPORT TO BSC
Unit
OF
Times
and 15
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
2530
OF
Times
and 20
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 30
Description

2531
Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 40
2532
Description

Usage

receive level.
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 63
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2533
10
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 15
Description
2534

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 20
Description

Usage

receive level.
Measurement
Point

2535

REPORT TO BSC
Unit
OF
Times
and 30
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
2536
OF
Times
and 40
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 63
Description

2537
Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
10
2538
Description

Usage

receive level.
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 15
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2539
and 20
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 30
Description
2540

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 40
Description

Usage

receive level.
Measurement
Point

2541

REPORT TO BSC
Unit
OF
Times
and 63
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
2542
OF
Times
10
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 15
Description

2543
Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 20
2544
Description

Usage

receive level.
Measurement
Point


REPORT TO BSC
Unit
OF
Times
and 30
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2545
and 40
Description

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
and 63
Description
2546

Usage

receive level.
Measurement
Point

REPORT TO BSC
Unit
OF
Times
2547
2548
Chapter
69
Measurement Report
Adjacent Cell
Measurement
Table of Contents
MR Adjacent Cell Measurement........................................ 2549
C901630001 Number of samples with C/I < -10db............. 2550
C901630002 Number of samples with C/I between -9db and
-5db ............................................................................ 2551
C901630003 Number of samples with C/I between -4db and
0db ............................................................................. 2551
C901630004 Number of samples with C/I between 1db and
5db ............................................................................. 2552
10db............................................................................ 2553
15db............................................................................ 2553
20db............................................................................ 2554
C901630008 Number of samples with C/I > 20db .............. 2555
MR Adjacent Cell
Measurement
Measurement values of this measurement task involve the downlink level. If the measurement report contains adjacent cell information, then subtract the adjacent cell's level from the local cell's
downlink level, and perform measurement according to the value.
The measurement point of all counters in this measurement task
2549

REPORT TO BSC
OF
samples with C/I < -10db
Description
Usage
Measurement
Point
This counter counts the number of samples with DL level in local

cell subtracting the level in adjacent cell < -10dB in received DL
radio measurement report (preprocessing report or enhanced preprocessing measurement report).
This counter is used to find out DL level of adjacent cell.
This counter increments while DL level in this cell in DL radio measurement report (preprocessing report or enhanced preprocessing
measurement report) received by BSC subtracting the level of adjacent cell is lower than 10dB, as shown in Figure 2526.
REPORT TO BSC
Unit
2550
OF
BTS SENDING MEASUREMENT
Times
Chapter 69 Measurement Report Adjacent Cell Measurement
samples with C/I between
-9db and -5db
Description
Usage
Measurement
Point
This counter counts the number of samples with DL level in local cell subtracting the level in adjacent cell within -9dB~-5dB in
received DL radio measurement report (preprocessing report or
enhanced preprocessing measurement report).
measurement report) received by BSC subtracting the level of adjacent cell is within -9dB~-5dB, as shown in Figure 2527.
REPORT TO BSC
Unit
OF
Times
-4db and 0db
Description
Usage
Measurement
Point
This counter counts the number of samples with DL level in local cell subtracting the level in adjacent cell within -4dB~0dB in
measurement report) received by BSC subtracting the level of adjacent cell is within -4dB~0dB, as shown in Figure 2528.
2551

REPORT TO BSC
Unit
OF
Times
1db and 5db
Description
Usage
Measurement
Point
This counter counts the number of samples with DL level in local cell subtracting the level in adjacent cell within 1dB~5dB in
measurement report) received by BSC subtracting the level of adjacent cell is within 1dB~5dB, as shown in Figure 2529.
REPORT TO BSC
Unit
2552
OF
Times
6db and 10db
Description
Usage
Measurement
Point
REPORT TO BSC
Unit
OF
Times
11db and 15db
Description
Usage
Measurement
Point
2553

REPORT TO BSC
Unit
OF
Times
16db and 20db
Description
Usage
Measurement
Point
REPORT TO BSC
Unit
2554
OF
Times
samples with C/I > 20db
Description
Usage
Measurement
Point
This counter counts the number of samples with DL level in local cell subtracting the level in adjacent cell > 20dB in received
DL radio measurement report (preprocessing report or enhanced
preprocessing measurement report).
measurement report) received by BSC subtracting the level of adjacent cell is higher than 20dB, as shown in Figure 2533.
REPORT TO BSC
Unit
OF
Times
2555
2556
Chapter
70
TRX Paging
Measurement
Table of Contents
Overview...................................................................... 2557
C901640001 Number of PS paging message discarded due to
full of the queue ............................................................ 2558
C901640002 Number of CS paging message discarded due to
full of the queue ............................................................ 2558
C901640003 Average length of PCH queue: 9*9................ 2559
C901640004 Average length of PCH queue: 9*64 .............. 2559
C901640005 The percentage of PCH Blocks validly
used ............................................................................ 2560
C901640006 Number of paging messages seized by
other hyper-priority messages while transmitting on PCH
blocks .......................................................................... 2560
C901640007 Number of paging messages retransmitted zero
times ........................................................................... 2560
C901640008 Number of paging messages retransmitted one
times ........................................................................... 2561
C901640009 Number of paging messages retransmitted two
times ........................................................................... 2561
C901640010 Number of paging messages retransmitted three
times ........................................................................... 2561
C901640011 Numbers of paging messages retransmitted four
times ........................................................................... 2562
Overview
The paging measurement measures the usage of paging channel
queue and the number of failures in receiving paging message due
to the paging message queue being full.
It measures the paging performance data of base station, including
the average length of paging queue at base station and the number
of discarded paging messages due to the queue being full.
Figure 2534 shows the paging performance measurement flow.
2557
FIGURE 2534 PAGING PERFORMANCE MEASUREMENT REPORTING
paging message discarded
due to full of the queue
Description
This counter counts the number of PS paging messages discarded

due to the queue being full.
Usage
This counter is used to find out the number of failures in receiving

PS paging messages at BTS.
Measurement
Point
Unit
The counter's value is obtained by querying database when the

paging performance measurement data is reported periodically.
Times
paging message discarded
due to full of the queue
Description
This counter counts the number of CS paging messages discarded

due to the queue being full.
Usage
This counter is used to find out the number of failures in receiving

CS paging messages at BTS.
2558
Chapter 70 TRX Paging Measurement
Measurement
Point
Unit

Times

of PCH queue: 9*9
Description
This counter counts the occupancy of PCH message buffer queue

which saves paging messages according to 2~9 51-multiframe
mode at BTS.
Usage
This counter is used to find out the occupancy of PCH message

buffer queue which saves paging messages according to 2~9
51-multiframe mode at BTS.
Measurement
Point
Unit

Times

of PCH queue: 9*64
Description
This counter counts the occupancy of PCH message buffer queue

which saves paging messages according to 64 51-multiframe mode
at BTS.
Usage
This counter is used to find out the occupancy of PCH message

buffer queue which saves paging messages according to 64
51-multiframe mode at BTS.
Measurement
Point
Unit

Times
2559
C901640005 The
percentage of PCH Blocks
validly used
Description
This counter records the percentage of sending valid information

on PCH resource block of CCCH of the cell.
Unit
Statistics Object
Percent
Cell
paging messages seized
by other hyper-priority
messages while transmitting
on PCH blocks
Description
This counter counts the number of sending paging message on the

resource block being delayed due to the PCH resource block being
preempted by message of higher priority.
Unit
Statistics Object
Times
Cell
C901640007 Number
of paging messages
retransmitted zero times
Description
This counter counts the number of paging messages not being

retransmitted after the original paging messages are sent.
Unit
2560
Times
Chapter 70 TRX Paging Measurement
Statistics Object
Cell
C901640008 Number
of paging messages
retransmitted one times
Description
This counter counts the number of paging messages being retransmitted once after the original paging messages are sent.
Unit
Statistics Object
Times
Cell
C901640009 Number
of paging messages
retransmitted two times
Description
This counter counts the number of paging messages being retransmitted twice after the original paging messages are sent.
Unit
Statistics Object
Times
Cell
C901640010 Number
of paging messages
retransmitted three times
Description
This counter counts the number of paging messages being retransmitted three times after the original paging messages are sent.
Unit
Times
2561
Statistics Object
Cell
C901640011 Numbers
of paging messages
retransmitted four times
Description
This counter counts the number of paging messages being retransmitted four times after the original paging messages are sent.
Unit
Statistics Object
2562
Times
Cell
Chapter
71
TRX Temperature Power

Measurement
Table of Contents
Overview...................................................................... 2563
C901650001 Maximum value of TRX power (db) ................ 2563
C901650002 Minimum value of TRX power (db)................. 2564
C901650003 Mean value of TRX power (db) ...................... 2564
C901650004 Maximum of TRX temperature (Celsius) ......... 2564
C901650005 Minimum of TRX temperature (Celsius) .......... 2564
C901650006 Mean of TRX temperature (Celsius) ............... 2565
Overview
The temperature and power of TRX are measured on TRU and reported to BSC periodically.
C901650001 Maximum
value of TRX power (db)
Description
This counter counts the maximum value of TRX's power within the
measurement period.
SDR base station does not support the measurement.
Measurement
Point
Unit
TRU is measured and reported periodically.

dbm
2563

of TRX power (db)
Description
This counter counts the minimum value of TRX's power within the
measurement period.
Measurement
Point
Unit

dbm
C901650003 Mean value of

TRX power (db)
Description
This counter counts the average value of TRX's power within the
measurement period.
Measurement
Point
Unit

dbm
TRX temperature (Celsius)
Description
This counter counts the maximum value of TRX's temperature

Measurement
Point
Unit

Celsius
C901650005 Minimum of
TRX temperature (Celsius)
Description
2564
This counter counts the minimum value of TRX's temperature

Chapter 71 TRX Temperature Power Measurement

Measurement
Point
Unit

Celsius
C901650006 Mean of TRX

temperature (Celsius)
Description
This counter counts the average value of TRX's temperature within

Measurement
Point
Unit

Celsius
2565
2566
Chapter
72
Terminal Ability Statistic

Table of Contents
Terminal Ability Statistics................................................ 2569
C901660001 Number of mobile support single TS DTM ability ............................................................................... 2569
C901660002 Number of mobile support DTM GPRS multi TS
ability 5 ....................................................................... 2570
ability 9 ....................................................................... 2571
ability 11...................................................................... 2572
C901660005 Number of mobile support DTM EGPRS multi TS
ability 5 ....................................................................... 2573
ability 9 ....................................................................... 2574
ability 11...................................................................... 2575
multi TS ability 5 ........................................................... 2576
multi TS ability 6 ........................................................... 2577
multi TS ability 9 ........................................................... 2578
multi TS ability 10 ......................................................... 2579
multi TS ability 11 ......................................................... 2580
C901660013 Number of mobile support extend DTM EGPRS
multi TS ability 5 ........................................................... 2581
multi TS ability 6 ........................................................... 2582
multi TS ability 9 ........................................................... 2583
multi TS ability 10 ......................................................... 2584
multi TS ability 11 ......................................................... 2585
1................................................................................. 2586
2................................................................................. 2588
3................................................................................. 2589
4................................................................................. 2591
5................................................................................. 2593
2567

6................................................................................. 2594
7................................................................................. 2596
8................................................................................. 2598
9................................................................................. 2599
10 ............................................................................... 2601
11 ............................................................................... 2603
12 ............................................................................... 2604
30 ............................................................................... 2606
31 ............................................................................... 2608
32 ............................................................................... 2609
33 ............................................................................... 2611
34 ............................................................................... 2613
1................................................................................. 2614
2................................................................................. 2616
3................................................................................. 2618
4................................................................................. 2619
5................................................................................. 2621
6................................................................................. 2623
7................................................................................. 2624
8................................................................................. 2626
9................................................................................. 2628
10 ............................................................................... 2629
11 ............................................................................... 2631
12 ............................................................................... 2633
30 ............................................................................... 2634
31 ............................................................................... 2636
32 ............................................................................... 2638
33 ............................................................................... 2639
34 ............................................................................... 2641
C901660052 Number of mobile support FR ....................... 2643
C901660053 Number of mobile support HR....................... 2643
2568
Chapter 72 Terminal Ability Statistic
C901660054 Number of mobile support EFR ..................... 2644

C901660055 Number of mobile support AMRFR ................. 2645
C901660056 Number of mobile support AMRHR................. 2645
C901660057 Number of mobile support wideband AMROFR ........................................................................... 2646
C901660058 Number of mobile support wideband AMRFR ............................................................................. 2647
C901660059 Number of mobile support wideband AMROHR .......................................................................... 2648
C901660060 Number of mobile support AMROHR .............. 2649
C901660061 Number of mobile support extend uplink
TBF ............................................................................. 2650
C901660062 Number of mobile support NACC ................... 2651
C901660063 Number of mobile support GPRS extend dynamic
allocation ..................................................................... 2652
C901660064 Number of mobile support EGPRS extend dynamic allocation ............................................................ 2653
C901660065 Number of sampling received Classmark3.......................................................................... 2654
C901660066 Number of sampling received radio access ability ............................................................................... 2655
C901660069 Num of MS supporting PS handover............... 2656
C901660070 The Number of MS which Support SAIC.......... 2657
C901660071 The Number of MS which not Support
SAIC............................................................................ 2658
Terminal Ability Statistics

These counters (CELL) count the relevant access capabilities for
the access terminal (MS), mainly counting the number of terminals
with different access capabilities.
mobile support single TS
DTM ability
Description
This counter counts the number of mobiles that support the capability of single TS DTM.
Usage
This counter measures the number of mobiles that support the

single TS DTM ability.
Measurement
Point
This counter increments while Rancs receives the Classmark Update message delivered by MSC or the Classmark Change message
sent by MS and the message indicates the MS supports the single
TS DTM ability. The measurement point is A1 or A2, as shown in
Figure 2535.
2569

SINGLE TS DTM ABILITY
Unit
POINT
OF
NUMBER
OF MOBILE SUPPORT
Times
mobile support DTM GPRS
multi TS ability 5
2570
Description
This counter counts the number of mobiles that support DTM GPRS
multi TS ability 5.
Usage
It is used to measure the number of mobiles that support DTM

GPRS multi TS ability 5.
Measurement
Point
sent by MS and the message indicates the MS supports DTM GPRS
multi TS ability 5. The measurement point is A1 or A2, as shown
in the figure below.

GPRS MULTI TS ABILITY 5
Unit
OF
NUMBER
OF MOBILE SUPPORT
DTM
Times
multi TS ability 9
Description
multi TS ability 9.
Usage

Measurement
Point
in Figure 2537.
2571

Unit
OF
NUMBER
OF MOBILE SUPPORT
DTM
Times
multi TS ability 11
2572
Description
multi TS ability 11.
Usage

Measurement
Point
in Figure 2538.

Unit
OF
NUMBER
OF MOBILE SUPPORT
DTM
Times
mobile support DTM EGPRS
multi TS ability 5
Description
This counter counts the number of mobiles that support DTM EGPRS multi TS ability 5.
Usage

EGPRS multi TS ability 5.
Measurement
Point
sent by MS and the message indicates the MS supports DTM EGPRS multi TS ability 5. The measurement point is A1 or A2, as
2573

EGPRS MULTI TS ABILITY 5
Unit
OF
NUMBER
OF MOBILE SUPPORT
DTM
Times
multi TS ability 9
2574
Description
Usage

Measurement
Point

Unit
OF
NUMBER
OF MOBILE SUPPORT
DTM
Times
multi TS ability 11
Description
Usage

Measurement
Point
2575

Unit
OF
NUMBER
OF MOBILE SUPPORT
DTM
Times
mobile support extend DTM
GPRS multi TS ability 5
2576
Description
This counter counts the number of mobiles that support extend

DTM GPRS multi TS ability 5.
Usage
It is used to measure the number of mobiles that support extend

Measurement
Point
sent by MS and the message indicates the MS supports extend DTM
GPRS multi TS ability 5. The measurement point is A1 or A2, as
FIGURE
EXTEND
Unit
2542 MEASUREMENT POINT OF NUMBER

DTM GPRS MULTI TS ABILITY 5
OF MOBILE SUPPORT
Times
Description

Usage

Measurement
Point
2577
FIGURE
EXTEND
Unit

OF MOBILE SUPPORT
Times
2578
Description

Usage

Measurement
Point
FIGURE
EXTEND
Unit

OF MOBILE SUPPORT
Times
Description

Usage

Measurement
Point
2579
FIGURE
EXTEND
Unit

OF MOBILE SUPPORT
Times
2580
Description

Usage

Measurement
Point
FIGURE
EXTEND
Unit

OF MOBILE SUPPORT
Times
EGPRS multi TS ability 5
Description

DTM EGPRS multi TS ability 5.
Usage

Measurement
Point
EGPRS multi TS ability 5. The measurement point is A1 or A2, as
2581
FIGURE
EXTEND
Unit

DTM EGPRS MULTI TS ABILITY 5
OF MOBILE SUPPORT
Times
2582
Description

Usage

Measurement
Point
FIGURE
EXTEND
Unit

OF MOBILE SUPPORT
Times
Description

Usage

Measurement
Point
2583
FIGURE
EXTEND
Unit

OF MOBILE SUPPORT
Times
2584
Description

Usage

Measurement
Point
FIGURE
EXTEND
Unit

OF MOBILE SUPPORT
Times
Description

Usage

Measurement
Point
2585
FIGURE
EXTEND
Unit

OF MOBILE SUPPORT
Times
mobile of GPRS multi TS
ability 1
2586
Description
This counter counts the number of mobiles that support GPRS multi
TS ability 1.
Usage
It is used to measure the number of mobiles that support GPRS

multi TS ability 1.
Measurement
Point
This counter increments while PS control plane receives the downlink assignment requests sent by the user plane, the resource requests sent by the user plane on two-phase access, or the instance
setup indication sent by the user plane and the message indicates
the MS supports GPRS multi TS ability 1. The measurement point
is A1, A2, and A3, as shown in Figure 2552, Figure 2553, Figure
2554.

MULTI TS ABILITY 1 - (1)
POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
2587
Unit
Times
ability 2
Description
TS ability 2.
Usage

multi TS ability 2.
Measurement
Point
2557.
2588
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 3
Description
TS ability 3.
Usage

multi TS ability 3.
Measurement
Point
This counter increments while PS control plane receives the downlink assignment requests sent by the user plane, the resource re-
2589
quests sent by the user plane on two-phase access, or the instance

2560.
2590

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS

Unit
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 4
Description
TS ability 4.
Usage

multi TS ability 4.
Measurement
Point
2563.
2591
Unit
2592

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 5
Description
TS ability 5.
Usage
This counter is used to measure the number of link setup requests

originated from BSC to TC.
Measurement
Point
2566.
POINT
OF
NUMBER
OF MOBILE OF
GPRS
2593
Unit

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 6
2594
Description
TS ability 6.
Usage

multi TS ability 6.
Measurement
Point
2569.
POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
2595

Unit
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 7
2596
Description
TS ability 7.
Usage

multi TS ability 7.
Measurement
Point
2572.
Unit

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
2597
ability 8
Description
TS ability 8.
Usage

multi TS ability 8.
Measurement
Point
2575.
2598
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 9
Description
TS ability 9.
Usage

multi TS ability 9.
Measurement
Point
2599
2578.
2600

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS

Unit
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 10
Description
TS ability 10.
Usage

Measurement
Point
2581.
2601
Unit
2602

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 11
Description
TS ability 11.
Usage

Measurement
Point
2584.
POINT
OF
NUMBER
OF MOBILE OF
GPRS
2603
Unit

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 12
2604
Description
TS ability 12.
Usage

Measurement
Point
2587.
POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
2605

Unit
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 30
2606
Description
TS ability 30.
Usage

Measurement
Point
2590.
Unit

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
2607
ability 31
Description
TS ability 31.
Usage

Measurement
Point
2593.
2608
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 32
Description
TS ability 32.
Usage

Measurement
Point
2609
2596.
2610

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS

Unit
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 33
Description
TS ability 33.
Usage

Measurement
Point
2599.
2611
Unit
2612

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
ability 34
Description
TS ability 34.
Usage

Measurement
Point
2602.
POINT
OF
NUMBER
OF MOBILE OF
GPRS
2613
Unit

POINT
OF
NUMBER
OF MOBILE OF
GPRS

POINT
OF
NUMBER
OF MOBILE OF
GPRS
Times
mobile of EGPRS multi TS
ability 1
2614
Description
This counter counts the number of mobiles that support EGPRS

multi TS ability 1.
Usage
It is used to measure the number of mobiles that support EGPRS

multi TS ability 1.
Measurement
Point
the MS supports EGPRS multi TS ability 1. The measurement point
2605.
POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2615

Unit
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 2
2616
Description

multi TS ability 2.
Usage

multi TS ability 2.
Measurement
Point
2608.

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2617
Unit
Times
ability 3
Description

multi TS ability 3.
Usage

multi TS ability 3.
Measurement
Point
2611.
2618
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 4
Description

multi TS ability 4.
Usage

multi TS ability 4.
Measurement
Point
2619
2614.
2620

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

Unit
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 5
Description

multi TS ability 5.
Usage
This counter is used to measure the number of link setup requests

originated from BSC to TC.
Measurement
Point
2617.
2621
2622

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
ability 6
Description

multi TS ability 6.
Usage

multi TS ability 6.
Measurement
Point
2620.
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2623
Unit

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 7
2624
Description

multi TS ability 7.
Usage

multi TS ability 7.
Measurement
Point

2623.
POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2625

Unit
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 8
2626
Description

multi TS ability 8.
Usage

multi TS ability 8.
Measurement
Point
2626.
Unit

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
2627
ability 9
Description

multi TS ability 9.
Usage

multi TS ability 9.
Measurement
Point
2629.
2628
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 10
Description

Usage

Measurement
Point
2629
the MS supports EGPRS multi TS ability 10. The measurement
point is A1, A2, and A3, as shown in Figure 2630, Figure 2631,
Figure 2632.
2630

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

Unit
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 11
Description

Usage

Measurement
Point
Figure 2635.
2631
Unit
2632

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 12
Description

Usage

Measurement
Point
Figure 2638.
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2633
Unit

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 30
2634
Description

Usage

Measurement
Point

Figure 2641.
POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2635

Unit
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 31
2636
Description

Usage

Measurement
Point
Figure 2644.

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2637
Unit
Times
ability 32
Description

Usage

Measurement
Point
Figure 2647.
2638
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 33
Description

Usage

Measurement
Point
2639

Figure 2650.
2640

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

Unit
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Times
ability 34
Description

Usage

Measurement
Point
Figure 2653.
2641
2642

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS

POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
mobile support FR
Description
Usage
Measurement
Point
This counter counts the number of mobiles that support FR.

It is used to measure the number of mobiles that support FR.
This counter increments while Rancs process receives the setup
(caller) or call confirmed message (callee) and the voice version
contained in this message is FR. The measurement point is A1
(caller) and A2 (callee), as shown in Figure 2654.
Unit
OF
NUMBER
OF MOBILE SUPPORT
FR
Times
mobile support HR
Description
Usage
Measurement
Point
This counter counts the number of mobiles that support HR.

It is used to measure the number of mobiles that support HR.
contained in this message is HR. The measurement point is A1
2643
Unit
OF
NUMBER
OF MOBILE SUPPORT
HR
Times
mobile support EFR
Description
Usage
Measurement
Point
This counter counts the number of mobiles that support EFR.

It is used to measure the number of mobiles that support EFR.
contained in this message is EFR. The measurement point is A1
Unit
2644
OF
NUMBER
Times
OF MOBILE SUPPORT
EFR
mobile support AMRFR
Description
This counter counts the number of mobiles that support AMRFR.
Usage
It is used to measure the number of mobiles that support AMRFR.
Measurement
Point

contained in this message is AMRFR. The measurement point is A1
AMRFR
Unit
OF
NUMBER
OF MOBILE SUPPORT
Times
mobile support AMRHR
Description
This counter counts the number of mobiles that support AMRHR.
Usage
It is used to measure the number of mobiles that support AMRHR.
Measurement
Point

contained in this message is AMRHR. The measurement point is
A1 (caller) and A2 (callee), as shown in Figure 2658.
2645

AMRHR
Unit
OF
NUMBER
OF MOBILE SUPPORT
Times
mobile support wideband
AMROFR
2646
Description
This counter counts the number of mobiles that support wideband

AMROFR.
Usage
It is used to measure the number of mobiles that support wideband

AMROFR.
Measurement
Point

contained in this message is wideband AMROFR. The measurement
point is A1 (caller) and A2 (callee), as shown in Figure 2659.

WIDEBAND AMROFR
Unit
POINT
OF
NUMBER
OF MOBILE SUPPORT
Times
AMRFR
Description

AMRFR.
Usage

AMRFR.
Measurement
Point

contained in this message is wideband AMRFR. The measurement
point is A1 (caller) and A2 (callee), as shown in Figure 2660.
2647

WIDEBAND AMRFR
Unit
POINT
OF
NUMBER
OF MOBILE SUPPORT
Times
AMROHR
2648
Description

AMROHR.
Usage

AMROHR.
Measurement
Point

contained in this message is wideband AMROHR. The measurement point is A1 (caller) and A2 (callee), as shown in Figure 2661.

WIDEBAND AMROHR
Unit
POINT
OF
NUMBER
OF MOBILE SUPPORT
Times
mobile support AMROHR
Description
This counter counts the number of mobiles that support AMROHR.
Usage
It is used to measure the number of mobiles that support AMROHR.
Measurement
Point

contained in this message is AMROHR. The measurement point is
A1 (caller) and A2 (callee), as shown in Figure 2662.
AMROHR
Unit
OF
NUMBER
OF MOBILE SUPPORT
Times
2649
mobile support extend uplink
TBF
2650
Description
This counter counts the number of mobiles that support extended

uplink TBF.
Usage
It is used to measure the number of mobiles that support extended

uplink TBF.
Measurement
Point
When PS control plane receives the downlink assignment requests

sent by the user plane or the resource requests sent by the user
plane on two-phase access, if extended uplink TBF is supported,
the counter increments. The measurement point is A1 and A2, as
EXTEND UPLINK TBF - (1)
POINT
OF
NUMBER
OF MOBILE SUPPORT

EXTEND UPLINK TBF - (2)
POINT
OF
NUMBER
OF MOBILE SUPPORT
Unit
Times
mobile support NACC
Description
Usage
Measurement
Point
This counter counts the number of mobiles that support NACC.

It is used to measure the number of mobiles that support NACC.
plane on two-phase access, if NACC is supported, the counter increments. The measurement point is A1 and A2, as shown in
NACC - (1)
OF
NUMBER
OF MOBILE SUPPORT

NACC - (2)
OF
NUMBER
OF MOBILE SUPPORT
2651
Unit
Times
mobile support GPRS
extend dynamic allocation
Description
This counter counts the number of mobiles that support GPRS extended dynamic allocation.
Usage

extended dynamic allocation.
Measurement
Point

plane on two-phase access, if GPRS extended dynamic allocation
is supported, the counter increments. The measurement point is
A1 and A2, as shown in Figure 2667 and Figure 2668.
EXTEND DYNAMIC ALLOCATION - (1)
2652
NUMBER
OF MOBILE SUPPORT
GPRS

EXTEND DYNAMIC ALLOCATION - (2)
Unit
NUMBER
OF MOBILE SUPPORT
GPRS
Times
mobile support EGPRS
extend dynamic allocation
Description

Usage

Measurement
Point

plane on two-phase access, if EGPRS extended dynamic allocation
is supported, the counter increments. The measurement point is
A1 and A2, as shown in Figure 2669 and Figure 2670.
2653
Unit

EGPRS EXTEND DYNAMIC ALLOCATION - (1)
OF MOBILE SUPPORT

EGPRS EXTEND DYNAMIC ALLOCATION - (2)
OF MOBILE SUPPORT
Times
C901660065 Number
of sampling received
Classmark3
2654
Description
This counter counts the number of samples that receive Classmark3.
Usage
It is used to measure the number of samples that receive Classmark3.
Measurement
Point
sent by MS and the message indicates Classmark3 is received. The

measurement point is A1 or A2, as shown in Figure 2671.
CLASSMARK3
Unit
OF
NUMBER
OF SAMPLING RECEIVED
Times
sampling received radio
access ability
Description
This counter counts the number of samples that receive radio access ability.
Usage
It is used to measure the number of samples that receive radio

access ability.
Measurement
Point
This counter increments while PS control plane receives the downlink assignment requests sent by the user plane or the resource
requests sent by the user plane on two-phase access and it counts
the number of samples that receive that radio access ability. The
measurement point is A1 and A2, as shown in Figure 2672 and
Figure 2673.
2655
Unit

RADIO ACCESS ABILITY - (1)
POINT
OF
NUMBER

RADIO ACCESS ABILITY - (2)
POINT
OF
NUMBER
Times
C901660069 Num of MS
supporting PS handover
Statistics object:
MS
Description
2656
MS
This counter counts the number of MSs that support PS handover.
This counter is used to find out the number of MSs that support
PS handover. After BSC receives the resource request from MS, if
the MS supports PS handover, the counter increments. The measurement point is A, as shown in Figure 2674.
FIGURE 2674
HANDOVER
Unit
MEASUREMENT POINT
OF
NUMBER
OF
MS
SUPPORTING
PS
Times
C901660070 The Number of

MS which Support SAIC
Description
This counter counts the number of mobile phones that support

SAIC.
Usage
This counter is used to find out the number of mobile phones that
support SAIC. It helps study the terminal ability of mobile phone.
Measurement
Point
1. When BSC receives the handover/assignment failure message

after sending the AssignCmd command, if the classmark is
changed or updated, the counter counts. The measurement
FIGURE 2675 ASSIGNMENT/HANDOVER FLOW
2. When BSC receives the Hoperformed Ack message, the counter

counts. The measurement point is A1, as shown in Figure
2676.
2657
FIGURE 2676 HANDOVER FLOW
Unit
Times
C901660071 The Number of

MS which not Support SAIC
Description
This counter counts the number of mobile phones that do not support SAIC.
Usage
This counter is used to find out the number of mobile phones that
do not support SAIC. It helps study the terminal ability of mobile
phone.
Measurement
Point
1. When BSC receives the handover/assignment failure message

after sending the AssignCmd command, if the classmark is
changed or updated, the counter counts.
2. When BSC receives the Hoperformed Ack message, the counter
counts.
Unit
2658
Times
Chapter
73
MTP3 Signaling Link

Statistics
Table of Contents
Overview...................................................................... 2660
C901670001 Duration of Signaling Link Out of Service......... 2660
C901670002 Number of Signaling Link Out of Service......... 2661
C901670003 Number of Message Signal Unit Sent ............. 2661
C901670004 Octets of SIF-SIO Sent ................................ 2661
C901670005 Number of Message Signal Unit Received......... 2662
C901670006 Octets of SIF-SIO Received .......................... 2662
C901670007 Peak Traffic of Signaling Link ........................ 2662
C901670008 Peak Traffic Duration of Signaling Link ........... 2663
C901670009 Number of Change Over on OMP ................... 2664
C901670010 Number of TFP Received .............................. 2664
C901670011 Rate of Mtp3 Link Occupy............................. 2664
C901670012 Number of SCCP Message Signal Unit Received.......................................................................... 2665
Sent ............................................................................ 2665
C901670014 Number of A2SP Message Signal Unit Received.......................................................................... 2665
Sent ............................................................................ 2666
C901670016 Number of Stm Message Signal Unit Received.......................................................................... 2666
C901670017 Number of Stm Message Signal Unit Sent......... 2666
C901670018 Number of Sltm Message Signal Unit Received.......................................................................... 2666
Sent ............................................................................ 2667
C901670020 Octets of SCCP SIF-SIO Received .................. 2667
C901670021 Octets of SCCP SIF-SIO Sent ........................ 2667
C901670022 Octets of MTP2 SIF-SIO Received .................. 2667
C901670023 Octets of MTP2 SIF-SIO Sent........................ 2668
C901670024 Octets of Stm SIF-SIO Received.................... 2668
C901670025 Octets of Stm SIF-SIO Sent.......................... 2668
C901670026 Octets of Sltm SIF-SIO Received ................... 2668
C901670027 Octets of Sltm SIF-SIO Sent ......................... 2669
C901670028 Number of message discarded due to Congestion ............................................................................. 2669
C901670029 Number of restrictions Level 1 ...................... 2669
C901670032 Duration of Restrictions Level 1..................... 2670
2659
C901670035 Duration of manual prohibition...................... 2671

C901670036 Number of local automatic change back ......... 2671
C901670037 Number of SL restoration ............................. 2671
C901670038 Number of Local management inhibit............. 2672
C901670039 Duration of SL inhibition due to Local management actions................................................................. 2672
C901670040 Number of remote management inhibit .......... 2672
C901670041 Duration of SL inhibition due to remote management actions................................................................. 2673
C901670042 Number of remote processor outage.............. 2673
C901670043 Duration of SL inhibition due to remote processor outage.................................................................... 2673
C901670044 Number of sending unaccess messages.......... 2674
C901670045 Number of sending flow-control discarded messages........................................................................... 2674
rate on outgoing signaling link......................................... 2674
rate on incoming signaling link ....................................... 2675
C901670048 Link type ................................................... 2676
C901670049 Number of TFA sent .................................... 2676
C901670050 Number of TFA received............................... 2676
C901670051 Number of TFC sent .................................... 2676
C901670052 Number of TFC received............................... 2677
C901670053 Number of RST sent .................................... 2677
C901670054 Number of RST received .............................. 2677
C901670055 Number of TRA sent .................................... 2677
C901670056 Number of TRA received .............................. 2678
C901670057 Number of UPU sent .................................... 2678
C901670058 Number of UPU received .............................. 2678
license ......................................................................... 2678
Overview
Message Transfer Part Level 3, MTP3 for short, implements bearer
of narrow-band messages and broad-band messages of upperlayer users. The MTP3 link measurement task takes the link as the
unit. It performs measurement of messages related to MTP3 link
management, the number of data messages received and sent,
and the number of bytes of data messages received and sent.
Statistic unit in this measurement is link.
This chapter introduces the meaning, usage, and measurement
point of MTP3 link measurement counters.
Signaling Link Out of Service
Description
2660
This counter counts the duration of the signaling link being faulty,
blocked, or not activated.
Chapter 73 MTP3 Signaling Link Statistics
Measurement
Point
Unit
During a measurement period, the counter counts the duration of

MTP3 link not in the service status.
Second
Signaling Link Out of Service
Description
This counter counts the number of the signaling link exiting the
service status.
Measurement
Point
The counter accumulates when the link status is changed from

available to unavailable.
Unit
Times
Message Signal Unit Sent
Description
This counter counts the number of MSUs sent on the signaling link.
Measurement
Point
The counter accumulates when the upper-layer user sends the

MSU message through MTP3 or MTP3 forwards the MSU message
outwards from the local office.
C901670004 Octets of
SIF-SIO Sent
Description
This counter counts the number of octets of SIF and SIO sent on
the signaling link.
Measurement
Point
The counter accumulates when the MSU message is sent on the

link (only counting the number of octets of SIF and SIO).
2661
C901670005 Number
of Message Signal Unit
Received
Description
This counter counts the number of MSUs received on the signaling

link.
Measurement
Point
The counter accumulates when the MSU message is received on

the link.
SIF-SIO Received
Description
This counter counts the number of octets of SIF and SIO received
on the signaling link.
Measurement
Point
The counter accumulates when the MSU message is received on

the link (only counting the number of octets of SIF and SIO).
C901670007 Peak Traffic of

Signaling Link
Description
During the measurement period, this counter counts the peak traffic load of the signaling link.
Because the M2PA link shares the bandwidth, precise calculation
of traffic load is not possible. The peak traffic load is calculated on
the basis of a 2 Mbps link:
Measurement unit time: 15 seconds
1. Number of bytes of messages sent within the measurement
unit time = Number of octets of SIF and SIO sent within the
measurement unit time + Number of MSUs sent within the
measurement unit time * Length of the message header
2. Number of bytes of messages received within the measurement unit time = Number of octets of SIF and SIO received
within the measurement unit time + Number of MSUs received
within the measurement unit time * Length of the message
header
2662
Note:
For 64 kbps link and broadband link, the message header's
length is 6. For 2 Mbps link and N * 64 kbps link, the message
header's length is 9.
3. Traffic load within the measurement unit time = 10000 * (Number of bytes of messages sent + Number of bytes of messages
received) * 8 / (Link bandwidth * 2 * 15)
Note:
Here, 10000 indicates , 8 indicates the number of bits of
the message's bytes, 2 indicates the receiving and the sending
are on two directions, and 15 indicates the measurement unit
time.
4. During the measurement period, the counter compares the
traffic load of each measurement unit time, and the maximum
traffic load is recorded as the peak traffic load.
Measurement
Point
Unit
During a measurement period, the counter records the peak traffic

load of the link.
C901670008 Peak Traffic

Duration of Signaling Link
Description
This counter records the duration of the signaling link being in the
status of peak traffic load within the measurement period. Like
the peak traffic load, the peak traffic duration is not precise, only
for reference.
At present, if the counter is not cleared, its value will be accumulated. If the buffer size is not unlimited, the counter's value
cannot be accumulated when its value reaches 900 seconds. If
the counter is cleared, the number of route being unavailable will
be cleared too. If the route is unavailable, then the following case
might exist and is considered normal: the number of link being
unavailable is 0 but the duration of link being unavailable is still
recorded.
Measurement
Point
Unit
This counter records the duration of the signaling link being in the
status of peak traffic load within the measurement period.
Second
2663
Change Over on OMP
Description
This counter counts the number of changeovers occurred on the

signaling link (on OMP).
Measurement
Point
When the MTP3 link exits the service and changeover is initiated
on the link, the counter accumulates.
C901670010 Number of TFP

Received
Description
This counter counts the number of transfer-prohibited messages

received on the signaling link.
Measurement
Point
The counter increments when the TFP message is received on the

link.
C901670011 Rate of Mtp3

Link Occupy
Description
This counter counts the ratio () of link bandwidth that the signaling message occupies. Because the M2PA link shares the bandwidth, precise calculation of ratio is not possible. The ratio is calculated on the basis of a 2 Mbps link, and the calculation result is
only for reference.
1. Number of bytes of messages sent = Number of octets of SIF
and SIO sent + Number of MSUs sent * Length of the message
header
2. Number of bytes of messages received = Number of octets of
SIF and SIO received + Number of MSUs received * Length of
the message header
Note:
For 64 kbps link and broadband link, the message header's
length is 6. For 2 Mbps link and N * 64 kbps link, the message
header's length is 9.
3. Link occupation ratio () = 10000 * (Number of bytes of messages sent + Number of bytes of messages received) * 8 / (Link
bandwidth * 2 * counting time)
2664
Measurement
Point
Unit
The counter counts when the request of MTP3 link performance

statistics is received.
SCCP Message Signal Unit
Received
Description
This counter counts the number of SCCP messages received on

the link.
Measurement
Point
The counter accumulates when the SCCP message is received on

the link. The counter increments when the link status is changed
from available to unavailable.
SCCP Message Signal Unit
Sent
Description
This counter counts the number of SCCP messages sent on the

link.
Measurement
Point
The counter accumulates when the SCCP message is sent on the

link.
A2SP Message Signal Unit
Received
Description
This counter counts the number of ALCAP messages received on

the link. The counter's value is not zero only for the broadband
link (ATM), for other link types, its value is always zero.
Measurement
Point
The counter accumulates when the ALCAP message is received on

the link.
2665
A2SP Message Signal Unit
Sent
Description
This counter counts the number of ALCAP messages sent on the

link. The counter's value is not zero only for the broadband link
(ATM), for other link types, its value is always zero.
Measurement
Point
The counter accumulates when the ALCAP message is sent on the

link.
Stm Message Signal Unit
Received
Description
This counter counts the number of SNM messages received on the

link.
Measurement
Point
The counter accumulates when the SNM message is received on

the link.
C901670017 Number of Stm

Message Signal Unit Sent
Description
This counter counts the number of SNM messages sent on the link.
Measurement
Point
The counter accumulates when the SNM message is sent on the

link.
Sltm Message Signal Unit
Received
Description
2666
This counter counts the number of STM messages (i.e. link test
message) received on the link.
Measurement
Point
The counter accumulates when the STM message is received on

the link.
Sltm Message Signal Unit
Sent
Description
This counter counts the number of STM messages (i.e. link test
message) sent on the link.
Measurement
Point
The counter accumulates when the STM message is sent on the

link.
SCCP SIF-SIO Received
Description
This counter counts the number of octets of SCCP SIF and SIO
received on the link.
Measurement
Point
The counter accumulates when the SCCP message is received on

the link.
SCCP SIF-SIO Sent
Description
This counter counts the number of octets of SCCP SIF and SIO
sent on the link.
Measurement
Point
The counter accumulates when the SCCP message is sent on the

link.
MTP2 SIF-SIO Received
Description
This counter counts the number of octets of ALCAP SIF and SIO
received on the link. The counter's value is not zero only for the
broadband link (ATM), for other link types, its value is always zero.
2667
Measurement
Point
The counter accumulates when the ALCAP message is received on

the link.
MTP2 SIF-SIO Sent
Description
This counter counts the number of octets of ALCAP SIF and SIO
sent on the link. The counter's value is not zero only for the broadband link (ATM), for other link types, its value is always zero.
Measurement
Point
The counter accumulates when the ALCAP message is sent on the

link.
C901670024 Octets of Stm

SIF-SIO Received
Description
This counter counts the number of octets of SNM SIF and SIO
received on the link.
Measurement
Point
The counter accumulates when the SNM message is received on

the link.
C901670025 Octets of Stm

SIF-SIO Sent
Description
This counter counts the number of octets of SNM SIF and SIO sent
on the link.
Measurement
Point
The counter accumulates when the SNM message is sent on the

link.
C901670026 Octets of Sltm

SIF-SIO Received
2668
Description
This counter counts the number of octets of SIF and SIO of the
link test message (STM) received on the link.
Measurement
Point
The counter accumulates when the STM message is received on

the link.
C901670027 Octets of Sltm

SIF-SIO Sent
Description
This counter counts the number of octets of SIF and SIO of the
link test message (STM) sent on the link.
Measurement
Point
The counter accumulates when the STM message is sent on the

link.
message discarded due to
Congestion
Description
This counter counts the number of messages discarded due to congestion. The counter's value is not zero only for ANSI standard,
for other protocol types, its value is always zero. When the function of flow control according to link level is enabled, the message
will not be discarded due to congestion.
Measurement
Point
When the MSU message is sent on the link, if the congestion level
of the link or office is higher than the message's priority, the message is discarded and the counter accumulates.
restrictions Level 1
Description
Measurement
Point
This counter counts the number of the link being at the congestion
level 1. The counter's value is not zero only for ANSI standard, for
other protocol types, its value is always zero.
The counter accumulates when the link congestion is at level 1.
Description
2669
Measurement
Point
Description
Measurement
Point
Restrictions Level 1
Description
This counter counts the duration of the link being at the congestion
Measurement
Point
The counter records the duration of the link being at the congestion
level 1 during a measurement period.
Unit
Second
Description
Measurement
Point
Unit
2670
Second
Description
Measurement
Point
Unit
Second
manual prohibition
Description
This counter counts the duration of the link being in the manual
deactivation status.
Measurement
Point
The counter records the duration of the link being in the manual
deactivation status during a measurement period.
Unit
Second
local automatic change back
Description
This counter counts the number of changebacks occurred on the

signaling link (on OMP).
Measurement
Point
When the MTP3 link is put into service and changeback is initiated
on the link, the counter accumulates.
Unit
Times
C901670037 Number of SL
restoration
Description
This counter counts the number of signaling link being restored to

be available.
Measurement
Point
The counter accumulates when the link status is changed from

unavailable to available.
Unit
Times
2671
Local management inhibit
Description
This counter counts the number of local inhibitions successfully

initiated by management entity (on OMP).
Measurement
Point
When the management entity initiates local inhibition successfully,

the counter accumulates.
Unit
Times
SL inhibition due to Local
management actions
Description
This counter counts the duration from local inhibition being initiated successfully and local uninhibition being initiated successfully
(on OMP).
Measurement
Point
When the local inhibition is initiated successfully, the counter starts

counting. When the local uninhibition succeeds, the counter stops
counting and records the duration.
Unit
Second
remote management inhibit
Description
This counter counts the number of remote inhibitions successfully

initiated by management entity (on OMP).
Measurement
Point
When the management entity initiates remote inhibition successfully, the counter accumulates.
Unit
2672
Times
SL inhibition due to remote
management actions
Description
This counter counts the duration from remote inhibition being initiated successfully and remote uninhibition being initiated successfully (on OMP).
Measurement
Point
When the remote inhibition is initiated successfully, the counter

starts counting. When the remote uninhibition succeeds, the
counter stops counting and records the duration.
Unit
Second
remote processor outage
Description
Measurement
Point
Unit
This counter counts the number of the remote processor being

faulty.
This counter accumulates when the remote processor is faulty.
Times
SL inhibition due to remote
processor outage
Description
Measurement
Point
Unit
This counter counts the duration of the remote processor being

faulty.
This counter counts when the remote processor is faulty.
Second
2673
sending unaccess messages
Description
This counter counts the number of transfer-prohibited messages

(TFP) on the link.
Measurement
Point
The counter accumulates when the TFP message is sent on the

link.
Unit
Times
C901670045 Number
of sending flow-control
discarded messages
Description
This counter counts the number of flow-control discarded messages sent on the link.
Measurement
Point
The counter accumulates when the flow-control discarded messages is sent on the link.
C901670046 Ten thousand

multiple bandwidth
occupancy rate on outgoing
signaling link
Description
This counter counts the ratio () of bandwidth occupied by the

outgoing link.
Outgoing link occupation ratio () = 10000 * Number of bytes of
messages sent * 8 / (Link bandwidth * Measurement time)
Note:
Here, 10000 indicates , multiplication of 8 indicates conversion
from byte to bit, the link bandwidth unit is bit/s, and the measurement time unit is s.
Number of bytes of messages sent = Number of octets of SIF and
SIO sent + Number of MSUs sent * Length of the message header
2674
Note:
For 64 kbps link and broadband link, the message header's length
is 6. For 2 Mbps link and N * 64 kbps link, the message header's
length is 9.
The link bandwidth is described as follows:
Measurement
Point
For 64 kbps link, N * 64 kbps link, and 2 Mbps link database

configuration, the bandwidth means the number of timeslots.
In other words, if the configured bandwidth is n, the bandwidth
is n * 64000 bps.
For broadband link, the bandwidth unit is kbps. In other words,

if the bandwidth obtained from the database is n, the bandwidth is n * 1000 bps.

C901670047 Ten thousand

multiple bandwidth
occupancy rate on incoming
signaling link
Description
This counter counts the ratio () of bandwidth occupied by the

incoming link.
Incoming link occupation ratio () = 10000 * Number of bytes of
messages received * 8 / (Link bandwidth * Measurement time)
Number of bytes of messages received = Number of octets of SIF
and SIO received + Number of MSUs received * Length of the
message header
Note:
For 64 kbps link and broadband link, the message header's length
is 6. For 2 Mbps link and N * 64 kbps link, the message header's
length is 9.
Measurement
Point

2675
C901670048 Link type

Description
This counter records the link type.
If the link or link group is 64 kbps, the corresponding value is

1, represented as Narrow 64K Signaling.
If the link or link group is n * 64 kbps, the corresponding value

is 2, represented as Narrow N*64K Signaling.
If the link or link group is 2 Mbps, the corresponding value is

3, represented as Narrow 2M Signaling.
If the link or link group is broadband, the corresponding value

is 4, represented as ATM Signaling - SSCS.
If the link or link group is M2PA, the corresponding value is 5,

represented as M2PA Signaling.
C901670049 Number of TFA

sent
Description
This counter counts the number of TFA messages sent on the link.
Measurement
Point
The counter accumulates when the TFA message is sent on the

link.
C901670050 Number of TFA

received
Description
This counter counts the number of TFA messages received on the

link.
Measurement
Point
The counter accumulates when the TFA message is received on

the link.
TFC sent
2676
Description
This counter counts the number of TFC messages sent on the link.
Measurement
Point
The counter accumulates when the TFC message is sent on the

link.
TFC received
Description
This counter counts the number of TFC messages received on the

link.
Measurement
Point
The counter accumulates when the TFC message is received on

the link.
RST sent
Description
This counter counts the number of RST messages (i.e. route-set

test message) sent on the link.
Measurement
Point
The counter accumulates when the RST message is sent on the

link.
RST received
Description
This counter counts the number of RST messages (i.e. route-set

test message) received on the link.
Measurement
Point
The counter accumulates when the RST message is received on

the link.
TRA sent
Description
This counter counts the number of service-restart-allowed messages (TRA) sent on the link.
Measurement
Point
The counter accumulates when the TRA message is sent on the

link.
2677
TRA received
Description
This counter counts the number of service-restart-allowed messages (TRA) received on the link.
Measurement
Point
The counter accumulates when the TRA message is received on

the link.
UPU sent
Description
This counter counts the number of user-part-unavailable messages (UPU) sent on the link.
Measurement
Point
The counter accumulates when the UPU message is sent on the

link.
UPU received
Description
This counter counts the number of user-part-unavailable messages (UPU) received on the link.
Measurement
Point
The counter accumulates when the UPU message is received on

the link.
message discard controlled
by license
Description
2678
When the number of forwarding message exceeds the maximum

forwarding times allowed in Licence, the overload control function
decides whether the subsequent messages will be discarded. If a
message should be discarded, then the message will not be forwarded outwards from the local office and is directly discarded,
and the counter accumulates.
Measurement
Point

forwarding times allowed in Licence, call the overload control function to decide whether the subsequent messages will be discarded.
2679
2680
Chapter
74
M3UA Performance
Statistics
Table of Contents
Overview...................................................................... 2682
C901680001 Number of data message sent ...................... 2682
C901680002 Number of data message received................. 2682
C901680003 Number of ASP Up message sent .................. 2683
C901680004 Number of ASP Up message received............. 2683
C901680005 Number of ASP Up Ack message received......... 2683
C901680006 Number of ASP Up Ack message sent ............ 2683
C901680007 Number of ASP Down message sent .............. 2684
C901680008 Number of ASP Down message received......... 2684
C901680009 Number of ASP Down Ack message received.......................................................................... 2684
C901680010 Number of ASP Down Ack message sent......... 2684
C901680011 Number of ASP Inactive message sent ........... 2685
C901680012 Number of ASP Inactive message received.......................................................................... 2685
C901680013 Number of ASP Inactive Ack message received.......................................................................... 2685
sent............................................................................. 2686
C901680015 Number of ASP Active message sent.............. 2686
C901680016 Number of ASP Active message received......... 2686
C901680017 Number of ASP Active Ack message received.......................................................................... 2686
C901680018 Number of ASP Active Ack message sent......... 2687
C901680019 Number of DAUD message sent .................... 2687
C901680020 Number of SCON message received............... 2687
C901680021 Number of DAVA message received ............... 2688
C901680022 Number of DUNA message received............... 2688
C901680023 Number of invalid message received.............. 2688
C901680024 Number of MGMT message sent .................... 2688
C901680025 Number of MGMT message received .............. 2689
C901680026 Number of Heartbeat message received ......... 2689
C901680027 Number of HeartBeat Ack message sent......... 2689
C901680028 Bytes of data message received .................... 2689
C901680029 Bytes of data message transmitted ............... 2690
C901680030 Bytes of MGMT message sent ....................... 2690
C901680031 Bytes of MGMT message received.................. 2690
C901680032 Counts of discarding messages by Flow Control .............................................................................. 2691
license ......................................................................... 2691
C901680034 Bytes of all message sent............................. 2691
C901680035 Bytes of all message received ....................... 2692
2681
C901680036
C901680037
C901680038
C901680039
Number
Number
Number
Number
of
of
of
of
ERROR message sent................... 2692

ERROR message received ............. 2692
NOTIFY message sent .................. 2692
NOTIFY message received ............ 2693
Overview
M3UA is short for MTP3-User Adaptation Layer. M3UA measurement performs measurement of messages related to M3UA link
management, the number of data messages received and sent,
and the number of bytes of data messages received and sent.
Statistic unit in this measurement is SCTP.
It supports IP bearer of messages of some SS7 MTP3 users.
It supports seamless operations of peer-layer MTP3 user protocols.
It supports MTP3 nework management functions.

point of M3UA performance measurement counters.
data message sent
Description
Measurement
Point
Unit
This counter counts the number of data messages sent.

The counter accumulates when the data message is sent.
Times
data message received
Description
Measurement
Point
Unit
2682
This counter counts the number of data messages received.

The counter accumulates when the data message is received.
Times
Chapter 74 M3UA Performance Statistics
ASP Up message sent
Description
Measurement
Point
Unit
This counter counts the number of ASP Up messages sent.

The counter accumulates when the ASP Up message is sent.
Times
ASP Up message received
Description
Measurement
Point
Unit
This counter counts the number of ASP Up messages received.

The counter accumulates when the ASP Up message is received.
Times
ASP Up Ack message
received
Description
This counter counts the number of ASP Up Ack messages received.
Measurement
Point
The counter accumulates when the ASP Up Ack message is received.
Unit
Times
ASP Up Ack message sent
Description
Measurement
Point
Unit
This counter counts the number of ASP Up Ack messages sent.

The counter accumulates when the ASP Up Ack message is sent.
Times
2683
ASP Down message sent
Description
Measurement
Point
Unit
This counter counts the number of ASP Down messages sent.

The counter accumulates when the ASP Down message is sent.
Times
C901680008 Number of ASP

Down message received
Description
This counter counts the number of ASP Down messages received.
Measurement
Point
The counter accumulates when the ASP Down message is received.
Unit
Times
ASP Down Ack message
received
Description
This counter counts the number of ASP Down Ack messages received.
Measurement
Point
The counter accumulates when the ASP Down Ack message is received.
Unit
Times
ASP Down Ack message
sent
2684
Description
This counter counts the number of ASP Down Ack messages sent.
Measurement
Point
The counter accumulates when the ASP Down Ack message is sent.
Unit
Times
ASP Inactive message sent
Description
Measurement
Point
Unit
This counter counts the number of ASP Inactive messages sent.

The counter accumulates when the ASP Inactive message is sent.
Times
ASP Inactive message
received
Description
This counter counts the number of ASP Inactive messages received.
Measurement
Point
The counter accumulates when the ASP Inactive message is received.
Unit
Times
ASP Inactive Ack message
received
Description
This counter counts the number of ASP Inactive Ack messages

received.
Measurement
Point
The counter accumulates when the ASP Inactive Ack message is

received.
Unit
Times
2685
ASP Inactive Ack message
sent
Description
This counter counts the number of ASP Inactive Ack messages

sent.
Measurement
Point
The counter accumulates when the ASP Inactive Ack message is

sent.
Unit
Times
ASP Active message sent
Description
Measurement
Point
Unit
This counter counts the number of ASP Active messages sent.

The counter accumulates when the ASP Active message is sent.
Times
C901680016 Number of ASP

Active message received
Description
This counter counts the number of ASP Active messages received.
Measurement
Point
The counter accumulates when the ASP Active message is received.
Unit
Times
ASP Active Ack message
received
Description
2686
This counter counts the number of ASP Active Ack messages received.
Measurement
Point
Unit
The counter accumulates when the ASP Active Ack message is received.
Times
ASP Active Ack message
sent
Description
This counter counts the number of ASP Active Ack messages sent.
Measurement
Point
The counter accumulates when the ASP Active Ack message is

sent.
Unit
Times
DAUD message sent
Description
Measurement
Point
Unit
This counter counts the number of DAUD messages sent.

The counter accumulates when the DAUD message is sent.
Times
SCON message received
Description
Measurement
Point
Unit
This counter counts the number of SCON messages received.

The counter accumulates when the SCON message is received.
Times
2687
DAVA message received
Description
Measurement
Point
Unit
This counter counts the number of DAVA messages received.

The counter accumulates when the DAVA message is received.
Times
DUNA message received
Description
Measurement
Point
Unit
This counter counts the number of DUNA messages received.

The counter accumulates when the DUNA message is received.
Times
invalid message received
Description
This counter counts the number of invalid data message received.
Measurement
Point
The counter counts when the key information carried in the message is incorrect.
Unit
Times
MGMT message sent
Description
2688
This counter counts the number of MGMT messages sent.
Measurement
Point
The counter accumulates when the MGMT message is sent.
MGMT message received
Description
Measurement
Point
This counter counts the number of MGMT messages received.

The counter accumulates when the MGMT message is received.
Heartbeat message received
Description
This counter counts the number of HeartBeat messages received.
Measurement
Point
The counter accumulates when the HeartBeat message is received.
Unit
Times
HeartBeat Ack message
sent
Description
Measurement
Point
Unit
This counter counts the number of HeartBeatAck messages sent.

The counter accumulates when the HeartBeatAck message is sent.
Times
C901680028 Bytes of data

message received
Description
Measurement
Point
This counter counts the number of bytes of DATA messages received by M3UA.
The counter counts when M3UA receives the DATA message.
2689
Unit
Byte
C901680029 Bytes of data

message transmitted
Description
Measurement
Point
Unit
This counter counts the number of bytes of DATA messages sent

by M3UA.
The counter counts when M3UA sends the DATA message.
Byte
C901680030 Bytes of MGMT

message sent
Description
This counter counts the number of bytes of MGMT messages sent.
Measurement
Point
The counter counts when the NTFY message or the ERR message
is sent.
Unit
Byte
C901680031 Bytes of MGMT

message received
Description
This counter counts the number of bytes of management messages received.
Measurement
Point
The counter counts when the NTFY message or the ERR message
is received.
Unit
2690
Byte
C901680032 Counts of
discarding messages by
Flow Control
Description
When a message is discarded due to flow control, the counter's

value increments. The measurement is performed according to
SCTP.
Measurement
Point
The counter counts when a message is discarded due to flow control.
by license
Description

message should be discarded, then the message will not be forwarded outwards from the local office and is directly discarded.
The condition is reported to OAM and the counter accumulates.
Measurement
Point

C901680034 Bytes of all

message sent
Description
Unit
This counter counts the bytes of all messages sent on SCTP, including data message, management message, ASPSM message,
ASPTM message, and MGMT message.
Byte
2691
C901680035 Bytes of all

message received
Description
Unit
This counter counts the bytes of all messages received on SCTP,

including data message, management message, ASPSM message,
ASPTM message, and MGMT message.
Byte
ERROR message sent
Description
Measurement
Point
Unit
This counter counts the number of ERROR messages sent.

The counter accumulates when the ERROR message is sent.
Times
ERROR message received
Description
Measurement
Point
Unit
This counter counts the number of ERROR messages received.

The counter accumulates when the ERROR message is received.
Times
NOTIFY message sent
Description
Measurement
Point
Unit
2692
This counter counts the number of NOTIFY messages sent.

The counter accumulates when the NOTIFY message is sent.
Times
NOTIFY message received
Description
Measurement
Point
Unit
This counter counts the number of NOTIFY messages received.

The counter accumulates when the NOTIFY message is received.
Times
2693
2694
Chapter
75
SCCP Performance
Statistics
Table of Contents
Overview...................................................................... 2696
C901690001 Number of UDT Sent ................................... 2696
C901690002 Number of UDT Received ............................. 2697
C901690003 Number of UDTS Sent ................................. 2697
C901690004 Number of UDTS Received ........................... 2697
C901690005 Number of ERR Sent ................................... 2697
C901690006 Number of ERR Received.............................. 2698
C901690007 Number of SSP Sent.................................... 2698
C901690008 Number of SSP Received.............................. 2698
C901690009 Number of RSR Sent ................................... 2698
C901690010 Number of RSR Received ............................. 2699
C901690011 Number of RSC Sent ................................... 2699
C901690012 Number of RSC Received ............................. 2699
C901690013 Number of UnAnswered SST......................... 2699
C901690014 Number of CREF Sent .................................. 2700
C901690015 Number of CREF Received ............................ 2700
C901690016 Number of XUDT Sent ................................. 2700
C901690017 Number of XUDT Received ........................... 2700
C901690018 Number of XUDTS Sent................................ 2701
C901690019 Number of XUDTS Received.......................... 2701
C901690020 Number of LUDT Sent.................................. 2701
C901690021 Number of LUDT Received ............................ 2701
C901690022 Number of LUDTS Sent ................................ 2702
C901690023 Number of LUDTS Received .......................... 2702
C901690024 Number of DT1 Received.............................. 2702
C901690025 Number of DT1 Sent.................................... 2702
C901690026 Number of DT2 Received.............................. 2703
C901690027 Number of DT2 Sent.................................... 2703
C901690028 Number of CONNECTREQ Sent...................... 2703
C901690029 Number of CONNECTCON Received ............... 2703
C901690030 Number of CONNECTIND Received ................ 2704
C901690031 Number of CONNECTRES Sent ...................... 2704
C901690032 Number of DISCONNECTREQ Sent................. 2704
C901690033 Number of DISCONNECTIND received............ 2704
C901690034 Number of CR Sent ..................................... 2705
C901690035 Number of CR Received ............................... 2705
C901690036 Number of CC Sent ..................................... 2705
C901690037 Number of CC Received ............................... 2705
C901690038 Number of UDT gtt...................................... 2705
C901690039 Number of UDTS gtt .................................... 2706
C901690040 Number of XUDT gtt .................................... 2706
C901690041 Number of XUDTS gtt .................................. 2706
C901690042 Number of LUDT gtt .................................... 2706
2695
C901690043 Number of LUDTS gtt .................................. 2707

C901690044 Number of UDT gtt failure ............................ 2707
C901690045 Number of UDTS gtt failure .......................... 2707
C901690046 Number of XUDT gtt failure .......................... 2707
C901690047 Number of XUDTS gtt failure ........................ 2708
C901690048 Number of LUDT gtt failure........................... 2708
C901690049 Number of LUDTS gtt failure......................... 2708
C901690050 Number of CR gtt........................................ 2708
C901690051 Number of CR gtt failure .............................. 2709
C901690052 Number of gtt Count ................................... 2709
C901690053 Number of gtt failure ................................... 2709
C901690054 Number of N_UnitDataReq LongUserData gtt
failure .......................................................................... 2709
C901690055 Number of UPU received .............................. 2710
C901690056 Number of SSA received .............................. 2710
C901690057 Number of SSA sent .................................... 2710
C901690058 Number of SST received .............................. 2710
C901690059 Number of SST sent .................................... 2711
Overview
SCCP is short for Signalling Connection Control Part. It works
with MTP3 to implement the network-layer function of Signaling
System No.7 (SS7 ), providing data transmission service which is
either connectionless or connection-oriented. SCCP performance
measurement takes module as the measurement unit. It measures the following information related to connectionless service
or connection-oriented service: the number of received or sent
data messages, the number of GT translations, and the number of
GT translation failures.
point of SCCP performance measurement counters.
UDT Sent
Description
Measurement
Point
Unit
2696
This counter counts the number of UDTs sent by SCCP of the local
office.
The counter accumulates when SCCP sends UDT.
Times
Chapter 75 SCCP Performance Statistics
UDT Received
Description
Measurement
Point
Unit
This counter counts the number of UDTs received by SCCP of the

local office.
The counter accumulates when SCCP receives UDT.
Times
UDTS Sent
Description
Measurement
Point
Unit
This counter counts the number of UDTSs sent by SCCP of the local
office.
The counter accumulates when SCCP sends UDTS.
Times
UDTS Received
Description
Measurement
Point
Unit
This counter counts the number of UDTSs received by SCCP of the

local office.
The counter accumulates when SCCP receives UDTS.
Times
ERR Sent
Description
This counter counts the number of ERRs sent by SCCP of the local
office.
2697
Measurement
Point
The counter accumulates when SCCP sends ERR.
ERR Received
Description
Measurement
Point
This counter counts the number of ERRs received by SCCP of the

local office.
The counter accumulates when SCCP receives ERR.
SSP Sent
Description
Measurement
Point
This counter counts the number of SSPs sent by SCCP of the local
office.
The counter accumulates when SCCP sends SSP.
SSP Received
Description
Measurement
Point
This counter counts the number of SSPs received by SCCP of the

local office.
The counter accumulates when SCCP receives SSP.
RSR Sent
Description
2698
This counter counts the number of RSRs sent by SCCP of the local
office.
Measurement
Point
The counter accumulates when SCCP sends RSR.
RSR Received
Description
Measurement
Point
This counter counts the number of RSRs received by SCCP of the

local office.
The counter accumulates when SCCP receives RSR.
RSC Sent
Description
Measurement
Point
This counter counts the number of RSCs sent by SCCP of the local
office.
The counter accumulates when SCCP sends RSC.
RSC Received
Description
Measurement
Point
This counter counts the number of RSCs received by SCCP of the

local office.
The counter accumulates when SCCP receives RSC.
UnAnswered SST
Description
This counter counts the number of SSTs that does not receive the
response. The SST is sent by SCCP of the local office.
Measurement
Point
The counter accumulates when the SST sent by SCCP does not
receive the response.
2699
CREF Sent
Description
Measurement
Point
This counter counts the number of CREFs sent by SCCP of the local
office.
The counter accumulates when SCCP sends CREF.
CREF Received
Description
Measurement
Point
This counter counts the number of CREFs received by SCCP of the

local office.
The counter accumulates when SCCP receives CREF.
XUDT Sent
Description
Measurement
Point
This counter counts the number of XUDTs sent by SCCP of the local
office.
The counter accumulates when SCCP sends XUDT.
XUDT Received
Description
2700
This counter counts the number of XUDTs received by SCCP of the

local office.
Measurement
Point
The counter accumulates when SCCP receives XUDT.
XUDTS Sent
Description
Measurement
Point
This counter counts the number of XUDTSs sent by SCCP of the

local office.
The counter accumulates when SCCP sends XUDTS.
XUDTS Received
Description
Measurement
Point
This counter counts the number of XUDTSs received by SCCP of

the local office.
The counter accumulates when SCCP receives XUDTS.
LUDT Sent
Description
Measurement
Point
This counter counts the number of LUDTs sent by SCCP of the local
office.
The counter accumulates when SCCP sends LUDT.
LUDT Received
Description
This counter counts the number of LUDTs received by SCCP of the

local office.
2701
Measurement
Point
The counter accumulates when SCCP receives LUDT.
LUDTS Sent
Description
Measurement
Point
This counter counts the number of LUDTSs sent by SCCP of the

local office.
The counter accumulates when SCCP sends LUDTS.
LUDTS Received
Description
Measurement
Point
This counter counts the number of LUDTSs received by SCCP of

the local office.
The counter accumulates when SCCP receives LUDTS.
C901690024 Number of DT1

Received
Description
Measurement
Point
This counter counts the number of DT1s received by SCCP of the

local office.
The counter accumulates when SCCP receives DT1.

Sent
Description
2702
This counter counts the number of DT1s sent by SCCP of the local
office.
Measurement
Point
The counter accumulates when SCCP sends DT1.

Received
Description
Measurement
Point
This counter counts the number of DT2s received by SCCP of the

local office.
The counter accumulates when SCCP receives DT2.

Sent
Description
Measurement
Point
This counter counts the number of DT2s sent by SCCP of the local
office.
The counter accumulates when SCCP sends DT2.
CONNECTREQ Sent
Description
Measurement
Point
This counter counts the number of sending CONNECTREQ to SCCP.

The counter accumulates when SCCP receives CONNECTREQ.
CONNECTCON Received
Description
This counter counts the number of sending CONNECTCON to SCCP.
2703
Measurement
Point
This counter accumulates when SCCP receives CONNECTCON.
CONNECTIND Received
Description
Measurement
Point
This counter counts the number of sending CONNECTRES to SCCP.

The counter accumulates when SCCP receives CONNECTRES.
CONNECTRES Sent
Description
Measurement
Point
This counter counts the number of sending CONNECTRES to SCCP.

The counter accumulates when SCCP receives CONNECTRES.
DISCONNECTREQ Sent
Description
This counter counts the number of sending DISCONNECTREQ to

SCCP.
Measurement
Point
The counter accumulates when SCCP receives DISCONNECTREQ.
DISCONNECTIND received
2704
Description
This counter counts the number of DISCONNECTINDs received

from SCCP.
Measurement
Point
This counter accumulates when DISCONNECTIND is received from

SCCP.
C901690034 Number of CR
Sent
Description
Measurement
Point
This counter counts the number of CRs sent by SCCP of the local
office.
The counter accumulates when SCCP sends CR.
Received
Description
Measurement
Point
This counter counts the number of CRs received by SCCP of the

local office.
The counter accumulates when SCCP receives CR.
C901690036 Number of CC
Sent
Description
Measurement
Point
This counter counts the number of CCs sent by SCCP of the local
office.
The counter accumulates when SCCP sends CC.
C901690037 Number of CC
Received
Description
Measurement
Point
This counter counts the number of CCs received by SCCP of the

local office.
The counter accumulates when SCCP receives CC.
UDT gtt
Description
This counter counts the number of UDT GT translations.
2705
Measurement
Point
The counter when uplink/downlink UDT GT translation is performed.
UDTS gtt
Description
Measurement
Point
This counter counts the number of UDTS GT translations.

The counter when uplink/downlink UDTS GT translation is performed.
XUDT gtt
Description
Measurement
Point
This counter counts the number of XUDT GT translations.

The counter when uplink/downlink XUDT GT translation is performed.
XUDTS gtt
Description
Measurement
Point
This counter counts the number of XUDTS GT translations.

The counter when uplink/downlink XUDTS GT translation is performed.
LUDT gtt
Description
Measurement
Point
2706
This counter counts the number of LUDT GT translations.

The counter when uplink/downlink LUDT GT translation is performed.
LUDTS gtt
Description
Measurement
Point
This counter counts the number of LUDTS GT translations.

The counter when uplink/downlink LUDTS GT translation is performed.
UDT gtt failure
Description
Measurement
Point
Unit
This counter counts the number of UDT GT translation failures.

The counter counts when uplink/downlink UDT GT translation fails.
Times
UDTS gtt failure
Description
Measurement
Point
Unit
This counter counts the number of UDTS GT translation failures.

The counter counts when uplink/downlink UDTS GT translation
fails.
Times
XUDT gtt failure
Description
Measurement
Point
This counter counts the number of XUDT GT translation failures.

The counter counts when uplink/downlink XUDT GT translation
fails.
2707
XUDTS gtt failure
Description
This counter counts the number of XUDTS GT translation failures.
Measurement
Point
The counter counts when uplink/downlink XUDTS GT translation

fails.
Unit
Times
LUDT gtt failure
Description
Measurement
Point
Unit
This counter counts the number of LUDT GT translation failures.

The counter counts when uplink/downlink LUDT GT translation
fails.
Times
LUDTS gtt failure
Description
This counter counts the number of LUDTS GT translation failures.
Measurement
Point
The counter counts when uplink/downlink LUDTS GT translation

fails.
Unit
Times
gtt
Description
Measurement
Point
Unit
2708
This counter counts the number of CR GT translations.

The counter when uplink/downlink CR GT translation is performed.
Times
gtt failure
Description
Measurement
Point
Unit
This counter counts the number of CR GT translation failures.

The counter counts when uplink/downlink CR GT translation fails.
Times
C901690052 Number of gtt

Count
Description
Measurement
Point
This counter counts the number of GT translations.

The counter counts when GT translation is performed.
C901690053 Number of gtt

failure
Description
Measurement
Point
Unit
This counter counts the number of GT translation failures.

The counter counts when GT translation fails.
Times
C901690054 Number
of N_UnitDataReq
LongUserData gtt failure
Description
This counter counts the number of failures of GT translation of

downlink N_UnitDataReq long user message.
Measurement
Point
The counter counts when the GT translation of downlink N_UnitDataReq long user message fails.
Unit
Times
2709
UPU received
Description
Measurement
Point
This counter counts the number of UPUs received by SCCP of the

local office.
The counter accumulates when SCCP receives UPU.
SSA received
Description
Measurement
Point
This counter counts the number of SSAs received by SCCP of the

local office.
The counter accumulates when SCCP receives SSA.
SSA sent
Description
Measurement
Point
This counter counts the number of SSAs sent by SCCP of the local
office.
The counter accumulates when SCCP sends SSA.
SST received
Description
2710
This counter counts the number of SSTs received by SCCP of the

local office.
Measurement
Point
The counter accumulates when SCCP receives SST.
SST sent
Description
Measurement
Point
This counter counts the number of SSTs sent by SCCP of the local
office.
The counter accumulates when SCCP sends SST.
2711
2712
Chapter
76
MTP3 Signaling Link Set

Statistics
Table of Contents
Overview...................................................................... 2713
C901700001 Duration of Signaling Link Set Out of Service ............................................................................. 2713
C901700002 Times of Signaling Link Set Out of Service ............................................................................. 2714
C901700003 Number of Available Signaling Link................ 2714
C901700004 Linkset type ............................................... 2714
Overview
Message Transfer Part Level 3, MTP3 for short, implements bearer
of narrow-band messages and broad-band messages of upperlayer users. This meaurement takes link set as the unit. It performs measurement of the following information: duration of link
set being unavailable, number of link sets being unavailable, and
number of links available. A signaling link set is available so long
as it has one link available. If all links in a signaling link set are
unavailable, the signaling link set is unavailable.
point of MTP3 signaling link set statistic measurement.
Signaling Link Set Out of
Service
Description
This counter counts the number of all links being available in the
signaling link set.
Measurement
Point
When the signaling link set's status changes from at least one link
being available to all links being unavailable, the counter increments.
Unit
Times
2713
C901700002 Times of
Signaling Link Set Out of
Service
Description
This counter counts the duration of all links being available in the
signaling link set.
Measurement
Point
During a measurement period, the counter starts counting when

all links in the signaling link set become unavailable and stops
counting once the signaling link set has a link available.
Unit
Second
Available Signaling Link
Description
This counter counts the number of available signaling links in the

signaling link set, including the signaling link currently being used.
Measurement
Point
This counter counts the number of available signaling links in the

signaling link set, including the signaling link currently being used.
C901700004 Linkset type

Description
2714
There are five link set types:
64 kbps signaling link set
n * 64 kbps signaling link set
2 Mbps signaling link set
Broadband signaling link set
M2PA signaling link set
Chapter
77
M3UA Error Statistics

Table of Contents
Overview...................................................................... 2716
C901710001 Invalid Version(T) ....................................... 2716
C901710002 Unsupported Message Class(T) ..................... 2716
C901710003 Unsupported Message Type(T) ...................... 2717
C901710004 Unexpected Message(T)............................... 2717
C901710005 Unsupported Traffic Mode Type(T) ................. 2717
C901710006 Invalid Routing Context(T) ........................... 2717
C901710007 Protocol Error(T)......................................... 2718
C901710008 Invalid Message Type(T) .............................. 2718
C901710009 Number of error message sent...................... 2718
C901710010 Invalid Version(R) ....................................... 2718
C901710011 Unsupported Message Class(R) ..................... 2719
C901710012 Unsupported Message Type(R)...................... 2719
C901710013 Unexpected Message(R) .............................. 2719
C901710014 Unsupported Traffic Mode Type(R) ................. 2719
C901710015 Invalid Routing Context(R) ........................... 2720
C901710016 Protocol Error(R) ........................................ 2720
C901710017 Invalid Message Type(R) .............................. 2720
C901710018 Number of error message received ................ 2720
C901710019 Unknown Remote User ................................ 2721
C901710020 Unequipped Remote User ............................. 2721
C901710021 Inaccessible Remote User ............................ 2721
C901710022 Number of DUPU message received ............... 2721
C901710023 Invalid Net APPEARANCE(T) ......................... 2722
C901710024 Invalid Net APPEARANCE(R) ......................... 2722
C901710025 Number of DUPU message sent which cause is
unknown ...................................................................... 2722
Unequipped Remote User ............................................... 2723
Inaccessible Remote User ............................................... 2723
C901710028 Number of DUPU message sent..................... 2723
license ......................................................................... 2724
C901710030 Sending invalid stream ID ............................ 2724
C901710031 Sending refuse error, reason is management
blocking ....................................................................... 2724
C901710032 Sending required ASP ID.............................. 2725
C901710033 Sending invalid ASP ID ................................ 2725
C901710034 Sending invalid parameter value ................... 2725
C901710035 Sending parameter field error ....................... 2725
C901710036 Sending unexpected parameter error............. 2726
C901710037 Sending destination status unknown.............. 2726
C901710038 Sending missing parameter error .................. 2726
C901710039 Sending no configured AS for ASP ................. 2726
C901710040 Receiving invalid stream ID .......................... 2727
2715
C901710041 Receiving refuse error, reason is management

blocking ....................................................................... 2727
C901710042 Receiving required ASP ID............................ 2727
C901710043 Receiving invalid ASP ID .............................. 2727
C901710044 Receiving invalid parameter value ................. 2728
C901710045 Receiving parameter field error ..................... 2728
C901710046 Receiving unexpected parameter error........... 2728
C901710047 Receiving destination status unknown............ 2728
C901710048 Receiving missing parameter error ................ 2729
C901710049 Receiving no configured AS for ASP ............... 2729
Overview
M3UA is short for MTP3-User Adaptation Layer. It supports IP
bearer of messages of some SS7 MTP3 users, seamless operations
of peer-layer MTP3 user protocols, and MTP3 nework management
functions. The M3UA error statistics task performs measurement
of various errors of M3UA.
point of M3UA error statistic measurement counters.
C901710001 Invalid
Version(T)
Description
This counter counts when an Error message is sent outwards from

the local office, with the error code of "Invalid Version".
Measurement
Point
The counter accumulates when an Error message with the error

code of "Invalid Version" is sent outwards from the local office.
C901710002 Unsupported
Message Class(T)
2716
Description

the local office, with the error code of "Unsupported Message
Class".
Measurement
Point

code of "Unsupported Message Class" is sent outwards from the
local office.
Chapter 77 M3UA Error Statistics
Message Type(T)
Description

the local office, with the error code of "Unsupported Message
Type".
Measurement
Point

code of "Unsupported Message Type" is sent outwards from the
local office.
C901710004 Unexpected
Message(T)
Description

the local office, with the error code of "Unexpected Message".
Measurement
Point

code of "Unexpected Message" is sent outwards from the local office.
Traffic Mode Type(T)
Description

the local office, with the error code of "Unsupported Traffic Mode".
Measurement
Point

code of "Unsupported Traffic Mode" is sent outwards from the local
office.
C901710006 Invalid Routing

Context(T)
Description

the local office, with the error code of "Invalid Routing Context".
Measurement
Point

code of "Invalid Routing Context" is sent outwards from the local
office.
2717
C901710007 Protocol
Error(T)
Description

the local office, with the error code of "Protocol Error".
Measurement
Point

code of "Protocol Error" is sent outwards from the local office.
C901710008 Invalid
Message Type(T)
Description
Measurement
Point
This counter counts the number of invalid message types sent. It

is same as the counter "Unsupported Message Type(T)".
The counter counts when the message type sent is invalid.
error message sent
Description
This counter counts the number of error messages sent outwards

from the local office.
Measurement
Point
The counter accumulates when the error message is sent outwards

from the local office.
C901710010 Invalid
Version(R)
2718
Description
This counter counts when an Error message is received, with the

error code of "Invalid Version".
Measurement
Point

code of "Invalid Version" is received.
Message Class(R)
Description

error code of "Unsupported Message Class".
Measurement
Point

code of "Unsupported Message Class" is received.
Message Type(R)
Description

error code of "Unsupported Message Type".
Measurement
Point

code of "Unsupported Message Type" is received.
C901710013 Unexpected
Message(R)
Description

error code of "Unexpected Message".
Measurement
Point

code of "Unexpected Message" is received.
Traffic Mode Type(R)
Description

error code of "Unsupported Traffic Mode".
Measurement
Point

code of "Unsupported Traffic Mode" is received.
2719
C901710015 Invalid Routing

Context(R)
Description

error code of "Invalid Routing Context".
Measurement
Point
The counter accumulates when an invalid routing context message

is received.
C901710016 Protocol
Error(R)
Description

error code of "Protocol Error".
Measurement
Point

code of "Protocol Error" is received.
C901710017 Invalid
Message Type(R)
Description
Measurement
Point
This counter counts the number of invalid message types received.

It is same as the counter "Unsupported Message Type(R)".
The counter counts when the message type received is invalid.
error message received
Description
Measurement
Point
Unit
2720
This counter counts the number of error messages received.

The counter accumulates when the error message is received.
Times
C901710019 Unknown
Remote User
Description
This counter counts when a DUPU message is received, with the

indication of "Unknown".
Measurement
Point
The counter accumulates when a DUPU message with the indication of "Unknown" is received.
C901710020 Unequipped
Remote User
Description

indication of "Unequipped Remote User".
Measurement
Point
The counter accumulates when a DUPU message with the indication of "Unequipped Remote User" is received.
C901710021 Inaccessible
Remote User
Description

indication of "Inaccessible Remote User".
Measurement
Point
The counter accumulates when a DUPU message with the indication of "Inaccessible Remote User" is received.
DUPU message received
Description
Measurement
Point
Unit
This counter counts the number of DUPU messages received.

The counter accumulates when the DUPU message is received.
Times
2721
C901710023 Invalid Net

APPEARANCE(T)
Description

the local office, with the error code of "Invalid Network Appearance".
Measurement
Point

code of "Invalid Network Appearance" is sent outwards from the
local office.
C901710024 Invalid Net

APPEARANCE(R)
Description

error code of "Invalid Network Appearance".
Measurement
Point

code of "Invalid Network Appearance" is received.
DUPU message sent which
cause is unknown
Description
This counter counts when a DUPU message is sent, with the indication of "Unknown".
Measurement
Point
The counter accumulates when a DUPU message with the indication of "Unknown" is sent.
Unit
2722
Times
C901710026 Number
of DUPU message sent
which cause is Unequipped
Remote User
Description
This counter counts when a DUPU message is sent, with the indication of "Unequipped Remote User".
Measurement
Point
The counter accumulates when a DUPU message with the indication of "Unequipped Remote User" is sent.
Unit
Times
DUPU message sent which
cause is Inaccessible
Remote User
Description
This counter counts when a DUPU message is sent, with the indication of "Inaccessible Remote User".
Measurement
Point
The counter accumulates when a DUPU message with the indication of "Inaccessible Remote User" is sent.
Unit
Times
DUPU message sent
Description
Measurement
Point
Unit
This counter counts the number of DUPU messages sent.

The counter accumulates when the DUPU message is sent.
Times
2723
by license
Description

message should be discarded, then the message will not be forwarded outwards from the local office and is directly discarded.
The condition is reported to OAM and the counter accumulates.
Measurement
Point

C901710030 Sending invalid

stream ID
Description

the local office, with the error code of "Invalid Stream ID".
Measurement
Point

code of "Invalid Stream ID" is sent outwards from the local office.
C901710031 Sending refuse

error, reason is management
blocking
2724
Description

the local office, with the error code of "Management Blocking Rejection".
Measurement
Point

code of "Management Blocking Rejection" is sent outwards from
the local office.
C901710032 Sending
required ASP ID
Description

the local office, with the error code of "ASP ID Required".
Measurement
Point

code of "ASP ID Required" is sent outwards from the local office.

ASP ID
Description

the local office, with the error code of "Invalid ASP ID".
Measurement
Point

code of "Invalid ASP ID" is sent outwards from the local office.

parameter value
Description

the local office, with the error code of "Invalid Parameter Value".
Measurement
Point

code of "Invalid Parameter Value" is sent outwards from the local
office.
C901710035 Sending
parameter field error
Description

the local office, with the error code of "Parameter Field Error".
Measurement
Point

code of "Parameter Field Error" is sent outwards from the local
office.
2725
C901710036 Sending
unexpected parameter error
Description

the local office, with the error code of "Unexpected Parameter".
Measurement
Point

code of "Unexpected Parameter" is sent outwards from the local
office.
C901710037 Sending
destination status unknown
Description

the local office, with the error code of "Destination Status Unknown".
Measurement
Point

code of "Destination Status Unknown" is sent outwards from the
local office.
C901710038 Sending
missing parameter error
Description

the local office, with the error code of "Missing Parameter Error".
Measurement
Point

code of "Missing Parameter Error" is sent outwards from the local
office.
C901710039 Sending no
configured AS for ASP
2726
Description

the local office, with the error code of "AS not configured with the
ASP".
Measurement
Point

code of "AS not configured with the ASP" is sent outwards from
the local office.
C901710040 Receiving
invalid stream ID
Description

error code of "Invalid Stream ID".
Measurement
Point

code of "Invalid Stream ID" is received.
refuse error, reason is
management blocking
Description

error code of "Management Blocking Rejection".
Measurement
Point

code of "Management Blocking Rejection" is received.
required ASP ID
Description

error code of "ASP ID Required".
Measurement
Point

code of "ASP ID Required" is received.
invalid ASP ID
Description

error code of "Invalid ASP ID".
Measurement
Point

code of "Invalid ASP ID" is received.
2727
invalid parameter value
Description

error code of "Invalid Parameter Value".
Measurement
Point

code of "Invalid Parameter Value" is received.
parameter field error
Description

error code of "Parameter Field Error".
Measurement
Point

code of "Parameter Field Error" is received.
unexpected parameter error
Description

error code of "Unexpected Parameter".
Measurement
Point

code of "Unexpected Parameter" is received.
destination status unknown
2728
Description

error code of "Destination Status Unknown".
Measurement
Point

code of "Destination Status Unknown" is received.
missing parameter error
Description

error code of "Missing Parameter Error".
Measurement
Point

code of "Missing Parameter Error" is received.
C901710049 Receiving no
configured AS for ASP
Description

error code of "AS not configured with the ASP".
Measurement
Point

code of "AS not configured with the ASP" is received.
2729
2730
Chapter
78
M3UA AS Performance
Statistics
Table of Contents
Overview...................................................................... 2731
C901720001 Number of service message transmitted......... 2731
C901720002 Bytes of service message transmitted ............ 2732
C901720003 Number of service message received ............. 2732
C901720004 Bytes of service message received ................ 2732
Overview
M3UA is short for MTP3-User Adaptation Layer. It supports IP
bearer of messages of some SS7 MTP3 users, seamless operations of peer-layer MTP3 user protocols, and MTP3 nework management functions. AS is short for Application Server. AS, which
works for M3UA, is the logic entity that works for the specific route
keyword of M3UA. This measurement takes AS as the unit. It performs measurement of the number of messages between M3UA
and upper-layer users and the number of bytes of messages between M3UA and upper-layer users. This chapter introduces the
meaning, usage, and measurement point of M3UA AS performance
statistic measurement counters.
service message transmitted
Description
This counter counts the number of upper-layer user messages sent

by AS of M3UA.
Measurement
Point
The counter counts when M3UA sends the upper-layer user message.
Unit
Times
2731
C901720002 Bytes of
service message transmitted
Description
This counter counts the number of bytes of upper-layer user messages sent by AS of M3UA.
Measurement
Point
The counter counts when M3UA sends the upper-layer user message.
Unit
Byte
service message received
Description
This counter counts the number of upper-layer user messages received by AS of M3UA.
Measurement
Point
The counter counts when M3UA receives the upper-layer user message from SCTP.
Unit
Times
C901720004 Bytes of
service message received
Description
This counter counts the number of bytes of upper-layer user messages received by AS of M3UA.
Measurement
Point
The counter counts when M3UA receives the upper-layer user message from SCTP.
Unit
2732
Byte
Chapter
79
Timer Statistics
Table of Contents
Overview...................................................................... 2733
C901730001 Number of all timers ................................... 2733
C901730002 Number of available timer ............................ 2734
C901730003 Peak value of timer ..................................... 2734
C901730004 Number of success to set timer..................... 2734
C901730005 Number of failure to set timer....................... 2734
Overview
Timer statistics performs measurement of the following information: total number of timers, number of available timers, peak
value of the timer, number of successes in setting timer, and number of failures in setting timer.
Timer resource refers to the memory block resource allocated according to the configuration during the system power-on process.
The total number of timers is fixed, which is decided by the system
configuration.
The number of available timers refers to the number of idle timer
control blocks.
Peak value of the timer refers to the maximum usage value of the
control block of the timer occupied during a period of time.
During the system running, if the timer control block is released
due to that the timer expires, the number of available timers increases. If the system sets timer to get the timer control block,
the number of available timers decreases.
C901730001 Number of all

timers
Description
This counter counts the total number of timers.
2733
Measurement
Point
The counter's value is fixed, depending on the configuration.
available timer
Description
Measurement
Point
This counter counts the number of available timers.

The counter counts when a timer control block is released successfully.
C901730003 Peak value of

timer
Description
Measurement
Point
This counter records the peak value of timer usage.

The counter counts when the timer usage exceeds the current peak
value.
success to set timer
Description
Measurement
Point
Unit
This counter counts the number of successes in setting timer.

The counter counts when the timer is set successfully.
Times
failure to set timer
Description
Measurement
Point
Unit
2734
This counter counts the number of failures in setting timer.

The counter counts when the timer setting fails.
Times
Chapter
80
Scheduling Performance
Statistics
Table of Contents
Overview...................................................................... 2735
C901740001 Number of active process............................. 2735
C901740002 Number of process ...................................... 2736
C901740003 Number of process scheduled ....................... 2736
Overview
Scheduling performance statistics refer to the statistics on the
scheduling of level-2 processes, including the number of active
process instances, number of process instances, and number of
processes instances scheduled in the last two seconds.
Through the statistics on the scheduling of level-2 processes, user
can have a rough knowledge of the system operation status. The
number of active process instances means the number of process
instances that can obtain CPU for operation and that are being running, that is, process instances in the ready queue or running state
under each scheduling task. The number of process instances
means the maximum number of process instances allowed for user
registration in registry. The number of tasks scheduled in current
2 seconds means the number of tasks that are scheduled in the
last two seconds.
active process
Description
Measurement
Point
This counter counts the total number of active processes.

The measurement point is determined during process creation and
is not changed during the operation.
2735
process
Description
Measurement
Point
This counter counts the total number of processes.

The measurement point is configured in the configuration file.
process scheduled
Description
Measurement
Point
2736
This counter counts the total number of scheduled processes.

This counter increments when a process is scheduled. It counts
the times of process scheduling in the last 2 seconds.
Chapter
81
UB Memory Performance
Statistics
Table of Contents
Overview...................................................................... 2737
C901750001 ID of UB Set............................................... 2737
C901750002 Size of UB.................................................. 2738
C901750003 Number of UB ............................................ 2738
C901750004 Number of UB used ..................................... 2738
Overview
UB memory performance statistics refer to the statistics on the
usage of current system UB and user UB on a certain board, including the statistics based on UB size and number of used UBs.
Two statistic methods are available:
Calculate UB usage based on quantity
Calculate UB usage based on size
The statistics based on quantity reflects the percentage of used

UB from the perspective of quantity. The statistics based on size
reflects the usage of UB from the perspective of used size. If the
query mode is 1, the system starts statistics based on the quantity
of used UBs and returns the percentage of currently used UBs. If
the query mode is -1, the system starts statistics based on the size
of used UBs and returns the percentage of currently used USs.
The unit of this UB performance statistics is board.
C901750001 ID of UB Set
Description
This counter counts the ID of a UB set. INNER_MEM_POOL_GROUP

represents the memory pool sets that are internally used.
USER_MEM_POOL_GROUP represents the memory pool sets that
are used by user.
2737
Measurement
Point
The measurement point is configured and unchanged.
C901750002 Size of UB
Description
Measurement
Point
This counter counts the size of the UBs in a UB set.

The measurement point is configured and unchanged.
C901750003 Number of UB
Description
Measurement
Point
This counter counts the number of UBs in the UB pool set.

The measurement point is related to current UB usage status and
may dynamically change with the addition or reduction of switching blocks.
C901750004 Number of UB
used
Description
Measurement
Point
2738
This counter counts the number of used UBs.

The measurement point is related to the current UB usage status.
Chapter
82
Hard Disk and FLASH

Table of Contents
Overview...................................................................... 2739
C901760001 Disk Device ID............................................ 2739
C901760002 Total space................................................. 2739
C901760003 Free space ................................................. 2740
Overview
The disks used by platform are hard disks and FLASHs. If the remaining space is insufficient, the upper application of those requiring storage is affected. Therefore, it is necessary to take real-time
statistics on disk space so that user can know the disk usage situation timely. Disk space performance statistics refer to the statistics
on remaining space and total space of disks on a board. The keyword is the device name of disk.
C901760001 Disk Device ID

Description
This counter indicates the disk device ID, which is /FLASH0,

/DOC0, /IDE0, /IDE1, /IDE2, or /IDE3.
Measurement
Point
The measurement point is related to the disk configuration on the

current board.
C901760002 Total space

Description
Measurement
Point
Unit
This counter counts the total space.

The measurement point is unchanged.
KB
2739
C901760003 Free space

Description
Measurement
Point
Unit
2740
This counter counts the free space.

The disk space occupation changes each time a file is added, modified, or deleted.
KB
Chapter
83
SCTP Protocol Statistics

Table of Contents
Overview...................................................................... 2742
C901770001 Number of Association Accepted ................... 2742
C901770002 Number of Association Initiated .................... 2742
C901770003 Number of Association Shutdown .................. 2742
C901770004 Number of Association Abort ........................ 2743
C901770005 Number of Chunk Retransmitted ................... 2743
C901770006 Number of Unordered Chunk Sent ................. 2743
C901770007 Number of Unordered Chunk Received ........... 2743
C901770008 Number of Chunk Sent ................................ 2743
C901770009 Number of Chunk Received .......................... 2744
C901770010 Number of Init Sent .................................... 2744
C901770011 Number of Init Received .............................. 2744
C901770012 Number of Init Ack Sent .............................. 2744
C901770013 Number of Init Ack Received ........................ 2744
C901770014 Number of COOKIE Sent .............................. 2745
C901770015 Number of Cookie Received .......................... 2745
C901770016 Number of Cookie Ack Sent .......................... 2745
C901770017 Number of Cookie Ack Received .................... 2745
C901770018 Number of Heartbeat Sent ........................... 2745
C901770019 Number of Heartbeat Received ..................... 2746
C901770020 Number of Heartbeat Ack Sent ..................... 2746
C901770021 Number of Heartbeat Ack Received................ 2746
C901770022 Number of Abort Chunk Sent ........................ 2746
C901770023 Number of Abort Chunk Received .................. 2747
C901770024 Number of Shutdown Chunk Sent ................. 2747
C901770025 Number of Shutdown Chunk Received............ 2747
C901770026 Number of Shutdown Ack Chunk Sent............ 2747
C901770027 Number of Shutdown Ack Chunk Received.......................................................................... 2748
C901770028 Number of Shutdown Complete Sent ............. 2748
C901770029 Number of Shutdown Complete Received......... 2748
C901770030 Number of Error Chunk Sent ........................ 2748
C901770031 Number of Error Chunk Received .................. 2749
C901770032 Number of ECNE Chunk Sent ........................ 2749
C901770033 Number of ECNE Chunk Received .................. 2749
C901770034 Number of CWR Chunk Sent......................... 2749
C901770035 Number of CWR Chunk Received ................... 2750
C901770036 Number of Error Packet Received .................. 2750
C901770037 Number of OOTB Chunk Received.................. 2750
C901770038 Number of ULP Sent Chunk Request in association alive ...................................................................... 2750
C901770039 Number of ULP Sent Chunk Request to SCTP OK
in association alive ........................................................ 2751
C901770040 Number of ULP Sent Chunk Request during a
little time ..................................................................... 2751
2741
C901770041 Number of ULP Sent Chunk Request to SCTP OK

during a little time ......................................................... 2751
C901770042 Number of SCTP Sent Chunk Request to
ULP ............................................................................. 2752
C901770043 Number of Abort Request from ULP ............... 2752
C901770044 Number of Received Abort From Peer ............ 2752
C901770045 Number of Link Break for Retransfer.............. 2752
Overview
SCTP, that is, stream control transmission protocol, supports the
transmission of PSTN signaling messages over IP network and the
transmission of signaling messages within IP network. This measurement task uses module as the unit to measure SCTP-related
data messages, number of management messages, and number
bytes. In addition, it classifies the statistics based on the local SCTP transceiving errors. This chapter describes the meanings, usages, and measurement points of SCTP stack measurement counters.
Association Accepted
Description
Measurement
Point
This counter counts the number of associations passively established.

When an association is accepted, this counter counts.
Association Initiated
Description
Measurement
Point
This counter counts the number of initiated associations.

When an association is actively initiated, this counter counts.
Association Shutdown
Description
2742
This counter counts the number of shutdown associations.
Chapter 83 SCTP Protocol Statistics
Measurement
Point
When an association is shut down, this counter counts.
Association Abort
Description
Measurement
Point
This counter counts the number of aborted associations.

When an association is aborted, this counter counts.
Chunk Retransmitted
Description
Measurement
Point
This counter counts the times of chunk retransmission.

When a chunks is retransmitted, this counter counts.
Unordered Chunk Sent
Description
Measurement
Point
This counter counts the number of sent unordered chunks.

When an unordered chunk is sent, this counter counts.
Unordered Chunk Received
Description
Measurement
Point
This counter counts the number of received unordered chunks.

When an unordered chunk is received, this counter counts.
Chunk Sent
Description
This counter counts the number of sent chunks.
2743
Measurement
Point
When a chunk is sent, this counter counts.
Chunk Received
Description
Measurement
Point
This counter counts the number of received chunks.

When a chunk is received, this counter counts.
C901770010 Number of Init

Sent
Description
Measurement
Point
This counter counts the number of sent INIT chunks.

When an INIT chunk is sent, this counter counts.

Received
Description
Measurement
Point
This counter counts the number of received INIT chunks.

When an INIT chunk is received, this counter counts.

Ack Sent
Description
Measurement
Point
This counter counts the number of sent INITACK chunks.

When an INITACK chunks is sent, this counter counts.

Ack Received
Description
2744
This counter counts the number of received INITACK chunks.
Measurement
Point
When an INITACK chunk is received, this counter counts.
COOKIE Sent
Description
Measurement
Point
This counter counts the number of sent COOKIE chunks.

When a COOKIE chunk is sent, this counter counts.
Cookie Received
Description
Measurement
Point
This counter counts the number of received COOKIE chunks.

When a COOKIE chunk is received, this counter counts.
Cookie Ack Sent
Description
Measurement
Point
This counter counts the number of sent COOKIE ACK chunks.

When a COOKIE ACK chunk is sent, this counter counts.
Cookie Ack Received
Description
Measurement
Point
This counter counts the number of received COOKIE ACK chunks.

When a COOKIE ACK chunk is received, this counter counts.
Heartbeat Sent
Description
This counter counts the number of sent heartbeat chunks.
2745
Measurement
Point
When a HEARTBEAT chunk is sent, this counter counts.
Heartbeat Received
Description
Measurement
Point
This counter counts the number of received heartbeats.

When a HEARTBEAT chunk is received, this counter counts.
Heartbeat Ack Sent
Description
Measurement
Point
This counter counts the number of sent heartbeat acknowledgement chunks.

When a HEARTBEAT ACK chunk is sent, this counter counts.
Heartbeat Ack Received
Description
Measurement
Point
This counter counts the number of sent heartbeat acknowledgement chunks.

When a HEARTBEAT ACK chunk is sent, this counter counts.
Abort Chunk Sent
Description
2746
This counter counts the number of sent ABORT chunks.
Measurement
Point
When an ABORT chunk is sent, this counter counts.
Abort Chunk Received
Description
Measurement
Point
This counter counts the number of received ABORT chunks.

When an ABORT chunk is received, this counter counts.
Shutdown Chunk Sent
Description
Measurement
Point
This counter counts the number of sent SHUTDOWN chunks.

When a SHUTDOWN chunk is sent, this counter counts.
Shutdown Chunk Received
Description
Measurement
Point
This counter counts the number of received SHUTDOWN chunks.

When a SHUTDOWN chunk is received, this counter counts.
Shutdown Ack Chunk Sent
Description
This counter counts the number of sent SHUTDOWN ACK chunks.
2747
Measurement
Point
When a SHUTDOWN ACK chunk is sent, this counter counts.
Shutdown Ack Chunk
Received
Description
Measurement
Point
This counter counts the number of received SHUTDOWN ACK

chunks.
When a SHUTDOWN ACK chunk is received, this counter counts.
Shutdown Complete Sent
Description
This counter counts the number of sent SHUTDOWN COMPLETE

chunks.
Measurement
Point
When a SHUTDOWN COMPLETE chunk is sent, this counter counts.
C901770029 Number
of Shutdown Complete
Received
Description
This counter counts the number of received SHUTDOWN COMPLETE chunks.
Measurement
Point
When a SHUTDOWN COMPLETE chunk is received, this counter

counts.
Error Chunk Sent
Description
2748
This counter counts the number of sent ERROR chunks.
Measurement
Point
When an ERROR chunk is sent, this counter counts.
Error Chunk Received
Description
Measurement
Point
This counter counts the number of received ERROR chunks.

When an ERROR chunk is received, this counter counts.
ECNE Chunk Sent
Description
Measurement
Point
This counter counts the number of sent ECNE chunks. As the implementation at bottom layer is not supported, the statistics are
invalid.
When an ECNE chunk is sent, this counter counts.
ECNE Chunk Received
Description
Measurement
Point
This counter counts the number of sent ECNE chunks. As the implementation at bottom layer is not supported, the statistics are
invalid.
When an ECNE chunk is sent, this counter counts.
CWR Chunk Sent
Description
This counter counts the number of sent CWR chunks. As the implementation at bottom layer is not supported, the statistics are
invalid.
2749
Measurement
Point
When a CWR chunk is sent, this counter counts.
CWR Chunk Received
Description
Measurement
Point
This counter counts the number of received CWR chunks. As the

implementation in bottom layer is not supported, the statistics are
invalid.
When a CWR chunk is received, this counter counts.
Error Packet Received
Description
Measurement
Point
This counter counts the number of received Error packets.

When an Error packet is received, this counter counts.
OOTB Chunk Received
Description
Measurement
Point
This counter counts the number of received OOTB chunks.

When an OOTB chunk is received, this counter counts.
ULP Sent Chunk Request in
association alive
2750
Description
This counter counts the number of chunk requests sent by ULP

when association is alive.
Measurement
Point
When ULP initiates chunk requests when association is alive, this

counter counts.
ULP Sent Chunk Request
to SCTP OK in association
alive
Description
This counter counts the number of successful chunk requests sent

by ULP to SCTP when association is alive. As the implementation
at bottom layer is not supported, the statistics is invalid.
Measurement
Point
Each time there is a successful chunk request sent by ULP when

association is alive, this counter counts.
ULP Sent Chunk Request
during a little time
Description
Measurement
Point
This counter counts the number of chunk requests sent by ULP. As

the implementation at bottom layer is not supported, the statistics
are invalid.
When ULP sends a chunk request, this counter counts.
ULP Sent Chunk Request to
SCTP OK during a little time
Description
This counter counts the number of successful chunk requests sent

by ULP to SCTP. As the implementation at bottom layer is not supported, the statistics are invalid.
Measurement
Point
When a chunk request sent by ULP to SCTP is successful, this

counter counts.
2751
SCTP Sent Chunk Request
to ULP
Description
Measurement
Point
This counter counts the number of chunk requests sent by SCTP

to ULP. As the implementation at bottom layer is not supported,
the statistics are invalid.
When SCTP sends chunk requests to ULP, this counter counts.
Abort Request from ULP
Description
Measurement
Point
This counter counts the number of ABORT requests from ULP. As

the implementation at lower layer is not supported, the statistics
are invalid.
When ULP sends an ABORT request to SCTP, this counter counts.
Received Abort From Peer
Description
This counter counts the number of received ABORT messages from

peer end. As the implementation at lower layer is not supported,
the statistics are invalid.
Measurement
Point
When SCTP receives an ABORT message from the peer end, this
counter counts.
C901770045 Number of Link

Break for Retransfer
2752
Description
This counter counts the number of link disconnections due to retransfer.
Measurement
Point
When a link is broken due to retransmission, this counter counts.
Chapter
84
SCTP Association
Statistics
Table of Contents
Overview...................................................................... 2753
C901780001 State of association..................................... 2753
C901780002 Send synchronous Msg to ULP fail ................. 2754
C901780003 ULPID from ULP invalid ................................ 2754
C901780004 Number of Association Initiated to ULP .......... 2754
C901780005 Number of Association Accepted to ULP ......... 2754
C901780006 Number of Association Restarted to ULP......... 2755
C901780007 Number of Association lost to ULP ................. 2755
C901780008 Number of Destroy instance ......................... 2755
C901780009 Number of Shutdown request from ULP.......... 2755
C901780010 Number of Abort request from ULP ................ 2756
Overview
Media Control Transmission Protocol (SCTP) supports transmission
of PSTN signaling messages over IP network and transmission of
signaling messages within IP network. Association refers to the
relation between two SCTP endpoints, including the protocol status information including the two endpoints, verification tag, and
Transmission Sequence Number (TSN). SCTP association-based
measurement task uses association as the unit to measure the
number of SCTP-related messages and bytes on each association,
etc. In addition, it classifies the local SCTP reception errors and
collects statistics respectively. This chapter describes the meanings, usages, and measurement points of SCTP association-based
measurement counters.
C901780001 State of
association
Description
Association states are as follows: Closed, Cookie wait, Cookie

Echoed, Established, Shutdown Pending, Shutdown Received,
Shutdown Sent, and Shutdown Ack Sent.
2753
Measurement
Point
None
C901780002 Send
synchronous Msg to ULP fail
Description
This counter counts the number of unsuccessful synchronization

message sent to ULP.
Measurement
Point
When synchronization messages are sent to ULP, this counter

counts.
C901780003 ULPID from

ULP invalid
Description
Measurement
Point
This counter counts the number of invalid ULPIDs returned by ULP.

When ULP returns ULPID, this counter counts.
Association Initiated to ULP
Description
Measurement
Point
This counter counts the number of associations initiated to ULP.

When association is actively established and Cookie ACK is received, this counter increments.
Association Accepted to
ULP
2754
Description
This counter counts the number of passively established associations reported to ULP.
Measurement
Point
When association is passively established and Cookie Echo is received, this counter increments.
Chapter 84 SCTP Association Statistics
Association Restarted to
ULP
Description
Measurement
Point
This counter counts the number of restarted associations reported

to ULP.
When an association is restarted, this counter counts.
Association lost to ULP
Description
Measurement
Point
This counter counts the number of lost associations reported to

ULP.
When an association is lost, this counter counts.
Destroy instance
Description
This counter counts the number of Destroy instance requests sent

by ULP.
Measurement
Point
When ULP sends a Destroy instance request, this counter counts.
Shutdown request from ULP
Description
This counter counts the number of association shutdown requests

sent by ULP.
2755
Measurement
Point
When ULP sends a SHUTDOWN message, this counter counts.
Abort request from ULP
Description
Measurement
Point
2756
This counter counts the number of association abort requests sent

by ULP.
When ULP sends an ABORT message, this counter counts.
Chapter
85
SDTB Fiber Performance

Statistics
Table of Contents
Overview...................................................................... 2759
C901790001 slot number (no description) ........................ 2759
C901790002 master/slave state (no description) ............... 2759
C901790003 SDH Type .................................................. 2759
C901790004 Regenerator Section BIP-8 Error ................... 2760
C901790005 Multiplex Section BIP-24 Error ...................... 2760
C901790006 VC-4 BIP-8 Error (High-order path 1) ............ 2760
C901790009 Multiplex Section Remote Error Indication ............................................................................. 2761
C901790010 VC-4 Remote Error Indication (High-order path
1)................................................................................ 2761
2)................................................................................ 2762
3)................................................................................ 2762
C901790013 Multiplex Section Remote Background Block Error Ratio....................................................................... 2762
C901790014 Multiplex Section Remote Errored Second Ratio ............................................................................... 2763
C901790015 Multiplex Section Remote Errored Second ............................................................................. 2763
C901790016 Multiplex Section Remote Severely Errored Second ............................................................................. 2763
C901790017 Multiplex Section Remote Unavailable Second ............................................................................. 2764
(High-order path 1) ....................................................... 2764
(High-order path 2) ....................................................... 2765
(High-order path 3) ....................................................... 2765
C901790021 VC-4 Remote Errored Second Ratio (High-order
path 1) ........................................................................ 2765
path 2) ........................................................................ 2766
path 3) ........................................................................ 2766
C901790024 VC-4 Remote Errored Second (High-order path
1)................................................................................ 2766
2)................................................................................ 2767
2757

3)................................................................................ 2767
C901790027 VC-4 Remote Severely Errored Second (Highorder path 1) ................................................................ 2767
C901790030 VC-4 Remote Unavailable Second (High-order
path 1) ........................................................................ 2768
path 2) ........................................................................ 2769
path 3) ........................................................................ 2769
C901790033 B1(Regenerator Section) BIP-8 Background
Block Error Ratio ........................................................... 2769
C901790034 B1(Regenerator Section) BIP-8 Errored Second
Ratio ........................................................................... 2770
C901790035 B1(Regenerator Section) BIP-8 Errored Second ............................................................................. 2770
C901790036 B1(Regenerator Section) BIP-8 Severely Errored
Second ........................................................................ 2771
C901790037 B1(Regenerator Section) BIP-8 Unavailable Second ............................................................................. 2771
C901790038 B2(Multiplex Section) BIP-24 Background Block
Error Ratio.................................................................... 2771
C901790039 B2(Multiplex Section) BIP-24 Errored Second
Ratio ........................................................................... 2772
C901790040 B2(Multiplex Section) BIP-24 Errored Second ............................................................................. 2772
C901790041 B2(Multiplex Section) BIP-24 Severely Errored
Second ........................................................................ 2773
C901790042 B2(Multiplex Section) BIP-24 Unavailable Second ............................................................................. 2773
C901790043 B3(VC-4) BIP-8 Background Block Error Ratio
(High-order path 1) ....................................................... 2773
(High-order path 2) ....................................................... 2774
(High-order path 3) ....................................................... 2774
C901790046 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 1) ................................................................... 2775
path 1) ........................................................................ 2776
path 2) ........................................................................ 2776
path 3) ........................................................................ 2776
C901790052 B3(VC-4) BIP-8 Severely Errored Second (Highorder path 1) ................................................................ 2777
C901790055 B3(VC-4) BIP-8 Unavailable Second (High-order
path 1) ........................................................................ 2778
2758
Chapter 85 SDTB Fiber Performance Statistics

path 2) ........................................................................ 2778
path 3) ........................................................................ 2778
C901790058 LOF second ................................................ 2779
Overview
The statistic task of SDTB optical channel performance collects statistics on the number of error codes of each network section and
channel layer in SDTB (accesses SDH transport network) receiving
signals. It is used to represent the data performance of each section and channel in SDH transport network. This chapter describes
the main performance statistic items, statistic method, and standard compliance of SDTB OI.
SDH Digital Trunk Board (SDTB) accesses SDH transport network
through a standard STM-1 port at line side. The system side provides 63 E1s or 84 T1s to bear TDM, IMA or PPP service for the
system. The statistic items of SDTB optical channel performance
include: SDH regenerator B1 error, SDH regenerator B2 error, SDH
high-order path B3 error, and SDH low-order path tributary BIP2
error. The statistic method is periodically querying the number of
errors of Rx signal at a fixed interval and implement error event
handling in accordance with ITU-T G.826.
C901790001 slot number

(no description)
Description
Measurement
Point
Unit
C901790002 master/slave
state (no description)
Description
Measurement
Point
Description
C901790003 SDH Type

SDH has the following types: AU-4, AU-3, and STS-3SDH.
2759
C901790004 Regenerator
Section BIP-8 Error
Description
Regeneration section overhead byte B1 is used as the BIP code to

monitor bit errors of regeneration section.
Measurement
Point
When the received B1 byte is verified to be inconsistent with the

result of BIP-8 check for regenerator section of previous STM-1
frame at local end, the block is assumed to have error and dwB1E
increments.
C901790005 Multiplex
Section BIP-24 Error
Description
Three multiplex section overhead byte B2s are used as the BIP
code to monitor bit errors of multiplex section.
Measurement
Point
When the received three B2 bytes are verified to be inconsistent

with the result of BIP-24 check for multiplex section of previous
STM-1 frame at local end, the block is assumed to have error and
dwB2E increments.
C901790006 VC-4 BIP-8

Error (High-order path 1)
Description
VC-4 POH byte B3 is used as the BIP code to monitor bit errors of
VC-4 path. It is valid when SDH type is AU-4, AU-3, and STS-3.
The corresponding high-order path is 1.
Measurement
Point
When the received B3 byte received by high-order path 1 is verified

to be inconsistent with the result of BIP-8 check for VC-4 section of
previous STM-1 frame at local end, the block is assumed to have
error and dwB3E1 increments.
C901790007 VC-4 BIP-8

Description
2760
This counter is similar to dwB3E1. When SDH type is AU-4, it is

meaningless. When SDH type is AU-3 or STS-3, it corresponds to
high-order path 2.
Measurement
Point
This counter is similar to dwB3E1. It corresponds to high-order

path 2.
C901790008 VC-4 BIP-8

Description

path 3.
Measurement
Point

path 3.
Section Remote Error
Indication
Description
When peer end device detects BIP-24 error according to the received three B2 bytes, it uses regenerator section overhead byte
M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI).
Measurement
Point
Because at most 24 bit errors can be found, the value range of M1

byte is 0 ~ 24. If M1 is not 0, it indicates that a remote error block
exists. In this case, dwMSREI increments.
C901790010 VC-4 Remote

Error Indication (High-order
path 1)
Description
When peer end device detects BIP-8 error according to the received B3 byte, it uses bit1 ~ bit4 of VC-4 POH byte G1 to send
the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). When SDH type is AU-4, AU-3, and STS-3, the
corresponding high-order path is 1.
Measurement
Point
Because at most eight bit errors can be found, the value range of
VC4-REI is 0 ~ 8. If VC4-REI is not 0, it indicates that a remote
error block exists. In this case, dwVC4REI1 increments.
2761

path 2)
Description
This counter is similar to dwVC4REI1. When SDH type is AU-4, it

is meaningless. When SDH type is AU-3 or STS-3, it corresponds
to high-order path 2.
Measurement
Point
This counter is similar to dwVC4REI1. It corresponds to high-order

path 2.

path 3)
Description

path 3.
Measurement
Point

path 3.
Section Remote Background
Block Error Ratio
2762
Description
M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI). Background block error
(BBE) refers to the error blocks after deducting the unusable time
and the error blocks appearing in the SES period. The ratio between the BBE numbers and total block numbers after deducting
the unusable time and all the blocks during the SES period is called
background block error rate (BBER).
Measurement
Point

exists. Multiplex Section-Remote Error Indication counter dwMSREI increments. SDTB periodically queries this counter, which
can serve as reference for the calculation of dwMSFEBBE.
Section Remote Errored
Second Ratio
Description
M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI). The ratio between the ES
within a specified period of measurement time and the total time
used is called error code second ratio (ESR).
Measurement
Point

can serve as reference for the calculation of dwMSFEER.
Section Remote Errored
Second
Description
M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI). When one second has one
or more error blocks or at least one deficiency, it is called an Error
Second (ES).
Measurement
Point

can serve as reference for the calculation of dwMSFEES.
Section Remote Severely
Errored Second
Description
M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI). When one second con-
2763
tains no less than 30% error blocks or at least one deficiency, it is

deemed as SES.
Measurement
Point

can serve as reference for the calculation of dwMSFESES.
Section Remote Unavailable
Second
Description
M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI). When SES is detected for
continuous 10 seconds, UAS starts (UAS includes these 10 seconds). When no SES is detected for continuous 10 seconds, UAS
ends (UAD excludes these 10 seconds).
Measurement
Point

can serve as reference for the calculation of dwMSFEUAS.

Background Block Error
Ratio (High-order path 1)
2764
Description
the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). Background block error (BBE) refers to the error
blocks after deducting the unusable time and the error blocks appearing in the SES period. The ratio between the BBE numbers
and total block numbers after deducting the unusable time and all
the blocks during the SES period is called background block error
rate (BBER). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.
Measurement
Point
error block exists. VC-4 path-Remote Error Indication counter
dwVC4REI increments. SDTB periodically queries this counter,
which can serve as reference for the calculation of dwVC4FEBBER1.

Description
This counter is similar to dwVC4FEBBER1. It corresponds to highorder path 2. When SDH type is AU-4, it is meaningless. When
SDH type is AU-3 or STS-3, it corresponds to high-order path 2.
Measurement
Point
This counter is similar to dwVC4FEBBER1. It corresponds to highorder path 2.

Description
Measurement
Point

Errored Second Ratio
(High-order path 1)
Description
the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). The ratio between the ES within a specified
period of measurement time and the total time used is called error code second ratio (ESR). When SDH type is AU-4, AU-3, and
STS-3, the corresponding high-order path is 1.
Measurement
Point
2765

which can serve as reference for the calculation of dwVC4FEER1.

(High-order path 2)
Description
This counter is similar to dwVC4FEER1. It corresponds to highorder path 2. When SDH type is AU-4, it is meaningless. When
SDH type is AU-3 or STS-3, it corresponds to high-order path 2.
Measurement
Point
This counter is similar to dwVC4FEER1. It corresponds to highorder path 2.

(High-order path 3)
Description
Measurement
Point

Errored Second (High-order
path 1)
2766
Description
the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). When one second has one or more error blocks
or at least one deficiency, it is called an Error Second (ES). When
SDH type is AU-4, AU-3, and STS-3, the corresponding high-order
path is 1.
Measurement
Point

which can serve as reference for the calculation of dwVC4FEES1.

path 2)
Description
This counter is similar to dwVC4FEES1. When SDH type is AU-4, it

Measurement
Point
This counter is similar to dwVC4FEES1. It corresponds to highorder path 2.

path 3)
Description
Measurement
Point

Severely Errored Second
(High-order path 1)
Description
the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). When one second contains no less than 30%
error blocks or at least one deficiency, it is deemed as SES. When
SDH type is AU-4, AU-3, and STS-3, the corresponding high-order
path is 1.
Measurement
Point
2767

which can serve as reference for the calculation of dwVC4FESES1.

(High-order path 2)
Description
This counter is similar to dwVC4FESES1. When SDH type is AU-4,

it is meaningless. When SDH type is AU-3 or STS-3, it corresponds
Measurement
Point
This counter is similar to dwVC4FESES1. It corresponds to highorder path 2.

(High-order path 3)
Description
Measurement
Point

Unavailable Second
(High-order path 1)
2768
Description
the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). When SES is detected for continuous 10 seconds,
UAS starts (UAS includes these 10 seconds). When no SES is detected for continuous 10 seconds, UAS ends (UAD excludes these
10 seconds). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.
Measurement
Point

which can serve as reference for the calculation of dwVC4FEUAS1.

Unavailable Second
(High-order path 2)
Description
This counter is similar to dwVC4FEUAS1. When SDH type is AU-4,

it is meaningless. When SDH type is AU-3 or STS-3, it corresponds
Measurement
Point
This counter is similar to dwVC4FEUAS1. It corresponds to highorder path 2.

Unavailable Second
(High-order path 3)
Description
Measurement
Point
C901790033 B1(Rege
nerator Section) BIP-8
Ratio
Description
Regeneration section overhead byte B1 is used as the BIP code

to monitor bit errors of regeneration section. Background block
error (BBE) refers to the error blocks after deducting the unusable
time and the error blocks appearing in the SES period. The ratio
between the BBE numbers and total block numbers after deducting
2769
Measurement
Point

frame at local end, the block is assumed to have error. Generator section BIP code counter dwB1E increments. SDTB periodically
queries this counter, which can serve as reference for the calculation of dwB1BBER.
C901790034 B1(Regenera
tor Section) BIP-8 Errored
Second Ratio
Description

monitor bit errors of regeneration section. The ratio between the
ES within a specified period of measurement time and the total
time used is called error code second ratio (ESR).
Measurement
Point

result of BIP-8 check of regenerator section of previous STM-1
queries this counter, which can serve as reference for the calculation of dwB1ER.
tor Section) BIP-8 Errored
Second
2770
Description

monitor bit errors of regeneration section. When one second has
one or more error blocks or at least one deficiency, it is called an
Error Second (ES).
Measurement
Point

queries this counter, which can serve as reference for the calculation of dwB1ES.
tor Section) BIP-8 Severely
Errored Second
Description
Regeneration section overhead byte B1 is used as the BIP code

to monitor bit errors of regeneration section. When one second
contains no less than 30% error blocks or at least one deficiency,
it is deemed as SES.
Measurement
Point

queries this counter, which can serve as reference for the calculation of dwB1SES.
C901790037 B1(Rege
nerator Section) BIP-8
Unavailable Second
Description

monitor bit errors of regeneration section. When SES is detected
for continuous 10 seconds, UAS starts (UAS includes these 10 seconds). When no SES is detected for continuous 10 seconds, UAS
ends (UAD excludes these 10 seconds).
Measurement
Point

queries this counter, which can serve as reference for the calculation of dwB1UAS
C901790038 B2(Multiplex
Section) BIP-24 Background
Block Error Ratio
Description
code to monitor bit errors of multiplex section. Background block
error (BBE) refers to the error blocks after deducting the unusable
time and the error blocks appearing in the SES period. The ratio
between the BBE numbers and total block numbers after deducting
2771
Measurement
Point

STM-1 frame at local end, the block is assumed to have error.
Muliplex section BIP code counter dwB2E increments. SDTB periodically queries this counter, which can serve as reference for the
calculation of dwB2BBER.
Section) BIP-24 Errored
Second Ratio
Description
code to monitor bit errors of multiplex section. The ratio between
the ES within a specified period of measurement time and the total
time used is called error code second ratio (ESR).
Measurement
Point

calculation of dwB2ER.
Section) BIP-24 Errored
Second
2772
Description
code to monitor bit errors of multiplex section. When one second
has one or more error blocks or at least one deficiency, it is called
an Error Second (ES).
Measurement
Point

calculation of dwB2ES.
Section) BIP-24 Severely
Errored Second
Description
code to monitor bit errors of multiplex section. When one second
contains no less than 30 error blocks or at least one deficiency, it
is deemed as SES.
Measurement
Point

calculation of dwB2SES.
Section) BIP-24 Unavailable
Second
Description
code to monitor bit errors of multiplex section. When SES is detected for continuous 10 seconds, UAS starts (UAS includes these
10 seconds). When no SES is detected for continuous 10 seconds,
UAS ends (UAD excludes these 10 seconds).
Measurement
Point

with the result of BIP-24 check for the multiplex section of previous STM-1 frame at local end, the block is assumed to have error.
calculation of dwB2UAS.
C901790043 B3(VC-4)
BIP-8 Background Block
Error Ratio (High-order path
1)
Description
VC-4 path. Background block error (BBE) refers to the error blocks
2773
after deducting the unusable time and the error blocks appearing
in the SES period. The ratio between the BBE numbers and total
block numbers after deducting the unusable time and all the blocks
during the SES period is called background block error rate (BBER).
When SDH type is AU-4, AU-3, and STS-3, the corresponding highorder path is 1.
Measurement
Point
When the B3 byte received by high-order path 1 is verified to be

inconsistent with the result of BIP-8 check for VC-4 block of previous STM-1 frame at local end, the block is assumed to have error.
VC-4 path BIP code counter dwB3E increments. SDTB periodically
queries this counter, which can serve as reference for the calculation of dwB3BBER1.
C901790044 B3(VC-4)
2)
Description
This counter is similar to dwB3BBER1. When SDH type is AU-4, it

Measurement
Point
This counter is similar to dwB3BBER1. It corresponds to high-order

path 2.
C901790045 B3(VC-4)
3)
2774
Description

path 3.
Measurement
Point

path 3.
C901790046 B3(VC-4)
BIP-8 Errored Second Ratio
(High-order path 1)
Description
VC-4 POH byte B3 is used as the BIP code to monitor bit errors
of VC-4 path. The ratio between the ES within a specified period
of measurement time and the total time used is called error code
second ratio (ESR). When SDH type is AU-4, AU-3, and STS-3, the
corresponding high-order path is 1.
Measurement
Point

inconsistent with the result of BIP-8 check for the VC-4 block of
previous STM-1 frame at local end through, the block is assumed
to have error. VC-4 path BIP code counter dwB3E increments.
SDTB periodically queries this counter, which can serve as reference for the calculation of dwB3ER1.
C901790047 B3(VC-4)
(High-order path 2)
Description
This counter is similar to dwB3ER1. When SDH type is AU-4, it is

high-order path 2.
Measurement
Point
This counter is similar to dwB3ER1. It corresponds to high-order

path 2.
C901790048 B3(VC-4)
(High-order path 3)
Description

path 3.
Measurement
Point

path 3.
2775
C901790049 B3(VC-4)
BIP-8 Errored Second
(High-order path 1)
Description
VC-4 path. When one second has one or more error blocks or at
least one deficiency, it is called an Error Second (ES). When SDH
type is AU-4, AU-3, and STS-3, the corresponding high-order path
is 1.
Measurement
Point

error. VC-4 path BIP code counter dwB3E increments. SDTB periodically queries this counter, which can serve as reference for the
calculation of dwB3ES1.
C901790050 B3(VC-4)
(High-order path 2)
Description
This counter is similar to dwB3ES1. When SDH type is AU-4, it is

high-order path 2.
Measurement
Point
This counter is similar to dwB3ES1. It corresponds to high-order

path 2.
C901790051 B3(VC-4)
(High-order path 3)
2776
Description

path 3.
Measurement
Point

path 3.
C901790052 B3(VC-4)
BIP-8 Severely Errored
Second (High-order path 1)
Description
of VC-4 path. When one second contains no less than 30% error
blocks or at least one deficiency, it is deemed as SES. When SDH
type is AU-4, AU-3, and STS-3, the corresponding high-order path
is 1.
Measurement
Point

error. VC-4 path BIP code counter dwB3E increments. SDTB periodically queries this counter, which can serve as reference for the
calculation of dwB3SES1.
C901790053 B3(VC-4)
Description
This counter is similar to dwB3SES1. When SDH type is AU-4, it

Measurement
Point
This counter is similar to dwB3SES1. It corresponds to high-order

path 2.
C901790054 B3(VC-4)
Description

path 3.
Measurement
Point

path 3.
2777
C901790055 B3(VC-4)
BIP-8 Unavailable Second
(High-order path 1)
Description
of VC-4 path. When SES is detected for continuous 10 seconds,
UAS starts (UAS includes these 10 seconds). When no SES is detected for continuous 10 seconds, UAS ends (UAD excludes these
10 seconds). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.
Measurement
Point

inconsistent with the result of BIP-8 check for VC-4 block of previous STM-1 frame at local end, the block is assumed to have error.
VC-4 path BIP code counter dwB3E increments. SDTB periodically
queries this counter, which can serve as reference for the calculation of dwB3UAS1.
C901790056 B3(VC-4)
(High-order path 2)
Description
This counter is similar to dwB3UAS1. When SDH type is AU-4, it

Measurement
Point
This counter is similar to dwB3UAS1. It corresponds to high-order

path 2.
C901790057 B3(VC-4)
(High-order path 3)
2778
Description

path 3.
Measurement
Point

path 3.
C901790058 LOF second

Description
This counter counts the seconds of LOF. The statistic result is 0 if

it is not temporally used.
Measurement
Point
This counter counts when LOF occurs and does not stop until LOF
restores.
2779
2780
Chapter
86
PEB22554 E1
Table of Contents
Overview...................................................................... 2781
C901800001 Frame type ................................................ 2782
C901800002 slip Duration ............................................. 2782
C901800003 Near end available Second ........................... 2782
C901800004 Near end unavailable Second........................ 2783
C901800005 Near end Errored Second ............................. 2783
C901800006 Near end Severely Errored Second ................ 2783
C901800007 Near end Background Block Error .................. 2784
C901800008 Frame Alignment Signal error ....................... 2784
C901800009 Cyclic Redundancy Check 4 error .................. 2784
C901800010 Bit error rate(PPM) ...................................... 2784
ten-thousandth) ............................................................ 2785
C901800012 Near end Errored Second rate(One ten-thousandth) ........................................................................ 2785
C901800013 Near end Severely Errored Second rate(One tenthousandth).................................................................. 2785
C901800014 Near end Background Block Error rate ........... 2785
C901800015 far end available Second .............................. 2786
C901800016 far end unavailable Second .......................... 2786
C901800017 far end Errored Second................................ 2786
C901800018 far end Severely Errored Second ................... 2787
C901800019 far end Background Block Error..................... 2787
C901800020 E-Bit ERROR............................................... 2787
C901800021 far end unavailable Second rate(One ten-thousandth) ........................................................................ 2787
C901800022 far end Errored Second rate(One ten-thousandth) ........................................................................ 2788
C901800023 far end Severely Errored Second rate(One tenthousandth).................................................................. 2788
C901800024 far end Background Block Error rate(One tenthousandth).................................................................. 2788
Overview
The statistic task of PEB22554 module E1 performance collects the
statistics on the number of error codes generated in receiving signals of PEB22554 module during transmission on different network
links. It is used to represent the data transmission performance of
2781
E1 signal in various sections and paths of transport network. This

chapter describes the main performance statistic items, statistic
method, and standard compliance of PEB22554 module.
PEB22554 module is a digital trunk access chip. It can connect
the transport network as standard E1 port at line side. The system side provides four E1s to bear services such as IMA for the
system. The performance statistic items of PEB22554 module in
E1 mode include FAS error, CRC error, and E-bit error. The statistic
method is as follows: query the number of error blocks of receiving end signals at the interval of 1S, and handle the error events
in accordance with ITU-T G.826 standard.
C901800001 Frame type

Description
There are two frame types: basic frame and multi-frame.

Basic frame: dual frame.
Multi-frame: CRC, CAS, CAS with CRC, forced multi-frame, and no
frame.
C901800002 slip Duration

Description
Measurement
Point
Unit
This counter counts the duration of code slip during detection period. Code slip occurs when receiving clock and transmitting clock
are insynchronous.
This counter counts the duration of code slip.
Second
C901800003 Near end

available Second
Description
Measurement
Point
Unit
2782
This counter counts the time available at near end, that is, the
result of excluding UAS from total detection period.
This counter counts the available seconds at near end.
Second
Chapter 86 PEB22554 E1 Performance Statistics
C901800004 Near end

unavailable Second
Description
Measurement
Point
Unit
If 10 consecutive near end SESs occur, the link is regarded to be

unavailable (UAS). The ten seconds are counted as unavailable
seconds. The link is regarded to be recovered if no near end SES
occurs in 10 consecutive seconds. These ten seconds are counted
as unavailable seconds.
This counter counts the unavailable seconds at near end.
Second
C901800005 Near end

Errored Second
Description
Measurement
Point
Unit
This counter increments each second near end detects LOF, LOS,
AIS alarm, and FAS error when link is available. For multi-frame,
this counter also counts the number of CRC-4 error blocks. If there
is one or more CRC-4 errors within a second, this counter increments.
This counter counts the errored seconds at near end.
Second
C901800006 Near end

Description
AIS alarm, and FAS (FAS>=26) error when link is available. For
multi-frame, this counter also counts the number of CRC-4 error
blocks. If there is more than 805 CRC-4 errors within a second,
Measurement
Point
When severely errored seconds at near end are detected, this

counter counts.
Unit
Second
2783
C901800007 Near end

Description
This counter counts the accumulation of CRC and FAS error counter
at each second. If a second is determined to be SES and UAS, it
is not counted.
Measurement
Point
When near end background block error occurs, this counter counts.
The basic frame is invalid and thus use 0.
Unit
Second
C901800008 Frame
Alignment Signal error
Description
Measurement
Point
This counter counts the number of FAS errors during the specified
period.
When FAS error is detected, this counter counts.
C901800009 Cyclic
Redundancy Check 4
error
Description
Measurement
Point
This counter counts the number of CRC4 errors during the specified
period.
When CRC4 error is detected, this counter counts.
C901800010 Bit error

rate(PPM)
Description
Measurement
Point
Unit
2784
For details, see the formula under the table.

This counter counts the number of errored codes.
PPM
C901800011 Near end

unavailable Second
rate(One ten-thousandth)
Description
Measurement
Point
Unit

When unavailable seconds are detected at near end, this counter
counts.
Ten-thousandth
C901800012 Near end

Errored Second rate(One
ten-thousandth)
Description
Measurement
Point
Unit

When errored seconds are detected at near end, this counter
counts.
Ten-thousandth
C901800013 Near end

Description
Measurement
Point
Unit

counter counts.
Ten-thousandth
C901800014 Near end

Background Block Error rate
Description
2785
Measurement
Point
When background block error is detected at near end, this counter

counts.
C901800015 far end

available Second
Description
Measurement
Point
Unit
This counter counts the time available at far end, that is, the result
of excluding UAS from total detection period.
This counter counts the available seconds at far end.
Second
C901800016 far end

unavailable Second
Description
If 10 consecutive far end SESs occur, the link is regarded to be

seconds. The link is regarded to be recovered if no far end SES
Measurement
Point
When unavailable seconds are detected at far end, this counter

counts.
Unit
Second
C901800017 far end Errored

Second
Description
This counter increments each second near end detects RAI alarm
and EBIT error when link is available.
Measurement
Point
When errored seconds are detected at far end, this counter counts.
Unit
2786
Second
C901800018 far end

Description
This counter increments each second far end detects RAI alarm
and EBIT (EBIT>=805) error when link is available.
Measurement
Point
When severely errored seconds are detected at far end, this

counter counts.
Unit
Second
C901800019 far end

Description
This counter counts the accumulation of EBIT error counter at each

second. If a second is determined to be SES and UAS, it is not
counted.
Measurement
Point
When far end background block errors are detected, this counter
counts.
C901800020 E-Bit ERROR

Description
Measurement
Point
Unit
This counter counts the times of sub-frame errors in multi-frame

during the detection period.
When EBIT error is detected, this counter counts.
Times
C901800021 far end

unavailable Second
Description
Measurement
Point
Unit

When unavailable seconds are detected at far end, this counter
counts.
Ten-thousandth
2787
C901800022 far end

Errored Second rate(One
ten-thousandth)
Description
Measurement
Point
Unit

When errored seconds are detected at far end, this counter counts.
Ten-thousandth
C901800023 far end

Description
Measurement
Point
Unit

When severely errored seconds are detected at far end, this
counter counts.
Ten-thousandth
C901800024 far end

Description
Measurement
Point
Unit
2788

When background block error is detected at far end, this counter
counts.
Ten-thousandth
Chapter
87
PEB22554 T1
Table of Contents
Overview...................................................................... 2789
C901810001 Frame type ................................................ 2790
C901810002 slip Duration ............................................. 2790
C901810003 Near end available Second ........................... 2790
C901810004 Near end unavailable Second........................ 2790
C901810005 Near end Errored Second ............................. 2791
C901810006 Near end Severely Errored Second ............... 2791
C901810007 number of Near end Background Block Error .............................................................................. 2791
C901810008 number of Frame Alignment Signal error......... 2792
C901810009 number of Cyclic Redundancy Check 6 error .............................................................................. 2792
C901810010 Bit error rate (PPM) ..................................... 2792
ten-thousandth) ............................................................ 2792
C901810012 Near end Errored Second rate (One ten-thousandth) ........................................................................ 2793
C901810013 Near end Severely Errored Second rate(One tenthousandth) ................................................................. 2793
C901810014 Near end Background Block Error rate ........... 2793
Overview
The statistic task of PEB22554 module T1 performance collects
the statistics on the number of error codes generated in receiving signals of PEB22554 module during transmission on different
network links. It is used to represent the data transmission performance of T1 signal in various sections and paths of transport network. This chapter describes the main performance statistic items,
statistic method, and standard compliance of PEB22554 module in
T1 mode.
PEB22554 module is a digital trunk access chip. It can connect
the transport network as standard T1 port at line side. The system side provides four T1s to bear services such as IMA for the
system. The performance statistic items of PEB22554 module in
T1 mode include FAS error and CRC error. The statistic method
is as follows: query the number of error blocks of receiving end
signals at the interval of 1s, and handle the error events in accordance with ITU-T G.826 standard.
2789
C901810001 Frame type

Description
There are two frame types: basic frame and multi-frame.
1 F24 (ESF) without CRC6
2 F24 (ESF) with CRC6
3 F12 (SF)
4 F4
5 F72
C901810002 slip Duration

Description
Measurement
Point
Unit
This counter counts the duration of code slip during detection period. Code slip occurs when receiving clock and transmitting clock
are insynchronous.
This counter counts the duration of code slip.
Second
C901810003 Near end

available Second
Description
Measurement
Point
This counter counts the time available at near end, that is, the
result of excluding UAS from total detection period.
This counter counts the available seconds at near end.
C901810004 Near end

unavailable Second
2790
Description
If 10 consecutive near end SESs occur, the link is regarded to be

seconds. The link is regarded to be recovered if no near end SES
Measurement
Point

counts.
Chapter 87 PEB22554 T1 Performance Statistics
C901810005 Near end

Errored Second
Description
AIS, RAI alarm, and FAS error when link is available. If CRC is
available, this counter counts the number of CRC-6 error blocks.
If there is one or more CRC-6 errors within a second, this counter
increments.
Measurement
Point

counts.
C901810006 Near end

Description
AIS, RAI alarm, and FAS (FAS>=26) error when link is available.
For F24 (ESF) with CRC6 format, this counter also counts the number of CRC-4 error blocks. If there is more than 805 CRC-4 errors
within a second, this counter increments.
Measurement
Point

counter counts.
C901810007 number of
Near end Background Block
Error
Description
This counter counts the accumulation of CRC and FAS error counter
at each second. If a second is determined to be SES and UAS, it
is not counted.
Measurement
Point
When near end background block errors are detected, this counter
counts.
2791
Frame Alignment Signal
error
Description
Measurement
Point
This counter counts the number of FAS errors during the specified
period.
When FAS error is detected, this counter counts.
Cyclic Redundancy Check 6
error
Description
Measurement
Point
This counter counts the number of CRC6 errors during the specified
period.
When CRC6 error is detected, this counter counts.
C901810010 Bit error rate

(PPM)
Description
Measurement
Point
Unit
See the formula.

This counter counts the number of errored codes.
PPM
C901810011 Near end

unavailable Second
Description
Measurement
Point
Unit
2792
See the formula.

counts.
Ten-thousandth
Chapter 87 PEB22554 T1 Performance Statistics
C901810012 Near end

Errored Second rate (One
ten-thousandth)
Description
Measurement
Point
Unit
See the formula.

counts.
Ten-thousandth
C901810013 Near end

Description
Measurement
Point
Unit
See the formula.

counter counts.
Ten-thousandth
C901810014 Near end

Background Block Error rate
Description
Measurement
Point
See the formula.

When background block errors are detected at near end, this
counter counts.
2793
2794
Chapter
88
MAC Port Flow Statistics

Table of Contents
Overview...................................................................... 2795
C901820001 receive bytes number (high 4 bytes) ............. 2796
C901820002 receive bytes number (low 4 bytes)............... 2796
C901820003 transmit bytes number (high 4 bytes)............ 2796
C901820004 transmit bytes number (low 4 bytes) ............. 2797
C901820005 physical band width..................................... 2797
C901820006 mean receiving bit rate ................................ 2797
C901820007 max receiving bit rate.................................. 2798
C901820008 mean transmitting bit rate ........................... 2798
C901820009 max transmitting bit rate ............................. 2798
C901820010 Number of packets discarded at RX side (high 4
bytes).......................................................................... 2799
C901820011 Number of packets discarded at RX side (low 4
bytes).......................................................................... 2799
C901820012 Number of packets discarded at TX side (high 4
bytes).......................................................................... 2799
C901820013 Number of packets discarded at TX side (low 4
bytes).......................................................................... 2800
C901820014 Number of packets received when receiving bit
rate is max during performance period ............................. 2800
C901820015 Number of packets sent when sending bit rate
is max during performance period.................................... 2800
Overview
Higher 4 bytes, lower 4 bytes: Because the transceiving data flow
might be beyond the range of 232 (4G), the value is recorded in
the form of two DWORDs (32 bits) to avoid data inaccuracy due
to overflow. The calculation method is as follows: Total value =
Value of higher 4 bytes * 232 + Value of lower 4 bytes.
The statistic object of the measurement is port of the board.
2795
C901820001 receive bytes

number (high 4 bytes)
Description
This counter counts the number of bytes received at the port.

When the message is received at the port, if the received message's lower 4 bytes' accumulation overflows, the counter increments.
Usage
This counter is used to find out the transceiving data flow at the
port within the measurement period.
Measurement
Point
Unit
The counter counts when the message is received at the port.

BYTE

number (low 4 bytes)
Description
This counter counts the number of bytes received at the port.

When the message is received at the port, the number of bytes
of the message is accumulated.
Usage
Measurement
Point
Unit
The counter counts when the message is received at the port.

BYTE
C901820003 transmit bytes

number (high 4 bytes)
Description
This counter counts the number of bytes transmitted at the port.

When the message is transmitted at the port, if the transmitted
message's lower 4 bytes' accumulation overflows, the counter increments.
Usage
Measurement
Point
The counter counts when the message is transmitted at the port.
Unit
2796
BYTE
Chapter 88 MAC Port Flow Statistics
C901820004 transmit bytes

number (low 4 bytes)
Description
This counter counts the number of bytes transmitted at the port.

When the message is transmitted at the port, the number of bytes
of the message is accumulated.
Usage
Measurement
Point
The counter counts when the message is transmitted at the port.
Unit
BYTE
C901820005 physical band

width
Description
This counter counts the port's physical bandwidth when the statistic data is reported.
Usage
This counter is used to find out the port's physical bandwidth. If

the port is faulty, then the bandwidth is 0 Mbit/s by default (meaningless in this case).
Measurement
Point
Unit
The counter counts when the data is reported.

Mbit/s
C901820006 mean receiving

bit rate
Description
This counter counts the average receiving rate at the port within
the measurement period. The counter's value = The number of
bytes received within the measurement period / Measurement period * 8
Usage
This counter is used to find out the average receiving rate at the
port.
Measurement
Point
Unit
The counter's value is calculated when the data is reported.

bit/s
2797
C901820007 max receiving

bit rate
Description
This counter counts the maximum receiving rate at the port within
the measurement period. The receiving rate at the port is measured every 30 seconds and recorded. When it is time to report
the data, the maximum receiving rate is taken as the counter's
value.
Usage
This counter is used to find out the maximum receiving rate at the
port.
Measurement
Point
Unit

bit/s
C901820008 mean
transmitting bit rate
Description
This counter counts the average transmitting rate at the port within
the measurement period. The counter's value = The number of
bytes transmitted within the measurement period / Measurement
period * 8
Usage
This counter is used to find out the average transmitting rate at

the port.
Measurement
Point
Unit

bit/s
C901820009 max
transmitting bit rate
Description
This counter counts the maximum transmitting rate at the port

within the measurement period. The transmitting rate at the port
is measured every 30 seconds and recorded. When it is time to
report the data, the maximum transmitting rate is taken as the
counter's value.
Usage
This counter is used to find out the maximum transmitting rate at

the port.
Measurement
Point
Unit
2798

bit/s
Chapter 88 MAC Port Flow Statistics
packets discarded at RX
side (high 4 bytes)
Description
Usage
Measurement
Point
This counter counts the number of packets discarded at the receiving end (higher 4 bytes).
The counter counts when the discarded packet is received at the
port.
packets discarded at RX
side (low 4 bytes)
Description
Usage
Measurement
Point
This counter counts the number of packets discarded at the receiving end (lower 4 bytes).
The counter counts when the discarded packet is received at the
port.
packets discarded at TX side
(high 4 bytes)
Description
Usage
Measurement
Point
This counter counts the number of packets discarded at the transmitting end (higher 4 bytes).
The counter counts when the discarded packet is transmitted at
the port.
2799
packets discarded at TX side
(low 4 bytes)
Description
Usage
Measurement
Point
This counter counts the number of packets discarded at the transmitting end (lower 4 bytes).
The counter counts when the discarded packet is transmitted at
the port.
packets received when
receiving bit rate is max
during performance period
Description
Usage
Measurement
Point
This counter counts the number of packets received at the peak

rate of the port.
Sampling is performed every second. Compare the receiving rate
with the peak rate, and the number of received packets of corresponding measurement points is recorded in the counter.
packets sent when sending
bit rate is max during
performance period
Description
Usage
Measurement
Point
2800
This counter counts the number of packets sent at the peak rate
of the port.
Sampling is performed every second. Compare the sending rate
with the peak rate, and the number of sent packets of corresponding measurement points is recorded in the counter.
Chapter
89
AMR Rate Statistics

Table of Contents
Overview...................................................................... 2801
C901830001 Total Num of DL AFS12.2k frame .................. 2802
C901830009 Total Num of DL AHS7.95k frame .................. 2805
C901830015 Total Num of UL AFS12.2k frame................... 2808
C901830023 Total Num of UL AHS7.95k frame .................. 2811
Overview
AMR rate statistics counts the total number of uplink/downlink
frames of absolute rate at the cell level.
AMR rate statistics at baseband counts the total number of uplink/downlink frames of absolute rate (coding frame) according to
cells. The full-rate channel has 8 rates while the half-rate channel
has 6 rates. Each carriers requires 28 counters.
Figure 2677 shows the AMR rate statistics flow.
2801
FIGURE 2677 AMR RATE STATISTICS REPORT
C901830001 Total Num of

DL AFS12.2k frame
Description
This counter counts the number of coding frames which adopt 12.2
k coding rate in downlink in AMR full-rate channel service.
Usage
This counter is used to find out the number of coding frames which
adopt 12.2 k coding rate in AMR full-rate channel service, and the
data is reported to the background in a granularity of 30 s. Multiply
the counter's accumulation value by 20 ms to get the traffic of AMR
rate within 30 s.
Measurement
Point
Unit
2802

AMR rate statistic data is reported periodically.
Number of frames
Chapter 89 AMR Rate Statistics

DL AFS10.2k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

DL AFS7.95k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

DL AFS7.40k frame
Description
Usage
rate within 30 s.
2803

Measurement
Point
Unit

Number of frames

DL AFS6.70k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

DL AFS5.90k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit
2804

Number of frames

DL AFS5.15k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

DL AFS4.75k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

DL AHS7.95k frame
Description
k coding rate in downlink in AMR half-rate channel service.
Usage
adopt 7.95 k coding rate in AMR half-rate channel service, and the
rate within 30 s.
2805

Measurement
Point
Unit

Number of frames

DL AHS7.40k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

DL AHS6.70k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit
2806

Number of frames

DL AHS5.90k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

DL AHS5.15k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

DL AHS4.75k frame
Description
Usage
rate within 30 s.
2807

Measurement
Point
Unit

Number of frames

UL AFS12.2k frame
Description
k coding rate in uplink in AMR full-rate channel service.
Usage
This counter is used to find out the number of uplink coding frames
which adopt 12.2 k coding rate in AMR full-rate channel service,
and the data is reported to the background in a granularity of 30
s. Multiply the counter's accumulation value by 20 ms to get the
traffic of AMR rate within 30 s.
Measurement
Point
Unit

Number of frames

UL AFS10.2k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit
2808

Number of frames

UL AFS7.95k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

UL AFS7.40k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

UL AFS6.70k frame
Description
Usage
rate within 30 s.
2809

Measurement
Point
Unit

Number of frames

UL AFS5.90k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

UL AFS5.15k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit
2810

Number of frames

UL AFS4.75k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

UL AHS7.95k frame
Description
k coding rate in uplink in AMR half-rate channel service.
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

UL AHS7.40k frame
Description
Usage
rate within 30 s.
2811

Measurement
Point
Unit

Number of frames

UL AHS6.70k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

UL AHS5.90k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit
2812

Number of frames

UL AHS5.15k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames

UL AHS4.75k frame
Description
Usage
rate within 30 s.
Measurement
Point
Unit

Number of frames
2813
2814
Chapter
90
PPP channel
measurement
Table of Contents
C901840001 Received byte count .................................... 2815
C901840002 Received packet count ................................. 2815
C901840003 Received framing aborts .............................. 2816
C901840004 Received FCS errors .................................... 2816
C901840005 Received packets greater than maximum
length .......................................................................... 2816
C901840006 Non-octet aligned frames received ................ 2817
C901840007 Received small datagrams discarded byte
count ........................................................................... 2817
C901840008 Received jumbo packets byte count............... 2817
C901840009 Received small datagrams discarded event
count ........................................................................... 2817
C901840010 Received jumbo packets count ...................... 2818
C901840011 Transmitted byte count ................................ 2818
C901840012 Transmitted packet count ............................. 2818
C901840013 Transmit framing aborts............................... 2818
C901840014 MLPPP ID ................................................... 2819
C901840015 PPP band width .......................................... 2819
C901840001 Received byte

count
Description
Measurement
Point
Unit
The received byte count.

when receiving data.
Byte
C901840002 Received
packet count
Description
The received packet count.
2815
Measurement
Point
Unit
The counter adds one when receiving data.

Piece
C901840003 Received
framing aborts
Description
Measurement
Point
Unit
The received framing aborts.

The counter adds one when receive the broken frame.
Piece
C901840004 Received FCS

errors
Description
Measurement
Point
Unit
The received FCS errors.

The counter adds one when receiving the FCS error occurs.
Piece
C901840005 Received
packets greater than
maximum length
Description
The received packets greater than maximum length.
Measurement
Point
The counter adds one when receiving jumbo packet.
Unit
2816
Piece
Chapter 90 PPP channel measurement
C901840006 Non-octet
aligned frames received
Description
Measurement
Point
Unit
The non-octet aligned frames received.

The counter adds one when receiving non-octet aligned frames.
Piece
C901840007 Received small

datagrams discarded byte
count
Description
Measurement
Point
Unit
The received small datagrams discarded byte count.

when discarding the small packet in RX direction.
Piece
C901840008 Received
jumbo packets byte count
Description
Measurement
Point
Unit
The received jumbo packets total length.

when receiving jumbo packet.
Byte
C901840009 Received small

datagrams discarded event
count
Description
Measurement
Point
Unit
The received small datagrams discarded event count.

The counter adds one when discarding small packet in RX direction.
Piece
2817
C901840010 Received
jumbo packets count
Description
Measurement
Point
Unit
The received chunk buffer allocation exceeded event count.

The counter adds one when receiving the jumbo package.
Piece
C901840011 Transmitted
byte count
Description
Measurement
Point
Unit
The transmitted byte count.

when transmitting data packet.
Byte
C901840012 Transmitted
packet count
Description
Measurement
Point
Unit
The transmitted packet count.

The counter adds one when transmitting data packet.
Piece
C901840013 Transmit
framing aborts
Description
Measurement
Point
Unit
2818
The Transmit framing aborts.

The counter adds one when transmitting frame.
Piece
Chapter 90 PPP channel measurement
C901840014 MLPPP ID
Description
Measurement
Point
Unit
ID of the ML-PPP that a PPP belongs to. It is only measured on the

EUIP board.
The counter is updated when a PPP is configured for an MP.
bps
C901840015 PPP band

width
Description
Measurement
Point
Unit
Bandwidth of PPP link.

When Configuration Ppp-port time slot, , the counter updated to
the current value.
bps
2819
2820
Chapter
91
UMAC Measurement
Table of Contents
Overview...................................................................... 2823
C901850001 receive discard packets flag.......................... 2823
C901850002 receive discard packets low 32bits................. 2824
C901850003 receive discard packets high 32bits ............... 2824
C901850004 receive bytes flag........................................ 2824
C901850005 receive bytes low 32bits .............................. 2825
C901850006 receive bytes high 32bits ............................. 2825
C901850007 receive packets flag .................................... 2825
C901850008 receive packets low 32bits ........................... 2826
C901850009 receive packets high 32bits .......................... 2826
C901850010 receive broadcast packets flag ...................... 2826
C901850011 receive broadcast packets low 32bits ............. 2827
C901850012 receive broadcast packets high 32bits............ 2827
C901850013 receive multicast packets flag ....................... 2827
C901850014 receive multicast packets low 32bits .............. 2828
C901850015 receive multicast packets high 32bits............. 2828
C901850016 receive CRC or align error packets flag........... 2828
C901850017 receive CRC or align error packets low
32bits .......................................................................... 2829
C901850018 receive CRC or align error packets high
32bits .......................................................................... 2829
C901850019 receive small than 64 bytes packets flag......... 2829
C901850020 receive small than 64 bytes packets low
32bits .......................................................................... 2830
C901850021 receive small than 64 bytes packets high
32bits .......................................................................... 2830
C901850022 receive large than 1518 bytes packets
flag ............................................................................. 2830
C901850023 receive large than 1518 bytes packets low
32bits .......................................................................... 2831
C901850024 receive large than 1518 bytes packets high
32bits .......................................................................... 2831
C901850025 The flag of received fragment packets............ 2831
C901850026 Number of fragment packets received (low 32
bit).............................................................................. 2832
C901850027 Number of received fragment packets (high 32
bit).............................................................................. 2832
C901850028 receive Jabber packets flag .......................... 2832
C901850029 receive Jabber packets low 32bits ................. 2833
C901850030 receive Jabber packets high 32bits ................ 2833
C901850031 receive Collision count flag ........................... 2833
C901850032 receive Collision count low 32bits .................. 2834
C901850033 receive Collision count high 32bits................. 2834
C901850034 receive 64 bytes packets flag........................ 2834
C901850035 receive 64 bytes packets low 32bits............... 2835
C901850036 receive 64 bytes packets high 32bits ............. 2835
2821
C901850037 receive 65 to 127 bytes packets flag.............. 2835

32bits .......................................................................... 2836
32bits .......................................................................... 2836
C901850040 receive 128 to 255 bytes packets flag ............ 2836
32bits .......................................................................... 2837
32bits .......................................................................... 2837
C901850043 receive 256 to 511 bytes packets flag ............ 2837
32bits .......................................................................... 2838
32bits .......................................................................... 2838
C901850046 receive 512 to 1023 bytes packets flag .......... 2838
32bits .......................................................................... 2839
32bits .......................................................................... 2839
32bits .......................................................................... 2840
32bits .......................................................................... 2840
C901850052 send discard packets flag ............................. 2840
C901850053 send discard packets low 32bits .................... 2841
C901850054 send discard packets high 32bits................... 2841
C901850055 send packet bytes flag ................................. 2841
C901850056 send packet bytes low 32bits........................ 2842
C901850057 send packets bytes high 32bits ..................... 2842
C901850058 send packets flag ........................................ 2842
C901850059 send packets low 32bits ............................... 2843
C901850060 send packets high 32bits.............................. 2843
C901850061 send broadcast packets flag ......................... 2843
C901850062 send broadcast packets low 32bits ................ 2844
C901850063 send broadcast packets high 32bits ............... 2844
C901850064 send multicast packets flag .......................... 2844
C901850065 send multicast packets low 32bits ................. 2845
C901850066 send multicast packets high 32bits ................ 2845
C901850067 send CRC or Align error packets flag.............. 2845
C901850068 send CRC or Align error packets low
32bits .......................................................................... 2846
C901850069 send CRC or Align error packets high
32bits .......................................................................... 2846
C901850070 send small than 64 bytes packets flag ........... 2846
C901850071 send small than 64 bytes packets low
32bits .......................................................................... 2847
C901850072 send small than 64 bytes packets high
32bits .......................................................................... 2847
C901850073 send large than 1518 bytes packets flag......... 2847
C901850074 send large than 1518 bytes packets low
32bits .......................................................................... 2848
C901850075 send large than 1518 bytes packets high
32bits .......................................................................... 2848
C901850076 The flag of sent fragment packets ................. 2848
C901850077 Number of sent fragment packets (low 32
bit).............................................................................. 2849
C901850078 Number of sent fragment packets (high 32
bit).............................................................................. 2849
2822
Chapter 91 UMAC Measurement
C901850079 send Jabber packets flag.............................. 2849

C901850080 send Jabber packets low 32bits..................... 2850
C901850081 send Jabber packets high 32bits ................... 2850
C901850082 send Collision count flag .............................. 2850
C901850083 send Collision count low 32bits ..................... 2851
C901850084 send Collision count high 32bits .................... 2851
C901850085 send 64 bytes packets flag ........................... 2851
C901850086 send 64 bytes packets low 32bits .................. 2852
C901850087 send 64 bytes packets high 32bits................. 2852
C901850088 send 65 to 127 bytes packets flag ................. 2852
C901850089 send 65 to 127 bytes packets low 32bits......... 2853
C901850090 send 65 to 127 bytes packets high 32bits......... 2853
C901850091 send 128 to 255 bytes packets flag ............... 2853
32bits .......................................................................... 2854
C901850094 send 256 to 511 bytes packets flag ............... 2854
32bits .......................................................................... 2855
C901850097 send 512 to 1023 bytes packets flag ............. 2855
32bits .......................................................................... 2856
32bits .......................................................................... 2856
C901850100 send 1024 to 1518 bytes packets flag............ 2856
32bits .......................................................................... 2857
32bits .......................................................................... 2857
C901850103 Logic port type ........................................... 2857
Overview
UMAC measurement performs measurement for transceiving packets, bytes, and incorrect packets on the MAC layer of each link.
Statistic unit in this measurement is link.
C901850001 receive discard

packets flag
Description
Usage
This counter flags the property of the statistic item.
If BIT7 is set as 1, it indicates that the current statistics is

invalid, that is, the statistics of the related higher 32 bits and
lower 32 bits are meaningless.
If BIT6 is set as 1, it indicates that the current statistics is of

low precision, the statistics of the related higher 32 bits are
invalid, and only the statistics of the related lower 32 bits are
valid.
2823
Measurement
Point
If BIT4 is set as 1, it indicates that the statistics overflow is

detected, however, it does not guarantee that all overflows are
detected.
None

packets low 32bits
Description
This counter records the lower 32 bits of the statistic item of discarded packet in the receiving direction.
Usage
This counter is used to find out the amount of packets discarded

in the receiving direction.
Measurement
Point
The counter counts when the packet is received.

packets high 32bits
Description
This counter records the higher 32 bits of the statistic item of discarded packet in the receiving direction.
Usage
This counter is used to find out the amount of packets discarded

in the receiving direction.
Measurement
Point

flag
Description
Usage
2824


valid.

detected.
Measurement
Point
None

low 32bits
Description
This counter records the lower 32 bits of the statistic item of total
bytes of received packets.
Usage
This counter is used to find out the total number of bytes received.
Measurement
Point

high 32bits
Description
This counter records the higher 32 bits of the statistic item of total
bytes of received packets.
Usage
This counter is used to find out the total number of bytes received.
Measurement
Point
C901850007 receive
packets flag
Description
Usage


valid.

detected.
2825
Measurement
Point
None
C901850008 receive
packets low 32bits
Description
Usage
Measurement
Point
This counter records the lower 32 bits of the statistic item of the
number of received packets.
This counter is used to find out the number of packets received.
C901850009 receive
packets high 32bits
Description
Usage
Measurement
Point
This counter records the higher 32 bits of the statistic item of the
number of received packets.
This counter is used to find out the number of packets received.
C901850010 receive
broadcast packets flag
Description
Usage
2826


valid.

detected.
Measurement
Point
None
C901850011 receive
broadcast packets low
32bits
Description
number of received broadcast packets.
Usage
This counter is used to find out the number of broadcast packets

received.
Measurement
Point
C901850012 receive
broadcast packets high
32bits
Description
number of received broadcast packets.
Usage
This counter is used to find out the number of broadcast packets

received.
Measurement
Point
C901850013 receive
multicast packets flag
Description
Usage


valid.

detected.
2827
Measurement
Point
None
C901850014 receive
multicast packets low 32bits
Description
number of received multicast packets.
Usage
This counter is used to find out the number of multicast packets

received.
Measurement
Point
C901850015 receive
multicast packets high
32bits
Description
number of received multicast packets.
Usage
This counter is used to find out the number of multicast packets

received.
Measurement
Point
C901850016 receive CRC

or align error packets flag
Description
Usage
2828


valid.

detected.
Measurement
Point
None

or align error packets low
32bits
Description
number of received CRC or alignment error packets.
Usage
This counter is used to find out the number of received CRC or

alignment error packets.
Measurement
Point

or align error packets high
32bits
Description
number of received CRC or alignment error packets.
Usage
This counter is used to find out the number of received CRC or

Measurement
Point
C901850019 receive small

than 64 bytes packets flag
Description
Usage


valid.

detected.
2829
Measurement
Point
None

than 64 bytes packets low
32bits
Description
number of received packets of which the size is smaller than 64
bytes.
Usage
This counter is used to find out the number of received packets of

which the size is smaller than 64 bytes.
Measurement
Point

than 64 bytes packets high
32bits
Description
number of received packets of which the size is smaller than 64
bytes.
Usage

which the size is smaller than 64 bytes.
Measurement
Point
C901850022 receive large

Description
Usage
2830


valid.
Measurement
Point

detected.
None

32bits
Description
number of received packets of which the size is larger than 1518
bytes.
Usage

which the size is larger than 1518 bytes.
Measurement
Point

than 1518 bytes packets
high 32bits
Description
number of received packets of which the size is larger than 1518
bytes.
Usage

which the size is larger than 1518 bytes.
Measurement
Point
C901850025 The flag of

received fragment packets
Description
Usage


2831
valid.
Measurement
Point

detected.
None
fragment packets received
(low 32 bit)
Description
number of received fragment packets.
Usage
This counter is used to find out the number of received fragment

packets.
Measurement
Point
received fragment packets
(high 32 bit)
Description
number of received fragment packets.
Usage
This counter is used to find out the number of received fragment

packets.
Measurement
Point
C901850028 receive Jabber

packets flag
Description
Usage
2832

Measurement
Point

valid.

detected.
None

packets low 32bits
Description
number of received Jabber packets.
Usage
This counter is used to find out the number of received Jabber

packets.
Measurement
Point

packets high 32bits
Description
number of received Jabber packets.
Usage
This counter is used to find out the number of received Jabber

packets.
Measurement
Point
C901850031 receive
Collision count flag
Description
Usage


valid.
2833
Measurement
Point

detected.
None
C901850032 receive
Collision count low 32bits
Description
number of received collisions.
Usage
This counter is used to find out the number of received collisions.
Measurement
Point
C901850033 receive
Collision count high 32bits
Description
number of received collisions.
Usage
This counter is used to find out the number of received collisions.
Measurement
Point
C901850034 receive 64
bytes packets flag
Description
Usage
2834


valid.

detected.
Measurement
Point
None
C901850035 receive 64
bytes packets low 32bits
Description
number of received packets of which the size is 64 bytes.
Usage

which the size is 64 bytes.
Measurement
Point
C901850036 receive 64
bytes packets high 32bits
Description
number of received packets of which the size is 64 bytes.
Usage

which the size is 64 bytes.
Measurement
Point
C901850037 receive 65 to
127 bytes packets flag
Description
Usage


valid.

detected.
2835
Measurement
Point
None
127 bytes packets low 32bits
Description
number of received packets of which the size is between 65 bytes
and 127 bytes.
Usage

which the size is between 65 bytes and 127 bytes.
Measurement
Point
C901850039 receive 65
to 127 bytes packets high
32bits
Description
and 127 bytes.
Usage

Measurement
Point

Description
Usage
2836


valid.

detected.
Measurement
Point
None

Description
and 255 bytes.
Usage

Measurement
Point
C901850042 receive 128

32bits
Description
and 255 bytes.
Usage

Measurement
Point

Description
Usage


valid.

detected.
2837
Measurement
Point
None

Description
and 511 bytes.
Usage

Measurement
Point
C901850045 receive 256

32bits
Description
and 511 bytes.
Usage

Measurement
Point

Description
Usage
2838


valid.

detected.
Measurement
Point
None
C901850047 receive 512

to 1023 bytes packets low
32bits
Description
and 1023 bytes.
Usage

Measurement
Point
C901850048 receive 512

32bits
Description
and 1023 bytes.
Usage

Measurement
Point
C901850049 receive 1024

to 1518 bytes packets flag
Description
Usage


valid.
2839
Measurement
Point

detected.
None
C901850050 receive 1024

32bits
Description
number of received packets of which the size is between 1024
bytes and 1518 bytes.
Usage

Measurement
Point
C901850051 receive 1024

32bits
Description
number of received packets of which the size is between 1024
Usage

Measurement
Point
C901850052 send discard

packets flag
Description
Usage
2840


valid.
Measurement
Point

detected.
None

packets low 32bits
Description
number of transmitted packets being discarded.
Usage
This counter is used to find out the number of transmitted packets

being discarded.
Measurement
Point
The counter counts when the packet is transmitted.

packets high 32bits
Description
number of transmitted packets being discarded.
Usage

being discarded.
Measurement
Point
C901850055 send packet

bytes flag
Description
Usage


valid.
2841
Measurement
Point

detected.
None
C901850056 send packet

bytes low 32bits
Description
This counter records the lower 32 bits of the statistic item of total
bytes of transmitted packets.
Usage
This counter is used to find out the total number of bytes of transmitted packets.
Measurement
Point
C901850057 send packets

bytes high 32bits
Description
This counter records the higher 32 bits of the statistic item of total
bytes of transmitted packets.
Usage
This counter is used to find out the total number of bytes of transmitted packets.
Measurement
Point

flag
Description
Usage
2842


valid.

detected.
Measurement
Point
None

low 32bits
Description
number of transmitted packets.
Usage
This counter is used to find out the total number of transmitted

packets.
Measurement
Point

high 32bits
Description
number of transmitted packets.
Usage
This counter is used to find out the total number of transmitted

packets.
Measurement
Point
C901850061 send broadcast

packets flag
Description
Usage


valid.

detected.
2843
Measurement
Point
None

packets low 32bits
Description
number of transmitted broadcast packets.
Usage
This counter is used to find out the number of transmitted broadcast packets.
Measurement
Point

packets high 32bits
Description
number of transmitted broadcast packets.
Usage
This counter is used to find out the number of transmitted broadcast packets.
Measurement
Point
C901850064 send multicast

packets flag
Description
Usage
2844


valid.

detected.
Measurement
Point
None

packets low 32bits
Description
number of transmitted multicast packets.
Usage
This counter is used to find out the number of transmitted multicast packets.
Measurement
Point

packets high 32bits
Description
number of transmitted multicast packets.
Usage
This counter is used to find out the number of transmitted multicast packets.
Measurement
Point
C901850067 send CRC or

Align error packets flag
Description
Usage


valid.

detected.
2845
Measurement
Point
None
C901850068 send CRC

or Align error packets low
32bits
Description
number of transmitted CRC or alignment error packets.
Usage
This counter is used to find out the number of transmitted CRC or

Measurement
Point
C901850069 send CRC

or Align error packets high
32bits
Description
number of transmitted CRC or alignment error packets.
Usage
This counter is used to find out the number of transmitted CRC or

Measurement
Point
C901850070 send small

Description
Usage
2846


valid.

detected.
Measurement
Point
None

32bits
Description
number of transmitted packets of which the size is smaller than
64 bytes.
Usage

of which the size is smaller than 64 bytes.
Measurement
Point

than 64 bytes packets high
32bits
Description
number of transmitted packets of which the size is smaller than
64 bytes.
Usage

of which the size is smaller than 64 bytes.
Measurement
Point
C901850073 send large

Description
Usage


valid.
2847
Measurement
Point

detected.
None

32bits
Description
number of transmitted packets of which the size is larger than
1518 bytes.
Usage

of which the size is larger than 1518 bytes.
Measurement
Point

than 1518 bytes packets
high 32bits
Description
number of transmitted packets of which the size is larger than
1518 bytes.
Usage

of which the size is larger than 1518 bytes.
Measurement
Point
C901850076 The flag of sent

fragment packets
Description
Usage
2848


valid.
Measurement
Point

detected.
None

fragment packets (low 32 bit)
Description
number of transmitted fragment packets.
Usage
This counter is used to find out the number of transmitted fragment packets.
Measurement
Point

fragment packets (high 32
bit)
Description
number of transmitted fragment packets.
Usage
This counter is used to find out the number of transmitted fragment packets.
Measurement
Point
C901850079 send Jabber

packets flag
Description
Usage


2849
valid.
Measurement
Point

detected.
None

packets low 32bits
Description
number of transmitted Jabber packets.
Usage
This counter is used to find out the number of transmitted Jabber

packets.
Measurement
Point

packets high 32bits
Description
number of transmitted Jabber packets.
Usage
This counter is used to find out the number of transmitted Jabber

packets.
Measurement
Point
C901850082 send Collision

count flag
Description
Usage
2850


valid.
Measurement
Point

detected.
None

count low 32bits
Description
number of transmitted collisions.
Usage
This counter is used to find out the number of transmitted collisions.
Measurement
Point

count high 32bits
Description
number of transmitted collisions.
Usage
This counter is used to find out the number of transmitted collisions.
Measurement
Point
C901850085 send 64 bytes

packets flag
Description
Usage


valid.

detected.
2851
Measurement
Point
None

packets low 32bits
Description
number of transmitted packets of which the size is 64 bytes.
Usage

of which the size is 64 bytes.
Measurement
Point

packets high 32bits
Description
number of transmitted packets of which the size is 64 bytes.
Usage

of which the size is 64 bytes.
Measurement
Point
C901850088 send 65 to 127

bytes packets flag
Description
Usage
2852


valid.

detected.
Measurement
Point
None
C901850089 send 65 to 127

bytes packets low 32bits
Description
number of transmitted packets of which the size is between 65
Usage

of which the size is between 65 bytes and 127 bytes.
Measurement
Point
C901850090 send 65 to 127

bytes packets high 32bits
Description
Usage

Measurement
Point
C901850091 send 128 to

Description
Usage


valid.

detected.
2853
Measurement
Point
None
C901850092 send 128 to

Description
Usage

Measurement
Point
C901850093 send 128 to

255 bytes packets high
32bits
Description
Usage

Measurement
Point
C901850094 send 256 to

Description
Usage
2854


valid.

detected.
Measurement
Point
None
C901850095 send 256 to

Description
Usage

Measurement
Point
C901850096 send 256 to

32bits
Description
Usage

Measurement
Point
C901850097 send 512 to

Description
Usage


valid.

detected.
2855
Measurement
Point
None
C901850098 send 512 to

1023 bytes packets low
32bits
Description
Usage

Measurement
Point
C901850099 send 512 to

32bits
Description
Usage

Measurement
Point
C901850100 send 1024 to

Description
Usage
2856


valid.
Measurement
Point

detected.
None
C901850101 send 1024

32bits
Description
Usage

Measurement
Point
C901850102 send 1024 to

32bits
Description
Usage

Measurement
Point
C901850103 Logic port type

Description
This counter records the logic port type (0: internal; 1: external;
0xffffffff: invalid).
Usage
None
Measurement
Point
None
Unit
None
2857
2858
Chapter
92
PS Handover Cause
Measurement
Table of Contents
Overview...................................................................... 2859
C901880001 Number of handover attempts due to uplink received strength ............................................................. 2860
C901880002 Number of handover attempts due to downlink
received strength .......................................................... 2860
quality ......................................................................... 2861
quality ......................................................................... 2862
C901880005 Number of handover attempts due to uplink interference .................................................................... 2862
interference .................................................................. 2863
PBGT ........................................................................... 2864
C901880008 Number of handover attempts due to large
TA ............................................................................... 2864
break up quickly............................................................ 2865
C901880010 Number of handover attempts due to macromicro switch ................................................................. 2866
C901880011 Number of handover attempts due to high traffic ............................................................................... 2866
standard level in FDD adjacent cell .................................. 2867
standard level in TDD adjacent cell .................................. 2868
PCCN ........................................................................... 2869
Overview
Counters of PS handover cause measurement are used to study
causes of PS handover initiated by MS during PS service process.
According to the cell's radio environment and BSC's configuration,
the PS handover algorithm's decision module initiates handover
due to vairous handover causes, optimizing the resource usage
and improving the PS service quality.
2859
uplink received strength
Statistics object
Description
BSC
This counter counts the number of handover attempts initiated by
MS due to too low uplink receiving strength. This counter is used
to find out the frequency of handover initiated by MS due to uplink receiving strength. If the counter's value is large, it indicates
that the uplink level is poor. After BSC receives the measurement
report, it performs handover decision. If the handover decision
indicates that handover is required and the handover is due to uplink receiving strength, the counter increments. The measurement
DUE TO UPLINK RECEIVED STRENGTH
Unit
NUMBER
OF HANDOVER ATTEMPTS
Times
downlink received strength
Statistics object
Description
2860
BSC
MS due to too low downlink receiving strength. This counter is
used to find out the frequency of handover initiated by MS due to
downlink receiving strength. If the counter's value is large, it indicates that the downlink level is poor. After BSC receives the measurement report, it performs handover decision. If the handover
decision indicates that handover is required and the handover is
due to downlink receiving strength, the counter increments. The
Chapter 92 PS Handover Cause Measurement

DUE TO DOWNLINK RECEIVED STRENGTH
Unit
NUMBER
Times
uplink quality
Statistics object
Description
BSC
MS due to too poor uplink quality. This counter is used to find out
the frequency of handover initiated by MS due to uplink quality.
If the counter's value is large, it indicates that the uplink quality
is poor. After BSC receives the measurement report, it performs
handover decision. If the handover decision indicates that handover is required and the handover is due to uplink quality, the
Figure 2680.
DUE TO UPLINK QUALITY
Unit
POINT
OF
NUMBER
Times
2861
downlink quality
Statistics object
Description
BSC
MS due to too poor downlink quality. This counter is used to find
out the frequency of handover initiated by MS due to downlink
quality. If the counter's value is large, it indicates that the downlink quality is poor. After BSC receives the measurement report,
it performs handover decision. If the handover decision indicates
that handover is required and the handover is due to downlink
quality, the counter increments. The measurement point is A, as
DUE TO DOWNLINK QUALITY
Unit
POINT
OF
NUMBER
Times
uplink interference
Statistics object
Description
2862
BSC
MS due to too strong uplink interference. This counter is used to
find out the frequency of handover initiated by MS due to uplink
interference. If the counter's value is large, it indicates that the
uplink interference is strong. After BSC receives the measurement
indicates that handover is required and the handover is due to
uplink interference, the counter increments. The measurement

DUE TO UPLINK INTERFERENCE
Unit
NUMBER
Times
downlink interference
Statistics object
Description
BSC
MS due to too strong downlink interference. This counter is used
to find out the frequency of handover initiated by MS due to downlink interference. If the counter's value is large, it indicates that
the downlink interference is strong. After BSC receives the measurement report, it performs handover decision. If the handover
due to downlink interference, the counter increments. The measurement point is A, as shown in Figure 2683.
DUE TO DOWNLINK INTERFERENCE
Unit
NUMBER
Times
2863
PBGT
Statistics object
Description
BSC
MS due to PBGT value. If the PBGT value is larger than zero, it
indicates that the radio environment of the adjacent cell is better
than that of the local cell. The PBGT handover will occur when the
number of times that the PBGT value is larger than zero reaches
the threshold value. This counter is used to find out the frequency
of handover initiated by MS due to PBGT value. If the counter's
value is large, it indicates that the local cell's signal is weaker than
that of the adjacent cell. After BSC receives the measurement
indicates that handover is required and the handover is due to
PBGT value, the counter increments. The measurement point is
FIGURE
DUE TO
Unit

PBGT
OF
NUMBER
Times
large TA
Statistics object
Description
2864
BSC
MS due to too large TA. Increasing TA indicates that MS is moving
away from the local cell. When the distance between MS and the
local cell reaches to a certain value, the handover due to large TA
will occur. This counter is used to find out the frequency of handover due to too large TA. The counter's value reflects the mobil-
ity of users in the local cell. After BSC receives the measurement
indicates that handover is required and the handover is due to too
large TA, the counter increments. The measurement point is A, as
FIGURE 2685
DUE TO LARGE
Unit
MEASUREMENT POINT
TA
OF
NUMBER
Times
uplink break up quickly
Statistics object
Description
BSC
MS due to uplink fast fading. If the uplink level drops suddenly
in several consecutive measurement reports, the handover due to
uplink fast fading will occur. This counter is used to find out the
frequency of handover due to uplink fast fading. The counter's
value reflects the stability of local radio environment. After BSC
receives the measurement report, it performs handover decision.
If the handover decision indicates that handover is required and
the handover is due to uplink fast fading, the counter increments.
DUE TO UPLINK BREAK UP QUICKLY
NUMBER
2865
Unit
Times
macro-micro switch
Statistics object
Description
BSC
This counter counts the number of handover attempts initiated
by MS due to macro-micro switch. If the adjacent cell's level is
larger than or equal to the threshold value and the adjacnet cell
is a lower-level cell, the macro-micro handover will occur. This
counter is used to find out the frequency of handover initiated by
MS due to macro-micro switch. The counter's value reflects the
traffic absorption of the micro cell. After BSC receives the measurement report, it performs handover decision. If the handover
due to macro-micro switch, the counter increments. The measurement point is A, as shown in Figure 2687.
DUE TO MACRO-MICRO SWITCH
Unit
NUMBER
Times
high traffic
Statistics object
Description
2866
BSC
This counter counts the number of MS's handover attempts due to
traffic. The handover is initiated by BSC, some traffic of the local
cell is moved to the destination cell, which reduces the traffic load
of the local cell. This counter is used to find out the frequency of
MS's handover due to traffic. The counter's value reflects the local
cell's service adjustment by BSC. After BSC receives the traffic
alarm, it performs handover decision. If the handover decision
indicates that handover is required, the counter increments. The
DUE TO HIGH TRAFFIC
Unit
POINT
OF
NUMBER
Times
handover attempts due to a
good standard level in FDD
adjacent cell
Statistics object
Description
BSC
This counter counts the number of MS's handover attempts due
to good base level in FDD adjacent cell. This counter is used to
find out the frequency of handover due to good base level in FDD
adjacent cell. The counter's value reflects the traffic absorption
in the FDD network. After BSC receives the measurement report,
that handover is required and the handover is due to good base
level in FDD adjacent cell, the counter increments. The measurement point is A, as shown in Figure 2689.
2867
FIGURE 2689 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS

DUE TO A GOOD STANDARD LEVEL IN FDD ADJACENT CELL
Unit
Times
handover attempts due to a
good standard level in TDD
adjacent cell
Statistics object
Description
BSC
This counter counts the number of MS's handover attempts due
to good base level in TDD adjacent cell. This counter is used to
find out the frequency of handover due to good base level in TDD
adjacent cell. The counter's value reflects the traffic absorption
in the TDD network. After BSC receives the measurement report,
that handover is required and the handover is due to good base
level in TDD adjacent cell, the counter increments. The measurement point is A, as shown in Figure 2690.
DUE TO A GOOD STANDARD LEVEL IN TDD ADJACENT CELL
Unit
2868
Times
PCCN
Statistics object
Description
BSC
This counter counts the number of MS's handover attempts due to
Packet Cell Change Notification (PCCN). This counter is used to find
out the frequency of handover due to Packet Cell Change Notification (PCCN). The counter's value reflects that the local cell's signal
is weaker than that of the destination cell specified by PCCN. After
BSC receives PCCN, if both the cell and MS support PS handover
and the cell allows handover due to PCCN, then MS attempts PS
handover, and the counter increments. The measurement point is
FIGURE
DUE TO
Unit

PCCN
OF
NUMBER
Times
2869
2870
Chapter
93
PS General Handover
Measurement
Table of Contents
Overview...................................................................... 2872
C901890001 Number of synchronous handover executions ............................................................................ 2872
C901890002 Number of successful synchronous handovers ......................................................................... 2873
C901890003 Number of pre-synchronous handover executions ............................................................................ 2874
C901890004 Number of successful pre-synchronous handovers ......................................................................... 2875
C901890005 Number of asynchronous handover executions ............................................................................ 2876
C901890006 Number of successful asynchronous handovers ......................................................................... 2877
C901890007 Number of normal handover executions ......... 2878
C901890008 Number of successful normal handovers......... 2879
C901890009 Number of optimised handover executions ............................................................................ 2880
C901890010 Number of successful optimised handovers ......................................................................... 2880
C901890011 Number of Intra-BSC inter-cell handover out attempts ......................................................................... 2881
C901890012 Number of Intra-BSC inter-cell handover out executions ....................................................................... 2882
C901890013 Number of successful Intra-BSC inter-cell handover out ..................................................................... 2883
C901890014 Number of Inter-BSC handover out attempts ......................................................................... 2884
C901890015 Number of Inter-BSC handover out executions ............................................................................ 2885
C901890016 Number of successful Inter-BSC handover
out .............................................................................. 2885
C901890017 Number of handover in attempts................... 2886
C901890018 Number of handover in executions ................ 2887
C901890019 Number of successful handover in ................. 2887
C901890020 Number of Intra-cell handover attempts......... 2888
C901890021 Number of Intra-Cell handover executions ............................................................................ 2889
C901890022 Number of successful Intra-cell handovers ......................................................................... 2889
C901890023 Number of invalid Intra-cell handovers........... 2889
C901890024 Number of 2G to FDD handover attempts......... 2890
C901890025 Number of 2G to FDD handover executions ............................................................................ 2890
2871
C901890026 Number of successful 2G to FDD handovers ......................................................................... 2891

C901890027 Number of 2G to TDD handover attempts......... 2892
C901890028 Number of 2G to TDD handover executions ............................................................................ 2892
C901890029 Number of successful 2G to TDD handovers ......................................................................... 2893
C901890030 Number of 3G to 2G handover attempts......... 2894
C901890031 Number of 3G to 2G handover executions ............................................................................ 2894
C901890032 Number of successful 3G to 2G handovers ......................................................................... 2895
C901890033 Number of T12 expiry.................................. 2896
C901890034 Number of PCCF received............................. 2896
messages received with cause Create PFC Failure .............. 2897
messages received with cause PS Handover Target not
allowed ....................................................................... 2898
messages received with cause PS Handover not Supported in
Target BSS or Target System........................................... 2899
messages received with cause other reasons..................... 2899
C901890039 Number of failure in optimised handover due to
failure alloc resource ..................................................... 2900
C901890040 Number of failure in optimised handover due to
PS handover not supported in target cell .......................... 2901
Overview
Counters of PS general handover measurement are used to study
the number of various types of PS handover successes and failures
during the PS service process. They also help study the frequency
of different types of abnormal handovers.
executions
Statistics object
Description
2872
Cell
This counter counts the number of synchronous handovers initiated by MS in the source cell. The source cell and destination cell
of the synchronous handover are under the same site. This counter
is used to find out the frequency of the synchronous handover initiated by MS in the source cell. It is one of the parameters that
evaluate the radio environment. When BSC sends the PS HAN-
Chapter 93 PS General Handover Measurement
DOVER COMMAND message to MS, if the handover is synchronous

handover, then the counter increments. The measurement point
OF
NUMBER
OF SYNCHRONOUS
HANDOVER EXECUTIONS
Unit
Times
successful synchronous
handovers
Statistics object
Description
Cell
This counter counts the number of successful synchronous handovers initiated by MS in the source cell. This counter is used to
find out the number of successful synchronous handovers in the
source cell. It helps study the synchronous handover condition. If
the handover is synchronous handover and is of normal handover
mode, then MS performs handover to the channel allocated in the
new cell after receiving the PS HANDOVER COMMAND message.
After the new cell receives the first correct RLC/MAC block, the
PS HANDOVER COMPLETE message is sent to SGSN, then SGSN
sends the DELETE BSS PFC message to notify the source cell to
release radio resource. When the source cell receives the DELETE
BSS PFC message, it indicates that the handover is completed, and
Figure 2693.
If the handover is synchronous handover and is of optimized handover mode, then MS performs handover to the channel allocated
in the new cell after receiving the PS HANDOVER COMMAND message. After the new cell receives the first correct RLC/MAC block,
the PS HANDOVER COMPLETE message is sent to SGSN, and the
optimized handover complete command (PS_OPTHO_END) is sent
to the source cell. Then, the source cell considers that the handover succeeds, and the counter increments. The measurement
2873
Unit

SYNCHRONOUS HANDOVERS - (1)
NUMBER
OF SUCCESSFUL

SYNCHRONOUS HANDOVERS - (2)
NUMBER
OF SUCCESSFUL
Times
executions
Statistics object
Description
2874
Cell
This counter counts the number of pre-synchronous handovers initiated by MS in the source cell. The source cell and destination cell
of the pre-synchronous handover are not under the same site. This
counter is used to find out the frequency of the pre-synchronous
handover initiated by MS in the source cell. It is one of the parameters that evaluate the radio environment. When BSC sends
the PS HANDOVER COMMAND message to MS, if the handover
is pre-synchronous handover, then the counter increments. The
OF
NUMBER
OF PRE-SYNCHRONOUS
HANDOVER EXECUTIONS
Unit
Times
successful pre-synchronous
handovers
Statistics object
Description
Cell
This counter counts the number of successful pre-synchronous
handovers initiated by MS in the source cell. This counter is used
to find out the number of successful pre-synchronous handovers
in the source cell. It helps study the pre-synchronous handover
condition. If the handover is pre-synchronous handover and is of
normal handover mode, then, after the new cell receives the first
correct RLC/MAC block, the PS HANDOVER COMPLETE message is
sent to SGSN, and SGSN sends the DELETE BSS PFC message to
notify the source cell to release radio resource. When the source
cell receives the DELETE BSS PFC message, it indicates that the
handover is completed, and the counter increments. The measurement point is A, as shown in Figure 2696.
If the handover is pre-synchronous handover and is of optimized
handover mode, then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is
sent to SGSN, and the optimized handover complete command
(PS_OPTHO_END) is sent to the source cell. Then, the source
cell considers that the handover succeeds, and the counter increments. The measurement point is A, as shown in Figure 2697.
2875
Unit

HANDOVER SUCCESSES - (1)
POINT
OF
NUMBER
OF PRE-SYNCHRONOUS

HANDOVER SUCCESSES - (2)
POINT
OF
NUMBER
OF PRE-SYNCHRONOUS
Times
executions
Statistics object
Description
2876
Cell
This counter counts the number of asynchronous handovers initiated by MS in the source cell. The source cell and destination
cell of the synchronous handover are not under the same site.
This counter is used to find out the frequency of the asynchronous
handover initiated by MS in the source cell. It is one of the parameters that evaluate the radio environment. When BSC sends
the PS HANDOVER COMMAND message to MS, if the handover is
asynchronous handover, then the counter increments. The measurement point is A, as shown in Figure 2698.
HANDOVER EXECUTIONS
Unit
POINT
OF
NUMBER
OF ASYNCHRONOUS
Times
successful asynchronous
handovers
Statistics object
Description
Cell
This counter counts the number of successful asynchronous handovers initiated by MS in the source cell. This counter is used
to find out the number of successful asynchronous handovers in
the source cell. It helps study the asynchronous handover condition. If the handover is asynchronous handover and is of normal
handover mode, then, after the new cell receives the first correct
RLC/MAC block, the PS HANDOVER COMPLETE message is sent
to SGSN, and SGSN sends the DELETE BSS PFC message to notify the source cell to release radio resource. When the source
If the handover is asynchronous handover and is of optimized
handover mode, then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is
sent to SGSN, and the optimized handover complete command
2877
Unit

ASYNCHRONOUS HANDOVERS -
POINT
(1)
OF
NUMBER
OF SUCCESSFUL

ASYNCHRONOUS HANDOVERS -
POINT
(2)
OF
NUMBER
OF SUCCESSFUL
Times
normal handover executions
Statistics object
Description
2878
Cell
This counter counts the number of normal handovers initiated by
MS in the source cell. This counter is used to find out the frequency
of the normal handover initiated by MS in the source cell. It is
one of the parameters that evaluate the radio environment. When
BSC sends the PS HANDOVER COMMAND message to MS, if the
handover is normal handover, then the counter increments. The
OF
NUMBER
OF NORMAL HANDOVER
EXECUTIONS
Unit
Times
C901890008 Number
of successful normal
handovers
Statistics object
Description
Cell
This counter counts the number of successful normal handovers
initiated by MS in the source cell. This counter is used to find out
the number of successful normal handovers in the source cell. It
helps study the normal handover condition. If the handover is of
normal handover mode, then, after the new cell receives the first
correct RLC/MAC block, the PS HANDOVER COMPLETE message is
sent to SGSN, and SGSN sends the DELETE BSS PFC message to
notify the source cell to release radio resource. When the source
FIGURE 2702
HANDOVERS
MEASUREMENT POINT
OF
NUMBER
OF SUCCESSFUL NORMAL
2879
Unit
Times
C901890009 Number
of optimised handover
executions
Statistics object
Description
Cell
This counter counts the number of optimized handover executions
initiated by MS in the source cell. During the optimized handover,
the source cell and the destination cell have the same NSE and
Routing Area Code (RAC). This counter is used to find out the frequency of the optimized handover execution in the source cell.
It is one of the parameters that evaluate the radio environment.
When BSC sends the PS HANDOVER COMMAND message to MS, if
the handover is optimized handover, then the counter increments.
FIGURE 2703
EXECUTIONS
Unit
MEASUREMENT POINT
OF
NUMBER
OF OPTIMISED HANDOVER
Times
C901890010 Number
of successful optimised
handovers
Statistics object
Description
2880
Cell
This counter counts the number of optimized handovers initiated
by MS in the source cell. This counter is used to find out the number of successful optimized handovers in the source cell. It helps
study the optimized handover condition. If the handover is of optimized handover mode, then, after the new cell receives the first
correct RLC/MAC block, the PS HANDOVER COMPLETE message
is sent to SGSN, and the optimized handover complete command

FIGURE 2704
HANDOVERS
Unit
MEASUREMENT POINT
OF
NUMBER
OF SUCCESSFUL OPTIMISED
Times
C901890011 Number
handover out attempts
Statistics object
Description
Cell
This counter counts the number of intra-BSC inter-cell outgoing
handover attempts initiated by MS in the source cell. This counter
is used to find out the frequency of the intra-BSC inter-cell outgoing handover attempt initiated by MS in the source cell. It is one of
the parameters that evaluate the radio environment. When user
plane receives the handover decision PSHO_PSCmd from control
plane, if it requires to initiate intra-BSC inter-cell handover, then
Figure 2705.
2881

OUTGOING HANDOVER ATTEMPTS
Unit
NUMBER
OF
INTRA-BSC
INTER-CELL
Times
C901890012 Number
handover out executions
Statistics object
Description
Cell
handover executions initiated by MS in the source cell. This
counter is used to find out the frequency of the intra-BSC inter-cell
outgoing handover execution initiated by MS in the source cell.
When BSC sends the PS HANDOVER COMMAND message to MS,
if the handover is intra-BSC inter-cell outgoing handover, then
in Figure 2706.
OUTGOING HANDOVER EXECUTIONS
Unit
2882
NUMBER
Times
OF
INTRA-BSC
INTER-CELL
C901890013 Number
of successful Intra-BSC
inter-cell handover out
Statistics object
Description
Cell
outgoing handovers initiated by MS in the source cell. This counter
is used to find out the number of successful intra-BSC inter-cell
outgoing handovers initiated by MS in the source cell. It helps
study the intra-BSC inter-cell outgoing handover condition. If the
handover is intra-BSC inter-cell handover and is of normal handover mode, then, after the new cell receives the first correct
RLC/MAC block, the PS HANDOVER COMPLETE message is sent
to SGSN, and SGSN sends the DELETE BSS PFC message to notify the source cell to release radio resource. When the source
If the handover is intra-BSC inter-cell handover and is of optimized handover mode, then, after the new cell receives the first
correct RLC/MAC block, the PS HANDOVER COMPLETE message
is sent to SGSN, and the optimized handover complete command
FIGURE 2707 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL
INTER-CELL OUTGOING HANDOVERS - (1)
INTRA-BSC
2883
FIGURE 2708 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL

INTER-CELL OUTGOING HANDOVERS - (2)
Unit
INTRA-BSC
Times
Inter-BSC handover out
attempts
Statistics object
Description
BSC
This counter counts the number of inter-BSC outgoing handover
attempts initiated by MS in the source cell. This counter is used to
find out the frequency of the inter-BSC outgoing handover attempt
initiated by MS in the source cell. It is one of the parameters that
evaluate the radio environment. When user plane receives the
handover decision PSHO_PSCmd from control plane, if it requires
to initiate inter-BSC handover, then the counter increments. The
HANDOVER ATTEMPTS
2884
POINT
OF
NUMBER
OF
INTER-BSC
OUTGOING
Unit
Times
Inter-BSC handover out
executions
Statistics object
Description
BSC
executions initiated by MS in the source cell. This counter is used
to find out the frequency of the inter-BSC outgoing handover execution initiated by MS in the source cell. It is one of the parameters that evaluate the radio environment. When BSC sends
the PS HANDOVER COMMAND message to MS, if the handover is
inter-BSC handover, then the counter increments. The measurement point is A, as shown in Figure 2710.
HANDOVER EXECUTIONS
Unit
POINT
OF
NUMBER
OF
INTER-BSC
OUTGOING
Times
C901890016 Number
of successful Inter-BSC
handover out
Statistics object
Description
BSC
This counter counts the number of successful inter-BSC handovers. This counter is used to find out the frequency of the
successful inter-BSC handover initiated by MS in the source cell.
When the source BSC receives the DELETE BSS PFC message
from SGSN, it indicates that the handover is completed, if the
handover is inter-BSC handover, the counter increments. The
2885

OUTGOING HANDOVERS
Unit
POINT OF NUMBER OF SUCCESSFUL INTER-BSC
Times
Statistics object
Description
BSC
This counter counts the number of inter-cell incoming handover attempts initiated by MS towards the destination cell. This counter
is used to find out the frequency of inter-cell incoming handover
attempt initiated by MS. It is one of the parameters that evaluate the radio environment. When the destination BSC receives
the SGSN handover request, it indicates that the resource request
succeeds, and the counter increments. The measurement point is
OF
NUMBER
ATTEMPTS
Unit
2886
Times
OF INCOMING HANDOVER
handover in executions
Statistics object
Description
BSC
This counter counts the number of BSC-controlled inter-cell incoming handover executions initiated by MS towards the destination
cell. This counter is used to find out the frequency of BSC-controlled inter-cell incoming handover attempt initiated by MS. It is
the destination BSC receives the SGSN handover request, it indicates that the resource request succeeds, and the counter increments. The measurement point is A, as shown in Figure 2713.
OF
NUMBER
OF INCOMING HANDOVER
EXECUTIONS
Unit
Times
successful handover in
Statistics object
Description
BSC
This counter counts the number of successful BSC-controlled intercell incoming handovers initiated by MS towards the destination
cell. This counter is used to find out the frequency of successful
BSC-controlled inter-cell incoming handover initiated by MS. It is
the destination BSC receives the first correct RLC/MAC block from
MS, it sends the PS handover completion message to SGSN, and
Figure 2714.
2887
FIGURE 2714
HANDOVERS
Unit
MEASUREMENT POINT
OF
NUMBER
OF SUCCESSFUL INCOMING
Times
Intra-cell handover attempts
Statistics object
Description
Cell
This counter counts the number of intra-cell handover attempts.
This counter is used to find out the frequency of intra-cell handover attempt initiated by MS. It is one of the parameters that
evaluate the radio environment. When BSC receives the measurement report from MS, it performs handover decision. If the
handover decision indicates that intra-cell handover is required,
Figure 2715.
FIGURE 2715
ATTEMPTS
Unit
2888
MEASUREMENT POINT
OF
NUMBER
Times
OF
INTRA-CELL
HANDOVER
C901890021 Number
of Intra-Cell handover
executions
Statistics object
Description
Unit
Cell
This counter counts the number of intra-cell handover executions
initiated by MS. This counter is used to find out the frequency
of intra-cell handover execution initiated by MS. It is one of the
parameters that evaluate the radio environment. After the MAC
module in BSC requests for resource successfully or unsuccessfully, the counter increments.
Times
C901890022 Number
of successful Intra-cell
handovers
Statistics object
Description
Unit
Cell
initiated by MS. This counter is used to find out the frequency
of intra-cell handover executions initiated by MS. It is one of the
parameters that evaluate the radio environment. After the MAC
module in BSC requests for resource successfully, the counter increments.
Times
invalid Intra-cell handovers
Statistics object
Description
Unit
Cell
This counter counts the number of failed intra-cell handovers initiated by MS. This counter is used to find out the frequency of
intra-cell handover executions initiated by MS. It is one of the parameters that evaluate the radio environment. After the MAC module in BSC fails to request for resource, the counter increments.
Times
2889
C901890024 Number of 2G
to FDD handover attempts
Statistics object
Description
BSC
This counter counts the number of 2G-to-FDD handover attempts
initiated by MS. This counter is used to find out the frequency of
handover attempt from 2G cell to FDD cell initiated by MS. It is
the source BSC receives the measurement report from MS, it performs handover decision. According to the decision result, if the
handover is FDD handover, the counter increments. The measurement point is A, as shown in Figure 2716.
OF
NUMBER
OF
2G
TO
FDD
HANDOVER
ATTEMPTS
Unit
Times
to FDD handover executions
Statistics object
Description
2890
BSC
This counter counts the number of 2G-to-FDD handover executions
handover execution from 2G cell to FDD cell initiated by MS. It is
the source BSC receives the handover request response message
issued by SGSN, it forms the PS HANDOVER COMMAND message
at Um interface and sends it to MS. If the handover is FDD handover, the counter increments. The measurement point is A, as
OF
NUMBER
OF
2G
TO
FDD
HANDOVER
EXECUTIONS
Unit
Times
successful 2G to FDD
handovers
Statistics object
Description
BSC
This counter counts the number of successful 2G-to-FDD handovers initiated by MS. This counter is used to find out the
frequency of successful handover from 2G cell to FDD cell initiated by MS. It is one of the parameters that evaluate the radio
environment. When the source BSC receives the DELETE BSS PFC
message from SGSN, it indicates that the handover is completed,
if the handover is FDD handover, the counter increments. The
FDD HANDOVERS
Unit
OF
NUMBER
OF SUCCESSFUL
2G
TO
Times
2891
to TDD handover attempts
Statistics object
Description
BSC
This counter counts the number of 2G-to-TDD handover attempts
handover attempt from 2G cell to TDD cell initiated by MS. It is
the source BSC receives the measurement report from MS, it performs handover decision. According to the decision result, if the
handover is TDD handover, the counter increments. The measurement point is A, as shown in Figure 2719.
OF
NUMBER
OF
2G
TO
TDD
HANDOVER
ATTEMPTS
Unit
Times
to TDD handover executions
Statistics object
Description
2892
BSC
This counter counts the number of 2G-to-TDD handover executions initiated by MS. This counter is used to find out the frequency
of handover execution from 2G cell to TDD cell initiated by MS. It is
the source BSC receives the handover request response message
issued by SGSN, it forms the PS HANDOVER COMMAND message
at Um interface and sends it to MS. If the handover is TDD handover, the counter increments. The measurement point is A, as
OF
NUMBER
OF
2G
TO
TDD
HANDOVER
EXECUTIONS
Unit
Times
successful 2G to TDD
handovers
Statistics object
Description
BSC
This counter counts the number of successful 2G-to-TDD handovers initiated by MS. This counter is used to find out the frequency of successful handover from 2G cell to TDD cell initiated
by MS. It is one of the parameters that evaluate the radio environment. When the source BSC receives the DELETE BSS PFC
message from SGSN, it indicates that the handover is completed,
if the handover is TDD handover, the counter increments. The
TDD HANDOVERS
Unit
OF
NUMBER
OF SUCCESSFUL
2G
TO
Times
2893
to 2G handover attempts
Statistics object
Description
BSC
This counter counts the number of 3G-to-2G outgoing handover
attempts initiated by MS. This counter is used to find out the frequency of 3G-to-2G handover attempt initiated by MS. It is one
of the parameters that evaluate the radio environment. When the
destination BSC receives the resource assignment, if the access
cell is 3G cell, the counter increments. The measurement point is
FIGURE 2722
ATTEMPTS
Unit
MEASUREMENT POINT
OF
NUMBER
OF
3G
TO
2G
HANDOVER
Times
to 2G handover executions
Statistics object
Description
2894
BSC
This counter counts the number of 3G-to-2G outgoing handover
executions initiated by MS. This counter is used to find out the frequency of 3G-to-2G handover execution initiated by MS. It is one
2G cell receives the handover request message issued by SGSN,
the counter increments when the following conditions are satisfied:
The cell is allocated with channel and the channel is activated, and
the source cell is 3G cell. The measurement point is A, as shown
in Figure 2723.
FIGURE 2723
EXECUTIONS
Unit
MEASUREMENT POINT
OF
NUMBER
OF
3G
TO
2G
HANDOVER
Times
C901890032 Number
of successful 3G to 2G
handovers
Statistics object
Description
BSC
This counter counts the number of successful 3G-to-2G incoming
handovers initiated by MS. This counter is used to find out the frequency of successful 3G-to-2G handover initiated by MS. It is one
2G cell receives the handover completion message, if the request
is due to SGSN-controlled inter-BSC incoming handover and the
source cell is 3G cell, the counter increments. The measurement
2G HANDOVERS
Unit
OF
NUMBER
OF SUCCESSFUL
3G
TO
Times
2895
C901890033 Number of T12

expiry
Statistics object
Description
BSC
This counter counts the number of T12 being timeout. This counter
is used to find out the frequency of handover failure due to T12
timeout. When T12 is timeout, the MAC instance in the source cell
considers that the handover fails, it records the destination cell of
the failed handover and clears the handover flag. If T12 is timeout
before BSC disables it, the counter increments. The measurement
Unit
OF
NUMBER
OF
T12
EXPIRY
Times
PCCF received
Statistics object
Description
2896
BSC
This counter counts the number of the Packet Cell Change Failure
messages received. When handover fails, MS returns to the original cell and sends the Packet Cell Change Failure message to BSC,
and BSC sends the PS Handover Cancel message to SGSN. When
BSC receives the Packet Cell Change Failure message from MS,
Figure 2726.
Unit
OF
NUMBER
OF
PCCF
RECEIVED
Times
PS-HANDOVER-REQUIRE
with cause Create PFC
Failure
Statistics object
Description
BSC
This counter counts the number of received PS Handover Required
Nack messages with the cause "Create PFC Failure". This counter
is used to find out the frequency of handover failure due to "Create
PFC Failure". When BSC receives the PS Handover Required Nack
message from SGSN with the cause of "Create PFC Failure", the
Figure 2727.
FIGURE 2727 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUIRED-NACK MESSAGES RECEIVED WITH CAUSE CREATE PFC FAILURE
Unit
Times
2897
PS-HANDOVER-REQUIRE
with cause PS Handover
Target not allowed
Statistics object
Description
BSC
Nack messages with the cause "PS Handover Target not allowed".
This counter is used to find out the frequency of handover failure
due to "PS Handover Target not allowed". When BSC receives the
PS Handover Required Nack message from SGSN with the cause
of "PS Handover Target not allowed", the counter increments. The
FIGURE 2728 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUIRED-NACK MESSAGES RECEIVED WITH CAUSE PS HANDOVER
TARGET NOT ALLOWED
Unit
2898
Times
PS-HANDOVER-REQUIRE
with cause PS Handover not
Supported in Target BSS or
Target System
Statistics object
Description
BSC
Nack messages with the cause "PS Handover not Supported in
Target BSS or Target System". This counter is used to find out
the frequency of handover failure due to "PS Handover not Supported in Target BSS or Target System". When BSC receives the
PS Handover Required Nack message from SGSN with the cause
of "PS Handover not Supported in Target BSS or Target System",
Figure 2729.
FIGURE 2729 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUIRED-NACK MESSAGES RECEIVED WITH CAUSE PS HANDOVER NOT
SUPPORTED IN TARGET BSS OR TARGET SYSTEM
Unit
Times
PS-HANDOVER-REQUIRE
with cause other reasons
Statistics object
BSC
2899
Description

Nack messages with the cause of other reasons. This counter is
used to find out the frequency of handover failure due to other reasons. When BSC receives the PS Handover Required Nack message from SGSN, which is not due to the cause of "Create PFC
Failure", "PS Handover Target not allowed", or "PS Handover not
Supported in Target BSS or Target System", the counter increments. The measurement point is A, as shown in Figure 2730.
FIGURE 2730 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUIRED-NACK MESSAGES RECEIVED WITH CAUSE OTHER REASONS
Unit
Times
failure in optimised handover
due to failure alloc resource
Statistics object
Description
2900
BSC
This counter counts the number of handover failure due to resource allocation failure in the optimized handover mode. This
counter is used to find out the frequency of handover failure due
to resource allocation failure in the optimized handover mode. If
RANUMC fails to create MS or RANPS instance, the counter increments. Then, RANUMC sends the EV_RANU_PS_OPTHO_ACK
message to the RANUHPMU module in the source cell, and the resource allocation result is written as resource allocation failure in
the message. The measurement point is A, as shown in Figure
2731.
FIGURE 2731 MEASUREMENT POINT OF NUMBER OF FAILURE IN OPTIMISED

HANDOVER DUE TO RESOURCE ALLCOATION FAILURE
Unit
Times
failure in optimised handover
due to PS handover not
supported in target cell
Statistics object
Description
BSC
This counter counts the number of handover failures due to that PS
handover is not supported in the destination cell in the optimized
handover mode. This counter is used to find out the frequency of
handover failure due to PS handover not supported in destination
cell in the optimized handover mode. When RANPS queries that
the cell does not support PS handover, the counter increments.
Then, RANPS sends the EV_RANU_PS_OPTHO_ACK message to
the RANUHPMU module in the source cell, the resource allocation
result is written as destination cell not supporting PS handover in
the message, and RANPS instance is released. The measurement
2901

PS HANDOVER NOT SUPPORTED IN TARGET CELL
Unit
2902
OF FAILURE IN OPTIMIZED HANDOVER DUE TO
Times
Chapter
94
IURG Measurement
Table of Contents
Overview...................................................................... 2903
C901900001 Number of relocation requests (on Iur-g)......... 2903
C901900002 Number of relocation executions (on
Iur-g) .......................................................................... 2904
C901900003
Number
of
relocation
successes
(on
Iur-g) .......................................................................... 2906
radio resource (on Iur-g) ................................................ 2907
terrestrial circuit resource (on Iur-g) ................................ 2907
C901900006 Number of relocation failures due to loss of UE
handover complete message (on Iur-g) ............................ 2908
C901900007 Number of relocation failures due to MS returning to original channel (on Iur-g) ..................................... 2909
C901900008 Number of relocation failures due to other
causes (on Iur-g) .......................................................... 2910
Overview
IURG measurement counters measure performance and status
of 2G/3G handover service implemented through Iur-g interface,
such as relocation requests received at Iur-g interface and handover failure causes.
relocation requests (on Iur-g)
Statistics object
Description
BSC
This counter counts the number of ENHANCED RELOCATION RESOURCE REQUEST messages received by BSC at Iur-g interface
from RNC. The measurement point is A1, as shown in Figure 2733.
(DBS is the database subsystem of BSC software)
2903
Unit
OF
RELOCATION (ON IUR-G)
Times
relocation executions (on
Iur-g)
Statistics object
Description
2904
BSC
After the radio resource is obtained, the handover relocation acknowledgement message is sent to the opposite end through Iur-g
Chapter 94 IURG Measurement
interface. The measurement point is A2, as shown in Figure 2734.

(DBS is the database subsystem of BSC software)
Unit
OF
Times
2905
relocation successes (on
Iur-g)
Statistics object
Description
BSC
Connect the link with the core nework and send the handover completion message successfully to the core network. The measurement point is A3, as shown in Figure 2735. (DBS is the database
subsystem of BSC software)
Unit
2906
OF
Times
relocation failures due to
no valid radio resource (on
Iur-g)
Statistics object
Description
BSC
Radio resource request fails. The measurement point is A4, as
shown in Figure 2736. (DBS is the database subsystem of BSC
software)
FIGURE 2736 MEASUREMENT POINT OF NUMBER OF RELOCATION FAILURES
DUE TO NO VALID RADIO RESOURCE (ON IUR-G)
Unit
Times
no valid terrestrial circuit
resource (on Iur-g)
Statistics object
Description
BSC
The terrestrial circuit allocated at A-interface is unavailable. The
measurement point is A5, as shown in Figure 2737. (DBS is the
database subsystem of BSC software)
2907

TERRESTRIAL CIRCUIT RESOURCE (ON IUR-G)
Unit
OF RELOCATION FAILURES DUE TO NO VALID
Times
relocation failures due
to loss of UE handover
complete message (on Iur-g)
Statistics object
Description
2908
BSC
Time expires but the handover completion message that indicates
MS accesses the network is not received. The measurement point
is A6, as shown in Figure 2738. (DBS is the database subsystem
of BSC software)
FIGURE 2738 MEASUREMENT POINT OF NUMBER OF RELOCATION FAILURES DUE TO LOSS OF

HANDOVER COMPLETE MESSAGE (ON IUR-G)
Unit
UE
Times
relocation failures due to MS
returning to original channel
(on Iur-g)
Statistics object
Description
BSC
BSC receives the handover relocation response message at Iur-g
interface, indicating that MS returns to the original channel. The
measurement point is A7, as shown in Figure 2739. (The figure
omits the intermediate process, and it only describes the follow-
2909
ing process: RNC initiates handover relocation, UE returns to the

original channel, and RNC notifies BSC to release resource.)
FIGURE
DUE TO
Unit
2739 MEASUREMENT POINT OF NUMBER OF RELOCATION

MS RETURNING TO ORIGINAL CHANNEL (ON IUR-G)
FAILURES
Times
other causes (on Iur-g)
Statistics object
Description
Unit
2910
BSC
Time expires but the handover request or access failure message
is not received from the core network. This counter counts handover failure causes except for those counted by C901900004 ~
C901900007.
Times
Chapter
95
RTCP Measurement
Table of Contents
Overview...................................................................... 2911
C901910001 local jitter (CS)........................................... 2911
C901910002 distant jitter (CS)........................................ 2912
C901910003 average one-way delay (CS)......................... 2913
C901910004 maximal one-way delay (CS) ........................ 2915
C901910005 local cumulative fraction lost (CS) ................. 2917
C901910006 distant cumulative fraction lost (CS) .............. 2918
C901910007 local jitter (PS) ........................................... 2919
C901910008 distant jitter (PS) ........................................ 2920
C901910009 average one-way delay (PS) ......................... 2921
C901910010 maximal one-way delay (PS) ........................ 2923
C901910011 local cumulative fraction lost (PS) ................. 2925
C901910012 distant cumulative fraction lost (PS) .............. 2926
Overview
RTCP measurement collects IP QoS data by directly extracting the
realtime monitoring data of RTP stream. This measurement counts
atomic values such as jitter, packet loss, and accumulated packet
loss, at the local end and the opposite end in CS stream and PS
stream.
C901910001 local jitter (CS)

Statistics object
Description
CELL
This parameter is calculated by IPRB at BSC. Suppose Si is the
time stamp of RTP packet i, and Ri is the local clock time when the
packet arrives the local end, then, the relative transmission time
of the two RTP packets i and j received at the local end is:
Relative transmission time = The receiver's clock time when RTP
packet arrives - RTP packet's RTP time stamp
Relative transmission time difference D(j, i) = (Rj - Sj) - (Ri - Si)
Jitter calculation formula: J(i) = J(i - 1) + (|D(i-1, i)| - J(i - 1))/16
2911
Oms_SlaProc accumulates the value within the statistics granularity. When the statistics granularity expires, divide the accumulated
value by the number of times of the parameter being received, and
fill the average value in the reported data area.
The counter's working flow is shown in Figure 2740.
Unit
OF LOCAL JITTER
(CS)
ms
C901910002 distant jitter

(CS)
Statistics object
Description
CELL
This parameter's value is directly extracted from the RTCP SR
packet sent from BTS, saved in IPRB, and reported to Host.
2912
Chapter 95 RTCP Measurement
Unit
OF LOCAL JITTER
(CS)
ms
C901910003 average
one-way delay (CS)
Statistics object
Description
CELL
This parameter is calculated by IPRB. Its physical meaning is the
delay between the RTP packet being sent and being received at the
opposite end, the calculation formula is: delay = (Current time Previous time - DLSR)/2
2913
Where, Current time and Previous time are obtained from the local
clock; Previous time is the time when SR packet is sent from the
local end, Current time is the time when the next SR packet is
received; DLSR is extracted from the SR packet sent from BTS.
2914
Unit
OF AVERAGE ONE-WAY DELAY
(CS)
ms
C901910004 maximal
one-way delay (CS)
Statistics object
Description
CELL
2915
Oms_SlaProc records the parameter's peak value within the statistics granularity. When the statistics granularity expires, fill the
peak value in the reported data area.
2916
OF MAXIMAL ONE-WAY DELAY
(CS)
Unit
ms
C901910005 local
cumulative fraction lost
(CS)
Statistics object
Description
CELL
udLocalTotalRcvCnt: Number of accumulatively received packets
at the local end within the report interval (the report interval is 5
s in this system)
This parameter is calculated by IPRB. IPRB accumulates the number of received RTP packets in uplink, when the report interval
expires, subtract the number of received packets 5 s ago from the
current number of received packets to calculate the parameter's
value.
udLocalIntervalLossCnt: Number of accumulatively lost packets at
the local end within the report interval
This parameter is calculated by IPRB. The number of accumulatively lost packets at the local end is calculated by subtracting the
number of actually received packets from the number of expected
received packets. The number of accumulatively lost packets at
the local end within the report interval is calculated by subtracting
the number of lost packets 5 s ago from the current number of
accumulatively lost packets at the local end.
Oms_SlaProc accumulates the two parameters respectively within
the statistics granularity, and marks the two values as udRcv and
udLoss. The counter's value is calculated according to the following formula:
If (udRcv + udLoss == 0) C901910005 = 0;
else C901910005 = 10000 udLoss/(udRcv + udLoss)
2917
Unit
OF LOCAL CUMULATIVE FRACTION LOST
(CS)
C901910006 distant
(CS)
Statistics object
Description
CELL
s in this system)
value.
2918

If (udRcv + udLoss == 0) C901910006 = 0;
Unit
OF DISTANT CUMULATIVE FRACTION LOST
(CS)
C901910007 local jitter (PS)

Statistics object
Description
CELL
This parameter is calculated by IPRB at BSC. Suppose Si is the
time stamp of RTP packet i, and Ri is the local clock time when the
packet arrives the local end, then, the relative transmission time
of the two RTP packets i and j received at the local end is:
2919
Relative transmission time = The receiver's clock time when RTP

packet arrives - RTP packet's RTP time stamp
Relative transmission time difference D(j, i) = (Rj - Sj) - (Ri - Si)
Jitter calculation formula: J(i) = J(i - 1) + (|D(i-1, i)| - J(i - 1))/16
Unit
OF LOCAL JITTER
(PS)
ms
C901910008 distant jitter

(PS)
Statistics object
Description
2920
CELL
This parameter's value is directly extracted from the RTCP SR
packet sent from BTS, saved in IPRB, and reported to Host.
Unit
OF DISTANT JITTER
(PS)
ms
C901910009 average
one-way delay (PS)
Statistics object
Description
CELL
2921
2922
Unit
OF AVERAGE ONE-WAY DELAY
(PS)
ms
C901910010 maximal
one-way delay (PS)
Statistics object
Description
CELL
2923
Oms_SlaProc records the parameter's peak value within the statistics granularity. When the statistics granularity expires, fill the
peak value in the reported data area.
2924
OF MAXIMAL ONE-WAY DELAY
(PS)
Unit
ms
C901910011 local
(PS)
Statistics object
Description
CELL
s in this system)
value.
If (udRcv + udLoss == 0) C901910011 = 0;
2925
Unit
OF LOCAL CUMULATIVE FRACTION LOST
(PS)
C901910012 distant
(PS)
Statistics object
Description
CELL
udDistantIntervalLossCnt: Number of accumulatively lost packets
at the opposite end within the report interval
IPRB extracts the number of accumulatively lost packets in downlink from SR packet sent from BTS. When the report interval expires, subtract the number of lost packets 5 s ago from the current
number of accumulatively lost packets to calculate the parameter's
value.
udDistantTotalRcvCnt: Number of accumulatively received packets at the opposite end within the report interval
This parameter is calculated by IPRB through subtracting the number of lost packets at the opposite end within 5 s from the number
of sent packets at the local end within 5 s.
2926

If (udRcv + udLoss == 0) C901910012 = 0;
Unit
OF DISTANT CUMULATIVE FRACTION LOST
(PS)
2927
2928
Chapter
96
DSP Measurement
Table of Contents
Overview...................................................................... 2929
C901920001 the times of loss of TRAU frame synchronization
in BIPB ........................................................................ 2929
Overview
TRAU frame refers to the data frame sent from BTS to BSC.
This data frame comprises of serial data, including the synchronization header that is easy to search for. After BIPB receives this
data frame, BIPB searches according to specific synchronization
header. If BIPB fails to search out the header, it is considered as
out of frame. If the number of TRAU frames that are out of frame
reaches the set value, the event of loss of TRAU frame synchronization is reported, which triggers relevant link release process.
Statistic unit in this measurement is times.
C901920001 the times

of loss of TRAU frame
synchronization in BIPB
Description
This counter counts the number of loss of TRAU frame synchronization detected by BIPB. This counter increments if the number of
loss of TRAU frame synchronization header reaches the sett value.
Usage
The counter is used to find out the frequency of search failure of

TRAU frame synchronization header.
Measurement
Point
BSC searches the synchronization header after receiving the TRAU

frame sent by BTS. The measurement point is A1, as shown in
Figure 2752.
2929

SYNCHRONIZATION IN BIPB
Unit
2930
POINT
OF THE TIMES OF LOSS OF
Second
TRAU
FRAME
Chapter
97
Access Control
Measurement
Table of Contents
Overview...................................................................... 2931
BandWidth UpLink ......................................................... 2932
BandWidth DownLink ..................................................... 2932
BandWidth UpLink ......................................................... 2933
BandWidth DownLink ..................................................... 2934
C901930005 Number of Pushing Down Uplink BandWidth .......................................................................... 2934
C901930006 Number of Pushing Down Downlink BandWidth
.................................................................................. 2935
C901930007 Number of Pushing Up Uplink BandWidth ......... 2936
C901930008 Number of Pushing Up Downlink BandWidth .......................................................................... 2937
BandWidth UpLink But Preempt PS IPAbis Successfully......... 2937
BandWidth DownLink But Preempt PS IPAbis Successfully............................................................................. 2938
Overview
Access control measurement counters counts the number of service access failure due to insufficient uplink/downlink Abis bandwidth during the service process in IP transmission mode.
Statistic unit in this measurement is IP bandwidth resource pool.
2931
CS Call Denied for Lack of
IPAbis BandWidth UpLink
Statistics object
Description
IPAbisPool
This counter counts the number of CS service access being rejected
due to insufficient uplink Abis bandwidth. It reflects whether the
uplink bandwidth of IP bandwidth resource pool, which is related
to Abis interface transmission, is appropriate. After BSC receives
the resource request from MS, it will allocate resource for MS. If
CS service access is rejected due to insufficient uplink Abis bandwidth, the counter increments. The measurement point is A, as
LACK OF IPABIS BANDWIDTH UPLINK
Unit
OF
CS CALL DENIED
FOR
Times
IPAbis BandWidth DownLink
Statistics object
Description
2932
IPAbisPool
This counter counts the number of CS service access being rejected
due to insufficient downlink Abis bandwidth. It reflects whether
the downlink bandwidth of IP bandwidth resource pool, which is
related to Abis interface transmission, is appropriate. After BSC
receives the resource request from MS, it will allocate resource for
MS. If CS service access is rejected due to insufficient downlink
Abis bandwidth, the counter increments. The measurement point
Chapter 97 Access Control Measurement

LACK OF IPABIS BANDWIDTH DOWNLINK
Unit
OF
CS CALL DENIED
FOR
Times
PS Call Denied for Lack of
Statistics object
Description
IPAbisPool
This counter counts the number of PS service access being rejected
due to insufficient uplink Abis bandwidth. It reflects whether the
uplink bandwidth of IP bandwidth resource pool, which is related
to Abis interface transmission, is appropriate. After BSC receives
the resource request from MS, it will allocate resource for MS. If PS
service access is rejected due to insufficient uplink Abis bandwidth,
Figure 2755.
LACK OF IPABIS BANDWIDTH UPLINK
Unit
OF
PS CALL DENIED
FOR
Times
2933
PS Call Denied for Lack of
Statistics object
Description
IPAbisPool
This counter counts the number of PS service access being rejected
due to insufficient downlink Abis bandwidth. It reflects whether
the downlink bandwidth of IP bandwidth resource pool, which is
related to Abis interface transmission, is appropriate. After BSC
receives the resource request from MS, it will allocate resource for
MS. If PS service access is rejected due to insufficient downlink
Abis bandwidth, the counter increments. The measurement point
LACK OF IPABIS BANDWIDTH DOWNLINK
Unit
OF
PS CALL DENIED
FOR
Times
Pushing Down Uplink
BandWidth
Description
This counter counts the number of pushing down uplink bandwidth

in the resource pool. When BSC control plane judges that the
actual uplink bandwidth exceeds C1, which is the safe allocation
upper limit about bandwidth at the resource pool, if the current
theoretically allocated uplink bandwidth of resource pool is larger
than available uplink bandwidth, BSC control plane sends the message of pushing down uplink bandwidth to BSC user plane, and the
counter increments.
Usage

uplink bandwidth in the resource pool.
2934
Measurement
Point
The counter counts when BSC control plane sends the message of
pushing down uplink bandwidth. The measurement point is A, as
FIGURE 2757 FLOW
POOL
Unit
OF
PUSHING DOWN UPLINK BANDWIDTH
IN
RESOURCE
Times
Pushing Down Downlink
BandWidth
Description
This counter counts the number of pushing down downlink bandwidth in the resource pool. When BSC control plane judges that
the actual downlink bandwidth exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, if the current theoretically allocated downlink bandwidth of resource pool is
larger than available downlink bandwidth, BSC control plane sends
the message of pushing down downlink bandwidth to BSC user
plane, and the counter increments.
Usage

downlink bandwidth in the resource pool.
Measurement
Point
pushing down downlink bandwidth. The measurement point is A,
2935
FIGURE 2758 FLOW
Unit
OF
PUSHING DOWN DOWNLINK BANDWIDTH
Times
C901930007 Number
of Pushing Up Uplink
BandWidth
Description
This counter counts the number of pushing up uplink bandwidth in

the resource pool. When BSC control plane judges that the actual
uplink bandwidth is lower than C3, which is the congestion pushing
up limit, BSC control plane sends the message of pushing up uplink
bandwidth to BSC user plane, and the counter increments.
Usage
The counter is used to find out the frequency of pushing up uplink

bandwidth in the resource pool.
Measurement
Point
The counter counts when BSC control plane sends the message
of pushing up uplink bandwidth. The measurement point is A, as
FIGURE 2759 FLOW
POOL
Unit
2936
OF
PUSHING UP UPLINK BANDWIDTH
Times
IN
RESOURCE
Pushing Up Downlink
BandWidth
Description
This counter counts the number of pushing up downlink bandwidth

in the resource pool. When BSC control plane judges that the actual downlink bandwidth is lower than C3, which is the congestion
pushing up limit, BSC control plane sends the message of pushing
up downlink bandwidth to BSC user plane, and the counter increments.
Usage
The counter is used to find out the frequency of pushing up downlink bandwidth in the resource pool.
Measurement
Point
pushing up downlink bandwidth. The measurement point is A, as
FIGURE 2760 FLOW
POOL
Unit
OF
PUSHING UP DOWNLINK BANDWIDTH
IN
RESOURCE
Times
But Preempt PS IPAbis
Successfully
Description
This counter counts the times that CS service preempts the PS IP

Abis resource successfully due to lack of the uplink IP Abis bandwidth during channel request.
2937
The counting criterion is not that the CS service is initiated successfully but that the Abis resource is preempted successfully.
Usage
None
Measurement
Point
None
Unit
Time
But Preempt PS IPAbis
Successfully
Description
This counter counts the times that CS service preempts the PS

IP Abis resource successfully due to lack of the downlink IP Abis
bandwidth during channel request.
The counting criterion is not that the CS service is initiated successfully but that the Abis resource is preempted successfully.
2938
Usage
None
Measurement
Point
None
Unit
Time
Chapter
98
Power Control
Measurement
Table of Contents
Overview...................................................................... 2939
C901940001 The count of iBSC receiving power control indication from BTS ............................................................ 2940
C901940002 The count of channel downlink power exceeding
TRX mean downlink power, when iBSC receives power control
indication from BTS ....................................................... 2940
C901940003 The count of CS service channel allocation failure caused by power shortage......................................... 2941
C901940004 The count of CS timeslot allocation failure
caused by power shortage .............................................. 2943
C901940005 The count of PS service channel allocation failure
C901940006 The count of PS timeslot allocation failure
Overview
The principle of dynamic power sharing is: To better use the rated
output power of the Power Amplifier (PA) of RRU, the BCCH carrier
occupies fixed transmitting power, and other service carriers can
dynamically share the transmitting power of RRU. Moreover, to
facilitate observing the result of power sharing, several counters
are added for power-sharing measurement.
Statistic unit in the power-sharing measurement is cell.
To use dynamic power sharing, the function of downlink dynamic
power control must be enabled first. After services are accessed,
the base station increases or decreases the downlink power according to the measurement report result.
2939

iBSC receiving power control
indication from BTS
Description
When iBSC receives the power control indication message (Abis

PowerControl Indication) from the base station, if the message
contains the downlink power adjustment information, the counter
increments.
Usage
This counter is used to find out the frequency of downlink dynamic

power control.
This counter is supported in version V6.20.600f or later.
Measurement
Point

PowerControl Indication) from the base station, if the message
contains the downlink power adjustment information, the counter
2761.
FIGURE 2761 POWER SHARING COUNTER 1

channel downlink power
exceeding TRX mean
downlink power, when iBSC
receives power control
indication from BTS
Description
2940

PowerControl Indication) from the base station, if the following
two conditions are satisfies, the counter increments: (1) The message contains the downlink power adjustment information. (2) The
Chapter 98 Power Control Measurement
value of degraded dBs (0 dB ~ 30 dB) for the channel by downlink

power control is smaller than the value of enhanced dBs (0 dB ~
1.5 dB) for the carrier by the power level configured in OMCR.
Usage
This counter is used to find out whether the function of dynamic

power sharing can make the power of service channel exceed the
average power of service carrier, that is, exceed (RRU's total power
- BCCH carrier's power) / number of service carriers.
Measurement
Point

PowerControl Indication) from the base station, if the following
two conditions are satisfies, the counter increments:
The message contains the downlink power adjustment information.
The value of degraded dBs (0 dB ~ 30 dB) for the channel by

downlink power control is smaller than the value of enhanced
dBs (0 dB ~ 1.5 dB) for the carrier by the power level configured in OMCR.

FIGURE 2762 FLOW
OF
REPORTING POWER CONTROL INDICATION MESSAGE

of CS service channel
allocation failure caused by
power shortage
Description
During the process of assignment or handover, if iBSC fails to allocate CS service channel due to insufficient power of RRU, the
counter increments.
Usage
This counter is used to find out the number of failures in allocating CS service channel due to insufficient power of RRU after the
function of dynamic power sharing is enabled.
2941
Measurement
Point
During the process of assignment or handover, if iBSC fails to allocate CS service channel due to insufficient power of RRU, the
FIGURE 2763 ASSIGNMENT FAILURE PROCESS
2942
FIGURE 2764 FAILURE IN ALLOCATING CHANNEL

OF INTERNAL HANDOVER
FOR
DESTINATION CELL
FIGURE 2765 FAILURE

HANDOVER
FOR
EXTERNAL INCOMING
IN
ALLOCATING CHANNEL

CS timeslot allocation failure
caused by power shortage
Description
When iBSC allocates CS service channel during the process of assignment or handover, if the function of dynamic power sharing is
enabled, there might be several channels that fail to be allocated
due to insufficient power of timeslots. The counter increments
when a channel fails to be allocated due to insufficient power of
timeslot.
Usage
This counter is used to find out the frequency of failing in allocating CS service channel due to insufficient power of RRU after the
Measurement
Point
When iBSC allocates CS service channel during the process of assignment or handover, if the function of dynamic power sharing is
enabled, there might be several channels that fail to be allocated
due to insufficient power of timeslots. The counter increments
when a channel fails to be allocated due to insufficient power of
timeslot. The measurement points are A1 and B1, as shown in
FIGURE 2766 C901940004A
2943
FIGURE 2767 C901940004B
FIGURE 2768 C901940004C

of PS service channel
allocation failure caused by
power shortage
2944
Description
After the dynamic power sharing function is enabled, when iBSC

allocates TBF for PS service, if the PS channel allocation fails due
to insufficient power of RRU, the counter increments.
Usage
This counter is used to find out the number of failures in allocating PS service channel due to insufficient power of RRU after the

Measurement
Point

allocates TBF for PS service, if the PS channel allocation fails due
to insufficient power of RRU, the counter increments.

PS timeslot allocation failure
caused by power shortage
Description

allocates TBF for PS service or during the process of requesting for
DTM channel, there might be several PS channels that fail to be
allocated due to insufficient power of RRU. The counter increments
when a PS channel fails to be allocated.
Usage
This counter is used to find out the frequency of failing in allocating

PS service channel or DTM channel due to insufficient power of RRU
after the function of dynamic power sharing is enabled.
Measurement
Point

allocates TBF for PS service or during the process of requesting for
DTM channel, there might be several PS channels that fail to be
allocated due to insufficient power of RRU. The counter increments
when a PS channel fails to be allocated.
2945
2946
Chapter
99
PS Adjacent Cell
Table of Contents
Overview...................................................................... 2948
C901950001 Number of handover attempts on the adjacent
cell .............................................................................. 2948
C901950002 Number of successful handovers from selected
cell to the adjacent cell .................................................. 2949
C901950003 Number of handover attempts from adjacent cell
to the selected cell ........................................................ 2950
C901950004 Number of successful handovers from adjacent
cell to the selected cell ................................................... 2951
to the adjacent cell due to better uplink quality ................. 2952
to the adjacent cell due to better downlink quality ............. 2954
cell to the adjacent cell due to better uplink quality ............ 2955
cell to the adjacent cell due to better downlink quality......... 2956
to the adjacent cell due to better uplink strength ............... 2958
to the adjacent cell due to better downlink strength ........... 2959
cell to the adjacent cell due to better uplink strength.......... 2960
C901950012 Number of successful handovers from selected cell to the adjacent cell due to better downlink
strength ....................................................................... 2962
cell to the adjacent cell due to PBGT ................................ 2964
to the adjacent cell due to large TA .................................. 2965
cell to the adjacent cell due to large TA ............................ 2966
to the adjacent cell due to high traffic .............................. 2968
cell to the adjacent cell due to high traffic ......................... 2969
2947
Overview
Counters of PS adjacent cell handover measurement counts the
number of MS's performing outgoing handover towards specific
adjacent cell and the number of MS's performing incoming handover from specific adjacent cell. It reflects the PS handover condition between the local cell and adjacent cells and helps improve
adjacent cell planning, thereby improves the PS service in cells
through PS handover.
handover attempts on the
adjacent cell
Statistics object
Description
Cell
This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell. This counter is used to
find out the number of MS's outgoing handover attempts from the
local cell to a specific cell. It helps check the direction of handover
between cells.
when the source cell sends the radio channel request message to
the destination cell. The measurement point is A, as shown in
Figure 2769.
ON THE ADJACENT CELL - (1)
POINT
OF
NUMBER
For SGSN-controlled external handover, the counter increments

when the source cell sends the handover request message to
SGSN. The measurement point is A, as shown in Figure 2770.
2948
Chapter 99 PS Adjacent Cell Handover Measurement

ON THE ADJACENT CELL - (2)
Unit
POINT
OF
NUMBER
Times
successful handovers from
cell
Statistics object
Description
Cell
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell. This counter is used to
find out the number of MS's successful outgoing handovers from
the local cell to a specific cell. It helps check the direction of handover between cells.
when the source cell receives the handover completion message
from the destination cell. The measurement point is A, as shown
in Figure 2771.
FIGURE 2771 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVERS
FROM SELECTED CELL TO THE ADJACENT CELL - (1)
2949
For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN and if the release is
due to handover success, then the counter increments. The measurement point is A, as shown in Figure 2772.
FROM SELECTED CELL TO THE ADJACENT CELL - (2)
Unit
Times
cell
Statistics object
Description
Cell
This counter counts the number of MS's incoming handover attempts from a specific cell to the local cell. This counter is used
to find out the number of MS's incoming handover attempts from
a specific cell to the local cell. It helps check the direction of handover between cells.
when the destination cell receives the radio channel request
message from the source cell. The measurement point is A, as
2950

FROM ADJACENT CELL TO THE SELECTED CELL - (1)

when the destination cell receives the handover request message
from SGSN. The measurement point is A, as shown in Figure 2774.
Unit
Times
cell
Statistics object
Description
Cell
This counter counts the number of MS's successful incoming handovers from a specific cell to the local cell. This counter is used to
find out the number of MS's successful incoming handovers from
a specific cell to the local cell. It helps check the direction of handover between cells.
when the destination cell receives the handover completion mes-
2951
sage from MS. The measurement point is A, as shown in Figure

2775.

when the destination cell receives the handover completion message from MS. The measurement point is A, as shown in Figure
2776.
Unit
Times
cell due to better uplink
quality
Statistics object
Description
2952
Cell
This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to uplink qulaity.
This counter is used to find out the number of MS's outgoing han-
dover attempts from the local cell to a specific cell due to uplink
quality. It helps check the direction of handover between cells.
For BSC-controlled inter-cell handover, when the destination cell
receives the radio channel request message from the source cell,
if the handover is due to uplink quality, the counter increments.
FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER UPLINK QUALITY
- (1)
For SGSN-controlled external handover, when the destination cell

receives the handover request message from SGSN, if the handover is due to uplink quality, the counter increments. The measurement point is A, as shown in Figure 2778.
- (2)
Unit
Times
2953
cell due to better downlink
quality
Statistics object
Description
Cell
This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to downlink qulaity.
This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to downlink
if the handover is due to downlink quality, the counter increments.
FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER DOWNLINK
QUALITY - (1)

receives the handover request message from SGSN, if the handover is due to downlink quality, the counter increments. The
2954

QUALITY - (2)
Unit
Times
quality
Statistics object
Description
Cell
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to uplink qulaity.
This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to uplink
For BSC-controlled inter-cell handover, when the source cell receives the handover completion message from the destination cell,
if the handover is due to uplink quality, the counter increments.
2955

- (1)
For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN, if the release is due
to handover success and the handover is due to uplink quality, the
Figure 2782.
- (2)
Unit
Times
quality
Statistics object
Description
2956
Cell
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to downlink qulaity.
This counter is used to find out the number of MS's successful out-
going handovers from the local cell to a specific cell due to downlink
if the handover is due to downlink quality, the counter increments.
QUALITY - (1)
to handover success and the handover is due to downlink quality,
Figure 2784.
QUALITY - (2)
Unit
Times
2957
strength
Statistics object
Description
Cell
This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to uplink strength.
This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to uplink
strength. It helps check the direction of handover between cells.
if the handover is due to uplink strength, the counter increments.
FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER UPLINK
STRENGTH - (1)

receives the handover request message from SGSN, if the handover is due to uplink strength, the counter increments. The measurement point is A, as shown in Figure 2786.
2958

STRENGTH - (2)
Unit
Times
strength
Statistics object
Description
Cell
This counter counts the number of MS's outgoing handover
attempts from the local cell to a specific cell due to downlink
strength. This counter is used to find out the number of MS's
outgoing handover attempts from the local cell to a specific cell
due to downlink strength. It helps check the direction of handover
between cells.
receives the radio channel request message from the source cell, if
the handover is due to downlink strength, the counter increments.
2959

STRENGTH - (1)

receives the handover request message from SGSN, if the handover is due to downlink strength, the counter increments. The
STRENGTH - (2)
Unit
Times
strength
Statistics object
Description
2960
Cell
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to uplink strength.
This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to uplink
if the handover is due to uplink strength, the counter increments.
STRENGTH - (1)
to handover success and the handover is due to uplink strength,
Figure 2790.
STRENGTH - (2)
Unit
Times
2961
strength
Statistics object
Description
Cell
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to downlink strength.
This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to downlink
if the handover is due to downlink strength, the counter increments. The measurement point is A, as shown in Figure 2791.
STRENGTH - (1)
to handover success and the handover is due to downlink strength,
Figure 2792.
2962

STRENGTH - (2)
Unit
Times
cell due to PBGT
Statistics object
Description
Cell
This counter counts the number of MS's outgoing handover
attempts from the local cell to a specific cell due to PBGT. This
counter is used to find out the number of MS's outgoing handover
attempts from the local cell to a specific cell due to PBGT. It helps
if the handover is due to PBGT, the counter increments. The measurement point is A, as shown in Figure 2793.
FROM SELECTED CELL TO THE ADJACENT CELL DUE TO PBGT - (1)
2963

receives the handover request message from SGSN, if the handover is due to PBGT, the counter increments. The measurement
Unit
Times
cell due to PBGT
Statistics object
Description
Cell
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to PBGT. This counter
is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to PBGT. It helps
if the handover is due to PBGT, the counter increments. The measurement point is A, as shown in Figure 2795.
2964

to handover success and the handover is due to PBGT, the counter
Unit
Times
cell due to large TA
Statistics object
Description
Cell
This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to too large TA.
This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to too large
TA. It helps check the direction of handover between cells.
2965
if the handover is due to too large TA, the counter increments. The
FROM SELECTED CELL TO THE ADJACENT CELL DUE TO LARGE TA - (1)

receives the handover request message from SGSN, if the handover is due to too large TA, the counter increments. The measurement point is A, as shown in Figure 2798.
Unit
Times
cell due to large TA
Statistics object
Description
2966
Cell
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to too large TA. This
counter is used to find out the number of MS's successful outgoing
handovers from the local cell to a specific cell due to too large TA.
It helps check the direction of handover between cells.
if the handover is due to too large TA, the counter increments. The
FIGURE 2799 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVER
to handover success and the handover is due to too large TA, the
Figure 2800.
Unit
Times
2967
cell due to high traffic
Statistics object
Description
Cell
This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to too heavy traffic.
This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to too heavy
traffic. It helps check the direction of handover between cells.
if the handover is due to too heavy traffic, the counter increments.
FROM SELECTED CELL TO THE ADJACENT CELL DUE TO HIGH TRAFFIC - (1)

receives the handover request message from SGSN, if the handover is due to too heavy traffic, the counter increments. The
2968

Unit
Times
cell due to high traffic
Statistics object
Description
Cell
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to too heavy traffic.
This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to too
heavy traffic. It helps check the direction of handover between
cells.
if the handover is due to too heavy traffic, the counter increments.
2969
to handover success and the handover is due to too heavy traffic,
Figure 2804.
Unit
2970
Times
Chapter
100
LAPDm Measurement
Table of Contents
Overview...................................................................... 2972
C902000001 Number of Error Indications due to T200 expired
on SDCCH .................................................................... 2973
C902000002 Number of Error Indications due to unsolicited
message on SDCCH ....................................................... 2973
DM response on SDCCH ................................................. 2974
error on SDCCH ............................................................ 2975
C902000005 Number of Error Indications due to frame content error on SDCCH ...................................................... 2975
C902000006 Number of Error Indications due to SABM command on SDCCH ........................................................... 2976
on TCH/F...................................................................... 2977
message on TCH/F......................................................... 2977
DM response on TCH/F ................................................... 2978
error on TCH/F .............................................................. 2979
C902000011 Number of Error Indications due to frame content error on TCH/F ....................................................... 2979
C902000012 Number of Error Indications due to SABM command on TCH/F ............................................................. 2980
on TCH/H ..................................................................... 2981
message on TCH/H ........................................................ 2981
DM response on TCH/H .................................................. 2982
error on TCH/H ............................................................. 2983
C902000017 Number of Error Indications due to frame content error on TCH/H ....................................................... 2983
C902000018 Number of Error Indications due to SABM command on TCH/H ............................................................ 2984
C902000019 Number of Release Indications due to T200 expired on SDCCH ............................................................ 2985
C902000020 Number of Release Indications due to unsolicited
DM response on SDCCH ................................................. 2985
C902000021 Number of Release Indications due to sequence
error on SDCCH ............................................................ 2986
C902000022 Number of Release Indications due to T200 expired on TCH/F (signaling) .............................................. 2987
2971

DM response on TCH/F (signaling) ................................... 2988
error on TCH/F (signaling) .............................................. 2988
C902000025 Number of Release Indications due to T200 expired on TCH/F (speech)................................................. 2989
DM response on TCH/F (speech) ...................................... 2990
error on TCH/F (speech) ................................................. 2991
C902000028 Number of Release Indications due to T200 expired on TCH/F (data) .................................................... 2991
DM response on TCH/F (data) ......................................... 2992
error on TCH/F (data) .................................................... 2993
C902000031 Number of Release Indications due to T200 expired on TCH/H (signaling).............................................. 2994
DM response on TCH/H (signaling)................................... 2994
error on TCH/H (signaling).............................................. 2995
C902000034 Number of Release Indications due to T200 expired on TCH/H (speech) ................................................ 2996
DM response on TCH/H (speech) ..................................... 2997
error on TCH/H (speech) ................................................ 2997
C902000037 Number of Release Indications due to T200 expired on TCH/H (data).................................................... 2998
DM response on TCH/H (data) ......................................... 2999
error on TCH/H (data) .................................................... 3000
C902000040 Number of Release Indications without Error Ind
on SDCCH .................................................................... 3000
on TCH/F (signaling) ...................................................... 3001
on TCH/F (speech)......................................................... 3001
on TCH/F (data) ............................................................ 3002
on TCH/H (signaling) ..................................................... 3002
on TCH/H (speech) ........................................................ 3002
on TCH/H (data)............................................................ 3003
Overview
LAPDm measurement is used to find out the number of LAPDm-related processes occurred, such as BTS sending the ERROR INDICATION message and the RELEASE INDICATION message to BSC
due to LAPDm's transceiving messages.
2972
Chapter 100 LAPDm Measurement
Error Indications due to
T200 expired on SDCCH
Description
During the call process, LAPDm sends I frame, SAMB frame and
DISC frame on SDCCH. If there is no response for a long time,
LAPDm sends the ERROR INDICATION message to BSC, and the
message contains the cause of "T200 expired".
Usage
This counter counts the number of ERROR INDICATION messages,

received by BSC from BTS, that contain the cause of "T200 expired".
Measurement
Point
The counter counts when BSC receives the ERROR INDICATION

FIGURE 2805 NUMBER
ON SDCCH
Unit
OF
ERROR INDICATIONS
DUE TO
T200
EXPIRED
Times
unsolicited message on
SDCCH
Description
During the call process, if LAPDm receives unexpected message

on SDCCH, it will send the ERROR INDICATION message to BSC,
and the message contains the cause of "unsolicited message".
Usage

received by BSC from BTS, that contain the cause of "unsolicited
message".
2973

Measurement
Point

MESSAGE ON SDCCH
Unit
ERROR INDICATIONS
DUE TO UNSOLICITED
Times
unsolicited DM response on
SDCCH
Description
During the call process, if LAPDm receives unexpected DM response message on SDCCH, it will send the ERROR INDICATION
message to BSC, and the message contains the cause of "unsolicited DM response".
Usage

DM response".
Measurement
Point

RESPONSE ON SDCCH
Unit
2974
ERROR INDICATIONS
Times
DUE TO UNSOLICITED
DM
sequence error on SDCCH
Description
During the call process, if LAPDm receives message with incorrect

sequence number on SDCCH, it will send the ERROR INDICATION
message to BSC, and the message contains the cause of "sequence
error".
Usage

received by BSC from BTS, that contain the cause of "sequence
error".
Measurement
Point

FIGURE 2808 NUMBER
ON SDCCH
Unit
OF
ERROR INDICATIONS
DUE TO SEQUENCE ERROR
Times
frame content error on
SDCCH
Description

content on SDCCH, it will send the ERROR INDICATION message
to BSC, and the message contains the cause of "frame content
error".
Usage

received by BSC from BTS, that contain the cause of "frame content error".
Measurement
Point

2975

ERROR ON SDCCH
Unit
ERROR INDICATIONS
DUE TO FRAME CONTENT
Times
SABM command on SDCCH
Description
During the call process, if LAPDm receives SABM frame after the
SDCCH connection is established, LAPDm will send the ERROR INDICATION message to BSC, and the message contains the cause
of "SABM command".
Usage

received by BSC from BTS, that contain the cause of "SABM command".
Measurement
Point

FIGURE 2810
ON SDCCH
Unit
2976
NUMBER
OF
ERROR INDICATIONS
Times
DUE TO
SABM
COMMAND
T200 expired on TCH/F
Description
DISC frame on TCH/F. If there is no response for a long time,
LAPDm will send the ERROR INDICATION message to BSC, and
the message contains the cause of "T200 expired".
Usage

Measurement
Point

FIGURE 2811 NUMBER
ON TCH/F
Unit
OF
ERROR INDICATIONS
DUE TO
T200
EXPIRED
Times
TCH/F
Description

on TCH/F, it will send the ERROR INDICATION message to BSC,
Usage

message".
Measurement
Point

2977

MESSAGE ON TCH/F
Unit
ERROR INDICATIONS
DUE TO UNSOLICITED
Times
TCH/F
Description
During the call process, if LAPDm receives unexpected DM response message on TCH/F, it will send the ERROR INDICATION
Usage

DM response".
Measurement
Point

FIGURE 2813 C902000009
Unit
2978
Times
sequence error on TCH/F
Description

sequence number on TCH/F, it will send the ERROR INDICATION
error".
Usage

error".
Measurement
Point

FIGURE 2814 NUMBER
ON TCH/F
Unit
OF
ERROR INDICATIONS
Times
TCH/F
Description

content on TCH/F, it will send the ERROR INDICATION message to
BSC, and the message contains the cause of "frame content error".
Usage

Measurement
Point

2979

ERROR ON TCH/F
Unit
ERROR INDICATIONS
Times
SABM command on TCH/F
Description
TCH/F connection is established, LAPDm will send the ERROR INDICATION message to BSC, and the message contains the cause
of "SABM command".
Usage

Measurement
Point

FIGURE 2816
ON TCH/F
Unit
2980
NUMBER
OF
ERROR INDICATIONS
Times
DUE TO
SABM
COMMAND
T200 expired on TCH/H
Description
DISC frame on TCH/H. If there is no response for a long time,
LAPDm will send the ERROR INDICATION message to BSC, and
the message contains the cause of "T200 expired".
Usage

Measurement
Point

FIGURE 2817 NUMBER
ON TCH/H
Unit
OF
ERROR INDICATIONS
DUE TO
T200
EXPIRED
Times
TCH/H
Description

on TCH/H, it will send the ERROR INDICATION message to BSC,
Usage

message".
Measurement
Point

2981

MESSAGE ON TCH/H
Unit
ERROR INDICATIONS
DUE TO UNSOLICITED
Times
TCH/H
Description
During the call process, if LAPDm receives unexpected DM response message on TCH/H, it will send the ERROR INDICATION
Usage

DM response".
Measurement
Point

RESPONSE ON TCH/H
Unit
2982
ERROR INDICATIONS
Times
DUE TO UNSOLICITED
DM
sequence error on TCH/H
Description

sequence number on TCH/H, it will send the ERROR INDICATION
error".
Usage

error".
Measurement
Point

FIGURE 2820 NUMBER
ON TCH/H
Unit
OF
ERROR INDICATIONS
Times
TCH/H
Description

content on TCH/H, it will send the ERROR INDICATION message
to BSC, and the message contains the cause of "frame content
error".
Usage

Measurement
Point

2983

ERROR ON TCH/H
Unit
ERROR INDICATIONS
Times
SABM command on TCH/H
Description
TCH/H connection is established, LAPDm will send the ERROR INDICATION message to BSC, and the message contains the cause
of "SABM command".
Usage

Measurement
Point

FIGURE 2822
ON TCH/H
Unit
2984
NUMBER
OF
ERROR INDICATIONS
Times
DUE TO
SABM
COMMAND
Release Indications due to
T200 expired on SDCCH
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION
message to BSC. When the call is on SDCCH and is stable, BSC
simultaneously receives the ERROR INDICATION message and the
RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "T200 expired".
Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of
"T200 expired".
Measurement
Point
When the call is in stable status, the counter counts when BSC
RELEASE INDICATION message (the ERROR INDICATION message
contains the cause of "T200 expired"). The measurement point is
FIGURE 2823
ON SDCCH
Unit
NUMBER
OF
RELEASE INDICATIONS
DUE TO
T200
EXPIRED
Times
SDCCH
Description
RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "unsolicited DM response".
2985
Usage
"unsolicited DM response".
Measurement
Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the
contains the cause of "unsolicited DM response"). The measurement point is A, as shown in Figure 2824.
FIGURE 2824 NUMBER OF RELEASE INDICATIONS
DM RESPONSE ON SDCCH
Unit
DUE TO UNSOLICITED
Times
sequence error on SDCCH
Description
RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "sequence error".
Usage
"sequence error".
Measurement
Point
2986
contains the cause of "sequence error"). The measurement point
FIGURE 2825
ON SDCCH
Unit
NUMBER
OF
RELEASE INDICATIONS
Times
Release Indications due
to T200 expired on TCH/F
(signaling)
Description
message to BSC. When the call is on TCH/F and is stable, BSC simultaneously receives the ERROR INDICATION message and the
Usage
"T200 expired".
Measurement
Point
FIGURE 2826 NUMBER
TCH/F (SIGNALING)
Unit
OF
RELEASE INDICATIONS
DUE TO
T200
EXPIRED ON
Times
2987
TCH/F (signaling)
Description
Usage
Measurement
Point
FIGURE 2827 NUMBER OF RELEASE
RESPONSE ON TCH/F (SIGNALING)
Unit
INDICATIONS
DUE TO UNSOLICITED
DM
Times
(signaling)
Description
2988
Usage
"sequence error".
Measurement
Point
ON TCH/F (SIGNALING)
Unit
RELEASE INDICATIONS
Times
(speech)
Description
Usage
"T200 expired".
Measurement
Point
2989

ON TCH/F (SPEECH)
Unit
RELEASE INDICATIONS
DUE TO
T200
EXPIRED
Times
TCH/F (speech)
Description
Usage
Measurement
Point
DM RESPONSE ON TCH/F (SPEECH)
Unit
2990
Times
DUE TO UNSOLICITED
(speech)
Description
Usage
"sequence error".
Measurement
Point
ON TCH/F (SPEECH)
Unit
RELEASE INDICATIONS
Times
(data)
Description
2991
Usage
"T200 expired".
Measurement
Point
FIGURE 2832 NUMBER
TCH/F (DATA)
Unit
OF
RELEASE INDICATIONS
DUE TO
T200
EXPIRED ON
Times
TCH/F (data)
Description
Usage
Measurement
Point
2992

DM RESPONSE ON TCH/F (DATA)
Unit
DUE TO UNSOLICITED
Times
(data)
Description
Usage
"sequence error".
Measurement
Point
ON TCH/F (DATA)
Unit
RELEASE INDICATIONS
Times
2993
to T200 expired on TCH/H
(signaling)
Description
message to BSC. When the call is on TCH/H and is stable, BSC
Usage
"T200 expired".
Measurement
Point
FIGURE 2835 NUMBER
TCH/H (SIGNALING)
Unit
OF
RELEASE INDICATIONS
DUE TO
T200
EXPIRED ON
Times
TCH/H (signaling)
Description
2994
Usage
Measurement
Point
FIGURE 2836 NUMBER OF RELEASE INDICATIONS DUE TO UNSOLICITED
RESPONSE ON TCH/H (SIGNALING)
Unit
DM
Times
(signaling)
Description
Usage
"sequence error".
Measurement
Point
2995

ON TCH/H (SIGNALING)
Unit
RELEASE INDICATIONS
Times
(speech)
Description
Usage
"T200 expired".
Measurement
Point
ON TCH/H (SPEECH)
Unit
2996
RELEASE INDICATIONS
Times
DUE TO
T200
EXPIRED
TCH/H (speech)
Description
Usage
Measurement
Point
DM RESPONSE ON TCH/H (SPEECH)
Unit
DUE TO UNSOLICITED
Times
(speech)
Description
2997
Usage
"sequence error".
Measurement
Point
ON TCH/H (SPEECH)
Unit
ERROR INDICATIONS
Times
(data)
Description
Usage
"T200 expired".
Measurement
Point
2998

ON TCH/H (DATA)
Unit
RELEASE INDICATIONS
DUE TO
T200
EXPIRED
Times
TCH/H (data)
Description
Usage
Measurement
Point
DM RESPONSE ON TCH/H (DATA)
Unit
DUE TO UNSOLICITED
Times
2999
(data)
Description
Usage
"sequence error".
Measurement
Point
ON TCH/H (DATA)
Unit
RELEASE INDICATIONS
Times
Release Indications without
Error Ind on SDCCH
Description
Usage
3000
This counter counts the times of receiving the Abis Rel Ind message without receiving the Abis Error Ind message when the MS
occupies the SDCCH.
None
Measurement
Point
None
Unit
Time
C902000041 Number
of Release Indications
without Error Ind on TCH/F
(signaling)
Description
occupies the TCH/F signaling channel.
Usage
None
Measurement
Point
None
Unit
Time
Error Ind on TCH/F (speech)
Description
occupies the TCH/F speech channel.
Usage
None
Measurement
Point
None
Unit
Time
3001
Error Ind on TCH/F (data)
Description
occupies the TCH/F data channel.
Usage
None
Measurement
Point
None
Unit
Time
C902000044 Number
of Release Indications
without Error Ind on TCH/H
(signaling)
Description
occupies the TCH/H signaling channel.
Usage
None
Measurement
Point
None
Unit
Time
Error Ind on TCH/H (speech)
Description
3002
occupies the TCH/H speech channel.
Usage
None
Measurement
Point
None
Unit
Time
Error Ind on TCH/H (data)
Description
occupies the TCH/H data channel.
Usage
None
Measurement
Point
None
Unit
Time
3003
3004
Chapter
101
Access Control Detailed

Cause Measurement
Table of Contents
Overview...................................................................... 3005
C902010001 Number of PS Uplink BandWidth Allocated More
than Overbooking .......................................................... 3006
C902010002 Number of PS Uplink BandWidth Measured More
than C2 ....................................................................... 3007
C902010003 Number of that Sum of PS Uplink BandWidth
Measured and Current BandWidth Allocated More than
C1 ............................................................................... 3008
C902010004 Number of PS Downlink BandWidth Allocated
More than Overbooking .................................................. 3009
C902010005 Number of PS Downlink BandWidth Measured
More than C2 ................................................................ 3010
C902010006 Number of that Sum of PS Downlink BandWidth Measured and Current BandWidth Allocated More than
C1 ............................................................................... 3011
C902010007 Number of CS Uplink BandWidth Allocated More
than Overbooking ......................................................... 3012
C902010008 Number of CS Uplink BandWidth Measured More
than C2........................................................................ 3012
C902010009 Number of that Sum of CS Uplink BandWidth
Measured and Current BandWidth Allocated More than
C1 ............................................................................... 3013
C902010010 Number of CS Downlink BandWidth Allocated
More than Overbooking .................................................. 3014
C902010011 Number of CS Downlink BandWidth Measured
More than C2 ................................................................ 3015
C902010012 Number of that Sum of CS Downlink BandWidth Measured and Current BandWidth Allocated More than
C1 ............................................................................... 3016
Overview
Access control detailed cause measurement involves uplink/downlink CS and PS access process.
The measurement point of access control cause statistics for
PS-bandwidth allocation is shown in Figure 2844.
3005
FIGURE 2844 ACCESS CONTROL
OF
PS-BANDWIDTH ALLOCATION
The measurement point of access control cause statistics for

CS-bandwidth allocation is shown in Figure 2845.
FIGURE 2845 ACCESS CONTROL
OF
CS-BANDWIDTH ALLOCATION
Uplink BandWidth Allocated
More than Overbooking
Description
This counter counts the number of PS uplink bandwidth access

rejects due to allocated uplink bandwidth exceeding OverBooking.
When BSC has new PS service to be activated, if BSC control plane
judges that the total current theoretically-allocated uplink bandwidth plus the theoretically-allocated uplink bandwidth needed by
the service exceeds the predefined rated bandwidth of the resource
pool, that is, OverBooking, the counter increments.
Usage
The counter is used to find out the frequency of allocated uplink

bandwidth for PS service exceeding OverBooking.
Measurement
Point
3006

judges that the allocated uplink bandwidth exceeds OverBooking,
Figure 2846.
Chapter 101 Access Control Detailed Cause Measurement

THAN OVERBOOKING
Unit
PS UPLINK BANDWIDTH ALLOCATED MORE
Times
Uplink BandWidth Measured
More than C2
Description
This counter counts the number of PS uplink bandwidth access rejects due to actual uplink bandwidth exceeding C2, which is the
safe allocation lower limit about bandwidth at the resource pool.
judges that the actual uplink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth
at the resource pool, the counter increments.
Usage
This counter is used to find out the frequency of actual uplink bandwidth for PS service exceeding C2, which is the safe allocation
lower limit about bandwidth at the resource pool.
Measurement
Point

at the resource pool, the counter counts. The measurement point
FIGURE 2847 NUMBER
C2
OF
PS UPLINK BANDWIDTH MEASURED MORE
THAN
3007
Unit
Times
that Sum of PS Uplink
BandWidth Measured
and Current BandWidth
Allocated More than C1
Description
Usage
This counter counts the number of PS uplink bandwidth access rejects due to actual uplink bandwidth plus the bandwidth allocated
for the current service exceeding C1, which is the safe allocation
upper limit about bandwidth at the resource pool. When BSC has
new PS service to be activated, if the following two conditions are
satisfied, the counter increments:
BSC control plane judges that the actual uplink bandwidth of

the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool.
The actual uplink bandwidth of the resource pool plus theoretically-allocated uplink bandwidth for the service exceeds C1,
which is the safe allocation upper limit about bandwidth at the
resource pool.
This counter is used to find out the frequency of actual uplink bandwidth for PS service plus the bandwidth allocated for the service
exceeding C1, which is the safe allocation upper limit about bandwidth at the resource pool.
Measurement
Point

judges that the actual uplink bandwidth plus the uplink bandwidth
allocated for the service exceeds C1, which is the safe allocation
upper limit about bandwidth at the resource pool, the counter
counts. The measurement point is A, as shown in Figure 2848.
FIGURE 2848
AND CURRENT
3008
NUMBER OF THAT SUM OF PS UPLINK BANDWIDTH MEASURED

BANDWIDTH ALLOCATED MORE THAN C1
Unit
Times
PS Downlink BandWidth
Allocated More than
Overbooking
Description
This counter counts the number of PS downlink bandwidth access

rejects due to allocated downlink bandwidth exceeding OverBooking. When BSC has new PS service to be activated, if BSC control
plane judges that the total current theoretically-allocated downlink bandwidth plus the theoretically-allocated downlink bandwidth
needed by the service exceeds the predefined rated bandwidth of
the resource pool, that is, OverBooking, the counter increments.
Usage
The counter is used to find out the frequency of allocated downlink

bandwidth for PS service exceeding OverBooking.
Measurement
Point

judges that the allocated downlink bandwidth exceeds OverBooking, the counter counts. The measurement point is A, as shown in
Figure 2849.
FIGURE 2849 NUMBER
THAN OVERBOOKING
Unit
OF
PS DOWNLINK BANDWIDTH ALLOCATED MORE
Times
3009
PS Downlink BandWidth
Measured More than C2
Description

rejects due to actual downlink bandwidth exceeding C2, which is
the safe allocation lower limit about bandwidth at the resource
pool. When BSC has new PS service to be activated, if BSC control
plane judges that the actual downlink bandwidth of the resource
pool exceeds C2, which is the safe allocation lower limit about
bandwidth at the resource pool, the counter increments.
Usage
This counter is used to find out the frequency of actual downlink

bandwidth for PS service exceeding C2, which is the safe allocation
Measurement
Point

judges that the actual downlink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth
FIGURE 2850 NUMBER
THAN C2
Unit
3010
OF
PS DOWNLINK BANDWIDTH MEASURED MORE
Times
that Sum of PS Downlink
BandWidth Measured
Description
Usage

rejects due to actual downlink bandwidth plus the bandwidth allocated for the current service exceeding C1, which is the safe
allocation upper limit about bandwidth at the resource pool. When
BSC has new PS service to be activated, if the following two conditions are satisfied, the counter increments:
BSC control plane judges that the actual downlink bandwidth

of the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool.
The actual downlink bandwidth of the resource pool plus theoretically-allocated downlink bandwidth for the service exceeds
C1, which is the safe allocation upper limit about bandwidth at
the resource pool.

bandwidth for PS service plus the bandwidth allocated for the service exceeding C1, which is the safe allocation upper limit about
bandwidth at the resource pool.
Measurement
Point

judges that the actual downlink bandwidth plus the downlink bandwidth allocated for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, the counter
FIGURE 2851 NUMBER OF THAT SUM OF PS DOWNLINK BANDWIDTH
MEASURED AND CURRENT BANDWIDTH ALLOCATED MORE THAN C1
Unit
Times
3011
Uplink BandWidth Allocated
More than Overbooking
Description
This counter counts the number of CS uplink bandwidth access

rejects due to allocated uplink bandwidth exceeding OverBooking.
When BSC has new CS service to be activated, if BSC control plane
judges that the total current theoretically-allocated uplink bandwidth plus the theoretically-allocated uplink bandwidth needed by
the service exceeds the predefined rated bandwidth of the resource
pool, that is, OverBooking, the counter increments.
Usage
The counter is used to find out the frequency of allocated uplink

bandwidth for CS service exceeding OverBooking.
Measurement
Point

judges that the allocated uplink bandwidth exceeds OverBooking,
Figure 2852.
THAN OVERBOOKING
Unit
CS UPLINK BANDWIDTH ALLOCATED MORE
Times
Uplink BandWidth Measured
More than C2
Description
3012
This counter counts the number of CS uplink bandwidth access rejects due to actual uplink bandwidth exceeding C2, which is the
safe allocation lower limit about bandwidth at the resource pool.
at the resource pool, the counter increments.
Usage
This counter is used to find out the frequency of actual uplink bandwidth for CS service exceeding C2, which is the safe allocation
Measurement
Point

FIGURE 2853 NUMBER
C2
Unit
OF
CS UPLINK BANDWIDTH MEASURED MORE
THAN
Times
that Sum of CS Uplink
BandWidth Measured
Description
This counter counts the number of CS uplink bandwidth access rejects due to actual uplink bandwidth plus the bandwidth allocated
for the current service exceeding C1, which is the safe allocation
upper limit about bandwidth at the resource pool. When BSC has
new CS service to be activated, if the following two conditions are
satisfied, the counter increments:
BSC control plane judges that the actual uplink bandwidth of

the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool.
The actual uplink bandwidth of the resource pool plus theoretically-allocated uplink bandwidth for the service exceeds C1,
which is the safe allocation upper limit about bandwidth at the
resource pool.
3013
Usage
This counter is used to find out the frequency of actual uplink bandwidth for CS service plus the bandwidth allocated for the service
exceeding C1, which is the safe allocation upper limit about bandwidth at the resource pool.
judges that the actual uplink bandwidth plus the uplink bandwidth
allocated for the service exceeds C1, which is the safe allocation
upper limit about bandwidth at the resource pool, the counter
FIGURE 2854
AND CURRENT
NUMBER OF THAT SUM OF CS UPLINK BANDWIDTH MEASURED

BANDWIDTH ALLOCATED MORE THAN C1
Measurement
Point
Unit
Times
CS Downlink BandWidth
Allocated More than
Overbooking
Description
This counter counts the number of CS downlink bandwidth access

rejects due to allocated downlink bandwidth exceeding OverBooking. When BSC has new CS service to be activated, if BSC control
plane judges that the total current theoretically-allocated downlink bandwidth plus the theoretically-allocated downlink bandwidth
needed by the service exceeds the predefined rated bandwidth of
the resource pool, that is, OverBooking, the counter increments.
Usage
The counter is used to find out the frequency of allocated downlink

bandwidth for CS service exceeding OverBooking.
Measurement
Point
3014

judges that the allocated downlink bandwidth exceeds OverBook-
ing, the counter counts. The measurement point is A, as shown in

Figure 2855.
FIGURE 2855 NUMBER
THAN OVERBOOKING
Unit
OF
CS DOWNLINK BANDWIDTH ALLOCATED MORE
Times
CS Downlink BandWidth
Measured More than C2
Description

rejects due to actual downlink bandwidth exceeding C2, which is
the safe allocation lower limit about bandwidth at the resource
pool. When BSC has new CS service to be activated, if BSC control plane judges that the actual downlink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit
about bandwidth at the resource pool, the counter increments.
Usage

bandwidth for CS service exceeding C2, which is the safe allocation
Measurement
Point

judges that the actual downlink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth
3015
FIGURE 2856
THAN C2
Unit
NUMBER
OF
CS DOWNLINK BANDWIDTH MEASURED MORE
Times
that Sum of CS Downlink
BandWidth Measured
Description
Usage

rejects due to actual downlink bandwidth plus the bandwidth allocated for the current service exceeding C1, which is the safe
allocation upper limit about bandwidth at the resource pool. When
BSC has new CS service to be activated, if the following two conditions are satisfied, the counter increments:
BSC control plane judges that the actual downlink bandwidth

of the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool.
The actual downlink bandwidth of the resource pool plus theoretically-allocated downlink bandwidth for the service exceeds
C1, which is the safe allocation upper limit about bandwidth at
the resource pool.

bandwidth for CS service plus the bandwidth allocated for the service exceeding C1, which is the safe allocation upper limit about
bandwidth at the resource pool.
Measurement
Point
3016

judges that the actual downlink bandwidth plus the downlink bandwidth allocated for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, the counter
FIGURE 2857 NUMBER OF THAT SUM OF CS DOWNLINK BANDWIDTH

MEASURED AND CURRENT BANDWIDTH ALLOCATED MORE THAN C1
Unit
Times
3017
3018
Chapter
102
BSC Group Call Setup

Measurement
Table of Contents
Overview...................................................................... 3019
C902020001 Number of VGCS setup attempts................... 3019
C902020002 Number of VGCS setup success .................... 3020
C902020003 Number of VGCS setup failure ...................... 3021
C902020004 Number of VBS setup attempts ..................... 3021
C902020005 Number of VBS setup success....................... 3022
C902020006 Number of VBS setup failure ........................ 3023
Overview
This measurement performs statistics for relevant performance indices during the setup process of VGCS service and VBS service,
including the number of attempts, successes, and failures of service setup.
Statistics object: BSC
VGCS setup attempts
Description
This counter counts the number of attempts of setting up VGCS.

When BSC receives the VGCS SETUP message (indicating VGCS
call), the counter increments. The measurement point is A1, as
3019
FIGURE 2858 ESTABLISHING VGCS (SUCCESS)

Unit
Statistics Object
Times
BSC
VGCS setup success
Description
This counter counts the number of successes in setting up VGCS.

When BSC sends the VGCS SETUP ACKNOWLEDGE message (corresponding to VGCS call) to MSC, the counter increments. The
FIGURE 2859 ESTABLISHING VGCS (SUCCESS)

Unit
3020
Times
Chapter 102 BSC Group Call Setup Measurement
Statistics Object
BSC
VGCS setup failure
Description
This counter counts the number of failures in setting up VGCS.

When BSC sends the VGCS SETUP REFUSE message (corresponding to VGCS call) to MSC, the counter increments. The measurement point is A1, as shown in Figure 2860.
FIGURE 2860 ESTABLISHING VGCS (FAILURE)

Unit
Statistics Object
Times
BSC
VBS setup attempts
Description
This counter counts the number of attempts of setting up VBS.

When BSC receives the VBS SETUP message (indicating VBS call),
in Figure 2861.
3021
FIGURE 2861 ESTABLISHING VBS (SUCCESS)

Unit
Statistics Object
Times
BSC
VBS setup success
Description
This counter counts the number of BSC's successfully setting up

VBS channel in a cell. When BSC sends the VBS SETUP ACKNOWLEDGE message (corresponding to VBS call) to MSC, the counter
2862.
FIGURE 2862 ESTABLISHING VBS (SUCCESS)

Unit
3022
Times
Chapter 102 BSC Group Call Setup Measurement
Statistics Object
BSC
VBS setup failure
Description
This counter counts the number of failures in setting up VBS. When

BSC sends the VBS SETUP REFUSE message (corresponding to VBS
call) to MSC, the counter increments. The measurement point is
FIGURE 2863 ESTABLISHING VBS (FAILURE)

Unit
Statistics Object
Times
BSC
3023
3024
Chapter
103
VGCS Measurement
Table of Contents
Overview...................................................................... 3026
C902030001 Number of VGCS assignment attempts .......... 3026
C902030002 Number of VGCS assignment success ............ 3027
C902030003 Number of VGCS assignment failure .............. 3027
C902030004 Number of VGCS Inter-BSC outgoing handover
attempts of Talker ......................................................... 3028
execution of Talker ........................................................ 3029
success of Talker ........................................................... 3030
failure of Talker ............................................................. 3031
C902030008 Number of VGCS Inter-BSC incoming handover
C902030011 Number of VGCS channel request attempts for
NOTIFICATION RESPONSE of Listener............................... 3034
C902030012 Number of VGCS channel request success for
C902030013 Number of VGCS channel request failure for NOTIFICATION RESPONSE of Listener................................... 3036
C902030014 Number of VGCS channel release for Listener
detection...................................................................... 3037
C902030015 Number of Talker drops due to radio link failure .............................................................................. 3038
C902030016 Number of Talker quit .................................. 3039
C902030017 Number of attempts for Listener uplink request ........................................................................... 3039
C902030018 Number of VGCS Intra-BSC Inter-cell outgoing
handover attempts of Talker............................................ 3040
handover execution of Talker........................................... 3041
handover success of Talker ............................................. 3042
handover failure of Talker ............................................... 3043
C902030022 Number of VGCS Intra-BSC Inter-cell incoming
C902030025 Number of NCH overflow of VGCS ................. 3046
3025
C902030026 Number of successes for Listener uplink request ........................................................................... 3047

C902030027 Number of failures for Listener uplink request ........................................................................... 3048
Overview
This measurement performs statistics for performance indices of
voice group call service flow, which involves VGCS assignment,
Talker handover, Listener notification response, and NCH overflow.
Statistics object: cell
VGCS assignment attempts
Description
This counter counts the number of assignment attempts due to

VGCS. When BSC receives the VGCS ASSIGNMENT REQUEST message (indicating VGCS call) of corresponding legal cell from MSC,
in Figure 2864.
FIGURE 2864 VGCS RESOURCE ASSIGNMENT SUCCESS

Unit
3026
Times
Chapter 103 VGCS Measurement
Statistics Object
Cell
VGCS assignment success
Description
This counter counts the number of successful assignments due to

VGCS. When BSC sends the VGCS ASSIGNMENT RESULT message
(corresponding to VGCS call) to MSC as response to the VGCS
ASSIGNMENT REQUEST message, the counter increments. The
FIGURE 2865 VGCS RESOURCE ASSIGNMENT SUCCESS

Unit
Statistics Object
Times
Cell
VGCS assignment failure
Description
This counter counts the number of assignment failures due to

VGCS. When BSC receives the VGCS/VBS ASSIGNMENT REQUEST
message from MSC, if channel allocation for group call service
fails due to one or other reasons, BSC sends the VGCS/VBS
ASSIGNMENT FAILURE message to MSC (corresponding to VGCS
call), and the counter increments. The measurement point is A1,
3027
FIGURE 2866 VGCS RESOURCE ASSIGNMENT FAILURE

Unit
Statistics Object
Times
Cell
VGCS Inter-BSC outgoing
handover attempts of Talker
Description
3028

attempts initiated from the source cell by the talker who is having
the VGCS service. When BSC receives the measurement report
from the talker's mobile phone, if the handover decision indicates
inter-cell handover is required but the currently attempted cell is
not under the BSC, then the original BSC will send the A_HO_RQD
message to MSC to trigger inter-BSC cell handover. In such cases,
in Figure 2867.
FIGURE 2867 INTER-BSC INTER-CELL OUTGOING HANDOVER SUCCESS

Unit
Statistics Object
Times
Cell
handover execution of Talker
Description

executions initiated from the source cell by the talker who is having
from the talker's mobile phone, it performs handover decision. If
the handover decision indicates inter-cell handover is required but
the currently attempted cell is not under the BSC, then the original
BSC will send the A_HO_RQD message to MSC to trigger inter-BSC
cell handover. If the original BSC receives the handover command
returned by MSC, the counter increments. The measurement point
3029

Unit
Statistics Object
Times
Cell
handover success of Talker
Description
3030
This counter counts the number of successful inter-BSC outgoing

handovers initiated from the source cell by the talker who is having
cell handover. If the mobile phone is successfully accessed to the
destination cell, the source cell receives the release command or
the HANDOVER SUCCEEDED message issued from MSC. In such
cases, the counter increments. The measurement point is A3, as

Unit
Statistics Object
Times
Cell
handover failure of Talker
Description
This counter counts the number of failures in inter-BSC outgoing handover requests initiated by the talker from the source cell.
When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently
attempted cell is not under the BSC, then the original BSC will
send the A_HO_RQD message to MSC to trigger inter-BSC cell handover. If the original BSC receives the handover rejection message
returned from MSC or does not receive any response from MSC
before the protection timer expires, the counter increments. The
3031
FIGURE 2870 INTER-BSC INTER-CELL OUTGOING HANDOVER FAILURE

Unit
Statistics Object
Times
Cell
VGCS Inter-BSC incoming
Description
This counter counts the number of attempts of incoming handover

towards the local cell when the talker, who is having the VGCS
service, is performing inter-BSC handover. When the destination
cell receives the HANDOVER REQUEST message from MSC, if the
request is due to incoming handover, the counter increments. The
FIGURE 2871 INTER-BSC INTER-CELL INCOMING HANDOVER SUCCESS
3032
Unit
Statistics Object
Times
Cell
Description
This counter counts the number of executions of incoming handover towards the local cell when the talker, who is having the
VGCS service, is performing inter-BSC handover. When the destination cell receives the HANDOVER REQUEST message from MSC,
if the channel is allocated and activated successfully, the counter
2872.

Unit
Statistics Object
Times
Cell
Description

towards the local cell when the talker, who is having the VGCS service, is performing inter-BSC handover. When the destination cell
3033
receives the handover completion message from Um interface, if

the handover is inter-BSC incoming handover, the counter increments. The measurement point is A3, as shown in Figure 2873.

Unit
Statistics Object
Times
Cell
VGCS channel request
attempts for NOTIFICATION
RESPONSE of Listener
Description
3034
This counter counts the number of attempts of BSC's allocating

VGCS channel during the listener's notification response flow.
When BSC receives the EST IND (NOTIFICATION RESPONSE)
message, the counter increments. The measurement point is A1,
FIGURE 2874 LISTENER'S NOTIFICATION RESPONSE PROCESS (SUCCESS)

Unit
Statistics Object
Times
Cell
success for NOTIFICATION
Description
This counter counts the number of BSC's successfully allocating

When BSC successfully allocates VGCS channel and returns the
VGCS/VBS ASSIGNMENT STATUS message to MSC, the counter
2875.
3035

Unit
Statistics Object
Times
Cell
failure for NOTIFICATION
Description
3036
This counter counts the number of failures in BSC's allocating

When BSC fails in allocating VGCS channel, the counter increments. The measurement point is A1, as shown in Figure 2876.
FIGURE 2876 LISTENER'S NOTIFICATION RESPONSE PROCESS (FAILURE)

Unit
Statistics Object
Times
Cell
VGCS channel release for
Listener detection
Description
This counter counts the number of VGCS channel being released

due to that BSC cannot detect the listener. When BSC cannot detect the listener on VGCS channel, it releases the VGCS channel
and returns the VGCS ASSIGNMENT STATUS message to MSC, and
in Figure 2877.
3037
FIGURE 2877 NO LISTENER DETECTED
IN
CELL

Unit
Statistics Object
Times
Cell
Talker drops due to radio
link failure
Description
This counter counts the number of BSC's releasing uplink due to

radio link fault at the talker end. When BSC detects on VGCS
channel that the radio link is broken at the talker end or the new
talker fails in occupying the channel, it sends the UPLINK RELEASE
INDICATION message to MSC, and the counter increments. The
FIGURE 2878 TALKER GIVING UP CONVERSATION
DUE TO
RADIO LINK FAILURE

Unit
3038
Times
Statistics Object
Cell
Talker quit
Description
This counter counts the number of the talker's, who is on the group
call channel, giving up the conversation due to one or other reasons. When BSC receives the UPLINK RELEASE message from
the talker, it sends the UPLINK RELEASE INDICATION message to
MSC, and the counter increments. The measurement point is A1,
FIGURE 2879 TALKER GIVING UP CONVERSATION

Unit
Statistics Object
Times
Cell
attempts for Listener uplink
request
Description
This counter counts the number of the listener's attempts of becoming a talker through uplink request. When BSC sends the UPLINK REQUEST message to MSC, the counter increments. The
3039
FIGURE 2880 UPLINK PREEMPTION PROCESS

Unit
Statistics Object
Times
Cell
VGCS Intra-BSC Inter-cell
of Talker
Description
3040

handover attempts initiated from the source cell by the talker who
is having the VGCS service. When BSC receives the measurement
report from the talker's mobile phone, it performs handover decision. If the handover decision indicates that intra-cell handover
is required and the currently attempted cell is under the BSC, the
Figure 2881.
FIGURE 2881 INTRA-BSC INTER-CELL HANDOVER (SUCCESS)

Unit
Statistics Object
Times
Cell
outgoing handover execution
of Talker
Description
This counter counts the number of executions of intra-BSC inter-cell outgoing handover initiated from the source cell by the
talker who is having the VGCS service. Here, execution means
the destination cell succeeds in requesting radio resource and the
message of resource available is returned. During the handover,
when the destination cell succeeds in requesting channel, it returns the message of radio resource available to the source cell.
After the source cell receives the message, if the channel request
is due to intra-BSC inter-cell handover, the counter increments.
3041

Unit
Statistics Object
Times
Cell
of Talker
Description
3042

outgoing handovers initiated from the source cell by the talker who
is having the VGCS service. During the handover, if the source
cell receives the handover completion message returned from the
destination cell, then it indicates that MS is accessed to the destination channel and the handover succeeds. In such cases, the
Figure 2883.

Unit
Statistics Object
Times
Cell
outgoing handover failure of
Talker
Description
This counter counts the number of failures of intra-BSC inter-cell

outgoing handovers initiated from the source cell by the talker who
is having the VGCS service. During the handover, whenever the
handover fails due to any exception, the counter increments. The
FIGURE 2884 INTRA-BSC INTER-CELL HANDOVER (FAILURE)
3043

Unit
Statistics Object
Times
Cell
of Talker
Description

towards the destination cell when the talker, who is having the
VGCS service, is performing intra-BSC inter-cell handover. When
the destination cell under the BSC receives the channel request
from the source cell, if the request is due to inter-cell handover,
in Figure 2885.
FIGURE 2885 INTRA-BSC INTER-CELL INCOMING HANDOVER

Unit
3044
Times
Statistics Object
Cell
C902030023 Number
of VGCS Intra-BSC
Inter-cell incoming handover
execution of Talker
Description
This counter counts the number of executions of incoming handover towards the destination cell when the talker, who is having
the VGCS service, is performing intra-BSC inter-cell handover. If
the channel is successfully activated in the destination cell under
the BSC and the request is due to inter-cell handover, the counter
2886.

Unit
Times
3045
Statistics Object
Cell
of Talker
Description

VGCS service, is performing intra-BSC inter-cell handover. When
the destination cell under the BSC receives the handover completion message, if the handover is intra-BSC inter-cell handover, the
Figure 2887.

Unit
Statistics Object
Times
Cell
NCH overflow of VGCS
Description
3046
This counter counts the number of overflows of VGCS notification

message on NCH channel. When BSC receives the ERROR REPORT
message from BTS, if the cause is "NOTIFICATION OVERFLOW",

Unit
Statistics Object
Times
Cell
successes for Listener uplink
request
Description
This counter counts the number of the listener's successfully becoming a talker through uplink request. When MSC sends the UPLINK REQUEST ACK message to BSC, if BSC returns the UPLINK
REQUEST CONFIRM message, the counter increments. The measurement point is A1, as shown in Figure 2888.

Unit
Times
3047
Statistics Object
Cell
failures for Listener uplink
request
Description
This counter counts the number of failures in the listener's becoming a talker through uplink request. After BSC sends the UPLINK
REQUEST message to MSC, if it receives UPLINK REQUEST REJECT
message from MSC or the timer expires, the counter increments.

Unit
Statistics Object
3048
Times
Cell
Chapter
104
VBS Measurement
Table of Contents
Overview...................................................................... 3050
C902040001 Number of VBS assignment attempts............. 3050
C902040002 Number of VBS assignment success .............. 3051
C902040003 Number of VBS assignment failure ................ 3051
C902040004 Number of VBS Inter-BSC outgoing handover
failure of Talker ............................................................. 3055
C902040008 Number of VBS Inter-BSC incoming handover
C902040011 Number of VBS channel request attempts for
C902040012 Number of VBS channel request success for NOTIFICATION RESPONSE of Listener................................... 3059
C902040013 Number of VBS channel request failure for NOTIFICATION RESPONSE of Listener................................... 3060
C902040014 Number of VBS channel release for Listener detection ......................................................................... 3061
handover failure of Talker ............................................... 3065
C902040019 Number of VBS Intra-BSC Inter-cell incoming
C902040022 Number of NCH overflow of VBS ................... 3068
C902040023 Number of Talker drops due to radio link failure .............................................................................. 3069
3049
Overview
This measurement performs statistics for performance indices of
voice broadcast service, which involves VBS assignment, Talker
handover, Listener notification response, and NCH overflow.
VBS assignment attempts
Description
This counter counts the number of assignment attempts due to

VBS. When BSC receives the VBS ASSIGNMENT REQUEST message (indicating VBS call) of corresponding legal cell from MSC,
in Figure 2890.
FIGURE 2890 VBS RESOURCE ASSIGNMENT SUCCESS

Unit
3050
Times
Chapter 104 VBS Measurement
Statistics Object
Cell
VBS assignment success
Description
This counter counts the number of successful assignments due to

VBS. When BSC sends the VBS ASSIGNMENT RESULT message
(corresponding to VBS call) to MSC as response to the VBS ASSIGNMENT REQUEST message, the counter increments. The measurement point is A2, as shown in Figure 2891.
FIGURE 2891 VBS RESOURCE ASSIGNMENT SUCCESS

Unit
Statistics Object
Times
Cell
VBS assignment failure
Description
This counter counts the number of assignment failures due to VBS.

When BSC receives the VGCS/VBS ASSIGNMENT REQUEST message from MSC, if channel allocation for group call service fails
due to one or other reasons, BSC sends the VGCS/VBS ASSIGNMENT FAILURE message to MSC (corresponding to VBS call), and
in Figure 2892.
3051
FIGURE 2892 VBS RESOURCE ASSIGNMENT FAILURE

Unit
Statistics Object
Times
Cell
VBS Inter-BSC outgoing
Description
3052

attempts initiated from the source cell by the talker who is having
the VBS service. When BSC receives the measurement report from
the talker's mobile phone, if the handover decision indicates intercell handover is required but the currently attempted cell is not
under the BSC, then the original BSC will send the A_HO_RQD
message to MSC to trigger inter-BSC cell handover. In such cases,
in Figure 2893.

Unit
Statistics Object
Times
Cell
handover execution of
Talker
Description

executions initiated from the source cell by the talker who is having the VBS service. When BSC receives the measurement report
from the talker's mobile phone, if the handover decision indicates
inter-cell handover is required but the currently attempted cell is
not under the BSC, then the original BSC will send the A_HO_RQD
message to MSC to trigger inter-BSC cell handover. If the original BSC receives the handover command returned by MSC, the
Figure 2894.
3053

Unit
Statistics Object
Times
Cell
Description
3054
This counter counts the number of successful inter-BSC outgoing

handovers initiated from the source cell by the talker who is having the VBS service. When BSC receives the measurement report
cell handover. If the mobile phone is successfully accessed to the
destination cell, the source cell receives the release command issued from MSC. In such cases, the counter increments. The measurement point is A3, as shown in Figure 2895.

Unit
Statistics Object
Times
Cell
handover failure of Talker
Description
This counter counts the number of failures of inter-BSC outgoing

handover request initiated from the source cell by the talker who
is having the VBS service. When BSC receives the measurement
report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is
required but the currently attempted cell is not under the BSC,
then the original BSC will send the A_HO_RQD message to MSC
to trigger inter-BSC cell handover. If the original BSC receives the
handover rejection message returned from MSC or does not receive any response from MSC before the protection timer expires,
in Figure 2896.
3055
FIGURE 2896 INTER-BSC OUTGOING HANDOVER FAILURE
OF
TALKER

Unit
Statistics Object
Times
Cell
VBS Inter-BSC incoming
Description

towards the destination cell when the talker, who is having the VBS
service, is performing inter-BSC handover. When the destination
cell receives the HANDOVER REQUEST message from MSC, if the
request is due to incoming handover, the counter increments. The
FIGURE 2897 INTER-BSC INTER-CELL INCOMING HANDOVER
3056
Unit
Statistics Object
Times
Cell
handover execution of
Talker
Description
This counter counts the number of executions of incoming handover towards the local cell when the talker, who is having the
VBS service, is performing inter-BSC handover. When the destination cell receives the HANDOVER REQUEST message from MSC,
if the channel is allocated and activated successfully, the counter
2898.

Unit
Times
3057
Statistics Object
Cell
Description

towards the local cell when the talker, who is having the VBS service, is performing inter-BSC handover. When the destination cell
receives the handover completion message from Um interface, if
the handover is inter-BSC incoming handover, the counter increments. The measurement point is A3, as shown in Figure 2899.

Unit
Statistics Object
Times
Cell
C902040011 Number
of VBS channel request
attempts for NOTIFICATION
Description
3058
This counter counts the number of attempts of BSC's allocating

VBS channel during the listener's notification response flow. When
BSC receives the EST IND (NOTIFICATION RESPONSE) message,

in Figure 2900.

Unit
Statistics Object
Times
Cell
C902040012 Number
success for NOTIFICATION
Description
This counter counts the number of BSC's successfully allocating

VBS channel during the listener's notification response flow.
When BSC successfully allocates VGCS channel and returns the
VGCS/VBS ASSIGNMENT STATUS message to MSC, the counter
2901.
3059

Unit
Statistics Object
Times
Cell
C902040013 Number
failure for NOTIFICATION
Description
3060
This counter counts the number of failures in BSC's allocating VBS

channel during the listener's notification response flow. When BSC
fails in allocating VGCS channel, the counter increments. The measurement point is A1, as shown in Figure 2902.
FIGURE 2902 LISTENER'S NOTIFICATION RESPONSE PROCESS (FAILURE)

Unit
Statistics Object
Times
Cell
VBS channel release for
Listener detection
Description
This counter counts the number of VBS channel being released due
to that BSC cannot detect the listener. When BSC cannot detect
the listener on VBS channel, it releases the VBS channel and returns the VGCS ASSIGNMENT STATUS message to MSC, and the
Figure 2903.
3061
FIGURE 2903 NO LISTENER DETECTED
IN
CELL

Unit
Statistics Object
Times
Cell
VBS Intra-BSC Inter-cell
of Talker
Description
3062

handover attempts initiated from the source cell by the talker who
is having the VBS service. When BSC receives the measurement
report from the talker's mobile phone, it performs handover decision. If the handover decision indicates that intra-cell handover
is required and the currently attempted cell is under the BSC, the
Figure 2904.

Unit
Statistics Object
Times
Cell
C902040016 Number of VBS

Intra-BSC Inter-cell outgoing
Description
This counter counts the number of executions of intra-BSC inter-cell outgoing handover initiated from the source cell by the
talker who is having the VBS service. Here, execution means the
destination cell succeeds in requesting radio resource and the message of resource available is returned. During the handover, when
the destination cell succeeds in requesting channel, it returns the
message of radio resource available to the source cell. After the
source cell receives the message, if the channel request is due to
intra-BSC inter-cell handover, the counter increments. The measurement point is A2, as shown in Figure 2905.
3063

Unit
Statistics Object
Times
Cell
of Talker
Description
3064

outgoing handovers initiated from the source cell by the talker
who is having the VBS service. During the handover, if the source
cell receives the handover completion message returned from the
destination cell, then it indicates that MS is accessed to the destination channel and the handover succeeds. In such cases, the
Figure 2906.

Unit
Statistics Object
Times
Cell
outgoing handover failure of
Talker
Description
This counter counts the number of failures of intra-BSC inter-cell

outgoing handovers initiated from the source cell by the talker
who is having the VBS service. During the handover, whenever
the handover fails due to any exception, the counter increments.
FIGURE 2907 INTRA-BSC INTER-CELL HANDOVER (FAILURE)
3065

Unit
Statistics Object
Times
Cell
of Talker
Description

VBS service, is performing intra-BSC inter-cell handover. When
the destination cell under the BSC receives the channel request
from the source cell, if the request is due to inter-cell handover,
in Figure 2908.

Unit
3066
Times
Statistics Object
Cell
C902040020 Number of VBS

Intra-BSC Inter-cell incoming
Description
This counter counts the number of executions of incoming handover towards the destination cell when the talker, who is having
the VBS service, is performing intra-BSC inter-cell handover. If
the channel is successfully activated in the destination cell under
2909.

Unit
Times
3067
Statistics Object
Cell
of Talker
Description

VBS service, is performing intra-BSC inter-cell handover. When
the destination cell under the BSC receives the handover completion message, if the handover is intra-BSC inter-cell handover, the
counter increments. The measurment point is A3, as shown in
Figure 2910.

Unit
Statistics Object
Times
Cell
NCH overflow of VBS
Description
3068
This counter counts the number of overflows of VBS notification

message on NCH channel. When BSC receives the ERROR REPORT
message from BTS, if the cause is "NOTIFICATION OVERFLOW",

Unit
Statistics Object
Times
Cell
Talker drops due to radio
link failure
Description
This counter counts the number of BSC's releasing the resource

occupied by the talker due to radio link fault at the talker end.
When BSC detects on VBS channel that the radio link is disconnected at the talker end, it releases the talker's resource, and the
Figure 2911.
FIGURE 2911 RELEASING TALKER'S RESOURCE
DUE TO
RADIO LINK FAILURE

Unit
Statistics Object
Times
Cell
3069
3070
Chapter
105
eMLPP Measurement
Table of Contents
Overview...................................................................... 3072
C902050001 Number of Talker is preempted ..................... 3072
C902050002 Number of Listener is preempted .................. 3072
C902050003 Number of preempt attempts due to VGCS
setup ........................................................................... 3073
C902050004 Number of preempt attempts due to VBS
setup ........................................................................... 3074
C902050005 Number of preempt execution due to VGCS
setup ........................................................................... 3075
C902050006 Number of preempt execution due to VBS
setup ........................................................................... 3076
C902050007 Number of preempt attempts due to NOTIFICATION RESPONSE of Listener ............................................ 3077
C902050008 Number of preempt execution due to NOTIFICATION RESPONSE of Listener ............................................ 3078
C902050009 Number of preempt attempts due to Inter-BSC
handover of Talker ......................................................... 3079
C902050010 Number of preempt execution due to Inter-BSC
handover of Talker ......................................................... 3080
C902050011 Number of preempt attempts due to Intra-BSC
Inter-cell handover of Talker ........................................... 3081
C902050012 Number of preempt execution due to Intra-BSC
C902050013 Number of queuing attempts due to VGCS
setup ........................................................................... 3083
C902050014 Number of queuing execution due to VGCS
setup ........................................................................... 3084
C902050015 Number of queuing attempts due to VBS
setup ........................................................................... 3085
C902050016 Number of queuing execution due to VBS
setup ........................................................................... 3086
C902050017 Number of queuing attempts due to NOTIFICATION RESPONSE of Listener ............................................ 3087
C902050018 Number of queuing execution due to NOTIFICATION RESPONSE of Listener ............................................ 3088
C902050019 Number of queuing attempts due to inter-BSC
incoming handover of Talker ........................................... 3089
C902050020 Number of queuing execution due to inter-BSC
incoming handover of Talker ........................................... 3090
C902050021 Number of queuing attempts due to Intra-BSC
C902050022 Number of queuing execution due to Intra-BSC
3071
Overview
This measurement performs statistics for conditions of high-priority group call service preempting resource from low-priority service. It involves the following performance data: the number of
forced release of listener/talker; the number of forced release due
to group call setup, listener's notification response, or talker handover; the number of queuing due to group call setup, listener's
notification response, or talker handover.
Talker is preempted
Description
This counter counts the number of TCH, which is occupied by the

talker, being forcedly released. The channel occupied by the talker
will be forcedly released by other high-priority call (no available
radio resource in the cell). When the channel instance where the
talker is located receives the forced release message from other
high-priority call, the counter increments.
Unit
Statistics Object
Times
Cell
Listener is preempted
Description
This counter counts the number of TCH, which is monitored by the

listener, being forcedly released. The group call/broadcast channel monitored by the listener will be forcedly released by other
high-priority call (no available radio resource in the cell). When
the group call channel instance where the listener is located receives the forced release message from other high-priority call,
Unit
3072
Times
Chapter 105 eMLPP Measurement
Statistics Object
Cell
preempt attempts due to
VGCS setup
Description
This counter counts the number of attempts of forced release due

to no available radio resource when BSC establishes the VGCS
channel for a cell. When BSC receives the assignment request
for establishing VGCS channel for a cell, if there is no available radio resource for the cell, it judges whether the forced release can
be attempted. If the forced release can be attempted, the counter
increments before the forced release message is sent to the forced
release instance. The measurement point is A1, as shown in Figure
2912.
FIGURE 2912 VGCS/VBS ESTABLISHMENT PROCESS

Unit
Times
3073
Statistics Object
Cell
VBS setup
Description

to no available radio resource when BSC establishes the VBS channel for a cell. When BSC receives the assignment request for
establishing VBS channel for a cell, if there is no available radio
resource for the cell, it judges whether the forced release can be
attempted. If the forced release can be attempted, the counter increments before the forced release message is sent to the forced
2913.

Unit
3074
Times
Statistics Object
Cell
preempt execution due to
VGCS setup
Description
This counter counts the number of executions of forced release

due to no available radio resource when BSC establishes the VGCS
channel for a cell. When BSC establishes the VGCS channel for a
cell, if there is no available radio channel for the cell, the forced
release is attempted. When the message that resource is available
returned from the forced release instance is received, the counter
2914.

Unit
Times
3075
Statistics Object
Cell
preempt execution due to
VBS setup
Description

due to no available radio resource when BSC establishes the VBS
channel for a cell. When BSC establishes the VBS channel for a
cell, if there is no available radio channel for the cell, the forced
release is attempted. When the message that resource is available
returned from the forced release instance is received, the counter
2915.

Unit
3076
Times
Statistics Object
Cell
C902050007 Number
of preempt attempts
due to NOTIFICATION
Description

to no available radio resource during the listener's notification response process. When BSC receives the listener's notification response to establish the VGCS/VBS channel for a cell, if there is no
available radio resource, it judges whether the forced release can
be attempted. If the forced release can be attempted, the counter
increments before the forced release message is sent to the forced
2916.
FIGURE 2916 LISTENER'S NOTIFICATION RESPONSE PROCESS

Unit
Times
3077
Statistics Object
Cell
C902050008 Number
of preempt execution
due to NOTIFICATION
Description

due to no available radio resource during the listener's notification
response process. When BSC receives the listener's notification
response to establish the VGCS/VBS channel for a cell, it will attempt forced release if there is no available radio resource. When
the message that resource is available returned from the forced
release instance is received, the counter increments. The measurement point is A2, as shown in Figure 2917.

Unit
3078
Times
Statistics Object
Cell
Inter-BSC handover of
Talker
Description

to the destination cell having no available radio resource when the
talker performs incoming handover towards a cell controlled by
another BSC. When the destination instance fails in channel allcoation, the forced release can be attempted according to MS's
priority and the configuration at MSC and BSC. When the destination cell under another BSC receives the radio channel request
message, if the request is due to inter-BSC incoming handover of
the talker and if the destination cell does not have available radio
channel, it is judged whether the forced release can be attempted.
If the forced release can be attempted, the counter increments before the destination cell sends the forced release message to the
forced release instance. The measurement point is A1, as shown
in Figure 2918.
FIGURE 2918 INTER-BSC HANDOVER
OF
TALKER
3079
Unit
Statistics Object
Times
Cell
preempt execution due
to Inter-BSC handover of
Talker
Description
This counter counts the number of executions of forced release due

another BSC. When the destination cell under another BSC receives the radio channel request message, if the request is due to
inter-BSC incoming handover of the talker and if the destination
cell does not have available radio channel, the forced release is
attempted. When the destination cell receives the message that
resource is available returned from the forced release instance,
in Figure 2919.
FIGURE 2919 INTER-BSC HANDOVER
OF
TALKER
3080
Unit
Statistics Object
Times
Cell
preempt attempts due
to Intra-BSC Inter-cell
handover of Talker
Description

talker performs intra-BSC inter-cell handover. When the destination instance fails in channel allocation, the forced release can be
attempted according to MS's priority and the configuration at MSC
and BSC. When the destination cell under the BSC receives the
radio channel request message, if the request is due to BSC-controlled inter-cell handover of the talker and if the destination cell
does not have available radio channel, it is judged whether the
forced release can be attempted. If the forced release can be attempted, the counter increments before the destination cell sends
the forced release message to the forced release instance. The
FIGURE 2920 INTRA-BSC INTER-CELL HANDOVER
OF
TALKER
3081
Unit
Statistics Object
Times
Cell
preempt execution due
handover of Talker
Description
This counter counts the number of executions of forced release due

talker performs intra-BSC inter-cell handover. When the destination cell under the BSC receives the radio channel request message, if the request is due to BSC-controlled inter-cell handover of
the talker and if the destination cell does not have available radio
channel, the forced release is attempted. When the destination
cell receives the message that resource is available returned from
the forced release instance, the counter increments. The measurement point is A2, as shown in Figure 2921.
FIGURE 2921 INTRA-BSC INTER-CELL HANDOVER
OF
TALKER

Unit
3082
Times
Statistics Object
Cell
queuing attempts due to
VGCS setup
Description
This counter counts the number of attempts of queuing due to a

cell having no available radio resource when BSC establishes the
VGCS channel for the cell. When BSC receives the VGCS assignment request to establish the VGCS channel for a cell, if there
is no available resource, it judges whether queuing can be performed. If queuing can be performed, the cell instance is added to
the queue waiting for resource, and the counter increments. The
FIGURE 2922 VGCS CELL ESTABLISHMENT PROCESS

Unit
Times
3083
Statistics Object
Cell
queuing execution due to
VGCS setup
Description
This counter counts the number of executions of queuing due to a

VGCS channel for the cell. When BSC receives the VGCS assignment request to establish the VGCS channel for a cell, if there is no
available resource, the cell instance is added to the queue waiting
for resource. When the cell instance receives the message that
resource is available, the counter increments. The measurement
FIGURE 2923 VGCS CELL ESTABLISHMENT PROCESS

Unit
3084
Times
Statistics Object
Cell
queuing attempts due to
VBS setup
Description
This counter counts the number of attempts of queuing due to a

VBS channel for the cell. When BSC receives the VBS assignment
request to establish the VBS channel for a cell, if there is no available resource, it judges whether queuing can be performed. If
queuing can be performed, the cell instance is added to the queue
waiting for resource, and the counter increments. The measurement point is A1, as shown in Figure 2924.
FIGURE 2924 VBS CELL ESTABLISHMENT PROCESS

Unit
Times
3085
Statistics Object
Cell
queuing execution due to
VBS setup
Description
This counter counts the number of executions of queuing due to

a cell having no available radio resource when BSC establishes
the VBS channel for the cell. When BSC receives the VBS assignment request to establish the VBS channel for a cell, if there is no
available resource, the cell instance is added to the queue waiting
for resource. When the cell instance receives the message that
resource is available, the counter increments. The measurement
FIGURE 2925 VBS CELL ESTABLISHMENT PROCESS

Unit
3086
Times
Statistics Object
Cell
C902050017 Number
of queuing attempts
due to NOTIFICATION
Description
This counter counts the number of attempts of queuing due to

no available radio resource when BSC establishes the VGCS/VBS
channel for the listener during the listener's notification response
flow. When BSC receives the listener's notification response message, if there is no available channel and if the listener is allowed
to wait for radio channel resource in the queue, the counter increments. The measurement point is A1, as shown in Figure 2926.

Unit
Times
3087
Statistics Object
Cell
C902050018 Number
of queuing execution
due to NOTIFICATION
Description

no available radio resource when BSC establishes the VGCS/VBS
channel for the listener during the listener's notification response
flow. When BSC receives the listener's notification response message, if there is no available channel and if the listener is allowed
to wait for radio channel resource in the queue, then the counter
increments if the listener gets the radio channel resource. The

Unit
3088
Times
Statistics Object
Cell
queuing attempts due
to inter-BSC incoming
handover of Talker
Description
This counter counts the number of attempts of queuing due to the

destination cell having no available radio resource when the talker
performs incoming handover towards a cell controlled by another
BSC. When BSC receives the handover request from MSC, which
is inter-BSC incoming handover of the talker, if there is no available channel and if VGCS/VBS is allowed to wait for radio channel
resource in the queue, the counter increments. The measurement
FIGURE 2928 INTER-BSC INCOMING HANDOVER
OF
TALKER

Unit
Times
3089
Statistics Object
Cell
queuing execution due
to inter-BSC incoming
handover of Talker
Description
This counter counts the number of executions of queuing due to the

destination cell having no available radio resource when the talker
performs incoming handover towards a cell controlled by another
BSC. When BSC receives the handover request from MSC, which is
inter-BSC incoming handover of the talker, if there is no available
channel and if VGCS/VBS is allowed to wait for radio channel resource in the queue, then the counter increments when the radio
channel resource is obtained through waiting. The measurement
OF
TALKER

Unit
3090
Times
Statistics Object
Cell
queuing attempts due
handover of Talker
Description
This counter counts the number of attempts of queuing due to

the destination cell having no available radio resource when the
the same BSC. If the following three conditions are satisfied, the
counter increments:
The request is due to BSC-controlled inter-cell incoming handover of the talker;
The destination cell does not have available radio channel;
VGCS/VBS is allowed to wait for radio channel resource in the

queue.

OF
TALKER

Unit
Times
3091
Statistics Object
Cell
queuing execution due
handover of Talker
Description

the destination cell having no available radio resource when the
talker performs incoming handover towards a cell controlled by the
same BSC. If the following three conditions are satisfied and the
radio channel resource is obtained through waiting, the counter
increments:
The request is due to BSC-controlled inter-cell incoming handover of the talker;
The destination cell does not have available radio channel;
VGCS/VBS is allowed to wait for radio channel resource in the

queue.

OF
TALKER

Unit
Statistics Object
3092
Times
Cell
Chapter
106
Flow Control
Measurement
Table of Contents
Overview...................................................................... 3093
C902110001 The number of Channel Requests overflowing .............................................................................. 3093
C902110002 The number of Paging Messages overflowing .............................................................................. 3094
Overview
Flow control measurement counters are used to measure BHCA or
paging message overload at the processor. Statistic unit in this
measurement is CMP.
C902110001 The number

of Channel Requests
overflowing
Description
After BSC receives the channel request message from BTS, it performs statistics of the number of channel requests within the unit
time. If the number exceeds the set threshold value, flow control
must be performed to discard subsequent channel request messages received in the meaurement period. After a unit time expires, check whether the number of channel requests received in
the measurement period exceeds the threshold value. If the number is larger than the threshold value, the counter increments. The
measurement point is shown in Figure 2932.
3093
OF
NUMBER
OF
CHANNEL REQUESTS

Unit
Statistics Object
Times
CMP
C902110002 The number

of Paging Messages
overflowing
Description
After BSC receives the paging message issued by MSC, it performs statistics of the number of paging messages that do not
contain eMLPP priority information received within the unit time.
If the number exceeds the set threshold value, flow control must
be performed to discard subsequent paging messages not containing eMLPP priority information received in the measurement
period. After a unit time expires, check whether the number of
common paging messages received in the measurement period
exceeds the threshold value. If the number is larger than the
threshold value, the counter increments. The measurement point
is shown in Figure 2933.
OF
NUMBER
OF
PAGING MESSAGES

Unit
Statistics Object
3094
Times
CMP
Chapter
107
SDCCH General
Table of Contents
Overview...................................................................... 3096
handover attempts (On SDCCH) ...................................... 3097
handover (On SDCCH) ................................................... 3098
handover success (On SDCCH) ........................................ 3099
attempts (On SDCCH) .................................................... 3100
request failures due to unclear factors (On SDCCH)............ 3101
request failures due to unavailable radio resource (On SDCCH) ........................................................................... 3102
request failures due to other factors (On SDCCH) .............. 3103
(On SDCCH) ................................................................. 3104
success (On SDCCH)...................................................... 3105
handover attempts (On SDCCH) ...................................... 3106
handover (On SDCCH) ................................................... 3107
attempts due to forced release (On SDCCH)...................... 3108
due to forced release (On SDCCH) ................................... 3109
attempts due to queue (On SDCCH)................................. 3110
due to queue (On SDCCH) .............................................. 3111
attempts due to forced handover (On SDCCH)................... 3112
due to forced handover (On SDCCH) ................................ 3113
handover success (On SDCCH) ........................................ 3114
C902120019 BSC-controlled incoming handover time due to
queue (On SDCCH) ........................................................ 3115
queue (On SDCCH) ........................................................ 3116
3095
C902120021 BSC-controlled incoming handover success time

success due to queue (On SDCCH)................................... 3119
attempts (On SDCCH) .................................................... 3120
C902120024 Number of incoming handover failure due to unavailable radio resource (On SDCCH) ............................... 3120
other factors (On SDCCH)............................................... 3121
(On SDCCH) ................................................................. 3122
attempts due to forced release (On SDCCH)...................... 3123
due to forced release (On SDCCH) ................................... 3124
attempts due to queue (On SDCCH)................................. 3125
attempts due to forced handover (On SDCCH)................... 3127
due to forced handover (On SDCCH) ................................ 3128
success (On SDCCH)...................................................... 3129
C902120034 MSC-controlled incoming handover time due to
queue (On SDCCH) ........................................................ 3129
queue (On SDCCH) ........................................................ 3131
C902120036 MSC-controlled incoming handover success time
success due to queue (On SDCCH)................................... 3134
Overview
SDCCH general handover measurement counters are used to count
the number of handover successes and handover failures on SDCCH and study the frequency of various abnormalities occurred
during the handover process. Statistic unit in this measurement
is cell.
3096
Chapter 107 SDCCH General Handover Measurement
(On SDCCH)
Description
This counter counts the number of attempts of intra-BSC inter-cell

outgoing handover initiated by MS on SDCCH in the source cell.
This counter is used to find out the frequency of intra-BSC intercell outgoing handover attempt initiated by MS. It is one of the
parameters that evaluate the radio environment.
When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision
indicates that inter-cell handover is required and the currently attempted cell is under the BSC, the counter increments. The measurement point is A, as shown in Figure 2934.
ATTEMPT (ON SDCCH)

Unit
Times
3097
Statistics Object
Cell
outgoing handover (On
SDCCH)
Description
This counter counts the number of executions of intra-BSC intercell outgoing handover initiated by MS on SDCCH in the source cell.
Here, execution means the destination cell succeeds in requesting
radio resource and the message of resource available is returned.
This counter is used to find out the frequency of execution of intra-BSC inter-cell outgoing handover initiated by MS. It is one of
the parameters that evaluate the radio environment, reflecting the
handover flow.
During the handover, when the destination cell succeeds in requesting channel, it returns the message of radio resource available to the source cell. After the source cell receives the message,
if the channel request is due to intra-BSC inter-cell handover, the
Figure 2935.
EXECUTION

Unit
3098
Times
Statistics Object
Cell
(On SDCCH)
Description

outgoing handover initiated by MS on SDCCH in the source cell.
This counter is used to find out the frequency of successful intraBSC inter-cell outgoing handover initiated by MS. It is one of the
parameters that evaluate the handover condition.
During the handover, if the source cell receives the handover completion message returned from the destination cell, then it indicates that MS is accessed to the destination channel and the handover succeeds. In such cases, the counter increments. The measurement point is A, as shown in Figure 2936.
SUCCESS

Unit
Times
3099
Statistics Object
Cell
handover attempts (On
SDCCH)
Description
This counter counts the number of attempts of MSC-controlled inter-BSC outgoing handover initiated by MS on SDCCH in the source
cell.
inter-BSC outgoing handover attempt initiated by MS. It is one of
the parameters that evaluate the radio environment.
When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is under a different BSC, then the source BSC will send
the A_HO_RQD message to MSC to trigger inter-BSC inter-cell
handover. In this case, the counter increments. The measurement point is A, as shown in Figure 2937.
FIGURE 2937 MSC-CONTROLLED OUTGOING HANDOVER ATTEMPT

Unit
3100
Times
Statistics Object
Cell
due to unclear factors (On
SDCCH)
Description
This counter counts the number of failures of MSC-controlled interBSC outgoing handover request initiated by MS on SDCCH in the
source cell, and the failure is due to unclear causes.
This counter is used to find out the frequency of failure of MSC-controlled outgoing handover request initiated by MS due to unclear
causes. It also helps study the condition of handover initiated by
MSC.
handover. If BSC does not receive any response message from
MSC before the protection timer expires, the counter increments.
FIGURE 2938 MSC-CONTROLLED OUTGOING HANDOVER FAILURE
UNCLEAR CAUSE
DUE TO

Unit
Times
3101
Statistics Object
Cell
resource (On SDCCH)
Description
source cell, and the failure is due to no available radio resource.
This counter is used to find out the frequency of failure of MSC-controlled outgoing handover request initiated by MS due to no available radio resource. It also helps study the condition of handover
initiated by MSC.
handover. If the source BSC receives the handover reject message from MSC and the cause is no available radio resource, the
Figure 2939.
FIGURE 2939 MSC-CONTROLLED HANDOVER REQUEST BEING REJECTED

Unit
3102
Times
Statistics Object
Cell
due to other factors (On
SDCCH)
Description
source cell, and the failure is due to causes except for no available
terrestrial resource and no available radio resource.
This counter is used to find out the frequency of failure of MSCcontrolled outgoing handover request initiated by MS due to other
causes. It also helps study the condition of handover initiated by
MSC.
handover. If the source BSC receives the handover reject message from MSC due to other causes, the counter increments. The
FIGURE 2940 MSC-CONTROLLED HANDOVER REQUEST BEING REJECTED

Unit
Times
3103
Statistics Object
Cell
handover (On SDCCH)
Description
This counter counts the number of MSC-controlled inter-BSC outgoing handovers initiated by MS on SDCCH in the source cell.
inter-BSC outgoing handover initiated by MS. It also helps study
the condition of handover initiated by MSC.
handover. If the source BSC receives the handover command returned by MSC, the counter increments. The measurement point
FIGURE 2941 NUMBER
EXECUTIONS
OF

Unit
3104
Times
Statistics Object
Cell
handover success (On
SDCCH)
Description
This counter counts the number of successful MSC-controlled inter-BSC outgoing handover initiated by MS on SDCCH in the source
cell.
This counter is used to find out the frequency of successful MSCcontrolled inter-BSC outgoing handover initiated by MS. It also
helps study the condition of handover initiated by MSC.
When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is under a different BSC, then the source BSC will
send the A_HO_RQD message to MSC to trigger inter-BSC inter-cell handover. If the mobile phone is successfully accessed
to the destination cell, the source cell receives the release command issued from MSC. In such cases, the counter increments.
FIGURE 2942 NUMBER
SUCCESSES
OF

Unit
Times
3105
Statistics Object
Cell
(On SDCCH)
Description
This counter counts the number of attempts of BSC-controlled inter-cell incoming handover initiated by MS towards the destination
cell.
inter-cell incoming handover attempt initiated by MS. It is one of
the parameters that evaluate the radio environment.
When the destination cell under the BSC receives the channel request from the source cell, if the request is due to inter-cell handover, the counter increments. The measurement point is A, as
ATTEMPT

Unit
3106
Times
Statistics Object
Cell
incoming handover (On
SDCCH)
Description
This counter counts the number of BSC-controlled inter-cell incoming handover executions initiated by MS towards SDCCH of
the destination cell.
inter-cell incoming handover initiated by MS. It is one of the parameters that evaluate the radio environment, reflecting the handover flow.
If the channel is successfully activated in the destination cell under
EXECUTION

Unit
Times
3107
Statistics Object
Cell
forced release (On SDCCH)
Description
During the process of BSC-controlled inter-cell incoming handover

towards SDCCH initiated by MS, this counter counts the number
of attempts of forced release due to no available radio resource in
the destination cell. When the destination instance fails in channel
allocation, the forced release can be attempted according to MS's
priority and the configuration at MSC and BSC.
attempt during the process of BSC-controlled inter-cell incoming
handover initiated by MS. It reflects the handover flow.
When the destination cell under the BSC receives the radio channel
request message, if the request is due to BSC-controlled inter-cell
handover and if the destination cell does not have available radio
channel, it is judged whether the forced release can be attempted.
If the forced release can be attempted, the counter increments
before the destination cell sends the forced release message to the
forced release instance. The measurement point is A, as shown in
Figure 2945.
FIGURE 2945 FORCED RELEASE ATTEMPT

Unit
3108
Times
Statistics Object
Cell
release (On SDCCH)
Description

of forced releases due to no available radio resource in the destination cell.
during the process of BSC-controlled inter-cell incoming handover
initiated by MS. It reflects the handover flow.
the forced release instance, the counter increments. The measurement point is A2, as shown in Figure 2946.

Unit
Times
3109
Statistics Object
Cell
queue (On SDCCH)
Description

of attempts of queuing due to no available radio resource in the
destination cell.
This counter is used to find out the frequency of queuing attempt
incoming handover and if the destination cell does not have available radio channel, it is judged whether queuing can be attempted.
If queuing can be performed, the destination cell instance is added
to the queue waiting for resource, and the counter increments. The
FIGURE 2947 QUEUING ATTEMPT

Unit
3110
Times
Statistics Object
Cell
handover due to queue (On
SDCCH)
Description

towards SDCCH initiated by MS, this counter counts the number of
queuings due to no available radio resource in the destination cell.
This counter is used to find out the frequency of queuing during the
MS. It reflects the handover flow.
request message, if the request is due to BSC-controlled intercell incoming handover and if the destination cell does not have
available radio channel, the destination instance is added into the
queue. When the destination cell receives the message of resource
available, the counter increments. The measurement point is A2,
3111

Unit
Statistics Object
Times
Cell
handover attempts due
to forced handover (On
SDCCH)
Description

of attempts of forced handover due to no available radio resource
in the destination cell.
attempt during the process of BSC-controlled inter-cell incoming
incoming handover and if the destination cell does not have available radio channel, it is judged whether forced handover can be
attempted. If the forced handover can be attempted, the counter
increments before the destination cell sends the forced handover
message to the forced handover instance. The measurement point
FIGURE 2949 FORCED HANDOVER ATTEMPT

Unit
3112
Times
Statistics Object
Cell
handover (On SDCCH)
Description

of forced handovers due to no available radio resource in the destination cell.
incoming handover and if the destination cell does not have available radio channel, the forced handover message is sent to the
forced handover instance and the destination cell is added into the
queue. When the destination cell receives the message of resource
available, the counter increments. The measurement point is A2,
3113
Unit
Statistics Object
Times
Cell
(On SDCCH)
Description
This counter counts the number of successful BSC-controlled intercell incoming handovers towards SDCCH initiated by MS.
This counter is used to find out the frequency of successful BSCcontrolled inter-cell incoming handover initiated by MS. It reflects
the handover flow.
When the destination cell under the BSC receives the handover
completion message, if the handover is BSC-controlled inter-cell
handover, the counter increments. The measurement point is A,
SUCCESS

Unit
3114
Times
Statistics Object
Cell
incoming handover time due
to queue (On SDCCH)
Description
This counter counts the total queuing time of waiting for resource
for BSC-controlled incoming handover towards SDCCH in the cell.
The queuing time means the duration from an instance entering
the queue to the instance exiting the queue.
This counter is used to find out the total queuing time of waiting for
resource for BSC-controlled incoming handover in the cell. It helps
study the cell's traffic and the condition of queuing for resource.
When the database obtains resource through dynamic channel conversion or when the MS releases resource, the queuing
instance receives the message of resource available. If the
resource request is due to BSC-controlled incoming handover,
the counter accumulates the queuing time. The measurement
If the instance's queuing timer expires and if the resource request is due to BSC-controlled incoming handover, the counter
accumulates the queuing time. The measurement point is A,
3115
During the instance's queuing process, when the instance is

released due to some causes, if the resource request is due to
BSC-controlled incoming handover, the counter accumulates
the queuing time. The measurement point is A, as shown in
Figure 2954.
FIGURE 2954 RELEASING INSTANCE
DURING
QUEUING

Unit
Statistics Object
Second
Cell
handover queue (On
SDCCH)
Description
This counter counts the number of queuings due to BSC-controlled

incoming handover towards SDCCH in the cell.
This counter is used to find out the total number of queuings due
to BSC-controlled incoming handover in the cell. It helps study
the cell's traffic.
3116
instance receives the message of resource available. If the resource request is due to BSC-controlled incoming handover, the
Figure 2955.
If the instance's queuing timer expires and if the resource request is due to BSC-controlled incoming handover, the counter
2956.

released due to some causes, if the resource request is due
to BSC-controlled incoming handover, the counter increments.
DURING
QUEUING
3117

Unit
Statistics Object
Times
Cell
time due to queue (On
SDCCH)
Description
This counter counts the total time of successfully obtaining SDCCH

resource through queuing due to BSC-controlled incoming handover in the cell.
This counter is used to find out the total time of successfully obtaining resource through queuing due to BSC-controlled incoming
handover in the cell. It helps study the effective queuing time.
When the database obtains resource through dynamic channel
conversion or when the MS releases resource, the queuing instance receives the message of resource available. If the resource
request is due to BSC-controlled incoming handover, the counter
accumulates the queuing time. The measurement point is A, as

Unit
3118
Second
Statistics Object
Cell
queue (On SDCCH)
Description
This counter counts the total number of SDCCHs successfully obtained through queuing due to BSC-controlled incoming handover
in the cell.
This counter is used to find out the total number of calls that successfully obtain resource through queuing due to BSC-controlled
incoming handover in the cell. It helps study the queuing success
rate.
request is due to BSC-controlled incoming handover, the counter
2959.

Unit
Times
3119
Statistics Object
Cell
handover attempts (On
SDCCH)
Description
This counter counts the number of attempts of inter-BSC incoming

handover initiated by MSC towards SDCCH in the local cell.
This counter is used to find out the frequency of inter-BSC incoming handover attempt initiated by MSC. It is one of the parameters
that evaluate the radio environment.
When the destination cell receives the channel request due to external incoming handover, the counter increments. The measurement point is A, as shown in Figure 2960.
FIGURE 2960 MSC-CONTROLLED INCOMING HANDOVER ATTEMPT

Unit
Statistics Object
Times
Cell
resource (On SDCCH)
Description
3120
During the process of inter-BSC incoming handover initiated by

MSC towards SDCCH in the local cell, this counter counts the num-
ber of incoming handover failures due to no available radio resource.

failure due to no available radio resource during the process of
inter-BSC incoming handover initiated by MSC. It helps study the
external handover flow.
After the destination cell receives the handover request message
issued by MSC, it allocates radio channel and attempts to activate
and connect the channel. If the process fails, the destination cell
sends the handover failure message to MSC, and the counter increments. The measurement point is A, as shown in Figure 2961.
FIGURE 2961 MSC-CONTROLLED INCOMING HANDOVER FAILURE

Unit
Statistics Object
Times
Cell
due to other factors (On
SDCCH)
Description
During the process of inter-BSC incoming handover initiated by

MSC towards SDCCH in the local cell, this counter counts the number of incoming handover failures due to causes except for blocked
circuit, unmatched circuit groups, and no available radio resource.
This counter is used to find out the frequency of incoming handover failure due to other causes during the process of inter-BSC
incoming handover initiated by MSC. It helps study the external
handover flow.
After the destination cell receives the handover request message
issued by MSC, if the incoming handover fails due to other causes,
the destination cell sends the handover failure message to MSC,
3121
and the counter increments.

The measurement point is A, as
FIGURE 2962 MSC-CONTROLLED INCOMING HANDOVER FAILURE

Unit
Statistics Object
Times
Cell
handover (On SDCCH)
Description
This counter counts the number of inter-BSC incoming handover

initiated by MSC towards SDCCH in the local cell.
This counter is used to find out the number of inter-BSC incoming
handovers initiated by MSC. It is one of the parameters that evaluate the radio environment, helping study the incoming handover
flow.
When the destination cell receives the handover request message
issued by MSC, if the channel is allocated and activated successfully, the counter increments. The measurement point is A, as
3122

Unit
Statistics Object
Times
Cell
forced release (On SDCCH)
Description
During the process of MSC-controlled inter-BSC incoming handover towards SDCCH initiated by MS, this counter counts the
number of attempts of forced release due to no available radio
resource in the destination cell. When the destination instance
fails in channel allocation, the forced release can be attempted according to MS's priority and the configuration at MSC and BSC.
attempt during the process of MSC-controlled inter-BSC incoming
When the destination cell receives the radio channel request message, if the request is due to MSC-controlled inter-BSC handover
and if the destination cell does not have available radio channel,
it is judged whether the forced release can be attempted. If the
forced release can be attempted, the counter increments before
the destination cell sends the forced release message to the forced
release instance. The measurement point is A, as shown in Figure
2964.
FIGURE 2964 FORCED RELEASE ATTEMPT

Unit
Times
3123
Statistics Object
Cell
release (On SDCCH)
Description
number of forced releases due to no available radio resource in
the destination cell.
during the process of MSC-controlled inter-BSC incoming handover
When the destination cell receives the radio channel request message, if the request is due to MSC-controlled inter-BSC incoming
the forced release instance, the counter increments. The measurement point is A, as shown in Figure 2965.

Unit
3124
Times
Statistics Object
Cell
queue (On SDCCH)
Description
number of attempts of queuing due to no available radio resource
This counter is used to find out the frequency of queuing attempt
it is judged whether queuing can be attempted. If queuing can be
performed, the detination cell instance is added to the queue waiting for resource, and the counter increments. The measurement
FIGURE 2966 QUEUING ATTEMPT

Unit
Times
3125
Statistics Object
Cell
handover due to queue (On
SDCCH)
Description
number of queuings due to no available radio resource in the destination cell.
This counter is used to find out the frequency of queuing during the
process of MSC-controlled inter-BSC incoming handover initiated
by MS. It reflects the handover flow.
channel, the destination instance is added into the queue. When
the destination cell receives the message of resource available,
Figure 2967.

Unit
3126
Times
Statistics Object
Cell
handover attempts due
to forced handover (On
SDCCH)
Description
number of attempts of forced handover due to no available radio resource in the destination cell.
attempt during the process of MSC-controlled inter-BSC incoming
it is judged whether forced handover can be attempted. If the
forced handover can be attempted, the counter increments before the destination cell sends the forced handover message to
the forced handover instance. The measurement point is A, as
FIGURE 2968 FORCED HANDOVER ATTEMPT

Unit
Times
3127
Statistics Object
Cell
handover (On SDCCH)
Description
number of forced handovers due to no available radio resource
channel, the forced handover message is sent to the forced handover instance and the destination cell is added into the queue.
When the destination cell receives the message of resource available, the counter increments. The measurement point is A, as
FIGURE 2969 MSC-CONTROLLED FORCED HANDOVER EXECUTION

Unit
3128
Times
Statistics Object
Cell
handover success (On
SDCCH)
Description
This counter counts the number of successful MSC-controlled inter-BSC incoming handovers towards SDCCH initiated by MS.
This counter is used to find out the frequency of successful MSCcontrolled inter-cell incoming handover initiated by MS. It reflects
the handover flow.
When the destination cell receives the handover completion message, if the handover is MSC-controlled inter-BSC incoming handover, the counter increments. The measurement point is A, as

Unit
Statistics Object
Times
Cell
C902120034 MSC-control
led incoming handover time
due to queue (On SDCCH)
Description
This counter counts the total queuing time of waiting for resource
for MSC-controlled incoming handover towards SDCCH in the cell.
3129
This counter is used to find out the total queuing time of waiting for
resource for MSC-controlled incoming handover in the cell. It helps
study the cell's traffic and the condition of queuing for resource.
instance receives the message of resource available. If the resource request is due to MSC-controlled incoming handover,
the counter accumulates the queuing time. The measurement
If the instance's queuing timer expires and if the resource request is due to MSC-controlled incoming handover, the counter
accumulates the queuing time. The measurement point is A,
3130

released due to some causes, if the resource request is due to
MSC-controlled incoming handover, the counter accumulates
the queuing time. The measurement point is A, as shown in
Figure 2973.
DURING
QUEUING

Unit
Statistics Object
Second
Cell
handover queue (On
SDCCH)
Description
This counter counts the number of queuings due to MSC-controlled

incoming handover towards SDCCH in the cell.
This counter is used to find out the total number of queuings due
to MSC-controlled incoming handover in the cell. It helps study
the cell's traffic.
instance receives the message of resource available. If the
resource request is due to MSC-controlled incoming handover,
in Figure 2974.
3131
If the instance's queuing timer expires and if the resource request is due to MSC-controlled incoming handover, the counter
2975.

released due to some causes, if the resource request is due
to MSC-controlled incoming handover, the counter increments.
DURING
QUEUING

Unit
3132
Times
Statistics Object
Cell
C902120036 MSC-contr
olled incoming handover
success time due to queue
(On SDCCH)
Description
This counter counts the total time of successfully obtaining SDCCH resource through queuing due to MSC-controlled incoming
handover in the cell.
This counter is used to find out the total time of successfully obtaining resource through queuing due to MSC-controlled incoming
handover in the cell. It helps study the effective queuing time.
request is due to MSC-controlled incoming handover, the counter
accumulates the queuing time. The measurement point is A, as

Unit
Second
3133
Statistics Object
Cell
queue (On SDCCH)
Description
This counter counts the total number of SDCCHs successfully obtained through queuing due to MSC-controlled incoming handover
in the cell.
This counter is used to find out the total number of calls that successfully obtain resource through queuing due to MSC-controlled
incoming handover in the cell. It helps study the queuing success
rate.
request is due to MSC-controlled incoming handover, the counter
2978.

Unit
Statistics Object
3134
Second
Cell
Chapter
108
Local Switch
Measurement
Table of Contents
Overview...................................................................... 3135
C902130001 The Request Number of Local Switch Establish
(Inside BSC) ................................................................. 3136
(Inside Site) ................................................................. 3136
(Inside Site Group) ........................................................ 3137
C902130004 The Request Number of Local Switch Release
(Return Normal Call) ...................................................... 3137
C902130005 The Failure Number of Establishing Local Switch
(Inside BSC/Connect Fail) ............................................... 3138
(Inside BSC/Other Reason Fail) ....................................... 3139
(Inside Site/Fail Returned by Site) ................................... 3139
(Inside Site Group/Fail Returned by Site) .......................... 3140
(Inside Site/No answer from Site).................................... 3141
(Inside Site Group/No answer from Site) .......................... 3142
(Inside Site/Other Reason Fail)........................................ 3142
(Inside Site Group/Other Reason Fail) .............................. 3143
(Abis unavailable).......................................................... 3143
(Connect Fail) ............................................................... 3144
(Ater unavailable).......................................................... 3145
Overview
Local switch measurement performs measurement for the success
rate of local switch establishment, failure causes, and the distribution of local switch types that are attempted to establish. Statistic
unit in this measurement is cell.
3135
C902130001 The Request

Number of Local Switch
Establish (Inside BSC)
Description
This counter counts the number of requests of local switch establishment inside BSC received by the service module from the
local switch management module. As shown in Figure 2979, when
the EV_LSMNG_LS_START_REQ message is received, if the local
switch type to be established is inside BSC, the counter counts.
FIGURE 2979 LOCAL SWITCH ESTABLISHMENT REQUEST

Unit
Statistics Object
Times
Cell

Establish (Inside Site)
Description
switch type to be established is inside site, the counter counts.
3136
Chapter 108 Local Switch Measurement

Unit
Statistics Object
Times
Cell

Establish (Inside Site Group)
Description
switch type to be established is inside site group, the counter
counts.

Unit
Statistics Object
Times
Cell

Release (Return Normal
Call)
Description
This counter counts the number of normal calls returned from the
local switch after the service module receives the request message. This measurement is performed at two measurement points.
The first measurement point: After handover is performed, if the
local switch cannot be held, the local switch management module
sends the request of local switch establishment to reestablish the
3137
voice channel that passes TC. After the RANCS module receives the
request message, the counter counts. The second measurement
point: If the local switch cannot be held due to various abnormalities, the local switch management module sends the request
of local switch termination. After the RANCS module receives the
termination request, the counter counts. The measurement points
are shown in Figure 2982 and Figure 2983.
FIGURE 2982 RETURNING NORMAL CALL REQUEST
DURING
FIGURE 2983 FORCEDLY RETURNING NORMAL CALL
FROM
HANDOVER
LOCAL SWITCH

Unit
Statistics Object
Times
Cell
C902130005 The Failure

Number of Establishing
Local Switch (Inside
BSC/Connect Fail)
Description
3138
This counter counts the number of failures of local switch establishment inside BSC, and the failure is due to connection failure. As
shown in Figure 2984, to establish the local switch inside BSC, the
DSP channel at the Abis interface processing board should be connected. When connecting the board fails or connecting the board
expires, the counter increments.
FIGURE 2984 ESTABLISHING LOCAL SWITCH INSIDE BSC

Unit
Statistics Object
Times
Cell

BSC/Other Reason Fail)
Description
This counter counts the number of failures of local switch establishment inside BSC, and the failure is due to other causes except
for connection failure.
Unit
Statistics Object
Times
Cell

Local Switch (Inside Site/Fail
Returned by Site)
Description
This counter counts the number of failures of local switch establishment inside the site, and the failure is due to response failure
of the site. As shown in Figure 2985, to establish the local switch
inside the site, the request of local switch establishment should
be sent to the site. After the site receives the request, it judges
3139
whether the local switch can be established with the relevant resource inside the site. If the local switch can be established, the
site returns the message that the local switch is established successfully; otherwise, the site returns the message that the local
switch establishment fails. If RANCS service receives the message indicating the failure of local switch establishment inside the
site (ABIS_LOCALSWITCH_NACK), the counter increments.
FIGURE 2985 FAILURE
OF
ESTABLISHING LOCAL SWITCH INSIDE SITE

Unit
Statistics Object
Times
Cell

Local Switch (Inside Site
Group/Fail Returned by Site)
Description
3140
This counter counts the number of failures of local switch establishment inside the site group, and the failure is due to response
failure of the site. As shown in Figure 2986, to establish the local
switch inside the site group, the request of local switch establishment should be sent to the site. After the site receives the
request, it judges whether to start sending voice package to the
opposite-end site and simultaneously receiving the voice package
from the opposite-end site. If the corresponding voice package
can be received from the opposite-end site within a period of time,
it indicates that the local switch is allowed, and the site returns
the message of the local switch being established successfully;
otherwise, the site returns the message that the local switch establishment fails. If RANCS service receives the message indicating the failure of local switch establishment inside the site group
(ABIS_LOCALSWITCH_NACK), the counter increments.
FIGURE 2986 FAILURE
OF
ESTABLISHING LOCAL SWITCH INSIDE SITE

Unit
Statistics Object
Times
Cell

Local Switch (Inside Site/No
answer from Site)
Description
This counter counts the number of failures of local switch establishment inside the site, and the failure is due to that the site's
responding time expires. As shown in Figure 2987, to establish
the local switch inside the site, the request of local switch establishment should be sent to the site. If it expires that RANCS service waits for the message indicating local switch establishment
success inside the site (ABIS_LOCALSWITCH_ACK), the counter
increments.
FIGURE 2987 RESPONDING TIME EXPIRES
SWITCH INSIDE SITE
WHEN
ESTABLISHING LOCAL

Unit
Times
3141
Statistics Object
Cell

Group/No answer from Site)
Description
This counter counts the number of failures of local switch establishment inside the site group, and the failure is due to that the site's
responding time expires. As shown in Figure 2988, to establish
the local switch inside the site group, the request of local switch
establishment should be sent to the site. If it expires that RANCS
service waits for the message indicating local switch establishment success inside the site group (ABIS_LOCALSWITCH_ACK),
FIGURE 2988 RESPONDING TIME EXPIRES
SWITCH INSIDE SITE
WHEN
ESTABLISHING LOCAL

Unit
Statistics Object
Times
Cell

Site/Other Reason Fail)
Description
3142
This counter counts the number of failures of local switch establishment inside the site, and the failure is due to other causes
except for that the site fails to respond and the site's responding
time expires.
Unit
Statistics Object
Times
Cell

Group/Other Reason Fail)
Description
This counter counts the number of failures of local switch establishment inside the site group, and the failure is due to other causes
except for that the site fails to respond and the site's responding
time expires.
Unit
Statistics Object
Times
Cell

Number of Returning Normal
Call (Abis unavailable)
Description
This counter counts the number of failures of the local switch returning the normal call, and the failure is due to Abis resource
unavailable. When the local switch is inside the site or the site
group, the corresponding Abis resource is not required after the
local switch is established, thus the resource is released. However,
when the local switch returns the normal call, the Abis resource
should be requested again. If the database module returns that
the Abis resource request fails, the counter increments. The measurement point is A, as shown in Figure 2989.
3143
FIGURE 2989 PROCESS

(TC IS INTERNAL)
OF
RETURNING NORMAL CALL
FROM
LOCAL SWITCH

Unit
Statistics Object
Times
Cell

Call (Connect Fail)
Description
This counter counts the number of failures of the local switch returning the normal call, and the failure is due to connection failure.
When the local switch returns the normal call, the Abis resource
and the TC resource (for external TC, it is Ater resource) should be
connected again. The measurement point is B, as shown in Figure
2990 and Figure 2991. If the board returns the message indicating connection failure or that the waiting for connection response
expires, the counter increments.
FIGURE 2990 PROCESS
(TC IS INTERNAL)
3144
OF
FROM
LOCAL SWITCH
FIGURE 2991 FAILURE

(TC IS EXTERNAL)
OF
FROM
LOCAL SWITCH

Unit
Statistics Object
Times
Cell

Call (Ater unavailable)
Description
This counter counts the number of failures of the local switch returning the normal call, and the failure is due to Ater resource
unavailable. When BSC is configured as TC being external, the
corresponding Ater resource is not required after the local switch
is established, thus the resource is released. However, when the
local switch returns the normal call, the Ater resource should be
requested again. If iTC returns that the Ater resource request
fails (Ater_ResrcReqNegAck), the counter increments. The measurement point is A, as shown in Figure 2992.
FIGURE 2992 FAILURE
(TC IS EXTERNAL)
OF
FROM
LOCAL SWITCH
3145

Unit
Statistics Object
3146
Times
Cell
Chapter
109
TFO Measurement
Table of Contents
C902420001 Number of first try to contact distant partner
after TFO being enabled ................................................. 3147
C902420002 Number of retrying to contact distant partner
after being interrupted ................................................... 3148
C902420003 Number of TFO contacting with distant partner
after first try................................................................. 3149
C902420004 Number of TFO recontacting with distant partner
after TFO being interrupted............................................. 3150
C902420005 Number of TFO establishment after first
try............................................................................... 3151
C902420006 Number of TFO reestablishment after being interrupted...................................................................... 3152
C902420007 Number of synchronization lost at A-Interface
resulting in TFO off ........................................................ 3153
C902420008 Number of codec type mismatch resulting in TFO
off ............................................................................... 3154
C902420009 Number of rate control failure resulting in TFO
off when using AMR codec type ....................................... 3155
TFO ............................................................................. 3155
TFO ............................................................................. 3156
C902420012 Number of active collection changes for establishing TFO ................................................................... 3156
C902420013 Number of active collection changes for optimizing TFO ........................................................................ 3156
C902420001 Number of first

try to contact distant partner
after TFO being enabled
Description
This counter counts the times that the TRAU attempts the TFO
negotiation for the first time.
This counter indicates the capability that the TRAU attempts TFO
negotiation for the first time during MS conversations by sending
the TFO message when TFO is enabled.
During MS conversations, the TRAU receives the TFO_Enable
message and starts the TFO state machine. When detecting the
3147
PCM_NON_IDLE message sent by the A interface, the TRAU sends

the TFO_FILL message to the A interface first, and then sends the
TFO_REQ/ACK message that carries the current speech version
info to the peer end to attempt TFO negotiation.
Usage
Measurement
Point
None
When the TRAU sends the TFO_REQ/ACK message for the first
time, this counter increases by 1, as shown in Figure 2993.
FIGURE 2993 NUMBER OF FIRST ATTEMPT
AFTER TFO BEING ENABLED
Unit
TO
CONTACT DISTANT PARTNER
Time
C902420002 Number
of retrying to contact
distant partner after being
interrupted
Description
This counter counts the times that the TRAU re-attempts TFO negotiation after first TFO negotiation.
This counter indicates the TFO re-negotiation capability when the
TFO interaction is out-of-sync and when the configuration changes
after handover during MS conversations.
During the TFO negotiation attempt, when the TFO interaction on
the A interface is out-of-sync, or the synchronization is lost after
TFO establishment, or speech version configuration changes due
to handover, the TRAU will re-send the TFO message that carries
the local configuration info to attempt renegotiation.
Usage
Measurement
Point
3148
None
When the TRAU re-sends the TFO_REQ(_L) message, this counter
increases by 1, as shown in Figure 2994.
Chapter 109 TFO Measurement
FIGURE 2994 NUMBER

BEING INTERRUPTED
Unit
OF
RETRYING
TO
CONTACT DISTANT PARTNER AFTER
Time
TFO contacting with distant
partner after first try
Description
This counter counts the times that the TRAU succeeds in the first
TFO negotiation attempt.
This counter indicates the capability that the TRAU succeeds in the
first TFO negotiation attempt.
The TRAU receives the TFO_Enable message and starts the TFO
state machine. When detecting the PCM_NON_IDLE message sent
by the A interface, the TRAU sends the TFO_FILL message to the
A interface first, and then sends the TFO_REQ/ACK message that
carries the current speech version info to the peer end to attempt
TFO negotiation. If the peer end supports TFO, the peer end will
also attempt TFO negotiation by sending a response after receiving the TFO message sent by the local end. When the local end
receives the TFO_ACK message replied by the peer end, it indicates that the negotiation succeeds.
Usage
Measurement
Point
None
When the TRAU receives the TFO_ACK/TFO_Frame message sent
by the peer end after sending the TFO_REQ/ACK message for the
first time to attempt TFO negotiation, this counter increases by 1,
3149
FIGURE 2995 NUMBER
OF
TFO
CONTACTING WITH DISTANT PARTNER AFTER
FIRST TRY
Unit
Time
TFO recontacting with
distant partner after TFO
being interrupted
Description
This counter counts the times that the TRAU succeeds in TFO negotiation reattempt.
This counter indicates the capability that the TRAU succeeds in TFO
negotiation reattempt.
During the TFO negotiation attempt, when the TFO interaction on
the A interface is out-of-sync, or the synchronization is lost after
TFO establishment, or speech version configuration changes due
to handover, the TRAU will re-send the TFO_REQ(_L) message that
carries the local configuration info to attempt renegotiation. If it
still supports TFO, the peer end will respond to the TFO message
sent by the local end or initiate the similar renegotiation. When
the local end receives the TFO_ACK(_L) message replied by the
peer end, it indicates that the renegotiation succeeds.
Usage
Measurement
Point
3150
None
When the TRAU receives the TFO_ACK(_L) message replied by the
peer end after re-sending the TFO_REQ(_L) message, this counter
increases by 1, as shown in Figure 2996.
FIGURE 2996 NUMBER OF TFO RECONTACTING WITH DISTANT PARTNER

AFTER TFO BEING INTERRUPTED
Unit
Time
TFO establishment after first
try
Description
This counter counts the times that the TRAU succeeds in TFO establishment after the first TFO negotiation.
establishment after the first TFO negotiation.
During MS conversations, the TRAU receives the TFO_Enable
message and starts the TFO state machine. When detecting
the PCM_NON_IDLE message sent by the A interface, the TRAU
sends the TFO message to attempt the first TFO negotiation. If it
supports TFO, the peer end will take similar action to attempt TFO
negotiation by responding to the TFO message sent by the local
end. When the local end receives the TFO_ACK message replied
by the peer end, it indicates that the negotiation succeeds. If
the codec algorithms of the two parties match according to the
negotiation result, the requirement for TFO establishment is met,
and the TRAU will send the TFO frame.
Usage
Measurement
Point
None
When the TRAU receives and uses the TFO frame, TFO is established and this counter increases by 1, as shown in Figure 2997.
3151
FIGURE 2997 NUMBER
Unit
OF
TFO ESTABLISHMENT AFTER FIRST TRY
Time
TFO reestablishment after
being interrupted
Description
This counter counts the times that the TRAU succeeds in TFO establishment after TFO renegotiation.
establishment after TFO renegotiation.
TFO may not be established successfully after the TRAU attempts
the first negotiation. When the TFO synchronization is lost or
speech version configuration changes due to handover, the TFO
establishment may be interrupted. When the TFO establishment
is interrupted, the TRAU will re-send the TFO_REQ(_L) message
that carries the local configuration info to attempt renegotiation. If
it still supports TFO, the peer end will respond to the TFO message
sent by the local end or initiate the similar renegotiation. When
the renegotiation is successful, the TRAU will send the TFO frame
if the codec algorithms match according to the negotiation result
indicating that the requirement for TFO establishment is met.
Usage
Measurement
Point
3152
None
When the TRAU receives and uses the TFO frame, TFO is established and this counter increases by 1, as shown in Figure 2998.
FIGURE 2998 NUMBER

INTERRUPTED
Unit
OF
TFO REESTABLISHMENT AFTER BEING
Time
synchronization lost at
A-Interface resulting in TFO
off
Description
This counter counts the times that TFO is interrupted due to synchronization loss on the A interface.
This counter indicates the situation that TFO is interrupted or cannot be established due to TFO synchronization loss.
When the TRAU attempts TFO establishment negotiation or TFO is
established, the interaction of the TFO message or TFO frame is
abnormal if synchronization on the A interface is lost. In this case,
the TFO cannot be established or will be interrupted.
Usage
Measurement
Point
None
When the TRAU attempts the TFO establishment negotiation, this
counter increases by 1 if the TFO message replied by the peer end
is interrupted or TFO cannot be established due to the failure in
receiving the TFO frame sent by the peer end, as shown in Figure
2999. When TFO is established, this counter increases by 1 if TFO
is interrupted due to TFO synchronization loss, as shown in Figure
3000.
3153
Unit
FIGURE 2999 NUMBER OF SYNCHRONIZATION LOSS

RESULTING IN TFO OFF 1
AT
A-INTERFACE
FIGURE 3000 NUMBER OF SYNCHRONIZATION LOSS

RESULTING IN TFO OFF 2
AT
A-INTERFACE
Time
C902420008 Number
of codec type mismatch
resulting in TFO off
Description
This counter counts the times that TFO is interrupted due to codec
algorithm mistach. This counter indicates the impact of the codec
algorithm configuration on TFO establishment.
When the TRAU succeeds in TFO negotiation, TFO cannot be established and this counter increases by 1 if the codec algorithms
of the two parties do not match according to the negotiation result. When TFO is established, TFO is interrupted and this counter
increases by 1 if the local or remote codec algorithm changes due
to handover and the codec algorithms do not match after renegotiation.
3154
Usage
None
Measurement
Point
None
Unit
Time
C902420009 Number of rate

control failure resulting in
TFO off when using AMR
codec type
Description
This counter counts the times that TFO cannot be established due
to rate control failure during TFO establishment when the MS uses
the AMR algorithm.
This counter indicates the times that TFO cannot be established
due to rate control failure when the MS uses the AMR algorithm.
After the TRAU succeeds in TFO negotiation, the TRAU sends the
TFO_SOON configuration message to the BTS, indicating that the
currently requested CMR is the highest speech coding rate that
meets the requirement for TFO establishment, if the codec algorithms of two parties are AMR and ACS configuration collection
meets the requirement for TFO establishment according to the negotiation result. Meanwhile, the TRAU starts a TFO timer, which
requires the BTS to control the uplink speech coding rate within
the permitted time range. After receiving the TFO_SOON message, the BTS controls the MS uplink rate. When detecting that
the uplink coding rate of the MS does not exceed CMR, the BTS considers that the rate control is successful and replies a TFO_SOON
message to the TRAU. If the TRAU does not receive the TFO_SOON
message replied by the BTS before the timer times out, it indicates
that the rate control fails and TFO cannot be established. In this
case, this counter increases by 1.
Usage
None
Measurement
Point
None
Unit
Time
C902420010 Number
of mode changes for
establishing TFO
Description
Related Features

ZGO-04-02-006 TFO
3155
mode changes for optimizing
TFO
Description
Related Features

ZGO-04-02-006 TFO
establishing TFO
Description
Related Features

ZGO-04-02-006 TFO
optimizing TFO
Description
Related Features
3156

ZGO-04-02-006 TFO
Chapter
110
IP SLA PD Statistic
Table of Contents
C902270001 PD Type..................................................... 3157
C902270002 PD SubType ............................................... 3158
C902270003 ULP Pno..................................................... 3158
C902270004 ULP TYPE ................................................... 3158
C902270005 ULP ID ...................................................... 3158
C902270006 Packet Type................................................ 3159
C902270007 Up Protocol ................................................ 3159
C902270008 Source IP 1 ................................................ 3159
C902270009 Source IP 2 ................................................ 3159
C902270010 Source IP 3 ................................................ 3159
C902270011 Source IP 4 ................................................ 3160
C902270012 Source Port ................................................ 3160
C902270013 Destination IP 1.......................................... 3160
C902270014 Destination IP 2.......................................... 3160
C902270015 Destination IP 3.......................................... 3161
C902270016 Destination IP 4.......................................... 3161
C902270017 Destination Port.......................................... 3161
C902270018 Send PD Request ........................................ 3162
C902270019 Receive PD Reply ........................................ 3162
C902270020 PD Packet Loss Rate .................................... 3162
C902270021 PD Packet statistics by watch time................. 3162
C902270022 PD Packet Loss Rate by watch time ............... 3163
C902270023 PD Packet Out of Sequence .......................... 3163
C902270024 Receive PD Request..................................... 3163
C902270025 Send PD Reply............................................ 3164
C902270025 Min Delay .................................................. 3164
C902270027 Max Delay.................................................. 3164
C902270028 Mean Delay ................................................ 3164
C902270029 Max Jitter .................................................. 3165
C902270030 Min Jitter ................................................... 3165
C902270031 Mean Jitter................................................. 3165
C902270032 Jitter Sampling Times .................................. 3165
C902270033 Number of delay sampling............................ 3166
C902270001 PD Type
Description
This counter indicates the PD type.
Usage
None
Measurement
Point
None
Unit
None
3157
C902270002 PD SubType
Description
For IP PD, each bit of ucPDSubType indicates a performance index.

For other detection type, this field is reserved.
Usage
None
Measurement
Point
None
Unit
None
C902270003 ULP Pno

Description
This counter indicates the process No. of the upper layer user.
Usage
None
Measurement
Point
None
Unit
None
C902270004 ULP TYPE

Description
The ULP type is used to differentiate multiple upper layer users

of a same process. For example, when SCTP/TCP/DNS/RTP of the
BRS process initiates detection, the respective protocol No. is set
as the ULP type.
Usage
None
Measurement
Point
None
Unit
None
C902270005 ULP ID
Description
3158
The ULP IDs are used to identify multiple detection tasks initiated
by a same upper layer user.
Usage
None
Measurement
Point
None
Unit
None
Chapter 110 IP SLA PD Statistic
C902270006 Packet Type

Description
This counter indicates the detection packet type (ICMP or UDP).
Usage
None
Measurement
Point
None
Unit
None
C902270007 Up Protocol
Description
This counter indicates No. of the upper layer protocol for internal
encapsulation (1: ICMP, 6: TCP, 17: UDP, 132: SCTP).
Usage
None
Measurement
Point
None
Unit
None
C902270008 Source IP 1
Description
This counter indicates source IP 1.
Usage
None
Measurement
Point
None
Unit
None
Description
Usage
None
Measurement
Point
None
Unit
None
Description
3159
Usage
None
Measurement
Point
None
Unit
None
Description
Usage
None
Measurement
Point
None
Unit
None
C902270012 Source Port

Description
This counter indicates No. of the source port.
Usage
None
Measurement
Point
None
Unit
None
C902270013 Destination IP
1
Description
This counter indicates destination IP 1.
Usage
None
Measurement
Point
None
Unit
None
2
Description
Usage
3160

None
Measurement
Point
None
Unit
None
3
Description
Usage
None
Measurement
Point
None
Unit
None
4
Description
Usage
None
Measurement
Point
None
Unit
None
C902270017 Destination
Port
Description
This counter indicates No. of the destination port.
Usage
None
Measurement
Point
None
Unit
None
3161
C902270018 Send PD
Request
Description
The counter counts the number of the sent PD Requests.
Usage
None
Measurement
Point
None
Unit
None
C902270019 Receive PD
Reply
Description
The counter counts the number of the received PD replies.
Usage
None
Measurement
Point
None
Unit
None
C902270020 PD Packet
Loss Rate
Description
Usage
Measurement
Point
Unit
This counter indicates the PD packet loss ratio. The field is scraped.
None
This counter is updated when the delay reporting timer times out
or PD response packet is received or PD status is queried.
0.1
statistics by watch time
Description
Usage
3162
The counter counts the number of packets received in the specified

watch time.
None
Measurement
Point
Unit
This counter is updated when a packet is received in the watch

time.
None
Loss Rate by watch time
Description
Usage
Measurement
Point
Unit
The counter indicates the packet loss ratio in the specified watch
time.
None
or the PD reply packet is received or the PD status is queried.
0.1
C902270023 PD Packet Out

of Sequence
Description
Usage
Measurement
Point
Unit
The counter counts the number of PD packets that are out of sequence.
None
This counter is increased by 1 when an out-of-sequence PD reply
packet is received.
None
C902270024 Receive PD
Request
Description
The counter counts the number of received PD requests.

This counter is not supported and its value is invalid currently.
Usage
Measurement
Point
Unit
None
This counter increases by 1 when a PD request is received.
None
3163
C902270025 Send PD Reply

Description
The counter counts the number of send PD replies.

This counter is not supported and its value is invalid currently.
Usage
Measurement
Point
Unit
None
This counter increases by 1 when a PD reply is rent.
None
C902270025 Min Delay

Description
Usage
Measurement
Point
Unit
The counter indicates the minimum delay.

None
This counter is updated when a PD reply packet is received.
ms
C902270027 Max Delay

Description
Usage
Measurement
Point
Unit
The counter indicates the maximum delay.

None
ms
C902270028 Mean Delay

Description
Usage
Measurement
Point
3164
The counter indicates the mean delay.

None
Unit
ms
C902270029 Max Jitter

Description
Usage
Measurement
Point
Unit
The counter indicates the maximum jitter.

None
ms
C902270030 Min Jitter

Description
Usage
Measurement
Point
Unit
The counter indicates the minimum jitter.

None
This counter is updated when the PD reply packet is received.
ms
C902270031 Mean Jitter

Description
Usage
Measurement
Point
Unit
The counter indicates the mean delay.

None
ms
C902270032 Jitter Sampling

Times
Description
Usage
Measurement
Point
Unit
The counter counts the number of jitter samplings.

None
Time
3165
delay sampling
Description
Usage
Measurement
Point
Unit
3166
The counter counts the number of delay samplings.

None
Time
Appendix
Corresponding
Relationship between
Basic Measurement
Counters and General
Measurement Counters
In the network management system, ZXG10 iBSC performance
measurement has two types, basic measurement and general
management. The difference between the two is that general
measurement is impossible unless a measurement task is created,
while basic measurement is used for regular reports, which can
be outputted without creating a measurement task.
Except different IDs, basic measurement counters and general
measurement counters share the same information, such as name,
description, and measurement. Table 1 lists the corresponding relationship between the two types of counters.
TABLE 1 CORRESPONDING RELATIONSHIP BETWEEN BASIC MEASUREMENT
COUNTERS AND GENERAL MEASUREMENT COUNTERS
Basic Measurement Counter ID
Corresponding General Measurement Counter ID
C900040001
C901000007
C900040002
C901000016
C900040003
C901000017
C900040004
C901000018
C900040005
C901000019
C900040006
C901000020
C900040007
C901000021
C900040008
C901000022
C900040009
C901000029
C900040010
C901000038
3167
3168
C900040011
C901000039
C900040012
C901000040
C900040013
C901000041
C900040014
C901000042
C900040015
C901000043
C900040016
C901000044
C900040017
C901000049
C900040018
C901000051
C900040019
C901010008
C900040020
C901010015
C900040021
C901010016
C900040022
C901010017
C900040023
C901010018
C900040024
C901010019
C900040025
C901010020
C900040026
C901010021
C900040027
C901010029
C900040028
C901010036
C900040029
C901010037
C900040030
C901010038
C900040031
C901010039
C900040032
C901010040
C900040033
C901010041
C900040034
C901010042
C900040035
C901010047
C900040036
C901010049
C900040037
C901010051
C900040038
C901010052
C900040039
C901010053
C900040040
C901010054
Appendix A Corresponding Relationship between Basic Measurement

Counters and General Measurement Counters
C900040041
C901010055
C900040042
C901010057
C900040043
C901010058
C900040044
C901010059
C900040045
C901010060
C900040046
C901010061
C900040047
C901020010
C900040048
C901020011
C900040049
C901020012
C900040050
C901020013
C900040051
C901020015
C900040052
C901020016
C900040053
C901020017
C900040054
C901020018
C900040055
C901020027
C900040056
C901020028
C900040057
C901020029
C900040058
C901020030
C900040059
C901020032
C900040060
C901020033
C900040061
C901020035
C900040062
C901020036
C900040063
C901020037
C900040064
C901020038
C900040065
C901020039
C900040066
C901020040
C900040067
C901020042
C900040068
C901020043
C900040069
C901020045
C900040070
C901020046
3169
3170
C900040071
C901020047
C900040072
C901020048
C900040073
C901020049
C900040074
C901020051
C900040075
C901020052
C900040076
C901020053
C900040077
C901020054
C900040078
C901160015
C900040079
C901160016
C900040080
C901030001
C900040081
C901030002
C900040082
C901030003
C900040083
C901030004
C900040084
C901030005
C900040085
C901030015
C900040086
C901030016
C900040087
C901030017
C900040088
C901030018
C900040089
C901030028
C900040090
C901030029
C900040091
C901030030
C900040092
C901030031
C900040093
C901030043
C900040094
C901030044
C900040095
C901030045
C900040096
C901030046
C900040097
C901030047
C900040098
C901030057
C900040099
C901030058
C900040100
C901030059

C900040101
C901030060
C900040102
C901030070
C900040103
C901030071
C900040104
C901030072
C900040105
C901030073
C900040106
C901030096
C900040107
C901030097
C900040108
C901170001
C900040109
C901170006
C900040110
C901170021
C900040111
C901170022
C900040112
C901170034
C900040113
C901170035
C900040114
C901180001
C900040115
C901180006
C900040116
C901180021
C900040117
C901180022
C900040118
C901180034
C900040119
C901180035
C900040120
C901190001
C900040121
C901190014
C900040122
C901190036
C900040123
C901190037
C900040124
C901190049
C900040125
C901190050
C900040126
C901190062
C900040127
C901190063
C900040128
C901200001
C900040129
C901200014
C900040130
C901200036
3171
3172
C900040131
C901200037
C900040132
C901200049
C900040133
C901200050
C900040134
C901200062
C900040135
C901200063
C900040136
C901040003
C900040137
C901040007
C900040138
C901040008
C900040139
C901040016
C900040140
C901040017
C900040141
C901000002
C900040142
C901000003
C900040143
C901000004
C900040144
C901000008
C900040145
C901000024
C900040146
C901000025
C900040147
C901000026
C900040148
C901000030
C900040149
C901000053
C900040150
C901000054
C900040151
C901000055
C900040152
C901000056
C900040153
C901000057
C900040154
C901000059
C900040155
C901000060
C900040156
C901000061
C900040157
C901000062
C900040158
C901000063
C900040159
C901010003
C900040160
C901010004

C900040161
C901010005
C900040162
C901010063
C900040163
C901010024
C900040164
C901010025
C900040165
C901010026
C900040166
C901010030
C900040167
C901040015
C900040168
C901010009
C900040169
C901000064
C900040170
C901000065
C900040171
C901010062
C900040172
C901030006
C900040173
C901030007
C900040174
C901030008
C900040175
C901030009
C900040176
C901030010
C900040177
C901030011
C900040178
C901030012
C900040179
C901030013
C900040180
C901030014
C900040181
C901030019
C900040182
C901030020
C900040183
C901030021
C900040184
C901030022
C900040185
C901030023
C900040186
C901030024
C900040187
C901030025
C900040188
C901030026
C900040189
C901030027
C900040190
C901030032
3173
3174
C900040191
C901030033
C900040192
C901030034
C900040193
C901030035
C900040194
C901030036
C900040195
C901030037
C900040196
C901030038
C900040197
C901030039
C900040198
C901030040
C900040199
C901030048
C900040200
C901030049
C900040201
C901030050
C900040202
C901030051
C900040203
C901030052
C900040204
C901030053
C900040205
C901030054
C900040206
C901030055
C900040207
C901030056
C900040208
C901030061
C900040209
C901030062
C900040210
C901030063
C900040211
C901030064
C900040212
C901030065
C900040213
C901030066
C900040214
C901030067
C900040215
C901030068
C900040216
C901030069
C900040217
C901030074
C900040218
C901030075
C900040219
C901030076
C900040220
C901030077

C900040221
C901030078
C900040222
C901030079
C900040223
C901030080
C900040224
C901030081
C900040225
C901030082
C900040232
C901020055
C900040233
C901020056
C900040234
C901020057
C900040235
C901020058
C900030001
C901460004
C900030002
C901460005
C900060001
C901110005
C900060002
C901110007
C900060003
C901250001
C900060004
C901250002
C900060005
C901250003
C900060006
C901250004
C900060007
C901250006
C900060008
C901250008
C900060009
C901250009
C900060010
C901260001
C900060011
C901260003
C900060012
C901260004
C900060013
C901260006
C900060014
C901260008
C900060015
C901260009
C900060016
C901260012
C900060017
C901260014
C900060018
C901260015
C900060019
C901260020
3175
3176
C900060020
C901260022
C900060021
C901260023
C900060022
C901260025
C900060023
C901260027
C900060024
C901260028
C900060025
C901260039
C900060026
C901260051
C900060027
C901260052
C900060028
C901260063
C900060029
C901260064
C900060030
C901260069
C900060031
C901260071
C900060032
C901260072
C900060033
C901260074
C900060034
C901260076
C900060035
C901260077
C900060036
C901260088
C900060037
C901260089
C900060038
C901270001
C900060039
C901270003
C900060040
C901270004
C900060041
C901270006
C900060042
C901270020
C900060043
C901270022
C900060044
C901270023
C900060045
C901270025
C900060046
C901270069
C900060047
C901270071
C900060048
C901270072
C900060049
C901270074

C900060050
C901150003
C900060051
C901150008
C900060052
C901070006
C900060053
C901070050
C900060054
C901070051
C900060055
C901070052
C900060056
C901120019
C900060057
C901120020
C900060058
C901120021
C900060059
C901120022
C900060060
C901120023
C900060061
C901120025
C900060062
C901120026
C900060063
C901120027
C900060064
C901120028
C900060065
C901120029
C900060066
C901120036
C900060067
C901120037
C900060068
C901120038
C900060069
C901120039
C900060070
C901120040
C900060071
C901120041
C900060072
C901120042
C900060073
C901120043
C900060074
C901120044
C900060075
C901120045
C900060076
C901120046
C900060077
C901120047
C900060078
C901120048
C900060079
C901120049
3177
3178
C900060080
C901120050
C900060081
C901120051
C900060082
C901060025
C900060083
C901060026
C900060084
C901060027
C900060085
C901060028
C900060086
C901060029
C900060087
C901060030
C900060088
C901060031
C900060089
C901060032
C900060090
C901060033
C900060091
C901060034
C900060092
C901060047
C900060093
C901090002
C900060094
C901090003
C900060095
C901090009
C900060096
C901090010
C900060097
C901090012
C900060098
C901090019
C900060099
C901090029
C900060100
C901090031
C900060101
C901090033
C900060102
C901090036
C900060103
C901090050
C900060104
C901090051
C900060105
C901090056
C900060106
C901090057
C900060107
C901090070
C900060108
C901090071
C900060109
C901090076

C900060110
C901090077
C900060111
C901090082
C900060112
C901090083
C900060113
C901090088
C900060114
C901090089
C900060115
C901090094
C900060116
C901090095
C900060117
C901090100
C900060118
C901090101
C900060119
C901090106
C900060120
C901090107
C900060121
C901080013
C900060122
C901080001
C900060123
C901080002
C900060124
C901080005
C900060125
C901080009
C900060126
C901080010
C900060127
C901080015
C900060128
C901080021
C900060129
C901080023
C900060130
C901080031
C900060131
C901110025
C900060132
C901150013
C900060133
C901080007
C900060134
C901080028
C900060135
C901270015
C900060136
C901110002
C900060137
C901110030
C900060138
C901260029
C900060139
C901260030
3179
3180
C900060140
C901260031
C900060141
C901260040
C900060142
C901260041
C900060143
C901260042
C900060144
C901260043
C900060145
C901260053
C900060146
C901260054
C900060147
C901260055
C900060148
C901260078
C900060149
C901260079
C900060150
C901260080
C900060151
C901070041
C900060152
C901280058
C900060153
C901280059
C900060154
C901280060
C900060155
C901080019
C900060156
C901260034
C900060157
C901260035
C900060158
C901260036
C900060159
C901260037
C900060160
C901260046
C900060161
C901260047
C900060162
C901260048
C900060163
C901260049
C900060164
C901260058
C900060165
C901260059
C900060166
C901260060
C900060167
C901260061
C900060168
C901260066
C900060169
C901260083

C900060170
C901260084
C900060171
C901260085
C900060172
C901260086
C900060173
C901260091
C900060174
C901270009
C900060175
C901270028
C900060176
C901270029
C900060177
C901270030
C900060178
C901270031
C900060179
C901270034
C900060180
C901270035
C900060181
C901270036
C900060182
C901270037
C900060183
C901270040
C900060184
C901270041
C900060185
C901270042
C900060186
C901270043
C900060187
C901270046
C900060188
C901270047
C900060189
C901270048
C900060190
C901270049
C900060191
C901270052
C900060192
C901270053
C900060193
C901270054
C900060194
C901270055
C900060195
C901270058
C900060196
C901270059
C900060197
C901270060
C900060198
C901270061
C900060199
C901270063
3181
3182
C900060200
C901270064
C900060201
C901270066
C900060202
C901270077
C900060203
C901270078
C900060204
C901270079
C900060205
C901270080
C900060206
C901270083
C900060207
C901270084
C900060208
C901270085
C900060209
C901270086
C900060210
C901270088
C900060211
C901270089
C900060212
C901270091
C900060213
C901090014
C900060214
C901090016
C900060215
C901090018
C900060216
C901090035
C900060217
C901080020
C900060218
C901080029
C900060219
C901070013
C900060220
C901070020
C900060221
C901070027
C900060222
C901070034
C900060223
C901070048
C900060224
C901060048
C900060225
C901060049
C900060226
C901060050
C900060227
C901060051
C900060228
C901060052
C900060229
C901060053

C900060230
C901060054
C900060231
C901060055
C900060232
C901060056
C900060233
C901060057
C900060234
C901060070
C900060235
C901270014
C900060236
C901110004
C900060237
C901090143
C900060238
C901090144
C900060239
C901090146
C900060240
C901090147
C900060241
C901250013
C900060242
C901250014
C900060243
C901250015
C900060244
C901070016
C900060245
C901070037
C900050001
C901410004
C900050002
C901410003
3183
3184
Figures
Figure 1 Measurement Point of Number of Requests for

Establishing GPRS Downlink Data TBF Before
T3192 Overtime ................................................11
Figure 2 Measurement Point of Number of Established GPRS
Downlink Data TBF Using Existing Resources .........11
Establishing GPRS Downlink Data TBF on Uplink
GPRS TBF PACCH...............................................12
Figure 4 Measurement Point of Number of GPRS DL TBF
Release due to N3105 Overflow ...........................13
Release due to Other Reasons .............................14
Forcing Release by Control Plane .........................14
Release due to Instance Suspension.....................15
Establishing GPRS Downlink Data TBF Before
T3192 Overtime ................................................17
Figure 9 Measurement Point of Number of Established GPRS
Downlink Data TBF Using Existing Resources .........17
Establishing GPRS Downlink Data TBF on Uplink
GPRS TBF PACCH...............................................18
Figure 11 Measurement Point of Number of EGPRS DL TBF
Release due to Other Reasons .............................20
Figure 15 Measurement Point of Number of GPRS UL Data
TBF Establishment Success on PACCH ..................24
3185
Figure 16 Measurement Point of Number of GPRS UL TBF

Figure 21 UL TBF Flow of 1-Step Access................................28
Figure 24 Measurement Point of Number of EGPRS UL TBF
Establishment Success on PACCH.........................31
Figure 25 Measurement Point of Number of EGPRS DL LLC
Frames.............................................................39
Figure 26 Measurement Point of Number of Discarded EGPRS
DL LLC Frames due to Buffer Overflow..................40
DL LLC Frames due to Life Time Expiration ............40
DL LLC Frames due to Other Reasons ...................41
Figure 29 Measurement Point of Number of DL Signaling LLC
Frames.............................................................42
DL Signaling LLC Frames due to Buffer Overflow ....42
Figure 31 Measurement Point of Number of Discarded
EGPRS DL Signaling LLC Frames due to Life Time
Expiration.........................................................43
DL Signaling LLC Frames due to Other Reasons .....44
Figure 33 Measurement Point of Total Bytes of Effective
Upper Layer Protocol Data Sent on DL PDCH .........45
Figure 34 Measurement Point of Total Bytes of Effective
Upper Layer Protocol Data Received on UL PDCH ...45
Figure 35 Measurement Point of Bytes of LLC Frame on GPRS
UL Data TBF .....................................................46
Figure 36 Measurement Point of Duration of GPRS UL Data
TBF .................................................................47
3186
Figures
Figure 37 Measurement Point of Duration of GPRS UL Data

TBF (Extended UL TBF) ......................................47
Figure 38 Measurement Point of Bytes of LLC Frame on GPRS
DL Data TBF .....................................................48
Figure 39 Measurement Point of Duration of GPRS DL Data
TBF .................................................................49
Figure 40 Measurement Point of Number of Effective Data
Blocks Received on GPRS UL TBF .........................50
Figure 41 Measurement Point of Number of NACK Blocks
Received on GPRS UL TBF ...................................50
Blocks Sent on GPRS DL TBF ...............................51
Sent on GPRS DL TBF.........................................52
Figure 44 Measurement Point of Bytes of LLC Frame on
EGPRS UL Data TBF ...........................................53
Figure 45 Measurement Point of Duration of EGPRS UL Data
TBF .................................................................53
Figure 46 Measurement Point of Duration of EGPRS UL Data
TBF (Extended UL TBF) ......................................54
Figure 47 Measurement Point of Bytes of LLC Frame on
EGPRS DL Data TBF ...........................................55
Figure 48 Measurement Point of Duration of EGPRS DL Data
TBF .................................................................56
Blocks Received on EGPRS UL TBF .......................57
Received on EGPRS UL TBF .................................57
Blocks Sent on EGPRS DL TBF .............................58
Figure 52 Measurement Point of Number of Nack Blocks Sent
on EGPRS DL TBF ..............................................59
Figure 53 Measurement Point of Downlink GPRS LLC Frames ...60
Figure 54 Measurement Point of Discarded Downlink GPRS
LLC Frames due to Buffer Overflow ......................60
LLC Frames due to Life Time Expiration ................61
LLC Frames due to Other Reasons........................62
3187
Figure 57 Measurement Point of Number of DL Dummy

Control Blocks on PACCH ....................................62
Figure 58 Measurement Point of Number of UL Dummy
Control Blocks on PACCH ....................................63
Figure 59 Measurement Point of Number of DL RLC Blocks on
PACCH (Excluding Dummy Block).........................64
Figure 60 Measurement Point of Number of DL RLC Pending
Blocks on PDTCH ...............................................64
Blocks on PDTCH ...............................................65
Blocks on PDTCH ...............................................66
Blocks on PDTCH ...............................................66
Figure 64 Measurement Point of Number of DL RLC NACK
Blocks on PDTCH ...............................................67
Blocks on PDTCH ...............................................68
Blocks on PDTCH ...............................................69
Blocks on PDTCH ...............................................69
Figure 68 Measurement Point of Number of DL RLC New
Blocks on PDTCH ...............................................70
Blocks on PDTCH ...............................................71
Blocks on PDTCH ...............................................71
Blocks on PDTCH ...............................................72
Figure 72 Measurement Point of Number of UL RLC Blocks
Excluding Dummy Blocks on PACCH .....................73
Figure 73 Measurement Point of Number of UL RLC Pending
Blocks on PDTCH ...............................................73
Blocks on PDTCH ...............................................74
Blocks on PDTCH ...............................................75
Blocks on PDTCH ...............................................75
3188
Figures
Figure 77 Measurement Point of Number of UL RLC NACK

Blocks on PDTCH ...............................................76
Blocks on PDTCH ...............................................77
Blocks on PDTCH ...............................................78
Blocks on PDTCH ...............................................78
Figure 81 Measurement Point of Number of UL RLC New
Blocks on PDTCH ...............................................79
Blocks on PDTCH ...............................................80
Blocks on PDTCH ...............................................80
Blocks on PDTCH ...............................................81
Figure 85 Measurement Point of Allocation Failures after
Receiving DL TBF Establishment Request ..............83
Receiving DL TBF Assignment Message .................84
Resource Reallocation Requests due to UL TBF
Establishment ...................................................84
Figure 88 Measurement Point of Number of GPRS DL
TBF Resource Reallocation Failure of channel
allocation due to UL TBF Establishment.................85
Resource Reallocation Requests due to LLC
Transmission .....................................................86
allocation due to LLC Transmission .......................87
Receiving DL TBF Establishment Request ..............88
Resource Reallocation Requests due to UL TBF
Establishment ...................................................89
3189

allocation due to UL TBF Establishment.................90
Transmission .....................................................91
Receiving CCCH Request.....................................93
Receiving PCCCH Request ...................................93
Figure 99 Measurement Point of Allocation Failures (DL GPRS
TBF Exists) .......................................................94
Resource Reallocation Requests due to DL TBF
Establishment ...................................................94
Transmission .....................................................96
Resource Reallocation Requests for Resource
Request............................................................98
Figure 105 Failing to Request for Resource from Database.......98
Figure 106 Measurement Point of Number of EGPRS Uplink
TBF Establishment Channel Allocation Failures ..... 100
Figure 107 Measurement Point of Allocation Failures (DL
GPRS TBF Exists)............................................. 100
Resource Reallocation Requests due to DL TBF
Establishment ................................................. 101
Receiving DL TBF Assignment Message ............... 101
3190
Figures

Transmission ................................................... 102
allocation due to LLC Transmission ..................... 103
Resource Reallocation Requests for Resource
Request.......................................................... 104
Figure 113 Failing to Request for Resource from Database..... 104
TBF Establishment Requests Before T3192
Expiration....................................................... 107
Figure 115 Measurement Point of GPRS DL TBF Establishment
Using Existing DL TBF Resource ......................... 108
Establishment Requests on PACCH ..................... 109
Establishment Requests on CCCH/PCCCH ............ 110
Figure 118 Measurement Point of Number of EGPRS DL
TBF Establishment Requests Before T3192
Expiration....................................................... 111
Establishment Using Existing DL TBF Resource..... 112
Establishment Requests on PACCH ..................... 112
Figure 121 Normal CCCH/PCCCH DL TBF Establishment
Process .......................................................... 113
Signaling TBF Release due to N3105 Overflow ..... 114
Release due to Other Reasons ........................... 115
Forcing Release by Control Plane ....................... 116
Release due to Instance Suspension................... 117
Figure 126 Measurement Point of Number of EGPRS DL
Signaling TBF Release due to N3105 Overflow ..... 118
Release due to Other Reasons ........................... 119
3191

Forcing Release by Control Plane ....................... 120
Release due to Instance Suspension................... 121
Figure 130 Measurement Point on Number of GPRS UL TBF
Reestablishments in Released State (1) .............. 122
Figure 131 Measurement Point on Number of GPRS UL TBF
Figure 132 Measurement Point of GPRS UL TBF
Establishments with Existing UL Resource ........... 123
Establishing UL GPRS TBF on PACCH .................. 124
Figure 134 Measurement Point on Number of EGPRS UL TBF
Figure 135 Measurement Point on Number of EGPRS UL TBF
Figure 136 Measurement Point of EGPRS UL TBF
Establishments with Existing UL Resource ........... 126
Establishing UL EGPRS TBF on PACCH................. 127
Figure 138 Measurement Point of Number of EGPRS UL TBF
Blocks on PDTCH ............................................. 131
Blocks on PDTCH ............................................. 132
Blocks on PDTCH ............................................. 132
Blocks on PDTCH ............................................. 133
Blocks on PDTCH ............................................. 134
Blocks on PDTCH ............................................. 134
Blocks on PDTCH ............................................. 135
Blocks on PDTCH ............................................. 136
3192
Figures

Blocks on PDTCH ............................................. 137
Blocks on PDTCH ............................................. 137
Blocks on PDTCH ............................................. 138
Blocks on PDTCH ............................................. 139
Blocks on PDTCH ............................................. 139
Blocks on PDTCH ............................................. 140
Blocks on PDTCH ............................................. 141
Blocks on PDTCH ............................................. 142
Blocks on PDTCH ............................................. 142
Blocks on PDTCH ............................................. 143
Blocks on PDTCH ............................................. 144
Blocks on PDTCH ............................................. 144
Blocks on PDTCH ............................................. 145
Blocks on PDTCH ............................................. 146
Blocks on PDTCH ............................................. 147
Blocks on PDTCH ............................................. 147
Blocks on PDTCH ............................................. 148
Blocks on PDTCH ............................................. 149
Blocks on PDTCH ............................................. 149
Blocks on PDTCH ............................................. 150
3193

Blocks on PDTCH ............................................. 151
Blocks on PDTCH ............................................. 152
Blocks on PDTCH ............................................. 152
Blocks on PDTCH ............................................. 153
Blocks on PDTCH ............................................. 154
Blocks on PDTCH ............................................. 154
Blocks on PDTCH ............................................. 155
Blocks on PDTCH ............................................. 156
Blocks on PDTCH ............................................. 157
Blocks on PDTCH ............................................. 157
Blocks on PDTCH ............................................. 158
Blocks on PDTCH ............................................. 159
Blocks on PDTCH ............................................. 159
Blocks on PDTCH ............................................. 160
Blocks on PDTCH ............................................. 161
Blocks on PDTCH ............................................. 162
Blocks on PDTCH ............................................. 162
Blocks on PDTCH ............................................. 163
Blocks on PDTCH ............................................. 164
Blocks on PDTCH ............................................. 164
3194
Figures

Blocks on PDTCH ............................................. 165
Blocks on PDTCH ............................................. 166
Blocks on PDTCH ............................................. 167
Blocks on PDTCH ............................................. 167
Blocks on PDTCH ............................................. 168
Blocks on PDTCH ............................................. 169
Figure 194 Measurement Point of Uplink GPRS TBF
Throughput..................................................... 169
Figure 195 Measurement Point of Downlink GPRS TBF
Throughput..................................................... 170
Figure 196 Measurement Point of Uplink EGPRS TBF
Throughput..................................................... 171
Figure 197 Measurement Point of Downlink EGPRS TBF
Throughput..................................................... 171
Figure 198 Radio Access Flow............................................ 183
Figure 200 Immediate Assignment Flow ............................. 185
Figure 203 Internal Handover Flow (Intra-Cell Handover)...... 188
Figure 204 External Handover Flow .................................... 188
Figure 205 Internal Handover Flow (Intra-Cell Handover)...... 189
Figure 206 External Handover Flow .................................... 190
Figure 210 Immediate Assignment Occupation Failure Flow
1 ................................................................... 194
Figure 211 Internal Handover Flow (Intra-Cell Handover, TC
Is Internal) .................................................... 195
Figure 212 Internal Handover Flow (Intra-Cell Handover,
Channel Type Changed, TC Is External) .............. 195
Figure 213 External Handover Flow (TC Is Internal) ............. 196
Figure 214 External Handover Flow (TC Is External) ............. 196
3195
Figure 215 Intra-BSC Handover Occupation Failure Flow ...... 197

Figure 216 Inter-BSC Handover Occupation Failure Flow ....... 197
Figure 218 Immediate Assignment Allocation Failure Flow 2 .. 199
Figure 219 Internal Handover Failure Flow 1 (Intra-Cell
Handover, TC Is Internal).................................. 200
Figure 220 External Handover Failure Flow 2 (TC Is Internal)
..................................................................... 200
Figure 222 Immediate Assignment Failure Flow 3................. 202
Figure 223 Common Assignment Flow (TC Is Internal) ......... 203
Figure 224 Common Assignment Flow (TC Is External) ........ 203
Figure 225 Common Assignment Failure Flow 1 (TC Is
Internal) ........................................................ 204
Is Internal) .................................................... 206
Internal) ....................................................... 211
Internal) ....................................................... 214
Internal) ........................................................ 217
Internal) ........................................................ 219
3196
Figures

Is Internal) .................................................... 221
Internal) ....................................................... 226
Internal) ........................................................ 228
Figure 259 Immediate Assignment Occupation Failure Flow
1 ................................................................... 230
Is Internal) .................................................... 231
Internal) ........................................................ 236
Is Internal) .................................................... 238
3197

Internal) ........................................................ 243
Is Internal) .................................................... 245
Figure 284 Idle-State MO Short Message Flow .................... 249
Figure 285 Idle-State MT Short Message Flow ..................... 251
Figure 286 Call Drop due to T3107 Timeout During Intra-Cell
Handover ....................................................... 252
Figure 287 Call Drop due to T3103 Timeout During Inter-Cell
Handover ....................................................... 253
Figure 288 Handover Decision ........................................... 265
Figure 299 BSC-Controlled Inter-Cell Outgoing Handover
Execution ....................................................... 272
Success.......................................................... 273
Figure 301 MSC-Controlled Outgoing Handover Execution ..... 274
Figure 302 MSC-Controlled Outgoing Handover Success........ 275
Figure 303 BSC-Controlled Inter-Cell Incoming Handover
Execution ....................................................... 275
Success.......................................................... 276
Figure 305 MSC-Controlled Incoming Handover Execution ..... 277
Figure 306 Forced Release Execution.................................. 278
3198
Figures
Figure 307 Queuing Execution ........................................... 278

Figure 308 MSC-Controlled Incoming Handover Success ....... 279
Execution ....................................................... 280
Success.......................................................... 281
Execution ....................................................... 282
Success.......................................................... 283
Execution ....................................................... 284
Success.......................................................... 285
Execution ....................................................... 286
Success.......................................................... 286
Execution ....................................................... 287
Success.......................................................... 288
Execution ....................................................... 289
Success.......................................................... 290
Execution ....................................................... 291
Success.......................................................... 292
Execution ....................................................... 293
Success.......................................................... 294
Figure 325 Intra-Cell Handover Execution ........................... 295
Figure 326 Intra-Cell Handover Success.............................. 295
Figure 327 Reporting Measurement Data ............................ 296
3199

Figure 338 Idle-State MT Short Message Flow ..................... 305
Figure 344 Common Assignment Flow 3 (TC Is Internal) ....... 311
Internal) ....................................................... 314
Handover ....................................................... 323
Handover ....................................................... 323
Figure 359 Call Drop due to Inter-BSC Handover Failure ....... 324
Figure 360 Measurement Point of Number of Abis Interface
Messages Sent to BTS from BSC ........................ 324
3200
Figures

..................................................................... 328
Figure 367 External Handover Failure Flow 3 (TC Is Internal) .. 329
..................................................................... 333
..................................................................... 337
3201

Is Internal) .................................................... 341
..................................................................... 344
Is Internal) .................................................... 348
Figure 404 Immediate Assignment Allocation Failure Flow 2 .. 350
Internal) ....................................................... 351
..................................................................... 356
3202
Figures

Internal) ....................................................... 360
..................................................................... 365
Internal) ....................................................... 369
..................................................................... 374
3203

Internal) ........................................................ 380
Is Internal) .................................................... 381
Internal) ....................................................... 383
..................................................................... 387
Internal) ........................................................ 392
Is Internal) .................................................... 393
Figure 467 Forced Release Execution ................................. 395
Figure 468 Queuing Execution .......................................... 396
3204
Figures
Figure 469 Forced Handover Execution ............................... 397

Figure 470 Forced Handover Execution ............................... 398
Handover ....................................................... 400
Handover ....................................................... 401
Handover ....................................................... 402
Handover ....................................................... 403
Handover ....................................................... 404
Handover ....................................................... 405
Handover ....................................................... 406
Handover ....................................................... 407
Handover ....................................................... 408
Handover ....................................................... 409
3205

Figure 501 MSC-Controlled Outgoing Handover Execution ..... 420
Figure 502 MSC-Controlled Outgoing Handover Success........ 420
Figure 503 MSC-Controlled Incoming Handover Execution ..... 421
Figure 508 Call Drops Caused by Radio Link Failure During
Assignment..................................................... 426
Figure 509 Call Drops Caused by Radio Link Failure During
Assignment..................................................... 427
Figure 510 - Measurement Point Of Number Of Resumption
For GPRS DL TBF In Delay State ........................ 435
Figure 511 Number Of Request Failures For Establishing
GPRS On PACCH (No Response From Control
Plane) ............................................................ 436
Figure 512 Failures For Establishing DL GPRS TBF On
CCCH/PCCCH (1) ............................................. 437
CCCH/PCCCH (2) ............................................. 437
Figure 514 Normal Establishment Of DL GPRS TBF On
CCCH/PCCCH .................................................. 439
Figure 515 LLC Frame Transmits GTTP Message In DTM
Mode ............................................................. 439
Figure 516 DTM Assignment In DTM Mode .......................... 440
Figure 517 Measurement Point Of Number Of Times For
Establishing GPRS DL TBF With Polling Failed On
CCCH/PCCCH .................................................. 441
Establishing GPRS DL TBF With Polling Failed On
CCCH/PCCCH .................................................. 441
CCCH/PCCCH .................................................. 443
Mode ............................................................. 443
CCCH/PCCCH .................................................. 445
3206
Figures

Mode ............................................................. 445
Figure 525 Normal Release Of DL TBF ................................ 446
Mode ............................................................. 447
Figure 527 - Measurement Point Of Number Of Resumption
For GPRS DL TBF In Delay State ........................ 448
Figure 528 Number Of Request Failures For Establishing
GPRS On PACCH (No Response From Control
Plane) ............................................................ 449
CCCH/PCCCH (1) ............................................. 450
CCCH/PCCCH (2) ............................................. 450
CCCH/PCCCH .................................................. 452
Mode ............................................................. 452
Establishing EGPRS DL TBF With Polling Failed On
CCCH/PCCCH .................................................. 454
Establishing EGPRS DL TBF With Polling Failed On
CCCH/PCCCH .................................................. 454
CCCH/PCCCH .................................................. 456
Mode ............................................................. 456
CCCH/PCCCH .................................................. 458
Mode ............................................................. 458
Mode ............................................................. 460
3207
Figure 544 Measurement Of Cumulated Overall DL

Connecting Time ............................................. 461
Connecting Time ............................................. 461
Connecting Time ............................................. 462
Mode ............................................................. 464
Mode ............................................................. 465
Figure 551 Measurement Point On Receiving New Data Block
In GPRS Extended UL State............................... 469
Figure 552 Measurement Point On Receiving Resource
Reassignment For GPRS UL TBF In Delayed UL
State ............................................................. 469
Figure 553 Measurement Point On Number Of Request
Failures Caused By Timeout For Establishing
GPRS On PACCH GPRS ..................................... 470
Figure 554 Measurement Point On Number Of Establishment
Failures Of GPRS UL TBF Caused By Competition
Solution Failure ............................................... 472
Failures Of GPRS UL TBF Caused By Not Receiving
Resource Request ............................................ 473
Figure 556 Measurement Point On Number Of SuccessfuL
GPRS UL TBF Establishment On CCCH/PCCCH
(I) ................................................................. 475
Figure 557 Measurement Point On Number Of Successful
GPRS UL TBF Establishment On CCCH/PCCCH
(II) ................................................................ 475
Figure 558 Measurement Point On Number Of Normal GPRS
UL TBF Release ............................................... 476
Figure 559 Measurement Point On Number Of Resumptions
For EGPRS UL TBF In Extended UL State ............. 477
Figure 560 Measurement Point On Number Of Resource
Reassignments For EGPRS UL TBF In Delayed UL
State ............................................................. 478
3208
Figures
Figure 561 Measurement Point On Number Of Request

Failures Caused By Timeout For Establishing
EGPRS On PACCH ............................................ 479
Failures Of EGPRS UL TBF Caused By Competition
Solving Failed.................................................. 480
Failures Of EGPRS UL TBF Caused By Not
Receiving Resource Request .............................. 481
EGPRS UL TBF Establishment On CCCH/PCCCH
(I) ................................................................. 483
EGPRS UL TBF Establishment On CCCH/PCCCH
(II) ................................................................ 484
Figure 566 Measurement Point On Number Of Normal EGPRS
UL TBF Release ............................................... 485
Signaling UL TBF Release.................................. 488
Signaling UL TBF Release.................................. 489
Figure 569 Measurement Point Of Size Of IP Packets Sent To
BIPB .............................................................. 492
Figure 570 Measurement Point Of Number Of IP Packets Sent
To BIPB .......................................................... 493
Figure 571 Measurement Point Of Size Of IP Packets Received
From BIPB ...................................................... 493
Figure 572 Measurement Point Of Number Of IP Packets
Received From BIPB......................................... 494
Figure 573 Measurement Point Of Size Of IP Packets Sent To
GIPB .............................................................. 495
Figure 574 Measurement Point Of Number Of IP Packets Sent
To GIPB.......................................................... 495
Figure 575 Measurement Point Of Size Of IP Packets Received
From GIPB...................................................... 496
Figure 576 Measurement Point Of Number Of IP Packets
Received From GIPB......................................... 497
Figure 577 Measurement Point Of Number Of Kbytes Carried
By DL EGPRS LLC Frame................................... 497
3209

By DL Signaling LLC Frame ............................... 498
By UL LLC Frame ............................................. 499
Figure 580 Measurement Point Of Number Of UL LLC
Frames........................................................... 499
Figure 581 Measurement Point Of Number Of Bytes Of DL
GPRS TBF LLC Frame ....................................... 500
EGPRS TBF LLC Frame...................................... 501
Signaling TBF LLC Frame .................................. 502
Figure 584 Measurement Point Of Number Of Bytes Of UL
GPRS TBF LLC Frame ....................................... 502
EGPRS TBF LLC Frame...................................... 503
Signaling TBF LLC Frame .................................. 504
Figure 587 Measurement Point Of Total Number Of
Completion Of GPRS UL Data TBF ...................... 505
Completion Of GPRS DL Data TBF ...................... 506
Completion Of EGPRS UL Data TBF..................... 507
Completion Of EGPRS DL Data TBF .................... 508
By DL GPRS LLC Frame .................................... 509
Figure 592 Measurement Point Of DL Pending RLC Block ...... 512
Figure 593 Measurement Point Of DL Retransmitted RLC
Block ............................................................. 512
Figure 594 Measurement Point Of DL First-Transmitted RLC
Block ............................................................. 513
Figure 595 Measurement Point Of UL Pending RLC Block ....... 513
Figure 596 Measurement Point Of UL Retransmitted RLC
Block ............................................................. 513
Figure 597 Measurement Point Of UL First-Transmitted RLC
Block ............................................................. 514
Figure 598 Measurement Point Of Number Of UL RLC Blocks
Lost ............................................................... 515
3210
Figures

Lost ............................................................... 515
Lost ............................................................... 516
Figure 601 Measurement Point Of Number Of Standstill Of
GPRS UL TBF Receiving Window ........................ 517
GPRS DL TBF Sending Window .......................... 518
GPRS DL TBF Sending Window .......................... 519
Figure 604 Measurement Point Of Number Of Increment Of
DL Coding Mode (EDGE RLC Block) .................... 520
DL Coding Mode (GPRS RLC Block) .................... 520
DL Coding Mode (GPRS RLC Block) .................... 521
UL Coding Mode .............................................. 522
UL Coding Mode .............................................. 523
DL Coding Mode (GPRS RLC Block)..................... 524
UL Coding Mode .............................................. 525
DL Coding Mode (GPRS RLC Block)..................... 526
UL Coding Mode .............................................. 527
Figure 616 Measurement Point of Downlink GPRS RLC Block
Coding Mode Adjustment .................................. 528
Figure 617 Measurement Point of Uplink RLC Block Coding
Mode Adjustment ............................................ 529
Figure 618 Measurement Point of Downlink EDGE RLC Block
Coding Mode Adjustment .................................. 530
3211
Figure 619 Measurement Point of Uplink RLC Block Coding

Mode Adjustment ............................................ 531
Figure 620 Sending Instant Assignment Message By AGCH
Channel (1) .................................................... 540
Channel (2) .................................................... 541
Figure 622 Sending PS Paging By PCH Channel.................... 541
Figure 623 SENDING CS PAGING BY PCH CHANNEL.............. 542
Channel ......................................................... 543
Figure 625 Sending Assignment Message By PAGCH Channel
(1) ................................................................ 544
Figure 626 Sending Assignment Message By PAGCH Channel
(2) ................................................................ 544
Figure 627 Sending PS Paging By PCH ChanneL ................... 545
Figure 628 Sending CS Paging By PCH Channel ................... 545
Figure 629 Sending Assignment Message By PAGCH
Channel ......................................................... 546
Figure 630 Number Of Packet Channel Requests On PRACH ... 547
Figure 631 Measurement Point Of General Assignment
Executions ...................................................... 562
Figure 632 Measurement Point Of Assignments For Forced
Release Attempts............................................. 563
Figure 633 Measurement point of assignment executions for
voice channel due to forced release.................... 564
Figure 634 Measurement point of handover for forced release
attempts ........................................................ 565
Figure 635 Measurement Point Of Handover Executions For
Voice Channel Due To Forced Release ................. 566
Figure 636 Measurement Point Of Assignments For Queuing
Attempts ........................................................ 567
Figure 637 Measurement Point Of Assignments for Execution
for Voice Channel due to Queuing ...................... 568
Figure 638 Measurement Point Of Assignments For Execution
For Voice Channel Due To Queuing ..................... 569
Figure 640 Measurement Point of Assignments for Directed
Retry Attempts................................................ 571
3212
Figures
Figure 641 Measurement Point of Assignments for Execution

for Voice Channel Due to Directed Retry ............. 572
Figure 642 Measurement Point Of General Assignment
Executions ...................................................... 573
Figure 643 Measurement Point Of Assignments For Forced
Figure 644 Measurement Point of Assignment Executions for
Voice Channel due to Forced Release .................. 575
Figure 645 Measurement Point of Handover for Forced
Attempts ........................................................ 578
Retry Attempts................................................ 582
for Voice Channel due to Directed Retry .............. 583
Retry Attempts................................................ 584
Retry Attempts................................................ 586
Retry Attempts................................................ 588
Retry Attempts................................................ 590
3213
Figure 661 Measurement Point of Assignment Failure due to

Circuit Obstruction on A-Interface ...................... 592
Figure 665 Measurement Point Of Number Of Assignment
Attempts Due To Forced Release (Emergency
Service) ......................................................... 596
Service) ......................................................... 597
Attempts ........................................................ 600
Figure 670 Measurement Point Of Assignments For
Execution For Voice Channel Due To Queuing....... 601
Figure 671 Measurement Point Of Number Of Forced
Handover Target Not Found (Assignment Forced
Handover) ...................................................... 602
Figure 673 Measurement Point Of Number Of Receiving
Forced Handover Failure Message From Low
Priority User During Forced Handover ................. 604
Figure 674 Measurement Point Of Number Of Receiving
Forced Handover Failure Message From Low
Priority User During Forced Handover ................. 605
Figure 675 Measurement Point Of Number Of Timeout For
Wait Resource (Assignment Forced Handover) ..... 606
Figure 676 Measurement Point Of Number Of Forced Release
Target Not Found (Assignment Forced Release).... 607
Figure 677 Measurement Point Of Number Of Timeout For
Wait Resource (Assignment Forced Release ......... 608
3214
Figures

Service) ......................................................... 610
Figure 680 Measurement Point of the Count of Assignment
Using FULL IP A-Interface ................................. 611
Using PCM over IP A-Interface........................... 612
Using PCM over TDM A-Interface ...................... 613
Failure Caused by "Requested Codec Type or
Codec Configuration not supported" ................... 614
Failure Caused by "Requested Codec Type or
Codec Configuration unavailable" ....................... 615
Failure Caused by "Requested A-Interface Type
not supported" ................................................ 616
Failure Caused by "Requested A-Interface Type
unavailable".................................................... 617
Failure Caused by "Call Identifier already
allocated" ....................................................... 618
Failure Caused by "Requested Redundancy Level
not supported" ................................................ 619
Failure Caused by "Call Access Control" .............. 620
Figure 690 Measurement Point of Number of Directed Retries
due to Radio Causes ........................................ 622
Figure 691 Number of Assignment Executions due to Directed
Retry ............................................................. 623
Figure 692 Measurement Point of Number of Directed Retries
due to Radio Causes ........................................ 624
Retry ............................................................. 625
Figure 694 Directed Retry Judgment .................................. 630
3215

Figure 707 Ho_Enquiry Handover....................................... 640
Figure 708 Traffic Handover .............................................. 641
Figure 713 Forced Handover Judgment ............................... 645
Figure 720 HO_Enquiry Handover ...................................... 651
Figure 732 HO_Enquiry Handover ...................................... 661
3216
Figures

Figure 743 CS Channel Transfer Handover .......................... 671
Figure 750 Handover Attempt due to Reducing Band
Resources of IPAbis.......................................... 681
Figure 751 Traffic-Migration Handover due to
MASTERPWR_ALM from TRX.............................. 682
Figure 752 Traffic-Migration Handover due to
MASTERPWR_ALM from TRX.............................. 682
Retry ............................................................. 683
Figure 757 Call Drop Due To A-Interface Failure In Immediate
Assignment Process ......................................... 691
Figure 758 Call Drop Due To Radio Link Failure In Immediate
Figure 759 Call Drop Due To Lapd Link Failure In Immediate
Figure 760 Call Drop Due To OMC-R Forced Release In
Immediate Assignment Process ......................... 694
Figure 761 Call Drop Due To Forced Release By Other Calls
In Immediate Assignment Process ..................... 695
Figure 762 Measurement Point of TWaitMSAccess Overtime ... 696
3217

Figure 765 Call Drop Due To LAPD Link Failure In Immediate
Figure 769 Call Drop Due To A-Interface Failure In
Figure 770 Call Drop Due To LAPD Link Failure In Assignment
Process .......................................................... 704
In Assignment Process ..................................... 706
Figure 775 Call Drop Due To Radio Link Failure In Assignment
Process .......................................................... 710
Figure 776 Call Drop Due To Lapd Link Failure In Assignment
Process .......................................................... 711
Figure 782 Call Drop Due To LAPD Link Failure In Immediate
3218
Figures

Process .......................................................... 722
Process .......................................................... 728
Process .......................................................... 730
Figure 794 Call Drop Due To Omc-R Forced Release In
Figure 797 Call Drop Due To Sccp Failure In Immediate
Figure 798 Call Drop Due To Sccp Failure In Immediate
Figure 799 Call Drop Due To SCCP Failure In Immediate
Figure 800 Call Drop Due To Inter-BSC Handover Failure....... 738
Figure 803 Measurement Point Of Number Of SDCCH Drops
Due To eMLPP Forced Handover ......................... 743
3219

Process .......................................................... 756
Process .......................................................... 757
Process .......................................................... 758
Process .......................................................... 759
Process .......................................................... 760
Process .......................................................... 761
Process .......................................................... 762
Process .......................................................... 763
Process .......................................................... 764
Process .......................................................... 765
Process .......................................................... 766
3220
Figures
Figure 828 Measurement Point of the Count of Drop Call

Caused by "IP Resource Reset" .......................... 767
Figure 829 Call Drop during Immediate Assignment due to
BTS Fault........................................................ 776
Figure 830 Call Drop during Immediate Assignment due to
BTS Fault........................................................ 777
Figure 831 Call Drop during Assignment due to BTS Fault ..... 778
Attempt ......................................................... 813
Figure 854 MSC-Controlled Outgoing Handover Attempts ...... 814
Figure 855 MSC-Controlled Outgoing Handover Request
Failures Due To Unclear Factors ......................... 815
Figure 856 MSC-Controlled Handover Request Failures ......... 816
Attempts ........................................................ 818
Figure 860 Forced Release Attempts................................... 819
Figure 861 Queuing Attempts............................................ 820
3221
Figure 862 Forced-Handover Attempts................................ 821

Figure 863 Execution In Queuing ....................................... 822
Figure 864 Incoming Handover Queuing Expires .................. 823
Figure 865 Instance Release During Queuing....................... 823
Figure 871 MSC-Controlled Incoming Handover Attempts...... 828
Figure 872 Unsuccessful MSC-Controlled External Incoming
Handover ....................................................... 829
Handover ....................................................... 830
Handover ....................................................... 831
Handover ....................................................... 831
Attempts ........................................................ 841
Figure 888 Successful BSC-Controlled Inter-Cell Incoming
Handover ....................................................... 842
Attempt ......................................................... 843
Figure 890 Successful BSC-Controlled Inter-Cell Outgoing
Handover ....................................................... 844
Attempts ........................................................ 845
3222
Figures

Handover ....................................................... 846
Attempt ......................................................... 847
Handover ....................................................... 848
Attempts ........................................................ 849
Attempt ......................................................... 850
Execution Flow ................................................ 851
Handover ....................................................... 852
Attempts ........................................................ 853
Attempt ......................................................... 854
Execution Flow ................................................ 855
Handover ....................................................... 856
Attempts ........................................................ 857
Handover ....................................................... 858
Attempt ......................................................... 859
Handover ....................................................... 860
Attempts ........................................................ 861
Handover ....................................................... 862
Attempt ......................................................... 863
Handover ....................................................... 864
Attempts ........................................................ 865
3223

Attempt ......................................................... 866
Execution Flow ................................................ 867
Handover ....................................................... 868
Attempts ........................................................ 869
Attempt ......................................................... 870
Execution Flow ................................................ 871
Handover ....................................................... 872
Attempts ........................................................ 873
Attempt ......................................................... 874
Execution Flow ................................................ 875
Handover ....................................................... 876
Attempts ........................................................ 877
Attempt ......................................................... 878
Execution Flow ................................................ 879
Handover ....................................................... 880
Attempts ........................................................ 881
Attempt ......................................................... 882
Execution Flow ................................................ 883
Handover ....................................................... 884
Attempts ........................................................ 885
3224
Figures

Attempt ......................................................... 886
Execution Flow ................................................ 887
Handover ....................................................... 888
Figure 935 Intra-Cell Handover Attempt ............................. 888
Figure 937 Successful Intra-Cell Handover .......................... 890
Figure 945 MSC-Controlled Outgoing Handover.................... 896
Figure 946 Successful MSC-Controlled Outgoing Handover .... 897
Figure 948 MSC-Controlled Incoming Handover ................... 898
Figure 950 Intra-Cell Incoming Handover Attempt................ 900
Figure 951 Intra-Cell Incoming Handover............................ 901
Attempts ........................................................ 908
Attempts ........................................................ 909
Figure 962 BSC-Controlled Inter-Cell Incoming Handover...... 910
Attempts ........................................................ 911
3225

Attempts ........................................................ 913
Attempts ........................................................ 914
Attempts ........................................................ 916
Figure 974 BSC-Controlled Forced Release On Incoming
Handover ....................................................... 922
Figure 976 BSC-Controlled Forced Handover On Incoming
Handover ....................................................... 924
Figure 978 BSC-Controlled Queue On Incoming Handover ..... 926
Figure 979 MSC-Controlled Forced Release Attempt On
Incoming Handover.......................................... 927
Figure 980 MSC-Controlled Forced Release On Incoming
Handover ....................................................... 928
Figure 981 MSC-Controlled Forced Handover Attempt On
Incoming Handover.......................................... 929
Figure 982 MSC-Controlled Forced Handover On Incoming
Handover ....................................................... 930
Figure 983 MSC-Controlled Queue Attempt On Incoming
Handover ....................................................... 931
Figure 984 MSC-Controlled Queue On Incoming Handover .... 932
Figure 985 Forced Handover Target Not Found
(BSC-Controlled Inter-Cell Handover Due
To Forced Handover) ........................................ 933
Figure 986 Send Forced Handover Request To Lower Pri
User (BSC-Controlled Inter-Cell Handover Due To
Forced Handover) ............................................ 934
Figure 987 Recv Failure From Lower Pri User Request
Resource For Forced Handover (BSC-Controlled
Inter-Cell Handover Due To Forced Handover) ..... 935
3226
Figures
Figure 988 Recv Failure From Lower Pri User Request

Resource For Forced Handover (BSC-Controlled
Inter-Cell Handover Due To Forced Handover) ..... 937
Figure 989 - High Pri User Time Out For Wait Resource
(BSC-Controlled Inter-Cell Handover Due To
Forced Handover) ............................................ 938
Figure 990 Forced Release Target Not Found (BSC-Controlled
Inter-Cell Handover Due To Forced Release) ........ 939
Figure 991 High Pri User Time Out For Wait Resource
(BSC-Controlled Inter-Cell Handover Due To
Forced Release)............................................... 940
Figure 992 MSC-Controlled Inter-PLMN Handover Flow ......... 949
Figure 993 MSC-Controlled Inter-PLMN Outgoing Handover
Execution ....................................................... 951
Figure 994 MSC-Controlled Inter-PLMN Outgoing Handover
Execution and No Abnormal Release................... 952
Figure 995 MSC-Controlled Inter-PLMN Incoming Handover
Flow .............................................................. 956
Figure 996 A-Interface Inter-PLMN Incoming Handover
Failure ........................................................... 957
Figure 997 Inter-MSC Handover ........................................ 961
Figure 998 Handover Success due to CS Service Migration .... 964
Figure 999 Intra-cell Handover Flow................................... 965
Figure 1000 Intra-cell Handover Flow ................................. 965
Figure 1011 Intra-BSC Inter-cell Handover Flow .................. 973
3227

Figure 1023 Inter-BSC Inter-cell Handover Flow .................. 985
Attempt ......................................................... 996
Figure 1036 MSC-Controlled Outgoing Handover Attempts .... 997
Handover ....................................................... 998
Figure 1038 Successful MSC-Controlled Outgoing Handover .. 998
Attempts ........................................................ 999
Figure 1040 MSC-Controlled Incoming Handover Attempts .... 999
Handover ..................................................... 1000
Figure 1042 MSC-Controlled Incoming Handover Success.... 1000
Attempts ...................................................... 1001
Figure 1044 MSC-Controlled Incoming Handover Attempts .. 1002
Attempts ...................................................... 1003
Handover ..................................................... 1004
Figure 1048 Successful MSC-Controlled Outgoing
Handover ..................................................... 1004
3228
Figures

Handover ..................................................... 1005
Handover ..................................................... 1006
Attempts ...................................................... 1007
Attempts ...................................................... 1008
Handover ..................................................... 1009
Handover ..................................................... 1010
Handover ..................................................... 1011
Handover ..................................................... 1011
Attempts ...................................................... 1012
Handover ..................................................... 1013
Handover ..................................................... 1014
Attempts ...................................................... 1015
Handover ..................................................... 1016
Handover ..................................................... 1016
Attempt ....................................................... 1017
Figure 1068 MSC-Controlled Outgoing Handover Attempts .. 1018
Figure 1069 Handover Flow............................................. 1019
Attempt ....................................................... 1021
Figure 1071 MSC-Controlled Inter-Cell Outgoing Handover
Attempt ....................................................... 1021
3229
Figure 1072 Number of BSC-Controlled Outgoing Handover

Successes..................................................... 1022
Figure 1073 Number of MSC-Controlled Outgoing Handover
Successes..................................................... 1022
Figure 1074 Radio Access Process.................................... 1027
Figure 1082 - BSC Receives the Measurement Report
Submitted BY BTS ......................................... 1082
Submitted BY BTS ......................................... 1082
Submitted BY BTS ......................................... 1083
Submitted BY BTS ......................................... 1084
Submitted BY BTS ......................................... 1084
Submitted BY BTS ......................................... 1085
Submitted BY BTS ......................................... 1086
Figure 1089 BSC Receives the Measurement Report
Submitted by BTS.......................................... 1086
Submitted BY BTS ......................................... 1087
Submitted BY BTS ......................................... 1087
Submitted BY BTS ......................................... 1088
Submitted BY BTS ......................................... 1089
Submitted By BTS.......................................... 1089
Submitted BY BTS ......................................... 1090
3230
Figures

Submitted BY BTS ......................................... 1091
Submitted BY BTS ......................................... 1091
Submitted BY BTS ......................................... 1092
Submitted BY BTS ......................................... 1093
Submitted BY BTS ......................................... 1093
Submitted BY BTS ......................................... 1094
Submitted BY BTS ......................................... 1095
Submitted BY BTS ......................................... 1095
Submitted BY BTS ......................................... 1096
Submitted by BTS.......................................... 1096
Submitted BY BTS ......................................... 1097
Submitted BY BTS ......................................... 1098
Submitted BY BTS ......................................... 1098
Submitted BY BTS ......................................... 1099
Submitted By BTS.......................................... 1100
Submitted BY BTS ......................................... 1100
Submitted BY BTS ......................................... 1101
Submitted BY BTS ......................................... 1102
Figure 1114 - Intra-Cell Handover Attempt ....................... 1109
Figure 1115 - Intra-Cell Incoming Handover...................... 1110
Figure 1116 - Successful Intra-Cell Handover .................... 1111
3231

Figure 1124 - Inter-Cell Handover Execution ..................... 1118
Figure 1126 - Handover Decision ..................................... 1120
Figure 1154 MS Measurement Report ............................... 1172
Figure 1156 - MS Measurement Report ............................. 1173
3232
Figures

Figure 1187 - Flow of MO Short Messages during
Conversation................................................. 1195
Conversation................................................. 1196
Figure 1189 - Flow of MT Short Message during
Conversation................................................. 1198
Conversation................................................. 1199
Conversation................................................. 1201
3233

Conversation................................................. 1202
Figure 1193 - Flow of MT Short Message in Idle Status ....... 1204
Figure 1194 - Flow of MO Short Message in Idle Status....... 1205
Figure 1195 - Flow of MT Short Message in Idle Status ....... 1206
Figure 1196 - Flow of MO Short Message in Idle Status....... 1207
Conversation................................................. 1210
Conversation................................................. 1211
Figure 1199 - Flow Of MT Short Message During
Conversation................................................. 1213
Figure 1200 - Flow Of MO Short Messages During
Conversation................................................. 1213
Conversation................................................. 1214
Conversation................................................. 1215
Figure 1203 - Measurement Point of Packet Resource Request
and Packet Access Reject ................................ 1218
Figure 1204 - Measurement Point of Packet Resource Request
and Packet Access Reject ................................ 1219
Figure 1205 - Measurement of Packet UL Assignment
Message ....................................................... 1220
Figure 1206 - Measurement Point Of Additional MS Access
Capabilities Message ...................................... 1221
Figure 1207 - DL Sent on PACCH in Packet Transmission
Mode ........................................................... 1222
Mode ........................................................... 1223
Figure 1209 - DL Sent on PACCH IN Packet Transmission
Mode ........................................................... 1224
Mode ........................................................... 1225
Figure 1211 - Signaling Transmission on PACCH................. 1226
Figure 1212 - Signaling Transmission on PACCH................. 1227
Figure 1213 - Measurement Point of Packet-Cell-ChangeRelated Counter (I)........................................ 1228
Figure 1214 - Measurement Point of Packet-Cell-ChangeRelated Counter (II)....................................... 1228
3234
Figures
Figure 1215 - Measurement Point of Packet Cell Change

Order and Packet Cell Change Failure ............... 1229
Figure 1216 - Measurement Point of Packet-Cell-ChangeRelated Counter (I)........................................ 1230
Figure 1217 - Measurement Point of Packet Cell Change
Order and Packet Cell Change Failure ............... 1231
Figure 1218 - Measurement Point of Packet Mobile Status
Message on PACCH ........................................ 1232
Figure 1219 - Measurement Point of Packet-Cell-ChangeRelated Counter ............................................ 1233
Figure 1220 - Measurement Point of DL TBF Establishes
Execution Polling ........................................... 1234
Figure 1221 - Measurement Point of Packet Power
Control/Timing Advance Message Sent on
PACCH ......................................................... 1235
Figure 1222 - Measurement Point of Packet-Service-CellData-Related Counter..................................... 1236
Figure 1225 - Flow of Establishing UL on PACCH under DL
Transmission Status ....................................... 1239
Figure 1226 - Flow of Establishing DL on PACCH under UL
Transmission Status ....................................... 1239
Figure 1227 - Measurement Point of BSC Issuing Packet
Paging Request Message................................. 1240
Figure 1228 - Measurement Point of BSC Issuing Packet
System Message............................................ 1241
Figure 1229 - DL Request ............................................... 1245
Figure 1230 - DL Assignment Request .............................. 1246
Figure 1231 - Database Application Failure due to Abis
Congestion (I)............................................... 1247
Figure 1232 - Database Application Failure due to Abis
Congestion (II) ............................................. 1248
Figure 1233 - Database Application Failure Due To RR
Congestion (I)............................................... 1249
Congestion (II) ............................................. 1249
3235
Figure 1235 - Database Application Failure due to UPPB-DSP

Channel Congestion (I)................................... 1250
Channel Congestion (II) ................................. 1250
Figure 1237 - Successful Resource Application................... 1251
Figure 1239 - PDCH Activation Failure .............................. 1253
Figure 1240 - Connection Failed due to BTS Connection
Failure ......................................................... 1253
Figure 1241 - Connection Failed Due To BIU Connection
Failure ......................................................... 1254
Figure 1242 - DL GPRS TBF Establishes Channel Activation
And Access Success ....................................... 1255
Figure 1243 - Immediate Assignment Sending Failure ........ 1256
Figure 1244 - Successful Immediate Assignment Sending ... 1257
Figure 1245 - Resource Application Failure Due To Abis
Congestion (Assigned By UL)........................... 1259
Figure 1246 - Resource Application Failure Due To RR
Figure 1247 - Resource Application Failure Due To UPPB-DSP
Channel Congestion (Assigned By UL) .............. 1261
Figure 1248 Successful Resource Application (Assigned By
UL) .............................................................. 1262
Figure 1249 - Successful Resource Application (Assigned By
UL) .............................................................. 1263
Figure 1251 - Connection Failure Due To BTS Connection
Failure ......................................................... 1265
Failure ......................................................... 1266
Figure 1253 - Successful Activation And Connection ........... 1267
Congestion (Resource Adjustment) .................. 1268
Channel Congestion (Resource Adjustment) ...... 1270
Figure 1257 Successful Resource Application (Resource
Adjustment) ................................................. 1271
3236
Figures
Figure 1258 - Successful Resource Application (Resource

Adjustment) ................................................. 1272
Figure 1260 - Connection Failed Due To BTS Connection
Failure ......................................................... 1274
Failure ......................................................... 1275
Figure 1263 - Release Request Due To Flush LL ................. 1277
Figure 1264 - Release Request Due To Suspend Request..... 1278
Figure 1265 - Release Request Due To PDCH REL............... 1279
Figure 1266 - Release Request Due To Normal Release
Request By MAC ............................................ 1279
Figure 1267 - Release Request Due To Abnormal Release
Request By MAC ............................................ 1280
Figure 1268 - Release Request Due To NSVC Unavailability .. 1281
Figure 1269 - Release Request Due To BVC Unavailability.... 1281
Figure 1270 - Release Request Due To Other Reasons ........ 1282
Figure 1271 - DL GPRS Resource Request Success ............. 1283
Figure 1274 - Resource Assignment Success ..................... 1285
Figure 1275 - Release DL GPRS TBF ................................. 1285
Figure 1276 - DL Request ............................................... 1290
Figure 1277 - DL Assignment Request .............................. 1290
Figure 1278 - Database Application Failure Due To Abis
Congestion (I)............................................... 1292
Congestion (II) ............................................. 1292
Congestion (I)............................................... 1293
Congestion (II) ............................................. 1293
Channel Congestion (I)................................... 1294
Channel Congestion (II) ................................. 1295
3237

Failure ......................................................... 1298
Failure ......................................................... 1299
Figure 1289 - Immediate Assignment Sending Failure ........ 1299
Congestion (Assigned by UL)........................... 1303
Figure 1295 Successful Resource Application (Assigned By
UL) .............................................................. 1306
Figure 1296 - Successful Resource Application (Assigned By
UL) .............................................................. 1307
Failure ......................................................... 1308
Failure ......................................................... 1309
Adjustment) ................................................. 1315
Adjustment) ................................................. 1316
Failure ......................................................... 1317
Failure ......................................................... 1318
Failure ......................................................... 1319
3238
Figures

Figure 1311 - Release Request Due To Suspend Request..... 1321
Figure 1312 - Release Request Due To PDCH REL............... 1322
Figure 1313 - Release Request due to Normal Release
Request by MAC ............................................ 1323
Figure 1314 - Release Request due to Abnormal Release
Request by MAC ............................................ 1323
Figure 1315 - Release Request due to NVSC Unavailability .. 1324
Figure 1318 Downlink EGPRS Requesting Resource
Successfully .................................................. 1326
Successfully .................................................. 1326
Successfully .................................................. 1327
Figure 1321 Assigning Resource Successfully..................... 1328
Figure 1322 Releasing Downlink EGPRS TBF ...................... 1328
Figure 1323 - Channel Request........................................ 1333
Figure 1324 - Packet Channel Request.............................. 1334
Figure 1325 - Packet Channel Request.............................. 1335
Figure 1326 - Channel Requests on CCCH due to One Phase
Access ......................................................... 1336
Figure 1327 - Packet Channel Requests on CCCH due to One
Phase Access ................................................ 1336
Figure 1328 - Channel Request due to Single Block Packet
Access ......................................................... 1337
Figure 1329 - Channel Request Due To Response Paging ..... 1338
Figure 1330 - Channel Requests due to Cell Update............ 1338
Figure 1331 - Channel Request Due To Mobile Management .. 1339
Figure 1332 - Channel Requests On PCCCH Due To Two
Phase Access ................................................ 1340
Figure 1333 - Packet Channel Requests On PCCCH Due To
Two Phase Access .......................................... 1340
Figure 1334 - Packet Channel Requests On PCCCH Due To
Short Access ................................................. 1341
Figure 1335 - DB Resource Requests Failure Due To Abis
Congestion (CCCH) ........................................ 1342
3239

Congestion (PCCCH) ...................................... 1342
Congestion (DL GPRS TBF Already Established) .. 1342
Figure 1338 - DB Resource Requests Failure Due To RR
Congestion (CCCH) ........................................ 1343
Figure 1341 DB Resource Requests Failure Due To
UPPB-DSP Channel Congestion (CCCH)............. 1345
Figure 1343 - DB Resource Requests Failure Due To
DPPB-DSP Congestion (DL GPRS TBF Already
Established).................................................. 1346
Figure 1344 - DB Resource Request Successes (CCCH) ....... 1347
Figure 1345 - DB Resource Request Successes (PCCCH) ..... 1347
Figure 1346 - Channel Request Successes On CCCH Due To
One Phase Access .......................................... 1348
Figure 1347 - Packet Channel Request Successes On CCCH
Due To One Phase Access ............................... 1348
Figure 1348 - Channel Requests Successes Due To Single
Block Packet Access ....................................... 1349
Figure 1349 - DB Resource Request Successes Due To
Response Paging ........................................... 1350
Figure 1350 - DB Resource Request Successes Due To Cell
Update ......................................................... 1351
Figure 1351 - DB Resource Request Successes Due To Mobile
Management (PCCCH) .................................... 1351
Figure 1352 - DB Resource Request Successes Due To Two
Phase Access (CCCH) ..................................... 1352
Figure 1353 - DB Resource Request Successes On PCCCH
Due To Two Phase Access ............................... 1353
Figure 1354 - DB Resource Request Successes Due To Short
Access (PCCCH) ............................................ 1354
Figure 1355 - DB Resource Request Successes Due To Short
Access (PCCCH) ............................................ 1355
Figure 1356 - UL GPRS TBF Establishment On PCCCH/CCCH .. 1355
3240
Figures

Failure ......................................................... 1357
Failure ......................................................... 1358
Figure 1362 - UL One-Phase-Access Resource Assignment
Successes..................................................... 1361
Figure 1363 - UL Two-Phase-Access Single Block Assignment
Successes..................................................... 1362
Congestion ................................................... 1363
Figure 1365 - Database Application Failure due to RR
Congestion ................................................... 1364
Channel Congestion ....................................... 1365
Figure 1367 Successful Resource Application ..................... 1365
Figure 1369 - PDTCH Activation Failure............................. 1367
Failure ......................................................... 1368
Failure ......................................................... 1369
Congestion .................................................. 1372
Figure 1375 - Resource Application Failure Due To UPPPB-DSP
Figure 1376 Release Request Due To Flush LL.................... 1375
Failure ......................................................... 1377
Figure 1380 - Connection Failed due to BIU Connection
Failure ......................................................... 1378
3241

Congestion (Resource Request) ....................... 1381
Congestion ................................................... 1382
Figure 1384 DB Resource Requests Failure due to UPPB-DSP
Channel Congestion (Resource Request) ........... 1383
Figure 1385 DB Resource Requests Successes (Resource
Request) ...................................................... 1383
Figure 1386 DB Resource Requests Successes (Resource
Request) ...................................................... 1384
Failure ......................................................... 1386
Failure ......................................................... 1387
Figure 1392 - Release Request due to Suspend Request ..... 1390
Figure 1393 - Release Request due to PDCH REL ............... 1391
Figure 1394 - Normal Release Request ............................. 1392
Figure 1395 - Release Request due to Abnormal Release
Request by MAC ............................................ 1392
Figure 1396 - Release Request due to NVSC Unavailability .. 1393
Figure 1399 - UL GPRS Resource Request Success ............. 1395
Figure 1402 - Resource Assignment Success ..................... 1397
Figure 1403 - Release UL GPRS TBF ................................. 1398
Figure 1404 - EGPRS Channel Request ............................. 1403
Figure 1405 - EGPRS Packet Channel Request ................... 1404
Figure 1406 - UL Assignment Request (DL GPRS TBF
ALREADY Established) .................................... 1405
Figure 1407 - EGPRS Channel Requests On CCCH Due To
One Phase Access .......................................... 1405
Figure 1408 - EGPRS Packet Channel Requests On CCCH Due
To One Phase Access...................................... 1406
3242
Figures

Two Phase Access .......................................... 1408
Figure 1410 - EGPRS Packet Channel Requests On PCCCH
Short Access ................................................. 1409
Figure 1412 - EGPRS Packet Channel Requests On PCCCH
Due To Short Access ...................................... 1409
Congestion (EGPRS) ...................................... 1410
Congestion (EGPRS) ...................................... 1411
UPPB-DSP Channel Congestion (EGPRS) ........... 1412
UPPB-DSP Congestion (DL GPRS TBF Already
Established).................................................. 1413
Figure 1419 - DB Resource Request Successes (EGPRS) ..... 1414
UPPB-DSP Channel Congestion (EGPRS) ........... 1415
DPPB-DSP Congestion (DL GPRS TBF Already
Established).................................................. 1415
Figure 1422 - EGPRS DB Resource Request Successes Due
To Two Phase Access (CCCH)........................... 1418
Figure 1423 - DB Resource Request Successes On PCCCH
To Short Access (CCCH).................................. 1419
To Short Access (PCCCH) ................................ 1419
Figure 1426 - DB Resource Request Successes (EGPRS) ..... 1420
Failure ......................................................... 1422
3243

Failure ......................................................... 1423
Figure 1430 - UL EGPRS TBF Establishes Channel Activation
And Access Success ....................................... 1423
Figure 1433 - UL One-Phase-Access Resource Assignment
Successes..................................................... 1427
Figure 1434 - UL Two-Phase-Access Single Block Assignment
Successes..................................................... 1427
Congestion ................................................... 1428
Figure 1436 - Database Application Failure due to RR
Congestion ................................................... 1429
Channel Congestion ....................................... 1430
Figure 1438 Successful Resource Application ..................... 1431
Failure ......................................................... 1434
Failure ......................................................... 1435
Figure 1443 - Resource Application Failure Due To ABIS
Adjustment) ................................................. 1441
Adjustment) ................................................. 1442
Failure ......................................................... 1444
Failure ......................................................... 1445
3244
Figures
Figure 1452 ................................................................. 1446

Congestion (Resource Request) ....................... 1448
Congestion ................................................... 1449
UPPB-DSP Channel Congestion (Resource
Request) ...................................................... 1450
Figure 1456 - DB Resource Requests Successes (Resource
Request) ...................................................... 1451
Figure 1457 - DB Resource Requests Successes (Resource
Request) ...................................................... 1452
Failure ......................................................... 1454
Failure ......................................................... 1455
Figure 1462 Release Request due to Suspend Request........ 1457
Figure 1463 Release Request due to Suspend Request........ 1458
Figure 1464 Release Request due to PDCH REL.................. 1458
Figure 1465 Release Request due to Normal Release Request
by MAC ........................................................ 1459
Figure 1466 Release Request due to Abnormal Release
Request by MAC ............................................ 1460
Figure 1467 - Release Request Due To NSVC Unavailability .. 1460
Figure 1470 - UL EGPRS Resource Request Success ........... 1462
Figure 1474 - Release UL EGPRS TBF ............................... 1465
Figure 1475 PAGING PS Process ...................................... 1468
Figure 1476 - Paging CS Process ..................................... 1469
Figure 1477 - FLUSH-LL Message..................................... 1469
Figure 1479 - BVC Blocking Process ................................. 1471
Figure 1480 - BVC Blocking Process ................................. 1471
3245
Figure 1481 - BVC Unblocking Process.............................. 1472

Figure 1482 - BVC Unblocking Process.............................. 1473
Figure 1483 - BVC Reset Process ..................................... 1473
Figure 1487 - Perform Location Process ............................ 1477
Figure 1492 - Receive FLUSH-LL For UL & DL TBF .............. 1482
Figure 1493 - Receive FLUSH-LL For DL TBF ...................... 1482
Figure 1494 - Receive FLUSH-LL For UL TBF ...................... 1483
Figure 1498 Measurement Point of sum of UL UNITDATA
message handled at BSSGP level ..................... 1493
Figure 1499 Measurement point of sum of DL UNITDATA
Figure 1500 Measurement Point of Number of RA-CAPABILITY
message recevied .......................................... 1494
Figure 1501 PTP Packet Paging Process ............................ 1495
Figure 1502 PTP Circuit Paging Process............................. 1496
Figure 1503 RA-CAPABILITY-UPDATE Process .................... 1496
Figure 1505 RADIO-STATUS Process ................................ 1498
Figure 1506 FLOW-CONTROL-BVC Process ........................ 1500
Figure 1508 FLOW-CONTROL-MS Process.......................... 1502
Figure 1510 FLOW-CONTROL-PFC Process......................... 1504
Figure 1512 STATUS Process ........................................... 1506
Figure 1514 CREATE-BSS-PFC Process.............................. 1510
3246
Figures
Figure 1518 MODIFY-BSS-PFC Process ............................. 1514

Figure 1520 DELETE-BSS-PFC Process .............................. 1516
Figure 1522 Measurement Point of Number of
PS-HANDOVER-REQUIRED messages sent
by BSC......................................................... 1518
PS-HANDOVER-REQUIRED-ACK messages
received by BSC ............................................ 1519
PS-HANDOVER-REQUIRED-NACK messages
received by BSC ............................................ 1520
PS-HANDOVER-REQUEST messages received by
BSC ............................................................. 1521
PS-HANDOVER-REQUEST-ACK messages
sent by BSC.................................................. 1522
PS-HANDOVER-REQUEST-NACK messages
sent by BSC.................................................. 1523
PS-HANDOVER-COMPLETE messages sent
by BSC......................................................... 1524
PS-HANDOVER-CANCEL messages sent by
BSC ............................................................. 1525
PS-HANDOVER-REQUEST messages with
Service UTRAN CCO received by BSC ............... 1526
CREATE-BSS-PFC messages with Service
UTRAN CCO received by BSC........................... 1527
Figure 1532 - Intra-cell Handover .................................... 1531
Figure 1533 - Intra-cell Handover .................................... 1532
Figure 1534 - Inter-Cell Handover Controlled By BSC ......... 1533
3247
Figure 1538 - BSC Receives Radio Link Failure Message

Reported By BTS ........................................... 1537
Figure 1539 - Inter-Cell Handover Failure ......................... 1538
Figure 1540 - Intra-Cell Handover Failure ......................... 1538
Figure 1541 - Channel Activation Measurement Point.......... 1539
Figure 1543 - TCH/F Channel Assignment Measurement
Point ............................................................ 1540
Point ............................................................ 1541
Point ............................................................ 1543
Point ............................................................ 1544
Figure 1549 - Inter-Cell Handover Failure ......................... 1545
Figure 1550 - Intra-Cell Handover Failure ......................... 1546
Figure 1551 - THoOutGo Timeout .................................... 1546
Figure 1554 - Channel Assignment Measurement Point ....... 1548
Figure 1555 - Channel Assignment Measurement Point ....... 1549
Submitted BY BTS ......................................... 1550
Submitted BY BTS ......................................... 1550
Submitted BY BTS ......................................... 1551
Submitted BY BTS ......................................... 1551
Submitted BY BTS ......................................... 1552
Submitted BY BTS ......................................... 1553
Submitted BY BTS ......................................... 1553
Submitted by BTS.......................................... 1554
3248
Figures

Submitted BY BTS ......................................... 1554
Submitted BY BTS ......................................... 1555
Submitted BY BTS ......................................... 1555
Submitted BY BTS ......................................... 1556
Submitted By BTS.......................................... 1556
Submitted BY BTS ......................................... 1557
Submitted BY BTS ......................................... 1558
Submitted BY BTS ......................................... 1558
Figure 1572 BSC Receives the measurement report
submitted by BTS .......................................... 1573
submitted by BTS .......................................... 1573
submitted by BTS .......................................... 1574
submitted by BTS .......................................... 1574
submitted by BTS .......................................... 1575
submitted by BTS .......................................... 1576
submitted by BTS .......................................... 1576
submitted by BTS .......................................... 1577
submitted by BTS .......................................... 1577
submitted by BTS .......................................... 1578
submitted by BTS .......................................... 1579
submitted by BTS .......................................... 1579
3249

submitted by BTS .......................................... 1580
submitted by BTS .......................................... 1581
submitted by BTS .......................................... 1581
submitted by BTS .......................................... 1582
submitted by BTS .......................................... 1582
submitted by BTS .......................................... 1583
submitted by BTS .......................................... 1584
submitted by BTS .......................................... 1584
Figure 1592 Immediate Assignment Failure Measurement
Point ............................................................ 1585
Figure 1593 Assignment Failure Measurement Point ........... 1586
Figure 1594 Handovers Failure Measurement Point............. 1586
Figure 1595 Resource Indication Measurement Point .......... 1587
submitted by BTS .......................................... 1590
submitted by BTS .......................................... 1591
submitted by BTS .......................................... 1591
submitted by BTS .......................................... 1592
submitted by BTS .......................................... 1593
submitted by BTS .......................................... 1593
submitted by BTS .......................................... 1594
3250
Figures

submitted by BTS .......................................... 1594
Figure 1608 Call Drop due to Radio Link Failure during
Immediate Assignment Process ....................... 1595
Assignment Process ....................................... 1596
Figure 1620 BSC Receives Measurement Report from BTS ... 1607
Figure 1621 Measurement Point when Channel Is Activated .. 1607
Figure 1622 The Process Of Immediate Assignment ........... 1610
Figure 1623 The Process Of Internal Handover (like intra-cell
handover) .................................................... 1611
Figure 1624 The Process Of External Handover .................. 1611
handover) .................................................... 1612
Figure 1627 The Process Of Immediate Assignment ........... 1614
handover) .................................................... 1615
3251

handover) .................................................... 1616
handover) .................................................... 1618
handover) .................................................... 1619
handover) .................................................... 1621
Figure 1638 Immediate Assignment Flow.......................... 1623
Figure 1639 Number of successful SDCCH assignments
(MOC).......................................................... 1624
Figure 1640 Number of unsuccessful SDCCH assignments
(MOC).......................................................... 1625
Figure 1641 Number of SDCCH assignment attempts
(MTC) .......................................................... 1626
(MTC) .......................................................... 1627
(MTC) .......................................................... 1628
Figure 1644 Number of SDCCH assignment attempts (call
re-establishment) .......................................... 1629
Figure 1645 Number of successful SDCCH assignments (call
re-establishment) .......................................... 1630
(call re-establishment) ................................... 1632
(emergency call) ........................................... 1633
(emergency call) ........................................... 1634
(emergency call) ........................................... 1635
(LOC)........................................................... 1636
(LOC)........................................................... 1637
3252
Figures

(LOC)........................................................... 1638
Figure 1653 Number of SDCCH assignment attempts (other
cause) ......................................................... 1639
(other cause) ................................................ 1640
(other cause) ................................................ 1641
Figure 1656 Immediate assignment flow........................... 1647
Figure 1657 Common assignment flow (internal TC)........... 1647
Figure 1658 Common assignment flow (external TC) .......... 1648
Figure 1659 Internal handover (like intra-cell handover) flow
(internal TC) ................................................. 1648
Figure 1660 Internal handover (during Intra-cell handover,
and channel types are changed) flow (external
TC) .............................................................. 1649
Figure 1661 External handover flow (internal TC)............... 1649
Figure 1662 External handover flow (external TC) .............. 1650
(internal TC) ................................................. 1651
TC) .............................................................. 1652
(internal TC) ................................................. 1655
TC) .............................................................. 1655
(internal TC) ................................................. 1657
TC) .............................................................. 1658
3253

(internal TC) ................................................. 1661
TC) .............................................................. 1661
(internal TC) ................................................. 1663
TC) .............................................................. 1664
Figure 1686 Internal handover (internal TC intra-cell
handover) failure flow 1.................................. 1666
Figure 1687 External handover failure flow (internal TC) ..... 1666
(internal TC) ................................................. 1670
TC) .............................................................. 1670
(internal TC) ................................................. 1674
TC) .............................................................. 1674
3254
Figures

(internal TC) ................................................. 1676
TC) .............................................................. 1677
(internal TC) ................................................. 1680
TC) .............................................................. 1681
(internal TC) ................................................. 1683
TC) .............................................................. 1683
(internal TC) ................................................. 1687
TC) .............................................................. 1687
(internal TC) ................................................. 1689
TC) .............................................................. 1690
3255

(internal TC) ................................................. 1693
TC) .............................................................. 1694
(internal TC) ................................................. 1700
TC) .............................................................. 1700
(internal TC) ................................................. 1704
TC) .............................................................. 1704
(internal TC) ................................................. 1706
TC) .............................................................. 1707
3256
Figures

(internal TC) ................................................. 1710
TC) .............................................................. 1711
Figure 1762 General Assignment Failure Flow 1 (external
TC) .............................................................. 1715
TC) .............................................................. 1716
Figure 1764 Internal handover (external TC intra-cell
handover, and channel types are changed) failure
flow 1 .......................................................... 1717
flow 2 .......................................................... 1719
Figure 1767 External handover failure flow 2 (external TC) .. 1719
TC) .............................................................. 1720
TC) .............................................................. 1721
flow 1 .......................................................... 1722
flow 2 .......................................................... 1723
3257

TC) .............................................................. 1725
TC) .............................................................. 1726
flow 1 .......................................................... 1727
flow 2 .......................................................... 1728
Figure 1780 Request Resource Failure .............................. 1730
Figure 1781 Channel allocation failure .............................. 1731
Figure 1805 Flow of Ordinary User's Call Being Released due
to Resource Being Preempted.......................... 1768
3258
Figures
Figure 1806 Flow of Handover for Ordinary User's Call due to

Resource Being Preempted ............................. 1769
Figure 1807 Flow of Occupying TCH/F during Assignment.... 1770
Figure 1808 Flow of Occupying TCH/F during Inter-BSC
Handover ..................................................... 1770
Figure 1809 Flow of Occupying TCH/F during Intra-BSC
Handover ..................................................... 1770
Handover ..................................................... 1771
Handover ..................................................... 1771
Handover ..................................................... 1772
Handover ..................................................... 1773
(internal TC) ................................................. 1780
TC) .............................................................. 1781
(internal TC) ................................................. 1783
TC) .............................................................. 1784
(internal TC) ................................................. 1788
3259

TC) .............................................................. 1788
(internal TC) ................................................. 1790
TC) .............................................................. 1791
Figure 1839 External handover failure flow 2 (internal TC) .. 1793
(internal TC) ................................................. 1795
TC) .............................................................. 1795
(internal TC) ................................................. 1797
TC) .............................................................. 1798
3260
Figures

(internal TC) ................................................. 1804
TC) .............................................................. 1804
(internal TC) ................................................. 1809
TC) .............................................................. 1810
(internal TC) ................................................. 1811
TC) .............................................................. 1812
(internal TC) ................................................. 1817
TC) .............................................................. 1817
(internal TC) ................................................. 1819
TC) .............................................................. 1820
3261

(internal TC) ................................................. 1825
TC) .............................................................. 1825
(internal TC) ................................................. 1827
TC) .............................................................. 1828
(internal TC) ................................................. 1831
TC) .............................................................. 1832
(internal TC) ................................................. 1838
3262
Figures

TC) .............................................................. 1838
(internal TC) ................................................. 1843
TC) .............................................................. 1844
(internal TC) ................................................. 1846
TC) .............................................................. 1846
(internal TC) ................................................. 1850
TC) .............................................................. 1850
3263

TC) .............................................................. 1855
TC) .............................................................. 1856
flow 1 .......................................................... 1857
flow 2 .......................................................... 1859
TC) .............................................................. 1860
TC) .............................................................. 1861
flow 1 .......................................................... 1862
flow 2 .......................................................... 1864
TC) .............................................................. 1865
TC) .............................................................. 1866
flow 1 .......................................................... 1867
flow 2 .......................................................... 1869
3264
Figures

Figure 1974 Resource releasing of ordinary users due to
being grabbed (TCH/H) .................................. 1905
Figure 1975 Handover of ordinary users due to being
grabbed (TCH/H) ........................................... 1906
Handover ..................................................... 1907
Handover ..................................................... 1907
Handover ..................................................... 1908
Handover ..................................................... 1908
Handover ..................................................... 1909
Handover ..................................................... 1910
3265
Figure 1985 BTS sends measurement point of Abis message

to BSC ......................................................... 1914
Figure 1986 Measurement Point when BSC Sends Abis
Message to BTS............................................. 1915
Message to BTS............................................. 1915
to BSC ......................................................... 1916
to BSC ......................................................... 1917
Message to BTS............................................. 1917
to BSC ......................................................... 1918
to BSC ......................................................... 1919
Message to BTS............................................. 1919
to BSC ......................................................... 1920
to BSC ......................................................... 1921
Message to BTS............................................. 1921
to BSC ......................................................... 1922
Message to BTS............................................. 1923
to BSC ......................................................... 1923
to BSC ......................................................... 1924
to BSC ......................................................... 1925
Message to BTS............................................. 1925
Message to BTS............................................. 1926
to BSC ......................................................... 1927
3266
Figures

to BSC ......................................................... 1928
Message to BTS............................................. 1928
to BSC ......................................................... 1929
to BSC ......................................................... 1930
Message to BTS............................................. 1930
to BSC ......................................................... 1931
Message to BTS............................................. 1932
Message to BTS............................................. 1932
Message to BTS............................................. 1933
Message to BTS............................................. 1934
to BSC ......................................................... 1935
to BSC ......................................................... 1935
Message to BTS............................................. 1936
to BSC ......................................................... 1937
to BSC ......................................................... 1937
Message to BTS............................................. 1938
Message to BTS............................................. 1939
to BSC ......................................................... 1939
to BSC ......................................................... 1940
to BSC ......................................................... 1941
3267

Message to BTS............................................. 1941
Message to BTS............................................. 1942
Message to BTS............................................. 1943
Message to BTS............................................. 1943
to BSC ......................................................... 1944
to BSC ......................................................... 1945
to BSC ......................................................... 1945
Message to BTS............................................. 1946
to BSC ......................................................... 1947
to BSC ......................................................... 1947
to BSC ......................................................... 1948
Message to BTS............................................. 1949
to BSC ......................................................... 1949
to BSC ......................................................... 1950
to BSC ......................................................... 1951
Message to BTS............................................. 1951
to BSC ......................................................... 1952
to BSC ......................................................... 1953
to BSC ......................................................... 1953
Message to BTS............................................. 1954
3268
Figures

Message to BTS............................................. 1955
Message to BTS............................................. 1955
to BSC ......................................................... 1956
Message to BTS............................................. 1957
Message to BTS............................................. 1957
to BSC ......................................................... 1958
to BSC ......................................................... 1959
to BSC ......................................................... 1959
Message to BTS............................................. 1960
to BSC ......................................................... 1961
Message to BTS............................................. 1961
to BSC ......................................................... 1962
to BSC ......................................................... 1963
to BSC ......................................................... 1963
to BSC ......................................................... 1964
to BSC ......................................................... 1965
Message to BTS............................................. 1965
to BSC ......................................................... 1966
to BSC ......................................................... 1967
Message to BTS............................................. 1967
3269

to BSC ......................................................... 1968
to BSC ......................................................... 1969
Message to BTS............................................. 1969
to BSC ......................................................... 1970
to BSC ......................................................... 1971
Message to BTS............................................. 1971
to BSC ......................................................... 1972
to BSC ......................................................... 1973
Message to BTS............................................. 1973
Message to BTS............................................. 1974
Message to BTS............................................. 1975
to BSC ......................................................... 1975
to BSC ......................................................... 1976
Message to BTS............................................. 1977
to BSC ......................................................... 1977
to BSC ......................................................... 1978
Message to BTS............................................. 1979
Message to BTS............................................. 1979
Message to BTS............................................. 1980
Message to BTS............................................. 1981
3270
Figures

Message to BTS............................................. 1981
Figure 2086 Measurement point of sum of UL UNITDATA
Figure 2087 Measurement point of sum of DL UNITDATA
Figure 2088 Measurement point of the number of
RA-CAPABILITY message received.................... 1986
Figure 2089 PTP Packet Paging Process ............................ 1987
Figure 2090 PTP Circuit Paging Process............................. 1987
Figure 2110 TIME OF PVC UNAVAILABLE .......................... 2007
Figure 2111 TIME OF PVC CONGESTION FRAME RELAY ...... 2007
Figure 2112 UPLINK/DOWNLINK NS DATA ........................ 2008
Figure 2113 UPLINK/DOWNLINK NS DATA ........................ 2009
Figure 2114 SENDING AND RECEIVING PDU DATA ............ 2009
Figure 2115 SENDING AND RECEIVING PDU DATA ............ 2010
Figure 2116 PDU DATA DISCARDED BY NS SUB LAYER ....... 2011
Figure 2117 NSVC RESETTING PROCESS .......................... 2011
3271
Figure 2121 NSVC BLOCKING PROCESS ........................... 2014

Figure 2125 NSVC UNBLOCKING PROCESS ....................... 2017
Figure 2129 FR REPORTING TRANSMISSION NETWORK
FAULT .......................................................... 2020
Figure 2130 BLOCKING NSVC BY BACKGROUND ............... 2020
Figure 2131 FR REPORTING EQUIPMENT FAULT ................. 2021
Figure 2132 NSVC BLOCKED ........................................... 2022
Figure 2133 NSVC UNKNOWN ......................................... 2022
Figure 2134 NS PROTOCOL ERROR .................................. 2023
Figure 2135 TEST PROCEDURE BEING ABNORMAL ............. 2024
Figure 2136 BLOCKING PROCEDURE BEING ABNORMAL...... 2025
Figure 2137 UNBLOCKING PROCEDURE BEING ABNORMAL
................................................................... 2026
Figure 2138 UPLINK/DOWNLINK DATA BECN BEING SET..... 2028
Figure 2139 UPLINK/DOWNLINK DATA BECN BEING SET..... 2029
Figure 2140 MEASUREMENT POINT OF BSS RECEIVING CS
PAGING MESSAGE ........................................ 2033
Figure 2141 MEASUREMENT POINT OF BSS RECEIVING PS
PAGING MESSAGE ........................................ 2033
Figure 2142 SUSPEND PROCESS...................................... 2034
Figure 2143 SUSPEND PROCESS...................................... 2035
Figure 2144 MEASUREMENT POINT OF BSS RECEIVING
SUSPEND_NACK MESSAGE ............................ 2035
Figure 2145 RESUME PROCESS ....................................... 2036
Figure 2146 RESUME PROCESS ....................................... 2037
RESUME_NACK MESSAGE ............................... 2037
Figure 2148 FLUSH_LL PROCESS ..................................... 2038
Figure 2149 FLUSH_LL PROCESS ..................................... 2039
Figure 2150 MEASUREMENT POINT OF BSS SENDING
LLC_DISCARDED MESSAGE............................. 2039
Figure 2151 BVC_BLOCK PROCESS .................................. 2040
Figure 2152 BVC_BLOCK PROCESS .................................. 2040
Figure 2153 BVC_UNBLOCK PROCESS ............................. 2041
3272
Figures
Figure 2154 BVC_UNBLOCK PROCESS ............................. 2042

Figure 2155 PROCESS OF SENDING BVC_RESET................ 2042
Figure 2156 PROCESS OF RECEIVING BVC_RESET ............. 2043
Figure 2157 PROCESS OF RECEIVING BVC_RESET ............. 2043
Figure 2158 PROCESS OF SENDING BVC_RESET................ 2044
Figure 2159 PERFORM_LOCATION_REQUEST PROCESS....... 2045
Figure 2160 PERFORM_LOCATION_REQUEST PROCESS....... 2045
PERFORM_LOCATION_ABORT MESSAGE............ 2046
Figure 2162 POSITION_COMMAND PROCESS .................... 2047
Figure 2163 POSITION_COMMAND PROCESS .................... 2047
Figure 2164 STATUS PROCESS ........................................ 2048
Figure 2166 POWER CONTROL MEASUREMENT .................. 2063
3273

Figure 2199 TEST PROCEDURE BEING ABNORMAL ............. 2104
Figure 2200 MEASUREMENT POINT OF THE NUMBER OF
RECEIVING RA-CAPABILITY MESSAGE .............. 2107
Figure 2201 PTP PACKET PAGING PROCESS ...................... 2107
Figure 2202 PTP CIRCUIT PAGING PROCESS ..................... 2108
Figure 2203 RA-CAPABILITY-UPDATE PROCESS ................. 2109
Figure 2204 RA-CAPABILITY-UPDATE PROCESS ................. 2109
Figure 2205 RADIO-STATUS PROCESS.............................. 2110
Figure 2206 FLOW-CONTROL-BVC PROCESS ..................... 2112
Figure 2207 FLOW-CONTROL-BVC PROCESS ..................... 2113
Figure 2208 FLOW-CONTROL-MS PROCESS ....................... 2113
Figure 2209 FLOW-CONTROL-MS PROCESS ....................... 2114
Figure 2210 FLOW-CONTROL-PFC PROCESS ...................... 2115
Figure 2211 FLOW-CONTROL-PFC PROCESS ...................... 2115
Figure 2214 CREATE-BSS-PFC PROCESS ........................... 2120
Figure 2218 MODIFY-BSS-PFC PROCESS........................... 2123
Figure 2219 MODIFY-BSS-PFC PROCESS........................... 2124
Figure 2220 DELETE-BSS-PFC PROCESS ........................... 2124
Figure 2221 DELETE-BSS-PFC PROCESS ........................... 2125
PS-HANDOVER-REQUIRED messages sent
by BSC......................................................... 2126
PS-HANDOVER-REQUIRED-ACK messages
received by BSC ............................................ 2127
received by BSC ............................................ 2128
3274
Figures

PS-HANDOVER-REQUEST messages received by
BSC ............................................................. 2129
PS-HANDOVER-REQUEST-ACK messages
sent by BSC.................................................. 2130
PS-HANDOVER-REQUEST-NACK messages
sent by BSC.................................................. 2131
PS-HANDOVER-COMPLETE messages sent
by BSC......................................................... 2132
PS-HANDOVER-CANCEL messages sent by
BSC ............................................................. 2133
PS-HANDOVER-REQUEST messages with
Service UTRAN CCO received by BSC ............... 2134
CREATE-BSS-PFC messages with Service
UTRAN CCO received by BSC........................... 2135
Figure 2232 MEASUREMENT POINT OF MSC SENDING
BSSMAP MESSAGE TO BSC ............................. 2166
Figure 2233 MEASUREMENT POINT OF BSC SENDING
BSSMAP MESSAGE TO MSC ............................. 2166
Figure 2234 MEASUREMENT POINT OF BSC RECEIVING
ASSIGNMENT REQUEST MESSAGE FROM MSC ... 2167
ASSIGNMENT COMPLETE MESSAGE TO MSC ...... 2167
ASSIGNMENT FAILURE MESSAGE TO MSC ......... 2168
RESOURCE REQUEST MESSAGE TO BSC ........... 2169
RESOURCE INDICATION MESSAGE TO MSC ....... 2169
PAGING MESSAGE TO BSC .............................. 2170
CIPHER MODE COMMAND MESSAGE TO BSC ..... 2171
3275

CIPHER MODE COMPLETE MESSAGE TO MSC ..... 2171
CIPHER MODE REJECT MESSAGE TO MSC ......... 2172
CLASSMARK UPDATE MESSAGE TO MSC ........... 2173
CLASSMARK UPDATE MESSAGE TO BSC ............ 2173
QUEUING INDICATION MESSAGE TO MSC ......... 2174
COMPLETE LAYER 3 INFORMATION MESSAGE TO
MSC............................................................. 2174
CLASSMARK REQUEST MESSAGE TO BSC.......... 2175
Figure 2248 MEASUREMENT POINT OF BSC SENDING LOAD
INDICATION MESSAGE TO MSC ....................... 2176
Figure 2249 MEASUREMENT POINT OF MSC SENDING LOAD
INDICATION MESSAGE TO BSC........................ 2176
HANDOVER REQUEST MESSAGE TO BSC ........... 2177
Figure 2251 INTER-BSC HANDOVER PROCESS INITIATED BY
BSC ............................................................. 2178
BSC ............................................................. 2179
BSC ............................................................. 2180
BSC ............................................................. 2181
BSC ............................................................. 2182
Figure 2256 PROCESS OF MSC SENDING HANDOVER
CANDIDATE ENQUIRE MESSAGE TO BSC........... 2182
Figure 2257 PROCESS OF MSC SENDING HANDOVER
CANDIDATE ENQUIRE MESSAGE TO BSC........... 2183
HANDOVER FAILURE MESSAGE TO MSC ............ 2184
HANDOVER PERFORMED MESSAGE TO MSC ...... 2184
3276
Figures

HANDOVER REQUIRED REJECT MESSAGE TO
BSC ............................................................. 2185
HANDOVER DETECT MESSAGE TO MSC............. 2186
Figure 2262 CLEAR PROCESS .......................................... 2186
Figure 2263 CLEAR PROCESS .......................................... 2187
Figure 2264 MEASUREMENT POINT OF BSC SENDING CLEAR
REQUEST MESSAGE TO MSC ........................... 2188
Figure 2265 MEASUREMENT POINT OF BSC SENDING SAPI
"N" REJECT MESSAGE TO MSC......................... 2188
CONFUSION MESSAGE TO MSC ....................... 2189
CONFUSION MESSAGE TO BSC........................ 2189
Figure 2268 UPLINK RESET PROCESS .............................. 2190
Figure 2269 DOWNLINK RESET PROCESS ......................... 2191
Figure 2270 DOWNLINK RESET PROCESS ......................... 2191
Figure 2271 UPLINK RESET PROCESS .............................. 2192
OVERLOAD MESSAGE TO MSC ......................... 2193
OVERLOAD MESSAGE TO BSC ......................... 2193
Figure 2274 MEASUREMENT POINT OF MSC SENDING MSC
INVOKE TRACE MESSAGE TO BSC.................... 2194
Figure 2275 MEASUREMENT POINT OF BSC SENDING BSS
INVOKE TRACE MESSAGE TO MSC ................... 2194
Figure 2276 MEASUREMENT POINT OF MSC SENDING BSS
INVOKE TRACE MESSAGE TO BSC ................... 2195
CONNECTIONLESS INFORMATION MESSAGE TO
MSC............................................................. 2196
CONNECTIONLESS INFORMATION MESSAGE TO
BSC ............................................................. 2196
SUSPEND MESSAGE TO MSC ........................... 2197
RESUME MESSAGE TO MSC............................. 2197
3277

COMMON ID MESSAGE TO BSC........................ 2198
Figure 2282 MEASUREMENT POINT OF MSC SENDING LSA
INFORMATION MESSAGE TO BSC ..................... 2198
Figure 2283 PROCESS OF MSC SENDING PERFORM
LOCATION REQUEST MESSAGE TO BSC ............ 2199
Figure 2284 PROCESS OF MSC SENDING PERFORM
LOCATION REQUEST MESSAGE TO BSC ............ 2200
PERFORM LOCATION ABORT MESSAGE TO BSC .. 2200
Figure 2286 PROCESS OF BSC SENDING BLOCK MESSAGE
TO MSC........................................................ 2201
Figure 2287 PROCESS OF BSC SENDING BLOCK MESSAGE
TO MSC........................................................ 2202
Figure 2288 PROCESS OF BSC SENDING UNBLOCK MESSAGE
TO MSC........................................................ 2202
Figure 2289 PROCESS OF BSC SENDING UNBLOCK MESSAGE
TO MSC........................................................ 2203
Figure 2290 PROCESS OF MSC SENDING BLOCK MESSAGE
TO BSC ....................................................... 2204
Figure 2291 PROCESS OF MSC SENDING BLOCK MESSAGE
TO BSC ....................................................... 2204
Figure 2292 PROCESS OF MSC SENDING UNBLOCK MESSAGE
TO BSC ....................................................... 2205
Figure 2293 PROCESS OF MSC SENDING UNBLOCK MESSAGE
TO BSC ....................................................... 2206
Figure 2294 PROCESS OF BSC SENDING RESET CIRCUIT
MESSAGE TO MSC ......................................... 2206
Figure 2295 PROCESS OF MSC SENDING RESET CIRCUIT
MESSAGE TO BSC.......................................... 2207
Figure 2296 PROCESS OF MSC SENDING RESET CIRCUIT
MESSAGE TO BSC.......................................... 2208
Figure 2297 PROCESS OF BSC SENDING RESET CIRCUIT
MESSAGE TO MSC ......................................... 2208
Figure 2298 PROCESS OF BSC SENDING CIRCUIT GROUP
BLOCK MESSAGE TO MSC ............................... 2209
Figure 2299 PROCESS OF MSC SENDING CIRCUIT GROUP
BLOCK MESSAGE TO BSC .............................. 2210
BLOCK MESSAGE TO BSC .............................. 2210
3278
Figures

BLOCK MESSAGE TO MSC ............................... 2211
UNBLOCK MESSAGE TO MSC ........................... 2212
UNBLOCK MESSAGE TO BSC ........................... 2212
UNBLOCK MESSAGE TO BSC ........................... 2213
UNBLOCK MESSAGE TO MSC .......................... 2214
UNEQUIPPED CIRCUIT MESSAGE TO MSC ......... 2215
UNEQUIPPED CIRCUIT MESSAGE TO BSC.......... 2215
Figure 2308 PROCESS OF MSC SENDING CHANGE CIRCUIT
MESSAGE TO BSC.......................................... 2216
Figure 2309 PROCESS OF MSC SENDING CHANGE CIRCUIT
MESSAGE TO BSC.......................................... 2217
Figure 2310 Measurement Point of the Count of Sending
INTERNAL HANDOVER REQUIRED .................... 2218
Figure 2311 Measurement Point of the Count of Receiving
INTERNAL HANDOVER COMMAND .................... 2219
Figure 2312 Measurement Point of the Count of Receiving
INTERNAL HANDOVER REJECT......................... 2220
Figure 2313 OMCR Initiating IP Resource Resetting Flow ..... 2221
Figure 2315 MSC Initiating IP Resource Resetting Flow ....... 2222
Figure 2316 MSC Initiating IP Resource Resetting Flow ....... 2223
A-INTERFACE DTAP MESSAGE TO MSC ............. 2226
A-INTERFACE DTAP MESSAGE TO BSC .............. 2226
A-INTERFACE BSSMAP MESSAGE TO MSC ......... 2227
Figure 2321 MEASUREMENT POINT OF BSC RECEIVING
A-INTERFACE BSSMAP MESSAGE FROM MSC ..... 2227
Figure 2322 REQUESTING RESOURCE FROM DATABASE
SUCCESSFULLY ............................................. 2235
3279

FAILURE ....................................................... 2236
SUCCESSFULLY ............................................. 2237
SUCCESSFULLY ............................................. 2238
SUCCESSFULLY ............................................. 2239
FAILURE ....................................................... 2239
Figure 2328 The times of User Plane transport without RTP
multiplexing.................................................. 2241
Figure 2329 The times of RTP multiplexing applied without
RTP header compression................................. 2241
Figure 2330 The times of RTP multiplexing applied with RTP
header compression ....................................... 2242
Figure 2331 Common Release Flow .................................. 2243
Figure 2332 Standby umc Database Being Released ........... 2243
Figure 2333 OMS Reporting Data to Database ................... 2244
Figure 2334 NACC Duration ............................................ 2305
Figure 2337 Measurement point of number of NACC success
................................................................... 2308
Figure 2338 Measurement point of number of NACCs ......... 2309
Figure 2339 Measurement point for the sum of C ............... 2310
Figure 2351 Measurement point of Number of RLC uplink
ACK TBF ....................................................... 2321
3280
Figures
Figure 2352 Measurement point of Number of RLC uplink

ACK TBF ....................................................... 2322
Figure 2353 Flow of Pushing Down Uplink Bandwidth.......... 2337
Figure 2354 Flow of Pushing Down Downlink Bandwidth...... 2338
Figure 2355 Flow of Pushing Up Uplink Bandwidth.............. 2339
Figure 2356 Flow of Pushing Up Downlink Bandwidth.......... 2339
Figure 2357 Status Query Process ................................... 2342
Figure 2360 Uplink NS Data ............................................ 2366
Figure 2361 Measurement Point of Average length of
queue .......................................................... 2372
Figure 2362 Measurement Point of Queuing Duration when
Queuing Fails ................................................ 2373
Queuing Succeeds ......................................... 2373
Queuing Fails ................................................ 2374
Figure 2368 Measurement Point of BTS Sending Channel
Activation Completion Message to BSC ............. 2380
Figure 2369 Measurement Point of MS Sending
Assignment/Handover Completion Message to
BSC ............................................................. 2380
Figure 2370 Measurement Point of BSC Receiving Paging
Message from A-Interface ............................... 2385
Figure 2371 Measurement Point of BSC Receiving PS/CS
Paging Message from Gb Interface ................... 2386
Figure 2372 Measurement Point of BSC Receiving Paging
Message from A-Interface ............................... 2386
3281
Figure 2375 Measurement Point of Number of BSC originated

SCCP Connection attempts.............................. 2394
Figure 2376 Measurement Point of Number of BSC originated
SCCP Connection attempts.............................. 2395
Figure 2377 Measurement Point of Number of negative
replies for SCCP connection request ................. 2397
Figure 2378 Measurement Point of Number of MSC originated
SCCP Connection Requests ............................. 2398
Figure 2379 Measurement Point of Number of MSC originated
SCCP Connection success ............................... 2399
Figure 2380 Measurement Point of Resending I Frame on
LAPD Link due to T200 Timeout ....................... 2421
Figure 2381 Measurement Point of Number of Resending
Frame upon Request ...................................... 2422
Figure 2382 Measurement Point of Number of Protocol
Errors .......................................................... 2423
Figure 2383 Measurement Point of Number of receiving
location request in CS .................................... 2430
Figure 2384 Measurement Point of Number of Location
Terminations Received in CS Domain ................ 2431
Figure 2385 Measurement Point of Number of TA Request in
CS ............................................................... 2432
Figure 2386 Measurement Point of Number of TA Responses
in CS Domain ................................................ 2432
Figure 2387 Measurement Point of Number of MS Position
Commands in CS Domain ............................... 2433
Response in CS Domain.................................. 2434
Successes in CS Domain................................. 2434
Figure 2390 Measurement Point of Number of location failure
due to abnormal status of Lb interface in CS ..... 2435
due to radio Timer expiration in CS .................. 2436
Figure 2392 Measurement Point of Number of Location Delays
in CS Domain due to Intra-BSC Handover ......... 2437
Failures due to Intra-BSS Handover Timer
Timeout in CS Domain.................................... 2437
3282
Figures

Failure due to Location Monitoring Timer Timeout
in CS Domain ................................................ 2438
Figure 2395 Measurement Point of Number of Location Failure
due to Inter-BSS handover in CS Domain.......... 2439
Failure due to Call Drop in CS Domain .............. 2440
Requests in PS Domain................................... 2441
Terminations Received in PS Domain ................ 2442
Figure 2399 Measurement Point of Number of TA Requests in
PS Domain.................................................... 2442
Figure 2400 Measurement Point of Number of TA Responses
in PS Domain ................................................ 2443
Commands in PS Domain................................ 2444
Response in PS Domain .................................. 2444
Successes in PS Domain ................................. 2445
due to abnormal status of Lb interface in PS...... 2446
Figure 2405 Number of Location Failures in PS domain due
to Radio Timer Timeout .................................. 2446
Failure due to Inter-Module Cell Reselection in PS
Domain ........................................................ 2447
Figure 2407 Measurement Point of Number of Sending
Location Information Messages to LCS due to
Intra-Module Cell Reselection in PS Domain....... 2448
Failure due to Location Monitoring Timer Timeout
in PS Domain ................................................ 2449
Figure 2409 Measurement Point of Number of RESET
Messages Received from SMLC ........................ 2452
Figure 2410 Measurement Point of Number of RESET ACK
Messages Sent to SMLC.................................. 2452
Figure 2411 Measurement Point of Number of RESET
Messages Sent to SMLC.................................. 2453
3283
Figure 2412 Measurement Point of Number of RESET ACK

Messages Received from SMLC ........................ 2454
Figure 2413 Measurement Point of Number of configured 16
K relay circuits of Ater interface ....................... 2456
Figure 2414 Measurement Point of Average of unavailable
16K relay circuits of Ater interface ................... 2457
Figure 2415 Measurement Point of Average of available 16 K
relay circuits of Ater interface.......................... 2458
Figure 2416 Measurement Point of Maximum of busy 16 K
relay circuits of Ater interface - (1) .................. 2459
Figure 2417 Measurement Point of Maximum of busy 16 K
Figure 2418 Measurement Point of Maximum of busy 8K
Figure 2419 Measurement Point of Maximum of busy 8K
Figure 2420 Measurement Point of Total busy time of 16 K
Figure 2421 Measurement Point of Total busy time of 16 K
Figure 2422 Measurement Point of Total busy time of 8K
Figure 2423 Measurement Point of Total busy time of 8K
Figure 2424 Measurement Point of Number of SCCP
establishment requests (BSC to TC) ................. 2466
Connection Successes .................................... 2467
Connection Failure due to Timeout ................... 2468
Connection Request Being Rejected.................. 2469
Figure 2428 Measurement Point of BTS Sending Meaurement
Report to BSC ............................................... 2474
Report to BSC ............................................... 2475
Report to BSC ............................................... 2476
Report to BSC ............................................... 2477
3284
Figures

Report to BSC ............................................... 2478
Report to BSC ............................................... 2478
Report to BSC ............................................... 2479
Report to BSC ............................................... 2480
Report to BSC ............................................... 2481
Report to BSC ............................................... 2482
Report to BSC ............................................... 2482
Report to BSC ............................................... 2483
Report to BSC ............................................... 2484
Report to BSC ............................................... 2485
Report to BSC ............................................... 2485
Report to BSC ............................................... 2486
Report to BSC ............................................... 2487
Report to BSC ............................................... 2488
Report to BSC ............................................... 2488
Report to BSC ............................................... 2489
Report to BSC ............................................... 2490
Report to BSC ............................................... 2491
Report to BSC ............................................... 2491
Report to BSC ............................................... 2492
3285

Report to BSC ............................................... 2493
Report to BSC ............................................... 2494
Report to BSC ............................................... 2494
Report to BSC ............................................... 2495
Report to BSC ............................................... 2496
Report to BSC ............................................... 2497
Report to BSC ............................................... 2497
Report to BSC ............................................... 2498
Report to BSC ............................................... 2499
Report to BSC ............................................... 2500
Report to BSC ............................................... 2500
Report to BSC ............................................... 2501
Report to BSC ............................................... 2502
Report to BSC ............................................... 2503
Report to BSC ............................................... 2503
Report to BSC ............................................... 2504
Report to BSC ............................................... 2505
Report to BSC ............................................... 2506
Report to BSC ............................................... 2506
Report to BSC ............................................... 2507
3286
Figures

Report to BSC ............................................... 2508
Report to BSC ............................................... 2509
Report to BSC ............................................... 2509
Report to BSC ............................................... 2510
Report to BSC ............................................... 2511
Report to BSC ............................................... 2512
Report to BSC ............................................... 2512
Report to BSC ............................................... 2513
Report to BSC ............................................... 2514
Report to BSC ............................................... 2515
Report to BSC ............................................... 2515
Report to BSC ............................................... 2516
Report to BSC ............................................... 2517
Report to BSC ............................................... 2518
Report to BSC ............................................... 2518
Report to BSC ............................................... 2519
Report to BSC ............................................... 2520
Report to BSC ............................................... 2521
Report to BSC ............................................... 2521
Report to BSC ............................................... 2522
3287

Report to BSC ............................................... 2523
Report to BSC ............................................... 2524
Report to BSC ............................................... 2524
Report to BSC ............................................... 2525
Report to BSC ............................................... 2526
Report to BSC ............................................... 2527
Report to BSC ............................................... 2527
Report to BSC ............................................... 2528
Report to BSC ............................................... 2529
Report to BSC ............................................... 2530
Report to BSC ............................................... 2530
Report to BSC ............................................... 2531
Report to BSC ............................................... 2532
Report to BSC ............................................... 2533
Report to BSC ............................................... 2533
Report to BSC ............................................... 2534
Report to BSC ............................................... 2535
Report to BSC ............................................... 2536
Report to BSC ............................................... 2536
Report to BSC ............................................... 2537
3288
Figures

Report to BSC ............................................... 2538
Report to BSC ............................................... 2539
Report to BSC ............................................... 2539
Report to BSC ............................................... 2540
Report to BSC ............................................... 2541
Report to BSC ............................................... 2542
Report to BSC ............................................... 2542
Report to BSC ............................................... 2543
Report to BSC ............................................... 2544
Report to BSC ............................................... 2545
Report to BSC ............................................... 2545
Report to BSC ............................................... 2546
Report to BSC ............................................... 2547
Report to BSC ............................................... 2550
Figure 2526 Measurement Point of BTS Sending Measurement
Report to BSC ............................................... 2550
Report to BSC ............................................... 2551
Report to BSC ............................................... 2552
Report to BSC ............................................... 2552
Report to BSC ............................................... 2553
Report to BSC ............................................... 2554
3289

Report to BSC ............................................... 2554
Report to BSC ............................................... 2555
Figure 2534 Paging Performance Measurement Reporting.... 2558
Figure 2535 Measurement Point of Number of mobile support
single TS DTM ability...................................... 2570
DTM GPRS multi TS ability 5............................ 2571
DTM GPRS multi TS ability 9............................ 2572
DTM GPRS multi TS ability 11.......................... 2573
DTM EGPRS multi TS ability 5 .......................... 2574
DTM EGPRS multi TS ability 9 .......................... 2575
DTM EGPRS multi TS ability 11 ........................ 2576
extend DTM GPRS multi TS ability 5 ................. 2577
extend DTM GPRS multi TS ability 10 ............... 2580
extend DTM GPRS multi TS ability 11 ............... 2581
extend DTM EGPRS multi TS ability 5 ............... 2582
extend DTM EGPRS multi TS ability 10.............. 2585
extend DTM EGPRS multi TS ability 11.............. 2586
3290
Figures
Figure 2552 Measurement Point of Number of mobile of

GPRS multi TS ability 1 - (1) ........................... 2587
3291

GPRS multi TS ability 10 - (1) ......................... 2602
3292
Figures

EGPRS multi TS ability 1 - (1) ......................... 2615
3293

EGPRS multi TS ability 10 - (1)........................ 2630
3294
Figures

3295

FR ............................................................... 2643
HR............................................................... 2644
EFR ............................................................. 2644
AMRFR ......................................................... 2645
AMRHR......................................................... 2646
wideband AMROFR......................................... 2647
wideband AMRFR ........................................... 2648
wideband AMROHR ........................................ 2649
AMROHR ...................................................... 2649
extend uplink TBF - (1) .................................. 2650
extend uplink TBF - (2) .................................. 2650
NACC - (1) ................................................... 2651
NACC - (2) ................................................... 2651
GPRS extend dynamic allocation - (1)............... 2652
GPRS extend dynamic allocation - (2)............... 2653
EGPRS extend dynamic allocation - (1) ............. 2654
EGPRS extend dynamic allocation - (2) ............. 2654
Figure 2671 Measurement Point of Number of sampling
received Classmark3 ...................................... 2655
3296
Figures

received radio access ability - (1) .................... 2656
received radio access ability - (2) .................... 2656
Figure 2674 Measurement Point of Number of MS supporting
PS handover ................................................. 2657
Figure 2675 Assignment/Handover Flow ........................... 2657
Figure 2676 Handover Flow............................................. 2658
Figure 2677 AMR Rate Statistics Report ............................ 2802
Figure 2678 Measurement Point of Number of handover
attempts due to uplink received strength .......... 2860
attempts due to downlink received strength ...... 2861
attempts due to uplink quality ......................... 2861
attempts due to downlink quality ..................... 2862
attempts due to uplink interference.................. 2863
attempts due to downlink interference.............. 2863
attempts due to PBGT .................................... 2864
attempts due to large TA ................................ 2865
attempts due to uplink break up quickly ........... 2865
attempts due to macro-micro switch ................ 2866
attempts due to high traffic............................. 2867
attempts due to a good standard level in FDD
adjacent cell ................................................. 2868
attempts due to a good standard level in TDD
adjacent cell ................................................. 2868
attempts due to PCCN .................................... 2869
3297
Figure 2692 Measurement Point of Number of synchronous

handover executions ...................................... 2873
Figure 2693 Measurement Point of Number of successful
synchronous handovers - (1)........................... 2874
synchronous handovers - (2)........................... 2874
pre-synchronous handover executions .............. 2875
pre-synchronous handover successes (1) .............................................................. 2876
pre-synchronous handover successes (2) .............................................................. 2876
Figure 2698 Measurement Point of Number of asynchronous
asynchronous handovers - (1) ......................... 2878
asynchronous handovers - (2) ......................... 2878
Figure 2701 Measurement Point of Number of normal
normal handovers.......................................... 2879
Figure 2703 Measurement Point of Number of optimised
optimised handovers ...................................... 2881
Figure 2705 Measurement Point of Number of Intra-BSC
inter-cell outgoing handover attempts .............. 2882
Figure 2706 Measurement Point of Number of Intra-BSC
inter-cell outgoing handover executions ............ 2882
Intra-BSC inter-cell outgoing handovers - (1) .... 2883
Intra-BSC inter-cell outgoing handovers - (2) .... 2884
Figure 2709 Measurement Point of Number of Inter-BSC
outgoing handover attempts ........................... 2884
Figure 2710 Measurement Point of Number of Inter-BSC
outgoing handover executions ......................... 2885
3298
Figures

Inter-BSC outgoing handovers......................... 2886
Figure 2712 Measurement Point of Number of incoming
handover attempts ........................................ 2886
Figure 2713 Measurement Point of Number of incoming
incoming handovers ....................................... 2888
Figure 2715 Measurement Point of Number of Intra-cell
Figure 2716 Measurement Point of Number of 2G to FDD
Figure 2717 Measurement Point of Number of 2G to FDD
Figure 2718 Measurement Point of Number of successful 2G
to FDD handovers .......................................... 2891
Figure 2719 Measurement Point of Number of 2G to TDD
Figure 2720 Measurement Point of Number of 2G to TDD
to TDD handovers.......................................... 2893
Figure 2722 Measurement Point of Number of 3G to 2G
Figure 2723 Measurement Point of Number of 3G to 2G
to 2G handovers............................................ 2895
Figure 2725 Measurement Point of Number of T12 expiry.... 2896
Figure 2726 Measurement Point of Number of PCCF
received ....................................................... 2897
received with cause Create PFC Failure ............. 2897
received with cause PS Handover Target not
allowed ....................................................... 2898
3299
received with cause PS Handover not Supported

in Target BSS or Target System ....................... 2899
received with cause other reasons ................... 2900
Figure 2731 Measurement Point of Number of failure in
optimised handover due to resource allcoation
failure .......................................................... 2901
Figure 2732 Measurement Point of Number of failure in
optimized handover due to PS handover not
supported in target cell .................................. 2902
Figure 2733 Measurement Point of Relocation (on Iur-g) ..... 2904
Figure 2736 Measurement Point of Number of relocation
failures due to no valid radio resource (on
Iur-g) .......................................................... 2907
failures due to no valid terrestrial circuit resource
(on Iur-g)..................................................... 2908
failures due to loss of UE handover complete
message (on Iur-g)........................................ 2909
failures due to MS returning to original channel
(on Iur-g)..................................................... 2910
Figure 2740 Measurement Point of local jitter (CS)............. 2912
Figure 2741 Measurement Point of local jitter (CS)............. 2913
Figure 2742 Measurement Point of average one-way delay
(CS) ............................................................ 2915
Figure 2743 Measurement Point of maximal one-way delay
(CS) ............................................................ 2916
Figure 2744 Measurement Point of local cumulative fraction
lost (CS) ...................................................... 2918
Figure 2745 Measurement Point of distant cumulative
fraction lost (CS) ........................................... 2919
Figure 2746 Measurement Point of local jitter (PS) ............. 2920
Figure 2747 Measurement Point of distant jitter (PS) .......... 2921
Figure 2748 Measurement Point of average one-way delay
(PS)............................................................. 2923
3300
Figures
Figure 2749 Measurement Point of maximal one-way delay

(PS)............................................................. 2924
Figure 2750 Measurement Point of local cumulative fraction
lost (PS)....................................................... 2926
Figure 2751 Measurement Point of distant cumulative
fraction lost (PS) ........................................... 2927
Figure 2752 Measurement Point of the times of loss of TRAU
frame synchronization in BIPB ......................... 2930
Figure 2753 Measurement Point of Number of CS Call Denied
for Lack of IPAbis BandWidth UpLink ................ 2932
Figure 2754 Measurement Point of Number of CS Call Denied
for Lack of IPAbis BandWidth DownLink ............ 2933
Figure 2755 Measurement Point of Number of PS Call Denied
for Lack of IPAbis BandWidth UpLink ................ 2933
Figure 2756 Measurement Point of Number of PS Call Denied
for Lack of IPAbis BandWidth DownLink ............ 2934
Figure 2757 Flow of Pushing Down Uplink Bandwidth in
Resource Pool ............................................... 2935
Figure 2758 Flow of Pushing Down Downlink Bandwidth...... 2936
Figure 2759 Flow of Pushing Up Uplink Bandwidth in
Resource Pool ............................................... 2936
Figure 2760 Flow of Pushing Up Downlink Bandwidth in
Resource Pool ............................................... 2937
Figure 2761 Power Sharing Counter 1 .............................. 2940
Figure 2762 Flow of Reporting Power Control Indication
Message ....................................................... 2941
Figure 2763 Assignment Failure Process ........................... 2942
Figure 2764 Failure in Allocating Channel for Destination Cell
of Internal Handover ...................................... 2942
Figure 2765 Failure in Allocating Channel for External
Incoming Handover........................................ 2942
Figure 2766 C901940004a.............................................. 2943
Figure 2767 C901940004b.............................................. 2944
Figure 2768 C901940004c .............................................. 2944
attempts on the adjacent cell - (1)................... 2948
attempts on the adjacent cell - (2)................... 2949
3301

handovers from selected cell to the adjacent cell
- (1) ............................................................ 2949
- (2) ............................................................ 2950
attempts from adjacent cell to the selected cell (1) .............................................................. 2951
attempts from adjacent cell to the selected cell (2) .............................................................. 2951
handovers from adjacent cell to the selected cell
- (1) ............................................................ 2952
handovers from adjacent cell to the selected cell
- (2) ............................................................ 2952
attempts from selected cell to the adjacent cell
due to better uplink quality - (1)...................... 2953
due to better downlink quality - (1).................. 2954
3302
Figures

due to better uplink strength - (1) ................... 2958
due to better downlink strength - (1) ............... 2960
due to PBGT - (1) .......................................... 2963
due to PBGT - (2) .......................................... 2964
due to PBGT - (1) .......................................... 2965
due to PBGT - (2) .......................................... 2965
3303

due to large TA - (1) ...................................... 2966
due to large TA - (2) ...................................... 2966
handover from selected cell to the adjacent cell
due to large TA - (1) ...................................... 2967
due to large TA - (2) ...................................... 2967
due to high traffic - (1)................................... 2968
Figure 2805 Number of Error Indications due to T200 expired
on SDCCH .................................................... 2973
Figure 2806 Number of Error Indications due to unsolicited
message on SDCCH ....................................... 2974
DM response on SDCCH.................................. 2974
Figure 2808 Number of Error Indications due to sequence
error on SDCCH............................................. 2975
Figure 2809 Number of Error Indications due to frame
content error on SDCCH ................................. 2976
Figure 2810 Number of Error Indications due to SABM
command on SDCCH ...................................... 2976
on TCH/F ...................................................... 2977
message on TCH/F......................................... 2978
3304
Figures
Figure 2813 C902000009 ............................................... 2978

error on TCH/F .............................................. 2979
content error on TCH/F................................... 2980
command on TCH/F ....................................... 2980
on TCH/H ..................................................... 2981
message on TCH/H ........................................ 2982
DM response on TCH/H................................... 2982
error on TCH/H.............................................. 2983
content error on TCH/H .................................. 2984
command on TCH/H ....................................... 2984
Figure 2823 Number of Release Indications due to T200
expired on SDCCH ......................................... 2985
Figure 2824 Number of Release Indications due to unsolicited
DM response on SDCCH.................................. 2986
Figure 2825 Number of Release Indications due to sequence
error on SDCCH............................................. 2987
expired on TCH/F (signaling) ........................... 2987
DM response on TCH/F (signaling) ................... 2988
error on TCH/F (signaling) .............................. 2989
expired on TCH/F (speech).............................. 2990
DM response on TCH/F (speech) ...................... 2990
error on TCH/F (speech) ................................. 2991
expired on TCH/F (data) ................................. 2992
3305

DM response on TCH/F (data) ......................... 2993
error on TCH/F (data) .................................... 2993
expired on TCH/H (signaling) .......................... 2994
DM response on TCH/H (signaling) ................... 2995
error on TCH/H (signaling) .............................. 2996
expired on TCH/H (speech) ............................. 2996
DM response on TCH/H (speech) ..................... 2997
error on TCH/H (speech) ................................ 2998
expired on TCH/H (data)................................. 2999
DM response on TCH/H (data) ......................... 2999
error on TCH/H (data) .................................... 3000
Figure 2844 Access Control of PS-Bandwidth Allocation....... 3006
Figure 2845 Access Control of CS-Bandwidth Allocation ...... 3006
Figure 2846 Number of PS Uplink Bandwidth Allocated More
than Overbooking .......................................... 3007
Figure 2847 Number of PS Uplink Bandwidth Measured More
than C2........................................................ 3007
Figure 2848 Number of that Sum of PS Uplink Bandwidth
Measured and Current Bandwidth Allocated More
than C1........................................................ 3008
Figure 2849 Number of PS Downlink Bandwidth Allocated
More than Overbooking .................................. 3009
Figure 2850 Number of PS Downlink Bandwidth Measured
More than C2 ................................................ 3010
Figure 2851 Number of that Sum of PS Downlink Bandwidth
than C1........................................................ 3011
Figure 2852 Number of CS Uplink Bandwidth Allocated More
than Overbooking ......................................... 3012
3306
Figures
Figure 2853 Number of CS Uplink Bandwidth Measured More

than C2........................................................ 3013
Figure 2854 Number of that Sum of CS Uplink Bandwidth
than C1........................................................ 3014
Figure 2855 Number of CS Downlink Bandwidth Allocated
More than Overbooking .................................. 3015
Figure 2856 Number of CS Downlink Bandwidth Measured
More than C2 ................................................ 3016
Figure 2857 Number of that Sum of CS Downlink Bandwidth
than C1........................................................ 3017
Figure 2858 Establishing VGCS (Success) ......................... 3020
Figure 2859 Establishing VGCS (Success) ......................... 3020
Figure 2860 Establishing VGCS (Failure) ........................... 3021
Figure 2861 Establishing VBS (Success) ........................... 3022
Figure 2862 Establishing VBS (Success) ........................... 3022
Figure 2863 Establishing VBS (Failure) ............................. 3023
Figure 2864 VGCS Resource Assignment Success............... 3026
Figure 2865 VGCS Resource Assignment Success............... 3027
Figure 2866 VGCS Resource Assignment Failure ................ 3028
Figure 2867 Inter-BSC Inter-Cell Outgoing Handover
Success........................................................ 3029
Success........................................................ 3030
Success........................................................ 3031
Failure ......................................................... 3032
Figure 2871 Inter-BSC Inter-Cell Incoming Handover
Success........................................................ 3032
Success........................................................ 3033
Success........................................................ 3034
Figure 2874 Listener's Notification Response Process
(Success) ..................................................... 3035
(Success) ..................................................... 3036
3307

(Failure) ....................................................... 3037
Figure 2877 No Listener Detected in Cell........................... 3038
Figure 2878 Talker Giving Up Conversation due to Radio Link
Failure ......................................................... 3038
Figure 2879 Talker Giving Up Conversation ....................... 3039
Figure 2880 Uplink Preemption Process ............................ 3040
Figure 2881 Intra-BSC Inter-Cell Handover (Success)......... 3041
Figure 2884 Intra-BSC Inter-Cell Handover (Failure) .......... 3043
Figure 2885 Intra-BSC Inter-Cell Incoming Handover ......... 3044
Figure 2890 VBS Resource Assignment Success ................. 3050
Figure 2891 VBS Resource Assignment Success ................. 3051
Figure 2892 VBS Resource Assignment Failure................... 3052
Success........................................................ 3053
Success........................................................ 3054
Success........................................................ 3055
Figure 2896 Inter-BSC Outgoing Handover Failure of Talker .. 3056
Figure 2897 Inter-BSC Inter-Cell Incoming Handover ......... 3056
(Success) ..................................................... 3059
(Success) ..................................................... 3060
(Failure) ....................................................... 3061
Figure 2903 No Listener Detected in Cell........................... 3062
Figure 2907 Intra-BSC Inter-Cell Handover (Failure) .......... 3065
3308
Figures

Figure 2911 Releasing Talker's Resource due to Radio Link
Failure ......................................................... 3069
Figure 2912 VGCS/VBS Establishment Process................... 3073
Figure 2916 Listener's Notification Response Process .......... 3077
Figure 2918 Inter-BSC Handover of Talker ........................ 3079
Figure 2919 Inter-BSC Handover of Talker ........................ 3080
Figure 2920 Intra-BSC Inter-Cell Handover of Talker .......... 3081
Figure 2921 Intra-BSC Inter-Cell Handover of Talker .......... 3082
Figure 2922 VGCS Cell Establishment Process ................... 3083
Figure 2923 VGCS Cell Establishment Process ................... 3084
Figure 2924 VBS Cell Establishment Process...................... 3085
Figure 2925 VBS Cell Establishment Process...................... 3086
Figure 2928 Inter-BSC Incoming Handover of Talker .......... 3089
Figure 2932 Measurement Point of Number of Channel
Requests ...................................................... 3094
Figure 2933 Measurement Point of Number of Paging
Messages ..................................................... 3094
Attempt (on SDCCH)...................................... 3097
Execution ..................................................... 3098
Success........................................................ 3099
Figure 2937 MSC-Controlled Outgoing Handover Attempt.... 3100
Figure 2938 MSC-Controlled Outgoing Handover Failure due
to Unclear Cause ........................................... 3101
Figure 2939 MSC-Controlled Handover Request Being
Rejected....................................................... 3102
3309
Figure 2940 MSC-Controlled Handover Request Being

Rejected....................................................... 3103
Executions .................................................... 3104
Successes..................................................... 3105
Attempt ....................................................... 3106
Execution ..................................................... 3107
Figure 2945 Forced Release Attempt ................................ 3108
Figure 2946 Forced Release Execution .............................. 3109
Figure 2947 Queuing Attempt ......................................... 3110
Figure 2948 Queuing Execution ....................................... 3111
Figure 2949 Forced Handover Attempt.............................. 3112
Figure 2950 Forced Handover Execution ........................... 3113
Success........................................................ 3114
Figure 2953 Incoming Handover Queuing Expires .............. 3116
Figure 2954 Releasing Instance during Queuing................. 3116
Figure 2960 MSC-Controlled Incoming Handover Attempt ... 3120
Figure 2961 MSC-Controlled Incoming Handover Failure ..... 3121
Figure 2962 MSC-Controlled Incoming Handover Failure ..... 3122
Figure 2963 MSC-Controlled Incoming Handover Execution .. 3122
Figure 2964 Forced Release Attempt ................................ 3123
Figure 2965 Forced Release Execution .............................. 3124
Figure 2966 Queuing Attempt ......................................... 3125
Figure 2968 Forced Handover Attempt.............................. 3127
Figure 2969 MSC-Controlled Forced Handover Execution ..... 3128
Figure 2970 MSC-Controlled Incoming Handover Success.... 3129
3310
Figures

Figure 2979 Local Switch Establishment Request ............... 3136
Figure 2982 Returning Normal Call Request during
Handover ..................................................... 3138
Figure 2983 Forcedly Returning Normal Call from Local
Switch.......................................................... 3138
Figure 2984 Establishing Local Switch Inside BSC .............. 3139
Figure 2985 Failure of Establishing Local Switch Inside Site .. 3140
Figure 2986 Failure of Establishing Local Switch Inside Site .. 3141
Figure 2987 Responding Time Expires when Establishing
Local Switch Inside Site .................................. 3141
Figure 2988 Responding Time Expires when Establishing
Local Switch Inside Site .................................. 3142
Figure 2989 Process of Returning Normal Call from Local
Switch (TC Is Internal) ................................... 3144
Figure 2990 Process of Returning Normal Call from Local
Switch (TC Is Internal) ................................... 3144
Figure 2991 Failure of Returning Normal Call from Local
Switch (TC Is External)................................... 3145
Figure 2992 Failure of Returning Normal Call from Local
Switch (TC Is External)................................... 3145
Figure 2993 Number of First Attempt to Contact Distant
Partner After TFO Being Enabled ...................... 3148
Figure 2994 Number of Retrying to Contact Distant Partner
After Being Interrupted .................................. 3149
Figure 2995 Number of TFO contacting with distant partner
after first try ................................................. 3150
Figure 2996 Number of TFO Recontacting With Distant
Partner After TFO Being Interrupted ................. 3151
Figure 2997 Number of TFO Establishment After First Try.... 3152
Figure 2998 Number of TFO Reestablishment After Being
Interrupted................................................... 3153
Figure 2999 Number of Synchronization Loss at A-Interface
Resulting in TFO Off 1 .................................... 3154
3311
Figure 3000 Number of Synchronization Loss at A-Interface

Resulting in TFO Off 2 .................................... 3154
3312
Tables
Table 1 Corresponding Relationship between Basic

Measurement Counters and General
Measurement Counters................................... 3167
3313
3314
Glossary
3G
- The 3rd Generation Mobile Communications
AGCH
- Absolute Grant Channel
ALCAP
- Access Link Control Application Protocol
ATM
- Asynchronous Transfer Mode
BHCA
- Busy Hour Call Attempt
BSC
- Base Station Controller
BSS
- Base Station System
BTS
- Base Transceiver Station
BVC
- BSSGP Virtual Connection
CCCH
- Common Control Channel
CMP
- Calling Main Processor
CPU
- Central Processing Unit
CS
- Circuit Switched
DB
- DataBase
DM
- Delay Measurement
DSP
- Digital Signal Processor
DTAP
- Direct Transfer Application Part
FDD
- Frequency Division Duplex
GPRS
- General Packet Radio Service
GSM
- Global System for Mobile Communication
HR
- Half Rate
3315
IMSI
- International Mobile Subscriber Identity
IP
- Internet Protocol
LAPD
- Link Access Procedure for D-channel
LLC
- Logic Link Control
MAC
- Medium Access Control
MO
- Mobile Originated
MOC
- Mobile Original Call
MS
- Mobile Station
MSC
- Mobile Switching Center
MSU
- Message Signal Unit
MT
- Mobile Terminated
MTC
- Mobile Terminated Call
NACC
- Network Assisted Cell Change
NSE
- Network Service Entity
NSVC
- Network Service Virtual Connection
OMC-R
- Operations& Maintenance Center-Radio
PACCH
- Packet Associated Control Channel
PCH
- Paging Channel
PCU
- Packet Control Unit
PDTCH
- Packet Data Traffic Channel
PDU
- Packet Data Unit
PRI
- Primary Rate Interface
PS
- Packet Switched
3316
Glossary
PSI
- PCF Session Identity
PSK
- Phase Shift Keying
QoS
- Quality of Service
RLC
- Radio Link Control
RMM
- RF Management Module
RMM is the control centre of RFS. It works on a 1+1 standby
mode.The clock reference is also provided by the RMM.
RR
- Resource Record
SACCH
- Slow Associated Control Channel
SAPI
- Service Access Point Identifier
SCCP
- SS7 Signaling Connection Control Part
SCCP
- Signaling Connection Control Part
SDCCH
- Stand alone Dedicated Control Channel
SGSN
- Service GPRS Supporting Node
SIF
- Signaling Information Field
SIO
- Service Information Octet
SM
- Short Message
SMM
- Session Manage Module
SNM
- Signaling Network Management
TCH
- Traffic Channel
TDD
- Time Division Duplex
TDM
- Time Division Multiplexing
TFA
- Transfer Allowed signal
TFC
- Transfer Controlled signal
TFI
- TDM Fiber Interface
3317
TFO
- Tandem Free Operation
TFP
- Transfer Prohibited signal
TRX
- Transmitter and Receiver
TS
- Time Slot
UL
- Uplink
USSD
- Unstructured Supplementary Service Data
eMLPP
- enhanced Multi-Level Precedence and Pre-emption
3318

BSC Performance Counter Reference

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

BSC Performance Counter Reference

Загружено:

Авторское право:

Доступные форматы

ZXG10 iBSC

Base Station Controller

Performance Counter Reference

Serial Number: SJ-20100524164252-015

About This Manual............................................. I

PS Basic Measurement (Cell).............................3

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900040013 Number of EGPRS DL TBF release due to

Confidential and Proprietary Information of ZTE CORPORATION

C900040033 Number of EGPRS UL signaling TBF

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900040054 Number of discarded EGPRS DL signaling

Confidential and Proprietary Information of ZTE CORPORATION

C900040076 Number of discarded GPRS DL LLC frames

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900040096 Number of UL RLC pending blocks in CS3 on

Confidential and Proprietary Information of ZTE CORPORATION

C900040114 Number of EGPRS DL TBF establishment

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900040130 Number of EGPRS UL TBF resource

Confidential and Proprietary Information of ZTE CORPORATION

C900040149 Number of GPRS DL signaling TBF release

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900040169 Number of GPRS DL TBF establishment

Confidential and Proprietary Information of ZTE CORPORATION

C900040189 Number of DL RLC NACK blocks in MCS9 on

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900040209 Number of UL RLC NACK blocks in MCS2 on

Confidential and Proprietary Information of ZTE CORPORATION

C900040235 Accumulated throughput of DL EGPRS

CPU Load Measurement................................. 173

CS Basic Measurement .................................. 175

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900060018 Number of signaling TCH/F assignment

Confidential and Proprietary Information of ZTE CORPORATION

C900060037 Number of data TCH/F assignment

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900060058 Average number of idle TCH/F with

Confidential and Proprietary Information of ZTE CORPORATION

C900060086 Number of TCH/F handover attempts due to

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900060105 Number of incoming handover from

Confidential and Proprietary Information of ZTE CORPORATION

C900060127 TCH/H busy time ...................................... 300

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900060146 Number of TCH/F allocation failure due

Confidential and Proprietary Information of ZTE CORPORATION

C900060163 Number of TCH/F allocation failure due

Confidential and Proprietary Information of ZTE CORPORATION

ZXG10 iBSC Performance Counter Reference

C900060178 Number of TCH/H allocation failure due

Confidential and Proprietary Information of ZTE CORPORATION

C900060191 Number of TCH/H allocation failure due to

Confidential and Proprietary Information of ZTE CORPORATION