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 CORPO-
RATION 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 dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. 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 2012–01–13 Add C901130073–C901130085
R1.3 2011–07–30 Updated to V6.20.614d
R1.2 2011–03–10 Updated to V6.20.614c
R1.1 2010–10–10 Updated to V6.20.614
R1.0 2010–07–20 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 I

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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION V


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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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
X Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION XXIX

C901020050 Number of Kbytes carried by GPRS DL LLC

frame................................................................. 508
Uplink-Downlink RLC Statistic Measure-
ment ............................................................. 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 Confidential and Proprietary Information of ZTE CORPORATION

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 Measure-
ment ............................................................. 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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

Radio Resource Availability Measure-
ment ............................................................. 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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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-outer-
circle handover attempts ...................................... 889
C901090109 Number of intra-cell inner-circle-to-outer-
circle handover success ........................................ 889
C901090110 Number of intra-cell outer-circle-to-inner-
C901090111 Number of intra-cell outer-circle-to-inner-
C901090112 Number of intra-cell inner-circle-to-inner-
C901090113 Number of intra-cell inner-circle-to-inner-
C901090114 Number of intra-cell outer-circle-to-outer-
Confidential and Proprietary Information of ZTE CORPORATION XLIX

C901090115 Number of intra-cell outer-circle-to-outer-

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
L Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 fail-
ure 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 Confidential and Proprietary Information of ZTE CORPORATION

connection for UL TBF establishment .................... 1310
C901180032 Number of EGPRS DL TBF resource realloca-
tion failure due to UL TBF establishment ............... 1310
tion 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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 fail-
ure on PACCH due to UPPB-DSP congestion........... 1426
LXXXVI Confidential and Proprietary Information of ZTE CORPORATION

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 realloca-
tion failure due to DL TBF establishment ............... 1437
tion success due to DL TBF establishment ............. 1437
transmission ..................................................... 1437
transmission ..................................................... 1438
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

attempts .......................................................... 1548
success ............................................................ 1549
C901230027 Number of samples with UL RQ = 0 ........... 1549
C901230035 Number of samples with DL RQ = 0........... 1554
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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
C Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

(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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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_ENHANCE-
MEAS_RESULT messages .................................... 1936
C901280033 Number of ABIS_ROUND_TRIP_DELAY_RE-
PORT messages................................................. 1937
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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_AS-
SIGN_CMD messages......................................... 1957
C901280067 Number of ABIS_PACKET_CON-
NECT_FAIL_IND messages .................................. 1958
C901280068 Number of ABIS_PACKET_PRACH_OVER-
LOAD 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_CON-
FIG_CHG messages ........................................... 1961
FIG_CHG_RESP messages .................................. 1962
C901280074 Number of ABIS_PACKET_PIA_DEL_IND
messages ......................................................... 1962
C901280075 Number of ABIS_PACKET_SEND_PIA_IND
messages ......................................................... 1963
FIG_REQ messages............................................ 1964
Confidential and Proprietary Information of ZTE CORPORATION 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_AC-
TIVE_NACK messages ........................................ 1966
C901280081 Number of ABIS_PS_CHANNEL_RELEASE
messages ......................................................... 1967
C901280082 Number of ABIS_PS_CHANNEL_RE-
LEASE_ACK messages ........................................ 1968
C901280083 Number of ABIS_PS_CHANNEL_RE-
LEASE_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 Confidential and Proprietary Information of ZTE CORPORATION

C901280097 Number of ABIS_CCMCONN_CMM_NACK
messages ......................................................... 1978
C901280098 Number ABIS_PACKET_ACCESS_REJ
messages ......................................................... 1978
SIGN_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_AC-
CESS_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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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 Measure-
ment ........................................................... 2105
Overview.................................................................. 2106
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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
sent................................................................. 2143
C901350013 Number of BVC_BLOCK_ACK message
received ........................................................... 2144
sent................................................................. 2144
received ........................................................... 2144
CXXVIII Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 mes-
sages............................................................... 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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 retransmis-
sion ................................................................. 2286
C901420014 RTT is lower than T1................................ 2286
C901420015 RTT is between T1 and T2 ........................ 2287
Confidential and Proprietary Information of ZTE CORPORATION CXXXIX

C901420016 RTT is higher than T2 .............................. 2287

C901420017 Number of network transmission dropped
packets ............................................................ 2287
C901420018 Maximum delay of network transmis-
sion ................................................................. 2288
C901420019 Minimum delay of network transmis-
sion ................................................................. 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 Confidential and Proprietary Information of ZTE CORPORATION

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 reselec-
tion ................................................................. 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
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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Measure-
ment ........................................................... 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION CLIII


C901620049 Number of samples of DL RQ=0 and receive
CLIV Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION CLV


CLVI Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 transmit-
ted .................................................................. 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
C901880013 Number of handover attempts due to a good
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
Confidential and Proprietary Information of ZTE CORPORATION 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 han-
dovers ............................................................. 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 Confidential and Proprietary Information of ZTE CORPORATION

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
C901900005 Number of relocation failures due to no valid
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
Confidential and Proprietary Information of ZTE CORPORATION 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
C901930002 Number of CS Call Denied for Lack of IPAbis
BandWidth DownLink ......................................... 2932
C901930003 Number of PS Call Denied for Lack of IPAbis
BandWidth UpLink ............................................. 2933
C901930004 Number of PS Call Denied for Lack of IPAbis
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 Confidential and Proprietary Information of ZTE CORPORATION

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 Measure-
ment ........................................................... 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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Measure-
ment ........................................................... 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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 Measure-
ment ........................................................... 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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

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
Confidential and Proprietary Information of ZTE CORPORATION 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 Confidential and Proprietary Information of ZTE CORPORATION

About This Manual
Purpose 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.
Intended � System Engineer
Audience
� Testing Engineer
� Planning Engineer
What Is in This This manual contains the following chapters.
Manual
Section Summary
Chapter 1, PS Basic Introduces the detailed information about

Measurement (BSC) counters related to PS basic measurement
(BSC).
Chapter 2, PS Basic Introduces the detailed information about

Measurement (Cell) counters related to PS basic measurement
(Cell).
Chapter 3, CPU Load Introduces the detailed information about

Measurement counters related to CPU load measurement.
Chapter 4, CS Basic Introduces the detailed information about

Measurement counters related to CS basic measurement.
Chapter 5, Configuration Introduces the detailed information about

Management Information counters related to configuration
Basic Measurement management information basic
measurement.
Chapter 6, Downlink Introduces the detailed information about

Data TBF Measurement counters related to downlink data TBF
measurement.
Chapter 7, Uplink Data Introduces the detailed information about

TBF Measurement counters related to uplink data TBF
measurement.
Chapter 8, Data Flow Introduces the detailed information about

Measurement counters related to data flow.
Chapter 9, Uplink- Introduces the detailed information about

Downlink RLC Statistic counters related to uplink/downlink RLC
Measurement statistic measurement.
Chapter 10, PS Introduces the detailed information about

Resource Used Statistic counters related to PS resource used
Measurement statistic measurement.
Chapter 11, Introduces the detailed information about

RMM Assignment counters related to RMM assignment
Measurement measurement.
Confidential and Proprietary Information of ZTE CORPORATION I

Section Summary
Chapter 12, Handover Introduces the detailed information about

Cause Measurement counters related to handover cause
measurement.
Chapter 13, RMM Call Introduces the detailed information

Drop Measurement about counters related to RMM call drop
measurement.
Chapter 14, Radio Introduces the detailed information

Resource Availability about counters related to radio resource
Measurement availability measurement.
Chapter 15, General Introduces the detailed information about

Handover Measurement counters related to general handover
measurement.
Chapter 16, Adjacent Cell Introduces the detailed information about

Handover Measurement counters related to adjacent cell handover
measurement.
Chapter 17, Radio Access Introduces the detailed information

Measurement about counters related to radio access
measurement.
Chapter 18, Radio Introduces the detailed information about

Measurement counters related to radio measurement.
Chapter 19, Sub Cell Introduces the detailed information about

Statistics counters related to sub cell statistics.
Chapter 20, MS TA Introduces the detailed information about

Measurement counters related to MS TA measurement.
Chapter 21, SAPI3 Introduces the detailed information about

Measurement counters related to SAPI3 measurement.
Chapter 22, Uplink Introduces the detailed information about

and Downlink PACCH counters related to uplink and downlink
Statistics PACCH statistics.

GPRS data TBF Statistics counters related to downlink GPRS data
TBF statistics.

EGPRS data TBF counters related to downlink EGPRS data
Statistics TBF statistics.
Chapter 25, Uplink GPRS Introduces the detailed information about

data TBF Statistics counters related to uplink GPRS data TBF
statistics.
Chapter 26, Uplink Introduces the detailed information about

EGPRS Data TBF counters related to uplink EGPRS data TBF
Statistics statistics.
Chapter 27, BSSGP Flow Introduces the detailed information about

Statistics counters related to BSSGP flow statistics.
Chapter 28, TRX Introduces the detailed information about

Measurement counters related to TRX measurement.
II Confidential and Proprietary Information of ZTE CORPORATION

About This Manual
Section Summary
Chapter 29, Gb Interface Introduces the detailed information about

Message Statistics counters related to Gb interface message
statistics.
Chapter 30, Timeslot Introduces the detailed information about

Measurement counters related to timeslot measurement.
Chapter 31, SDCCH Introduces the detailed information about

Measurement counters related to SDCCH measurement.
Chapter 32, TCH/F Introduces the detailed information about

Measurement counters related to TCH/F measurement.
Chapter 33, TCH/H Introduces the detailed information about

Measurement counters related to TCH/H measurement.
Chapter 34, Abis Introduces the detailed information about

Interface Message counters related to Abis interface message
Counter Measurement counter measurement.
Chapter 35, Gb Message Introduces the detailed information about

Statistics (BVC Cell) counters related to Gb interface message
statistics (BVC cell).
Chapter 36, NSVC Introduces the detailed information

Statistic Measurement about counters related to NSVC statistic
measurement.
Chapter 37, NSE Statistic Introduces the detailed information

Measurement about counters related to NSE statistic
measurement.
Chapter 38, BTS TRX Introduces the detailed information about

Measurement counters related to BTS TRX measurement.
Chapter 39, NSVC on Introduces the detailed information about

IPGB HOST Measurement counters related to NSVC on IPGB HOST
measurement.
Chapter 40, GB Introduces the detailed information about

Message on IPGB HOST counters related to GB message on IPGB
Measurement HOST measurement.
Chapter 41, NSE on IPGB Introduces the detailed information about

HOST Measurement counters related to NSE on IPGB HOST
measurement.
Chapter 42, BSSMAP Introduces the detailed information about

Message Measurement counters related to BSSMAP message
measurement.
Chapter 43, A-Interface Introduces the detailed information about

Message Measurement counters related to A-Interface message
measurement.
Chapter 44, Terrestrial Introduces the detailed information about

Resource Availability counters related to terrestrial resource
Measurement availability measurement.
Chapter 45, Ater Introduces the detailed information

Message Measurement about counters related to Ater message
measurement.
Confidential and Proprietary Information of ZTE CORPORATION III

Section Summary
Chapter 46, MTP2 Introduces the detailed information about

Signaling Link counters related to MTP2 signaling link
Chapter 47, CPU/MEM Introduces the detailed information

Measurement about counters related to CPU/MEM
measurement.
Chapter 48, SCTP AS Introduces the detailed information about

Measurement counters related to SCTP AS measurement.
Chapter 49, IP Port Introduces the detailed information about

Performance Statistics counters related to IP port performance
statistics.
Chapter 50, GTRUNK Introduces the detailed information about

Resource Statistics counters related to GTRUNK resource
statistics.
Chapter 51, Other Introduces the detailed information about

Process Statistics counters related to other process statistics.
Chapter 52, FR Carried Introduces the detailed information about

Links Statistics counters related to FR carried links
statistics.
Chapter 53, OMP PS Introduces the detailed information about

Service Statistics counters related to OMP PS service
statistics.
Chapter 54, SNS on OMP Introduces the detailed information about

Statistics counters related to SNS on OMP statistics.
Chapter 55, IPGB Introduces the detailed information about

StrongARM NSVC counters related to IPGB StrongARM NSVC
Chapter 56, IPGB Introduces the detailed information about

StrongARM Gb Statistics counters related to IPGB StrongARM Gb
statistics.
Chapter 57, Queue Introduces the detailed information about

Measurement counters related to queue measurement.
Chapter 58, Handover Introduces the detailed information

Synchronization Mode about counters related to handover
Measurement synchronization mode measurement.
Chapter 59, Paging Introduces the detailed information about

Message Measurement counters related to paging message
measurement.
Chapter 60, Reserved Introduces the detailed information about

Channel Measurement counters related to reserved channel
measurement.
Chapter 61, SCCP Introduces the detailed information about

Connection Measurement counters related to SCCP connection
measurement.
Chapter 62, DTM Cell Introduces the detailed information about

Measurement counters related to DTM cell measurement.
IV Confidential and Proprietary Information of ZTE CORPORATION

About This Manual
Section Summary
Chapter 63, LAPD Introduces the detailed information about

Measurement counters related to LAPD measurement.
Chapter 64, LCS Introduces the detailed information about

Measurement counters related to LCS measurement.
Chapter 65, LB Global Introduces the detailed information about

Message Measurement counters related to LB global message
measurement.
Chapter 66 Ater Interface Introduces the detailed information about

Relays Measurement counters related to Ater interface relays
measurement.

Ater Interface counters related to Ater interface SCCP
SCCP Connections connections measurement.
Measurement

Measurement counters related to measurement report
Report Serving Cell serving cell measurement.
Measurement

Measurement Report counters related to measurement report
Adjacent Cell adjacent cell measurement.
Measurement
Chapter 70, TRX Paging Introduces the detailed information

Measurement about counters related to TRX paging
measurement.
Chapter 71, TRX Introduces the detailed information about

Temperature Power counters related to TRX temperature power
Chapter 72, Terminal Introduces the detailed information

Ability Statistics about counters related to terminal ability
statistics.

Signaling Link Statistics counters related to MTP3 signaling link
statistics.
Chapter 74, M3UA Introduces the detailed information about

Performance Statistics counters related to M3UA performance
statistics.
Chapter 75, SCCP Introduces the detailed information about

Performance Statistics counters related to SCCP performance
statistics.

Signaling Link Set counters related to MTP3 signaling link set
Chapter 77, M3UA Error Introduces the detailed information about

Statistics counters related to M3UA error statistics.
Confidential and Proprietary Information of ZTE CORPORATION V

Section Summary
Chapter 78, M3UA AS Introduces the detailed information about

Performance Statistics counters related to M3UA AS performance
statistics.
Chapter 79, Timer Introduces the detailed information about

Statistics counters related to timer statistics.
Chapter 80, Scheduling Introduces the detailed information about

Performance Statistics counters related to scheduling performance
statistics.
Chapter 81, UB Memory Introduces the detailed information

Performance Statistics about counters related to UB memory
performance statistics.
Chapter 82, Hardware Introduces the detailed information about

and FLASH Performance counters related to hardware and FLASH
Statistics performance statistics.
Chapter 83, SCTP Introduces the detailed information about

Protocol Stack Statistics counters related to SCTP protocol stack
statistics.
Chapter 84, SCTP Introduces the detailed information about

Association ULP Statistics counters related to SCTP association ULP
statistics.
Chapter 85, SDTB Fiber Introduces the detailed information about

Performance Statistics counters related to SDTB fiber performance
statistics.
Chapter 86, PEB22554 Introduces the detailed information

E1 Performance Statistics about counters related to PEB22554 E1
Chapter 87, PEB22554 Introduces the detailed information

T1 Performance Statistics about counters related to PEB22554 T1
Chapter 88, MAC Port Introduces the detailed information about

Flow Statistics counters related to MAC port flow statistics.
Chapter 89, AMR Rate Introduces the detailed information about

Statistics counters related to AMR rate statistics.
Chapter 90, PPP channel Introduces the detailed information

measurement about counters related to PPP channel
measurement.
Chapter 91, UMAC Introduces the detailed information about

Measurement counters related to UMAC measurement.
Chapter 92, PS Handover Introduces the detailed information about

Cause Measurement counters related to PS handover cause
measurement.
Chapter 93, PS General Introduces the detailed information about

Handover Measurement counters related to PS general handover
measurement.
Chapter 94, IURG Introduces the detailed information about

Measurement counters related to IURG measurement.
VI Confidential and Proprietary Information of ZTE CORPORATION

About This Manual
Section Summary
Chapter 95, RTCP Introduces the detailed information about

Measurement counters related to RTCP measurement.
Chapter 96, DSP Introduces the detailed information about

Measurement counters related to DSP measurement.
Chapter 97, Access Introduces the detailed information

Control Measurement about counters related to access control
measurement.
Chapter 98, Power Introduces the detailed information

Control Measurement about counters related to power control
measurement.
Chapter 99, PS Introduces the detailed information about

Adjacent Cell Handover counters related to PS adjacent cell
Measurement handover measurement.
Chapter 100, LAPDm Introduces the detailed information about

Measurement counters related to LAPDm measurement.
Chapter 101, Access Introduces the detailed information about

Control Detailed Cause counters related to access control detailed
Measurement cause measurement.
Chapter 102, BSC Group Introduces the detailed information about

Call Setup Measurement counters related to BSC group call setup
measurement.
Chapter 103, VGCS Introduces the detailed information about

Measurement counters related to VGCS measurement.
Chapter 104, VBS Introduces the detailed information about

Measurement counters related to VBS measurement.
Chapter 105, eMLPP Introduces the detailed information about

Measurement counters related to eMLPP measurement.
Chapter 106, Flow Introduces the detailed information

Control Measurement about counters related to flow control
measurement.
Chapter 107, SDCCH Introduces the detailed information

General Handover about counters related to SDCCH general
Measurement handover measurement.
Chapter 108, Local Introduces the detailed information

Switch Measurement about counters related to local switch
measurement.
Chapter 109, TFO Introduces the detailed information about

Measurement counters related to TFO Measurement.
Chapter 110, IP SLA PD Introduces the detailed information about

Statistic counters related to IP SLA PD Statistic.
Confidential and Proprietary Information of ZTE CORPORATION VII

This page is intentionally blank.
VIII Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
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 FR accumulates all the bytes received from Gb interface BRCH.
Point
Unit Byte
bytes sent to data link
Description This counter counts the total number of bytes sent from all BRCHs
on FR sub-layer.
Confidential and Proprietary Information of ZTE CORPORATION 1

Usage This counter is used to find out the bytes sent from BRCH and to
observe BSC load status.
Measurement FR accumulates all the bytes sent from Gb interface BRCH.
Point
Unit Byte
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2
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 con-
trol 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 establish-
ment ...............................................................................16
C900040008 Number of GPRS DL data TBF establish-
ment ...............................................................................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 con-
trol plane .........................................................................20
C900040013 Number of EGPRS DL TBF release due to in-
stance suspension .............................................................21
C900040014 Number of EGPRS DL TBF release due to inner
abnormal .........................................................................21
C900040015 Number of EGPRS DL signaling TBF establish-
ment ...............................................................................22
C900040016 Number of EGPRS DL data TBF establish-
ment ...............................................................................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 suc-
cess 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 con-

trol 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 establish-
ment ...............................................................................27
C900040026 Number of GPRS UL data TBF establish-
ment ...............................................................................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 con-
trol plane .........................................................................32
C900040031 Number of EGPRS UL TBF release due to in-
stance suspension .............................................................32
C900040032 Number of EGPRS UL TBF release due to inner
abnormal .........................................................................33
C900040033 Number of EGPRS UL signaling TBF establish-
ment ...............................................................................33
C900040034 Number of EGPRS UL data TBF establish-
ment ...............................................................................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 re-
lease 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 re-
lease 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 re-
ceived 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 EG-
PRS 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 re-
quests .............................................................................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 re-
quest ...............................................................................98
C900040128 Number of EGPRS UL TBF establishment re-
quests .............................................................................99
C900040129 Number of EGPRS UL TBF establishment failure
C900040130 Number of EGPRS UL TBF resource reallocation
requests due to DL TBF establishment ................................ 100
tion failure of channel allocation due to DL TBF establish-
ment ............................................................................. 101
requests due to LLC transmission....................................... 102
failure of channel allocation due to LLC transmission ............ 102
requests for resource request............................................ 103
tion failure due to database allocation failure for resource re-
quest ............................................................................. 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
quests before T3192 expiration ......................................... 110
C900040146 Number of EGPRS DL TBF establishment using
existing DL TBF resource .................................................. 111


quests on PACCH............................................................. 112
quests 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 re-
lease 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 re-
lease by control plane ...................................................... 120
to instance suspension ..................................................... 120
to inner abnormal............................................................ 121
C900040159 Number of GPRS UL TBF establishments in re-
lease state...................................................................... 122
C900040160 Number of GPRS UL TBF establishment with ex-
isting 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 re-
lease state...................................................................... 125
C900040164 Number of EGPRS UL TBF establishment with
existing UL resource ........................................................ 126
quests on PACCH............................................................. 127
quests on CCCH/PCCCH.................................................... 127
C900040167 Number of dynamic PDCH preemption for CS
service ........................................................................... 128
on CCCH/PCCCH.............................................................. 129
on PACCH....................................................................... 129
quests 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.

C900040001 Number
of GPRS DL TBF
establishment success
on PACCH
Description This counter counts the number of successful DL GPRS TBF estab-
lishments on the UL/DL GPRS TBF PACCH.
Measurement When the DL GPRS TBF is established on the UL/DL GPRS TBF
Point 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


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 When the N3105 counter value exceeds N3105Max, this counter
Point increments. The measurement point is A1, as shown in Figure 4.

FIGURE 4 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RELEASE

DUE TO N3105 OVERFLOW
Unit 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 re-
leased abnormally.

Measurement The measurement point is A1, as shown in Figure 5.

Point
DUE TO OTHER REASONS
Unit 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 When the user plane receives the release request from the control
Point plane, this counter increments. The measurement point is A, as
shown in Figure 6.
FIGURE 6 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF FORCING

RELEASE BY CONTROL PLANE

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 When the DL block assigning timer expires, this counter incre-
Point ments. The measurement point is A, as shown in Figure 7.

DUE TO INSTANCE SUSPENSION
Unit 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

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

Measurement During the DL TBF transmission, if the message fails to be sent
Point at the radio interface, the RLC instance fails to be created, or the
resource reassignment fails, this counter increments.
Unit 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 up-
date.
Measurement When the DL TBF is created successfully and the TBF type is GPRS
Point signaling TBF, the counter increments. The measurement point is
similar to those of C900040001 and C901000014.
Unit Times
C900040008 Number
of GPRS DL data TBF
establishment
This counter counts the number of establishments of GPRS DL TBF
for user data (no-UL-signaling) transmission.
Measurement When the DL TBF is created successfully and the TBF type is GPRS
Point data TBF, the counter increments. The measurement point is sim-
ilar to those of C900040001 and C901000014.
Unit Times

C900040009 Number
of EGPRS DL TBF
on PACCH
Description This counter counts the number of successful DL EGPRS TBF es-
tablishments on the UL/DL EGPRS TBF PACCH.
Measurement When the DL EGPRS TBF is established on the UL/DL EGPRS TBF
Point 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


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 abnor-
mally.
Point increments. The measurement point is A1, as shown in Figure 11.

FIGURE 11 MEASUREMENT POINT OF NUMBER OF EGPRS DL TBF RELEASE

Unit 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 re-
leased abnormally.


Point
Unit 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
shown in Figure 13.
FIGURE 13 MEASUREMENT POINT 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.
Point ments. The measurement point is A1, as shown in Figure 14.

Unit 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

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

Measurement During the DL TBF transmission, if the message fails to be sent
Point at the radio interface, the RLC instance fails to be created, or the
resource reassignment fails, this counter increments.
Unit Times
EGPRS DL signaling TBF
establishment
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 When the DL TBF is created successfully and the TBF type is sig-
Point naling TBF, the counter increments. The measurement point is
similar to those of C900040001 and C901000014.
Unit Times
EGPRS DL data TBF
establishment
This counter counts the number of establishments of EGPRS DL
TBF for user data (no-UL-signaling) transmission.
Measurement When the DL TBF is created successfully and the TBF type is data
Point TBF, the counter increments. The measurement point is similar to
those of C900040001 and C901000014.
Unit Times

C900040017 Average
number of GPRS DL TBF
simultaneous establishment
Description This counter counts the average number of DL GPRS TBF estab-
lishments in a cell.
Measurement The counter acquires the measurement value regularly. The num-
Point ber 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 estab-
lishments in a cell.
Measurement The counter acquires the measurement value regularly. The num-
Point ber 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 estab-
lishments on PACCH

Measurement The measurement point is A, as shown in Figure 15.

Point
FIGURE 15 MEASUREMENT POINT OF NUMBER OF GPRS UL DATA TBF
ESTABLISHMENT SUCCESS ON PACCH
Unit Times
GPRS UL TBF release due
to N3101 overflow
Description After the UL TBF is established, MS will transmit data on the BSS-
assigned 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 The measurement point is N3101 overflow, as A shown in Figure
Point 16.
FIGURE 16 MEASUREMENT POINT OF NUMBER OF GPRS UL TBF RELEASE

Unit Times

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.
Measurement The measurement point is N3103 overflow, as A shown in Figure
Point 17.

Unit 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 The measurement point is arrival of the release request, as A
Point shown in Figure 18.

FIGURE 18 MEASUREMENT POINT OF NUMBER OF GPRS UL TBF FORCING

Unit 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.
TBF due to suspension of the instance.
Measurement The measurement point is that UPPB detects suspension of the
Point instance, as A shown in Figure 19.

Unit Times
to inner abnormal
Description TBF is abnormally released due to UPPB internal error.


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

Unit 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 es-
tablishments.
Measurement The measurement point is that UPPB access type is signaling TBF.
Point 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.

FIGURE 21 UL TBF FLOW OF 1-STEP ACCESS

Unit Times
C900040026 Number
of GPRS UL data TBF
establishment
TBF and data TBF.
Usage The counter counts the number of GPRS UL data TBF link estab-
lishments.
Measurement The measurement point is when UPPB access type is data TBF. For
Point example, the TBF type is detected as DATA_TBF, as A1 shown in
Figure 23.

Unit Times
C900040027 Number
of EGPRS UL TBF
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 EGPRS UL TBF es-
tablishments on PACCH.
Point
FIGURE 24 MEASUREMENT POINT OF NUMBER OF EGPRS UL TBF
ESTABLISHMENT SUCCESS ON PACCH
Unit Times
EGPRS UL TBF release due
to N3101 overflow
UL TBF.
Usage The counter counts the number of abnormal releases of EGPRS UL
Measurement The measurement point is when N3101 overflow.
Point
Unit Times
to N3103 overflow


Measurement The measurement point is when N3103 overflow.
Point
Unit Times
EGPRS UL TBF forcing
Usage The counter counts the number of forced releases of EGPRS UL
TBF due to release request from the control plane.
Measurement The measurement point is arrival of the release request.
Point
Unit Times
TBF due to suspension of the instance.
Point instance.
Unit Times

to inner abnormal
TBF due to internal error.
Measurement The measurement point is abnormal UPPB suspension.
Point
Unit Times
EGPRS UL signaling TBF
establishment
TBF and data TBF.
Usage The counter counts the number of EGPRS UL signaling TBF link
establishments.
Measurement The measurement point is that UPPB access type is signaling TBF.
Point
Unit Times
EGPRS UL data TBF
establishment
TBF and data TBF.
Usage The counter counts the number of EGPRS UL data TBF link estab-
lishments.
Measurement The measurement point is that UPPB access type is data TBF.
Point
Unit Times

C900040035 Average
number of GPRS UL TBF
Description There may be more than one TBF in the system during the sam-
pling period. Average number of uplink GPRS TBF establishing
simultaneously = Number of UL GPRS TBFs established simulta-
neously in the sampling period / Times of sampling
Usage This counter counts the average number of UL GPRS TBF estab-
lishing simultaneously.
Measurement When UPPB receives the message informing UL GPRS TBF estab-
Point lishment, the number of TBFs is refreshed and the times of sam-
pling accumulates.
Unit Times
C900040036 Average
number of EGPRS UL TBF
Description There may be more than one TBF in the system during the sam-
pling period. Average number of uplink EGPRS TBF establishing
simultaneously = Number of UL EGPRS TBFs established simulta-
neously in the sampling period / Times of sampling
Usage This counter counts the average number of UL EGPRS TBF estab-
lishing simultaneously.
Measurement When UPPB receives the message informing UL EGPRS TBF es-
Point tablishment, the number of TBFs is refreshed and the times of
sampling accumulates.
Unit Times

release due to N3101
overflow
UL TBF.
Usage The counter counts the number of abnormal releases of GPRS sig-
naling UL TBF due to N3101 overflow.
Measurement The measurement point is N3101 overflow.
Point
Unit Times
overflow
naling UL TBF due to N3103 overflow.
Point
Unit Times

forcing release by control
plane
Usage The counter counts the number of forced releases of GPRS signal-
ing UL TBF due to release request from the control plane.
Point
Unit Times
release due to instance
suspension
naling UL TBF due to suspension of the instance.
Point instance.
Unit Times
C900040041 Number
of GPRS UL signaling
TBF release due to inner
abnormal

naling UL TBF due to internal error.
Point
Unit Times
overflow
UL TBF.
Usage The counter counts the number of abnormal releases of EGPRS
signaling UL TBF due to N3101 overflow.
Point
Unit Times
overflow
signaling UL TBF due to N3103 overflow.
Point
Unit Times

plane
Usage The counter counts the number of forced releases of EGPRS sig-
naling UL TBF due to release request from the control plane.
Point
Unit Times
suspension
signaling UL TBF due to suspension of the instance.
Point instance.
Unit Times
C900040046 Number
of EGPRS UL signaling
abnormal


signaling UL TBF due to internal error.
Point
Unit Times
EGPRS DL LLC frames
Description 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.
Usage The counter counts the number of EGPRS DL LLC frames.
Point
FIGURE 25 MEASUREMENT POINT OF NUMBER OF EGPRS DL LLC FRAMES
Unit 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 mes-
sage to SGSN.
Usage The counter counts the number of discarded EGPRS DL LLC frames
due to buffer overflow.


Point
FIGURE 26 MEASUREMENT POINT OF NUMBER OF DISCARDED EGPRS DL
LLC FRAMES DUE TO BUFFER OVERFLOW
Unit Times
frames due to life time
expiration
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.
Point
LLC FRAMES DUE TO LIFE TIME EXPIRATION
Unit Times

frames due to other reasons
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.
Point
LLC FRAMES DUE TO OTHER REASONS
Unit Times
C900040051 Number of DL
signaling LLC frames
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.


Point
FIGURE 29 MEASUREMENT POINT OF NUMBER OF DL SIGNALING LLC
FRAMES
Unit Times
discarded EGPRS DL
signaling LLC frames due to
buffer overflow
UPPB fails to acquire buffer, then it will send the LLC Discard mes-
sage to SGSN.
Usage The counter counts the number of discarded EGPRS DL signaling
LLC frames due to buffer overflow.
Point
SIGNALING LLC FRAMES DUE TO BUFFER OVERFLOW
Unit Times

discarded EGPRS DL
life time expiration
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.
Point
SIGNALING LLC FRAMES DUE TO LIFE TIME EXPIRATION
Unit Times
discarded EGPRS DL
other reasons
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 sig-
naling LLC frames due to other reasons than the above two in
C900040052 and C900040053.


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 accord-
ing to given Abis bandwidth.
Measurement During the DL PCU frame transmission, if the number of Abis TSs
Point 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 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 The counter counts the bytes of effective upper layer protocol data
sent on DL PDCH.
Point
FIGURE 33 MEASUREMENT POINT OF TOTAL BYTES OF EFFECTIVE UPPER
LAYER PROTOCOL DATA SENT ON DL PDCH
Unit Byte
Related Features 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 The counter counts the bytes of effective upper layer protocol data
received on UL PDCH.
Point
FIGURE 34 MEASUREMENT POINT OF TOTAL BYTES OF EFFECTIVE UPPER
LAYER PROTOCOL DATA RECEIVED ON UL PDCH
Unit Byte

Related Features ZGB-06-01-005 BSC Supervision
C900040058 Bytes of LLC

frame on GPRS UL data
TBF
Usage The counter counts the bytes carried by GPRS UL data TBF LLC
frame.
Point
FIGURE 35 MEASUREMENT POINT OF BYTES OF LLC FRAME ON GPRS UL
DATA TBF
Unit Byte
C900040059 Duration of
GPRS UL data TBF
Description 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 ex-
tended uplink status is subtracted.
Usage The counter counts the duration of GPRS UL data TBF.
Measurement The duration lasts from UPPB’s reception of UL TBF establishment
Point 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.

FIGURE 36 MEASUREMENT POINT OF DURATION OF GPRS UL DATA TBF
FIGURE 37 MEASUREMENT POINT OF DURATION OF GPRS UL DATA TBF

(EXTENDED UL TBF)

Unit ms

frame on GPRS DL data
TBF
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 The counter counts the bytes of LLC frame on GPRS DL data TBF.
Point
FIGURE 38 MEASUREMENT POINT OF BYTES OF LLC FRAME ON GPRS DL
DATA TBF
Unit Byte
GPRS DL data TBF
Description The duration lasts from BSS’s reception of the DL TBF estab-
lishment 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.
Usage The counter counts the duration of GPRS DL data TBF.
Measurement The counter starts counting when UPPB receives DL TBF establish-
Point ment request until BSS finishes sending all current data and MS

returns acknowledgement response for all. During the delay, af-

ter 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 measure-
ment point is A and B, as shown in Figure 39.
FIGURE 39 MEASUREMENT POINT OF DURATION OF GPRS DL DATA TBF
Unit 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 re-
sult is the number of data blocks.
Usage The counter counts the number of effective data blocks received
on GPRS UL TBF.


Point
FIGURE 40 MEASUREMENT POINT OF NUMBER OF EFFECTIVE DATA BLOCKS
RECEIVED ON GPRS UL TBF
Unit Times
Related Features ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode
NACK blocks received on
GPRS UL TBF
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 Then counter increments when BSS correctly receives a NACK
Point block. The measurement point is A, as shown in Figure 41.
FIGURE 41 MEASUREMENT POINT OF NUMBER OF NACK BLOCKS RECEIVED

ON GPRS UL TBF
Unit 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 re-
ceives 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 Then counter increments when Packet DownLink Ack/EGPRS
Point 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 Times
NACK blocks sent on GPRS
DL TBF

Usage The counter counts the number of NACK blocks sent on GPRS DL
TBF.
Measurement Then counter increments when Packet DownLink Ack/EGPRS
Point Packet Downlink Ack indicates that MS fails to receive the RLC
block. The measurement point is A2, as shown in Figure 43.
FIGURE 43 MEASUREMENT POINT OF NUMBER OF NACK BLOCKS SENT ON

GPRS DL TBF
Unit Times

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


Point
FIGURE 44 MEASUREMENT POINT OF BYTES OF LLC FRAME ON EGPRS
UL DATA TBF
Unit Byte
EGPRS UL data TBF
Description 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 ex-
tended uplink status is subtracted.
Usage The counter counts the duration of EGPRS UL data TBF.
Measurement The duration lasts from UPPB’s reception of UL TBF establishment
Point request to transmission of Packet Uplink Ack with FAI=1. The mea-
surement point is A, as shown in Figure 45. For extended UL TBF,
the measurement point is A and B, as shown in Figure 46.
FIGURE 45 MEASUREMENT POINT OF DURATION OF EGPRS UL DATA TBF

FIGURE 46 MEASUREMENT POINT OF DURATION OF EGPRS UL DATA TBF

(EXTENDED UL TBF)
Unit ms

frame on EGPRS DL data
TBF
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 The counter counts the bytes of LLC frame on EGPRS DL data TBF.


Point
FIGURE 47 MEASUREMENT POINT OF BYTES OF LLC FRAME ON EGPRS
DL DATA TBF
Unit Byte
EGPRS DL data TBF
Description The duration lasts from BSS’s reception of the DL TBF estab-
lishment 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.
Usage The counter counts the duration of EGPRS DL data TBF.
Measurement The counter starts counting when UPPB receives DL TBF establish-
Point ment request until BSS finishes sending all current data and MS
returns acknowledgement response for all. During the delay, af-
ter 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 measure-
ment point is A and B, as shown in Figure 48.

FIGURE 48 MEASUREMENT POINT OF DURATION OF EGPRS DL DATA TBF
Unit ms
C900040070 Number
of effective data blocks
received on EGPRS UL TBF
blocks and sends them to BSS. Only when BSS receives all these
RLC blocks can it recompose the LLC frame.
Usage The counter counts the number of effective data blocks received
on EGPRS UL TBF.


Point
RECEIVED ON EGPRS UL TBF
Unit Times
NACK blocks received on
EGPRS UL TBF
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 Then counter increments when BSS correctly receives a NACK
Point block. The measurement point is A, as shown in Figure 50.
FIGURE 50 MEASUREMENT POINT OF NUMBER OF NACK BLOCKS RECEIVED

ON EGPRS UL TBF
Unit Times

effective data blocks sent on
EGPRS DL TBF
Usage The counter counts the number of effective data blocks sent on
EGPRS DL TBF.
Measurement The counter increments when Packet DownLink Ack/EGPRS Packet
Point 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 Times
NACK blocks sent on
EGPRS DL TBF

Usage The counter counts the number of NACK blocks sent on EGPRS DL
TBF.
Measurement The counter increments when Packet DownLink Ack/EGPRS Packet
Point Downlink Ack indicates that MS fails to receive the RLC block. The
measurement point is A2, as shown in Figure 52.
FIGURE 52 MEASUREMENT POINT OF NUMBER OF NACK BLOCKS SENT ON

EGPRS DL TBF
Unit 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 The counter is updated when the BSSGP module saves LLC frames.
Point The measurement point is A, as shown in Figure 53.

FIGURE 53 MEASUREMENT POINT OF DOWNLINK GPRS LLC FRAMES
Unit 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.
FIGURE 54 MEASUREMENT POINT OF DISCARDED DOWNLINK GPRS LLC

FRAMES DUE TO BUFFER OVERFLOW
Unit 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.
Point
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.


FRAMES DUE TO OTHER REASONS
Unit 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 If the DL control block sent from BTS to MS is a DL Dummy control
Point block, the counter increments. The measurement point is A, as
shown in Figure 57.
FIGURE 57 MEASUREMENT POINT OF NUMBER OF DL DUMMY CONTROL

BLOCKS ON PACCH
Unit Times

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 trans-
mission mode.
Measurement If the DL control block sent from BTS to MS is an UL Dummy control
Point block, the counter increments. The measurement point is A, as
shown in Figure 58.
FIGURE 58 MEASUREMENT POINT OF NUMBER OF UL DUMMY CONTROL

BLOCKS ON PACCH
Unit 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 When BSC sends a DL control block (except DUMMY block) to MS
Point through BTS, the counter increments. The measurement point is
A, as shown in Figure 59.

FIGURE 59 MEASUREMENT POINT OF NUMBER OF DL RLC BLOCKS ON

PACCH (EXCLUDING DUMMY BLOCK)
Unit Times
Related Features 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 When BSC sends a pending RLC block whose coding method is CS1
Point to MS, the counter increments. The measurement point is A, as
shown in Figure 60.
FIGURE 60 MEASUREMENT POINT OF NUMBER OF DL RLC PENDING BLOCKS

ON PDTCH
Unit Times
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

on PDTCH
Point to MS via BTS, the counter increments. The measurement point is

ON PDTCH
Unit Times
on PDTCH


ON PDTCH
Unit Times
on PDTCH

ON PDTCH
Unit Times

RLC NACK blocks in CS1 on
PDTCH
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 When BSC sends retransmitted RLC block whose coding method
Point is CS1 to MS via BTS, the counter increments. The measurement
point is A, as shown in Figure 64.
FIGURE 64 MEASUREMENT POINT OF NUMBER OF DL RLC NACK BLOCKS

ON PDTCH
Unit Times
PDTCH


ON PDTCH
Unit Times
PDTCH


ON PDTCH
Unit Times
PDTCH

ON PDTCH
Unit Times

RLC new blocks in CS1 on
PDTCH
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 When BSC sends first-transmitted RLC block (with coding method
Point of CS1) to MS via BTS, the counter increments. The measurement
FIGURE 68 MEASUREMENT POINT OF NUMBER OF DL RLC NEW BLOCKS

ON PDTCH
Unit Times
PDTCH


ON PDTCH
Unit Times
PDTCH

ON PDTCH
Unit Times

PDTCH

ON PDTCH
Unit 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.

Usage The counter counts the number of uplink RLC blocks expect DUMMY
blocks received by BSC on PACCH.
Measurement When BSC receives an UL control block (except the DUMMY block)
Point from MS, the counter increments. The measurement point is A, as
shown in Figure 72.
FIGURE 72 MEASUREMENT POINT OF NUMBER OF UL RLC BLOCKS

EXCLUDING DUMMY BLOCKS ON PACCH
Unit Times
on PDTCH
Description After receiving UL data block, BSC decides whether it is retransmit-
ted 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 This counter counts the number of useful UL CS1-coded pending
RLC blocks received by BSC on PDTCH.
Measurement When BSC receives CS1-coded UL pending RLC block, the counter
Point increments. The measurement point is A, as shown in Figure 73.
FIGURE 73 MEASUREMENT POINT OF NUMBER OF UL RLC PENDING BLOCKS

ON PDTCH
Unit Times


on PDTCH

ON PDTCH
Unit Times
on PDTCH


ON PDTCH
Unit Times
on PDTCH

ON PDTCH

Unit Times
PDTCH
This counter counts the number of useful UL CS1-coded retrans-
mitted RLC blocks received on PDTCH.
Usage This counter counts the number of useful UL CS1-coded retrans-
mitted RLC blocks received by BSC on PDTCH.
Measurement When BSC receives CS1-coded UL retransmitted RLC block, the
Point counter increments. The measurement point is A, as shown in
Figure 77.
FIGURE 77 MEASUREMENT POINT OF NUMBER OF UL RLC NACK BLOCKS

ON PDTCH
Unit Times
PDTCH


Figure 78.

ON PDTCH
Unit Times
PDTCH
Figure 79.


ON PDTCH
Unit Times
PDTCH
Figure 80.

ON PDTCH
Unit Times

PDTCH
This counter counts the number of useful UL CS1-coded first-trans-
Usage This counter counts the number of useful UL CS1-coded first-trans-
Measurement When BSC receives CS1-coded UL first-transmitted RLC block, the
Figure 81.
FIGURE 81 MEASUREMENT POINT OF NUMBER OF UL RLC NEW BLOCKS

ON PDTCH
Unit Times
PDTCH


Figure 82.

ON PDTCH
Unit Times
PDTCH
Figure 83.

ON PDTCH
Unit Times

PDTCH
Figure 84.

ON PDTCH
Unit 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 first-
transmitted blocks.

Usage The counter counts the number of data blocks received by UL
PDTCH.
Measurement When MS transmits an UL RLC block to BSC through BTS (including
Point the retransmitted RLC blocks, blocks to be confirmed and the first-
transmitted blocks), this counter increments.
Unit 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 retrans-
mitted 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 When BSC transmits a DL RLC block to BTS (including the retrans-
Point mitted RLC blocks, blocks to be confirmed and the first-transmitted
blocks), this counter increments.
Unit 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 es-
tablish 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 estab-
lishment requests received by PS control plane when BSC attempts
to establish DL GPRS TBFs.
Measurement This counter increments in the following two cases:
Point
� When PS control plane receives a DL TBF establishment request
from PS user plane, this counter increments.

� When UL GPRS TBF exists and DL GPRS TBF is to be estab-

lished, if PS control plane receives the DL assignment message
Unit 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.
Point
� When PS control plane receives the DL TBF establishment re-
quest from PS user plane, it will apply to database for re-
sources. If it fails to obtain the resources, this counter incre-
ments. The measurement point is A, as shown in Figure 85.
FIGURE 85 MEASUREMENT POINT OF ALLOCATION FAILURES AFTER

RECEIVING DL TBF ESTABLISHMENT REQUEST
� 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
counter increments. The measurement point is A, as shown in
Figure 86.


RECEIVING DL TBF ASSIGNMENT MESSAGE
Unit Times
GPRS DL TBF resource
reallocation requests due to
UL TBF establishment
Description The counter counts the number of GPRS DL TBF resource reallo-
cation requests due to UL TBF establishment.
Usage The counter collects information about the frequency of GPRS DL
TBF resource reallocation requests.
Measurement When MS has already established a DL GPRS TBF, if PS control
Point 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 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 es-
tablish an UL TBF on PACCH, PS control plane should apply to data-
base 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 When MS has already established a DL GPRS TBF, if PS control
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

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 When PS control plane receives a resource reallocation request
Point from PS user plane, if the current DL GPRS TBF exists, this counter
increments. The measurement point is A, as shown in Figure 89.

REALLOCATION REQUESTS DUE TO LLC TRANSMISSION
Unit Times
to LLC transmission
Description 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 re-
source allocations during the DL GPRS TBF transmission after PS
control plane receives the resource reallocation request and ap-
plies to database for resources.
Measurement After PS control plane receives a resource reallocation request
Point 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 establish-
ment requests received by control plane. It is the sum of CCCH/PC-
CCH requests (C901180002) and PACCH requests (C901180003).
Usage The counter collects information about the frequency of DL es-
tablishment requests received by the control plane when BSC at-
tempts to establish DL EGPRS TBFs.
Point
� When PS control plane receives a DL TBF establishment request
� When UL EGPRS TBF exists and DL EGPRS TBF is to be estab-
lished, if PS control plane receives the DL assignment message
Unit Times

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 fail-
ures caused by PDCH, Abis, and PCU having no available resource
or in abnormal status.
allocation failures when BSC attempts to establish EGPRS DL TBFs
and RANPS applies to database for resources.
Point
� When PS control plane receives the DL TBF establishment re-
quest from PS user plane, it will apply to database for re-

RECEIVING DL TBF ESTABLISHMENT REQUEST
� When UL EGPRS TBF exists and DL EGPRS TBF is to be es-

tablished, if PS control plane receives the DL TBF assignment
message from PS user plane, it will apply to database for re-


Unit Times
EGPRS DL TBF resource
Description The counter counts the number of EGPRS downlink TBF resource
reallocation requests (concurrent PACCH UL TBF establishment re-
quest).
Usage The counter collects information about the frequency of EGPRS
downlink TBF resource reallocation requests.
Measurement When MS has already established a DL EGPRS TBF, if PS control
in Figure 93.

REALLOCATION REQUESTS DUE TO UL TBF ESTABLISHMENT
Unit Times

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 When MS has already established a DL EGPRS TBF, if PS control

REALLOCATION FAILURE OF CHANNEL ALLOCATION DUE TO UL TBF
ESTABLISHMENT
Unit Times

LLC transmission
LLC frame changes during the DL EGPRS TBF transmission.
reallocation requests received by PS control plane during the DL
EGPRS TBF transmission.
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

source allocations during the DL EGPRS TBF transmission after PS
in Figure 96.

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 re-
quests (C901190002), PCCCH requests (C901190004) and PACCH
requests (C901190006).
requests when MS attempts to establish GPRS services.
Measurement This counter increments in the following three cases:
Point
� 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.
Unit 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 re-
source or in abnormal status.
allocation failures when the system attempts to establish GPRS UL
TBFs.
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
� 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
� When MS has already established a DL GPRS TBF, if PS control

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

FIGURE 99 MEASUREMENT POINT OF ALLOCATION FAILURES (DL GPRS

TBF EXISTS)
Unit 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 When MS has already established an UL GPRS TBF, if PS control
Point 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 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 re-
source reallocation failures of channel allocation caused by failed
DL TBF establishment allocation.
Usage The counter collects information about the frequency of GPRS UL
Measurement When MS has already established an UL GPRS TBF, if PS control

Unit Times

LLC transmission
LLC frame changes during the UL GPRS TBF transmission.
reallocation requests received by PS control plane during the UL
GPRS TBF transmission.
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 During the UL GPRS TBF transmission, because UL/DL LLC frame

source allocations during the UL GPRS TBF transmission after PS
in Figure 103.

TRANSMISSION
Unit 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.
allocation requests received by PS control plane during the UL
GPRS TBF transmission (including 2-step UL access and UL TBF
transmission).
Measurement When PS control plane receives a resource allocation request from
Point PS user plane, this counter increments, as A shown in Figure 104.


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.
source 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.
Point from MS and applies to database for resources, if it fails to ob-
tain the resources, this counter increments, as A shown in Figure
105.
FIGURE 105 FAILING TO REQUEST FOR RESOURCE FROM DATABASE
Unit Times

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 re-
quests (C901200003), PCCCH requests (C901200005) and PACCH
requests (C901200006).
requests when MS attempts to establish EDGE services.
Point
� 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.
Unit 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 re-
source or in abnormal status.
allocation failures when the system attempts to establish EGPRS
UL TBFs.
Point
� When PS control plane receives an EGPRS channel request on
CCCH or an EGPRS Packet channel request on PCCCH from MS,

FIGURE 106 MEASUREMENT POINT OF NUMBER OF EGPRS UPLINK TBF

ESTABLISHMENT CHANNEL ALLOCATION FAILURES
� When MS has already established a DL EGPRS TBF, if PS control

plane receives an UL TBF assignment message from PS user
plane, it will apply to database for resources. If it fails to ob-
tain the resources, this counter increments. The measurement
FIGURE 107 MEASUREMENT POINT OF ALLOCATION FAILURES (DL

GPRS TBF EXISTS)
Unit Times
EGPRS UL TBF resource
Description The counter counts the number of EGPRS UL TBF resource reallo-
cation requests due to DL TBF establishment.
Usage The counter collects information about the frequency of EGPRS UL
Measurement 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 re-
source reallocation failures of channel allocation caused by failed
Usage The counter collects information about the frequency of EGPRS UL
Measurement When MS has already established an UL EGPRS TBF, if PS control

Unit Times

LLC transmission
LLC frame changes during the UL EGPRS TBF transmission.
reallocation requests received by PS control plane during the UL
EGPRS TBF transmission.
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 During the UL EGPRS TBF transmission, because UL/DL LLC frame

source allocations during the UL EGPRS TBF transmission after PS
in Figure 111.

TRANSMISSION
Unit 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.
allocation requests received by PS control plane during the UL
EGPRS TBF transmission (including 2-step UL access and UL TBF
transmission).
Measurement When PS control plane receives a resource allocation request from
Point PS user plane, this counter increments, as A shown in Figure 112.


REALLOCATION REQUESTS FOR RESOURCE REQUEST
Unit Times
for resource request
Description During the UL EGPRS TBF transmission, after receiving the re-
source allocation request from MS, PS control plane applies to
database for resources. This counter counts the number of failed
resource allocations.
source allocations during the UL EGPRS TBF transmission (includ-
ing 2-step UL access and UL TBF transmission) after PS control
plane receives the resource allocation request from MS and ap-
Point from MS and applies to database for resources, if it fails to ob-
tain the resources, this counter increments, as A shown in Figure
113.
FIGURE 113 FAILING TO REQUEST FOR RESOURCE FROM DATABASE
Unit Times

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 The counter's value can be obtained by querying the database
Point when periodic measurement data is reported.
Unit Times
Related Features 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 The counter increments when dynamic PDCH is idle and the data-
Point base starts reclaiming dynamic PDCH.
Unit Times
Related Features ZGO-03-02-002 Enhancement on Channel Allocation
ZGO-03-02-003 Full dynamic channel allocation on Um interface
PDCH used by TBF in each
cell
Description This counter counts the sum of PDCH used by all TBF in the serving
cell.

Usage This counter is used to find out the condition of multi-timeslot al-
location in the serving cell.
Measurement The counter's value can be obtained by querying the database
Point 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.
Point
� Request for database
� Release database
� Report periodic measurement data
Unit 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.
Point
� Request for database
� Release database
� Report periodic measurement data
Unit 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 After the DL GPRS TBF transmits all LLC frames and the DL RLC
Point block with FBI = 1, T3193 is started. During T3193 running,
when BSC receives new LLC frame and sends DL assignment, this
counter increments.
The measurement point is A, as shown in Figure 114.

ESTABLISHMENT REQUESTS BEFORE T3192 EXPIRATION
Unit Times

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 During the UL GPRS TBF transmission, when BSC receives the DL
Point 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 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 re-
quests 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.

Point
ESTABLISHMENT REQUESTS ON PACCH
Unit 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 Under MS’s packet idle status, when BSC sends the request for
Point 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.


ESTABLISHMENT REQUESTS ON CCCH/PCCCH
Unit 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 After the DL EGPRS TBF transmits all LLC frames and the DL RLC
Point block with FBI = 1, T3193 is started. During T3193 running,
when BSC receives new LLC frame and sends DL assignment, this
counter increments.

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 During the UL EGPRS TBF transmission, when BSC receives the DL
Point LLC frame, it uses the existing resource to establish DL GPRS 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 re-
quests control plane for resource.
This counter counts the number of times of requesting control
plane for resource to establish EGPRS DL TBF on PACCH.
Point
ESTABLISHMENT REQUESTS ON PACCH
Unit Times

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 Under MS’s packet idle status, when BSC sends the request for
Point 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

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
Point increments. The measurement point is A1, as shown in Figure
122.
FIGURE 122 MEASUREMENT POINT OF NUMBER OF GPRS DL SIGNALING

TBF RELEASE DUE TO N3105 OVERFLOW
Unit Times

release due to other reasons
Description 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, acti-
vate 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.
Point
Unit 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.

FIGURE 124 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF FORCING

Unit Times
suspension
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.


Unit 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 During the transmission of GPRS signaling DL TBF, if the message
Point fails to be sent at the radio interface, the RLC instance fails to
be created, or the resource reassignment fails, this counter incre-
ments.
Unit Times

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 abnor-
mally.
126.
FIGURE 126 MEASUREMENT POINT OF NUMBER OF EGPRS DL SIGNALING

TBF RELEASE DUE TO N3105 OVERFLOW
Unit Times

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, acti-
vate 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 EG-
PRS signaling DL TBF is released abnormally.
Point
Unit Times

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.

FORCING RELEASE BY CONTROL PLANE
Unit Times
suspension
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.


Unit 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 During the transmission of EGPRS signaling DL TBF, if the mes-
Point sage fails to be sent at the radio interface, the RLC instance fails
to be created, or the resource reassignment fails, this counter in-
crements.
Unit Times

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 con-
sidered:
� 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 The measurement point is A, as shown in Figure 130 and Figure
Point 131.
FIGURE 130 MEASUREMENT POINT ON NUMBER OF GPRS UL TBF

REESTABLISHMENTS IN RELEASED STATE (1)

FIGURE 131 MEASUREMENT POINT ON NUMBER OF GPRS UL TBF

Unit Times
C900040160 Number
of GPRS UL TBF
establishment with existing
UL resource
Description To accelerate TBF establishment, UPPB caches MS’s UL/DL re-
source 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.
Point
FIGURE 132 MEASUREMENT POINT OF GPRS UL TBF ESTABLISHMENTS
WITH EXISTING UL RESOURCE
Unit Times

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 re-
ceiving this request.
Usage This counter records the number of requests for establishing UL
GPRS TBF on PACCH.
Point
ESTABLISHING UL GPRS TBF ON PACCH
Unit 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 When Packet DL Ack message with UL TBF establishment request
Point is received, and the TBF type is EGPRS, the counter increments.
Unit 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 con-
sidered:
� 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 The measurement point is A, as shown in Figure 134 and Figure
Point 135.
FIGURE 134 MEASUREMENT POINT ON NUMBER OF EGPRS UL TBF


FIGURE 135 MEASUREMENT POINT ON NUMBER OF EGPRS UL TBF

Unit Times
C900040164 Number
of EGPRS UL TBF
establishment with existing
UL resource
Description To accelerate TBF establishment, UPPB caches MS’s UL/DL re-
source 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.
Point
FIGURE 136 MEASUREMENT POINT OF EGPRS UL TBF ESTABLISHMENTS
WITH EXISTING UL RESOURCE
Unit 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 re-
ceiving this request.
Usage This counter records the number of requests for establishing UL
EGPRS TBF on PACCH.
Point
ESTABLISHING UL EGPRS TBF ON PACCH
Unit 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 EG-
PRS UL TBF on CCCH/PCCCH.


Point
FIGURE 138 MEASUREMENT POINT OF NUMBER OF EGPRS UL TBF
Unit 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 The counter increments when the following conditions are satis-
Point fied:
� When the service instance is performing CS service but fails to
request for the radio channel
� The database initiates the dynamic PDCH collection
Unit Times

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.
Point
FIGURE 139 MEASUREMENT POINT OF NUMBER OF GPRS UL TBF
Unit 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 When a request is sent to establish DL TBF on PACCH and the TBF
Point type is GPRS, this counter increments.
Unit Times

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 When a request is sent to establish DL TBF on PACCH and the TBF
Point 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 When Packet DL Ack message with UL TBF establishment request
Point is received, and the TBF type is GPRS, this counter increments.
Unit Times
DL RLC pending blocks in
MCS1 on PDTCH


from BSC to MS, with coding method of MCS1.
PDTCH, with coding method of MCS1.
Measurement When BSC sends a pending RLC block whose coding method is
Point MCS1 to MS, the counter increments. The measurement point is
FIGURE 140 MEASUREMENT POINT OF NUMBER OF DL RLC PENDING

BLOCKS ON PDTCH
Unit Times
ZGO-03-05-001 Modulation and Coding Scheme #1~#9
MCS2 on PDTCH
Point MCS2 to MS via BTS, the counter increments. The measurement


BLOCKS ON PDTCH
Unit Times
MCS3 on PDTCH

BLOCKS ON PDTCH
Unit Times

MCS4 on PDTCH
point is A, as shown inFigure 143.

BLOCKS ON PDTCH
Unit Times
MCS5 on PDTCH


BLOCKS ON PDTCH
Unit Times
MCS6 on PDTCH

BLOCKS ON PDTCH
Unit Times

MCS7 on PDTCH

BLOCKS ON PDTCH
Unit Times
MCS8 on PDTCH


BLOCKS ON PDTCH
Unit Times
MCS9 on PDTCH


BLOCKS ON PDTCH
Unit Times
RLC NACK blocks in MCS1
on PDTCH
blocks from BSC to MS, with coding method of MCS1.
sent on PDTCH, with coding method of MCS1.
Measurement When BSC sends retransmitted RLC block whose coding method is

ON PDTCH
Unit Times

on PDTCH

ON PDTCH
Unit Times
on PDTCH


ON PDTCH
Unit Times
on PDTCH

ON PDTCH
Unit Times

on PDTCH

ON PDTCH
Unit Times
on PDTCH


ON PDTCH
Unit Times
on PDTCH


ON PDTCH
Unit Times
on PDTCH

ON PDTCH
Unit Times

on PDTCH

ON PDTCH
Unit Times
RLC new blocks in MCS1 on
PDTCH
RLC blocks from BSC to MS, with coding method of MCS1.
RLC blocks sent by BSC on PDTCH, with coding method of MCS1.

Point of MCS1) to MS via BTS, the counter increments. The measure-
ment point is A, as shown in Figure 158.

ON PDTCH
Unit Times
PDTCH

ON PDTCH
Unit Times

PDTCH

ON PDTCH
Unit Times
PDTCH


ON PDTCH
Unit Times
PDTCH


ON PDTCH
Unit Times
PDTCH

ON PDTCH
Unit Times

PDTCH

ON PDTCH
Unit Times
PDTCH


ON PDTCH
Unit Times
PDTCH

ON PDTCH
Unit Times

UL RLC pending blocks in
MCS1 on PDTCH
This counter counts the number of useful UL MCS1-coded pending
Usage This counter counts the number of useful UL MCS1-coded pending
Measurement When BSC receives MCS1-coded UL pending RLC block, the
Figure 167.
FIGURE 167 MEASUREMENT POINT OF NUMBER OF UL RLC PENDING

BLOCKS ON PDTCH
Unit Times
MCS2 on PDTCH

Figure 168.

BLOCKS ON PDTCH
Unit Times
MCS3 on PDTCH
Figure 169.


BLOCKS ON PDTCH
Unit Times
MCS4 on PDTCH
Figure 170.

BLOCKS ON PDTCH
Unit Times

MCS5 on PDTCH
Figure 171.

BLOCKS ON PDTCH
Unit Times
MCS6 on PDTCH


Figure 172.

BLOCKS ON PDTCH
Unit Times
MCS7 on PDTCH
Figure 173.

BLOCKS ON PDTCH
Unit Times

MCS8 on PDTCH
Figure 174.

BLOCKS ON PDTCH
Unit Times
MCS9 on PDTCH

Figure 175.

BLOCKS ON PDTCH
Unit Times
on PDTCH
This counter counts the number of useful UL MCS1-coded retrans-
Usage This counter counts the number of useful UL MCS1-coded retrans-
Measurement When BSC receives MCS1-coded UL retransmitted RLC block, the
Figure 176.


ON PDTCH
Unit Times
on PDTCH
Figure 177.

ON PDTCH
Unit Times

on PDTCH
Figure 178.

ON PDTCH
Unit Times
on PDTCH


Figure 179.

ON PDTCH
Unit Times
on PDTCH
Figure 180.

ON PDTCH
Unit Times

on PDTCH
Figure 181.

ON PDTCH
Unit Times
on PDTCH

Figure 182.

ON PDTCH
Unit Times
on PDTCH
Figure 183.


ON PDTCH
Unit Times
on PDTCH
Figure 184.

ON PDTCH
Unit Times

PDTCH
This counter counts the number of useful UL MCS1-coded first-
transmitted RLC blocks received on PDTCH.
Usage This counter counts the number of useful UL MCS1-coded first-
transmitted RLC blocks received by BSC on PDTCH.
Measurement When BSC receives MCS1-coded UL first-transmitted RLC block,
Point the counter increments. The measurement point is A, as shown in
Figure 185.

ON PDTCH
Unit Times
PDTCH


Figure 186.

ON PDTCH
Unit Times
PDTCH
Figure 187.

ON PDTCH
Unit Times

PDTCH
Figure 188.

ON PDTCH
Unit Times
PDTCH

Figure 189.

ON PDTCH
Unit Times
PDTCH
Figure 190.


ON PDTCH
Unit Times
PDTCH
Figure 191.

ON PDTCH
Unit Times

PDTCH
Figure 192.

ON PDTCH
Unit Times
PDTCH


Figure 193.

ON PDTCH
Unit Times
C900040232 Accumulated
throughput of UL GPRS TBF
Description This counter counts the total uplink GPRS throughput after the
UPPB board receives uplink data blocks. When the URLC mod-
ule 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.
Usage This counter counts the throughput of uplink GPRS TBF.
Measurement The counter is updated when the URLC module receives uplink data
Point blocks. The measurement point is A, as shown in Figure 194.
FIGURE 194 MEASUREMENT POINT OF UPLINK GPRS TBF THROUGHPUT
Unit kBps * kB

throughput of DL GPRS TBF
Description 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.
Usage This counter counts the throughput of downlink GPRS TBF.
Measurement The counter is updated when the DRLC module receives the Packet
Point DownLink Ack message. The measurement point is A, as shown
in Figure 195.
FIGURE 195 MEASUREMENT POINT OF DOWNLINK GPRS TBF THROUGHPUT
Unit kBps * kB
throughput of UL EGPRS
TBF
Description This counter counts the total uplink EGPRS throughput after the
UPPB board receives uplink data blocks. When the URLC mod-
ule 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.
Usage This counter counts the throughput of uplink EGPRS TBF.
Measurement The counter is updated when the URLC module receives uplink data
Point blocks. The measurement point is A, as shown in Figure 196.

FIGURE 196 MEASUREMENT POINT OF UPLINK EGPRS TBF THROUGHPUT
Unit kBps * kB
throughput of DL EGPRS
TBF
Description 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.
Usage This counter counts the throughput of downlink EGPRS TBF.
Measurement The counter is updated when the DRLC module receives the EGPRS
Point Packet DownLink Ack message. The measurement point is A, as
FIGURE 197 MEASUREMENT POINT OF DOWNLINK EGPRS TBF THROUGHPUT
Unit kBps * kB


Chapter 3
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 After a collection period ends, calculation will be executed accord-
Point ing 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 The measurement point is the peak value of the sampling main
Point processor load during collection period.
Unit Percent


Chapter 4
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 assign-
ment ............................................................................. 184
C900060004 Number of SDCCH seizure success for assign-
ment ............................................................................. 185
C900060005 Number of SDCCH seizure failure for assign-
ment ............................................................................. 186
C900060006 Number of SDCCH seizure attempts for han-
dover............................................................................. 187
C900060007 Number of SDCCH seizure failure for han-
dover............................................................................. 189
C900060008 Number of SDCCH allocation success for assign-
ment ............................................................................. 190
C900060009 Number of SDCCH allocation failure for assign-
ment ............................................................................. 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 as-
signment........................................................................ 202
C900060020 Number of voice TCH/F seizure failure for as-
signment........................................................................ 204
handover........................................................................ 205
C900060022 Number of voice TCH/F seizure failure for han-
dover............................................................................. 208
C900060023 Number of TCH/F allocation success for assign-
ment (speech version1).................................................... 209

C900060024 Number of TCH/F allocation failure due to chan-

nel activation failure for assignment (speech version1) ......... 210
C900060028 Number of voice TCH/F assignment suc-
cess............................................................................... 215
C900060029 Number of voice TCH/F assignment failure for
assignment..................................................................... 216
C900060030 Number of data TCH/F seizure attempts for as-
signment........................................................................ 217
C900060031 Number of data TCH/F seizure failure for assign-
ment ............................................................................. 219
C900060032 Number of data TCH/F seizure attempts for han-
dover............................................................................. 220
C900060033 Number of data TCH/F seizure failure for han-
dover............................................................................. 223
C900060034 Number of data TCH/F allocation success for as-
signment........................................................................ 224
C900060035 Number of data TCH/F allocation failure due to
channel activation failure for assignment ............................ 225
C900060036 Number of data TCH/F assignment suc-
cess............................................................................... 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 as-
signment........................................................................ 234
C900060043 Number of voice TCH/H seizure failure for as-
signment........................................................................ 236
handover........................................................................ 237
C900060045 Number of voice TCH/H seizure failure for han-
dover............................................................................. 240
C900060046 Number of data TCH/H seizure attempts for as-
signment........................................................................ 241
C900060047 Number of data TCH/H seizure failure for assign-
ment ............................................................................. 243
C900060048 Number of data TCH/H seizure attempts for han-
dover............................................................................. 244
C900060049 Number of data TCH/H seizure failure for han-
dover............................................................................. 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 fail-
ure ................................................................................ 251
C900060053 Number of SDCCH drops................................ 253
C900060054 Number of TCH/F drops ................................. 254
C900060055 Number of TCH/H drops................................. 254

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


handover success ............................................................ 273
C900060095 Number of MSC-controlled outgoing hand-
over .............................................................................. 273
C900060096 Number of MSC-controlled outgoing handover
success .......................................................................... 274
handover........................................................................ 275
C900060099 Number of MSC-controlled incoming han-
dover............................................................................. 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 un-
defined layer(GSM900) to current layer (GSM1800) ............. 281
C900060105 Number of incoming handover from undefined
layer (GSM1800) to current layer (GSM900) ....................... 282
defined 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 chan-
nel ................................................................................ 299
C900060126 Average number of unavailable radio chan-
nel ................................................................................ 300

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 fail-
ure ................................................................................ 307
C900060136 Number of MOC access attempts..................... 308
C900060137 Number of wireless access due to paging re-
sponses ......................................................................... 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 mes-
sages............................................................................. 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
nel activation failure for handover(speech version1) ............. 327
connection failure for handover (speech version1)................ 328
nel activation failure for handover(speech version2) ............. 332


nel 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 chan-
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


C900060199 Number of Voice TCH/H assignment suc-
cess............................................................................... 378
C900060200 Number of Voice TCH/H assignment fail-
ure ................................................................................ 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 suc-
cess............................................................................... 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 han-
dover 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 han-
dover 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

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 at-
tempts due to good C/I .................................................... 414
C900060231 Number of TCH/H inter-subcell handover at-
tempts due to bad C/I ...................................................... 414
PBGT ............................................................................. 415
large TA ......................................................................... 416
other reasons.................................................................. 417
C900060235 Number of signaling TCH/H assignment suc-
cess............................................................................... 417
C900060236 Number of MOC access success ...................... 418
C900060237 Number of dual band outgoing handover .......... 419
C900060238 Number of dual band outgoing handover suc-
cess............................................................................... 420
C900060239 Number of dual band incoming handover ......... 421
C900060240 Number of dual band incoming handover suc-
cess............................................................................... 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 evalu-
ate 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.

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 The counter counts when MS requests for channel from BSC and
Point 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 ac-
cess reason is due to MTC). The counter increments when the fol-
lowing two conditions are satisfied:
� MS receives the IMM_ASS message from BSC and successfully
accesses the channel.

� 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 This counter counts when BSC receives the EST_IND message.
Point The measurement point is A4, as shown in Figure 199.
Unit Times
SDCCH seizure attempts for
assignment
Description 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, C900060003 and
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 ac-
cumulate simultaneously.
Usage 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 This counter counts when BSC completes requesting for channel
Point (due to assignment) (C900060004 + C900060005). The measure-
ment point is A1, as shown in Figure 200.
FIGURE 200 IMMEDIATE ASSIGNMENT FLOW
Unit Times
Related Features ZGB-03-02-003 Dynamic Configuration of SDCCH
ZGB-06-01-007 Cell Traffic Statistics
SDCCH seizure success for
assignment
attempts to allocate channel for the request. This counter accu-
mulates when allocation and occupation succeed.
Usage This counter counts the number of successful SDCCH channel oc-
cupations during assignment.
Measurement This counter counts when BSC requests for channel (due to assign-
Point ment) and occupies the channel successfully. The measurement
point is A1, as shown in Figure 201.

Unit Times
SDCCH seizure failure for
assignment
attempts to allocate channel for the request.
� If allocation succeeds but occupation fails, this counter accu-
mulates.
� 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 fail-
ures during assignment.
Measurement This counter counts when BSC requests for channel (due to assign-
Point ment) but fails to occupy the channel. The measurement point is
A1, as shown in Figure 202.

Unit Times
SDCCH seizure attempts for
handover
Description SDCCH channel allocation attempt is activated by the channel re-
quest 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 re-
source.
� 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.


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 BSC completes requesting for channel (due to handover), or BSC
Point 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 Times


ZGO-02-02-004 SDCCH/SDCCH Handover
SDCCH seizure failure for
handover
Description SDCCH channel allocation attempt is activated by the channel re-
quest 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.
source. If the waiting for resource fails, this counter accumu-
lates.
does not change.
Usage This counter counts the number of SDCCH occupation failure.
Measurement BSC requests for channel (due to handover) but fails to occupy
Point the channel, or BSC fails to wait for internal resource. The mea-
surement point is B1 as shown in Figure 205 and C1 as shown in
Figure 206.
FIGURE 205 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER)

FIGURE 206 EXTERNAL HANDOVER FLOW
Unit Times
SDCCH allocation success
for assignment
Description After BSC responds the channel request message to allocate and
occupy SDCCH channel successfully, BSC sends the CHL_ACT mes-
sage to BTS to activate this SDCCH. If the SDCCH is activated suc-
cessfully (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 al-
locations during assignment.
Measurement This counter counts when BSC receives the CHL_ACT_ACK mes-
Point sage from BTS and the cause is assignment. The measurement

Unit Times
SDCCH allocation failure for
assignment
sage to BTS to activate this SDCCH. If channel activation fails due
to receiving channel activation failure message, incorrect chan-
nel 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 fail-
ure during assignment.
Measurement BSC activates SDCCH channel due to assignment, but receives
Point channel activation failure message, incorrect channel activation
response message, T9103 being timeout, channel instance being
released, or channel being forcibly released. The measurement

Unit Times
signaling TCH/F seizure
attempts for assignment
Description This counter counts the number of TCH/F channel occupation at-
tempts during assigning signaling channels, including the number
of occupation success (C901260002) and the number of occupa-
tion failure (C900060011).
Usage After BSC receives the channel request, it attempts to allocate
channel for the request.
� If the request returns that the transceiver is faulty,
� For other cases, C900060010 and C900060011 accumulate si-
multaneously.
Point (due to assignment and the channel is used as signaling channel)
(C901260002 + C900060011). The measurement point is A1, as

Unit Times
Related Features ZGB-03-01-004 Immediate TCH Assignment
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
ZGO-03-02-002 Enhancement on Channel Allocation
failure for assignment
Description This counter counts the number of TCH/F channel occupation fail-
ures during assigning signaling channels.
After BSC receives the channel request, it attempts to allocate
does not change.
Measurement BSC requests for channel (due to assignment and the channel is
Point used as signaling channel) but fails to occupy the channel, or BSC
fails to wait for internal resource. The measurement point is A1,

FIGURE 210 IMMEDIATE ASSIGNMENT OCCUPATION FAILURE FLOW 1
Unit Times
attempts for handover
Description This counter counts the number of TCH/F channel occupation at-
tempts during signaling channel handover, including the number
simultaneously.
source.
� If the waiting for resource fails, C900060012 and
Measurement BSC completes requesting for channel (due to handover and the
Point channel is used as signaling channel), or BSC receives the inter-
nal message of waiting for resource successfully or waiting for re-
source 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)

FIGURE 213 EXTERNAL HANDOVER FLOW (TC IS INTERNAL)
FIGURE 214 EXTERNAL HANDOVER FLOW (TC IS EXTERNAL)
Unit Times
Related Features ZGB-02-02-001 Basic Handover

failure for handover
ures during signaling channel handover.
lates.
does not change.
Measurement 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 Times

signaling TCH/F allocation
success for assignment
Description This counter counts the number TCH/F channel being allocated
successfully during signaling channel assignment.
After BSC responds the channel request message to allocate and
occupy TCH/F channel successfully, BSC sends the CHL_ACT mes-
sage to BTS to activate this TCH/F channel. If the activation suc-
ceeds (that is, when BSC receives the CHL_ACT_ACK message
from BTS), the counter accumulates.
Measurement The counter increments when BSC receives the CHL_ACT_ACK
Point message from BTS, the cause is due to assignment and the
channel is used as signaling channel. The measurement point is
Unit Times
Description This counter counts the number of TCH/F channel allocation fail-
ures 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 BSC activates TCH/F channel due to assignment and uses it as
Point signaling channel, but receives channel activation failure message,
incorrect channel activation response message, T9103 being time-
out, channel instance being released, or channel being forcibly re-
leased. The measurement point is A2, as shown in Figure 218.
FIGURE 218 IMMEDIATE ASSIGNMENT ALLOCATION FAILURE FLOW 2
Unit Times
Description This counter counts the number of TCH/F channel allocation fail-
sage to BTS to activate this TCH/F channel.
released forcibly, this counter will accumulate.
Measurement BSC activates TCH/F channel due to handover and uses it as sig-
Point naling channel, but receives channel activation failure message,
leased.

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 Times
signaling TCH/F assignment
Description This counter counts the number of successful assignments of
TCH/F as signaling channel.
sage 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 accumu-
lates when BSC receives the message correctly.

Measurement For immediate assignment, this counter counts when BSC receives
Point the EST_IND message correctly. The measurement point is A3, as
Unit 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.
Point incorrect EST_IND message or T3101 is timeout. The measure-

FIGURE 222 IMMEDIATE ASSIGNMENT FAILURE FLOW 3
Unit 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.
source.

Measurement BSC completes requesting for channel (due to assignment and the
Point channel is used as voice channel), or BSC receives the internal
message of waiting for resource successfully or waiting for re-
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 Times
Related Features ZGB-06-01-007 Cell Traffic Statistics

voice TCH/F seizure failure
for assignment
ure during voice channel assignment.
After BSC receives the channel request message, it attempts to
lates.
does not change.
Point 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 Times

C900060021 Number
to be occupied during voice channel handover, including the num-
ber of occupation success (C901260024) and the number of occu-
pation failure (C900060022).
simultaneously.
source.


INTERNAL)


Unit Times

for handover
ure during voice channel handover.
� If allocation or occupation fails, this counter accumulates.
lates.
does not change.
Measurement BSC requests for channel (due to handover and the channel is used
Point 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 Times

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).
sage to BTS to activate this TCH/F. If the TCH/F is activated suc-
Point sage 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.

Unit Times
Related Features 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).
sage to BTS to activate this TCH/F. If channel activation fails due
Measurement BSC activates TCH/F channel due to assignment and uses the
Point 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 Times
version2)

Unit Times
Related Features ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
version3)


Unit Times
ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

version3)
due to channel activation failure during voice channel assignment
(speech version 3).
sage to BTS to activate this TCH/F. If channel activation fails due
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 Times

voice TCH/F assignment
success
TCH/F as voice channel.
sage to BTS to activate this TCH/F. For assignment from A-inter-
face, after BSC receives the assignment success message, the
Measurement For assignment from A-interface, the counter accumulates when
Point BSC receives the assignment success message. The measurement

Unit Times
as voice channel.
Measurement This counter counts when BSC receives assignment failure mes-
Point sage, abnormal message, channel instance being released, chan-
nel instance being released forcibly, or timer timeout message.
The measurement point is B5, as shown in Figure 242.

Unit Times
data TCH/F seizure attempts
for assignment
to be occupied during data channel assignment, including the num-
simultaneously.
source.


Point channel is used as data channel), or BSC receives the internal mes-
sage of waiting for resource successfully or waiting for resource
failed (C901260070 + C900060031). The measurement point is
Unit Times
Related Features ZGB-01-03-002 Data Traffic Channels

data TCH/F seizure failure
for assignment
ure during data channel assignment.
lates.
does not change.
Point 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 Times

data TCH/F seizure attempts
for handover
to be occupied during data channel handover, including the number
simultaneously.
source.
C1 as shown in Figure 246 and Figure 247, and D1 as shown in
Figure 248 and Figure 249.


INTERNAL)


Unit Times

for handover
ure during data channel handover.
lates.
does not change.
Point as data channel) but fails to occupy the channel, or BSC fails to
Unit Times


TCH/F allocation success for
assignment
successfully during data channel assignment.
as data channel. The measurement point is B3, as shown in Figure
252 and Figure 253.

Unit Times
data TCH/F allocation failure
due to channel activation
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 chan-
nel activation fails due to receiving channel activation failure mes-
sage, incorrect channel activation response message, T9103 being
timeout, channel instance being released or channel being forcibly
released, this counter accumulates.
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.

Unit Times

TCH/F assignment success
TCH/F as data channel.
message to BTS to activate this TCH/F. For assignment from A-in-
terface, after BSC receives the assignment success message, the

Unit Times

TCH/F assignment failure
as data channel.


Unit 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

� For other cases, C900060038 and C900060039 accumulate si-

multaneously.
Point (due to assignment and the channel is used as signaling channel)
Unit 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 fail-
ure during signaling channel assignment.
does not change.

fails to wait for internal resource. The measurement point is A1,

FIGURE 259 IMMEDIATE ASSIGNMENT OCCUPATION FAILURE FLOW 1
Unit Times
to be occupied during signaling channel handover, including the
simultaneously.
source.

Point channel is used as signaling channel), or BSC receives the inter-
nal message of waiting for resource successfully or waiting for re-

INTERNAL)


Unit Times

lates.
does not change.
Measurement 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 Times

C900060042 Number
of voice TCH/H seizure
to be occupied during voice channel assignment, including the
simultaneously.
source.

Unit Times

voice TCH/H seizure failure
for assignment
ure during voice channel assignment.
lates.
does not change.
Point used as voice channel) but fails to occupy the channel, or BSC
fails to wait for internal resource. The measurement point is B1,
Unit Times

C900060044 Number
to be occupied during voice channel handover, including the num-
simultaneously.
source.


INTERNAL)


Unit Times

for handover
ure during voice channel handover.
� If allocation or occupation fails, this counter accumulates.
lates.
does not change.
Point as voice channel) but fails to occupy the channel, or BSC fails to
Unit Times


TCH/H seizure attempts for
assignment
to be occupied during data channel assignment, including the num-
simultaneously.
source.

Unit Times

data TCH/H seizure failure
for assignment
ure during data channel assignment.
lates.
does not change.
Point 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 Times


TCH/H seizure attempts for
handover
to be occupied during data channel handover, including the number
simultaneously.
source.
C1 as shown in Figure 278 and Figure 279, and D1 as shown in


INTERNAL)


Unit Times

for handover
ure during data channel handover.
lates.
does not change.
Point as data channel) but fails to occupy the channel, or BSC fails to
Unit Times

SAPI3 link establishment
requests on SDCCH
(MO-SM)
Description This counter counts the number of short message link establish-
ments of mobile originating call on SDCCH. On SDCCH, BSC re-
ceives the EST_IND message sent by BTS. If the layer-3 informa-
tion in this message is SAPI = 3, this counter increments.
Usage This counter is used to find out the frequency of SAPI 3 link estab-
lishment on SDCCH.
Measurement This counter counts when BSC receives the EST_IND message
Point (SAPI = 3) from BTS. The measurement point is B1, as shown
in Figure 284.

FIGURE 284 IDLE-STATE MO SHORT MESSAGE FLOW
Unit Times
Related Features ZGB-01-03-003 Short Message Service (SMS)

requests on SDCCH
(MT-SM)
ments 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 estab-
lishment request on SDCCH.
Measurement This counter counts when BSC sends the EST_REQ message (SAPI
Point = 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 Times
SDCCH drops due to
handover failure
Description This counter counts the number of call drops due to handover fail-
ure on SDCCH. Call drop occurs after MS requests for SDCCH suc-
cessfully. 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.

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 send-
ing 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 SDCCH is activated after BSC initiates the handover flow. After
Point that:
� If RANCS is in the status of RADIO_APPLY and sends the intra-
cell 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 DUE TO T3107 TIMEOUT DURING INTRA-CELL

HANDOVER
� If RANCS is in the status of RADIO_APPLY and sends the inter-

287.

FIGURE 287 CALL DROP DUE TO T3103 TIMEOUT DURING INTER-CELL

HANDOVER
� If RANCS is in the status of RADIO_APPLY and sends the ex-

ternal 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.
Unit 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 This counter increments when call drop occurs on SDCCH channel
Point due to radio link failure, LAPD link failure, or handover failure.
Unit Times

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 The counter increments when call drop occurs on TCH/F channel
Unit 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 The counter increments when call drop occurs on TCH/H channel
Unit Times

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 This counter counts when querying the database periodically.
Point
Unit Times
ZGO-03-02-001 Idle Channel Measurement
C900060057 Average
interference band 2
Point
Unit Times
C900060058 Average
interference band 3

Point
Unit Times
C900060059 Average
interference band 4
Point
Unit Times
C900060060 Average
interference band 5
Point
Unit Times

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
Point
Unit Times
Related Features ZGO-01-01-001 Half Rate
C900060062 Average
interference band 2
Point
Unit Times

C900060063 Average
interference band 3
Point
Unit Times
C900060064 Average
interference band 4
Point
Unit Times

C900060065 Average
interference band 5
Point
Unit Times
samples with UL RQ = 0
Description This counter counts the number of samples with Uplink (UL) Re-
ceiving 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 The counter increments if UL RQ = 0 in the measurement report
Point 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 measure-
ment report, if the UL RQ = 1, the counter increments.
= 1.

Unit Times
= 2.
Unit Times
= 3.
Unit Times
= 4.
Unit Times

= 5.
Unit Times
= 6.
Unit Times
= 7.
Unit Times

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 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
ment report, if the DL RQ = 1, the counter increments.
= 1.
Unit Times
= 2.
Unit Times

= 3.
Unit Times
= 4.
Unit Times
= 5.
Unit Times

= 6.
Unit Times
= 7.
Unit Times
TCH/F handover attempts
due to UL strength
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 BSC performs handover decision after receiving measurement re-
Point port on TCH/F channel. If handover decision succeeds and the
handover is due to UL strength, this counter increments. The mea-
surement point is A, as shown in Figure 288.

FIGURE 288 HANDOVER DECISION
Unit 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.
DL receiving strength on TCH/F channel. If the counter's value is
too large, it indicates poor DL level on TCH/F channel.
handover is due to DL strength, this counter increments. The mea-
Unit Times

due to UL quality
quality too poor on TCH/F channel.
UL quality on TCH/F channel. If the counter's value is too large, it
indicates poor UL quality on TCH/F channel.
handover is due to UL quality, this counter increments. The mea-
Unit Times
due to DL quality
Description This counter counts the number of handover attempts due to DL
quality too poor on TCH/F channel.
DL quality on TCH/F channel. If the counter's value is too large, it
indicates poor DL quality on TCH/F channel.
handover is due to DL quality, this counter increments. The mea-

Unit Times
due to UL interference
interference too large on TCH/F channel.
UL interference on TCH/F channel. If the counter's value is too
large, it indicates large UL interference on TCH/F channel.
handover is due to UL interference, this counter increments. The
measurement point is A, as shown in Figure 292.
Unit Times

due to DL interference
interference too large on TCH/F channel.
DL interference on TCH/F channel. If the counter's value is too
large, it indicates large DL interference on TCH/F channel.
handover is due to DL interference, this counter increments. The
Unit Times
due to good C/I
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 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.

handover is due to too large C/I ratio, this counter increments.

Unit Times
due to bad C/I
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.
to too low C/I ratio on TCH/F 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.
handover is due to too low C/I ratio, this counter increments. The
Unit Times

due to PBGT
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.
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.
handover is due to PBGT value, this counter increments. The mea-
Unit Times
due to large TA
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.
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.
handover is due to too large TA, this counter increments. The
Unit 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.
any other reason.
handover is due to any other reason beyond the handover reasons
mentioned previously, this counter increments. The measurement

Unit Times
BSC-controlled inter-cell
outgoing handover
Description This counter counts the number of intra-BSC inter-cell handover-
out 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 During the handover process, if the target cell requests for chan-
Point nel 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 Times

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 intra-
BSC inter-cell outgoing handover. It is one of the parameters that
evaluate the handover situation.
Measurement During the handover process, when the source cell receives the
Point 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 Times
MSC-controlled outgoing
handover
Description This counter counts the number of MSC-controlled inter-BSC out-
going handover executions.

Usage This counter is used to find out the frequency of MSC-controlled

inter-BSC outgoing handover execution, and it reflects the han-
dover situation.
Measurement BSC performs handover decision after receiving MS measurement
Point 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 han-
dover command returned from MSC, the counter increments. The
FIGURE 301 MSC-CONTROLLED OUTGOING HANDOVER EXECUTION
Unit Times
handover success
Description This counter counts the number of successful MSC-controlled in-
ter-BSC outgoing handovers.
Usage This counter is used to find out the frequency of successful MSC-
controlled inter-BSC outgoing handover, and it reflects the han-
dover situation.
Measurement BSC performs handover decision after receiving MS measurement
Point 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 Times
incoming handover
Description This counter counts the number of BSC-controlled inter-cell incom-
ing 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 parame-
ters that evaluate radio environment, and it reflects the handover
situation.
Measurement If channel activation succeeds in the target cell within BSC and the
Point request is due to inter-cell handover, the counter increments. The
FIGURE 303 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER

EXECUTION
Unit Times

incoming handover success
Description This counter counts the number of successful BSC-controlled inter-
cell incoming handovers.
Usage This counter shows the frequency of successful BSC-controlled in-
ter-cell incoming handover, and it reflects the handover situation.
Measurement When the target cell within BSC receives the handover completion
Point message, if the request is due to BSC-controlled inter-cell han-
dover, the counter increments. The measurement point is A, as
FIGURE 304 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Unit Times
MSC-controlled incoming
handover
Description This counter counts the number of MSC-controlled inter-BSC in-
coming handover executions.
inter-BSC incoming handover executions. It is one of the parame-
ters that evaluate radio environment, and it reflects the handover
situation.
Measurement After the target cell receives the handover request message issued
Point 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 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 The target cell receives the radio channel request message. If
Point 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 in-
crements. The measurement point is A, as shown in Figure 306.

FIGURE 306 FORCED RELEASE EXECUTION
Unit Times
ZGO-01-03-001 eMLPP
handover due to queue
counter counts the number of queuing executions due to no avail-
able radio resource in the target cell.
Usage This counter is used to find out the frequency of queuing execu-
tions during MSC-controlled inter-BSC incoming handover process,
and it reflects the handover situation.
Measurement The target cell receives the radio channel request message. If the
Point 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 mea-
FIGURE 307 QUEUING EXECUTION

Unit Times
ZGO-01-03-001 eMLPP
handover success
ter-BSC incoming handovers.
controlled inter-BSC incoming handover, and it reflects the han-
dover situation.
Measurement When the target cell receives the handover completion message, if
Point the request is due to MSC-controlled inter-BSC incoming handover,
the counter increments. The measurement point is A, as shown in
Figure 308.
FIGURE 308 MSC-CONTROLLED INCOMING HANDOVER SUCCESS
Unit Times

incoming handover from
undefined layer (GSM900)
to current layer(GSM1800)
Description This counter counts the number of incoming handover execu-
tions 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 When the target cell (GSM1800) within BSC receives the channel
Point activation response message, if the request is due to BSC-con-
trolled inter-cell handover and the source cell (GSM900) is the
undefined layer cell, the counter increments. The measurement

EXECUTION
Unit Times
ZGO-05-02-010 Multi-band Networking
ZGO-05-02-008 Multi-layer Cell Structure

C900060104 Number
of incoming handover
success from undefined
layer(GSM900) to current
layer (GSM1800)
Description This counter counts the number of successful incoming han-
dover from the undefined layer cell (GSM900) to the target cell
Usage This counter is used to find out the frequency of successful incom-
ing handover from the undefined layer cell (GSM900) to the target
cell (GSM1800). It reflects the handover situation.
Measurement When the target cell (GSM1800) within BSC receives the handover
Point completion message, if the request is due to BSC-controlled in-
ter-cell handover and the source cell (GSM900) is the undefined
layer cell, the counter increments. The measurement point is A,
Unit Times

to current layer (GSM900)
Description This counter counts the number of incoming handover execu-
tions from the undefined layer cell (GSM1800) to the target cell
executions from the undefined layer cell (GSM1800) to target cell
Measurement When the target cell (GSM900) within BSC receives the channel
Point activation response message, if the request is due to BSC-con-
trolled inter-cell handover and the source cell (GSM1800) is the
undefined layer cell, the counter increments. The measurement

EXECUTION
Unit Times

C900060106 Number
layer(GSM1800) to current
layer(GSM900)
Description This counter counts the number of successful incoming han-
dover from the undefined layer cell (GSM1800) to the target cell
Usage This counter is used to find out the frequency of successful in-
coming handover from the undefined layer cell (GSM1800) to the
target cell (GSM900). It reflects the handover situation.
Measurement When the target cell (GSM900) within BSC receives the handover
Point completion message, if the request is due to BSC-controlled in-
ter-cell handover and the source cell (GSM1800) is the undefined
layer cell, the counter increments. The measurement point is A,
Unit Times

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.
executions from the cell (GSM900) to the target cell (GSM1800)
in the same layer. It reflects the handover situation.
Measurement When the target cell (GSM1800) receives the channel activation
Point response message, if the request is due to BSC-controlled inter-
cell handover and the source cell (GSM900) is in the same layer,
Figure 313.

EXECUTION
Unit Times
from the same layer GSM900
to GSM1800
Description This counter counts the number of successful incoming handovers

ing handover from the cell (GSM900) to the target cell (GSM1800)
Measurement When the target cell (GSM1800) receives the handover comple-
Point tion 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 Times
GSM900 to GSM1800 from
the upper layer
from the upper layer cell (GSM900) to the target cell (GSM1800)
during BSC-controlled inter-cell handover.
executions from the upper layer cell (GSM900) to the target cell
cell handover and the source cell (GSM900) is in the upper layer,
Figure 315.


EXECUTION
Unit Times
from GSM900 to GSM1800
in the upper layer
ing handover from the upper layer cell (GSM900) to the target cell
handover and the source cell (GSM900) is in the upper layer, the
Figure 316.

Unit Times
GSM900 to GSM1800 in the
lower layer
from the lower layer cell (GSM900) to the target cell (GSM1800)
executions from the lower layer cell (GSM900) to the target cell
cell handover and the source cell (GSM900) is in the lower layer,
Figure 317.

EXECUTION
Unit Times

in the lower layer
ing handover from the lower layer cell (GSM900) to the target cell
handover and the source cell (GSM900) is in the lower layer, the
Figure 318.
Unit Times

the same layer
executions from the cell (GSM1800) to the target cell (GSM900)
Measurement When the target cell (GSM900) receives the channel activation re-
Point sponse 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 Times

from the same layer
ing handover from the cell (GSM1800) to the target cell (GSM900)
Measurement When the target cell (GSM900) receives the handover completion
dover and the source cell (GSM1800) is in the same layer, the
Figure 320.
Unit Times

the upper layer
executions from the upper layer cell (GSM1800) to the target cell
handover and the source cell (GSM1800) is in the upper layer, the
Figure 321.

EXECUTION
Unit Times

from the upper layer
ing handover from the upper layer cell (GSM1800) to the target
dover and the source cell (GSM1800) is in the upper layer, the
Figure 322.
Unit Times

the lower layer
executions from the lower layer cell (GSM1800) to the target cell
handover and the source cell (GSM1800) is in the lower layer, the
Figure 323.

EXECUTION
Unit Times

from the lower layer
ing handover from the lower layer cell (GSM1800) to the target
dover and the source cell (GSM1800) is in the lower layer, the
Figure 324.
Unit Times
Intra-cell handover
Description 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 mes-
sage of resource available is returned.

Usage This counter is used to find out the frequency of MS-initiated intra-
cell handover execution. It is one of the parameters that evaluate
radio environment. It reflects the handover situation.
Measurement During the handover process, if the target channel request suc-
Point ceeds, 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 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 intra-
cell handover. It is one of the parameters that evaluate handover.
Measurement During the intra-cell handover process, if the source instance re-
Point ceives 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 Times

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 de-
creases by 1. After a TCH/H is occupied, before a TCH/H is re-
leased, or when the system reports the periodical measurement
data, if this counter's value is less than the number of actual oc-
cupied 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 up-
dated before the release of a TCH/H.
Usage 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.
Measurement The counter counts at the following three time points:
Point
� After the TCH/H is occupied successfully, if the maximum num-
ber 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 Times

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 Query the database when periodic measurement data is reported
Point to get the value of the counter. The measurement point is A, as
Unit Times
C900060123 Average
number of unavailable
SDCCH
Description This counter counts the number of SDCCHs that can not be as-
signed 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.

Unit 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 ref-
erence for judging whether to increase the number of SDCCHs.
Point
� When an SDCCH is acquired successfully, this counter calcu-
lates 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:

� Measurement value = (Current time – Last measurement time
point) × Number of MSs that are occupying the channels

� The reported measurement value is accumulated by each mea-

surement value. After each accumulation, the last measure-
ment 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, Num-
ber of MSs that are occupying the channels decreases by
1.
Unit 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 re-
source usage situation of the cell.
Unit Times
ZGO-04-04-002 Intelligent TRX Shutdown

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 re-
source usage situation of the cell.
Unit Times
C900060127 TCH/H busy

time
Description This counter counts the busy time of TCH/Hs, which reflects the
traffic volume of TCH/H.
occupation time of TCH/H. It can be used as a reference for judging
whether to increase the number of TCH/Hs.
Point
� 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.


ment 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.
Unit 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 de-
creases by 1. After a TCH/F is occupied, before a TCH/F is re-
leased, or when the system reports the periodical measurement
data, if this counter's value is less than the number of actual oc-
cupied 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 up-
dated 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.


Point
� After the TCH/F is occupied successfully, if the maximum num-
ber of busy TCH/Fs exceeds the counter’s recorded value;
� Before the TCH/F 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/Fs exceeds the counter's
recorded value.
Unit Times
C900060129 TCH/F busy

time
Description This counter counts the busy time of TCH/Fs, which reflects the
traffic volume of TCH/F.
occupation time of TCH/F. It can be used as a reference for judging
whether to increase the number of TCH/Fs.
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.


ment 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.
Unit Second
healthy TRXs
Description This counter counts the number of the TRXs that can be used nor-
mally.
Usage This counter is used to find out the number of available TRXs and
resource usage in the current cell to facilitate troubleshooting.

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 ac-
cess cause in the layer-3 information in this message is “CM SER-
VICE REQ”, this counter increments.
Usage This counter is used to find out the frequency of the access due to
CM SERVICE REQ of MOC.
Unit 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 This counter counts when BSC receives the EST_CONF message
Point (SAPI = 3) from BTS. The measurement point is D2, as shown in
Figure 338.
FIGURE 338 IDLE-STATE MT SHORT MESSAGE FLOW

Unit 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.
Unit Times
available defined TCH/F
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.

Unit 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.
Point incorrect EST_IND message or T3101 is timeout. The measure-

Unit Times
MOC access attempts
Description This counter counts the number of channel requests due to Mo-
bile 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 This counter counts when MS requests for channel from BSC and
Point 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 re-
sponses. After BSC receives the EST_IND message, if the access
cause in the layer-3 information in this message is ‘paging re-
sponses’, this counter increments.
Usage This counter is used to find out the frequency of the access due to
paging responses.

Unit Times
Related Features 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).
After BSC responds to the channel request message to allocate and
occupy TCH/F channel successfully, BSC sends the CMM connec-
tion 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 BSC uses TCH/F for assignment, but the problem such as receiving
Point connection failure message, incorrect connection response mes-
sage, 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 Times
to BIU connection failure
version1)
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 con-
nection failure message, incorrect BIU connection response mes-
sage, or timer timeout, this counter accumulates.
sage, or timer timeout occurs during BIU connection process. The

Unit Times
to TCU connection failure
version1)
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 con-
nection failure message, incorrect TCU connection response mes-
sage, or timer timeout occurs during TCU connection process. The

Unit Times
version2)
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, incor-
rect channel activation response message, T9103 timeout, chan-
nel instance being released or channel being released forcibly, this
Measurement BSC activates TCH/F as voice channel (using speech version 2) for
Point 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.

Unit Times
version2)
speech version 2).

Unit Times
version2)
speech version 2).

Unit Times
version2)
speech version 2).
Unit Times

version3)
speech version 3).
Unit Times

version3)
speech version 3).
Unit Times

version3)
speech version 3).
Unit Times


to BTS connection failure for
assignment)
due to BTS connection failure when assigning data channel.
message or timer timeout, this counter accumulates.
sage or timer timeout occurs during CMM connection process. The
Unit Times
due to BIU connection failure
for assignment
due to BIU connection failure when assigning data channel.


sage or timer timeout, this counter accumulates.
Measurement BSC uses TCH/F for assignment, but receives connection failure
Point message, incorrect connection response message or timer timeout
during BIU connection process. The measurement point is B2, as
Unit Times

to TCU connection failure for
assignment
due to TCU connection failure when assigning data channel.
Measurement BSC uses TCH/F for assignment, but receiving connection failure
during TCU connection process. The measurement point is B2, as

Unit Times
voice TCH/H drops due to
handover failure
ure on TCH/H voice channel. Call drop occurs after MS requests
for TCH/H voice channel successfully. If the problem is due to han-
dover failure, the counter increments.
handover failure on TCH/H voice channel.
Measurement TCH/H voice channel is activated after BSC initiates the handover
Point flow. After that:
357.


HANDOVER

358.

HANDOVER

handover timer is timeout, then the counter increments. The

FIGURE 359 CALL DROP DUE TO INTER-BSC HANDOVER FAILURE
Unit 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 mes-
sages sent from BSC.
Usage This counter is used to find out the frequency of transmitting pag-
ing command messages at Abis interface. These messages are
from A-interface.
Measurement When BSC sends ABIS_INTER_PAGING_CMD message to BTS, this
Figure 360.
FIGURE 360 MEASUREMENT POINT OF NUMBER OF ABIS INTERFACE

MESSAGES SENT TO BTS FROM BSC
Unit Times

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 mes-
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 When BSC sends ABIS_INTER_CSPAGING_CMD message to BTS,
Point this counter increments. The measurement point is A, as shown
in Figure 361.

Unit 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 mes-
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 When BSC sends ABIS_INTER_PSPAGING_CMD message to BTS,
Point this counter increments. The measurement point is A, as shown
in Figure 362.


Unit Times
available defined TCH/H
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.
Unit Times

TCH/F allocation failure
failure for handover(speech
version1)
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 acti-
vate 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 BSC activates TCH/F channel as voice channel due to handover,
Point but receives channel activation failure message, incorrect chan-
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.


Unit Times
ZGB-02-02-001 Basic Handover
handover (speech version1)
Description This counter counts the number of failing to allocate TCH/F chan-
nel due to BTS connection failure during voice channel handover
Measurement BSC uses TCH/F channel for handover, but receives connection
Point 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 Times
to BIU connection failure for
due to BIU connection failure during voice channel handover (using
speech version 1).

Measurement BSC uses TCH/F for handover, but receives connection failure mes-
Point sage, 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 Times
nel due to TCU connection failure during voice channel handover


during TCU connection process. The measurement point is C2 as

Unit Times

failure for handover(speech
version2)
in Figure 373.


Unit Times


Unit Times
speech version 2).



Unit Times


Unit Times
failure for handover (speech
version3)


in Figure 381.

Unit Times


Unit Times

speech version 3).

Unit Times


Unit Times

Voice TCH/F handover
success
Description This counter counts the number of successful TCH/F channel han-
dover 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 accu-
mulates on source instances. For external handover, the counter
accumulates on target instances because the source instance is
not under this BSC.
Measurement The counter counts when BSC receives the ASS_COM/HO_COM
Point 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)



Unit Times
due to channel activation failure during data channel handover.
BSC sends the channel activation message CHL_ACT to BTS to ac-
tivate this TCH/F. If the channel activation fails due to receiving
channel activation failure message, incorrect channel activation
released, or channel being forcibly released, this counter accumu-
lates.
Measurement 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.


Unit Times

handover
due to BTS connection failure during data channel handover.


Unit Times
for handover
due to BIU connection failure during data channel handover.



Unit Times

handover
due to TCU connection failure during data channel handover.



Unit Times

TCH/F handover success
Description This counter counts the number of successful TCH/F channel han-
dover during data channel handover.


external handover.
not under this BSC.

INTERNAL)


Unit Times

signaling TCH/H allocation
Description This counter counts the number of TCH/H channel allocation fail-
ures 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 BSC activates TCH/H channel due to assignment and uses it as
Point signaling channel, but receives channel activation failure message,
leased. The measurement point is A2, as shown in Figure 404.
FIGURE 404 IMMEDIATE ASSIGNMENT ALLOCATION FAILURE FLOW 2
Unit Times

TCH/H allocation failure due
version1)
ure due to channel activation failure when assigning voice channel
message to BTS to activate this TCH/H. If the channel activation
Measurement BSC activates TCH/H as voice channel (using speech version 1) for
in Figure 405.
Unit Times

version1)
Description This counter counts the number of failing to allocate TCH/H chan-
nel due to BTS connection failure when assigning voice channel
occupy TCH/H channel successfully, BSC sends the CMM connec-
Measurement BSC uses TCH/H for assignment, but the problem such as receiving
Unit Times

version1)
nel due to BIU connection failure when assigning voice channel
occupy TCH/H channel successfully, BSC sends the BIU connection
Unit Times

version1)
nel due to TCU connection failure when assigning voice channel
occupy TCH/H channel successfully, BSC sends the TCU connection
Unit Times

TCH/H allocation failure
version1)
nel due to channel activation failure during voice channel handover
occupy TCH/H channel successfully, if the connection succeeds,
vate this TCH/H. If channel activation fails due to receiving channel
Measurement BSC activates TCH/H channel as voice channel due to handover,
in Figure 410.


Unit Times
Measurement BSC uses TCH/H channel for handover, but receives connection


Unit Times
nel due to BIU connection failure during voice channel handover

Measurement BSC uses TCH/H for handover, but receives connection failure mes-

Unit Times



Unit Times

version2)
in Figure 417.
Unit Times

version2)
Unit Times

version2)
Unit Times

version2)
Unit Times

version2)
in Figure 422.


Unit Times


Unit Times


Unit Times



Unit Times

version3)
in Figure 429.
Unit Times

version3)
Unit Times

version3)
Unit Times

version3)
Unit Times

version3)
in Figure 434.


Unit Times


Unit Times


Unit Times



Unit Times

Voice TCH/H assignment
success
TCH/H as voice channel.
occupy TCH/H channel successfully, BSC sends the CHL_ACT mes-
sage to BTS to activate this TCH/H. For assignment from A-in-

Unit Times
failure
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.

Unit Times
Voice TCH/H handover
success
Description This counter counts the number of successful TCH/H channel han-
dover during voice channel handover.
external handover.
not under this BSC.


INTERNAL)


Unit Times

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 BSC activates TCH/H channel due to assignment and uses the
Point channel as data channel, but receives channel activation failure
being timeout, channel instance being released, or channel be-
ing forcibly released. The measurement point is B3, as shown in
Figure 448.
Unit Times


assignment
nel due to BTS connection failure when assigning data channel.
message or timer timeout, this counter accumulates.
sage or timer timeout occurs during CMM connection process. The
Unit Times
for assignment
nel due to BIU connection failure when assigning data channel.


Measurement BSC uses TCH/H for assignment, but receives connection failure
during BIU connection process. The measurement point is B2, as
Unit Times

assignment
nel due to TCU connection failure when assigning data channel.
Measurement BSC uses TCH/H for assignment, but receiving connection failure
during TCU connection process. The measurement point is B2, as

Unit Times
nel due to channel activation failure during data channel handover.
BSC sends the channel activation message CHL_ACT to BTS to ac-
tivate this TCH/H. If the channel activation fails due to receiving
channel activation failure message, incorrect channel activation
released, or channel being forcibly released, this counter accumu-
lates.
Measurement 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 Times

handover
nel due to BTS connection failure during data channel handover.


Unit Times
for handover
nel due to BIU connection failure during data channel handover.



Unit Times

handover
nel due to TCU connection failure during data channel handover.



Unit Times

TCH/H assignment success
TCH/H as data channel.

message to BTS to activate this TCH/H. For assignment from A-in-

Unit Times


TCH/H assignment failure
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.
Unit Times

TCH/H handover success
Description This counter counts the number of successful TCH/H channel han-
dover during data channel handover.
on newly-allocated TCH/H channel, this counter accumulates. The


external handover.
not under this BSC.

INTERNAL)


Unit Times

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 exe-
cution during BSC-controlled inter-cell incoming handover process.
It reflects the status of the handover flow.
Measurement The target cell within BSC receives the radio channel request mes-
Point sage. If the request is due to BSC-controlled inter-cell incom-
ing 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 in-
stance, the counter increments. The measurement point is A2, as
FIGURE 467 FORCED RELEASE EXECUTION
Unit Times
ZGO-01-03-001 eMLPP

handover due to queues
counter counts the number of queuing executions due to no avail-
able radio resource in the target cell.
Usage This counter is used to find out the frequency of queuing execu-
tion during BSC-controlled inter-cell incoming handover process.
It reflects the status of the handover flow.
Point sage. 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 incre-
ments. The measurement point is A2, as shown in Figure 468.
FIGURE 468 QUEUING EXECUTION
Unit Times
ZGO-01-03-001 eMLPP

handover
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.
Point sage. 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
increments. The measurement point is A2, as shown in Figure
469.
FIGURE 469 FORCED HANDOVER EXECUTION
Unit Times
ZGO-01-03-001 eMLPP

handover
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
executions during MSC-controlled inter-BSC incoming handover
process. It reflects the status of the handover flow.
Measurement The target cell receives the radio channel request message. If the
Point 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 in-
stance is added to the waiting queue. When the target cell receives
the message of resource available, the counter increments. The
FIGURE 470 FORCED HANDOVER EXECUTION
Unit Times
ZGO-01-03-001 eMLPP
unavailable defined TCH/H
counter counts the number of unavailable TCH/H channel config-
ured 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.
Unit 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 config-
ured 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.

Unit Times
signaling TCH/F drops due
to handover failure
ure 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.
handover failure on TCH/F signaling channel.
Measurement TCH/F signaling channel is activated after BSC initiates the han-
Point dover flow. After that:
473.

HANDOVER



474.

HANDOVER

Unit Times

voice TCH/F drops due to
handover failure
Description This counter counts the number of call drops on TCH/F voice chan-
nel 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.
voice channel due to handover failure.
Measurement TCH/F voice channel is activated after BSC initiates the handover
476.

HANDOVER

477.


HANDOVER

Unit Times
data TCH/F drops due to
handover failure
Description This counter counts the number of call drops on TCH/F data chan-
nel due to handover failure. Call drop occurs after MS requests for

TCH/F data channel successfully. The counter increments if call

drop is due to handover failure.
data channel due to handover failure.
Measurement TCH/F data channel is activated after BSC initiates the handover
479.

HANDOVER

480.


HANDOVER

Unit Times

signaling TCH/H drops due
to handover failure
ure 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.
handover failure on TCH/H signaling channel.
Measurement TCH/H signaling channel is activated after BSC initiates the han-
Point dover flow. After that:
482.

HANDOVER

483.


HANDOVER

Unit Times

data TCH/H drops due to
handover failure
ure on TCH/H data channel. Call drop occurs after MS requests
for TCH/H data channel successfully. If the problem is due to han-
dover failure, the counter increments.
handover failure on TCH/H data channel.
Measurement TCH/H data channel is activated after BSC initiates the handover
485.

HANDOVER

486.


HANDOVER

Unit Times

TCH/H handover attempts
due to UL strength
receiving strength too low on TCH/H channel.
UL receiving strength on TCH/H channel. If the counter's value is
too large, it indicates poor UL level on TCH/H channel.
Point port on TCH/H channel. If handover decision succeeds and the
handover is due to UL strength, this counter increments. The mea-
Unit Times
due to DL strength
receiving strength too low on TCH/H channel.
DL receiving strength on TCH/H channel. If the counter's value is
too large, it indicates poor DL level on TCH/H channel.
handover is due to DL strength, this counter increments. The mea-

Unit Times
due to UL quality
quality too poor on TCH/H channel.
UL quality on TCH/H channel. If the counter’s value is too large, it
indicates poor UL quality on TCH/H channel.
handover is due to UL quality, this counter increments. The mea-
Unit Times

due to DL quality
quality too poor on TCH/H channel.
DL quality on TCH/H channel. If the counter’s value is too large,
it indicates poor DL quality on TCH/H channel.
handover is due to DL quality, this counter increments. The mea-
Unit Times
interference too large on TCH/H channel.
UL interference on TCH/H channel. If the counter's value is too
large, it indicates large UL interference on TCH/H channel.
handover is due to UL interference, this counter increments. The

Unit Times
interference too large on TCH/H channel.
DL interference on TCH/H channel. If the counter's value is too
large, it indicates large DL interference on TCH/H channel.
handover is due to DL interference, this counter increments. The
Unit Times

C900060230 Number
of TCH/H inter-subcell
handover attempts due to
good C/I
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.
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.
handover is due to too large C/I ratio, this counter increments.
Unit Times
C900060231 Number
of TCH/H inter-subcell
bad C/I
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.
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.
handover is due to too low C/I ratio, this counter increments. The
Unit Times
due to PBGT
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.
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.
handover is due to PBGT value, this counter increments. The mea-

Unit Times
due to large TA
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.
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.
handover is due to too large TA, this counter increments. The
Unit Times

other reason beyond the handover reasons mentioned previously.
any other reason.
handover is due to any other reason beyond the handover reasons
mentioned previously, this counter increments. The measurement
Unit 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 mes-
sage and sends EST_IND to BSC. The counter increments when
BSC receives the message correctly.
Measurement For immediate assignment, the counter increments when BSC re-
Point ceives the EST_IND message correctly. The measurement point is

Unit Times
MOC access success
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 The counter increments when BSC receives the EST_IND message.

Unit Times
C900060237 Number of dual

band outgoing handover
going handovers that are initiated by MS in the source cell (the
source cell and the target cell are of different frequency bands).
inter-BSC outgoing handover that is initiated by MS. The source
cell and the target cell are of different frequency bands.
Measurement BSC performs handover decision after receiving the measurement
Point report sent by MS. If the decision indicates that inter-cell han-
dover 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 han-
dover. 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

FIGURE 501 MSC-CONTROLLED OUTGOING HANDOVER EXECUTION
Unit Times
Related Features ZGO-05-02-010 Multi-band Networking

band outgoing handover
success
ter-BSC outgoing handovers that are initiated by MS in the source
cell (the source cell and the target cell are of different frequency
bands).
controlled inter-BSC outgoing handover that is initiated by MS. The
source cell and the target cell are of different frequency bands.
Measurement BSC performs handover decision after receiving the measurement
Point report sent by MS. If the decision indicates that inter-cell han-
dover is necessary and if the current cell to which the handover is
attempted is a cell under different BSC, then BSC sends the han-
dover 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 in-
FIGURE 502 MSC-CONTROLLED OUTGOING HANDOVER SUCCESS
Unit 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 in-
coming handover that is initiated by MSC. The source cell and the
target cell are of different frequency bands.
Measurement After the target cell receives the handover request issued by MSC,
Point if the target cell occupies and activates the channel successfully
FIGURE 503 MSC-CONTROLLED INCOMING HANDOVER EXECUTION
Unit Times

success
ter-BSC incoming handovers that are initiated by MS (the source
cell and the target cell are of different frequency bands).
inter-cell handover that is initiated by MS. The source cell and the
target cell are of different frequency bands.
Measurement After the target cell receives the handover completion message, if
Point the request is due to MSC-controlled inter-BSC incoming handover


Unit Times
C900060241 Number
of SDCCH assignment
attempts
Description 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 speci-
fied time, it indicates that the SDCCH channel assignment suc-
ceeds, C900060241 and C900060242 accumulate simultane-
ously.
� 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 This counter counts when BSC receives the EST_IND message or
Point the assignment completion message, or when T3101 is timeout

Unit Times
C900060242 Number
of SDCCH assignments
success
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 SD-
CCH channel when BSC sends the IMM_ASS message.
Measurement This counter counts when BSC receives the correct EST_IND mes-
Point sage or the assignment completion message. The measurement

Unit Times
SDCCH assignment failure
If BSC receives the incorrect EST_IND message or T3101 is time-
out, it indicates that the SDCCH channel assignment fails, then
Usage This counter counts the number of MS failing to access SDCCH
channel when BSC sends the IMM_ASS message.
Measurement This counter counts when BSC receives the incorrect EST_IND
Point message or when T3101 is timeout. The measurement point is

Unit 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 On TCH/F voice channel, when BSC receives Connection Failure
Point Indication message at Abis interface, this counter counts. The

FIGURE 508 CALL DROPS CAUSED BY RADIO LINK FAILURE DURING

ASSIGNMENT
Unit Times
ZGB-06-01-001 Monitoring Um Interface
radio link failure
Description 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 On TCH/H voice channel, when BSC receives Connection Failure
Point Indication message at Abis interface, this counter counts. The
FIGURE 509 CALL DROPS CAUSED BY RADIO LINK FAILURE DURING

ASSIGNMENT
Unit Times
Related Features ZGB-06-01-001 Monitoring Um Interface


Chapter 5
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 mea-
surement period.
Statistic unit in this measurement is cell.
C900090001 Cell frequency

band
Description This counter records frequency bands set in the cell. Refer to con-
figuration 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

TRX
Description This counter records the number of TRXs in the cell.
Usage This counter is used to find out the number of TRXs in the cell at
specific time segment.
Unit Times
TCH
Description This counter records the number of voice channels in the cell.
Usage This counter is used to find out the number of voice channels in
the cell at specific time segment.
Unit 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 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.

(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 carri-
ers: 2.28 for a single carrier, 8.25 for dual carriers, 14.04 for three
carriers, and 21.04 for four carriers.
static PDTCH
Description This counter records the number of static PDTCHs in the cell.
Usage This counter is used to find out the number of static PDTCHs in the
cell at specific time segment.
Unit Times
dynamic PDTCH
Description This counter records the number of dynamic PDTCHs in the cell.
Usage This counter is used to find out the number of dynamic PDTCHs in
the cell at specific time segment.

Unit Times

Chapter 6
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 execu-
tion on CCCH/PCCCH ....................................................... 438
tion failure on CCCH/PCCCH due to polling failed ................. 440
tion 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 execu-
tion on CCCH/PCCCH ....................................................... 451
tion failure on CCCH/PCCCH due to polling failed ................. 453
tion 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

C901000048 Max number of GPRS DL TBF simultaneous es-

tablishment .................................................................... 462
C901000050 Max number of EGPRS DL TBF simultaneous es-
tablishment .................................................................... 463
C901000052 Number of GPRS DL signaling TBF normal re-
lease ............................................................................. 463
C901000058 Number of EGPRS DL signaling TBF normal re-
lease ............................................................................. 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 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 When the DL GPRS TBF transmits all LLC frames and receives new
Point 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 Times
Related Features 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.

Measurement When the BSC sends DL Assign Request, the timer waiting for re-
Point sponse 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
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 When PACCH fails to send the assignment messages or fails to
Point create DL RLC instances, the counter increments.
Unit 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 During the DL GPRS TBF establishment on CCCH/PCCCH, if there is
Point 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)

Unit Times
C901000010 Number
of GPRS DL TBF
CCCH/PCCCH due to other
reasons
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 During the DL GPRS TBF establishment on CCCH/PCCCH, after the
Point 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
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-

ment, the user plane is informed too and it believes the DL TBF
establishment has started.
Measurement During the DL GRPS TBF establishment on CCCH/PCCCH, after the
Point 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

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
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.
Measurement � While waiting for MS’s responding with the AB form of packet
Point control ack message, if timeout occurs or messages informing
control block loss exceed the specified number, this counter
517.
� While waiting for MS’s responding with the AB form of packet
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

C901000013 Number
of GPRS DL TBF
success on CCCH/PCCCH
due to polling succeeded
CCCH/PCCCH
DL TBF establishment execution success on CCCH/PCCCH due to
polling succeeded
Description � When MS is in the idle state, after BSC receives DL LLC frames
from SGSN, BSC should originate DL TBF establishment as-
signed 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 tim-
ing advance setting, it indicates that the operation is success-
ful.
� In the DTM mode, if the user plane receives the DTM assign-
ment message from the control plane, the operation is consid-
ered 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 establish-
ments, the DL TBF establishment is also considered to be suc-
cessful.
Measurement When BSC receives the packet control ack message from MS after
Point 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

Unit Times
C901000014 Number
of GPRS DL TBF
on CCCH/PCCCH
CCCH/PCCCH
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.
ments, the GPRS DL TBF establishment is also considered to
be successful.
Measurement � If the assignment is on PCCCH, after the user plane sends the
Point 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

Unit Times
GPRS DL TBF normal
release
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 con-
sidered 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 After the DL GPRS TBF transmits the last data block (FBI=1) and
Point 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

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 After the DL EGPRS TBF transmits all LLC frames and before the
Point 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.

FIGURE 527 - MEASUREMENT POINT OF NUMBER OF RESUMPTION FOR

GPRS DL TBF IN DELAY STATE
Unit Times
Related Features ZGB-03-05-013 Delayed TBF Release in DL
C901000027 Number
of EGPRS DL TBF
PACCH due to time out
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 When the BSC sends DL Assignment Request, the timer waiting for
Point 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
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 When PACCH fails to send the assignment messages or fails to
Point create DL RLC instances, the counter increments.
Unit Times

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 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 During the DL EGPRS TBF establishment on CCCH/PCCCH, if there
Point is no radio resource assigned by the control plane within the spec-
ified time, this counter increments. The measurement points are
A, as shown in Figure 529 and Figure 530.

CCCH/PCCCH (1)

CCCH/PCCCH (2)

Unit Times
C901000032 Number
of EGPRS DL TBF
reasons
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 During the DL EGRPS TBF establishment on CCCH/PCCCH, after
Point 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/PC-
CCH
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-
ment, the user plane is informed too and it believes the DL TBF
establishment has started.
Measurement � During the DL EGRPS TBF establishment on CCCH/PCCCH, after
Point 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).

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
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 � While waiting for MS’s responding with the AB form of packet
Point control ack message, if timeout occurs or messages informing
control block loss exceed the specified number, this counter
534.
� While waiting for MS’s responding with the AB form of packet
control ack message, if the release request is received from
control plane, this counter increments. The measurement

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 Times

C901000035 Number
of EGPRS DL TBF
success on CCCH/PCCCH
due to polling succeeded
Definition 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 tim-
ing advance setting, it indicates that the operation is success-
ful.
ments, the DL TBF establishment is also considered to be suc-
cessful.
Measurement When BSC receives the packet control ack message from MS after
Point 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.


CCCH/PCCCH

Unit Times
C901000036 Number
of EGPRS DL TBF
on CCCH/PCCCH
Definition 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.
ments, the EGPRS DL TBF establishment is also considered to
be successful.
Measurement � If the assignment is on PCCCH, after the user plane sends the
Point 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.


CCCH/PCCCH

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 con-
sidered 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 After the DL EGPRS TBF transmits the last data block (FBI=1) and
Point when BSC receives the last DL response message (FAI=1), this
counter increments. The measurement points are A, as shown in
Figure 542andFigure 543.

Unit Times
C901000045 Time of GPRS

DL TBF connection
Definition Time of GPRS DL TBF connection
Description This counter counts the cumulated overall DL connecting time of
GPRS TBF within a cell.
Measurement � (1) When GPRS TBF RLC transmission starts, this counter ac-
Point cumulates.
� (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
EGPRS TBF within a cell.
Measurement The measurement point and the formulas are as shown in Figure
Point 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


signaling TBF within a cell.
Measurement The measurement point and the formulas are as shown in Figure
Point 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 Max number of GPRS DL TBF simultaneous establishment
Description The counter counts the maximum number of DL GPRS TBFs that
are established simultaneously within a cell.
Measurement � When GPRS TBF RLC transmission starts, the GPRS TBFs in the
Point 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 Times

C901000050 Max number

of EGPRS DL TBF
Definition Max number of EGPRS DL TBF simultaneous establishment
Description The counter counts the maximum number of DL EGPRS TBFs that
are established simultaneously within a cell.
Measurement � When EGPRS TBF RLC transmission starts, the EGPRS TBFs in
Point the cell increments by 1 and compares with the saved maxi-
mum 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 After the DL GPRS signaling TBF transmits the last data block
Point (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.

Unit Times
normal release
Definition Number of EGPRS DL signaling TBF normal release
Description 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 After the DL EGPRS signaling TBF transmits the last data block
Point (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


Chapter 7
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 es-
tablishment .................................................................... 486
C901010048 Max number of EGPRS UL TBF simultaneous es-
tablishment .................................................................... 487

C901010050 Number of GPRS UL signaling TBF normal re-

lease ............................................................................. 487
C901010056 Number of EGPRS UL signaling TBF normal re-
lease ............................................................................. 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 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 This counter increments when a new data block is received in GPRS
Point 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 re-
ceiving 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 This counter increments when UPPB receives UL resource reassign
Point 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 Times
Related Features ZGB-03-05-014 Delayed TBF Release in UL

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.
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
Definition Number of GPRS establishment failure on PACCH due to other rea-
sons
UL data to transmit but no corresponding TBF is available, UL TBF
establishment request will be sent out by Packet Downlink Ack. Gen-
erally, network will assign resources to MS; However, UL TBF es-
tablishment request fails if there is any condition abnormal.


by other reasons for establishing GPRS on PACCH.
Measurement This counter increments when the request for establishing GPRS
Point 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/down-
link TBF is available, MS initiates UL TBF establishment flow, de-
pending 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, net-
work sends Packet UL Ack with TLLI as well.
After sending out assignment message, if network does not re-
ceive RLC block or Packet Resource Request/ Additional MS Radio Ac-
cess 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 estab-
lishment on CCCH/PCCCH due to the failure of one-step success
competition solution.


Point
FIGURE 554 MEASUREMENT POINT ON NUMBER OF ESTABLISHMENT
FAILURES OF GPRS UL TBF CAUSED BY COMPETITION SOLUTION FAILURE
Unit Times
Related Features ZGB-03-05-007 One Phase Access
C901010011 Number
of GPRS UL TBF
CCCH/PCCCH due to not
receive resource request
due to not receive resource request
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 Assign-
ment according to MS’s 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 This counter is used to record number of failed GPRS UL TBF es-
tablishment on CCCH/PCCCH caused by not receiving resource re-
quest.


Point
FAILURES OF GPRS UL TBF CAUSED BY NOT RECEIVING RESOURCE
REQUEST
Unit Times
Related Features ZGB-03-05-008 Two Phase Access
C901010012 Number
of GPRS UL TBF
reasons
so that solution by competion can be completed. Meanwhile, net-
ment according to MS’s wireless radio access capability.

Usage This counter is used to record number of failed GPRS UL TBF es-
tablishment on CCCH/PCCCH caused by any other reasons.
Measurement This counter increments when GPRS UL TBF establishment fails
Point 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 Number of GPRS UL TBF establishment success on CCCH/PCCCH
ment according to MS’s wireless radio access capability.
Usage This counter is used to record number of successful GPRS UL TBF
establishment on CCCH/PCCCH.
Measurement This counter increments when GPRS UL TBF establishment on
Point 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)

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.
Point
FIGURE 558 MEASUREMENT POINT ON NUMBER OF NORMAL GPRS UL
TBF RELEASE
Unit 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.
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 Number of EGPRS UL TBF resource reassign in delay uplink state
Description 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.

Usage This counter is used to record number of resource reassignments

for EGPRS UL TBF in delayed UL state.
Point
FIGURE 560 MEASUREMENT POINT ON NUMBER OF RESOURCE
REASSIGNMENTS FOR EGPRS UL TBF IN DELAYED UL STATE
Unit Times
Related Features ZGB-03-05-014 Delayed TBF Release in UL
EGPRS establishment
failure on PACCH due to
time out
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.
by timeout for establishing EGPRS on PACCH.


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
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.
by other reasons for establishing GPRS on PACCH.
Measurement This counter increments when request for establishing EGPRS on
Point PACCH fails because of other reasons except timer is timeout.
Unit Times

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
After sending out assignment message, if network does not receive
RLC block or Packet Resource Request/ Additional MS Radio Access Ca-
pabilities from MS till timer is timeout, solution for one-step access
by competition fails.
Usage This counter is used to record number of failed EGPRS UL TBF es-
tablishment on CCCH/PCCCH caused by competition solving failed.
Point
FAILURES OF EGPRS UL TBF CAUSED BY COMPETITION SOLVING FAILED
Unit Times

C901010032 Number
of EGPRS UL TBF
receive resource request
due to not receive resource request
that, network assigns new resource for MS by Packet UL Assignment
according to MS’s 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 This counter is used to record number of failed EGPRS UL TBF
establishment on CCCH/PCCCH caused by not receiving resource
request.
Point
FAILURES OF EGPRS UL TBF CAUSED BY NOT RECEIVING RESOURCE
REQUEST
Unit Times
Related Features ZGB-03-05-008 Two Phase Access

C901010033 Number
of EGPRS UL TBF
reasons
so that solution by competition can be completed. Meanwhile, net-
according to MS’s 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 This counter increments when EGPRS UL TBF establishment fails
Point 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
Definition Number of EGPRS UL TBF establishment success on CCCH/PCCCH


according to MS’s wireless radio access capability.
Usage This counter is used to record number of successful EGPRS UL TBF
establishment on CCCH/PCCCH.
Measurement This counter increments when EGPRS UL TBF establishment on
Point 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)

FIGURE 565 MEASUREMENT POINT ON NUMBER OF SUCCESSFUL EGPRS

UL TBF ESTABLISHMENT ON CCCH/PCCCH (II)
Unit Times
EGPRS UL TBF normal
release
Definition 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, notify-
ing BSS to release TBF normally.
Usage This counter is used to record number of normal EGPRS UL TBF
releases.


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 The counter starts to accumulate when UPPB receives the UL GPRS
Point TBF establishment indication, and stops when UL GPRS TBF on
UPPB ends normally.
Unit Second
C901010044 Time of
EGPRS UL TBF connection
Definition Time of EGPRS UL TBF connection


time of EGPRS TBF.
Measurement The counter starts to accumulate when UPPB receives the UL EG-
Point PRS 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
time of signaling TBF.
Measurement The counter starts to accumulate when UPPB receives the UL sig-
Point naling 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 Max number of GPRS UL TBF simultaneous establishment
Description During the measurement period, there might be several TBFs ex-
isting simultaneously. This counter is used to find out the maxi-
mum 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 This counter increments when UPPB receives UL GPRS TBF estab-
Point lishment indication, and decrements when the UL GPRS TBF re-
leases.
Unit 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 ex-
isting simultaneously. This counter is used to find out the maxi-
mum 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 This counter increments when UPPB receives UL EGPRS TBF es-
Point tablishment indication, and decrements when the UL EGPRS TBF
releases.
Unit Times
normal release
Definition Number of GPRS UL signaling TBF normal release
Usage This counter is used to record number of normal GPRS signaling
UL TBF releases.

Measurement The measurement point is A, as shown inFigure 567.

Point
FIGURE 567 MEASUREMENT POINT ON NUMBER OF NORMAL GPRS
SIGNALING UL TBF RELEASE
Unit Times
normal release
Definition Number of EGPRS UL signaling TBF normal release
Usage This counter is used to record number of normal EGPRS signaling
UL TBF releases.


Point
FIGURE 568 MEASUREMENT POINT ON NUMBER OF NORMAL GPRS
SIGNALING UL TBF RELEASE
Unit Times


Chapter 8
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.

Kbytes of IP packet sent to
BIPB
Definition Number of Kbytes of IP packet sent to BIPB
Description 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 The counter counts the size of IP packets sent to BIPB. The mea-
surement unit is Byte.
Point
FIGURE 569 MEASUREMENT POINT OF SIZE OF IP PACKETS SENT TO BIPB
Unit Byte
packets sent to BIPB
Definition Number of packets sent to BIPB
Usage The counter counts the number of IP packets sent to BIPB.

Chapter 8 Data Flow Measurement

Point
FIGURE 570 MEASUREMENT POINT OF NUMBER OF IP PACKETS SENT TO
BIPB
Unit Times
Kbytes of IP packet received
from BIPB
Definition Number of Kbytes of IP packet received from BIPB
This counter counts the payload received within iBSC.
Usage The counter counts the size of IP packets received from BIPB. The
measurement unit is Byte.
Point
FIGURE 571 MEASUREMENT POINT OF SIZE OF IP PACKETS RECEIVED
FROM BIPB
Unit Byte

packets received from BIPB
Definition Number of packets received from BIPB
Usage The counter counts the number of packets received from BIPB.
Point
FIGURE 572 MEASUREMENT POINT OF NUMBER OF IP PACKETS RECEIVED
FROM BIPB
Unit Times
Kbytes of IP packet sent to
GIPB
Definition Number of Kbytes of IP packet sent to GIPB
Description 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 re-
ceived 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 The counter counts the size of IP packets sent to GIPB. The mea-
surement unit is Byte.


Point
FIGURE 573 MEASUREMENT POINT OF SIZE OF IP PACKETS SENT TO GIPB
Unit Byte
packets sent to GIPB
Definition Number of packets sent to GIPB
through IP packet.
Usage The counter counts the number of IP packets sent to GIPB.
Point
FIGURE 574 MEASUREMENT POINT OF NUMBER OF IP PACKETS SENT TO
GIPB
Unit Times

Kbytes of IP packet received
from GIPB
Definition 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 The counter counts the size of IP packets received from GIPB. The
measurement unit is Byte.
Point
FIGURE 575 MEASUREMENT POINT OF SIZE OF IP PACKETS RECEIVED
FROM GIPB
Unit Byte
packets received from GIPB
Definition Number of packets received from GIPB
through IP packet.
Usage The counter counts the number of IP packets received from GIPB.


Point
FIGURE 576 MEASUREMENT POINT OF NUMBER OF IP PACKETS RECEIVED
FROM GIPB
Unit Times
Kbytes carried by EGPRS
DL LLC frame
Definition Number of Kbytes carried by EGPRS DL LLC frame
access capacity to carry MS) and according to the CMP command,
Usage The counter counts the number of Kbytes carried by DL EGPRS LLC
frame.
Point
FIGURE 577 MEASUREMENT POINT OF NUMBER OF KBYTES CARRIED BY DL
EGPRS LLC FRAME
Unit Byte

Kbytes carried by DL
signaling LLC frame
Definition 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 The counter counts the number of Kbytes carried by DL signaling
LLC frame.
Point
FIGURE 578 MEASUREMENT POINT OF NUMBER OF KBYTES CARRIED BY
DL SIGNALING LLC FRAME
Unit Byte
Kbytes carried by UL LLC
frame
Definition Number of Kbytes carried by UL LLC frame
Description The UL UPPB sends the composed LLC frames to GIPB through IP
packet.
Usage The counter counts the number of Kbytes carried by UL LLC frame.


Point
UL LLC FRAME
Unit Byte
LLC frames
Definition Number of UL LLC frames
Description The UL UPPB sends the composed LLC frames to GIPB through IP
packet.
This counter performs statistics for LLC layer, and the statistic re-
sult is the number of frames.
Usage The counter counts the number of UL LLC frames.
Point
FIGURE 580 MEASUREMENT POINT OF NUMBER OF UL LLC FRAMES
Unit Times

Bytes of GPRS DL TBF LLC
frame
Definition Number of Bytes of GPRS DL TBF LLC frame
by setting RRBP to let MS report Packet DL Ack.
Usage The counter counts the number of bytes of DL GPRS TBF LLC frame.
Point
FIGURE 581 MEASUREMENT POINT OF NUMBER OF BYTES OF DL GPRS
TBF LLC FRAME
Unit Byte
Bytes of EGPRS DL TBF
LLC frame
Definition Number of Bytes of EGPRS DL TBF LLC frame


by setting RRBP to let MS report EGPRS Packet DL Ack.
Usage The counter counts the number of bytes of DL EGPRS TBF LLC
frame.
Point
FIGURE 582 MEASUREMENT POINT OF NUMBER OF BYTES OF DL EGPRS
TBF LLC FRAME
Unit Byte
Bytes of DL signaling TBF
LLC frame
Definition 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.


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 Number of Bytes of UL GPRS TBF LLC frame
them into the LLC frame and sends it to SGSN.
Usage The counter counts the number of bytes of UL GPRS TBF LLC frame.
Point
FIGURE 584 MEASUREMENT POINT OF NUMBER OF BYTES OF UL GPRS
TBF LLC FRAME
Unit Byte

Bytes of EGPRS UL TBF
LLC frame
Definition Number of Bytes of EGPRS UL TBF LLC frame
Usage The counter counts the number of bytes of UL EGPRS TBF LLC
frame.
Point
FIGURE 585 MEASUREMENT POINT OF NUMBER OF BYTES OF UL EGPRS
TBF LLC FRAME
Unit Byte
Bytes of UL signaling TBF
LLC frame
Definition Number of Bytes of UL signaling TBF LLC frame
Usage The counter counts the number of bytes of UL signaling TBF LLC
frame.


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 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.


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 net-
work 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.


Point
FIGURE 588 MEASUREMENT POINT OF TOTAL NUMBER OF COMPLETION OF
GPRS DL DATA TBF
Unit Times
EGPRS UL data TBF
completion
Definition 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.


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 net-
work 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.

Measurement The measurement point is A, as shown inFigure 590.

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 Number of Kbytes carried by GPRS DL LLC frame
access capacity to carry MS) and according to the CMP command,
Usage The counter counts the number of Kbytes carried by DL GPRS LLC
frame.


Point
DL GPRS LLC FRAME
Unit Byte


Chapter 9
Uplink-Downlink RLC
Statistic Measurement
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

Overview
RLC blocks are classified into control block and data block based
on the content. Data block includes RLC block waiting to be ac-
knowledged (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 accord-
ing 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.

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.

FIGURE 597 MEASUREMENT POINT OF UL FIRST-TRANSMITTED RLC BLOCK
C901030041 Bytes of GPRS

DL RLC lost on PDTCH
Definition Bytes of GPRS DL RLC lost on PDTCH
Description This counter is not used for the time being.
C901030042 Bytes of
EGPRS DL RLC lost on
PDTCH
Definition Bytes of EGPRS DL RLC lost on PDTCH
RLC Blocks lost
Definition 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 transmis-
sion.
Usage This counter is used to find out the number of RLC data blocks lost
on PDTCH.
Measurement The counter increments when UL RLC data blocks from BTS get
Point 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
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 The counter increments when CS-coded UL RLC block from BTS
Point gets lost. The measurement point is A, as shown in Figure 599.
Unit Byte

C901030085 Bytes of
EGPRS UL RLC lost on
PDTCH
Definition Bytes of EGPRS UL RLC lost on PDTCH
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 The counter increments when MCS-coded UL RLC block from BTS
Point gets lost. The measurement point is A, as shown in Figure 600.
Unit Byte
standstill of GPRS UL TBF
receiving window
Definition Number of standstill of GPRS UL TBF receiving window
Description This counter counts the number of standstill of UL receiving win-
dow after UL GPRS TBF establishment.
Usage This counter is used to find out the number of standstill of UL GPRS
TBF receiving window.
Measurement The counter increments when receiving window is found to come
Point 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 win-
dow after UL EGPRS TBF establishment.
Usage This counter is used to find out the number of standstill of UL EG-
PRS TBF receiving window.
Measurement The counter increments when receiving window is found to come
Point to a standstill in RLC layer after UL EGPRS TBF establishment.
Unit Times
standstill of GPRS DL TBF
sending window
Definition Number of standstill of GPRS DL TBF sending window
Description This counter counts the number of standstill of DL sending window
after DL GPRS TBF establishment.

Usage This counter is used to find out the number of standstill of DL GPRS
TBF sending window.
Measurement The counter increments when sending window is detected to stag-
Point nate during RLC block sending to BTS from BSC. The measurement

DL TBF SENDING WINDOW
Unit Times
standstill of EGPRS DL TBF
sending window
Definition 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 The counter increments when sending window is detected to
Point standstill during RLC block sending to BTS from BSC. The mea-


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 num-
ber of DL coding scheme increase.
Usage This counter is used to find out the increase of DL RLC block coding
scheme.
Measurement The counter increments when coding scheme of DL RLC blocks
Point sending to BTS from BSC is increased. The measurement point is
A as shown in Figure 604 (for EDGE) and Figure 605 (for GPRS).

FIGURE 604 MEASUREMENT POINT OF NUMBER OF INCREMENT OF DL

CODING MODE (EDGE RLC BLOCK)

CODING MODE (GPRS RLC BLOCK)
Unit Times
Related Features ZGB-03-05-012 GPRS Link Adaptation
ZGO-03-05-002 EGPRS Link Adaptation
decrement of DL coding
mode
Definition 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 num-
ber of DL coding scheme decrease.
Usage This counter is used to find out the decrease of DL RLC block coding
scheme.
Measurement The counter increments when coding scheme of DL RLC blocks
Point 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 Times

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 num-
ber of UL coding scheme increase.
Usage This counter is used to find out the increase of UL RLC block coding
scheme.
Measurement The counter increments when coding scheme of UL RLC blocks is
Point increased. The measurement point is A, as shown in Figure 608.
FIGURE 608 MEASUREMENT POINT OF NUMBER OF INCREMENT OF UL

CODING MODE
Unit Times
decrement of UL coding
mode
Definition Number of decrement 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 num-
ber of UL coding scheme decrease.

Usage This counter is used to find out the decrease of UL RLC block coding
scheme.
Measurement The counter increments when coding scheme of UL RLC blocks
Point sending to BTS from BSC is decreased. The measurement point is

CODING MODE
Unit 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 The counter increments When coding scheme of RLC block is
Point changed from GMSK to 8PSK (MCS5~MCS9). The measurement
point is A, as shown in Figure 610, Figure 611, and Figure 612.





CODING MODE
Unit Times
Related Features ZGO-03-05-002 EGPRS Link Adaptation
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 The counter increments when coding scheme of RLC block is
Point 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.





CODING MODE
Unit Times
Related Features ZGO-03-05-002 EGPRS Link Adaptation
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 When the coding mode of downlink RLC block sent to BTS from BSC
Point is upgraded, the counter increments. The measurement point is

FIGURE 616 MEASUREMENT POINT OF DOWNLINK GPRS RLC BLOCK

CODING MODE ADJUSTMENT
Unit 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.
block's coding mode being degraded.
Measurement When the coding mode of downlink RLC block sent to BTS from
Point BSC is degraded, the counter increments.
Unit Times
increment of GPRS UL
coding mode
Description 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 When the coding mode of uplink RLC block received by BSC is
Point upgraded, the counter increments. The measurement point is A,
FIGURE 617 MEASUREMENT POINT OF UPLINK RLC BLOCK CODING MODE

ADJUSTMENT
Unit Times
decrement of GPRS UL
coding mode
is degraded.
being degraded.
Point degraded, the counter increments.
Unit Times

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.
block's coding mode being upgraded.
Measurement When the coding mode of downlink RLC block sent to BTS from BSC
Point is upgraded, the counter increments. The measurement point is
FIGURE 618 MEASUREMENT POINT OF DOWNLINK EDGE RLC BLOCK

CODING MODE ADJUSTMENT
Unit Times
decrement 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 degraded.

block's coding mode being degraded.
Measurement When the coding mode of downlink RLC block sent to BTS from
Point BSC is degraded, the counter increments.
Unit Times
increment of EGPRS UL
coding mode
is upgraded.
being upgraded.
Point upgraded, the counter increments. The measurement point is A,
FIGURE 619 MEASUREMENT POINT OF UPLINK RLC BLOCK CODING MODE

ADJUSTMENT
Unit Times

decrement of EGPRS UL
coding mode
is degraded.
being degraded.
Point degraded, the counter increments.
Unit Times

Chapter 10
PS Resource Used
Statistic Measurement
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 ex-
ists ................................................................................ 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 ex-
ists ................................................................................ 539
C901040014 Time of PDCH used at least one UL TBF ex-
ists ................................................................................ 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

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 chan-
nels ............................................................................... 555
C901040049 Number of requested uplink radio chan-
nels ............................................................................... 555
C901040050 Number of requested downlink radio chan-
nels ............................................................................... 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 cell’s requirements for
Abis resource, which helps to adjust or expand Abis resource.
Measurement Inquire the database when periodic measurement data report to
Point get the counter value.
Unit 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.
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.
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 cur-
rent cell.
Usage This counter is used to find out the number of available static PD-
CHs in the current cell, which helps to make troubleshooting.
Unit Times

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.
Unit Times
Related Features ZGB-03-02-005 GPRS-only (without voice) Timeslots Configurable
ZGO-03-02-010 GPRS and EGPRS Channels Allocated Separately
C901040009 Time of DL
PDCH congestion
Definition Time of DL PDCH congestion
Description 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 cal-
culation repeats. When getting the periodic measurement value,
if the congestion label is set, such calculation repeats. The accu-
mulation of these calculations makes the total time of DL PDCH
congestion.
Usage 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 The measurement is taken at three time points listed below:

Point
� Before DL PDCH attempts to occupy, if the congestion label is
set, this counter calculates the congestion time and accumu-
lates 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 con-
gestion label is set, this counter calculates the congestion time
and accumulates them.
Unit Second
C901040010 Time of UL
PDCH congestion
Definition Time of UL PDCH congestion
Description 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 cal-
culation repeats. When getting the periodic measurement value,
if the congestion label is set, such calculation repeats. The accu-
mulation of these calculations makes the total time of UL PDCH
congestion.
Usage This counter is used to find out the busyness of UL PDCH, which
configured.
Point
� Before UL PDCH attempts to occupy, if the congestion label is
set, this counter calculates the congestion time and accumu-
lates 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 con-
gestion label is set, this counter calculates the congestion time
and accumulates them.
Unit Second

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.
Point
� When PDCH resource is acquired successfully, this counter cal-
culates and accumulates.
� When PDCH resource is released, this counter calculates and
accumulates.
� When reporting the measurement data periodically, this
counter calculates and accumulates.
Unit Second
Related Features ZGO-03-02-010 GPRS and EGPRS Channels Allocated Separately

used at least one UL/DL
EGPRS TBF exists
Definition Time of PDCH used at least one UL /DL EGPRS TBF exists
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.
Point
accumulates.
Unit Second


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 re-
garded to be used. This counter counts the time of PDCH used by
DL. The value of the counter reflects the PDCH traffic.
Point
accumulates.
Unit 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 re-
garded to be used. This counter counts the time of PDCH used by
UL. The value of the counter reflects the PDCH traffic.
Point
accumulates.


Unit 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 If BSC starts UL single block or UL TBF channel assignment, when
Point non-DRX MS assigns DL TBF, the counter increments. The mea-
surement points are A1 and A2 as shown in Figure 620 and Figure
621.
FIGURE 620 SENDING INSTANT ASSIGNMENT MESSAGE BY AGCH CHANNEL

(1)


(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 When BSC sends Paging PS message on PCH, the counter incre-
Point ments. The measurement point is A as shown in Figure 622.
FIGURE 622 SENDING PS PAGING BY PCH CHANNEL
Unit Times

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.
CS message on PCH by BSC in the current cell.
Measurement When BSC sends Paging CS message on PCH, the counter incre-
Point ments. The measurement point is A as shown in Figure 623.
FIGURE 623 SENDING CS PAGING BY PCH CHANNEL
Unit Times
PCH
Definition Number of immediate assignment on PCH
Description This counter counts the number of Imm Assign message sent on PCH
by BSC.
message on PCH by BSC in the current cell.
Measurement If BSC starts to establish DL TBF, when DRX MS sends Imm Assign
Point 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
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 If BSC starts UL single block or UL TBF channel assignment, when
Point non-DRX MS assigns DL TBF, the counter increments. The mea-
surement points are A1 and A2, as shown in Figure 625and Figure
626.

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 Number of PS paging requests on PPCH
Description This counter counts the number of Paging PS message sent on
PPCH by BSC.
PS message on PPCH by BSC in the current cell.

Measurement When BSC sends Paging PS message on PPCH, the counter incre-
FIGURE 627 SENDING PS PAGING BY PCH CHANNEL
Unit 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.
CS message on PPCH by BSC in the current cell.
Measurement When BSC sends Paging CS message on PPCH, the counter incre-
FIGURE 628 SENDING CS PAGING BY PCH CHANNEL

Unit Times
PPCH
Definition Number of immediate assignment on PPCH
PPCH by BSC.
message on PPCH by BSC in the current cell.
Measurement If BSC starts to establish DL TBF, when DRX MS sends Imm Assign
Point message on PPCH, the counter increments. The measurement
FIGURE 629 SENDING ASSIGNMENT MESSAGE BY PAGCH CHANNEL
Unit Times
Packet Channel Request on
PRACH
Description 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 When BSC receives EGPRS Packet Channel Request message or
Point 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 When the database of BSC starts to assign Abis TS, the counter
Point 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 data-
base.
Usage This counter is used to find out the frequency of Abis TS assign-
ment sampling. It is one of the parameters to observe the Abis TS
using.

Measurement When the database assigns Abis TS, the counter increments.
Point
Unit 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 re-
quest. It is one of the parameters to observe multi-TS using when
assigning PS channels in the current cell.
Measurement When service processing module starts PS channel request and
Point 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 re-
quest.
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 When service processing module starts PS channel request and
Point database assigns PDCH, the counter increments.
Unit Times
C901040031 Maximum
value of Abis TS used to CS
Definition 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-ac-
cess sites, it counts the maximum bandwidth occupied by CS ser-
vice. This counter reflects the transcient occupation and the busi-
est 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 The counter counts when CS user requests for the Abis resource
Point 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.
cell's CS service, which helps adjust the usage of Abis resource.
Measurement The counter counts when CS user requests for the Abis resource
Point successfully or releases the Abis resource successfully.
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 accu-
mulated 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 The counter accumulates when CS user requests for the Abis re-
Point source successfully or releases the Abis resource successfully.

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 The counter accumulates when CS user requests for the Abis re-
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-ac-
cess sites, it counts the maximum bandwidth occupied by PS ser-
vice. This counter reflects the transcient occupation and the busi-
est level of Abis resource in the cell's PS service.
cell's PS service, which helps adjust the usage of Abis resource.
Measurement The counter counts when PS user requests for the Abis resource
Point successfully.

of Abis TS used to PS
Definition 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.
cell's PS service, which helps adjust the usage of Abis resource.
Measurement The counter counts when PS user requests for the Abis resource
Point successfully or releases the Abis resource successfully.


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 accu-
mulated 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 The counter accumulates when PS user requests for the Abis re-
sampling of PS
Definition Number of sampling of PS
Abis resource in the cell's PS service.
Usage This counter reflects the average occupation of Abis resource in PS
service.
Measurement The counter accumulates when PS user requests for the Abis re-
C901040039 MAX CS used

number of exclusive ABIS
Description This counter counts the maximum number of Abis timeslots occu-
pied by CS service in the cell. Upon the request of releasing CS

channel, the system checks the total number of Abis timeslots oc-
cupied 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 The counter counts upon channel conversion due to request of
Point releasing CS channel and refreshing dynamic CS channel.
C901040040 MIN CS used

Description This counter counts the minimum number of Abis timeslots occu-
pied by CS service in the cell. Upon the request of releasing CS
cupied by CS service in the cell. If the number is less than the
by CS service in the cell.
Point releasing CS channel and refreshing dynamic CS channel.
C901040041 MAX PS used

Description This counter counts the maximum number of Abis timeslots occu-
pied by PS service in the cell. Upon the request of releasing PS
cupied by PS service in the cell. If the number is larger than the
by PS service in the cell.
Point releasing PS channel and refreshing dynamic PS channel.
C901040042 MIN PS used

Description This counter counts the minimum number of Abis timeslots occu-
pied by PS service in the cell. Upon the request of releasing PS

cupied by PS service in the cell. If the number is less than the

by PS service in the cell.
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 The counter counts in the four following cases.
Point
1. The counter increments after one phase access receives the
indication message.
2. The counter increments after two phase access sends the re-
source 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 For the counter C901040043, if the maximum number of users is
Point 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

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
Point
1. The counter increments after one phase access receives the
indication message.
2. The counter increments after two phase access sends the re-
source 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 For the counter C901040043, if the maximum number of users is
Point 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
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


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 chan-
nels in the cell and site within the measurement period.
Usage This counter counts the number of assigned downlink radio chan-
Measurement The counter counts in the following three cases.
Point
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 Consistent with that for C901040047.
Point
Unit Times

requested downlink radio
channels
Description This counter counts the number of requested downlink radio chan-
Usage This counter counts the number of requested downlink radio chan-
Measurement Consistent with that for C901040048.
Point
Unit 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 The counter counts when the RANUMC module receives the
Point EV_DBS_PSCHANEXPAND message.
Unit Times
channel expand perform
Description This counter counts the number of channel expansions in PS ser-
vice.
Usage This counter is used to find out the number of channel expansions
executed by RANPS.
Measurement This counter counts when the RANPS module receives the
Point EV_RANUMC_PSCHANEXPAND message.
Unit 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 This counter counts when the RANPS module successfully requests
Point the resource for expansion from database.
Unit Times


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 chan-
nel 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 chan-
nel due to queuing........................................................... 569
C901050010 Number of assignments for directed retry at-
tempts 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


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 obstruc-
tion ............................................................................... 591
C901050032 Assignment unsuccessful due to circuit obstruc-
tion 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 (as-
signment forced handover) ............................................... 604
C901050045 Number of time out for wait resource (assign-
ment forced handover)..................................................... 605
C901050046 Number of forced release target not found (as-
signment forced release) .................................................. 606
C901050047 Number of time out for wait resource (assign-
ment forced release)........................................................ 607
C901050048 Number of get before grab released channel (as-
C901050049 Number of get before grab released channel(as-
C901050050 The count of Assignment using FULL IP A-Inter-
face ............................................................................... 610

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 sup-
ported" .......................................................................... 613
"Requested Codec Type or Codec Configuration unavail-
able" ............................................................................. 614
C901050055 The count of Assignment Failure caused by "Re-
quested A-Interface Type not supported" ............................ 615
quested A-Interface Type unavailable" ................................ 616
C901050057 The count of Assignment Failure caused by "Call
Identifier already allocated" .............................................. 617
quested Redundancy Level not supported" .......................... 618
C901050059 The count of Assignment Failure caused by "Call
Access Control" ............................................................... 619
C901050060 Attempt Number of mode modify for assign-
ment ............................................................................. 620
C901050061 Success Number of mode modify for assign-
ment ............................................................................. 621
tempts for voice channel because of radio........................... 621
channel due to directed retry because of radio..................... 622
tempts 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 descrip-
tion 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 assign-
ment 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

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 re-
source.
Measurement In voice channel assignment flow, the counter increments when
Point source cell receives message that resource is available from target
cell after sending channel request, and successfully sends assign-
ment 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 avail-
able 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 BSC fails in allocating channel due to no available resource. It
Point releases other channels forcedly when the system allows.
� 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 Times
Related Features 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 exe-
cutions for voice channel due to forced release in MS accessing
process.

Measurement The counter increments if radio resource request fails in voice

Point channel assignment, forced released can be carried out and in-
stance 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
FIGURE 633 MEASUREMENT POINT OF ASSIGNMENT EXECUTIONS FOR VOICE

CHANNEL DUE TO FORCED RELEASE
Unit Times
handover attempts for voice
due to forced release
Definition Number of handover attempts for voice due to forced release
Description BSC attempts to operate outgoing handover to the cell voice chan-
nel for forced release when it fails in voice channel allocation due
to no available resource. The counter counts the number of han-
dover 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 The counter increments when BSC fails in general voice chan-
Point nel assignment and the system allows forced release and there is
proper instance of forcing release that sends forced release mes-
sage to instance of forced release. The measurement point is A,

FIGURE 634 MEASUREMENT POINT OF HANDOVER FOR FORCED RELEASE

ATTEMPTS
Unit Times
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 chan-
nel for forced release when it fails in voice channel allocation due
dover 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.
Point channel assignment, handover for voice channel due to forced re-
lease can be carried out and instance of forcing handover sends
forced handover message to instance of forced handover, and re-
source available message is received and channel is obtained suc-
cessfully. The measurement point is B, as shown in Figure 635.

FIGURE 635 MEASUREMENT POINT OF HANDOVER EXECUTIONS FOR VOICE

Unit Times
assignments for voice
channel due to queuing
Definition Number of assignments for voice channel due to queuing
Description BSC attempts to assign voice channel after receiving Radio App
able and the system doesn’t allow forced release or can’t 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.
queuing attempts for voice channel in MS accessing process.
Measurement The counter increments when BSC fails in general voice chan-
Point nel 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 Times
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.
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.

FIGURE 637 MEASUREMENT POINT OF ASSIGNMENTS FOR EXECUTION FOR

VOICE CHANNEL DUE TO QUEUING
Unit Times
assignment success voice
Definition Duration of assignment success voice channel due to queuing
Description 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 chan-
nel is the time when channel is obtained minus the time when the
instance began to queue. The counter accumulates the total du-
rations of successful assignment for queuing for voice channel.
Usage This counter is used to check the intra-cell queuing status and rep-
resents whether queuing can relieve traffic congestion effectively.
Measurement The counter accumulates duration of successful assignment for
Point queuing for voice channel if radio resource request fails in voice
channel assignment, queuing can be carried out and instance of
successfully. The measurement points are A and B, as shown in
Figure 638.


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 queu-
ing for voice channel.
Point channel assignment, queuing can be carried out and instance of
successfully. The measurement point is B, as shown in Figure 639.


Unit Times
assignments for directed
retry attempts for voice
channel
Definition Number of assignments for directed retry attempts for voice chan-
nel
Description If BSC fails in voice channel request, and source cell allows di-
rected 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.
directed retry attempts for voice channel and check whether the
cell’s radio environment can satisfy the traffic demand.
Measurement The counter increments when source cell receives no available ra-
Point dio resource message from target cell and source cell supports di-
can be found and Radio_App message is sent to target cell. The

FIGURE 640 MEASUREMENT POINT OF ASSIGNMENTS FOR DIRECTED RETRY

ATTEMPTS
Unit Times
Related Features 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 di-
rected 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 The counter increments when directed retry is carried out and tar-
Point get cell obtains channel successfully and source cell receives radio
resource available message from target cell in voice channel as-
signment process. The measurement point is B, as shown in Figure
641.


VOICE CHANNEL DUE TO DIRECTED RETRY
Unit Times
general assignments for
execution for data
Definition 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 In data channel assignment flow, the counter increments when
Point 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
able and the system allows forced release, then BSC carries out
forced release to other channels. This counter counts the number
of forced release.
forced release attempts in MS accessing process.
Measurement BSC fails in allocating channel due to no available resource and
Point 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.

FIGURE 643 MEASUREMENT POINT OF ASSIGNMENTS FOR FORCED RELEASE

ATTEMPTS
Unit Times
Definition 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.
cutions for data channel due to forced release in MS accessing
process.
Measurement The counter increments if radio resource request fails in data chan-
Point nel 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 FOR VOICE

Unit Times
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 chan-
nel for forced release when it fails in data channel allocation due
dover 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 The counter increments when BSC fails in general data channel as-
Point signment and the system allows forced release and there is proper
instance of forcing release that sends forced release message to in-
stance of forced release. The measurement point is A, as shown
in Figure 645.


ATTEMPTS
Unit Times
handover executions for
Definition Number of handover executions for data due to forced release
Description BSC attempts to operate outgoing handover to the cell data chan-
nel for forced release when it fails in data channel allocation due
dover 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 The counter increments if radio resource request fails in data
Point 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 Times
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 mes-
sage in assignment flow; if there is no proper channel available
and the system doesn’t allow forced release or can’t 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.
queuing attempts for data channel in MS accessing process.
Measurement The counter increments when BSC fails in general data channel as-
Point signment and the system allows queuing and the instance queues.


ATTEMPTS
Unit Times
for data due to queuing
Definition 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.
Point nel assignment, queuing can be carried out and instance of queu-
ing receives resource available message and obtains channel suc-


Unit Times
C901050019 Total duration

of successful assignments
for data due to queuing
Definition Total duration of successful assignments for data due to queuing
Description 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 chan-
nel is the time when channel is obtained minus the time when the
instance began to queue. The counter accumulates the total du-
rations of successful assignment for queuing for data channel.
Measurement The counter accumulates duration of successful assignment for
Point queuing for data channel if radio resource request fails in data
channel assignment, queuing can be carried out and instance of
successfully. The measurement points are A and B, as shown in
Figure 649.


Unit Times
assignments success for
data due to queuing
Description This counter counts the number of successful assignments of queu-
ing for data channel.
Point nel assignment, queuing can be carried out and instance of queu-
ing receives resource available message and obtains channel suc-


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.
directed retry attempts for data channel and check whether the
cell’s radio environment can satisfy the traffic demand.
Measurement The counter increments when source cell receives no available ra-
Point dio resource message from target cell and source cell supports di-
can be found and Radio_App message is sent to target cell. The


ATTEMPTS
Unit Times
data due to directed retry
Definition 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 The counter increments when directed retry is carried out and tar-
Point get cell successfully obtains channel and source cell receives radio
resource available message from target cell in data channel assign-
ment process. The measurement point is B, as shown in Figure
652.


Unit Times
C901050023 Number
of assignment for retry
attempts FDD cell for voice
channel
Definition Number of assignment for retry attempts FDD cell for voice chan-
nel
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 The counter increments in voice channel assignment when source
Point 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.


ATTEMPTS
Unit 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
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.
cutions due to directed retry to FDD cell for voice channel and
represent FDD cell directed retry status.
Measurement The counter increments in voice channel assignment when target
Point 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 Times
C901050025 Number
attempts FDD cell for data
Definition Number of assignment for retry attempts FDD cell for data
FDD cell for data channel.
attempts FDD cell for data channel and represent FDD cell traffic
sharing status in data channel assignment.
Measurement The counter increments in data channel assignment when source
Point 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.


ATTEMPTS
Unit Times
FDD cell for data
FDD cell for data
directed retry to FDD cell for data channel.
Usage This counter is used to find out the number of assignment ex-
ecutions due to directed retry to FDD cell for data channel and
represent FDD cell directed retry status.
Measurement The counter increments in data channel assignment when target
Point cell in directed retry is FDD cell and successfully obtains channel
and source cell receives radio resource available message from tar-
get cell. The measurement point is B, as shown in Figure 656.


Unit Times
C901050027 Number
attempts TDD cell for voice
channel
Definition Number of assignment for retry attempts TDD cell for voice chan-
nel
TDD cell for voice channel.
attempts TDD cell for voice channel and represent TDD cell traffic
sharing status in voice channel assignment.
Measurement The counter increments in voice channel assignment when source
Point 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.


ATTEMPTS
Unit Times
TDD cell for voice channel
TDD cell for voice channel
directed retry to TDD cell for voice channel.
cutions due to directed retry to TDD cell for voice channel and
represent TDD cell directed retry status.
Measurement The counter increments in voice channel assignment when target
Point cell in directed retry is TDD cell and successfully obtains channel


Unit Times
C901050029 Number
attempts TDD cell for data
Definition Number of assignment for retry attempts TDD cell for data
TDD cell for data channel.
attempts TDD cell for data channel and represent TDD cell traffic
sharing status in data channel assignment.
Measurement The counter increments in data channel assignment when source
Point 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.


ATTEMPTS
Unit Times
TDD cell for data
TDD cell for data
directed retry to TDD cell for data channel.
Usage This counter is used to find out the number of assignment ex-
ecutions due to directed retry to TDD cell for data channel and
represent TDD cell directed retry status.
Measurement The counter increments in data channel assignment when target
Point cell in directed retry is TDD cell and successfully obtains channel


Unit 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 ob-
struction status on A-interface in assignment flow.
Measurement Target cell checks circuit after receiving assignment request message
Point sent by MSC; the counter increments if the circuit is obstructed.

FIGURE 661 MEASUREMENT POINT OF ASSIGNMENT FAILURE DUE TO

CIRCUIT OBSTRUCTION ON A-INTERFACE
Unit Times
unsuccessful due to circuit
obstruction unmatched
Definition Assignment unsuccessful due to circuit obstruction unmatched
Description This counter counts the number of assignment failure due to circuit
unmatched on A-interface.
due to circuit unmatched on A-interface and to check circuit un-
matched status on A-interface in assignment flow.
Measurement Target cell checks circuit after receiving assignment request message
Point sent by MSC; the counter increments if the circuit is unmatched.


Unit 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.
due to no valid radio resource and to check radio resource assign-
ment status in assignment flow.
Measurement � Source cell sends channel request to target cell after receiving
Point 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 receiv-
ing assignment request message; the counter increments if Ra-
dio_App is overtime due to no responding message. The mea-
surement point is A, as shown inFigure 663.


Unit Times
unsuccessful due to other
causes
Definition Assignment unsuccessful due to other causes
Description This counter counts the number assignment failure due to other
causes on A-interface.
due to other causes and to check A-interface status in assignment
flow.
Measurement Target cell receives assignment request message sent by MSC; the
Point 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 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 mes-
sage, it attempts to assign the voice channel. If there is no suit-
able 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 emer-
gency call.
Measurement BSC fails to assign channel due to no available resource, if forced
Point 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 in-
stance, then the counter increments when the forcing release in-
stance sends the forced release message to the forced release
instance. The measurement point is A, as shown in Figure 665.

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)
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 suc-
cessful. 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 assign-
ments due to forced release during the MS access process of an
emergency call.
Measurement During the voice channel assignment process, if the radio resource
Point request fails and forced release is allowed, the forcing release in-
stance sends the forced release message to the forced release in-
stance. If the message of resource available is received, then the
resource is obtained successfully, and in this case, the counter in-
crements. 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 (emer-
gency service)
Description When BSC fails to assign voice channel due to no available re-
source, it attempts forced handover towards external cell. If the
call is an emergency call, the counter counts the number of forced
handover attempts.
due to forced handover during the MS access process of an emer-
gency call.
Measurement During an emergency call, BSC fails to assign voice channel. If
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 han-
dover instance. The measurement point is A, as shown in Figure
667.


ATTEMPTS
Unit Times
assignment executions
channel due to forced
handover (emergency
service)
Definition Number of assignment executions channel due to forced han-
dover(emergency service)
call is an emergency call, the counter counts the number of suc-
cessful forced handover.
ments due to forced handover during the MS access process of an
emergency call.
Measurement During the voice channel assignment process for emergency call, if
Point 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 ser-
vice)
able 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).
due to queuing during the MS access process of an emergency call.
Point queuing is allowed, then the instance is added to the queue and
Figure 669.


ATTEMPTS
Unit Times
(emergency service)
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 suc-
cessful, the counter counts the number of successful assignments
due to queuing (emergency service).
ments due to queuing during the MS access process of an emer-
gency call.
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)
source, 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.
Point forced handover is allowed but there is no suitable forced handover
instance, then the counter increments. The measurement point is

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)
Definition Number of send forced handover request to lower PRI user (as-
signment forced handover)
source, 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 When BSC fails to assign voice channel, if forced handover is al-
Point lowed 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 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)
source, it attempts forced handover towards external cell. If forc-
ing handover target instance is found in the cell, the forced han-
dover is initiated. Then, if the forced handover fails due to re-
source 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 re-
quest failure.
Point lowed and there is suitable forcing handover instance, then the

counter increments in the following case: the forcing handover in-

stance 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 measure-
ment 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)
Definition Number of lower PRI user handover failure (assignment forced
handover)
source, it attempts forced handover towards external cell. If forc-
ing handover target instance is found in the cell, the forced han-
dover is initiated. Then, if the forced handover fails due to han-
dover execution failure, the counter counts the number of receiv-
ing handover execution failure message from low priority user dur-
ing the forced handover.
access process, this counter is used to find out the number of re-
ceiving the forced handover failure message due to handover ex-
ecution failure.

Point lowed and there is suitable forced handover target instance, then
the counter increments in the following case: the forcing han-
dover 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 fail-
ure. 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 han-
dover)
source, 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 ac-
cess process, this counter is used to find out the number of timeout
due to waiting for forced handover target instance resource.

Point lowed and there is suitable forced handover target instance, then
the counter increments when the waiting for forced handover tar-
get 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)
Definition Number of forced release target not found (assignment forced re-
lease)
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.
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)
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 ac-
cess process, this counter is used to find out the number of timeout
due to waiting for forced release target instance resource.
Measurement When BSC fails to assign voice channel, if forced release is al-
Point lowed and there is suitable forced release target instance, then
the counter increments when the waiting for forced release tar-
get instance resource is timeout. The measurement point is B, as

FIGURE 677 MEASUREMENT POINT OF NUMBER OF TIMEOUT FOR WAIT

RESOURCE (ASSIGNMENT FORCED RELEASE
Unit Times
get before grab released
channel (assignment forced
handover)
Definition Number of get before grab released channel (assignment forced
handover)
handover succeeds in getting the forced handover target resource,
the counter counts the number of preempting the released chan-
nel during the forced handover.
access process, this counter is used to find out the number of pre-
empting the released channel.
Measurement During the voice channel assignment process for emergency call,
Point 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)
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 suc-
cessful, and the counter counts the number of successful forced
releases (emergency service).
ments due to forced release during the MS access process.
Point request fails and forced release is allowed, the forcing release in-
stance sends the forced release message to the forced release in-
stance. If the message of resource available is received, then the
resource is obtained successfully, and in this case, the counter in-
crements. The measurement point is B, as shown in Figure 679.


Unit Times
C901050050 The count of

Assignment using FULL IP
A-Interface
Statistics object CELL
Description 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 transmis-
sion mode according to the assignment request's content. After
MS assignment is completed, BSC decides the A-interface trans-
mission mode for the service before sending the assignment com-
pletion message. If the A-interface transmission mode is all-IP
A-interface transmission, the counter increments. The measure-

FIGURE 680 MEASUREMENT POINT OF THE COUNT OF ASSIGNMENT USING FULL IP A-INTERFACE
Unit Times

Assignment using PCM over
IP A-Interface
pletion message. If the A-interface transmission mode is PCMoIP
transmission, the counter increments. The measurement point is

FIGURE 681 MEASUREMENT POINT OF THE COUNT OF ASSIGNMENT USING PCM OVER IP
A-INTERFACE
Unit Times

Assignment using PCM over
TDM A-Interface
pletion message. If the A-interface transmission mode is TDM
transmission, the counter increments. The measurement point is

FIGURE 682 MEASUREMENT POINT OF THE COUNT OF ASSIGNMENT USING PCM OVER TDM
A-INTERFACE
Unit Times

Assignment Failure caused
by "Requested Codec Type
or Codec Configuration not
supported"
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 assign-
ment 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.

FIGURE 683 MEASUREMENT POINT OF THE COUNT OF ASSIGNMENT FAILURE CAUSED BY "REQUESTED
CODEC TYPE OR CODEC CONFIGURATION NOT SUPPORTED"
Unit Times

by "Requested Codec Type
or Codec Configuration
unavailable"
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 incre-
ments. The measurement point is B, as shown in Figure 684.

CODEC TYPE OR CODEC CONFIGURATION UNAVAILABLE"
Unit Times

by "Requested A-Interface
Type not supported"
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 fail-
ure message is sent to MSC, and the counter increments. The

A-INTERFACE TYPE NOT SUPPORTED"
Unit Times

by "Requested A-Interface
Type unavailable"
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 assign-
ment 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 Times

by "Call Identifier already
allocated"
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 incre-

FIGURE 687 MEASUREMENT POINT OF THE COUNT OF ASSIGNMENT FAILURE CAUSED BY "CALL
IDENTIFIER ALREADY ALLOCATED"
Unit Times

by "Requested Redundancy
Level not supported"
MSC's assignment request, which is of data type or fax service
type, is received, the system selects voice version as well as trans-
mission redundancy mode according to the field Codec List (MSC
Preferred) in the assignment request. If the transmission redun-
dancy mode is not supported by BSC, then the assignment failure
message is sent to MSC, and the counter increments. The mea-

REDUNDANCY LEVEL NOT SUPPORTED"
Unit Times

by "Call Access Control"
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.

FIGURE 689 MEASUREMENT POINT OF THE COUNT OF ASSIGNMENT FAILURE CAUSED BY "CALL
ACCESS CONTROL"
Unit 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 1. The channel type requested by the assignment is same as the
Point 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 re-
quested by the assignment is unmatched with that actually
occupied.
2. On re-assignment, the channel type for re-assignment is re-
lated 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 assign-
ment is unmatched with that actually occupied.
Unit Times

C901050061 Success
Number of mode modify for
assignment
Description This counter counts the number of successes for mode modifica-
tion.
Usage This counter counts the number of successes for mode modifica-
tion in the process of assignment.
Measurement This counter increments while receiving the response message
Point 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 di-
rected retry due to radio cause and if the source cell finds out a bet-
ter cell according to the measurement report on SDCCH, it sends
the Radio_App message to the destination cell, and the counter

FIGURE 690 MEASUREMENT POINT OF NUMBER OF DIRECTED RETRIES DUE

TO RADIO CAUSES
This counter is supported in version V6.20.614b.

Unit Times
Statistics Object 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 re-
ceives the message of radio resource available from the destina-
tion cell. The measurement point is B, as shown in Figure 691.

FIGURE 691 NUMBER OF ASSIGNMENT EXECUTIONS DUE TO DIRECTED RETRY

Unit Times
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 di-
rected retry due to radio cause and if the source cell finds out a bet-
ter cell according to the measurement report on SDCCH, it sends
the Radio_App message to the destination cell, and the counter

FIGURE 692 MEASUREMENT POINT OF NUMBER OF DIRECTED RETRIES DUE

TO RADIO CAUSES

Unit Times
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 re-
ceives the message of radio resource available from the destina-
tion cell. The measurement point is B, as shown in Figure 693.


Unit Times


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 at-
tempts due to good C/I .................................................... 635
C901060009 Number of SDCCH inter-subcell handover at-
tempts 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


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 traf-
fic ................................................................................. 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 as-
signment 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

Chapter 12 Handover Cause Measurement

Fragment reorganization .................................................. 672
C901060074 Number of TCH/F handover attempts due to en-
ergy conservation ............................................................ 673
C901060075 Number of TCH/F handover attempts due to en-
ergy 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 re-
ducing 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 MAS-
TERPWR_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 al-
gorithm judgment module can carry out handover due to several
different handover causes, so as to realize functions such as opti-
mizing resource usage, improving call quality and rescuing calls.

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 In assignment process, the counter increments if source instance
Point 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 Times

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 BSC carries out handover judgment after receiving SDDCH mea-
Point surement report; the counter increments if judgment result is yes
and handover cause is uplink signal strength. The measurement
Unit Times
Related Features ZGO-02-02-004 SDCCH/SDCCH Handover
due to DL received strength
Definition Number of SDCCH handover attempts due to DL received strength
low downlink received strength (on SDCCH).
due to downlink received strength (on SDCCH); high number
means SDCCH downlink signal strength is low.

and handover cause is downlink signal strength. The measure-

Unit Times
SDCCH Handover attempt
due to UL quality
Definition Number of SDCCH Handover attempt due to UL quality.
bad uplink quality (on SDCCH).
due to uplink quality (on SDCCH); high number means SDCCH
uplink quality is bad.
and handover cause is uplink quality. The measurement point is
Unit Times

due to DL quality
Definition Number of SDCCH Handover attempt due to DL quality.
bad downlink quality (on SDCCH).
due to downlink quality (on SDCCH); high number means SDCCH
downlink quality is bad.
and handover cause is downlink quality. The measurement point
Unit Times
Definition Number of SDCCH handover attempts due to UL interference.
high uplink interference (on SDCCH).
due to uplink interference (on SDCCH); high number means SD-
CCH uplink interference is high.
Point surement report; the counter increments if judgment result is
yes and handover cause is uplink interference. The measurement

Unit Times
Definition Number of SDCCH handover attempts due to DL interference.
high downlink interference (on SDCCH).
due to downlink interference (on SDCCH); high number means
SDCCH downlink interference is high.
and handover cause is downlink interference. The measurement
Unit Times

C901060008 Number
of SDCCH inter-subcell
good C/I
Definition Number of SDCCH inter-subcell handover attempts due to good
C/I
high C/I RATIO (on SDCCH). This handover only happens in sub-
cell configuration and C/I algorithm is used; MS is handed over
from first cell to second cell.
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.
and handover cause is C/I RATIO (on SDCCH) (Good C/I). The
Unit Times
C901060009 Number
of SDCCH inter-subcell
bad C/I
Definition Number of SDCCH inter-subcell handover attempts due to bad C/I

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.
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.
and handover cause is C/I RATIO (on SDCCH) (Bad C/I). The mea-
Unit Times
C901060010 Number
SDCCH of handover
attempts due to PBGT
Definition 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.
due to PBGT (on SDCCH); high number means present cell’s SD-
CCH signal is worse than that of the adjacent cell.
and handover cause is PBGT (on SDCCH). The measurement point

Unit 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.
due to large TA (on SDCCH); its value can represent mobility of
the subscriber in the cell in a certain extent.
and handover cause is large TA (on SDCCH). The measurement
Unit Times

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 up-
link break up quickly (on SDCCH). If SDCCH uplink level decreases
abruptly in several continuous measurement reports, handover at-
tempts due to uplink break up quickly may occur.
due to uplink break up quickly (on SDCCH); its value can represent
stability of the current radio environment in a certain extent.
and handover cause is uplink break up quickly (on SDCCH). The
Unit Times
ZGO-02-02-006 Rapid Level Drop Handover
ZGO-02-02-015 Enhanced Cell Reselection Procedure
due to macro-micro switch
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.


due to macro-micro switch (on SDCCH); its value can represent
the status of micro cell absorbing traffic.
and handover cause is macro-micro switch (on SDCCH). The mea-
Unit Times
Related Features 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.
due to MSC request (on SDCCH); its value can represent the status
that MSC adjusts the present cell traffic.
Measurement BSC carries out handover judgment after receiving HO_ENQUIRY mes-
Point sage sent by MSC; the counter increments if judgment result is
yes. The measurement point is A, as shown inFigure 707.

FIGURE 707 HO_ENQUIRY HANDOVER
Unit Times
due to traffic
Definition Number of SDCCH handover attempts due to traffic.
Description This counter counts the number of handover attempts due to traf-
fic (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.
due to traffic (on SDCCH); its value can represent the status that
BSC adjusts the present cell traffic.
Measurement BSC carries out handover judgment after receiving SDCCH traf-
Point fic 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 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.
TA and wastage (on SDCCH). This handover only happens in sub-
cell 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.
due to large TA and wastage (on SDCCH); its value can represent
the mobility of subscriber among sub-cells in the cell.
and handover cause is large TA and wastage (on SDCCH). The

Unit 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 sub-
TA and PassLoss are lower than set threshold, MS is handed over
due to small TA and wastage (on SDCCH); its value can represent
and handover cause is small TA and wastage (on SDCCH). The
Unit 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).
due to a good standard level in FDD adjacent cell (on SDCCH); its
value can represent status that 3G network absorbs traffic.
and handover cause is good standard level in FDD adjacent cell (on
SDCCH). The measurement point is A, as shown in Figure 711.
Unit Times
C901060019 Number
due to forced transfer
Definition Number SDCCH handover attempts due to forced transfer.
Description This counter counts the number of forced transfer handover at-
tempts (on SDCCH). If the TCH utilizing rate of the present cell
reaches a set percentage of the threshold, BSC will try to handover

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 han-
dover attempts (on SDCCH); its value can represent the present
cell’s channel utilizing status and traffic sharing status.
and handover cause is forced transfer handover attempts (on SD-
CCH). The measurement point is A, as shown in Figure 712.
Unit Times
Related Features ZGO-02-02-003 Directed-Shift Handover
SDCCH handover during
assignment due to forced
transfer
Definition Number of SDCCH handover during assignment due to forced
transfer.
Description This counter counts the number of forced handovers during as-
signment (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 dur-
ing assignment (on SDCCH); its value can represent the present
cell’s TCH utilizing status and traffic sharing status.
Measurement BSC has no available TCH to allocate during the assignment
Point 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 Times
SDCCH handover during
transfer
Definition Number of SDCCH handover during handover due to forced trans-
fer.
Description This counter counts the number of forced handovers during han-
dover (on SDCCH).

Usage This counter is used to find out frequency of forced handovers

during handover (on SDCCH); its value can represent the present
Measurement BSC has no available TCH to allocate during the handover process
Point and it carries out forced handover judgment; the counter incre-
ments if judgment result is yes and the channel type of forced han-
dover instance is SDCCH. The measurement point is A, as shown
in Figure 714.
Unit Times
due to increased TA
Definition Number of SDCCH handover attempts due to increased TA.
Description This counter counts the number of handover attempts due to in-
creased 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.
and handover is from second cell to first cell. The measurement
Unit 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 de-
creased TA (on SDCCH). This handover only happens in expanding
counts the number of MS handover from first cell to second cell
first cell to second cell in sub-cell.
and handover is from first cell to second cell. The measurement

Unit Times
due to other factors
Definition Number of SDCCH Handover attempt due to other factors.
other reason except reasons mentioned above (on SDCCH).
due to any other reason (on SDCCH).
and handover cause is any other reason. The measurement point
Unit Times

Definition Number of TCH/F handover attempts due to quick break up of UL.
link break up quickly (on TCH/F). If TCH/F uplink level decreases
due to uplink break up quickly (on TCH/F); its value can represent
Measurement BSC carries out handover judgment after receiving TCH/F mea-
and handover cause is uplink break up quickly (on TCH/F). The
Unit Times
Definition Number of TCH/F handover attempts due to macro-micro switch.
macro-micro switch (on TCH/F). If adjacent cell level is not lower


due to macro-micro switch (on TCH/F); its value can represent the
status of micro cell absorbing traffic.
and handover cause is macro-micro switch (on TCH/F). The mea-
Unit Times
ZGO-02-02-001 Handover between Macro- and Micro-cells
due to MSC request
Definition Number of TCH/F handover attempts due to MSC request.
request (on TCH/F). Handover is originated by MSC, some calls
due to MSC request (on TCH/F); its value can represent the status
Measurement BSC carries out handover judgment after receiving “HO_ENQUIRY”
Point message sent by MSC; the counter increments if judgment result
is yes. The measurement point is A, as shown in Figure 720.

Unit 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.
due to traffic (on TCH/F); its value can represent the status that
Measurement BSC carries out handover judgment after receiving TCH/F traffic
Point alarm, the counter increments if judgment result is yes. The mea-

Unit Times
Definition Number of TCH/F handover attempts due to large TA and wastage.
TA and wastage (on TCH/F). This handover only happens in sub-
due to large TA and wastage (on TCH/F); its value can represent
and handover cause is large TA and wastage (on TCH/F). The mea-
Unit Times

Definition Number of TCH/F handover attempts due to small TA and wastage.
TA and wastage (on TCH/F). This handover only happens in sub-
due to small TA and wastage (on TCH/F); its value can represent
and handover cause is small TA and wastage (on TCH/F). The mea-
Unit 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.
good standard level in 3G adjacent cell (on TCH/F).


due to a good standard level in 3G adjacent cell (on TCH/F); its
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 Times
Definition Number of TCH/F handover attempts due to forced transfer.
tempts (on TCH/F). If the TCH utilizing rate of the present cell
handover.
dover attempts (on TCH/F); its value can represent the present
yes and handover cause is forced transfer handover attempts (on
TCH/F). The measurement point is A, as shown in Figure 725.

Unit Times
ZGO-02-02-003 Directed-Shift Handover
TCH/F handover during
assignment due to forced
transfer
Definition Number of TCH/F handover during assignment due to forced trans-
fer.
signment (on TCH/F). If all TCH of the present cell are occupied
kind of handover is called forced handover.
ing assignment (on TCH/F); its value can represent the present
forced handover instance is TCH/F. The measurement point is A,

Unit Times
during handover due to
forced transfer
Definition Number of TCH/F handover attempts during handover due to
forced transfer.
dover (on TCH/F).
ing handover (on TCH/F); its value can represent the present cell’s
TCH utilizing status and traffic sharing status.
ments 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 Times
due to TA increase
Definition Number of TCH/F handover attempts due to TA increase.
creased TA (on TCH/F). This handover only happens in expanding

Unit Times
due to TA decrease
Definition Number of TCH/F handover attempts due to TA decrease.
creased TA (on TCH/F). This handover only happens in expanding

Unit Times
Definition Number of TCH/H handover attempts due to quick break up of UL.
link break up quickly (on TCH/H). If TCH/H uplink level decreases
due to uplink break up quickly (on TCH/H); its value can represent
Measurement BSC carries out handover judgment after receiving TCH/H mea-
and handover cause is uplink break up quickly (on TCH/H). The
Unit Times

Definition Number of TCH/H handover attempts due to macro-micro switch.
macro-micro switch (on TCH/H). If adjacent cell level is not lower
due to macro-micro switch (on TCH/H); its value can represent the
status of micro cell absorbing traffic.
and handover cause is macro-micro switch (on TCH/H). The mea-
Unit Times
ZGO-02-02-001 Handover between Macro- and Micro-cells
due to MSC request
Definition Number of TCH/H handover attempts due to MSC request.
request (on TCH/H). Handover is originated by MSC, some calls


due to MSC request (on TCH/H); its value can represent the status
Measurement BSC carries out handover judgment after receiving HO_ENQUIRY mes-
Point sage sent by MSC; the counter increments if judgment result is
yes. The measurement point is A, as shown in Figure 732.
Unit 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.
due to traffic (on TCH/H); its value can represent the status that
Measurement BSC carries out handover judgment after receiving TCH/H traffic
Point alarm, the counter increments if judgment result is yes. The mea-

Unit Times
Definition Number of TCH/H handover attempts due to large TA and wastage.
TA and wastage (on TCH/H). This handover only happens in sub-
due to large TA and wastage (on TCH/H); its value can represent
and handover cause is large TA and wastage (on TCH/H). The mea-

Unit Times
Definition Number of TCH/H handover attempts due to small TA and wastage.
TA and wastage (on TCH/H). This handover only happens in sub-
due to small TA and wastage (on TCH/H); its value can represent
and handover cause is small TA and wastage (on TCH/H). The mea-
Unit Times

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.
good standard level in 3G adjacent cell (on TCH/H).
due to a good standard level in 3G adjacent cell (on TCH/H); its
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 Times

Definition Number of TCH/H handover attempts due to forced transfer.
tempts (on TCH/H). If the TCH utilizing rate of the present cell
handover.
dover attempts (on TCH/H); its value can represent the present
yes and handover cause is forced transfer handover attempts (on
TCH/H). The measurement point is A, as shown in Figure 737.
Unit Times
during assignment due to
forced transfer
Definition Number of TCH/H handover attempts during assignment due to
forced transfer.

signment (on TCH/H). If all TCH of the present cell are occupied
kind of handover is called forced handover.
ing assignment (on TCH/H); its value can represent the present
forced handover instance is TCH/H. The measurement point is A,
Unit Times

during handover due to
forced transfer
Definition Number of TCH/H handover attempts during handover due to
forced transfer.
dover (on TCH/H).
ing handover (on TCH/H); its value can represent the present cell’s
TCH utilizing status and traffic sharing status.
ments if judgment result is yes and the channel type of forced han-
dover instance is TCH/H. The measurement point is A, as shown
in Figure 739.
Unit Times

during handover due to TA
increase
Definition Number of TCH/H handover attempts during handover due to TA
increase.
creased TA (on TCH/H). This handover only happens in expanding
Unit Times

during handover due to TA
decrease
Definition Number of TCH/H handover attempts during handover due to TA
decrease.
creased TA (on TCH/H). This handover only happens in expanding
Unit Times
Definition Number of TCH/H handover attempts due to other reasons

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.
and handover is caused by other reasons. The measurement point
Unit Times
due to CS channel transfer
Definition 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 han-
dover 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 During call service, due to other call services released, CS service
Point channel transfer is issued to do intra-cell handover. The service
occupying middle timeslot can be migrated to edge timeslot, pro-
viding available sustainable channels for PS. This counter incre-
ments if the channel type of instance is TCH/F. The measurement

FIGURE 743 CS CHANNEL TRANSFER HANDOVER
Unit Times
Related Features 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 chan-
nel on TCH/H. This may lead to intra-cell handover.
channel handover on TCH/H by BSC.
Measurement During call service, due to other call service released, CS service
Point channel transfer is issued to do intra-cell handover. The service
occupying middle timeslot service can be migrated to edge times-
lot, providing available continual channel. This counter increments
if channel type for handover instance is TCH/H. The measurement

Unit Times
C901060073 Number
of TCH/H handover
attempts due to Fragment
reorganization
Definition Number of TCH/H handover attempts due to Fragment reorgani-
zation
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 com-
bining two half-rate channel on TCH/H by BSC.
Measurement New call service instance does not apply for full-rate channel, or
Point due to other call service released, fragment reorganization is is-
sued to do intra-cell handover. It will combine two half-rate service
into one timeslot. The couner increments while one full-rate chan-
nel is idle. The measurement point is A, as shown in Figure 745.

Unit 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 Carrier is intelligently powered off by energy conservation, do in-
Point tra-cell handover for the call service on the carrier to be powered
off and migrated to other carrier. If channel type of handover in-
stance is TCH/F, this counter increments. The measurement point

Unit Times
Related Features ZGO-04-04-001 TCH Migration to BCCH TRX
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/H by BSC.
Usage This counter is used to find out handover frequency due to energy
conservation on TCH/H by BSC.
Measurement Carrier is intelligently powered off by energy conservation, do in-
Point tra-cell handover for the call service on the carrier to be powered
off and migrated to other carrier. If channel type of handover in-
stance is TCH/H, this counter increments. The measurement point

Unit Times
Related Features 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 chan-
nel forcedly released.
service seizured by PS on TCH/F.
Measurement After PS service channel application is failed, do intra-cell handover
Point 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

Unit Times
due to CS channel is forced
release
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.
service seizured by PS on TCH/H.
Measurement After PS service channel application is failed, do intra-cell handover
Point 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 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 N/A
Point
Unit Times

due to downlink rapid drop
high downlink level on SDCCH.
Usage This counter measures the frequency of handover due to the down-
link level on SDCCH. The higher value indicates the higher down-
link level on SDCCH.
Measurement This counter increments if the handover decision is done after re-
Point ceiving the measurement report on SDCCH by BSC and the han-
dover is caused by the rapid downlink drop.
Unit Times
high downlink level on TCH/F.
link level on TCH/F. The higher value indicates the higher downlink
level on TCH/F.
Point ceiving the measurement report on TCH/F by BSC and the han-
Unit Times
high downlink level on TCH/H.
link level on TCH/H. The higher value indicates the higher downlink
level on TCH/H.

Point ceiving the measurement report on TCH/H by BSC and the han-
Unit Times
C901060082 Attempts of
handover on TCH/F caused
by power adjustment
Description After the dynamic power sharing function is enabled, iBSC per-
forms real-time monitoring for the power usage of each RRU's
timeslots. When a channel is allocated, the power it uses is reg-
istered; 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 han-
dover due to RRU power congestion.
Measurement When iBSC detects the power a RRU's timeslot currently uses
Point reaches the threshold of power congestion control, it selects
occupying TCH/F, the counter increments.
handover on TCH/H caused
by power adjustment
Description After the dynamic power sharing function is enabled, iBSC per-
forms real-time monitoring for the power usage of each RRU's
timeslots. When a channel is allocated, the power it uses is reg-
istered; 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


occupying TCH/H, the counter increments.
Usage This counter is used to find out the frequency of HR service han-
dover due to RRU power congestion.
Measurement When iBSC detects the power a RRU's timeslot currently uses
Point reaches the threshold of power congestion control, it selects
occupying TCH/H, the counter increments.
by local switch
Description The counter counts when the local switch initiates FR service han-
dover.
This counter is supported in version V6.20.614a.
Unit Times
handover on TCH/H caused
by local switch
Description The counter counts when the local switch initiates HR service han-
dover.
Unit Times

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 num-
ber 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 al-
lowed, the counter counts.
FIGURE 750 HANDOVER ATTEMPT DUE TO REDUCING BAND RESOURCES OF

IPABIS

Unit Times
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, af-
ter the EV_DBS_CS_MOV message is received, the system judges

FIGURE 751 TRAFFIC-MIGRATION HANDOVER DUE TO MASTERPWR_ALM

FROM TRX

Unit Times
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, af-
ter the EV_DBS_CS_MOV message is received, the system judges
FIGURE 752 TRAFFIC-MIGRATION HANDOVER DUE TO MASTERPWR_ALM

FROM TRX

Unit Times

directed retry for PBGT
Description After MSC assigns the channel, if the measurement report on SD-
CCH 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 in-
dicates a cell with better signal, then the better cell is selected
for channel assignment attempt, and the counter increments. The

Unit Times

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 han-
dover is required and the handover is due to downlink quality fast
fading, the counter increments. The measurement point is A, as

Unit Times
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.

After BSC receives the measurement report on TCH/F, it performs


Unit Times
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 Times


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 fail-
ure ................................................................................ 691
C901070003 Number of SDCCH drops due to LAPD link fail-
ure ................................................................................ 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 fail-
ure ................................................................................ 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 con-
tact 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 re-
lease by other calls .......................................................... 706
C901070021 Number of voice TCH/F drops due to other fail-
ure ................................................................................ 707
C901070022 Number of data TCH/F drops due to loss of con-
tact 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

C901070026 Number of data TCH/F drops due to forced re-

C901070028 Number of data TCH/F drops due to other fail-
ure ................................................................................ 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 con-
tact 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 re-
C901070042 Number of voice TCH/H drops due to other fail-
ure ................................................................................ 725
C901070043 Number of data TCH/H drops due to loss of con-
tact 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 re-
C901070049 Number of data TCH/H drops due to other fail-
ure ................................................................................ 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

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 Ac-
tive/Standby Changeover ................................................. 770
C901070097 Number of data TCH/F drops due to BIPB Ac-
C901070098 Number of signaling TCH/H drops due to BIPB
C901070099 Number of voice TCH/H drops due to BIPB Ac-
C901070100 Number of data TCH/H drops due to BIPB Ac-
C901070101 Number of SDCCH drops due to LAPD Ac-
C901070102 Number of voice TCH/F drops due to LAPD Ac-
C901070103 Number of data TCH/F drops due to LAPD Ac-
C901070104 Number of signaling TCH/F drops due to LAPD
C901070105 Number of voice TCH/H drops due to LAPD Ac-
C901070106 Number of data TCH/H drops due to LAPD Ac-

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 Ac-
C901070111 Number of SDCCH drops due to BTS fail-
ure ................................................................................ 776
C901070112 Number of signaling TCH/F drops due to BTS
failure ............................................................................ 777
C901070113 Number of voice TCH/F drops due to BTS fail-
ure ................................................................................ 778
C901070114 Number of data TCH/F drops due to BTS fail-
ure ................................................................................ 779
C901070115 Number of signaling TCH/H drops due to BTS
failure ............................................................................ 780
C901070116 Number of voice TCH/H drops due to BTS fail-
ure ................................................................................ 781
C901070117 Number of data TCH/H drops due to BTS fail-
ure ................................................................................ 782
C901070118 Call Drop by Releasing Local Switch................. 783
Overview
Channels that take part in the measurement statistic include SD-
CCH, 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 re-
lease, forced release by other calls, handover failure, as well as
other failure.
SDCCH drops due to loss of
contact with RANA
Definition 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 The counter counts the number of failures due to loss of contact
Point 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
� 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
Unit 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 fail-
ures (On SDCCH). The counter increments if the phenomenon that
call drops after MS has obtained SDCCH is caused by radio link fail-
ures.
radio link failures (On SDCCH).
Measurement The counter increments when BSC receives CONNectiOn FAILure IN-
Point DicatiOn message on Abis interface on SDCCH. The measurement

FIGURE 758 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE

ASSIGNMENT PROCESS
Unit Times
ZGO-04-02-007 AMR Radio Link Timers
SDCCH drops due to LAPD
link failure
Definition Number of SDCCH drops due to LAPD link failure
Description This counter counts the number of call drop due to LAPD link fail-
ures (On SDCCH). The counter increments if the phenomenon that
call drops after MS has obtained SDCCH is caused by LAPD link fail-
ures.
LAPD link failures (On SDCCH).
Measurement The counter increments when BSC receives DLREL_IND message
Point 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.
OMC-R forced releases (on SDCCH).
Measurement The counter increments when BSC receives OMC-R forced release
Point message from database on SDCCH. The measurement point is A,

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 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 phe-
nomenon that call drops after MS has obtained SDCCH is caused
by forced releases by other calls.
forced releases by other calls (On SDCCH).
Measurement The counter increments when BSC receives forced release mes-
Point sage 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 Number of SDCCH drops due to other failure
Description 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.
other failures (On SDCCH).
Measurement The counter increments when T3107 is overtime under ASSIGN
Point status on SDCCH, or when timer that waits for access is overtime
or forced release caused by other faults. The measurement point

FIGURE 762 MEASUREMENT POINT OF TWAITMSACCESS OVERTIME
Unit Times
to loss of contact with RANA
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 in-
crements 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.
RANCS losing contact with RANA (on TCH/F signaling channel).
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-inter-
face from RANA is received, the counter increments; mean-

while, BSC releases the channel and instance, the measure-

ment point is A2, as shown inFigure 763.

ASSIGNMENT PROCESS
Unit Times
to radio link failure
Definition Number of signaling TCH/F drops due to radio link failure
ures (On TCH/F signaling). The counter increments if the phenom-
enon that call drops after MS has obtained TCH/F signaling channel
is caused by radio link failures.
radio link failures (On TCH/F signaling).
Point DicatiOnmessage on Abis interface on TCH/F signaling channel.
The measurement point is A, as shown inFigure 764.


ASSIGNMENT PROCESS
Unit Times
to LAPD link failure
Definition Number of signaling TCH/F drops due to LAPD link failure
Description This counter counts the number of call drops due to LAPD link fail-
ures (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.
LAPD link failures (on TCH/F signaling channel).
Point from LAPD on TCH/F signaling channel. The measurement point


ASSIGNMENT PROCESS
Unit Times
to OMC-R forced release
Definition Number of signaling TCH/F drops due to OMC-R forced release
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.
OMC-R forced releases (on TCH/F signaling channel).
Point message from database on TCH/F signaling channel. The mea-


ASSIGNMENT PROCESS
Unit Times
to forced release by other
calls
Definition Number of signaling TCH/F drops due to forced release by other
calls
by other calls (on TCH/F signaling channel). The counter incre-
ments if the phenomenon that call drops after MS has obtained
TCH/F signaling channel is caused by forced releases by other calls.
forced releases by other calls (on TCH/F signaling channel).
Point sage from other calls on TCH/F signaling channel. The measure-


Unit Times
to other failure
Definition Number of signaling TCH/F drops due to other failure
(on TCH/F signaling channel). The counter increments if the phe-
nomenon 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 fail-
ure, OMCR forced release, forced release by other calls, handover
failure).
other failures (on TCH/F signaling channel).
Point status on TCH/F, or when timer that waits for access is overtime

Unit Times
loss of contact with RANA
Definition Number of voice TCH/F drops due to loss of contact with RANA
contact with RANA (on TCH/F voice channel). The counter incre-
TCH/F voice channel is caused by failures due to RANCS losing
contact with RANA (on TCH/F voice channel).
RANCS losing contact with RANA (on TCH/F voice channel).
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 mea-

FIGURE 769 CALL DROP DUE TO A-INTERFACE FAILURE IN ASSIGNMENT

PROCESS
Unit Times
LAPD link failure
Definition Number of voice TCH/F drops due to LAPD link failure
ures (on TCH/F voice channel). The counter increments if the phe-
nomenon that call drops after MS has obtained TCH/F voice chan-
nel is caused by LAPD link failures.
LAPD link failures (on TCH/F voice channel).

Measurement The counter increments when BSC receives DLREL_INDmessage from

Point 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 Times
Definition 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.
OMC-R forced releases (on TCH/F voice channel).
Point message from database on TCH/F voice channel. The measure-
FIGURE 771 CALL DROP DUE TO OMC-R FORCED RELEASE IN ASSIGNMENT

PROCESS
Unit Times

forced release by other calls
Definition Number of voice TCH/F drops due to forced release by other calls
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.
forced releases by other calls (on TCH/F voice channel).
Point sage from other calls on TCH/F voice channel. The measurement

ASSIGNMENT PROCESS
Unit Times

other failure
Definition 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 in-
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 han-
dover failure.
other failures (on TCH/F voice channel).

Unit Times
Definition Number of data TCH/F drops due to loss of contact with RANA
contact with RANA (on TCH/F data channel). The counter incre-
TCH/F data channel is caused by failures due to RANCS losing con-
tact with RANA (on TCH/F data channel).
RANCS losing contact with RANA (on TCH/F data channel).
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 Times
radio link failure
Definition Number of data TCH/F drops due to radio link failure
ures (on TCH/F data channel). The counter increments if the phe-
nomenon that call drops after MS has obtained TCH/F data channel
radio link failures (on TCH/F data channel).
Point message on Abis interface on TCH/F data channel. The
DicatiOn

FIGURE 775 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT

PROCESS
Unit Times
LAPD link failure
Definition Number of data TCH/F drops due to LAPD link failure
ures (on TCH/F data channel). The counter increments if the phe-
nomenon that call drops after MS has obtained TCH/F data channel
is caused by LAPD link failures.

LAPD link failures (on TCH/F data channel).
Point from LAPD on TCH/F data channel. The measurement point is A,

PROCESS
Unit Times
Definition Number of data TCH/F drops due to OMC-R forced release

releases (on TCH/F data channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/F data
OMC-R forced releases (on TCH/F data channel).
Point message from database on TCH/F data channel. The measure-

PROCESS
Unit Times

Definition Number of data TCH/F drops due to forced release by other calls
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.
forced releases by other calls (on TCH/F data channel).
Point sage from other calls on TCH/F data channel. The measurement

ASSIGNMENT PROCESS
Unit Times

other failure
Definition Number of data TCH/F drops due to other failure
(on TCH/F data channel). The counter increments if the phenom-
enon 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).
other failures (on TCH/F data channel).
Unit Times

to loss of contact with RANA
Definition Number of signaling TCH/H drops due to loss of contact with RANA
contact with RANA (on TCH/H signaling channel). The counter in-
TCH/H signaling channel is caused by failures due to RANCS losing
contact with RANA (on TCH/H signaling channel).
RANCS losing contact with RANA (on TCH/H signaling channel).
Measurement The counter counts the number of failures due to loss of con-
Point tact 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 fail-
ure 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-inter-
face from RANA is received, the counter increments; mean-

ASSIGNMENT PROCESS
Unit Times

to radio link failure
Definition Number of signaling TCH/H drops due to radio link failure
ures (on TCH/H signaling channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/H signal-
ing channel is caused by radio link failures.
radio link failures (on TCH/H signaling channel).
Point message on Abis interface on TCH/H signaling channel.
DicatiOn

ASSIGNMENT PROCESS
Unit Times

to LAPD link failure
Definition Number of signaling TCH/H drops due to LAPD link failure
ures (on TCH/H signaling channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/H signal-
ing channel is caused by LAPD link failures.
LAPD link failures (on TCH/H signaling channel).
Point from LAPD on TCH/H signaling channel. The measurement point

ASSIGNMENT PROCESS
Unit Times
to OMC-R forced release
Definition Number of signaling TCH/H drops due to OMC-R forced release

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.
OMC-R forced releases (on TCH/H signaling channel).
Point message from database on TCH/H signaling channel. The mea-

ASSIGNMENT PROCESS
Unit Times
to forced release by other
calls
Definition Number of signaling TCH/H drops due to forced release by other
calls
by other calls (on TCH/H signaling channel). The counter incre-
TCH/H signaling channel is caused by forced releases by other
calls.
forced releases by other calls (on TCH/H signaling channel).

Point sage from other calls on TCH/H signaling channel. The measure-

Unit Times
to other failure
Definition Number of signaling TCH/H drops due to other failure
(on TCH/H signaling channel). The counter increments if the phe-
nomenon 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 fail-
ure, OMCR forced release, forced release by other calls, handover
failure).
other failures (on TCH/H signaling channel).
Point status on TCH/H, or when timer that waits for access is overtime

Unit Times
Definition Number of voice TCH/H drops due to loss of contact with RANA
contact with RANA (on TCH/H voice channel). The counter incre-
TCH/H voice channel is caused by failures due to RANCS losing
contact with RANA (on TCH/H voice channel).
RANCS losing contact with RANA (on TCH/H voice channel).
Point with RANA (on TCH/H voice channel) in the following two cases:
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-in-
terface from RANA is received, the counter increments; mean-

PROCESS
Unit Times
LAPD link failure
Definition Number of voice TCH/H drops due to LAPD link failure
ures (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 LAPD link failures.
LAPD link failures (on TCH/H voice channel).
Point from LAPD on TCH/H voice channel. The measurement point is A,

PROCESS
Unit Times

Definition Number of voice TCH/H drops due to OMC-R forced release
releases (on TCH/H voice channel). The counter increments if the
phenomenon that call drops after MS has obtained TCH/H voice
OMC-R forced releases (on TCH/H voice channel).
Point message from database on TCH/H voice channel. The measure-

PROCESS
Unit Times


Definition Number of voice TCH/H drops due to forced release by other calls
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.
forced releases by other calls (on TCH/H voice channel).
Point sage from other calls on TCH/H voice channel. The measurement


ASSIGNMENT PROCESS
Unit Times
other failure
Definition Number of voice TCH/H drops due to other failure
(on TCH/H voice channel). The counter increments if the phenom-
enon that call drops after MS has obtained TCH/H voice channel is

other failures (on TCH/H voice channel).
Unit Times
Definition Number of data TCH/H drops due to loss of contact with RANA
contact with RANA (on TCH/H data channel). The counter incre-

TCH/H data channel is caused by failures due to RANCS losing

contact with RANA (on TCH/H data channel).
RANCS losing contact with RANA (on TCH/H data channel).
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 mea-

PROCESS
Unit Times

radio link failure
Definition Number of data TCH/H drops due to radio link failure
ures (on TCH/H data channel). The counter increments if the phe-
nomenon that call drops after MS has obtained TCH/H data channel
radio link failures (on TCH/H data channel).
Point message on Abis interface on TCH/H data channel. The
DicatiOn

PROCESS
Unit Times


LAPD link failure
Definition Number of data TCH/H drops due to LAPD link failure
ures (on TCH/H data channel). The counter increments if the phe-
nomenon that call drops after MS has obtained TCH/H data channel
is caused by LAPD link failures.
LAPD link failures (on TCH/H data channel).
Point from LAPD on TCH/H data channel. The measurement point is A,


PROCESS
Unit Times
Definition 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

OMC-R forced releases (on TCH/H data channel).
Measurement The counter increments when BSC receives OMCR forced release
Point message from database on TCH/H data channel. The measure-

PROCESS
Unit Times

Definition Number of data TCH/H drops due to forced release by other calls
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.
forced releases by other calls (on TCH/H data channel).
Point sage from other calls on TCH/H data channel. The measurement

ASSIGNMENT PROCESS
Unit Times


other failure
Definition Number of data TCH/H drops due to other failure
(on TCH/H data channel). The counter increments if the phenom-
enon that call drops after MS has obtained TCH/H data channel is
other failures (on TCH/H data channel).
Unit Times


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 fail-
ures.
Measurement The counter counts the number of abnormal release flow launched
Point 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

� 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.
Unit 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.
Point by RANA to RANCS due to SCCP link failure on TCH/F in the fol-
lowing cases:
Figure 798.


ASSIGNMENT PROCESS

798.
� T9101 is overtime, the measurement point is A4, as shown
inFigure 798.
798.
Unit Times

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 fail-
ures.
Point by RANA to RANCS due to SCCP link failure on TCH/H in the fol-
lowing cases:
Figure 799.

ASSIGNMENT PROCESS

799.
Figure 799.


799.
Unit 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 mes-
sage 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 The counter increments when the content of HO_REQ message is
Point incorrect. The measurement point is A2, as shown in Figure 800.
Unit Times

other cause on TCH/F
Definition Number of RANA link releases due to other cause on TCH/F
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.
by other cause on TCH/F.
Unit Times
other cause on TCH/H
Definition Number of RANA link releases due to other cause on TCH/H
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.
by other cause on TCH/H.


Unit Times
SDCCH short messages
drops
Definition Number of SDCCH short messages drops
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 mes-
sages drops.
Measurement The counter increments when call drops due to radio link failure or
Point LAPD link release or handover failure while doing short message
service.
Unit 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 mes-
sages drops.
service.
Unit 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 mes-
sages drops.
service.
Unit Times

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 re-
quest 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 The counter increments when call drops due to TCH/F channel re-
Point quest failure when CS service is forcedly released due to PS ser-
vice.
Unit 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 The counter increments when call drops due to TCH/H channel
Point request failure when CS service is forcedly released due to PS ser-
vice.
Unit 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.
due to eMLPP forced handover.
Measurement The counter counts when T3107 and T3103 are timeout under AS-
Point SIGN status on SDCCH. The measurement point is A, as shown in
Figure 803.
FIGURE 803 MEASUREMENT POINT OF NUMBER OF SDCCH DROPS DUE TO

EMLPP FORCED HANDOVER
Unit 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 han-
dover, the counter increments.
Usage This counter is used to find out the frequency of call drop on sig-
naling TCH/F due to eMLPP forced handover

Point SIGN status on signaling TCH/F. The measurement point is A, as

Unit Times
Definition 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.
Point SIGN status on voice TCH/F. The measurement point is A, as shown
in Figure 805.


Unit 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.
Point SIGN status on data TCH/F. The measurement point is A, as shown
in Figure 806.


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 han-
Usage This counter is used to find out the frequency of call drop on sig-
naling TCH/H due to eMLPP forced handover.
Point SIGN status on signaling TCH/H. The measurement point is A, as

Unit Times
Definition Number of voice TCH/H drops due to eMLPP forced handover
Description 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 The counter counts when T3107 and T3103 are timeout under
Point ASSIGN status on voice TCH/H. The measurement point is A, as

Unit 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.
Point SIGN status on data TCH/H. The measurement point is A, as shown
in Figure 809.


Unit Times
C901070071 Bad quality of

UL receiving (On SDCCH)
Definition Bad quality of UL receiving (On SDCCH)
radio link failure. After MS obtains SDCCH, call drop occurs. If
the problem is caused by bad uplink receiving quality, the counter
increments.
due to radio link failure which is caused by bad uplink receiving
quality.
Measurement The counter counts when BSC receives the CONNectiOn FAILure IN-
Point DicatiOn message at Abis interface on SDCCH. The measurement


ASSIGNMENT PROCESS
Unit Times

DL receiving (On SDCCH)
Definition Bad quality of DL receiving (On SDCCH)
radio link failure. After MS obtains SDCCH, call drop occurs. If the
problem is caused by bad downlink receiving quality, the counter
increments.
due to radio link failure which is caused by bad downlink receiving
quality.


ASSIGNMENT PROCESS
Unit Times
C901070073 Lower
electrical level of UL (On
SDCCH)
Definition Lower electrical level of UL (On SDCCH)
the problem is caused by low uplink receiving level, the counter
increments.
due to radio link failure which is caused by low uplink receiving
level.


ASSIGNMENT PROCESS
Unit Times
C901070074 Lower
electrical level of DL (On
SDCCH)
Definition Lower electrical level of DL (On SDCCH)
the problem is caused by low downlink receiving level, the counter
increments.
due to radio link failure which is caused by low downlink receiving
level.


ASSIGNMENT PROCESS
Unit Times
signaling drops due to TA
too far (On SDCCH)
Definition Number of signaling drops due to TA too far (On SDCCH)
radio link failure. After MS obtains SDCCH, call drop occurs. If the
problem is caused by TA being too far, the counter increments.
due to radio link failure which is caused by TA being too far.


ASSIGNMENT PROCESS
Unit Times
C901070076 Reasons of the

other radios (On SDCCH)
Definition Reasons of the other radios (On SDCCH)
the problem is not due to the above five causes (i.e. bad uplink
receiving quality, bad downlink receiving quality, low uplink receiv-
ing level, low downlink receiving level, and TA being too far), the
counter increments.
due to radio link failure which is caused by other radio problems.


ASSIGNMENT PROCESS
Unit Times

UL receiving (On TCH/F)
Definition Bad quality of UL receiving (On TCH/F)
Description This counter counts the number of call drops on TCH/F due to ra-
dio link failure. After MS obtains TCH/F, call drop occurs. If the
problem is caused by bad uplink receiving quality, the counter in-
crements.
quality.
Measurement The counter counts when BSC receives the CONNectiOn FAILure INDi-
Point catiOn message at Abis interface on TCH/F. The measurement point


ASSIGNMENT PROCESS
Unit Times

DL receiving (On TCH/F)
Definition Bad quality of DL receiving (On TCH/F)
increments.
quality.


PROCESS
Unit Times
C901070079 Lower
TCH/F)
Definition Lower electrical level of UL (On TCH/F)
problem is caused by low uplink receiving level, the counter incre-
ments.
level.

Point DicatiOn message at Abis interface on TCH/F. The measurement

PROCESS
Unit Times
C901070080 Lower
TCH/F)
Definition Lower electrical level of DL (On TCH/F)
problem is caused by low downlink receiving level, the counter in-
crements.

level.

PROCESS
Unit Times
too far (On TCH/F)
Definition Number of signaling drops due to TA too far (On TCH/F)


PROCESS
Unit Times

other radios (On TCH/F)
Definition Reasons of the other radios (On TCH/F)

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 prob-
lem 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.
Point DicatiOn message at Abis interface on TCH/F. The measurement

PROCESS
Unit 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.
quality.
Point DicatiOn message at Abis interface on TCH/H. The measurement

PROCESS
Unit Times


DL receiving (On TCH/H)
Definition Bad quality of DL receiving (On TCH/H)
radio link failure. After MS obtains TCH/H, call drop occurs. If the
increments.
quality.

PROCESS
Unit Times

C901070085 Lower
TCH/H)
Definition Lower electrical level of UL (On TCH/H)
the problem is caused by low uplink receiving level, the counter
increments.
level.

PROCESS
Unit Times

C901070086 Lower
TCH/H)
Definition Lower electrical level of DL (On TCH/H)
the problem is caused by low downlink receiving level, the counter
increments.
level.

PROCESS
Unit Times

too far (On TCH/H)
Definition Number of signaling drops due to TA too far (On TCH/H)
radio link failure. After MS obtains TCH/H, call drop occurs. If the

PROCESS
Unit Times


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 prob-
lem 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.

PROCESS
Unit Times

C901070089 The Count of

Drop Call caused by "IP
Resource Reset"
Description On the premise that the 3GPP IPA function is implemented, dur-
ing the IP resource resetting process (initiated at MSC or at BSC),
BSC releases relevant calls when it receives the IP resource reset-
ting request or the IP resource resetting response from MSC. The
counter increments upon each released call. The measurement
FIGURE 828 MEASUREMENT POINT OF THE COUNT OF DROP CALL CAUSED BY "IP RESOURCE RESET"
Unit Times

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 AbisConnectFailureIndi-
cation 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 When BSC receives the AbisConnectFailureIndication message
Point from BTS, if the voice version used is full-rate voice version 1,
then the counter counts.
Unit Times
Unit Times


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.
half-rate version 1 radio link failures on TCH/F.
Point from BTS, if the voice version used is half-rate voice version 1,
Unit 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.
half-rate version 3 radio link failures on TCH/F.
Point from BTS, if the voice version used is half-rate voice version 3,
Unit Times

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 Times
voice TCH/F drops due
Changeover
Unit Times

TCH/F drops due to BIPB
Active/Standby Changeover
Unit Times

Changeover
Unit Times
voice TCH/H drops due
Changeover
Unit Times

TCH/H drops due to BIPB


Unit Times
SDCCH drops due to LAPD
received and the cause is CAUSE_LAPDEXCH.
Unit Times
to LAPD Active/Standby
Changeover
Unit Times

TCH/F drops due to LAPD


Unit Times
Changeover
Unit Times
Changeover
Unit Times


TCH/H drops due to LAPD
Unit Times
Changeover
Unit Times
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 chan-

nel is FR, the counter increments.
This counter is supported in version V6.20.611f.
Unit Times
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 chan-
nel is HR, the counter increments.
This counter is supported in version V6.20.611f.
Unit Times
SDCCH drops due to BIPB
Unit Times

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 in-
FIGURE 829 CALL DROP DURING IMMEDIATE ASSIGNMENT DUE TO BTS

FAULT
When BSC receives the O&M status report message from BTS and
the cause is BTS being blocked due to fault, the service being af-
fected should be released. If the service being affected is on SD-
CCH, the counter increments.
Unit Times

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.
fected should be released. If the service being affected is on sig-
naling TCH/F, the counter increments.
FIGURE 830 CALL DROP DURING IMMEDIATE ASSIGNMENT DUE TO BTS

FAULT

Unit Times

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
FIGURE 831 CALL DROP DURING ASSIGNMENT DUE TO BTS FAULT
fected should be released. If the service being affected is on voice
TCH/F, the counter increments.

Unit Times
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
fected should be released. If the service being affected is on data
TCH/F, the counter increments.


Unit Times
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.
fected should be released. If the service being affected is on sig-
naling TCH/H, the counter increments.


Unit Times
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

fected should be released. If the service being affected is on voice

TCH/H, the counter increments.

Unit Times
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

fected should be released. If the service being affected is on data
TCH/H, the counter increments.

Unit Times
C901070118 Call Drop by

Releasing Local Switch
Description This counter counts the number of call drops due to failure in re-
leasing 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

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 Times

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

Description This counter counts the maximum number of busy SDCCHs in the
cell within measurement period; its value represents SDDCH in-
stantaneous occupation status and the busiest extent.
System records SDCCH occupation number in cells. The occupa-
tion number increments after SDCCH has been occupied success-
fully; 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 num-
ber after SDCCH has been occupied successfully and before SD-
CCH 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 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.
Measurement The counter counts in the following three cases:
Point
� 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 periodi-
cally. The measurement point is A, as shown in Figure 836.
Unit 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 measure-
ment data reported periodically in the system is the mean number
of busy SDCCH.
SDCCH.
Measurement The counter counts when measurement data are reported period-
Point ically. The measurement point is A, as shown in Figure 837.
Unit Times
C901080006 SDCCH
congestion time
Definition SDCCH congestion time
Description 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

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.
SDCCH.
Point
� 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 re-
ported periodically, the counter counts congestion time and
accumulates. The measurement point is A, as shown in Figure
838.
Unit Second
unavailable defined SDCCH
Definition Number of unavailable defined SDCCH
Description 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 The counter value is inquired from database when periodical mea-
Point surement data are reported. The measurement point is A, as
Unit 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.

Unit Times
C901080012 Average
number of busy radio
channel
Definition 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.

Unit 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 Occupation number updates after TCH/H has been occupied and
Point released successfully, the counter value is reported when mea-
surement data are reported periodically. The measurement point

Unit Times

time(SpeechVer1)
Definition TCH/H busy time (SpeechVer1).
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 occupa-
tion time of TCH/H in cells; its value can be used as the reference
for whether to increase TCH/Hs.
Point
� The counter counts time and accumulates when TCH/H is ob-
tained successfully
� The counter counts time and accumulates when TCH/H is re-
leased
� 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 num-
ber 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 re-
leased after accumulation.
Unit 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 occupa-
tion time of TCH/H in cells; its value can be used as the reference
for whether to increase TCH/Hs.
Point
� The counter counts time and accumulates when TCH/H is ob-
tained successfully

� The counter counts time and accumulates when TCH/H is re-

leased

ber 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 re-
Unit Second
C901080018 TCH/H
congestion time
Definition TCH/H congestion time
Description 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 con-
gestion mark is set when requiring TCH/H, then this period of con-
gestion 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 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.
Point
� 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 Second

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 Occupation number updates after TCH/F has been occupied and
Point released successfully, the counter value is reported when mea-
surement data are reported periodically. The measurement point
Unit Times

time(SpeechVer1)
Definition TCH/F busy time (SpeechVer1)
Description This counter counts the total TCH/F busy time (SpeechVer1) in
cells; its value represents traffic on TCH/F (SpeechVer1).

Usage This counter is used to find out the busy extent and mean occu-
pation time of TCH/F in cells; its value can be used as the refer-
ence for whether to increase TCH/Fs and the proportion of using
SpeechVer1.
Point
� The counter counts time and accumulates when TCH/F is ob-
tained successfully
� The counter counts time and accumulates when TCH/F is re-
leased

ber 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 re-
Unit Second


time(SpeechVer2)
Definition TCH/F busy time (SpeechVer2)
SpeechVer2.
Point
tained successfully
leased

Unit Second



time(SpeechVer3)
Definition TCH/F busy time(SpeechVer3)
SpeechVer3.
Point
tained successfully
leased



Unit Second
C901080027 TCH/F
congestion time
Definition TCH/F congestion time
Description 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 con-
gestion mark is set when requiring TCH/F, then this period of con-
gestion 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 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.
Point
� 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 Second
TRXs
Definition Number of TRX s
Description This counter counts the total number of TRXs in all status config-
ured in the cell.
Usage This counter is used to find out the configured TRX number and
resource utilizing status in the present cell.

Unit Times
C901080032 Reserved
TCH/F busy time
Definition Reserved TCH/F busy time
Description Reserved TCH is the channel that can only be occupied by sub-
scribers 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.
Point
� The counter counts when reserved TCH/F is obtained success-
fully
� 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 success-
fully 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.

Measurement The counter counts at the following time points.

Point
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 When the confirmation message (tGetCellDownTimeAck.wResult)
Point of cell's interruption duration obtained from database is true, the
counter counts.
Unit 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 han-
dover............................................................................. 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 cir-
cuit block ....................................................................... 828
C901090026 Number of incoming handover failure due to cir-
cuit group mismatch ........................................................ 829
C901090027 Number of incoming handover failure due to un-
available radio resource.................................................... 830
other factors ................................................................... 831
attempts due to forced release .......................................... 832
attempts due to queue ..................................................... 833


attempts due to forced handover ....................................... 834
C901090037 MSC-controlled incoming handover time due to
queue ............................................................................ 835
C901090038 Queue number of MSC-controlled incoming han-
dover............................................................................. 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
defined layer to the same frequency .................................. 846
undefined layer to the same frequency ............................... 847
C901090048 Number of outgoing handover success from un-
defined 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 cur-
rent 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 un-
defined layer (GSM1800) to current layer (GSM900) ............ 856
upper layer to the same frequency..................................... 857
C901090062 Number of incoming handover success from up-
per 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

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

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 han-
dover............................................................................. 900
C901090124 Number of intra-cell TCH/F-to-TCH/F handover
success .......................................................................... 901
C901090125 Number of intra-cell TCH/F-to-TCH/H han-
dover............................................................................. 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 han-
dover............................................................................. 904
C901090129 Number of intra-cell TCH/H-to-TCH/F handover
success .......................................................................... 905
C901090130 Number of intra-cell TCH/H-to-TCH/H han-
dover............................................................................. 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 han-
dover............................................................................. 909
C901090134 Number of inter-cell TCH/F-to-TCH/F handover
success .......................................................................... 909
C901090135 Number of inter-cell TCH/F-to-TCH/H han-
dover............................................................................. 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 han-
dover............................................................................. 913
C901090139 Number of inter-cell TCH/H-to-TCH/F handover
success .......................................................................... 914
C901090140 Number of inter-cell TCH/H-to-TCH/H han-
dover............................................................................. 915
C901090141 Number of inter-cell TCH/H-to-TCH/H handover
success .......................................................................... 916
C901090142 Total dual-band outgoing handover at-
tempts ........................................................................... 917
C901090145 Number of dual band incoming handover at-
tempts ........................................................................... 918
C901090148 Number of intra-cell invalid handovers ............. 919


handover attempts due to forced release (emergency ser-
vice) .............................................................................. 920
handover (forced release) (emergency service) ................... 921
handover attempts due to forced handover (emergency serv-
ice) ............................................................................... 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 ser-
vice) .............................................................................. 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 han-
dover) ........................................................................... 932
lower PRI user (BSC-controlled inter-cell handover due to
forced handover) ............................................................. 933
C901090163 Number of recv failure from lower PRI user re-
quest resource for forced handover (BSC-controlled inter-cell
handover due to forced handover) ..................................... 934
(BSC-controlled inter-cell handover due to forced han-
dover) ........................................................................... 936
C901090165 Number of high PRI user time out for wait re-
source (BSC-controlled inter-cell handover due to forced han-
dover) ........................................................................... 937
C901090166 Number of forced release target not found (BSC-
controlled inter-cell handover due to forced release) ............ 938
source (BSC-controlled inter-cell handover due to forced re-
lease) ............................................................................ 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 re-
source for forced handover (MSC-controlled incoming han-
dover due to forced handover) .......................................... 942
(MSC-controlled incoming handover due to forced han-
dover) ........................................................................... 942

source (MSC-controlled incoming handover due to forced han-
dover) ........................................................................... 943
(MSC-controlled incoming handover due to forced re-
lease) ............................................................................ 943
source (MSC-controlled incoming handover due to forced re-
lease) ............................................................................ 944
C901090177 Number of handover attempts due to eMLPP
forced handover .............................................................. 946
C901090178 Number of handover due to eMLPP forced han-
dover............................................................................. 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 re-
source ........................................................................... 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


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 reorgani-
zation ............................................................................ 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


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 suc-
cesses, failures, and frequency of abnormal events during han-
dover. 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.

outgoing handover attempts
Definition Number of BSC-controlled inter-cell outgoing handover attempts
Description This counter counts the Number of BSC-controlled inter-cell out-
going handover attempts originated from the source cell by MS.
outgoing handover. It is one of the parameters to measure the
wireless environment.
Measurement BSC starts the handover decision after it receives the measure-
Point ment 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 Times
handover attempts
Definition Number of MSC-controlled outgoing handover attempts
going handover attempts originated from the source cell by MS.


inter-BSC outgoing handover attempts. It is one of the parameters
to measure the wireless environment.
current attempt cells are governed by different BSCs, the source
BSC will send MSC the handover request A_HO_RQD to trigger in-
ter-BSC handover, and the counter increments. The measurement
FIGURE 854 MSC-CONTROLLED OUTGOING HANDOVER ATTEMPTS
Unit Times
handover request failures
due to unclear factors
Definition Number of MSC-controlled outgoing handover request failures due
to unclear factors
going handover request failures due to unclear factors originated
from the source cell by MS.
outgoing handover request failures due to unclear reasons, and to
find out the MSC-originated handover status.
ter-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 Times
due to unavailable ground
resource
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.
outgoing handover request failures due to unavailable ground re-
source, and to find out the MSC-originated handover status.
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

FIGURE 856 MSC-CONTROLLED HANDOVER REQUEST FAILURES
Unit Times
due to unavailable radio
resource
Definition Number of MSC-controlled outgoing request failures due to un-
available radio resource
going 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 unavail-
able radio resource, and to find out the MSC-originated handover
status.
ter-BSC handover. If the source BSC receives the feedback from
MSC that the handover request is rejected due to unavailable ra-
dio resource, the counter increments. The measurement point is

Unit Times
to other factors
going handover request failures due to other factors excluding
unavailable ground resource and unavailable radio resource origi-
nated from the source cell by MS.
MSC-controlled outgoing handover request failures due to other
factors, and to find out the MSC-originated handover status.
ter-BSC handover. If the source BSC receives the feedback from
MSC that the handover request is rejected due to other factors,
Figure 858.

Unit 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 in-
coming handover attempts from MS to target cell.
incoming handover attempts originated by MS. It is one of the
parameters to measure the wireless environment.
Measurement When intra-BSC target cell receives the channel request from the
Point source cell, if the request is due to inter-cell handover, the counter

ATTEMPTS
Unit 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 origi-
nated by target cell due to unavailable radio resource during the
process of MS -originated BSC-controlled inter-cell incoming han-
dover. When target instance fails to allocate the channel, forced
release attempts could be originated referring to the MS priority
and MSC & BSC settings.
BSC-controlled inter-cell incoming handover attempts due to
forced release, which reflects the handover status.
Measurement When intra-BSC target cell receives the wireless channel applica-
Point tion 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 at-
tempt is feasible, the counter increments before the target cell
sends forced release message to the instance that is to be re-
leased. The measurement point is A, as shown in Figure 860.
FIGURE 860 FORCED RELEASE ATTEMPTS
Unit Times
ZGO-01-03-001 eMLPP

queue
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.
queue, which reflects the handover status.
Measurement When intra-BSC target cell receives the wireless channel applica-
Point tion 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 Times
ZGO-01-03-001 eMLPP

forced handover
forced handover
Description This counter counts the number of forced-handover attempts orig-
inated by target cell due to unavailable radio resource during the
process of MS-originated BSC-controlled inter-cell incoming han-
dover.
forced handover, which reflects the handover status.
Measurement When intra-BSC target cell receives the wireless channel appli-
Point cation request, if the application cause is BSC-controlled inter-
cell incoming handover and wireless channel is unavailable to tar-
get cell, forced-handover attempt decision starts. If forced-han-
dover 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 Times
ZGO-01-03-001 eMLPP

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. Queu-
ing 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 under-
stand the traffic status and the situation of the queuing for re-
source.
Measurement � Under the condition that database acquires resource via dy-
Point namic channel conversion or MS releases resource and queu-
ing instance receives usable message, if the application cause
is BSC-controlled incoming handover, the queuing time accu-
mulates. The measurement point is A, as shown in Figure 863.
FIGURE 863 EXECUTION IN QUEUING
� If the instance queuing timer expires, and the application cause

is BSC-controlled incoming handover, the queuing time accu-

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 BSC-
controlled incoming handover, the queuing time accumulates.
FIGURE 865 INSTANCE RELEASE DURING QUEUING
Unit Second

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.
Point namic channel conversion or MS releases resource and queu-
is BSC-controlled incoming handover, the counter increments.

is BSC-controlled incoming handover, the counter increments.


released due to certain causes, if the application cause is BSC-
controlled incoming handover, the counter increments. The
Unit Times

C901090022 BSC-controlled
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 suc-
cessful 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 han-
dover due to queue and acquiring resource, and to find out the
valid queuing time.
Measurement Under the condition that database acquires resource via dynamic
Point channel conversion or MS releases resource, when queuing in-
stance receives resource usable message, if the application cause
is BSC-controlled incoming handover, the queuing time accumu-
lates. The measurement point is A, as shown in Figure 869.
Unit 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 suc-
cessfully acquiring resource.
Usage This counter is used to find out the total number of calls that partic-
ipate in BSC-controlled intra-cell incoming handover due to queue
and successfully acquiring resource, and to find out the success
ratio of queuing.
Point channel conversion or MS releases resource and queuing instance
receives resource usable message, if the application cause is BSC-
controlled incoming handover, the counter increments. The mea-
Unit Times

handover attempts
Definition Number of MSC-controlled incoming handover attempts
Description This counter counts the number of MSC-originated inter-BSC in-
coming 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 parame-
ters to measure the wireless environment.
Measurement When the target cell receives the channel application, if the ap-
Point plication cause is external incoming handover, the counter incre-
FIGURE 871 MSC-CONTROLLED INCOMING HANDOVER ATTEMPTS
Unit Times
incoming handover failure
due to circuit block
Definition Number of incoming handover failure due to circuit block
Description 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 cir-
cuit block, and is used to observe the external handover flow.
Measurement When the target cell receives the handover request from MSC,
Point 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 Times
due to circuit group mismatch
Definition Number of incoming handover failure due to circuit group mis-
match
Description This counter counts the number of unsuccessful MSC-originated in-
ter-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 cir-
cuit group mismatch, and is used to observe the external handover
flow.
Measurement When the target cell receives the handover request from MSC, it
Point checks the ground circuit. If the requested ground circuit does not
match, the counter increments. The measurement point is A, as


HANDOVER
Unit Times
due to unavailable radio
resource
Definition Number of incoming handover failure requests due to unavailable
radio resource
inter-BSC incoming handover due to unavailable radio resource.
Usage This counter is used to find out the frequency of unsuccessful MSC-
originated inter-BSC incoming handover due to unavailable radio
resource, and is used to observe the external handover flow.
Point allocates the wireless channels and attempts to activate and con-
nect. If one link fails and the target cell sends MSC the handover
failure message, the counter increments. The measurement point


HANDOVER
Unit Times
Definition Number of incoming handover failure due to other factors
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 MSC-
originated inter-BSC incoming handover due to other factors, and
is used to observe the external handover flow.
Point sends MSC the handover failure message. If the failure is due to
other factors, the counter increments. The measurement point is

HANDOVER

Unit 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 origi-
nated by target cell due to unavailable radio resource during the
process of MS-originated MSC-controlled inter-BSC incoming han-
dover. When target instance fails to allocate the channel, forced
release attempts could be originated referring to the MS priority
and MSC & BSC settings.
MSC-controlled inter-BSC incoming handover attempts due to
forced release, which reflects the handover status.
Measurement When the target cell receives the wireless channel application re-
Point quest, if the application cause is MSC-controlled inter-BSC incom-
ing 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 Times


ZGO-01-03-001 eMLPP
queue
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.
queue, which reflects the handover status.
queuing attempt decision starts. If queuing attempt is feasible,
the target cell has the target instance waiting in the queuing, and
Figure 877.
Unit Times

ZGO-01-03-001 eMLPP
forced handover
forced handovers
Description This counter counts the number of forced-handover attempts orig-
inated by target cell due to unavailable radio resource during the
process of MS-originated MSC-controlled inter-BSC incoming han-
dover.
forced handover, which reflects the handover status.
forced-handover attempt decision starts. If forced-handover at-
tempt 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 Times
ZGO-01-03-001 eMLPP

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 under-
stand the traffic status and the situation of the queuing for re-
source.
Point namic channel conversion or MS releases resource, and queu-
is MSC-controlled incoming handover, the queuing time accu-

is MSC-controlled incoming handover, the queuing time accu-


released due to some causes, if the application cause is MSC-
controlled incoming handover, the queuing time accumulates.
Unit 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.
Point namic channel conversion or MS releases resource, and queu-
is MSC-controlled incoming handover, the counter increments.

is MSC-controlled incoming handover, the counter increments.


released due to some causes, if the application cause is MSC-
controlled incoming handover, the counter increments. The
Unit 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 suc-
cessful 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.
Point channel conversion or MS releases resource, when queuing in-
stance receives resource usable message, if the application cause
is MSC-controlled incoming handover, the queuing time accumu-
lates. The measurement point is A, as shown in Figure 885.
Unit Second

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 partic-
ipate in MSC-controlled intra-cell incoming handover due to queue
and successfully acquires resource, and to find out the success ra-
tio of queuing.
Point channel conversion or MS releases resource, and queuing instance
receives resource usable message, if the application cause is MSC-
controlled incoming handover, the counter increments. The mea-
Unit Times

from the same layer and
frequency
Definition Number of incoming handover attempts from the same layer and
frequency
ing handover attempts the target cell receives from the same layer
and frequency.
incoming handover attempts from the same layer and frequency,
which helps to make the network planning.
Measurement When intra-BSC target cell receives the channel application re-
Point quest 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 Times
Related Features ZGO-05-02-008 Multi-layer Cell Structure

from the same layer and
frequency
Definition Number of incoming handover success from the same layer and
frequency
cell incoming handover the target cell receives from the same layer
and frequency.
incoming handover success from the same layer and frequency,
and is used to observe the handover flow.
Measurement When intra-BSC target cell receives the handover completed mes-
Point sage, 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 Times

to the same layer and
frequency
Definition Number of outgoing handover attempts to the same layer and fre-
quency
Description This counter counts the number of BSC-controlled inter-cell out-
going handover attempts the target cell sends to the same layer
and frequency.
outgoing handover attempts to the same layer and frequency,
Point ment 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 Times

to the same layer and
frequency
Definition Number of outgoing handover success to the same layer and fre-
quency
cell outgoing handover the target cell sends to the same layer and
frequency.
Usage This counter is used to find out the frequency of successful BSC-
controlled outgoing handover to the same layer and frequency,
Measurement During the process of BSC-controlled handover, if the source cell
Point 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 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 in-
coming handover attempts the target cell receives from undefined
layer to the same frequency.
incoming handover attempts from undefined layer to the same
frequency, which helps to make the network planning.
incoming handover and the source cell is at the undefined layer
and the same frequency, the counter increments. The measure-

ATTEMPTS
Unit Times

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 in-
ter-cell incoming handover the target cell receives from undefined
layer to the same frequency.
incoming handover success from undefined layer to the same fre-
quency, which helps to observe the handover flow.
Point sage, 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 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 outgo-
ing handover attempts the source cell sends from undefined layer
to the same frequency.
outgoing handover attempts from undefined layer to the same fre-
quency, which helps to make the network planning.
current attempt cells are BSC-controlled internal cells at undefined
layer and the same frequency, the counter increments. The mea-
Unit Times

same frequency
Definition Number of outgoing handover success from undefined layer to the
same frequency
cell outgoing handover the source cell sends from undefined layer
controlled outgoing handover from undefined layer to the same
frequency, which helps to make the network planning.
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 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)
ing handover attempts the target cell (GSM1800) receives from
undefined layer (GSM900).
incoming handover attempts from undefined layer (GSM900) to
current layer (GSM1800), which helps to make the network plan-
ning.
Measurement When intra-BSC target cell (GSM1800) receives the channel ap-
Point plication request from the source cell (GSM900), if the application
cause is inter-cell incoming handover and the source cell is at un-
defined layer, the counter increments. The measurement point is

ATTEMPTS
Unit Times

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)
going handover attempts the source cell (GSM900) sends to un-
defined layer (GSM1800).
outgoing handover attempts from undefined layer (GSM900) to
ning.
current attempt cells are BSC-controlled internal cells at unde-
fined layer (GSM1800) and the current serving cell is GSM900,
Figure 896.
Unit Times

outgoing handover from
current layer (GSM900) to
Definition Number of outgoing handover from current layer (GSM900) to un-
defined layer (GSM1800)
going handover the source cell (GSM900) sends to undefined layer
(GSM1800).
ning.
Point (GSM900) receives the radio resource unavailable message from
the target cell (GSM1800), and the target cell is at undefined layer

EXECUTION FLOW
Unit Times

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)
ter-cell outgoing handover the source cell (GSM900) sends from
undefined layer to the same frequency (GSM1800).
frequency (GSM900) to current layer (GSM1800), which helps to
make the network planning.
Point (GSM900) receives the handover completed message from the tar-
get cell (GSM1800), and the target cell is at undefined layer and
the same frequency, the counter increments. The measurement

HANDOVER
Unit Times

C901090055 Number
layer (GSM900)
Definition Number of incoming handover attempts from undefined layer
ing handover attempts the target cell (GSM900) receives from un-
incoming handover attempts from undefined layer (GSM1800) to
ning.
Measurement When intra-BSC target cell (GSM900) receives the channel appli-
Point cation request from the source cell (GSM1800), if the application
cause is inter-cell incoming handover and the source cell is at un-
defined layer, the counter increments. The measurement point is

ATTEMPTS
Unit Times

C901090058 Number
layer (GSM900)
Definition Number of outgoing handover attempts from undefined layer
going handover attempts the source cell (GSM1800) sends to un-
ning.
current attempted cell is BSC-controlled internal cell at undefined
layer (GSM900) or lower-layer cell at same frequency (GSM1800),
Figure 900.
Unit Times

to current layer (GSM900)
Definition Number of outgoing handover from undefined layer (GSM1800) to
current layer (GSM900)
ing handover the source cell (GSM1800) sends to undefined layer
(GSM900).
ning.
the target cell (GSM900), and the target cell is at undefined layer

EXECUTION FLOW
Unit Times

C901090060 Number
layer (GSM900)
Definition Number of outgoing handover success from undefined layer
undefined layer to the same frequency (GSM900).
frequency (GSM1800) to current layer (GSM900), which helps to
make the network planning.
Point (GSM1800) receives the handover completed message from the
target cell (GSM900), and the target cell is at undefined layer and

HANDOVER
Unit Times

from upper layer to the same
frequency
Definition Number of incoming handover attempts from upper layer to the
same frequency
ing handover attempts the target cell receives from upper layer to
the same frequency.
incoming handover attempts from upper layer to the same fre-
incoming handover and the source cell is at upper layer and the
same frequency, the counter increments. The measurement point

ATTEMPTS
Unit Times

from upper layer to the same
frequency
Definition Number of incoming handover success from upper layer to the
same frequency
cell 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 in-
coming handover success from upper layer to the same frequency,
Point sage, 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 Times

from the same frequency to
upper layer
Definition Number of outgoing handover attempts from the same frequency
to upper layer
going handover attempts the source cell sends from upper layer
outgoing handover attempts from upper layer to the same fre-
current attempt cells are BSC-controlled internal cells at upper
Unit Times

upper layer
Definition Number of outgoing handover success from the same frequency
to upper layer
cell outgoing handover the source cell sends from upper layer to
the same frequency.
controlled outgoing handover from upper layer to the same fre-
it means that MS has accessed the target channel, handover suc-
cessful. If the target cell is at upper layer and the same frequency,
Figure 906.

HANDOVER
Unit Times

from lower layer to the same
frequency
Definition Number of incoming handover attempts from lower layer to the
same frequency
ing handover attempts the target cell receives from lower layer to
the same frequency.
incoming handover attempts from lower layer to the same fre-
incoming handover and the source cell is at lower layer and the

ATTEMPTS
Unit Times

from lower layer to the same
frequency
Definition Number of incoming handover success from lower layer to the
same frequency
cell 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 in-
coming handover success from lower layer to the same frequency,
Point sage, 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 Times

lower layer
Definition Number of outgoing handover attempts from the same frequency
to lower layer
going handover attempts the source cell sends from the same fre-
quency to lower layer.
outgoing handover attempts from the same frequency to lower
layer, which helps to make the network planning.
current attempt cells are BSC-controlled internal cells at lower
Unit Times

lower layer
Definition Number of outgoing handover success from the same frequency
to lower layer
ter-cell outgoing handover the source cell sends from the same
frequency to lower layer.
controlled outgoing handover from the same frequency to lower
layer, which helps to make the network planning.
and the target cell is at lower layer and the same frequency, the
Figure 910.

HANDOVER
Unit Times

from the same layer GSM900
to GSM1800
Definition Number of incoming handover attempts from the same layer
GSM900 to GSM1800
the same layer (GSM900).
incoming handover attempts from the same layer GSM900 to
GSM1800, which helps to make the network planning.
cause is inter-cell handover and the source cell is at the same layer,
Figure 911.

ATTEMPTS
Unit Times

to the same layer GSM900
to GSM1800
Definition Number of outgoing handover attempts to the same layer GSM900
to GSM1800
going handover attempts the source cell (GSM900) sends to the
same layer (GSM1800).
outgoing handover attempts to the same layer GSM900 to
Point ment 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 Times

outgoing handover to the
same layer GSM900 to
GSM1800
Definition Number of outgoing handover to the same layer GSM900 to
GSM1800
going handover the source cell (GSM900) sends to the same layer
(GSM1800).
outgoing handover attempts to the same layer GSM900 to
the target cell (GSM1800), and the target cell is at the same layer
and frequency, the counter increments. The measurement point

EXECUTION FLOW
Unit Times
to the same layer GSM900
to GSM1800
Definition Number of outgoing handover success to the same layer GSM900
to GSM1800


ter-cell outgoing handover the source cell (GSM900) sends to the
same layer and frequency (GSM1800).
controlled outgoing handover to the same layer and frequency
from GSM900 to GSM1800, which helps to make the network plan-
ning.
get cell (GSM1800), and the target cell is at the same layer and

HANDOVER
Unit Times
Definition Number of incoming handover attempts from GSM900 to GSM1800
upper layer (GSM900).
incoming handover attempts at upper layer and from GSM900 to

cause is inter-cell handover and the source cell is at upper layer,
Figure 915.

ATTEMPTS
Unit Times
to the upper layer
Definition Number of outgoing handover attempts from GSM900 to GSM1800
to the upper layer
going handover attempts the source cell (GSM900) sends to upper
layer (GSM1800).
outgoing handover attempts from GSM900 to GSM1800 to the up-
per layer, which helps to make the network planning.
layer (GSM1800) and the current serving cell is GSM900, the
Figure 916.

Unit Times
GSM900 to GSM1800 to the
upper layer
Definition Number of outgoing handover from GSM900 to GSM1800 to the
upper layer
going handover the source cell (GSM900) sends to upper layer
(GSM1800).
the target cell (GSM1800), and the target cell is at upper layer and


EXECUTION FLOW
Unit Times
to the upper layer
Definition Number of outgoing handover success from GSM900 to GSM1800
to the upper layer
cell outgoing handover the source cell (GSM900) sends from upper
layer to the same frequency (GSM1800).
quency from GSM900 to GSM1800, which helps to make the net-
work planning.
get cell (GSM1800), and the target cell is at upper layer and the


HANDOVER
Unit Times
lower layer (GSM900).
incoming handover attempts at lower layer and from GSM900 to
cause is inter-cell handover and the source cell is at lower layer,
Figure 919.


ATTEMPTS
Unit Times
going handover attempts the source cell (GSM900) sends to lower
layer (GSM1800).
outgoing handover attempts to lower layer and from GSM900 to
Figure 920.

Unit Times
GSM900 to GSM1800 in the
lower layer
Definition Number of outgoing handover from GSM900 to GSM1800 in the
lower layer
going handover the source cell (GSM900) sends to lower layer
(GSM1800).
outgoing handover attempts to lower layer and from GSM900 to
the target cell (GSM1800), and the target cell is at lower layer and


EXECUTION FLOW
Unit Times
in the lower layer
in the lower layer
cell outgoing handover the source cell (GSM900) sends from the
same frequency to lower layer (GSM1800).
controlled outgoing handover from the same frequency to lower
layer from GSM900 to GSM1800, which helps to make the network
planning.
get cell (GSM1800), and the target cell is at lower layer and the


HANDOVER
Unit Times
from the same layer
from the same layer
ing handover attempts the target cell (GSM900) receives from the
incoming handover attempts at the same layer and from GSM1800
to GSM900, which helps to make the network planning.
cause is inter-cell handover and the source cell is at the same layer,
Figure 923.


ATTEMPTS
Unit Times
from the same layer
from the same layer
going handover attempts the source cell (GSM1800) sends to the
outgoing handover attempts to the same layer and from GSM1800
Point ment 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.

Unit Times
the same layer
Definition Number of outgoing handover from GSM1800 to GSM900 from the
same layer
ing handover the source cell (GSM1800) sends to the same layer
(GSM900).
outgoing handover attempts to the same layer and from GSM1800
the target cell (GSM900), and the target cell is at the same layer
and frequency, the counter increments. The measurement point


EXECUTION FLOW
Unit Times
from the same layer
from the same layer
cell outgoing handover the source cell (GSM1800) sends to the
same layer and frequency (GSM900).
controlled outgoing handover to the same layer and frequency and
from GSM1800 to GSM900, which helps to make the network plan-
ning.
target cell (GSM900), and the target cell is at the same layer and


HANDOVER
Unit Times
ing handover attempts the target cell (GSM900) receives from up-
per layer (GSM1800).
incoming handover attempts at upper layer and from GSM1800 to
cause is inter-cell handover and the source cell is at upper layer,
Figure 927.


ATTEMPTS
Unit Times
to the upper layer
to the upper layer
ing handover attempts the source cell (GSM1800) sends to upper
layer (GSM900).
Figure 928.

Unit Times
upper layer
upper layer
going handover the source cell (GSM1800) sends to upper layer
(GSM900).
the target cell (GSM900), and the target cell is at upper layer and


EXECUTION FLOW
Unit Times
to the upper layer
to the upper layer
upper layer to the same frequency (GSM900).
quency and from GSM1800 to GSM900, which helps to make the
network planning.
target cell (GSM900), and the target cell is at upper layer and the


HANDOVER
Unit Times
Description This counter counts the number of BSC-controlled inter-cell in-
coming handover attempts the target cell (GSM900) receives from
lower layer (GSM1800).
incoming handover attempts from GSM1800 to GSM900 from the
lower layer, which helps to make the network planning.
cause is inter-cell handover and the source cell is at lower layer,
Figure 931.


ATTEMPTS
Unit Times
to the lower layer
to the lower layer
ing handover attempts the source cell (GSM1800) sends to lower
layer (GSM900).
outgoing handover attempts from GSM1800 to GSM900 to the
Figure 932.

Unit Times
lower layer
lower layer
going handover the source cell (GSM1800) sends to lower layer
(GSM900).
outgoing handover attempts from GSM1800 to GSM900 to the
the target cell (GSM900), and the target cell is at lower layer and


EXECUTION FLOW
Unit Times
to the lower layer
to the lower layer
cell 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.
target cell (GSM900), and the target cell is at lower layer and the


HANDOVER
Unit 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.
Point ment report from MS. If intra-cell handover is necessary, the
Figure 935.
FIGURE 935 INTRA-CELL HANDOVER ATTEMPT
Unit 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 han-
dover attempts originated by MS when configuring the sub cell.
Usage This counter is used to find out the frequency of inter-sub cell in-
ner-circle-to-outer-circle handover attempts. It is one of the pa-
rameters to measure the sub cell operation status.
Point ment report from MS. If inner-circle-to-outer-circle handover is
necessary, the counter increments. The measurement point is A,
Unit 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-outer-
circle handovers originated by MS when configuring the sub cell.
Usage This counter is used to find out the frequency of successful inter-
sub cell inner-circle-to-outer-circle handovers.
Measurement During handover, if the source instance receives the handover
Point completed message from the target instance, and the application

cause is inner-circle-to-outer-circle handover, the counter incre-

FIGURE 937 SUCCESSFUL INTRA-CELL HANDOVER
Unit 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 han-
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 pa-
Point ment report from MS. If outer-circle-to-inner-circle handover is

Unit 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-in-
ner-circle handovers originated by MS when configuring the sub
cell.
sub cell outer-circle-to-inner-circle handovers, and is to find out
the success ratio of intra-sub cell handovers.
cause is outer-circle-to-inner-circle handover, the counter incre-
Unit Times

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 han-
inner-circle-to-inner-circle handover attempts. It is one of the pa-
Point ment report from MS. If inner-circle-to-inner-circle handover is
Unit Times
intra-cell inner-circle-to-inner
-circle handover success
Definition Number of intra-cell inner-circle-to-inner-circle handover success
Description This counter counts the number of successful inner-circle-to-inner-
circle handovers originated by MS when configuring the sub cell.
sub cell inner-circle-to-inner-circle handovers.

cause is inner-circle-to-inner-circle handover, the counter incre-

Unit Times
intra-cell outer-circle-to-oute
Definition Number of intra-cell outer-circle-to-outer-circle handover at-
tempts
Description This counter counts the number of outer-circle-to-outer-circle han-
outer-circle-to-outer-circle handover attempts. It is one of the
parameters to measure the sub cell operation status.
Point ment report from MS. If outer-circle-to-outer-circle handover is

Unit 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-cir-
cle-to-outer-circle handovers originated by MS when configuring
the sub cell.
sub cell outer-circle-to-outer-circle handovers.
cause is outer-circle-to-outer-circle handover, the counter incre-
Unit Times

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.
current attempt cells are 3G cells, BSC sends MSC the handover
request message A_HO_RQD, the counter increments. The mea-
Unit Times
Related Features ZGO-02-02-014 IMSI Based Handover
handover from 2G to 3G
Definition Number of handover from 2G to 3G


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.
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 Times
handover success from 2G
to 3G
Definition 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.
current attempt cells are governed by various BSCs, BSC sends
MSC the handover request message A_HO_RQD to trigger the in-
ter-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 Times
handover attempts from 3G
to 2G
Definition Number of handover attempts from 3G to 2G
attempts originated by MS.
Usage This counter is used to find out the frequency of handover attempts
environment.
Measurement When 2G cell receives the channel application request, if the ap-
Point plication cause is external incoming handover and the source cell
is 3G cell, the counter increments. The measurement point is A,
as shown inFigure 947.

Unit Times
Related Features ZGO-02-03-002 GSM/WCDMA Interworking
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 When 2G cell receives the channel handover request from MSC, if
Point 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 Times

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 When 2G cell receives the handover completed message, if the
Point application cause is MSC-controlled inter-BSC incoming handover
and the source cell is 3G cell, the counter increments. The mea-
Unit 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 incom-
ing handover attempts from TCH/F. It is one of the parameters to
measure the wireless environment.

Measurement When BSC receives the channel application request, if the applica-
Point tion cause is intra-cell handover, and the source channel is TCH/F,
Figure 950.
FIGURE 950 INTRA-CELL INCOMING HANDOVER ATTEMPT
Unit Times
intra-cell TCH/F-to-TCH/F
handover
Definition Number of intra-cell TCH/F-to-TCH/F handover
Description This counter counts the number of intra-cell TCH/F-to-TCH/F in-
coming handover originated by MS.
Usage This counter is used to find out the frequency of intra-cell TCH/F-
to-TCH/F incoming handover attempts. It is one of the parameters
Measurement When BSC receives the channel application request, if the ap-
Point plication 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 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-to-
TCH/F incoming handover originated by MS.
tra-cell TCH/F-to-TCH/F incoming handover. It is one of the pa-
rameters to measure the wireless environment.
Point tion 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


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 in-
Usage This counter is used to find out the frequency of intra-cell TCH/F-
to-TCH/H incoming handover attempts. It is one of the parameters
Point plication cause is intra-cell handover, and the source channel is
TCH/H; if the new channel is successfully applied and activated,
Figure 953.
Unit Times

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-to-
TCH/H incoming handover originated by MS.
tra-cell TCH/F-to-TCH/H incoming handover. It is one of the pa-
Point tion cause is intra-cell handover, and the source channel is TCH/F;
is TCH/H, the counter increments. The measurement point is A,
Unit Times
from TCH/H
Definition Number of intra-cell handover attempts from TCH/H
Description This counter counts the number of intra-cell incoming handover
attempts from TCH/H originated by MS.

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
Point tion cause is intra-cell handover, and the source channel is TCH/H,
Figure 955.
Unit Times
intra-cell TCH/H-to-TCH/F
handover
Definition Number of intra-cell TCH/H-to-TCH/F handover
Description This counter counts the number of intra-cell TCH/H-to-TCH/F in-
Usage This counter is used to find out the frequency of intra-cell TCH/H-
Point tion 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 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-to-
tra-cell TCH/H-to-TCH/F incoming handover. It is one of the pa-
is TCH/F, the counter increments. The measurement point is A,

Unit Times
intra-cell TCH/H-to-TCH/H
handover
Definition Number of intra-cell TCH/H-to-TCH/H handover
Description This counter counts the number of intra-cell TCH/H-to-TCH/H in-
Usage This counter is used to find out the frequency of intra-cell TCH/H-
new channel is TCH/H, the counter increments. The measurement

Unit 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-to-
tra-cell TCH/H-to-TCH/H incoming handover. It is one of the pa-

Unit 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 incom-
ing handover attempts from TCH/F. It is one of the parameters to
Point tion cause is inter-cell handover, and the source channel is TCH/F,
Figure 960.

ATTEMPTS
Unit Times

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 in-
Usage This counter is used to find out the frequency of inter-cell TCH/F-
Point plication 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 Times
inter-cell TCH/F-to-TCH/F
handover success
Definition Number of inter-cell TCH/F-to-TCH/F handover success
Description This counter counts the number of successful inter-cell TCH/F-to-

ter-cell TCH/F-to-TCH/F incoming handover. It is one of the pa-
Point tion cause is inter-cell handover, and the source channel is TCH/F;
Unit Times
inter-cell TCH/F-to-TCH/H
handover
Definition Number of inter-cell TCH/F-to-TCH/H handover
Description This counter counts the number of inter-cell TCH/F-to-TCH/H in-
Usage This counter is used to find out the frequency of inter-cell TCH/F-


ATTEMPTS
Unit 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-to-
ter-cell TCH/F-to-TCH/H incoming handover. It is one of the pa-

Unit Times
inter-cell handover attempts
from TCH/H
Definition 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
Point tion cause is inter-cell handover, and the source channel is TCH/H,
Figure 965.


ATTEMPTS
Unit 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 in-
Usage This counter is used to find out the frequency of inter-cell TCH/H-
Point tion cause is inter-cell handover, and the source channel is TCH/H;
new channel is TCH/F, the counter increments. The measurement


ATTEMPTS
Unit Times
inter-cell TCH/H-to-TCH/F
handover success
Definition Number of inter-cell TCH/H-to-TCH/F handover success
Description This counter counts the number of successful inter-cell TCH/H-to-
ter-cell TCH/H-to-TCH/F incoming handover. It is one of the pa-

Unit 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 in-
Usage This counter is used to find out the frequency of inter-cell TCH/H-


ATTEMPTS
Unit Times
inter-cell TCH/H-to-TCH/H
handover success
Definition Number of inter-cell TCH/H-to-TCH/H handover success
Description This counter counts the number of successful inter-cell TCH/H-to-
ter-cell TCH/H-to-TCH/H incoming handover. It is one of the pa-

Unit 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 in-
ter-BSC (the source cell and the target cell are at different bands)
outgoing handover attempts. It is one of the parameters to mea-
sure the wireless environment.
current attempt cells are governed by different BSCs, BSC will send
MSC the handover request A_HO_RQD to trigger inter-BSC han-
dover. If the source cell and the target cell that are at different
bands, the counter increments. The measurement point is A, as

Unit Times

attempts
Definition 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 When the target cell receives the channel application request, if the
Point application cause is external incoming handover, and the source
cell and the target cell that are at different bands, the counter in-

Unit Times
intra-cell invalid handovers
Definition Number of intra-cell invalid handovers
Description This counter counts the number of intra-cell invalid handovers. In-
valid handover refers to that: handovers continue to happen in a
cell where there is UL /DL interference; if the number of the han-
dovers exceeds the pre-set threshold, intra-cell handover punish-
ment 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 consid-
ered 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 When BSC receives the channel application request, if the appli-
Point cation cause is intra-cell interference handover, and such interfer-
ence handover has already occurred in the pre-defined scope of
time, the counter increments. The measurement point is A, as

Unit Times
ZGO-02-02-005 Handover Failure Penalty
(emergency service)
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-con-
trolled inter-cell incoming handover initiated by a MS on emer-
gency service. Target instance can initiate forced release attempt
based on MS priority and MSC & BSC settings during channel allo-
cation failure.
Usage This counter counts the frequency of forced release attempts oc-
curred during BSC-controlled inter-cell incoming handover initi-
ated by a MS. It can reflect the handover process.
Measurement Intra-BSC target cell receives radio channel request to determine
Point whether to do forced release 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 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 re-
lease) (emergency service)
Description This counter counts the number of forced release due to unavail-
able radio resource in target cell in the process of BSC-controlled
inter-cell incoming handover initiated by a MS on emergency ser-
vice.
Usage This counter counts the frequency of forced release occurred dur-
ing BSC-controlled inter-cell incoming handover initiated by a MS.
It can reflect the handover process.
Measurement Intra-BSC target cell receives radio channel request to do forced
Point 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 mes-
sage sent from forced instance. The measurement point is A2, as

FIGURE 974 BSC-CONTROLLED FORCED RELEASE ON INCOMING HANDOVER
Unit Times
due to forced handover
(emergency service)
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 BSC-
controlled inter-cell incoming handover initiated by a MS on emer-
gency service.
Usage This counter counts the frequency of forced handover attempts
occurred during BSC-controlled inter-cell incoming handover initi-
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 unavail-
vice.
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 Intra-BSC target cell receives radio channel request and adds it
Point into a queue after sending forced handover message to forced han-
dover instance if the request reason is BSC-controlled inter-cell in-
coming handover and the target cell has not available radio chan-
nel. This counter increments if target cell receives available re-
source message. The measurement point is A2, as shown in Figure
976.

FIGURE 976 BSC-CONTROLLED FORCED HANDOVER ON INCOMING

HANDOVER
Unit Times
due to queue (emergency
service)
due to queue (emergency service)
Description This counter counts the number of queue attempts due to unavail-
vice.
Usage This counter counts the frequency of queue attempts occurred dur-
ing BSC-controlled inter-cell incoming handover initiated by a MS.
Point whether to do queue 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 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 BSC-
controlled inter-cell incoming handover initiated by a MS. It can
reflect the handover process.
Measurement Intra-BSC target cell receives radio channel request and adds tar-
Point get 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 re-
ceives available resource message. The measurement point is A2,

FIGURE 978 BSC-CONTROLLED QUEUE ON INCOMING HANDOVER
Unit Times
forced release (emergency
service)
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-con-
trolled inter-BSC incoming handover initiated by a MS on emer-
gency service. Target instance can initiate forced release attempt
based on MS priority and MSC & BSC settings during channel allo-
cation failure.

Usage This counter counts the frequency of forced release attempts oc-
curred during BSC-controlled inter-BSC incoming handover initi-
Measurement Target cell receives radio channel request to determine whether to
Point 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 measure-
ment 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)
able radio resource in target cell in the process of MSC-controlled
inter-BSC incoming handover initiated by a MS on emergency ser-
vice.
during BSC-controlled inter-BSC incoming handover initiated by a
dover instance if the request reason is MSC-controlled inter-BSC
incoming handover and the target cell has not available radio chan-
source message. The measurement point is A, as shown in Figure
980.

FIGURE 980 MSC-CONTROLLED FORCED RELEASE ON INCOMING HANDOVER
Unit Times
MSC-controlled inter-cell
due to forced handover
(emergency service)
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 MSC-
controlled inter-BSC incoming handover initiated by a MS on emer-
gency service.
Usage This counter counts the frequency of forced handover attempt oc-
curred during MSC-controlled inter-BSC incoming handover initi-
ated by a emergent MS. It can reflect the handover process.
Measurement Target cell receives radio channel request to determine whether
Point to do forced handover attempt if the request reason is MSC-con-
trolled 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)
vice.
during BSC-controlled inter-BSC incoming handover initiated by a
dover instance if the request reason is MSC-controlled inter-BSC
incoming handover and the target cell has not available radio chan-
source message. The measurement point is A, as shown in Figure
982.

FIGURE 982 MSC-CONTROLLED FORCED HANDOVER ON INCOMING

HANDOVER
Unit Times
queue (emergency service)
queue (emergency service)
Description This counter counts the number of queue attempts due to unavail-
vice.
Usage This counter counts the frequency of queue attempts occurred dur-
ing BSC-controlled inter-BSC incoming handover initiated by a MS.
Measurement Target cell receives radio channel request to determine whether to
Point do a queue if the request reason is MSC-controlled inter-BSC in-
coming handover and the target cell has not available radio chan-
nel. 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) (emer-
gency 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 BSC-
controlled inter-BSC incoming handover initiated by a MS. It can
reflect the handover process.
Measurement Target cell receives radio channel request and adds target instance
Point 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

FIGURE 984 MSC-CONTROLLED QUEUE ON INCOMING HANDOVER
Unit Times
forced handover target
not found (BSC-controlled
inter-cell handover due to
forced handover)
Definition Number of forced handover target not found (BSC-controlled inter-
cell 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 Intra-BSC target cell receives radio channel request if the request
Point reason is BSC-controlled inter-cell incoming handover and the tar-
get cell has not available radio channel. This counter increments if
the forced handover target is not found after initiating forced han-
dover 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 re-
quest to lower priority user on forced handover attempt due to
unavailable radio resource in target cell in the process of BSC-con-
trolled inter-cell incoming handover initiated by a MS.
Usage This counter counts the frequency of sending forced handover re-
quest to a lower priority user during BSC-controlled inter-cell in-
coming handover initiated by a MS. It can reflect the handover
process.
get cell has not available radio channel. This counter increments
if sending forced handover request to a lower priority user after

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)
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 pri-
ority 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.
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

failure (BSC-controlled
forced handover)
Definition Number of lower PRI user handover failure (BSC-controlled inter-
cell handover due to forced handover)
Description This counter counts the number of receiving failure from lower pri-
ority user due to handover failure 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 handover failure
from a lower priority user during BSC-controlled inter-cell incom-
ing handover initiated by a MS. It can reflect the handover process.
if receiving handover failure from a lower priority user after initi-
ating 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.

if timeout for waiting resource occurs after initiating forced han-
dover. 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)
Definition Number of forced release target not found (BSC-controlled inter-
cell 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.
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.
while initiating forced release during BSC-controlled inter-cell in-

coming handover initiated by a MS. It can reflect the handover

process.
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)
Definition Number of HO Target not found (MSC-controlled incoming han-
dover due to forced handover)
Description This counter counts the number of HO Target not found (MSC-
controlled incoming handover due to forced handover)

Usage 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.
Measurement � This counter increments after BSC receives incoming handover
Point message and does forced handover attempt due to unavailable
resource.
� This counter increments if the interval timer to search for han-
dover 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.
Unit 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 re-
quest 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 envi-
ronment.
Measurement � This counter increments after BSC receives incoming handover
Point message and does forced handover attempt due to unavailable
resource.
� This counter increments if the interval timer to search for han-
dover target is timeout on handover.
handover attempt fails.
Unit Times

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 han-
dover)
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 envi-
ronment.
Measurement This counter increments if BSC receives forced handover failure
Point and incoming handover fails due to failure of resource request.
Unit Times
failure (MSC-controlled
forced handover)
Definition Number of lower PRI user handover failure (MSC-controlled incom-
ing 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 This counter increments if BSC receives forced handover failure

Point and incoming handover fails due to failure of forced handover.
Unit Times

resource (MSC-controlled
forced handover)
Definition Number of high PRI user time out for wait resource (MSC-con-
trolled 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 han-
dover).
for higher priority user on MSC-controlled incoming handover due
to forced handover. It is one of parameters to measure radio en-
vironment.
Measurement This counter increments if the timer of waiting for resource after
Point initiating forced handover.
Unit Times
found (MSC-controlled
forced release)
Definition Number of forced release target not found (MSC-controlled incom-
ing 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).

Usage This counter counts the frequency of forced release target not
found on MSC-controlled incoming handover due to forced han-
dover. It is one of parameters to measure radio environment.
Measurement � This counter increments after BSC receives incoming forced
Point 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.
Unit Times

resource (MSC-controlled
forced release)
Definition Number of high PRI user time out for wait resource (MSC-con-
trolled 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).
for higher priority user on MSC-controlled incoming handover due
to forced release. It is one of parameters to measure radio envi-
ronment.
Measurement This counter increments if the timer of waiting for resource is time-
Point out after initiating forced release.
Unit Times

handover)
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 mea-
sure radio environment.
Measurement This counter increments if BSC receives effective messages in re-
Point source message on forced handover and the messages hold data-
base resource.
Unit Times
release)
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 This counter increments if BSC receives effective messages in re-
Point source message on forced release and the messages hold database
resource.
Unit Times

Definition Number of handover attempts due to eMLPP forced handover
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 This counter increments if it is forced handover on intra-cell han-
Point dover.
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 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 This counter increments if it is forced handover on intra-cell han-
Point dover.
This counter increments if it is forced handover based on hier-
archy and frequency relationship on BSC-controlled inter-cell or
MSC-controlled outgoing handover.
Unit 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 ra-
dio environment.
Measurement This counter increments if it is intra-cell forced handover on han-
Point dover success.
This counter increments if it is forced handover based on hier-
archy and frequency relationship on BSC-controlled inter-cell or
MSC-controlled outgoing handover success.
Unit Times
between PLMN
This counter is not used for the time being.
outgoing handover between
PLMN

between PLMN
handover attempts between
PLMN
handover request fail
between PLMN due to
unknown reason

between PLMN due to
unavailable ground resource
Description This counter counts the number of failures of MSC-controlled in-
ter-PLMN outgoing handover requests due to no available ground
resource. When MSC receives the handover request rejection mes-
sage from BSC on TCH, it queries the rejection cause. If the re-
jection cause is CAUSE_REQ_CIC_UNAVAIL, then the counter in-
crements.
Usage This counter is used to find out the frequency of failure of MSC-con-
trolled 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 When MSC receives the handover request rejection message
Point 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

between PLMN due to
unavailable radio resource
between PLMN due to other
reasons
Description This counter counts the number of failures of MSC-controlled in-
ter-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 MSC-
controlled inter-PLMN outgoing handover request initiated by MS
due to other reasons. It also helps study the condition of handover
initiated by MSC.
Measurement When MSC receives the handover request rejection message from
Point 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.
Unit 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 out-
going handover initiated by MS. It also helps study the condition
of handover initiated by MSC.
Measurement 1. When BSC receives the command Clear Cmd from A-interface,
Point 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.

FIGURE 994 MSC-CONTROLLED INTER-PLMN OUTGOING HANDOVER EXECUTION AND NO ABNORMAL

RELEASE
Unit Times
handover success between
PLMN
ter-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 MSC-
controlled inter-PLMN outgoing handovers. It also helps study the
handover initiated by MSC.
Measurement When BSC receives the command Clear Cmd from MSC, the timer
Point THOOUTGO is timeout. If the cause in the command Clear Cmd is
CAUSE_HO_SUCCESSFUL, then the counter counts.
Unit Times

incoming handover attempt
between PLMN
incoming handover between
PLMN
incoming handover
force-release attempt
between PLMN

PLMN due to force release
incoming handover queue
attempt between PLMN
PLMN due to queue

incoming handover
force-handover attempt
between PLMN
PLMN due to force handover
between PLMN

handover attempt between
PLMN
Description This counter counts the number of MSC-controlled inter-PLMN
incoming handover attempts. When BSC receives the RadioAp-
ply 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 in-
ter-PLMN incoming handover attempts. It also helps study the
handover initiated by MSC.
Measurement When BSC receives the RadioApply message from MSC, it queries
Point the cause. If AppCause is INCOME_HO, then the counter counts.
The measurement point is A1, as shown in Figure 995.
FIGURE 995 MSC-CONTROLLED INTER-PLMN INCOMING HANDOVER FLOW
Unit Times

C901090200 A interface
incoming handover fail
between PLMN due to circuit
block
Description This counter counts the number of A-interface inter-PLMN incom-
ing handover failures due to circuit's being blocked. When MSC re-
ceives the Handover Failure message, if the handover fails due to
CAUSE_REQ_CIC_UNAVAIL and the handover is inter-PLMN han-
dover, then the counter increments.
Usage This counter is used to find out the number of A-interface inter-
PLMN incoming handover failures due to circuit's being blocked. It
also helps study the handover initiated by MSC.
Measurement When MSC receives the Handover Failure message, if the handover
Point 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

between PLMN due to circuit
unmatch
ing handover failures due to circuit mismatching. When MSC re-
ceives the Handover Failure message, if the handover fails due
to CAUSE_CIRCUIT_POOL_MISMATCH and the handover is inter-
PLMN handover, then the counter increments.
Usage This counter is used to find out the number of A-interface inter-
PLMN incoming handover failures due to circuit mismatching. It
also helps study the handover initiated by MSC.
Measurement When MSC receives the Handover Failure message, if the handover
Point failiure cause in this message is CAUSE_CIRCUIT_POOL_MIS-
MATCH and the handover is inter-PLMN handover, then the
counter counts.
Unit Times
between PLMN due to
unavailable radio resource
ing 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 in-
ter-PLMN incoming handover failures due to no available radio re-
source. It also helps study the handover initiated by MSC.
Measurement 1. When MSC receives the Handover Failure message, if the han-
Point dover 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 han-
dover failiure cause in this message is CAUSE_NO_RR_AVAI

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 in-
ter-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 MSC-
controlled inter-PLMN incoming handover force-release. It also
helps study the inter-PLMN incoming handover force-release initi-
ated by MSC.

Measurement When BSC receives the command HoReq from MSC, if no radio re-
Point source is available and forced release is allowed, then the counter
counts.
Unit Times
due to force release
Description This counter counts the number of MSC-controlled inter-PLMN in-
coming 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.
ter-PLMN incoming handover due to forced release. It also helps
study the inter-PLMN incoming handover initiated by MSC due to
forced release.
Measurement When BSC receives the command HoReq from MSC, if the CS in-
Point stance carries the RADIO_AVAILABLE message and forced release
is allowed, then the counter counts.
Unit Times
handover queue attempt
between PLMN
ter-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 When BSC receives the command Ho Req from MSC, it sends the
Point 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 in-
coming handover due to queuing. After BSC receives the han-
dover command, it requests for channel resource. If the request
fails, the cause of channel request is INCOME_HO, queuing is al-
lowed, and the handover is inter-PLMN incoming handover, then
ter-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 When BSC receives the command HoReq from MSC, if the CS in-
Point stance carries the RADIO_AVAILABLE message and queuing is al-
lowed, then the counter counts.

Unit Times
handover force-handover
ter-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 MSC-
controlled 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 When BSC receives the command Ho Req from MSC, it sends the
Point command Chan Act to BTS. If no channel request fails but forced
handover is allowed, then the counter counts.
Unit Times
due to force handover

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 When Rancs receives the CS service migration sent from DBS, if
Point byCsMoveCause == HR_DEFRAG, then the counter counts.
Unit 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.

Measurement When BSC receives the CS service migration command from DBS,
Point 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 DUE TO CS SERVICE MIGRATION
Unit Times
handover attempt from AMR
FR to AMR HR due to high
load
Description 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 Times
handover from AMR FR to
AMR HR due to high load
handover from AMR FR to AMR HR,if the radio resource is available
and the channel activation succeeds, the counter increments. The

Unit Times

handover success from AMR
FR to AMR HR due to high
load
handover from AMR FR to AMR HR,if the MS successfully performs
handover to the new channel and the handover completion mes-
sage is sent, the counter increments. The measurement point is

Unit Times
handover attempt from FR to
HR due to high load
handover from FR to HR, it will trigger the process of finding an ex-
isted 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 Times
handover from FR to HR due
to high load
handover from FR to HR,if the radio resource is available and the
channel activation succeeds, the counter increments. The mea-
surement point is A2, as shown in Figure 1003.

Unit Times

handover success from FR
to HR due to high load
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 Times
handover attempt from AMR
HR to AMR FR due to bad
quality
Description Suppose the voice quality of an AMR HR call is poor. If all other
handover conditions are not satisfied but the threshold of intra-
cell 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 Times
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

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 Times
handover attempt from HR
to FR due to bad quality
Description Suppose the voice quality of an HR call is poor. If all other han-
dover conditions are not satisfied but the threshold of intra-cell
handover from HR to FR is reached, the intra-cell handover at-
tempt from HR to FR is initiated, and the counter increments. The


Unit Times
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

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 chan-
nel and the handover completion message is sent, the counter in-
crements. The measurement point is A3, as shown in Figure 1010.

Unit Times
outgoing handover attempts,
Description During the process of intra-BSC inter-cell handover, after BSC re-
ceives the measurement report from MS, it performs handover de-
cision. 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 Times
outgoing handover, from
GSM900 to GSM900
Description During the process of intra-BSC inter-cell handover, after BSC suc-
cessfully 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


Unit Times
outgoing handover success,
Description 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 desti-
nation cell's frequency band is 900 MHz, the counter increments.


Unit Times
cision. If it decides intra-BSC inter-cell handover is required and if


Unit Times
GSM1800 to GSM1800


Unit Times
cell. If the source cell's frequency band is 1800 MHz and the
destination cell's frequency band is 1800 MHz, the counter incre-
ments. The measurement point is A3, as shown in Figure 1016.


Unit Times
cision. 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 Times
GSM900 to GSM1800


Unit Times
cell. If the source cell's frequency band is 900 MHz and the desti-
nation cell's frequency band is 1800 MHz, the counter increments.


Unit Times
cision. If it decides intra-BSC inter-cell handover is required and if


Unit Times
GSM1800 to GSM900


Unit Times
cell. If the source cell's frequency band is 1800 MHz and the des-
tination cell's frequency band is 900 MHz, the counter increments.


Unit Times
Description 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 mea-

FIGURE 1023 INTER-BSC INTER-CELL HANDOVER FLOW

Unit Times
GSM900 to GSM900
BSC receives the HANDOVER COMMAND message from MSC. If


Unit Times
Description During the process of inter-BSC inter-cell handover, MS success-
fully 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 Times


Unit Times

GSM1800 to GSM1800

Unit Times

1800 MHz and the destination cell's frequency band is 1800 MHz,
in Figure 1028.

Unit Times


Unit Times
GSM900 to GSM1800


Unit Times
in Figure 1031.


Unit Times
frequency band is 900 MHz, the counter increments. The measure-

Unit Times
GSM1800 to GSM900

Unit Times

in Figure 1034.

Unit Times

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 PBGT ...................................... 1013
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

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 han-
dover from the selected cell to the adjacent cell so as to know the
handover situation.
Measurement � When handover happens between cells inside one BSC, and
Point source cell sends radio channel request message to target cell,
in Figure 1035.

ATTEMPT
� When external handover happens inside one MSC, and source

cell sends handover request message to MSC, the counter in-
crements. The measurement point is A, as shown in Figure
1036.

Chapter 16 Adjacent Cell Handover Measurement
Unit 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 han-
dover situation.
Point source cell receives handover completion message from target
cell, the counter increments. The measurement point is A, as


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 Times
handover attempts from
adjacent cell to the selected
cell.
Definition Number of handover attempts from adjacent cell to the selected
cell.

dover from adjacent cell to the selected cell so as to know the
handover situation.
Measurement � When handover happens between cells inside one BSC, target
Point 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 Times

adjacent cell to the selected
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.
Point target cell receives handover completion message from MS, the
Figure 1041.

HANDOVER
� When external handover happens inside one MSC, and tar-

get cell receives handover completion message from MS, the
Figure 1042.
Unit Times

cell due to better UL quality.
Definition Number of handover attempts from selected cell to the adjacent
cell due to better UL quality
dover from a selected cell to the adjacent cell so as to know the
handover situation.
Point target cell receives radio channel request message from source
cell due to better UL quality, the counter increments. The mea-

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

Unit Times
Related Features ZGB-02-02-002 Basic Handover Decision Criteria
cell due to better DL quality.
cell due to better DL quality
dover from selected cell to the adjacent cell so as to know the
handover situation.
cell due to better DL quality, the counter increments. The mea-


ATTEMPTS

cell receives handover request message from MSC due to bet-
ter DL quality, the counter increments. The measurement point
Unit Times
cell due to better UL quality.
Definition Number of successful handover from the selected cell to the adja-
cent cell due to better UL quality.

Usage 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
Point source cell receives handover completion message from tar-
get cell due to better UL quality, the counter increments. The

HANDOVER

cell receives release command from MSC due to better UL qual-
ity, the counter increments. The measurement point is A, as
Unit Times

cell due to better DL quality.
Definition Number of handover success from selected cell to the adjacent cell
due to better DL quality
from a selected cell to the adjacent cell due to better DL quality so
Point source cell receives handover completion message from tar-
get 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.

Unit Times
cell due to better UL strength.
dover from a selected cell to the adjacent cell due to better UL
strength so as to know the handover situation.
cell due to better UL strength, the counter increments. The


ATTEMPTS

ter UL strength, the counter increments. The measurement
point is A, as shown in Figure 1052
Unit Times
cell due to better DL strength.

dover 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

ter DL strength, the counter increments. The measurement
Unit Times

Definition Number of successful handover from selected cell to the adjacent
cell due to better UL strength
from a selected cell to the adjacent cell due to better UL strength
so as to know the handover situation.
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

Unit Times
cent cell due to better DL strength
from a selected cell to the adjacent cell due to better DL strength
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 Times
cell due to PBGT
Definition Number of handover attempts from the selected cell to the adja-
cent cell due to better PBGT

dover 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 measure-
ment point is A, as shown inFigure 1059.

ATTEMPTS

ter PBGT, the counter increments. The measurement point is
Unit 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
cell due to better PBGT, the counter increments. The measure-

HANDOVER

cell receives release command from MSC due to better PBGT,
in Figure 1062.

Unit Times
cell due to other factors.
Definition Number of handover attempts from the selected cell to the adja-
cent cell due to other factors.
dover from a selected cell to the adjacent cell due to other factors,
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.
cent cell due to other factors

Usage 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 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 inap-
propriate parameter setting.
Measurement � For BSC-controlled inter-cell handover, the counter increments
Point 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.

Unit Times
C901100018 The max of

RTD
Description This counter counts the maximum reference time difference be-
tween 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 dwRT-
DMa.
Usage This counter is used to find out the maximum reference time dif-
ference between two cells.
Measurement When BSC receives the Assign Complete message, if it contains
Point the mobile time difference, then the counter counts. The mea-

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 mes-
sage 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 When BSC receives the Assign Complete message from MS, if it
Point contains the mobile time difference, then the counter counts.
Unit Times

C901100020 The number of

RTD
Description This counter counts the number of sampled reference time differ-
ences 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 When BSC receives the Assign Complete message from MS, if it
Point contains the mobile time difference, then the counter counts.
Unit Times
cell due to DL quality rapid
drop
Description This counter counts the number of MS's outgoing handover at-
tempts 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 han-
dover attempts from the local cell to a specific cell. It helps check
the direction of handover between cells.
� 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 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

cell due to DL quality rapid
drop
Description This counter counts the number of MS's successful outgoing han-
dovers 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.
� For BSC-controlled inter-cell handover, the counter increments
when the source cell receives the handover completion mes-
sage 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 OF BSC-CONTROLLED OUTGOING HANDOVER

SUCCESSES
FIGURE 1073 NUMBER OF MSC-CONTROLLED OUTGOING HANDOVER

SUCCESSES


Unit Times


Chapter 17
Radio Access
Measurement
Table of Contents
Overview...................................................................... 1026
C901110001 Number of invalid access requests................. 1027
C901110003 Number of MOC access success for pro-
cesses.......................................................................... 1027
C901110006 Number of MTC access success for pro-
cesses.......................................................................... 1028
C901110008 Number of call re-establishment access at-
tempts ......................................................................... 1028
C901110009 Number of call re-establishment access success
for processes ................................................................ 1029
C901110010 Number of call re-establishment access suc-
cess............................................................................. 1029
C901110011 Number of emergency calls access at-
tempts ......................................................................... 1030
C901110012 Number of emergency calls access success for
processes ..................................................................... 1030
C901110013 Number of emergency calls access suc-
cess............................................................................. 1031
C901110014 Number of LOC access attempts ................... 1031
C901110015 Number of LOC access success for pro-
cesses.......................................................................... 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 at-
tempts ......................................................................... 1034
C901110021 Number of LMU Establishment access success
for processes ................................................................ 1034
C901110022 Number of LMU Establishment access suc-
cess............................................................................. 1035
C901110023 Number of accesses due to location up-
date ............................................................................ 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 Supple-
ment ........................................................................... 1037
C901110029 Number of CM service requests of LCS........... 1037

C901110031 Number of wireless access due to call re-estab-

lishments ..................................................................... 1037
C901110032 Number of wireless accesses due to IMSI de-
tachment ..................................................................... 1038
C901110033 Number of wireless accesses due to other
causes ......................................................................... 1038
C901110034 Number of access due to Notification re-
sponse ......................................................................... 1039
C901110035 Number of access due to Immediate
setup ........................................................................... 1040
C901110036 Number of access due to Talker indica-
tion ............................................................................. 1041
C901110037 Number of access due to DATA Indication......... 1042
C901110038 Number of access due to priority uplink re-
quest ........................................................................... 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 adjust-
ment, 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 send-
ing 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 num-
ber 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 suc-
cessful access to the number of access request represents the col-
lision 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.

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 The counter increments when MS fails in requiring radio channel
Point 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

Description This counter counts the Number of MOC access success for pro-
cesses. The counter increments when BSC allows MS to be ac-
cessed into the network due to MOC attempts and accepts channel
request sent by MS and allocates and activates channel success-
fully. 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 The counter increments when channel is activated successfully.
Point 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 pro-
cesses. The counter increments when BSC allows MS to be ac-
cessed into the network due to MTC attempts and accepts channel
request sent by MS and allocates and activates channel success-
fully. 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.
Process.
Unit Times
C901110008 Number of call

re-establishment access
attempts
Definition Number of call re-establishment access attempts
Description This counter counts the Number of call re-establishment access at-
tempts. The counter increments when MS sends CHL_REQ message
through BTS to BSC for requiring radio channel, if TA does not ex-
ceed 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 The counter increments when MS requires channel from BSC and
Point TA does not exceed the scope. The measurement point is A1, as
shown in Figure Radio Access Process.
Unit 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 acti-
vates channel successfully. Meanwhile, BSC sends IMM_ASS mes-
sage to MS.
processes due to call re-establishment.
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 mes-
sage 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 The counter increments when BSC receives EST_IND message. The
Point measurement point is A4, as shown in Figure Radio Access Process.
Unit Times

emergency calls access
attempts
Definition Number of emergency calls access attempts
Description This counter counts the Number of emergency calls access at-
ceed cell scope and the access cause is emergency calls.
attempts due to emergency calls.
Unit Times
Related Features ZGB-01-03-001 Emergency Call Handling
Definition Number of emergency calls access success for processes
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.
processes due to emergency calls.
Process.
Unit Times

success
Definition Number of emergency calls access success
Description This counter counts the Number of emergency calls access suc-
cess. 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.
Unit 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.
attempts due to LOC.
Unit Times
LOC access success for
processes
Definition Number of LOC access success for processes

Description This counter counts the number of successful random access pro-
cesses 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.
processes due to LOC.
Process.
Unit Times
LOC access success
Definition Number of LOC access success
Description This counter counts the number of access success. The counter in-
crements when MS receives IMM_ASS message sent by BSC and suc-
cessfully 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 suc-
cess.
Unit Times
C901110017 Number
of other causes access
attempts
Definition 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.
attempts due to other causes.

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 pro-
cesses for other causes. The counter increments when BSC al-
lows 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.
processes due to other causes.
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.
Unit Times

LMU Establishment Access
attempts
Definition Number of LMU Establishment Access attempts
Description This counter counts the Number of LMU Establishment Access at-
ceed cell scope and the access cause is LMU establishment.
Usage This counter is used to find out the frequency of LMU establishment
access request.
Unit Times
LMU Establishment access
Definition Number of LMU Establishment access success for processes
Description This counter counts the Number of LMU Establishment access suc-
cess 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.
access request successfully.
Process.
Unit Times

LMU Establishment access
success
Definition Number of LMU Establishment access success
Description This counter counts the Number of LMU Establishment access suc-
cess. The counter increments when MS sends CHL_REQ message
ceed cell scope and the access cause is LMU establishment.
access successfully.
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 lo-
cation 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.
Unit Times
Access due to CM SERVICE
REQ
Definition Number of Access due to CM SERVICE REQ

Description This counter counts the Number of Access due to CM SERVICE REQ.
The counter increments when the access cause in Layer3 informa-
tion 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.
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.
Unit Times
service requests of SMS
Definition Number of access of SMS's CM SERVICE REQ
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.
Unit 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 SER-
VICE 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 supple-
ment's CM SERVICE REQ.
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 SER-
VICE 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.
Unit Times
wireless access due to call
re-establishments
Definition Number of wireless accesses due to call re-establishments
Description This counter counts the Number of wireless accesses due to call
re-establishments. The counter increments when the access cause

in Layer3 information carried in EST_IND message received by BSC

is call re-establishments.
accesses due to call re-establishments.
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.
accesses due to IMSI detachment.
Unit Times
wireless accesses due to
other causes
Definition Number of wireless accesses due to other causes
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.
accesses due to other causes.
Unit Times

access due to Notification
response
Description This counter counts the number of accesses due to notification re-
sponse in the group call service. After BSC receives the EST_IND
message, if the layer-3 information carried in this message indi-
cates that the access is due to MS's response to notification, then
in Figure 1075.

Unit Times

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
cates that the access is due to immediate setup, then the counter
1076.

Unit Times

C901110036 Number
of access due to Talker
indication
Description This counter counts the number of accesses due to Talker indi-
cation in the group call service. After BSC receives the EST_IND
cates that the access is due to Talker indication, then the counter
1077.

Unit Times

C901110037 Number
of access due to DATA
Indication
Description This counter counts the number of accesses due to DATA indica-
tion in the group call service. After BSC receives the EST_IND
cates that the access is due to DATA indication, then the counter
1078.

Unit Times

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
cates that the access is due to priority uplink request, then the
Figure 1079.

Unit Times

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 Times

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 Times


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 chan-
nels ............................................................................. 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 chan-
nels ............................................................................. 1052
C901120006 Total value of DL quality strength values in wire-
less 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 chan-
nels ............................................................................. 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


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 estab-
lishing TFO ................................................................... 1062
C901120057 Number of active collection changes for optimiz-
ing TFO ........................................................................ 1063
C901120058 Number of samples with voice quality is excel-
lent ............................................................................. 1063
good............................................................................ 1063
medium ....................................................................... 1064
bad ............................................................................. 1064
C901120062 Number of samples with voice quality is aw-
fully............................................................................. 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 chan-
nels on SDCCH.............................................................. 1072
in radio channels on SDCCH ............................................ 1073
C901120084 Maximum received DL signal strength in radio

Chapter 18 Radio Measurement
C901120086 Total value of DL signal strength in radio chan-

nels 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 chan-
nels 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 chan-
nels on TCH .................................................................. 1081
C901120101 Number of samples with UL RQ = 0 on SD-
CCH............................................................................. 1081
CCH............................................................................. 1082
CCH............................................................................. 1083
CCH............................................................................. 1083
CCH............................................................................. 1084
CCH............................................................................. 1085
CCH............................................................................. 1085
CCH............................................................................. 1086
C901120109 Number of samples with DL RQ = 0 on SD-
CCH............................................................................. 1086
CCH............................................................................. 1087
CCH............................................................................. 1088
CCH............................................................................. 1088
CCH............................................................................. 1089
CCH............................................................................. 1090
CCH............................................................................. 1090


CCH............................................................................. 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
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 in-
quired in database when periodical measurement is reported.

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 measure-
ment 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 The counter increments when BSC receives UL measurement re-
Point port 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 mea-
surement 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 sig-
nal 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 The counter counts when BSC receives UL measurement report or
Point pre-processing measurement report.
Unit None


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.
Unit None
wireless channels
Definition Number of DL signal quality samples in radio channels
Description This counter counts the number of received DL radio measure-
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 The counter increments when BSC receives DL measurement re-
Unit Times

DL signal quality in wireless
channels
Definition 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 mea-
surement 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 sig-
nal 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 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.
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-pro-
cessing measurement report.
Usage This counter is used to find out frequency of received UL signal
strength samples in radio channels.


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 mea-
surement report received by BSC is higher than the recorded high-
est 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.
Unit None
C901120009 Minimum
Definition Minimum received UL signal strength in radio channels
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 mea-
surement 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
Unit 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 accu-
mulates values of UL signal strength in radio channels in UL mea-
surement 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.
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-pro-
cessing measurement report.
Usage This counter is used to find out frequency of received DL signal
strength samples in radio channels.
Unit Times
C901120012 Maximum
Definition Maximum received DL signal strength in radio channels

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 mea-
surement report received by BSC is higher than the recorded high-
est 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
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 mea-
surement 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
Unit None

of DL signal strength in
wireless channels
Definition 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 accu-
mulates values of DL signal strength in radio channels in DL mea-
surement 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.


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 re-
port.
Usage This counter is used to find out frequency of TA samples in radio
channels.
Measurement The counter increments when BSC receives measurement report
Point 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 re-
ports. 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 The counter counts when BSC receives measurement report or
Unit Second

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 ra-
dio measurement reports. The counter accumulates values of TA
in radio channels in measurement report or pre-processing mea-
surement report received by BSC.
Usage This counter is used to find out status of total value of TA in radio
channels.
Measurement 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 inter-
ference band 0.
Usage This counter is used to find out number of idle TCH/Fs with inter-
ference band 0.
Measurement The counter increments when timed database inquiry is carried
Point out.
Unit Times

of idle TCH/Hs with
interference band 0
Definition Mean number of idle TCH/Hs with interference band 0.
Description This counter counts the mean number of idle TCH/Hs with inter-
ference band 0.

Usage This counter is used to find out number of idle TCH/Hs with inter-
ference band 0.
Point out.
Unit 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 inter-
ference band 0.
Usage This counter is used to find out number of idle SDCCHs with inter-
ference band 0.
Point out.
Unit Times
Related Features ZGO-03-02-001 Idle Channel Measurement

of idle SDCCHs with
interference band 1
ference band 1.
ference band 1.
Point out.
Unit Times


of idle SDCCHs with
interference band 2
ference band 2.
ference band 2.
Point out.
Unit Times

of idle SDCCHs with
interference band 3
ference band 3.
ference band 3.
Point out.
Unit Times

of idle SDCCHs with
interference band 4
Definition Mean number of idle SDCCHs with interference band 4.
ference band 4.

ference band 4.
Point out.
Unit Times

of idle SDCCHs with
interference band 5
ference band 5.
ference band 5.
Point out.
Unit Times
TFO initiations
Definition Number of TFO initiations
Description This counter counts the number of TFOs established by BSC.
Measurement When the RANCS service process of BSC receives TFO status mes-
Point sage and TFO has been established, the counter increments.
Unit Times
Related Features ZGO-04-02-006 TFO
using noise suppression
Definition Number of using noise suppression

Description This counter does not count for the time being.
C901120054 Number
of mode changes for
establishing TFO
Definition Number of mode changes for establishing TFO
mode changes for optimizing
TFO
Definition Number of mode changes for optimizing TFO
active collection changes for
establishing TFO
Definition Number of active collection changes for establishing TFO

active collection changes for
optimizing TFO
Definition Number of active collection changes for optimizing 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 re-
ceived, 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 When BSCreceives the UL measurement report, preprocessing
Point 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.
channel.

Measurement When BSC receives the UL measurement report, preprocessing

report, if the voice quality is good, the counter increments.
Unit 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 re-
ceived, if the voice quality is medium, the counter increments.
channel.
report, if the voice quality is medium, the counter increments.
Unit Times
bad
Definition Number of samples with voice quality is bad
Description This counter counts the number of voice quality being bad. When
voice quality is bad, the counter increments.
channel.
report, if the voice quality is bad, the counter increments.
Unit 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.
channel.
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 The counter's value is obtained from the periodic measurement
Point report.
C901120064 Total Number

of uplink frame on FR_V1
Description This counter counts the number of uplink frames of full-rate ver-
sion 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.
Point report.

version 2.
Point report.

Description This counter counts the number of uplink voice frames of full-rate
version 2.
Point report.
version 3.
Point report.


Description This counter counts the number of uplink voice frames of full-rate
version 3.
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.
Point report.

of uplink frame on HR_V1
Description This counter counts the number of uplink voice frames of half-rate
version 1.
of half-rate version 1. The counter increments every 20 ms.
Point report.
Description This counter counts the number of uplink error frames of half-rate
version 3.

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.
Point report.

Description This counter counts the number of uplink voice frames of half-rate
version 3.
of half-rate version 3. The counter increments every 20 ms.
Point report.
radio channels on SDCCH
Definition Number of UL signal quality samples in radio channels on SDCCH
samples in radio channels on SDCCH.
Unit Times

UL signal quality in radio
channels on SDCCH
Definition Level of worst UL signal quality in radio channels on SDCCH

recorded.
signal quality in radio channels on SDCCH.
Unit None

Definition Total value of UL quality level values in radio channels on SDCCH
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 measure-
ment report received by BSC.
level values in radio channels on SDCCH.
Unit None
Definition Number of DL signal quality samples in radio channels on SDCCH
samples in radio channels on SDCCH.


Unit Times

DL signal quality in radio
channels on SDCCH
Definition Level of worst DL signal quality in radio channels on SDCCH
recorded.
signal quality in radio channels on SDCCH.
Unit None

Definition Total value of DL quality level values in radio channels on SDCCH
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 measure-
level values in radio channels on SDCCH.
Unit None

samples in radio channels
on SDCCH
on SDCCH
samples in radio channels on SDCCH in UL measurement report.
The counter increments when BSC receives UL measurement re-
port or pre-processing measurement report.
strength samples in radio channels on SDCCH.
Unit Times
C901120080 Maximum
in radio channels on SDCCH
Definition Maximum received UL signal strength in radio channels on SDCCH
radio channels on SDCCH 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.
signal strength in radio channels on SDCCH.
Unit None

C901120081 Minimum
Definition Minimum received UL signal strength in radio channels on SDCCH
radio channels on SDCCH 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.
Unit None

UL signal strength in radio
channels on SDCCH
Definition Total value of UL signal strength in radio channels on SDCCH
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 measure-
strength in radio channels on SDCCH.
Unit None

on SDCCH
on SDCCH
samples in radio channels on SDCCH in DL measurement report.
The counter increments when BSC receives DL measurement re-
port or pre-processing measurement report.
strength samples in radio channels on SDCCH.
Unit Times
C901120084 Maximum
Definition Maximum received DL signal strength in radio channels on SDCCH
radio channels on SDCCH 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.
Unit None

Definition Minimum DL received signal strength in radio channels on SDCCH
radio channels on SDCCH 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
Unit None

DL signal strength in radio
channels on SDCCH
Definition Total value of DL signal strength in radio channels on SDCCH
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 measure-
strength in radio channels on SDCCH.
Unit None

radio channels on TCH
Definition Number of UL signal quality samples in radio channels on TCH
samples in radio channels on TCH.
Unit Times

UL signal quality in radio
channels on TCH
Definition Level of worst UL signal quality in radio channels on TCH
recorded.
signal quality in radio channels on TCH.
Unit None


Definition Total value of UL quality level values in radio channels on TCH
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.
level values in radio channels on TCH.
Unit None
Definition Number of DL signal quality samples in radio channels on TCH
samples in radio channels on TCH.
Unit Times

DL signal quality in radio
channels on TCH
Definition Level of worst DL signal quality in radio channels on TCH

recorded.
signal quality in radio channels on TCH.
Unit None

Definition Total value of DL quality level values in radio channels on TCH
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.
level values in radio channels on TCH.
Unit None
on TCH
on TCH
samples in radio channels on TCH in UL measurement report. The
counter increments when BSC receives UL measurement report or


strength samples in radio channels on TCH.
Unit Times
C901120094 Maximum
in radio channels on TCH
Definition Maximum received UL signal strength in radio channels on TCH
radio channels on TCH in UL measurement report. If the UL signal
strength in radio channel in UL measurement report or pre-pro-
cessing measurement report received by BSC is higher than the
recorded highest UL signal strength, then the new highest UL sig-
nal strength will be recorded.
signal strength in radio channels on TCH.
Unit None
C901120095 Minimum
Definition Minimum received UL signal strength in radio channels on TCH
radio channels on TCH in UL measurement report. If the UL signal
strength in radio channel in UL measurement report or pre-pro-
cessing measurement report received by BSC is lower than the
recorded lowest UL signal strength, then the new lowest UL signal
Unit 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.
strength in radio channels on TCH.
Unit None
on TCH
on TCH
samples in radio channels on TCH in DL measurement report. The
counter increments when BSC receives DL measurement report or
strength samples in radio channels on TCH.
Unit Times

C901120098 Maximum
Definition Maximum received DL signal strength in radio channels on TCH
radio channels on TCH in DL measurement report. If the DL signal
strength in radio channel in DL measurement report or pre-pro-
cessing measurement report received by BSC is higher than the
recorded highest DL signal strength, then the new highest DL sig-
nal strength will be recorded.
Unit None
Definition Minimum DL received signal strength in radio channels on TCH
radio channels on TCH in DL measurement report. If the DL signal
strength in radio channel in DL measurement report or pre-pro-
cessing measurement report received by BSC is lower than the
recorded lowest DL signal strength, then the new lowest DL signal
Unit 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.
strength in radio channels on TCH.
Unit None
samples with UL RQ = 0 on
SDCCH
Definition Number of samples with UL RQ = 0 on SDCCH
Description BTS measures the level, quality, and interference of UL signal re-
ceived in channel, and reports it to BSC, in combination with mea-
surement 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 BSC receives the measurement report submitted by BTS, if UL
Point RQ=0 in measurement report, this counter increments. The mea-

FIGURE 1082 - BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED

BY BTS
Unit Times
SDCCH
Description This measurement value is the sample number with UL RQ=1 in
measurement report.

BY BTS
Unit Times

SDCCH
measurement report.

BY BTS
Unit Times
SDCCH
measurement report.


BY BTS
Unit Times
SDCCH
measurement report.

BY BTS
Unit Times

SDCCH
measurement report.

BY BTS
Unit Times
SDCCH
measurement report.


BY BTS
Unit Times
SDCCH
measurement report.
FIGURE 1089 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY

BTS
Unit Times
samples with DL RQ = 0 on
SDCCH
Definition 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 BSC receives the measurement report submitted by BTS, if DL

BY BTS
Unit Times
SDCCH
measurement report.

BY BTS
Unit Times

SDCCH
measurement report.

BY BTS
Unit Times
SDCCH
measurement report.


BY BTS
Unit Times
SDCCH
measurement report.

BY BTS
Unit Times

SDCCH
measurement report.

BY BTS
Unit Times
SDCCH
measurement report.


BY BTS
Unit Times
SDCCH
measurement report.
Measurement BSC receives the measurement report submitted by BTS, if DL RQ
Point = 7 in measurement report, this counter increments. The mea-

BY BTS
Unit Times

TCH
Definition Number of samples with UL RQ = 0 on TCH
per 480 ms.
This measurement value is the sample number with UL RQ=0 in
measurement report.

BY BTS
Unit Times
TCH
measurement report.


BY BTS
Unit Times
TCH
measurement report.

BY BTS
Unit Times

TCH
measurement report.

BY BTS
Unit Times
TCH
measurement report.


BY BTS
Unit Times
TCH
measurement report.

BY BTS
Unit Times

TCH
measurement report.

BY BTS
Unit Times
TCH
measurement report.

BTS

Unit Times
TCH
Definition Number of samples with DL RQ = 0 on TCH
measurement report.

BY BTS
Unit Times
TCH
measurement report.


BY BTS
Unit Times
TCH
measurement report.

BY BTS
Unit Times

TCH
measurement report.

BY BTS
Unit Times
TCH
measurement report.


BY BTS
Unit Times
TCH
measurement report.

BY BTS
Unit Times

TCH
measurement report.

BY BTS
Unit Times
TCH
measurement report.
Measurement BSC receives the measurement report submitted by BTS, if DL RQ
Point = 7 on TCH in measurement report, this counter increments. The


BY BTS
Unit 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 at-
tempts of the second sub cell .......................................... 1116
C901130015 Number of outgoing inter-cell handover execu-
tion 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

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 sec-
ond 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 sec-
ond 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 sec-
ond sub cell (used for assignment) .................................. 1149
C901130052 Number of TCH/H seizure success of the second

Chapter 19 Sub Cell Statistics
C901130053 Number of TCH/H seizure failure of the second

C901130054 Number of TCH/H seizure attempts of the sec-
ond 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 sec-
ond sub cell .................................................................. 1156
C901130063 Number of TCH/F handover attempts of the sec-
ond sub cell .................................................................. 1157
C901130064 Number of TCH/F handover success of the sec-
ond 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 sec-
ond sub cell .................................................................. 1160
C901130068 Number of TCH/H handover success of the sec-
ond 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


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 han-
dover 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 Call database interface to count promptly.
Point
Unit Times
ZGO-05-02-009 Concentric Circle Technology

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.
Point
Unit 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.
sub cell.
Point
Unit Times

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
sub cell.
Point
Unit Times
handover attempts from the
first sub cell to the second
sub cell
Definition Number of handover attempts from the first sub cell to the second
sub cell
from the first sub cell to the second sub cell.
attempts from the first sub cell to the second sub cell, as one of
the parameters to measure radio environment.
Measurement When BSC receives measurement reports from MS, it makes han-
Point dover decision. If it is decided to do intra-cell handover, and cur-
rent 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 Times
Related Features 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
execution from the first sub cell to the second sub cell, as one of
Measurement During inter-sub-cell handover within a cell, this counter incre-
Point ments 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

FIGURE 1115 - INTRA-CELL INCOMING HANDOVER
Unit Times
handover success from the
sub cell
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
success from the first sub cell to the second sub cell, as one of the
parameters to measure radio environment.
Measurement During inter-sub-cell handover within a cell, target sub cell will re-
Point ceive handover completion message, indicating that MS success-
fully 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 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
from the second sub cell to the first sub cell.
attempts from the second sub cell to the first sub cell, as one of
rent 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

Unit Times
handover execution from the
sub cell
Definition Number of handover execution from the second sub cell to the first
sub cell
execution from the second sub cell to the first sub cell, as one of
� Current channel is in the second sub cell
� Source channel is in the first sub cell

Unit 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
ins success from the second sub cell to the first sub cell, as one of
� Target sub cell receives handover completion message
� Target channel is in the first sub cell
� Source channel is in the second sub cell

Unit Times
handover attempts in the
second sub cell
Definition Number of handover attempts in the second sub cell
within the second sub cell.
attempts within the second sub cell, as one of the parameters to
measure radio environment.
rent sub cell is the second sub cell, and if handover reason is in-
terference handover, this counter increments. The measurement
Unit Times

Related Features ZGO-05-02-009 Concentric Circle Technology
handover execution in the
second sub cell
Definition Number of handover execution in the second sub cell
execution within the second sub cell, as one of the parameters to
measure radio environment.
� Current channel is in the first sub cell
� Source channel is in the second sub cell
Unit Times

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 han-
dover from the second sub cell to the second sub cell, as one of
� Target sub cell receives handover completion message
� Target channel is in the second sub cell
� Source channel is in the first sub cells
Unit Times
outgoing inter-cell handover
attempts of the second sub
cell
Definition 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 han-
dover attempts originated from the second sub cell, as one of the
parameters to measure radio environment.
Point dover decision. If it is decided to do inter-cell handover, and source
cell is the second sub cell, this counter increments. The measure-
Unit 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 suc-
cessful handover originated from the second sub cell, as one of
Measurement During inter-sub-cell handover within a cell, source instance re-
Point ceives the handover completion message returned from target in-
stance, indicating the MS has accessed to target channel. If source
sub cell is the second sub cell, this counter increments. The mea-

FIGURE 1124 - INTER-CELL HANDOVER EXECUTION
Unit Times
success 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 suc-
cessful handover originated from the second sub cell, as one of
Measurement During inter-sub-cell handover within a cell, source instance re-
Point ceives the handover completion message returned from target in-
stance, indicating the MS has accessed to target channel. If source
sub cell is the second sub cell, this counter increments. The mea-

Usage 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 at-
tempts, 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 Make handover decision after BSC receives measurement reports.
Point 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 .

FIGURE 1126 - HANDOVER DECISION
Unit 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
too low DL receiving strength and originated from full rate channel
tempts, caused by DL receiving strength and originated from full
� Handover is caused by DL strength

Usage 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
too poor UL quality and originated from full rate channel in the
second sub cell.
tempts, caused by UL quality and originated from full rate channel
in the second sub cell, as one of the references for radio environ-
ment in the second sub cell.
� Handover is caused by UL quality
The measurement point is A, as shown inFigure 1128 .

Unit Times
C901130020 Handover
attempts due to DL quality of
Definition Handover attempts due to DL quality of the full rate second sub
cell
too poor DL quality and originated from full rate channel in the
second sub cell.
tempts, caused by DL quality and originated from full rate channel
� Handover is caused by DL quality
Unit 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
PBGT and originated from full rate channel in the second sub cell.
tempts, caused by PBGT and originated from full rate channel in
the second sub cell, as one of the references for radio environment
� Handover is caused by PBGT
Unit Times
C901130022 Handover
attempts due to traffic of the
full rate second sub cell
Definition Handover attempts due to traffic of the full rate second sub cell
traffic and originated from full rate channel in the second sub cell.

tempts, caused by traffic and originated from full rate channel in
� Handover is caused by traffic
� Current channel is full rate one, this counter increments
Units Times
Related Features ZGO-02-02-007 Traffic Based Handover
C901130023 Handover
attempts due to UL
interference of the full
rate second sub cell (on
TCH/F)
Definition Handover attempts due to UL interference of the full rate second
sub cell (on TCH/F)
UL interference and originated from full rate channel in the second
sub cell.
tempts, 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.
Unit 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)
DL interference and originated from full rate channel in the second
sub cell.
tempts, caused by DL interference and originated from full rate

� Handover is caused by DL interference
Unit 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)
too good C/I and originated from full rate channel in the second
sub cell.
tempts, caused by too good C/I and originated from full rate chan-
nel in the second sub cell, as one of the references for radio envi-
ronment in the second sub cell.
� Handover is caused by too good C/I

Unit 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)
too bad C/I and originated from full rate channel in the second sub
cell.
tempts, caused by too bad C/I and originated from full rate channel
� Handover is caused by too bad C/I

Unit 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)
too large path loss and TA and originated from full rate channel in
tempts, 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.
� Handover is caused by too large path loss and TA

Unit Times
ZGO-04-02-005 Co-BCCH
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)
too small path loss and TA and originated from full rate channel in
tempts, caused by too small path loss and TA and originated from
� Handover is caused by too small path loss and TA

Unit 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 sec-
ond sub cell (on TCH/F)
forced transfer handover and originated from full rate channel in
the second sub cell
tempts, caused by forced transfer handover and originated from
� Handover is caused by forced transfer

Unit 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 at-
tempts, caused by other causes and originated from full rate chan-
� Handover is caused by other reasons

Unit 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
too low UL receiving strength and originated from half rate channel
� Handover is caused by UL strength
� Current channel is half rate one

Unit 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
too low DL receiving strength and originated from half rate channel
tempts, caused by DL receiving strength and originated from half
� Handover is caused by DL strength

Unit 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
too poor UL quality and originated from half full rate channel in
tempts, caused by UL quality and originated from half rate channel
� Handover is caused by UL quality

Unit Times
C901130034 Handover
attempts due to DL quality of
Definition Handover attempts due to DL quality of the half rate second sub
cell
too poor DL quality and originated from half rate channel in the
second sub cell.
tempts, caused by DL quality and originated from full rate channel
� Handover is caused by DL quality
Unit Times

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
PBGT and originated from half rate channel in the second sub cell.
tempts, caused by PBGT and originated from half rate channel in
� Handover is caused by PBGT
Unit Times
C901130036 Handover
attempts due to traffic of the
Definition Handover attempts due to traffic of the half rate second sub cell
traffic and originated from half rate channel in the second sub cell.

tempts, caused by traffic and originated from half rate channel in
Unit Times
Related Features ZGO-02-02-007 Traffic Based Handover
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
UL interference and originated from half rate channel in the second
sub cell.
tempts, caused by UL interference and originated from half rate


� Handover is caused by UL interference
Unit Times
C901130038 Handover
attempts due to DL
interference of the half
Definition Handover attempts due to DL interference of the half rate second
sub cell (on TCH/F)
DL interference and originated from half rate channel in the second
sub cell.
tempts, caused by DL interference and originated from half rate
� Handover is caused by DL interference

Unit Times
C901130039 Handover
attempts due to C/I of the
Definition Handover attempts due to C/I of the half rate second sub cell
too good C/I and originated from half rate channel in the second
sub cell.
tempts, caused by too good C/I and originated from half rate chan-
� Handover is caused by too good C/I
The measurement point is A, as shown in Figure 1148

Unit Times
C901130040 Handover
attempts due to C/I of the
Definition Handover attempts due to C/I of the half rate second sub cell
too bad C/I and originated from half rate channel in the second
sub cell.
tempts, caused by too bad C/I and originated from half rate chan-
� Handover is caused by too bad C/I

Unit Times
C901130041 Handover
and too large TA of the half
Definition Handover attempts due to path loss and too large GSMBSS-TA of
too large path loss and TA and originated from half rate channel
tempts, caused by too large path loss and TA and originated from
half rate channel in the second sub cell, as one of the references
� Handover is caused by too large path loss and TA
Unit Times

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)
too small path loss and TA and originated from half rate channel
tempts, caused by too small path loss and TA and originated from
� Handover is caused by too small path loss and TA
Unit Times

forced transfer handover
attempts of the half rate
second sub cell
Definition Number of forced transfer handover attempts of the half rate sec-
ond sub cell (on TCH/F)
forced transfer handover and originated from half rate channel in
tempts, caused by forced transfer handover and originated from
� Handover is caused by forced transfer
Unit Times
Related Features ZGO-02-02-003 Directed-Shift Handover

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
other causes and originated from half rate channel in the second
sub cell.
tempts, caused by other causes and originated from half rate chan-
� Handover is caused by other reasons
Unit Times

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 chan-
nel 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 Measurement points of this counter include two types.
Point
� When successfully applying for channel, if channel type is
TCH/F, and application reason is assignment, this counter
increments. Successful application includes:
� Successful resource application
� Resource acquisition by queuing, seizure, or dynamic chan-
nel 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:
� Receive release command while waiting for resource state
� Failed to configure instance number while seizing channel
� Timeout while queuing or seizure, or waiting for resource
timer
� No available radio resource
Unit Times

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 This counter increments when following conditions are met:
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 con-
version.
Unit Times
TCH/F seizure failure of the
second sub cell (used for
assignment)
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 When channel application is failed, if channel type is TCH/F, and

Point application reason is assignment, this counter increments. Failure
reasons of application channel include:
� Timeout while queuing or seizure, or waiting for resource timer
Unit 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 chan-
nel in the second sub cell.
Measurement Measurement points of this counter include two types.
Point
� When channel is successfully applied, if channel type is TCH/F,
and application reason is handover, this counter increments.
Successful application includes: successful resource applica-
tion; 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;
timer;
� No available radio resource.
Unit Times

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
Measurement This counter increments when following conditions are met:
Point
� Channel is successfully applied
� Channel type is TCH/F
� Application reason is handover
version.
Unit Times
TCH/F seizure failure of the
handover)
Definition Number of TCH/F seizure failure of the second sub cell (used for
handover)

TCH/F channel in the second sub cell, as one of the references for
Measurement When channel application is failed, if channel type is TCH/F, and
Point application reason is handover, this counter increments. Failure
version.
Unit 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
in TCH/H channel in the second sub cell, as one of the references
Measurement Measurement points of this counter include two types:
Point
� When channel is successfully applied, if channel type is TCH/H,
channel conversion.
� When channel application is failed, if channel type is TCH/H,


timer
Unit 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
Measurement When successfully applying for channel, if channel type is TCH/H,
Point and application reason is assignment, this counter increments.
version.
Unit Times

TCH/H seizure failure of the
assignment)
Definition Number of TCH/H seizure failure of the second sub cell (used for
assignment)
TCH/H channel in the second sub cell, as one of the references for
Measurement When channel application is failed, if channel type is TCH/H, and
Point application reason is assignment, this counter increments. Failure
Unit 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

Measurement Measurement points of this counter include two types:

Point
� When channel is successfully applied, if channel type is TCH/H,
channel conversion.
� When channel application is failed, if channel type is TCH/H,
timer
Unit 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
Measurement When channel is successfully applied, if channel type is TCH/H, and
Point application reason is handover, this counter increments. Success-
ful application includes: successful resource application; resource
acquisition by queuing, seizure, or dynamic channel conversion.
Unit Times

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
TCH/H channel in the second sub cell, as one of the references for
Measurement When channel application is failed, if channel type is TCH/H and
Point application reason is handover, this counter increments. Failure
Unit Times
TCH/F call drops in the
second sub cell
Definition Number of TCH/F call drops in the second sub cell
Description This counter counts the number of call drops in TCH/F channel in

Usage This counter is used to find out the frequency of call drops in TCH/F
Measurement During call drops, if current channel is TCH/F, this counter incre-
Point ments. Call drops include following cases:
� 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
Unit 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 During call drops, if current channel is TCH/H, this counter incre-
Point ments. Call drops include following cases:
� 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
Unit Times


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 sec-
ond 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 This counter will count at following two cases:
Point
� 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.
Unit 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 sec-
ond 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 This counter will count at following two cases:
Point
� 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.
Unit Times

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 be-
ing 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 con-
dition of the second sub cell.
This counter is supported in version V6.20.200f or above.
Measurement 1. When BSC receives the release command in the WaitAccess
Point 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 This counter counts the number of successful TCH/F assignments


ing 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 1. When BSC receives the Um interface assignment completion
Point 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
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 re-
ceives the release command, the Um interface assignment com-
pletion 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 in-
tra-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 condi-
tion of the second sub cell.
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, inter-
cell 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,

inter-cell handover, external incoming handover, or internal di-

rected 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 com-
pletion 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 han-
dover, 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 condi-
channel is full-rate channel, and the channel request is due
Unit Times

TCH/H assignment attempts
Description This counter counts the number of attempts of TCH/H assignment
ing 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 con-
dition of the second sub cell.
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 assign-
ment, then the counter counts.
Unit Times
Description This counter counts the number of successful TCH/H assignments
ing 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 successful TCH/H
assignments for the second sub cell. It helps study the access
condition of the second sub cell.
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 re-
ceives the release command, the Um interface assignment com-
pletion 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 in-
tra-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 condi-
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, inter-
cell handover, external incoming handover, or internal directed
retry, then the counter counts.
channel is half-rate channel, and the channel request is due

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 com-
pletion 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 condi-
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 as-
signment). When BSC requests radio resource from DBS, if the

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 chan-
nel, 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 In the RadioApply status, when BSC requests radio resource from
Point DBS, if the request succeeds and the following conditions are satis-
fied, 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.
Unit 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 chan-
nel, 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.
cell being preferred, the sub cell ID is 1, the channel is full-rate
channel, and the channel request is due to handover.
Unit 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 as-
signment). When BSC requests radio resource from DBS, if the
being preferred, the sub cell ID is 1, the channel is half-rate chan-
nel, 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.
cell being preferred, the sub cell ID is 1, the channel is half-rate
channel, and the channel request is due to assignment.
Unit 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 chan-
nel, 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.

cell being preferred, the sub cell ID is 1, the channel is half-rate
channel, and the channel request is due to handover.
Unit 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 This counter is incremented when channel assignment in subcell 2
Point of the cell is determined.
Unit Times
C901130074 Number
Execution to the Second
Sub Cell Directly From the
Cell in the Same Site
Description This counter counts the times that an inter-cell handover is per-
formed 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 han-
dover is performed to hand over an MS to subcell 2 of the cell from
another cell in the same site.

Measurement This counter is incremented when the assigned channel in subcell

Point 2 of the cell is activated.
Unit 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 han-
dovers from a cell in the same site to subcell 2 of the cell.
Measurement This counter is incremented when a HANDOVER COMPLETE mes-
Point sage 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
hand over an MS to subcell 2 of the cell from a cell in another site
controlled by the same BSC.
that occur to hand over an MS to subcell 2 of the cell from a cell
in another site controlled by the same BSC.
Unit Times

C901130077 Number
Execution to the Second
Sub Cell Directly From
Another Site
formed 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.
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.
dovers that hand over an MS to subcell 2 of the cell from a cell
in another site controlled by the same BSC.
cell.
Unit Times

Handover Attempts to the
Second Sub Cell Directly
From Another BSC
hand over an MS to subcell 2 of the cell from a cell controlled by
another BSC.
that occur to hand over an MS to subcell 2 of the cell from a cell
controlled by another BSC.
Unit Times
Handover Execution to the
From Another BSC
formed 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.
Unit Times

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.
dovers that hand over an MS to subcell 2 of the cell from a cell
controlled by another BSC.
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 This counter is incremented when an inter-subcell handover is de-
Point cided.
Unit Times

Handover to the Second
Sub Cell Too Fast After
Handover From Another Cell
in the Same Site
cell from another cell in the same site.
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.
Point cided.
Unit Times
Handover to the First Sub
From Another Site
cell from a cell in another site.
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.
Point cided.
Unit Times

Handover to the Second Sub
From Another Site
cell from a cell in another site.
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.
Point cided.
Unit 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 measure-
ment 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.

TA=0
Description This counter counts the number of times of TA=0 in the MS mea-
surement 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 This counter increments when BSC receives the MS measurement
Point 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 Number of 0<TA<= 2
Description 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.
Point report with 0<TA<=2. The measurement point is A, as shown in
Figure 1155.

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.
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
Figure 1157.

Unit Times
6<TA<=8
Figure 1158.
Unit Times
8<TA<=10

Figure 1159.
Unit Times
10<TA<=12
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.
in Figure 1160.
Unit Times

12<TA<=14
in Figure 1161.
Unit Times
14<TA<=16
in Figure 1162.
Unit Times

16<TA<=18
in Figure 1163.
Unit Times
18<TA<=20
in Figure 1164.

Unit Times
20<TA<=22
in Figure 1165.
Unit Times
22<TA<=24


in Figure 1166.
Unit Times
24<TA<=26
in Figure 1167.
Unit Times

26<TA<=28
in Figure 1168.
Unit Times
28<TA<=30
in Figure 1169.

Unit Times
30<TA<=32
in Figure 1170.
Unit Times
32<TA<=34


in Figure 1171.
Unit Times
34<TA<=36
in Figure 1172.
Unit Times

36<TA<=38
in Figure 1173.
Unit Times
38<TA<=40
Definition Number of 38<TA<=40
in Figure 1174.

Unit Times
40<TA<=42
in Figure 1175.
Unit Times
42<TA<=44


in Figure 1176.
Unit Times
C901140024 Number
44<TA<=46
in Figure 1177.
Unit Times

46<TA<=48
in Figure 1178.
Unit Times
48<TA<=50
in Figure 1179.

Unit Times
50<TA<=52
in Figure 1180.
Unit Times
52<TA<=54


in Figure 1181.
Unit Times
54<TA<=56
in Figure 1182.
Unit Times

56<TA<=58
in Figure 1183.
Unit Times
58<TA<=60
Definition Number of 58<TA<=60
in Figure 1184.

Unit Times
60<TA<=63
in Figure 1185.
Unit Times
TA>63
Definition Number of TA > 63
Description This counter counts the number of times of TA>63 in the MS mea-
surement 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.
Point report with TA>63. The measurement point is A, as shown in
Figure 1186.
Unit Times


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

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 Number of SAPI3 link establishments on SACCH/F (MO-SM)
ment of mobile originating call through SACCH/F. On SDCCH/F,
BSC receives EST_IND message sent by BTS. If the layer 3 infor-
mation in this message is SAPI=3, the counter increments.
Usage This counter is used to find out the frequency of SAPI3 link estab-
lishments on SACCH/F.
Measurement This counter counts the number of BSC receiving EST_IND message
Point sent by BTS with SAPI=3. The measurement point is A, as shown
inFigure 1187.

Chapter 21 SAPI3 Measurement
FIGURE 1187 - FLOW OF MO SHORT MESSAGES DURING CONVERSATION
Unit Times
on SACCH/H (MO-SM)
Definition Number of SAPI3 link establishments on SACCH/H (MO-SM)
ment of mobile originating call through SACCH/H. On SDCCH/H,
BSC receives EST_IND message sent by BTS. If the layer 3 informa-
tion in this message is SAPI=3, the counter increments.
lishments on SACCH/H.
Measurement This counter counts the number of BSC receiving EST_IND mes-
Point sage sent by BTS with SAPI=3. The measurement point is A1, as

Unit Times
on FACCH/F (MO-SM)
Definition Number of SAPI3 link establishments on FACCH/F (MO-SM)
ment 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.
lishments on FACCH/F.
Measurement This counter is not realized at present in the system.
Point
Unit Times

on FACCH/H (MO-SM)
Definition Number of SAPI3 link establishments on FACCH/H (MO-SM)
ment of mobile originating call through FACCH/H. On FACCH/H,
BSC receives EST_IND message sent by BTS. If the layer 3 informa-
tion in this message is SAPI=3, the counter increments.
lishments on FACCH/H.
Point
Unit Times
requests on SACCH/F
(MT-SM)
Definition Number of SAPI3 link establishments on SACCH/F (MT-SM)
ment 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.
lishment requests on SACCH/F.
Measurement This counter counts the number of BSC sending EST_REQ message
Point 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.

FIGURE 1189 - FLOW OF MT SHORT MESSAGE DURING CONVERSATION
Unit Times
requests on SACCH/H
(MT-SM)
Definition Number of SAPI3 link establishments on SACCH/H (MT-SM)
ment of mobile originating call through SACCH/H. On SACCH/H, if
lishment requests on SACCH/H.
Measurement This counter counts the number of BSC sending EST_REQ message
Point 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.

Unit Times
requests on FACCH/F
(MT-SM)
Definition Number of SAPI3 link establishments on FACCH/F (MT-SM)
ment 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.
lishments on FACCH/F.
Point
Unit Times

requests on FACCH/H
(MT-SM)
Definition Number of SAPI3 link establishments on FACCH/H (MT-SM)
ment of mobile terminating call through FACCH/H. On FACCH/H,
lishments on FACCH/H.
Point
Unit Times
successful SAPI3 link
establishments on SACCH/F
(MT-SM)
Definition Number of successful SAPI3 link establishments on SACCH/F (MT-
SM)
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 This counter counts the number of BSC receiving EST_IND message
Point send by BTS with SAPI=3. The measurement point is C2, as shown
in Figure 1191.

Unit Times
establishments on SACCH/H
(MT-SM)
Definition Number of SAPI3 link establishments on SACCH/H (MT-SM)
ment 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.
lishment requests on SACCH/H.
Measurement This counter counts the number of BSC sending EST_CONF message
Point 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 .

Unit Times
establishments on FACCH/F
(MT-SM)
Definition Number of successful SAPI3 link establishments on FACCH/F (MT-
SM)
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 estab-
lishment succeeds, and the counter increments.
lishment requests on SACCH/F.
Point
Unit Times

establishments on FACCH/H
(MT-SM)
Definition Number of successful SAPI3 link establishments on FACCH/H (MT-
SM)
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 establish-
ment succeeds, and the counter increments.
Usage This counter is used to find out the frequency of successful SAPI3
link establishments on FACCH/H.
Point
Unit 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 This counter counts the number of BSC receiving DTAP packet sent
Point 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 .

FIGURE 1193 - FLOW OF MT SHORT MESSAGE IN IDLE STATUS

FIGURE 1194 - FLOW OF MO SHORT MESSAGE IN IDLE STATUS
Unit 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 .
point-to-point message on SDCCH DL.

Measurement This counter counts the number of BSC receiving DTAP packet
Point 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 OF MT SHORT MESSAGE IN IDLE STATUS

FIGURE 1196 - FLOW OF MO SHORT MESSAGE IN IDLE STATUS
Unit 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.

point-to-point short messages on FACCH/F UL.
Point
Unit 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.
point-to-point short messages on FACCH/F UL.
Point
Unit Times
C901150020 Number
of DTAP messages
on FACCH/H UL for
messages
Definition Number of DTAP messages on FACCH/H UL for point-to-point short
messages.
sent by MS to network side through FACCH/H.

point-to-point short messages on FACCH/H UL.
Point
Unit 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.
sent by network side to MS through FACCH/H.
point-to-point short messages on FACCH/H DL.
Point
Unit 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.
sent by network side to MS through SACCH/F.

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.
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 .

Unit 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.
sent by network side to MS through SACCH/F.
point-to-point short messages on SACCH/F DL.


Point
Unit Times
C901150024 Number
of DTAP messages
on SACCH/H UL for
messages
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.
point-to-point short messages on SACCH/H UL.
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.


Unit 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.
sent by network side to MS through SACCH/H.
point-to-point short messages on SACCH/H DL.
Measurement This counter counts the number of BSC sending DTAP packet to
Point 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.

Unit Times


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 mes-
sage ............................................................................ 1219
C901160003 Number of Packet UL Assignment mes-
sage ............................................................................ 1219
C901160004 Number of Additional MS access capabilities
message ...................................................................... 1220
C901160005 Number of Packet DL Assignment mes-
sage ............................................................................ 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 mes-
sage ............................................................................ 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 mes-
sage ............................................................................ 1227
C901160012 Number of Packet Cell Change Failure mes-
sage ............................................................................ 1229
C901160013 Number of Packet Cell Change Notification mes-
sage ............................................................................ 1229
C901160014 Number of Packet Cell Change Order mes-
sage ............................................................................ 1230
C901160017 Number of packet mobile TBF status mes-
sages........................................................................... 1231
C901160018 Number of packet neighbor cell data mes-
sages........................................................................... 1232
C901160019 Number of packet PDCH release mes-
sages........................................................................... 1233
C901160020 Number of packet polling request mes-
sages........................................................................... 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 mes-
sages........................................................................... 1236
C901160024 Number of packet SI status messages ........... 1237
C901160025 Number of packet timeslot reconfigure mes-
sages........................................................................... 1238
C901160026 Number of packet paging request mes-
sage ............................................................................ 1239

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 mes-
sages on PACCH, including packet access reject, packet resource
request, packet UL assignment, and so on.
C901160001 Number
of Packet access reject
message
Definition Number of Packet access reject message
Description 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 When the UPPB of BSC sends packet access reject messages to
Point MS, the counter increments. The measurement point is A2, as
FIGURE 1203 - MEASUREMENT POINT OF PACKET RESOURCE REQUEST AND

PACKET ACCESS REJECT
Unit Times

Chapter 22 Uplink and Downlink PACCH Statistics
Packet resource request
message
Definition Number of Packet access reject message
Description 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.
Measurement When the UPPB of BSC receives packet resource request mes-
Point sages, the counter increments. The measurement point is A1, as
FIGURE 1204 - MEASUREMENT POINT OF PACKET RESOURCE REQUEST AND

PACKET ACCESS REJECT
Unit Times
Packet UL Assignment
message
Definition Number of Packet UL Assignment message
Description Packet UL assignment can be sent on both PCCCH and PACCH.
When established for TBF double steps, the first packet UL assign-
ment 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.

This counter counts the number of packet UL assignment mes-

sages sent by BSC on PACCH.
Measurement When the type of DL control block sent by BSC is packet UL as-
Point signment, the counter increments. The measurement point is A,
FIGURE 1205 - MEASUREMENT OF PACKET UL ASSIGNMENT MESSAGE
Unit Times
Additional MS access
capabilities message
Definition Number of Additional MS access capabilities messages.
Description This counter counts the number of additional MS access capabili-
ties messages received by BSC on PACCH in packet transmission
mode.
Measurement When the type of UL control block received by BSC is additional
Point 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 mes-
sages sent by BSC on PACCH in packet transmission mode.
Measurement When the type of DL control block sent by BSC is packet DL as-
Point signment, the counter increments. The measurement point is A,
as shown inFigure 1207 .

FIGURE 1207 - DL SENT ON PACCH IN PACKET TRANSMISSION MODE
Unit Times
C901160006 Number
of Packet TBF release
message
Definition Number of packet TBF release messages
Description This counter counts the number of packet TBF release messages
on PACCH sent by BSC.
Measurement When the type of DL control block sent by BSC is packet TBF re-
Point lease, the counter increments. The measurement point is A, as
shown inFigure 1208.

Unit Times
C901160007 Number
of Packet DL Ack/Nack
message
Definition Number of packet DL Ack/Nack messages.
Description 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 When the type of UL control block sent by BSC is packet DL
Point Ack/Nack, the counter increments. The measurement points are
A, A1, as shown inFigure 1209 .

Unit Times
EGPRS Packet DL Ack/Nack
message
Definition Number of EGPRS Packet DL Ack/Nack messages.
Description 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 transmis-
sion mode.
Measurement When the type of UL control block sent by BSC is EGPRS packet DL
Point Ack/Nack, the counter increments. The measurement points are
A and A1, as shown inFigure 1210.

Unit 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 When the type of DL control block sent by BSC is packet UL
Point Ack/Nack, the counter increments. The measurement point is A,

FIGURE 1211 - SIGNALING TRANSMISSION ON PACCH
Unit Times
C901160010 Number
of Packet Control
Acknowledgement message
Definition Number of Packet Control Acknowledgement message
Description This counter counts the number of packet control acknowledge-
ment messages received by BSC on PACCH in packet transmission
mode.
Measurement When the type of UL control block received by BSC is packet con-
Point trol acknowledgement, the counter increments. The measurement
point is B, as shown inFigure 1212.

FIGURE 1212 - SIGNALING TRANSMISSION ON PACCH
Unit Times
C901160011 Number
of Packet Cell Change
Continue message
Definition Number of Packet Cell Change Continue message
Description If MS intends to handoff from service cell to destination cell, it will
initiate packet cell change notification to BSC to request the sys-
tem 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 BSC initiates timer after receiving PACKET NEIGHBOR CELL CHANGE NOTI-
Point FICATION. If 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.

FIGURE 1213 - MEASUREMENT POINT OF PACKET-CELL-CHANGE-RELATED

COUNTER (I)
BSC initiates timer after receiving the PACKET NEIGHBOR CELL CHANGE
NOTIFICATION message. If timer times out and doesn’t 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 Times

Packet Cell Change Failure
message
Definition Number of Packet Cell Change Failure message
Description 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 mes-
sages received by BSC on PACCH in packet transmission mode.
Measurement When the type of UL control block sent by BSC is packet cell change
Point failure, the counter increments. The measurement point is A3, as
FIGURE 1215 - MEASUREMENT POINT OF PACKET CELL CHANGE ORDER

AND PACKET CELL CHANGE FAILURE
Unit Times
C901160013 Number
of Packet Cell Change
Notification message
Definition Number of Packet Cell Change Notification messages.

Description If MS intends to handoff from service cell to destination cell, it will

initiate packet cell change notification to BSC to request the sys-
tem 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 When the type of UL control block received by BSC is packet cell
Point change notification, the counter increments. The measurement
point is A1, as shown inFigure 1216.

COUNTER (I)
Unit Times
Packet Cell Change Order
message
Definition 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 When BSC sends packet cell change order messages, the counter
Point increments. The measurement point is A2, as shown inFigure
1217.

FIGURE 1217 - MEASUREMENT POINT OF PACKET CELL CHANGE ORDER

AND PACKET CELL CHANGE FAILURE
Unit 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 mes-
sages sent by BSC on PACCH in packet service.
Measurement When the type of UL control block received by BSC is packet mo-
Point bile TBF, the counter increments. The measurement point is A, as

FIGURE 1218 - MEASUREMENT POINT OF PACKET MOBILE STATUS MESSAGE

ON PACCH
Unit Times
packet neighbor cell data
messages
Definition Number of packet neighbor cell data messages.
Description 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 When the type of DL control block sent by BSC is packet neighbor-
Point ing cell data, the counter increments. The measurement point is
A2, as shown inFigure 1219.


COUNTER
Unit 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 When the type of DL control block sent by BSC is packet PDCH
Point release, the counter increments.
Unit Times
packet polling request
messages
Definition Number of packet polling request messages.

Description This counter counts the number of packet polling request mes-
sages sent by BSC on PACCH in packet transmission mode.
Measurement When the type of DL control block sent by BSC is packet polling re-
Point quest, counter increments. The measurement point is A, as shown
inFigure 1220 .
FIGURE 1220 - MEASUREMENT POINT OF DL TBF ESTABLISHES EXECUTION

POLLING
Unit Times
packet power control/timing
advance messages
Definition 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 When the type of DL control block sent by BSC is packet power
Point control/timing advance message, counter increments. The mea-

FIGURE 1221 - MEASUREMENT POINT OF PACKET POWER CONTROL/TIMING

ADVANCE MESSAGE SENT ON PACCH
Unit Times
packet PSI status message
Definition Number of packet PSI status messages.
Description 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 When the type of UL control block sent by BSC is packet PSI Status
Point message, counter increments. The measurement point is A1, as

FIGURE 1222 - MEASUREMENT POINT OF PACKET-SERVICE-CELL-DATA-

RELATED COUNTER
Unit Times
packet serving cell data
messages
Definition Number of packet serving cell data messages.
Description Network uses packet serving cell data to send the system mes-
sages 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 When the type of DL control block sent by BSC is packet serving
Point cell data messages, the counter increments. The measurement
point is A2, as shown inFigure 1223 .


RELATED COUNTER
Unit Times
packet SI status messages
Definition Number of packet SI status messages.
Description 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 re-
ceived by BSC on PACCH.
Measurement When the type of UL control block sent by BSC is packet SI status
Point message, counter increments. The measurement point is A1, as


RELATED COUNTER
Unit Times
packet timeslot reconfigure
messages
Definition Number of packet timeslot reconfigure messages.
Description 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 When the type of DL control block sent by BSC is packet times-
Point lot reconfigure messages, counter increments. The measurement
point is A, as shown inFigure 1225 andFigure 1226 .

FIGURE 1225 - FLOW OF ESTABLISHING UL ON PACCH UNDER DL

TRANSMISSION STATUS
FIGURE 1226 - FLOW OF ESTABLISHING DL ON PACCH UNDER UL

TRANSMISSION STATUS
Unit Times
packet paging request
message
Definition Number of packet paging request message.

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 mes-
sages sent by BSC on PACCH.
Measurement When the type of DL control block sent by BSC to MS through BTS
Point is packet paging request messages, the counter increments. The
FIGURE 1227 - MEASUREMENT POINT OF BSC ISSUING PACKET PAGING

REQUEST MESSAGE
Unit Times
C901160027 Number of PSI

message
Definition Number of packet PSI message.
Description This counter counts the number of PSI messages sent by BSC on
PACCH in packet service.
Measurement When the type of DL control block sent by BSC to MS through BTS
Point is packet system message, the counter increments. The measure-

FIGURE 1228 - MEASUREMENT POINT OF BSC ISSUING PACKET SYSTEM

MESSAGE
Unit Times


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 es-
tablishment .................................................................. 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 estab-
lishment 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 realloca-
tion failure due to Abis congestion for UL TBF establish-
ment ........................................................................... 1258
failure due to RR congestion for UL TBF establishment......... 1259


failure due to UPPB-DSP channel congestion for UL TBF es-
tablishment .................................................................. 1260
success of channel allocation due to UL TBF establish-
ment ........................................................................... 1261
C901170027 Number of allocated PDCH for GPRS DL TBF re-
source reallocation due to UL TBF establishment ................ 1262
failure due to channel activate failure for UL TBF establish-
ment ........................................................................... 1263
failure due to BTS connection failure for UL TBF establish-
ment ........................................................................... 1264
failure due to BIU connection failure for UL TBF establish-
ment ........................................................................... 1265
success of channel activate and connection for UL TBF estab-
lishment....................................................................... 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 trans-
mission ........................................................................ 1270
success of channel allocation due to LLC transmission......... 1271
C901170040 Number of allocated PDCH for GPRS DL TBF re-
source reallocation due to LLC transmission ...................... 1272
failure due to channel activate failure for LLC transmis-
sion ............................................................................. 1273
failure due to BTS connection failure for LLC transmis-
sion ............................................................................. 1274
failure due to BIU connection failure for LLC transmis-
sion ............................................................................. 1275
success of channel activate and connection for LLC transmis-
sion ............................................................................. 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

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 re-
ceived 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 When RANPS module receives the DL request (EV_RANUMC_DLASS_REQ)
Point sent from RANUMC module, the counter increments. The mea-
FIGURE 1229 - DL REQUEST

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 After MS has established GPRS UL TBF, RANPS module receives
Point 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 No statistics temporarily.

C901170005 Number
of GPRS DL TBF
not support DTM
C901170007 Number
of GPRS DL TBF
Abis congestion
Definition Number of GPRS DL TBF establishment failure due to Abis conges-
tion.
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 The measurement is taken at two time points listed below:
Point
� 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 DUE TO ABIS

CONGESTION (I)

� After MS establishes GPRS UL TBF, RANPS module receives

EV_MAC_DL_ASSIGN_REQ message sent from RANU module, if re-
source application fails and the cause of failure is Abis conges-
tion, the counter increments. The measurement point is A, as

CONGESTION (II)
Unit Times
C901170008 Number
of GPRS DL TBF
RR congestion
Definition Number of GPRS DL TBF establishment failure due to RR conges-
tion.
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).
applies to database for resource and the cause of failures is RR
Point
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)

source application fails and the cause of failure is RR conges-

CONGESTION (II)
Unit 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.

database for resource and the cause of failures is UPPB-DSP chan-
nel congestion when BSC attempts to establish GPRS DL TBF.
applies to database for resource and the cause of failures is UPPB-
DSP channel congestion when BSC attempts to establish GPRS DL
TBF.
Point
EV_RANUMC_DLASS_REQ 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.
FIGURE 1235 - DATABASE APPLICATION FAILURE DUE TO UPPB-DSP

CHANNEL CONGESTION (I)

source application fails and the cause of failure is UPPB-DSP
channel congestion, the counter increments. The measure-

CHANNEL CONGESTION (II)
Unit Times

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 re-
source application that RANPS sends when BSC attempts to es-
tablish GPRS DL TBF.
Measurement After RANPS module receives DL request message
Point (EV_RANUMC_DLASS_REQ) sent from RANUMC module, when resource
application succeeds, the counter increments. The measurement
FIGURE 1237 - SUCCESSFUL RESOURCE APPLICATION
Unit 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.


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 ac-
tivate 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 fail-
ure when BSC establishes GPRS DL TBF (including establishing DL
TBF initially and establishing DL TBF while UL TBF already exists).
Point
� When BSC receives PDCH activation failure message reported
by BTS, the counter increments. The measurement point is A,

FIGURE 1239 - PDCH ACTIVATION FAILURE
� If 'wait for PDCH activate & connection response' timer expires,

and BSC has not received PDCH activate response message
reported by BTS, the counter increments.
Unit Times
C901170013 Number
of GPRS DL TBF
BTS connection failed
Definition Number of GPRS DL TBF establishment failure due to BTS connec-
tion 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 fail-
ure 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).
Point
� If RANPS module receives connection failed message reported
by connection module, and the cause of failure is BTS connec-
tion failed, the counter increments. The measurement point is
A, as shown inFigure 1240.
FIGURE 1240 - CONNECTION FAILED DUE TO BTS CONNECTION FAILURE


and BSC has not received connection success response mes-
sage reported by connection module, the counter increments.
Unit Times
C901170014 Number
of GPRS DL TBF
BIU connection failed
Definition Number of GPRS DL TBF establishment failed due to BIU connec-
tion failure.
Description This counter counts the number of connection failure due to BIU
connection failed when BSC establishes GPRS DL TBF.
ure due to BIU connection failed when BSC establishes GPRS DL
Measurement If RANPS module receives connection failed message reported by
Point 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 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 When RANPS module receives channel activate response message
Point reported by BTS and connection success response message re-
ported by connection module, the counter increments. The mea-
surement 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
due to not receive PIA
Description This counter counts the number of DL immediate assignment mes-
sage sending failures when BSC establishes GPRS DL TBF.

Usage This counter is used to find out the frequency of DL immediate

assignment message sending failures when BSC establishes GPRS
DL TBF.
Point
� 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
� If 'wait for immediate assignment sending indication' timer ex-

pires, and BSC has not received immediate assignment send-
ing message, the counter increments.
Unit Times
C901170017 Number
of GPRS DL TBF
CCCH/PCCCH due to
UPPB-DSP congestion
due to UPPB-DSP congestion.
Description No statistics for this counter is meaningless to GPRS DL TBF.

C901170018 Number
of GPRS DL TBF
PACCH due to UPPB-DSP
congestion
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 as-
signment 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 When RANPS module receives successful immediate assignment
Point sending message (SPS_ABIS_PACKET_SEND_PIA_IND) reported by BTS,
Figure 1244.
FIGURE 1244 - SUCCESSFUL IMMEDIATE ASSIGNMENT SENDING
Unit Times

C901170020 Number
of GPRS DL TBF
on PACCH
Definition Number of GPRS DL TBF establishment success on PACCH.
Abis congestion for UL TBF
establishment
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 re-
allocation failure. This counter counts the number of DL resource
reallocation failure due to Abis congestion.
resource reallocation failure due to Abis congestion.
Measurement MS has established GPRS DL TBF, and after RANPS module receives
Point EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if resource
application fails due to Abis congestion, the counter increments.

FIGURE 1245 - RESOURCE APPLICATION FAILURE DUE TO ABIS

CONGESTION (ASSIGNED BY UL)
Unit 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 (num-
ber of MS reaches the peak in each channel), TAI/TFI (no TAI or
TFI) and no PDCH (no PS channel).
resource reallocation failure due to RR congestion.
Point EV_MAC_UL_ASSIGN_REQmessage sent from RANU module, if resource
application fails due to RR congestion, the counter increments.

FIGURE 1246 - RESOURCE APPLICATION FAILURE DUE TO RR CONGESTION

(ASSIGNED BY UL)
Unit Times
reallocation failure due
to UPPB-DSP channel
congestion for UL TBF
establishment
Definition Number of GPRS DL TBF resource reallocation failure due to UPPB-
DSP 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.
resource reallocation failure due to UPPB-DSP channel congestion.
Point EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if resource
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 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 applica-
tion success.
resource reallocation success.
Point EV_MAC_UL_ASSIGN_REQmessage sent from RANU module, if resource

FIGURE 1248 SUCCESSFUL RESOURCE APPLICATION (ASSIGNED BY UL)
Unit Times
C901170027 Number
of allocated PDCH for
reallocation due to UL TBF
establishment
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 allo-
cated PDCH when GPRS DL TBF resource is reallocated.
Point EV_MAC_UL_ASSIGN_REQmessage sent from RANU module, when re-
source 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 Times
channel activate failure for
Definition Number of GPRS DL TBF resource reallocation failure due to chan-
nel 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.
Point
� When BSC receives PDCH activate failure message reported by
BTS, the counter increments. The measurement point is A, as


Unit Times
BTS connection failure for
Definition Number of GPRS DL TBF resource reallocation failure due to BTS
connection failure for UL TBF establishment
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.
Point
� If RANPS module receives connection failure message reported
tion failure, the counter increments. The measurement point

FIGURE 1251 - CONNECTION FAILURE DUE TO BTS CONNECTION

FAILURE
� If 'wait for PDCH activation & connection response' timer ex-

pires, and BSC has not received connection success response
message reported by connection module, the counter incre-
ments.
Unit Times
BIU connection failure for UL
TBF establishment
Definition Number of GPRS DL TBF resource reallocation failure due to BIU
connection failure during the process of GPRS DL TBF resource
reallocation.
due to BIU connection failure during the process of GPRS DL TBF
Measurement If RANPS module receives connection failure message reported
Point by connection module, and the cause of failure is BIU connection
failure, the counter increments. The measurement point is A, as

Unit Times
channel activate and
connection for UL TBF
establishment
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.
success during the process of GPRS DL TBF resource reallocation.

FIGURE 1253 - SUCCESSFUL ACTIVATION AND CONNECTION
Unit Times
reallocation failure due to UL
TBF establishment
Definition Number of GPRS DL TBF resource reallocation failure due to UL
TBF establishment.
reallocation success due to
Definition Number of GPRS DL TBF resource reallocation success due to UL
TBF establishment.

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 adjust-
ment 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 fail-
ure is Abis congestion).
Usage This counter is used to find out the frequency of resource appli-
cation failures after RANPS receives resource adjustment request
during GPRS DL TBF transmission (the cause of database applica-
tion failure is Abis congestion).
Measurement After RANPS module receives EV_MAC_RESOURCE_ADJU_REQ message
Point sent from MAC, if resource application fails due to Abis congestion,
inFigure 1254.

CONGESTION (RESOURCE ADJUSTMENT)
Unit Times

RR congestion for LLC
transmission
Definition Number of GPRS DL TBF resource reallocation failure due to RR
failures after RANPS receives resource adjustment request during
ure is RR congestion).
Usage
Point sent from MAC, if resource application fails due to RR congestion,
in Figure 1255.

(RESOURCE ADJUSTMENT)
Unit Times

to UPPB-DSP channel
congestion for LLC
transmission
Definition Number of GPRS DL TBF resource reallocation failure due to UPPB-
DSP channel congestion for LLC transmission.
message. This counter counts the number of resource reallocation
failure after RANPS receives resource adjustment request during
ure is UPPB-DSP channel congestion).
Usage This counter is used to find out the frequency of resource reallo-
cation failure after RANPS receives resource adjustment request
during GPRS DL TBF transmission (the cause of database applica-
tion failure is UPPB-DSP channel congestion).
Point sent from MAC, if resource application fails due to UPPB-DSP
channel congestion, the counter increments. The measurement

CHANNEL CONGESTION (RESOURCE ADJUSTMENT)
Unit Times

channel allocation due to
LLC transmission
allocation due to LLC transmission.
message. This counter counts the number of resource realloca-
tion success after RANPS receives resource adjustment request
during GPRS DL TBF transmission.
cation success after RANPS receives resource adjustment request
Point sent from MAC, if resource application succeeds, the counter
1257.
FIGURE 1257 SUCCESSFUL RESOURCE APPLICATION (RESOURCE

ADJUSTMENT)
Unit Times

C901170040 Number
reallocation due to LLC
transmission
Definition Number of allocated PDCH for GPRS DL TBF resource reallocation
due to LLC transmission.
LLC changes. RANPS applies for resource after it receives the mes-
sage. 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 al-
located PDCH after RANPS receives resource adjustment request
accumulates the PDTCH number. The measurement point is A, as
FIGURE 1258 - SUCCESSFUL RESOURCE APPLICATION (RESOURCE

ADJUSTMENT)
Unit Times

LLC transmission
Definition Number of GPRS DL TBF resource reallocation failure due to chan-
nel 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 trans-
mission.
Usage This counter is used to find out the frequency of PDCH activate fail-
ure after BSC receives resource adjustment request during GPRS
DL TBF transmission.
Point

Unit Times

LLC transmission
Definition Number of GPRS DL TBF resource reallocation failure due to BTS
connection failure for LLC transmission.
connection failure after BSC receives resource adjustment request
due to BTS connection failure after BSC receives resource adjust-
ment request during GPRS DL TBF transmission.
Measurement measurement is taken at two time points listed below:
Point
FIGURE 1260 - CONNECTION FAILED DUE TO BTS CONNECTION

FAILURE

Unit Times

BIU connection failure for
LLC transmission
Definition Number of GPRS DL TBF resource reallocation failure due to BIU
due to BIU connection failure after BSC receives resource adjust-
ment request during GPRS DL TBF transmission.
Unit Times

connection for LLC
transmission
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.
success after BSC receives resource adjustment request during
GPRS DL TBF transmission.
Unit Times
LLC transmission
Definition Number of GPRS DL TBF resource reallocation failure due to LLC
transmission.

LLC transmission
Definition 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.
forcing Release Requests due to flush LL received by RANPS.
Measurement When RANPS module receives Release Request message
Point (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

to GPRS suspend requests
Definition Number of GPRS DL TBF release due to GPRS suspend requests.
GPRS suspend requests.
Usage This counter is used to find out the frequency of GPRS DL TBF forc-
ing Release Requests due to suspend requests received by RANPS.
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 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.
forcing Release Requests (EV_RANCCM_PDCH_REL) received by RANPS.
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 re-
quests.
Description This counter counts the number of GPRS DL TBF normal release
due to normal Release Request by MAC.
forcing Release Requests due to normal Release Request by MAC
received by RANPS.
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

GPRS DL TBF abnormal
requests
Definition Number of GPRS DL TBF abnormal release due to user plane re-
quests.
Description This counter counts the number of GPRS DL TBF abnormal release
due to abnormal Release Request by MAC.
forcing Release Requests due to abnormal Release Request by MAC
received by RANPS.
Point (EV_MAC_REL_IND) reported by MAC, if the cause of release is ab-
normal 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 Number of GPRS DL TBF release due to NSVC unavailability.
NSVC unavailability.
forcing Release Requests due to NSVC unavailability received by
RANPS.


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.
BVC unavailability.
Usage This counter is used to find out the frequency of GPRS DL TBF forc-
ing Release Requests due to BVC unavailability received by RANPS.
is BVC unavailability, and GPRS DL TBF exists, the counter incre-
ments. The measurement point is A, as shown inFigure 1269 .
FIGURE 1269 - RELEASE REQUEST DUE TO BVC UNAVAILABILITY
Unit Times

to other reasons
Definition Number of GPRS DL TBF release due to other reasons.
other reasons.
forcing Release Requests due to other reasons received by RANPS.
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 Number of DL GPRS TBF grab resources.
Description 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 This counter increments while DL GPRS TBF is established during
Point 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 Times
Related Features � 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.
TBF resource is grabbed. Measurement point is A as shown
inFigure 1272.
Unit Times

GPRS TBF queuing
Definition Number of DL GPRS TBF queuing.
Description This counter counts the number of DL GPRS TBF queuing.
queuing.
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 Times
GPRS TBF queuing success
Definition Number of DL GPRS TBF queuing success.
Description This counter counts the number of DL GPRS TBF queuing success.
queuing success.
Measurement This counter increments while DL GPRS TBF is established dur-
Point ing resource adjustment, the instance to be queued successfully
assigns resource for user plane, and database is successfully reg-
istered. Measurement point is A as shown in Figure 1274.

FIGURE 1274 - RESOURCE ASSIGNMENT SUCCESS
Unit 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.
release during queuing.
Measurement This counter increments while DL GPRS TBF is released and in-
Point stance still in queuing state. The measurement point is A as shown
inFigure 1275.
FIGURE 1275 - RELEASE DL GPRS TBF
Unit Times


Chapter 24
Downlink EGPRS Data

TBF Statistics
Table of Contents
Overview...................................................................... 1289
quests on CCCH/PCCCH.................................................. 1289
quests 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 es-
tablishment 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
tion failure due to Abis congestion for UL TBF establish-
ment ........................................................................... 1302
failure due to RR congestion for UL TBF establishment......... 1303


failure due to UPPB-DSP channel congestion for UL TBF es-
tablishment .................................................................. 1304
tion success of channel allocation due to UL TBF establish-
ment ........................................................................... 1305
resource reallocation due to UL TBF establishment ............. 1306
failure due to channel activate failure for UL TBF establish-
ment ........................................................................... 1307
failure due to BTS connection failure for UL TBF establish-
ment ........................................................................... 1308
failure due to BIU connection failure for UL TBF establish-
ment ........................................................................... 1309
success of channel activate and connection for UL TBF estab-
lishment....................................................................... 1310
failure due to UL TBF establishment ................................. 1310
success due to UL TBF establishment ............................... 1311
failure due to UPPB-DSP channel congestion for LLC transmis-
sion ............................................................................. 1313
resource reallocation due to LLC transmission.................... 1315
tion failure due to channel activate failure for LLC transmis-
sion ............................................................................. 1316
tion failure due to BTS connection failure for LLC transmis-
sion ............................................................................. 1317
tion failure due to BIU connection failure for LLC transmis-
sion ............................................................................. 1318
success of channel activate and connection for LLC transmis-
sion ............................................................................. 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

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 suc-
cess............................................................................. 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/PC-
CCH.
Description This counter counts the number of DL establishment requests re-
ceived 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 When RANPS module receives the DL request (EV_RANUMC_DLASS_REQ)
Point sent from RANUMC module, the counter increments. This mea-

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 After MS has established EGPRS UL TBF, RANPS module receives
Point message sent from RANU module, the counter
EV_MAC_DL_ASSIGN_REQ
increments. This measurement point is A, as shown inFigure 1277.
FIGURE 1277 - DL ASSIGNMENT REQUEST
Unit Times

C901180004 Number
of EGPRS DL TBF
CPU
Definition Number of EGPRS DL TBF establishment failure due to CPU.
C901180005 Number
of EGPRS DL TBF
not support DTM
Definition 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 con-
gestion.
database for resource and the cause of failures is Abis congestion
when BSC attempts to establish EGPRS DL TBF.
applies to database for resource and the cause of failures is Abis
congestion when BSC attempts to establish EGPRS DL TBF.
Point

application fails and the cause of failure is Abis congestion,

the counter increments. The measurement point is A, as

CONGESTION (I)
� After MS establishes EGPRS UL TBF, RANPS module receives

source application fails and the cause of failure is Abis conges-

CONGESTION (II)
Unit Times
C901180008 Number
of EGPRS DL TBF
RR congestion
Definition Number of EGPRS DL TBF establishment failure due to RR conges-
tion.

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).
This counter is used to find out the frequency of failures that RANPS
Point
application fails and the cause of failure is RR congestion, the
inFigure 1280.

CONGESTION (I)

source application fails and the cause of failure is RR conges-

CONGESTION (II)
Unit Times

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.
database for resource and the cause of failures is UPPB-DSP chan-
nel congestion when BSC attempts to establish EGPRS DL TBF.
applies to database for resource and the cause of failures is UPPB-
DSP channel congestion when BSC attempts to establish EGPRS
DL TBF.
Point
application fails and the cause of failure is UPPB-DSP channel

CHANNEL CONGESTION (I)
� After MS establishes EGPRS UL TBF, RANPS module receives

EV_MAC_DL_ASSIGN_REQmessage sent from RANU module, if re-
source application fails and the cause of failure is UPPB-DSP
channel congestion, the counter increments. The measure-


CHANNEL CONGESTION (II)
Unit 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 re-
source application that RANPS sends when BSC attempts to es-
tablish EGPRS DL TBF.
Unit Times

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.
PDCH when BSC attempts to establish EGPRS DL TBF.
Point EV_RANUMC_DLASS_REQsent from RANUMC module, when resource
application succeeds, the counter accumulates the PDCH number.
Unit Times
C901180012 Number
of EGPRS DL TBF
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.

failure when BSC establishes EGPRS DL TBF (including establish-
ing DL TBF initially and establishing DL TBF while UL TBF already
exists).
Point
� 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 connec-
tion failure.
connection failed when BSC establishes EGPRS DL TBF.
ure due to BTS connection failed when BSC establishes EGPRS DL
Point


FAILURE

ments.
Unit Times
C901180014 Number
of EGPRS DL TBF
Definition Number of EGPRS DL TBF establishment failed due to BIU connec-
tion failure.
connection failed when BSC establishes EGPRS DL TBF.
ure due to BIU connection failed when BSC establishes EGPRS DL
Measurement If RANPS module receives connection failed message reported by
Point 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.
establishment success when BSC establishes EGPRS DL TBF.
FIGURE 1289 - IMMEDIATE ASSIGNMENT SENDING FAILURE
Unit Times

C901180016 Number
of EGPRS DL TBF
receive PIA
due to not receive PIA
Description This counter counts the number of DL immediate assignment mes-
sage sending failures when BSC establishes EGPRS DL TBF.
Usage This counter is used to find out the frequency of DL immediate as-
signment message sending failures when BSC establishes EGPRS
DL TBF.
Point
� When RANPS module receives immediate assignment send-
ing failure message EV_PACKET_PIA_DEL_IND reported by BTS, the
inFigure 1290.
� If 'wait for immediate assignment sending indication' timer ex-

pires, and BSC has not received immediate assignment send-
ing message, the counter increments.
Unit Times

C901180017 Number
of EGPRS DL TBF
CCCH/PCCCH due to
UPPB-DSP congestion
Description No statistics for this counter is meaningless to EGPRS DL TBF.
C901180018 Number
of EGPRS DL TBF
congestion
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 as-
signment message sendings when BSC establishes EGPRS DL TBF.
Usage This counter is used to find out the frequency of EGPRS DL TBF

Measurement When RANPS module receives successful immediate assignment

Point sending message (SPS_ABIS_PACKET_SEND_PIA_IND) reported by BTS,
inFigure 1291.

Unit Times
C901180020 Number
of EGPRS DL TBF
on PACCH
Definition Number of EGPRS DL TBF establishment success on PACCH.
Abis congestion for UL TBF
establishment
Definition 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.
Measurement MS has established EGPRS DL TBF, and after RANPS module re-
Point ceives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if re-
source application fails due to Abis congestion, the counter incre-
ments. The measurement point is A, as shown inFigure 1292.

Unit 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.


resource reallocation failure due to RR congestion.
source application fails due to RR congestion, the counter incre-

(ASSIGNED BY UL)
Unit Times
to UPPB-DSP channel
congestion for UL TBF
establishment
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.

resource reallocation failure due to UPPB-DSP channel congestion.
Point ceives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if
resource application fails due to UPPB-DSP channel congestion,
inFigure 1294.

Unit 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.
resource reallocation success.
source application succeeds, the counter increments. The mea-

FIGURE 1295 SUCCESSFUL RESOURCE APPLICATION (ASSIGNED BY UL)
Unit Times
C901180027 Number
reallocation due to UL TBF
establishment
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 allo-
cated PDCH when EGPRS DL TBF resource is reallocated.
Measurement MS has established EGPRS DL TBF, and after RANPS module
Point 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 Times
Definition Number of EGPRS DL TBF resource reallocation failure due to chan-
nel 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.
failure during the process of EGPRS DL TBF resource reallocation.
Point
shown in

Unit Times
Definition Number of EGPRS DL TBF resource reallocation failure due to BTS
connection failure during the process of EGPRS DL TBF resource
reallocation.
due to BTS connection failure during the process of EGPRS DL TBF
Point

FAILURE


ments.
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.
connection failure during the process of EGPRS DL TBF resource
reallocation.
due to BIU connection failure during the process of EGPRS DL TBF
Unit Times

connection for UL TBF
establishment
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.
success during the process of EGPRS DL TBF resource reallocation.
Unit Times
reallocation failure due to UL
TBF establishment
Definition Number of EGPRS DL TBF resource reallocation failure due to UL
TBF establishment.

Definition 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 adjust-
failures after RANPS receives resource adjustment request dur-
ing EGPRS DL TBF transmission (the cause of database application
failure is Abis congestion).
during EGPRS DL TBF transmission (the cause of database appli-
cation failure is Abis congestion).
Point sent from MAC, if resource application fails due to Abis congestion,
inFigure 1301 .


Unit Times
transmission
Definition Number of EGPRS DL TBF resource reallocation failure due to RR
failures after RANPS receives resource adjustment request dur-
ing EGPRS DL TBF transmission (the cause of database application
failure is RR congestion).
cation failure is RR congestion).
Point sent from MAC, if resource application fails due to RR congestion,
inFigure 1302 .


Unit 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.
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 fail-
ure is UPPB-DSP channel congestion).
cation failure after RANPS receives resource adjustment request
cation failure is UPPB-DSP channel congestion).
Point sent from MAC, if resource application fails due to UPPB-DSP
channel congestion, the counter increments. The measurement


Unit Times
LLC transmission
LLC changes. RANPS applies for resource after receiving the mes-
sage. This counter counts the number of resource reallocation
success after RANPS receives resource adjustment request during
EGPRS DL TBF transmission.
cation success after RANPS receives resource adjustment request
during EGPRS DL TBF transmission.
1304.


ADJUSTMENT)
Unit Times
C901180040 Number
transmission
Definition Number of allocated PDCH for EGPRS DL TBF resource reallocation
LLC changes. RANPS applies for resource after it receives the mes-
sage. 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 al-
located PDCH after RANPS receives resource adjustment request
accumulates the PDTCH number. The measurement point is A, as


ADJUSTMENT)
Unit 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 trans-
mission.
failure after BSC receives resource adjustment request during EG-
PRS DL TBF transmission.
Point


Unit Times
LLC transmission
Definition Number of EGPRS DL TBF resource reallocation failure due to BTS
due to BTS connection failure after BSC receives resource adjust-
ment request during EGPRS DL TBF transmission.
Point


FAILURE

Unit Times
LLC transmission
Definition Number of EGPRS DL TBF resource reallocation failure due to BIU
due to BIU connection failure after BSC receives resource adjust-
ment request during EGPRS DL TBF transmission.

Unit Times
connection for LLC
transmission
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.
success after BSC receives resource adjustment request during

Unit Times
LLC transmission
Definition Number of EGPRS DL TBF resource reallocation failure due to LLC
transmission.
LLC transmission
Definition Number of EGPRS DL TBF resource reallocation success due to LLC
transmission.
to flush LL
Definition 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.
forcing Release Requests due to flush LL received by RANPS.


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.
EGPRS suspend requests.
forcing Release Requests due to suspend requests received by
RANPS.
is SUSPEND, and EGPRS DL TBF exists, the counter increments.
Unit Times

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.
forcing Release Requests (EV_RANCCM_PDCH_REL) received by RANPS.
Point (EV_RANCCM_PDCH_REL) reported by RANCCM module, if EGPRS DL
TBF exists, the counter increments. The measurement point is A,
Unit Times
EGPRS DL TBF normal
requests
Definition Number of EGPRS DL TBF normal release due to user plane re-
quests.
Description This counter counts the number of EGPRS DL TBF abnormal release
received by RANPS.
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 DUE TO NORMAL RELEASE REQUEST BY

MAC
Unit Times
EGPRS DL TBF abnormal
requests
Definition Number of EGPRS DL TBF abnormal release due to user plane re-
quests
Description This counter counts the number of EGPRS DL TBF abnormal release
received by RANPS.
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 Times

Definition Number of EGPRS DL TBF release due to NSVC unavailability.
forcing Release Requests due to NSVC unavailability received by
RANPS.
is NSVC unavailability, and EGPRS DL TBF exists, the counter
increments. The measurement point is A, as shown inFigure
1315.
FIGURE 1315 - RELEASE REQUEST DUE TO NVSC UNAVAILABILITY
Unit Times
Definition Number of EGPRS DL TBF release due to BVC unavailability.
BVC unavailability.
forcing Release Requests due to BVC unavailability received by
RANPS.
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.
other reasons.
forcing Release Requests due to other reasons received by RANPS.
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.

Usage The counter is used to find out the frequency of downlink EGPRS
TBF grabbing other TBF resources.
Measurement During the downlink EGPRS TBF establishment and resource ad-
Point justment process, if the resource request succeeds and the other
TBF resources is grabbed, the counter increments. The measure-
FIGURE 1318 DOWNLINK EGPRS REQUESTING RESOURCE SUCCESSFULLY
Unit Times
grab instance by DL EGPRS
TBF
Description This counter counts the number of instances grabbed by downlink
EGRPS TBF.
TBF grabbing other TBF resources.
Measurement During the downlink EGPRS TBF establishment and resource
Point 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.

Unit Times
EGPRS TBF queuing
Description This counter counts the number of downlink EGRPS TBF's queuing.
TBF's queuing.
Point justment process, if the resource request succeeds but it can not
guarantee queuing at the QoS rate, the counter increments. The
Unit Times
DL EGPRS TBF queuing
success
Description This counter counts the number of downlink EGRPS TBF's queuing
success.
TBF's queuing success.
Point justment process, when the queuing instance assigns resource to
the user plane successfully and registers in database successfully,


Figure 1321.
FIGURE 1321 ASSIGNING RESOURCE SUCCESSFULLY
Unit Times
EGPRS TBF release TBF
during queuing
Description This counter counts the number of downlink EGRPS TBF's releasing
TBF during queuing.
TBF's releasing TBF during queuing.
Measurement When the downlink EGPRS TBF releases TBF, if the instance is
Point still in queuing status, the counter increments. The measurement
FIGURE 1322 RELEASING DOWNLINK EGPRS TBF
Unit Times

Chapter 25
Uplink GPRS Data TBF

Statistics
Table of Contents
Overview...................................................................... 1332
on CCCH ...................................................................... 1332
quests on CCCH ............................................................ 1333
on PCCCH..................................................................... 1333
quests 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


due to TWO PHASE access .............................................. 1352
due to short access........................................................ 1353
C901190026 Number of allocated PDCH for GPRS UL TBF es-
tablishment .................................................................. 1354
C901190030 Number of GPRS UL TBF channel activate estab-
lishment 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 realloca-
tion failure due to Abis congestion for DL TBF establish-
ment ........................................................................... 1362
failure due to RR congestion for DL TBF establishment......... 1363
failure due to UPPB-DSP channel congestion for DL TBF es-
tablishment .................................................................. 1364
success of channel allocation due to DL TBF establish-
ment ........................................................................... 1365
C901190042 Number of allocated PDCH for GPRS UL TBF re-
source reallocation due to DL TBF establishment................ 1366
failure due to channel activate failure for DL TBF establish-
ment ........................................................................... 1367
failure due to BTS connection failure for DL TBF establish-
ment ........................................................................... 1368
failure due to BIU connection failure for DL TBF establish-
ment ........................................................................... 1369
success of channel activate and connection for DL TBF estab-
lishment....................................................................... 1370
failure due to DL TBF establishment ................................. 1371
success due to DL TBF establishment ............................... 1371
failure due to UPPB-DSP channel congestion for LLC trans-
mission ........................................................................ 1373

Chapter 25 Uplink GPRS Data TBF Statistics

source reallocation due to LLC transmission ...................... 1375
failure due to channel activate failure for LLC transmis-
sion ............................................................................. 1376
failure due to BTS connection failure for LLC transmis-
sion ............................................................................. 1377
failure due to BIU connection failure for LLC transmis-
sion ............................................................................. 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 re-
quest ........................................................................... 1382
success due to resource request ...................................... 1383
source reallocation due to resource request ...................... 1384
C901190069 Number of GPRS UL TBF resourse realloca-
tion failure due to channel activate failure for resource
request ........................................................................ 1385
C901190070 Number of GPRS UL TBF resourse reallo-
cation failure due to BTS connection failure for resource
request ........................................................................ 1386
C901190071 Number of GPRS UL TBF resourse reallo-
cation failure due to BIU connection failure for resource
request ........................................................................ 1387
success of channel activate and connection for resource re-
quest ........................................................................... 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

C901190081 Number of GPRS UL TBF release due to BVC un-

availability .................................................................... 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 es-
tablishment, maintain and release of UL GPRS TBF. The statistic
unit is cell.
C901190002 Number
of GPRS UL TBF
on CCCH
Definition 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.
on CCCH when MS attempts using GPRS service.
Measurement When BSC receives channel requests on CCCH from MS, the
Point counter increments. The measurement point is A, as shown
inFigure 1323.

FIGURE 1323 - CHANNEL REQUEST
Usage Times
C901190003 Number
of EGPRS UL TBF
on CCCH
Definition Number of EGPRS UL TBF establishment requests on CCCH.
Description 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.
on PCCCH when MS attempts using GPRS service.
Measurement When BSC receives channel requests on PCCCH from MS, the
inFigure 1324.

FIGURE 1324 - PACKET CHANNEL REQUEST
Unit Times
C901190005 Number
of EGPRS UL TBF
on PCCCH
Definition Number of EGPRS UL TBF establishment requests on PCCCH.
Description This counter is not meaningful in UL GPRS TBF statistic, and is not
used.
C901190006 Number
of GPRS UL TBF
on PACCH
Definition 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 estab-
lishment attempts on PACCH under the situation when DL GPRS
TBF is already established.

Measurement In the situation when DL GPRS TBF is established, PS control

Point 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 es-
tablishment attempts due to one phase access.
Measurement The counter accumulates at the following two time points:
Point
� If BSC receives channel requests from MS on CCCH due to one
phase access, the counter increments. The measurement point

FIGURE 1326 - CHANNEL REQUESTS ON CCCH DUE TO ONE PHASE

ACCESS

FIGURE 1327 - PACKET CHANNEL REQUESTS ON CCCH DUE TO ONE

PHASE ACCESS
Unit Times

due to single block packet
access
Definition Number of cell attempts for UL assignment due to single block
packet access.

Description This counter counts the number of packet channel requests on PC-
CCH 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 re-
quests when MS attempting UL GPRS TBF establishment due to
single block packet access.
Measurement If BSC receives channel requests on PCCCH from MS due to sin-
Point gle block packet access. The measurement point is A, as shown
inFigure 1328.
FIGURE 1328 - CHANNEL REQUEST DUE TO SINGLE BLOCK PACKET ACCESS
Unit Times

due to response paging
Definition Number of cell attempts for UL assignment due to response pag-
ing.
Description This counter counts the number of packet channel requests when
MS attempting UL GPRS TBF establishment due to response pag-
ing.
response paging.
Measurement When BSC receives channel requests on PCCCH from MS due to
Point response paging, the counter increments. The measurement point

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.
cell update.
Measurement When BSC receives channel requests on PCCCH from MS duet to
Point cell update, the counter increments. The measurement point is A,
FIGURE 1330 - CHANNEL REQUESTS DUE TO CELL UPDATE
Unit Times


due to mobility management
Definition Number of cell attempts for UL assignment due to mobility man-
agement
Description The counter counts the number of packet channel requests on PC-
CCH when MS attempting UL GPRS TBF establishment due to mo-
bile management.
mobile management.
Measurement If BSC receives channel requests on PCCCH from MS due to mobile
Point 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.
tablishment attempts due to two phase access.


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 Times
Related Features GB-03-05-008 Two Phase Access

due to short access
Definition Number of cell attempts for UL assignment due to short access.


PCCCH when MS attempting UL GPRS TBF establishment due to
short access.
tablishment attempts due to short access.
Measurement If BSC receives packet channel requests on PCCCH from MS on
Point PCCCH due to short access, the counter increments. The mea-
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 conges-
tion.
Description The counter records the number of DB resource application failure
when attempting UL GPRS TBF establishment due to Abis conges-
tion.
Usage This counter is used to find out the number of DB resource appli-
cation failure when attempting UL GPRS TBF establishment due to
Abis congestion.
Measurement The counter accumulates at the following three time points:
Point
� 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.

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 measure-

CONGESTION (DL GPRS TBF ALREADY ESTABLISHED)
Unit Times

C901190016 Number
of GPRS UL TBF
RR congestion
Definition Number of GPRS UL TBF establishment failure due to RR conges-
tion.
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.
RR congestion.
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.


CONGESTION (PCCCH)

from PS user plane on CCCH and fails to apply for DB resource
due to RR congestion, the counter increments. The measure-

Unit Times
C901190017 Number
of GPRS UL TBF
to UPPB-DSP channel
congestion
Definition Number of GPRS UL TBF establishment failure due to UPPB-DSP
channel congestion.


when attempting UL GPRS TBF establishment due to UPPB-DSP
channel congestion.
UPPB-DSP channel congestion.
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 PC-

CCH and fails to apply for DB resource due to UPPB-DSP chan-
nel congestion, the counter increments. The measurement

CONGESTION (PCCCH)

from PS user plane on CCCH (DL GPRS TBF already estab-
lished) and fails to apply for DB resource due to UPPB-DSP

FIGURE 1343 - DB RESOURCE REQUESTS FAILURE DUE TO DPPB-DSP

Unit Times
C901190018 Number
of GPRS UL TBF
allocate success
Definition Number of GPRS UL TBF establishment channel allocate success.
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.
Point
and succeeds in applying for DB resource, the counter incre-

FIGURE 1344 - DB RESOURCE REQUEST SUCCESSES (CCCH)
� If PS control panel receives channel requests from MS on PC-

CCH and succeed in applying for DB resource, the counter in-
crements. The measurement point is A, as shown inFigure
1345.
FIGURE 1345 - DB RESOURCE REQUEST SUCCESSES (PCCCH)
� If only GPRS is supported in the network, PS control plane re-

ceives EGPRS channel request on CCCH or on PCCCH from MS,
and DB resource request succeeds, the counter increments.
Unit 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.

Description This counter counts the number of successful UL GPRS TBF estab-
lishment due to one phase access.
tablishment successes due to one phase access.
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 Times
Related Features 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 estab-
lishment 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 If PS control plane receives channel requests on PCCCH from MS
Point due to single block packet access and DB resource request suc-
ceeds, 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.

lishment due to response paging.
TBF establishment due to response paging.
Measurement When PS control plane receives channel requests on PCCCH from
Point 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
Definition Number of cell success for GPRS UL assignment due to cell upda-
tion.
lishment due to cell update
TBF establishment due to cell update.
Measurement When PS control plane receives channel requests on PCCCH from
Point 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.
lishment due to mobile management.
TBF establishment due to mobile management.
Measurement If PS control plane receives channel requests on PCCCH from MS
Point due to mobile management and DB resource request succeeds,
inFigure 1351.
FIGURE 1351 - DB RESOURCE REQUEST SUCCESSES DUE TO MOBILE

MANAGEMENT (PCCCH)

Unit Times
assignment due to TWO
PHASE access
Definition Number of cell success for GPRS UL assignment due to TWO PHASE
access.
lishment due to two phase access.
TBF establishment due to two phase access.
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)
� 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 Times
Related Features ZGB-03-05-008Two Phase Access
assignment due to short
access
Definition Number of cell success for GPRS UL assignment due to short ac-
cess.
lishment due to short access.
TBF establishment due to short access.
Point
� If BSC receives channel requests from MS on CCCH due to
short access and DB resource request succeeds, the counter
1354.

FIGURE 1354 - DB RESOURCE REQUEST SUCCESSES DUE TO SHORT

ACCESS (PCCCH)
� If only GPRS is supported in the network, PS control plane

receives GPRS channel request on CCCH or on PCCCH from MS,
Unit Times
allocated PDCH for GPRS
Definition Number of allocated PDCH for GPRS UL TBF establishment.
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.
Point
� 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 Times

C901190027 Number
of GPRS UL TBF
Definition Number of GPRS UL TBF establishment failure due to channel ac-
tivate 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).
Point
� When BSC receives PDTCH channel activate failure message
reported by BTS, the counter increments. The measurement
� When 'wait for PDTCH channel activation and connection re-

sponse' counter times out and BSC fails to receive PDTCH ac-
tivate response message reported by BTS, this counter incre-
ments.
Unit Times

C901190028 Number
of GPRS UL TBF
Definition Number of GPRS UL TBF establishment failure due to BTS connec-
tion failed.
Description This counter counts the number of failure to establish UL GPRS
TBF due to BTS connection failure.
lishment failure (including initially establish UL TBF and establish
UL TBF when DL TBF exists) due to BTS connection failure.
Point
� When PS control plane receives connection failure message re-
ported by connection module due to BTS connection failure, the
Figure 1358.
� When 'wait for PDTCH channel activate and connection re-

sponse' counter times out and BSC fails to receive connection
success response message reported by connection module,
Unit Times

C901190029 Number
of GPRS UL TBF
Definition Number of GPRS UL TBF establishment failure due to BIU connec-
tion failed.
TBF due to BIU connection failure.
UL TBF when DL TBF exists) due to BIU connection failure.
Measurement When PS control plane receives connection failure message
Point reported by connection modules due to BIU connection failure,
inFigure 1359.
Usage Times
GPRS UL TBF channel
success
Definition 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 When PS control plane receives channel activate response mes-
Point sage reported by BTS and connection successes acknowledgement
message reported by connection module, the counter increments.

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 as-
signment message to MS when establishing UL GPRS TBF.
Usage This counter is used to find out the number of failure to send im-
mediate assignment message to MS when establishing UL GPRS
TBF.
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 assign-
ment and sending indication message, the counter increments.

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
TBF.
Usage This counter is used to find out the number of failure to establish
UL GPRS TBF.
Measurement When PS control plane assigns single block through two phase ac-
Point cess 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 Times

GPRS UL TBF establisment
UPPB-DSP congestion
Definition Number of GPRS UL TBF establishment failure on PACCH due to
Description 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
lishment and receiving MS TLL1.
TBF establishment and receiving MS TLL1.
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

� 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 Number of GPRS UL TBF establishment success on PACCH.
Abis congestion for DL TBF
establishment
Definition 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 real-
location failure due to Abis congestion.
Measurement In the situation when UL GPRS TBF is established, PS control plane
Point receives DL assignment request message from PS user plane, and
DB resource request fails due to Abis congestion, the counter in-
crements. The measurement point is A, as shown inFigure 1364 .

CONGESTION
Unit Times
RR congestion for DL TBF
establishment
Definition Number of GPRS UL TBF resource reallocation failure due to RR
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.

location failure due to RR congestion.
DB resource request fails due to RR congestion, the counter incre-
FIGURE 1365 - DATABASE APPLICATION FAILURE DUE TO RR CONGESTION
Unit Times
to UPPB-DSP channel
congestion for DL TBF
establishment
Definition Number of GPRS UL TBF resource reallocation failure due to UPPB
-DSP channel congestion for DL TBF establishment.
records the number of UL resource reallocation failure due to
UPPB-DSP channel resource congestion.
location failure due to UPPB-DSP channel congestion.
DB resource request fails due to UPPB-DSP channel congestion,
inFigure 1366.


CHANNEL CONGESTION
Unit 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 establish-
ment on PACCH when UL GPRS TBF is already established.
Usage This counter is used to find out the number of DL GPRS TBF real-
location successes.
DB resource request succeeds, the counter increments. The mea-
FIGURE 1367 SUCCESSFUL RESOURCE APPLICATION

Unit 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.
PDTCH when UL GPRS TBF is successfully reallocated.
DB resource request succeeds, the counter increments. The mea-
Unit Times

GPRS UL TBF resourse
Definition Number of GPRS UL TBF resource reallocation failure due to chan-
nel activate failure for DL TBF establishment.
Description The counter records the number of PDTCH activate failure during
UL GPRS TBF resource reallocation.
failure during UL GPRS TBF resource reallocation.
Point
from BTS, the counter increments. The measurement point is
A, as shown inFigure 1369 .
FIGURE 1369 - PDTCH ACTIVATION FAILURE
� When 'Wait for PDTCH channel activation and connection re-

sponse' timer times out, and BSC fails to receive PDTCH chan-
nel activate response message from BTS, the counter incre-
ments.
Unit Times

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
Point
� When PS control plane receives connection failure message
from connection module due to BTS connection failure, the
inFigure 1370 .

sponse' timer times out, and BSC fails to receive connection
success message from connection module, the counter incre-
ments.
Unit 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 fail-
ure during UL GPRS TBF resource reallocation.
Measurement When PS control plane receives connection failure message from
Point connection module due to BIU connection failure, the counter in-
crements. The measurement point is A, as shown inFigure 1371.
Unit Times

connection for DL TBF
establishment
activate and connection for DL TBF establishment
Description The counter records the number of channel activate and connec-
tion successes during UL GPRS TBF resource reallocation.
connection successes during UL GPRS TBF resource reallocation.
Measurement When PS control plane receives channel activate ack message and
Point connection success ack message from connection module due to
BIU connection failure, the counter increments. The measurement

Unit Times

reallocation failure due to DL
TBF establishment
Definition Number of GPRS UL TBF resource reallocation failure due to DL
TBF establishment.
Definition Number of GPRS UL TBF resource reallocation success due to DL
TBF establishment.
transmission
congestion for LLC transmission
Description During UL GPRS TBF transmission process, PS user plane sends re-
source 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

failure due to Abis resource congestion after PS control plane re-

ceiving resource reallocation request during UL GPRS TBF trans-
mission 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 When PS control plane receives resource reallocation message
Point from PS user plane, and DB resource request fails due to Abis
congestion, the counter increments. The measurement point is

CONGESTION
Unit Times
transmission
congestion for LLC transmission
Description During UL GPRS TBF transmission process, PS user plane sends re-
source reallocation message to PS control plane due to LLC frame
failure due to radio resource congestion after PS control plane re-
ceiving resource reallocation request during UL EGPRS TBF trans-
mission process.
There are three causes leading to RR congestion: MS per channel
(reaches its maximum), TAI/TFI (not available), and no PDTCH.

RR congestion after PS control plane receiving resource realloca-
tion request during UL EGPRS TBF transmission process.
Point from PS user plane, and DB resource request fails due to RR
congestion, the counter increments. The measurement point is A,

Unit Times
to UPPB-DSP channel
congestion for LLC
transmission
Definition Number of GPRS UL TBF resource reallocation failure due to UPPB-
DSP 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 trans-
mission process.
Usage This counter is used to find out DB resource request failure due
to UPPB-DSP channel congestion after PS control plane receiving

resource reallocation request during UL GPRS TBF transmission

process.
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 Times
LLC transmission
allocation due to LLC transmission
successes after PS control plane receiving resource reallocation re-
quest 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 dur-
ing UL EGPRS TBF transmission process.
Point from PS user plane, and DB resource request succeeds, the
inFigure 1376.

FIGURE 1376 RELEASE REQUEST DUE TO FLUSH LL
Unit Times
C901190055 Number
transmission
Definition Number of allocated PDTCH for GPRS UL TBF resource reallocation
message. The counter records the number of successfully allo-
cated PDTCH after PS control plane receiving resource reallocation
requests during UL GPRS TBF.
PDTCH when UL GPRS TBF is successfully reallocated.
inFigure 1377.
Unit Times

LLC transmission
nel 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
Point

ments.
Unit 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 re-
quest during UL GPRS TBF transmission.
failure during UL GPRS TBF resource transmission.
Point
inFigure 1379.

FAILURE

ments.
Unit Times

LLC transmission
Definition Number of GPRS UL TBF resource reallocation failure due to BIU
UL GPRS TBF transmission.
ure during UL GPRS TBF transmission.
Unit Times

channel activate for LLC
transmission
activate for LLC transmission.
tion successes during UL GPRS TBF transmission.
connection successes during UL GPRS TBF tranmission.
Unit Times
LLC transmission
Definition Number of GPRS UL TBF resource reallocation failure due to LLC
transmission.

LLC transmission
Definition Number of GPRS UL TBF resource reallocation success due to LLC
transmission.
resource request
Definition Number of GPRS UL TBF resource reallocation requests for re-
source request.
Abis congestion for resource
request
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.
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 PS control plane receives resource request message from PS user
Point plane, and DB resource request fails due to Abis congestion, the
Figure 1382.

CONGESTION (RESOURCE REQUEST)
Unit Times
RR congestion for resource
request
congestion for resource request.
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)
due to RR congestion during UL GPRS TBF process (including UL
two-phase access and UL TBF transmission).


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 Times
to UPPB-DSP channel
congestion for resource
request
UPPB-DSP channel congestion during UL GPRS TBF.
due to UPPB-DSP channel congestion during UL GPRS TBF process
(including UL two-phase access and UL TBF transmission).
Figure 1384.

FIGURE 1384 DB RESOURCE REQUESTS FAILURE DUE TO UPPB-DSP

CHANNEL CONGESTION (RESOURCE REQUEST)
Unit 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.
successes after PS control plane receives resource request from
MS during UL GPRS TBF process (including UL two-phase access
and UL TBF transmission).
Point plane, and DB resource request succeeds, the counter increments.
FIGURE 1385 DB RESOURCE REQUESTS SUCCESSES (RESOURCE REQUEST)

Unit Times
C901190068 Number
reallocation due to resource
request
Description The counter records the number of successful allocated PDTCH af-
ter PS control plane receives resource request message from MS
during UL GPRS TBF process.
PDTCH after PS control plane receives resource request from MS
during UL GPRS TBF process (including UL two-phase access and
FIGURE 1386 DB RESOURCE REQUESTS SUCCESSES (RESOURCE REQUEST)
Unit Times

resource request
nel activate failure for resource request.
UL GPRS TBF resource reallocation after PS control plane receives
resource request message.
Usage The counter records the number of PDTCH activate 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).
Point

ments.
Unit Times

resource request
Definition Number of GPRS UL TBF resource reallocation failure due to BTS
connection failure for resource request.
connection failure during UL GPRS TBF resource reallocation after
PS control plane receives resource request message.
Usage The counter records the number of connection failure due to BTS
PS control plane receives resource request message in UL GPRS
TBF process (including UL two-phase access and one-phase TBF
transmission).
Point
inFigure 1388 .

ments.
Unit 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 The counter records the number of connection failure due to BIU
transmission).
Unit Times

connection for resource
request
activate and connection for resource request
tion 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 connec-
tion 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 trans-
mission).

Unit Times

resource request
Definition Number of GPRS UL TBF resource reallocation failure due to re-
source request.
resource request
Definition Number of GPRS UL TBF resource reallocation failure due to real-
location 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 When PS control plane of BSC receives FLUSH message from SGSN
Point and release is executed when UL GPRS TBF is established, the
Figure 1391.

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.
due to GPRS suspend requests.
Measurement When PS control plane of BSC receives SUSPEND message from
Point SGSN and release is executed when UL GPRS TBF is established,
inFigure 1392.
Unit Times

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 When PS control plane of BSC receives PDCH RELEASE message from
Point CS control plane when UL GPRS TBF is established, the counter
Unit 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 When PS control plane of BSC receives NORMAL RELEASE REQUEST mes-
Point sage from PS user plane when UL GPRS TBF exists, the counter

FIGURE 1394 - NORMAL RELEASE REQUEST
Unit Times
GPRS UL TBF abnormal
requests
Definition Number of GPRS UL TBF abnormal release due to user plane re-
quests.
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 ab-
normal release due to user plane requests.
Measurement When PS control plane receives ABNORMAL RELEASE REQUEST message
Point from PS user plane when UL GPRS TBF exists, the counter incre-

BY MAC
Unit 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
after receiving forcing release request due to NSVC unavailability.
Measurement When PS control plane receives NSVC unavailability command to
Point release PS control plane module from DB when UL GPRS TBF ex-
ists, the counter increments. The measurement point is A, as
FIGURE 1396 - RELEASE REQUEST DUE TO NVSC UNAVAILABILITY
Unit 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.
after receiving forcing release request due to BVC unavailability.
Measurement When PS control plane receives BVC unavailability command to re-
Point lease PS control plane module from DB when UL GPRS TBF exists,
inFigure 1397.

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.
after receiving forcing release request due to other reasons.
Measurement When PS control plane receives release message due to other rea-
Point sons when UL GPRS TBF exists, the counter increments. The mea-
Unit Times

GPRS TBF grab resources
Definition Number of UL GPRS TBF grab resources.
Description 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 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 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.
TBF resource is grabbed. Measurement point is A, as shown
inFigure 1400.

Unit Times
GPRS TBF queuing
Definition Number of UL GPRS TBF queuing.
Description This counter counts the number of UL GPRS TBF queuing.
A as shown inFigure 1401.
Unit 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.
queuing success.
Measurement This counter increments while UL GPRS TBF is established dur-
assigns resource for user plane, and database is successfully reg-
istered. Measurement point is A as shown inFigure 1402.
FIGURE 1402 - RESOURCE ASSIGNMENT SUCCESS
Unit 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.
Measurement This counter increments while UL GPRS TBF is released and in-
inFigure 1403.

FIGURE 1403 - RELEASE UL GPRS TBF
Unit Times

Chapter 26
Uplink EGPRS Data TBF

Statistics
Table of Contents
Overview...................................................................... 1402
on CCCH ...................................................................... 1402
quests on CCCH ............................................................ 1402
on PCCCH..................................................................... 1403
quests 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


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 es-
tablishment success....................................................... 1423
due to not receive PIA.................................................... 1424
on PCCCH/CCCH due to UPPB-DSP congestion ................... 1425
on PCCCH/CCCH............................................................ 1426
on PACCH..................................................................... 1427
tion failure due to Abis congestion for DL TBF establish-
ment ........................................................................... 1428
failure due to RR congestion for DL TBF establishment......... 1429
failure due to UPPB-DSP channel congestion for DL TBF es-
tablishment .................................................................. 1430
tion success of channel allocation due to DL TBF establish-
ment ........................................................................... 1431
resource reallocation due to DL TBF establishment ............. 1432
failure due to channel activate failure for DL TBF establish-
ment ........................................................................... 1433
failure due to BTS connection failure for DL TBF establish-
ment ........................................................................... 1434
failure due to BIU connection failure for DL TBF establish-
ment ........................................................................... 1435
success of channel activate and connection for DL TBF estab-
lishment....................................................................... 1436
failure due to DL TBF establishment ................................. 1437
success due to DL TBF establishment ............................... 1437
failure due to UPPB-DSP channel congestion for LLC transmis-
sion ............................................................................. 1439

Chapter 26 Uplink EGPRS Data TBF Statistics

resource reallocation due to LLC transmission ................... 1441
tion failure due to channel activate failure for LLC transmis-
sion ............................................................................. 1442
tion failure due to BTS connection failure for LLC transmis-
sion ............................................................................. 1443
tion failure due to BIU connection failure for LLC transmis-
sion ............................................................................. 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 re-
quest ........................................................................... 1449
C901200067 Number of EGPRS UL TBF resource reallo-
cation success due to database allocation for resource
request ........................................................................ 1450
resource reallocation due to resource request.................... 1451
tion failure due to channel activate failure for resource re-
quest ........................................................................... 1452
tion failure due to BTS connection failure for resource re-
quest ........................................................................... 1453
tion failure due to BIU connection failure for resource re-
quest ........................................................................... 1454
success of channel activate and connection for resource re-
quest ........................................................................... 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

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 suc-
cess............................................................................. 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 Number of GPRS UL TBF establishment requests on CCCH
C901200003 Number
of EGPRS UL TBF
on CCCH
Definition Number of EGPRS UL TBF establishment requests on CCCH.
Description This counter counts the number of EGPRS channel requests on
CCCH when MS using EGPRS service.

on CCCH when MS attempts using EGPRS service.
Measurement When BSC receives channel requests on CCCH from MS, the
inFigure 1404.
FIGURE 1404 - EGPRS CHANNEL REQUEST
Unit Times
Related Features ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
C901200004 Number
of GPRS UL TBF
on PCCCH
Definition Number of GPRS UL TBF establishment requests on PCCCH.
Description The counter is not used.
C901200005 Number
of EGPRS UL TBF
on PCCCH
Definition Number of EGPRS UL TBF establishment requests on PCCCH.
PCCCH when MS attempts using EGPRS service.

on PCCCH when MS attempts using EGPRS service.
Measurement 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 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 es-
tablishment attempts on PACCH under the situation when DL GPRS
TBF is already established.
Measurement In the situation when DL EGPRS TBF is established, PS control
Point 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.
MS attempting UL EGPRS TBF establishment or the number of
packet channel requests on PCCCH due to one phase access.
tablishment attempts due to one phase access.
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 PC-

CCH due to one phase access, the counter increments. The

FIGURE 1408 - EGPRS PACKET CHANNEL REQUESTS ON CCCH DUE

TO ONE PHASE ACCESS
Unit Times
Related Features � ZGB-03-05-007 One Phase Access
� ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

due to single block packet
access
Definition Number of cell attempts for UL assignment due to single block
packet access

due to response paging
Definition Number of cell attempts for UL assignment due to response pag-
ing.


due to cell updating
Definition Number of cell attempts for UL assignment due to cell updating.

due to mobility management
Definition Number of cell attempts for UL assignment due to mobility man-
agement
Description The counter is not used currently.

due to TWO PHASE access
Definition Number of cell attempts for UL assignment due to TWO PHASE
access.
MS attempting UL EGPRS TBF establishment or the number of
packet channel requests on PCCCH due to two phase access.
tablishment attempts due to two phase access.
Point
� If BSC receives EGPRS channel requests from MS on CCCH due
to two phase access, the counter increments. The measure-

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 Times

due to short access
Definition Number of cell attempts for UL assignment due to short access.
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.
tablishment attempts due to short access.
Point
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 PC-

CCH due to short access, the counter increments. The mea-
FIGURE 1412 - EGPRS PACKET CHANNEL REQUESTS ON PCCCH DUE

TO SHORT ACCESS
Unit Times
C901200015 Number
of EGPRS UL TBF
Abis congestion
Definition Number of EGPRS UL TBF establishment failure due to Abis con-
gestion.
when attempting UL EGPRS TBF establishment due to Abis con-
gestion.
cation failure when attempting UL EGPRS TBF establishment due
to Abis congestion.


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 re-
source due to Abis congestion, the counter increments. The

Unit Times
Related Features � ZGO-03-02-002 Enhancement on Channel Allocation
C901200016 Number
of EGPRS UL TBF
RR congestion
Definition Number of EGPRS UL TBF establishment failure due to RR conges-
tion.


when attempting UL EGPRS TBF establishment due to radio re-
source congestion. There are three causes that lead to radio re-
source congestion: MS per channel (MS number on each channel
reaches its maximum), no TAI/TFI and no PDCH.
to RR congestion.
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 re-
source due to RR congestion, the counter increments. The

Unit Times

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
when attempting UL EGPRS TBF establishment due to UPPB-DSP
channel congestion.
to UPPB-DSP channel congestion.
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)



Unit 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.
successes when attempting UL GPRS TBF establishment.
Measurement If PS control plane receives EGPRS channel requests from MS on
Point CCCH or EGPRS Packet channel request on PCCCH and succeeds in
applying for DB resource, the counter increments. The measure-

FIGURE 1419 - DB RESOURCE REQUEST SUCCESSES (EGPRS)
Unit 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.
when attempting UL EGPRS TBF establishment due to UPPB-DSP
channel congestion.
to UPPB-DSP channel congestion.
Point
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 Times
Related Features � ZGB-03-05-007 One Phase Access

cell success for EGPRS UL
assignment due to single
block packet access
Definition Number of cell success for EGPRS UL assignment due to single
block packet access
Description This counter is not used.
assignment due to response
paging
Definition Number of cell success for EGPRS UL assignment due to response
paging
cell success for EGPRS
UL assignment due to cell
updating
Definition Number of cell success for EGPRS UL assignment due to cell up-
dating.

assignment due to mobility
management
Definition 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 es-
tablishment 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.
Point
to two phase access and DB resource request succeeds, the
Figure 1422.

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 suc-
ceeds, the counter increments. The measurement point is A,
FIGURE 1423 - DB RESOURCE REQUEST SUCCESSES ON PCCCH DUE

TO TWO PHASE ACCESS
Unit Times
Related Features � ZGB-03-05-008 Two Phase Access
assignment due to short
access
Definition Number of cell success for EGPRS UL assignment due to short ac-
cess.

tablishment due to short access.
TBF establishment due to short access.
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 Times

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 When PS control plane receives EGPRS channel requests on CCCH
Point from MS or EGPRS Packet channel request on PCCCH and DB re-
source requests succeed, the counter increments. The measure-
FIGURE 1426 - DB RESOURCE REQUEST SUCCESSES (EGPRS)
Unit Times
C901200027 Number
of EGPRS UL TBF
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 This counter is used to find out the number of PDTCH activate fail-
ure when establishing UL EGPRS TBF (including initially establish
UL TBF and establish UL TBF when DL TBF exists).
Point
reported by BTS, the counter increments. The measurement
� When 'wait for PDTCH channel activation and connection re-

sponse' counter times out and BSC fails to receive PDTCH ac-
tivate response message reported by BTS, this counter incre-
ments.
Unit Times
C901200028 Number
of EGPRS UL TBF
Definition Number of EGPRS UL TBF establishment failure due to BTS con-
nection 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 estab-
UL TBF when DL TBF exists) due to BTS connection failure.
Point
� When PS control plane receives connection failure message re-
ported by connection module due to BTS connection failure, the
Figure 1428.


FAILURE
� When 'wait for PDTCH channel activate and connection re-

sponse' counter times out and BSC fails to receive connection
success response message reported by connection module,
Unit Times
C901200029 Number
of EGPRS UL TBF
Definition Number of EGPRS UL TBF establishment failure due to BIU con-
nection failed.
TBF due to BIU connection failure.
Usage This counter is used to find out the number of UL EGPRS TBF estab-
UL TBF when DL TBF exists) due to BIU connection failure.
Measurement When PS control plane receives connection failure message re-
Point ported by connection modules due to BIU connection failure, the
Figure 1429.

Unit 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.
connection successes when establishing UL EGPRS TBF.
Measurement When PS control plane receives channel activate response mes-
Point sage reported by BTS and connection successes acknowledgement
message reported by connection module, the counter increments.
FIGURE 1430 - UL EGPRS TBF ESTABLISHES CHANNEL ACTIVATION AND

ACCESS SUCCESS

Unit 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 as-
signment message to MS when establishing UL EGPRS TBF.
Usage This counter is used to find out the number of failure to send im-
mediate assignment message to MS when establishing UL EGPRS
TBF.
Point
� When PS control plane receives immediate assignment failure
message reported by BTS, the counter increments. The mea-
� When 'wait for immediate assignment and sending indication'

counter times out and BSC fails to receive immediate assign-
ment and sending indication message, the counter increments.
Unit 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.
TBF.
Usage This counter is used to find out the number of failure to establish
UL EGPRS TBF.
Measurement When PS control plane assigns single block through two phase ac-
Point cess 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 Times

C901200033 Number
of EGPRS UL TBF
congestion
Definition 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.
tablishment and receiving MS TLL1.
Usage This counter is used to find out the number of successful UL EGPRS
TBF establishment and receiving MS TLL1.
Point
� When PS control plane receives MS TLL1 MAC establishment in-
dication message reported by PS user plane in the premise of
one phase access, the counter increments. The measurement

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 Times
C901200035 Number
of EGPRS UL TBF
on PACCH
Definition Number of EGPRS UL TBF establishment success on PACCH.

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.
location failure due to Abis congestion.
Measurement In the situation when UL EGPRS TBF is established, PS control
Point plane receives DL assignment request message from PS user
plane, and DB resource request fails due to Abis congestion,
inFigure 1435.

CONGESTION
Unit Times

RR congestion for DL TBF
establishment
Definition Number of EGPRS UL TBF resource reallocation failure due to RR
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 re-
allocation failure due to RR congestion.
plane, and DB resource request fails due to RR congestion, the
inFigure 1436.
FIGURE 1436 - DATABASE APPLICATION FAILURE DUE TO RR CONGESTION
Unit Times

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.
allocation failure due to UPPB-DSP channel congestion.
plane, and DB resource request fails due to UPPB-DSP channel

CHANNEL CONGESTION
Unit 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 establish-
ment on PACCH when UL EGPRS TBF is already established.
Usage This counter is used to find out the number of DL EGPRS TBF re-
allocation successes.
plane, and DB resource request succeeds, the counter increments.
FIGURE 1438 SUCCESSFUL RESOURCE APPLICATION
Unit Times

C901200042 Number
reallocation due to DL TBF
establishment
Definition Number of allocated PDTCH for EGPRS UL TBF resource realloca-
tion due to DL TBF establishment.
Description The counter records the number of successful allocated PDTCH
when UL EGPRS TBF is successfully reallocated.
PDTCH when UL EGPRS TBF is successfully reallocated.
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 succeeds, the counter incre-
Unit Times

Definition Number of EGPRS UL TBF resource reallocation failure due to chan-
nel activate failure for DL TBF establishment.
failure during UL EGPRS TBF resource reallocation.
Point

ments.
Unit Times

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.
Point
in Figure 1441.

FAILURE

ments.
Unit Times

BIU connection failure for DL
TBF establishment
Definition Number of EGPRS UL TBF resource reallocation failure due to BIU
UL EGPRS TBF resource reallocation.
ure during UL EGPRS TBF resource reallocation.
Unit Times

connection for DL TBF
establishment
activate and connection for DL TBF establishment
tion successes during UL EGPRS TBF resource reallocation.
connection successes during UL EGPRS TBF resource reallocation.

Unit Times

reallocation failure due to DL
TBF establishment
Definition Number of EGPRS UL TBF resource reallocation failure due to DL
TBF establishment.
Definition Number of EGPRS UL TBF resource reallocation success due to DL
TBF establishment.
transmission

failure due to Abis resource congestion after PS control plane re-

mission process.
Abis resource congestion after PS control plane receiving resource
reallocation request during UL EGPRS TBF transmission process.
Point from PS user plane, and DB resource request fails due to Abis

Unit Times
transmission
failure due to radio resource congestion after PS control plane re-
mission process.
There are three causes leading to RR congestion: MS per channel
(reaches its maximum), TAI/TFI (not available), and no PDTCH.

RR congestion after PS control plane receiving resource realloca-
tion request during UL EGPRS TBF transmission process.
Point from PS user plane, and DB resource request fails due to RR

Unit Times
to UPPB-DSP channel
congestion for LLC
transmission
UPPB-DSP channel congestion for LLC transmission.
message. The counter records the number of DB resource re-
quest 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

resource reallocation request during UL EGPRS TBF transmission

process.
Point from PS user plane, and DB resource request fails due to
UPPB-DSP channel congestion, the counter increments. The

Unit Times
LLC transmission
successes after PS control plane receiving resource reallocation re-
quest 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 dur-
ing UL EGPRS TBF transmission process.
Figure 1447.


ADJUSTMENT)
Unit Times
C901200055 Number
transmission
tion due to LLC transmission.
message. The counter records the number of successfully allo-
cated PDTCH after PS control plane receiving resource reallocation
requests during UL EGPRS TBF.
PDTCH when UL EGPRS TBF is successfully reallocated.
inFigure 1448.


ADJUSTMENT)
Unit Tines
LLC transmission
Definition Number of EGPRS UL TBF resource reallocation failure due to chan-
nel 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
Point


ments.
Unit Times
LLC transmission
connection failure after BSC receiving resource reallocation re-
quest during UL EGPRS TBF transmission.
failure during UL EGPRS TBF resource transmission.
Point
in


FAILURE

ments.
Unit Times
LLC transmission
UL EGPRS TBF transmission.
ure during UL EGPRS TBF transmission.

Unit Times
channel activate for LLC
transmission
activate for LLC transmission
tion successes during UL EGPRS TBF transmission.
connection successes during UL EGPRS TBF tranmission.
point is A, as shown in .

FIGURE 1452
Unit Times
LLC transmission
Definition Number of EGPRS UL TBF resource reallocation failure due to LLC
transmission.
LLC transmission
Definition Number of EGPRS UL TBF resource reallocation success due to LLC
transmission.

resource request
Definition Number of EGPRS UL TBF resource reallocation requests for re-
source request.
Abis 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 EGPRS TBF.
during UL EGPRS TBF process (including UL two-phase access and
Point plane, and DB resource request fails due to Abis congestion, the
Figure 1453.


CONGESTION (RESOURCE REQUEST)
Unit Times
RR congestion for resource
request
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).
due to RR congestion during UL EGPRS TBF process (including UL
two-phase access and UL TBF transmission).
Measurement PS control plane receives resource request message from MS, and
Point DB resource request fails due to RR congestion, the counter incre-

FIGURE 1454 - DB RESOURCE REQUESTS FAILURE DUE TO RR CONGESTION
Unit Times
to UPPB-DSP channel
congestion for resource
request
UPPB-DSP channel congestion for resource request.
UPPB-DSP channel congestion during UL EGPRS TBF.
due to UPPB-DSP channel congestion during UL EGPRS TBF process
(including UL two-phase access and UL TBF transmission).
Figure 1455.


CHANNEL CONGESTION (RESOURCE REQUEST)
Unit Times
reallocation success due
to database allocation for
resource request
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.
successes after PS control plane receives resource request from
MS during UL EGPRS TBF process (including UL two-phase access
and UL TBF transmission).

FIGURE 1456 - DB RESOURCE REQUESTS SUCCESSES (RESOURCE REQUEST)
Unit Times
C901200068 Number
reallocation due to resource
request
tion due to resource request.
Description The counter records the number of successful allocated PDTCH af-
ter PS control plane receives resource request message from MS
during UL EGPRS TBF process.
PDTCH after PS control plane receives resource request from MS
during UL EGPRS TBF process (including UL two-phase access and

FIGURE 1457 - DB RESOURCE REQUESTS SUCCESSES (RESOURCE REQUEST)
Unit Times
resource request
Number of EGPRS UL TBF resource reallocation failure due to chan-
nel activate failure for resource request.
The counter records the number of PDTCH activate failure during
UL EGPRS TBF resource reallocation after PS control plane receives
resource request message.
The counter records the number of PDTCH activate 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).
The counter accumulates at the following two time points:
A, as shown in .


ments.
Unit Times
resource request
connection failure during UL EGPRS TBF resource reallocation after
Usage The counter records the number of connection failure due to BTS
transmission).
Point
in Figure 1459.


FAILURE

ments.
Unit Times
resource request
Description The counter records the number of connection failure due to BIU
Usage The counter records the number of connection failure due to BIU
PS control plane receives resource request message in UL EGPRS
transmission).

Unit Times
connection for resource
request
activate and connection for resource request
tion 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 connec-
tion 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 trans-
mission).


Unit Times
resource request
resource request

to flush LL
Description This counter counts the number of UL EGPRS TBF release after PS
control plane receiving request due to flush LL.
lease after PS control plane receiving request due to flush LL.
Measurement When PS control plane of BSC receives FLUSH message from SGSN
Point and release is executed when UL EGPRS TBF is established, the
Figure 1462.
FIGURE 1462 RELEASE REQUEST DUE TO SUSPEND REQUEST
Unit Times
Description This counter counts the number of UL EGPRS TBF release after PS
control plane receiving request due to GPRS suspend requests.
lease due to GPRS suspend requests.
Measurement When PS control plane of BSC receives SUSPEND message from
Point SGSN and release is executed when UL EGPRS TBF is established,
Figure 1463.

FIGURE 1463 RELEASE REQUEST DUE TO SUSPEND REQUEST
Unit 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 forc-
ing release by CS.
Measurement When PS control plane of BSC receives PDCH RELEASE message
Point from CS control plane when UL EGPRS TBF is established, the
Figure 1464.
FIGURE 1464 RELEASE REQUEST DUE TO PDCH REL
Unit Times

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 nor-
mal release due to user plane requests.
Measurement When PS control plane of BSC receives NORMAL RELEASE RE-
Point QUEST message from PS user plane when UL EGPRS TBF exists,
Figure 1465.
FIGURE 1465 RELEASE REQUEST DUE TO NORMAL RELEASE REQUEST BY

MAC
Unit 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 ab-
normal release due to user plane requests.
Measurement When PS control plane receives ABNORMAL RELEASE REQUEST
Point message from PS user plane when UL EGPRS TBF exists, the
Figure 1466.

FIGURE 1466 RELEASE REQUEST DUE TO ABNORMAL RELEASE REQUEST

BY MAC
Unit 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
lease after receiving forcing release request due to NSVC unavail-
ability.
Measurement When PS control plane receives NSVC unavailability command to
Point release PS control plane module from DB when UL EGPRS TBF
FIGURE 1467 - RELEASE REQUEST DUE TO NSVC UNAVAILABILITY
Unit 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.
lease after receiving forcing release request due to BVC unavail-
ability.
Measurement When PS control plane receives BVC unavailability command to
Point 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.
lease after receiving forcing release request due to other reasons.
Measurement When PS control plane receives release message due to other rea-
Point sons when UL EGPRS TBF exists, the counter increments. The

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 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 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.
TBF resource is grabbed. Measurement point is A as shown in
Figure 1471.
Unit Times
EGPRS TBF queuing
Definition Number of UL EGPRS TBF queuing.
Description This counter counts the number of UL EGPRS TBF queuing.
queuing.
A as shown in Figure 1472.

Unit 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.
queuing success.
Measurement This counter increments while UL EGPRS TBF is established dur-
assigns resource for user, and database is successfully registered.
Measurement point is A as shown inFigure 1473.

Unit 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.
Measurement This counter increments while UL EGPRS TBF is released and in-
in Figure 1474.
FIGURE 1474 - RELEASE UL EGPRS TBF
Unit Times


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 re-
ceived ......................................................................... 1472
C901210009 Number of BVC-RESET message sent ............ 1473
C901210010 Number of BVC-RESET-ACK message received
.................................................................................. 1474
C901210011 Number of BVC-RESET message re-
ceived.......................................................................... 1474
sent............................................................................. 1475
C901210013 Number of PERFORM-LOCATION-REQUEST mes-
sage received................................................................ 1476
message sent ............................................................... 1477
C901210015 Number of PERFORM-LOCATION-ABORT mes-
sage received................................................................ 1478
sent............................................................................. 1479
C901210017 Number of POSITION-RESPONSE message re-
ceived.......................................................................... 1480
C901210018 Number of Flush-LL received if UL/DL TBF ex-
ist ............................................................................... 1481
C901210019 Number of Flush-LL received if DL TBF ex-
ist ............................................................................... 1482
C901210020 Number of Flush-LL received if UL TBF ex-
ist ............................................................................... 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 reselec-
tion ............................................................................. 1490
Overview
TRX measurement is to measure the success or failure condition
of channel activation, assignment, and handover in the unit of car-
rier. 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 origi-
nates packet paging for MS in designated cell. This counter counts
the number of receiving this message.
Measurement When BSC receives a “PAGING PS” message, this counter incre-
FIGURE 1475 PAGING PS PROCESS
Unit Times
paging CS message
Definition Number of paging CS message
Description 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 When BSC receives a PAGING CS message, this counter increments.

Point The measurement point is A, as shown inFigure 1476.
FIGURE 1476 - PAGING CS PROCESS
Unit 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 When BSC receives a FLUSH-LL message, this counter increments.
FIGURE 1477 - FLUSH-LL MESSAGE
Unit Times

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 When BSC receives a FLUSH-LL-ACK message, this counter incre-
Unit Times
BVC-BLOCK message sent
Definition 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 When BSC sends a BVC-BLOCK message, this counter increments.
Point 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 des-
ignated BVC blocked by BSC, and this counter counts the number
of receiving this message by BSC.
Measurement When BSC receives a BVC-BLOCK-ACK message, this counter incre-
Point ments. The measurement point is A2, as shown inFigure 1480 .
FIGURE 1480 - BVC BLOCKING PROCESS
Unit Times

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 unblock-
ing designated BVC by BSC.
Measurement When BSC sends a BVC-UNBLOCK message, this counter increments.
Point 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 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 When BSC receives a BVC-UNBLOCK-ACK message, this counter incre-
Point ments. 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 When BSC sends a BVC-RESET message, this counter increments.
FIGURE 1483 - BVC RESET PROCESS

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 desig-
nated BVC reset by BSC, and this counter counts the number of
receiving this message by BSC.
Measurement When BSC receives a BVC-RESET-ACK essage, this counter incre-
Unit Times
BVC-RESET message
received
Definition 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.
The measurement point is A3, as shown inFigure 1485.
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 When BSC sends a BVC-RESET-ACK message, this counter increments.

Unit Times
PERFORM-LOCATION-RE
QUEST message received
Definition Number of PERFORM-LOCATION-REQUEST message received.
Description SGSN sends location request message to request BSC to do a lo-
cating 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 When BSC receives a PERFORM-LOCATION-REQUEST message, this
Point 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 mes-
sage 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 When BSC sends a PERFORM-LOCATION- RESPONSE message, this counter
1488.

Unit Times
PERFORM-LOCATION-AB
ORT message received
Definition 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 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 BSC sends a POSITION-COMMAND message, this counter increments.

Unit Times
POSITION-RESPONSE
message received
Definition 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 num-
ber of receiving this message by BSC.
Measurement When BSC receives a POSITION-RESPONSE message, this counter in-
Point crements. 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 Each time BSC receives a FLUSH-LL message and MS is conducting
Point DL data service, this counter increments. The measurement point

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
message during DL data service made by MS.
Measurement When BSC receives a FLUSH-LL message and MS is conducting UL
Point data service, this counter increments. The measurement point is
FIGURE 1493 - RECEIVE FLUSH-LL FOR DL TBF

Unit Times
Flush-LL received if UL TBF
exist
Definition Number of Flush-LL received if UL TBF exist
message during UL data service made by MS.
Measurement When BSC receives a FLUSH-LL message and MS is conducting UL
Point 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 mes-
sage by BSC, and the number of same NSE for new and previous
cells.
Measurement When BSC receives a FLUSH-LL message and new and previous cells
Point are same NSE, this counter increments. The measurement point
is A1, as shown inFigure 1495.

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 inter-
cell 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 When BSC receives a FLUSH-LL message and new and previous cells
Point are same BSS or different NSEs, this counter increments. The
Unit 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 inter-
cell 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 When BSC receives a FLUSH-LL message, and new and previous
Point 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 When PS control plane receives the indication of LLC frame trans-
Point ferring success or failure from PS user plane, the number of bytes
of LLC frames successfully transferred is accumulated.
Unit Byte


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 down-
link TBFs being established simultaneously occurs.
Usage This counter is used to find out the number of LLC frames success-
fully transferred after LLC frame transferring is initiated.
Point ferring success or failure from PS user plane, the number of LLC
frames successfully transferred is accumulated.
Unit Times

failed bytes
Description If LLC frame transferring is supported, then this counter counts
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.
Point ferring failure from PS user plane, the number of bytes of LLC
frames failed to be transferred is accumulated.
Unit 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.

Point ferring failure from PS user plane, the number of LLC frames failed
to be transferred is accumulated.
Unit Times

failed num
1. V6.20.200a ~ V6.20.200e
This counter is not used.
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 simul-
taneously occurs.
ii. Usage
This counter is used to find out the number of LLC frames
failed to be transferred after LLC frame transferring is ini-
tiated.
iii. Measurement Point
When PS control plane receives the indication of LLC frame
transferring completion from PS user plane, if the transfer-
ring 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 simul-
taneously occurs.

ii. Usage
successfully transferred after LLC frame transferring is ini-
tiated.
transferring completion from PS user plane, if the transfer-
ring succeeds, then the counter increments.
iv. Unit
Times

via cell reselection
Description 1. V6.20.200a ~ V6.20.200e
If LLC frame transferring is supported, then this counter counts
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 reestablish-
ment in downlink within BSC.
Usage 1. V6.20.200a ~ V6.20.200e
This counter is used to find out the number of LLC frames suc-
cessfully 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 1. V6.20.200a ~ V6.20.200e
Point
transferring success from PS user plane, if the LLC frame trans-
ferring is due to cell reselection, then the counter increments.
2. V6.20.200f
When PS control plane processes the downlink TBF link estab-
lishment request sent from PS user plane, if the link estab-
lishment request is due to self-recovery in downlink, then the
counter increments.
Unit 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 down-
link TBFs are established simultaneously).
2. V6.20.200f
the number of successful self-recovered TBF link reestablish-
ments in downlink within BSC.
Usage 1. V6.20.200a ~ V6.20.200e
This counter is used to find out the number of LLC frames suc-
cessfully 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 1. V6.20.200a ~ V6.20.200e
Point
transferring success from PS user plane, if the LLC frame trans-
ferring is not due to cell reselection, then the counter incre-
ments.
2. V6.20.200f
When BSC receives the PIA_SEND_IND message from BTS, if
the downlink TBF establishment is due to downlink self-recov-
ered 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


tiated due to cell reselection.
transferring failure from PS user plane, if the LLC frame
transferring is due to cell reselection, then the counter in-
crements.
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
tiated 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

Chapter 28
GB Message Statistic
Table of Contents
Overview...................................................................... 1492
BSSGP level.................................................................. 1493
BSSGP level.................................................................. 1493
C901220003 Number of receiving RA-CAPABILITY mes-
sage ............................................................................ 1494
BSC ............................................................................. 1495
BSC ............................................................................. 1495
sent............................................................................. 1496
C901220007 Number of RA-CAPABILITY-UPDATE-ACK mes-
sage 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 Un-
known ......................................................................... 1507
C901220021 Number of Status messages sent with cell ser-
vice congestion ............................................................. 1507
C901220022 Number of status messages sent with protocol
error............................................................................ 1508
C901220023 Number of status messages sent with Processor
overload....................................................................... 1508

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 pro-
tocol error .................................................................... 1509
cessor overload ............................................................. 1509
C901220028 Number of DOWNLOAD-BSS-PFC messages sent
by BSC......................................................................... 1510
C901220029 Number of BVCCREATE-BSS-PFC messages re-
ceived 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 re-
ceived 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 re-
ceived 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 mes-
sages 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 transmis-
sion number of different PTP messages at Gb BSSGP level in
GPRS service (such as RA-CAPABILITY, RADIO-STATUS, DOWN-
LOAD-BSS-PFC).

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 This counter increments each time BSC sends a UL-UNITDATA
Point message. The measurement point is A, as shown in Figure 1498.
FIGURE 1498 MEASUREMENT POINT OF SUM OF UL UNITDATA MESSAGE

HANDLED AT BSSGP LEVEL
Unit 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 This counter increments each time BSC receives a “DL-UNITDATA”

FIGURE 1499 MEASUREMENT POINT OF SUM OF DL UNITDATA MESSAGE

Unit 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 When BSC receives a “RA-CAPABILITY” message, this counter in-
Point crements. The measurement point is A, as shown in Figure 1500.
FIGURE 1500 MEASUREMENT POINT OF NUMBER OF RA-CAPABILITY

MESSAGE RECEVIED
Unit Times

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 re-
ceiving this message by BSC.
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 When BSC receives a “PAGING CS” message, this counter incre-

FIGURE 1502 PTP CIRCUIT PAGING PROCESS
Unit Times
RA-CAPABILITY-UPDATE
message sent
Description BSC sends the RA-CAPABILITY-UPDATE message to SGSN to re-
quest for the current wireless capability of MS. This counter counts
the number of BSC's sending this message.
Measurement When BSC sends a “RA-CAPABILITY-UPDATE” message to SGSN,
Point this counter increments. The measurement point is A1, as shown
in Figure 1503.
FIGURE 1503 RA-CAPABILITY-UPDATE PROCESS
Unit Times

RA-CAPABILITY-UPDATE-
ACK message received
Description SGSN sends RA-CAPABILITY-UPDATE-ACK message to BSC, to in-
dicate current wireless capability of MS. This counter counts the
Measurement When BSC receives a “RA-CAPABILITY-UPDATE-ACK” message
Point 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 mes-
sage.
Measurement When BSC sends a “RADIO-STATUS” message to SGSN, this
Figure 1505.

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 ab-
normality occurs at radio interface. This counter counts the num-
ber of BSC's sending this message due to “Losing wireless associ-
ation with MS”.
sage.
Measurement When BSC sends a RADIO-STATUS message to SGSN due to “Los-
Point ing wireless association with MS”, this counter increments.
Unit Times

sent by BSC due to bad link
quality
ber of BSC's sending this message due to “bad link quality”.
sage.
Measurement When BSC sends a RADIO-STATUS message to SGSN due to “bad
Point link quality”, this counter increments.
Unit Times
sent by BSC due to cell
reselection command
ber of BSC's sending this message due to “cell reselection com-
mand”.
sage.
Measurement When BSC sends a RADIO-STATUS message to SGSN due to “cell
Point reselection command”, this counter increments.
Unit Times

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 num-
ber of BSC's sending this message.
Measurement When BSC sends a FLOW-CONTROL-BVC message, this counter
1506.
FIGURE 1506 FLOW-CONTROL-BVC PROCESS
Unit Times
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
counts the number of BSC's receiving this message.

Measurement When BSC receives a “FLOW-CONTROL-BVC-ACK” message, this

Point counter increments. The measurement point is A2, as shown in
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 When BSC sends the “FLOW-CONTROL-MS” message, this counter
1508.

FIGURE 1508 FLOW-CONTROL-MS PROCESS
Unit Times
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 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 When BSC sends the FLOW-CONTROL-PFC message, this counter
1510.

FIGURE 1510 FLOW-CONTROL-PFC PROCESS
Unit Times
FLOW-CONTROL-PFC-
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 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 abnormal-
ity occurs. This counter counts the number of BSC's sending this
message.
Measurement When BSC sends the STATUS message, this counter increments.

FIGURE 1512 STATUS PROCESS
Unit Times
status messages received
by BSC
Description SGSN sends the status message to BSC to indicate that abnormal-
ity occurs. This counter counts the number of BSC's receiving this
message.
Measurement When BSC receives the STATUS message, this counter increments.

Unit Times
status messages sent with
BVCI Unknown
message due to “BVCI Unknown”.
Measurement When BSC sends a "STATUS" message due to “BVCI Unknown”,
Point this counter increments.
Unit Times
Status messages sent with
cell service congestion
message due to “cell service congestion”.
Measurement When BSC sends a STATUS message due to “cell service conges-
Point tion”, this counter increments.

Unit Times
protocol error
message due to “protocol error”.
Measurement When BSC sends a STATUS message due to “protocol error”, this
Point counter increments.
Unit Times
Processor overload
Description BSC sends status message to SGSN, to indicate exception oc-
curred. This counter counts the number of sending this message
by BSC due to “processor overload”.
Measurement 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 oc-
curred. This counter counts the number of receiving this message
by BSC due to “BVCI Unknown”.
Measurement When BSC receives a STATUS message due to “BVCI Unknown”,
Unit Times

with cell service congestion
by BSC due to “cell service congestion”.
Measurement When BSC receives a STATUS message due to “cell service con-
Point gestion”, this counter increments.
Unit Times
with protocol error
by BSC due to “protocol error”.
Measurement When BSC receives a STATUS message due to “protocol error”, this
Unit Times
with processor overload
Measurement When BSC receives a STATUS message due to “processor over-
Point load”, this counter increments.
Unit Times

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 When BSC sends the “DOWNLOAD-BSS-PFC” message, this
Figure 1514.
FIGURE 1514 CREATE-BSS-PFC PROCESS
Unit Times

BVCCREATE-BSS-PFC
Description SGSN sends the CREATE-BSS-PFC message to request BSC to cre-
ate or modify a packet flow control context. This counter counts
the number of BSC's receiving this message.
Measurement 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-

text. This counter counts the number of BSC's sending this mes-
sage.
Measurement When BSC sends a CREATE-BSS-PFC-ACK message, this counter
1516.
Unit Times
CREATE-BSS-PFC-NACK
Description BSC sends the CREATE-BSS-PFC-NACK message to deny the re-
quest of SGSN creating or modifying a packet flow control context.
Measurement 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 When BSC sends the MODIFY-BSS-PFC message, this counter in-
Point crements. The measurement point is A1, as shown in Figure 1518.

FIGURE 1518 MODIFY-BSS-PFC PROCESS
Unit Times
MODIFY-BSS-PFC-ACK
Description SGSN sends the MODIFY-BSS-PFC-ACK message to BSC to con-
firm the modification of packet flow control context. This counter
Measurement 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 When BSC receives a DELETE-BSS-PFC message, this counter in-

FIGURE 1520 DELETE-BSS-PFC PROCESS
Unit Times
DELETE-BSS-PFC-ACK
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 When BSC sends a DELETE-BSS-PFC-ACK message, this counter
1521.

Unit Times
DELETE-BSS-PFC-REQ
PS-HANDOVER-REQUI
RED messages sent by BSC
Statistics object BSC
Description 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 measure-

FIGURE 1522 MEASUREMENT POINT OF NUMBER OF PS-HANDOVER-

REQUIRED MESSAGES SENT BY BSC
Unit Times
PS-HANDOVER-REQUIRE
D-ACK messages received
by BSC
Description 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 Times
PS-HANDOVER-REQUIRE
D-NACK messages received
by BSC
Description If SGSN receives the non-acknowledgement message for PS
handover request from BSC, then SGSN sends the PS-HAN-
DOVER-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


REQUIRED-NACK MESSAGES RECEIVED BY BSC
Unit Times
PS-HANDOVER-REQUEST
Description This counter counts the number of PS-HANDOVER-REQUEST mes-
sages received by BSC from SGSN. The counter increments when
BSC receives the PS-HANDOVER-REQUEST message. The mea-


REQUEST MESSAGES RECEIVED BY BSC
Unit Times
PS-HANDOVER-REQUES
T-ACK messages sent by
BSC
Description 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


REQUEST-ACK MESSAGES SENT BY BSC
Unit Times
PS-HANDOVER-REQUES
T-NACK messages sent by
BSC
Description 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 fail-
ure of creating MS or PS instance, sent by BSC. The counter incre-

ments when BSC sends the PS-HANDOVER-REQUEST-NACK mes-

sage. The measurement point is A3, as shown in Figure 1527.

REQUEST-NACK MESSAGES SENT BY BSC
Unit Times
PS-HANDOVER-COMPL
ETE messages sent by BSC
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. The counter increments when BSC sends the
PS-HANDOVER-REQUEST-COMPLETE message. The measure-

COMPLETE MESSAGES SENT BY BSC
Unit Times
PS-HANDOVER-CANCEL
Description 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-HAN-
DOVER-CANCEL message. The measurement point is A, as shown
in Figure 1529.


CANCEL MESSAGES SENT BY BSC
Unit Times
PS-HANDOVER-REQUEST
messages with Service
UTRAN CCO received by
BSC
Description 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 de-
codes the message to decide whether the message contains the
field Service UTRAN CCO. If the message contains the field, the
Figure 1530.


REQUEST MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Unit Times
C901220046 Number
of CREATE-BSS-PFC
BSC
Description 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 mes-
sage to decide whether the message contains the field Service
UTRAN CCO. If the message contains the field, the counter incre-

FIGURE 1531 MEASUREMENT POINT OF NUMBER OF CREATE-BSS-PFC

MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Unit Times


Chapter 29
TRX Measurement
Table of Contents
Overview...................................................................... 1531
C901230001 Number of intra-cell handover in at-
tempts ......................................................................... 1531
C901230002 Number of intra-cell handover ins suc-
cess............................................................................. 1532
C901230003 Number of Intra-BSC inter-cell handover in at-
tempts ......................................................................... 1532
C901230004 Number of Intra-BSC intra-cell handover ins
success ........................................................................ 1533
C901230005 Number of Intra-MSC inter-cell handover in at-
tempts ......................................................................... 1534
C901230006 Number of Intra-MSC inter-cell handover ins
success ........................................................................ 1535
C901230007 TCH busy time............................................ 1535
C901230008 Number of TCH seizures (including han-
dover) ......................................................................... 1536
C901230009 Number of call drops due to TCH LAPD break-
age.............................................................................. 1536
C901230010 Number of call drops due to TCH radio link fail-
ure .............................................................................. 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 (includ-
ing 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


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

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 car-
rier. 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, re-
ceiving quality, interference, and concentric circle, its source cell
is same as target cell. During intra-cell handover, first send CHAN-
NEL ACTIVATE message to target channel, and BTS responds CHANNEL
ACTIVATE ACK message.
Measurement During intra-cell handover, measurement point will be counted af-
Point ter BSC receives CHANNEL ACTIVATE ACK. The measurement point is A,
FIGURE 1532 - INTRA-CELL HANDOVER
Unit Times

intra-cell handover ins
success
Definition Number of intra-cell handover ins success.
Description During intra-cell handover, after target channel is successfully ac-
tivated, 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 During intra-cell handover, the measurement point will be counted
Point after receive ASSIGNMENT COMPLETE. The measurement point is A2, as
FIGURE 1533 - INTRA-CELL HANDOVER
Unit Times
C901230003 Number
of Intra-BSC inter-cell
handover in attempts
Definition Number of Intra-BSC inter-cell handover in attempts
Description During inter-cell handover controlled by BSC, source and target
cells are different cells under same BSC. During inter-cell han-
dover, first send CHANNEL ACTIVATE message to target channel.

Measurement During inter-cell handover controlled by BSC, measurement point

Point will be counted after BSC receives CHANNEL ACTIVATE ACK message.
FIGURE 1534 - INTER-CELL HANDOVER CONTROLLED BY BSC
Unit 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 mes-
sage of MS from target channel, inter-cell handover is successfully
completed.
Measurement During inter-cell handover controlled by BSC, measurement point
Point will be counted after BSC receives HANDOVER COMPLETE message. The

Unit Times
C901230005 Number
of Intra-MSC inter-cell
handover in attempts
Definition Number of Intra-MSC inter-cell handover in attempts
Description Inter-cell handover controlled by MSC is conducted after BSC re-
ceives HANDOVER REQUEST message from MSC. After BSC receives han-
dover request message, first send CHANNEL ACTIVATE to acquisition
target channel.
Measurement During inter-cell handover (incoming) controlled by MSC, mea-
Point surement point will be counted after BSC receives CHANNEL ACTIVATE
ACK. The measurement point is A1, as shown in Figure 1536.
Unit Times

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 COM-
PLETE message sent by MS, handover is successfully done.
Measurement During inter-cell handover controlled by MSC, measurement point
Point will be counted after BSC receives HANDOVER COMPLETE message from
MS. The measurement point is A2, as shown in Figure 1537.
Unit Times
C901230007 TCH busy time

Definition TCH busy time
Description 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

B, the number of MS seizing channel will be decremented after

accumulation.
Measurement There are 3 measurement points:
Point
� Accumulate while successfully acquire voice channel resource
� Accumulate while release voice channel resource
� Accumulate by regular measurement and acquisition
Unit Second
TCH seizures (including
handover)
Definition Number of TCH seizures (including handover)
Description The number of seizure voice channel on carrier, including TCH/F
and TCH/H. This can reflect the traffic busy degree of carrier.
Measurement Count while successfully acquire voice channel service.
Point
Unit Times

drops due to TCH LAPD
breakage
Definition Number of call drops due to TCH LAPD breakage.
Description When LAPD link is disconnected, the call on carrier will be in-
terrupted, and this counter will record call interruption condition
caused by disconnected LAPD.
Measurement Count while receive LAPD Disconnected message.
Point
Unit 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 Count while receiving radio link failure message. The measure-
Point ment 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 Number of TCH handover call drops.
Description During handover, if HANDOVER COMMAND or ASSIGNMENT COMMAND (intra-cell
handover) has been sent, but BSC doesn’t receive HANDOVER COMPLETE
message or ASSIGNMENT COMPLETE message during guard time, the
handover is failed and intra-cell handover and BSC controlled inter-
cell handover will be interrupted. This counter records the call
interruption condition caused by handover failure.
Measurement This counter will count at following cases:
Point
� When receiving T3013 timer timeout message. The measure-

FIGURE 1539 - INTER-CELL HANDOVER FAILURE
� When receiving T3107 timer timeout message. The measure-

ment point is A2, as shown in .Figure 1540.
FIGURE 1540 - INTRA-CELL HANDOVER FAILURE
Unit Times
TCH/F activation attempts
(including handover)
Definition Number of TCH/F activation attempts (including handover)
Description Count the number of originating CHANNEL ACTIVATE messages from
carrier TCH/F channel.
Measurement Count after BSC sends CHANNEL ACTIVATE message to BTS. The mea-
Point surement point is A1, as shown inFigure 1541.

FIGURE 1541 - CHANNEL ACTIVATION MEASUREMENT POINT
Unit 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 Count after BSC receives CHANNEL ACTIVATE ACK message. The mea-
Point surement point is A2, as shown inFigure 1542 .

Unit Times
Definition Number of TCH/F assignment attempts.
Description Count the number of sending ASSIGNMENT COMMAND by BSC while as-
signing TCH/F channel.
Measurement Count after BSC sends ASSIGNMENT COMMAND message to BTS. The
Point measurement point is A1, as shownFigure 1543.
FIGURE 1543 - TCH/F CHANNEL ASSIGNMENT MEASUREMENT POINT
Unit Times
Definition Number of TCH/F assignment success
Description When assign TCH/F channel, BSC sends ASSIGNMENT COMMAND mes-
sage to assignment channel, after BSC receives EST IND or ASSIGN-
MENT COMPLETE message, channel assignment is successful.
Measurement Count after BSC receives EST IND or ASSIGNMENT COMPLETE message.

Unit 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.
Point surement point is A1, as shown inFigure 1545.

Unit Times
Related Features � ZGO-01-01-001 Half Rate
� ZGO-03-02-005 Dynamic Half Rate Allocation
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.
Unit Times
TCH/H assignment attempts
Definition Number of TCH/H assignment attempts
Description Count the number of sending ASSIGNMENT COMMAND by BSC while as-
signing TCH/H channel.

Measurement Count after BSC sends ASSIGNMENT COMMAND message to BTS. The
Point measurement point is A1, as shown inFigure 1547 .
Unit Times
Definition Number of TCH/H assignment success
Description When assign TCH/H channel, BSC sends ASSIGNMENT COMMAND mes-
sage to assignment channel, after BSC receives EST IND or ASSIGN-
MENT COMPLETE message, channel assignment is successful.
Measurement Count after BSC receives EST IND or ASSIGNMENT COMPLETE message.

Unit
C901230020 SDCCH busy

time
Definition SDCCH busy time
Description 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 mea-
sured 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 There are 3 measurement points as follows.
Point
� Accumulate while successfully acquire SDCCH channel re-
source
� Accumulate while release SDCCH channel resource
� Accumulate by regular measurement and acquisition
Unit Times

attempts for SDCCH
Definition Number of attempts for SDCCH
Description Count the number of successful and failed SDCCH application dur-
ing assignment and handover.
Measurement Count after BSC applying for SDCCH is successful or failed.
Point
Unit Times
SDCCH call drops
Definition Number of SDCCH call drops
Description During assignment and handover, ASSIGNMENT COMPLETE or HANDOVER
COMPLETE is not received aftersend ASSIGNMENT COMMAND or HANDOVER
COMMAND message. After T3103 or T3107 timer times out, it is con-
sidered as SDCCH failure, see Figure 1549 andFigure 1550.
FIGURE 1549 - INTER-CELL HANDOVER FAILURE

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 This counter will count at following cases:
Point
� 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.
Unit 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.
Unit Times
SDCCH activation success
Definition Number of SDCCH activation success (including handover)
Description Count the number of successful activation from carrier SDCCH
channel.

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 Count after BSC sends IMMEDIATE ASSIGNMENT message or ASSIGNMENT
Point COMMAND to BTS. The measurement point is A1, as shown in Figure
1554.
FIGURE 1554 - CHANNEL ASSIGNMENT MEASUREMENT POINT

Unit Times
SDCCH assignment success
Definition Number of SDCCH assignment success
Description When assign SDCCH channel, BSC sends IMMEDIATE ASSIGNMENT mes-
sage or ASSIGNMENT COMMAND message to assignment channel, after
BSC receives EST IND (CM SERV REQ), channel assignment is success-
ful.
Measurement Count after BSC receives EST IND (CM SERV REQ) message. The mea-
Point surement point is A2, as shown in Figure 1555.
FIGURE 1555 - CHANNEL ASSIGNMENT MEASUREMENT POINT
Unit Times
Definition Number of samples with UL RQ = 0
per 480 ms.

This measurement value is the sample number with UL RQ=0 in

measurement report.

BY BTS
Unit Times
measurement report.

BY BTS
Unit Times

measurement report.

BY BTS
Unit Times
measurement report.

BY BTS

Unit Times
measurement report.

BY BTS
Unit Times
measurement report.


BY BTS
Unit Times
measurement report.

BY BTS
Unit Times
measurement report.



BTS
Unit Times
Definition Number of samples with DL RQ = 0
measurement report.

BY BTS
Unit Times


measurement report.

BY BTS
Unit Times
measurement report.

BY BTS
Unit Times

measurement report.

BY BTS
Unit Times
measurement report.

BY BTS

Unit Times
measurement report.

BY BTS
Unit Times
measurement report.


BY BTS
Unit Times
measurement report.

BY BTS
Unit Times

of idle TCH/Fs with
interference band 0

Description 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.
Measurement Count when regularly query database.
Point
Unit Times

of idle TCH/Fs with
interference band 1
Description This measurement value is idle TCH/F number when interference
band is 1 in carrier.
Point
Unit Times

of idle TCH/Fs with
interference band 2
Point
Unit Times


of idle TCH/Fs with
interference band 3
Point
Unit Times

of idle TCH/Fs with
interference band 4
Point
Unit Times

of idle TCH/Fs with
interference band 5
Point
Unit Times


of idle TCH/Hs with
interference band 0
Definition Mean number of idle TCH/Hs with interference band 0
Description This measurement value is idle TCH/H number when interference
Point
Unit Times

of idle TCH/Hs with
interference band 1
Point
Unit Times

of idle TCH/Hs with
interference band 2
Point

Unit Times

of idle TCH/Hs with
interference band 3
Point
Unit Times

of idle TCH/Hs with
interference band 4
Point
Unit Times


of idle TCH/Hs with
interference band 5
Point
Unit Times

of idle SDCCHs with
interference band 0
Description This measurement value is idle SDCCH number when interference
Point
Unit Times

of idle SDCCHs with
interference band 1
Point
Unit Times


of idle SDCCHs with
interference band 2
Point
Unit Times

of idle SDCCHs with
interference band 3
Point
Unit Times

of idle SDCCHs with
interference band 4
Point
Unit Times


of idle SDCCHs with
interference band 5
Point
Unit Times
TRX poweroff
Definition Number of TRX power off.
Description This counter counts the number of TRX smart power off, excluding
normal POWER OFF.
Measurement This counter increments during smart power on.
Point
Unit Times
Related Features ZGO-04-04-002 Intelligent TRX Shutdown
TRX poweroff
Definition Duration of TRX power off.
Description This counter counts the duration of TRX power off.
Measurement This counter increments during smart power on.
Point
Unit Times
Related Features ZGO-04-04-002 Intelligent TRX Shutdown

Description Enable the function of reporting voice quality information, and
count the number of error frames of voice version 1 in the mea-
surement report received on the FR channel.
Measurement The counter counts when the measurement report (preprocess-
Point ing measurement report or enhanced measurement report) is re-
ceived.
Unit Times

count the number of voice frames of voice version 1 in the mea-
ceived.
Unit Times
ceived.
Unit Times


ceived.
Unit Times
ceived.
Unit Times

ceived.
Unit Times

surement report received on the HR channel.
ceived.
Unit Times

ceived.
Unit Times
ceived.
Unit Times


ceived.
Unit Times


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 sam-
ples ............................................................................. 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 sam-
ples ............................................................................. 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 in-
terference 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

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 rea-
sons ............................................................................ 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 environ-
ment 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 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 After BSC receives the measurement report from BTS, if UL RQ in
Point 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 After BSC receives the measurement report from BTS, if UL RQ
Point 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 Total value of UL RQ
Description This counter counts the total value of UL RQ of a timeslot of a cell
in the measurement report.

Usage This counter is used to find out the Total value of UL RQ in a times-
lot of a cell. It is one of the parameters that evaluate timeslot radio
environment.
Measurement After BSC receives the measurement report from BTS, the counter
Point 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 The counter increments after BSC receives the measurement re-
Point port from BTS. The measurement point is A, as shown in Figure
1575.
Unit 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 After BSC receives the measurement report from BTS, if DL RQ in
Point 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 After BSC receives the measurement report from BTS, if DL RQ
Point in the report is less than the value in the counter, the DL RQ in
Figure 1577.

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 times-
lot of a cell. It is one of the parameters that evaluate timeslot radio
environment.
Point accumulates DL RQ value for relevant timeslot. The measurement
Unit NA
scans of DL RQ
Definition Number of scans of DL RQ
Description 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.
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 After BSC receives the measurement report from BTS, if received
Point 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

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 After BSC receives the measurement report from BTS, if the value
Point 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 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.
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.
1583.
Unit Times

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 After BSC receives the measurement report from BTS, if DL recep-
Point tion strength in the report is bigger than the value in the counter,
the DL reception strength in the counter is replaced. The mea-
Unit dBm
C901240014 Minimum
value of received DL signal
strength
Definition 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 After BSC receives the measurement report from BTS, if DL recep-
Point tion strength in the report is less than the value in the counter, the
DL reception strength in the counter is replaced. The measure-

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
Point accumulates DL reception strength value for relevant timeslot. The
Unit dBm
samples
Definition Number of received DL signal strength samples

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
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
Point accumulates MS power value for relevant timeslot. The measure-
Unit 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 transmit-
ting 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
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.
Point accumulates BTS power value for relevant timeslot. The measure-

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
1591.
Unit dBm
immediate assignment
failure
Definition 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 After BSC sent immediate assignment to MS, if access Timer over-
Point times, the counter increments in relevant timeslot. The measure-
In the waiting state, case release caused by any reason, leads
immediate assignment failure, then the counter increments in rel-
evant 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 times-
lot in a cell. It is one of the parameters that evaluate timeslot radio
environment.
Measurement After BSC sent assignment to MS, if access Timer overtimes, the
Point counter increments in relevant timeslot. The measurement point
In the waiting state, case release caused by any reason, leads as-
signment failure, then the counter increments in relevant timeslot.

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 After BSC sent handover to MS, if access Timer overtimes, the
Point 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 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 times-
lot radio environment.
Measurement When BSC received resource indication from BTS updating inter-
Point ference band, if interference band reported is bigger than the value
in the counter, the value in the counter is replaced. The measure-
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
Point ference band, if interference band reported is less than the value
in the counter, the value in the counter is replaced. The measure-

Unit NA
C901240026 Interference
value
Definition Total value of interference
Description This counter counts the total value of interference band in a times-
lot in a cell.
Usage This counter is used to find out the total value of interference band
Point ference band, the counter accumulates interference value for rel-
evant timeslot. The measurement point is A, as shown in Figure
1597.
Unit 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 The counter increments in relevant timeslot after BSC receives re-
Point source indication from BTS updating interference band. The mea-
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 The counter increments in relevant timeslot after BSC receives ra-
Point dio link failure from BTS. The measurement point is A, as shown
in Figure 1599.

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 times-
lot 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 times-
lot in a cell. It is one of the parameters that evaluate timeslot radio
environment.
Measurement When BSC receives measurement report from BTS, calculate the
Point 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 Minimum value of path balance

Description This counter counts the Minimum value of path balance in a times-
lot 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 times-
lot in a cell. It is one of the parameters that evaluate timeslot
radio environment.
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.
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

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 sam-
pling in a timeslot in a cell. It is one of the parameters that eval-
uate timeslot radio environment.
Measurement The counter increments in relevant timeslot when BSC receives
Point measurement point from BTS and calculates path balance. The
Unit Times
C901240033 Value of UL
loss
Definition 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.
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 Number of regular scanning and sampling of UL loss
Description 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.
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 Total value of DL loss
Description This counter counts the maximum of DL loss in a timeslot in a cell.

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.
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 Number of regular scanning and sampling of DL loss
Description 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.
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 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 � The counter counts when BSC receives the CONNectiOn FAIL-
Point ure INDicatiOn message at Abis interface on SDCCH. The mea-
FIGURE 1608 CALL DROP DUE TO RADIO LINK FAILURE DURING

� The counter counts when BSC receives the CONNectiOn FAIL-

ure INDicatiOn message at Abis interface on TCH. The mea-


ASSIGNMENT PROCESS
Unit Times
drops due to the bad quality
of DL receive
Definition 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.
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.




ASSIGNMENT PROCESS
Unit Times
drops due to the low electric
level of UL
Definition Number of drops due to the low electric level of UL
call drop occurs. If the problem is caused by low uplink receiving
level, the counter increments.
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.




ASSIGNMENT PROCESS
Unit Times
drops due to the low electric
level of DL
Definition 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.
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.




ASSIGNMENT PROCESS
Unit Times
drops due to the TA too far
Definition Number of drops due to the TA too far
call drop occurs. If the problem is caused by TA being too far, the
counter increments.
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.





ASSIGNMENT PROCESS
Unit Times
drops due to the other radio
reasons
Definition 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.

timeslot due to radio link failure which is caused by other radio
problems. It is one of the radio parameters that evaluate the
timeslot.

� counter counts when BSC receives the CONNectiOn FAILure IN-

DicatiOn message at Abis interface on TCH. The measurement


ASSIGNMENT PROCESS
Unit Times
C901240043 The valid time

of the used voice channel
Definition 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 When BSC receives the measurement report from BTS, the counter
Point 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 FROM BTS
Unit 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 parame-
ters that evaluate the timeslot.
Measurement When BSC receives the CHANNEL ACTIVATE ACK message, the
Figure 1621.
FIGURE 1621 MEASUREMENT POINT WHEN CHANNEL IS ACTIVATED
Unit Times


Chapter 31
SDCCH Measurement
Table of Contents
Overview...................................................................... 1610
C901250005 Number of SDCCH seizure success for Han-
dover........................................................................... 1611
C901250007 Number of SDCCH allocation attempts for As-
signment...................................................................... 1613
C901250010 Number of SDCCH allocation attempts for han-
dover........................................................................... 1614
C901250011 Number of SDCCH allocation success for han-
dover........................................................................... 1616
C901250012 Number of SDCCH allocation failure for han-
dover........................................................................... 1617
C901250016 Number of SDCCH handover failure ............... 1618
C901250017 Number of SDCCH handover success ............. 1620
C901250018 Number of SDCCH handover failure with Recon-
nection ........................................................................ 1622
C901250019 Number of SDCCH handover failure without Re-
connection.................................................................... 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 (emer-
gency call).................................................................... 1632
(emergency call) ........................................................... 1633
(emergency call) ........................................................... 1634
(LOC) .......................................................................... 1635
(LOC) .......................................................................... 1636


(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 im-
mediate assignment is shown in Figure 1622.
FIGURE 1622 THE PROCESS OF IMMEDIATE ASSIGNMENT
The Measurement point Of SDCCH counters in the process of in-

ternal handover (like intra-cell handover) is shown in Figure 1623.

Chapter 31 SDCCH Measurement
FIGURE 1623 THE PROCESS OF INTERNAL HANDOVER (LIKE INTRA-CELL

HANDOVER)
The Measurement point Of SDCCH counters in the process of ex-

ternal 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

Description SDCCH allocation attempt is triggered by the channel request mes-

sage RADIO_APPLY from other channel instances. BSC attempts
to allocate SDCCH after receiving the message. If SDCCH alloca-
tion 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 applica-
tion response shows transceiver is faulty, the three counters do
not change.
Usage This counter records the number of SDCCH seizure success for
handover.
Measurement When BSC requesting for SDCCH (due to handover) is completed
Point 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.

HANDOVER)

Unit Times
Related Features � ZGB-03-02-003 Dynamic Configuration of SDCCH
� ZGO-02-02-004 SDCCH/SDCCH Handover
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 After BSC responds the channel request message to allocate and
sage to BTS to activate this SDCCH channel. If the activation suc-
from BTS), this counter and C900060008 increment simultane-
ously. Otherwise, if the channel could not be activated due to
receiving channel activation failure message, incorrect channel ac-
tivation response message, T9103 timeout, channel instance be-
ing released or channel being released forcibly, this counter and
C900060009 increment simultaneously.
Measurement BSC activates SDCCH due to assignment (C900060008+C900060
Point 009). The measurement point is A2 as shown in Figure 1627.

FIGURE 1627 THE PROCESS OF IMMEDIATE ASSIGNMENT
Unit Times
SDCCH allocation attempts
for handover
Definition Number of SDCCH allocation attempts for handover
from BTS), this counter and C901250011 increment simultane-
ously. Otherwise, if the channel could not be activated due to
receiving channel activation failure message, incorrect channel ac-
tivation response message, T9103 timeout, channel instance be-
ing 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 BSC activates SDCCH due to handover (C901250011+C90125001
Point 2). The measurement point is B2 as shown in Figure 1628and C2


HANDOVER)
Unit Times

SDCCH allocation success
for handover
Definition Number of SDCCH allocation success for handover
from BTS), it means SDCCH allocation succeeds completely and
Usage This counter records the number of SDCCH allocations success for
handover.
Measurement When BSC receives the CHL_ACT_ACK message from BTS due to
Point handover. The measurement point is B2 as shown in Figure 1630,
and C2 as shown in Figure 1631.

HANDOVER)

Unit Times
SDCCH allocation failure for
handover
Definition Number of SDCCH allocation failure for handover
sage to BTS to activate this SDCCH channel. If the channel could
not be activated due to receiving channel activation failure mes-
sage, incorrect channel activation response message, T9103 time-
out, 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 BSC activates SDCCH for handover, but encounters the following
Point situation: receives channel activation failed message, channel ac-
tivation response message is incorrect, T9103 is time-out, channel
instance is released, or channel is released forcibly. The measure-
ment point is B2 as shown in Figure 1632 and C2 as shown in
Figure 1633.


HANDOVER)
Unit Times
SDCCH handover failure
Definition 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. Other-
wise, handover fails and same time BSC has not received any fail-
ure message, this counter and C901250019 increment simultane-
ously.
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 When BSC receives ASS_COM message (intra-cell handover),
Point 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.

HANDOVER)

Unit Times
SDCCH handover success
Definition 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 SD-
CCH newly allocated in the process of handover.
Measurement BSC receives ASS_COM message (intra-cell handover) or HO_COM
Point message (inter-cell handover). The measurement point is B3 as
shown in Figure 1636and C3 as shown in Figure 1637.


HANDOVER)
Unit Times

with Reconnection
Definition Number of SDCCH handover failure with Reconnection
Description In the process of handover, when BSC receives ASSIGN_FAIL mes-
sage 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 re-
ceives handover failure message.
Measurement BSC receives HO_FAILURE message.
Point
Unit Times
without Reconnection
Definition Number of SDCCH handover failure without Reconnection
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 When BSC has not received any HO_FAILURE message, time-out
Point message, channel instance is released, or channel is released
forcibly.
Unit Times

C901250020 Number
of SDCCH assignment
attempts (MOC)
Description After BSC responds to the channel request due to MOC and suc-
cessfully allocates and activates SDCCH, BSC sends the immediate
assignment message IMM_ASS to MS to notify it to use the chan-
nel. 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 time-
out, 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 The counter counts when BSC receives the EST_IND message
Point or the assignment completion message, or T3101 is timeout
(C901250021+C901250022). The measurement point is A3, as
Unit Times

C901250021 Number
of successful SDCCH
assignments (MOC)
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 measure-
FIGURE 1639 NUMBER OF SUCCESSFUL SDCCH ASSIGNMENTS (MOC)
Measurement The counter counts when BSC correctly receives the EST_IND mes-
Point sage or the assignment completion message.
Unit Times

unsuccessful SDCCH
assignments (MOC)
If BSC receives the EST_IND message incorrectly or T3101 is time-
out, it indicates that SDCCH assignment fails, and this counter ac-
cumulates.
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 The counter counts when BSC receives the EST_IND message in-
Point correctly or T3101 is timeout. The measurement point is A3, as
FIGURE 1640 NUMBER OF UNSUCCESSFUL SDCCH ASSIGNMENTS (MOC)
Unit Times

C901250023 Number
of SDCCH assignment
attempts (MTC)
Description After BSC responds to the channel request due to MTC and suc-
Usage When the channel access is due to MTC, this counter is used to
FIGURE 1641 NUMBER OF SDCCH ASSIGNMENT ATTEMPTS (MTC)
Unit Times

C901250024 Number
of successful SDCCH
assignments (MTC)
Usage When the channel access is due to MTC, this counter is used to find
FIGURE 1642 NUMBER OF SUCCESSFUL SDCCH ASSIGNMENTS (MTC)

Unit Times

unsuccessful SDCCH
assignments (MTC)
cumulates.
Usage When the channel access is due to MTC, this counter is used to find
FIGURE 1643 NUMBER OF UNSUCCESSFUL SDCCH ASSIGNMENTS (MTC)
Unit Times

SDCCH assignment attem
pts (call re-establishment)
Description After BSC responds to the channel request due to call reestablish-
ment 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 mak-
ing 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).
FIGURE 1644 NUMBER OF SDCCH ASSIGNMENT ATTEMPTS (CALL

RE-ESTABLISHMENT)

Unit Times
C901250027 Number
of successful SDCCH
assignments (call
re-establishment)
counter is used to find out the number of MS's successfully ac-
cessing 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 SDCCH ASSIGNMENTS (CALL

RE-ESTABLISHMENT)

Unit Times
unsuccessful SDCCH
assignments (call
re-establishment)
cumulates.
counter is used to find out the number of MS's failing in accessing
the allocated SDCCH after BSC sends the IMM_ASS message.

FIGURE 1646 NUMBER OF UNSUCCESSFUL SDCCH ASSIGNMENTS (CALL

RE-ESTABLISHMENT)
Unit 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).

FIGURE 1647 NUMBER OF SDCCH ASSIGNMENT ATTEMPTS (EMERGENCY

CALL)
Unit Times
C901250030 Number
of successful SDCCH
assignments (emergency
call)
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-

responding SDCCH after BSC sends the IMM_ASS message. The

FIGURE 1648 NUMBER OF SUCCESSFUL SDCCH ASSIGNMENTS (EMERGENCY

CALL)

Unit Times
unsuccessful SDCCH
assignments (emergency
call)
cumulates.

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.
FIGURE 1649 NUMBER OF UNSUCCESSFUL SDCCH ASSIGNMENTS

(EMERGENCY CALL)
Unit Times
C901250032 Number
of SDCCH assignment
attempts (LOC)
Description After BSC responds to the channel request due to LOC and success-
fully allocates and activates SDCCH, BSC sends the immediate as-
signment 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 LOC, this counter is used to
FIGURE 1650 NUMBER OF SDCCH ASSIGNMENT ATTEMPTS (LOC)
Unit Times
C901250033 Number
of successful SDCCH
assignments (LOC)
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)

Unit Times
unsuccessful SDCCH
assignments (LOC)
message to BSC.


cumulates.
Usage When the channel access is due to LOC, this counter is used to find
FIGURE 1652 NUMBER OF UNSUCCESSFUL SDCCH ASSIGNMENTS (LOC)
Unit Times
C901250035 Number
of SDCCH assignment
attempts (other cause)
Description 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 mes-
sage IMM_ASS to MS to notify it to use the channel. After MS
receives the message, it sends the SABM frame to BTS via SD-
CCH. 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).
FIGURE 1653 NUMBER OF SDCCH ASSIGNMENT ATTEMPTS (OTHER CAUSE)
Unit Times
C901250036 Number
of successful SDCCH
assignments (other cause)


to BSC.
of MS's successfully accessing the corresponding SDCCH after BSC
sends the IMM_ASS message. The measurement point is A3, as
FIGURE 1654 NUMBER OF SUCCESSFUL SDCCH ASSIGNMENTS (OTHER

CAUSE)

Unit Times
unsuccessful SDCCH
assignments (other cause)


to BSC.
cumulates.
of MS's failing in accessing the allocated SDCCH after BSC sends
the IMM_ASS message.
FIGURE 1655 NUMBER OF UNSUCCESSFUL SDCCH ASSIGNMENTS (OTHER

CAUSE)
Unit Times
C901250038 Count of USSD

attempts to connect
Description This counter counts the number of attempts of connecting USSD
service.

Unit Times
C901250039 Average
dialoge time of USSD
services
Description This counter counts the average conversation time of USSD ser-
vice.
Unit Second
C901250040 Dialog counts

of USSD services
Description This counter counts the number of conversations of USSD service.
Unit Times

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 at-
tempt .......................................................................... 1660
C901260017 Number of signaling TCH/F handover suc-
cess............................................................................. 1663
C901260018 Number of signaling TCH/F handover failure with
reconnection ................................................................. 1665
without reconnection...................................................... 1667
C901260021 Number of voice TCH/F seizure success for as-
signment...................................................................... 1668
C901260024 Number of voice TCH/F seizure success for han-
dover........................................................................... 1669
C901260026 Number of TCH/F allocation attempts for assign-
ment (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 assign-
assignment (speech version 3) ........................................ 1685
C901260062 Number of voice TCH/F assignment attempts by
BSC ............................................................................. 1691

C901260065 Number of voice TCH/F handover at-

tempts ......................................................................... 1692
C901260067 Number of Voice TCH/F handover failure......... 1695
C901260068 Number of Voice TCH/F handover failure mes-
sages do not received by BSC ......................................... 1697
C901260070 Number of data TCH/F seizure success for as-
signment...................................................................... 1698
C901260073 Number of data TCH/F seizure success for han-
dover........................................................................... 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 at-
tempts ......................................................................... 1708
C901260090 Number of data TCH/F handover at-
tempts ......................................................................... 1709
C901260092 Number of data TCH/F handover failure ......... 1712
C901260093 Number of data TCH/F handover failure mes-
assignment due to TIPB connection failure (Speech version
1)................................................................................ 1715
C901260095 Number of data TCH/F allocation failure for as-
signment due to Resource request to iTC failure (Speech ver-
sion 1) ......................................................................... 1716
handover due to TIPB connection failure (Speech version
1)................................................................................ 1717
C901260097 Number of data TCH/F allocation failure for han-
dover due to Resource request to iTC failure (Speech version
1)................................................................................ 1718
2)................................................................................ 1719
sion 2) ......................................................................... 1720
2)................................................................................ 1721
2)................................................................................ 1723
3)................................................................................ 1724
sion 3) ......................................................................... 1725
3)................................................................................ 1726
3)................................................................................ 1728

Chapter 32 TCH/F Measurement
C901260106 Number of TCH/F allocation failure due to re-

quest 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
quest 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
quest AIPB resource failure for assignment (data).............. 1747
quest UDP port failure for assignment (data)..................... 1748
connection failure for assignment (data) ........................... 1748
quest AIPB resource failure for handover (data)................. 1749
quest UDP port failure for handover (data)........................ 1750
connection failure for handover (data).............................. 1751
C901260130 Number of assign TCH/F release by forced han-
dover to forced handover source...................................... 1752

C901260131 Number of assign TCH/F release by forced han-

dover to queuing user .................................................... 1752
C901260132 Number of restore TCH/F release by forced han-
dover 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 re-
lease to queuing user..................................................... 1754
C901260135 Number of restore TCH/F release by forced re-
lease to DBS ................................................................. 1754
assignment (cause:Abis) ................................................ 1755
handover (cause:Abis) ................................................... 1756
signment (cause:Abis) ................................................... 1756
dover (cause:Abis ) ....................................................... 1757
ment (cause:Abis) ......................................................... 1757
dover (cause:Abis) ........................................................ 1758
assignment (cause:radio resource) .................................. 1758
handover (cause:radio resource) ..................................... 1759
signment (cause:radio resource) ..................................... 1759
dover (cause:radio resource) .......................................... 1760
ment (cause:radio resource) ........................................... 1760
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 be-
ing 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 pri-
ority users (TCH/F) ........................................................ 1772

Overview
In GSM BSC signaling system, allocation and usage of TCH/F chan-
nel mainly exist in assignment and handover flow, where assign-
ment flow includes immediate assignment and common assign-
ment; handover flow includes internal and external handover.
For the measurement positions of TCH/F counter in immediate as-
signment flow, see Figure 1656.
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)

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 HANDOVER (LIKE INTRA-CELL HANDOVER) FLOW

(INTERNAL TC)

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)

FIGURE 1662 EXTERNAL HANDOVER FLOW (EXTERNAL TC)
Definition Number of signaling TCH/F seizure success for assignment
Description 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 BSC successfully applies for channel (due to assignment, used for
Point signaling channel) and does successful assignment. The measure-
ment point is A1, as shown in Figure 1663

Unit Times
success for handover
Definition Number of signaling TCH/F seizure success for handover
Description 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 cor-
responding resource occurs.
Measurement BSC successfully applies for channel (due to handover, used for
Point 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)



Unit Times
Related Features � ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
� ZGO-03-02-011 Channel Repacking
Definition Number of signaling TCH/F allocation attempts for assignment
Description This counter counts the number of signaling TCH/F allocation at-
tempts 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 accumu-
late simultaneously; reversely, if channel activation failure due to
receive channel activation failure message, incorrect channel acti-
vation response message, timer T9103 timeout, channel instance
released, channel force-released, this counter and C900060015
accumulate simultaneously.
Measurement After BSC activates TCH/F (due to assignment, used for signaling
Point channel), this counter accumulates when CHL_ACT_ACK message
sent by BTS is received correctly, channel activation failure mes-
sage is received, channel activation response message is not cor-
rect, timer T9103 times out, channel instance is released, or chan-
nel is forcibly released. (C900060014+C900060015) The mea-

Unit Times
Definition Number of signaling TCH/F allocation attempts for handover
Description This counter counts the number of signaling TCH/F allocation at-
tempts during handover of signaling channel, including the number
of allocation success (C901260011) and failure (C900060016).
After BSC responds channel request message allocation and suc-
cessfully seizes TCH/F channel, BSC sends channel activation mes-
sage CHL_ACT to BTS to activate this TCH/F. if activation success,
TCH/F allocation success, this counter and C901260011 accumu-
late simultaneously; reversely, if channel activation failure due to
receive channel activation failure message, incorrect channel acti-
vation response message, timer T9103 timeout, channel instance
released, channel force-released, this counter and C900060016
Measurement After BSC activates TCH/F (due to handover, used for signaling
Point channel), this counter accumulates when CHL_ACT_ACK message
sent by BTS is received correctly, channel activation failure mes-
sage is received, channel activation response message is not cor-
rect, timer T9103 times out, channel instance is released, or chan-
nel is forcibly released. (C901260011+C900060016) The mea-
surement points are C3 and D3, as shown in Figure 1669, Figure
1670,Figure 1671 and Figure 1672.


(INTERNAL TC)


Unit Times

Definition Number of signaling TCH/F allocation success for handover
Description This counter counts the number of signaling TCH/F allocation suc-
cess during handover of signaling channel.
cessfully 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 This counter accumulates when CHL_ACT_ACK correctly receives
Point 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)



Unit Times
Definition Number of signaling TCH/F assignment attempts for assignment
Description 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 assign-
ment, 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 can’t be received
within specified duration, this assignment is failed.
Measurement For immediate assignment, this counter accumulates when BSC
Point correctly receives EST_IND message or T3101 times out (that is,
MS access notice can’t be received within specified duration). The

Unit Times
signaling TCH/F handover
attempt
Definition Number of signaling TCH/F handover attempt
Description 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 chan-
nel; this counter and C901260018 accumulate when handover fail-
ure message is received; this counter and C901260019 accumu-
late 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, han-
dover success symbolic message is HO_COM. For intra-cell and in-
ter-cell handover, this counter accumulates on the basis of source
instance; for external handover, this counter accumulates on tar-
get instance because source instance doesn’t at this BSC side.
Measurement This counter accumulates when BSC detects handover success
Point message, ASS_COM/HO_COM, sent from reallocated TCH/F chan-
nel, 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)


Unit Times

success
Definition Number of signaling TCH/F handover success
Description his counter counts the number of signaling TCH/F handover suc-
cess 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, han-
dover success symbolic message is HO_COM. For intra-cell and in-
ter-cell handover, this counter accumulates on the basis of source
instance; for external handover, this counter accumulates on tar-
get instance because source instance doesn’t at this BSC side.
Measurement BSC receives ASS_COM or HO_COM message. The measurement
Point points are C4 and D4, as shown in Figure 1682, Figure 1683, Figure
1684, and Figure 1685.

(INTERNAL TC)



Unit Times
failure with reconnection
Definition Number of signaling TCH/F handover failure with reconnection
Description This counter counts the number of signaling TCH/F handover fail-
ure 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 pre-
vious channel.
Measurement BSC receives ASS_FAIL or HO_FAIL message. The measurement
Point points are C4 and D4, as shown in Figure 1686, Figure 1687.

FIGURE 1686 INTERNAL HANDOVER (INTERNAL TC INTRA-CELL HANDOVER)

FAILURE FLOW 1
FIGURE 1687 EXTERNAL HANDOVER FAILURE FLOW (INTERNAL TC)
Unit 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 fail-
ure without reconnection during handover of signaling channel.
This counter accumulates when MS handover fails or it can’t re-
turn to previous channel after BSC sends assignment command or
handover command to MS.
Measurement This counter accumulates when BSC receives messages of excep-
Point tion, released instance, force-released instance, or timer timeout.
The measurement point is C4, as shown in Figure 1688, Figure
1689.

FAILURE FLOW 2

FAILURE FLOW 3
Unit Times

C901260021 Number
Definition Number of voice TCH/F seizure success for assignment
Description This counter counts the number of voice TCH/F seizure success
during assignment of signaling channel.
Point voice channel) and does successful seizure, or BSC receives inter-
nal waiting resource effective message. The measurement point
is B1, as shown in Figure 1690, Figure 1691.

Unit Times
� ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
C901260024 Number
Definition Number of voice TCH/F seizure success for handover
Description This counter counts the number of voice TCH/F seizure success
Point voice channel) and does successful seizure, or BSC receives inter-
nal waiting resource effective message. The measurement points
are C1 and D1, as shown in Figure 1692, Figure 1693, Figure 1694,
and Figure 1695.


(INTERNAL TC)


Unit Times

TCH/F allocation attempts
version 1)
Definition Number of TCH/F allocation attempts for assignment (speech ver-
sion 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).
cessfully 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 This counter accumulates when allocation succeeds or fails (due
Point to assignment, used for voice channel, using speech version 1).
The measurement points are B2 and B3, as shown in Figure 1696,
Figure 1697.

Unit Times
Related Features � ZGB-01-01-001 Full Rate (FR) Speech Codec
� ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
by BSC for handover
(speech version 1)
Definition Number of TCH/F allocation attempts by BSC for handover (speech
version 1)
during handover of voice channel (for speech version 1), includ-
ing the number of allocation success (C901260033) and failure
(C900060156+C900060157+C900060158+C900060159).
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.


(INTERNAL TC)


Unit Times

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 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)



Unit Times
version 2)
sion 2)
(C900060141+C900060142+C900060143+C900060144).


Figure 1707.
Unit Times

by BSC for handover
(speech version 2)
version 2)
(C900060160+C900060161+C900060162+C900060163).

(INTERNAL TC)



Unit Times
version 2)
Definition Number of TCH/F allocation success by BSC for handover (speech
version 2)


(INTERNAL TC)


Unit Times

by BSC for assignment
(speech version 3)
sion 3)
(C900060027+C900060145+C900060146+C900060147).
Figure 1717.

Unit Times
� ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
by BSC for handover
(speech version 3)
version 3)
(C900060164+C900060165+C900060166+C900060167).


(INTERNAL TC)


Unit Times

version 3)
Definition Number of TCH/F allocation success by BSC for handover (speech
version 3)

(INTERNAL TC)



Unit Times
attempts by BSC
Definition Number of voice TCH/F assignment attempts by BSC
Description This counter counts the number of voice TCH/F assignment at-
tempts when assigning TCH/F channel as voice channel, includ-
ing 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 can’t
be received within specified duration, that is, this assignment
failed at this time.
Measurement For the assignment from port A, BSC receives the messages of
Point 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.

Unit Times
voice TCH/F handover
attempts
Definition Number of voice TCH/F handover attempts
Description 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 dura-
tion, 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 can’t receive HO_FAIL-
URE, 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 doesn’t
at this BSC side.
Measurement This counter accumulates when BSC receives ASS_COM/HO_COM
Point message, ASS_FAIL/HO_FAIL message, or messages of exception,
released instance, force-released instance, or timer timeout. The

(INTERNAL TC)



Unit Times
failure
Definition Number of Voice TCH/F handover failure
Description 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
vious channel.


FAILURE FLOW 1
Unit 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 can’t return to
source channel after BSC sends assignment / handover command
to MS.
Point tion, 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

FAILURE FLOW 3

Unit Times
data TCH/F seizure success
for assignment
Definition Number of data TCH/F seizure success for assignment
Description This counter counts the number of data TCH/F seizure success dur-
ing assignment of signaling channel.
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.

Unit Times
data TCH/F seizure success
for handover
Definition Number of data TCH/F seizure success for handover
Description This counter counts the number of data TCH/F seizure success dur-
ing handover of signaling channel.
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.


(INTERNAL TC)


Unit Times


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 After BSC responds channel request message allocation and suc-
Point to assignment, used for data channel). The measurement points
are B2 and B3, as shown in Figure 1742, Figure 1743.

Unit Times

by BSC for handover
Definition Number of data TCH/F allocation attempts by BSC for handover
Description 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).
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.


(INTERNAL TC)


Unit Times


TCH/F allocation success for
handover
Definition Number of data TCH/F allocation success for handover
Description This counter counts the number of data TCH/F allocation success
Measurement This counter accumulates when CHL_ACT_ACK correctly receives
Point 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)



Unit Times

Definition Number of data TCH/F assignment attempts
Description This counter counts the number of voice TCH/F assignment at-
tempts when assigning TCH/F channel as data channel, includ-
ing 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 can’t
be received within specified duration, that is, this assignment
failed at this time.
Measurement For the assignment from port A, BSC receives the messages of
Point 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 Times

Definition Number of data TCH/F handover attempts
Description 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 re-
sponse-less handover failure (C901260093).

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 dura-
tion, 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 can’t receive HO_FAIL-
URE, 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 doesn’t
at this BSC side.
Measurement This counter accumulates when BSC receives ASS_COM/HO_COM
Point message, ASS_FAIL/HO_FAIL message, or messages of exception,
released instance, force-released instance, or timer timeout. The

(INTERNAL TC)



Unit Times
data TCH/F handover failure
Definition Number of data TCH/F handover failure
Description his counter counts the number of data TCH/F handover failure dur-
ing handover of data channel.
channel, fails to access to new channel and returns to previous
vious channel.


FAILURE FLOW 1
Unit Times

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 can’t return to
source channel after BSC sends assignment / handover command
to MS.
Point tion, released instance, force-released instance, or timer timeout.
The measurement point is C4, as shown in Figure 1760and Figure
1761.

FAILURE FLOW 2

FAILURE FLOW 3

Unit 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.
cessfully 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 mes-
sage, or timer timeout.
Measurement BSC uses TCH/F due to assignment; this counter accumulates
Point 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 Times

for assignment due to
Resource request to iTC
failure (Speech version 1)
Definition Number of data TCH/F allocation failure for assignment due to Re-
source 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.
cessfully 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.
Point when it receives the messages of unavailable iTC, incorrect re-
sponse message, or timer timeout during iTC resource application.
Unit Times

for handover due to TIPB
version 1)
Definition Number of data TCH/F allocation failure for handover due to TIPB
handover due to TIPB connection failure (speech version 1) during
handover.
Point when it receives messages of connection failure, incorrect con-
nection response, or timer timeout during TIU connection. The
measurement points are C2 and D2, as shown in Figure 1764and
Figure 1765.
FIGURE 1764 INTERNAL HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER,

AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 1

Unit Times
data TCH/F allocation
failure for handover due to
Definition Number of data TCH/F allocation failure for handover due to Re-
handover due to resource request to iTC failure (speech version 1)
cessfully seizes TCH/F channel, BSC requests TC resource after
determining channel types are changed. If application of iTC re-
source fails due to receive the messages of unavailable iTC re-
source, incorrect response, or timer timeout, this leads to TCH/F
assignment failure, and this counter accumulates.
Measurement BSC uses TCH/F due to handover; this counter accumulates when
Point 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.


FIGURE 1767 EXTERNAL HANDOVER FAILURE FLOW 2 (EXTERNAL TC)
Unit Times
version 2)


Unit Times
Definition Number of data TCH/F allocation failure for assignment due to Re-
accumulates.


Point when it receives the messages of unavailable iTC, incorrect re-
sponse message, or timer timeout during iTC resource application.
Unit Times
version 2)
handover.
Figure 1771.


Unit Times

Point it receives the messages of unavailable iTC resource, incorrect re-
sponse message, or timer timeout during iTC resource applica-
tion. The measurement points are C1 and D1, as shown in Figure
1772and Figure 1773.


Unit Times
version 3)

Unit Times
Definition Number of data TCH/F allocation failure for assignment due to re-
accumulates.
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.

Unit Times
version 3)
handover.
Figure 1777.


Unit Times

Point it receives the messages of unavailable iTC resource, incorrect re-
sponse message, or timer timeout during iTC resource applica-
tion. The measurement points are C1 and D1, as shown in Figure


Unit 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 data-
base, 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 This counter increments while BSC correctly receives database re-
Point turn failure or no AIPB board resource, and the reason to apply
for channel is assignment and purpose is voice channel. The mea-
surement point is A as shown in Figure 1780.

FIGURE 1780 REQUEST RESOURCE FAILURE
Unit Times
Related Features 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)
due to UDP port failure during assigning voice channel.
(speech version 1), access request is sent to access module, if ac-
cess module returns access failure due to UDP port request failure.
failure due to request UDP port failure.
Measurement This counter increments while BSC correctly receives EV_RAN-
Point CONN_IPA_CONN_NACK message returned by access module, and
the reason is request UDP port failure for assignment. The mea-

FIGURE 1781 CHANNEL ALLOCATION FAILURE
Unit Times
to AIPB connection failure
version 1)
Definition Number of TCH/F allocation failure due to AIPB connection failure
failure due to AIPB access failure.
Point CONN_IPA_CONN_NACK message returned by access module (the
reason is AIPB access failure) or TwaitConn timer timeout for as-
signment. The measurement point is A as shown in Figure 1782.
Unit Times

version 1)
failure for handover (speech version 1)
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.
Point turn failure or no AIPB board resource, and the reason to apply for
channel is handover and purpose is voice channel. The measure-
ment point is A as shown in Figure 1783.
Unit Times
Related Features � ZGO-03-02-011 Channel Repacking
� ZGO-05-04-003 A over IP

due to request UDP port
version 1)
for handover (speech version 1)
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.
the reason is request UDP port failure for handover. The measure-
Unit Times

to AIPB connection failure for
handover (speech version 1)
due to AIPB access failure during handover.
access module returns failure and the reason is failed to access
AIPB.
reason is AIPB access failure) or TwaitConn timer timeout for han-
dover. The measurement point is A as shown in Figure 1785.
Unit Times

(speech version 2)
Unit Times

version 2)
Unit Times

version 2)
Unit Times

version 2)
Unit Times

version 2)
This counter increments while BSC receives EV_RANUMC_RA-
DIO_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.
Unit Times

AIPB.
Unit Times

(speech version 3)
Unit Times
Related Features � ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

version 3)
Unit Times

version 3)
Unit Times

version 3)
DIO_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
Unit Times

version 3)
UDP port.
Unit Times

AIPB.
Unit Times

failure for assignment (data)
(data) to apply for AIPB board resource from database, failed re-
quest (including database return failure or no AIPB resource) in-
dicates TCH/F allocation failure.
Unit Times

for assignment (data)
(data), access request is sent to access module, if access module
returns access failure due to UDP port request failure.
Unit Times

Unit Times
failure for handover (data)
When BSC receives EV_RANUMC_RADIO_APPLY message (data),
the reason to request channel is handover, to request AIPB re-
source from database. This counter increments if failed to request
AIPB (including database returning failure or no AIPB resource),
indicating TCH/F allocation failure.

Unit Times
for handover (data)
for handover (data)
the reason to request channel is handover, to request access re-
quest for access module. This counter increments while access
module returns failure and the reason is failed to request UDP
port.

Unit Times
for handover (data)
for handover (data)
module returns failure and the reason is failed to access AIPB.
Unit Times


assign TCH/F release by
forced handover to forced
handover source
Definition Number of assign TCH/F release by forced handover to forced han-
dover 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 as-
signed to the forced handover source.
The BSC CS service instance is forcibly handover to release re-
source, 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 The BSC CS service instance is forcibly handover to release re-
Point source, 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
signed to the queuing user.
source, if the released TCH/F resource is assigned to the queuing
user, the counter accumulates.

by forced handover being assigned to the queuing user.
Point source, if the released TCH/F resource is assigned to the queuing
Unit Times
restore TCH/F release by
forced handover to DBS
Definition Number of restore TCH/F release by forced handover to DBS
signed to the queuing user.
by forced handover being restored to DBS.
Point source, 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 re-
source, if the released TCH/F resource is assigned to the forced
release source, the counter accumulates.

by forced release being assigned to the forced release source.
Measurement The BSC CS service instance is forcibly released to release re-
Point source, 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
assigned to the queuing user.
by forced release being assigned to the queuing user.
Point source, if the released TCH/F resource is assigned to the queuing
Unit Times
restore TCH/F release by
forced release to DBS
Definition Number of restore TCH/F release by forced release to DBS
restored to the database instead of being assigned to other users.
source, if the released TCH/F resource is just released instead of

by forced release being restored to DBS.
Point source, if the released TCH/F resource is just released instead of
Unit 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 The counter counts when the request for channel is sent to BSC
Point (due to assignment, used for signaling channel) and the channel
is occupied successfully.
Unit Times

(cause:Abis)
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 avail-
able Abis resource, the counter accumulates. If the request is re-
sponded 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.
Point (due to handover, used for signaling channel) but the channel oc-
cupation 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 at-
tempts during the process of voice channel assignment. When
Point (due to assignment, used for voice channel) but the channel oc-
Unit Times

for handover (cause:Abis )
tempts 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
Point (due to handover, used for voice channel) but the channel occu-
pation fails or waiting for resource inside BSC fails.
Unit Times
Description This counter counts the number of failed data TCH/F seizure at-
tempts during the process of data channel assignment. When
Point (due to assignment, used for data channel) but the channel occu-
Unit Times

for handover (cause:Abis)
tempts during the process of data channel handover. When BSC
Point (due to handover, used for data channel) but the channel occupa-
tion fails or waiting for resource inside BSC fails.
Unit Times
(cause:radio resource)
available radio resource, the counter accumulates. If the request
Unit Times

(cause:radio resource)
able radio resource, the counter accumulates. If the request is re-
Unit Times
for assignment (cause:radio
resource)
Unit Times

for handover (cause:radio
resource)
the request. If the channel occupation fails due to no available
radio resource, the counter accumulates. If the request is re-
Unit Times
resource)
tempts during the process of data channel assignment. When BSC
Unit Times

resource)
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 simultane-
ously 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 For the assignment from A-interface, the counter accumulates in
Point the following cases: BSC receives the message of assignment suc-
cess, assignment failure, timer timeout, or exception, instance be-
ing released, or instance being forcibly released.
Unit Times

FR_V1 assignment success
Description This counter counts the number of successes of assigning TCH/F
A-interface, this counter accumulates after the assignment suc-
cess message is received.
Measurement For the assignment from A-interface, this counter accumulates af-
Point ter BSC receives the assignment success message.
Unit Times
Unit Times

Unit Times
Unit Times
Unit Times

FR_V1 handover
Description This counter counts the number of handover attempts that the des-
tination voice channel is of full-rate voice version 1. During han-
dover, after MS is successfully accessed on the new channel, BSC
will receive the assignment completion message ASS_COM (in-
tra-cell handover) or HO_COM message (inter-cell handover and
external handover). If BSC correctly receives the above mes-
sages 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 consid-
ered as handover failure without return, the counter accumulates.
mulates on the basis of source instances. For external handover,
because the source instance is not at the BSC, the counter accu-
mulates on the basis of destination instances.
Measurement This counter accumulates when BSC receives the
Point 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 chan-
nel. 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 The counter counts when BSC receives the ASS_COM message or
Point the HO_COM message.
Unit Times

FR_V2 handover
Unit Times
Unit Times

FR_V3 handover
Unit Times
Unit 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 be-
ing 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 After the ordinary user obtains TCH/F, if the forced release mes-
Point sage from other call is received, the counter counts. The mea-

FIGURE 1805 FLOW OF ORDINARY USER'S CALL BEING RELEASED DUE TO

RESOURCE BEING PREEMPTED
Unit Times
C901260186 Handover of
ordinary users due to be
grabbed (TCH/F)
Description This counter counts the number of handovers performed for ordi-
nary 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 per-
formed for ordinary user's call on TCH/F due to high-priority user's
preempting resource.


Measurement After the ordinary user obtains TCH/F, if the forced handover mes-
Point sage is received, the counter counts. The measurement point is
FIGURE 1806 FLOW OF HANDOVER FOR ORDINARY USER'S CALL DUE TO

RESOURCE BEING PREEMPTED
Unit Times
Channel Request of priority
users (TCH/F)
Description This counter counts the number of requesting for TCH/F by high-
priority users.


channel for the request. If the channel request is initiated by high-
priority user, the counter increments.
Usage This counter is used to find out the number of requesting for TCH/F
by high-priority users.
Measurement When the high-priority user requests for TCH/F, the counter
Point 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
Unit Times

Successful Channel seize of
priority users (TCH/F)
Description This counter counts the number of high-priority users' requesting
for TCH/F successfully.
priority 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 When the high-priority user requests for TCH/F, if the channel is
Point obtained successfully, the counter counts. The measurement point
is A, as shown in Figure 1810, Figure 1811, and Figure 1812.
Unit Times

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 When high-priority user requests for TCH/F but there is no avail-
Point able resource, if high-priority user preempts resource from or-
dinary user successfully, the counter counts. The measurement

Unit Times


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 at-
tempts by BSC .............................................................. 1793
C901270016 Number of signaling TCH/H handover at-
tempts ......................................................................... 1794
C901270017 Number of signaling TCH/H handover suc-
cess............................................................................. 1797
C901270018 Number of signaling TCH/H handover fail-
ure .............................................................................. 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 as-
signment...................................................................... 1802
C901270024 Number of voice TCH/H seizure success for han-
dover........................................................................... 1803
C901270026 Number of TCH/H allocation attempts for assign-
ment by BSC (speech version 1)...................................... 1806
C901270027 Number of TCH/H allocation success for assign-
ment (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 han-
dover (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 han-
dover by BSC (speech version 2) ..................................... 1816
C901270045 Number of TCH/H allocation success for han-

C901270050 Number of TCH/H allocation attempts for assign-

C901270051 Number of TCH/H allocation success for assign-
for handover (speech version 3) ...................................... 1824
C901270057 Number of TCH/H allocation success for han-
C901270062 Number of Voice TCH/H assignment attempts by
BSC ............................................................................. 1829
C901270065 Number of Voice TCH/H handover at-
tempts ......................................................................... 1831
C901270067 Number of Voice TCH/H handover failure......... 1833
C901270068 Number of Voice TCH/H handover failure mes-
C901270070 Number of data TCH/H seizure success for as-
signment...................................................................... 1836
C901270073 Number of data TCH/H seizure success for han-
dover........................................................................... 1837
C901270075 Number of data TCH/H allocation attempts for
assignment by BSC........................................................ 1840
C901270076 Number of data TCH/H allocation success for as-
signment...................................................................... 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 at-
tempts ......................................................................... 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 as-
signment due to TIPB connection failure (Speech version
1)................................................................................ 1855
C901270095 Number of TCH/H allocation failure for assign-
ment 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 han-
1)................................................................................ 1858
2)................................................................................ 1860
2)................................................................................ 1861
C901270101 Number of TCH/H allocation failure for han-
2)................................................................................ 1863
3)................................................................................ 1865

Chapter 33 TCH/H Measurement

3)................................................................................ 1866
C901270105 Number of TCH/H allocation failure for hand-
over due to Resource request to iTC failure (Speech version
3)................................................................................ 1868
C901270106 Number of TCH/H allocation failure due to re-
1)................................................................................ 1869
1)................................................................................ 1870
C901270108 Number of TCH/H allocation failure due to AIPB
1)................................................................................ 1872
2)................................................................................ 1875
2)................................................................................ 1876
2)................................................................................ 1878
3)................................................................................ 1881
3)................................................................................ 1882
3)................................................................................ 1884
quest AIPB resource failure for assignment (data).............. 1887
quest UDP port failure for assignment (data)..................... 1888
connection failure for assignment (data) ........................... 1888


quest AIPB resource failure for handover (data)................. 1889
quest UDP port failure for handover (data)........................ 1890
connection failure for handover (data).............................. 1891
C901270130 Number of assign TCH/H release by forced han-
dover to forced handover source...................................... 1892
C901270131 Number of assign TCH/H release by forced han-
dover to queuing user .................................................... 1892
C901270132 Number of restore TCH/H release by forced han-
dover to DBS ................................................................ 1893
C901270133 Number of assign TCH/H release by forced re-
lease to forced release source ......................................... 1893
C901270134 Number of assign TCH/H release by forced re-
lease to queuing user..................................................... 1894
C901270135 Number of restore TCH/H release by forced re-
lease to DBS ................................................................. 1894
C901270136 Number of signaling TCH/H seize failure for as-
sign due to Abis lack ...................................................... 1895
C901270137 Number of signaling TCH/H seize failure for han-
dover due to Abis lack .................................................... 1895
signment (cause:Abis) ................................................... 1896
dover (cause:Abis ) ....................................................... 1896
ment (cause:Abis) ......................................................... 1897
dover (cause:Abis) ........................................................ 1897
C901270142 Number of signaling TCH/H seize failure for as-
sign due to radio resource lack ........................................ 1898
C901270143 Number of signaling TCH/H seize failure for han-
dover due to radio resource lack ...................................... 1898
signment (cause:radio resource) ..................................... 1899
ment (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 be-
ing 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 pri-
ority users (TCH/H) ....................................................... 1909

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 as-
signment; handover processes include inner handover and outer
handover.
The measurement point of TCH/H counters in immediate assign-
ment process is shown in Figure 1816.
When TC is internal and external, the measurement point of

TCH/H counter in general assignment processes is shown in Figure

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)


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.

Definition Number of signaling TCH/H seizure success for assignment
Description 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 BSC applies for channel (due to assignment, it is used for signaling
Point channels) and seizure succeeds. The measurement point is A1, as

Unit Times
� ZGO-03-02-003 Full dynamic channel allocation on Um inter-
face
Definition Number of signaling TCH/H seizure success for handover.
Description This counter counts the number of TCH/H seizure success in sig-
naling channel handover.
After BSC receives channel request message, it tries to assign
channel for the request. This counter will accumulate if assign-
ment 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 BSC applies for channel (because handover, usage are signaling
Point channels) and seizure succeeds, or it receives inner waiting re-
source valid message. The measurement points are C1, D1, as

(INTERNAL TC)



Unit Times
face
attempts by BSC for
assignment
Definition Number of signaling TCH/H assignment attempts by BSC for as-
signment
Description This counter counts the number of TCH/H channel attempts be-
ing assigned on allocating signaling channel, including the num-
ber of assignment success (C901270008) and assignment failure
(900060174).
After BSC responds channel request message assignment and suc-
cessfully seizes TCH/H channel, BSC send channel activation mes-
sage 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, chan-
nel instance being released, channel being forced to disconnect
etc, this counter and C900060174 will accumulate simultaneously.

Measurement After BSC activates TCH/H (because allocation, usage are sig-
Point naling 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 Times
face
Definition Number of signaling TCH/H allocation success for assignment
Description This counter counts the number of TCH/H channel success assign-
ment on allocating signaling channel.
After BSC responds channel request messages assignment and
successfully seizures channel, BSC sends channel activation mes-
sage 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 BSC receives correctly CHL_ACT_ACK message sent by BTS and
Point the reason is that allocation and usage are signaling channel. The

Unit Times
face
attempts by BSC due to
handover
Definition Number of signaling TCH/H allocation attempts by BSC due to han-
dover
Description This counter counts the number of TCH/H channel attempt
being allocated in signaling channel handover, including success-
ful 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

Measurement After BSC activates TCH/H (because allocation, usage are signaling
Point channel), receives correctly the CHL_ACK_ACK message sent by
BTS, or receives channel activation failure message, wrong chan-
nel 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)


Unit Times
face

success due to handover
Definition Number of signaling TCH/H allocation success due to handover
Description This counter counts the number of successful TCH/H channel as-
signment in signaling channel handover.
After BSC responds channel request messages assignment and
successfully occupies channel, BSC sends channel activation mes-
sage CHL_ACT to BTS to activate the TCH/H. If activated success-
fully, it will receive CHL_ACT_ACK message sent by BTS, it indi-
cates that TCH/H assigns successfully and the counter accumu-
lates.
Measurement BSC receives correctly CHL_ACT_ACK message sent by BTS and
Point 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)



Unit Times
face
failure due to handover
Definition Number of signaling TCH/H allocation failure due to handover
Description This counter counts the number of TCH/H channel assignment fail-
ure.
cessfully occupies TCH/H channel, BSC send channel activation
message CHL_ACT to BTS to activate the TCH/H. If channel ac-
tivation fails due to receiving channel activation failure message,
wrong channel activation response message, timer T9103 timeout,
channel instance being released, channel being forced to discon-
nection etc, this counter will increment.
Measurement BSC activates TCH/H to be used as signaling channel because of
Point handover, but receiving channel activation failure message, wrong
channel activation response message, timer T9103 timeout, chan-
nel 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
FIGURE 1839 EXTERNAL HANDOVER FAILURE FLOW 2 (INTERNAL TC)
Unit Times
face
attempts by BSC
Definition Number of signaling TCH/H assignment attempts by BSC
Description This counter counts the number of attempt allocating TCH/H chan-
nel to be signaling channel.
cessfully 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-

cumulates; if it is impossible to receive the MS access notification

in the certain time, this allocation fails.
Measurement For immediate allocation, this counter counts the number when
Point BSC receives EST_IND message correctly or T31.3 timeout (not
receive the MS access notification in the certain time). The mea-
Unit Times
signaling TCH/H handover
attempts
Definition Number of signaling TCH/H handover attempts
Description 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

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 On newly assigned TCH/H channel, BSC check the handover
Point 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)


Unit Times

success
Definition Number of signaling TCH/H handover success
Description This counter counts the number of TCH/H channel success in sig-
naling 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 BSC receives ASS_COM or HO_COM message. The measurement
Point points are C4, D4, as shown in Figure 1845, Figure 1846, Figure
1847 and Figure 1848.

(INTERNAL TC)



Unit Times
failure
Definition Number of signaling TCH/H handover failure
Description 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 chan-
nel, receives allocation failure on original channel or handover fail-
ure.
Point points are C4, D4, as shown in Figure 1849, Figure 1850.


FAILURE FLOW 1
Unit Times

received by BSC
Definition Number of signaling TCH/H handover failure messages do not re-
ceived by BSC
Description This counter counts the number of TCH/H channel return no han-
dover 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 BSC receives abnormal message, or instance being released, in-
Point stance being forced to disconnection, timer timeout message. The
measurement point is C4, as shown in Figure 1851, Figure 1852.

FAILURE FLOW 2

FAILURE FLOW 3

Unit Times
C901270021 Number
Definition Number of voice TCH/H seizure success for assignment
Description 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 pos-
sible to queue or force to disconnect, it enters the state of waiting
for resource. This counter accumulates if waiting succeeds.
Measurement BSC applies for channel (because allocation, usage are voice chan-
Point nel) and occupation succeeds or BSC receives inner waiting re-
source valid message. The measurement point is B1, as shown in
Figure 1853, Figure 1854.

FAILURE FLOW 1

Unit Times
face
C901270024 Number
Definition 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 pos-
sible to queue or force to disconnect, it enters the state of waiting
for resource. This counter accumulates if waiting succeeds.
Measurement BSC applies for channel (because handover, usage are voice chan-
Point nel) and occupation succeeds or BSC receives inner waiting re-


(INTERNAL TC)


Unit Times
face

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 fail-
ure (C900060175+C900060176+900060177+C900060178)
After BSC respond channel request message assignment and suc-
cessfully occupied TCH/H channel, BSC first finishes connection,
then sends channel activation message CHL_ACT to BTS to acti-
vate 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 simultane-
ously; on the contrary, if failed, this counter and another counter
related the failure reason accumulate siulataneously.
Measurement Assignment succeeds or fails (because allocation and usage are
Point voice channel, use voice version 1). The measurement points are
B2, B3, as shown in Figure 1859, Figure 1860.

Unit Times
face
TCH/H allocation success
version1)
Definition Number of TCH/H allocation success for assignment (speech ver-
sion1)
to assign on allocation voice channel (used for voice version 1).
cessfully 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 BSC correctly receives the CHL_ACT_ACK message sent by BTS,
Point and because allocation and usage are voice channel (use voice
version 1). The measurement point is B3, as shown in Figure 1861,
Figure 1862.

Unit Times
face

by BSC during handover
(speech version 1)
Definition Number of TCH/H allocation attempts by BSC during handover
(speech version 1)
to assign on voice channel (use voice version 1) handover, in-
cluding assignment success (C901270033) and assignment failure
(C900060179+C900060180+900060181+C900060182)
then sends channel activation message CHL_ACT to BTS to acti-
vate 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 si-
multaneously; on the contrary, if failed, this counter and another
counter related the failure reason accumulate simultaneously.
Measurement Assignment succeeds or fails (because handover, usage are voice
Point channel, use voice version 1). The measurement points are C3,
D3, as shown in Figure 1863, Figure 1864, and Figure 1865.

(INTERNAL TC)


Unit Times
face

during handover (speech
version 1)
Definition Number of TCH/H allocation success during handover (speech ver-
sion 1)
ment on voice channel (use voice version 1).
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.
Point and because handover and usage are voice channel (use voice ver-
sion 1). The measurement points are C3, D3, as shown in Figure
1866, Figure 1867, Figure 1868, and Figure 1869.

(INTERNAL TC)



Unit Times
face
by BSC for assignment
(speech version 2)
Definition Number of TCH/H allocation attempts by BSC for assignment
(speech version 2)
to assign on allocation voice channel (use voice version 2), in-
(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 suc-
ceeds, this counter and C901270039 accumulate simultaneously;
on the contrary, if failed, this counter and another counter related
the failure reason accumulate simultaneously.

Measurement Assignment succeeds or fails (because allocation, usage are voice

Point channel, use voice version 2). The measurement points are B2,
B3, as shown in Figure 1870, Figure 1871.
Unit Times
face

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)
ment on allocation voice channel (use voice version 2).
version 2). The measurement point is B3, as shown in Figure 1872,
Figure 1873.

Unit Times
face
�
for handover by BSC
(speech version 2)
Definition Number of TCH/H allocation attempts for handover by BSC (speech
version 2)
to assign on voice channel (use voice version 2) handover, in-
(C900060187+C900060188+900060189+C900060190)


D3, as shown in Figure 1874, Figure 1875, Figure 1876, and Figure
1877.

(INTERNAL TC)


Unit Times
face

for handover (speech version
2)
Definition Number of TCH/H allocation success for handover (speech version
2)

(INTERNAL TC)



Unit Times
face
version 3)
Definition Number of TCH/H allocation attempts for assignment (speech ver-
sion 3)
to assign on allocation voice channel (use voice version 3), in-
(C900060191+C900060192+900060193+C900060194)

Measurement Assignment succeeds or fails (because allocation, usage are voice

Point channel, use voice version 3). The measurement points are B2,
B3, as shown in Figure 1882and Figure 1883.
Unit Times
face

version 3)
Definition Number of TCH/H allocation success for assignment (speech ver-
sion 3)
ment on allocation voice channel (use voice version 3).
version 3). The measurement point is B3, as shown in Figure 1884
and Figure 1885.

Unit Times
face
by BSC for handover
(speech version 3)
Definition Number of TCH/H allocation attempts by BSC for handover (speech
version 3)
to assign on voice channel (use voice version 3), including
assignment success (C901270057) and assignment failure
(C900060195+C900060196+900060197+C900060198)


D3, as shown in Figure 1886, Figure 1887, Figure 1888, and Figure
1889.

(INTERNAL TC)


Unit Times
face

for handover (speech version
3)
Definition Number of TCH/H allocation success for handover (speech version
3)
CHL_ACT to BTS to activate the TCH/H. If activation succeeds, it

(INTERNAL TC)



Unit Times
face
attempts by BSC
Definition Number of Voice TCH/H assignment attempts by BSC
Description 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-in-
terface, 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 For allocation from A-interface, BSC correctly receives the alloca-
Point tion success message, allocation failure message, timer timeout
message, or abnormal message, the instance being released, the
instance being forced to disconnection, this counter accumulates.

The measurement point is B5, as shown in Figure 1894and Figure

1895.
Unit Times

attempts
Definition Number of Voice TCH/H handover attempts
Description This counter counts the number of TCH/H channel attempt in
voice channel handover, including the number of TCH/H han-
dover 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 re-
ceives 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 accumu-
lates.
Measurement BSC receives ASS_COM/HO_COM message, ASS_FAIL/HO_FAIL
Point message or receive abnormal message, the instance being re-
leased, the instance being forced to disconnection, timer timeout.
The measurement points are C4, D4, as shown in Figure 1896,

(INTERNAL TC)



Unit Times
failure
Definition Number of Voice TCH/H handover failure
Description This counter counts the number of TCH/H channel returning han-
dover failure on voice channel handover.
MS is in handover on TCH/H channel, accesses new channel fail-
ure and returns original channel. This counter accumulates when
receiving allocation failure/handover failure on original channel.
Measurement BSC receives the ASS_FAIL/HO_FAIL message. The measurement
Point points are C4, D4, as shown in Figure 1900and Figure 1901.


FAILURE FLOW 1
Unit 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 BSC receives abnormal message, timer timeout message or the in-
Point stance being released, the instance being forced to disconnection.
The measurement points are C4, D4, as shown in Figure 1902and
Figure 1903.

FAILURE FLOW 2

FAILURE FLOW 3

Unit Times
data TCH/H seizure success
for assignment
Definition 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 BSC applies for channel (because allocation, usage are data chan-
Point nels) and occupies successfully, or BSC receives inner waiting re-
source valid message. The measurement points is B1, as shown
in Figure 1904and Figure 1905.

Unit Times
face
data TCH/H seizure success
for handover
Definition 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 BSC applies for channel (because handover, usage are data chan-
Point nels) and occupies successfully, or BSC receives inner waiting re-


(INTERNAL TC)


Unit Times
face


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 suc-
cess (C901270076) and assignment failure (C900060202 +
C900060203 + C900060204 + C900060205).
Usage After BSC responds channel request message assignment and suc-
ceeds, this related counter and C901270076 accumulate simulta-
neously; on the contrary, if fails, this counter and another counter
related the failure reason accumulate simultaneously.
Measurement Assignment succeeds or fails (because allocation, usage are data
Point channel). The measurement points are B2, B5, as shown in Figure

Unit Times
face

for assignment
Definition Number of data TCH/H allocation success for assignment
Description 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.
Point and because allocation and usage are data channel. The measure-
ment points is B3, as shown in Figure 1912and Figure 1913.

Unit Times
face


by BSC
Definition Number of data TCH/H allocation attempts by BSC
Description This counter counts the number of TCH/H channel being at-
tempted to assign on data channel handover, including assignment
success (C901270082) and assignment failure (C900060206 +
C900060207 + C900060208 + C900060209).
ceeds, this related counter and C901270082 accumulate simulta-
neously; on the contrary, if fails, this counter and another counter
related the failure reason accumulate simultaneously.
Measurement Assignment succeeds or fails (because handover, usage are data
Point channels). The measurement points are C3, D3, as shown in
Figure 1914, Figure 1915, Figure 1916, and Figure 1917.

(INTERNAL TC)



Unit Times
face

for handover
Definition Number of data TCH/H allocation success for handover
Description This counter counts the number of TCH/H channel assignment suc-
cessfully on data channel handover.
will receive the CHL_ACT_ACK message sent by BTS and indicate
that TCH/H assignment succeeds. This counter accumulates.
Point and because handover and usage are data channel. The measure-
ment points are C3, D3, as shown in Figure 1918, Figure 1919,


(INTERNAL TC)


Unit Times
face

data TCH/H assignment
attempts by BSC
Definition Number of data TCH/H assignment attempts by BSC
Description 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-in-
terface, 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 For allocation from A-interface, BSC correctly receives the allo-
Point cation success message, allocation failure message, timer time-
out 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.

Unit Times
face

Definition Number of data TCH/H handover attempts
Description 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 re-
ceives 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 simultane-
ously.
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 accumu-
lates.

Measurement BSC receives ASS_COM/HO_COM message, ASS_FAIL/HO_FAIL

Point message or receive abnormal message, the instance being re-
leased, the instance being forced to disconnection, timer timeout.
The measurement points are C4, D4, as shown in Figure 1924,

(INTERNAL TC)


Unit Times
face

data TCH/H handover failure
Definition Number of data TCH/H handover failure
Description This counter counts the number of TCH/H channel returning han-
dover 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 re-
ceiving allocation failure/handover failure on original channel.
Measurement BSC receives the ASS_FAIL/HO_FAIL message. The measurement
Point points are C4, D4, as shown in Figure 1928and Figure 1929.

FAILURE FLOW 1

Unit Times
face
data TCH/H handover failure
do not received by BSC
Definition Number of data TCH/H handover failure do not received by BSC
Description 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 chan-
nel, then accumulate.
Measurement BSC receives abnormal message, the instance being released, the
Point instance being forced to disconnect or timer timeout message.
The measurement point is C4, as shown in Figure 1930and Figure
1931.


FAILURE FLOW 2

FAILURE FLOW 3
Unit Times
face

TCH/H allocation failure for
assignment due to TIPB
version 1)
Definition Number of TCH/H allocation failure for assignment due to TIPB
ure due to TIPB connection failure when allocating voice channel
(use voice version 1).
cessfully occupied TCH/H channel, BSC sends TIU connection re-
quest to TIPB. If TIU connection fails due to receiving TIU con-
nection failure, or wrong TIU connection respond message, timer
timeout, then this counter will accumulate.
Measurement Due to allocation BSC uses TCH/H. Receive connection failure mes-
Point sage, wrong connection respond message, or timer timeout when
in TIU connection. The measurement point is B2, as shown in
Figure 1932.
Unit Times

Definition Number of TCH/H allocation failure for assignment due to Resource
request to iTC failure (Speech version 1)
ure due to iTC application resource failure when allocating voice
channel (use voice version 1).
cessfully occupied TCH/H channel, BSC apply for resource to iTC.
If iTC application resource fails due to receiving iTC resource un-
availability, or wrong response message, or timer timeout, then it
contributes to TCH/H assignment failure and this counter will ac-
cumulate.
Measurement Due to allocation BSC uses TCH/H. Receive iTC resource unabail-
Point ability, wrong respond message, or timer timeout when in iTC ap-
plication resource. The measurement point is B1, as shown in
Figure 1933.
Unit Times

version 1)
Definition Number of TCH/H allocation failure for handover due to TIPB con-
nection failure (Speech version 1)
ure due to TIU connection failure when in voice channel handover
nection failure, or wrong TIU connection response message, timer
Measurement Due to handover BSC uses TCH/H. Receive connection failure mes-
Point sage, wrong connection response message, or timer timeout when
in TIU connection. The measurement points are C2, D2, as shown


Unit Times
handover due to Resource
request to iTC failure
(Speech version 1)
Definition Number of TCH/H allocation failure for handover due to Resource
ure due to iTC application resource failure when voice channel han-
dover (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.

Point ability, wrong response message, or timer timeout when in iTC ap-
plication resource. The measurement points are C1, D1, as shown

Unit Times

version 2)
ure due to TIPB connection failure when allocating voice channel
Figure 1938.
Unit Times

cessfully occupied TCH/H channel, BSC apply for resource to iTC.
cumulate.
Point ability, wrong response message, or timer timeout when in iTC
application resource. The measurement point is B1, as shown in
Figure 1939.
Unit Times

version 2)
ure due to TIU connection failure when voice channel handover


Unit Times
(Speech version 2)
ure 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.

Measurement Due to handover BSC uses TCH/H. Receive iTC resource un avail-

Unit Times

version 3)
ure due to TIU connection failure when allocating voice channel
Figure 1944.
Unit Times

cessfully occupies TCH/H channel, BSC apply for resource to iTC.
cumulate.
Measurement Due to allocation BSC uses TCH/H. Receive iTC resource unavail-
Point ability, wrong response message, or timer timeout when in iTC
application resource. The measurement point is B1, as shown in
Figure 1945.
Unit Times

version 3)
ure due to TIU connection failure when voice channel (use voice
version 3) handover.
cessfully occupies TCH/H channel, BSC sends TIU connection re-


Unit Times
(Speech version 3)
ure due to iTC application resource failure when voice channel (use
voice version 3) handover.
cessfully occupies TCH/H channel, BSC applies for resource to iTC.
cumulate.
Measurement Due to allocation BSC uses TCH/H. Receive iTC resource unavail-


in Figure 1948 and Figure 1949.

Unit Times
(speech version 1)
Definition Number of TCH/H allocation failure due to request AIPB resource

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
Unit Times
version 1)
Definition Number of TCH/H allocation failure due to request UDP port failure


Unit Times
version 1)
Definition Number of TCH/H allocation failure due to AIPB connection failure

Unit Times
version 1)
resource), indicating TCH/H allocation failure.

Unit Times
Related Features ZGO-03-02-011 Channel Repacking
version 1)
UDP port.

Unit Times
AIPB.
Unit Times

(speech version 2)
Unit Times

version 2)
Unit Times

version 2)
Unit Times

version 2)
Unit Times

version 2)
DIO_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.
Unit Times

AIPB.
Unit Times

(speech version 3)
Unit Times
Related Features ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

version 3)
Unit Times

version 3)
Unit Times

version 3)
DIO_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
Unit Times

version 3)
UDP port.
Unit Times

AIPB.
Unit Times

(data) to apply for AIPB board resource from database, failed re-
quest (including database return failure or no AIPB resource) in-
dicates TCH/H allocation failure.
Unit Times

Unit Times


Unit Times
the reason to request channel is handover, to request AIPB re-
source from database. This counter increments if failed to request
AIPB (including database returning failure or no AIPB resource),
indicating TCH/H allocation failure.

Unit Times
for handover (data)
for handover (data)
module returns failure and the reason is failed to request UDP
port.

Unit Times
for handover (data)
for handover (data)
module returns failure and the reason is failed to access AIPB.
Unit Times

assign TCH/H release by
forced handover to forced
handover source
Definition Number of assign TCH/H release by forced handover to forced han-
dover source
counts the number of times that the released TCH/H resource is
assigned to the forced handover source.
source, 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 re-
leased by forced handover being assigned to the forced handover
source.
Point source, 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
source, if the released TCH/H resource is assigned to the queuing
leased by forced handover being assigned to the queuing user.
Point source, if the released TCH/H resource is assigned to the queuing
Unit Times

restore TCH/H release by
forced handover to DBS
Definition Number of restore TCH/H release by forced handover to DBS
source, if the released TCH/H resource is just released instead of
leased by forced handover being restored to DBS.
Point source, 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 re-
lease source
assigned to the forced release source.
source, 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.
Point source, if the released TCH/H resource is assigned to the forced
Unit Times

forced release to queuing
user
Definition Number of assign TCH/H release by forced release to queuing user
source, if the released TCH/H resource is assigned to the queuing
leased by forced release being assigned to the queuing user.
Point source, if the released TCH/H resource is assigned to the queuing
Unit Times
restore TCH/H release by
forced release to DBS
Definition Number of restore TCH/H release by forced release to DBS
source, if the released TCH/H resource is just released instead of
leased by forced release being restored to DBS.
Point source, if the released TCH/H resource is just released instead of
Unit 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
Unit Times
Abis lack
Unit Times

Description This counter counts the number of failed voice TCH/H seizure at-
Unit Times
for handover (cause:Abis )
Unit Times

Description This counter counts the number of failed data TCH/H seizure at-
tempts during the process of data channel assignment. When
Unit Times
for handover (cause:Abis)
Unit Times

failure for assign due to radio
resource lack
available radio resource, the counter accumulates. If the request
Unit Times
radio resource lack
Unit Times

resource)
Unit Times
resource)
Unit Times

resource)
tempts during the process of data channel assignment. When BSC
Unit Times
resource)
Unit 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
Unit Times
HR_V1 assignment success
Description This counter counts the number of successes of assigning TCH/H
Unit Times
HR_V3 assignment attempts
Description This counter counts the number of attempts of assigning TCH/H


Unit Times
HR_V3 assignment success
Description This counter counts the number of successes of assigning TCH/H
Unit Times
HR_V1 handover
tination voice channel is of half-rate voice version 1. During han-

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 chan-
Unit Times
HR_V3 handover
tination voice channel is of half-rate voice version 3. During han-
Unit Times

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 chan-
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 or-
dinary 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 After the ordinary user obtains TCH/H, if the forced release mes-
Point sage from other call is received, the counter counts. The mea-

FIGURE 1974 RESOURCE RELEASING OF ORDINARY USERS DUE TO BEING

GRABBED (TCH/H)
Unit Times
C901270178 Handover of
ordinary users due to being
grabbed (TCH/H)
Description This counter counts the number of handovers performed for ordi-
nary 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

Usage This counter is used to find out the number of handovers per-
formed for ordinary user's call on TCH/H due to high-priority user's
preempting resource.
Measurement After the ordinary user obtains TCH/H, if the forced handover mes-
Point sage is received, the counter counts. The measurement point is
FIGURE 1975 HANDOVER OF ORDINARY USERS DUE TO BEING GRABBED

(TCH/H)
Unit Times

Channel Request of priority
users (TCH/H)
Description This counter counts the number of requesting for TCH/H by high-
priority users.
priority user, the counter increments.
Usage This counter is used to find out the number of requesting for TCH/H
by high-priority users.
Measurement When the high-priority user requests for TCH/H, the counter
Point counts. The measurement point is A, as shown in Figure 1976,
Unit Times

Successful Channel seize of
priority users (TCH/H)
Description This counter counts the number of high-priority users' requesting
for TCH/H successfully.
priority 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 When the high-priority user requests for TCH/H, if the channel is
Point obtained successfully, the counter counts. The measurement point
is A, as shown in Figure 1979, Figure 1980, and Figure 1981.
Unit 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 When high-priority user requests for TCH/H but there is no avail-
Point able resource, if high-priority user preempts resource from or-
dinary user successfully, the counter counts. The measurement

Unit Times

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 mes-
sages........................................................................... 1916
C901280004 Number of ESTABLISH REQUEST mes-
sages........................................................................... 1917
C901280005 Number of ESTABLISH CONFIRM mes-
sages........................................................................... 1918
C901280006 Number of ESTABLISH INDICATION mes-
sages........................................................................... 1918
C901280007 Number of RELEASE REQUEST messages......... 1919
C901280008 Number of RELEASE CONFIRM messages......... 1920
C901280009 Number of RELEASE INDICATION mes-
sages........................................................................... 1920
C901280010 Number of UNIT DATA REQUEST mes-
sages........................................................................... 1921
C901280011 Number of UNIT DATA INDICATION mes-
sages........................................................................... 1922
C901280012 Number of CHANNEL ACTIVATION mes-
sages........................................................................... 1922
C901280013 Number of CHANNEL ACTIVATION ACK mes-
sages........................................................................... 1923
C901280014 Number of CHANNEL ACTIVATION Negative ACK
messages ..................................................................... 1924
C901280015 Number of CONNECTION FAILURE INDICATION
messages ..................................................................... 1924
C901280016 Number of DEACTIVATE SACCH mes-
sages........................................................................... 1925
C901280017 Number of ENCRYPTION COMMAND mes-
sages........................................................................... 1926
C901280018 Number of HANDOVER DETECTION mes-
sages........................................................................... 1926
C901280019 Number of MEASUREMENT RESULT mes-
sages........................................................................... 1927
C901280020 Number of MODE MODIFY REQUEST mes-
sages........................................................................... 1928
C901280021 Number of MODE MODIFY ACK messages......... 1929
C901280022 Number of MODE MODIFY NACK mes-
sages........................................................................... 1929
C901280023 Number of PHYSICAL CONTEXT REQUEST mes-
sages........................................................................... 1930

C901280024 Number of PHYSICAL CONTEXT CONFIRM mes-

sages........................................................................... 1931
C901280025 Number of RF CHANNEL RELEASE mes-
sages........................................................................... 1931
C901280026 Number of MS POWER CONTROL mes-
sages........................................................................... 1932
C901280027 Number of BS POWER CONTROL mes-
sages........................................................................... 1933
C901280028 Number of PREPROCESSED CONFIGURE mes-
sages........................................................................... 1933
C901280029 Number of PREPROCESSED MEASUREMENT RE-
SULT messages ............................................................. 1934
C901280030 Number of RF CHANNEL RELEASE ACK mes-
sages........................................................................... 1935
C901280031 Number of SACCH INFO MODIFY mes-
sages........................................................................... 1936
C901280032 Number of ABIS_PREPROC_ENHANCE-
MEAS_RESULT messages ................................................ 1936
C901280033 Number of ABIS_ROUND_TRIP_DELAY_REPORT
messages ..................................................................... 1937
C901280034 Number of ABIS_PRE_HO_NOTIFY mes-
sages........................................................................... 1938
C901280035 Number of ABIS_BCCH_INFO messages......... 1938
C901280036 Number of ABIS_CCCH_LOAD_IND mes-
sages........................................................................... 1939
C901280037 Number of ABIS_CHL_RQD messages............ 1940
C901280038 Number of ABIS_DELETE_IND messages......... 1940
C901280039 Number of ABIS_PAGING_CMD mes-
sages........................................................................... 1941
C901280040 Number of ABIS_IMM_ASSIGN_CMD mes-
sages........................................................................... 1942
C901280041 Number of ABIS_SMS_BROADCAST_REQ mes-
sages........................................................................... 1942
C901280042 Number of ABIS_SMS_BROADCAST_CMD mes-
sages........................................................................... 1943
C901280043 Number of ABIS_CBCH_LOAD_IND mes-
sages........................................................................... 1944
C901280044 Number of ABIS_EGPRS_CHL_REQ mes-
sages........................................................................... 1944
C901280045 Number of ABIS_LOAD_CONTROL mes-
sages........................................................................... 1945
C901280046 Number of ABIS_END_LOAD_CONTROL mes-
sages........................................................................... 1946
C901280047 Number of ABIS_END_LOAD_CONTROL_ACK
messages ..................................................................... 1946
C901280048 Number of ABIS_PCCCH_LOAD_IND mes-
sages........................................................................... 1947
C901280049 Number of ABIS_RF_RESRC_IND mes-
sages........................................................................... 1948
C901280050 Number of ABIS_SACCH_FILLING mes-
sages........................................................................... 1948
C901280051 Number of ABIS_OVERLOAD messages .......... 1949
C901280052 Number of ABIS_ERROR_REPORT mes-
sages........................................................................... 1950
C901280053 Number of ABIS_SYSINFO_REQ mes-
sages........................................................................... 1950
C901280054 Number of ABIS_SI_BC_END messages ......... 1951
C901280055 Number of ABIS_SI_NACK messages............. 1952
C901280056 Number of ABIS_PWRCTRL_IND mes-
sages........................................................................... 1952

Chapter 34 Abis Interface Message Counter Measurement
C901280057 Number of ABIS_SYSINFO_ACK mes-

sages........................................................................... 1953
C901280061 Number of ABIS_PACKET_PBCCH_INF mes-
sages........................................................................... 1954
C901280062 Number of ABIS_PACKET_CCCH_PARA mes-
sages........................................................................... 1954
C901280063 Number of ABIS_PACKET_PBCCH_PARA mes-
sages........................................................................... 1955
C901280064 Number of ABIS_PACKET_CHN_REQ mes-
sages........................................................................... 1956
C901280065 Number of ABIS_PACKET_PAGING_CMD mes-
sages........................................................................... 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 mes-
sages........................................................................... 1960
C901280071 Number of ABIS_PACKET_TA_REQUEST_ACK
messages ..................................................................... 1960
C901280072 Number of ABIS_PACKET_CHN_CONFIG_CHG
messages ..................................................................... 1961
FIG_CHG_RESP messages .............................................. 1962
C901280074 Number of ABIS_PACKET_PIA_DEL_IND mes-
sages........................................................................... 1962
C901280075 Number of ABIS_PACKET_SEND_PIA_IND mes-
sages........................................................................... 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 mes-
sages........................................................................... 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 mes-
sages........................................................................... 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 mes-
sages........................................................................... 1969
C901280085 Number of ABIS_PSCONN_CMM_ACK mes-
sages........................................................................... 1970
C901280086 Number of ABIS_PSCONN_CMM_NACK mes-
sages........................................................................... 1970
C901280087 Number of ABIS_GLOBAL_RESET mes-
sages........................................................................... 1971
C901280088 Number of ABIS_GLOBAL_RESET_ACK mes-
sages........................................................................... 1972
C901280089 Number of ABIS_GLOBAL_RESET_NACK mes-
sages........................................................................... 1972

C901280090 Number of ABIS_PACKET_UP_ASSIGN mes-

sages........................................................................... 1973
C901280091 Number of ABIS_PACKET_DOWN_ASSIGN mes-
sages........................................................................... 1974
C901280092 Number of ABIS_CSCONN_CMM_REQ mes-
sages........................................................................... 1974
C901280093 Number of ABIS_CSCONN_CMM_ACK mes-
sages........................................................................... 1975
C901280094 Number of ABIS_CSCONN_CMM_NACK mes-
sages........................................................................... 1976
C901280095 Number of ABIS_CCMCONN_CMM_REQ mes-
sages........................................................................... 1976
C901280096 Number of ABIS_CCMCONN_CMM_ACK mes-
sages........................................................................... 1977
C901280097 Number of ABIS_CCMCONN_CMM_NACK mes-
sages........................................................................... 1978
C901280098 Number ABIS_PACKET_ACCESS_REJ mes-
sages........................................................................... 1978
SIGN_CMD_NEW messages ............................................ 1979
C901280100 Number of PACKET_DOWNLINK_ASSIGN mes-
sages........................................................................... 1980
C901280101 Number of PACKET_UPLINK_ASSIGN mes-
sages........................................................................... 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 inter-
face. 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.

FIGURE 1986 MEASUREMENT POINT WHEN BSC SENDS ABIS MESSAGE

TO BTS
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 mes-
sage to be confirmed transmitting on Abis interface.
Measurement This counter increments when BSC sends DATA REQuest message
Point to BTS. The measurement point is A, as shown in Figure 1987.

TO BTS
Unit Times

C901280002 Number
of DATA INDICATION
messages
Definition Number of DATA INDICATION messages
Description This counter counts the number of data indication messages re-
ceived by BSC on Abis interface.
Usage This counter is used to find out the frequency of data indication
messages transmitting on Abis interface.
Measurement This counter increments when BSC receives DATA INDication mes-
Point sage. The measurement point is A, as shown in Figure 1988.
Unit Times
ERROR INDICATION
messages
Definition 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 inter-
face messages received by BSC.
Usage This counter is used to find out the frequency of error indication
Measurement This counter increments when BSC receives ERROR INDication

Unit 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 This counter increments when BSC sends Establish Request mes-
Point sage to BTS. The measurement point is A, as shown in Figure 1990.

TO BTS
Unit Times

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 This counter increments when BSC receives Establish Confirm
Unit Times
ESTABLISH INDICATION
messages
Definition Number of ESTABLISH INDICATION messages
Description When MS receives assignment command (including immediate as-
signment) 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 Indica-
tion messages transmitting on Abis interface.
Measurement This counter increments when BSC receives Establish Indication

Unit 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 This counter increments when BSC sends Release Request mes-
Point sage to BTS. The measurement point is A, as shown in Figure 1993.

TO BTS
Unit Times

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 This counter increments when BSC receives Release Confirm mes-
Point sages. The measurement point is A, as shown in Figure 1994.
Unit Times
RELEASE INDICATION
messages
Definition 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 mes-
sage 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 This counter increments when BSC receives Release Indication
Point messages. The measurement point is A, as shown in Figure 1995.

Unit 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 RE-
QUEST messages transmitting on Abis interface.
Measurement This counter increments when BSC sends UNIT DATA REQUEST
Point messages to BTS. The measurement point is A, as shown in Figure
1996.

TO BTS
Unit Times

UNIT DATA INDICATION
messages
Definition Number of UNIT DATA INDICATION messages
Description BTS sends a UNIT DATA INDICATION message to BTS. The mes-
sage 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 INDI-
CATION messages transmitting on Abis interface.
Measurement This counter increments when BSC receives UNIT DATA INDICA-
Point TION messages. The measurement point is A, as shown in Figure
1997.
Unit Times
CHANNEL ACTIVATION
messages
Definition 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 AC-
TIVATION messages sent by BSC to BTS.
Usage This counter is used to find out the frequency of CHANNEL ACTI-
VATION messages transmitting on Abis interface.
Measurement This counter increments when BSC sends CHANNEL ACTIVATION


TO BTS
Unit Times
CHANNEL ACTIVATION
ACK messages
Definition Number of CHANNEL ACTIVATION ACK messages
Description After BSC finishes activating channel, it sends CHANNEL ACTIVA-
TION ACK message to BSC as the response of channel activation
message. This counter counts the number of CHANNEL ACTIVA-
TION ACK messages of Abis interface messages received by BSC.
VATION ACK messages transmitting on Abis interface.
Measurement This counter increments when BSC receives CHANNEL ACTIVATION
Point ACK messages. The measurement point is A, as shown in Figure
1999.
Unit Times

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 mes-
sages of Abis interface messages received by BSC.
VATION Negative ACK messages transmitting on Abis interface.
Measurement This counter increments when BSC receives CHANNEL ACTIVATION
Point Negative ACK messages. The measurement point is A, as shown
in Figure 2000.
Unit Times
CONNECTION FAILURE
INDICATION messages
Definition 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 FAIL-
URE 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 This counter increments when BSC receives CONNECTION FAIL-

Point URE INDICATION messages. The measurement point is A, as
Unit 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 acti-
vate 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 This counter increments when BSC receives DEACTIVATE SACCH

TO BTS
Unit Times

ENCRYPTION COMMAND
messages
Definition Number of ENCRYPTION COMMAND messages
Description BSC initiate ENCRYPTION COMMAND message to require encryp-
tion. 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 COM-
MAND messages transmitting on Abis interface.
Measurement This counter increments when BSC sends ENCRYPTION COMMAND
2003.

TO BTS
Unit Times
HANDOVER DETECTION
messages
Definition 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 HAN-
DOVER 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 DETC-
TION messages transmitting on Abis interface.

Measurement This counter increments when BSC receives HANDOVER DETCTION

Unit Times
MEASUREMENT RESULT
messages
Definition Number of MEASUREMENT RESULT messages
Description In general, MS reports a measurement report ( Um interface mes-
sage 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 This counter increments when BSC receives MEASUREMENT RE-
Point SULTS messages. The measurement point is A, as shown in Figure
2005.

Unit Times
MODE MODIFY REQUEST
messages
Definition Number of MODE MODIFY REQUEST messages
Description During the allocation or inner handover process, when the chan-
nel 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 This counter increments when BSC sends MODE MODIFY REQUEST
2006.

TO BTS
Unit 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.
ACK messages transmitting on Abis interface.
Measurement This counter increments when BSC receives MODE MODIFY ACK
Unit Times
MODE MODIFY NACK
messages
Definition Number of MODE MODIFY NACK messages
Description After BTS receives MODE MODIFY REQUEST messages, it is im-
possible 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
NACK messages transmitting on Abis interface.
Measurement This counter increments when BSC receives MODE MODIFY NACK

Unit Times
PHYSICAL CONTEXT
REQUEST messages
Definition Number of PHYSICAL CONTEXT REQUEST messages
Description When BSC needs to know the current channel of MS (physical con-
text), it sends PHYSICAL CONTEXT REQUEST messages to BTS to
apply. This counter counts the number of PHYSICAL CONTEXT RE-
QUEST messages of Abis interface messages sent by BSC.
Usage This counter is used to find out the frequency of PHYSICAL CON-
TEXT REQUEST messages transmitting on Abis interface.
Measurement This counter increments when BSC sends PHYSICAL CONTEXT RE-
Point QUEST messages to BTS. The measurement point is A, as shown
in Figure 2009.

TO BTS
Unit Times

PHYSICAL CONTEXT
CONFIRM messages
Definition Number of PHYSICAL CONTEXT CONFIRM messages
Description After BTS receives PHYSICAL CONTEXT REQUEST messages, re-
port to BSC about related physical context through PHYSICAL CON-
TEXT COMFIRM messages. This counter counts the number of
PHYSICAL CONTEXT COMFIRM messages of Abis interface mes-
sages received by BSC.
Usage This counter is used to find out the frequency of PHYSICAL CON-
TEXT COMFIRM messages transmitting on Abis interface.
Measurement This counter increments when BSC receives PHYSICAL CONTEXT
Point COMFIRM messages to BTS. The measurement point is A, as shown
in Figure 2010.
Unit Times
RF CHANNEL RELEASE
messages
Definition Number of RF CHANNEL RELEASE messages
Description When the certain logical channel is not used, BSC needs to no-
tify 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 RE-
LEASE messages transmitting on Abis interface.

Measurement This counter increments when BSC sends RF CHANNEL RELEASE

2011.

TO BTS
Unit Times
MS POWER CONTROL
messages
Definition Number of MS POWER CONTROL messages
Description BSC can calculate the proper transmitting power used by MS ac-
cording 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 CON-
TROL messages transmitting on Abis interface.
Measurement This counter increments when BSC sends MS POWER CONTROL
2012.

TO BTS

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 con-
trol 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 CON-
Measurement This counter increments when BSC sends BS POWER CONTROL
2013.

TO BTS
Unit Times
C901280028 Number
of PREPROCESSED
CONFIGURE messages
Definition Number of PREPROCESSED CONFIGURE messages
Description In order to reduce the load of processed measurement report of
BSC and the messages flux of Abis interface, the process of prepro-
cessed measurement report can be used. First BTS processes the

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 This counter increments when BSC sends PREPROCESSED CON-
Point FIGURE messages to BTS. The measurement point is A, as shown
in Figure 2014.

TO BTS
Unit Times
C901280029 Number
of PREPROCESSED
MEASUREMENT RESULT
messages
Definition Number of PREPROCESSED MEASUREMENT RESULT messages
Description After BTS receives PREPROCESSED CONFIGURE messages, it
begins to preprocess the measurement report, sends the pre-
processed result to BSC through PREPROCESSED MEASUREMENT
RESULT messages. This counter counts the number of PRE-
PROCESSED 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 This counter increments when BSC receives PREPROCESSED MEA-
Point SUREMENT RESULT messages to BTS. The measurement point is

Unit 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 RE-
LEASE ACK messages transmitting on Abis interface.
Measurement This counter increments when BSC receives RF CHANNEL RELEASE
Point ACK messages to BTS. The measurement point is A, as shown in
Figure 2016.
Unit Times

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 inform-
ing 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 MOD-
IFY messages transmitting on Abis interface.
Measurement This counter increments when BSC sends SACCH INFO MODIFY
2017.

TO BTS
Unit Times
ABIS_PREPROC_ENH
ANCEMEAS_RESULT
messages
Definition Number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages
Description This counter counts the number of ABIS_PREPROC_ENHANCE-
MEAS_RESULT messages received by BSC.

Usage This counter is used to find out the frequency of enhanced prepro-
cessed measurement report message transmitting on Abis inter-
face.
Measurement This counter increments when BSC receives ABIS_PREPROC_EN-
Point HANCEMEAS_RESULT messages. The measurement point is A, as
Unit 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_DE-
LAY_REPORT messages received by BSC.
Usage This counter is used to find out the frequency of ROUND TRIP DE-
LAY REPORT messages transmitting on Abis interface.
Measurement This counter increments when BSC receives ROUND TRIP DELAY
Point REPORT messages. The measurement point is A, as shown in
Figure 2019.
Unit Times

ABIS_PRE_HO_NOTIFY
messages
Definition Number of ABIS_PRE_HO_NOTIFY messages
Description This counter counts the number of ABIS_PRE_HO_NOTIFY mes-
Usage This counter is used to find out the frequency of PRE_HO_NOTIFY
Measurement This counter increments when BSC sends PRE-HANDOVER NOFI-
Point CATION messages. The measurement point is A, as shown in
Figure 2020.

TO BTS
Unit Times
C901280035 Number
of ABIS_BCCH_INFO
messages
Definition 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 This counter increments when BSC sends BCCH INFOMATION mes-


TO BTS
Unit 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 indi-
cation messages transmitting on Abis interface.
Measurement This counter increments when BSC receives CCCH LOAD INDICA-
2022.
Unit Times

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 This counter increments when BSC receives CHANNEL REQUIRED
Unit Times
C901280038 Number
of ABIS_DELETE_IND
messages
Definition 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 INDICA-
TION 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 INDICA-
Measurement This counter increments when BSC receives DELETE INDICATION

Unit 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 COM-
MAND messages transmitting on Abis interface.
Measurement This counter increments when BSC sends PAGING COMMAND mes-
Point sages to BTS. The measurement point is A, as shown in Figure
2025.

TO BTS
Unit Times

ABIS_IMM_ASSIGN_CMD
messages
Definition Number of ABIS_IMM_ASSIGN_CMD messages
Description After BSC receives MS channel request, it tries for assigning one
channel accordingly and activates the channel, then sends one IM-
MEDIATE ASSIGN COMMAND message to BTS.
This message includes one complete Um interface RR layer IMME-
DIATE 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 AS-
SIGN COMMAND messages transmitting on Abis interface.
Measurement This counter increments when BSC sends IMMEDIATE ASSIGN
Point COMMAND messages to BTS. The measurement point is A, as

TO BTS
Unit Times
ABIS_SMS_BROADCAST_
REQ messages
Definition Number of ABIS_SMS_BROADCAST_REQ messages
Description This counter counts the number of ABIS_SMS_BROADCAST_REQ

Usage This counter is used to find out the frequency of SMS BROADCAST
Measurement This counter increments when BSC sends SMS BROADCAST RE-
Point QUEST messages to BTS. The measurement point is A, as shown
in Figure 2027.

TO BTS
Unit Times
Related Features 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 This counter increments when BSC sends MS BROADCAST COM-
Point MAND messages to BTS. The measurement point is A, as shown
in Figure 2028.

TO BTS

Unit Times
Related Features 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 IN-
DICATION messages transmitting on Abis interface.
Measurement This counter increments when BSC receives CBCH LOAD INDICA-
Point TION messages to BTS. The measurement point is A, as shown in
Figure 2029.
Unit Times
ABIS_EGPRS_CHL_REQ
messages
Definition Number of ABIS_EGPRS_CHL_REQ messages
Description This counter counts the number of ABIS_EGPRS_CHL_REQ mes-
sages sent by BSC.
Usage This counter is used to find out the frequency of EGPRS_CHL_REQ

Measurement This counter increments when BSC receives ABIS_EG-

Point PRS_CHL_REQ messages. The measurement point is A, as shown
in Figure 2030.
Unit 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 INDI-
CATION messages transmitting on Abis interface.
Measurement This counter increments when BSC receives CCCHLOAD INDICA-
2031.
Unit Times

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 CON-
Measurement This counter increments when BSC sends ABIS_END_LOAD_CON-
Point TROL messages to BTS. The measurement point is A, as shown in
Figure 2032.

TO BTS
Unit Times
ABIS_END_LOAD_CONTR
OL_ACK messages
Definition Number of ABIS_END_LOAD_CONTROL_ACK messages
Description This counter counts the number of ABIS_END_LOAD_CON-
TROL_ACK messages received by BSC.
Usage This counter is used to find out the frequency of END LOAD CON-
TROL RETURN messages transmitting on Abis interface.
Measurement This counter increments when BSC receives ABIS_END_LOAD_C-
Point ONTROL_ACK messages to BTS. The measurement point is A, as

Unit 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 com-
mand 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 This counter increments when BSC receives ABIS_PC-
Point CCH_LOAD_CONTROL_IND messages to BTS. The measurement
Unit Times

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 mes-
sages 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 This counter increments when BSC receives RF RESOURCE IN-
Point DICATION messages. The measurement point is A, as shown in
Figure 2035.
Unit Times
ABIS_SACCH_FILLING
messages
Definition 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 INFORMA-
TION 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 This counter increments when BSC sends SACCH FILLING mes-


TO BTS
Unit 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 mes-
sages transmitting on Abis interface.
Measurement This counter increments when BSC receives overload messages.
Unit Times

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 mes-
Measurement This counter increments when BSC receives error report mes-
Unit Times
ABIS_SYSINFO_REQ
messages
Definition 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 informa-
tion requirement messages transmitting on Abis interface.
Measurement This counter increments when BSC receives ABIS_SYSINFO_REQ

Unit 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 infor-
mation broadcast end indication messages transmitting on Abis
interface.
Measurement This counter increments when BSC sends ABIS_SI_BC_END mes-
2040.

TO BTS
Unit Times

ABIS_SI_NACK messages
Definition Number of ABIS_SI_NACK messages
Description This counter counts the number of ABIS_SI_NACK messages re-
ceived by BSC.
Usage This counter is used to find out the frequency of SI_NACK mes-
Measurement This counter increments when BSC receives ABIS_SI_NACK mes-
2041.
Unit Times
ABIS_PWRCTRL_IND
messages
Definition 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 This counter increments when BSC receives ABIS_PWRCTRL_IND

Unit 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 INFOR-
MATION ACKNOWLEDGE messages transmitting on Abis interface.
Measurement This counter increments when BSC receives ABIS_SYSINFO_ACK
Unit Times

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 This counter increments when BSC sends ABIS_PACKET_PBCCH-
Point _INF messages. The measurement point is A, as shown in Figure
2044.

TO BTS
Unit Times
ABIS_PACKET_CCCH_P
ARA messages
Definition 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 INFORMA-
Measurement This counter increments when BSC sends ABIS_PACKET_CCCH_P-
Point ARA messages. The measurement point is A, as shown in Figure
2045.


TO BTS
Unit 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 PATAME-
TER messages transmitting on Abis interface.
Measurement This counter increments when BSC sends ABIS_PACKET_PBCCH_
Point PARA messages to BTS. The measurement point is A, as shown in
Figure 2046.

TO BTS
Unit Times

ABIS_PACKET_CHN_REQ
messages
Definition Number of ABIS_PACKET_CHN_REQ messages
Description This counter counts the number of ABIS_PACKET_CHN_REQ mes-
Usage This counter is used to find out the frequency of UL PACKET CHAN-
NEL REQUIREMENT messages transmitting on Abis interface.
Measurement This counter increments when BSC receives ABIS_PACKET_CHN_
Point REQ messages to BTS. The measurement point is A, as shown in
Figure 2047.
Unit Times
ABIS_PACKET_PAGING_
CMD messages
Definition 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 This counter increments when BSC sends ABIS_PACKET_PAG-
Point ING_CMD messages to BTS. The measurement point is A, as


TO BTS
Unit 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 ASSIGN-
MENT messages of Abis interface messages sent by BSC.
Usage This counter is used to find out the frequency of PACKET IMMEDI-
ATE ASSIGNMENT messages transmitting on Abis interface.
Measurement This counter increments when BSC sends ABIS_PACKET_IMM_AS-
Point SIGN_CMD messages to BTS. The measurement point is A, as

TO BTS
Unit Times

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 IN-
DICATION 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 This counter increments when BSC receives ABIS_PACKET_CON-
Point NECT_FAIL_IND messages to BTS. The measurement point is A,
Unit Times
ABIS_PACKET_PRACH_O
VERLOAD messages
Definition 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 This counter increments when BSC receives ABIS_PACKET_PRAC-
Point H_OVERLOAD messages. The measurement point is A, as shown
in Figure 2051.

Unit 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 This counter increments when BSC receives ABIS_PACKET_PCH_
Point OVERLOAD messages. The measurement point is A, as shown in
Figure 2052.
Unit Times

ABIS_PACKET_TA_REQU
EST messages
Definition Number of ABIS_PACKET_TA_REQUEST messages
Description This counter counts the number of TIME ADVANCE REQUEST mes-
sages of Abis interface messages sent by BSC.
Usage This counter is used to find out the frequency of TIME ADVANCE
Measurement This counter increments when BSC sends ABIS_PACKET_TA_RE-
Point QUEST messages. The measurement point is A, as shown in Figure
2053.

TO BTS
Unit Times
ABIS_PACKET_TA_REQU
EST_ACK messages
Definition Number of ABIS_PACKET_TA_REQUEST_ACK messages
Description This counter counts the number of TIME ADVANCE REQUEST AC-
KNOWLEDGE 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 inter-
face.
Measurement This counter increments when BSC receives ABIS_PACKET_TA_RE-
Point QUEST_ACK messages. The measurement point is A, as shown in
Figure 2054.

Unit 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 CON-
FIGURATION CHANGE messages transmitting on Abis interface.
Measurement This counter increments when BSC sends ABIS_PACKET_CHG_C-
Point ONFIG_CHG messages. The measurement point is A, as shown in
Figure 2055.

TO BTS
Unit Times

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 CON-
FIGURATION CHANGE RESPONSE messages transmitting on Abis
interface.
Measurement This counter increments when BSC receives ABIS_PACKET_CHG-
Point _CONFIG_CHG_RESP messages. The measurement point is A, as
Unit Times
ABIS_PACKET_PIA_DEL_
IND messages
Definition 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 This counter increments when BSC receives ABIS_PACKET_PIA-
Point _DEL_IND messages. The measurement point is A, as shown in
Figure 2057.

Unit 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 inter-
face 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 This counter increments when BSC receives ABIS_PACKET_SEN-
Point D_PIA_IND messages. The measurement point is A, as shown in
Figure 2058.
Unit Times

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 CONFIGURA-
TION 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 inter-
face.
Measurement This counter increments when BSC receives ABIS_PACKET_CHN_
Point CONFIG_REQ messages. The measurement point is A, as shown
in Figure 2059.
Unit Times
ABIS_EGPRS_PACKET_C
HN_REQ messages
Definition 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 This counter increments when BSC receives ABIS_EGPRS_PACKET
Point _CHN_REQ messages. The measurement point is A, as shown in
Figure 2060.

Unit 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 AC-
TIVE COMMAND messages transmitting on Abis interface.
Measurement This counter increments when BSC sends ABIS_PS_CHANNEL _AC-
Point TIVE messages. The measurement point is A, as shown in Figure
2061.

TO BTS
Unit Times

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 AC-
KNOWLEDGEMENT COMMAND messages of Abis interface
TIVE ACKNOWLEDGEMENT COMMAND messages transmitting on
Abis interface.
Measurement This counter increments when BSC receives ABIS_PS_CHANNEL
Point _ACTIVE_ACK messages. The measurement point is A, as shown
in Figure 2062.
Unit Times
ABIS_PS_CHANNEL_ACTI
VE_NACK messages
Definition Number of ABIS_PS_CHANNEL_ACTIVE_NACK messages
Description This counter counts the number of PS CHANNEL ACTIVE UNAC-
KNOWLEDGEMENT COMMAND messages of Abis interface mes-
TIVE UNACKNOWLEDGEMENT COMMAND messages transmitting
on Abis interface.
Measurement This counter increments when BSC receives ABIS_PS_CHANNEL
Point _ACTIVE_NACK messages. The measurement point is A, as shown
in Figure 2063.

Unit 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 COM-
MAND messages of Abis interface messages sent by BSC.
Usage This counter is used to find out the frequency of PS CHANNEL RE-
LEASE COMMAND messages transmitting on Abis interface.
Measurement This counter increments when BSC sends ABIS_PS_CHANNEL_RE-
Point LEASE messages to BTS. The measurement point is A, as shown
in Figure 2064.

TO BTS
Unit Times

ASE_ACK messages
Definition Number of ABIS_PS_CHANNEL_RELEASE_ACK messages
Description This counter counts the number of PS CHANNEL RELEASE AC-
KNOWLEDGEMENT COMMAND messages of Abis interface mes-
LEASE ACKNOWLEDGEMENT COMMAND messages transmitting on
Abis interface.
Measurement This counter increments when BSC receives ABIS_PS_CHAN-
Point NEL_RELEASE_ACK messages. The measurement point is A, as
Unit Times
ASE_NACK messages
Definition Number of ABIS_PS_CHANNEL_RELEASE_NACK messages
Description This counter counts the number of PS CHANNEL RELEASE UN-
ACKNOWLEDGEMENT COMMAND messages of Abis interface mes-
LEASE UNACKNOWLEDGEMENT COMMAND messages transmitting
on Abis interface.
Measurement This counter increments when BSC receives ABIS_PS_CHAN-
Point NEL_RELEASE_NACK messages. The measurement point is A, as

Unit 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 This counter increments when BSC sends ABIS_PSCONN_CMM_
Figure 2067.

TO BTS
Unit Times

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 mes-
sages sent by BSC.
SUCCESS COMMAND ACKNOWLEDGEMENT messages transmitting
on Abis interface.
Measurement This counter increments when BSC receives ABIS_PSCONN_CMM-
Point _ACK messages. The measurement point is A, as shown in Figure
2068.
Unit Times
ABIS_PSCONN_CMM_N
ACK messages
Definition Number of ABIS_PSCONN_CMM_NACK messages
Description This counter counts the number of PS CONNECTION FAILURE COM-
MAND ACKNOWLEDGEMENT messages of Abis interface messages
sent by BSC.
FAILURE COMMAND ACKNOWLEDGEMENT messages transmitting
on Abis interface.
Measurement This counter increments when BSC receives ABIS_PSCONN_CMM_
Point NACK messages. The measurement point is A, as shown in Figure
2069.

Unit Times
ABIS_GLOBAL_RESET
messages
Definition Number of ABIS_GLOBAL_RESET messages
Description This counter counts the number of GLOBAL RESET COMMAND mes-
sages of Abis interface messages sent by BSC.
Usage This counter is used to find out the frequency of GLOBAL RESET
Measurement This counter increments when BSC sends ABIS_GLOBAL_RESET
2070.

TO BTS
Unit Times

ABIS_GLOBAL_RESET_
ACK messages
Definition Number of ABIS_GLOBAL_RESET_ACK messages
Description This counter counts the number of GLOBAL RESET ACKNOWL-
EDGEMENT COMMAND messages of Abis interface messages sent
by BSC.
ACKNOWLEDGEMENT COMMAND messages transmitting on Abis
interface.
Measurement This counter increments when BSC receives ABIS_GLOBAL_RE-
Point SET_ACK messages. The measurement point is A, as shown in
Figure 2071.
Unit Times
ABIS_GLOBAL_RESET_N
ACK messages
Definition Number of ABIS_GLOBAL_RESET_NACK messages
Description This counter counts the number of GLOBAL RESET UNACKNOWL-
EDGEMENT COMMAND messages of Abis interface messages sent
by BSC.
UNACKNOWLEDGEMENT COMMAND messages transmitting on
Abis interface.
Measurement This counter increments when BSC receives ABIS_GLOBAL_RE-
Point SET_NACK messages. The measurement point is A, as shown in
Figure 2072.

Unit 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 ASSIGN-
MENT COMMAND messages transmitting on Abis interface.
Measurement This counter increments when BSC sends ABIS_PACKET_UP_AS-
Point SIGN messages to BTS. The measurement point is A, as shown in
Figure 2073.

TO BTS
Unit Times

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 ASSIGN-
MENT COMMAND messages transmitting on Abis interface.
Measurement This counter increments when BSC sends ABIS_PACKET_DOWN_
Point ASSIGN messages to BTS. The measurement point is A, as shown
in Figure 2074.

TO BTS
Unit Times
ABIS_CSCONN_CMM_
REQ messages
Definition 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 This counter increments when BSC sends ABIS_CSCONN_CMM_
Figure 2075.


TO BTS
Unit Times
ABIS_CSCONN_CMM_
ACK messages
Definition Number of ABIS_CSCONN_CMM_ACK messages
Description This counter counts the number of CS CONNECTION SUCCESS
on Abis interface.
Measurement This counter increments when BSC receives ABIS_CSCONN_CMM-
Point _ACK messages. The measurement point is A, as shown in Figure
2076.
Unit Times

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
on Abis interface.
Measurement This counter increments when BSC receives ABIS_CSCONN_CMM_
Point NACK messages. The measurement point is A, as shown in Figure
2077.
Unit Times
ABIS_CCMCONN_CMM_
REQ messages
Definition 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 This counter increments when BSC sends ABIS_CCM-
Point CONN_CMM_REQ messages to BTS. The measurement point is A,


TO BTS
Unit Times
ABIS_CCMCONN_CMM_
ACK messages
Definition Number of ABIS_CCMCONN_CMM_ACK messages
Description This counter counts the number of CCM CONNECTION SUCCESS
on Abis interface.
Measurement This counter increments when BSC receives ABIS_CCM-
Point CONN_CMM_ACK messages. The measurement point is A, as
Unit Times

ABIS_CCMCONN_CMM_N
ACK messages
Definition Number of ABIS_CCMCONN_CMM_NACK messages
Description This counter counts the number of CCM CONNECTION FAILURE
on Abis interface.
Measurement This counter increments when BSC receives ABIS_CCM-
Point CONN_CMM_NACK messages. The measurement point is A, as
Unit Times
C901280098 Number ABIS

_PACKET_ACCESS_REJ
messages
Definition 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 RE-
JECT messages transmitting on Abis interface.
Measurement This counter increments when BSC sends ABIS_PACKET_AC-
Point CESS_REJ messages to BSC. The measurement point is A, as


TO BTS
Unit 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 assign-
ment messages in the Abis interface messages sent by BSC.
Usage The counter is used to find out the frequency of new packet im-
mediate assignment messages transmitted at Abis interface.
Measurement When BSC sends the ABIS_PACKET_IMM_ASSIGN_CMD_NEW
Point message to BTS, the counter increments. The measurement point

TO BTS
Unit Times

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 When BSC sends the PACKET_DOWNLINK_ASSIGN message to
Point BTS, the counter increments. The measurement point is A, as

TO BTS
Unit Times
PACKET_UPLINK_ASSIGN
messages
Definition Number of PACKET_UPLINK_ASSIGN messages
Description This counter counts the number of packet uplink assignment mes-
sages in the Abis interface messages sent by BSC.
Usage The counter is used to find out the frequency of packet uplink as-
signment messages transmitted at Abis interface.
Measurement When BSC sends the PACKET_UPLINK_ASSIGN message to BTS,
Figure 2084.


TO BTS
Unit 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 When BSC sends the ABIS_PACKET_ACCESS_REJ_NEW message
Point to BTS, the counter increments. The measurement point is A, as

TO BTS
Unit Times


Chapter 35
Gb Message Statistics
(BVC Cell)
Table of Contents
Overview...................................................................... 1984
BSSGP level.................................................................. 1984
BSSGP level.................................................................. 1985
C901290003 Number of RA-CAPABILITY message re-
ceived.......................................................................... 1986
BSC ............................................................................. 1986
BSC ............................................................................. 1987
sent............................................................................. 1987
sage received................................................................ 1988
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 Un-
known ......................................................................... 1996
C901290021 Number of Status messages sent with Cell ser-
vice congestion ............................................................. 1996

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 pro-
tocol error .................................................................... 1998
C901290027 Number of Status messages received with Pro-
cessor overload ............................................................. 1998
by BSC......................................................................... 1999
ceived by BSC............................................................... 1999
sent by BSC.................................................................. 2000
sent by BSC.................................................................. 2001
BSC ............................................................................. 2001
ceived by BSC............................................................... 2002
by BSC......................................................................... 2003
C901290035 Number of DELETE -BSS-PFC-ACK messages
sent by BSC.................................................................. 2003
C901290036 Number of DELETE -BSS-PFC-REQ messages re-
ceived 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 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 When BSC sends a “UL-UNITDATA” message, this counter incre-

Chapter 35 Gb Message Statistics (BVC Cell)
FIGURE 2086 MEASUREMENT POINT OF SUM OF UL UNITDATA MESSAGE

Unit 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 When BSC receives a “DL-UNITDATA” message, this counter incre-
FIGURE 2087 MEASUREMENT POINT OF SUM OF DL UNITDATA MESSAGE

Unit Times

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.
Point crements. The measurement point is A, as shown in Figure 2088.
FIGURE 2088 MEASUREMENT POINT OF THE NUMBER OF RA-CAPABILITY

MESSAGE RECEIVED
Unit Times
by BSC
Definition 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 re-

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 re-
Unit Times
message sent
Definition Number of RA-CAPABILITY-UPDATE message sent

Description SGSN sends RA-CAPABILITY-UPDATE message to SGSN, to indi-

cate current wireless capability of MS. This counter counts the
number of sending this message by BSC.
Point this counter increments. The measurement point is A1, as shown
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 in-
dicate current wireless capability of MS. This counter counts the
Measurement When BSC sends a “RA-CAPABILITY-UPDATE-ACK” message from
Point SGSN, this counter increments. The measurement point is A2, as
Unit Times

C901290008 Number
of Wireless Status PDU
Definition Number of Wireless Status PDU messages sent by BSC
Description BSC sends wireless status PDU message, to indicate exception at
SGSN radio interface. This counter counts the number of sending
Usage 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 send-
ing this message by BSC due to “Losing wireless association with
MS”.
Measurement When BSC sends a RADIO-STATUS message due to “Losing wire-
Point less association with MS”, this counter increments.

Unit Times
sent by BSC due to Bad Link
Quality
Definition Number of wireless status messages sent by BSC due to Bad Link
Quality
ing this message by BSC due to “bad link quality”.
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 re-
selection command
ing this message by BSC due to “cell reselection command”.
Unit 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 When BSC sends a “FLOW-CONTROL-BVC” message, this counter
Point increments, as A1 measurement position shown in Figure 2094.
Unit Times
FLOW-CONTROL-BVC-
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
Figure 2095.

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 When BSC sends a “FLOW-CONTROL-MS” message, this counter
2096.
Unit 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 ac-
cepted flow control policy for current MS. This counter counts the
Measurement When BSC receives a “FLOW-CONTROL-MS-ACK” message, this
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 When BSC sends a “FLOW-CONTROL-PFC” message, this counter
2098.

Unit Times
FLOW-CONTROL-PFC-
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 When BSC receives a “FLOW-CONTROL-PFC-ACK” message, this
Figure 2099.
Unit Times

Status messages sent by
BSC
Definition Number of Status messages sent by BSC
by BSC.
Measurement When BSC sends a “STATUS” message, this counter increments.
Unit Times
Status messages received
by BSC
Definition Number of Status messages received by BSC
by BSC.
Measurement When BSC receives a “STATUS” message, this counter increments.

Unit Times
BVCI Unknown
Definition Number of Status messages sent with BVCI Unknown
Measurement When BSC sends a STATUS message due to “BVCI Unknown”, this
Unit Times
Cell service congestion
Definition Number of Status messages sent with Cell service congestion
Measurement When BSC sends a STATUS message due to “cell service conges-
Unit Times

protocol error
Definition Number of Status messages sent with protocol error
Measurement When BSC sends a STATUS message due to “protocol error”, this
Unit Times
Processor overload
Definition Number of Status messages sent with Processor overload
Measurement When BSC sends a STATUS message due to “processor overload”,
Unit Times
with BVCI Unknown
Definition Number of Status messages received with BVCI Unknown
Measurement When BSC receives a STATUS message due to “BVCI Unknown”,
Unit Times

with Cell service congestion
Definition Number of Status messages received with Cell service congestion
Measurement When BSC receives a STATUS message due to “cell service con-
Unit Times
with protocol error
Definition Number of Status messages received with protocol error
Measurement When BSC receives a STATUS message due to “protocol error”, this
Unit Times
with Processor overload
Definition Number of Status messages received with cause “Processor over-
load”
Measurement When BSC receives a STATUS message due to “processor over-
Unit Times

DOWNLOAD-BSS-PFC
Definition Number of DOWNLOAD-BSS-PFC messages sent by BSC
Description BSC sends DOWNLOAD-BSS-PFC message, to request SGSN orig-
inate CREATE-BSS-PFC process. This counter counts the number
of sending this message by BSC.
Measurement 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 num-
ber of receiving this message by BSC.
2103.

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 When BSC sends a “CREATE-BSS-PFC-ACK” message, this counter
2104.

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 When BSC sends a “CREATE-BSS-PFC-NACK” message, this
Figure 2105.
Unit Times
C901290032 Number
of MODIFY-BSS-PFC
Definition Number of MODIFY-BSS-PFC messages sent by BSC
Description BSC sends MODIFY-BSS-PFC message to SGSN to request modify
packet flow control context. This counter counts the number of

Measurement When BSC sends a “MODIFY-BSS-PFC” message, this counter in-

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 When BSC receives a “MODIFY-BSS-PFC-ACK” message, this
Figure 2107.
Unit 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 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 When BSC sends a “DELETE-BSS-PFC-ACK” message, this counter
2109.

Unit Times
DELETE -BSS-PFC-REQ
Definition 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 op-
posite end .................................................................... 2012
C901300011 Number of reset confirm messages send to op-
posite 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 oppo-
site 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


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 ex-
ceeding 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 in-
teraction 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 Time of PVC unavailable
Description This counter counts the time during which NSVC can not be used
for data transmission.
Measurement The counter starts counting when NSVC link becomes abnormal
Point 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 The counter starts counting when SGSN receives data in which
Point 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


congestion of level 1
Definition Time of PVC congestion of level 1
bytes received from SGSN
Definition Number of bytes received from SGSN
Description 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 The NSVC load can be checked through this counter.
Measurement FR accumulates the number of bytes received from Gb interface.
Point The measurement point is A1.
FIGURE 2112 UPLINK/DOWNLINK NS DATA
Unit Byte
bytes sent to SGSN
Definition Number of bytes sent to SGSN
Description This counter counts the number of bytes sent to SGSN from NS
sublayer.

contains FR header.
Measurement FR accumulates the number of bytes sent each time. The mea-
Point surement point is A2.
FIGURE 2113 UPLINK/DOWNLINK NS DATA
Unit Byte
PDU data sent by NS sub
layer
Definition Number of PDU data sent by NS sub layer
Description This counter counts the number of PDU data sent to SGSN from
NS sub layer.
Usage The NSVC service load can be checked through this counter.
'
Measurement The counter increments each time BSC's FR sends a PDU data to
Point SGSN. The measurement point is A1.
FIGURE 2114 SENDING AND RECEIVING PDU DATA
Unit Times

PDU data received by NS
sub layer
Definition Number of PDU data received by NS sub layer
Description This counter counts the number of PDU data received by NS sub
layer from SGSN.
'
Measurement The counter increments each time BSC's FR receives a PDU data
Point from SGSN. The measurement point is A2.
FIGURE 2115 SENDING AND RECEIVING PDU DATA
Unit Times
PDU data discarded by NS
sub layer
Definition Number of PDU data discarded by NS sub layer
Description 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 � The counter increments when NS sub layer receives an illegal
Point 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 Number of reset messages send to opposite end by NS sub layer
Description NS sub layer sends the NSVC resetting message to indicate SGSN
to reset specified NSVC. This counter counts the number of reset-
ting messages sent to opposite end by NS sub layer.
Usage The counter counts the number of BSC resetting specified NSVC.
'
Measurement Each time BSC sends the “NS-RESET” message, this counter in-
Point crements. The measurement point is A1.
FIGURE 2117 NSVC RESETTING PROCESS
Unit Times

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 mes-
sages received by BSC from the opposite end.
Usage The counter counts the number of SGSN resetting specified NSVC.
'
Measurement Each time BSC receives the “NS-RESET” message, this counter
Point increments. The measurement point is A3.
Unit Times
reset confirm messages
send to opposite end by NS
sub layer
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 num-
ber of sending this message by BSC.
Measurement 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 Each time BSC receives the “NS-RESET-ACK” message, this
Point counter increments. The measurement point is A2.
Unit Times

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 Each time BSC sends the “NS-BLOCK” message, this counter in-
FIGURE 2121 NSVC BLOCKING PROCESS
Unit Times
received blocking messages
sent by opposite end
Definition 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 block-
ing specified NSVC.
Measurement 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 Each time BSC sends the “NS-BLOCK-ACK” message, this counter
Unit Times

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 Each time BSC receives the “NS-BLOCK-ACK” message, this
Unit Times
unblocking messages send
to opposite end by NS sub
layer
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 in-
dicate SGSN to unblock specified NSVC. This counter counts the
number of BSC's unblocking specified NSVC.

Measurement 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 un-
block specified NSVC. This counter counts the number of SGSN's
unblocking specified NSVC.
Measurement Each time BSC receives the “NS-UNBLOCK” message, this counter

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 no-
tify SGSN that specified NSVC is unblocked. This counter counts
Measurement Each time BSC sends the “NS-UNBLOCK-ACK” message, this
Unit Times
C901300020 Number
of received unblocking
acknowledge messages
replied by opposite end
Definition 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 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 When NS sub layer receives reported fault from frame relay and
Point the fault is due to transmission network fault, the counter incre-
ments. The measurement point is A1.

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 inter-
ference
transmission due to O interference.
Measurement When NS sub layer receives the blocking request from background,
Point the counter increments. The measurement point is A1.
FIGURE 2130 BLOCKING NSVC BY BACKGROUND
Unit 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
transmission due to equipment fault.
Measurement When NS sub layer receives reported fault from frame relay and
Point 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
transmission due to NSVC block.
Measurement When NS sub layer sends the status message which is due to NSVC
Point BLOCKED, the counter increments. The measurement point is A1.

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
transmission due to unknown NSVC.
Measurement When NS sub layer sends the status message which is due to un-
Point known NSVC, the counter increments. The measurement point is
A1.
FIGURE 2133 NSVC UNKNOWN
Unit Times

transmission due to protocol
error
Definition Number of abnormal cases in NS transmission due to protocol error
transmission due to protocol error.
Measurement When NS sub layer sends the status message which is due to pro-
Point tocol error, including PDU semantic error, PDU being incompatible
with protocol, protocol error, invalid necessary IE, and missing nec-
essary 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 maxi-
mum retransmission times being exceeded during the NS sub layer
test procedure.
Measurement When the number of NS sub layer's sending NS-ALIVE PDU ex-
Point ceeds the maximum retransmission times NS-ALIVE-RETRIES and
there is no response, the counter increments. The measurement
point is A1.

FIGURE 2135 TEST PROCEDURE BEING ABNORMAL
Unit Times
C901300028 Number
of blocking procedure
failure (after exceeding the
maximum times)
Definition Number of blocking procedure failure (after exceeding the maxi-
mum times)
blocking procedure.
Measurement When the number of NS sub layer's sending NS-BLOCK PDU
Point exceeds the maximum retransmission times NS-BLOCK-RETRIES
and there is no response, the counter increments. The measure-
ment 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 max-
imum times)
unblocking procedure.
Measurement When the number of NS sub layer's sending NS-UNBLOCK PDU ex-
Point ceeds the maximum retransmission times NS-UNBLOCK-RETRIES
and there is no response, the counter increments. The measure-
ment point is A1.

FIGURE 2137 UNBLOCKING PROCEDURE BEING ABNORMAL
Unit Times
congestion occurrence of
level 1
Definition Number of congestion occurrence of level 1
congestion recovery of level
1
Definition Number of congestion recovery of level 1

level 2
2
level 3
3

BECN
Definition Number of BECN
Description This counter counts the number of setting BECN in the data sent
by SGSN.
Usage The counter counts the number of NSVC backward congestions.
Measurement When BECN in the data received by FR from SGSN is set, the
Point counter accumulates. The measurement point is A1.
FIGURE 2138 UPLINK/DOWNLINK DATA BECN BEING SET
Unit Times
FECN
Definition Number of FECN
Description This counter counts the number of setting FECN in the data sent
by SGSN.
Usage The counter counts the number of NSVC forward congestions.
Measurement When FECN in the data received by FR from SGSN is set, the
Point counter accumulates. The measurement point is A2.

FIGURE 2139 UPLINK/DOWNLINK DATA BECN BEING SET
Unit Times


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 re-
ceived.......................................................................... 2034
C901310005 Number of SUSPEND-NACK message re-
ceived.......................................................................... 2035
C901310006 Number of RESUME message sent................. 2036
C901310007 Number of RESUME-ACK message re-
ceived.......................................................................... 2036
C901310008 Number of RESUME-NACK message re-
ceived.......................................................................... 2037
C901310009 Number of FLUSH-LL message received ......... 2038
C901310010 Number of FLUSH-LL-ACK message sent......... 2038
sent............................................................................. 2039
C901310013 Number of BVC_BLOCK_ACK message re-
ceived.......................................................................... 2040
ceived.......................................................................... 2041
ceived.......................................................................... 2042
sent............................................................................. 2043
C901310019 Number of BVC-RESET-ACK message re-
ceived.......................................................................... 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 mes-
sage received................................................................ 2046
C901310023 Number of POSITION_COMMAND message
sent............................................................................. 2046
C901310024 Number of POSITION_RESPONSE message re-
ceived.......................................................................... 2047
C901310025 Number of status messages sent .................. 2048
C901310026 Number of status messages received ............. 2048


known ......................................................................... 2049
C901310028 Number of status messages sent with cell ser-
vice congestion ............................................................. 2049
error............................................................................ 2050
C901310030 Number of status messages sent with processor
overload....................................................................... 2050
C901310031 Number of status messages sent with semanti-
cally 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 unex-
pected conditional IE...................................................... 2053
C901310036 Number of status messages sent with condi-
tional IE error ............................................................... 2053
status incompatible error................................................ 2054
unknown ...................................................................... 2054
tocol error .................................................................... 2055
cessor overload ............................................................. 2055
C901310042 Number of status messages received with BVC
blocking ....................................................................... 2056
C901310043 Number of status messages received with se-
mantically incorrect PDU................................................. 2056
C901310044 Number of status messages received with invalid
mandatory IE................................................................ 2057
C901310045 Number of status messages received with miss-
ing mandatory IE .......................................................... 2057
ing conditional IE........................................................... 2057
C901310047 Number of status messages received with unex-
C901310048 Number of status messages received with con-
ditional IE error............................................................. 2058
tocol 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 mea-
surement entity. It performs statistics for paging message, status
indication message, and signaling BVC resetting message received
by NSE at BSS.

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 When BSS receives a message of which the type is GB_PAG-
Point ING_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.
Point ING_PS, the counter increments. The measurement point is A.
FIGURE 2141 MEASUREMENT POINT OF BSS RECEIVING PS

PAGING MESSAGE

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 When BSS sends the SUSPEND message, the counter increments.
FIGURE 2142 SUSPEND PROCESS
Unit 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 When BSS receives the SUSPEND_ACK message, the counter in-

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 SUS-
PEND_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 re-
sponse when MS requests for terminating GPRS service.
Measurement When BSS receives the SUSPEND_NACK message, the counter in-
FIGURE 2144 MEASUREMENT POINT OF BSS RECEIVING

SUSPEND_NACK MESSAGE
Unit 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 When BSS sends the RESUME message, the counter increments.
FIGURE 2145 RESUME PROCESS
Unit 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 When BSS receives the RESUME_ACK message, the counter incre-
Point ments. 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.
sponse when MS requests for resuming GPRS service.
Measurement When BSS receives the RESUME_NACK message, the counter in-

RESUME_NACK MESSAGE
Unit Times

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 When BSS receives the FLUSH_LL message, the counter incre-
FIGURE 2148 FLUSH_LL PROCESS
Unit Times
FLUSH-LL-ACK message
sent
Definition 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 When BSS sends the FLUSH_LL_ACK message, the counter incre-

FIGURE 2149 FLUSH_LL PROCESS
Unit Times
LLC-DISCARDED message
sent
Definition Number of LLC-DISCARDED message sent
Description When the LLC PDU stored in BSS is deleted, the LLC_DISCARDED
message is sent to SGSN. This counter counts the number of send-
ing LLC_DISCARDED message from NSE.
Usage The counter is used to find out the storage of LLC PDU in BSS.
Measurement When BSS sends the LLC_DISCARDED message, the counter in-
Point crements. The measurement point is A.
FIGURE 2150 MEASUREMENT POINT OF BSS SENDING

LLC_DISCARDED MESSAGE
Unit Times
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 The counter is used to find out the frequency of BSS's requesting
to block BVC.
Measurement When BSS sends the BVC_BLOCK message, the counter incre-
FIGURE 2151 BVC_BLOCK PROCESS
Unit Times
C901310013 Number
of BVC_BLOCK_ACK
message received
Definition Number of BVC_BLOCK_ACK message received
Description When SGSN receives the BVC_BLOCK message from BSS, it identi-
fies 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.
Usage The counter is used to find out cases when BVC is blocked.
Measurement When BSS receives the BVC_BLOCK_ACK message, the counter
FIGURE 2152 BVC_BLOCK PROCESS
Unit Times

BVC-UNBLOCK message
sent
Description When BSS unblocks the blocked BVC, it will send the BVC_UN-
BLOCK message to SGSN. This counter counts the number of send-
ing BVC_UNBLOCK message from NSE.
to unblock BVC.
Measurement When BSS sends the BVC_UNBLOCK message, the counter incre-
FIGURE 2153 BVC_UNBLOCK PROCESS
Unit Times
C901310015 Number
of BVC-UNBLOCK-ACK
message received
Definition Number of BVC-UNBLOCK-ACK message received
Description When SGSN receives the BVC_UNBLOCK message from BSS,
it identifies the BVC to be unblocked and replies the BVC_UN-
BLOCK_ACK message to BSS. This counter counts the number of
BVC_UNBLOCK_ACK messages received by NSE.
Usage The counter is used to find out cases when BVC is unblocked.
Measurement When BSS receives the BVC_UNBLOCK_ACK message, the counter

FIGURE 2154 BVC_UNBLOCK PROCESS
Unit Times
Description This counter counts the number of PCU sending signaling BVC re-
setting message through Gb interface.
Usage The counter is used to find out the frequency of requesting to
restart BVC due to BVC failure.
Measurement When NSE at BSC sends message of which the type is BVC_RESET
Point 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

Description This counter counts the number of PCU's receiving the signaling
BVC resetting message.
Usage The counter is used to find out cases when BVC is restarted.
Measurement When NSE at BSC receives message of which the type is BVC_RE-
Point SET and BVCI is zero, the counter increments. The measurement
point is A1.
FIGURE 2156 PROCESS OF RECEIVING BVC_RESET
Unit Times
sent
Definition Number of BVC-RESET-ACK message sent
Description When PCU receives the signaling BVC resetting message from Gb
interface, it replies the signaling BVC resetting acknowledge mes-
sage. This counter counts the number of NSE's sending signaling
BVC resetting acknowledge message.
Usage The counter is used to find out cases of SGSN initializing BVC.
Measurement When NSE at BSC sends message of which the type is BVC_RE-
Point SET_ACK and BVCI is zero, the counter increments. The measure-
ment point is A2.
FIGURE 2157 PROCESS OF RECEIVING BVC_RESET
Unit Times

received
Definition Number of BVC_RESET_ACK message received
Description Number of PCU's receiving the signaling BVC resetting acknowl-
edge message. This counter counts the number of NSE's receiving
signaling BVC resetting acknowledge message.
Usage The counter is used to find out cases of BVC initialization.
Point SET_ACK and BVCI is zero, the counter increments. The measure-
ment point is A2.
FIGURE 2158 PROCESS OF SENDING BVC_RESET
Unit Times
PERFORM_LOCATION_RE
QUEST message received
Definition 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_LOCA-
TION_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 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 re-
sponse, and then send the result in the PERFORM_LOCATION_RE-
SPONSE 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 re-
quest from SGSN.
Measurement When BSS sends the PERFORM_LOCATION_RESPONSE message,
FIGURE 2160 PERFORM_LOCATION_REQUEST PROCESS
Unit Times

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 terminat-
ing location towards BSS.
Measurement When BSS receives the PERFORM_LOCATION_ABORT message,
Point the counter increments. The measurement point is A.

PERFORM_LOCATION_ABORT MESSAGE
Unit Times
POSITION_COMMAND
message sent
Definition Number of POSITION_COMMAND message sent
Description BSS triggers the positioning command process by sending PO-
SITION_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.
to implement positioning command to SGSN.
Measurement 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 POSI-
TION_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 re-
sponse 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 When BSS receives the POSITION_RESPONSE message, the
FIGURE 2163 POSITION_COMMAND PROCESS
Unit Times

status messages sent
Definition Number of status messages sent
Description When NSE receives downlink BSSGP PDU, if there is any abnormal-
ity, 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 informa-
tion, 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 When NSE at BSC sends message of which the type is STATUS to
Point opposite end entity, the counter increments. The measurement
point is A1.
Unit Times
Definition Number of status messages received
Description If the BSSGP PDU sent by NSE to SGSN is abnormal, NSE will re-
ceive 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 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 When NSE sends the STATUS message to opposite end entity and
Point the message indicates that the abnormality is due to "BVCI un-
known", the counter increments.
Unit Times
Definition Number of status messages sent with cell service congestion
to opposite end entity, the message indicating "cell traffic conges-
tion".
to "cell traffic congestion" occurring when NSE receives downlink
BSSGP PDU.

Point the message indicates that the abnormality is due to "cell traffic
congestion", the counter increments.
Unit Times
protocol error
Definition Number of status messages sent with protocol error
to opposite end entity, the message indicating "Protocol error".
to "Protocol error" occurring when NSE receives downlink BSSGP
PDU.
Point the message indicates that the abnormality is due to "Protocol er-
ror", the counter increments.
Unit Times
processor overload
Definition Number of status messages sent with processor overload
Description This counter counts the number of NSE's sending STATUS mes-
sage to opposite end entity, the message indicating "Processor
overload".
to "Processor overload" occurring when NSE receives downlink
BSSGP PDU.
Point the message indicates that the abnormality is due to "Processor
overload", the counter increments.
Unit Times

semantically incorrect PDU
Definition Number of status messages sent with semantically incorrect PDU
sage 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 down-
link BSSGP PDU.
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 informa-
tion element
to opposite end entity, the message indicating "Invalid mandatory
information".
to "Invalid mandatory information" occurring when NSE receives
downlink BSSGP PDU.
Measurement When NSE sends the STATUS message to opposite end entity
Point and the message indicates that the abnormality is due to "Invalid
mandatory information", the counter increments.
Unit Times

missing mandatory IE
Definition Number of status messages sent with missing mandatory IE
to opposite end entity, the message indicating "Missing mandatory
IE".
to "Missing mandatory IE" occurring when NSE receives downlink
BSSGP PDU.
Point the message indicates that the abnormality is due to "Missing
mandatory IE", the counter increments.
Unit Times
missing conditional IE
Definition Number of status messages sent with missing conditional IE
to opposite end entity, the message indicating "Missing conditional
IE".
to "Missing conditional IE" occurring when NSE receives downlink
BSSGP PDU.
Point the message indicates that the abnormality is due to "Missing con-
ditional IE", the counter increments.
Unit Times

unexpected conditional IE
Definition Number of status messages sent with unexpected conditional IE
sage to opposite end entity, the message indicating "Unexpected
conditional IE".
"Unexpected conditional IE" occurring when NSE receives downlink
BSSGP PDU.
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
sage to opposite end entity, the message indicating "Conditional
IE error".
to "Conditional IE error" occurring when NSE receives downlink
BSSGP PDU.
Point the message indicates that the abnormality is due to "Conditional
IE error", the counter increments.
Unit Times

protocol status incompatible
error
Definition Number of status messages sent with protocol status incompatible
error
to opposite end entity, the message indicating "PDU not compatible
with the protocol state".
to "PDU not compatible with the protocol state" occurring when
NSE receives downlink BSSGP PDU.
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 Number of status messages received with BVCI unknown
Description This counter counts the number of received STATUS messages
which indicate "BVCI unknown".
"BVCI unknown" occurring when SGSN receives downlink BSSGP
PDU.
Measurement When PCU receives STATUS message which indicates "BVCI un-
Point known", the counter increments.
Unit Times

Definition Number of status messages received with cell service congestion
Description This counter counts the number of PCU's receiving STATUS mes-
sage from SGSN, the message indicating "cell traffic congestion".
to "cell traffic congestion" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "cell traffic
Point congestion", the counter increments.
Unit Times
with protocol error
Definition Number of status messages received with protocol error
which indicate "Protocol error".
to "Protocol error" occurring when SGSN receives downlink BSSGP
PDU.
Measurement When PCU receives STATUS message which indicates "Protocol er-
Point ror", the counter increments.
Unit Times
Definition Number of status messages received with processor overload
sage from SGSN, the message indicating "Processor overload".

to "Processor overload" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Processor
Point overload", the counter increments.
Unit Times
with BVC blocking
Definition Number of status messages received with BVC blocking
sage from SGSN, the message indicating "BVCI-blocked".
to "BVCI-blocked" occurring when SGSN receives downlink BSSGP
PDU.
Measurement When PCU receives STATUS message which indicates "BVCI-
Point blocked", the counter increments.
Unit Times
with semantically incorrect
PDU
Definition Number of status messages received with semantically incorrect
PDU
which indicate "Semantically incorrect PDU".
"Semantically incorrect PDU" occurring when SGSN receives down-
link BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Semanti-
Point cally incorrect PDU", the counter increments.
Unit Times

with invalid mandatory IE
Definition Number of status messages received with invalid mandatory IE
which indicate "Invalid mandatory information".
to "Invalid mandatory information" occurring when SGSN receives
downlink BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Invalid
Point mandatory information", the counter increments.
Unit Times
with missing mandatory IE
Definition Number of status messages received with missing mandatory IE
which indicate "Missing mandatory IE".
to "Missing mandatory IE" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Missing
Point mandatory IE", the counter increments.
Unit Times
with missing conditional IE
Definition Number of status messages received with missing conditional IE
which indicate "Missing conditional IE".

to "Missing conditional IE" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Missing con-
Point ditional IE", the counter increments.
Unit Times
with unexpected conditional
IE
Definition Number of status messages received with unexpected conditional
IE
which indicate "Unexpected conditional IE".
"Unexpected conditional IE" occurring when SGSN receives down-
link BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Unexpected
Point conditional IE", the counter increments.
Unit Times
with conditional IE error
Definition Number of status messages received with conditional IE error
which indicate "Conditional IE error".
to "Conditional IE error" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Conditional
Point IE error", the counter increments.
Unit Times

C901310049 Number
of status messages
received with protocol
status incompatible error
Definition Number of status messages received with protocol status incom-
patible error
which indicate "PDU not compatible with the protocol state".
SGSN receives downlink BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "PDU not
Point compatible with the protocol state", the counter increments.
Unit Times
with SGSN congestion
Definition Number of status messages received with SGSN congestion
sage from SGSN, the message indicating "SGSN congestion".
to "SGSN congestion" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "SGSN con-
Point gestion", the counter increments.
Unit Times


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

C901320024 Number of power scans of UL signal level......... 2086

C901320025 Total value of power scans of DL signal qual-
ity ............................................................................... 2087
C901320026 Number of power scans of DL signal qual-
ity ............................................................................... 2088
C901320027 Total value of power scans of UL signal qual-
ity ............................................................................... 2089
C901320028 Number of power scans of UL signal qual-
ity ............................................................................... 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 Re-
sult ............................................................................. 2095
C901320034 Periodic BS Power (TCH/F) Search Times......... 2095
C901320035 Sum of Periodic BS Power (TCH/H) Search Re-
sult ............................................................................. 2096
C901320036 Number of Periodic BS Power (TCH/H)
Search ......................................................................... 2096
C901320037 Sum of Periodic BS Power (SDCCH) Search Re-
sult ............................................................................. 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 mea-
surement 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 pe-
riodically reports the power control statistic result to BSC through
the PC TEST RPT message. The power control measurement result

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 peri-
odical power sampling is A3. BSC collects the power control mea-
surement 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 config-
ured uplink receiving level threshold according to the power con-
trol algorithm and makes decision. If BTS decides to increase MS's
transmission power, it sends the message of increasing transmis-
sion power to MS, and the counter increments.
Measurement The counter counts when BTS sends the message of increasing
Point transmission power to MS. The measurement point is A1

Unit Times
Related Features ZGO-04-02-002 Dynamic MS Power Control
rapid increase in MS power
due to UL signal level
Definition Number of rapid increase in MS power due to UL signal level
Description In rapid power control, after BTS measures the uplink level and
trol algorithm and makes decision. If BTS decides to increase MS's
transmission power, it sends the message of increasing transmis-
Point transmission power to MS. The measurement point is A1.

Unit Times
normal decrease of MS
power due to UL signal level
Definition Number of normal decrease of MS power due to UL signal level
trol algorithm and makes decision. If BTS decides to decrease MS's
transmission power, it sends the message of decreasing transmis-
Measurement The counter counts when BTS sends the message of decreasing

Unit Times
rapid decrease in MS power
due to UL signal level
Definition Number of rapid decrease in MS power due to UL signal level

Unit 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 measure-
ment 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 in-
creasing transmission power to BTS, and the counter increments.
Point transmission power to itself. The measurement point is A2.

Unit Times
Related Features ZGO-04-02-001 Dynamic BTS Power Control
rapid increase in BS power
due to DL signal level
Definition Number of rapid increase in BS power due to DL signal level
Description In rapid power control, after BTS receives the MS measurement re-
port, it compares the MS's downlink receiving level and quality with
the configured downlink receiving level threshold and downlink re-
ceiving 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.

Unit Times
normal decrease of BS
power due to DL signal level
Definition Number of normal decrease of BS power due to DL signal level
ment 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 de-

Unit Times
rapid decrease in BS power
due to DL signal level
Definition 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

Unit Times
normal increases of MS
power due to UL signal
quality
Definition Number of normal increases of MS power due to UL signal quality
quality of MS, it compares the MS's uplink quality with the con-
figured 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 trans-
mission power to MS, and the counter increments.

Unit Times
rapid increase in MS power
due to UL signal quality
Definition Number of rapid increase in MS power due to UL signal quality
quality of MS, it compares the MS's uplink quality with the con-
figured 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 trans-
mission power to MS, and the counter increments.

Unit Times
normal decrease of MS
power due to UL signal
quality
Definition Number of normal decrease of MS power due to UL signal quality
quality of MS, it compares the MS's uplink quality with the config-
ured uplink receiving quality threshold according to the power con-

Unit Times
rapid decrease in MS power
due to UL signal quality
Definition Number of rapid decrease in MS power due to UL signal quality
quality of MS, it compares the MS's uplink quality with the config-
ured uplink receiving quality threshold according to the power con-

Unit Times
normal increases of BS
power due to DL signal
quality
Definition Number of normal increases of BS power due to DL signal quality
ment 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 in-

Unit Times
rapid increase in BTS power
due to DL signal quality
Definition Number of rapid increase in BTS power due to DL signal quality
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 in-

Unit Times
normal decrease of BS
quality
Definition Number of normal decrease of BS power due to DL signal quality
ment 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 de-

Unit Times
rapid decrease in BTS
quality
Definition Number of rapid decrease in BTS power due to DL signal quality
report, it compares the MS's downlink receiving quality with the
configured downlink receiving quality threshold according to the

Unit 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 The counter accumulates when BTS performs periodical scanning.

Unit Grade
C901320018 Number
sampling of MS utilization
power
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 accumu-
lates the value. Each time a MS utilization power value is accu-
mulated, the counter increments. During the period of reporting
measurement result to BSC, BTS may perform multiple periodi-
cal scannings. This counter accumulates the number of periodical
scannings.
Measurement The counter counts when BTS performs periodical scanning. The
Point measurement point is A3.

Unit 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 The counter accumulates when BTS performs periodical scanning.

Unit Grade
C901320020 Number
sampling of BS utilization
power
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 accu-
mulated, 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.

Unit 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.

Unit Grade
level
Definition 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 num-
ber of periodical scannings.

Unit 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 peri-
odically scans the uplink signal level on channels of TRX and ac-
cmulates. During the period of reporting measurement result to
accumulates the uplink signal level value of each scanning.

Unit Grade
level
Definition Number of power scans of UL signal level
Description To get the average uplink signal level received by TRX, BTS period-
ically scans the uplink signal level on channels of TRX and accmu-
lates. 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.

Unit 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 qual-
ity value of each scanning.

Unit Grade
quality
Definition 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 down-
link signal quality is accumulated, the counter increments. During
the period of reporting measurement result to BSC, BTS may per-
form multiple periodical scannings. This counter accumulates the
number of periodical scannings.

Unit Times

quality
Definition Total value of power scans of UL signal quality
Description To get the average uplink signal quality received by TRX, BTS pe-
riodically 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.

Unit Grade
quality
Definition Number of power scans of UL signal quality
Description To get the average uplink signal quality received by TRX, BTS pe-
riodically 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.

Unit 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 The counter counts when BSC receives the reported power control
Point measurement message PC TEST RPT. The measurement point is
B1.

Unit Grade

of UL signal level in regular
scan
Definition Minimum value of UL signal level in regular scan
counters, this counter records the minimum uplink signal level
value.
B1.

Unit Grade
C901320031 Maximum
value obtained in regular
scan of DL signal level
Definition Maximum value obtained in regular scan of DL signal level
counters, this counter records the maximum downlink signal level
value.
B1.

Unit Grade

obtained in regular scan of
DL signal level
Definition Minimum value obtained in regular scan of DL signal level
counters, this counter records the minimum downlink signal level
value.
B1.

Unit 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 peri-
odical scannings.
Measurement When the power control message is received and if the channel is
Point TCH/F, then obtain the BS power in the message and accumulate.
Unit Grade
C901320034 Periodic BS
Power (TCH/F) Search
Times
Definition Periodic BS Power (TCH/F) Search Times

Description This counter counts the number of periodical scanning of BS power

(TCH/F).
Measurement When the power control message is received, if the channel is
Point TCH/F and the message contains BS power information, then the
counter increments.
Unit 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 peri-
odical scannings.
Point TCH/H, then obtain the BS power in the message and accumulate.
Unit Grade
Periodic BS Power (TCH/H)
Search
Definition Number of Periodic BS Power (TCH/H) Search
(TCH/H).
Point TCH/H and the message contains BS power information, then the
counter increments.
Unit 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 peri-
odical scannings.
Point SDCCH, then obtain the BS power in the message and accumulate.
Unit Grade
Periodic BS Power (SDCCH)
Search
Definition Number of Periodic BS Power (SDCCH) Search
(SDCCH).
Measurement When the power control message is received, if the channel is SD-
Point CCH and the message contains BS power information, then the
counter increments.
Unit 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.
Point TCH/F, then obtain the downlink signal level in the message and
accumulate.

Unit Grade
(TCH/F) Search
Definition This counter counts the number of periodical scanning of downlink
signal level (TCH/F).
(TCH/F) of periodical scannings.
Point TCH/F and the message contains downlink signal level informa-
tion, then the counter increments.
Unit Times
C901320041 Sum of
(TCH/H) Search Result
Definition Sum of Periodic DL Signal Level (TCH/H) Search Result
(TCH/H) of periodical scannings.
Point TCH/H, then obtain the downlink signal level in the message and
accumulate.
Unit Grade

(TCH/H) Search
Definition Number of Periodic DL Signal Level (TCH/H) Search
Description This counter counts the number of periodical scanning of downlink
signal level (TCH/H).
Point TCH/H and the message contains downlink signal level informa-
tion, then the counter increments.
Unit 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 (SD-
CCH) of periodical scannings.
Point SDCCH, then obtain the downlink signal level in the message and
accumulate.
Unit Grade
(SDCCH) Search
Definition Number of Periodic DL Signal Level (SDCCH) Search
Description This counter counts the number of periodical scanning of downlink
signal level (SDCCH).

Measurement When the power control message is received, if the channel is SD-
Point CCH and the message contains downlink signal level information,
Unit 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 mea-
sure signaling interaction and data transmission at NS layer of Gb
interface in GPRS service. It also performs statistics for abnormal-
ities 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 The counter starts counting when NSVC link becomes abnormal
Point and stops counting when NSVC link becomes normal. The duration

between the two time points is the time during which NSVC is
unavailable.
Unit Second
Related Features ZGO-05-04-002 Gb over IP
transmission due to network
fault
Definition Number of abnormal cases in NS transmission due to network fault
transmission due to O&M
interference
Definition Number of abnormal cases in NS transmission due to O&M inter-
ference

Chapter 39 NSVC on IPGB HOST Measurement
C901330004 Number
of abnormal cases in
NS transmission due to
equipment fault
Definition 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
transmission due to unknown NSVC.
Measurement During the NS sub layer signaling interaction, the counter accu-
Point mulates the number of signaling transmitted by unknown NSVC.
Unit Times
transmission due to protocol
error
Definition Number of abnormal cases in NS transmission due to protocol error
transmission due to protocol error.

Measurement When the field in NS signaling is inconsistent with that defined in

Point protocol, the counter accumulates.
Unit Times
unsuccess test due to over
max
Definition Number of unsuccess test due to over max
test procedure.
Measurement When the number of NS sub layer's sending NS-ALIVE PDU ex-
Point ceeds 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 Times

Chapter 40
GB Message on IPGB
HOST Measurement
Table of Contents
Overview...................................................................... 2106
C901340001 Number of RA-CAPABILITY message rece-
vied............................................................................. 2107
BSC ............................................................................. 2107
BSC ............................................................................. 2108
sent............................................................................. 2108
sage received................................................................ 2109
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
known ......................................................................... 2117
vice congestion ............................................................. 2117
error............................................................................ 2118
C901340021 Number of status messages sent with Processor
overload....................................................................... 2118


Unknown...................................................................... 2118
tocol error .................................................................... 2119
cessor overload ............................................................. 2120
by BSC......................................................................... 2120
ceived by BSC............................................................... 2121
sent by BSC.................................................................. 2121
sent by BSC.................................................................. 2122
BSC ............................................................................. 2123
ceived by BSC............................................................... 2123
by BSC......................................................................... 2124
sent by BSC.................................................................. 2125
C901340034 Number of DELETE-BSS-PFC-REQ messages re-
ceived 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 mes-
sages 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, RADIO-
STATUS, and DOWNLOAD-BSS-PFC.

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.
FIGURE 2200 MEASUREMENT POINT OF THE NUMBER OF

RECEIVING RA-CAPABILITY MESSAGE
Unit 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
Point ments. The measurement point is A.
Unit Times

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
Unit Times
message sent
Definition Number of RA-CAPABILITY-UPDATE message sent
Description BSC sends the RA-CAPABILITY-UPDATE message to SGSN to re-
quest for the current wireless capability of MS. This counter counts
the number of BSC's sending this message.
Point this counter increments. The measurement point is A1.

Unit 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 When BSC receives a “RA-CAPABILITY-UPDATE-ACK” message
Point from SGSN, this counter increments. The measurement point is
A2.
Unit Times

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
sage.
Point counter increments. The measurement point is A.
Unit Times
sent by BSC due to losing
Definition Number of wireless status messages sent by BSC due to losing
ber of BSC's sending this message due to “Losing wireless associ-
ation with MS”.
sage.
Measurement When BSC sends a RADIO-STATUS message to SGSN due to “Los-
Point ing wireless association with MS”, this counter increments.
Unit Times

sent by BSC due to bad link
quality
Definition Number of wireless status messages sent by BSC due to bad link
quality
ber of BSC's sending this message due to “bad link quality”.
sage.
Unit Times
sent by BSC due to cell
reselection command
Definition Number of wireless status messages sent by BSC due to cell res-
election command
ber of BSC's sending this message due to “cell reselection com-
mand”.
sage.
Unit Times

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 num-
ber of BSC's sending this message.
Measurement When BSC sends a “FLOW-CONTROL-BVC” message, this counter
Point increments. The measuremnt point is A1.
Unit Times
FLOW-CONTROL-BVC-
BSC
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

Unit 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 When BSC sends the “FLOW-CONTROL-MS” message, this counter
Unit Times

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 When BSC receives a “FLOW-CONTROL-MS-ACK” message, this
Unit Times
FLOW-CONTROL-PFC
Definition 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 When BSC sends the “FLOW-CONTROL-PFC” message, this counter

Unit Times
FLOW-CONTROL-PFC-
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 When BSC receives a “FLOW-CONTROL-PFC-ACK” message, this
Unit Times

status messages sent by
BSC
Definition Number of status messages sent by BSC
message.
Measurement When BSC sends the “STATUS” message, this counter increments.
Unit Times
by BSC
Definition Number of status messages received by BSC
message.
Measurement When BSC receives the “STATUS” message, this counter incre-

Unit Times
BVCI Unknown
Measurement When BSC sends a "STATUS" message due to “BVCI Unknown”,
Unit Times
Measurement When BSC sends a "STATUS" message due to “cell service conges-
Unit Times

protocol error
Measurement When BSC sends a "STATUS" message due to “protocol error”, this
Unit Times
Processor overload
Definition Number of status messages sent with Processor overload
message due to “processor overload”.
Measurement When BSC sends a "STATUS" message due to “processor overload”,
Unit Times
with BVCI Unknown
Definition Number of status messages received with BVCI Unknown

Measurement When BSC receives a "STATUS" message due to “BVCI Unknown”,

Unit Times
Measurement When BSC receives a "STATUS" message due to “cell service con-
Unit Times
with protocol error
Measurement When BSC receives a "STATUS" message due to “protocol error”,
Unit Times

message due to “processor overload”.
Measurement When BSC receives a "STATUS" message due to “processor over-
Unit 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 When BSC sends the “DOWNLOAD-BSS-PFC” message, this
Unit 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 cre-
ate or modify a packet flow control context. This counter counts
Unit 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 con-
text. This counter counts the number of BSC's sending this mes-
sage.
Measurement When BSC sends a CREATE-BSS-PFC-ACK message, this counter

Unit 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 re-
quest of SGSN creating or modifying a packet flow control context.
Measurement When BSC sends a CREATE-BSS-PFC-NACK message, this counter
Unit 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 When BSC sends the “MODIFY-BSS-PFC” message, this counter
Unit Times
MODIFY-BSS-PFC-ACK
Definition Number of MODIFY-BSS-PFC-ACK messages received by BSC
Description SGSN sends the MODIFY-BSS-PFC-ACK message to BSC to con-
firm the modification of packet flow control context. This counter
Measurement When BSC receives a MODIFY-BSS-PFC-ACK message, this

Unit 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 When BSC receives a DELETE-BSS-PFC message, this counter in-
Unit 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 When BSC sends a DELETE-BSS-PFC-ACK message, this counter
Unit Times
DELETE-BSS-PFC-REQ
Definition Number of DELETE-BSS-PFC-REQ messages received by BSC

PS-HANDOVER-REQUI
RED messages sent by BSC
Description 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
message. The measurement point is A, as shown in Figure 2222.

REQUIRED MESSAGES SENT BY BSC
Times
PS-HANDOVER-REQUIRE
D-ACK messages received
by BSC
Description 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
Times
PS-HANDOVER-REQUIRE
D-NACK messages received
by BSC
Description If SGSN receives the non-acknowledgement message for PS han-
dover 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 in IP transmission mode. The counter increments when BSC
receives the PS-HANDOVER-REQUIRED-NACK message. The mea-


REQUIRED-NACK MESSAGES RECEIVED BY BSC
Times
PS-HANDOVER-REQUEST
Description 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 mes-
sages received by BSC from SGSN. The counter increments when
BSC receives the PS-HANDOVER-REQUEST message. The mea-


REQUEST MESSAGES RECEIVED BY BSC
Times
PS-HANDOVER-REQUES
T-ACK messages sent by
BSC
SGSN, it implements PS handover flow and sends the PS-HAN-
DOVER-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


REQUEST-ACK MESSAGES SENT BY BSC
Times
PS-HANDOVER-REQUES
T-NACK messages sent by
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 incre-
ments when BSC sends the PS-HANDOVER-REQUEST-NACK mes-
sage. The measurement point is A3, as shown in Figure 2227.

REQUEST-NACK MESSAGES SENT BY BSC
Times
PS-HANDOVER-COMPL
ETE messages sent by BSC

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 incre-
ments when BSC sends the PS-HANDOVER-REQUEST-COMPLETE
message. The measurement point is A, as shown in Figure 2228.

COMPLETE MESSAGES SENT BY BSC
Times
PS-HANDOVER-CANCEL
Description 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
Times
PS-HANDOVER-REQUEST
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 trans-
mission 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 mes-
sage contains the field, the counter increments. The measurement


REQUEST MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Times
C901340044 Number
of CREATE-BSS-PFC
BSC
Description 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


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
ceived.......................................................................... 2140
ceived.......................................................................... 2140
ceived.......................................................................... 2141
ceived.......................................................................... 2141
C901350009 Number of FLUSH-LL message received ......... 2142
C901350010 Number of FLUSH-LL-ACK message sent......... 2142
sent............................................................................. 2143
C901350013 Number of BVC_BLOCK_ACK message re-
ceived.......................................................................... 2144
ceived.......................................................................... 2144
ceived.......................................................................... 2145
sent............................................................................. 2146
C901350019 Number of BVC-RESET-ACK message re-
ceived.......................................................................... 2146
C901350020 Number of PERFORM– LOCATION-REQUEST
message received.......................................................... 2147
message sent ............................................................... 2147
C901350022 Number of PERFORM-LOCATION-ABORT mes-
sage received................................................................ 2148
sent............................................................................. 2148
C901350024 Number of POSITION-RESPONSE message re-
ceived.......................................................................... 2149
C901350025 Number of status messages sent .................. 2149
C901350026 Number of status messages received ............. 2150


known ......................................................................... 2150
vice congestion ............................................................. 2151
error............................................................................ 2151
C901350030 Number of status messages sent with processor
overload....................................................................... 2152
C901350031 Number of status messages sent with semanti-
cally incorrect PDU ........................................................ 2152
mandatory information element....................................... 2153
mandatory IE................................................................ 2153
conditional IE................................................................ 2154
C901350035 Number of status messages sent with unex-
C901350036 Number of status messages sent with condi-
tional IE error ............................................................... 2155
status incompatible error................................................ 2155
unknown ...................................................................... 2156
tocol error .................................................................... 2156
cessor overload ............................................................. 2157
C901350042 Number of status messages received with BVC
blocking ....................................................................... 2157
C901350043 Number of status messages received with se-
mantically incorrect PDU................................................. 2158
C901350044 Number of status messages received with invalid
mandatory IE................................................................ 2158
ing mandatory IE .......................................................... 2159
ing conditional IE........................................................... 2159
C901350047 Number of status messages received with unex-
C901350048 Number of status messages received with con-
ditional IE error............................................................. 2160
tocol 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.

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.
Point ING_CS, the counter increments.
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.
Point ING_PS, the counter increments.
Unit Times
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 When BSS sends the SUSPEND message, the counter increments.
Point
Unit 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 When BSS sends the SUSPEND_ACK message, the counter incre-
Point ments.
Unit Times
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 SUS-
PEND_NACK message to BSS. This counter counts the number of
SUSPEND_NACK messages received by NSE.
sponse when MS requests for terminating GPRS service.
Measurement When BSS sends the SUSPEND_NACK message, the counter in-
Point crements.
Unit 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 When BSS sends the RESUME message, the counter increments.
Point
Unit 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 When BSS sends the RESUME_ACK message, the counter incre-
Point ments.
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.
sponse when MS requests for resuming GPRS service.
Measurement When BSS receives the RESUME_NACK message, the counter in-
Point crements.
Unit 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 When BSS receives the FLUSH_LL message, the counter incre-
Point ments.
Unit Times
FLUSH-LL-ACK message
sent
Definition 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 When BSS sends the FLUSH_LL_ACK message, the counter incre-
Point ments.

Unit Times
LLC-DISCARDED message
sent
Definition Number of LLC-DISCARDED message sent
Description When the LLC PDU stored in BSS is deleted, the LLC_DISCARDED
message is sent to SGSN. This counter counts the number of send-
ing LLC_DISCARDED message from NSE.
Usage The counter is used to find out the storage of LLC PDU in BSS.
Measurement When BSS sends the LLC_DISCARDED message, the counter in-
Point crements.
Unit Times
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.
to block BVC.
Measurement When BSS sends the BVC_BLOCK message, the counter incre-
Point ments.
Unit Times

C901350013 Number
of BVC_BLOCK_ACK
message received
Definition Number of BVC-BLOCK-ACK message received
Description When SGSN receives the BVC_BLOCK message from BSS, it identi-
fies 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.
Usage The counter is used to find out cases when BVC is blocked.
Point increments.
Unit Times
BVC-UNBLOCK message
sent
Description When BSS unblocks the blocked BVC, it will send the BVC_UN-
BLOCK message to SGSN. This counter counts the number of send-
ing BVC_UNBLOCK message from NSE.
to unblock BVC.
Measurement When BSS sends the BVC_UNBLOCK message, the counter incre-
Point ments.
Unit Times
C901350015 Number
of BVC-UNBLOCK-ACK
message received
Definition Number of BVC-UNBLOCK-ACK message received

Description When SGSN receives the BVC_UNBLOCK message from BSS,

it identifies the BVC to be unblocked and replies the BVC_UN-
BLOCK_ACK message to BSS. This counter counts the number of
BVC_UNBLOCK_ACK messages received by NSE.
Usage The counter is used to find out cases when BVC is unblocked.
Point increments.
Unit Times
Description This counter counts the number of PCU sending signaling BVC re-
setting message through Gb interface.
Usage The counter is used to find out the frequency of requesting to
restart BVC due to BVC failure.
Measurement When NSE at BSC sends message of which the type is BVC_RESET
Point and BVCI is zero, the counter increments.
Unit Times
BVC-RESET message
received
Description This counter counts the number of PCU's receiving the signaling
BVC resetting message.
Usage The counter is used to find out cases when BVC is restarted.
Point SET and BVCI is zero, the counter increments.
Unit Times

sent
Definition Number of BVC-RESET-ACK message sent
Description 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 sig-
naling BVC resetting acknowledgement message.
Usage The counter is used to find out cases of SGSN initializing BVC.
Measurement When NSE at BSC sends message of which the type is BVC_RE-
Point SET_ACK and BVCI is zero, the counter increments.
Unit Times
received
Definition Number of BVC-RESET-ACK message received
Description Number of PCU's receiving the signaling BVC resetting acknowl-
edgement message. This counter counts the number of NSE's re-
ceiving signaling BVC resetting acknowledgement message.
Usage The counter is used to find out cases of BVC initialization.
Point SET_ACK and BVCI is zero, the counter increments.
Unit Times

C901350020 Number
of PERFORM–
LOCATION-REQUEST
message received
Definition 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_LOCA-
TION_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.
Point the counter increments.
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 re-
sponse, and then send the result in the PERFORM_LOCATION_RE-
SPONSE 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 re-
quest from SGSN.
Unit Times

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 terminat-
ing location towards BSS.
Unit Times
POSITION-COMMAND
message sent
Definition Number of POSITION_COMMAND message sent
Description BSS triggers the positioning command process by sending PO-
SITION_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.
to implement positioning command to SGSN.
Measurement When BSS sends the POSITION_COMMAND message, the counter
Point increments.
Unit Times

POSITION-RESPONSE
message received
Definition Number of POSITION_RESPONSE message received
Description When SGSN receives the TOM message, SGSN will send the POSI-
TION_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 re-
sponse 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 When BSS receives the POSITION_RESPONSE message, the
Unit Times
Definition Number of status messages sent
Description When NSE receives downlink BSSGP PDU, if there is any abnormal-
ity, 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 When NSE at BSC sends message of which the type is STATUS to
Point the opposite end entity, the counter increments.
Unit Times

Definition Number of status messages received
Description If the BSSGP PDU sent by NSE to SGSN is abnormal, NSE will re-
ceive 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 When NSE receives the STATUS message, the counter increments.
Point
Unit Times
BVCI Unknown
to opposite end entity, the message indicating "BVCI unknown".
to "BVCI unknown" occurring when NSE receives downlink BSSGP
PDU.
Point the message indicates that the abnormality is due to "BVCI un-
known", the counter increments.
Unit Times

to opposite end entity, the message indicating "cell traffic conges-
tion".
to "cell traffic congestion" occurring when NSE receives downlink
BSSGP PDU.
Point the message indicates that the abnormality is due to "cell traffic
congestion", the counter increments.
Unit Times
protocol error
to opposite end entity, the message indicating "Protocol error".
to "Protocol error" occurring when NSE receives downlink BSSGP
PDU.
Point the message indicates that the abnormality is due to "Protocol er-
ror", the counter increments.
Unit Times

processor overload
Definition Number of status messages sent with processor overload
sage to opposite end entity, the message indicating "Processor
overload".
to "Processor overload" occurring when NSE receives downlink
BSSGP PDU.
Point the message indicates that the abnormality is due to "Processor
overload", the counter increments.
Unit Times
semantically incorrect PDU
Definition Number of status messages sent with semantically incorrect PDU
sage to opposite end entity, the message indicating "Semantically
incorrect PDU".
"Semantically incorrect PDU" occurring when NSE receives down-
link BSSGP PDU.
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 informa-
tion element
to opposite end entity, the message indicating "Invalid mandatory
information".
to "Invalid mandatory information" occurring when NSE receives
downlink BSSGP PDU.
Measurement When NSE sends the STATUS message to opposite end entity
Point and the message indicates that the abnormality is due to "Invalid
mandatory information", the counter increments.
Unit Times
missing mandatory IE
Definition Number of status messages sent with missing mandatory IE
to opposite end entity, the message indicating "Missing mandatory
IE".
to "Missing mandatory IE" occurring when NSE receives downlink
BSSGP PDU.
Point the message indicates that the abnormality is due to "Missing
mandatory IE", the counter increments.
Unit Times

missing conditional IE
Definition Number of status messages sent with missing conditional IE
to opposite end entity, the message indicating "Missing conditional
IE".
to "Missing conditional IE" occurring when NSE receives downlink
BSSGP PDU.
Point the message indicates that the abnormality is due to "Missing con-
ditional IE", the counter increments.
Unit Times
unexpected conditional IE
Definition Number of status messages sent with unexpected conditional IE
sage to opposite end entity, the message indicating "Unexpected
conditional IE".
"Unexpected conditional IE" occurring when NSE receives downlink
BSSGP PDU.
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
sage to opposite end entity, the message indicating "Conditional
IE error".
to "Conditional IE error" occurring when NSE receives downlink
BSSGP PDU.
Point the message indicates that the abnormality is due to "Conditional
IE error", the counter increments.
Unit Times
protocol status incompatible
error
Definition Number of status messages sent with protocol status incompatible
error
to opposite end entity, the message indicating "PDU not compatible
with the protocol state".
NSE receives downlink BSSGP PDU.
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 Number of status messages received with BVCI unknown
which indicate "BVCI unknown".
"BVCI unknown" occurring when SGSN receives downlink BSSGP
PDU.
Measurement When PCU receives STATUS message which indicates "BVCI un-
Point known", the counter increments.
Unit Times
sage from SGSN, the message indicating "cell traffic congestion".
to "cell traffic congestion" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "cell traffic
Point congestion", the counter increments.
Unit Times
with protocol error


which indicate "Protocol error".
to "Protocol error" occurring when SGSN receives downlink BSSGP
PDU.
Measurement When PCU receives STATUS message which indicates "Protocol er-
Point ror", the counter increments.
Unit Times
sage from SGSN, the message indicating "Processor overload".
to "Processor overload" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Processor
Point overload", the counter increments.
Unit Times
with BVC blocking
Definition Number of status messages received with BVC blocking
sage from SGSN, the message indicating "BVCI-blocked".
to "BVCI-blocked" occurring when SGSN receives downlink BSSGP
PDU.
Measurement When PCU receives STATUS message which indicates "BVCI-
Point blocked", the counter increments.
Unit Times

with semantically incorrect
PDU
Definition Number of status messages received with semantically incorrect
PDU
which indicate "Semantically incorrect PDU".
"Semantically incorrect PDU" occurring when SGSN receives down-
link BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Semanti-
Point cally incorrect PDU", the counter increments.
Unit Times
with invalid mandatory IE
Definition Number of status messages received with invalid mandatory IE
which indicate "Invalid mandatory information".
to "Invalid mandatory information" occurring when SGSN receives
downlink BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Invalid
Point mandatory information", the counter increments.
Unit Times

with missing mandatory IE
Definition Number of status messages received with missing mandatory IE
which indicate "Missing mandatory IE".
to "Missing mandatory IE" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Missing
Point mandatory IE", the counter increments.
Unit Times
with missing conditional IE
Definition Number of status messages received with missing conditional IE
which indicate "Missing conditional IE".
to "Missing conditional IE" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Missing con-
Point ditional IE", the counter increments.
Unit Times

with unexpected conditional
IE
Definition Number of status messages received with unexpected conditional
IE
which indicate "Unexpected conditional IE".
"Unexpected conditional IE" occurring when SGSN receives down-
link BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Unexpected
Point conditional IE", the counter increments.
Unit Times
with conditional IE error
Definition Number of status messages received with conditional IE error
which indicate "Conditional IE error".
to "Conditional IE error" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "Conditional
Point IE error", the counter increments.
Unit Times

C901350049 Number
of status messages
received with protocol
status incompatible error
Definition Number of status messages received with protocol status incom-
patible error
which indicate "PDU not compatible with the protocol state".
SGSN receives downlink BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "PDU not
Point compatible with the protocol state", the counter increments.
Unit Times
with SGSN congestion
Definition Number of status messages received with SGSN congestion
sage from SGSN, the message indicating "SGSN congestion".
to "SGSN congestion" occurring when SGSN receives downlink
BSSGP PDU.
Measurement When PCU receives STATUS message which indicates "SGSN con-
Point gestion", the counter increments.
Unit Times


Chapter 42
BSSMAP Message
Measurement
Table of Contents
Overview...................................................................... 2165
C901360001 Number of ASSIGNMENT REQUEST mes-
sages........................................................................... 2166
C901360002 Number of ASSIGNMENT COMPLETE mes-
sages........................................................................... 2167
C901360003 Number of ASSIGNMENT FAILURE mes-
sages........................................................................... 2168
C901360004 Number of RESOURCE REQUEST mes-
sages........................................................................... 2168
C901360005 Number of RESOURCE INDICATION mes-
sages........................................................................... 2169
C901360006 Number of PAGING messages ....................... 2170
C901360007 Number of CIPHER MODE COMMAND mes-
sages........................................................................... 2170
C901360008 Number of CIPHER MODE COMPLETE mes-
sages........................................................................... 2171
C901360009 Number of CIPHER MODE REJECT mes-
sages........................................................................... 2172
C901360010 Number of sent CLASSMARK UPDATE mes-
sages........................................................................... 2172
C901360011 Number of received CLASSMARK UPDATE mes-
sages........................................................................... 2173
C901360012 Number of QUEUING INDICATION mes-
sages........................................................................... 2173
C901360013 Number of COMPLETE LAYER 3 INFORMATION
messages ..................................................................... 2174
C901360014 Number of CLASSMARK REQUEST mes-
sages........................................................................... 2175
C901360015 Number of uplink LOAD INDICATION mes-
sages........................................................................... 2175
C901360016 Number of downlink LOAD INDICATION mes-
sages........................................................................... 2176
C901360017 Number of HANDOVER REQUEST mes-
sages........................................................................... 2177
C901360018 Number of HANDOVER REQUIRED mes-
sages........................................................................... 2177
C901360019 Number of HANDOVER COMMAND mes-
sages........................................................................... 2178
C901360020 Number of HANDOVER REQUEST ACK mes-
sages........................................................................... 2179
C901360021 Number of HANDOVER COMPLETE mes-
sages........................................................................... 2180

C901360022 Number of HANDOVER SUCCEEDED mes-

sages........................................................................... 2181
C901360023 Number of HANDOVER CANDIDATE ENQUIRE
messages ..................................................................... 2182
C901360024 Number of HANDOVER CANDIDATE RESPONSE
messages ..................................................................... 2183
C901360025 Number of HANDOVER FAILURE mes-
sages........................................................................... 2183
C901360026 Number of HANDOVER PERFORMED mes-
sages........................................................................... 2184
C901360027 Number of HANDOVER REQUIRED REJECT mes-
sages........................................................................... 2185
C901360028 Number of HANDOVER DETECT mes-
sages........................................................................... 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 mes-
sages........................................................................... 2191
C901360038 Number of DL RESET ACKNOWLEDGE mes-
sages........................................................................... 2192
C901360039 Number of UL OVERLOAD messages .............. 2192
C901360040 Number of DL OVERLOAD messages .............. 2193
C901360041 Number of MSC INVOKE TRACE mes-
sages........................................................................... 2193
C901360042 Number of sent BSS INVOKE TRACE mes-
sages........................................................................... 2194
C901360043 Number of received BSS INVOKE TRACE mes-
sages........................................................................... 2195
C901360044 Number of sent CONNECTIONLESS INFORMA-
TION messages ............................................................. 2195
C901360045 Number of received CONNECTIONLESS INFOR-
MATION 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 mes-
sages........................................................................... 2199
C901360051 Number of PERFORM LOCATION RESPONSE
messages ..................................................................... 2199
C901360052 Number of PERFORM LOCATION ABORT mes-
sages........................................................................... 2200
C901360053 Number of sent BLOCK messages.................. 2200
C901360054 Number of received BLOCK ACK mes-
sages........................................................................... 2201
C901360055 Number of sent UNBLOCK messages ............. 2202
C901360056 Number of received UNBLOCK ACK mes-
sages........................................................................... 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

Chapter 42 BSSMAP Message Measurement
C901360063 Number of UL RESET CIRCUIT ACK mes-

sages........................................................................... 2207
C901360064 Number of DL RESET CIRCUIT ACK mes-
sages........................................................................... 2208
C901360065 Number of UL CIRCUIT GROUP BLOCK mes-
sages........................................................................... 2209
C901360066 Number of DL CIRCUIT GROUP BLOCK mes-
sages........................................................................... 2209
C901360067 Number of UL CIRCUIT GROUP BLOCKING AC-
KNOWLEDGE messages .................................................. 2210
C901360068 Number of DL CIRCUIT GROUP BLOCKING AC-
C901360069 Number of UL CIRCUIT GROUP UNBLOCK mes-
sages........................................................................... 2211
C901360070 Number of DL CIRCUIT GROUP UNBLOCK mes-
sages........................................................................... 2212
C901360071 Number of UL CIRCUIT GROUP UNBLOCKING
ACKNOWLEDGE messages .............................................. 2213
C901360072 Number of DL CIRCUIT GROUP UNBLOCKING
C901360073 Number of UL UNEQUIPPED CIRCUIT mes-
sages........................................................................... 2214
C901360074 Number of DL UNEQUIPPED CIRCUIT mes-
sages........................................................................... 2215
C901360075 Number of CHANGE CIRCUIT messages ......... 2216
C901360076 Number of CHANGE CIRCUIT ACK mes-
sages........................................................................... 2216
C901360077 Number of HANDOVER PERFORMED ACK mes-
sages........................................................................... 2217
C901360078 The count of Sending INTERNAL HANDOVER RE-
QUIRED ....................................................................... 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 mes-
sages........................................................................... 2221
C901360083 Number of UL RESET IP RESOURCE ACKOWN-
LEDGE messages........................................................... 2222
C901360084 Number of DL RESET IP RESOURCE mes-
sages........................................................................... 2222
C901360085 Number of DL RESET IP RESOURCE ACKNOWL-
EDGE messages ............................................................ 2223
Overview
The BSSMAP message measurement performs statistics for various
BSSMAP messages at A-interface. It is used to find out the fre-
quency 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

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 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. Dur-
ing the paging process, MSC can also change mode at radio inter-
face 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 re-
quest messages transmitted at A-interface.
Measurement 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 re-
ceives the RR message ASSIGNMENT COMPLETE from Um inter-
face, it sends an ASSIGNMENT COMPLETE message of A-interface
BSSMAP protocol to MSC. This counter counts the number of as-
signment completion messages in A-interface BSSMAP messages
sent to MSC from BSC.
Usage The counter is used to find out the frequency of assignment com-
pletion messages transmitted at A-interface.
Measurement When BSC sends the ASSIGNMENT COMPLETE message to MSC,
FIGURE 2235 MEASUREMENT POINT OF BSC SENDING

ASSIGNMENT COMPLETE MESSAGE TO MSC
Unit Times

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 When BSC sends the ASSIGNMENT FAILURE message to MSC, the
Point counter increments. The measurement point is A

ASSIGNMENT FAILURE MESSAGE TO MSC
Unit Times
RESOURCE REQUEST
messages
Definition Number of RESOURCE REQUEST messages
Description MSC sends the RESOURCE REQUEST message to BSC, the mes-
sage 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 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 re-
source 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 When BSC sends the RESOURCE INDICATION message to MSC,
FIGURE 2238 MEASUREMENT POINT OF BSC SENDING RESOURCE

INDICATION MESSAGE TO MSC
Unit Times

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 When BSC receives the PAGING message, the counter increments.
Point The measurement point is A.
FIGURE 2239 MEASUREMENT POINT OF MSC SENDING PAGING

MESSAGE TO BSC
Unit Times
CIPHER MODE COMMAND
messages
Definition 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 mes-
sages 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 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
COMPLETE messages transmitted at A-interface.
Measurement 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

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-inter-
face BSSMAP messages sent to MSC from BSC.
REJECT messages transmitted at A-interface.
Measurement 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 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 CLASS-
MARK UPDATE messages transmitted at A-interface.
Measurement 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 CLASS-
MARK UPDATE messages transmitted at A-interface.
Measurement When BSC receives the CLASSMARK UPDATE message, the counter
Point 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

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 INDI-
CATION messages transmitted at A-interface.
Measurement 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 INFORMA-
TION 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 When BSC sends the COMPLETE LAYER 3 INFORMATION message
Point to MSC, the counter increments. The measurement point is A.
FIGURE 2246 MEASUREMENT POINT OF BSC SENDING COMPLETE

LAYER 3 INFORMATION MESSAGE TO MSC

Unit Times
CLASSMARK REQUEST
messages
Definition Number of CLASSMARK REQUEST messages
Description When MSC wants MS classmark information, it sends a CLASS-
MARK REQUEST message to BSC. This counter counts the number
of CLASSMARK REQUEST messages in A-interface BSSMAP mes-
Usage The counter is used to find out the frequency of CLASSMARK RE-
QUEST messages transmitted at A-interface.
Measurement 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 re-
porting 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-inter-
Usage The counter is used to find out the frequency of uplink load indi-
cation messages transmitted at A-interface.

Measurement 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 When BSC receives the LOAD INDICATION message, the counter
FIGURE 2249 MEASUREMENT POINT OF MSC SENDING LOAD

INDICATION MESSAGE TO BSC
Unit 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 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 mes-
sages in A-interface BSSMAP messages sent to MSC from BSC.
Usage The counter is used to find out the frequency of HANDOVER RE-
QUIRED messages transmitted at A-interface.
Measurement When BSC sends the HANDOVER REQUIRED message to MSC, the

FIGURE 2251 INTER-BSC HANDOVER PROCESS INITIATED BY BSC
Unit Times
HANDOVER COMMAND
messages
Definition 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 HAN-
DOVER COMMAND messages in A-interface BSSMAP messages re-
ceived by BSC.
Usage The counter is used to find out the frequency of HANDOVER COM-
MAND messages transmitted at A-interface.
Measurement 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 suc-
cessfully 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
QUEST ACK messages transmitted at A-interface.
Measurement When BSC sends the HANDOVER REQUEST ACK message to MSC,

Unit Times
HANDOVER COMPLETE
messages
Definition 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 COM-
PLETE messages transmitted at A-interface.
Measurement 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 SUC-
CEEDED messages transmitted at A-interface.
Measurement When BSC receives the HANDOVER SUCCEEDED message, the

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 maxi-
mum number of handover requests that can be triggered and can-
didate cells that can be used for handover. This counter counts the
number of HANDOVER CANDIDATE ENQUIRE messages in A-inter-
face BSSMAP messages received by BSC.
Usage The counter is used to find out the frequency of HANDOVER CAN-
DIDATE ENQUIRE messages transmitted at A-interface.
Measurement When BSC receives the HANDOVER CANDIDATE ENQUIRE mes-
Point sage, the counter increments. The measurement point is A1.
FIGURE 2256 PROCESS OF MSC SENDING HANDOVER CANDIDATE

ENQUIRE MESSAGE TO BSC

Unit Times
HANDOVER CANDIDATE
RESPONSE messages
Definition Number of HANDOVER CANDIDATE RESPONSE messages
Description After BSC receives the HANDOVER CANDIDATE ENQUIRE mes-
sage, 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 RE-
SPONSE messages in A-interface BSSMAP messages sent to MSC
from BSC.
Usage The counter is used to find out the frequency of HANDOVER CAN-
DIDATE RESPONSE messages transmitted at A-interface.
Measurement When BSC sends the HANDOVER CANDIDATE RESPONSE message
Point 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

Description This counter counts the number of HANDOVER FAILURE messages

Usage The counter is used to find out the frequency of HANDOVER FAIL-
URE messages transmitted at A-interface.
Measurement 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-in-
terface BSSMAP messages sent to MSC from BSC.
Usage The counter is used to find out the frequency of HANDOVER PER-
FORMED messages transmitted at A-interface.
Measurement When BSC sends the HANDOVER PERFORMED message to MSC,

PERFORMED MESSAGE TO MSC
Unit Times

HANDOVER REQUIRED
REJECT messages
Definition Number of HANDOVER REQUIRED REJECT messages
Description This counter counts the number of HANDOVER REQUIRED REJECT
QUIRED REJECT messages transmitted at A-interface.
Measurement 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 DE-
TECT messages transmitted at A-interface.
Measurement When BSC sends the HANDOVER DETECT message to MSC, the


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 When BSC receives the CLEAR COMMAND message, the counter
FIGURE 2262 CLEAR PROCESS
Unit Times

C901360030 Number
of CLEAR COMPLETE
messages
Definition Number of CLEAR COMPLETE messages
Description After BSC receives the CLEAR COMMAND message, it starts corre-
sponding release process and returns the CLEAR COMPLETE mes-
sage 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 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 When BSC sends the CLEAR REQUEST message to MSC, the

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 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 Number of UL CONFUSION messages
Description 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 mes-

sages sent to MSC from BSC.
Usage The counter is used to find out the frequency of uplink CONFUSION
Measurement 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 mes-
Usage The counter is used to find out the frequency of downlink CONFU-
SION messages transmitted at A-interface.
Measurement When BSC receives the CONFUSION message, the counter incre-
FIGURE 2267 MEASUREMENT POINT OF MSC SENDING CONFUSION

MESSAGE TO BSC
Unit Times

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 mes-
sages transmitted at A-interface.
Measurement When BSC sends the RESET message to MSC, the counter incre-
FIGURE 2268 UPLINK RESET PROCESS
Unit Times
RESET messages
Definition 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 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 RE-
SET 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 AC-
KNOWLEDGE messages transmitted at A-interface.
Measurement When BSC sends the RESET ACKNOWLEDGE message to MSC, the
FIGURE 2270 DOWNLINK RESET PROCESS
Unit Times

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 re-
leases 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
ACKNOWLEDGE messages transmitted at A-interface.
Measurement When BSC receives the RESET ACKNOWLEDGE message, the
FIGURE 2271 UPLINK RESET PROCESS
Unit Times
OVERLOAD messages
Definition 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 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 periodi-
cally. This counter counts the number of OVERLOAD messages in
Usage The counter is used to find out the frequency of downlink OVER-
LOAD messages transmitted at A-interface.
Measurement When BSC receives the OVERLOAD message, the counter incre-
FIGURE 2273 MEASUREMENT POINT OF MSC SENDING OVERLOAD

MESSAGE TO BSC
Unit Times
MSC INVOKE TRACE
messages
Definition Number of MSC INVOKE TRACE messages

Description When MSC needs to generate tracing records of specified calls for
BSC, it will send a MSC INVOKE TRACE message to the corre-
sponding 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 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 corre-
sponding 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 IN-
VOKE TRACE messages transmitted at A-interface.
Measurement When BSC sends the BSS INVOKE TRACE message to MSC, the
FIGURE 2275 MEASUREMENT POINT OF BSC SENDING BSS INVOKE

TRACE MESSAGE TO MSC

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 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 INFORMA-
TION messages in A-interface BSSMAP messages sent by BSC.
Usage The counter is used to find out the frequency of sending CONNEC-
TIONLESS INFORMATION messages transmitted at A-interface.
Measurement When BSC sends the CONNECTIONLESS INFORMATION message
Point to MSC, the counter increments. The measurement point is A.


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 INFORMA-
TION messages in A-interface BSSMAP messages received by BSC.
Usage The counter is used to find out the frequency of receiving CONNEC-
TIONLESS INFORMATION messages transmitted at A-interface.
Measurement When BSC receives the CONNECTIONLESS INFORMATION mes-
Point sage, 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 Number of SUSPEND messages
Description 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 mes-
Measurement When BSC sends the SUSPEND message to MSC, the counter in-
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 When BSC sends the RESUME message to MSC, the counter incre-
FIGURE 2280 MEASUREMENT POINT OF BSC SENDING RESUME

MESSAGE TO MSC
Unit Times

Common ID messages
Definition Number of Common ID messages
Description This counter counts the number of Common ID messages in A-in-
terface BSSMAP messages received by BSC.
Usage The counter is used to find out the frequency of Common ID mes-
Measurement When BSC receives the Common ID message, the counter incre-
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 When BSC receives the LSA INFORMATION message, the counter
FIGURE 2282 MEASUREMENT POINT OF MSC SENDING LSA

INFORMATION MESSAGE TO BSC

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 LOCA-
TION REQUEST messages transmitted at A-interface.
Measurement 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 RE-
from BSC.
TION RESPONSE messages transmitted at A-interface.
Measurement When BSC sends the PERFORM LOCATION RESPONSE message to
Point MSC, the counter increments. The measurement point is A2.

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
TION ABORT messages transmitted at A-interface.
Measurement 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 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 When BSC sends the BLOCK message to MSC, the counter incre-
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 han-
dling 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 When BSC receives the BLOCK ACK message, the counter incre-

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 When BSC sends the UNBLOCK message to MSC, the counter in-
FIGURE 2288 PROCESS OF BSC SENDING UNBLOCK MESSAGE TO

MSC
Unit 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-inter-
face BSSMAP messages received by BSC.
Usage The counter is used to find out the frequency of receiving UNBLOCK
Measurement When BSC receives the UNBLOCK ACK message, the counter in-
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 When BSC receives the BLOCK message, the counter increments.

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 han-
dling 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 When BSC sends the BLOCK ACK message to MSC, the counter
FIGURE 2291 PROCESS OF MSC SENDING BLOCK MESSAGE TO BSC
Unit 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 num-
ber of UNBLOCK messages in A-interface BSSMAP messages re-
ceived by BSC.
Usage The counter is used to find out the frequency of receiving UNBLOCK
Measurement When BSC receives the UNBLOCK message, the counter incre-
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-inter-
Usage The counter is used to find out the frequency of sending UNBLOCK
Measurement When BSC sends the UNBLOCK ACK message to MSC, the counter

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 mes-
sage 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 CIR-
CUIT messages transmitted at A-interface.
Measurement When BSC sends the RESET CIRCUIT message to MSC, the counter
FIGURE 2294 PROCESS OF BSC SENDING RESET CIRCUIT MESSAGE

TO MSC
Unit Times

RESET CIRCUIT messages
Definition Number of DL RESET CIRCUIT messages
Description When MSC detects that an abnormal SCCP connection release
sage to BSC. This counter counts the number of RESET CIRCUIT
CIRCUIT messages transmitted at A-interface.
Measurement When BSC receives the RESET CIRCUIT message, the counter in-
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
sage 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 CIR-
CUIT ACK messages transmitted at A-interface.
Measurement When BSC sends the RESET CIRCUIT ACK message to MSC, the

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
sage 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
CIRCUIT ACK messages transmitted at A-interface.
Measurement When BSC receives the RESET CIRCUIT ACK message, the counter
FIGURE 2297 PROCESS OF BSC SENDING RESET CIRCUIT MESSAGE

TO MSC
Unit 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 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 When BSC receives the CIRCUIT GROUP BLOCK message, the

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 mes-
sages
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
GROUP BLOCKING ACKNOWLEDGE messages transmitted at A-in-
terface.
Measurement When BSC sends the CIRCUIT GROUP BLOCKING ACKNOWLEDGE
Point message to MSC, the counter increments. The measurement point
is A2.
FIGURE 2300 PROCESS OF MSC SENDING CIRCUIT GROUP BLOCK

MESSAGE TO BSC
Unit Times

C901360068 Number
of DL CIRCUIT
GROUP BLOCKING
Definition Number of DL CIRCUIT GROUP BLOCKING ACKNOWLEDGE mes-
sages
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
GROUP BLOCKING ACKNOWLEDGE messages transmitted at A-in-
terface.
Measurement When BSC receives the CIRCUIT GROUP BLOCKING ACKNOWL-
Point EDGE 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 Number of UL CIRCUIT GROUP UNBLOCK messages
Description When BSC decides to unblock some terrestrial circuit of A-inter-
face, it sends a CIRCUIT GROUP UNBLOCK message to MSC. This

counter counts the number of CIRCUIT GROUP UNBLOCK mes-

sages in A-interface BSSMAP messages sent to MSC from BSC.
GROUP UNBLOCK messages transmitted at A-interface.
Measurement 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-inter-
face, it sends a CIRCUIT GROUP UNBLOCK message to BSC. This
counter counts the number of CIRCUIT GROUP UNBLOCK mes-
GROUP UNBLOCK messages transmitted at A-interface.
Measurement When BSC receives the CIRCUIT GROUP UNBLOCK message, the
FIGURE 2303 PROCESS OF MSC SENDING CIRCUIT GROUP

UNBLOCK MESSAGE TO BSC

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-inter-
face, 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 ACKNOWL-
EDGE messages in A-interface BSSMAP messages sent to MSC
from BSC.
GROUP UNBLOCKING ACKNOWLEDGE messages transmitted at
A-interface.
Measurement When BSC sends the CIRCUIT GROUP UNBLOCKING ACKNOWL-
Point EDGE message to MSC, the counter increments. The measure-
ment point is A2.
FIGURE 2304 PROCESS OF MSC SENDING CIRCUIT GROUP

UNBLOCK MESSAGE TO BSC
Unit Times

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-in-
terface, 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 CIR-
CUIT GROUP UNBLOCKING ACKNOWLEDGE messages transmitted
at A-interface.
Measurement When BSC receives the CIRCUIT GROUP UNBLOCKING ACKNOWL-
Point EDGE 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 Number of UL UNEQUIPPED CIRCUIT messages
Description 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 UN-
EQUIPPED CIRCUIT messages transmitted at A-interface.
Measurement 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 UN-
EQUIPPED CIRCUIT messages transmitted at A-interface.
Measurement When BSC receives the UNEQUIPPED CIRCUIT message, the

UNEQUIPPED CIRCUIT MESSAGE TO BSC
Unit Times

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 cir-
cuit 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 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 Number of CHANGE CIRCUIT ACK 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 cir-
cuit 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 mes-

Usage The counter is used to find out the frequency of CHANGE CIRCUIT
Measurement 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 Number of HANDOVER PERFORMED ACK messages
Description This counter counts the number of HANDOVER PERFORMED ACK
messages received by BSC from MSC.
This counter counts the number of CHANGE CIRCUIT ACK mes-
Usage The counter is used to find out cases of BSC receiving the HAN-
DOVER PERFORMED ACK message from MSC.
Measurement When BSC receives the HANDOVER PERFORMED ACK message
Point from MSC, the counter increments.
Unit Times
C901360078 The count

of Sending INTERNAL
HANDOVER REQUIRED

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 3GPP TS 48008


of Receiving INTERNAL
HANDOVER COMMAND
Description 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
FIGURE 2311 MEASUREMENT POINT OF THE COUNT OF RECEIVING

INTERNAL HANDOVER COMMAND


of Receiving INTERNAL
HANDOVER REJECT
Description 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
FIGURE 2312 MEASUREMENT POINT OF THE COUNT OF RECEIVING

INTERNAL HANDOVER REJECT
INTERNAL HANDOVER
ENQUIRY messages
Description This counter counts the number of INTERNAL HANDOVER EN-
QUIRY 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
Description This counter counts the number of IP resource resettings initiated
by BSC towards MSC. OMCR initiates the IP resource resetting re-
quest, and the IPRSCRST module initiates the IP resource reset-
ting 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 mea-
Unit Times

UL RESET IP RESOURCE
ACKOWNLEDGE messages
Description This counter counts the number of IP resource resetting response
messages sent to MSC from BSC. MSC initiates IP resource re-
setting towards BSC, and the IPRSCRST module at OMP sends IP
resource resetting response to MSC through the ADispatch mod-
ule. 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
Description This counter counts the number of IP resource resetting requests
initiated by MSC towards BSC. MSC initiates the IP resource re-
setting requests towards the IPRSCRST module through the ADis-
patch module. When the ADispatch module receives the IP re-
source resetting request from MSC, the counter increments. The

FIGURE 2316 MSC INITIATING IP RESOURCE RESETTING FLOW
Unit Times
DL RESET IP RESOURCE
Description 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


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 up-
link/downlink DTAP message, BSSMAP message, and received in-
correct BSSMAP message. Statistic unit in this measurement is
CMP.
DTAP messages
Definition Number of UL DTAP messages
Description This counter counts the number of A-interface DTAP messages sent
to MSC from BSC.
This counter counts the number of HANDOVER CANDIDATE RE-
from BSC.
Usage The counter analyzes the frequency of uplink DTAP messages

Measurement The counter counts when BSC sends the DTAP message to MSC.
Point The measurement point is A.

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 The counter counts when BSC receives the Connection Indication
Point 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 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 mes-
sage, or UnitData Request message.
Usage The counter analyzes the frequency of uplink BSSMAP messages
Measurement The counter counts when BSC sends the Connection Request mes-
Point sage, Data Request message, or UnitData Request message to
MSC, these messages containing BSSMAP message. The mea-
surement 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 Con-
nection Indication message, Connection Confirm message, Data
Indication message, and UnitData Indication message.
Usage The counter analyzes the frequency of downlink BSSMAP messages
Measurement The counter counts when BSC receives the Connection Indica-
Point tion message, Connection Confirm message, Data Indication mes-
sage, 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

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 in-
clude L3 message with zero length, BSSMAP message of which the
length does not match the length of its contained L3 message, de-
coding error, or messge type error.
Usage The counter analyzes the frequency of received incorrect BSSMAP
Measurement The counter counts when BSC receives incorrect BSSMAP mes-
Point sage.
Unit Times
chosen for MSC Load share
by NULL_NRI
Definition Number of chosen for MSC Load share by NULL_NRI
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 The counter counts when iBSC chooses an appropriate MSC route
Point for MS access.
Unit 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 The counter counts when iBSC chooses an appropriate MSC route
Point for MS access.
Unit Times


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 cir-
cuits ............................................................................ 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 statis-
tics for the availability of terrestrial resource at A-interface, in-
cluding 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-

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 Mean number of available trunk circuits
Description This counter counts the average number of trunk circuits that can
be used normally.
Usage The counter reflects the current trunk circuit usage.
Measurement The counter counts when system periodically queries database for
Point circuit information.
Unit Times

of unavailable trunk circuits
Definition Mean number of unavailable trunk circuits
Description This counter counts the average number of trunk circuits that can
not be used normally, including the number of circuits being occu-
pied and the number of circuits being blocked.
Usage The counter reflects the current trunk circuit usage.
Unit Times
C901380003 Maximum
number of busy trunk circuits
Definition 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 There are three measurement points for the maximum number of
Point busy trunk circuits.

Chapter 44 Terrestrial Resource Availability Measurement
� 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.
Unit Times
C901380004 Busy time of

trunk circuit
Definition Busy time of trunk circuit
Description This counter counts the total time of all trunk circuits being occu-
pied during the measurement period.
Usage The counter reflects the busy condition of trunk circuits.
Measurement There are three measurement points for the busy time of trunk
Point 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 oc-
cupation time and accumulates.
Unit Second
C901380005 Congestion
time of trunk circuit
Definition Congestion time of trunk circuit
Description This counter counts the total time of failing to request trunk circuit
Usage The counter reflects the congestion condition of trunk circuits.
Measurement There are three measurement points for the congestion time of
Point trunk circuits.
� Before the trunk circuit is attempted to be occupied, if the con-
gestion identifier is set, then the counter calculates the conges-
tion time and accumulates.

� 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 accu-
mulates.
Unit Second

of available UDP port
Definition Mean number of available UDP port
Description 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.
Unit Times

of unavailable UDP port
Definition Mean number of unavailable UDP port
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.
Unit Times

allocation AIPB board
success
Definition Number of allocation AIPB board success
Description This counter counts the number of allocating AIPB board success-
fully. The RANCS module receives the EV_RANUMC_RADIO_AP-
PLY 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 When the request of AIPB board from database is returned suc-
Point cessfully, the counter accumulates. The measurement point is A.
FIGURE 2322 REQUESTING RESOURCE FROM DATABASE

SUCCESSFULLY
Unit 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 allo-
cation failure.
Measurement When the request of AIPB board from database fails, the counter
Point accumulates. The measurement point is A.

FIGURE 2323 REQUESTING RESOURCE FROM DATABASE FAILURE
Unit 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 oc-
cupied.
Usage The counter is used to find out the maximum number of UDP ports
being occupied.
Point
� 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.
Unit Times
successful one time request
UDP port to AIPB
Definition 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 mes-
sage, and after requesting database for AIPB resource success-
fully, 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 re-
questing AIPB board for UDP port through only one request.
Measurement When the connection succeeds and the requesting AIPB board for
Point UDP port succeeds through only one request, the counter accu-
mulates. The measurement point is A

SUCCESSFULLY
Unit Times
successful two time request
UDP port to AIPB
Definition 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.
questing AIPB board for UDP port through two requests.

Point UDP port succeeds after two requests, the counter accumulates.
The measurement point is A.

SUCCESSFULLY
Unit Times
C901380013 Number
of successful three time
request UDP port to AIPB
Definition 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.
questing AIPB board for UDP port through three requests.
Point UDP port succeeds after three requests, the counter accumulates.
The measurement point is A.


SUCCESSFULLY
Unit Times
failure request UDP port to
AIPB
Definition Number of failure request UDP port to AIPB
Description 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 re-
questing 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 When the connection failure message is returned, the counter ac-
Point cumulates. The measurement point is A.
FIGURE 2327 REQUESTING RESOURCE FROM DATABASE FAILURE
Unit Times

C901380015 Seizure
duration of UDP port
Definition Seizure duration of UDP port
Description This counter counts the total time of UDPPort being occupied.
Usage The counter is used to find out the total time of UDPPort being
occupied.
Point
� Before UDPPort is occupied successfully, the counter calculates
the occupation time and accumulates.
� Before UDPPort is released, the counter calculates the occupa-
tion time and accumulates.
� During periodical measurement, the counter calculates the oc-
cupation time and accumulates.
Unit 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 con-
sistent, 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 After the call is established, BSC and MGW negotiate the RTP trans-
Point mission mode. When control plane receives the RTP_MUX_RPT
message from user plane, if the RTP multiplexing mode is not ap-
plied, the counter counts. The measurement point is A, as shown
in Figure 2328.

FIGURE 2328 THE TIMES OF USER PLANE TRANSPORT WITHOUT RTP

MULTIPLEXING
Unit Times
C901380017 The times

of RTP multiplexing
applied without RTP header
compression
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 multi-
plexing mode in AoIP call at BSC side.
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 RTP MULTIPLEXING APPLIED WITHOUT RTP

HEADER COMPRESSION
Unit Times

C901380018 The times

of RTP multiplexing
applied with RTP header
compression
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.
message from user plane, if the compressed RTP multiplexing
mode is applied, the counter counts. The measurement point is
FIGURE 2330 THE TIMES OF RTP MULTIPLEXING APPLIED WITH RTP

HEADER COMPRESSION
Unit Times

of busy trunk circuits
Description 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 ac-
tive-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.
Usage This counter is used to find out the occupation of trunk circuits.

Measurement 1. When BSC receives the release command and releases the
Point 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 ter-

restrial circuit, the counter counts. The measurement point is
FIGURE 2332 STANDBY UMC DATABASE BEING RELEASED
Unit Times


of seizure UDP port
Description This counter counts the average number of occupied UDP ports.
Usage The counter is used to find out the average number of occupied
UDP ports.
Measurement IPA performance statistics is implemented when Oms reports data.
Point 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 TO DATABASE
Unit Times

Chapter 45
Ater Message
Measurement
Table of Contents
Overview...................................................................... 2247
C901390001 Number of UL BLOCK Ater single CIRCUIT mes-
sages........................................................................... 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 mes-
sages........................................................................... 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 mes-
sages........................................................................... 2250
C901390010 Number of DL RESET Ater CIRCUIT mes-
sages........................................................................... 2250
C901390011 Number of UL RESET Ater CIRCUIT ACKNOWL-
EDGE messages ............................................................ 2251
C901390012 Number of DL RESET Ater CIRCUIT ACKNOWL-
EDGE messages ............................................................ 2251
C901390013 Number of UL BLOCK Ater GROUP CIRCUIT mes-
sages........................................................................... 2252
C901390014 Number of DL BLOCK Ater GROUP CIRCUIT mes-
sages........................................................................... 2252
C901390015 Number of UL BLOCKING Ater GROUP CIRCUIT
C901390016 Number of DL BLOCKING Ater GROUP CIRCUIT
C901390017 Number of UL UNBLOCK GROUP CIRCUIT mes-
sages on Ater................................................................ 2253
C901390018 Number of DL UNBLOCK Ater GROUP CIRCUIT
messages ..................................................................... 2254
C901390019 Number of UL UNBLOCKING Ater GROUP CIR-
CUIT ACKNOWLEDGE messages ...................................... 2254
C901390020 Number of DL UNBLOCKING Ater GROUP CIR-
CUIT ACKNOWLEDGE messages ...................................... 2254
C901390021 Number of UL UNEQUIPPED Ater CIRCUIT mes-
sages........................................................................... 2255

C901390022 Number of DL UNEQUIPPED Ater CIRCUIT mes-

sages........................................................................... 2255
C901390023 Number of UL BLOCK A CIRCUIT mes-
sages........................................................................... 2256
C901390024 Number of DL BLOCKING A CIRCUIT ACKNOWL-
EDGE messages ............................................................ 2256
C901390025 Number of UL UNBLOCK A CIRCUIT mes-
sages........................................................................... 2256
C901390026 Number of DL UNBLOCKING A CIRCUIT AC-
C901390027 Number of DL BLOCK A CIRCUIT mes-
sages........................................................................... 2257
C901390028 Number of UL BLOCKING A CIRCUIT ACKNOWL-
EDGE messages ............................................................ 2257
C901390029 Number of DL UNBLOCK A CIRCUIT mes-
sages........................................................................... 2258
C901390030 Number of UL UNBLOCKING A CIRCUIT AC-
C901390031 Number of UL BLOCK A CIRCUIT GROUP mes-
sages........................................................................... 2258
C901390032 Number of DL BLOCK A CIRCUIT GROUP mes-
sages........................................................................... 2259
C901390033 Number of UL BLOCKING A CIRCUIT GROUP AC-
C901390034 Number of DL BLOCKING A CIRCUIT GROUP AC-
C901390035 Number of UL UNBLOCK A CIRCUIT GROUP mes-
sages........................................................................... 2260
C901390036 Number of DL UNBLOCK A CIRCUIT GROUP mes-
sages........................................................................... 2260
C901390037 Number of UL UNBLOCKING A CIRCUIT GROUP
C901390038 Number of DL UNBLOCKING A CIRCUIT GROUP
C901390039 Number of UL UNEQUIPPED A CIRCUIT mes-
sages........................................................................... 2261
C901390040 Number of DL UNEQUIPPED A CIRCUIT mes-
sages........................................................................... 2262
C901390041 Number of UL Ater RESET messages.............. 2262
C901390042 Number of DL Ater RESET messages ............. 2262
C901390043 Number of UL Ater RESET ACKNOWLEDGE mes-
sages........................................................................... 2263
C901390044 Number of DL Ater RESET ACKNOWLEDGE mes-
sages........................................................................... 2263
C901390045 Number of UL Ater CONFUSION mes-
sages........................................................................... 2263
C901390046 Number of DL Ater CONFUSION mes-
sages........................................................................... 2264
C901390047 Number of RESOURCE REQUEST mes-
sages........................................................................... 2264
C901390048 Number of RESOURCE INDICATION mes-
sages........................................................................... 2264
C901390049 Number of RESOURCE NON-INDICATION mes-
sages........................................................................... 2265
C901390050 Number of resource release request mes-
sages........................................................................... 2265
C901390051 Number of resource release acknowledge mes-
sages........................................................................... 2266
C901390052 Number of resource failure messages ............ 2266
C901390053 Number of TFO status messages ................... 2266

Chapter 45 Ater Message Measurement
C901390054 Number of TFO common voice type mes-

sages........................................................................... 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 AterDis-
patch according to iTC office.
BLOCK Ater single CIRCUIT
messages
Definition Number of UL BLOCK Ater single CIRCUIT messages
Description This counter counts the number of “BLOCK” messages sent by BSC
to iTC.
Measurement When BSC sends a “BLOCK” message, this counter increments.
Point
Unit Times
Related Features 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 When BSC receives a “BLOCKING ACKNOWLEDGE” message, this
Unit Times

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 When BSC sends an “UNBLOCK” message, this counter incre-
Point ments.
Unit 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 When BSC receives an “UNBLOCKING ACKNOWLEDGE” message,
Unit Times
BLOCK Ater single CIRCUIT
messages
Definition Number of DL BLOCK Ater single CIRCUIT messages
Description This counter counts the number of “BLOCK” messages received by
BSC from iTC.

Measurement When BSC receives a “BLOCK” message, this counter increments.

Point
Unit 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 When BSC sends a “BLOCKING ACKNOWLEDGE” message, this
Unit 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 When BSC receives an “UNBLOCK” message, this counter incre-
Point ments.
Unit Times

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 When BSC sends an “UNBLOCKING ACKNOWLEDGE” message,
Unit 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 When BSC sends a “RESET CIRCUIT” message, this counter incre-
Point ments.
Unit Times
DL RESET Ater CIRCUIT
messages
Definition Number of DL RESET Ater CIRCUIT messages
Description This counter counts the number of “RESET CIRCUIT” messages
received by BSC from iTC.

Measurement When BSC receives a “RESET CIRCUIT” message, this counter in-
Point crements.
Unit Times
UL RESET Ater CIRCUIT
Definition Number of UL RESET Ater CIRCUIT ACKNOWLEDGE messages
Description This counter counts the number of “RESET CIRCUIT ACKNOWL-
EDGE” messages sent by BSC to iTC.
Measurement When BSC sends a “RESET CIRCUIT ACKNOWLEDGE” message,
Unit Times
DL RESET Ater CIRCUIT
Definition Number of DL RESET Ater CIRCUIT ACKNOWLEDGE messages
Description This counter counts the number of “RESET CIRCUIT ACKNOWL-
EDGE” messages received by BSC from iTC.
Measurement When BSC receives a “RESET CIRCUIT ACKNOWLEDGE” message,
Unit Times

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” mes-
sages sent by BSC to iTC.
Measurement When BSC sends a “BLOCK CIRCUIT GROUP” message, this
Unit 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” mes-
sages received by BSC from iTC.
Measurement When BSC receives a “BLOCK CIRCUIT GROUP” message, this
Unit Times
BLOCKING Ater GROUP
CIRCUIT ACKNOWLEDGE
messages
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 When BSC sends a “BLOCKING CIRCUIT GROUP ACKNOWLEDGE”

Point message, this counter increments.
Unit 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 When BSC receives a “BLOCKING CIRCUIT GROUP ACKNOWL-
Point EDGE” message, this counter increments.
Unit 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 When BSC sends an UL UNBLOCK GROUP CIRCUIT messages on
Point Ater, this counter increments.
Unit Times

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 When BSC receives an “UNBLOCK CIRCUIT GROUP” message, this
Unit 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 When BSC sends an “UNBLOCKING CIRCUIT GROUP ACKNOWL-
Unit Times
UNBLOCKING Ater GROUP
CIRCUIT ACKNOWLEDGE
messages
Definition Number of DL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE
messages

Description This counter counts the number of “UNBLOCKING CIRCUIT GROUP

Measurement When BSC receives an “UNBLOCKING CIRCUIT GROUP ACKNOWL-
Unit Times
UL UNEQUIPPED Ater
CIRCUIT messages
Definition Number of UL UNEQUIPPED Ater CIRCUIT messages
Description This counter counts the number of “UNEQUIPPED CIRCUIT” mes-
Measurement When BSC sends an “UNEQUIPPED CIRCUIT” message, this
Unit Times
DL UNEQUIPPED Ater
CIRCUIT messages
Definition Number of DL UNEQUIPPED Ater CIRCUIT messages
Description This counter counts the number of “UNEQUIPPED CIRCUIT” mes-
Measurement When BSC receives an “UNEQUIPPED CIRCUIT” message, this
Unit Times

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 When BSC sends a “BLOCK A CIRCUIT” message, this counter in-
Point crements.
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 AC-
KNOWLEDGE” messages received by BSC from iTC.
Measurement When BSC receives a BLOCKING A CIRCUIT ACKNOWLEDGE” mes-
Point sage, this counter increments.
Unit Times
UL UNBLOCK A CIRCUIT
messages
Definition Number of UL UNBLOCK A CIRCUIT messages
Description This counter counts the number of “UNBLOCK A CIRCUIT” mes-
Measurement When BSC sends an “UNBLOCK A CIRCUIT” message, this counter
Point increments.
Unit Times

UNBLOCKING A CIRCUIT
Definition Number of DL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages
Description This counter counts the number of “UNBLOCKING A CIRCUIT AC-
Measurement 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 When BSC receives a “BLOCK A CIRCUIT” message, this counter
Point 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 AC-
KNOWLEDGE” messages sent by BSC to iTC.
Measurement When BSC sends a “BLOCKING A CIRCUIT ACKNOWLEDGE” mes-
Unit Times

DL UNBLOCK A CIRCUIT
messages
Definition Number of DL UNBLOCK A CIRCUIT messages
Description This counter counts the number of “UNBLOCK A CIRCUIT” mes-
Measurement When BSC receives an “UNBLOCK A CIRCUIT” message, this
Unit Times
Definition Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages
Description This counter counts the number of “UNBLOCKING A CIRCUIT AC-
KNOWLEDGE” messages sent by BSC to iTC.
Measurement When BSC sends an “UNBLOCKING A CIRCUIT ACKNOWLEDGE”
Unit Times
BLOCK A CIRCUIT GROUP
messages
Definition Number of UL BLOCK A CIRCUIT GROUP messages
Description This counter counts the number of “BLOCK A CIRCUIT GROUP”
Measurement When BSC sends a “BLOCK A CIRCUIT GROUP” message, this
Unit 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 When BSC receives a “BLOCK A CIRCUIT GROUP” message, this
Unit Times
UL BLOCKING A CIRCUIT
GROUP ACKNOWLEDGE
messages
Definition Number of UL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE mes-
sages
Description This counter counts the number of “BLOCKING A CIRCUIT GROUP
Measurement When BSC sends a “BLOCKING A CIRCUIT GROUP ACKNOWL-
Unit Times
DL BLOCKING A CIRCUIT
GROUP ACKNOWLEDGE
messages
Definition Number of DL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE mes-
sages
Description This counter counts the number of “BLOCKING A CIRCUIT GROUP

Measurement When BSC receives a “BLOCKING A CIRCUIT GROUP ACKNOWL-

Unit 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 When BSC sends an “UNBLOCK A CIRCUIT GROUP” message, this
Unit Times
DL UNBLOCK A CIRCUIT
GROUP messages
Definition Number of DL UNBLOCK A CIRCUIT GROUP messages
Description This counter counts the number of “UNBLOCK A CIRCUIT GROUP”
Measurement When BSC receives an “UNBLOCK A CIRCUIT GROUP” message,
Unit 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 When BSC sends an “UNBLOCKING A CIRCUIT GROUP ACKNOWL-
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 When BSC receives an “UNBLOCKING A CIRCUIT GROUP AC-
Point KNOWLEDGE” message, this counter increments.
Unit Times
UNEQUIPPED A CIRCUIT
messages
Definition Number of UL UNEQUIPPED A CIRCUIT messages
Description This counter counts the number of “UNEQUIPPED A CIRCUIT” mes-

Measurement When BSC sends an “UNEQUIPPED A CIRCUIT” message, this

Unit Times
UNEQUIPPED A CIRCUIT
messages
Definition Number of DL UNEQUIPPED A CIRCUIT messages
Description This counter counts the number of “UNEQUIPPED A CIRCUIT” mes-
Measurement When BSC receives an “UNEQUIPPED A CIRCUIT” message, this
Unit Times
Ater RESET messages
Definition Number of UL Ater RESET messages
Description This counter counts the number of “RESET” messages sent by BSC
to iTC.
Measurement When BSC sends a “RESET” message, this counter increments.
Point
Unit Times
Ater RESET messages
Definition Number of DL Ater RESET messages
Description This counter counts the number of “RESET” messages received by
BSC from iTC.
Measurement When BSC receives a “RESET” message, this counter increments.
Point
Unit Times

C901390043 Number
of UL Ater RESET
Definition Number of UL Ater RESET ACKNOWLEDGE messages
Description This counter counts the number of “RESET ACKNOWLEDGE” mes-
Measurement When BSC sends a “RESET ACKNOWLEDGE” message, this counter
Point increments.
Unit Times
C901390044 Number
of DL Ater RESET
Definition Number of DL Ater RESET ACKNOWLEDGE messages
Description This counter counts the number of “RESET ACKNOWLEDGE” mes-
Measurement When BSC receives a “RESET ACKNOWLEDGE” message, this
Unit Times
UL Ater CONFUSION
messages
Definition Number of UL Ater CONFUSION messages
Description This counter counts the number of “CONFUSION” messages sent
by BSC to iTC.

Measurement When BSC sends a “CONFUSION” message, this counter incre-

Point ments.
Unit Times
DL Ater CONFUSION
messages
Definition Number of DL Ater CONFUSION messages
Description This counter counts the number of “CONFUSION” messages re-
ceived by BSC from iTC.
Measurement When BSC receives a “CONFUSION” message, this counter incre-
Point ments.
Unit Times
RESOURCE REQUEST
messages
Definition Number of RESOURCE REQUEST messages
Description This counter counts the number of “RESOURCE REQUEST” mes-
Measurement When BSC sends a “RESOURCE REQUEST” message, this counter
Point increments.
Unit Times
RESOURCE INDICATION
messages
Definition Number of RESOURCE INDICATION messages

Description This counter counts the number of “RESOURCE REQUEST AC-

Measurement 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 When BSC receives a “RESOURCE REQUEST NEGTIVE ACKNOWL-
Unit Times
resource release request
messages
Definition Number of resource release request messages
Description This counter counts the number of “RESOURCE RELEASE RE-
QUEST” messages sent by BSC to iTC.
Measurement When BSC sends a “RESOURCE RELEASE REQUEST” message, this
Unit Times

C901390051 Number
of resource release
acknowledge messages
Definition Number of resource release acknowledge messages
Description This counter counts the number of “RESOURCE RELEASE AC-
Measurement When BSC receives a “RESOURCE RELEASE ACKNOWLEDGE” mes-
Unit Times
resource failure messages
Definition Number of resource failure messages
Description This counter counts the number of “RESOURCE FAILURE” mes-
Measurement When BSC receives a “RESOURCE FAILURE” message, this counter
Point increments.
Unit Times
TFO status messages
Definition Number of TFO status messages
Description This counter counts the number of “TFO STATE” messages received
by BSC from iTC.
Measurement When BSC receives a “TFO STATE” message, this counter incre-
Point ments
Unit Times

TFO common voice type
messages
Definition Number of TFO common voice type messages
Description This counter counts the number of “TFO CONMMONTYPE” mes-
Measurement When BSC receives a “TFO CONMMONTYPE” message, this counter
Point increments.
Unit Times
TFO control messages
Definition Number of TFO control messages
Description This counter counts the number of “TFO CONTROL INFORMATION”
Measurement When BSC sends a “TFO CONTROL INFORMATION” message, this
Unit Times


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 Re-
ceived.......................................................................... 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 conges-
tion ............................................................................. 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.

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 When an MTP2 link receives a message code stream carrying
Point 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 incre-
ments.(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 When a message octet is shorter than 6 or longer than 127, this
Unit Times
C901400003 Number of Out

of Alignment
Definition Number of Out of Alignment
Description 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 When the flag is invalid or the length of the signal unit exceeds
Point 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 non-
octet 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 When an octet composed of non-8 bits occurs, this counter incre-
Point ments.
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 re-
ceived by an MTP2 link.
Measurement When a CRC error occurs, this counter increments.
Point
Unit Times

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 When errors other than the above four types occur, this counter
Point 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 ac-
knowledgements received by an MTP2 link.
Measurement When an MTP2 link receives a negative acknowledgement, this
Unit Times
C901400008 Octets of MSU

Retransmitted
Definition Octets of MSU Retransmitted
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 When an MTP2 link is retransmitted, this counter increments by
Point the corresponding octet.
Unit 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 When an MTP2 link is resent, this counter increments by the cor-
Point responding 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 When an MTP2 link receives AlignNtpsbl during alignment, this
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 When an MTP2 link receives an error SU, this counter increments.
Point
Unit Times

MSU discarded due to
congestion
Definition Number of MSU discarded due to congestion
Description This counter counts the number of MSUs discarded due to conges-
tion 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 When an MTP2 link discards MSU due to congestion, this counter
Point 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 When an MTP2 link is broken due to abnormal FIBBSN, this counter
Point increments.
Unit Times
SL failure due to Excessive
delay of ack
Definition 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.
to excessive delay of acknowledgement.

Measurement When an MTP2 link is broken due to excessive delay of acknowl-

Point edgement, this counter increments.
Unit Times
error rate
Definition Number of SL failure due to Excessive error rate
error rate.
to excessive error rate.
Measurement When an MTP2 link is broken due to excessive error rate, this
Unit Times
duration of congestion
Definition Number of SL failure due to Excessive duration of congestion
duration of congestion.
to excessive duration of congestion.
Measurement When an MTP2 link is broken due to congestion, this counter in-
Point crements.
Unit Times


Chapter 47
CPU MEM Measurement
Table of Contents
Overview...................................................................... 2277
C901410001 Peak memory usage of the main proces-
sor .............................................................................. 2277
C901410002 Mean value of the memory usage.................. 2278
C901410003 Peak load of CPU usage of the main proces-
sor .............................................................................. 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 oc-
curred.......................................................................... 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 main-
tenance, 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 In the sampling period, sample a memory usage every 2 seconds.
Point

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 In the sampling period, sample a memory usage every 2 seconds.
Point
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 In the sampling period, sample a CPU usage every 2 seconds and
Point use the peak value as the maximum value of the measurement
point.
Unit Percent
C901410004 Mean ratio of

the CPU usage
Definition Mean ratio of the CPU usage

Chapter 47 CPU MEM Measurement
Description This counter samples CPU usage at an interval of 2 seconds, aver-

ages 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 In the sampling period, sample a CPU usage every 2 seconds. Di-
Point vide the sum of the values of all measurement points by the num-
ber 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 con-
ditions.
Measurement In the sampling period, count and record the maximum values of
Point 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 In the sampling period, trace the time when the load of main pro-
Point cessor reaches peak. At the end of collection period, output the
traced time point.
Unit Second

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 In the sampling period, do sampling at an interval of 2 seconds
Point and get the maximum kilo-bytes of the rest UB.
Unit Byte
C901410008 Mean
kilo-bytes of the rest UB
Definition Mean kilo-bytes of the rest UB
Description 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.
Usage This counter is used to find out the condition of the rest UB.
Measurement At the end of a collection period, average the bytes of the rest UB
Point sampled every 2 seconds.
Unit 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 retransmis-
sion ............................................................................. 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 pack-
ets .............................................................................. 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 transmis-
sion ............................................................................. 2289
C901420023 Maximum dithering of network transmis-
sion ............................................................................. 2290
C901420024 Minimum dithering of network transmis-
sion ............................................................................. 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 trans-
mission ........................................................................ 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 retransmis-
sion ............................................................................. 2293

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 When SCTP drops packets, this counter will count.
Point
Unit Times
received SCTP packets
Definition Number of received SCTP packets
Description This counter counts the number of IP packets received by the SCTP,
including heartbeat and SHUTDOWN. When SCTP receives pack-
ets, this counter increments.
Usage This counter is used to find out the number of packets received by
SCTP.
Measurement When SCTP receives packets, this counter will count.
Point
Unit 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 When SCTP receives DATA packets, this counter will count.
Point
Unit 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 When SCTP sends packets, this counter will count.
Point
Unit 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 When SCTP sends DATA packets, this counter will count.
Point
Unit Times

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 When SCTP sends messages to ULP, this counter will count.
Point
Unit 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 accumu-
lates.
Usage This counter is used to find out the number of message bytes sent
by SCTP to ULP.
Measurement When SCTP sends messages to ULP, this counter will count.
Point
Unit Times
messages received from ulp
Definition Number 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 messages received
by SCTP from ULP.
Measurement When SCTP receives ULP messages, this counter will count.
Point
Unit 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 re-
ceived by SCTP from ULP.
Measurement When SCTP receives ULP messages, this counter will count.
Point
Unit 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 When congestion control module zooms out congestion windows,
Point this counter will count.
Unit Times
congestion
Definition Duration of congestion
Description This counter counts the congestion duration.
Usage This counter is used to find out the duration of SCTP congestion.
Measurement SCTP congestion control.
Point

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 trans-
mitted by SCTP.
Measurement When SCTP fast transmits chunks, this counter will count.
Point
Unit 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 trans-
mitted by SCTP.
Measurement When SCTP retransmits chunks due to timeout, this counter will
Point count.
Unit Times
C901420014 RTT is lower

than T1
Definition 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 When the sampled RTT is lower than T1, this counter will counts.
Point

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 When the sampled RTT is between T1 and T2, this counter will
Point 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 When the sampled RTT is higher than T2, this counter will count.
Point
Unit None
C901420017 Number
of network transmission
dropped packets
Definition Number of network transmission dropped packets
Description 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 re-
transmission.

Usage This counter is used to find out the statistics of packets dropped
during network transmission.
Measurement If SCTP receives no response after sending packets, this counter
Point will count during retransmission.
Unit Times
Related Features 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 When RTT is calculated based on RTO sampling, determine the
Point maximum delay of network transmission.
Unit ms
C901420019 Minimum delay

of network transmission
Definition Minimum delay of network transmission
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.
Point minimum delay of network transmission.
Unit 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 trans-
mission for processing SCTP packets.
Measurement When RTT is calculated based on RTO sampling, delay of network
Point transmission is accumulated.
Unit 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 trans-
Usage This counter is used to find out the total delay of network trans-
Measurement When RTT is calculated based on RTO sampling, delay of network
Point transmission is accumulated.
Unit ms
delay samples of network
transmission
Definition Number of delay samples of network transmission

Description This counter counts the number of delay samples of network trans-
mission. 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 When a delay sampling is done in measurement interval, this
Point counter will count.
Unit Times
C901420023 Maximum
dithering of network
transmission
Definition Maximum dithering of network transmission
Description This counter counts the maximum dithering of network transmis-
sion of SCTP packets in an interval. When the actual network
transmission dithering is greater than maximum dithering of net-
work transmission, the actual one prevails.
Usage This counter is used to find out the maximum dithering of network
transmission.
Point maximum dithering of network transmission.
Unit ms
C901420024 Minimum
dithering of network
transmission
Definition Minimum dithering of network transmission
Description This counter counts the minimum dithering of network transmis-
sion of SCTP packets in an interval. When the actual network
transmission dithering is smaller than maximum dithering of net-
work transmission, it replaces the minimum dithering of network
transmission.
Usage This counter is used to find out the minimum dithering of network
transmission.


Point minimum dithering of network transmission.
Unit 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 trans-
Measurement When RTT is calculated based on RTO sampling, dithering of net-
Point work transmission is accumulated.
Unit 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 trans-
Measurement When RTT is calculated based on RTO sampling, dithering of net-
Point work transmission is accumulated.
Unit ms

dithering samples of network
transmission
Definition Number of dithering samples of network transmission
Description This counter counts the number of delay samples of network trans-
mission. 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 When a dithering sampling is done in measurement interval, this
Point counter will count.
Unit 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 The counter counts when the data block marked as lost by SCTP
Point (due to retransmission timer being timeout or determined by rapid
retransmission algorithm) is sent.
Unit Number of data blocks
C901420029 Chunks Trans

On Send Dirction
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 The counter counts when the data block is sent. Here, the data
Point block is the one sent for the first time.
Unit Number of data blocks
abort from peer
Description This counter counts the number of link breaks due to abort initiated
from the peer end.
Usage This counter is supported in version V6.20.61 or later.
Measurement When the abort message is received from the peer end, the
Unit Times
C901420031 Number
of association break by
retransmission
Description This counter counts the number of link breaks due to retransmis-
sion.
Measurement When the link breaks due to retransmission, the counter incre-
Point ments.
Unit Times


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 num-
ber of messages received, transmitted, and discarded at the ex-
ternal 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 re-
ceived/transmitted messages per second (PPS) at the port by con-
trolling 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.

Measurement The counter accumulates when there is message received at IP

Point port.
Unit 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 The counter accumulates when there is message sent at IP port.
Point
Unit 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 re-
ceiving 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 The counter accumulates when there is incorrect message dis-
Point carded at the receiving end of IP port.
Unit Times
C901430004 Packets
number discarded at tx end
Definition Packets number discarded at tx end
Description This counter counts the number of messages discarded at the
transmitting end of IP port. The counter increments when an in-
correct 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 The counter accumulates when there is incorrect message dis-
Point carded at the transmitting end of IP port.
Unit Times


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 sam-
pling ............................................................................ 2300
Overview
GTRUNK refers to the timeslot resource on UPU DSP. GTRUNK re-
source 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 times-
lot resource being occupied within the measurement period.
Usage This counter is used to find out the occupation of UPU DSP times-
lot resource by PS service, which helps optimize the UPU DSP re-
source.
Measurement The counter counts when PS user requests for the UPU DSP times-
Point lot resource successfully.
Unit Times

the used sampling according
to DSP TS
Description This counter counts the number of available UPU DSP timeslot re-
source 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.
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.
Unit Times
C901440004 Number
sampling
Definition 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.
Unit Times


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 receiv-
ing flush LL................................................................... 2308
C901450006 Number of UL packet channel frame adjust-
ment ........................................................................... 2309
C901450007 Number of DL packet channel frame adjust-
ment ........................................................................... 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


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 pe-
riod in Gb ..................................................................... 2330
C901450041 The min length of downlink packet latency pe-
riod in Gb ..................................................................... 2330
C901450042 The average length of downlink packet latency
period in Gb.................................................................. 2331
C901450043 The length of downlink packet latency period be-
tween 0 and 100 ms (100 included) in Gb......................... 2331
tween 100 ms and 200 ms (200 included) in Gb ................ 2332
tween 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 pe-
riod 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 Band-
Width .......................................................................... 2339
Overview
Other process measurements contain the measurement on adjust-
ments of frame number and NACC processes.

Chapter 51 Other Process Statistics
C901450001 Max time of

NACC cell reselection
Description Do NACC after receiving the Packet Cell Change Notification mes-
sage 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.
Usage It is used to measure the max duration of NACC.
Measurement The NACC duration is a sampling period, starting with BSS receiv-
Point ing 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
MS.
Usage It is used to measure the minimum duration of NACC.


Point
Minimum time of this NACC is the minimum of all NACC periods in

a sampling period.
C901450003 Total time of

MS.
Usage It is used to measure the total time of all successful NACCs in this
cell.
Point

Total time of this NACC is the sum of all NACC periods in a sampling
period.
(PCCN to flush LL)
MS.
Usage It is used to measure the number of NACC success.
Point

FIGURE 2337 MEASUREMENT POINT OF NUMBER OF NACC SUCCESS
without receiving flush LL
sage sent by MS at network side. The MS decides whether to do
cell reselection after the MS gets the system message about ad-
jacent cell at network side.
Usage It is used to measure the number of NACC without receiving flush
LL.
Point

FIGURE 2338 MEASUREMENT 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 ad-
justment.
Measurement Do the measurement while the uplink frame number carried in
Point 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

adjustment degree of downlink frame number through PCU frame.

Adjust the downlink frame number on the channel if the adjust-
ment value is not 0.
Usage It is used to measure the number of DL packet channel frame ad-
justment.
Measurement Do the measurement while the adjustment value of downlink frame
Point number carried in uplink PCU frame is not 0 and not located in the
protection period.
C901450008 Sum of C
Description This counter counts the C value in channel quality report while
DRLC receives GPRS PACKET DOWNLINK ACK or EGPRS PACKET
DOWNLINK ACK.
Usage This counter measures the C value about the channel quality.
Measurement For GPRS or EGPRS, this counter increments while receiving
Point PACKET DOWNLINK ACK. The measurement point is A, as shown
in Figure 2339.
FIGURE 2339 MEASUREMENT POINT FOR THE SUM OF C
Unit None
C901450009 Sum of RxQual

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 This counter increments while GPRS receives PACKET DOWNLINK
Point 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 chan-
nel quality.
Measurement This counter increments when EGPRS receives PACKET DOWNLINK
Point 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.

Unit None
C901450011 Sum of
GMSK-CV-BEP
Description This counter counts the GMSK-CV-BEP value in channel quality re-
port while DRLC receives EGPRS PACKET DOWNLINK ACK.
Usage This counter measures the GMSK-CV-BEP value about the channel
quality.
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 chan-
nel quality.
Point ACK and the 8PSK_MEAN_BEP indication bit is 1 in the channel
2343.

Unit None
C901450013 Sum of
8PSK-CV-BEP
Description This counter counts the 8PSK-CV-BEP value in channel quality re-
port while DRLC receives EGPRS PACKET DOWNLINK ACK.
Usage This counter measures the 8PSK-CV-BEP value about the channel
quality.
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 For GPRS or EGPRS, this counter increments while receiving
Point PACKET DOWNLINK ACK. The measurement point is A, as shown
in Figure 2345.

Unit Times
sampling of RxQual
Description This counter counts the number of RxQual sampling points in chan-
nel quality report while DRLC receives GPRS PACKET DOWNLINK
ACK.
Usage This counter measures the number of RxQual sampling points
about the channel quality.
Measurement This counter increments while GPRS receives PACKET DOWNLINK
Point 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.
2347.

Unit None
sampling of GMSK-CV-BEP
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
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
2349.

Unit None
sampling of 8PSK-CV-BEP
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
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 assign-
ment message shall be recorded under the acknowledgement
mode.
Usage This counter measures the number of uplink TBFs under the ac-
knowledgement mode.
Measurement This counter measures the number of TBFs when URLC receives
Point the uplink assginment or DTM assignment and the resource as-
signment message shall be recorded under the acknowledgement
mode. The measurement point is A, as shown in Figure 2351.
FIGURE 2351 MEASUREMENT POINT OF NUMBER OF RLC UPLINK ACK TBF
Unit Times

RLC uplink NACK TBF
Description This counter counts the number of TBFs while URLC receives the
uplink assginment or DTM assignment and the resource assign-
ment message shall be recorded under the unacknowledgement
mode.
Usage This counter measures the number of uplink TBFs under the un-
acknowledgement mode.
Measurement This counter measures the number of TBFs when URLC receives the
Point uplink assginment or DTM assignment and the resource assign-
ment message shall be recorded under the unacknowledgement
mode. The measurement point is A, as shown in Figure 2352.
FIGURE 2352 MEASUREMENT POINT OF NUMBER OF RLC UPLINK ACK TBF
Unit Times
DL-UNITDATA messages
with Service UTRAN CCO
received by BSC

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 Cell
Description This counter counts the maximum delay of the cell's PS service
at Abis interface within the measurement period. When the up-
link 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.

Unit ms
C901450027 The min length

of packet latency period in
Abis
Description This counter counts the minimum delay of the cell's PS service
at Abis interface within the measurement period. When the up-
link 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.
Unit ms
C901450028 The average

length of packet latency
period in Abis
Description 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 up-
link 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
Description 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 lat-
est delay.
Unit ms
C901450030 The length

of packet latency period
between 0 and 20 ms (20
included) in Abis
Description 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.
Unit Times


between 20 ms and 40 ms
(40 included) in Abis
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 num-
ber and downlink frame number of PS service at BSC are synchro-
nized, 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.
Unit Times

counter increments.
Unit Times


counter increments.
Unit Times

counter increments.
Unit Times


Description 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,
Unit Times

Unit Times


Unit Times

Unit Times

C901450039 The length of

packet latency period larger
than 180 ms in Abis
the cell's PS service at Abis interface is in the range of (180 ms,
+∞] within the measurement period. When the uplink frame num-
counter increments.
Unit Times
C901450040 The max length

of downlink packet latency
period in Gb
Description 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 down-
link received time from the downlink sent time to get the downlink
delay at Gb interface. After comparison, the counter records the
maximum delay.
Unit ms

period in Gb
Description 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
Description 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 aver-
age delay.
Unit ms

period between 0 and 100
ms (100 included) in Gb
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.
Unit Times


period between 100 ms and
200 ms (200 included) in Gb
the cell's PS service in downlink transmission at Gb interface is in
the range of (100 ms, 200 ms] within the measurement period.
Unit Times

Unit Times


Unit Times

Unit Times


1000 ms (1000 included) in
Gb
Unit Times

period larger than 1000 ms
in Gb
the cell's PS service in downlink transmission at Gb interface is
in the range of (1000 ms, +∞) within the measurement period.
Unit Times

C901450050 The max

length of uplink packet
Description This counter counts the maximum delay of the cell's PS service in
uplink transmission at Gb interface within the measurement pe-
riod. 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 inter-
face. After comparison, the counter records the maximum delay.
Unit ms

of uplink packet latency
period in Gb
Description This counter counts the minimum delay of the cell's PS service in
uplink transmission at Gb interface within the measurement pe-
riod. 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 inter-
face. After comparison, the counter records the minimum delay.
Unit ms

length of uplink packet
Description This counter counts the average delay of the cell's PS service in up-
link 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. 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 1. When BSC receives the Channel Request message from MS, if
Point 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 When BSC receives the downlink data from SGSN, if BSC fails to
Point create the BSSGP instance, then the counter counts.
Unit 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 up-
link 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 push-
ing 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 The counter counts when BSC user plane receives the message of
Point pushing down uplink bandwidth. The measurement point is A, as
FIGURE 2353 FLOW OF PUSHING DOWN UPLINK BANDWIDTH
Unit Times
Pushing Down Downlink
BandWidth
Description This counter counts the number of pushing down downlink band-
width in the cell. When BSC control plane judges that the actual
downlink bandwidth exceeds C1, which is the safe allocation up-
per limit about bandwidth at the resource pool, if the current the-
oretically 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.

When BSC user plane receives the message, the counter incre-
ments.
Usage The counter is used to find out the frequency of pushing down
downlink bandwidth in the cell.
Point pushing down downlink bandwidth. The measurement point is A,
FIGURE 2354 FLOW OF PUSHING DOWN DOWNLINK BANDWIDTH
Unit 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 The counter counts when BSC user plane receives the message
Point of pushing up uplink bandwidth. The measurement point is A, as

FIGURE 2355 FLOW OF PUSHING UP UPLINK BANDWIDTH
Unit 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 down-
link bandwidth in the cell.
Point pushing up downlink bandwidth. The measurement point is A, as
FIGURE 2356 FLOW OF PUSHING UP DOWNLINK BANDWIDTH
Unit Times


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 in-
formation at FR sublayer of NS layer at Gb interface in GPRS ser-
vice, 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 sta-
tus 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 When BSC sends the "Status Enquiry" message, this counter in-

FIGURE 2357 STATUS QUERY PROCESS
Status ACK Message
received
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 When BSC receives the "Status" message, this counter incre-

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 During the process of querying BRCH's status, this counter incre-
Point ments when error occurs at N392 every N393. The measurement

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 FR accumulates the number of bytes received on BRCH from Gb
Point interface.
bytes sent on BRCH
Description This counter counts the number of bytes sent on BRCH of FR sub-
layer.
contains FR header.
Usage Check the number of bytes sent on BRCH to observe the load of
BRCH.
Measurement FR accumulates the number of bytes sent on BRCH from Gb inter-
Point face.

Chapter 53
OMP PS Service
Statistics
Table of Contents
Overview...................................................................... 2345
ceived.......................................................................... 2346
ceived.......................................................................... 2346
ceived.......................................................................... 2347
ceived.......................................................................... 2347
Overview
Counters of OMP-PS service statistics counts messages related to
PS service on OMP, including messages of suspension and resum-
ing. These counters are used to observe the frequency of MS's
requesting for terminating GPRS service and resuming GPRS ser-
vice.
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 The counter counts when the GB_SUSPEND message is sent.
Point
Unit Times

SUSPEND-ACK message
received
Description This counter counts the number of SUSPEND-ACK messages re-
ceived by site or cell from an SGSN within the measurement pe-
riod.
Usage This counter counts the number of SUSPEND-ACK messages re-
riod.
Measurement The counter counts when the GB_SUSPEND_ACK message is re-
Point ceived from SGSN.
Unit Times
received
Description This counter counts the number of SUSPEND-NACK messages re-
riod.
Usage This counter counts the number of SUSPEND-NACK messages re-
riod.
Measurement The counter counts when the GB_SUSPEND_NACK message is re-
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 The counter counts when the GB_RESUME message is sent.
Point
Unit Times

Chapter 53 OMP PS Service Statistics
RESUME-ACK message
received
Description This counter counts the number of RESUME-ACK messages re-
riod.
Usage This counter counts the number of RESUME-ACK messages re-
riod.
Measurement The counter counts when the GB_RESUME_ACK message is re-
Unit Times
RESUME-NACK message
received
Description This counter counts the number of RESUME-NACK messages re-
riod.
Usage This counter counts the number of RESUME-NACK messages re-
riod.
Measurement The counter counts when the GB_RESUME_NACK message is re-
Unit Times


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 ac-
knowledgements ........................................................... 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 re-
ceived successful acknowledgements ............................... 2352
C901480007 Number of SNS-CONFIG initiated by BSC re-
ceived failed acknowledgements ...................................... 2352
C901480008 Number of SNS-CONFIG initiated by BSC with-
out response................................................................. 2353
C901480009 Number of SNS-CONFIG initiated by SGSN re-
C901480010 Number of SNS-CONFIG initiated by SGSN re-
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 re-
C901480019 Number of SNS-DELETE initiated by BSC re-
C901480020 Number of SNS-DELETE initiated by BSC without
response ...................................................................... 2359
C901480021 Number of SNS-DELETE initiated by SGSN re-
C901480022 Number of SNS-DELETE initiated by SGSN re-
BSC ............................................................................. 2360
BSC received successful acknowledgements ...................... 2361
BSC received failed acknowledgements ............................ 2361


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 config-
ured 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 The counter counts in the following two cases:
Point
1. The configuration at background is modified, and the database
triggers the counting.
2. The SNS process timer expires, triggering the counting.
Unit Times
SNS-SIZE received success
ful acknowledgements
Description This counter counts the number of acknowledged responses from
NSE after NSE receives the SNS-SIZE message within the mea-
surement period.
Usage This counter counts the number of acknowledged responses from
NSE after NSE receives SNS-SIZE within the measurement period.

Chapter 54 SNS on OMP Statistics
Measurement The counter counts when the EV_NSCTRL_SIZE_ACK message

Point from SGSN is received.
Unit 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 This counter counts the number of unacknowledged responses
from NSE after NSE receives SNS-SIZE within the measurement
period.
Measurement After the SNS-SIZE message is received, this counter counts when
Point NSE sends response message with the cause of unavailable NSVC
or unavailable IPV4.
Unit Times
SNS-SIZE initiated by BSC
without response
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

Measurement The counter counts after NSE sends the SNS-CONFIG message.
Point
Unit Times
BSC received successful
acknowledgements
Description This counter counts the number of acknowledged responses from
NSE after NSE receives the SNS-CONFIG message within the mea-
surement period.
Usage This counter counts the number of acknowledged responses from
NSE after NSE receives the SNS-CONFIG message successfully
Measurement The counter counts when NSE returns the acknowledged response
Point after receiving the SNS-CONFIG message.
Unit Times
SNS-CONFIG initiated
by BSC received failed
acknowledgements
Description This counter counts the number of unacknowledged responses
from NSE after NSE receives the SNS-CONFIG message within
Usage This counter counts the number of unacknowledged responses
from NSE after NSE receives the SNS-CONFIG message within
Measurement The counter counts when NSE returns the unacknowledged re-
Point sponse after receiving the SNS-CONFIG message.
Unit Times

BSC without response
Description This counter counts the number of SNS-CONFIG messages initi-
ated by BSC but without any response within the measurement
period.
Usage This counter counts the number of SNS-CONFIG messages initi-
ated by BSC but without any response within the measurement
period.
Measurement The counter counts when it is timeout during the process of waiting
Point for NSE's response for the SNS-CONFIG message.
Unit 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 This counter counts the number of acknowledged responses of
SNS-CONFIG messages initiated by SGSN within the measurement
period.
Measurement The counter counts when the EV_NSCTRL_CONFIG_IND message
Point is received which indicates that the IP endpoint at SGSN is
recorded successfully.
Unit Times

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 The counter counts when the EV_NSCTRL_CONFIG_IND message
Point is received which indicates that the IP endpoint at SGSN fails to
be recorded.
Unit Times
SNS-ADD initiated by BSC
Description This counter counts the number of SNS-ADD messages initiated
by BSC within the measurement period.
Usage This counter counts the number of SNS-ADD messages initiated
Measurement The counter counts when BSC sends the EV_NSOAM_ADD_REQ
Point message.
Unit 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 pe-
riod.
Usage This counter counts the number of acknowledged responses of the
SNS-ADD message initiated by BSC within the measurement pe-
riod.
Measurement When BSC receives the EV_NSCTRL_SNSACK_IND message with
Point acknowledgement, the counter increments.
Unit 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 This counter counts the number of unacknowledged responses of
the SNS-ADD message initiated by BSC within the measurement
period.
Point unacknowledgement, the counter increments.
Unit Times

SNS-ADD initiated by BSC
without response
Description This counter counts the number of SNS-ADD messages initiated
by BSC but without any response within the measurement period.
Usage This counter counts the number of SNS-ADD messages initiated
Measurement The counter counts when it is timeout during the process of BSC's
Point waiting for the response for the SNS-ADD message.
Unit Times
acknowledgements
SNS-ADD messages initiated by SGSN within the measurement
period.
period.
Measurement The counter counts when the EV_NSCTRL_ADD_IND message is
Point received which indicates that the IP endpoint at SGSN is recorded
successfully.
Unit Times

SGSN received failed
acknowledgements
period.
period.
Measurement The counter counts when the EV_NSCTRL_ADD_IND message is
Point received which indicates that the IP endpoint at SGSN fails to be
recorded.
Unit Times
SNS-DELETE initiated by
BSC
Description This counter counts the number of SNS-DELETE messages initiated
Usage This counter counts the number of SNS-DELETE messages initiated
Measurement The counter counts when the EV_NSOAM_DELETE_REQ message
Point is sent.
Unit Times

acknowledgements
SNS-DELETE message initiated by BSC within the measurement
period.
SNS-DELETE message initiated by BSC within the measurement
period.
Measurement The counter counts when BSC receives the SNS-ACK message with
Point acknowledgement.
Unit Times
SNS-DELETE initiated
acknowledgements
the SNS-DELETE message initiated by BSC within the measure-
ment period.
the SNS-DELETE message initiated by BSC within the measure-
ment period.
Measurement The counter counts when BSC receives the SNS-ACK message with
Point unacknowledgement.
Unit Times

BSC without response
Description This counter counts the number of SNS-DELETE messages initiated
Usage This counter counts the number of SNS-DELETE messages initiated
Point waiting for the response of SNS-DELETE message.
Unit Times
acknowledgements
SNS-DELETE messages initiated by SGSN within the measurement
period.
period.
Measurement The counter counts when the EV_NSCTRL_DELETE_IND message
Point is received which indicates that the IP endpoint at SGSN is
recorded successfully.
Unit Times

SNS-DELETE initiated
by SGSN received failed
acknowledgements
period.
period.
Measurement The counter counts when the EV_NSCTRL_DELETE_IND message
Point is received which indicates that the IP endpoint at SGSN fails to
be recorded.
Unit Times
SNS-CHANGEWEIGHT
initiated by BSC
Description This counter counts the number of SNS-CHANGEWEIGHT mes-
sages initiated by BSC within the measurement period.
Usage This counter counts the number of SNS-CHANGEWEIGHT mes-
sages initiated by BSC within the measurement period.
Measurement The counter counts when BSC receives the EV_NSOAM_CHANGE-
Point WEIGHT_REQ message.
Unit Times

SNS-CHANGEWEIGHT
initiated by BSC
received successful
acknowledgements
SNS-CHANGEWEIGHT message initiated by BSC within the mea-
surement period.
SNS-CHANGEWEIGHT message initiated by BSC within the mea-
surement period.
Point acknowledgement, the counter increments.
Unit Times
SNS-CHANGEWEIGHT
initiated by BSC received
failed acknowledgements
the SNS-CHANGEWEIGHT message initiated by BSC within the
measurement period.
the SNS-CHANGEWEIGHT message initiated by BSC within the
measurement period.
Point unacknowledgement, the counter increments.
Unit Times

SNS-CHANGEWEIGHT
initiated by BSC without
response
Description This counter counts the number of SNS-CHANGEWEIGHT mes-
sages initiated by BSC but without any response within the mea-
surement period.
Usage This counter counts the number of SNS-CHANGEWEIGHT mes-
sages initiated by BSC but without any response within the mea-
surement period.
Point waiting for the response for the SNS-CHANGEWEIGHT message.
Unit Times
SNS-CHANGEWEIGHT
initiated by SGSN
received successful
acknowledgements
SNS-CHANGEWEIGHT message initiated by SGSN within the mea-
surement period.
SNS-CHANGEWEIGHT message initiated by SGSN within the mea-
surement period.
Measurement The counter counts when the EV_NSCTRL_CHANGEWEIGHT_IND
Point message is received which indicates that the IP endpoint at SGSN
is recorded successfully.
Unit Times

SNS-CHANGEWEIGHT
initiated by SGSN received
failed acknowledgements
the SNS-CHANGEWEIGHT message initiated by SGSN within the
measurement period.
the SNS-CHANGEWEIGHT message initiated by SGSN within the
measurement period.
Measurement The counter counts when the EV_NSCTRL_CHANGEWEIGHT_IND
Point message is received which indicates that the IP endpoint at SGSN
fails to be recorded.
Unit Times


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 interac-
tion and data transmission at NS layer of Gb interface in GPRS
service.
bytes received from SGSN
bytes sent to SGSN
Description This counter counts the number of bytes sent to SGSN from NS
sub layer.


Measurement IP accumulates the number of bytes sent each time. The mea-
Point surement point is A1, as shown in Figure 2360.
FIGURE 2360 UPLINK NS DATA
Unit Byte
PDU data sent by NS sub
layer
PDU data received by NS
sub layer

Chapter 55 IPGB StrongARM NSVC Statistics
PDU data discarded by NS
sub layer


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

UNITDATA messages

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 suc-
cess. 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 han-
dover process.
Usage The counter's value is calculated by dividing the total queue length
by the number of queues.
Measurement When the measurement period expires, divide the total queue
Point length by the number of queues to calculate the counter's value.
The measurement point is shown in Figure 2361.

FIGURE 2361 MEASUREMENT POINT OF AVERAGE LENGTH OF QUEUE
Unit Times
queuing
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 sub-
tracting 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 This counter counts the total queuing time of a user in the
Point 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.
FIGURE 2362 MEASUREMENT POINT OF QUEUING DURATION WHEN

QUEUING FAILS

QUEUING SUCCEEDS
Unit Times

queuing
Description This counter counts the number of users entering the queue dur-
ing 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 This counter counts the number of queuing users in a cell. The
Point counter increments every time a user exits the queue. The mea-
surement point is B2, as shown in Figure 2364 and Figure 2365.

QUEUING FAILS


QUEUING SUCCEEDS
Unit 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 This counter counts the total queuing time of a user in the cell
Point 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


QUEUING SUCCEEDS
Unit Second
queuing success
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 ac-
quiring resource after queuing in a cell.
Measurement This counter counts the number of users acquiring resource after
Point 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 Times


Chapter 58
HO Synchronization
Mode Measurement
Table of Contents
Overview...................................................................... 2379
C901520001 Number of synchronous handover execu-
tions ............................................................................ 2380
C901520002 Number of synchronous handover suc-
cesses.......................................................................... 2381
C901520003 Number of pre-synchronous handover execu-
tions ............................................................................ 2381
C901520004 Number of pre-synchronous handover suc-
cesses.......................................................................... 2381
C901520005 Number of pseudo-synchronous handover exe-
cutions......................................................................... 2382
C901520006 Number of pseudo-synchronous handover suc-
cesses.......................................................................... 2382
C901520007 Number of asynchronous handover execu-
tions ............................................................................ 2383
C901520008 Number of asynchronous handover suc-
cesses.......................................................................... 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 han-
dover executions. If the uplink handover (assignment) is com-
pleted, 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.

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 execu-
tions after the uplink channel activation completion message is
received.
Usage This counter is used to find out the number of synchronous han-
dover executions in the cell.
Measurement After BSC receives the channel activation completion message
Point from BTS, if the handover is synchronous handover, the counter
increments.
Unit Times

Chapter 58 HO Synchronization Mode Measurement
synchronous handover
successes
Description This counter counts the number of successful synchronous han-
dovers after the uplink handover(assignment) completion mes-
sage is received.
Usage This counter is used to find out the number of successful syn-
chronous handovers in the cell.
Measurement After BSC receives the uplink handover (assignment) completion
Point 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 ex-
ecutions 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.
Point from BTS, if the handover is pre-synchronous handover, the
counter increments.
Unit Times
pre-synchronous handover
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-syn-


Point message from BTS, if the handover is pre-synchronous handover,
Unit 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.
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 pseudo-
synchronous handovers in the cell.
Point message from BTS, if the handover is pseudo-synchronous han-
Unit Times

Chapter 58 HO Synchronization Mode Measurement
asynchronous handover
executions
Description This counter counts the number of asynchronous handover exe-
cutions after the uplink channel activation completion message is
received.
Usage This counter is used to find out the number of asynchronous han-
dover executions in the cell.
Point from BTS, if the handover is asynchronous handover, the counter
increments.
Unit Times
asynchronous handover
successes
Description This counter counts the number of successful asynchronous han-
dovers after the uplink handover(assignment) completion mes-
sage is received.
Usage This counter is used to find out the number of successful asyn-
Point message from BTS, if the handover is asynchronous handover, the
counter increments.
Unit Times


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 in-
terface ......................................................................... 2387
C901530003 Number of paging messages from CS of Gb in-
terface ......................................................................... 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. Measure-
ment points of paging message measurement counters are A, as
FIGURE 2370 MEASUREMENT POINT OF BSC RECEIVING PAGING MESSAGE

FROM A-INTERFACE

FIGURE 2371 MEASUREMENT POINT OF BSC RECEIVING PS/CS PAGING

MESSAGE FROM GB INTERFACE
Statistic unit in this measurement is BSC.
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 When BSC receives the paging message from A-interface, the
Figure 2372.
FIGURE 2372 MEASUREMENT POINT OF BSC RECEIVING PAGING MESSAGE

FROM A-INTERFACE
Unit 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 When BSC receives the PS paging message from Gb interface, the
Figure 2373.
Unit 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.


Measurement When BSC receives the CS paging message from Gb interface, the
Figure 2374.
Unit 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 occu-
pation condition of reserved channels in the cell. If the channel
resource request to the database succeeds and the acquired re-
source 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
source is reserved channel, the counter counts.

Usage This counter is used to find out the occupation condition of re-
served channels.
Measurement During the channel assignment process, when the voice channel
Point resource request to the database succeeds and the acquired re-
source 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
served channels.
Measurement 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
served channels.
Measurement During the channel handover process, when the voice channel
Unit 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 re-
source request to the database succeeds and the acquired re-
served channels.
Measurement During the channel handover process, when the data channel re-
Point source request to the database succeeds and the acquired re-
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.
served channels in the cell.
Measurement BSC performs statistics every 15 minutes.
Point
Unit Second


Chapter 61
SCCP Connection
Measurement
Table of Contents
Overview...................................................................... 2393
C901550001 Number of BSC originated SCCP Connection at-
tempts ......................................................................... 2394
C901550002 Number of BSC originated SCCP Connection suc-
cess............................................................................. 2395
C901550003 Number of BSC originated SCCP Connection fail-
ure due to timeout......................................................... 2396
C901550004 Number of negative replies for SCCP connection
request ........................................................................ 2396
C901550005 Number of MSC originated SCCP Connection Re-
quests ......................................................................... 2397
success ........................................................................ 2398
Overview
Counters of SCCP connection measurement count the following
information: the number of SCCP link establishment requests ini-
tiated 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 num-
ber 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.

BSC originated SCCP
Connection attempts
Description This counter counts the number of SCCP link establishment re-
quests 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 When BSC sends the Connect Req message to MSC, the counter
FIGURE 2375 MEASUREMENT POINT OF NUMBER OF BSC ORIGINATED

SCCP CONNECTION ATTEMPTS
Unit Times

Chapter 61 SCCP Connection Measurement
BSC originated SCCP
Connection success
Description This counter counts the number of successful SCCP link establish-
ments 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 When BSC receives the SCCP connection confirmation message
Point from MSC, the counter increments. The measurement point is A,
FIGURE 2376 MEASUREMENT POINT OF NUMBER OF BSC ORIGINATED

SCCP CONNECTION ATTEMPTS
Unit Times

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 establish-
ment failures due to timeout, and the SCCP link establishment is
initiated by BSC towards MSC.
Measurement When the timer T9105 expires, the counter increments.
Point
Unit Times
negative replies for SCCP
connection request
quests being rejected, and the SCCP link establishment is initiated
by BSC towards MSC.
ment requests being rejected, and the SCCP link establishment is
initiated by BSC towards MSC.
Measurement When the Rana process receives the DISCONNECT IND message
Point from the ADispatch process, the counter increments. The mea-

FIGURE 2377 MEASUREMENT POINT OF NUMBER OF NEGATIVE REPLIES FOR

SCCP CONNECTION REQUEST
Unit Times
MSC originated SCCP
Connection Requests
quests initiated by MSC.
ment requests initiated by MSC.
Measurement When BSC receives the Connect Indication message from MSC,
Figure 2378.

FIGURE 2378 MEASUREMENT POINT OF NUMBER OF MSC ORIGINATED

SCCP CONNECTION REQUESTS
Unit Times
MSC originated SCCP
Connection success
Description This counter counts the number of successful SCCP link establish-
ments initiated by MSC.
Usage This counter is used to find out the number of successful SCCP link
establishments initiated by MSC.
Measurement When BSC sends the Connect Response message to MSC, the
Figure 2379.

FIGURE 2379 MEASUREMENT POINT OF NUMBER OF MSC ORIGINATED

SCCP CONNECTION SUCCESS
Unit Times


Chapter 62
DTM Cell Measurement
Table of Contents
Overview...................................................................... 2402
C901560001 Number of voice access in mobile with DTM abil-
ity ............................................................................... 2402
C901560002 Number of packet access in mobile with DTM
ability .......................................................................... 2403
C901560003 Number of received IMSI when link estab-
lish .............................................................................. 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 assign-
ment success in dedicated mode .................................... 2406
C901560010 Number of UL DTM database resource assign-
ment 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 suc-
cess............................................................................. 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 suc-
cess............................................................................. 2411
C901560021 Number of DL DTM resource assignment fail-
ure .............................................................................. 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 han-

dover........................................................................... 2413
C901560026 Number of successfully DL DTM establish-
ment ........................................................................... 2414
Overview
DTM cell measurement studies the DTM service condition of mo-
bile 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 mo-
bile phone that has the DTM capability in the cell within the mea-
surement 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.
Point
1. When BSC receives the Classmark Change message from MS, if
Classmark3 carries the information that the MS has DTM multi-
timeslot 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 des-
tination cell receives the Radio Apply message, if Classmark3
carries the information that the MS has DTM multi-timeslot ca-
pability, the counter increments.
Unit 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.
Point
1. During uplink two-step access, when BSC receives the resource
request which indicates that MS has DTM multi-timeslot capa-
bility, the counter increments.
2. During downlink access, when BSC receives the down-
link assignment request which indicates that MS has DTM
multi-timeslot capability, the counter increments.
Unit Times
received IMSI when link
establish
Description This counter counts the number of IMSIs received during link es-
tablishment in the cell within the measurement period.
Usage This counter is used to find out the number of IMSIs received dur-
ing link establishment in the cell.
Measurement When BSC receives the COMMON ID message from MSC, if no IMSI
Point information is saved originally, then the IMSI information carried
in the COMMON ID message is saved, and the counter increments.
Unit Times

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 During inter-cell handover or external handover, when the des-
Point tination cell receives the Radio Apply message which carries the
IMSI information, the counter increments.
Unit 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 During BSC's voice service process, the counter increments when
Point the GTTP message (GPRS information) is received from MS.
Unit Times
BSC successfully sent GTTP
message under DTM mode
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 During BSC's voice service process, when the GTTP message is re-
Point ceived from MS and then is successfully sent to SGSN, the counter
increments.
Unit 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 measure-
ment 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 During BSC's voice service process, the counter increments when
Point the DTM request message is received from MS.
Unit 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 1. When BSC receives the DTM request from MS but does not
Point process due to MS not on SDCCH, the counter increments.
2. When BSC receives the DTM request from MS but does not
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.
4. When BSC receives the DTM request from MS but does not
process due to the DTM request being repeated, the counter
increments.
Unit Times

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 During BSC's voice service process, when the DTM request is
Point received from MS and the resource is acquired successfully, the
counter increments.
Unit Times
face
C901560010 Number
of UL DTM database
resource assignment failure
in dedicated mode
Description This counter counts the number of failed uplink DTM service re-
questing 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 During BSC's voice service process, when the DTM request is re-
Point ceived from MS and the resource request fails, the counter incre-
ments.
Unit Times
face

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.
Point ceived 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 Times
handover(intra-cell) success
due to uplink DTM
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 After the intra-cell handover is completed, if BSC judges that the
Point MS is implementing DTM service, the counter increments.
Unit Times

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 mea-
surement period.
Usage This counter is used to find out the number of failed intra-cell han-
dovers due to uplink DTM service in dedicated mode in the cell.
Measurement During intra-cell handover, when the handover fails due to BSC
Point assignment failure or T3107 timeout, if BSC judges that the MS is
implementing DTM service, the counter increments.
Unit 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.
Point ceived and the DTM service fails due to MS being in the handover
status, the counter increments.
Unit Times
UL DTM link establishment
success
Description This counter counts the number of successful uplink DTM service
establishments in dedicated mode in the cell within the measure-
ment period.

Usage This counter is used to find out the number of successful uplink
DTM service establishments in dedicated mode in the cell.
Measurement During the uplink establishment process, the ranps module on CMP
Point 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 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 During BSC's voice service process, when the downlink LLC data
Point frame is received in GTTP mode, the counter increments.
Unit 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 During BSC's voice service process, when the LLC frame is sent on
Point FACCH in GTTP mode, the counter increments.
Unit Times

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 dedi-
cated mode in the cell within the measurement period.
Measurement During BSC's voice service process, when DTM service is intiated
Point due to receiving LLC data frame sent by SGSN, the counter incre-
ments.
Unit 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 During BSC's voice service process, when DTM service is initiated
Point 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 mes-
sage, PS assignment message, and LLC frame sending message.
In this case, the counter increments.
Unit Times

DTM resource assignment
success
Description This counter counts the number of downlink DTM service request-
ing 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.
Point due to receiving LLC data frame sent by SGSN and the resource is
acquired successfully, the counter increments.
Unit Times
face
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.
Point due to receiving LLC data frame sent by SGSN and the resource
request fails, the counter increments.
Unit Times
face

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.
Point ceived 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 Times
successfully handover
occurs due to DL DTM
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 After the intra-cell handover is completed, if BSC judges that the
Point MS is implementing DTM service and the DTM resource assignment
is in downlink, the counter increments.
Unit 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 han-
dovers due to downlink DTM service in dedicated mode in the cell.
Measurement During intra-cell handover, when the handover fails due to BSC
Point 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 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.
Point ceived, if DTM service fails due to MS being in the handover status
and if DTM service is in downlink, the counter increments.
Unit Times

C901560026 Number
of successfully DL DTM
establishment
Description This counter counts the number of successful downlink DTM ser-
vice establishments in dedicated mode in the cell within the mea-
surement period.
Usage This counter is used to find out the number of successful downlink
DTM service establishments in dedicated mode in the cell.
Measurement During downlink DTM service process, when the RANPS module
Point on CMP inside BSC receives the instance establishment indication
message from the MAC module on UPPB, the counter increments.
Unit 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 Applica-
tion ............................................................................. 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

Overview
LAPD measurement counters reflect the message transceiving
condition at Abis interface between BSC and BTS. The measure-
ment takes each LAPD link (channel cluster) as the statistics unit.
It measures the transmitted data volume on LAPD link and mes-
sage 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 re-
ceived 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 The counter counts when SPB receives the EV_DLDATA_REQ mes-
Point sage from CMP.
C901570002 Number of BTS

Sent to MP
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 The counter counts when CMP receives the EV_DLDATA_IND mes-
Point sage 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 The counter counts when BTS receives the I frame from SPB.
Point
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 The counter counts when SPB receives the I frame from BTS.
Point
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

Measurement The counter counts when BTS receives the UI frame from SPB.
Point
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 The counter counts when SPB receives the UI frame from BTS.
Point
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 The counter counts when BTS receives the LAPD message from
Point SPB.
Received Frame
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 The counter counts when SPB receives the LAPD message from
Point 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 num-
ber 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 The counter counts when a message is discarded due to the high-
Point priority 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 num-
ber 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 The counter counts when a message is discarded due to the low-
Point priority 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 receiv-
ing high-priority LAPD messages from CMP on LAPD link.

Measurement The counter counts when SPB receives the high-priority message
Point from CMP.
Success in Low Priority
Queue
Description This counter counts the number of low-priority LAPD message en-
tering the queue successfully.
Usage This counter is used to find out the number of successfully receiv-
ing low-priority LAPD messages from CMP on LAPD link.
Measurement The counter counts when SPB receives the low-priority message
Point from CMP.
C901570013 Number of in
Queue Request UB Fail
Description This counter counts the number of failed UB requests when receiv-
ing the high/low-priority message on LAPD link.
Usage This counter is used to find out memory request failure when re-
ceiving the high/low-priority LAPD message from CMP on LAPD
link.
Measurement The counter counts when UB request fails during the process of
Point receiving the high/low-priority message on LAPD link.
C901570014 Resend
Number
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 The counter counts when I frame is resent on LAPD link due to
Point T200 timeout. The measurement point is A, as shown in Figure
2380.

FIGURE 2380 MEASUREMENT POINT OF RESENDING I FRAME ON LAPD

LINK DUE TO T200 TIMEOUT
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 re-
turns 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 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.
Point

FIGURE 2381 MEASUREMENT POINT OF NUMBER OF RESENDING FRAME

UPON REQUEST
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 establish-
ments.
Measurement LAPD link establishment negotiation is completed, and the system
Point enters multi-frame establishment status.
C901570017 Broken
Number
Description This counter counts the number of LAPD link breaks.
Usage This counter is used to find out the number of LAPD link breaks.
Measurement The LAPD link is released, and the system enters the status of
Point waiting for link establishment.

C901570018 Protocol Error

Number
Description When protocol error occurs on LAPD link, the multi-frame link pro-
tocol reports the protocol error to the layer management entity.
This counter counts the number of protocol error messages re-
ceived by the layer management entity.
Usage This counter is used to find out protocol errors on LAPD link.
Point
FIGURE 2382 MEASUREMENT POINT 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 The counter counts when the LAPD process receives the T200 time-
Point out message.

T201 Overtime
Description T201 defines the time limit of response for LAPD identification au-
thentication. 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 re-
quest is acknowledged.
Point out message.
T203 Overtime
Description T203 defines the maximum time allowed for no frame interaction.
This counter counts the number of T203 timeout on LAPD link.
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.
Point out message.
T204 Overtime
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.
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 op-
posite end due to hop frame in the slide window, indicating that the
transmission delay difference between different channels is large.
Point out message.

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 mes-
sage 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 When an I frame outside of the slide window is received by the
Point 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 mes-
sage 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 When an unexpected frames in the slide window is received by the
Point 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 During the message receiving process of slide window of LAPD
Point link, the counter counts when the frame numbers received on all
channels exceed the expected frame number.

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 The counter counts when message transmission on LAPD link fails
Point 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 The uplink flow on LAPD link is counted every 5 minutes, and the
Point maximum flow is recorded.
C901570028 Max Down

Flow
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 The downlink flow on LAPD link is counted every 5 minutes, and
Point 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 re-
ceived from BTS on LAPD link during the performance measuremnt
report process. Such frames include all types of frames in the LAPD
protocol.
Measurement The current flow of uplink messages on LAPD link is recorded every
Point 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 re-
port process. Such frames include all types of frames in the LAPD
protocol.
Measurement The current flow of downlink messages on LAPD link is recorded
Point every 5 minutes.


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 sta-
tus 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 han-
dover 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 han-
dover 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 sta-
tus 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

Overview
LCS measurement involves counters used for evaluating perfor-
mance and status of location services, such as the number of lo-
cation 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 The counter counts when CS domain receives the location request
Point from the core network. The measurement point is A, as shown in
Figure 2383.
FIGURE 2383 MEASUREMENT POINT OF NUMBER OF RECEIVING LOCATION

REQUEST IN CS
Unit Times
Related Features � ZGO-01-03-002 LCS with CGI+TA
� ZGO-01-03-003 LCS with AGPS

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 The counter counts when CS domain receives the location termi-
Point nation from the core network. The measurement point is A, as
FIGURE 2384 MEASUREMENT POINT OF NUMBER OF LOCATION

TERMINATIONS RECEIVED IN CS DOMAIN
Unit 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 re-
quests is counted.
Measurement The counter counts the number of TA requests when iBSC receives
Point the location request from SMLC. The measurement point is A, as

FIGURE 2385 MEASUREMENT POINT OF NUMBER OF TA REQUEST IN CS
Unit Times
Related Features ZGO-01-03-002 LCS with CGI+TA
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 The counter counts when iBSC sends TA response to SMLC after
Point receiving TA request correctly from SMLC. The measurement point
FIGURE 2386 MEASUREMENT POINT OF NUMBER OF TA RESPONSES IN

CS DOMAIN
Unit Times

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 The counter counts when the MS position command in CS domain
Point is received. The measurement point is A, as shown in Figure 2387.
FIGURE 2387 MEASUREMENT POINT OF NUMBER OF MS POSITION

COMMANDS IN CS DOMAIN
Unit Times
Related Features ZGO-01-03-003 LCS with AGPS
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 The counter counts when iBSC receives the position response from
Point MS. The measurement point is A, as shown in Figure 2388.


RESPONSE IN CS DOMAIN
Unit Times
location success in CS
Description This counter counts the number of location successes in CS do-
main.
Measurement The counter counts when iBSC receives the position result from
Point SMLC. The measurement point is A, as shown in Figure 2389.
FIGURE 2389 MEASUREMENT POINT OF NUMBER OF LOCATION SUCCESSES

IN CS DOMAIN
Unit Times

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 When the location request from the core network is received, if
Point 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 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 After iBSC sends the location command to MS, the radio timer
Point starts. When the timer is timeout, the counter counts the number

of location failures in CS domain due to radio timer timeout. The


TO RADIO TIMER EXPIRATION IN CS
Unit Times
sending BSSLAP RESET
message due to Intra-BSS
handover in CS
Description During the MS position process, when intra-BSC handover occurs,
the counter counts the number of location delays.
Measurement During the MS position process, intra-BSC handover occurs, the
Point counter counts the number of location delays when the handover
completion message is received from MS. The measurement point

FIGURE 2392 MEASUREMENT POINT OF NUMBER OF LOCATION DELAYS IN

CS DOMAIN DUE TO INTRA-BSC HANDOVER
Unit 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 The counter counts when the intra-BSC handover timer is timeout
Point 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


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 The counter counts when the location monitoring timer is timeout.

TO LOCATION MONITORING TIMER TIMEOUT IN CS DOMAIN
Unit Times

Inter-BSS handover in CS
Description When the MS position command is received from SMLC, if the ex-
ternal handover flow is initiated, the location will fail.
Measurement When the MS position command is received, if the external han-
Point dover flow is initiated, the counter counts. The measurement point

TO INTER-BSS HANDOVER IN CS DOMAIN
Unit Times
location failure due to call
drop in CS
Description During the location process, iBSC receives the clear command from
the core network.
Measurement During the location process, the counter counts when iBSC re-
Point ceives the clear command from the core network. The measure-

FIGURE 2396 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURE

DUE TO CALL DROP IN CS DOMAIN
Unit 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 fail-
ure, and timer setting failure.
Measurement The counter counts when the following problems occur: message
Point sending failure between modules, requesting SCCP connection fail-
Unit Times
receiving location request in
PS
Description This counter counts the number of location requests received by
PS domain from the core network.

Measurement The counter counts when PS domain receives the location request
Point from the core network. The measurement point is A, as shown in
Figure 2397.
FIGURE 2397 MEASUREMENT POINT OF NUMBER OF LOCATION REQUESTS

IN PS DOMAIN
Unit Times
receiving location abort in
PS
Description This counter counts the number of location terminations received
by PS domain from the core network.
Measurement The counter counts when PS domain receives the location termi-
Point nation from the core network. The measurement point is A, as

FIGURE 2398 MEASUREMENT POINT OF NUMBER OF LOCATION

TERMINATIONS RECEIVED IN PS DOMAIN
Unit 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 re-
quests is counted.
Measurement The counter counts the number of TA requests when iBSC receives
Point the location request from SMLC. The measurement point is A, as
FIGURE 2399 MEASUREMENT POINT OF NUMBER OF TA REQUESTS IN PS

DOMAIN
Unit Times

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 The counter counts when iBSC sends TA response to SMLC after
Point receiving TA request correctly from SMLC. The measurement point
FIGURE 2400 MEASUREMENT POINT OF NUMBER OF TA RESPONSES IN

PS DOMAIN
Unit 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 The counter counts when BSC receives the MS position command
Point in PS domain. The measurement point is A, as shown in Figure
2401.


COMMANDS IN PS DOMAIN
Unit 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 The counter counts when iBSC receives the position response from
Point the core network. The measurement point is A, as shown in Figure
2402.

RESPONSE IN PS DOMAIN
Unit Times

location success in PS
Description This counter counts the number of location successes in PS do-
main.
Measurement The counter counts when iBSC receives the position result from
Point SMLC. The measurement point is A, as shown in Figure 2403.
FIGURE 2403 MEASUREMENT POINT OF NUMBER OF LOCATION SUCCESSES

IN PS DOMAIN
Unit 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 When the location request from the core network is received, if
Point the Lb interface link is broken, the counter counts the number of
location failures in PS domain due to abnormal Lb interface status.


TO ABNORMAL STATUS OF LB INTERFACE IN PS
Unit 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 After iBSC sends the location command to the core network, the
Point 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 IN PS DOMAIN DUE TO

RADIO TIMER TIMEOUT
Unit Times


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 During the positioning process in PS domain, if inter-module cell
Point reselection occurs, the counter counts when the FLUSH LL mes-
sage is received from the core network. The measurement point

TO INTER-MODULE CELL RESELECTION IN PS DOMAIN
Unit Times

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 During the positioning process in PS domain, if intra-module cell
Point reselection occurs, the counter counts when the FLUSH LL mes-
sage 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 Times
location Timer expiration in
PS
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 The counter counts when the location monitoring timer is timeout.

TO LOCATION MONITORING TIMER TIMEOUT IN PS DOMAIN
Unit Times
location failure due to other
BSC's cause in PS
Description Location fails due to other causes inside iBSC, such as message
sending failure between modules, requesting SCCP connection fail-
Measurement The counter counts when the following problems occur: message
Point sending failure between modules, requesting SCCP connection fail-
Unit Times


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 The RESET message is received at BSC from SMLC.
Measurement The counter counts when the RESET message is received at BSC
Point from SMLC. The measurement point is A, as shown in Figure 2409.

FIGURE 2409 MEASUREMENT POINT OF NUMBER OF RESET MESSAGES

RECEIVED FROM SMLC
Unit 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 The counter counts when the RESET ACK message is sent to SMLC
Point from BSC. The measurement point is A, as shown in Figure 2410.
FIGURE 2410 MEASUREMENT POINT OF NUMBER OF RESET ACK MESSAGES

SENT TO SMLC

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 The counter counts when the RESET message is sent to SMLC from
Point BSC. The measurement point is A, as shown in Figure 2411.
FIGURE 2411 MEASUREMENT POINT OF NUMBER OF RESET MESSAGES

SENT TO SMLC
Unit Times
receiving RESET ACK
message from SMLC
Description This counter counts the number of RESET ACK messages received
at BSC from SMLC.
Measurement The counter counts when the RESET ACK message is received at
Point BSC from SMLC. The measurement point is A, as shown in Figure
2412.

FIGURE 2412 MEASUREMENT POINT OF NUMBER OF RESET ACK MESSAGES

RECEIVED FROM SMLC
Unit Times

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 in-
terface ......................................................................... 2458
C901600005 Maximum of busy 8 K relay circuits of Ater in-
terface ......................................................................... 2459
interface ...................................................................... 2461
C901600007 Total busy time of 8 K relay circuits of Ater in-
terface ......................................................................... 2462
Overview
Ater interface relay measurement (office) involves measurement
of the following information: the number of 16 K relay circuits con-
figured 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 in-
terface.

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 iBSC queries the database periodically, and saves the value ob-
Point tained from the database in this counter. The measurement point
FIGURE 2413 MEASUREMENT POINT OF NUMBER OF CONFIGURED 16 K

RELAY CIRCUITS OF ATER INTERFACE
Unit 16 K
C901600002 Average
of unavailable 16K relay
circuits of Ater interface
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
FIGURE 2414 MEASUREMENT POINT OF AVERAGE OF UNAVAILABLE 16K

RELAY CIRCUITS OF ATER INTERFACE
Unit 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.

FIGURE 2415 MEASUREMENT POINT OF AVERAGE OF AVAILABLE 16 K RELAY

CIRCUITS OF ATER INTERFACE
Unit 16 K
busy 16 K relay circuits of
Ater interface
Description This counter counts the maximum number of busy 16 K relay cir-
cuits at Ater interface.
Usage This counter is used to find out the maximum number of busy 16
K relay circuits at Ater interface.
Measurement iBSC queries the database periodically and saves the value ob-
Point tained from the database in this counter, or the counter counts
when Ater interface terrestrial circuit is released. The measure-
ment 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.)

FIGURE 2416 MEASUREMENT POINT OF MAXIMUM OF BUSY 16 K RELAY

CIRCUITS OF ATER INTERFACE - (1)
FIGURE 2417 MEASUREMENT POINT OF MAXIMUM OF BUSY 16 K RELAY

Unit Times
busy 8 K relay circuits of Ater
interface
Description This counter counts the maximum number of busy 8 K relay cir-
cuits at Ater interface.
Usage This counter is used to find out the maximum number of busy 8 K
relay circuits at Ater interface.

released.)
FIGURE 2418 MEASUREMENT POINT OF MAXIMUM OF BUSY 8K RELAY

FIGURE 2419 MEASUREMENT POINT OF MAXIMUM OF BUSY 8K RELAY

Unit 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
released.)
FIGURE 2420 MEASUREMENT POINT OF TOTAL BUSY TIME OF 16 K RELAY


FIGURE 2421 MEASUREMENT POINT OF TOTAL BUSY TIME OF 16 K RELAY

Unit Second
C901600007 Total busy time

of 8 K relay circuits of Ater
interface
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
released.)

FIGURE 2422 MEASUREMENT POINT OF TOTAL BUSY TIME OF 8K RELAY

FIGURE 2423 MEASUREMENT POINT OF TOTAL BUSY TIME OF 8K RELAY

Unit Second


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 ini-
tiated by BSC towards TC.
Usage This counter is used to find out the number of link establishment
requests initiated by BSC towards TC.

Measurement Rancs sends the TC resource request to Ater interface. The counter
Point increments when Ater interface sends the SCCP link establishment
request to iTC. The measurement point is A, as shown in Figure
2424.
FIGURE 2424 MEASUREMENT POINT OF NUMBER OF SCCP ESTABLISHMENT

REQUESTS (BSC TO TC)
Unit Times
SCCP establishments
success (BSC to TC)
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 estab-
lishments initiated by BSC towards TC. The BSC-to-TC link estab-
lishment success rate can be calculated according to this counter's
value and the number of link establishment requests.
Measurement When the Ater process receives the Connect Conf message from
Point iTC, the counter increments. The measurement point is A, as

Chapter 67 Ater Interface SCCP Connections Measurement
FIGURE 2425 MEASUREMENT POINT OF NUMBER OF SCCP CONNECTION

SUCCESSES
Unit 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 When the Ater process expires at the timer TAterWaitConn, the
Figure 2426.


FAILURE DUE TO TIMEOUT
Unit Times
C901610004 Number
of SCCP establishment
refused (BSC to TC)
Description This counter counts the number of rejected link establishment re-
quests initiated by BSC towards TC.
Measurement When the Ater process receives the Disconnect Ind message from
Point the AterDispatch process, the counter increments. The measure-

Chapter 67 Ater Interface SCCP Connections Measurement

REQUEST BEING REJECTED
Unit Times


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


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

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


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 up-
link/downlink quality and receiving level in the measurement
report. The measurement point of all counters in this measure-
ment task is A, as shown in Figure 2428.
FIGURE 2428 MEASUREMENT POINT OF BTS SENDING MEAUREMENT

REPORT TO BSC

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 (prepro-
cessing report or enhanced preprocessing measurement report).
This counter increments when BSC receives the UL radio mea-
surement report (preprocessing report or enhanced preprocessing
measurement report) in which UL RQ=0 and receive level is be-
tween 0 and 10.
Usage This counter is used to find out radio channel's UL quality and re-
ceive level.
Measurement This counter counts when BSC receives the UL radio measurement
Point report (preprocessing report or enhanced preprocessing measure-
ment 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 Times

receive level between 11
and 15
tween 11 and 15.
ceive level.
ment 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 Times
and 20


tween 16 and 20.
ceive level.

REPORT TO BSC
Unit Times
and 30
tween 21 and 30.
ceive level.


REPORT TO BSC
Unit Times
and 40
tween 31 and 40.
ceive level.

REPORT TO BSC

Unit Times
and 63
tween 41 and 63.
ceive level.

REPORT TO BSC
Unit Times

10
tween 0 and 10.
ceive level.

REPORT TO BSC
Unit Times
and 15


tween 11 and 15.
ceive level.

REPORT TO BSC
Unit Times
and 20
tween 16 and 20.
ceive level.


REPORT TO BSC
Unit Times
and 30
tween 21 and 30.
ceive level.

REPORT TO BSC
Unit Times

and 40
tween 31 and 40.
ceive level.

REPORT TO BSC
Unit Times
and 63


tween 41 and 63.
ceive level.

REPORT TO BSC
Unit Times
10
tween 0 and 10.
ceive level.


REPORT TO BSC
Unit Times
and 15
tween 11 and 15.
ceive level.

REPORT TO BSC
Unit Times

and 20
tween 16 and 20.
ceive level.

REPORT TO BSC
Unit Times
and 30


tween 21 and 30.
ceive level.

REPORT TO BSC
Unit Times
and 40
tween 31 and 40.
ceive level.


REPORT TO BSC
Unit Times
and 63
tween 41 and 63.
ceive level.

REPORT TO BSC
Unit Times

10
tween 0 and 10.
ceive level.

REPORT TO BSC
Unit Times
and 15


tween 11 and 15.
ceive level.

REPORT TO BSC
Unit Times
and 20
tween 16 and 20.
ceive level.


REPORT TO BSC
Unit Times
and 30
tween 21 and 30.
ceive level.

REPORT TO BSC
Unit Times

and 40
tween 31 and 40.
ceive level.

REPORT TO BSC
Unit Times
and 63


tween 41 and 63.
ceive level.

REPORT TO BSC
Unit Times
10
tween 0 and 10.
ceive level.


REPORT TO BSC
Unit Times
and 15
tween 11 and 15.
ceive level.

REPORT TO BSC
Unit Times

and 20
tween 16 and 20.
ceive level.

REPORT TO BSC
Unit Times
and 30


tween 21 and 30.
ceive level.

REPORT TO BSC
Unit Times
and 40
tween 31 and 40.
ceive level.


REPORT TO BSC
Unit Times
and 63
tween 41 and 63.
ceive level.

REPORT TO BSC
Unit Times

10
tween 0 and 10.
ceive level.

REPORT TO BSC
Unit Times
and 15


tween 11 and 15.
ceive level.

REPORT TO BSC
Unit Times
and 20
tween 16 and 20.
ceive level.


REPORT TO BSC
Unit Times
and 30
tween 21 and 30.
ceive level.

REPORT TO BSC
Unit Times

and 40
tween 31 and 40.
ceive level.

REPORT TO BSC
Unit Times
and 63


tween 41 and 63.
ceive level.

REPORT TO BSC
Unit Times
10
tween 0 and 10.
ceive level.


REPORT TO BSC
Unit Times
and 15
tween 11 and 15.
ceive level.

REPORT TO BSC
Unit Times

and 20
tween 16 and 20.
ceive level.

REPORT TO BSC
Unit Times
and 30


tween 21 and 30.
ceive level.

REPORT TO BSC
Unit Times
and 40
tween 31 and 40.
ceive level.


REPORT TO BSC
Unit Times
and 63
tween 41 and 63.
ceive level.

REPORT TO BSC
Unit Times

10
tween 0 and 10.
ceive level.

REPORT TO BSC
Unit Times
and 15


tween 11 and 15.
ceive level.

REPORT TO BSC
Unit Times
and 20
tween 16 and 20.
ceive level.


REPORT TO BSC
Unit Times
and 30
tween 21 and 30.
ceive level.

REPORT TO BSC
Unit Times

and 40
tween 31 and 40.
ceive level.

REPORT TO BSC
Unit Times
and 63


tween 41 and 63.
ceive level.

REPORT TO BSC
Unit 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 (prepro-
This counter increments when BSC receives the DL radio mea-
measurement report) in which DL RQ=0 and receive level is be-
tween 0 and 10.
Usage This counter is used to find out radio channel's DL quality and
receive level.
Measurement This counter counts when BSC receives the DL radio measurement
ment report) in which DL RQ=0 and receive level is between 0 and


REPORT TO BSC
Unit Times
and 15
tween 11 and 15.
receive level.
ment report) in which DL RQ=0 and receive level between 11 and

REPORT TO BSC
Unit Times

and 20
tween 16 and 20.
receive level.
ment report) in which DL RQ=0 and receive level is between 16

REPORT TO BSC
Unit Times
and 30


tween 21 and 30.
receive level.

REPORT TO BSC
Unit Times
and 40
tween 31 and 40.
receive level.


REPORT TO BSC
Unit Times
and 63
tween 41 and 63.
receive level.

REPORT TO BSC
Unit Times

10
tween 0 and 10.
receive level.

REPORT TO BSC
Unit Times
and 15


tween 11 and 15.
receive level.

REPORT TO BSC
Unit Times
and 20
tween 16 and 20.
receive level.


REPORT TO BSC
Unit Times
and 30
tween 21 and 30.
receive level.

REPORT TO BSC
Unit Times

and 40
tween 31 and 40.
receive level.

REPORT TO BSC
Unit Times
and 63


tween 41 and 63.
receive level.

REPORT TO BSC
Unit Times
10
tween 0 and 10.
receive level.


REPORT TO BSC
Unit Times
and 15
tween 11 and 15.
receive level.

REPORT TO BSC
Unit Times

and 20
tween 16 and 20.
receive level.

REPORT TO BSC
Unit Times
and 30


tween 21 and 30.
receive level.

REPORT TO BSC
Unit Times
and 40
tween 31 and 40.
receive level.


REPORT TO BSC
Unit Times
and 63
tween 41 and 63.
receive level.

REPORT TO BSC
Unit Times

10
tween 0 and 10.
receive level.

REPORT TO BSC
Unit Times
and 15


tween 11 and 15.
receive level.

REPORT TO BSC
Unit Times
and 20
tween 16 and 20.
receive level.


REPORT TO BSC
Unit Times
and 30
tween 21 and 30.
receive level.

REPORT TO BSC
Unit Times

and 40
tween 31 and 40.
receive level.

REPORT TO BSC
Unit Times
and 63


tween 41 and 63.
receive level.

REPORT TO BSC
Unit Times
10
tween 0 and 10.
receive level.


REPORT TO BSC
Unit Times
and 15
tween 11 and 15.
receive level.

REPORT TO BSC
Unit Times

and 20
tween 16 and 20.
receive level.

REPORT TO BSC
Unit Times
and 30


tween 21 and 30.
receive level.

REPORT TO BSC
Unit Times
and 40
tween 31 and 40.
receive level.


REPORT TO BSC
Unit Times
and 63
tween 41 and 63.
receive level.

REPORT TO BSC
Unit Times

10
tween 0 and 10.
receive level.

REPORT TO BSC
Unit Times
and 15


tween 11 and 15.
receive level.

REPORT TO BSC
Unit Times
and 20
tween 16 and 20.
receive level.


REPORT TO BSC
Unit Times
and 30
tween 21 and 30.
receive level.

REPORT TO BSC
Unit Times

and 40
tween 31 and 40.
receive level.

REPORT TO BSC
Unit Times
and 63


tween 41 and 63.
receive level.

REPORT TO BSC
Unit Times
10
tween 0 and 10.
receive level.


REPORT TO BSC
Unit Times
and 15
tween 11 and 15.
receive level.

REPORT TO BSC
Unit Times

and 20
tween 16 and 20.
receive level.

REPORT TO BSC
Unit Times
and 30


tween 21 and 30.
receive level.

REPORT TO BSC
Unit Times
and 40
tween 31 and 40.
receive level.


REPORT TO BSC
Unit Times
and 63
tween 41 and 63.
receive level.

REPORT TO BSC
Unit Times

10
tween 0 and 10.
receive level.

REPORT TO BSC
Unit Times
and 15


tween 11 and 15.
receive level.

REPORT TO BSC
Unit Times
and 20
tween 16 and 20.
receive level.


REPORT TO BSC
Unit Times
and 30
tween 21 and 30.
receive level.

REPORT TO BSC
Unit Times

and 40
tween 31 and 40.
receive level.

REPORT TO BSC
Unit Times
and 63


tween 41 and 63.
receive level.

REPORT TO BSC
Unit Times


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 down-
link level. If the measurement report contains adjacent cell infor-
mation, 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


REPORT TO BSC
samples with C/I < -10db
Description 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 pre-
processing measurement report).
Usage This counter is used to find out DL level of adjacent cell.
Measurement This counter increments while DL level in this cell in DL radio mea-
Point surement report (preprocessing report or enhanced preprocessing
measurement report) received by BSC subtracting the level of ad-
jacent cell is lower than –10dB, as shown in Figure 2526.
FIGURE 2526 MEASUREMENT POINT OF BTS SENDING MEASUREMENT

REPORT TO BSC
Unit Times

Chapter 69 Measurement Report Adjacent Cell Measurement
samples with C/I between
-9db and -5db
Description This counter counts the number of samples with DL level in lo-
cal cell subtracting the level in adjacent cell within -9dB~-5dB in
received DL radio measurement report (preprocessing report or
enhanced preprocessing measurement report).
jacent cell is within -9dB~-5dB, as shown in Figure 2527.

REPORT TO BSC
Unit Times
-4db and 0db
cal cell subtracting the level in adjacent cell within -4dB~0dB in
jacent cell is within -4dB~0dB, as shown in Figure 2528.


REPORT TO BSC
Unit Times
1db and 5db
cal cell subtracting the level in adjacent cell within 1dB~5dB in
jacent cell is within 1dB~5dB, as shown in Figure 2529.

REPORT TO BSC
Unit Times

6db and 10db

REPORT TO BSC
Unit Times
11db and 15db


REPORT TO BSC
Unit Times
16db and 20db

REPORT TO BSC
Unit Times

samples with C/I > 20db
cal cell subtracting the level in adjacent cell > 20dB in received
DL radio measurement report (preprocessing report or enhanced
preprocessing measurement report).
jacent cell is higher than 20dB, as shown in Figure 2533.

REPORT TO BSC
Unit Times


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.

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 The counter's value is obtained by querying database when the
Point paging performance measurement data is reported periodically.
Unit 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.

Chapter 70 TRX Paging Measurement

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.
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.
Unit Times

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 Percent
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 Times
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 Times

Chapter 70 TRX Paging Measurement
C901640008 Number
of paging messages
retransmitted one times
Description This counter counts the number of paging messages being retrans-
mitted once after the original paging messages are sent.
Unit Times
C901640009 Number
of paging messages
retransmitted two times
mitted twice after the original paging messages are sent.
Unit Times
C901640010 Number
of paging messages
retransmitted three times
mitted three times after the original paging messages are sent.
Unit Times

C901640011 Numbers
of paging messages
retransmitted four times
mitted four times after the original paging messages are sent.
Unit Times

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 re-
ported 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 TRU is measured and reported periodically.
Point
Unit dbm


of TRX power (db)
Description This counter counts the minimum value of TRX's power within the
measurement period.
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.
Point
Unit dbm
TRX temperature (Celsius)
Description This counter counts the maximum value of TRX's temperature
Point
Unit Celsius
C901650005 Minimum of
TRX temperature (Celsius)
Description This counter counts the minimum value of TRX's temperature

Chapter 71 TRX Temperature Power Measurement

Point
Unit Celsius
C901650006 Mean of TRX

temperature (Celsius)
Description This counter counts the average value of TRX's temperature within
Point
Unit Celsius


Chapter 72
Terminal Ability Statistic
Table of Contents
Terminal Ability Statistics................................................ 2569
C901660001 Number of mobile support single TS DTM abil-
ity ............................................................................... 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


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

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 AM-
ROFR ........................................................................... 2646
RFR ............................................................................. 2647
ROHR .......................................................................... 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 dy-
namic allocation ............................................................ 2653
C901660065 Number of sampling received Class-
mark3.......................................................................... 2654
C901660066 Number of sampling received radio access abil-
ity ............................................................................... 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 capa-
bility of single TS DTM.
Usage This counter measures the number of mobiles that support the
single TS DTM ability.
Measurement This counter increments while Rancs receives the Classmark Up-
Point date 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.

FIGURE 2535 MEASUREMENT POINT OF NUMBER OF MOBILE SUPPORT

SINGLE TS DTM ABILITY
Unit Times
mobile support DTM GPRS
multi TS ability 5
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.
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.

FIGURE 2536 MEASUREMENT POINT OF NUMBER OF MOBILE SUPPORT DTM

GPRS MULTI TS ABILITY 5
Unit Times
multi TS ability 9
multi TS ability 9.
in Figure 2537.


Unit Times
multi TS ability 11
multi TS ability 11.
in Figure 2538.


Unit Times
mobile support DTM EGPRS
multi TS ability 5
Description This counter counts the number of mobiles that support DTM EG-
PRS multi TS ability 5.
EGPRS multi TS ability 5.
sent by MS and the message indicates the MS supports DTM EG-
PRS multi TS ability 5. The measurement point is A1 or A2, as


EGPRS MULTI TS ABILITY 5
Unit Times
multi TS ability 9


Unit Times
multi TS ability 11


Unit Times
mobile support extend DTM
GPRS multi TS ability 5
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
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


EXTEND DTM GPRS MULTI TS ABILITY 5
Unit Times


Unit Times


Unit Times


Unit Times


Unit Times
EGPRS multi TS ability 5
DTM EGPRS multi TS ability 5.
EGPRS multi TS ability 5. The measurement point is A1 or A2, as


EXTEND DTM EGPRS MULTI TS ABILITY 5
Unit Times


Unit Times


Unit Times


Unit Times


Unit Times
mobile of GPRS multi TS
ability 1
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 This counter increments while PS control plane receives the down-
Point link assignment requests sent by the user plane, the resource re-
quests 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.

FIGURE 2552 MEASUREMENT POINT OF NUMBER OF MOBILE OF GPRS

MULTI TS ABILITY 1 - (1)



Unit Times
ability 2
TS ability 2.
multi TS ability 2.
2557.




Unit Times
ability 3
TS ability 3.
multi TS ability 3.


2560.




Unit Times
ability 4
TS ability 4.
multi TS ability 4.
2563.




Unit Times

ability 5
TS ability 5.
Usage This counter is used to measure the number of link setup requests
originated from BSC to TC.
2566.




Unit Times
ability 6
TS ability 6.
multi TS ability 6.

2569.




Unit Times
ability 7
TS ability 7.
multi TS ability 7.
2572.




Unit Times

ability 8
TS ability 8.
multi TS ability 8.
2575.




Unit Times
ability 9
TS ability 9.
multi TS ability 9.

2578.




Unit Times
ability 10
TS ability 10.
2581.




Unit Times

ability 11
TS ability 11.
2584.




Unit Times
ability 12
TS ability 12.

2587.




Unit Times
ability 30
TS ability 30.
2590.




Unit Times

ability 31
TS ability 31.
2593.




Unit Times
ability 32
TS ability 32.

2596.




Unit Times
ability 33
TS ability 33.
2599.




Unit Times

ability 34
TS ability 34.
2602.




Unit Times
mobile of EGPRS multi TS
ability 1
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.

the MS supports EGPRS multi TS ability 1. The measurement point
2605.
FIGURE 2603 MEASUREMENT POINT OF NUMBER OF MOBILE OF EGPRS




Unit Times
ability 2
multi TS ability 2.
multi TS ability 2.
2608.





Unit Times
ability 3
multi TS ability 3.
multi TS ability 3.
2611.




Unit Times
ability 4
multi TS ability 4.
multi TS ability 4.

2614.




Unit Times
ability 5
multi TS ability 5.
Usage This counter is used to measure the number of link setup requests
originated from BSC to TC.
2617.





Unit Times
ability 6
multi TS ability 6.
multi TS ability 6.
2620.




Unit Times
ability 7
multi TS ability 7.
multi TS ability 7.


2623.




Unit Times
ability 8
multi TS ability 8.
multi TS ability 8.
2626.




Unit Times

ability 9
multi TS ability 9.
multi TS ability 9.
2629.




Unit Times
ability 10

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.




Unit Times
ability 11
Figure 2635.




Unit Times

ability 12
Figure 2638.




Unit Times
ability 30


Figure 2641.




Unit Times
ability 31
Figure 2644.





Unit Times
ability 32
Figure 2647.




Unit Times
ability 33


Figure 2650.




Unit Times
ability 34
Figure 2653.





Unit Times
mobile support FR
Description This counter counts the number of mobiles that support FR.
Usage It is used to measure the number of mobiles that support FR.
Measurement This counter increments while Rancs process receives the setup
Point (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.
FIGURE 2654 MEASUREMENT POINT OF NUMBER OF MOBILE SUPPORT FR
Unit Times
mobile support HR
Description This counter counts the number of mobiles that support HR.
Usage It is used to measure the number of mobiles that support HR.
contained in this message is HR. The measurement point is A1

FIGURE 2655 MEASUREMENT POINT OF NUMBER OF MOBILE SUPPORT HR
Unit Times
mobile support EFR
Description This counter counts the number of mobiles that support EFR.
Usage It is used to measure the number of mobiles that support EFR.
contained in this message is EFR. The measurement point is A1
FIGURE 2656 MEASUREMENT POINT OF NUMBER OF MOBILE SUPPORT EFR
Unit Times

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.
contained in this message is AMRFR. The measurement point is A1

AMRFR
Unit 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.
contained in this message is AMRHR. The measurement point is
A1 (caller) and A2 (callee), as shown in Figure 2658.


AMRHR
Unit Times
mobile support wideband
AMROFR
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.
contained in this message is wideband AMROFR. The measurement
point is A1 (caller) and A2 (callee), as shown in Figure 2659.


WIDEBAND AMROFR
Unit Times
AMRFR
AMRFR.
AMRFR.
contained in this message is wideband AMRFR. The measurement
point is A1 (caller) and A2 (callee), as shown in Figure 2660.


WIDEBAND AMRFR
Unit Times
AMROHR
AMROHR.
AMROHR.
contained in this message is wideband AMROHR. The measure-
ment point is A1 (caller) and A2 (callee), as shown in Figure 2661.


WIDEBAND AMROHR
Unit 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.
contained in this message is AMROHR. The measurement point is
A1 (caller) and A2 (callee), as shown in Figure 2662.

AMROHR
Unit Times

mobile support extend uplink
TBF
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 When PS control plane receives the downlink assignment requests
Point 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)

EXTEND UPLINK TBF - (2)

Unit Times
mobile support NACC
Description This counter counts the number of mobiles that support NACC.
Usage It is used to measure the number of mobiles that support NACC.
plane on two-phase access, if NACC is supported, the counter in-
crements. The measurement point is A1 and A2, as shown in

NACC - (1)

NACC - (2)

Unit Times
mobile support GPRS
extend dynamic allocation
Description This counter counts the number of mobiles that support GPRS ex-
tended dynamic allocation.
extended dynamic allocation.
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.
FIGURE 2667 MEASUREMENT POINT OF NUMBER OF MOBILE SUPPORT GPRS

EXTEND DYNAMIC ALLOCATION - (1)

FIGURE 2668 MEASUREMENT POINT OF NUMBER OF MOBILE SUPPORT GPRS

EXTEND DYNAMIC ALLOCATION - (2)
Unit Times
mobile support EGPRS
extend dynamic allocation
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.


EGPRS EXTEND DYNAMIC ALLOCATION - (1)

EGPRS EXTEND DYNAMIC ALLOCATION - (2)
Unit Times
C901660065 Number
of sampling received
Classmark3
Description This counter counts the number of samples that receive Class-
mark3.
Usage It is used to measure the number of samples that receive Class-
mark3.

sent by MS and the message indicates Classmark3 is received. The

measurement point is A1 or A2, as shown in Figure 2671.
FIGURE 2671 MEASUREMENT POINT OF NUMBER OF SAMPLING RECEIVED

CLASSMARK3
Unit Times
sampling received radio
access ability
Description This counter counts the number of samples that receive radio ac-
cess ability.
Usage It is used to measure the number of samples that receive radio
access ability.
Point link 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.


RADIO ACCESS ABILITY - (1)

RADIO ACCESS ABILITY - (2)
Unit Times
C901660069 Num of MS
supporting PS handover
Statistics object: MS
MS
Description 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 mea-

FIGURE 2674 MEASUREMENT POINT OF NUMBER OF MS SUPPORTING PS

HANDOVER
Unit 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 1. When BSC receives the handover/assignment failure message
Point 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.

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 sup-
port 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 1. When BSC receives the handover/assignment failure message
Point 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 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 Re-
ceived.......................................................................... 2665
Sent ............................................................................ 2665
C901670014 Number of A2SP Message Signal Unit Re-
ceived.......................................................................... 2665
Sent ............................................................................ 2666
C901670016 Number of Stm Message Signal Unit Re-
ceived.......................................................................... 2666
C901670017 Number of Stm Message Signal Unit Sent......... 2666
C901670018 Number of Sltm Message Signal Unit Re-
ceived.......................................................................... 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 Conges-
tion ............................................................................. 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 manage-
ment actions................................................................. 2672
C901670040 Number of remote management inhibit .......... 2672
C901670041 Duration of SL inhibition due to remote manage-
ment actions................................................................. 2673
C901670042 Number of remote processor outage.............. 2673
C901670043 Duration of SL inhibition due to remote proces-
sor outage.................................................................... 2673
C901670044 Number of sending unaccess messages.......... 2674
C901670045 Number of sending flow-control discarded mes-
sages........................................................................... 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 upper-
layer 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 This counter counts the duration of the signaling link being faulty,
blocked, or not activated.

Chapter 73 MTP3 Signaling Link Statistics
Measurement During a measurement period, the counter counts the duration of

Point MTP3 link not in the service status.
Unit Second
Signaling Link Out of Service
Description This counter counts the number of the signaling link exiting the
service status.
Measurement The counter accumulates when the link status is changed from
Point available to unavailable.
Unit Times
Message Signal Unit Sent
Description This counter counts the number of MSUs sent on the signaling link.
Measurement The counter accumulates when the upper-layer user sends the
Point 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 The counter accumulates when the MSU message is sent on the
Point link (only counting the number of octets of SIF and SIO).

C901670005 Number
of Message Signal Unit
Received
Description This counter counts the number of MSUs received on the signaling
link.
Measurement The counter accumulates when the MSU message is received on
Point the link.
SIF-SIO Received
Description This counter counts the number of octets of SIF and SIO received
on the signaling link.
Measurement The counter accumulates when the MSU message is received on
Point 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 traf-
fic 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 measure-
ment 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

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 * (Num-

ber 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 During a measurement period, the counter records the peak traffic
Point load of the link.
Unit ‱
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 accu-
mulated. 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 This counter records the duration of the signaling link being in the
Point status of peak traffic load within the measurement period.
Unit Second

Change Over on OMP
Description This counter counts the number of changeovers occurred on the
signaling link (on OMP).
Measurement When the MTP3 link exits the service and changeover is initiated
Point 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 The counter increments when the TFP message is received on the
Point link.
C901670011 Rate of Mtp3

Link Occupy
Description This counter counts the ratio (‱) of link bandwidth that the sig-
naling message occupies. Because the M2PA link shares the band-
width, precise calculation of ratio is not possible. The ratio is cal-
culated 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 mes-

sages sent + Number of bytes of messages received) * 8 / (Link
bandwidth * 2 * counting time)

Measurement The counter counts when the request of MTP3 link performance
Point statistics is received.
Unit ‱
SCCP Message Signal Unit
Received
Description This counter counts the number of SCCP messages received on
the link.
Measurement The counter accumulates when the SCCP message is received on
Point 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 The counter accumulates when the SCCP message is sent on the
Point 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 The counter accumulates when the ALCAP message is received on
Point the link.

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 The counter accumulates when the ALCAP message is sent on the
Point link.
Stm Message Signal Unit
Received
Description This counter counts the number of SNM messages received on the
link.
Measurement The counter accumulates when the SNM message is received on
Point the link.
C901670017 Number of Stm

Message Signal Unit Sent
Description This counter counts the number of SNM messages sent on the link.
Measurement The counter accumulates when the SNM message is sent on the
Point link.
Sltm Message Signal Unit
Received
Description This counter counts the number of STM messages (i.e. link test
message) received on the link.

Measurement The counter accumulates when the STM message is received on

Point 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 The counter accumulates when the STM message is sent on the
Point link.
SCCP SIF-SIO Received
Description This counter counts the number of octets of SCCP SIF and SIO
received on the link.
Measurement The counter accumulates when the SCCP message is received on
Point the link.
SCCP SIF-SIO Sent
Description This counter counts the number of octets of SCCP SIF and SIO
sent on the link.
Measurement The counter accumulates when the SCCP message is sent on the
Point 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.

Measurement The counter accumulates when the ALCAP message is received on

Point 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 broad-
band link (ATM), for other link types, its value is always zero.
Measurement The counter accumulates when the ALCAP message is sent on the
Point 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 The counter accumulates when the SNM message is received on
Point 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 The counter accumulates when the SNM message is sent on the
Point link.
C901670026 Octets of Sltm

SIF-SIO Received
Description This counter counts the number of octets of SIF and SIO of the
link test message (STM) received on the link.
Measurement The counter accumulates when the STM message is received on
Point 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 The counter accumulates when the STM message is sent on the
Point link.
message discarded due to
Congestion
Description This counter counts the number of messages discarded due to con-
gestion. The counter's value is not zero only for ANSI standard,
for other protocol types, its value is always zero. When the func-
tion of flow control according to link level is enabled, the message
will not be discarded due to congestion.
Measurement When the MSU message is sent on the link, if the congestion level
Point of the link or office is higher than the message's priority, the mes-
sage is discarded and the counter accumulates.
restrictions Level 1
Description 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.
Measurement The counter accumulates when the link congestion is at level 1.
Point


Point
Point
Restrictions Level 1
Description This counter counts the duration of the link being at the congestion
Measurement The counter records the duration of the link being at the congestion
Point level 1 during a measurement period.
Unit Second
Unit Second

Unit Second
manual prohibition
Description This counter counts the duration of the link being in the manual
deactivation status.
Measurement The counter records the duration of the link being in the manual
Point 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 When the MTP3 link is put into service and changeback is initiated
Point 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 The counter accumulates when the link status is changed from
Point unavailable to available.
Unit Times

Local management inhibit
Description This counter counts the number of local inhibitions successfully
initiated by management entity (on OMP).
Measurement When the management entity initiates local inhibition successfully,
Point the counter accumulates.
Unit Times
SL inhibition due to Local
management actions
Description This counter counts the duration from local inhibition being initi-
ated successfully and local uninhibition being initiated successfully
(on OMP).
Measurement When the local inhibition is initiated successfully, the counter starts
Point 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 When the management entity initiates remote inhibition success-
Point fully, the counter accumulates.
Unit Times

SL inhibition due to remote
management actions
Description This counter counts the duration from remote inhibition being initi-
ated successfully and remote uninhibition being initiated success-
fully (on OMP).
Measurement When the remote inhibition is initiated successfully, the counter
Point starts counting. When the remote uninhibition succeeds, the
counter stops counting and records the duration.
Unit Second
remote processor outage
Description This counter counts the number of the remote processor being
faulty.
Measurement This counter accumulates when the remote processor is faulty.
Point
Unit Times
SL inhibition due to remote
processor outage
Description This counter counts the duration of the remote processor being
faulty.
Measurement This counter counts when the remote processor is faulty.
Point
Unit Second

sending unaccess messages
Description This counter counts the number of transfer-prohibited messages
(TFP) on the link.
Measurement The counter accumulates when the TFP message is sent on the
Point link.
Unit Times
C901670045 Number
of sending flow-control
discarded messages
Description This counter counts the number of flow-control discarded mes-
sages sent on the link.
Measurement The counter accumulates when the flow-control discarded mes-
Point sages 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 measure-
ment 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

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:

� 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 band-
width 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.

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 The counter accumulates when the TFA message is sent on the
Point link.
C901670050 Number of TFA

received
Description This counter counts the number of TFA messages received on the
link.
Measurement The counter accumulates when the TFA message is received on
Point the link.
TFC sent
Description This counter counts the number of TFC messages sent on the link.
Measurement The counter accumulates when the TFC message is sent on the
Point link.

TFC received
Description This counter counts the number of TFC messages received on the
link.
Measurement The counter accumulates when the TFC message is received on
Point the link.
RST sent
Description This counter counts the number of RST messages (i.e. route-set
test message) sent on the link.
Measurement The counter accumulates when the RST message is sent on the
Point link.
RST received
Description This counter counts the number of RST messages (i.e. route-set
test message) received on the link.
Measurement The counter accumulates when the RST message is received on
Point the link.
TRA sent
Description This counter counts the number of service-restart-allowed mes-
sages (TRA) sent on the link.
Measurement The counter accumulates when the TRA message is sent on the
Point link.

TRA received
Description This counter counts the number of service-restart-allowed mes-
sages (TRA) received on the link.
Measurement The counter accumulates when the TRA message is received on
Point the link.
UPU sent
Description This counter counts the number of user-part-unavailable mes-
sages (UPU) sent on the link.
Measurement The counter accumulates when the UPU message is sent on the
Point link.
UPU received
Description This counter counts the number of user-part-unavailable mes-
sages (UPU) received on the link.
Measurement The counter accumulates when the UPU message is received on
Point the link.
message discard controlled
by license
Description 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 for-
warded outwards from the local office and is directly discarded,
and the counter accumulates.

Measurement When the number of forwarding message exceeds the maximum

Point forwarding times allowed in Licence, call the overload control func-
tion to decide whether the subsequent messages will be discarded.


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 re-
ceived.......................................................................... 2684
C901680010 Number of ASP Down Ack message sent......... 2684
C901680011 Number of ASP Inactive message sent ........... 2685
C901680012 Number of ASP Inactive message re-
ceived.......................................................................... 2685
C901680013 Number of ASP Inactive Ack message re-
ceived.......................................................................... 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 re-
ceived.......................................................................... 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 Con-
trol .............................................................................. 2691
license ......................................................................... 2691
C901680034 Bytes of all message sent............................. 2691
C901680035 Bytes of all message received ....................... 2692

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
Overview
M3UA is short for MTP3-User Adaptation Layer. M3UA measure-
ment 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 pro-
tocols.
� It supports MTP3 nework management functions.
point of M3UA performance measurement counters.
data message sent
Description This counter counts the number of data messages sent.
Measurement The counter accumulates when the data message is sent.
Point
Unit Times
data message received
Description This counter counts the number of data messages received.
Measurement The counter accumulates when the data message is received.
Point
Unit Times

Chapter 74 M3UA Performance Statistics
ASP Up message sent
Description This counter counts the number of ASP Up messages sent.
Measurement The counter accumulates when the ASP Up message is sent.
Point
Unit Times
ASP Up message received
Description This counter counts the number of ASP Up messages received.
Measurement The counter accumulates when the ASP Up message is received.
Point
Unit Times
ASP Up Ack message
received
Description This counter counts the number of ASP Up Ack messages received.
Measurement The counter accumulates when the ASP Up Ack message is re-
Point ceived.
Unit Times
ASP Up Ack message sent
Description This counter counts the number of ASP Up Ack messages sent.
Measurement The counter accumulates when the ASP Up Ack message is sent.
Point
Unit Times

ASP Down message sent
Description This counter counts the number of ASP Down messages sent.
Measurement The counter accumulates when the ASP Down message is sent.
Point
Unit Times
C901680008 Number of ASP

Down message received
Description This counter counts the number of ASP Down messages received.
Measurement The counter accumulates when the ASP Down message is received.
Point
Unit Times
ASP Down Ack message
received
Description This counter counts the number of ASP Down Ack messages re-
ceived.
Measurement The counter accumulates when the ASP Down Ack message is re-
Point ceived.
Unit Times
ASP Down Ack message
sent
Description This counter counts the number of ASP Down Ack messages sent.
Measurement The counter accumulates when the ASP Down Ack message is sent.
Point

Unit Times
ASP Inactive message sent
Description This counter counts the number of ASP Inactive messages sent.
Measurement The counter accumulates when the ASP Inactive message is sent.
Point
Unit Times
ASP Inactive message
received
Description This counter counts the number of ASP Inactive messages re-
ceived.
Measurement The counter accumulates when the ASP Inactive message is re-
Point ceived.
Unit Times
ASP Inactive Ack message
received
Description This counter counts the number of ASP Inactive Ack messages
received.
Measurement The counter accumulates when the ASP Inactive Ack message is
Point received.
Unit Times

ASP Inactive Ack message
sent
Description This counter counts the number of ASP Inactive Ack messages
sent.
Measurement The counter accumulates when the ASP Inactive Ack message is
Point sent.
Unit Times
ASP Active message sent
Description This counter counts the number of ASP Active messages sent.
Measurement The counter accumulates when the ASP Active message is sent.
Point
Unit Times
C901680016 Number of ASP

Active message received
Description This counter counts the number of ASP Active messages received.
Measurement The counter accumulates when the ASP Active message is re-
Point ceived.
Unit Times
ASP Active Ack message
received
Description This counter counts the number of ASP Active Ack messages re-
ceived.

Measurement The counter accumulates when the ASP Active Ack message is re-
Point ceived.
Unit Times
ASP Active Ack message
sent
Description This counter counts the number of ASP Active Ack messages sent.
Measurement The counter accumulates when the ASP Active Ack message is
Point sent.
Unit Times
DAUD message sent
Description This counter counts the number of DAUD messages sent.
Measurement The counter accumulates when the DAUD message is sent.
Point
Unit Times
SCON message received
Description This counter counts the number of SCON messages received.
Measurement The counter accumulates when the SCON message is received.
Point
Unit Times

DAVA message received
Description This counter counts the number of DAVA messages received.
Measurement The counter accumulates when the DAVA message is received.
Point
Unit Times
DUNA message received
Description This counter counts the number of DUNA messages received.
Measurement The counter accumulates when the DUNA message is received.
Point
Unit Times
invalid message received
Description This counter counts the number of invalid data message received.
Measurement The counter counts when the key information carried in the mes-
Point sage is incorrect.
Unit Times
MGMT message sent
Description This counter counts the number of MGMT messages sent.

Measurement The counter accumulates when the MGMT message is sent.

Point
MGMT message received
Description This counter counts the number of MGMT messages received.
Measurement The counter accumulates when the MGMT message is received.
Point
Heartbeat message received
Description This counter counts the number of HeartBeat messages received.
Measurement The counter accumulates when the HeartBeat message is received.
Point
Unit Times
HeartBeat Ack message
sent
Description This counter counts the number of HeartBeatAck messages sent.
Measurement The counter accumulates when the HeartBeatAck message is sent.
Point
Unit Times
C901680028 Bytes of data

message received
Description This counter counts the number of bytes of DATA messages re-
ceived by M3UA.
Measurement The counter counts when M3UA receives the DATA message.
Point

Unit Byte
C901680029 Bytes of data

message transmitted
Description This counter counts the number of bytes of DATA messages sent
by M3UA.
Measurement The counter counts when M3UA sends the DATA message.
Point
Unit Byte
C901680030 Bytes of MGMT

message sent
Description This counter counts the number of bytes of MGMT messages sent.
Measurement The counter counts when the NTFY message or the ERR message
Point is sent.
Unit Byte
C901680031 Bytes of MGMT

message received
Description This counter counts the number of bytes of management mes-
sages received.
Measurement The counter counts when the NTFY message or the ERR message
Point is received.
Unit 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 The counter counts when a message is discarded due to flow con-
Point trol.
by license
warded outwards from the local office and is directly discarded.
The condition is reported to OAM and the counter accumulates.
C901680034 Bytes of all

message sent
Description This counter counts the bytes of all messages sent on SCTP, in-
cluding data message, management message, ASPSM message,
ASPTM message, and MGMT message.
Unit Byte

C901680035 Bytes of all

message received
Description This counter counts the bytes of all messages received on SCTP,
including data message, management message, ASPSM message,
ASPTM message, and MGMT message.
Unit Byte
ERROR message sent
Description This counter counts the number of ERROR messages sent.
Measurement The counter accumulates when the ERROR message is sent.
Point
Unit Times
ERROR message received
Description This counter counts the number of ERROR messages received.
Measurement The counter accumulates when the ERROR message is received.
Point
Unit Times
NOTIFY message sent
Description This counter counts the number of NOTIFY messages sent.
Measurement The counter accumulates when the NOTIFY message is sent.
Point
Unit Times

NOTIFY message received
Description This counter counts the number of NOTIFY messages received.
Measurement The counter accumulates when the NOTIFY message is received.
Point
Unit Times


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

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 mea-
sures 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 This counter counts the number of UDTs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends UDT.
Point
Unit Times

Chapter 75 SCCP Performance Statistics
UDT Received
Description This counter counts the number of UDTs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives UDT.
Point
Unit Times
UDTS Sent
Description This counter counts the number of UDTSs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends UDTS.
Point
Unit Times
UDTS Received
Description This counter counts the number of UDTSs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives UDTS.
Point
Unit Times
ERR Sent
Description This counter counts the number of ERRs sent by SCCP of the local
office.

Measurement The counter accumulates when SCCP sends ERR.

Point
ERR Received
Description This counter counts the number of ERRs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives ERR.
Point
SSP Sent
Description This counter counts the number of SSPs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends SSP.
Point
SSP Received
Description This counter counts the number of SSPs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives SSP.
Point
RSR Sent
Description This counter counts the number of RSRs sent by SCCP of the local
office.

Measurement The counter accumulates when SCCP sends RSR.

Point
RSR Received
Description This counter counts the number of RSRs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives RSR.
Point
RSC Sent
Description This counter counts the number of RSCs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends RSC.
Point
RSC Received
Description This counter counts the number of RSCs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives RSC.
Point
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 The counter accumulates when the SST sent by SCCP does not
Point receive the response.

CREF Sent
Description This counter counts the number of CREFs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends CREF.
Point
CREF Received
Description This counter counts the number of CREFs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives CREF.
Point
XUDT Sent
Description This counter counts the number of XUDTs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends XUDT.
Point
XUDT Received
Description This counter counts the number of XUDTs received by SCCP of the
local office.

Measurement The counter accumulates when SCCP receives XUDT.

Point
XUDTS Sent
Description This counter counts the number of XUDTSs sent by SCCP of the
local office.
Measurement The counter accumulates when SCCP sends XUDTS.
Point
XUDTS Received
Description This counter counts the number of XUDTSs received by SCCP of
the local office.
Measurement The counter accumulates when SCCP receives XUDTS.
Point
LUDT Sent
Description This counter counts the number of LUDTs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends LUDT.
Point
LUDT Received
Description This counter counts the number of LUDTs received by SCCP of the
local office.

Measurement The counter accumulates when SCCP receives LUDT.

Point
LUDTS Sent
Description This counter counts the number of LUDTSs sent by SCCP of the
local office.
Measurement The counter accumulates when SCCP sends LUDTS.
Point
LUDTS Received
Description This counter counts the number of LUDTSs received by SCCP of
the local office.
Measurement The counter accumulates when SCCP receives LUDTS.
Point
C901690024 Number of DT1

Received
Description This counter counts the number of DT1s received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives DT1.
Point

Sent
Description This counter counts the number of DT1s sent by SCCP of the local
office.

Measurement The counter accumulates when SCCP sends DT1.

Point

Received
Description This counter counts the number of DT2s received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives DT2.
Point

Sent
Description This counter counts the number of DT2s sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends DT2.
Point
CONNECTREQ Sent
Description This counter counts the number of sending CONNECTREQ to SCCP.
Measurement The counter accumulates when SCCP receives CONNECTREQ.
Point
CONNECTCON Received
Description This counter counts the number of sending CONNECTCON to SCCP.

Measurement This counter accumulates when SCCP receives CONNECTCON.

Point
CONNECTIND Received
Description This counter counts the number of sending CONNECTRES to SCCP.
Measurement The counter accumulates when SCCP receives CONNECTRES.
Point
CONNECTRES Sent
Description This counter counts the number of sending CONNECTRES to SCCP.
Measurement The counter accumulates when SCCP receives CONNECTRES.
Point
DISCONNECTREQ Sent
Description This counter counts the number of sending DISCONNECTREQ to
SCCP.
Measurement The counter accumulates when SCCP receives DISCONNECTREQ.
Point
DISCONNECTIND received
Description This counter counts the number of DISCONNECTINDs received
from SCCP.
Measurement This counter accumulates when DISCONNECTIND is received from
Point SCCP.

C901690034 Number of CR
Sent
Description This counter counts the number of CRs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends CR.
Point
Received
Description This counter counts the number of CRs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives CR.
Point
C901690036 Number of CC
Sent
Description This counter counts the number of CCs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends CC.
Point
C901690037 Number of CC
Received
Description This counter counts the number of CCs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives CC.
Point
UDT gtt
Description This counter counts the number of UDT GT translations.

Measurement The counter when uplink/downlink UDT GT translation is per-

Point formed.
UDTS gtt
Description This counter counts the number of UDTS GT translations.
Measurement The counter when uplink/downlink UDTS GT translation is per-
Point formed.
XUDT gtt
Description This counter counts the number of XUDT GT translations.
Measurement The counter when uplink/downlink XUDT GT translation is per-
Point formed.
XUDTS gtt
Description This counter counts the number of XUDTS GT translations.
Measurement The counter when uplink/downlink XUDTS GT translation is per-
Point formed.
LUDT gtt
Description This counter counts the number of LUDT GT translations.
Measurement The counter when uplink/downlink LUDT GT translation is per-
Point formed.

LUDTS gtt
Description This counter counts the number of LUDTS GT translations.
Measurement The counter when uplink/downlink LUDTS GT translation is per-
Point formed.
UDT gtt failure
Description This counter counts the number of UDT GT translation failures.
Measurement The counter counts when uplink/downlink UDT GT translation fails.
Point
Unit Times
UDTS gtt failure
Description This counter counts the number of UDTS GT translation failures.
Measurement The counter counts when uplink/downlink UDTS GT translation
Point fails.
Unit Times
XUDT gtt failure
Description This counter counts the number of XUDT GT translation failures.
Measurement The counter counts when uplink/downlink XUDT GT translation
Point fails.

XUDTS gtt failure
Description This counter counts the number of XUDTS GT translation failures.
Measurement The counter counts when uplink/downlink XUDTS GT translation
Point fails.
Unit Times
LUDT gtt failure
Description This counter counts the number of LUDT GT translation failures.
Measurement The counter counts when uplink/downlink LUDT GT translation
Point fails.
Unit Times
LUDTS gtt failure
Description This counter counts the number of LUDTS GT translation failures.
Measurement The counter counts when uplink/downlink LUDTS GT translation
Point fails.
Unit Times
gtt
Description This counter counts the number of CR GT translations.
Measurement The counter when uplink/downlink CR GT translation is performed.
Point
Unit Times

gtt failure
Description This counter counts the number of CR GT translation failures.
Measurement The counter counts when uplink/downlink CR GT translation fails.
Point
Unit Times
C901690052 Number of gtt

Count
Description This counter counts the number of GT translations.
Measurement The counter counts when GT translation is performed.
Point
C901690053 Number of gtt

failure
Description This counter counts the number of GT translation failures.
Measurement The counter counts when GT translation fails.
Point
Unit 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 The counter counts when the GT translation of downlink N_Unit-
Point DataReq long user message fails.
Unit Times

UPU received
Description This counter counts the number of UPUs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives UPU.
Point
SSA received
Description This counter counts the number of SSAs received by SCCP of the
local office.
Measurement The counter accumulates when SCCP receives SSA.
Point
SSA sent
Description This counter counts the number of SSAs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends SSA.
Point
SST received
Description This counter counts the number of SSTs received by SCCP of the
local office.

Measurement The counter accumulates when SCCP receives SST.

Point
SST sent
Description This counter counts the number of SSTs sent by SCCP of the local
office.
Measurement The counter accumulates when SCCP sends SST.
Point


Chapter 76
MTP3 Signaling Link Set

Statistics
Table of Contents
Overview...................................................................... 2713
C901700001 Duration of Signaling Link Set Out of Ser-
vice ............................................................................. 2713
C901700002 Times of Signaling Link Set Out of Ser-
vice ............................................................................. 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 upper-
layer users. This meaurement takes link set as the unit. It per-
forms 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 When the signaling link set's status changes from at least one link
Point being available to all links being unavailable, the counter incre-
ments.
Unit Times

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 During a measurement period, the counter starts counting when
Point 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 This counter counts the number of available signaling links in the
Point signaling link set, including the signaling link currently being used.
C901700004 Linkset type

Description 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

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 The counter accumulates when an Error message with the error
Point code of "Invalid Version" is sent outwards from the local office.
C901710002 Unsupported
Message Class(T)
the local office, with the error code of "Unsupported Message
Class".
Point code of "Unsupported Message Class" is sent outwards from the
local office.

Chapter 77 M3UA Error Statistics
Message Type(T)
the local office, with the error code of "Unsupported Message
Type".
Point code of "Unsupported Message Type" is sent outwards from the
local office.
C901710004 Unexpected
Message(T)
the local office, with the error code of "Unexpected Message".
Point code of "Unexpected Message" is sent outwards from the local of-
fice.
Traffic Mode Type(T)
the local office, with the error code of "Unsupported Traffic Mode".
Point code of "Unsupported Traffic Mode" is sent outwards from the local
office.
C901710006 Invalid Routing

Context(T)
the local office, with the error code of "Invalid Routing Context".
Point code of "Invalid Routing Context" is sent outwards from the local
office.

C901710007 Protocol
Error(T)
the local office, with the error code of "Protocol Error".
Point code of "Protocol Error" is sent outwards from the local office.
C901710008 Invalid
Message Type(T)
Description This counter counts the number of invalid message types sent. It
is same as the counter "Unsupported Message Type(T)".
Measurement The counter counts when the message type sent is invalid.
Point
error message sent
Description This counter counts the number of error messages sent outwards
from the local office.
Measurement The counter accumulates when the error message is sent outwards
Point from the local office.
C901710010 Invalid
Version(R)
Description This counter counts when an Error message is received, with the
error code of "Invalid Version".
Point code of "Invalid Version" is received.

Message Class(R)
error code of "Unsupported Message Class".
Point code of "Unsupported Message Class" is received.
Message Type(R)
error code of "Unsupported Message Type".
Point code of "Unsupported Message Type" is received.
C901710013 Unexpected
Message(R)
error code of "Unexpected Message".
Point code of "Unexpected Message" is received.
Traffic Mode Type(R)
error code of "Unsupported Traffic Mode".
Point code of "Unsupported Traffic Mode" is received.

C901710015 Invalid Routing

Context(R)
error code of "Invalid Routing Context".
Measurement The counter accumulates when an invalid routing context message
Point is received.
C901710016 Protocol
Error(R)
error code of "Protocol Error".
Point code of "Protocol Error" is received.
C901710017 Invalid
Message Type(R)
Description This counter counts the number of invalid message types received.
It is same as the counter "Unsupported Message Type(R)".
Measurement The counter counts when the message type received is invalid.
Point
error message received
Description This counter counts the number of error messages received.
Measurement The counter accumulates when the error message is received.
Point
Unit Times

C901710019 Unknown
Remote User
Description This counter counts when a DUPU message is received, with the
indication of "Unknown".
Measurement The counter accumulates when a DUPU message with the indica-
Point tion of "Unknown" is received.
C901710020 Unequipped
Remote User
indication of "Unequipped Remote User".
Point tion of "Unequipped Remote User" is received.
C901710021 Inaccessible
Remote User
indication of "Inaccessible Remote User".
Point tion of "Inaccessible Remote User" is received.
DUPU message received
Description This counter counts the number of DUPU messages received.
Measurement The counter accumulates when the DUPU message is received.
Point
Unit Times

C901710023 Invalid Net

APPEARANCE(T)
the local office, with the error code of "Invalid Network Appear-
ance".
Point code of "Invalid Network Appearance" is sent outwards from the
local office.
C901710024 Invalid Net

APPEARANCE(R)
error code of "Invalid Network Appearance".
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 indi-
cation of "Unknown".
Point tion of "Unknown" is sent.
Unit Times

C901710026 Number
of DUPU message sent
which cause is Unequipped
Remote User
cation of "Unequipped Remote User".
Point tion of "Unequipped Remote User" is sent.
Unit Times
DUPU message sent which
cause is Inaccessible
Remote User
cation of "Inaccessible Remote User".
Point tion of "Inaccessible Remote User" is sent.
Unit Times
DUPU message sent
Description This counter counts the number of DUPU messages sent.
Measurement The counter accumulates when the DUPU message is sent.
Point
Unit Times

by license
warded outwards from the local office and is directly discarded.
The condition is reported to OAM and the counter accumulates.
C901710030 Sending invalid

stream ID
the local office, with the error code of "Invalid Stream ID".
Point code of "Invalid Stream ID" is sent outwards from the local office.
C901710031 Sending refuse

error, reason is management
blocking
the local office, with the error code of "Management Blocking Re-
jection".
Point code of "Management Blocking Rejection" is sent outwards from
the local office.

C901710032 Sending
required ASP ID
the local office, with the error code of "ASP ID Required".
Point code of "ASP ID Required" is sent outwards from the local office.

ASP ID
the local office, with the error code of "Invalid ASP ID".
Point code of "Invalid ASP ID" is sent outwards from the local office.

parameter value
the local office, with the error code of "Invalid Parameter Value".
Point code of "Invalid Parameter Value" is sent outwards from the local
office.
C901710035 Sending
parameter field error
the local office, with the error code of "Parameter Field Error".
Point code of "Parameter Field Error" is sent outwards from the local
office.

C901710036 Sending
unexpected parameter error
the local office, with the error code of "Unexpected Parameter".
Point code of "Unexpected Parameter" is sent outwards from the local
office.
C901710037 Sending
destination status unknown
the local office, with the error code of "Destination Status Un-
known".
Point code of "Destination Status Unknown" is sent outwards from the
local office.
C901710038 Sending
missing parameter error
the local office, with the error code of "Missing Parameter Error".
Point code of "Missing Parameter Error" is sent outwards from the local
office.
C901710039 Sending no
configured AS for ASP
the local office, with the error code of "AS not configured with the
ASP".
Point code of "AS not configured with the ASP" is sent outwards from
the local office.

C901710040 Receiving
invalid stream ID
error code of "Invalid Stream ID".
Point code of "Invalid Stream ID" is received.
refuse error, reason is
management blocking
error code of "Management Blocking Rejection".
Point code of "Management Blocking Rejection" is received.
required ASP ID
error code of "ASP ID Required".
Point code of "ASP ID Required" is received.
invalid ASP ID
error code of "Invalid ASP ID".
Point code of "Invalid ASP ID" is received.

invalid parameter value
error code of "Invalid Parameter Value".
Point code of "Invalid Parameter Value" is received.
parameter field error
error code of "Parameter Field Error".
Point code of "Parameter Field Error" is received.
unexpected parameter error
error code of "Unexpected Parameter".
Point code of "Unexpected Parameter" is received.
destination status unknown
error code of "Destination Status Unknown".
Point code of "Destination Status Unknown" is received.

missing parameter error
error code of "Missing Parameter Error".
Point code of "Missing Parameter Error" is received.
C901710049 Receiving no
configured AS for ASP
error code of "AS not configured with the ASP".
Point code of "AS not configured with the ASP" is received.


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 opera-
tions of peer-layer MTP3 user protocols, and MTP3 nework man-
agement 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 per-
forms measurement of the number of messages between M3UA
and upper-layer users and the number of bytes of messages be-
tween 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 The counter counts when M3UA sends the upper-layer user mes-
Point sage.
Unit Times

C901720002 Bytes of
service message transmitted
Description This counter counts the number of bytes of upper-layer user mes-
sages sent by AS of M3UA.
Measurement The counter counts when M3UA sends the upper-layer user mes-
Point sage.
Unit Byte
service message received
Description This counter counts the number of upper-layer user messages re-
ceived by AS of M3UA.
Measurement The counter counts when M3UA receives the upper-layer user mes-
Point sage from SCTP.
Unit Times
C901720004 Bytes of
service message received
Description This counter counts the number of bytes of upper-layer user mes-
sages received by AS of M3UA.
Measurement The counter counts when M3UA receives the upper-layer user mes-
Point sage from SCTP.
Unit 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 informa-
tion: total number of timers, number of available timers, peak
value of the timer, number of successes in setting timer, and num-
ber of failures in setting timer.
Timer resource refers to the memory block resource allocated ac-
cording 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 in-
creases. 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.

Measurement The counter's value is fixed, depending on the configuration.

Point
available timer
Description This counter counts the number of available timers.
Measurement The counter counts when a timer control block is released success-
Point fully.
C901730003 Peak value of

timer
Description This counter records the peak value of timer usage.
Measurement The counter counts when the timer usage exceeds the current peak
Point value.
success to set timer
Description This counter counts the number of successes in setting timer.
Measurement The counter counts when the timer is set successfully.
Point
Unit Times
failure to set timer
Description This counter counts the number of failures in setting timer.
Measurement The counter counts when the timer setting fails.
Point
Unit 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 run-
ning, 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 This counter counts the total number of active processes.
Measurement The measurement point is determined during process creation and
Point is not changed during the operation.

process
Description This counter counts the total number of processes.
Measurement The measurement point is configured in the configuration file.
Point
process scheduled
Description This counter counts the total number of scheduled processes.
Measurement This counter increments when a process is scheduled. It counts
Point 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, in-
cluding 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.

Measurement The measurement point is configured and unchanged.

Point
C901750002 Size of UB
Description This counter counts the size of the UBs in a UB set.
Measurement The measurement point is configured and unchanged.
Point
C901750003 Number of UB
Description This counter counts the number of UBs in the UB pool set.
Measurement The measurement point is related to current UB usage status and
Point may dynamically change with the addition or reduction of switch-
ing blocks.
C901750004 Number of UB
used
Description This counter counts the number of used UBs.
Measurement The measurement point is related to the current UB usage status.
Point

Chapter 82
Hard Disk and FLASH

Performance Statistics
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 re-
maining space is insufficient, the upper application of those requir-
ing storage is affected. Therefore, it is necessary to take real-time
statistics on disk space so that user can know the disk usage situa-
tion timely. Disk space performance statistics refer to the statistics
on remaining space and total space of disks on a board. The key-
word 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 The measurement point is related to the disk configuration on the
Point current board.
C901760002 Total space

Description This counter counts the total space.
Measurement The measurement point is unchanged.
Point
Unit KB

C901760003 Free space

Description This counter counts the free space.
Measurement The disk space occupation changes each time a file is added, mod-
Point ified, or deleted.
Unit 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 Re-
ceived.......................................................................... 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 associa-
tion 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
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 mea-
surement 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 lo-
cal SCTP transceiving errors. This chapter describes the mean-
ings, usages, and measurement points of SCTP stack measure-
ment counters.
Association Accepted
Description This counter counts the number of associations passively estab-
lished.
Measurement When an association is accepted, this counter counts.
Point
Association Initiated
Description This counter counts the number of initiated associations.
Measurement When an association is actively initiated, this counter counts.
Point
Association Shutdown
Description This counter counts the number of shutdown associations.

Chapter 83 SCTP Protocol Statistics
Measurement When an association is shut down, this counter counts.

Point
Association Abort
Description This counter counts the number of aborted associations.
Measurement When an association is aborted, this counter counts.
Point
Chunk Retransmitted
Description This counter counts the times of chunk retransmission.
Measurement When a chunks is retransmitted, this counter counts.
Point
Unordered Chunk Sent
Description This counter counts the number of sent unordered chunks.
Measurement When an unordered chunk is sent, this counter counts.
Point
Unordered Chunk Received
Description This counter counts the number of received unordered chunks.
Measurement When an unordered chunk is received, this counter counts.
Point
Chunk Sent
Description This counter counts the number of sent chunks.

Measurement When a chunk is sent, this counter counts.

Point
Chunk Received
Description This counter counts the number of received chunks.
Measurement When a chunk is received, this counter counts.
Point
C901770010 Number of Init

Sent
Description This counter counts the number of sent INIT chunks.
Measurement When an INIT chunk is sent, this counter counts.
Point

Received
Description This counter counts the number of received INIT chunks.
Measurement When an INIT chunk is received, this counter counts.
Point

Ack Sent
Description This counter counts the number of sent INITACK chunks.
Measurement When an INITACK chunks is sent, this counter counts.
Point

Ack Received
Description This counter counts the number of received INITACK chunks.

Measurement When an INITACK chunk is received, this counter counts.

Point
COOKIE Sent
Description This counter counts the number of sent COOKIE chunks.
Measurement When a COOKIE chunk is sent, this counter counts.
Point
Cookie Received
Description This counter counts the number of received COOKIE chunks.
Measurement When a COOKIE chunk is received, this counter counts.
Point
Cookie Ack Sent
Description This counter counts the number of sent COOKIE ACK chunks.
Measurement When a COOKIE ACK chunk is sent, this counter counts.
Point
Cookie Ack Received
Description This counter counts the number of received COOKIE ACK chunks.
Measurement When a COOKIE ACK chunk is received, this counter counts.
Point
Heartbeat Sent
Description This counter counts the number of sent heartbeat chunks.

Measurement When a HEARTBEAT chunk is sent, this counter counts.

Point
Heartbeat Received
Description This counter counts the number of received heartbeats.
Measurement When a HEARTBEAT chunk is received, this counter counts.
Point
Heartbeat Ack Sent
Description This counter counts the number of sent heartbeat acknowledge-
ment chunks.
Measurement When a HEARTBEAT ACK chunk is sent, this counter counts.
Point
Heartbeat Ack Received
Description This counter counts the number of sent heartbeat acknowledge-
ment chunks.
Measurement When a HEARTBEAT ACK chunk is sent, this counter counts.
Point
Abort Chunk Sent
Description This counter counts the number of sent ABORT chunks.

Measurement When an ABORT chunk is sent, this counter counts.

Point
Abort Chunk Received
Description This counter counts the number of received ABORT chunks.
Measurement When an ABORT chunk is received, this counter counts.
Point
Shutdown Chunk Sent
Description This counter counts the number of sent SHUTDOWN chunks.
Measurement When a SHUTDOWN chunk is sent, this counter counts.
Point
Shutdown Chunk Received
Description This counter counts the number of received SHUTDOWN chunks.
Measurement When a SHUTDOWN chunk is received, this counter counts.
Point
Shutdown Ack Chunk Sent
Description This counter counts the number of sent SHUTDOWN ACK chunks.

Measurement When a SHUTDOWN ACK chunk is sent, this counter counts.

Point
Shutdown Ack Chunk
Received
Description This counter counts the number of received SHUTDOWN ACK
chunks.
Measurement When a SHUTDOWN ACK chunk is received, this counter counts.
Point
Shutdown Complete Sent
Description This counter counts the number of sent SHUTDOWN COMPLETE
chunks.
Measurement When a SHUTDOWN COMPLETE chunk is sent, this counter counts.
Point
C901770029 Number
of Shutdown Complete
Received
Description This counter counts the number of received SHUTDOWN COM-
PLETE chunks.
Measurement When a SHUTDOWN COMPLETE chunk is received, this counter
Point counts.
Error Chunk Sent
Description This counter counts the number of sent ERROR chunks.

Measurement When an ERROR chunk is sent, this counter counts.

Point
Error Chunk Received
Description This counter counts the number of received ERROR chunks.
Measurement When an ERROR chunk is received, this counter counts.
Point
ECNE Chunk Sent
Description This counter counts the number of sent ECNE chunks. As the im-
plementation at bottom layer is not supported, the statistics are
invalid.
Measurement When an ECNE chunk is sent, this counter counts.
Point
ECNE Chunk Received
Description This counter counts the number of sent ECNE chunks. As the im-
invalid.
Measurement When an ECNE chunk is sent, this counter counts.
Point
CWR Chunk Sent
Description This counter counts the number of sent CWR chunks. As the im-
invalid.

Measurement When a CWR chunk is sent, this counter counts.

Point
CWR Chunk Received
Description This counter counts the number of received CWR chunks. As the
implementation in bottom layer is not supported, the statistics are
invalid.
Measurement When a CWR chunk is received, this counter counts.
Point
Error Packet Received
Description This counter counts the number of received Error packets.
Measurement When an Error packet is received, this counter counts.
Point
OOTB Chunk Received
Description This counter counts the number of received OOTB chunks.
Measurement When an OOTB chunk is received, this counter counts.
Point
ULP Sent Chunk Request in
association alive
Description This counter counts the number of chunk requests sent by ULP
when association is alive.
Measurement When ULP initiates chunk requests when association is alive, this
Point 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 Each time there is a successful chunk request sent by ULP when
Point association is alive, this counter counts.
ULP Sent Chunk Request
during a little time
Description This counter counts the number of chunk requests sent by ULP. As
the implementation at bottom layer is not supported, the statistics
are invalid.
Measurement When ULP sends a chunk request, this counter counts.
Point
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 sup-
ported, the statistics are invalid.
Measurement When a chunk request sent by ULP to SCTP is successful, this

SCTP Sent Chunk Request
to ULP
Description 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.
Measurement When SCTP sends chunk requests to ULP, this counter counts.
Point
Abort Request from ULP
Description This counter counts the number of ABORT requests from ULP. As
the implementation at lower layer is not supported, the statistics
are invalid.
Measurement When ULP sends an ABORT request to SCTP, this counter counts.
Point
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 When SCTP receives an ABORT message from the peer end, this
C901770045 Number of Link

Break for Retransfer
Description This counter counts the number of link disconnections due to re-
transfer.
Measurement When a link is broken due to retransmission, this counter counts.
Point

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 sta-
tus 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 mean-
ings, 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.

Measurement None
Point
C901780002 Send
synchronous Msg to ULP fail
Description This counter counts the number of unsuccessful synchronization
message sent to ULP.
Measurement When synchronization messages are sent to ULP, this counter
Point counts.
C901780003 ULPID from

ULP invalid
Description This counter counts the number of invalid ULPIDs returned by ULP.
Measurement When ULP returns ULPID, this counter counts.
Point
Association Initiated to ULP
Description This counter counts the number of associations initiated to ULP.
Measurement When association is actively established and Cookie ACK is re-
Point ceived, this counter increments.
Association Accepted to
ULP
Description This counter counts the number of passively established associa-
tions reported to ULP.
Measurement When association is passively established and Cookie Echo is re-
Point ceived, this counter increments.

Chapter 84 SCTP Association Statistics
Association Restarted to
ULP
Description This counter counts the number of restarted associations reported
to ULP.
Measurement When an association is restarted, this counter counts.
Point
Association lost to ULP
Description This counter counts the number of lost associations reported to
ULP.
Measurement When an association is lost, this counter counts.
Point
Destroy instance
Description This counter counts the number of Destroy instance requests sent
by ULP.
Measurement When ULP sends a Destroy instance request, this counter counts.
Point
Shutdown request from ULP
Description This counter counts the number of association shutdown requests
sent by ULP.

Measurement When ULP sends a SHUTDOWN message, this counter counts.

Point
Abort request from ULP
Description This counter counts the number of association abort requests sent
by ULP.
Measurement When ULP sends an ABORT message, this counter counts.
Point

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 Indica-
tion ............................................................................. 2761
C901790010 VC-4 Remote Error Indication (High-order path
1)................................................................................ 2761
2)................................................................................ 2762
3)................................................................................ 2762
C901790013 Multiplex Section Remote Background Block Er-
ror Ratio....................................................................... 2762
C901790014 Multiplex Section Remote Errored Second Ra-
tio ............................................................................... 2763
C901790015 Multiplex Section Remote Errored Sec-
ond ............................................................................. 2763
C901790016 Multiplex Section Remote Severely Errored Sec-
ond ............................................................................. 2763
C901790017 Multiplex Section Remote Unavailable Sec-
ond ............................................................................. 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


3)................................................................................ 2767
C901790027 VC-4 Remote Severely Errored Second (High-
order path 1) ................................................................ 2767
order path 2) ................................................................ 2768
order path 3) ................................................................ 2768
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 Sec-
ond ............................................................................. 2770
C901790036 B1(Regenerator Section) BIP-8 Severely Errored
Second ........................................................................ 2771
C901790037 B1(Regenerator Section) BIP-8 Unavailable Sec-
ond ............................................................................. 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 Sec-
ond ............................................................................. 2772
C901790041 B2(Multiplex Section) BIP-24 Severely Errored
Second ........................................................................ 2773
C901790042 B2(Multiplex Section) BIP-24 Unavailable Sec-
ond ............................................................................. 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-or-
der path 1) ................................................................... 2775
der path 2) ................................................................... 2775
der path 3) ................................................................... 2775
path 1) ........................................................................ 2776
path 2) ........................................................................ 2776
path 3) ........................................................................ 2776
C901790052 B3(VC-4) BIP-8 Severely Errored Second (High-
order path 1) ................................................................ 2777
order path 2) ................................................................ 2777
order path 3) ................................................................ 2777
C901790055 B3(VC-4) BIP-8 Unavailable Second (High-order
path 1) ........................................................................ 2778

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 sta-
tistics 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 sec-
tion and channel in SDH transport network. This chapter describes
the main performance statistic items, statistic method, and stan-
dard 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 pro-
vides 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 C901790003 SDH Type
Description SDH has the following types: AU-4, AU-3, and STS-3SDH.

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 When the received B1 byte is verified to be inconsistent with the
Point 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 When the received three B2 bytes are verified to be inconsistent
Point 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 When the received B3 byte received by high-order path 1 is verified
Point 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 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 This counter is similar to dwB3E1. It corresponds to high-order

Point path 2.
C901790008 VC-4 BIP-8

Description This counter is similar to dwB3E2. It corresponds to high-order
path 3.
Measurement This counter is similar to dwB3E2. It corresponds to high-order
Point path 3.
Section Remote Error
Indication
Description When peer end device detects BIP-24 error according to the re-
ceived three B2 bytes, it uses regenerator section overhead byte
M1 to send the check result to the local end as Multiplex Sec-
tion-Remote Error Indication (MS-REI).
Measurement Because at most 24 bit errors can be found, the value range of M1
Point 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)
ceived 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 Indi-
cation (VC4-REI). When SDH type is AU-4, AU-3, and STS-3, the
corresponding high-order path is 1.
Measurement Because at most eight bit errors can be found, the value range of
Point VC4-REI is 0 ~ 8. If VC4-REI is not 0, it indicates that a remote
error block exists. In this case, dwVC4REI1 increments.


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 This counter is similar to dwVC4REI1. It corresponds to high-order
Point path 2.

path 3)
Description This counter is similar to dwVC4REI2. It corresponds to high-order
path 3.
Measurement This counter is similar to dwVC4REI2. It corresponds to high-order
Point path 3.
Section Remote Background
Block Error Ratio
tion-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 be-
tween 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).
exists. Multiplex Section-Remote Error Indication counter dwM-
SREI increments. SDTB periodically queries this counter, which
can serve as reference for the calculation of dwMSFEBBE.

Section Remote Errored
Second Ratio
tion-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).
can serve as reference for the calculation of dwMSFEER.
Section Remote Errored
Second
tion-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).
can serve as reference for the calculation of dwMSFEES.
Section Remote Severely
Errored Second
tion-Remote Error Indication (MS-REI). When one second con-

tains no less than 30% error blocks or at least one deficiency, it is

deemed as SES.
can serve as reference for the calculation of dwMSFESES.
Section Remote Unavailable
Second
tion-Remote Error Indication (MS-REI). When SES is detected for
continuous 10 seconds, UAS starts (UAS includes these 10 sec-
onds). When no SES is detected for continuous 10 seconds, UAS
ends (UAD excludes these 10 seconds).
can serve as reference for the calculation of dwMSFEUAS.

Background Block Error
Ratio (High-order path 1)
cation (VC4-REI). Background block error (BBE) refers to the error
blocks after deducting the unusable time and the error blocks ap-
pearing 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 cor-
responding high-order path is 1.
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 dwVC4FEB-

BER1.

Description This counter is similar to dwVC4FEBBER1. It corresponds to high-
order 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 This counter is similar to dwVC4FEBBER1. It corresponds to high-
Point order path 2.

Description This counter is similar to dwVC4FEBBER2. It corresponds to high-
order path 3.
Measurement This counter is similar to dwVC4FEBBER2. It corresponds to high-
Point order path 3.

Errored Second Ratio
(High-order path 1)
the check result to the local end as VC-4 path-Remote Error In-
dication (VC4-REI). The ratio between the ES within a specified
period of measurement time and the total time used is called er-
ror code second ratio (ESR). When SDH type is AU-4, AU-3, and
STS-3, the corresponding high-order path is 1.


which can serve as reference for the calculation of dwVC4FEER1.

(High-order path 2)
Description This counter is similar to dwVC4FEER1. It corresponds to high-
order 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 This counter is similar to dwVC4FEER1. It corresponds to high-
Point order path 2.

(High-order path 3)
Description This counter is similar to dwVC4FEER2. It corresponds to high-
order path 3.
Measurement This counter is similar to dwVC4FEER2. It corresponds to high-
Point order path 3.

Errored Second (High-order
path 1)
cation (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.


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 This counter is similar to dwVC4FEES1. It corresponds to high-
Point order path 2.

path 3)
Description This counter is similar to dwVC4FEES2. It corresponds to high-
order path 3.
Measurement This counter is similar to dwVC4FEES2. It corresponds to high-
Point order path 3.

Severely Errored Second
(High-order path 1)
the check result to the local end as VC-4 path-Remote Error In-
dication (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.


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 This counter is similar to dwVC4FESES1. It corresponds to high-
Point order path 2.

(High-order path 3)
Description This counter is similar to dwVC4FESES2. It corresponds to high-
order path 3.
Measurement This counter is similar to dwVC4FESES2. It corresponds to high-
Point order path 3.

Unavailable Second
(High-order path 1)
the check result to the local end as VC-4 path-Remote Error Indica-
tion (VC4-REI). When SES is detected for continuous 10 seconds,
UAS starts (UAS includes these 10 seconds). When no SES is de-
tected for continuous 10 seconds, UAS ends (UAD excludes these
10 seconds). When SDH type is AU-4, AU-3, and STS-3, the cor-


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 This counter is similar to dwVC4FEUAS1. It corresponds to high-
Point order path 2.

Unavailable Second
(High-order path 3)
Description This counter is similar to dwVC4FEUAS2. It corresponds to high-
order path 3.
Measurement This counter is similar to dwVC4FEUAS2. It corresponds to high-
Point order path 3.
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


frame at local end, the block is assumed to have error. Genera-
tor section BIP code counter dwB1E increments. SDTB periodically
queries this counter, which can serve as reference for the calcula-
tion of dwB1BBER.
C901790034 B1(Regenera
tor Section) BIP-8 Errored
Second Ratio
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).
Point result of BIP-8 check of regenerator section of previous STM-1
tion of dwB1ER.
tor Section) BIP-8 Errored
Second
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).
tion 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.
tion of dwB1SES.
C901790037 B1(Rege
nerator Section) BIP-8
Unavailable Second
monitor bit errors of regeneration section. When SES is detected
for continuous 10 seconds, UAS starts (UAS includes these 10 sec-
onds). When no SES is detected for continuous 10 seconds, UAS
ends (UAD excludes these 10 seconds).
tion of dwB1UAS
C901790038 B2(Multiplex
Section) BIP-24 Background
Block Error Ratio
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

STM-1 frame at local end, the block is assumed to have error.
Muliplex section BIP code counter dwB2E increments. SDTB peri-
odically queries this counter, which can serve as reference for the
calculation of dwB2BBER.
Section) BIP-24 Errored
Second Ratio
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).
calculation of dwB2ER.
Section) BIP-24 Errored
Second
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).
calculation of dwB2ES.

Section) BIP-24 Severely
Errored Second
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.
calculation of dwB2SES.
Section) BIP-24 Unavailable
Second
code to monitor bit errors of multiplex section. When SES is de-
tected 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).
Point with the result of BIP-24 check for the multiplex section of previ-
ous 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)
VC-4 path. 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 When the B3 byte received by high-order path 1 is verified to be
Point inconsistent with the result of BIP-8 check for VC-4 block of previ-
VC-4 path BIP code counter dwB3E increments. SDTB periodically
tion of dwB3BBER1.
C901790044 B3(VC-4)
2)
Description This counter is similar to dwB3BBER1. When SDH type is AU-4, it
Measurement This counter is similar to dwB3BBER1. It corresponds to high-order
Point path 2.
C901790045 B3(VC-4)
3)
Description This counter is similar to dwB3BBER2. It corresponds to high-order
path 3.
Measurement This counter is similar to dwB3BBER2. It corresponds to high-order
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.
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 refer-
ence 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 This counter is similar to dwB3ER1. It corresponds to high-order
Point path 2.
C901790048 B3(VC-4)
(High-order path 3)
Description This counter is similar to dwB3ER2. It corresponds to high-order
path 3.
Measurement This counter is similar to dwB3ER2. It corresponds to high-order
Point path 3.

C901790049 B3(VC-4)
BIP-8 Errored Second
(High-order path 1)
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.
error. VC-4 path BIP code counter dwB3E increments. SDTB peri-
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 This counter is similar to dwB3ES1. It corresponds to high-order
Point path 2.
C901790051 B3(VC-4)
(High-order path 3)
Description This counter is similar to dwB3ES2. It corresponds to high-order
path 3.
Measurement This counter is similar to dwB3ES2. It corresponds to high-order
Point path 3.

C901790052 B3(VC-4)
BIP-8 Severely Errored
Second (High-order path 1)
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.
error. VC-4 path BIP code counter dwB3E increments. SDTB peri-
calculation of dwB3SES1.
C901790053 B3(VC-4)
Description This counter is similar to dwB3SES1. When SDH type is AU-4, it
Measurement This counter is similar to dwB3SES1. It corresponds to high-order
Point path 2.
C901790054 B3(VC-4)
Description This counter is similar to dwB3SES2. It corresponds to high-order
path 3.
Measurement This counter is similar to dwB3SES2. It corresponds to high-order
Point path 3.

C901790055 B3(VC-4)
BIP-8 Unavailable Second
(High-order path 1)
of VC-4 path. When SES is detected for continuous 10 seconds,
UAS starts (UAS includes these 10 seconds). When no SES is de-
tected for continuous 10 seconds, UAS ends (UAD excludes these
10 seconds). When SDH type is AU-4, AU-3, and STS-3, the cor-
Point inconsistent with the result of BIP-8 check for VC-4 block of previ-
VC-4 path BIP code counter dwB3E increments. SDTB periodically
tion 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 This counter is similar to dwB3UAS1. It corresponds to high-order
Point path 2.
C901790057 B3(VC-4)
(High-order path 3)
Description This counter is similar to dwB3UAS2. It corresponds to high-order
path 3.
Measurement This counter is similar to dwB3UAS2. It corresponds to high-order
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 This counter counts when LOF occurs and does not stop until LOF
Point restores.


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-thou-
sandth) ........................................................................ 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-thou-
sandth) ........................................................................ 2787
C901800022 far end Errored Second rate(One ten-thou-
sandth) ........................................................................ 2788
C901800023 far end Severely Errored Second rate(One ten-
thousandth).................................................................. 2788
C901800024 far end Background Block Error rate(One ten-
thousandth).................................................................. 2788
Overview
The statistic task of PEB22554 module E1 performance collects the
statistics on the number of error codes generated in receiving sig-
nals of PEB22554 module during transmission on different network
links. It is used to represent the data transmission performance of

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 sys-
tem 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 receiv-
ing 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 This counter counts the duration of code slip during detection pe-
riod. Code slip occurs when receiving clock and transmitting clock
are insynchronous.
Measurement This counter counts the duration of code slip.
Point
Unit Second
C901800003 Near end

available Second
Description This counter counts the time available at near end, that is, the
result of excluding UAS from total detection period.
Measurement This counter counts the available seconds at near end.
Point
Unit Second

Chapter 86 PEB22554 E1 Performance Statistics
C901800004 Near end

unavailable Second
Description 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.
Measurement This counter counts the unavailable seconds at near end.
Point
Unit Second
C901800005 Near end

Errored Second
Description 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 incre-
ments.
Measurement This counter counts the errored seconds at near end.
Point
Unit Second
C901800006 Near end

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 When severely errored seconds at near end are detected, this
Unit Second

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 When near end background block error occurs, this counter counts.
Point The basic frame is invalid and thus use 0.
Unit Second
C901800008 Frame
Alignment Signal error
Description This counter counts the number of FAS errors during the specified
period.
Measurement When FAS error is detected, this counter counts.
Point
C901800009 Cyclic
Redundancy Check 4
error
Description This counter counts the number of CRC4 errors during the specified
period.
Measurement When CRC4 error is detected, this counter counts.
Point
C901800010 Bit error

rate(PPM)
Description For details, see the formula under the table.
Measurement This counter counts the number of errored codes.
Point
Unit PPM

C901800011 Near end

unavailable Second
rate(One ten-thousandth)
Measurement When unavailable seconds are detected at near end, this counter
Point counts.
Unit Ten-thousandth
C901800012 Near end

Errored Second rate(One
ten-thousandth)
Measurement When errored seconds are detected at near end, this counter
Point counts.
Unit Ten-thousandth
C901800013 Near end

Unit Ten-thousandth
C901800014 Near end

Background Block Error rate

Measurement When background block error is detected at near end, this counter
Point counts.
C901800015 far end

available Second
Description This counter counts the time available at far end, that is, the result
of excluding UAS from total detection period.
Measurement This counter counts the available seconds at far end.
Point
Unit 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 When unavailable seconds are detected at far end, this counter
Point 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 When errored seconds are detected at far end, this counter counts.
Point
Unit 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 When severely errored seconds are detected at far end, this
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 When far end background block errors are detected, this counter
Point counts.
C901800020 E-Bit ERROR

Description This counter counts the times of sub-frame errors in multi-frame
during the detection period.
Measurement When EBIT error is detected, this counter counts.
Point
Unit Times
C901800021 far end

unavailable Second
Measurement When unavailable seconds are detected at far end, this counter
Point counts.
Unit Ten-thousandth

C901800022 far end

Errored Second rate(One
ten-thousandth)
Measurement When errored seconds are detected at far end, this counter counts.
Point
Unit Ten-thousandth
C901800023 far end

Measurement When severely errored seconds are detected at far end, this
Unit Ten-thousandth
C901800024 far end

Measurement When background block error is detected at far end, this counter
Point counts.
Unit 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 Er-
ror .............................................................................. 2791
C901810008 number of Frame Alignment Signal error......... 2792
C901810009 number of Cyclic Redundancy Check 6 er-
ror .............................................................................. 2792
C901810010 Bit error rate (PPM) ..................................... 2792
ten-thousandth) ............................................................ 2792
C901810012 Near end Errored Second rate (One ten-thou-
sandth) ........................................................................ 2793
C901810013 Near end Severely Errored Second rate(One ten-
thousandth) ................................................................. 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 receiv-
ing signals of PEB22554 module during transmission on different
network links. It is used to represent the data transmission perfor-
mance of T1 signal in various sections and paths of transport net-
work. 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 sys-
tem 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 accor-
dance with ITU-T G.826 standard.

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 This counter counts the duration of code slip during detection pe-
riod. Code slip occurs when receiving clock and transmitting clock
are insynchronous.
Measurement This counter counts the duration of code slip.
Point
Unit Second
C901810003 Near end

available Second
Description This counter counts the time available at near end, that is, the
result of excluding UAS from total detection period.
Measurement This counter counts the available seconds at near end.
Point
C901810004 Near end

unavailable Second
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
Point counts.

Chapter 87 PEB22554 T1 Performance Statistics
C901810005 Near end

Errored Second
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.
Point counts.
C901810006 Near end

AIS, RAI alarm, and FAS (FAS>=26) error when link is available.
For F24 (ESF) with CRC6 format, this counter also counts the num-
ber of CRC-4 error blocks. If there is more than 805 CRC-4 errors
within a second, this counter increments.
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 When near end background block errors are detected, this counter
Point counts.

Frame Alignment Signal
error
Description This counter counts the number of FAS errors during the specified
period.
Measurement When FAS error is detected, this counter counts.
Point
Cyclic Redundancy Check 6
error
Description This counter counts the number of CRC6 errors during the specified
period.
Measurement When CRC6 error is detected, this counter counts.
Point
C901810010 Bit error rate

(PPM)
Description See the formula.
Measurement This counter counts the number of errored codes.
Point
Unit PPM
C901810011 Near end

unavailable Second
Point counts.
Unit Ten-thousandth

Chapter 87 PEB22554 T1 Performance Statistics
C901810012 Near end

Errored Second rate (One
ten-thousandth)
Point counts.
Unit Ten-thousandth
C901810013 Near end

Unit Ten-thousandth
C901810014 Near end

Background Block Error rate
Measurement When background block errors are detected at near end, this


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.

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 mes-
sage's lower 4 bytes' accumulation overflows, the counter incre-
ments.
Usage This counter is used to find out the transceiving data flow at the
port within the measurement period.
Measurement The counter counts when the message is received at the port.
Point
Unit 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.
Measurement The counter counts when the message is received at the port.
Point
Unit 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 in-
crements.
Measurement The counter counts when the message is transmitted at the port.
Point
Unit 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.
Measurement The counter counts when the message is transmitted at the port.
Point
Unit BYTE
C901820005 physical band

width
Description This counter counts the port's physical bandwidth when the statis-
tic 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 (mean-
ingless in this case).
Measurement The counter counts when the data is reported.
Point
Unit 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 pe-
riod * 8
Usage This counter is used to find out the average receiving rate at the
port.
Measurement The counter's value is calculated when the data is reported.
Point
Unit bit/s

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 mea-
sured 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.
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.
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.
Point
Unit bit/s

Chapter 88 MAC Port Flow Statistics
packets discarded at RX
side (high 4 bytes)
Description This counter counts the number of packets discarded at the re-
ceiving end (higher 4 bytes).
Measurement The counter counts when the discarded packet is received at the
Point port.
packets discarded at RX
side (low 4 bytes)
Description This counter counts the number of packets discarded at the re-
ceiving end (lower 4 bytes).
Measurement The counter counts when the discarded packet is received at the
Point port.
packets discarded at TX side
(high 4 bytes)
Description This counter counts the number of packets discarded at the trans-
mitting end (higher 4 bytes).
Measurement The counter counts when the discarded packet is transmitted at
Point the port.

packets discarded at TX side
(low 4 bytes)
Description This counter counts the number of packets discarded at the trans-
mitting end (lower 4 bytes).
Measurement The counter counts when the discarded packet is transmitted at
Point the port.
packets received when
receiving bit rate is max
during performance period
Description This counter counts the number of packets received at the peak
rate of the port.
Measurement Sampling is performed every second. Compare the receiving rate
Point with the peak rate, and the number of received packets of corre-
sponding measurement points is recorded in the counter.
packets sent when sending
bit rate is max during
performance period
Description This counter counts the number of packets sent at the peak rate
of the port.
Measurement Sampling is performed every second. Compare the sending rate
Point with the peak rate, and the number of sent packets of correspond-
ing 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 up-
link/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.

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.
Point AMR rate statistic data is reported periodically.
Unit Number of frames

Chapter 89 AMR Rate Statistics

DL AFS10.2k frame
rate within 30 s.

DL AFS7.95k frame
rate within 30 s.

DL AFS7.40k frame
rate within 30 s.



DL AFS6.70k frame
rate within 30 s.

DL AFS5.90k frame
rate within 30 s.


DL AFS5.15k frame
rate within 30 s.

DL AFS4.75k frame
rate within 30 s.

DL AHS7.95k frame
k coding rate in downlink in AMR half-rate channel service.
adopt 7.95 k coding rate in AMR half-rate channel service, and the
rate within 30 s.



DL AHS7.40k frame
rate within 30 s.

DL AHS6.70k frame
rate within 30 s.


DL AHS5.90k frame
rate within 30 s.

DL AHS5.15k frame
rate within 30 s.

DL AHS4.75k frame
rate within 30 s.



UL AFS12.2k frame
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.

UL AFS10.2k frame
rate within 30 s.


UL AFS7.95k frame
rate within 30 s.

UL AFS7.40k frame
rate within 30 s.

UL AFS6.70k frame
rate within 30 s.



UL AFS5.90k frame
rate within 30 s.

UL AFS5.15k frame
rate within 30 s.


UL AFS4.75k frame
rate within 30 s.

UL AHS7.95k frame
k coding rate in uplink in AMR half-rate channel service.
rate within 30 s.

UL AHS7.40k frame
rate within 30 s.



UL AHS6.70k frame
rate within 30 s.

UL AHS5.90k frame
rate within 30 s.


UL AHS5.15k frame
rate within 30 s.

UL AHS4.75k frame
rate within 30 s.


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 The received byte count.
Measurement when receiving data.
Point
Unit Byte
C901840002 Received
packet count
Description The received packet count.

Measurement The counter adds one when receiving data.

Point
Unit Piece
C901840003 Received
framing aborts
Description The received framing aborts.
Measurement The counter adds one when receive the broken frame.
Point
Unit Piece
C901840004 Received FCS

errors
Description The received FCS errors.
Measurement The counter adds one when receiving the FCS error occurs.
Point
Unit Piece
C901840005 Received
packets greater than
maximum length
Description The received packets greater than maximum length.
Measurement The counter adds one when receiving jumbo packet.
Point
Unit Piece

Chapter 90 PPP channel measurement
C901840006 Non-octet
aligned frames received
Description The non-octet aligned frames received.
Measurement The counter adds one when receiving non-octet aligned frames.
Point
Unit Piece
C901840007 Received small

datagrams discarded byte
count
Description The received small datagrams discarded byte count.
Measurement when discarding the small packet in RX direction.
Point
Unit Piece
C901840008 Received
jumbo packets byte count
Description The received jumbo packets total length.
Measurement when receiving jumbo packet.
Point
Unit Byte
C901840009 Received small

datagrams discarded event
count
Description The received small datagrams discarded event count.
Measurement The counter adds one when discarding small packet in RX direction.
Point
Unit Piece

C901840010 Received
jumbo packets count
Description The received chunk buffer allocation exceeded event count.
Measurement The counter adds one when receiving the jumbo package.
Point
Unit Piece
C901840011 Transmitted
byte count
Description The transmitted byte count.
Measurement when transmitting data packet.
Point
Unit Byte
C901840012 Transmitted
packet count
Description The transmitted packet count.
Measurement The counter adds one when transmitting data packet.
Point
Unit Piece
C901840013 Transmit
framing aborts
Description The Transmit framing aborts.
Measurement The counter adds one when transmitting frame.
Point
Unit Piece

Chapter 90 PPP channel measurement
C901840014 MLPPP ID
Description ID of the ML-PPP that a PPP belongs to. It is only measured on the
EUIP board.
Measurement The counter is updated when a PPP is configured for an MP.
Point
Unit bps
C901840015 PPP band

width
Description Bandwidth of PPP link.
Measurement When Configuration Ppp-port time slot, , the counter updated to
Point the current value.
Unit bps


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

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

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 pack-
ets, bytes, and incorrect packets on the MAC layer of each link.
Statistic unit in this measurement is link.
C901850001 receive discard

packets flag
Description This counter flags the property of the statistic item.
Usage � 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.

� If BIT4 is set as 1, it indicates that the statistics overflow is

detected, however, it does not guarantee that all overflows are
detected.
Measurement None
Point

packets low 32bits
Description This counter records the lower 32 bits of the statistic item of dis-
carded packet in the receiving direction.
Usage This counter is used to find out the amount of packets discarded
in the receiving direction.
Measurement The counter counts when the packet is received.
Point

packets high 32bits
Description This counter records the higher 32 bits of the statistic item of dis-
carded packet in the receiving direction.
Usage This counter is used to find out the amount of packets discarded
in the receiving direction.
Point

flag
valid.
detected.

Measurement None
Point

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.
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.
Point
C901850007 receive
packets flag
valid.
detected.

Measurement None
Point
C901850008 receive
packets low 32bits
Description This counter records the lower 32 bits of the statistic item of the
number of received packets.
Usage This counter is used to find out the number of packets received.
Point
C901850009 receive
packets high 32bits
Description This counter records the higher 32 bits of the statistic item of the
number of received packets.
Usage This counter is used to find out the number of packets received.
Point
C901850010 receive
broadcast packets flag
valid.
detected.

Measurement None
Point
C901850011 receive
broadcast packets low
32bits
number of received broadcast packets.
Usage This counter is used to find out the number of broadcast packets
received.
Point
C901850012 receive
broadcast packets high
32bits
number of received broadcast packets.
Usage This counter is used to find out the number of broadcast packets
received.
Point
C901850013 receive
multicast packets flag
valid.
detected.

Measurement None
Point
C901850014 receive
multicast packets low 32bits
number of received multicast packets.
Usage This counter is used to find out the number of multicast packets
received.
Point
C901850015 receive
multicast packets high
32bits
number of received multicast packets.
Usage This counter is used to find out the number of multicast packets
received.
Point
C901850016 receive CRC

or align error packets flag
valid.
detected.

Measurement None
Point

or align error packets low
32bits
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.
Point

or align error packets high
32bits
number of received CRC or alignment error packets.
Usage This counter is used to find out the number of received CRC or
Point
C901850019 receive small

than 64 bytes packets flag
valid.
detected.

Measurement None
Point

than 64 bytes packets low
32bits
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.
Point

than 64 bytes packets high
32bits
number of received packets of which the size is smaller than 64
bytes.
which the size is smaller than 64 bytes.
Point
C901850022 receive large

valid.


detected.
Measurement None
Point

32bits
number of received packets of which the size is larger than 1518
bytes.
which the size is larger than 1518 bytes.
Point

than 1518 bytes packets
high 32bits
number of received packets of which the size is larger than 1518
bytes.
which the size is larger than 1518 bytes.
Point
C901850025 The flag of

received fragment packets

valid.
detected.
Measurement None
Point
fragment packets received
(low 32 bit)
number of received fragment packets.
Usage This counter is used to find out the number of received fragment
packets.
Point
received fragment packets
(high 32 bit)
number of received fragment packets.
Usage This counter is used to find out the number of received fragment
packets.
Point
C901850028 receive Jabber

packets flag


valid.
detected.
Measurement None
Point

packets low 32bits
number of received Jabber packets.
Usage This counter is used to find out the number of received Jabber
packets.
Point

packets high 32bits
number of received Jabber packets.
Usage This counter is used to find out the number of received Jabber
packets.
Point
C901850031 receive
Collision count flag
valid.


detected.
Measurement None
Point
C901850032 receive
Collision count low 32bits
number of received collisions.
Usage This counter is used to find out the number of received collisions.
Point
C901850033 receive
Collision count high 32bits
number of received collisions.
Usage This counter is used to find out the number of received collisions.
Point
C901850034 receive 64
bytes packets flag
valid.
detected.

Measurement None
Point
C901850035 receive 64
bytes packets low 32bits
number of received packets of which the size is 64 bytes.
which the size is 64 bytes.
Point
C901850036 receive 64
bytes packets high 32bits
number of received packets of which the size is 64 bytes.
which the size is 64 bytes.
Point
C901850037 receive 65 to
127 bytes packets flag
valid.
detected.

Measurement None
Point
127 bytes packets low 32bits
number of received packets of which the size is between 65 bytes
and 127 bytes.
which the size is between 65 bytes and 127 bytes.
Point
C901850039 receive 65
to 127 bytes packets high
32bits
and 127 bytes.
Point

valid.
detected.

Measurement None
Point

and 255 bytes.
Point
C901850042 receive 128

32bits
and 255 bytes.
Point

valid.
detected.

Measurement None
Point

and 511 bytes.
Point
C901850045 receive 256

32bits
and 511 bytes.
Point

valid.
detected.

Measurement None
Point
C901850047 receive 512

to 1023 bytes packets low
32bits
and 1023 bytes.
Point
C901850048 receive 512

32bits
and 1023 bytes.
Point
C901850049 receive 1024

to 1518 bytes packets flag
valid.


detected.
Measurement None
Point
C901850050 receive 1024

to 1518 bytes packets low
32bits
number of received packets of which the size is between 1024
bytes and 1518 bytes.
Point
C901850051 receive 1024

32bits
number of received packets of which the size is between 1024
bytes and 1518 bytes.
Point
C901850052 send discard

packets flag

valid.
detected.
Measurement None
Point

packets low 32bits
number of transmitted packets being discarded.
Usage This counter is used to find out the number of transmitted packets
being discarded.
Measurement The counter counts when the packet is transmitted.
Point

packets high 32bits
number of transmitted packets being discarded.
being discarded.
Point
C901850055 send packet

bytes flag
valid.


detected.
Measurement None
Point
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 trans-
mitted packets.
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 trans-
mitted packets.
Point

flag
valid.
detected.

Measurement None
Point

low 32bits
number of transmitted packets.
Usage This counter is used to find out the total number of transmitted
packets.
Point

high 32bits
number of transmitted packets.
Usage This counter is used to find out the total number of transmitted
packets.
Point
C901850061 send broadcast

packets flag
valid.
detected.

Measurement None
Point

packets low 32bits
number of transmitted broadcast packets.
Usage This counter is used to find out the number of transmitted broad-
cast packets.
Point

packets high 32bits
number of transmitted broadcast packets.
Usage This counter is used to find out the number of transmitted broad-
cast packets.
Point
C901850064 send multicast

packets flag
valid.
detected.

Measurement None
Point

packets low 32bits
number of transmitted multicast packets.
Usage This counter is used to find out the number of transmitted multi-
cast packets.
Point

packets high 32bits
number of transmitted multicast packets.
Usage This counter is used to find out the number of transmitted multi-
cast packets.
Point
C901850067 send CRC or

Align error packets flag
valid.
detected.

Measurement None
Point
C901850068 send CRC

or Align error packets low
32bits
number of transmitted CRC or alignment error packets.
Usage This counter is used to find out the number of transmitted CRC or
Point
C901850069 send CRC

or Align error packets high
32bits
number of transmitted CRC or alignment error packets.
Usage This counter is used to find out the number of transmitted CRC or
Point
C901850070 send small

valid.
detected.

Measurement None
Point

32bits
number of transmitted packets of which the size is smaller than
64 bytes.
of which the size is smaller than 64 bytes.
Point

than 64 bytes packets high
32bits
number of transmitted packets of which the size is smaller than
64 bytes.
of which the size is smaller than 64 bytes.
Point
C901850073 send large

valid.


detected.
Measurement None
Point

32bits
number of transmitted packets of which the size is larger than
1518 bytes.
of which the size is larger than 1518 bytes.
Point

than 1518 bytes packets
high 32bits
number of transmitted packets of which the size is larger than
1518 bytes.
of which the size is larger than 1518 bytes.
Point
C901850076 The flag of sent

fragment packets

valid.
detected.
Measurement None
Point

fragment packets (low 32 bit)
number of transmitted fragment packets.
Usage This counter is used to find out the number of transmitted frag-
ment packets.
Point

fragment packets (high 32
bit)
number of transmitted fragment packets.
Usage This counter is used to find out the number of transmitted frag-
ment packets.
Point
C901850079 send Jabber

packets flag

valid.
detected.
Measurement None
Point

packets low 32bits
number of transmitted Jabber packets.
Usage This counter is used to find out the number of transmitted Jabber
packets.
Point

packets high 32bits
number of transmitted Jabber packets.
Usage This counter is used to find out the number of transmitted Jabber
packets.
Point
C901850082 send Collision

count flag
valid.


detected.
Measurement None
Point

count low 32bits
number of transmitted collisions.
Usage This counter is used to find out the number of transmitted colli-
sions.
Point

count high 32bits
number of transmitted collisions.
Usage This counter is used to find out the number of transmitted colli-
sions.
Point
C901850085 send 64 bytes

packets flag
valid.
detected.

Measurement None
Point

packets low 32bits
number of transmitted packets of which the size is 64 bytes.
of which the size is 64 bytes.
Point

packets high 32bits
number of transmitted packets of which the size is 64 bytes.
of which the size is 64 bytes.
Point
C901850088 send 65 to 127

bytes packets flag
valid.
detected, however, it does n

BSC Performance Counter Reference

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

BSC Performance Counter Reference

Caricato da

Copyright:

Formati disponibili

ZXG10 iBSC

Base Station Controller

Copyright © 2010 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revison No. Revision Date Revision Reason

Serial Number: SJ-20100524164252-015

About This Manual............................................. I

Confidential and Proprietary Information of ZTE CORPORATION I

C900040013 Number of EGPRS DL TBF release due to

II Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION III

C900040054 Number of discarded EGPRS DL signaling

IV Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION V

C900040096 Number of UL RLC pending blocks in CS3 on

VI Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION VII

C900040130 Number of EGPRS UL TBF resource

VIII Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION IX

C900040169 Number of GPRS DL TBF establishment

X Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XI

C900040209 Number of UL RLC NACK blocks in MCS2 on

XII Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XIII

C900060018 Number of signaling TCH/F assignment

XIV Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XV

C900060058 Average number of idle TCH/F with

XVI Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XVII

C900060105 Number of incoming handover from

XVIII Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XIX

C900060146 Number of TCH/F allocation failure due

XX Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XXI

C900060178 Number of TCH/H allocation failure due

XXII Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XXIII

C900060207 Number of data TCH/H allocation failure due

XXIV Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XXV

C900090004 Number of SDCCH .................................... 430

XXVI Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XXVII

C901010012 Number of GPRS UL TBF establishment

XXVIII Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XXIX

C901020050 Number of Kbytes carried by GPRS DL LLC

XXX Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XXXI

C901040027 Sum of Abis TS used sampling .................... 547

XXXII Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XXXIII

C901050023 Number of assignment for retry attempts

XXXIV Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XXXV

C901050060 Attempt Number of mode modify for

XXXVI Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION XXXVII

C901060042 Number of TCH/F handover attempts due to