SJ-20100414142254-015-ZXG10 iBSC (V6.20.21) Base Station Controller Performance Counter Reference PDF

ZXG10 iBSC
Base Station Controller

Performance Counter Reference
Version:6.20.21
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revison No. Revision Date Revision Reason
R1.2 20101115 Add related features for the counters
R1.1 20100830 Add the following content: layers related to data flow statistics cou
nters, and whether the counter's statistics contain header informa
tion
Revise the description of basic measurement counters and general

measurement counters
R1.0 20100430 First edition
Serial Number: SJ-20100414142254-015
Publishing Date: 20101115(R1.2)

Content
About This Manual ......................................................................................... I
Chapter 1 PS Basic Measurement (BSC) ................................................. 1-1
1.1 Overview ........................................................................................................... 1-1
1.2 C900030001 Number of bytes received from data link .......................................... 1-1
1.3 C900030002 Number of bytes sent to data link ................................................... 1-1
Chapter 2 PS Basic Measurement (Cell) .................................................. 2-1

2.1 Overview ........................................................................................................... 2-7
2.2 C900040001 Number of GPRS DL TBF establishment success on PACCH ........... 2-7
2.3 C900040002 Number of GPRS DL TBF release due to N3105 overflow................. 2-8
2.4 C900040003 Number of GPRS DL TBF release due to other reasons ................... 2-9
2.5 C900040004 Number of GPRS DL TBF forcing release by control plane.............. 2-10
2.6 C900040005 Number of GPRS DL TBF release due to instance suspension.........2-11
2.7 C900040006 Number of GPRS DL TBF release due to inner abnormal................ 2-12
2.8 C900040007 Number of GPRS DL signaling TBF establishment ......................... 2-12
2.9 C900040008 Number of GPRS DL data TBF establishment ................................ 2-13
2.10 C900040009 Number of EGPRS DL TBF establishment success on PACCH ..... 2-13
2.11 C900040010 Number of EGPRS DL TBF release due to N3105 overflow........... 2-15
2.12 C900040011 Number of EGPRS DL TBF release due to other reasons.............. 2-16
2.13 C900040012 Number of EGPRS DL TBF forcing release by control plane ......... 2-16
2.14 C900040013 Number of EGPRS DL TBF release due to instance suspension ..... 2-17
2.15 C900040014 Number of EGPRS DL TBF release due to inner abnormal ........... 2-18
2.16 C900040015 Number of EGPRS DL signaling TBF establishment ..................... 2-19
2.17 C900040016 Number of EGPRS DL data TBF establishment............................ 2-19
2.18 C900040017 Average number of GPRS DL TBF simultaneous establishment
..................................................................................................................... 2-19
2.19 C900040018 Average number of EGPRS DL TBF simultaneous establishment
..................................................................................................................... 2-20
2.20 C900040019 Number of GPRS UL data TBF establishment success on
PACCH .......................................................................................................... 2-20
2.21 C900040020 Number of GPRS UL TBF release due to N3101 overflow............. 2-21
2.22 C900040021 Number of GPRS UL TBF release due to N3103 overflow............. 2-22
2.23 C900040022 Number of GPRS UL TBF forcing release by control plane............ 2-22
2.24 C900040023 Number of GPRS UL TBF release due to instance suspension...... 2-23
2.25 C900040024 Number of GPRS UL TBF release due to inner abnormal.............. 2-24
I
2.26 C900040025 Number of GPRS UL signaling TBF establishment ....................... 2-24
2.27 C900040026 Number of GPRS UL data TBF establishment .............................. 2-26
2.28 C900040027 Number of EGPRS UL TBF establishment success on PACCH ..... 2-27
2.29 C900040028 Number of EGPRS UL TBF release due to N3101 overflow........... 2-28
2.30 C900040029 Number of EGPRS UL TBF release due to N3103 overflow........... 2-29
2.31 C900040030 Number of EGPRS UL TBF forcing release by control plane ......... 2-29
2.32 C900040031 Number of EGPRS UL TBF release due to instance suspension ..... 2-30
2.33 C900040032 Number of EGPRS UL TBF release due to inner abnormal ........... 2-30
2.34 C900040033 Number of EGPRS UL signaling TBF establishment ..................... 2-31
2.35 C900040034 Number of EGPRS UL data TBF establishment............................ 2-31
2.36 C900040035 Average number of GPRS UL TBF simultaneous establishment
..................................................................................................................... 2-31
2.37 C900040036 Average number of EGPRS UL TBF simultaneous establishment
..................................................................................................................... 2-32
2.38 C900040037 Number of GPRS UL signaling TBF release due to N3101
overflow ......................................................................................................... 2-32
2.39 C900040038 Number of GPRS UL signaling TBF release due to N3103
overflow ......................................................................................................... 2-33
2.40 C900040039 Number of GPRS UL signaling TBF forcing release by control
plane ............................................................................................................. 2-33
2.41 C900040040 Number of GPRS UL signaling TBF release due to instance
suspension..................................................................................................... 2-34
2.42 C900040041 Number of GPRS UL signaling TBF release due to inner
abnormal........................................................................................................ 2-34
2.43 C900040042 Number of EGPRS UL signaling TBF release due to N3101
overflow ......................................................................................................... 2-35
2.44 C900040043 Number of EGPRS UL signaling TBF release due to N3103
overflow ......................................................................................................... 2-35
2.45 C900040044 Number of EGPRS UL signaling TBF forcing release by control
plane ............................................................................................................. 2-36
2.46 C900040045 Number of EGPRS UL signaling TBF release due to instance
suspension..................................................................................................... 2-36
2.47 C900040046 Number of EGPRS UL signaling TBF release due to inner
abnormal........................................................................................................ 2-37
2.48 C900040047 Number of EGPRS DL LLC frames.............................................. 2-37
2.49 C900040048 Number of discarded EGPRS DL LLC frames due to buffer
overflow ......................................................................................................... 2-38
2.50 C900040049 Number of discarded EGPRS DL LLC frames due to life time
expiration ....................................................................................................... 2-38
II
2.51 C900040050 Number of discarded EGPRS DL LLC frames due to other
reasons ......................................................................................................... 2-39
2.52 C900040051 Number of DL signaling LLC frames ............................................ 2-40
2.53 C900040052 Number of discarded EGPRS DL signaling LLC frames due to
buffer overflow................................................................................................ 2-40
life time expiration........................................................................................... 2-41
other reasons ................................................................................................. 2-42
2.56 C900040055 Number of data blocks transmitted according to given Abis
bandwidth ...................................................................................................... 2-43
2.57 C900040056 Bytes of effective upper layer protocol data sent on DL PDCH ...... 2-43
2.58 C900040057 Bytes of effective upper layer protocol data received on UL
PDCH ........................................................................................................... 2-44
2.59 C900040058 Bytes of LLC frame on GPRS UL data TBF ................................. 2-45
2.60 C900040059 Duration of GPRS UL data TBF................................................... 2-45
2.61 C900040060 Bytes of LLC frame on GPRS DL data TBF ................................. 2-47
2.62 C900040061 Duration of GPRS DL data TBF................................................... 2-48
2.63 C900040062 Number of effective data blocks received on GPRS UL TBF.......... 2-49
2.64 C900040063 Number of NACK blocks received on GPRS UL TBF ................... 2-50
2.65 C900040064 Number of effective data blocks sent on GPRS DL TBF ............... 2-51
2.66 C900040065 Number of NACK blocks sent on GPRS DL TBF .......................... 2-52
2.67 C900040066 Bytes of LLC frame on EGPRS UL data TBF ............................... 2-53
2.68 C900040067 Duration of EGPRS UL data TBF................................................. 2-54
2.69 C900040068 Bytes of LLC frame on EGPRS DL data TBF ............................... 2-55
2.70 C900040069 Duration of EGPRS DL data TBF................................................. 2-56
2.71 C900040070 Number of effective data blocks received on EGPRS UL TBF ....... 2-57
2.72 C900040071 Number of NACK blocks received on EGPRS UL TBF ................. 2-58
2.73 C900040072 Number of effective data blocks sent on EGPRS DL TBF ............. 2-59
2.74 C900040073 Number of NACK blocks sent on EGPRS DL TBF ....................... 2-60
2.75 C900040074 Number of GPRS DL LLC frames ................................................ 2-61
2.76 C900040075 Number of discarded GPRS DL LLC frames due to buffer
overflow ......................................................................................................... 2-62
2.77 C900040076 Number of discarded GPRS DL LLC frames due to life time
expiration ....................................................................................................... 2-63
2.78 C900040077 Number of discarded GPRS DL LLC frames due to other
reasons.......................................................................................................... 2-63
2.79 C900040078 Number of DL dummy control blocks on PACCH .......................... 2-64
2.80 C900040079 Number of UL dummy control blocks on PACCH .......................... 2-65
III
2.81 C900040080 Number of DL RLC blocks on PACCH (excluding dummy block) ..... 2-65
2.82 C900040081 Number of DL RLC pending blocks in CS1 on PDTCH.................. 2-66
2.86 C900040085 Number of DL RLC NACK blocks in CS1 on PDTCH .................... 2-70
2.90 C900040089 Number of DL RLC new blocks in CS1 on PDTCH........................ 2-74
2.94 C900040093 Number of UL RLC blocks excluding dummy blocks on PACCH ..... 2-77
2.95 C900040094 Number of UL RLC pending blocks in CS1 on PDTCH.................. 2-78
2.99 C900040098 Number of UL RLC NACK blocks in CS1 on PDTCH .................... 2-82
2.100 C900040099 Number of UL RLC NACK blocks in CS2 on PDTCH................... 2-83
2.103 C900040102 Number of UL RLC new blocks in CS1 on PDTCH...................... 2-86
2.107 C900040106 Number of UL data blocks received on PDTCH .......................... 2-90
2.108 C900040107 Number of DL data blocks sent on PDTCH................................. 2-90
2.109 C900040108 Number of GPRS DL TBF establishment requests ..................... 2-91
2.110 C900040109 Number of GPRS DL TBF establishment failure due to database
allocation failure ............................................................................................. 2-91
2.111 C900040110 Number of GPRS DL TBF resource reallocation requests due to
UL TBF establishment .................................................................................... 2-93
2.112 C900040111 Number of GPRS DL TBF resource reallocation failure due to
2.113 C900040112 Number of GPRS DL TBF resource reallocation requests due to
LLC transmission............................................................................................ 2-94
IV
LLC transmission ........................................................................................... 2-95
2.115 C900040114 Number of EGPRS DL TBF establishment requests ................... 2-96
2.116 C900040115 Number of EGPRS DL TBF establishment failure due to
database allocation failure............................................................................... 2-96
2.117 C900040116 Number of EGPRS DL TBF resource reallocation requests due
to UL TBF establishment ................................................................................ 2-97
2.118 C900040117 Number of EGPRS DL TBF resource reallocation failure due to
2.119 C900040118 Number of EGPRS DL TBF resource reallocation requests due
to LLC transmission ........................................................................................ 2-99
LLC transmission ..........................................................................................2-100
2.121 C900040120 Number of GPRS UL TBF establishment requests ....................2-100
2.122 C900040121 Number of GPRS UL TBF establishment failure due to database
allocation failure ............................................................................................2-101
2.123 C900040122 Number of GPRS UL TBF resource reallocation requests due
to DL TBF establishment................................................................................2-102
2.124 C900040123 Number of GPRS UL TBF resource reallocation failure due to
DL TBF establishment ...................................................................................2-103
2.125 C900040124 Number of GPRS UL TBF resource reallocation requests due
to LLC transmission .......................................................................................2-104
LLC transmission...........................................................................................2-105
2.127 C900040126 Number of GPRS UL TBF resource reallocation requests for
resource request ...........................................................................................2-106
database allocation failure for resource request ...............................................2-106
2.129 C900040128 Number of EGPRS UL TBF establishment requests...................2-107
2.130 C900040129 Number of EGPRS UL TBF establishment failure due to
database allocation failure..............................................................................2-108
2.131 C900040130 Number of EGPRS UL TBF resource reallocation requests due
2.132 C900040131 Number of EGPRS UL TBF resource reallocation failure due to
DL TBF establishment ................................................................................... 2-110
2.133 C900040132 Number of EGPRS UL TBF resource reallocation requests due
to LLC transmission ....................................................................................... 2-110
LLC transmission........................................................................................... 2-111
2.135 C900040134 Number of EGPRS UL TBF resource reallocation requests for
resource request ........................................................................................... 2-112
V
database allocation failure for resource request ............................................... 2-113
2.137 C900040136 Average number of available PDCH.......................................... 2-113
2.138 C900040137 Number of forcing conversation dynamic from PDCH to TCH by
BSC.............................................................................................................. 2-114
2.139 C900040138 Number of PDCH used by TBF in each cell ............................... 2-114
2.140 C900040139 Maximum number of used PDCH.............................................. 2-115
2.141 C900040140 Average number of used PDCH................................................ 2-115
2.142 C900040141 Number of GPRS DL TBF establishment requests before T3192
expiration ...................................................................................................... 2-116
2.143 C900040142 Number of GPRS DL TBF establishment using existing DL TBF
resource ....................................................................................................... 2-117
2.144 C900040143 Number of GPRS DL TBF establishment requests on
PACCH ......................................................................................................... 2-117
CCCH/PCCCH .............................................................................................. 2-118
2.146 C900040145 Number of EGPRS DL TBF establishment requests before
T3192 expiration............................................................................................ 2-119
2.147 C900040146 Number of EGPRS DL TBF establishment using existing DL
TBF resource ................................................................................................2-120
2.148 C900040147 Number of EGPRS DL TBF establishment requests on
PACCH .........................................................................................................2-121
CCCH/PCCCH ..............................................................................................2-122
2.150 C900040149 Number of GPRS DL signaling TBF release due to N3105
overflow ........................................................................................................2-123
2.151 C900040150 Number of GPRS DL signaling TBF release due to other
reasons.........................................................................................................2-124
2.152 C900040151 Number of GPRS DL signaling TBF forcing release by control
plane ............................................................................................................2-124
2.153 C900040152 Number of GPRS DL signaling TBF release due to instance
suspension....................................................................................................2-125
2.154 C900040153 Number of GPRS DL signaling TBF release due to inner
abnormal.......................................................................................................2-126
2.155 C900040154 Number of EGPRS DL signaling TBF release due to N3105
overflow ........................................................................................................2-127
2.156 C900040155 Number of EGPRS DL signaling TBF release due to other
reasons.........................................................................................................2-128
2.157 C900040156 Number of EGPRS DL signaling TBF forcing release by control
plane ............................................................................................................2-128
VI
2.158 C900040157 Number of EGPRS DL signaling TBF release due to instance
suspension....................................................................................................2-129
2.159 C900040158 Number of EGPRS DL signaling TBF release due to inner
abnormal.......................................................................................................2-130
2.160 C900040159 Number of GPRS UL TBF establishments in release state .........2-131
2.161 C900040160 Number of GPRS UL TBF establishment with existing UL
resource .......................................................................................................2-132
2.162 C900040161 Number of GPRS UL TBF establishment requests on
PACCH .........................................................................................................2-132
2.163 C900040162 Number of EGPRS UL data TBF establishments on PACCH ......2-133
2.164 C900040163 Number of EGPRS UL TBF establishments in release state .......2-134
2.165 C900040164 Number of EGPRS UL TBF establishment with existing UL
resource .......................................................................................................2-135
2.166 C900040165 Number of EGPRS UL TBF establishment requests on
PACCH .........................................................................................................2-135
2.167 C900040166 Number of EGPRS UL TBF establishment requests on
CCCH/PCCCH ..............................................................................................2-136
2.168 C900040167 Number of dynamic PDCH preemption for CS service................2-137
CCCH/PCCCH ..............................................................................................2-137
PACCH .........................................................................................................2-138
PACCH .........................................................................................................2-139
PACCH .........................................................................................................2-139
2.173 C900040172 Number of DL RLC pending blocks in MCS1 on PDTCH ............2-140
2.182 C900040181 Number of DL RLC NACK blocks in MCS1 on PDTCH...............2-149
VII
2.191 C900040190 Number of DL RLC new blocks in MCS1 on PDTCH ..................2-158
2.200 C900040199 Number of UL RLC pending blocks in MCS1 on PDTCH ............2-167
2.209 C900040208 Number of UL RLC NACK blocks in MCS1 on PDTCH...............2-176
2.211 C900040210 Number of UL RLC NACK blocks in MCS3 on PDTCH ...............2-178
2.212 C900040211 Number of UL RLC NACK blocks in MCS4 on PDTCH ...............2-179
2.218 C900040217 Number of UL RLC new blocks in MCS1 on PDTCH ..................2-185
VIII
Chapter 3 CPU Load Measurement........................................................... 3-1

3.1 Overview ........................................................................................................... 3-1
3.2 C900050001 Average load of the processor......................................................... 3-1
3.3 C900050002 Peak value of the processor load..................................................... 3-1
Chapter 4 CS Basic Measurement ............................................................ 4-1

4.1 Overview ........................................................................................................... 4-8
4.2 C900060001 Number of MTC access attempts .................................................... 4-8
4.3 C900060002 Number of MTC access success ..................................................... 4-9
4.4 C900060003 Number of SDCCH seizure attempts for assignment....................... 4-10
4.5 C900060004 Number of SDCCH seizure success for assignment ........................4-11
4.6 C900060005 Number of SDCCH seizure failure for assignment .......................... 4-12
4.7 C900060006 Number of SDCCH seizure attempts for handover.......................... 4-13
4.8 C900060007 Number of SDCCH seizure failure for handover ............................. 4-15
4.9 C900060008 Number of SDCCH allocation success for assignment .................... 4-17
4.10 C900060009 Number of SDCCH allocation failure for assignment ..................... 4-18
4.11 C900060010 Number of signaling TCH/F seizure attempts for assignment ......... 4-19
4.12 C900060011 Number of signaling TCH/F seizure failure for assignment............. 4-20
4.13 C900060012 Number of signaling TCH/F seizure attempts for handover ............ 4-21
4.14 C900060013 Number of signaling TCH/F seizure failure for handover................ 4-24
4.15 C900060014 Number of signaling TCH/F allocation success for assignment ...... 4-25
4.16 C900060015 Number of signaling TCH/F allocation failure for assignment ......... 4-26
4.17 C900060016 Number of signaling TCH/F allocation failure for handover ............ 4-27
4.18 C900060017 Number of signaling TCH/F assignment success for
assignment .................................................................................................... 4-28
4.19 C900060018 Number of signaling TCH/F assignment failure for assignment ...... 4-29
4.20 C900060019 Number of voice TCH/F seizure attempts for assignment .............. 4-30
4.21 C900060020 Number of voice TCH/F seizure failure for assignment.................. 4-32
4.22 C900060021 Number of voice TCH/F seizure attempts for handover ................. 4-33
4.23 C900060022 Number of voice TCH/F seizure failure for handover ..................... 4-36
4.24 C900060023 Number of TCH/F allocation success for assignment (speech
version1)........................................................................................................ 4-37
4.25 C900060024 Number of TCH/F allocation failure due to channel activation
failure for assignment (speech version1) .......................................................... 4-38
IX
version2)........................................................................................................ 4-39
version3)........................................................................................................ 4-40
failure for assignment (speech version3) .......................................................... 4-42
4.29 C900060028 Number of voice TCH/F assignment success ............................... 4-43
4.30 C900060029 Number of voice TCH/F assignment failure for assignment ........... 4-44
4.31 C900060030 Number of data TCH/F seizure attempts for assignment ............... 4-45
4.32 C900060031 Number of data TCH/F seizure failure for assignment ................... 4-47
4.33 C900060032 Number of data TCH/F seizure attempts for handover................... 4-48
4.34 C900060033 Number of data TCH/F seizure failure for handover ...................... 4-51
4.35 C900060034 Number of data TCH/F allocation success for assignment............. 4-52
4.36 C900060035 Number of data TCH/F allocation failure due to channel activation
failure for assignment...................................................................................... 4-53
4.37 C900060036 Number of data TCH/F assignment success................................. 4-54
4.38 C900060037 Number of data TCH/F assignment failure.................................... 4-56
4.39 C900060038 Number of signaling TCH/H seizure attempts for assignment ........ 4-57
4.40 C900060039 Number of signaling TCH/H seizure failure for assignment ............ 4-58
4.41 C900060040 Number of signaling TCH/H seizure attempts for handover ........... 4-59
4.42 C900060041 Number of signaling TCH/H seizure failure for handover ............... 4-62
4.43 C900060042 Number of voice TCH/H seizure attempts for assignment.............. 4-63
4.44 C900060043 Number of voice TCH/H seizure failure for assignment ................. 4-65
4.45 C900060044 Number of voice TCH/H seizure attempts for handover ................. 4-66
4.46 C900060045 Number of voice TCH/H seizure failure for handover..................... 4-69
4.47 C900060046 Number of data TCH/H seizure attempts for assignment ............... 4-70
4.48 C900060047 Number of data TCH/H seizure failure for assignment................... 4-72
4.49 C900060048 Number of data TCH/H seizure attempts for handover .................. 4-73
4.50 C900060049 Number of data TCH/H seizure failure for handover ...................... 4-76
4.51 C900060050 Number of SAPI3 link establishment requests on SDCCH
(MO-SM)........................................................................................................ 4-77
4.52 C900060051 Number of SAPI3 link establishment requests on SDCCH
(MT-SM) ........................................................................................................ 4-79
4.53 C900060052 Number of SDCCH drops due to handover failure......................... 4-80
4.54 C900060053 Number of SDCCH drops............................................................ 4-82
4.55 C900060054 Number of TCH/F drops.............................................................. 4-83
4.56 C900060055 Number of TCH/H drops ............................................................. 4-83
4.57 C900060056 Average number of idle TCH/F with interference band 1................ 4-84
X
4.62 C900060061 Average number of idle TCH/H with interference band 1 ............... 4-86
4.67 C900060066 Number of samples with UL RQ = 0............................................. 4-89
4.75 C900060074 Number of samples with DL RQ = 0............................................. 4-93
4.83 C900060082 Number of TCH/F handover attempts due to UL strength .............. 4-97
4.84 C900060083 Number of TCH/F handover attempts due to DL strength .............. 4-98
4.85 C900060084 Number of TCH/F handover attempts due to UL quality ................ 4-99
4.86 C900060085 Number of TCH/F handover attempts due to DL quality ................ 4-99
4.87 C900060086 Number of TCH/F handover attempts due to UL interference........4-100
4.88 C900060087 Number of TCH/F handover attempts due to DL interference........4-101
4.89 C900060088 Number of TCH/F handover attempts due to good C/I..................4-102
4.90 C900060089 Number of TCH/F handover attempts due to bad C/I....................4-103
4.91 C900060090 Number of TCH/F handover attempts due to PBGT .....................4-104
4.92 C900060091 Number of TCH/F handover attempts due to large TA ..................4-105
4.93 C900060092 Number of TCH/F handover attempts due to other reasons ..........4-106
4.94 C900060093 Number of BSC-controlled inter-cell outgoing handover ...............4-106
XI
4.95 C900060094 Number of BSC-controlled inter-cell outgoing handover
success ........................................................................................................4-107
4.96 C900060095 Number of MSC-controlled outgoing handover ............................4-108
4.97 C900060096 Number of MSC-controlled outgoing handover success ...............4-109
4.98 C900060097 Number of BSC-controlled inter-cell incoming handover............... 4-110
4.99 C900060098 Number of BSC-controlled inter-cell incoming handover
success ........................................................................................................ 4-111
4.100 C900060099 Number of MSC-controlled incoming handover .......................... 4-112
4.101 C900060100 Number of MSC-controlled incoming handover due to forced
release.......................................................................................................... 4-113
4.102 C900060101 Number of MSC-controlled incoming handover due to queue ...... 4-114
4.103 C900060102 Number of MSC-controlled incoming handover success ............. 4-115
4.104 C900060103 Number of incoming handover from undefined layer (GSM900)
to current layer(GSM1800) ............................................................................. 4-115
4.105 C900060104 Number of incoming handover success from undefined
layer(GSM900) to current layer (GSM1800)..................................................... 4-116
4.106 C900060105 Number of incoming handover from undefined layer (GSM1800)
to current layer (GSM900) .............................................................................. 4-117
4.107 C900060106 Number of incoming handover success from undefined
layer(GSM1800) to current layer(GSM900) ..................................................... 4-118
4.108 C900060107 Number of incoming handover from the same layer GSM900 to
GSM1800 ..................................................................................................... 4-119
4.109 C900060108 Number of incoming handover success from the same layer
GSM900 to GSM1800....................................................................................4-120
4.110 C900060109 Number of incoming handover from GSM900 to GSM1800 from
the upper layer ..............................................................................................4-121
4.111 C900060110 Number of incoming handover success from GSM900 to
GSM1800 in the upper layer...........................................................................4-122
4.112 C900060111 Number of incoming handover from GSM900 to GSM1800 in
the lower layer...............................................................................................4-123
GSM1800 in the lower layer ...........................................................................4-124
the same layer...............................................................................................4-125
GSM900 from the same layer .........................................................................4-126
the upper layer ..............................................................................................4-127
GSM900 from the upper layer.........................................................................4-128
XII
the lower layer...............................................................................................4-129
GSM900 from the lower layer .........................................................................4-130
4.120 C900060119 Number of Intra-cell handover...................................................4-131
4.121 C900060120 Number of Intra-cell handover success .....................................4-132
4.122 C900060121 Maximum number of busy TCH/H .............................................4-133
4.123 C900060122 Average number of available SDCCH .......................................4-134
4.124 C900060123 Average number of unavailable SDCCH....................................4-135
4.125 C900060124 SDCCH busy time ...................................................................4-136
4.126 C900060125 Average number of available radio channel ...............................4-137
4.127 C900060126 Average number of unavailable radio channel ...........................4-137
4.128 C900060127 TCH/H busy time .....................................................................4-138
4.129 C900060128 Maximum number of busy TCH/F .............................................4-139
4.130 C900060129 TCH/F busy time .....................................................................4-140
4.131 C900060130 Number of healthy TRXs ..........................................................4-141
4.132 C900060131 Number of CM service requests of MOC ...................................4-142
4.133 C900060132 Number of SAPI3 link establishment success on SDCCH
(MT-SM) .......................................................................................................4-143
4.134 C900060133 Number of available defined SDCCH ........................................4-144
4.135 C900060134 Number of available defined TCH/F ..........................................4-145
4.136 C900060135 Number of signaling TCH/H assignment failure..........................4-146
4.137 C900060136 Number of MOC access attempts .............................................4-147
4.138 C900060137 Number of wireless access due to paging responses .................4-148
4.139 C900060138 Number of TCH/F allocation failure due to BTS connection
failure for assignment (speech version1) .........................................................4-149
4.140 C900060139 Number of TCH/F allocation failure due to BIU connection
4.141 C900060140 Number of TCH/F allocation failure due to TCU connection
XIII
4.149 C900060148 Number of data TCH/F allocation failure due to BTS connection
failure for assignment) ...................................................................................4-159
4.150 C900060149 Number of data TCH/F allocation failure due to BIU connection
failure for assignment.....................................................................................4-160
4.151 C900060150 Number of data TCH/F allocation failure due to TCU connection
4.152 C900060151 Number of voice TCH/H drops due to handover failure...............4-162
4.153 C900060152 Number of Abis interface paging command messages ...............4-164
4.154 C900060153 Number of Abis CS paging messages.......................................4-165
4.155 C900060154 Number of Abis PS paging messages .......................................4-166
4.156 C900060155 Number of available defined TCH/H..........................................4-166
failure for handover(speech version1) .............................................................4-167
failure for handover (speech version1) ............................................................4-169
failure for handover(speech version2) .............................................................4-172
XIV
4.169 C900060168 Number of Voice TCH/F handover success ...............................4-182
4.170 C900060169 Number of data TCH/F allocation failure due to channel
activation failure for handover.........................................................................4-184
4.171 C900060170 Number of data TCH/F allocation failure due to BTS connection
failure for handover........................................................................................4-185
4.172 C900060171 Number of data TCH/F allocation failure due to BIU connection
4.173 C900060172 Number of data TCH/F allocation failure due to TCU connection
4.174 C900060173 Number of data TCH/F handover success .................................4-189
4.175 C900060174 Number of signaling TCH/H allocation failure for assignment ......4-191
4.176 C900060175 Number of TCH/H allocation failure due to channel activation
4.177 C900060176 Number of TCH/H allocation failure due to BTS connection
4.178 C900060177 Number of TCH/H allocation failure due to BIU connection
4.179 C900060178 Number of TCH/H allocation failure due to TCU connection
XV
failure for assignment (speech version3) ......................................................... 4-211
4.200 C900060199 Number of Voice TCH/H assignment success............................4-218
4.201 C900060200 Number of Voice TCH/H assignment failure...............................4-220
4.202 C900060201 Number of Voice TCH/H handover success ...............................4-221
4.203 C900060202 Number of data TCH/H allocation failure due to channel
activation failure for assignment......................................................................4-223
4.204 C900060203 Number of data TCH/H allocation failure due to BTS connection
4.205 C900060204 Number of data TCH/H allocation failure due to BIU connection
4.206 C900060205 Number of data TCH/H allocation failure due to TCU connection
4.207 C900060206 Number of data TCH/H allocation failure due to channel
activation failure for handover.........................................................................4-227
4.208 C900060207 Number of data TCH/H allocation failure due to BTS connection
4.209 C900060208 Number of data TCH/H allocation failure due to BIU connection
4.210 C900060209 Number of data TCH/H allocation failure due to TCU connection
4.211 C900060210 Number of data TCH/H assignment success..............................4-232
XVI
4.212 C900060211 Number of data TCH/H assignment failure.................................4-233
4.213 C900060212 Number of data TCH/H handover success.................................4-234
4.214 C900060213 Number of BSC-controlled incoming handover due to forced
release..........................................................................................................4-237
4.215 C900060214 Number of BSC-controlled incoming handover due to
queues..........................................................................................................4-238
4.216 C900060215 Number of BSC-controlled incoming handover due to forced
handover.......................................................................................................4-239
4.217 C900060216 Number of MSC-controlled incoming handover due to forced
handover.......................................................................................................4-241
4.218 C900060217 Number of unavailable defined TCH/H ......................................4-242
4.219 C900060218 Number of unavailable defined TCH/F ......................................4-243
4.220 C900060219 Number of signaling TCH/F drops due to handover failure..........4-244
4.221 C900060220 Number of voice TCH/F drops due to handover failure ...............4-246
4.222 C900060221 Number of data TCH/F drops due to handover failure ................4-248
4.223 C900060222 Number of signaling TCH/H drops due to handover failure .........4-250
4.224 C900060223 Number of data TCH/H drops due to handover failure ................4-252
4.225 C900060224 Number of TCH/H handover attempts due to UL strength ...........4-254
4.226 C900060225 Number of TCH/H handover attempts due to DL strength ...........4-255
4.227 C900060226 Number of TCH/H handover attempts due to UL quality .............4-256
4.228 C900060227 Number of TCH/H handover attempts due to DL quality .............4-256
4.229 C900060228 Number of TCH/H handover attempts due to UL interference ......4-257
4.230 C900060229 Number of TCH/H handover attempts due to DL interference ......4-258
4.231 C900060230 Number of TCH/H inter-subcell handover attempts due to good
C/I ................................................................................................................4-259
4.232 C900060231 Number of TCH/H inter-subcell handover attempts due to bad
C/I ................................................................................................................4-260
4.233 C900060232 Number of TCH/H handover attempts due to PBGT ...................4-261
4.234 C900060233 Number of TCH/H handover attempts due to large TA................4-262
4.235 C900060234 Number of TCH/H handover attempts due to other reasons........4-263
4.236 C900060235 Number of signaling TCH/H assignment success.......................4-264
4.237 C900060236 Number of MOC access success ..............................................4-265
4.238 C900060237 Number of dual band outgoing handover...................................4-266
4.239 C900060238 Number of dual band outgoing handover success......................4-267
4.240 C900060239 Number of dual band incoming handover ..................................4-268
4.241 C900060240 Number of dual band incoming handover success .....................4-269
4.242 C900060241 Number of SDCCH assignment attempts ..................................4-269
4.243 C900060242 Number of SDCCH assignments success .................................4-271
XVII
4.244 C900060243 Number of SDCCH assignment failure ......................................4-272
4.245 C900060244 Number of voice TCH/F drops due to radio link failure................4-273
4.246 C900060245 Number of voice TCH/H drops due to radio link failure ...............4-274
Chapter 5 Configuration Management Infomation Basic

Measurement .......................................................................................... 5-1
5.1 Overview ........................................................................................................... 5-1
5.2 C900090001 Cell frequency band ....................................................................... 5-1
5.3 C900090002 Number of TRX .............................................................................. 5-2
5.4 C900090003 Number of TCH.............................................................................. 5-2
5.5 C900090004 Number of SDCCH......................................................................... 5-2
5.6 C900090005 Radio capacity (call loss 1) ............................................................. 5-3
5.7 C900090006 Radio capacity (call loss 2) ............................................................. 5-3
5.8 C900090007 Radio capacity (based on TRX)....................................................... 5-3
5.9 C900090008 Number of static PDTCH ................................................................ 5-4
5.10 C900090009 Number of dynamic PDTCH .......................................................... 5-4
Chapter 6 Downlink Data TBF Measurement ........................................... 6-1

6.1 Overview ........................................................................................................... 6-2
6.2 C901000001 Number of GPRS DL TBF resumption in delay state......................... 6-2
6.3 C901000005 Number of GPRS DL TBF establishment failure on PACCH due to
time out............................................................................................................ 6-3
6.4 C901000006 Number of GPRS DL TBF establishment failure on PACCH due to
other reasons ................................................................................................... 6-4
6.5 C901000009 Number of GPRS DL TBF establishment failure on CCCH/PCCCH
due to time out ................................................................................................. 6-5
6.6 C901000010 Number of GPRS DL TBF establishment failure on CCCH/PCCCH
due to other reasons ......................................................................................... 6-6
6.7 C901000011 Number of GPRS DL TBF establishment execution on
CCCH/PCCCH ................................................................................................. 6-6
6.8 C901000012 Number of GPRS DL TBF establishment execution failure on
CCCH/PCCCH due to polling failed ................................................................... 6-8
6.9 C901000013 Number of GPRS DL TBF establishment execution success on
CCCH/PCCCH due to polling succeeded ......................................................... 6-10
6.10 C901000014 Number of GPRS DL TBF establishment success on
CCCH/PCCCH ............................................................................................... 6-12
6.11 C901000015 Number of GPRS DL TBF normal release .................................... 6-14
6.12 C901000023 Number of EGPRS DL TBF resumption in delay state................... 6-15
6.13 C901000027 Number of EGPRS DL TBF establishment failure on PACCH due
to time out ...................................................................................................... 6-16
XVIII
6.14 C901000028 Number of EGPRS DL TBF establishment failure on PACCH due
to other reasons ............................................................................................. 6-17
6.15 C901000031 Number of EGPRS DL TBF establishment failure on
CCCH/PCCCH due to time out ........................................................................ 6-18
CCCH/PCCCH due to other reasons................................................................ 6-19
6.17 C901000033 Number of EGPRS DL TBF establishment execution on
CCCH/PCCCH ............................................................................................... 6-19
6.18 C901000034 Number of EGPRS DL TBF establishment execution failure on
CCCH/PCCCH due to polling failed ................................................................. 6-21
6.19 C901000035 Number of EGPRS DL TBF establishment execution success on
CCCH/PCCCH due to polling succeeded ......................................................... 6-23
6.20 C901000036 Number of EGPRS DL TBF establishment success on
CCCH/PCCCH ............................................................................................... 6-25
6.21 C901000037 Number of EGPRS DL TBF normal release.................................. 6-27
6.22 C901000045 Time of GPRS DL TBF connection .............................................. 6-28
6.23 C901000046 Time of EGPRS DL TBF connection ............................................ 6-29
6.24 C901000047 Time of DL signaling TBF connection........................................... 6-30
6.25 C901000048 Max number of GPRS DL TBF simultaneous establishment .......... 6-30
6.26 C901000050 Max number of EGPRS DL TBF simultaneous establishment ........ 6-31
6.27 C901000052 Number of GPRS DL signaling TBF normal release ...................... 6-31
6.28 C901000058 Number of EGPRS DL signaling TBF normal release.................... 6-33
Chapter 7 Uplink Data TBF Measurement ................................................ 7-1

7.1 Overview ........................................................................................................... 7-2
7.2 C901010001 Number of GPRS UL TBF resumption in extend uplink state ............. 7-2
7.3 C901010002 Number of GPRS UL TBF resource reassign in delay uplink state ..... 7-3
7.4 C901010006 Number of GPRS establishment failure on PACCH due to time
out................................................................................................................... 7-4
7.5 C901010007 Number of GPRS establishment failure on PACCH due to other
reasons............................................................................................................ 7-5
7.6 C901010010 Number of GPRS UL TBF establishment failure on CCCH/PCCCH
due to competition solving failed ........................................................................ 7-6
due to not receive resource request ................................................................... 7-7
due to other reasons ......................................................................................... 7-8
7.9 C901010013 Number of GPRS UL TBF establishment success on
CCCH/PCCCH ................................................................................................. 7-9
7.10 C901010014 Number of GPRS UL TBF normal release .....................................7-11
XIX
7.11 C901010022 Number of EGPRS UL TBF resumption in extend uplink state ....... 7-12
7.12 C901010023 Number of EGPRS UL TBF resource reassign in delay uplink
state .............................................................................................................. 7-13
7.13 C901010027 Number of EGPRS establishment failure on PACCH due to time
out................................................................................................................. 7-13
7.14 C901010028 Number of EGPRS establishment failure on PACCH due to other
reasons.......................................................................................................... 7-14
7.15 C901010031 Number of EGPRS UL TBF establishment failure on
CCCH/PCCCH due to competition solving failed............................................... 7-15
CCCH/PCCCH due to not receive resource request.......................................... 7-16
CCCH/PCCCH due to other reasons................................................................ 7-17
7.18 C901010034 Number of EGPRS UL TBF establishment success on
CCCH/PCCCH ............................................................................................... 7-18
7.19 C901010035 Number of EGPRS UL TBF normal release.................................. 7-20
7.20 C901010043 Time of GPRS UL TBF connection .............................................. 7-21
7.21 C901010044 Time of EGPRS UL TBF connection ............................................ 7-22
7.22 C901010045 Time of UL signaling TBF connection........................................... 7-22
7.23 C901010046 Max number of GPRS UL TBF simultaneous establishment .......... 7-23
7.24 C901010048 Max number of EGPRS UL TBF simultaneous establishment ........ 7-23
7.25 C901010050 Number of GPRS UL signaling TBF normal release ...................... 7-24
7.26 C901010056 Number of EGPRS UL signaling TBF normal release.................... 7-25
Chapter 8 Data Flow Measurement........................................................... 8-1

8.1 Overview ........................................................................................................... 8-1
8.2 C901020001 Number of Kbytes of IP packet sent to BIPB .................................... 8-2
8.3 C901020002 Number of packets sent to BIPB...................................................... 8-2
8.4 C901020003 Number of Kbytes of IP packet received from BIPB .......................... 8-3
8.5 C901020004 Number of packets received from BIPB ........................................... 8-4
8.6 C901020005 Number of Kbytes of IP packet sent to GIPB .................................... 8-5
8.7 C901020006 Number of packets sent to GIPB ..................................................... 8-6
8.8 C901020007 Number of Kbytes of IP packet received from GIPB .......................... 8-7
8.9 C901020008 Number of packets received from GIPB ........................................... 8-7
8.10 C901020009 Number of Kbytes carried by EGPRS DL LLC frame....................... 8-8
8.11 C901020014 Number of Kbytes carried by DL signaling LLC frame...................... 8-9
8.12 C901020019 Number of Kbytes carried by UL LLC frame ................................. 8-10
8.13 C901020020 Number of UL LLC frames ...........................................................8-11
8.14 C901020021 Number of Bytes of GPRS DL TBF LLC frame ..............................8-11
XX
8.15 C901020022 Number of Bytes of EGPRS DL TBF LLC frame ........................... 8-12
8.16 C901020023 Number of Bytes of DL signaling TBF LLC frame.......................... 8-13
8.17 C901020024 Number of Bytes of UL GPRS TBF LLC frame ............................. 8-14
8.18 C901020025 Number of Bytes of EGPRS UL TBF LLC frame ........................... 8-15
8.19 C901020026 Number of Bytes of UL signaling TBF LLC frame.......................... 8-16
8.20 C901020031 Number of GPRS UL data TBF completion .................................. 8-16
8.21 C901020034 Number of GPRS DL data TBF completion .................................. 8-17
8.22 C901020041 Number of EGPRS UL data TBF completion ................................ 8-18
8.23 C901020044 Number of EGPRS DL data TBF completion ................................ 8-19
8.24 C901020050 Number of Kbytes carried by GPRS DL LLC frame ....................... 8-20
Chapter 9 Uplink-Downlink RLC Statistic Measurement ........................ 9-1

9.1 Overview ........................................................................................................... 9-1
9.2 C901030041 Bytes of GPRS DL RLC lost on PDTCH........................................... 9-3
9.3 C901030042 Bytes of EGPRS DL RLC lost on PDTCH......................................... 9-4
9.4 C901030083 Number of UL RLC Blocks lost ........................................................ 9-4
9.5 C901030084 Bytes of GPRS UL RLC lost on PDTCH........................................... 9-5
9.6 C901030085 Bytes of EGPRS UL RLC lost on PDTCH......................................... 9-5
9.7 C901030086 Number of standstill of GPRS UL TBF receiving window ................... 9-6
9.8 C901030087 Number of standstill of EGPRS UL TBF receiving window................. 9-7
9.9 C901030088 Number of standstill of GPRS DL TBF sending window..................... 9-8
9.10 C901030089 Number of standstill of EGPRS DL TBF sending window ................ 9-8
9.11 C901030090 Number of increment of DL coding mode ....................................... 9-9
9.12 C901030091 Number of decrement of DL coding mode .....................................9-11
9.13 C901030092 Number of increment of UL coding mode ..................................... 9-12
9.14 C901030093 Number of decrement of UL coding mode .................................... 9-13
9.15 C901030094 Number of conversion from GMSK to 8PSK ................................. 9-14
9.16 C901030095 Number of conversion from 8PSK to GMSK ................................. 9-16
9.17 C901030153 Number of increment of GPRS DL coding mode ........................... 9-17
9.18 C901030154 Number of decrement of GPRS DL coding mode.......................... 9-18
9.19 C901030155 Number of increment of GPRS UL coding mode ........................... 9-19
9.20 C901030156 Number of decrement of GPRS UL coding mode.......................... 9-20
9.21 C901030157 Number of increment of EGPRS DL coding mode......................... 9-20
9.22 C901030158 Number of decrement of EGPRS DL coding mode........................ 9-21
9.23 C901030159 Number of increment of EGPRS UL coding mode......................... 9-22
9.24 C901030160 Number of decrement of EGPRS UL coding mode........................ 9-22
Chapter 10 PS Resource Used Statistic Measurement......................... 10-1

10.1 Overview ....................................................................................................... 10-2
XXI
10.2 C901040001 Maximum number of Abis TS used .............................................. 10-2
10.3 C901040002 Average number of Abis TS used ................................................ 10-3
10.4 C901040004 Average number of unavailable PDCH......................................... 10-3
10.5 C901040005 Number of available static PDCH................................................. 10-3
10.6 C901040006 Number of unavailable static PDCH............................................. 10-4
10.7 C901040009 Time of DL PDCH congestion...................................................... 10-5
10.8 C901040010 Time of UL PDCH congestion...................................................... 10-5
10.9 C901040011 Time of PDCH used at least one UL/DL TBF exists....................... 10-6
10.10 C901040012 Time of PDCH used at least one UL/DL EGPRS TBF exists ........ 10-7
10.11 C901040013 Time of PDCH used at least one DL TBF exists .......................... 10-8
10.12 C901040014 Time of PDCH used at least one UL TBF exists .......................... 10-9
10.13 C901040018 Number of immediate assignment on AGCH .............................. 10-9
10.14 C901040019 Number of paging PS requests on PCH .................................... 10-11
10.15 C901040020 Number of paging CS requests on PCH .................................... 10-11
10.16 C901040021 Number of immediate assignment on PCH ................................10-12
10.17 C901040022 Number of immediate assignment on PAGCH ...........................10-13
10.18 C901040023 Number of paging PS requests on PPCH ..................................10-14
10.19 C901040024 Number of paging CS requests on PPCH..................................10-15
10.20 C901040025 Number of immediate assignment on PPCH..............................10-16
10.21 C901040026 Number of Packet Channel Request on PRACH........................10-17
10.22 C901040027 Sum of Abis TS used sampling.................................................10-18
10.23 C901040028 Number of Abis TS used sampling............................................10-18
10.24 C901040029 Sum of PDCH used sampling ...................................................10-19
10.25 C901040030 Number of PDCH used sampling ..............................................10-19
10.26 C901040031 Maximum value of Abis TS used to CS .....................................10-20
10.27 C901040032 Minimum value of Abis TS used to CS ......................................10-20
10.28 C901040033 Total value of the regular sampling used to CS ..........................10-21
10.29 C901040034 Number of sampling of CS .......................................................10-21
10.30 C901040035 Maximum value of Abis TS used to PS......................................10-22
10.31 C901040036 Minimum value of Abis TS used to PS ......................................10-22
10.32 C901040037 Total value of the regular sampling used to PS ..........................10-23
10.33 C901040038 Number of sampling of PS........................................................10-24
10.34 C901040039 MAX CS used number of exclusive ABIS ..................................10-24
10.35 C901040040 MIN CS used number of exclusive ABIS ...................................10-25
10.36 C901040041 MAX PS used number of exclusive ABIS...................................10-25
10.37 C901040042 MIN PS used number of exclusive ABIS....................................10-26
10.38 C901040043 Average Number of GPRS User ...............................................10-26
XXII
10.39 C901040044 Maximum number of GPRS User..............................................10-27
10.40 C901040045 Average Number of EGPRS User .............................................10-27
10.41 C901040046 Maximum number of EDGE User..............................................10-28
10.42 C901040047 Number of assigned uplink radio channels ................................10-28
10.43 C901040048 Number of assigned downlink radio channels ............................10-29
10.44 C901040049 Number of requested uplink radio channels ...............................10-29
10.45 C901040050 Number of requested downlink radio channels...........................10-30
10.46 C901040051 Number of PS channel expand .................................................10-30
10.47 C901040052 Number of PS channel expand perform.....................................10-30
10.48 C901040053 Number of PS channel expand success ....................................10-31
Chapter 11 RMM Assignment Measurement.......................................... 11-1

11.1 Overview.........................................................................................................11-3
11.2 C901050001 Number of general assignment executions for voice channel ..........11-3
11.3 C901050002 Number of assignments attempts for voice due to forced
release............................................................................................................11-4
11.4 C901050003 Number of assignment executions for voice channel due to
forced release .................................................................................................11-5
11.5 C901050004 Number of handover attempts for voice due to forced release.........11-6
11.6 C901050005 Number of handover executions for voice channel due to forced
release............................................................................................................11-7
11.7 C901050006 Number of assignments for voice channel due to queuing ..............11-8
11.8 C901050007 Number of assignments for execution for voice channel due to
queuing......................................................................................................... 11-10
11.9 C901050008 Duration of assignment success voice channel due to queuing...... 11-11
11.10 C901050009 Number of assignments success for voice channel due to
queuing......................................................................................................... 11-12
11.11 C901050010 Number of assignments for directed retry attempts for voice
channel......................................................................................................... 11-13
11.12 C901050011 Number of assignments for execution for voice channel due to
directed retry ................................................................................................. 11-14
11.13 C901050012 Number of general assignments for execution for data ............... 11-15
11.14 C901050013 Number of assignments attempts for data due to forced
release.......................................................................................................... 11-16
11.15 C901050014 Number of assignment executions for data due to forced
release.......................................................................................................... 11-17
11.16 C901050015 Number of handover attempts for data due to forced release ...... 11-18
11.17 C901050016 Number of handover executions for data due to forced
release.......................................................................................................... 11-19
11.18 C901050017 Number of assignments attempts for data due to queuing........... 11-20
XXIII
11.19 C901050018 Number of assignments for execution for data due to queuing ...... 11-22
11.20 C901050019 Total duration of successful assignments for data due to
queuing......................................................................................................... 11-23
11.21 C901050020 Number of assignments success for data due to queuing ........... 11-24
11.22 C901050021 Number of assignments attempts for data due to directed
retry.............................................................................................................. 11-24
11.23 C901050022 Number of assignment executions for data due to directed
retry.............................................................................................................. 11-26
11.24 C901050023 Number of assignment for retry attempts FDD cell for voice
channel......................................................................................................... 11-27
11.25 C901050024 Number of assignment executions for data due to directed retry
to FDD cell for voice channel .......................................................................... 11-28
11.26 C901050025 Number of assignment for retry attempts FDD cell for data ......... 11-29
to FDD cell for data........................................................................................ 11-30
11.28 C901050027 Number of assignment for retry attempts TDD cell for voice
channel......................................................................................................... 11-31
to TDD cell for voice channel .......................................................................... 11-33
11.30 C901050029 Number of assignment for retry attempts TDD cell for data ......... 11-34
to TDD cell for data........................................................................................ 11-35
11.32 C901050031 Assignment unsuccessful due to circuit obstruction .................... 11-36
11.33 C901050032 Assignment unsuccessful due to circuit obstruction
unmatched .................................................................................................... 11-37
11.34 C901050033 Assignment unsuccessful due to no valid radio resource ............ 11-38
11.35 C901050034 Assignment unsuccessful due to other causes ........................... 11-39
11.36 C901050035 Number of assignments attempts due to forced release
(emergency service) ...................................................................................... 11-40
11.37 C901050036 Number of assignment executions channel due to forced
release (emergency service) .......................................................................... 11-41
11.38 C901050037 Number of assignment attempts due to forced handover
11.39 C901050038 Number of assignment executions channel due to forced
handover (emergency service) ....................................................................... 11-43
11.40 C901050039 Number of assignments channel due to queuing (emergency
service)......................................................................................................... 11-44
11.41 C901050040 Number of assignments for execution channel due to queuing
XXIV
11.42 C901050041 Number of forced handover target not found (assignment forced
handover) ..................................................................................................... 11-46
11.43 C901050042 Number of send forced handover request to lower PRI user
(assignment forced handover) ........................................................................ 11-47
11.44 C901050043 Number of received failure from lower PRI user request
resource for forced handover (assignment forced handover) ............................ 11-49
11.45 C901050044 Number of lower PRI user handover failure (assignment forced
handover) ..................................................................................................... 11-50
11.46 C901050045 Number of time out for wait resource (assignment forced
handover) ..................................................................................................... 11-51
11.47 C901050046 Number of forced release target not found (assignment forced
release) ........................................................................................................ 11-52
11.48 C901050047 Number of time out for wait resource (assignment forced
release) ........................................................................................................ 11-53
11.49 C901050048 Number of get before grab released channel (assignment
forced handover) ........................................................................................... 11-54
11.50 C901050049 Number of get before grab released channel(assignment forced
release) ........................................................................................................ 11-55
11.51 C901050050 The count of Assignment using FULL IP A-Interface................... 11-56
11.52 C901050051 The count of Assignment using PCM over IP A-Interface............ 11-57
11.53 C901050052 The count of Assignment using PCM over TDM A-Interface ....... 11-58
11.54 C901050053 The count of Assignment Failure caused by "Requested Codec
Type or Codec Configuration not supported".................................................... 11-59
11.55 C901050054 The count of Assignment Failure caused by "Requested Codec
Type or Codec Configuration unavailable" ....................................................... 11-60
11.56 C901050055 The count of Assignment Failure caused by "Requested
A-Interface Type not supported"...................................................................... 11-61
A-Interface Type unavailable" ......................................................................... 11-62
11.58 C901050057 The count of Assignment Failure caused by "Call Identifier
already allocated" .......................................................................................... 11-63
Redundancy Level not supported" .................................................................. 11-64
11.60 C901050059 The count of Assignment Failure caused by "Call Access
Control"......................................................................................................... 11-65
11.61 C901050060 Attempt Number of mode modify for assignment ........................ 11-66
11.62 C901050061 Success Number of mode modify for assignment....................... 11-67
Chapter 12 Handover Cause Measurement ........................................... 12-1

12.1 Overview ....................................................................................................... 12-3
12.2 C901060001 Number of handover attempts due to directed retry....................... 12-3
XXV
12.3 C901060002 Number of SDCCH handover attempts due to UL received
strength ........................................................................................................ 12-4
12.4 C901060003 Number of SDCCH handover attempts due to DL received
strength ......................................................................................................... 12-5
12.5 C901060004 Number of SDCCH Handover attempt due to UL quality ............... 12-6
12.6 C901060005 Number of SDCCH Handover attempt due to DL quality................ 12-7
12.7 C901060006 Number of SDCCH handover attempts due to UL interference ...... 12-8
12.8 C901060007 Number of SDCCH handover attempts due to DL interference ...... 12-9
12.9 C901060008 Number of SDCCH inter-subcell handover attempts due to good
C/I ................................................................................................................12-10
12.10 C901060009 Number of SDCCH inter-subcell handover attempts due to bad
C/I ................................................................................................................ 12-11
12.11 C901060010 Number SDCCH of handover attempts due to PBGT..................12-12
12.12 C901060011 Number of SDCCH handover attempts due to large TA .............12-13
12.13 C901060012 Number of SDCCH handover attempts due to quick break up of
UL ................................................................................................................12-14
12.14 C901060013 Number of SDCCH handover attempts due to macro-micro
switch ..........................................................................................................12-15
12.15 C901060014 Number of SDCCH handover attempts due to MSC request ......12-16
12.16 C901060015 Number of SDCCH handover attempts due to traffic ..................12-17
12.17 C901060016 Number of SDCCH handover attempts due to large TA and
wastage ........................................................................................................12-18
12.18 C901060017 Number of SDCCH handover attempts due to small TA and
wastage ........................................................................................................12-19
12.19 C901060018 Number of SDCCH Handover attempt due to a preferable
electricity level of 3G adjacent cell ..................................................................12-20
12.20 C901060019 Number SDCCH handover attempts due to forced transfer.........12-21
12.21 C901060020 Number of SDCCH handover during assignment due to forced
transfer .........................................................................................................12-22
12.22 C901060021 Number of SDCCH handover during handover due to forced
transfer ........................................................................................................12-23
12.23 C901060022 Number of SDCCH handover attempts due to increased TA ......12-25
12.24 C901060023 Number of SDCCH handover attempts due to TA decrease........12-26
12.25 C901060024 Number of SDCCH Handover attempt due to other factors ........12-27
12.26 C901060035 Number of TCH/F handover attempts due to quick break up of
UL ................................................................................................................12-27
12.27 C901060036 Number of TCH/F handover attempts due to macro-micro
switch ...........................................................................................................12-28
12.28 C901060037 Number of TCH/F handover attempts due to MSC request .........12-29
12.29 C901060038 Number of TCH/F handover attempts due to traffic ....................12-30
XXVI
12.30 C901060039 Number of TCH/F handover attempts due to large TA and
wastage ........................................................................................................12-31
12.31 C901060040 Number of TCH/F handover attempts due to small TA and
wastage ........................................................................................................12-32
12.32 C901060041 Number of TCH/F handover attempts due to preferable
electricity level in 3G adjacent cell ..................................................................12-33
12.33 C901060042 Number of TCH/F handover attempts due to forced transfer .......12-34
12.34 C901060043 Number of TCH/F handover during assignment due to forced
transfer .........................................................................................................12-35
12.35 C901060044 Number of TCH/F handover attempts during handover due to
forced transfer ...............................................................................................12-36
12.36 C901060045 Number of TCH/F handover attempts due to TA increase ...........12-38
12.37 C901060046 Number of TCH/F handover attempts due to TA decrease..........12-39
12.38 C901060058 Number of TCH/H handover attempts due to quick break up of
UL ................................................................................................................12-40
12.39 C901060059 Number of TCH/H handover attempts due to macro-micro
switch ...........................................................................................................12-41
12.40 C901060060 Number of TCH/H handover attempts due to MSC request.........12-42
12.41 C901060061 Number of TCH/H handover attempts due to traffic ....................12-43
12.42 C901060062 Number of TCH/H handover attempts due to large TA and
wastage ........................................................................................................12-44
12.43 C901060063 Number of TCH/H handover attempts due to small TA and
wastage ........................................................................................................12-45
12.44 C901060064 Number of TCH/H handover attempts due to a preferable
electricity level in 3G adjacent cell ..................................................................12-46
12.45 C901060065 Number of TCH/H handover attempts due to forced transfer.......12-47
12.46 C901060066 Number of TCH/H handover attempts during assignment due to
forced transfer ...............................................................................................12-48
12.47 C901060067 Number of TCH/H handover attempts during handover due to
forced transfer ...............................................................................................12-49
TA increase ...................................................................................................12-51
TA decrease..................................................................................................12-52
12.50 C901060070 Number of TCH/H handover attempts due to other reasons........12-53
12.51 C901060071 Number of TCH/F handover attempts due to CS channel
transfer .........................................................................................................12-53
12.52 C901060072 Number of TCH/H handover attempts due to CS channel
transfer .........................................................................................................12-54
XXVII
12.53 C901060073 Number of TCH/H handover attempts due to Fragment
reorganization ...............................................................................................12-56
12.54 C901060074 Number of TCH/F handover attempts due to energy
conservation..................................................................................................12-57
12.55 C901060075 Number of TCH/F handover attempts due to energy
conservation..................................................................................................12-58
12.56 C901060076 Number of TCH/F handover attempts due to CS channel is
forced release ...............................................................................................12-59
12.57 C901060077 Number of TCH/H handover attempts due to CS channel is
forced release ...............................................................................................12-60
12.58 C901060078 Number of TCH/F handover attempts due to FR to HR during
cell busy .......................................................................................................12-61
12.59 C901060079 Number of SDCCH handover attempts due to downlink rapid
drop..............................................................................................................12-62
12.60 C901060080 Number of TCH/F handover attempts due to downlink rapid
drop..............................................................................................................12-62
12.61 C901060081 Number of TCH/H handover attempts due to downlink rapid
drop..............................................................................................................12-63
Chapter 13 RMM Call Drop Measurement .............................................. 13-1

13.1 Overview ....................................................................................................... 13-3
13.2 C901070001 Number of SDCCH drops due to loss of contact with RANA .......... 13-3
13.3 C901070002 Number of SDCCH drops due to radio link failure ......................... 13-4
13.4 C901070003 Number of SDCCH drops due to LAPD link failure ........................ 13-5
13.5 C901070004 Number of SDCCH drops due to OMC-R forced release ............... 13-6
13.6 C901070005 Number of SDCCH drops due to forced release by other calls ....... 13-7
13.7 C901070007 Number of SDCCH drops due to other failure ............................... 13-8
13.8 C901070008 Number of signaling TCH/F drops due to loss of contact with
RANA ............................................................................................................ 13-9
13.9 C901070009 Number of signaling TCH/F drops due to radio link failure ............13-10
13.10 C901070010 Number of signaling TCH/F drops due to LAPD link failure ......... 13-11
13.11 C901070011 Number of signaling TCH/F drops due to OMC-R forced
release..........................................................................................................13-12
13.12 C901070012 Number of signaling TCH/F drops due to forced release by
other calls .....................................................................................................13-13
13.13 C901070014 Number of signaling TCH/F drops due to other failure ................13-14
13.14 C901070015 Number of voice TCH/F drops due to loss of contact with
RANA ...........................................................................................................13-15
13.15 C901070017 Number of voice TCH/F drops due to LAPD link failure ..............13-17
13.16 C901070018 Number of voice TCH/F drops due to OMC-R forced release ......13-19
XXVIII
13.17 C901070019 Number of voice TCH/F drops due to forced release by other
calls..............................................................................................................13-20
13.18 C901070021 Number of voice TCH/F drops due to other failure .....................13-22
13.19 C901070022 Number of data TCH/F drops due to loss of contact with
RANA ...........................................................................................................13-23
13.20 C901070023 Number of data TCH/F drops due to radio link failure .................13-24
13.21 C901070024 Number of data TCH/F drops due to LAPD link failure................13-26
13.22 C901070025 Number of data TCH/F drops due to OMC-R forced release .......13-27
13.23 C901070026 Number of data TCH/F drops due to forced release by other
calls..............................................................................................................13-29
13.24 C901070028 Number of data TCH/F drops due to other failure.......................13-30
13.25 C901070029 Number of signaling TCH/H drops due to loss of contact with
RANA ...........................................................................................................13-31
13.26 C901070030 Number of signaling TCH/H drops due to radio link failure ..........13-33
13.27 C901070031 Number of signaling TCH/H drops due to LAPD link failure.........13-34
13.28 C901070032 Number of signaling TCH/H drops due to OMC-R forced
release..........................................................................................................13-35
13.29 C901070033 Number of signaling TCH/H drops due to forced release by
other calls .....................................................................................................13-36
13.30 C901070035 Number of signaling TCH/H drops due to other failure................13-37
13.31 C901070036 Number of voice TCH/H drops due to loss of contact with
RANA ...........................................................................................................13-38
13.32 C901070038 Number of voice TCH/H drops due to LAPD link failure ..............13-39
13.33 C901070039 Number of voice TCH/H drops due to OMC-R forced release ......13-41
13.34 C901070040 Number of voice TCH/H drops due to forced release by other
calls..............................................................................................................13-42
13.35 C901070042 Number of voice TCH/H drops due to other failure .....................13-44
13.36 C901070043 Number of data TCH/H drops due to loss of contact with
RANA ...........................................................................................................13-45
13.37 C901070044 Number of data TCH/H drops due to radio link failure.................13-46
13.38 C901070045 Number of data TCH/H drops due to LAPD link failure ...............13-48
13.39 C901070046 Number of data TCH/H drops due to OMC-R forced release.......13-49
13.40 C901070047 Number of data TCH/H drops due to forced release by other
calls..............................................................................................................13-51
13.41 C901070049 Number of data TCH/H drops due to other failure ......................13-52
13.42 C901070053 Number of SDCCH link failures ................................................13-54
13.43 C901070054 Number of TCH/F link failures...................................................13-55
13.44 C901070055 Number of TCH/H link failures ..................................................13-57
XXIX
13.45 C901070056 Number of RANA link releases due to other cause on
SDCCH.........................................................................................................13-58
13.46 C901070057 Number of RANA link releases due to other cause on TCH/F ......13-59
13.47 C901070058 Number of RANA link releases due to other cause on TCH/H ......13-60
13.48 C901070059 Number of SDCCH short messages drops ................................13-61
13.49 C901070060 Number of TCH/F short messages drops ..................................13-62
13.50 C901070061 Number of TCH/H short messages drops ..................................13-62
13.51 C901070062 Number of TCH/F drops due to CS channel is forced release by
PS ................................................................................................................13-63
13.52 C901070063 Number of TCH/H drops due to CS channel is forced release by
PS ................................................................................................................13-64
13.53 C901070064 Number of SDCCH drops due to eMLPP forced handover..........13-64
13.54 C901070065 Number of signaling TCH/F drops due to eMLPP forced
handover.......................................................................................................13-65
13.55 C901070066 Number of voice TCH/F drops due to eMLPP forced
handover.......................................................................................................13-66
13.56 C901070067 Number of data TCH/F drops due to eMLPP forced handover ......13-67
13.57 C901070068 Number of sigaling TCH/H drops due to eMLPP forced
handover.......................................................................................................13-68
13.58 C901070069 Number of voice TCH/H drops due to eMLPP forced
handover.......................................................................................................13-69
13.59 C901070070 Number of data TCH/H drops due to eMLPP forced
handover.......................................................................................................13-70
13.60 C901070071 Bad quality of UL receiving (On SDCCH) ..................................13-71
13.61 C901070072 Bad quality of DL receiving (On SDCCH) ..................................13-72
13.62 C901070073 Lower electrical level of UL (On SDCCH) ..................................13-73
13.63 C901070074 Lower electrical level of DL (On SDCCH) ..................................13-74
13.64 C901070075 Number of signaling drops due to TA too far (On SDCCH)..........13-75
13.65 C901070076 Reasons of the other radios (On SDCCH) .................................13-76
13.66 C901070077 Bad quality of UL receiving (On TCH/F) ....................................13-77
13.67 C901070078 Bad quality of DL receiving (On TCH/F) ....................................13-78
13.68 C901070079 Lower electrical level of UL (On TCH/F) ....................................13-79
13.69 C901070080 Lower electrical level of DL (On TCH/F) ....................................13-81
13.70 C901070081 Number of signaling drops due to TA too far (On TCH/F)............13-82
13.71 C901070082 Reasons of the other radios (On TCH/F) ...................................13-84
13.72 C901070083 Bad quality of UL receiving (On TCH/H) ....................................13-85
13.73 C901070084 Bad quality of DL receiving (On TCH/H) ....................................13-87
13.74 C901070085 Lower electrical level of UL (On TCH/H) ....................................13-88
13.75 C901070086 Lower electrical level of DL (On TCH/H) ....................................13-90
XXX
13.76 C901070087 Number of signaling drops due to TA too far (On TCH/H) ...........13-91
13.77 C901070088 Reasons of the other radios (On TCH/H)...................................13-93
13.78 C901070089 The Count of Drop Call caused by "IP Resource Reset" .............13-94
13.79 C901070090 Number of FR_V1 radio link fail ................................................13-95
13.82 C901070093 Number of HR_V1 radio link fail................................................13-97
13.83 C901070094 Number of HR_V3 radio link fail................................................13-97
Chapter 14 Radio Resource Availability Measurement ........................ 14-1

14.1 Overview ....................................................................................................... 14-1
14.2 C901080003 Maximum Number of Busy SDCCHs............................................ 14-1
14.3 C901080004 Average processor load .............................................................. 14-3
14.4 C901080006 SDCCH congestion time ............................................................. 14-4
14.5 C901080008 Number of unavailable defined SDCCH ....................................... 14-5
14.6 C901080011 Maximum number of busy radio channel ...................................... 14-6
14.7 C901080012 Average number of busy radio channel ........................................ 14-7
14.8 C901080014 Average number of busy TCH/H .................................................. 14-8
14.9 C901080016 TCH/H busy time(SpeechVer1).................................................... 14-9
14.10 C901080017 TCH/H busy time(SpeechVer3).................................................14-10
14.11 C901080018 TCH/H congestion time ............................................................14-12
14.12 C901080022 Average number of busy TCH/F ...............................................14-13
14.13 C901080024 TCH/F busy time(SpeechVer1) .................................................14-14
14.16 C901080027 TCH/F congestion time ............................................................14-18
14.17 C901080030 Number of TRXs......................................................................14-20
14.18 C901080032 Reserved TCH/F busy time ......................................................14-21
14.19 C901080033 Maximum number of busy TCH/F .............................................14-22
14.20 C901080034 Cell down time.........................................................................14-22
Chapter 15 General Handover Measurement......................................... 15-1

15.1 Overview ....................................................................................................... 15-8
attempts......................................................................................................... 15-8
15.3 C901090004 Number of MSC-controlled outgoing handover attempts................ 15-9
15.4 C901090005 Number of MSC-controlled outgoing handover request failures
due to unclear factors ....................................................................................15-10
XXXI
due to unavailable ground resource ................................................................ 15-11
due to unavailable radio resource ...................................................................15-12
due to other factors........................................................................................15-13
attempts........................................................................................................15-14
15.9 C901090013 Number of BSC-controlled incoming handover attempts due to
forced release ...............................................................................................15-15
queue ...........................................................................................................15-16
forced handover ............................................................................................15-17
15.12 C901090020 BSC-controlled incoming handover time due to queue ...............15-18
15.13 C901090021 Number of BSC-controlled incoming handover due to queue ......15-20
15.14 C901090022 BSC-controlled incoming handover success time due to
queue ...........................................................................................................15-22
15.15 C901090023 Number of BSC-controlled incoming handover success due to
queue ...........................................................................................................15-23
15.16 C901090024 Number of MSC-controlled incoming handover attempts ............15-24
15.17 C901090025 Number of incoming handover failure due to circuit block ...........15-25
15.18 C901090026 Number of incoming handover failure due to circuit group
mismatch ......................................................................................................15-26
15.19 C901090027 Number of incoming handover failure due to unavailable radio
resource .......................................................................................................15-27
15.20 C901090028 Number of incoming handover failure due to other factors ..........15-28
15.21 C901090030 Number of MSC-controlled incoming handover attempts due to
forced release ...............................................................................................15-29
queue ...........................................................................................................15-30
forced release ...............................................................................................15-31
15.24 C901090037 MSC-controlled incoming handover time due to queue...............15-32
15.25 C901090038 Number of MSC-controlled incoming handover due to queue ......15-35
15.26 C901090039 MSC-controlled incoming handover success time due to
queue ...........................................................................................................15-37
15.27 C901090040 Number of MSC-controlled incoming handover success due to
queue ...........................................................................................................15-38
XXXII
15.28 C901090041 Number of incoming handover attempts from the same layer
and frequency ...............................................................................................15-39
15.29 C901090042 Number of incoming handover success from the same layer
and frequency ...............................................................................................15-40
15.30 C901090043 Number of outgoing handover attempts to the same layer and
frequency......................................................................................................15-41
15.31 C901090044 Number of outgoing handover success to the same layer and
frequency......................................................................................................15-42
15.32 C901090045 Number of incoming handover attempts from undefined layer to
the same frequency .......................................................................................15-43
15.33 C901090046 Number of incoming handover success from undefined layer to
15.34 C901090047 Number of outgoing handover attempts from undefined layer to
15.35 C901090048 Number of outgoing handover success from undefined layer to
15.36 C901090049 Number of incoming handover attempts from undefined layer
(GSM900) to current layer (GSM1800)............................................................15-47
15.37 C901090052 Number of outgoing handover attempts from current layer
(GSM900) to undefined layer (GSM1800)........................................................15-48
15.38 C901090053 Number of outgoing handover from current layer (GSM900) to
undefined layer (GSM1800)............................................................................15-49
15.39 C901090054 Number of outgoing handover success from current layer
(GSM900) to undefined layer (GSM1800)........................................................15-50
15.40 C901090055 Number of incoming handover attempts from undefined layer
15.41 C901090058 Number of outgoing handover attempts from undefined layer
15.42 C901090059 Number of outgoing handover from undefined layer (GSM1800)
to current layer (GSM900) ..............................................................................15-53
15.43 C901090060 Number of outgoing handover success from undefined layer
15.44 C901090061 Number of incoming handover attempts from upper layer to the
same frequency.............................................................................................15-55
15.45 C901090062 Number of incoming handover success from upper layer to the
same frequency.............................................................................................15-56
15.46 C901090063 Number of outgoing handover attempts from the same
frequency to upper layer.................................................................................15-57
15.47 C901090064 Number of outgoing handover success from the same
frequency to upper layer.................................................................................15-58
XXXIII
15.48 C901090065 Number of incoming handover attempts from lower layer to the
same frequency.............................................................................................15-59
15.49 C901090066 Number of incoming handover success from lower layer to the
same frequency.............................................................................................15-60
15.50 C901090067 Number of outgoing handover attempts from the same
frequency to lower layer .................................................................................15-61
15.51 C901090068 Number of outgoing handover success from the same
frequency to lower layer .................................................................................15-62
15.52 C901090069 Number of incoming handover attempts from the same layer
GSM900 to GSM1800....................................................................................15-63
15.53 C901090072 Number of outgoing handover attempts to the same layer
GSM900 to GSM1800....................................................................................15-64
15.54 C901090073 Number of outgoing handover to the same layer GSM900 to
GSM1800 .....................................................................................................15-65
15.55 C901090074 Number of outgoing handover success to the same layer
GSM900 to GSM1800....................................................................................15-66
15.56 C901090075 Number of incoming handover attempts from GSM900 to
GSM1800 from the upper layer.......................................................................15-67
15.57 C901090078 Number of outgoing handover attempts from GSM900 to
GSM1800 to the upper layer...........................................................................15-68
15.58 C901090079 Number of outgoing handover from GSM900 to GSM1800 to
the upper layer ..............................................................................................15-69
15.59 C901090080 Number of outgoing handover success from GSM900 to
GSM1800 to the upper layer...........................................................................15-70
GSM1800 from the lower layer .......................................................................15-71
GSM1800 from the lower layer .......................................................................15-72
15.62 C901090085 Number of outgoing handover from GSM900 to GSM1800 in
the lower layer...............................................................................................15-73
GSM1800 in the lower layer ...........................................................................15-74
15.66 C901090091 Number of outgoing handover from GSM1800 to GSM900 from
the same layer...............................................................................................15-77
XXXIV
GSM900 from the upper layer.........................................................................15-79
GSM900 to the upper layer ............................................................................15-80
the upper layer ..............................................................................................15-81
GSM900 to the upper layer ............................................................................15-82
GSM900 from the lower layer .........................................................................15-83
GSM900 to the lower layer .............................................................................15-84
the lower layer...............................................................................................15-85
GSM900 to the lower layer .............................................................................15-86
15.76 C901090105 Number of intra-cell handover attempts.....................................15-87
15.77 C901090108 Number of intra-cell inner-circle-to-outer-circle handover
attempts........................................................................................................15-88
15.78 C901090109 Number of intra-cell inner-circle-to-outer-circle handover
success ........................................................................................................15-89
15.79 C901090110 Number of intra-cell outer-circle-to-inner-circle handover
attempts........................................................................................................15-90
15.80 C901090111 Number of intra-cell outer-circle-to-inner-circle handover
success ........................................................................................................15-91
15.81 C901090112 Number of intra-cell inner-circle-to-inner-circle handover
attempts........................................................................................................15-92
15.82 C901090113 Number of intra-cell inner-circle-to-inner-circle handover
success ........................................................................................................15-93
15.83 C901090114 Number of intra-cell outer-circle-to-outer-circle handover
attempts........................................................................................................15-94
15.84 C901090115 Number of intra-cell outer-circle-to-outer-circle handover
success ........................................................................................................15-95
15.85 C901090116 Number of handover attempts from 2G to 3G.............................15-96
15.86 C901090117 Number of handover from 2G to 3G ..........................................15-97
15.87 C901090118 Number of handover success from 2G to 3G .............................15-98
15.88 C901090119 Number of handover attempts from 3G to 2G.............................15-99
15.89 C901090120 Number of handover from 3G to 2G ........................................15-100
15.90 C901090121 Number of handover success from 3G to 2G ...........................15-100
15.91 C901090122 Number of intra-cell handover attempts from TCH/F ................15-101
XXXV
15.92 C901090123 Number of intra-cell TCH/F-to-TCH/F handover .......................15-102
15.93 C901090124 Number of intra-cell TCH/F-to-TCH/F handover success ..........15-103
15.94 C901090125 Number of intra-cell TCH/F-to-TCH/H handover.......................15-104
15.95 C901090126 Number of intra-cell TCH/F-to-TCH/H handover success..........15-105
15.96 C901090127 Number of intra-cell handover attempts from TCH/H ................15-106
15.97 C901090128 Number of intra-cell TCH/H-to-TCH/F handover.......................15-107
15.98 C901090129 Number of intra-cell TCH/H-to-TCH/F handover success..........15-108
15.99 C901090130 Number of intra-cell TCH/H-to-TCH/H handover ......................15-109
15.100 C901090131 Number of intra-cell TCH/H-to-TCH/H handover success ....... 15-110
15.101 C901090132 Number of inter-cell handover attempts from TCH/F............... 15-111
15.102 C901090133 Number of inter-cell TCH/F-to-TCH/F handover ..................... 15-112
15.103 C901090134 Number of inter-cell TCH/F-to-TCH/F handover success ........ 15-113
15.104 C901090135 Number of inter-cell TCH/F-to-TCH/H handover..................... 15-114
15.105 C901090136 Number of inter-cell TCH/F-to-TCH/H handover success........ 15-115
15.106 C901090137 Number of inter-cell handover attempts from TCH/H .............. 15-116
15.107 C901090138 Number of inter-cell TCH/H-to-TCH/F handover..................... 15-117
15.108 C901090139 Number of inter-cell TCH/H-to-TCH/F handover success........ 15-118
15.109 C901090140 Number of inter-cell TCH/H-to-TCH/H handover .................... 15-119
15.110 C901090141 Number of inter-cell TCH/H-to-TCH/H handover success........15-120
15.111 C901090142 Total dual-band outgoing handover attempts ..........................15-121
15.112 C901090145 Number of dual band incoming handover attempts .................15-122
15.113 C901090148 Number of intra-cell invalid handovers ...................................15-123
attempts due to forced release (emergency service) ......................................15-124
(forced release) (emergency service) ............................................................15-125
attempts due to forced handover (emergency service) ...................................15-126
(forced handover) (emergency service) .........................................................15-127
attempts due to queue (emergency service) ..................................................15-129
(queue) (emergency service) ........................................................................15-130
15.120 C901090155 Number of MSC-controlled incoming handover attempts due
to forced release (emergency service)...........................................................15-131
15.121 C901090156 Number of MSC-controlled incoming handover (forced
release) (emergency service) .......................................................................15-132
XXXVI
15.122 C901090157 Number of MSC-controlled inter-cell incoming handover
attempts due to forced handover (emergency service) ...................................15-133
15.123 C901090158 Number of MSC-controlled incoming handover (forced
release) (emergency service) .......................................................................15-134
15.124 C901090159 Number of MSC-controlled incoming handover attempts due
to queue (emergency service) ......................................................................15-135
15.125 C901090160 Number of MSC-controlled incoming handover (queue)
(emergency service) ....................................................................................15-136
15.126 C901090161 Number of forced handover target not found (BSC-controlled
inter-cell handover due to forced handover)...................................................15-137
(BSC-controlled inter-cell handover due to forced handover) ..........................15-138
15.128 C901090163 Number of recv failure from lower PRI user request resource
for forced handover (BSC-controlled inter-cell handover due to forced
handover) ...................................................................................................15-139
15.129 C901090164 Number of lower PRI user handover failure (BSC-controlled
inter-cell handover due to forced handover)...................................................15-141
15.130 C901090165 Number of high PRI user time out for wait resource
(BSC-controlled inter-cell handover due to forced handover) ..........................15-142
15.131 C901090166 Number of forced release target not found (BSC-controlled
inter-cell handover due to forced release)......................................................15-143
(BSC-controlled inter-cell handover due to forced release) .............................15-145
15.133 C901090168 Number of HO Target not found (MSC-controlled incoming
handover due to forced handover) ................................................................15-146
(MSC-controlled incoming handover due to forced handover) .........................15-147
15.135 C901090170 Number of failure to lower PRI user request resource for forced
handover (MSC-controlled incoming handover due to forced handover) ..........15-148
15.136 C901090171 Number of lower PRI user handover failure (MSC-controlled
incoming handover due to forced handover) ..................................................15-148
(MSC-controlled incoming handover due to forced handover) .........................15-149
15.138 C901090173 Number of forced release target not found (MSC-controlled
incoming handover due to forced release) .....................................................15-150
(MSC-controlled incoming handover due to forced release) ............................15-150
forced handover) .........................................................................................15-151
forced release) ............................................................................................15-152
XXXVII
15.142 C901090177 Number of handover attempts due to eMLPP forced
handover.....................................................................................................15-152
15.143 C901090178 Number of handover due to eMLPP forced handover .............15-153
15.144 C901090179 Number of handover success due to eMLPP forced
handover.....................................................................................................15-153
attempts between PLMN ..............................................................................15-154
between PLMN............................................................................................15-154
success between PLMN...............................................................................15-154
15.148 C901090183 Number of MSC-controlled outgoing handover attempts
between PLMN............................................................................................15-154
15.149 C901090184 Number of MSC-controlled outgoing handover request fail
between PLMN due to unknown reason ........................................................15-154
between PLMN due to unavailable ground resource ......................................15-155
between PLMN due to unavailable radio resource .........................................15-156
between PLMN due to other reasons ............................................................15-156
15.153 C901090188 Number of MSC-controlled outgoing handover between
PLMN .........................................................................................................15-156
15.154 C901090189 Number of MSC-controlled outgoing handover success
between PLMN............................................................................................15-158
attempt between PLMN................................................................................15-158
between PLMN............................................................................................15-158
force-release attempt between PLMN ...........................................................15-158
between PLMN due to force release .............................................................15-159
15.159 C901090194 Number of BSC-controlled inter-cell incoming handover queue
between PLMN due to queue .......................................................................15-159
force-handover attempt between PLMN ........................................................15-159
between PLMN due to force handover ..........................................................15-159
XXXVIII
success between PLMN...............................................................................15-159
15.164 C901090199 Number of MSC-controlled incoming handover attempt
between PLMN ...........................................................................................15-160
15.165 C901090200 A interface incoming handover fail between PLMN due to
circuit block .................................................................................................15-161
circuit unmatch ............................................................................................15-162
unavailable radio resource ...........................................................................15-162
other reason................................................................................................15-163
15.169 C901090204 Number of MSC-controlled incoming handover between
PLMN .........................................................................................................15-163
15.170 C901090205 Number of MSC-controlled incoming handover force-release
15.171 C901090206 Number of MSC-controlled incoming handover between PLMN
due to force release .....................................................................................15-164
15.172 C901090207 Number of MSC-controlled incoming handover queue attempt
between PLMN............................................................................................15-164
due to queue ...............................................................................................15-165
15.174 C901090209 Number of MSC-controlled incoming handover force-handover
due to force handover ..................................................................................15-167
15.176 C901090211 Number of MSC-controlled incoming handover success
between PLMN ...........................................................................................15-167
15.177 C901090212 Number of handover due to Fragment reorganization.............15-167
15.178 C901090213 Number of handover success due to Fragment
reorganization .............................................................................................15-167
Chapter 16 Adjacent Cell Handover Measurement ............................... 16-1

16.1 Overview ....................................................................................................... 16-2
16.2 C901100001 Number of handover attempts on the adjacent cell........................ 16-2
16.3 C901100002 Number of handover success from selected cell to the adjacent
cell................................................................................................................. 16-3
16.4 C901100003 Number of handover attempts from adjacent cell to the selected
cell................................................................................................................. 16-4
16.5 C901100004 Number of handover success from adjacent cell to the selected
cell................................................................................................................. 16-6
XXXIX
16.6 C901100005 Number of handover attempts from selected cell to the adjacent
cell due to better UL quality. ............................................................................ 16-7
cell due to better DL quality. ............................................................................ 16-8
cell due to better UL quality. ...........................................................................16-10
cell due to better DL quality. ........................................................................... 16-11
cell due to better UL strength..........................................................................16-12
cell due to better DL strength..........................................................................16-14
cell due to better UL strength..........................................................................16-15
cell due to better DL strength..........................................................................16-16
cell due to PBGT ...........................................................................................16-18
cell due to PBGT ...........................................................................................16-19
cell due to other factors. .................................................................................16-20
16.17 C901100016 Number of successful handover from selected cell to the
adjacent cell due to other factors. ...................................................................16-21
16.18 C901100017 Number of pingpong handover (handover to source cell) ............16-23
16.19 C901100018 The max of RTD ......................................................................16-24
16.20 C901100019 The sum of RTD ......................................................................16-25
16.21 C901100020 The number of RTD .................................................................16-26
Chapter 17 Radio Access Measurement ................................................ 17-1

17.1 Overview ....................................................................................................... 17-1
17.2 C901110001 Number of invalid access requests............................................... 17-2
17.3 C901110003 Number of MOC access success for processes ............................ 17-3
17.4 C901110006 Number of MTC access success for processes ............................. 17-3
17.5 C901110008 Number of call re-establishment access attempts.......................... 17-4
17.6 C901110009 Number of call re-establishment access success for processes ..... 17-5
17.7 C901110010 Number of call re-establishment access success .......................... 17-5
17.8 C901110011 Number of emergency calls access attempts ................................ 17-6
17.9 C901110012 Number of emergency calls access success for processes ............ 17-6
17.10 C901110013 Number of emergency calls access success ............................... 17-7
XL
17.11 C901110014 Number of LOC access attempts................................................ 17-8
17.12 C901110015 Number of LOC access success for processes ........................... 17-8
17.13 C901110016 Number of LOC access success ................................................ 17-9
17.14 C901110017 Number of other causes access attempts ................................... 17-9
17.15 C901110018 Number of successful random access processes for other
causes ..........................................................................................................17-10
17.16 C901110019 Number of other causes access success ...................................17-10
17.17 C901110020 Number of LMU Establishment Access attempts ........................ 17-11
17.18 C901110021 Number of LMU Establishment access success for
processes .....................................................................................................17-12
17.19 C901110022 Number of LMU Establishment access success .........................17-12
17.20 C901110023 Number of accesses due to location update...............................17-13
17.21 C901110024 Number of Access due to CM SERVICE REQ............................17-13
17.22 C901110026 Number of CM service requests of Emergency Call ....................17-14
17.23 C901110027 Number of CM service requests of SMS ....................................17-15
17.24 C901110028 Number of CM service requests of Supplement..........................17-15
17.25 C901110029 Number of CM service requests of LCS .....................................17-16
17.26 C901110031 Number of wireless access due to call re-establishments............17-16
17.27 C901110032 Number of wireless accesses due to IMSI detachment ...............17-17
17.28 C901110033 Number of wireless accesses due to other causes .....................17-17
Chapter 18 Radio Measurement.............................................................. 18-1

18.1 Overview ....................................................................................................... 18-2
18.2 C901120001 Number of UL signal quality samples in wireless channels ............ 18-2
18.3 C901120002 Level of worst UL signal quality in wireless channels..................... 18-3
18.4 C901120003 Total value of UL quality level values in wireless channels ............. 18-3
18.5 C901120004 Number of DL signal quality samples in wireless channels ............ 18-4
18.6 C901120005 Level of worst DL signal quality in wireless channels..................... 18-4
18.7 C901120006 Total value of DL quality strength values in wireless channels........ 18-5
18.8 C901120007 Number of received UL signal strength samples in wireless
channels ........................................................................................................ 18-6
18.9 C901120008 Maximum received UL signal strength in wireless channels ........... 18-6
18.10 C901120009 Minimum received UL signal strength in wireless channels .......... 18-7
18.11 C901120010 Total value of UL signal strength in wireless channels.................. 18-7
18.12 C901120011 Number of received DL signal strength samples in wireless
channels ........................................................................................................ 18-8
18.13 C901120012 Maximum received DL signal strength in wireless channels ......... 18-9
18.14 C901120013 Minimum DL received signal strength in radio channels............... 18-9
18.15 C901120014 Total value of DL signal strength in wireless channels ................18-10
XLI
18.16 C901120015 Number of TA samples in wireless channels ..............................18-10
18.17 C901120016 Maximum TA in wireless channels............................................. 18-11
18.18 C901120017 Total number of TAs in wireless channels .................................. 18-11
18.19 C901120018 Mean number of idle TCH/Fs with interference band 0 ...............18-12
18.20 C901120024 Mean number of idle TCH/Hs with interference band 0 ...............18-13
18.21 C901120030 Mean number of idle SDCCHs with interference band 0 .............18-13
18.27 C901120052 Number of TFO initiations.........................................................18-16
18.28 C901120053 Number of using noise suppression ..........................................18-17
18.29 C901120054 Number of mode changes for establishing TFO .........................18-17
18.30 C901120055 Number of mode changes for optimizing TFO ............................18-18
18.31 C901120056 Number of active collection changes for establishing TFO ..........18-18
18.32 C901120057 Number of active collection changes for optimizing TFO.............18-18
18.33 C901120058 Number of samples with voice quality is excellent ......................18-19
18.34 C901120059 Number of samples with voice quality is good ............................18-19
18.35 C901120060 Number of samples with voice quality is medium........................18-20
18.36 C901120061 Number of samples with voice quality is bad..............................18-20
18.37 C901120062 Number of samples with voice quality is awfully .........................18-21
18.38 C901120063 Number of uplink error frame on FR_V1 ....................................18-22
18.39 C901120064 Total Number of uplink frame on FR_V1 ....................................18-22
18.44 C901120069 Number of uplink error frame on HR_V1....................................18-24
18.45 C901120070 Total Number of uplink frame on HR_V1....................................18-24
18.46 C901120071 Number of uplink error frame on HR_V3....................................18-25
18.47 C901120072 Total Number of uplink frame on HR_V3....................................18-25
Chapter 19 Sub Cell Statistics................................................................. 19-1

19.1 Overview ....................................................................................................... 19-3
19.2 C901130001 Number of available TCH/Fs in the second sub cell ...................... 19-4
19.3 C901130002 Number of unavailable TCH/Fs in the second sub cell................... 19-4
19.4 C901130003 Number of available TCH/Hs in the second sub cell ...................... 19-5
XLII
19.5 C901130004 Number of unavailable TCH/Hs in the second sub cell .................. 19-5
19.6 C901130005 Number of handover attempts from the first sub cell to the second
sub cell .......................................................................................................... 19-6
19.7 C901130006 Number of handover execution from the first sub cell to the
second sub cell .............................................................................................. 19-7
19.8 C901130007 Number of handover success from the first sub cell to the second
sub cell .......................................................................................................... 19-8
19.9 C901130008 Number of handover attempts from the second sub cell to the
first sub cell .................................................................................................... 19-9
19.10 C901130009 Number of handover execution from the second sub cell to the
first sub cell ...................................................................................................19-10
19.11 C901130010 Number of handover success from the second sub cell to the
first sub cell ................................................................................................... 19-11
19.12 C901130011 Number of handover attempts in the second sub cell..................19-12
19.13 C901130012 Number of handover execution in the second sub cell ................19-13
19.14 C901130013 Number of handover success in the second sub cell ..................19-14
19.15 C901130014 Number of outgoing inter-cell handover attempts of the second
sub cell .........................................................................................................19-15
19.16 C901130015 Number of outgoing inter-cell handover execution of the second
sub cell .........................................................................................................19-16
19.17 C901130016 Number of outgoing inter-cell handover success of the second
sub cell .........................................................................................................19-17
19.18 C901130017 Handover attempts due to UL receiving strength of the full rate
second sub cell .............................................................................................19-18
19.19 C901130018 Handover attempts due to DL receiving strength of the full rate
second sub cell .............................................................................................19-19
19.20 C901130019 Handover attempts due to UL quality of the full rate second sub
cell ...............................................................................................................19-20
19.21 C901130020 Handover attempts due to DL quality of the full rate second sub
cell ...............................................................................................................19-21
19.22 C901130021 Handover attempts due to PBGT of the full rate second sub
cell ...............................................................................................................19-22
19.23 C901130022 Handover attempts due to traffic of the full rate second sub
cell ...............................................................................................................19-23
19.24 C901130023 Handover attempts due to UL interference of the full rate second
sub cell (on TCH/F)........................................................................................19-24
19.25 C901130024 Handover attempts due to DL interference of the full rate second
sub cell (on TCH/F)........................................................................................19-25
19.26 C901130025 Handover attempts due to good CI of the full rate second sub
cell (on TCH/F) ..............................................................................................19-26
XLIII
19.27 C901130026 Handover attempts due to bad CI of the full rate second sub cell
(on TCH/F)....................................................................................................19-27
19.28 C901130027 Handover attempts due to path loss and too large TA of the full
rate second sub cell (on TCH/F) .....................................................................19-28
19.29 C901130028 Handover attempts due to path loss and too small TA of the full
rate second sub cell (on TCH/F) .....................................................................19-29
19.30 C901130029 Number of forced transfer handover attempts of the full rate
second sub cell (on TCH/F) ............................................................................19-30
19.31 C901130030 Handover attempts due to other causes of the full rate second
sub cell .........................................................................................................19-32
19.32 C901130031 Handover attempts due to UL receiving strength of the half rate
second sub cell .............................................................................................19-33
19.33 C901130032 Handover attempts due to DL receiving strength of the half rate
second sub cell .............................................................................................19-34
19.34 C901130033 Handover attempts due to UL quality of the half rate second sub
cell ...............................................................................................................19-35
19.35 C901130034 Handover attempts due to DL quality of the half rate second sub
cell ...............................................................................................................19-36
19.36 C901130035 Handover attempts due to PBGT of the half rate second sub
cell ...............................................................................................................19-37
19.37 C901130036 Handover attempts due to traffic of the half rate second sub
cell ...............................................................................................................19-38
19.38 C901130037 Handover attempts due to UL interference of the half rate
second sub cell .............................................................................................19-39
19.39 C901130038 Handover attempts due to DL interference of the half rate
second sub cell .............................................................................................19-40
19.40 C901130039 Handover attempts due to C/I of the half rate second sub cell ......19-41
19.41 C901130040 Handover attempts due to C/I of the half rate second sub cell ......19-42
19.42 C901130041 Handover attempts due to path loss and too large TA of the half
rate second sub cell.......................................................................................19-43
19.43 C901130042 Handover attempts due to path loss and too small TA of the half
rate second sub cell.......................................................................................19-44
19.44 C901130043 Number of forced transfer handover attempts of the half rate
second sub cell .............................................................................................19-45
19.45 C901130044 Handover attempts due to other causes of the half rate second
sub cell .........................................................................................................19-46
19.46 C901130045 Number of attempts of TCH/F seizure of the second sub cell
(used for assignment) ....................................................................................19-47
19.47 C901130046 Number of TCH/F seizure success of the second sub cell (used
for assignment) .............................................................................................19-48
XLIV
19.48 C901130047 Number of TCH/F seizure failure of the second sub cell (used
for assignment) .............................................................................................19-49
19.49 C901130048 Number of attempts of TCH/F seizure of the second sub cell
(used for handover) .......................................................................................19-49
19.50 C901130049 Number of TCH/F seizure success of the second sub cell (used
for handover).................................................................................................19-50
19.51 C901130050 Number of TCH/F seizure failure of the second sub cell (used
for handover).................................................................................................19-51
19.52 C901130051 Number of TCH/H seizure attempts of the second sub cell (used
for assignment) .............................................................................................19-52
19.53 C901130052 Number of TCH/H seizure success of the second sub cell (used
for assignment) .............................................................................................19-53
19.54 C901130053 Number of TCH/H seizure failure of the second sub cell (used
for assignment) .............................................................................................19-54
19.55 C901130054 Number of TCH/H seizure attempts of the second sub cell (used
for handover).................................................................................................19-55
19.56 C901130055 Number of TCH/H seizure success of the second sub cell (used
for handover).................................................................................................19-56
19.57 C901130056 Number of TCH/H seizure failure of the second sub cell (used
for handover).................................................................................................19-56
19.58 C901130057 Number of TCH/F call drops in the second sub cell ....................19-57
19.59 C901130058 Number of TCH/H call drops in the second sub cell....................19-58
19.60 C901130059 TCH/F busy time in the second sub cell.....................................19-59
19.61 C901130060 TCH/H busy time in the second sub cell ....................................19-60
19.62 C901130061 Number of TCH/F assignment attempts of the second sub
cell ...............................................................................................................19-60
19.63 C901130062 Number of TCH/F assignment success of the second sub
cell ...............................................................................................................19-61
19.64 C901130063 Number of TCH/F handover attempts of the second sub cell.......19-62
19.65 C901130064 Number of TCH/F handover success of the second sub cell .......19-63
19.66 C901130065 Number of TCH/H assignment attempts of the second sub
cell ...............................................................................................................19-64
19.67 C901130066 Number of TCH/H assignment success of the second sub
cell ...............................................................................................................19-64
19.68 C901130067 Number of TCH/H handover attempts of the second sub cell ......19-65
19.69 C901130068 Number of TCH/H handover success of the second sub cell .......19-66
19.70 C901130069 TCH/F of the first sub cell seizure success when prefer the
second sub cell (used for assignment) ............................................................19-67
19.71 C901130070 TCH/F of the first sub cell seizure success when prefer the
second sub cell (used for handover) ...............................................................19-68
XLV
19.72 C901130071 TCH/H of the first sub cell seizure success when prefer the
second sub cell (used for assignment) ............................................................19-68
19.73 C901130072 TCH/H of the first sub cell seizure success when prefer the
second sub cell (used for handover) ...............................................................19-69
Chapter 20 MS TA Measurement............................................................. 20-1

20.1 Overview ....................................................................................................... 20-2
20.2 C901140001 Number of TA=0 ......................................................................... 20-2
20.3 C901140002 Number of 0<TA<= 2................................................................... 20-2
20.4 C901140003 Number of 2<TA<=4 ................................................................... 20-3
20.5 C901140004 Number of 4<TA<=6 ................................................................... 20-4
20.6 C901140005 Number of 6<TA<=8 ................................................................... 20-5
20.7 C901140006 Number of 8<TA<=10.................................................................. 20-5
20.8 C901140007 Number of 10<TA<=12................................................................ 20-6
20.9 C901140008 Number of 12<TA<=14................................................................ 20-7
20.10 C901140009 Number of 14<TA<=16 .............................................................. 20-7
20.11 C901140010 Number of 16<TA<=18 .............................................................. 20-8
20.12 C901140011 Number of 18<TA<=20 .............................................................. 20-9
20.13 C901140012 Number of 20<TA<=22 .............................................................. 20-9
20.14 C901060013 Number of 22<TA<=24.............................................................20-10
20.15 C901140014 Number of 24<TA<=26 ............................................................. 20-11
20.16 C901140015 Number of 26<TA<=28 .............................................................20-12
20.17 C901140016 Number of 28<TA<=30 .............................................................20-12
20.18 C901140017 Number of 30<TA<=32 .............................................................20-13
20.19 C901140018 Number of 32<TA<=34 .............................................................20-14
20.20 C901140019 Number of 34<TA<=36 .............................................................20-14
20.21 C901140020 Number of 36<TA<=38 .............................................................20-15
20.22 C901140021 Number of 38<TA<=40 .............................................................20-16
20.23 C901140022 Number of 40<TA<=42 .............................................................20-17
20.24 C901140023 Number of 42<TA<=44 .............................................................20-17
20.25 C901140024 Number 44<TA<=46.................................................................20-18
20.26 C901140025 Number of 46<TA<=48 .............................................................20-19
20.27 C901140026 Number of 48<TA<=50 .............................................................20-19
20.28 C901140027 Number of 50<TA<=52 .............................................................20-20
20.29 C901140028 Number of 52<TA<=54 .............................................................20-21
20.30 C901140029 Number of 54<TA<=56 .............................................................20-22
20.31 C901140030 Number of 56<TA<=58 .............................................................20-22
20.32 C901140031 Number of 58<TA<=60 .............................................................20-23
20.33 C901140032 Number of 60<TA<=63 .............................................................20-24
XLVI
20.34 C901140033 Number of TA>63 ....................................................................20-24
Chapter 21 SAPI3 Measurement ............................................................. 21-1

21.1 Overview ....................................................................................................... 21-2
21.2 C901150001 Number of SAPI3 link establishments on SACCH/F (MO-SM)........ 21-2
21.3 C901150002 Number of SAPI3 link establishments on SACCH/H (MO-SM) ....... 21-3
21.4 C901150004 Number of SAPI3 link establishments on FACCH/F (MO-SM) ........ 21-4
21.5 C901150005 Number of SAPI3 link establishments on FACCH/H (MO-SM)........ 21-5
21.6 C901150006 Number of SAPI3 link establishment requests on SACCH/F
(MT-SM) ........................................................................................................ 21-6
21.7 C901150007 Number of SAPI3 link establishment requests on SACCH/H
(MT-SM) ........................................................................................................ 21-7
21.8 C901150009 Number of SAPI3 link establishment requests on FACCH/F
(MT-SM) ........................................................................................................ 21-8
21.9 C901150010 Number of SAPI3 link establishment requests on FACCH/H
(MT-SM) ........................................................................................................ 21-9
21.10 C901150011 Number of successful SAPI3 link establishments on SACCH/F
(MT-SM) ........................................................................................................ 21-9
21.11 C901150012 Number of successful SAPI3 link establishments on SACCH/H
(MT-SM) ....................................................................................................... 21-11
21.12 C901150014 Number of successful SAPI3 link establishments on FACCH/F
(MT-SM) .......................................................................................................21-12
21.13 C901150015 Number of successful SAPI3 link establishments on FACCH/H
(MT-SM) .......................................................................................................21-12
21.14 C901150016 Number of DTAP messages used as SDCCH UL point-to-point
short messages (SMs) ...................................................................................21-13
21.15 C901150017 Number of DTAP messages used as SDCCH DL point-to-point
short messages (SMs) ...................................................................................21-15
21.16 C901150018 Number of DTAP messages on FACCH/F UL for point-to-point
short messages .............................................................................................21-17
21.17 C901150019 Number of DTAP messages on FACCH/F DL for point-to-point
short messages .............................................................................................21-18
21.18 C901150020 Number of DTAP messages on FACCH/H UL for point-to-point
short messages .............................................................................................21-19
21.19 C901150021 Number of DTAP messages on FACCH/H DL for point-to-point
short messages .............................................................................................21-19
21.20 C901150022 Number of DTAP messages on SACCH/F DL for point-to-point
short messages .............................................................................................21-20
21.21 C901150023 Number of DTAP messages on SACCH/F DL for point-to-point
short messages .............................................................................................21-22
XLVII
21.22 C901150024 Number of DTAP messages on SACCH/H UL for point-to-point
short messages .............................................................................................21-22
21.23 C901150025 Number of DTAP messages on SACCH/H DL for point-to-point
short messages .............................................................................................21-24
Chapter 22 Uplink and Downlink PACCH Statistics .............................. 22-1

22.1 Overview ....................................................................................................... 22-1
22.2 C901160001 Number of Packet access reject message .................................... 22-2
22.3 C901160002 Number of Packet resource request message .............................. 22-2
22.4 C901160003 Number of Packet UL Assignment message ................................. 22-3
22.5 C901160004 Number of Additional MS access capabilities message ................. 22-4
22.6 C901160005 Number of Packet DL Assignment message ................................. 22-5
22.7 C901160006 Number of Packet TBF release message ..................................... 22-6
22.8 C901160007 Number of Packet DL Ack/Nack message .................................... 22-7
22.9 C901160008 Number of EGPRS Packet DL Ack/Nack message........................ 22-8
22.10 C901160009 Number of Packet UL Ack/Nack message .................................. 22-9
22.11 C901160010 Number of Packet Control Acknowledgement message ..............22-10
22.12 C901160011 Number of Packet Cell Change Continue message .................... 22-11
22.13 C901160012 Number of Packet Cell Change Failure message .......................22-12
22.14 C901160013 Number of Packet Cell Change Notification message .................22-13
22.15 C901160014 Number of Packet Cell Change Order message.........................22-14
22.16 C901160017 Number of packet mobile TBF status messages ........................22-15
22.17 C901160018 Number of packet neighbor cell data messages .........................22-16
22.18 C901160019 Number of packet PDCH release messages ..............................22-17
22.19 C901160020 Number of packet polling request messages..............................22-18
22.20 C901160021 Number of packet power control/timing advance messages ........22-18
22.21 C901160022 Number of packet PSI status message......................................22-19
22.22 C901160023 Number of packet serving cell data messages ...........................22-20
22.23 C901160024 Number of packet SI status messages ......................................22-21
22.24 C901160025 Number of packet timeslot reconfigure messages ......................22-22
22.25 C901160026 Number of packet paging request message ...............................22-23
22.26 C901160027 Number of PSI message ..........................................................22-24
Chapter 23 Downlink GPRS Data TBF Statistics ................................... 23-1

23.1 Overview ....................................................................................................... 23-3
CCCH/PCCCH ............................................................................................... 23-3
23.3 C901170003 Number of GPRS DL TBF establishment requests on PACCH ....... 23-4
23.4 C901170004 Number of GPRS DL TBF establishment failure due to CPU.......... 23-5
XLVIII
23.5 C901170005 Number of GPRS DL TBF establishment failure due to not
support DTM .................................................................................................. 23-5
23.6 C901170007 Number of GPRS DL TBF establishment failure due to Abis
congestion ..................................................................................................... 23-5
23.7 C901170008 Number of GPRS DL TBF establishment failure due to RR
congestion ..................................................................................................... 23-6
23.8 C901170009 Number of GPRS DL TBF establishment failure due to
UPPB-DSP channel congestion....................................................................... 23-8
23.9 C901170010 Number of GPRS DL TBF establishment channel allocate
success ......................................................................................................... 23-9
23.10 C901170011 Number of allocated PDCH for GPRS DL TBF establishment ......23-10
23.11 C901170012 Number of GPRS DL TBF establishment failure due to channel
activate failed ................................................................................................ 23-11
23.12 C901170013 Number of GPRS DL TBF establishment failure due to BTS
connection failed ...........................................................................................23-12
23.13 C901170014 Number of GPRS DL TBF establishment failure due to BIU
23.14 C901170015 Number of GPRS DL TBF channel activate establishment
success ........................................................................................................23-14
23.15 C901170016 Number of GPRS DL TBF establishment failure on
CCCH/PCCCH due to not receive PIA ............................................................23-15
23.16 C901170017 Number of GPRS DL TBF establishment failure on
CCCH/PCCCH due to UPPB-DSP congestion .................................................23-16
23.17 C901170018 Number of GPRS DL TBF establishment failure on PACCH due
to UPPB-DSP congestion...............................................................................23-16
23.18 C901170019 Number of GPRS DL TBF establishment success on
PCCCH/CCCH ..............................................................................................23-17
23.19 C901170020 Number of GPRS DL TBF establishment success on PACCH ......23-17
Abis congestion for UL TBF establishment ......................................................23-18
RR congestion for UL TBF establishment ........................................................23-19
UPPB-DSP channel congestion for UL TBF establishment ...............................23-20
23.23 C901170026 Number of GPRS DL TBF resource reallocation success due to
UL TBF establishment ...................................................................................23-21
23.24 C901170027 Number of allocated PDCH for GPRS DL TBF resource
reallocation due to UL TBF establishment .......................................................23-22
channel activate failure for UL TBF establishment............................................23-23
XLIX
BTS connection failure for UL TBF establishment ............................................23-24
BIU connection failure for UL TBF establishment .............................................23-25
23.28 C901170031 Number of GPRS DL TBF resource reallocation success of
channel activate and connection for UL TBF establishment ..............................23-26
Abis congestion for LLC transmission .............................................................23-27
RR congestion for LLC transmission ...............................................................23-29
UPPB-DSP channel congestion for LLC transmission ......................................23-30
23.35 C901170040 Number of allocated PDCH for GPRS DL TBF resource
reallocation due to LLC transmission...............................................................23-32
channel activate failure for LLC transmission ...................................................23-33
BTS connection failure for LLC transmission ...................................................23-34
BIU connection failure for LLC transmission ....................................................23-35
23.39 C901170044 Number of GPRS DL TBF resource reallocation success of
channel activate and connection for LLC transmission .....................................23-36
23.42 C901170047 Number of GPRS DL TBF release due to flush LL......................23-37
23.43 C901170048 Number of GPRS DL TBF release due to GPRS suspend
requests........................................................................................................23-38
23.44 C901170049 Number of GPRS DL TBF forcing release by CS........................23-38
23.45 C901170050 Number of GPRS DL TBF normal release due to user plane
requests........................................................................................................23-39
23.46 C901170051 Number of GPRS DL TBF abnormal release due to user plane
requests........................................................................................................23-40
23.47 C901170052 Number of GPRS DL TBF release due to NSVC unavailability ......23-41
L
23.48 C901170053 Number of GPRS DL TBF release due to BVC unavailability ......23-42
23.49 C901170054 Number of GPRS DL TBF release due to other reasons .............23-42
23.50 C901170055 Number of DL GPRS TBF grab resources .................................23-43
23.51 C901170056 Number of grab instance by DL GPRS TBF ...............................23-44
23.52 C901170057 Number of DL GPRS TBF queuing............................................23-45
23.53 C901170058 Number of DL GPRS TBF queuing success...............................23-46
23.54 C901170059 Number of DL GPRS TBF release TBF during queuing ..............23-47
Chapter 24 Downlink EGPRS Data TBF Statistics................................. 24-1

24.1 Overview ....................................................................................................... 24-3
CCCH/PCCCH ............................................................................................... 24-3
24.3 C901180003 Number of EGPRS DL TBF establishment requests on PACCH ..... 24-4
24.4 C901180004 Number of EGPRS DL TBF establishment failure due to CPU ....... 24-5
24.5 C901180005 Number of EGPRS DL TBF establishment failure due to not
support DTM .................................................................................................. 24-5
24.6 C901180007 Number of EGPRS DL TBF establishment failure due to Abis
congestion ..................................................................................................... 24-5
24.7 C901180008 Number of EGPRS DL TBF establishment failure due to RR
congestion ..................................................................................................... 24-7
24.8 C901180009 Number of EGPRS DL TBF establishment failure due to
UPPB-DSP channel congestion....................................................................... 24-8
24.9 C901180010 Number of EGPRS DL TBF establishment channel allocate
success ......................................................................................................... 24-9
24.10 C901180011 Number of allocated PDCH for EGPRS DL TBF
establishment ................................................................................................24-10
24.11 C901180012 Number of EGPRS DL TBF establishment failure due to channel
activate failed ................................................................................................ 24-11
24.12 C901180013 Number of EGPRS DL TBF establishment failure due to BTS
24.13 C901180014 Number of EGPRS DL TBF establishment failure due to BIU
24.14 C901180015 Number of EGPRS DL TBF channel activate establishment
success ........................................................................................................24-14
CCCH/PCCCH due to not receive PIA ............................................................24-15
CCCH/PCCCH due to UPPB-DSP congestion .................................................24-16
24.17 C901180018 Number of EGPRS DL TBF establishment failure on PACCH
due to UPPB-DSP congestion ........................................................................24-16
LI
PCCCH/CCCH ..............................................................................................24-17
PACCH .........................................................................................................24-17
Abis congestion for UL TBF establishment ......................................................24-18
RR congestion for UL TBF establishment ........................................................24-19
UPPB-DSP channel congestion for UL TBF establishment ...............................24-20
24.23 C901180026 Number of EGPRS DL TBF resource reallocation success due
to UL TBF establishment................................................................................24-21
24.24 C901180027 Number of allocated PDCH for EGPRS DL TBF resource
reallocation due to UL TBF establishment .......................................................24-22
channel activate failure for UL TBF establishment............................................24-23
BTS connection failure for UL TBF establishment ............................................24-24
BIU connection failure for UL TBF establishment .............................................24-25
24.28 C901180031 Number of EGPRS DL TBF resource reallocation success of
channel activate and connection for UL TBF establishment ..............................24-26
to UL TBF establishment................................................................................24-27
24.35 C901180040 Number of allocated PDCH for EGPRS DL TBF resource
LII
24.39 C901180044 Number of EGPRS DL TBF resource reallocation success of
channel activate and connection for LLC transmission .....................................24-36
24.42 C901180047 Number of EGPRS DL TBF release due to flush LL ...................24-38
24.43 C901180048 Number of EGPRS DL TBF release due to EGPRS suspend
requests........................................................................................................24-38
24.44 C901180049 Number of EGPRS DL TBF forcing release by CS .....................24-39
24.45 C901180050 Number of EGPRS DL TBF normal release due to user plane
requests........................................................................................................24-40
24.46 C901180051 Number of EGPRS DL TBF abnormal release due to user plane
requests........................................................................................................24-41
24.47 C901180052 Number of EGPRS DL TBF release due to NSVC
unavailability .................................................................................................24-41
24.48 C901180053 Number of EGPRS DL TBF release due to BVC unavailability ......24-42
24.49 C901180054 Number of EGPRS DL TBF release due to other reasons...........24-43
24.50 C901180055 Number of DL EGPRS TBF grab resources ...............................24-44
24.51 C901180056 Number of grab instance by DL EGPRS TBF.............................24-44
24.52 C901180057 Number of DL EGPRS TBF queuing .........................................24-45
24.53 C901180058 Number of DL EGPRS TBF queuing success ............................24-46
24.54 C901180059 Number of DL EGPRS TBF release TBF during queuing ............24-47
Chapter 25 Uplink GPRS Data TBF Statistics ........................................ 25-1

25.1 Overview ....................................................................................................... 25-4
25.2 C901190002 Number of GPRS UL TBF establishment requests on CCCH......... 25-4
25.3 C901190003 Number of EGPRS UL TBF establishment requests on CCCH....... 25-5
25.4 C901190004 Number of GPRS UL TBF establishment requests on PCCCH....... 25-5
25.5 C901190005 Number of EGPRS UL TBF establishment requests on PCCCH ..... 25-6
25.6 C901190006 Number of GPRS UL TBF establishment requests on PACCH ....... 25-6
25.7 C901190007 Number of cell attempts for UL assignment due to ONE PHASE
access ........................................................................................................... 25-7
25.8 C901190008 Number of cell attempts for UL assignment due to single block
packet access ................................................................................................ 25-9
25.9 C901190009 Number of cell attempts for UL assignment due to response
paging ........................................................................................................... 25-9
LIII
25.10 C901190010 Number of cell attempts for UL assignment due to cell
updating........................................................................................................25-10
25.11 C901190011 Number of cell attempts for UL assignment due to mobility
management ................................................................................................. 25-11
25.12 C901190012 Number of cell attempts for UL assignment due to TWO PHASE
access ..........................................................................................................25-12
25.13 C901190013 Number of cell attempts for UL assignment due to short
access ..........................................................................................................25-13
25.14 C901190015 Number of GPRS UL TBF establishment failure due to Abis
congestion ....................................................................................................25-14
25.15 C901190016 Number of GPRS UL TBF establishment failure due to RR
congestion ....................................................................................................25-16
25.16 C901190017 Number of GPRS UL TBF establishment failure due to
UPPB-DSP channel congestion......................................................................25-17
25.17 C901190018 Number of GPRS UL TBF establishment channel allocate
success ........................................................................................................25-19
25.18 C901190019 Number of cell success for GPRS UL assignment due to ONE
PHASE access ..............................................................................................25-20
25.19 C901190020 Number of cell success for GPRS UL assignment due to single
block packet access.......................................................................................25-22
25.20 C901190021 Number of cell success for GPRS UL assignment due to
response paging............................................................................................25-23
25.21 C901190022 Number of cell success for GPRS UL assignment due to cell
updating........................................................................................................25-23
25.22 C901190023 Number of cell success for GPRS UL assignment due to
mobility management.....................................................................................25-24
25.23 C901190024 Number of cell success for GPRS UL assignment due to TWO
PHASE access ..............................................................................................25-25
25.24 C901190025 Number of cell success for GPRS UL assignment due to short
access ..........................................................................................................25-26
25.25 C901190026 Number of allocated PDCH for GPRS UL TBF establishment ......25-27
25.26 C901190027 Number of GPRS UL TBF establishment failure due to channel
activate failed ................................................................................................25-29
25.27 C901190028 Number of GPRS UL TBF establishment failure due to BTS
25.28 C901190029 Number of GPRS UL TBF establishment failure due to BIU
25.29 C901190030 Number of GPRS UL TBF channel activate establishment
success ........................................................................................................25-32
25.30 C901190031 Number of GPRS UL TBF establishment failure due to not
receive PIA ...................................................................................................25-32
LIV
25.31 C901190032 Number of GPRS UL TBF establisment failure on
PCCCH/CCCH due to UPPB-DSP congestion .................................................25-33
25.32 C901190033 Number of GPRS UL TBF establisment failure on PACCH due
to UPPB-DSP congestion...............................................................................25-34
25.33 C901190034 Number of GPRS UL TBF establishment success on
PCCCH/CCCH ..............................................................................................25-34
25.34 C901190035 Number of GPRS UL TBF establishment success on PACCH ......25-36
Abis congestion for DL TBF establishment ......................................................25-36
RR congestion for DL TBF establishment ........................................................25-37
UPPB-DSP channel congestion for DL TBF establishment ...............................25-38
25.38 C901190041 Number of GPRS UL TBF resource reallocation success due to
25.39 C901190042 Number of allocated PDCH for GPRS UL TBF resource
reallocation due to DL TBF establishment .......................................................25-40
25.40 C901190043 Number of GPRS UL TBF resourse reallocation failure due to
channel activate failure for DL TBF establishment............................................25-41
BTS connection failure for DL TBF establishment ............................................25-42
BIU connection failure for DL TBF establishment .............................................25-43
25.43 C901190046 Number of GPRS UL TBF resource reallocation success of
channel activate and connection for DL TBF establishment ..............................25-44
25.45 C901190048 Number of GPRS UL TBF resourse reallocation success due to
LV
25.54 C901190059 Number of GPRS UL TBF resourse reallocation success of
channel activate for LLC transmission .............................................................25-54
25.57 C901190062 Number of GPRS UL TBF resource reallocation requests for
Abis congestion for resource request ..............................................................25-55
RR congestion for resource request ................................................................25-56
UPPB-DSP channel congestion for resource request .......................................25-58
reallocation due to resource request ...............................................................25-60
channel activate failure for resource request....................................................25-61
BTS connection failure for resource request ....................................................25-62
BIU connection failure for resource request .....................................................25-63
25.66 C901190072 Number of GPRS UL TBF resource reallocation success of
channel activate and connection for resource request ......................................25-64
25.69 C901190075 Number of GPRS UL TBF release due to flush LL......................25-65
25.70 C901190076 Number of GPRS UL TBF release due to GPRS suspend
requests........................................................................................................25-66
25.71 C901190077 Number of GPRS UL TBF forcing release by CS........................25-67
25.72 C901190078 Number of GPRS UL TBF normal release due to user plane
requests........................................................................................................25-68
LVI
25.73 C901190079 Number of GPRS UL TBF abnormal release due to user plane
requests........................................................................................................25-68
25.74 C901190080 Number of GPRS UL TBF release due to NSVC unavailability ......25-69
25.75 C901190081 Number of GPRS UL TBF release due to BVC unavailability ......25-70
25.76 C901190082 Number of GPRS UL TBF release due to other reasons .............25-71
25.77 C901190083 Number of UL GPRS TBF grab resources .................................25-71
25.78 C901190084 Number of grab instance by UL GPRS TBF ...............................25-72
25.79 C901190085 Number of UL GPRS TBF queuing............................................25-73
25.80 C901190086 Number of UL GPRS TBF queuing success...............................25-74
25.81 C901190087 Number of UL GPRS TBF release TBF during queuing ..............25-75
Chapter 26 Uplink EGPRS Data TBF Statistics...................................... 26-1

26.1 Overview ....................................................................................................... 26-4
26.2 C901200002 Number of GPRS UL TBF establishment requests on CCCH......... 26-4
26.3 C901200003 Number of EGPRS UL TBF establishment requests on CCCH ...... 26-4
26.4 C901200004 Number of GPRS UL TBF establishment requests on PCCCH ...... 26-5
26.5 C901200005 Number of EGPRS UL TBF establishment requests on PCCCH ..... 26-5
26.6 C901200006 Number of GPRS UL TBF establishment requests on PACCH....... 26-6
26.7 C901200007 Number of cell attempts for UL assignment due to ONE PHASE
access ........................................................................................................... 26-7
26.8 C901200008 Number of cell attempts for UL assignment due to single block
packet access ................................................................................................ 26-8
26.9 C901200009 Number of cell attempts for UL assignment due to response
paging ........................................................................................................... 26-9
26.10 C901200010 Number of cell attempts for UL assignment due to cell
updating......................................................................................................... 26-9
26.11 C901200011 Number of cell attempts for UL assignment due to mobility
management .................................................................................................. 26-9
26.12 C901200012 Number of cell attempts for UL assignment due to TWO PHASE
access ..........................................................................................................26-10
26.13 C901200013 Number of cell attempts for UL assignment due to short
access .......................................................................................................... 26-11
26.14 C901200015 Number of EGPRS UL TBF establishment failure due to Abis
congestion ....................................................................................................26-12
26.15 C901200016 Number of EGPRS UL TBF establishment failure due to RR
congestion ....................................................................................................26-14
UPPB-DSP channel congestion......................................................................26-15
26.17 C901200018 Number of EGPRS UL TBF establishment channel allocate
success ........................................................................................................26-16
LVII
26.18 C901200019 Number of cell success for EGPRS UL assignment due to ONE
PHASE access ..............................................................................................26-17
26.19 C901200020 Number of cell success for EGPRS UL assignment due to
single block packet access .............................................................................26-19
response paging............................................................................................26-19
26.21 C901200022 Number of cell success for EGPRS UL assignment due to cell
updating........................................................................................................26-19
mobility management.....................................................................................26-20
26.23 C901200024 Number of cell success for EGPRS UL assignment due to TWO
PHASE access ..............................................................................................26-20
26.24 C901200025 Number of cell success for EGPRS UL assignment due to short
access ..........................................................................................................26-21
26.25 C901200026 Number of allocated PDCH for EGPRS UL TBF
establishment ................................................................................................26-23
channel activate failed ...................................................................................26-24
26.27 C901200028 Number of EGPRS UL TBF establishment failure due to BTS
26.28 C901200029 Number of EGPRS UL TBF establishment failure due to BIU
26.29 C901200030 Number of EGPRS UL TBF channel activate establishment
success ........................................................................................................26-27
26.30 C901200031 Number of EGPRS UL TBF establishment failure due to not
receive PIA ...................................................................................................26-27
PCCCH/CCCH due to UPPB-DSP congestion .................................................26-28
26.32 C901200033 Number of EGPRS UL TBF establishment failure on PACCH
due to UPPB-DSP congestion ........................................................................26-30
PCCCH/CCCH ..............................................................................................26-30
PACCH .........................................................................................................26-31
Abis congestion for DL TBF establishment ......................................................26-32
RR congestion for DL TBF establishment ........................................................26-33
UPPB-DSP channel congestion for DL TBF establishment ...............................26-34
LVIII
26.38 C901200041 Number of EGPRS UL TBF resource reallocation success due
26.39 C901200042 Number of allocated PDCH for EGPRS UL TBF resource
reallocation due to DL TBF establishment .......................................................26-36
channel activate failure for DL TBF establishment............................................26-37
BTS connection failure for DL TBF establishment ............................................26-38
BIU connection failure for DL TBF establishment .............................................26-39
26.43 C901200046 Number of EGPRS UL TBF resource reallocation success of
channel activate and connection for DL TBF establishment ..............................26-40
reallocation due to LLC transmission ..............................................................26-46
channel activate for LLC transmission .............................................................26-50
26.57 C901200062 Number of EGPRS UL TBF resource reallocation requests for
LIX
Abis congestion for resource request ..............................................................26-52
RR congestion for resource request ................................................................26-53
UPPB-DSP channel congestion for resource request .......................................26-54
to database allocation for resource request .....................................................26-55
reallocation due to resource request ...............................................................26-56
channel activate failure for resource request....................................................26-57
BTS connection failure for resource request ....................................................26-58
BIU connection failure for resource request .....................................................26-59
channel activate and connection for resource request ......................................26-60
to resource request........................................................................................26-61
26.69 C901200075 Number of EGPRS UL TBF release due to flush LL ...................26-61
26.70 C901200076 Number of EGPRS UL TBF release due to GPRS suspend
requests........................................................................................................26-62
26.71 C901200077 Number of EGPRS UL TBF forcing release by CS .....................26-63
26.72 C901200078 Number of EGPRS UL TBF normal release due to user plane
requests........................................................................................................26-63
26.73 C901200079 Number of EGPRS UL TBF abnormal release due to user plane
requests........................................................................................................26-64
26.74 C901200080 Number of EGPRS UL TBF release due to NSVC
unavailability .................................................................................................26-65
26.75 C901200081 Number of EGPRS UL TBF release due to BVC unavailability ......26-65
26.76 C901200082 Number of EGPRS UL TBF release due to other reasons ..........26-66
26.77 C901200083 Number of UL EGPRS TBF grab resources...............................26-67
26.78 C901200084 Number of grab instance by UL EGPRS TBF ............................26-68
26.79 C901200085 Number of UL EGPRS TBF queuing .........................................26-69
26.80 C901200086 Number of UL EGPRS TBF queuing success ............................26-70
26.81 C901200087 Number of UL EGPRS TBF release TBF during queuing............26-71
Chapter 27 BSSGP Flow Statistic ........................................................... 27-1
LX
27.1 Overview ....................................................................................................... 27-2
27.2 C901210001 Number of paging PS message ................................................... 27-2
27.3 C901210002 Number of paging CS message................................................... 27-2
27.4 C901210003 Number of Flush-LL Message received........................................ 27-3
27.5 C901210004 Number of Flush-LL-ACK Message sent ...................................... 27-4
27.6 C901210005 Number of BVC-BLOCK message sent........................................ 27-5
27.7 C901210006 Number of BVC-BLOCK-ACK message received ......................... 27-5
27.8 C901210007 Number of BVC-UNBLOCK message sent ................................... 27-6
27.9 C901210008 Number of BVC-UNBLOCK-ACK message received .................... 27-7
27.10 C901210009 Number of BVC-RESET message sent ...................................... 27-8
27.11 C901210010 Number of BVC-RESET-ACK message received ....................... 27-9
27.12 C901210011 Number of BVC-RESET message received ...............................27-10
27.13 C901210012 Number of BVC-RESET-ACK message sent ............................. 27-11
27.14 C901210013 Number of PERFORM-LOCATION-REQUEST message
received ........................................................................................................27-12
27.15 C901210014 Number of PERFORM-LOCATION-RESPONSE message
sent ..............................................................................................................27-13
27.16 C901210015 Number of PERFORM-LOCATION-ABORT message
received ........................................................................................................27-14
27.17 C901210016 Number of POSITION-COMMAND message sent......................27-15
27.18 C901210017 Number of POSITION-RESPONSE message received ..............27-16
27.19 C901210018 Number of Flush-LL received if UL/DL TBF exist .......................27-17
27.20 C901210019 Number of Flush-LL received if DL TBF exist.............................27-18
27.21 C901210020 Number of Flush-LL received if UL TBF exist.............................27-19
27.22 C901210021 Number of reroute intra NSE ....................................................27-20
27.23 C901210022 Number of reroute inter NSE intra BSS cell ...............................27-21
27.24 C901210023 Number of reroute inter NSE inter BSS cell ...............................27-21
27.25 C901210024 LLC transfer bytes ...................................................................27-22
27.26 C901210025 LLC transfer frames .................................................................27-23
27.27 C901210026 LLC transfer failed bytes ..........................................................27-23
27.28 C901210027 LLC transfer failed frames ........................................................27-24
27.29 C901210028 LLC transfer failed num............................................................27-24
27.30 C901210029 LLC transfer succeeded num....................................................27-25
27.31 C901210030 LLC transfer via cell reselection ................................................27-25
27.32 C901210031 LLC transfer not via cell reselection ..........................................27-26
27.33 C901210032 LLC transfer fail Num via cell reselection...................................27-27
27.34 C901210033 LLC transfer fail Num not via cell reselection .............................27-27
Chapter 28 Gb Interface Message Statistics.......................................... 28-1
LXI
28.1 Overview ....................................................................................................... 28-2
28.2 C901220001 Sum of UL UNITDATA messages handled at BSSGP level............ 28-2
28.3 C901220002 Sum of DL UNITDATA messages handled at BSSGP level............ 28-3
28.4 C901220003 Number of receiving RA-CAPABILITY message ........................... 28-4
28.5 C901220004 Number of PTP packet paging received by BSC ........................... 28-5
28.6 C901220005 Number of PTP circuit paging received by BSC ............................ 28-6
28.7 C901220006 Number of RA-CAPABILITY-UPDATE message sent .................... 28-6
28.8 C901220007 Number of RA-CAPABILITY-UPDATE-ACK message received ...... 28-7
28.9 C901220008 Number of wireless status PDU messages sent by BSC ............... 28-8
28.10 C901220009 Number of wireless status messages sent by BSC due to losing
wireless association with MS ........................................................................... 28-9
28.11 C901220010 Number of wireless status messages sent by BSC due to bad
link quality .....................................................................................................28-10
28.12 C901220011 Number of wireless status messages sent by BSC due to cell
reselection command.....................................................................................28-10
28.13 C901220012 Number of FLOW-CONTROL-BVC messages sent by BSC ....... 28-11
28.14 C901220013 Number of FLOW-CONTROL-BVC-ACK messages received by
BSC.............................................................................................................. 28-11
28.15 C901220014 Number of FLOW-CONTROL-MS messages sent by BSC .........28-12
28.16 C901220015 Number of FLOW-CONTROL-MS-ACK messages received by
BSC..............................................................................................................28-13
28.17 C901220016 Number of FLOW-CONTROL-PFC messages sent by BSC........28-14
28.18 C901220017 Number of FLOW-CONTROL-PFC-ACK messages received by
BSC..............................................................................................................28-15
28.19 C901220018 Number of status messages sent by BSC .................................28-16
28.20 C901220019 Number of status messages received by BSC ...........................28-17
28.21 C901220020 Number of status messages sent with BVCI Unknown ...............28-18
28.22 C901220021 Number of Status messages sent with cell service
congestion ....................................................................................................28-19
28.23 C901220022 Number of status messages sent with protocol error ..................28-19
28.24 C901220023 Number of status messages sent with Processor overload .........28-19
28.25 C901220024 Number of status messages received with BVCI Unknown .........28-20
28.26 C901220025 Number of status messages received with cell service
congestion ....................................................................................................28-20
28.27 C901220026 Number of status messages received with protocol error............28-20
28.28 C901220027 Number of status messages received with processor
overload........................................................................................................28-21
28.29 C901220028 Number of DOWNLOAD-BSS-PFC messages sent by BSC .......28-21
LXII
28.30 C901220029 Number of BVCCREATE-BSS-PFC messages received by
BSC..............................................................................................................28-22
28.31 C901220030 Number of CREATE-BSS-PFC-ACK messages sent by BSC ......28-23
28.32 C901220031 Number of CREATE-BSS-PFC-NACK messages sent by
BSC..............................................................................................................28-24
28.33 C901220032 Number of MODIFY-BSS-PFC messages sent by BSC ..............28-25
28.34 C901220033 Number of MODIFY-BSS-PFC-ACK messages received by
BSC..............................................................................................................28-26
28.35 C901220034 Number of DELETE-BSS-PFC messages received by BSC........28-27
28.36 C901220035 Number of DELETE-BSS-PFC-ACK messages sent by BSC ......28-28
28.37 C901220036 Number of DELETE-BSS-PFC-REQ messages received by
BSC..............................................................................................................28-29
28.38 C901220037 Number of PS-HANDOVER-REQUIRED messages sent by
BSC..............................................................................................................28-29
28.39 C901220038 Number of PS-HANDOVER-REQUIRED-ACK messages
received by BSC............................................................................................28-30
28.40 C901220039 Number of PS-HANDOVER-REQUIRED-NACK messages
received by BSC............................................................................................28-31
28.41 C901220040 Number of PS-HANDOVER-REQUEST messages received by
BSC..............................................................................................................28-32
28.42 C901220041 Number of PS-HANDOVER-REQUEST-ACK messages sent by
BSC..............................................................................................................28-33
28.43 C901220042 Number of PS-HANDOVER-REQUEST-NACK messages sent
by BSC .........................................................................................................28-34
28.44 C901220043 Number of PS-HANDOVER-COMPLETE messages sent by
BSC..............................................................................................................28-36
28.45 C901220044 Number of PS-HANDOVER-CANCEL messages sent by
BSC..............................................................................................................28-37
28.46 C901220045 Number of PS-HANDOVER-REQUEST messages with Service
UTRAN CCO received by BSC .......................................................................28-38
28.47 C901220046 Number of CREATE-BSS-PFC messages with Service UTRAN
CCO received by BSC ...................................................................................28-39
Chapter 29 TRX Measurement................................................................. 29-1

29.1 Overview ....................................................................................................... 29-2
29.2 C901230001 Number of intra-cell handover in attempts .................................... 29-3
29.3 C901230002 Number of intra-cell handover ins success ................................... 29-4
29.4 C901230003 Number of Intra-BSC inter-cell handover in attempts..................... 29-5
29.5 C901230004 Number of Intra-BSC intra-cell handover ins success.................... 29-5
29.6 C901230005 Number of Intra-MSC inter-cell handover in attempts .................... 29-6
29.7 C901230006 Number of Intra-MSC inter-cell handover ins success ................... 29-7
LXIII
29.8 C901230007 TCH busy time ........................................................................... 29-8
29.9 C901230008 Number of TCH seizures (including handover) ............................. 29-9
29.10 C901230009 Number of call drops due to TCH LAPD breakage ...................... 29-9
29.11 C901230010 Number of call drops due to TCH radio link failure....................... 29-9
29.12 C901230011 Number of TCH handover call drops .........................................29-10
29.13 C901230012 Number of TCH/F activation attempts (including handover) ........ 29-11
29.14 C901230013 Number of TCH/F activation success (including handover) .........29-12
29.15 C901230014 Number of TCH/F assignment attempts ....................................29-13
29.16 C901230015 Number of TCH/F assignment success .....................................29-14
29.17 C901230016 Number of TCH/H activation attempts (including handover) ........29-15
29.18 C901230017 Number of TCH/H activation success (including handover).........29-16
29.19 C901230018 Number of TCH/H assignment attempts ....................................29-17
29.20 C901230019 Number of TCH/H assignment success.....................................29-18
29.21 C901230020 SDCCH busy time ...................................................................29-19
29.22 C901230021 Number of attempts for SDCCH................................................29-20
29.23 C901230022 Number of SDCCH call drops ...................................................29-20
29.24 C901230023 Number of SDCCH activation attempts (including handover) ......29-22
29.25 C901230024 Number of SDCCH activation success (including handover) .......29-22
29.26 C901230025 Number of SDCCH assignment attempts ..................................29-23
29.27 C901230026 Number of SDCCH assignment success ...................................29-24
29.28 C901230027 Number of samples with UL RQ = 0 ..........................................29-25
29.36 C901230035 Number of samples with DL RQ = 0 ..........................................29-30
LXIV
29.50 C901230049 Mean number of idle TCH/Hs with interference band 0...............29-38
29.62 C901230061 Number of TRX poweroff..........................................................29-44
29.63 C901230062 Duration of TRX poweroff .........................................................29-44
29.70 C901230069 Number of uplink error frame on HR_V1 ...................................29-47
29.71 C901230070 Total Number of uplink frame on HR_V1 ...................................29-47
29.72 C901230071 Number of uplink error frame on HR_V3 ...................................29-48
29.73 C901230072 Total Number of uplink frame on HR_V3 ...................................29-48
Chapter 30 Timeslot Measurement ......................................................... 30-1

30.1 Overview ....................................................................................................... 30-2
30.2 C901240001 Maximum value of UL RQ ........................................................... 30-2
30.3 C901240002 Minimum value of UL RQ ............................................................ 30-3
30.4 C901240003 Value of UL RQ .......................................................................... 30-3
30.5 C901240004 Number of scans of UL RQ ......................................................... 30-4
30.6 C901240005 Maximum value of DL RQ ........................................................... 30-5
30.7 C901240006 Minimum value of DL RQ ............................................................ 30-6
LXV
30.8 C901240007 Value of DL RQ .......................................................................... 30-6
30.9 C901240008 Number of scans of DL RQ ......................................................... 30-7
30.10 C901240009 Maximum value of received UL signal strength ........................... 30-8
30.11 C901240010 Minimum value of received UL signal strength ............................ 30-8
30.12 C901240011 Total value of received UL signal strength................................... 30-9
30.13 C901240012 Number of received UL signal strength samples ........................30-10
30.14 C901240013 Maximum value of received DL signal strength .......................... 30-11
30.15 C901240014 Minimum value of received DL signal strength ...........................30-12
30.16 C901240015 Total value of received DL signal strength .................................30-12
30.17 C901240016 Number of received DL signal strength samples ........................30-13
30.18 C901240017 Value of power scans of MS transmitting power .........................30-14
30.19 C901240018 Number of power scans of MS transmitting power .....................30-15
30.20 C901240019 Value of power scans of BTS power..........................................30-15
30.21 C901240020 Number of power scans of BTS power ......................................30-16
30.22 C901240021 Number of immediate assignment failure...................................30-17
30.23 C901240022 Number of assignment failure ...................................................30-18
30.24 C901240023 Number of handovers failure ....................................................30-19
30.25 C901240024 Maximum interference value.....................................................30-20
30.26 C901240025 Minimum interference value .....................................................30-21
30.27 C901240026 Interference value....................................................................30-21
30.28 C901240027 Number of regular scanning and sampling of interference
value ............................................................................................................30-22
30.29 C901240028 Number of call drop .................................................................30-23
30.30 C901240029 Maximum value of path balance ...............................................30-24
30.31 C901240030 Minimum value of path balance ................................................30-24
30.32 C901240031 Value of path balance ..............................................................30-25
30.33 C901240032 Number of regular scanning and sampling of path balance.........30-26
30.34 C901240033 Value of UL loss ......................................................................30-27
30.35 C901240034 Number of regular scanning and sampling of UL loss.................30-27
30.36 C901240035 Total value of DL loss...............................................................30-28
30.37 C901240036 Number of regular scanning and sampling of DL loss.................30-29
30.38 C901240037 Number of drops due to the bad quality of UL receive ................30-30
30.39 C901240038 Number of drops due to the bad quality of DL receive ................30-31
30.40 C901240039 Number of drops due to the low electric level of UL....................30-33
30.41 C901240040 Number of drops due to the low electric level of DL....................30-35
30.42 C901240041 Number of drops due to the TA too far.......................................30-37
30.43 C901240042 Number of drops due to the other radio reasons ........................30-39
30.44 C901240043 The valid time of the used voice channel ...................................30-41
LXVI
30.45 C901240044 Number of activated voice channel ...........................................30-42
Chapter 31 SDCCH Measurement ........................................................... 31-1

31.1 Overview ....................................................................................................... 31-1
31.2 C901250005 Number of SDCCH seizure success for Handover ........................ 31-3
31.3 C901250007 Number of SDCCH allocation attempts for Assignment ................. 31-5
31.4 C901250010 Number of SDCCH allocation attempts for handover..................... 31-6
31.5 C901250011 Number of SDCCH allocation success for handover...................... 31-8
31.6 C901250012 Number of SDCCH allocation failure for handover ........................ 31-9
31.7 C901250016 Number of SDCCH handover failure ........................................... 31-11
31.8 C901250017 Number of SDCCH handover success ........................................31-12
31.9 C901250018 Number of SDCCH handover failure with Reconnection ...............31-14
31.10 C901250019 Number of SDCCH handover failure without Reconnection ........31-14
Chapter 32 TCH/F Measurement ............................................................. 32-1

32.1 Overview ....................................................................................................... 32-4
32.2 C901260002 Number of signaling TCH/F seizure success for assignment ......... 32-7
32.3 C901260005 Number of signaling TCH/F seizure success for handover............. 32-8
32.4 C901260007 Number of signaling TCH/F allocation attempts for assignment ...... 32-11
32.5 C901260010 Number of signaling TCH/F allocation attempts for handover........32-12
32.6 C901260011 Number of signaling TCH/F allocation success for handover.........32-15
32.7 C901260013 Number of signaling TCH/F assignment attempts for
assignment ...................................................................................................32-17
32.8 C901260016 Number of signaling TCH/F handover attempt .............................32-18
32.9 C901260017 Number of signaling TCH/F handover success ............................32-21
32.10 C901260018 Number of signaling TCH/F handover failure with
reconnection .................................................................................................32-23
32.11 C901260019 Number of signaling TCH/F handover failure without
reconnection .................................................................................................32-25
32.12 C901260021 Number of voice TCH/F seizure success for assignment ............32-26
32.13 C901260024 Number of voice TCH/F seizure success for handover ...............32-27
32.14 C901260026 Number of TCH/F allocation attempts for assignment (speech
version 1)......................................................................................................32-30
32.15 C901260032 Number of TCH/F allocation attempts by BSC for handover
(speech version 1) .........................................................................................32-31
32.16 C901260033 Number of TCH/F allocation success by BSC for handover
(speech version 1) .........................................................................................32-34
32.17 C901260038 Number of TCH/F allocation attempts for assignment (speech
version 2)......................................................................................................32-36
LXVII
(speech version 2) .........................................................................................32-38
(speech version 2) .........................................................................................32-40
32.20 C901260050 Number of TCH/F allocation attempts by BSC for assignment
(speech version 3) .........................................................................................32-43
(speech version 3) .........................................................................................32-44
(speech version 3) .........................................................................................32-47
32.23 C901260062 Number of voice TCH/F assignment attempts by BSC ...............32-49
32.24 C901260065 Number of voice TCH/F handover attempts ...............................32-51
32.25 C901260067 Number of Voice TCH/F handover failure ..................................32-54
32.26 C901260068 Number of Voice TCH/F handover failure messages do not
received by BSC............................................................................................32-55
32.27 C901260070 Number of data TCH/F seizure success for assignment .............32-56
32.28 C901260073 Number of data TCH/F seizure success for handover ................32-58
32.29 C901260075 Number of data TCH/F allocation attempts for assignment .........32-60
32.30 C901260081 Number of data TCH/F allocation attempts by BSC for
handover.......................................................................................................32-62
32.31 C901260082 Number of data TCH/F allocation success for handover .............32-64
32.32 C901260087 Number of data TCH/F assignment attempts .............................32-67
32.33 C901260090 Number of data TCH/F handover attempts ................................32-68
32.34 C901260092 Number of data TCH/F handover failure ....................................32-71
32.35 C901260093 Number of data TCH/F handover failure messages do not
received by BSC............................................................................................32-72
32.36 C901260094 Number of data TCH/F allocation failure for assignment due to
TIPB connection failure (Speech version 1) .....................................................32-73
Resource request to iTC failure (Speech version 1) .........................................32-74
32.38 C901260096 Number of data TCH/F allocation failure for handover due to
LXVIII
32.48 C901260106 Number of TCH/F allocation failure due to request AIPB
resource failure for assignment (speech version 1) ..........................................32-88
32.49 C901260107 Number of TCH/F allocation failure due to request UDP port
failure for assignment (speech version 1) ........................................................32-89
32.50 C901260108 Number of TCH/F allocation failure due to AIPB connection
resource failure for handover (speech version 1)..............................................32-91
failure for handover (speech version 1) ...........................................................32-92
resource failure for handover (speech version 2)..............................................32-97
resource failure for assignment (speech version 3) ........................................32-100
failure for assignment (speech version 3) ......................................................32-101
LXIX
resource failure for handover (speech version 3)............................................32-103
failure for handover (speech version 3) .........................................................32-104
resource failure for assignment (data) ...........................................................32-106
failure for assignment (data) .........................................................................32-107
failure for assignment (data) .........................................................................32-108
resource failure for handover (data) ..............................................................32-109
failure for handover (data) ............................................................................ 32-110
failure for handover (data) ............................................................................ 32-111
32.72 C901260130 Number of assign TCH/F release by forced handover to forced
handover source.......................................................................................... 32-112
32.73 C901260131 Number of assign TCH/F release by forced handover to
queuing user ............................................................................................... 32-113
32.74 C901260132 Number of restore TCH/F release by forced handover to
DBS............................................................................................................ 32-113
32.75 C901260133 Number of assign TCHF release by forced release to forced
release source............................................................................................. 32-114
32.76 C901260134 Number of assign TCH/F release by forced release to queuing
user ............................................................................................................ 32-114
32.77 C901260135 Number of restore TCH/F release by forced release to DBS...... 32-115
32.78 C901260136 Number of signaling TCH/F seizure failure for assignment
(cause:Abis) ................................................................................................ 32-116
32.79 C901260137 Number of signaling TCH/F seizure failure for handover
(cause:Abis) ................................................................................................ 32-116
32.80 C901260138 Number of voice TCH/F seizure failure for assignment
(cause:Abis) ................................................................................................ 32-117
32.81 C901260139 Number of voice TCH/F seizure failure for handover (cause:Abis
) ................................................................................................................. 32-117
32.82 C901260140 Number of data TCH/F seizure failure for assignment
(cause:Abis) ................................................................................................ 32-118
32.83 C901260141 Number of data TCH/F seizure failure for handover
(cause:Abis) ................................................................................................ 32-118
LXX
32.84 C901260142 Number of signaling TCH/F seizure failure for assignment
(cause:radio resource) ................................................................................. 32-119
32.85 C901260143 Number of signaling TCH/F seizure failure for handover
(cause:radio resource) ................................................................................. 32-119
32.86 C901260144 Number of voice TCH/F seizure failure for assignment
(cause:radio resource) .................................................................................32-120
32.87 C901260145 Number of voice TCH/F seizure failure for handover
32.88 C901260146 Number of data TCH/F seizure failure for assignment
32.89 C901260147 Number of data TCH/F seizure failure for handover (cause:radio
resource) ....................................................................................................32-121
32.90 C901260148 Number of FR_V1 assignment attempts ..................................32-122
32.91 C901260149 Number of FR_V1 assignment success...................................32-122
32.96 C901260154 Number of FR_V1 handover...................................................32-125
32.97 C901260155 Number of FR_V1 handover success......................................32-125
32.98 C901260156 Number of FR_V2 handover...................................................32-126
32.99 C901260157 Number of FR_V2 handover success......................................32-126
32.100 C901260158 Number of FR_V3 handover .................................................32-127
32.101 C901260159 Number of FR_V3 handover success ....................................32-128
Chapter 33 TCH/H Measurement............................................................. 33-1

33.1 Overview ....................................................................................................... 33-5
33.2 C901270002 Number of signaling TCH/H seizure success for assignment ......... 33-8
33.3 C901270005 Number of signaling TCH/H seizure success for handover ............ 33-9
33.4 C901270007 Number of signaling TCH/H allocation attempts by BSC for
assignment ...................................................................................................33-12
33.5 C901270008 Number of signaling TCH/H allocation success for assignment ......33-13
33.6 C901270010 Number of signaling TCH/H allocation attempts by BSC due to
handover.......................................................................................................33-14
33.7 C901270011 Number of signaling TCH/H allocation success due to
handover.......................................................................................................33-17
33.8 C901270012 Number of signaling TCH/H allocation failure due to handover ......33-19
33.9 C901270013 Number of signaling TCH/H assignment attempts by BSC............33-20
33.10 C901270016 Number of signaling TCH/H handover attempts .........................33-21
33.11 C901270017 Number of signaling TCH/H handover success ..........................33-24
LXXI
33.12 C901270018 Number of signaling TCH/H handover failure.............................33-27
33.13 C901270019 Number of signaling TCH/H handover failure messages do not
received by BSC............................................................................................33-28
33.14 C901270021 Number of voice TCH/H seizure success for assignment............33-29
33.15 C901270024 Number of voice TCH/H seizure success for handover...............33-31
33.16 C901270026 Number of TCH/H allocation attempts for assignment by BSC
(speech version 1) .........................................................................................33-34
33.17 C901270027 Number of TCH/H allocation success for assignment (speech
version1).......................................................................................................33-35
33.18 C901270032 Number of TCH/H allocation attempts by BSC during handover
(speech version 1) .........................................................................................33-37
33.19 C901270033 Number of TCH/H allocation success during handover (speech
version 1)......................................................................................................33-39
33.20 C901270038 Number of TCH/H allocation attempts by BSC for assignment
(speech version 2) .........................................................................................33-41
33.21 C901270039 Number of TCH/H allocation success by BSC for assignment
(speech version 2) .........................................................................................33-43
33.22 C901270044 Number of TCH/H allocation attempts for handover by BSC
(speech version 2) .........................................................................................33-44
33.23 C901270045 Number of TCH/H allocation success for handover (speech
version 2)......................................................................................................33-47
33.24 C901270050 Number of TCH/H allocation attempts for assignment (speech
version 3)......................................................................................................33-49
33.25 C901270051 Number of TCH/H allocation success for assignment (speech
version 3)......................................................................................................33-51
33.26 C901270056 Number of TCH/H allocation attempts by BSC for handover
(speech version 3) .........................................................................................33-52
33.27 C901270057 Number of TCH/H allocation success for handover (speech
version 3)......................................................................................................33-55
33.28 C901270062 Number of Voice TCH/H assignment attempts by BSC...............33-57
33.29 C901270065 Number of Voice TCH/H handover attempts ..............................33-59
33.30 C901270067 Number of Voice TCH/H handover failure..................................33-62
33.31 C901270068 Number of Voice TCH/H handover failure messages do not
received by BSC............................................................................................33-63
33.32 C901270070 Number of data TCH/H seizure success for assignment .............33-64
33.33 C901270073 Number of data TCH/H seizure success for handover ................33-66
33.34 C901270075 Number of data TCH/H allocation attempts for assignment by
BSC..............................................................................................................33-68
33.35 C901270076 Number of data TCH/H allocation success for assignment..........33-70
33.36 C901270081 Number of data TCH/H allocation attempts by BSC ...................33-71
LXXII
33.37 C901270082 Number of data TCH/H allocation success for handover.............33-74
33.38 C901270087 Number of data TCH/H assignment attempts by BSC ................33-76
33.39 C901270090 Number of data TCH/H handover attempts................................33-78
33.40 C901270092 Number of data TCH/H handover failure ...................................33-81
33.41 C901270093 Number of data TCH/H handover failure do not received by
BSC..............................................................................................................33-82
33.42 C901270094 Number of TCH/H allocation failure for assignment due to TIPB
connection failure (Speech version 1) .............................................................33-84
33.43 C901270095 Number of TCH/H allocation failure for assignment due to
33.44 C901270096 Number of TCH/H allocation failure for handover due to TIPB
33.45 C901270097 Number of TCH/H allocation failure for handover due to
33.54 C901270106 Number of TCH/H allocation failure due to request AIPB
33.55 C901270107 Number of TCH/H allocation failure due to request UDP port
33.56 C901270108 Number of TCH/H allocation failure due to AIPB connection
LXXIII
resource failure for assignment (speech version 2) ........................................33-105
failure for handover (speech version 2) ......................................................... 33-110
resource failure for assignment (speech version 3) ........................................ 33-111
failure for assignment (speech version 3) ...................................................... 33-112
failure for assignment (speech version 3) ...................................................... 33-113
resource failure for handover (speech version 3)............................................ 33-114
resource failure for assignment (data) ........................................................... 33-117
failure for assignment (data) ......................................................................... 33-118
failure for assignment (data) ......................................................................... 33-119
resource failure for handover (data) ..............................................................33-120
failure for handover (data) ............................................................................33-121
failure for handover (data) ............................................................................33-122
33.78 C901270130 Number of assign TCH/H release by forced handover to forced
handover source..........................................................................................33-123
LXXIV
33.79 C901270131 Number of assign TCH/H release by forced handover to
queuing user ...............................................................................................33-123
33.80 C901270132 Number of restore TCH/H release by forced handover to
DBS............................................................................................................33-124
33.81 C901270133 Number of assign TCH/H release by forced release to forced
release source.............................................................................................33-124
33.82 C901270134 Number of assign TCH/H release by forced release to queuing
user ............................................................................................................33-125
33.83 C901270135 Number of restore TCH/H release by forced release to DBS ......33-126
33.84 C901270136 Number of signaling TCH/H seize failure for assign due to Abis
lack.............................................................................................................33-126
33.85 C901270137 Number of signaling TCH/H seize failure for handover due to
Abis lack .....................................................................................................33-127
33.86 C901270138 Number of voice TCH/H seizure failure for assignment
(cause:Abis) ................................................................................................33-127
33.87 C901270139 Number of voice TCH/H seizure failure for handover (cause:Abis
) .................................................................................................................33-128
33.88 C901270140 Number of data TCH/H seizure failure for assignment
(cause:Abis) ................................................................................................33-128
33.89 C901270141 Number of data TCH/H seizure failure for handover
(cause:Abis) ................................................................................................33-129
33.90 C901270142 Number of signaling TCH/H seize failure for assign due to radio
resource lack...............................................................................................33-129
33.91 C901270143 Number of signaling TCH/H seize failure for handover due to
radio resource lack ......................................................................................33-130
33.92 C901270144 Number of voice TCH/H seizure failure for assignment
33.93 C901270145 Number of voice TCH/H seizure failure for handover
33.94 C901270146 Number of data TCH/H seizure failure for assignment
33.95 C901270147 Number of data TCH/H seizure failure for handover (cause:radio
resource) ....................................................................................................33-132
33.96 C901270148 Number of HR_V1 assignment attempts .................................33-132
33.97 C901270149 Number of HR_V1 assignment success ..................................33-133
33.98 C901270150 Number of HR_V3 assignment attempts .................................33-133
33.99 C901270151 Number of HR_V3 assignment success ..................................33-134
33.100 C901270152 Number of HR_V1 handover ................................................33-134
33.101 C901270153 Number of HR_V1 handover success....................................33-135
33.102 C901270154 Number of HR_V3 handover ................................................33-135
LXXV
33.103 C901270155 Number of HR_V3 handover success....................................33-136
Chapter 34 Abis Interface Message Counter Measurement ................. 34-1

34.1 Overview ....................................................................................................... 34-3
34.2 C901280001 Number of DATA REQUEST messages ....................................... 34-4
34.3 C901280002 Number of DATA INDICATION messages .................................... 34-5
34.4 C901280003 Number of ERROR INDICATION messages................................. 34-5
34.5 C901280004 Number of ESTABLISH REQUEST messages.............................. 34-6
34.6 C901280005 Number of ESTABLISH CONFIRM messages .............................. 34-7
34.7 C901280006 Number of ESTABLISH INDICATION messages........................... 34-8
34.8 C901280007 Number of RELEASE REQUEST messages ................................ 34-9
34.9 C901280008 Number of RELEASE CONFIRM messages................................34-10
34.10 C901280009 Number of RELEASE INDICATION messages ..........................34-10
34.11 C901280010 Number of UNIT DATA REQUEST messages ............................ 34-11
34.12 C901280011 Number of UNIT DATA INDICATION messages .........................34-12
34.13 C901280012 Number of CHANNEL ACTIVATION messages .........................34-13
34.14 C901280013 Number of CHANNEL ACTIVATION ACK messages..................34-14
34.15 C901280014 Number of CHANNEL ACTIVATION Negative ACK
messages .....................................................................................................34-14
34.16 C901280015 Number of CONNECTION FAILURE INDICATION
messages .....................................................................................................34-15
34.17 C901280016 Number of DEACTIVATE SACCH messages.............................34-16
34.18 C901280017 Number of ENCRYPTION COMMAND messages .....................34-17
34.19 C901280018 Number of HANDOVER DETECTION messages.......................34-18
34.20 C901280019 Number of MEASUREMENT RESULT messages ......................34-19
34.21 C901280020 Number of MODE MODIFY REQUEST messages .....................34-20
34.22 C901280021 Number of MODE MODIFY ACK messages ..............................34-20
34.23 C901280022 Number of MODE MODIFY NACK messages............................34-21
34.24 C901280023 Number of PHYSICAL CONTEXT REQUEST messages ...........34-22
34.25 C901280024 Number of PHYSICAL CONTEXT CONFIRM messages ............34-23
34.26 C901280025 Number of RF CHANNEL RELEASE messages ........................34-24
34.27 C901280026 Number of MS POWER CONTROL messages ..........................34-25
34.28 C901280027 Number of BS POWER CONTROL messages...........................34-25
34.29 C901280028 Number of PREPROCESSED CONFIGURE messages .............34-26
34.30 C901280029 Number of PREPROCESSED MEASUREMENT RESULT
messages .....................................................................................................34-27
34.31 C901280030 Number of RF CHANNEL RELEASE ACK messages ................34-28
34.32 C901280031 Number of SACCH INFO MODIFY messages ...........................34-29
LXXVI
34.33 C901280032 Number of ABIS_PREPROC_ENHANCEMEAS_RESULT
messages .....................................................................................................34-30
34.34 C901280033 Number of ABIS_ROUND_TRIP_DELAY_REPORT
messages .....................................................................................................34-31
34.35 C901280034 Number of ABIS_PRE_HO_NOTIFY messages.........................34-31
34.36 C901280035 Number of ABIS_BCCH_INFO messages .................................34-32
34.37 C901280036 Number of ABIS_CCCH_LOAD_IND messages ........................34-33
34.38 C901280037 Number of ABIS_CHL_RQD messages ....................................34-34
34.39 C901280038 Number of ABIS_DELETE_IND messages................................34-35
34.40 C901280039 Number of ABIS_PAGING_CMD messages ..............................34-35
34.41 C901280040 Number of ABIS_IMM_ASSIGN_CMD messages ......................34-36
34.42 C901280041 Number of ABIS_SMS_BROADCAST_REQ messages .............34-37
34.43 C901280042 Number of ABIS_SMS_BROADCAST_CMD messages .............34-38
34.44 C901280043 Number of ABIS_CBCH_LOAD_IND messages ........................34-39
34.45 C901280044 Number of ABIS_EGPRS_CHL_REQ messages .......................34-40
34.46 C901280045 Number of ABIS_LOAD_CONTROL messages .........................34-41
34.47 C901280046 Number of ABIS_END_LOAD_CONTROL messages ................34-41
34.48 C901280047 Number of ABIS_END_LOAD_CONTROL_ACK messages........34-42
34.49 C901280048 Number of ABIS_PCCCH_LOAD_IND messages ......................34-43
34.50 C901280049 Number of ABIS_RF_RESRC_IND messages...........................34-44
34.51 C901280050 Number of ABIS_SACCH_FILLING messages ..........................34-44
34.52 C901280051 Number of ABIS_OVERLOAD messages..................................34-45
34.53 C901280052 Number of ABIS_ERROR_REPORT messages.........................34-46
34.54 C901280053 Number of ABIS_SYSINFO_REQ messages.............................34-47
34.55 C901280054 Number of ABIS_SI_BC_END messages..................................34-48
34.56 C901280055 Number of ABIS_SI_NACK messages ......................................34-48
34.57 C901280056 Number of ABIS_PWRCTRL_IND messages ............................34-49
34.58 C901280057 Number of ABIS_SYSINFO_ACK messages .............................34-50
34.59 C901280061 Number of ABIS_PACKET_PBCCH_INF messages...................34-51
34.60 C901280062 Number of ABIS_PACKET_CCCH_PARA messages .................34-51
34.61 C901280063 Number of ABIS_PACKET_PBCCH_PARA messages ...............34-52
34.62 C901280064 Number of ABIS_PACKET_CHN_REQ messages .....................34-53
34.63 C901280065 Number of ABIS_PACKET_PAGING_CMD messages ...............34-54
34.64 C901280066 Number of ABIS_PACKET_IMM_ASSIGN_CMD messages .......34-55
34.65 C901280067 Number of ABIS_PACKET_CONNECT_FAIL_IND
messages .....................................................................................................34-55
34.66 C901280068 Number of ABIS_PACKET_PRACH_OVERLOAD messages ......34-56
34.67 C901280069 Number of ABIS_PACKET_PCH_OVERLOAD messages ..........34-57
LXXVII
34.68 C901280070 Number of ABIS_PACKET_TA_REQUEST messages ...............34-58
34.69 C901280071 Number of ABIS_PACKET_TA_REQUEST_ACK messages.......34-58
34.70 C901280072 Number of ABIS_PACKET_CHN_CONFIG_CHG messages ......34-59
34.71 C901280073 Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP
messages .....................................................................................................34-60
34.72 C901280074 Number of ABIS_PACKET_PIA_DEL_IND messages ................34-61
34.73 C901280075 Number of ABIS_PACKET_SEND_PIA_IND messages .............34-62
34.74 C901280076 Number of ABIS_PACKET_CHN_CONFIG_REQ messages ......34-62
34.75 C901280077 Number of ABIS_EGPRS_PACKET_CHN_REQ messages........34-63
34.76 C901280078 Number of ABIS_PS_CHANNEL_ACTIVE messages ................34-64
34.77 C901280079 Number of ABIS_PS_CHANNEL_ACTIVE_ACK messages........34-65
34.78 C901280080 Number of ABIS_PS_CHANNEL_ACTIVE_NACK messages ......34-66
34.79 C901280081 Number of ABIS_PS_CHANNEL_RELEASE messages .............34-66
34.80 C901280082 Number of ABIS_PS_CHANNEL_RELEASE_ACK
messages .....................................................................................................34-67
34.81 C901280083 Number of ABIS_PS_CHANNEL_RELEASE_NACK
messages .....................................................................................................34-68
34.82 C901280084 Number of ABIS_PSCONN_CMM_REQ messages ...................34-69
34.83 C901280085 Number of ABIS_PSCONN_CMM_ACK messages....................34-70
34.84 C901280086 Number of ABIS_PSCONN_CMM_NACK messages .................34-70
34.85 C901280087 Number of ABIS_GLOBAL_RESET messages ..........................34-71
34.86 C901280088 Number of ABIS_GLOBAL_RESET_ACK messages .................34-72
34.87 C901280089 Number of ABIS_GLOBAL_RESET_NACK messages ...............34-73
34.88 C901280090 Number of ABIS_PACKET_UP_ASSIGN messages ..................34-74
34.89 C901280091 Number of ABIS_PACKET_DOWN_ASSIGN messages ............34-74
34.90 C901280092 Number of ABIS_CSCONN_CMM_REQ messages ...................34-75
34.91 C901280093 Number of ABIS_CSCONN_CMM_ACK messages ...................34-76
34.92 C901280094 Number of ABIS_CSCONN_CMM_NACK messages .................34-77
34.93 C901280095 Number of ABIS_CCMCONN_CMM_REQ messages ................34-78
34.94 C901280096 Number of ABIS_CCMCONN_CMM_ACK messages ................34-78
34.95 C901280097 Number of ABIS_CCMCONN_CMM_NACK messages ..............34-79
34.96 C901280098 Number ABIS_PACKET_ACCESS_REJ messages ...................34-80
34.97 C901280099 Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW
messages .....................................................................................................34-81
34.98 C901280100 Number of PACKET_DOWNLINK_ASSIGN messages ..............34-82
34.99 C901280101 Number of PACKET_UPLINK_ASSIGN messages ....................34-82
34.100 C901280102 Number of ABIS_PACKET_ACCESS_REJ_NEW
messages .....................................................................................................34-83
LXXVIII
Chapter 35 Gb Message Statistics (BVC Cell) ....................................... 35-1
35.1 Overview ....................................................................................................... 35-2
35.4 C901290003 Number of RA-CAPABILITY message received ............................ 35-4
35.9 C901290008 Number of Wireless Status PDU messages sent by BSC .............. 35-7
35.10 C901290009 Number of Wireless Status messages sent by BSC due to
Losing Wireless Association with MS ............................................................... 35-8
35.11 C901290010 Number of wireless status messages sent by BSC due to Bad
Link Quality .................................................................................................... 35-9
35.12 C901290011 Number of Wireless status messages sent by BSC due to Cell
reselection command...................................................................................... 35-9
35.13 C901290012 Number of FLOW-CONTROL-BVC messages sent by BSC .......35-10
BSC..............................................................................................................35-10
35.15 C901290014 Number of FLOW-CONTROL-MS messages sent by BSC ......... 35-11
BSC..............................................................................................................35-12
BSC..............................................................................................................35-13
35.19 C901290018 Number of Status messages sent by BSC .................................35-14
35.20 C901290019 Number of Status messages received by BSC...........................35-15
35.21 C901290020 Number of Status messages sent with BVCI Unknown...............35-15
35.22 C901290021 Number of Status messages sent with Cell service
congestion ....................................................................................................35-16
35.23 C901290022 Number of Status messages sent with protocol error..................35-16
35.24 C901290023 Number of Status messages sent with Processor overload.........35-17
35.25 C901290024 Number of Status messages received with BVCI Unknown ........35-17
35.26 C901290025 Number of Status messages received with Cell service
congestion ....................................................................................................35-18
35.27 C901290026 Number of Status messages received with protocol error ...........35-18
35.28 C901290027 Number of Status messages received with Processor
overload........................................................................................................35-19
LXXIX
BSC..............................................................................................................35-20
BSC..............................................................................................................35-22
BSC..............................................................................................................35-24
35.36 C901290035 Number of DELETE -BSS-PFC-ACK messages sent by BSC ......35-25
35.37 C901290036 Number of DELETE -BSS-PFC-REQ messages received by
BSC..............................................................................................................35-26
Chapter 36 NSVC Statistic Measurement............................................... 36-1

36.1 Overview ....................................................................................................... 36-2
36.2 C901300001 Time of PVC unavailable............................................................. 36-2
36.3 C901300002 Time of PVC congestion frame relay ............................................ 36-3
36.4 C901300003 Time of PVC congestion of level 1 ............................................... 36-4
36.5 C901300004 Number of bytes received from SGSN ......................................... 36-4
36.6 C901300005 Number of bytes sent to SGSN ................................................... 36-5
36.7 C901300006 Number of PDU data sent by NS sub layer................................... 36-5
36.8 C901300007 Number of PDU data received by NS sub layer ............................ 36-6
36.9 C901300008 Number of PDU data discarded by NS sub layer .......................... 36-7
36.10 C901300009 Number of reset messages send to opposite end by NS sub
layer .............................................................................................................. 36-8
36.11 C901300010 Number of received reset messages sent by opposite end .......... 36-8
36.12 C901300011 Number of reset confirm messages send to opposite end by NS
sub layer ........................................................................................................ 36-9
36.13 C901300012 Number of received reset confirm messages sent by opposite
end ...............................................................................................................36-10
36.14 C901300013 Number of blocking messages send to opposite end by NS sub
layer ............................................................................................................. 36-11
36.15 C901300014 Number of received blocking messages sent by opposite
end ............................................................................................................... 36-11
36.16 C901300015 Number of blocking confirm messages send to opposite end by
NS sub layer .................................................................................................36-12
36.17 C901300016 Number of received blocking confirm messages sent by
opposite end .................................................................................................36-13
36.18 C901300017 Number of unblocking messages send to opposite end by NS
sub layer .......................................................................................................36-14
LXXX
36.19 C901300018 Number of received unblocking messages sent by opposite
end ...............................................................................................................36-14
36.20 C901300019 Number of unblocking confirm messages send to opposite end
by NS sub layer .............................................................................................36-15
36.21 C901300020 Number of received unblocking acknowledge messages replied
by opposite end .............................................................................................36-16
36.22 C901300021 Number of abnormal cases in NS transmission due to network
fault ..............................................................................................................36-17
36.23 C901300022 Number of abnormal cases in NS transmission due to O&M
interference ...................................................................................................36-17
36.24 C901300023 Number of abnormal cases in NS transmission due to
equipment fault..............................................................................................36-18
36.25 C901300024 Number of abnormal cases in NS transmission due to NSVC
block.............................................................................................................36-19
36.26 C901300025 Number of abnormal cases in NS transmission due to unknown
NSVC ...........................................................................................................36-20
36.27 C901300026 Number of abnormal cases in NS transmission due to protocol
error .............................................................................................................36-20
36.28 C901300027 Number of test failure (while over max) .....................................36-21
36.29 C901300028 Number of blocking procedure failure (after exceeding the
maximum times) ............................................................................................36-22
36.30 C901300029 Number of unblocking procedure failure (after exceeding the
maximum times) ............................................................................................36-23
36.31 C901300030 Number of congestion occurrence of level 1 ..............................36-24
36.32 C901300031 Number of congestion recovery of level 1..................................36-24
36.37 C901300036 Number of BECN.....................................................................36-26
36.38 C901300037 Number of FECN .....................................................................36-26
Chapter 37 NSE Statistic Measurement ................................................. 37-1

37.1 Overview ....................................................................................................... 37-2
37.2 C901310001 Number of CS Paging received by BSS ....................................... 37-2
37.3 C901310002 Number of PS Paging received by BSS ....................................... 37-3
37.4 C901310003 Number of SUSPEND message sent ........................................... 37-4
37.5 C901310004 Number of SUSPEND-ACK message received............................. 37-4
37.6 C901310005 Number of SUSPEND-NACK message received .......................... 37-5
37.7 C901310006 Number of RESUME message sent............................................. 37-6
LXXXI
37.8 C901310007 Number of RESUME-ACK message received............................... 37-7
37.9 C901310008 Number of RESUME-NACK message received ............................ 37-7
37.10 C901310009 Number of FLUSH-LL message received ................................... 37-8
37.11 C901310010 Number of FLUSH-LL-ACK message sent.................................. 37-9
37.12 C901310011 Number of LLC-DISCARDED message sent..............................37-10
37.13 C901310012 Number of BVC-BLOCK message sent .....................................37-10
37.14 C901310013 Number of BVC_BLOCK_ACK message received ..................... 37-11
37.15 C901310014 Number of BVC-UNBLOCK message sent ................................37-12
37.16 C901310015 Number of BVC-UNBLOCK-ACK message received ..................37-13
37.17 C901310016 Number of BVC-RESET message sent .....................................37-13
37.19 C901310018 Number of BVC-RESET-ACK message sent .............................37-15
37.20 C901310019 Number of BVC-RESET-ACK message received .......................37-16
37.21 C901310020 Number of PERFORM_LOCATION_REQUEST message
received ........................................................................................................37-16
37.22 C901310021 Number of PERFORM_LOCATION_RESPONSE message
sent ..............................................................................................................37-17
37.23 C901310022 Number of PERFORM_LOCATION_ABORT message
received ........................................................................................................37-18
37.24 C901310023 Number of POSITION_COMMAND message sent .....................37-19
37.25 C901310024 Number of POSITION_RESPONSE message received..............37-19
37.26 C901310025 Number of status messages sent..............................................37-20
37.27 C901310026 Number of status messages received .......................................37-21
37.29 C901310028 Number of status messages sent with cell service congestion ......37-22
37.31 C901310030 Number of status messages sent with processor overload..........37-24
37.32 C901310031 Number of status messages sent with semantically incorrect
PDU .............................................................................................................37-24
37.33 C901310032 Number of status messages sent with invalid mandatory
information element .......................................................................................37-25
37.34 C901310033 Number of status messages sent with missing mandatory IE ......37-25
37.35 C901310034 Number of status messages sent with missing conditional IE ......37-26
37.36 C901310035 Number of status messages sent with unexpected conditional
IE .................................................................................................................37-26
37.37 C901310036 Number of status messages sent with conditional IE error ..........37-27
37.38 C901310037 Number of status messages sent with protocol status
incompatible error..........................................................................................37-27
37.39 C901310038 Number of status messages received with BVCI unknown..........37-28
LXXXII
congestion ....................................................................................................37-29
overload........................................................................................................37-30
37.43 C901310042 Number of status messages received with BVC blocking............37-30
37.44 C901310043 Number of status messages received with semantically
incorrect PDU................................................................................................37-31
37.45 C901310044 Number of status messages received with invalid mandatory
IE .................................................................................................................37-31
37.46 C901310045 Number of status messages received with missing mandatory
IE .................................................................................................................37-32
37.47 C901310046 Number of status messages received with missing conditional
IE .................................................................................................................37-32
37.48 C901310047 Number of status messages received with unexpected
conditional IE ................................................................................................37-33
37.49 C901310048 Number of status messages received with conditional IE
error .............................................................................................................37-34
37.50 C901310049 Number of status messages received with protocol status
37.51 C901310050 Number of status messages received with SGSN congestion ......37-35
Chapter 38 BTS TRX Measurement ........................................................ 38-1

38.1 Overview ....................................................................................................... 38-2
38.2 C901320001 Number of normal increases of MS power due to UL signal
level............................................................................................................... 38-3
38.3 C901320002 Number of rapid increase in MS power due to UL signal level........ 38-4
38.4 C901320003 Number of normal decrease of MS power due to UL signal level ..... 38-5
38.5 C901320004 Number of rapid decrease in MS power due to UL signal level ...... 38-6
38.6 C901320005 Number of normal increases of BS power due to DL signal level ..... 38-7
38.7 C901320006 Number of rapid increase in BS power due to DL signal level ........ 38-8
38.8 C901320007 Number of normal decrease of BS power due to DL signal level ..... 38-9
38.9 C901320008 Number of rapid decrease in BS power due to DL signal level ......38-10
38.10 C901320009 Number of normal increases of MS power due to UL signal
quality........................................................................................................... 38-11
38.11 C901320010 Number of rapid increase in MS power due to UL signal
quality...........................................................................................................38-12
38.12 C901320011 Number of normal decrease of MS power due to UL signal
quality...........................................................................................................38-13
38.13 C901320012 Number of rapid decrease in MS power due to UL signal
quality...........................................................................................................38-14
LXXXIII
38.14 C901320013 Number of normal increases of BS power due to DL signal
quality...........................................................................................................38-15
38.15 C901320014 Number of rapid increase in BTS power due to DL signal
quality...........................................................................................................38-16
38.16 C901320015 Number of normal decrease of BS power due to DL signal
quality...........................................................................................................38-17
38.17 C901320016 Number of rapid decrease in BTS power due to DL signal
quality...........................................................................................................38-18
38.18 C901320017 Total value of each result of regular scanning of MS utilization
power ...........................................................................................................38-19
38.19 C901320018 Number of regular scanning and sampling of MS utilization
power ...........................................................................................................38-20
38.20 C901320019 Total value of each result of regular scanning of BS utilization
power ...........................................................................................................38-21
38.21 C901320020 Number of regular scanning and sampling of BS utilization
power ...........................................................................................................38-22
38.22 C901320021 Total value of power scans of DL signal level.............................38-23
38.23 C901320022 Number of power scans of DL signal level .................................38-24
38.24 C901320023 Total value of power scans of UL signal level.............................38-25
38.25 C901320024 Number of power scans of UL signal level .................................38-26
38.26 C901320025 Total value of power scans of DL signal quality ..........................38-27
38.27 C901320026 Number of power scans of DL signal quality ..............................38-28
38.28 C901320027 Total value of power scans of UL signal quality ..........................38-29
38.29 C901320028 Number of power scans of UL signal quality ..............................38-30
38.30 C901320029 Maximum value of UL signal level in regular scan ......................38-31
38.31 C901320030 Minimum value of UL signal level in regular scan .......................38-32
38.32 C901320031 Maximum value obtained in regular scan of DL signal level ........38-33
38.33 C901320032 Minimum value obtained in regular scan of DL signal level .........38-34
38.34 C901320033 Sum of Periodic BS Power (TCH/F) Search Result ....................38-35
38.35 C901320034 Periodic BS Power (TCH/F) Search Times ................................38-35
38.36 C901320035 Sum of Periodic BS Power (TCH/H) Search Result ....................38-36
38.37 C901320036 Number of Periodic BS Power (TCH/H) Search .........................38-36
38.38 C901320037 Sum of Periodic BS Power (SDCCH) Search Result ..................38-37
38.39 C901320038 Number of Periodic BS Power (SDCCH) Search........................38-37
38.40 C901320039 Sum of Periodic DL Signal Level (TCH/F) Search Result............38-38
38.41 C901320040 Number of Periodic DL Signal Level (TCH/F) Search .................38-38
38.42 C901320041 Sum of Periodic DL Signal Level (TCH/H) Search Result ...........38-39
38.43 C901320042 Number of Periodic DL Signal Level (TCH/H) Search.................38-39
38.44 C901320043 Sum of Periodic DL Signal Level (SDCCH) Search Result..........38-40
LXXXIV
38.45 C901320044 Number of Periodic DL Signal Level (SDCCH) Search ...............38-40
Chapter 39 NSVC on IPGB HOST Measurement.................................... 39-1

39.1 Overview ....................................................................................................... 39-1
39.2 C901330001 Time of PVC unavailable............................................................. 39-1
39.3 C901330002 Number of abnormal cases in NS transmission due to network
fault ............................................................................................................... 39-2
39.4 C901330003 Number of abnormal cases in NS transmission due to O&M
interference .................................................................................................... 39-2
39.5 C901330004 Number of abnormal cases in NS transmission due to equipment
fault ............................................................................................................... 39-2
39.6 C901330005 Number of abnormal cases in NS transmission due to unknown
NSVC ............................................................................................................ 39-3
39.7 C901330006 Number of abnormal cases in NS transmission due to protocol
error .............................................................................................................. 39-3
39.8 C901330007 Number of unsuccess test due to over max .................................. 39-4
Chapter 40 GB Message on IPGB HOST Measurement ........................ 40-1

40.1 Overview ....................................................................................................... 40-2
40.2 C901340001 Number of RA-CAPABILITY message recevied ............................ 40-2
40.7 C901340006 Number of wireless status PDU messages sent by BSC ............... 40-6
40.8 C901340007 Number of wireless status messages sent by BSC due to losing
wireless association with MS ........................................................................... 40-7
40.9 C901340008 Number of wireless status messages sent by BSC due to bad
link quality ...................................................................................................... 40-7
40.10 C901340009 Number of wireless status messages sent by BSC due to cell
reselection command...................................................................................... 40-8
40.11 C901340010 Number of FLOW-CONTROL-BVC messages sent by BSC......... 40-9
BSC............................................................................................................... 40-9
40.13 C901340012 Number of FLOW-CONTROL-MS messages sent by BSC .........40-10
BSC.............................................................................................................. 40-11
BSC..............................................................................................................40-12
40.17 C901340016 Number of status messages sent by BSC .................................40-13
LXXXV
40.18 C901340017 Number of status messages received by BSC ...........................40-14
40.22 C901340021 Number of status messages sent with Processor overload .........40-16
40.23 C901340022 Number of status messages received with BVCI Unknown .........40-17
congestion ....................................................................................................40-17
overload........................................................................................................40-18
BSC..............................................................................................................40-19
BSC..............................................................................................................40-21
BSC..............................................................................................................40-23
40.34 C901340033 Number of DELETE-BSS-PFC-ACK messages sent by BSC ......40-24
40.35 C901340034 Number of DELETE-BSS-PFC-REQ messages received by
BSC..............................................................................................................40-25
40.36 C901340035 Number of PS-HANDOVER-REQUIRED messages sent by
BSC..............................................................................................................40-25
40.37 C901340036 Number of PS-HANDOVER-REQUIRED-ACK messages
received by BSC............................................................................................40-26
received by BSC............................................................................................40-27
40.39 C901340038 Number of PS-HANDOVER-REQUEST messages received by
BSC..............................................................................................................40-28
40.40 C901340039 Number of PS-HANDOVER-REQUEST-ACK messages sent by
BSC..............................................................................................................40-29
40.41 C901340040 Number of PS-HANDOVER-REQUEST-NACK messages sent
by BSC .........................................................................................................40-30
40.42 C901340041 Number of PS-HANDOVER-COMPLETE messages sent by
BSC..............................................................................................................40-32
40.43 C901340042 Number of PS-HANDOVER-CANCEL messages sent by
BSC..............................................................................................................40-32
LXXXVI
40.44 C901340043 Number of PS-HANDOVER-REQUEST messages with Service
UTRAN CCO received by BSC .......................................................................40-33
40.45 C901340044 Number of CREATE-BSS-PFC messages with Service UTRAN
CCO received by BSC ...................................................................................40-34
Chapter 41 NSE on IPGB HOST Measurement ...................................... 41-1

41.1 Overview ....................................................................................................... 41-2
41.2 C901350001 Number of CS Paging received by BSS ....................................... 41-2
41.3 C901350002 Number of PS Paging received by BSS ....................................... 41-3
41.10 C901350009 Number of FLUSH-LL message received ................................... 41-7
41.11 C901350010 Number of FLUSH-LL-ACK message sent.................................. 41-8
41.12 C901350011 Number of LLC-DISCARDED message sent............................... 41-8
41.13 C901350012 Number of BVC-BLOCK message sent ...................................... 41-9
41.14 C901350013 Number of BVC_BLOCK_ACK message received .....................41-10
41.15 C901350014 Number of BVC-UNBLOCK message sent ................................41-10
41.16 C901350015 Number of BVC-UNBLOCK-ACK message received .................. 41-11
41.17 C901350016 Number of BVC-RESET message sent ..................................... 41-11
41.19 C901350018 Number of BVC-RESET-ACK message sent .............................41-13
41.20 C901350019 Number of BVC-RESET-ACK message received .......................41-13
41.21 C901350020 Number of PERFORM LOCATION-REQUEST message
received ........................................................................................................41-14
41.22 C901350021 Number of PERFORM-LOCATION-RESPONSE message
sent ..............................................................................................................41-15
41.23 C901350022 Number of PERFORM-LOCATION-ABORT message
received ........................................................................................................41-15
41.24 C901350023 Number of POSITION-COMMAND message sent......................41-16
41.25 C901350024 Number of POSITION-RESPONSE message received ..............41-17
41.26 C901350025 Number of status messages sent..............................................41-17
41.27 C901350026 Number of status messages received .......................................41-18
LXXXVII
41.31 C901350030 Number of status messages sent with processor overload..........41-21
41.32 C901350031 Number of status messages sent with semantically incorrect
PDU .............................................................................................................41-21
41.33 C901350032 Number of status messages sent with invalid mandatory
information element .......................................................................................41-22
41.34 C901350033 Number of status messages sent with missing mandatory IE ......41-23
41.35 C901350034 Number of status messages sent with missing conditional IE ......41-23
41.36 C901350035 Number of status messages sent with unexpected conditional
IE .................................................................................................................41-24
41.37 C901350036 Number of status messages sent with conditional IE error ..........41-25
41.38 C901350037 Number of status messages sent with protocol status
41.39 C901350038 Number of status messages received with BVCI unknown..........41-26
congestion ....................................................................................................41-27
overload........................................................................................................41-28
41.43 C901350042 Number of status messages received with BVC blocking............41-29
41.44 C901350043 Number of status messages received with semantically
incorrect PDU................................................................................................41-29
41.45 C901350044 Number of status messages received with invalid mandatory
IE .................................................................................................................41-30
41.46 C901350045 Number of status messages received with missing mandatory
IE .................................................................................................................41-31
41.47 C901350046 Number of status messages received with missing conditional
IE .................................................................................................................41-31
41.48 C901350047 Number of status messages received with unexpected
conditional IE ................................................................................................41-32
41.49 C901350048 Number of status messages received with conditional IE
error .............................................................................................................41-33
41.50 C901350049 Number of status messages received with protocol status
41.51 C901350050 Number of status messages received with SGSN congestion ......41-34
Chapter 42 BSSMAP Message Measurement ........................................ 42-1

42.1 Overview ....................................................................................................... 42-3
42.2 C901360001 Number of ASSIGNMENT REQUEST messages.......................... 42-4
42.3 C901360002 Number of ASSIGNMENT COMPLETE messages ....................... 42-4
42.4 C901360003 Number of ASSIGNMENT FAILURE messages............................ 42-5
LXXXVIII
42.5 C901360004 Number of RESOURCE REQUEST messages............................. 42-6
42.6 C901360005 Number of RESOURCE INDICATION messages.......................... 42-7
42.7 C901360006 Number of PAGING messages .................................................... 42-8
42.8 C901360007 Number of CIPHER MODE COMMAND messages....................... 42-8
42.9 C901360008 Number of CIPHER MODE COMPLETE messages ...................... 42-9
42.10 C901360009 Number of CIPHER MODE REJECT messages ........................42-10
42.11 C901360010 Number of sent CLASSMARK UPDATE messages .................... 42-11
42.12 C901360011 Number of received CLASSMARK UPDATE messages..............42-12
42.13 C901360012 Number of QUEUING INDICATION messages ..........................42-12
42.14 C901360013 Number of COMPLETE LAYER 3 INFORMATION messages ......42-13
42.15 C901360014 Number of CLASSMARK REQUEST messages ........................42-14
42.16 C901360015 Number of uplink LOAD INDICATION messages .......................42-15
42.17 C901360016 Number of downlink LOAD INDICATION messages ...................42-16
42.18 C901360017 Number of HANDOVER REQUEST messages ..........................42-16
42.19 C901360018 Number of HANDOVER REQUIRED messages ........................42-17
42.20 C901360019 Number of HANDOVER COMMAND messages ........................42-18
42.21 C901360020 Number of HANDOVER REQUEST ACK messages ..................42-19
42.22 C901360021 Number of HANDOVER COMPLETE messages........................42-20
42.23 C901360022 Number of HANDOVER SUCCEEDED messages .....................42-21
42.24 C901360023 Number of HANDOVER CANDIDATE ENQUIRE messages .......42-22
42.25 C901360024 Number of HANDOVER CANDIDATE RESPONSE
messages .....................................................................................................42-23
42.26 C901360025 Number of HANDOVER FAILURE messages ............................42-24
42.27 C901360026 Number of HANDOVER PERFORMED messages.....................42-25
42.28 C901360027 Number of HANDOVER REQUIRED REJECT messages...........42-25
42.29 C901360028 Number of HANDOVER DETECT messages.............................42-26
42.30 C901360029 Number of CLEAR COMMAND messages ................................42-27
42.31 C901360030 Number of CLEAR COMPLETE messages ...............................42-28
42.32 C901360031 Number of CLEAR REQUEST messages..................................42-28
42.33 C901360032 Number of SAPI "N" REJECT messages...................................42-29
42.34 C901360033 Number of UL CONFUSION messages.....................................42-30
42.35 C901360034 Number of DL CONFUSION messages.....................................42-31
42.36 C901360035 Number of UL RESET messages..............................................42-32
42.37 C901360036 Number of DL RESET messages..............................................42-32
42.38 C901360037 Number of UL RESET ACKNOWLEDGE messages ..................42-33
42.39 C901360038 Number of DL RESET ACKNOWLEDGE messages ..................42-34
42.40 C901360039 Number of UL OVERLOAD messages ......................................42-35
42.41 C901360040 Number of DL OVERLOAD messages ......................................42-35
LXXXIX
42.42 C901360041 Number of MSC INVOKE TRACE messages.............................42-36
42.43 C901360042 Number of sent BSS INVOKE TRACE messages ......................42-37
42.44 C901360043 Number of received BSS INVOKE TRACE messages ................42-38
42.45 C901360044 Number of sent CONNECTIONLESS INFORMATION
messages .....................................................................................................42-39
42.46 C901360045 Number of received CONNECTIONLESS INFORMATION
messages .....................................................................................................42-39
42.47 C901360046 Number of SUSPEND messages..............................................42-40
42.48 C901360047 Number of RESUME messages................................................42-41
42.49 C901360048 Number of Common ID messages ............................................42-42
42.50 C901360049 Number of LSA INFORMATION messages ...............................42-42
42.51 C901360050 Number of PERFORM LOCATION REQUEST messages ..........42-43
42.52 C901360051 Number of PERFORM LOCATION RESPONSE messages ........42-44
42.53 C901360052 Number of PERFORM LOCATION ABORT messages ...............42-45
42.54 C901360053 Number of sent BLOCK messages ...........................................42-45
42.55 C901360054 Number of received BLOCK ACK messages .............................42-46
42.56 C901360055 Number of sent UNBLOCK messages ......................................42-47
42.57 C901360056 Number of received UNBLOCK ACK messages ........................42-48
42.58 C901360057 Number of received BLOCK messages .....................................42-49
42.59 C901360058 Number of sent BLOCK ACK messages ...................................42-49
42.60 C901360059 Number of received UNBLOCK messages ................................42-50
42.61 C901360060 Number of sent UNBLOCK ACK messages...............................42-51
42.62 C901360061 Number of UL RESET CIRCUIT messages ...............................42-52
42.63 C901360062 Number of DL RESET CIRCUIT messages ...............................42-53
42.64 C901360063 Number of UL RESET CIRCUIT ACK messages .......................42-53
42.65 C901360064 Number of DL RESET CIRCUIT ACK messages .......................42-54
42.66 C901360065 Number of UL CIRCUIT GROUP BLOCK messages..................42-55
42.67 C901360066 Number of DL CIRCUIT GROUP BLOCK messages..................42-56
42.68 C901360067 Number of UL CIRCUIT GROUP BLOCKING ACKNOWLEDGE
messages .....................................................................................................42-57
42.69 C901360068 Number of DL CIRCUIT GROUP BLOCKING ACKNOWLEDGE
messages .....................................................................................................42-58
42.70 C901360069 Number of UL CIRCUIT GROUP UNBLOCK messages .............42-58
42.71 C901360070 Number of DL CIRCUIT GROUP UNBLOCK messages .............42-59
42.72 C901360071 Number of UL CIRCUIT GROUP UNBLOCKING
ACKNOWLEDGE messages ..........................................................................42-60
42.73 C901360072 Number of DL CIRCUIT GROUP UNBLOCKING
XC
42.74 C901360073 Number of UL UNEQUIPPED CIRCUIT messages ....................42-62
42.75 C901360074 Number of DL UNEQUIPPED CIRCUIT messages ....................42-63
42.76 C901360075 Number of CHANGE CIRCUIT messages .................................42-63
42.77 C901360076 Number of CHANGE CIRCUIT ACK messages .........................42-64
42.78 C901360077 Number of HANDOVER PERFORMED ACK messages .............42-65
42.79 C901360078 The count of Sending INTERNAL HANDOVER REQUIRED .......42-66
42.80 C901360079 The count of Receiving INTERNAL HANDOVER COMMAND ......42-68
42.81 C901360080 The count of Receiving INTERNAL HANDOVER REJECT .........42-70
42.82 C901360081 Number of INTERNAL HANDOVER ENQUIRY messages .........42-70
42.83 C901360082 Number of UL RESET IP RESOURCE messages......................42-71
42.84 C901360083 Number of UL RESET IP RESOURCE ACKOWNLEDGE
messages .....................................................................................................42-72
42.85 C901360084 Number of DL RESET IP RESOURCE messages......................42-73
42.86 C901360085 Number of DL RESET IP RESOURCE ACKNOWLEDGE
messages .....................................................................................................42-73
Chapter 43 A-Interface Message Measurement..................................... 43-1

43.1 Overview ....................................................................................................... 43-1
43.2 C901370001 Number of UL DTAP messages................................................... 43-1
43.3 C901370002 Number of DL DTAP messages................................................... 43-2
43.4 C901370003 Number of UL BSSMAP messages.............................................. 43-3
43.5 C901370004 Number of DL BSSMAP messages.............................................. 43-3
43.6 C901370005 Number of DL BSSMAP messages received with error ................. 43-4
43.7 C901370006 Number of chosen for MSC Load share by NULL_NRI.................. 43-5
43.8 C901370007 Number of chosen for MSC Load share by the NRI not in the
MSC pool....................................................................................................... 43-5
Chapter 44 Terrestrial Resource Availability Measurement ................. 44-1

44.1 Overview ....................................................................................................... 44-1
44.2 C901380001 Mean number of available trunk circuits ....................................... 44-2
44.3 C901380002 Mean number of unavailable trunk circuits.................................... 44-2
44.4 C901380003 Maximum number of busy trunk circuits ....................................... 44-3
44.5 C901380004 Busy time of trunk circuit ............................................................. 44-3
44.6 C901380005 Congestion time of trunk circuit.................................................... 44-4
44.7 C901380006 Mean number of available UDP port ............................................ 44-4
44.8 C901380007 Mean number of unavailable UDP port......................................... 44-5
44.9 C901380008 Number of allocation AIPB board success.................................... 44-5
44.10 C901380009 Number of allocation AIPB board failure ..................................... 44-6
44.11 C901380010 Maximum number of seizure UDP port ....................................... 44-7
XCI
44.12 C901380011 Number of successful one time request UDP port to AIPB ........... 44-8
44.13 C901380012 Number of successful two time request UDP port to AIPB ........... 44-9
44.14 C901380013 Number of successful three time request UDP port to AIPB........44-10
44.15 C901380014 Number of failure request UDP port to AIPB .............................. 44-11
44.16 C901380015 Seizure duration of UDP port....................................................44-12
44.17 C901380019 Mean number of busy trunk circuits...........................................44-12
44.18 C901380020 Mean number of seizure UDP port............................................44-14
Chapter 45 Ater Message Measurement ................................................ 45-1

45.1 Overview ....................................................................................................... 45-2
45.2 C901390001 Number of UL BLOCK Ater single CIRCUIT messages ................. 45-3
45.3 C901390002 Number of DL BLOCKING Ater single CIRCUIT ACKNOWLEDGE
messages ...................................................................................................... 45-3
45.4 C901390003 Number of UL UNBLOCK Ater single CIRCUIT messages ............ 45-4
45.5 C901390004 Number of DL UNBLOCKING Ater single CIRCUIT
ACKNOWLEDGE messages ........................................................................... 45-4
45.6 C901390005 Number of DL BLOCK Ater single CIRCUIT messages ................. 45-5
45.7 C901390006 Number of UL BLOCKING Ater single CIRCUIT ACKNOWLEDGE
messages ...................................................................................................... 45-5
45.8 C901390007 Number of DL UNBLOCK Ater single CIRCUIT messages ............ 45-6
45.9 C901390008 Number of UL UNBLOCKING Ater single CIRCUIT
ACKNOWLEDGE messages ........................................................................... 45-6
45.10 C901390009 Number of UL RESET Ater CIRCUIT messages ......................... 45-7
45.11 C901390010 Number of DL RESET Ater CIRCUIT messages ......................... 45-7
45.12 C901390011 Number of UL RESET Ater CIRCUIT ACKNOWLEDGE
messages ...................................................................................................... 45-8
45.13 C901390012 Number of DL RESET Ater CIRCUIT ACKNOWLEDGE
messages ...................................................................................................... 45-8
45.14 C901390013 Number of UL BLOCK Ater GROUP CIRCUIT messages............ 45-9
45.15 C901390014 Number of DL BLOCK Ater GROUP CIRCUIT messages............ 45-9
45.16 C901390015 Number of UL BLOCKING Ater GROUP CIRCUIT
45.17 C901390016 Number of DL BLOCKING Ater GROUP CIRCUIT
45.18 C901390017 Number of UL UNBLOCK GROUP CIRCUIT messages on
Ater .............................................................................................................. 45-11
45.19 C901390018 Number of DL UNBLOCK Ater GROUP CIRCUIT messages ...... 45-11
45.20 C901390019 Number of UL UNBLOCKING Ater GROUP CIRCUIT
XCII
45.21 C901390020 Number of DL UNBLOCKING Ater GROUP CIRCUIT
45.22 C901390021 Number of UL UNEQUIPPED Ater CIRCUIT messages .............45-13
45.23 C901390022 Number of DL UNEQUIPPED Ater CIRCUIT messages .............45-13
45.24 C901390023 Number of UL BLOCK A CIRCUIT messages............................45-14
45.25 C901390024 Number of DL BLOCKING A CIRCUIT ACKNOWLEDGE
messages .....................................................................................................45-14
45.26 C901390025 Number of UL UNBLOCK A CIRCUIT messages .......................45-14
45.27 C901390026 Number of DL UNBLOCKING A CIRCUIT ACKNOWLEDGE
messages .....................................................................................................45-15
45.28 C901390027 Number of DL BLOCK A CIRCUIT messages............................45-15
45.29 C901390028 Number of UL BLOCKING A CIRCUIT ACKNOWLEDGE
messages .....................................................................................................45-16
45.30 C901390029 Number of DL UNBLOCK A CIRCUIT messages .......................45-16
45.31 C901390030 Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE
messages .....................................................................................................45-17
45.32 C901390031 Number of UL BLOCK A CIRCUIT GROUP messages...............45-17
45.33 C901390032 Number of DL BLOCK A CIRCUIT GROUP messages...............45-18
45.34 C901390033 Number of UL BLOCKING A CIRCUIT GROUP
45.35 C901390034 Number of DL BLOCKING A CIRCUIT GROUP
45.36 C901390035 Number of UL UNBLOCK A CIRCUIT GROUP messages..........45-19
45.37 C901390036 Number of DL UNBLOCK A CIRCUIT GROUP messages..........45-20
45.38 C901390037 Number of UL UNBLOCKING A CIRCUIT GROUP
45.39 C901390038 Number of DL UNBLOCKING A CIRCUIT GROUP
45.40 C901390039 Number of UL UNEQUIPPED A CIRCUIT messages .................45-21
45.41 C901390040 Number of DL UNEQUIPPED A CIRCUIT messages .................45-22
45.42 C901390041 Number of UL Ater RESET messages ......................................45-22
45.43 C901390042 Number of DL Ater RESET messages ......................................45-22
45.44 C901390043 Number of UL Ater RESET ACKNOWLEDGE messages ...........45-23
45.45 C901390044 Number of DL Ater RESET ACKNOWLEDGE messages ...........45-23
45.46 C901390045 Number of UL Ater CONFUSION messages..............................45-24
45.47 C901390046 Number of DL Ater CONFUSION messages..............................45-24
45.48 C901390047 Number of RESOURCE REQUEST messages ..........................45-25
45.49 C901390048 Number of RESOURCE INDICATION messages .......................45-25
45.50 C901390049 Number of RESOURCE NON-INDICATION messages ..............45-26
XCIII
45.51 C901390050 Number of resource release request messages .........................45-26
45.52 C901390051 Number of resource release acknowledge messages.................45-27
45.53 C901390052 Number of resource failure messages.......................................45-27
45.54 C901390053 Number of TFO status messages .............................................45-28
45.55 C901390054 Number of TFO common voice type messages .........................45-28
45.56 C901390055 Number of TFO control messages ............................................45-28
Chapter 46 MTP2 Signal Link Measurement .......................................... 46-1

46.1 Overview ....................................................................................................... 46-1
46.2 C901400001 Number of error SU due to Abnormal Flag ................................... 46-1
46.3 C901400002 Number of error SU Length Error................................................. 46-2
46.4 C901400003 Number of Out of Alignment ........................................................ 46-3
46.5 C901400004 Number of error SU due not to Octet............................................ 46-3
46.6 C901400005 Number of error SU due to CRC Error.......................................... 46-4
46.7 C901400006 Number of Other error ................................................................ 46-4
46.8 C901400007 Number of Negative Acknowledgement Received......................... 46-5
46.9 C901400008 Octets of MSU Retransmitted ...................................................... 46-5
46.10 C901400009 Number of MSU Resend ........................................................... 46-6
46.11 C901400010 Number of Align Error ............................................................... 46-6
46.12 C901400011 Number of Error SU .................................................................. 46-6
46.13 C901400012 Number of MSU discarded due to congestion ............................. 46-7
46.14 C901400013 Number of SL failure due to Abnormal FIBR BSNR..................... 46-7
46.15 C901400014 Number of SL failure due to Excessive delay of ack .................... 46-8
46.16 C901400015 Number of SL failure due to Excessive error rate ........................ 46-8
46.17 C901400016 Number of SL failure due to Excessive duration of congestion ..... 46-9
Chapter 47 CPU MEM Measurement....................................................... 47-1

47.1 Overview ....................................................................................................... 47-1
47.2 C901410001 Peak memory usage of the main processor.................................. 47-1
47.3 C901410002 Mean value of the memory usage................................................ 47-2
47.4 C901410003 Peak load of CPU usage of the main processor............................ 47-2
47.5 C901410004 Mean ratio of the CPU usage ...................................................... 47-3
47.6 C901410005 Duration of the main processor keeping in peak state ................... 47-3
47.7 C901410006 The time when peak load CPU usage occurred ............................ 47-4
47.8 C901410007 peak kilo-bytes of the rest UB...................................................... 47-4
47.9 C901410008 Mean kilo-bytes of the rest UB..................................................... 47-5
Chapter 48 SCTP AS Measurement ........................................................ 48-1

48.1 Overview ....................................................................................................... 48-1
48.2 C901420001 Number of IP packets dropped by SCTP due to some reasons...... 48-2
XCIV
48.3 C901420002 Number of received SCTP packets .............................................. 48-2
48.4 C901420003 Bytes of packets received from ip ................................................ 48-3
48.5 C901420004 Number of packets sent to ip....................................................... 48-3
48.6 C901420005 Bytes of packets sent to ip .......................................................... 48-4
48.7 C901420006 Number of messages sent to ulp ................................................. 48-4
48.8 C901420007 Bytes of messages sent to ulp..................................................... 48-5
48.9 C901420008 Number of messages received from ulp ....................................... 48-5
48.10 C901420009 Bytes of messages received from .............................................. 48-6
48.11 C901420010 Number of Congestion .............................................................. 48-6
48.12 C901420011 Duration of congestion .............................................................. 48-7
48.13 C901420012 Chunk number of fast retransmission ......................................... 48-7
48.14 C901420013 Chunk number of time-out retransmission .................................. 48-8
48.15 C901420014 RTT is lower than T1................................................................. 48-8
48.16 C901420015 RTT is between T1 and T2 ........................................................ 48-9
48.17 C901420016 RTT is higher than T2 ............................................................... 48-9
48.18 C901420017 Number of network transmission dropped packets .....................48-10
48.19 C901420018 Maximum delay of network transmission ...................................48-10
48.20 C901420019 Minimum delay of network transmission .................................... 48-11
48.21 C901420020 Total delay of network transmission(high 4 bytes) ......................48-12
48.22 C901420021 Total delay of network transmission(low 4 bytes)........................48-12
48.23 C901420022 Number of delay samples of network transmission.....................48-13
48.24 C901420023 Maximum dithering of network transmission ..............................48-13
48.25 C901420024 Minimum dithering of network transmission ...............................48-14
48.26 C901420025 Total dithering of network transmission(high 4 bytes)..................48-15
48.27 C901420026 Total dithering of network transmission(low 4 bytes)...................48-15
48.28 C901420027 Number of dithering samples of network transmission ................48-16
48.29 C901420028 Chunks Lost On Send Dirction..................................................48-17
48.30 C901420029 Chunks Trans On Send Dirction ...............................................48-17
Chapter 49 IP Port Performance Statistics ............................................ 49-1

49.1 Overview ....................................................................................................... 49-1
49.2 C901430001 Packets number received............................................................ 49-1
49.3 C901430002 Packets number transmitted........................................................ 49-2
49.4 C901430003 Packets number discarded at rx end ............................................ 49-2
49.5 C901430004 Packets number discarded at tx end ............................................ 49-3
Chapter 50 GTRUNK Resource Statistics .............................................. 50-1

50.1 Overview ....................................................................................................... 50-1
50.2 C901440001 Maximum of used DSP TS .......................................................... 50-1
XCV
50.3 C901440002 Maximum of the used sampling according to DSP TS ................... 50-2
50.4 C901440003 Amount of used DSP TS ............................................................. 50-2
50.5 C901440004 Number of regular scanning and sampling ................................... 50-3
Chapter 51 Other Process Statistics ...................................................... 51-1

51.1 Overview ....................................................................................................... 51-2
51.2 C901450001 Max time of NACC cell reselection............................................... 51-3
51.3 C901450002 Minimum time of NACC cell reselection ....................................... 51-4
51.4 C901450003 Total time of NACC cell reselection .............................................. 51-5
51.5 C901450004 Number of NACC cell reselection (PCCN to flush LL) ................... 51-6
51.6 C901450005 Number of NACC cell reselection without receiving flush LL .......... 51-7
51.7 C901450006 Number of UL packet channel frame adjustment .......................... 51-8
51.8 C901450007 Number of DL packet channel frame adjustment .......................... 51-8
51.9 C901450008 Sum of C ................................................................................... 51-8
51.10 C901450009 Sum of RxQual......................................................................... 51-9
51.11 C901450010 Sum of GMSK-MEAN-BEP.......................................................51-10
51.12 C901450011 Sum of GMSK-CV-BEP ............................................................ 51-11
51.13 C901450012 Sum of 8PSK-MEAN-BEP ........................................................51-12
51.14 C901450013 Sum of 8PSK-CV-BEP .............................................................51-13
51.15 C901450014 Number of sampling of C..........................................................51-14
51.16 C901450015 Number of sampling of RxQual.................................................51-15
51.17 C901450016 Number of sampling of GMSK-MEAN-BEP................................51-16
51.18 C901450017 Number of sampling of GMSK-CV-BEP.....................................51-17
51.19 C901450018 Number of sampling of 8PSK-MEAN-BEP .................................51-18
51.20 C901450019 Number of sampling of 8PSK-CV-BEP ......................................51-19
51.21 C901450020 Number of RLC uplink ACK TBF...............................................51-20
51.22 C901450021 Number of RLC uplink NACK TBF ............................................51-21
51.23 C901450022 Number of DL-UNITDATA messages with Service UTRAN CCO
received by BSC............................................................................................51-22
51.24 C901450023 Total Block Num ......................................................................51-22
51.25 C901450024 UL Idle Block Num...................................................................51-22
51.26 C901450025 DL Idle Block Num...................................................................51-22
51.27 C901450026 The max length of packet latency period in Abis ........................51-22
51.28 C901450027 The min length of packet latency period in Abis .........................51-23
51.29 C901450028 The average length of packet latency period in Abis...................51-23
51.30 C901450029 The latest length of packet latency period in Abis.......................51-24
51.31 C901450030 The length of packet latency period between 0 and 20 ms (20
included) in Abis ............................................................................................51-24
XCVI
51.32 C901450031 The length of packet latency period between 20 ms and 40 ms
(40 included) in Abis ......................................................................................51-25
(60 included) in Abis ......................................................................................51-25
(80 included) in Abis ......................................................................................51-26
(100 included) in Abis ....................................................................................51-26
51.36 C901450035 The length of packet latency period between 100 ms and 120
ms (120 included) in Abis ...............................................................................51-27
51.40 C901450039 The length of packet latency period larger than 180 ms in
Abis ..............................................................................................................51-29
51.41 C901450040 The max length of downlink packet latency period in Gb.............51-29
51.42 C901450041 The min length of downlink packet latency period in Gb .............51-30
51.43 C901450042 The average length of downlink packet latency period in Gb.......51-30
51.44 C901450043 The length of downlink packet latency period between 0 and
100 ms (100 included) in Gb...........................................................................51-31
51.45 C901450044 The length of downlink packet latency period between 100 ms
and 200 ms (200 included) in Gb ....................................................................51-31
and 1000 ms (1000 included) in Gb ................................................................51-33
51.50 C901450049 The length of downlink packet latency period larger than 1000
ms in Gb .......................................................................................................51-34
51.51 C901450050 The max length of uplink packet latency period in Gb.................51-34
51.52 C901450051 The min length of uplink packet latency period in Gb..................51-35
51.53 C901450052 The average length of uplink packet latency period in Gb ...........51-35
51.54 C901450053 LLC Stall Num .........................................................................51-35
51.55 C901450054 MAC Resource Congestion ......................................................51-36
XCVII
51.56 C901450055 BSSGP Resource Congestion ..................................................51-36
Chapter 52 FR Carried Links Statistics .................................................. 52-1

52.1 Overview ....................................................................................................... 52-1
52.2 C901460001 Number of Status enquiry Message sent...................................... 52-1
52.3 C901460002 Number of Status ACK Message received.................................... 52-2
52.4 C901460003 Number of link exception............................................................. 52-3
52.5 C901460004 Number of bytes received on BRCH ............................................ 52-4
52.6 C901460005 Number of bytes sent on BRCH................................................... 52-4
Chapter 53 OMP PS Service Statistics ................................................... 53-1

53.1 Overview ....................................................................................................... 53-1
Chapter 54 SNS on OMP Statistics ......................................................... 54-1

54.1 Overview ....................................................................................................... 54-2
54.2 C901480001 Number of SNS-SIZE initiations................................................... 54-2
54.3 C901480002 Number of SNS-SIZE received successful acknowledgements ...... 54-3
54.4 C901480003 Number of SNS-SIZE failures...................................................... 54-3
54.5 C901480004 Number of SNS-SIZE initiated by BSC without response............... 54-4
54.6 C901480005 Number of SNS-CONFIG initiated by BSC ................................... 54-4
54.7 C901480006 Number of SNS-CONFIG initiated by BSC received successful
acknowledgements ......................................................................................... 54-4
54.8 C901480007 Number of SNS-CONFIG initiated by BSC received failed
54.9 C901480008 Number of SNS-CONFIG initiated by BSC without response ......... 54-5
54.10 C901480009 Number of SNS-CONFIG initiated by SGSN received successful
54.11 C901480010 Number of SNS-CONFIG initiated by SGSN received failed
54.12 C901480011 Number of SNS-ADD initiated by BSC........................................ 54-7
54.13 C901480012 Number of SNS-ADD initiated by BSC received successful
54.14 C901480013 Number of SNS-ADD initiated by BSC received failed
54.15 C901480014 Number of SNS-ADD initiated by BSC without response ............. 54-9
XCVIII
54.16 C901480015 Number of SNS-ADD initiated by SGSN received successful
54.17 C901480016 Number of SNS-ADD initiated by SGSN received failed
acknowledgements ........................................................................................54-10
54.18 C901480017 Number of SNS-DELETE initiated by BSC ................................54-10
54.19 C901480018 Number of SNS-DELETE initiated by BSC received successful
acknowledgements ........................................................................................ 54-11
54.20 C901480019 Number of SNS-DELETE initiated by BSC received failed
54.21 C901480020 Number of SNS-DELETE initiated by BSC without response ......54-12
54.22 C901480021 Number of SNS-DELETE initiated by SGSN received successful
54.23 C901480022 Number of SNS-DELETE initiated by SGSN received failed
54.24 C901480023 Number of SNS-CHANGEWEIGHT initiated by BSC..................54-14
54.25 C901480024 Number of SNS-CHANGEWEIGHT initiated by BSC received
successful acknowledgements .......................................................................54-14
54.26 C901480025 Number of SNS-CHANGEWEIGHT initiated by BSC received
failed acknowledgements ...............................................................................54-15
54.27 C901480026 Number of SNS-CHANGEWEIGHT initiated by BSC without
response.......................................................................................................54-15
54.28 C901480027 Number of SNS-CHANGEWEIGHT initiated by SGSN received
successful acknowledgements .......................................................................54-16
54.29 C901480028 Number of SNS-CHANGEWEIGHT initiated by SGSN received
failed acknowledgements ...............................................................................54-17
Chapter 55 IPGB StrongARM NSVC Statistics ...................................... 55-1

55.1 Overview ....................................................................................................... 55-1
55.2 C901490001 Number of bytes received from SGSN ......................................... 55-1
55.3 C901490002 Number of bytes sent to SGSN ................................................... 55-1
55.4 C901490003 Number of PDU data sent by NS sub layer................................... 55-2
55.5 C901490004 Number of PDU data received by NS sub layer ............................ 55-2
55.6 C901490005 Number of PDU data discarded by NS sub layer .......................... 55-3
Chapter 56 IPGB StrongARM Gb Statistics ........................................... 56-1

56.1 Overview ....................................................................................................... 56-1
Chapter 57 Queue Measurement............................................................. 57-1

57.1 Overview ....................................................................................................... 57-1
57.2 C901510001 Average length of queue ............................................................. 57-1
XCIX
57.3 C901510002 Duration of queuing .................................................................... 57-2
57.4 C901510003 Number of queuing ..................................................................... 57-4
57.5 C901510004 Duration of queuing success ....................................................... 57-6
57.6 C901510005 Number of queuing success ........................................................ 57-7
Chapter 58 Handover Synchronization Mode Measurement................ 58-1

58.1 Overview ....................................................................................................... 58-1
58.2 C901520001 Number of synchronous handover executions .............................. 58-2
58.3 C901520002 Number of synchronous handover successes............................... 58-3
58.4 C901520003 Number of pre-synchronous handover executions ........................ 58-3
58.5 C901520004 Number of pre-synchronous handover successes......................... 58-4
58.6 C901520005 Number of pseudo-synchronous handover executions .................. 58-4
58.7 C901520006 Number of pseudo-synchronous handover successes................... 58-5
58.8 C901520007 Number of asynchronous handover executions ............................ 58-5
58.9 C901520008 Number of asynchronous handover successes............................. 58-6
Chapter 59 Paging Message Measurement............................................ 59-1

59.1 Overview ....................................................................................................... 59-1
59.2 C901530001 Number of paging messages....................................................... 59-2
59.3 C901530002 Number of paging messages from PS of Gb interface ................... 59-3
59.4 C901530003 Number of paging messages from CS of Gb interface................... 59-4
Chapter 60 Reserved Channel Measurement ........................................ 60-1

60.1 Overview ....................................................................................................... 60-1
60.2 C901540001 Number of voice allocations of reserved full rate channel in
assignment .................................................................................................... 60-1
60.3 C901540002 Number of data allocations of reserved full rate channel in
assignment .................................................................................................... 60-2
60.4 C901540003 Number of voice allocations of reserved full rate channel in
handover........................................................................................................ 60-2
60.5 C901540004 Number of data allocations of reserved full rate channel in
handover........................................................................................................ 60-3
60.6 C901540005 Reserved seizure duration of reserved full rate channel ................ 60-3
Chapter 61 SCCP Connection Measurement ......................................... 61-1

61.1 Overview ....................................................................................................... 61-1
61.2 C901550001 Number of BSC originated SCCP Connection attempts................. 61-1
61.3 C901550002 Number of BSC originated SCCP Connection success ................. 61-2
61.4 C901550003 Number of BSC originated SCCP Connection failure due to
timeout........................................................................................................... 61-4
61.5 C901550004 Number of negative replies for SCCP connection request ............. 61-4
C
61.6 C901550005 Number of MSC originated SCCP Connection Requests............... 61-5
61.7 C901550006 Number of MSC originated SCCP Connection success ................. 61-6
Chapter 62 DTM Cell Measurement ........................................................ 62-1

62.1 Overview ....................................................................................................... 62-2
62.2 C901560001 Number of voice access in mobile with DTM ability ....................... 62-2
62.3 C901560002 Number of packet access in mobile with DTM ability ..................... 62-2
62.4 C901560003 Number of received IMSI when link establish ............................... 62-3
62.5 C901560004 Number of RANCS module received IMSI when handover ............ 62-4
62.6 C901560005 Number of mobile sent GTTP message under DTM mode............. 62-4
62.7 C901560006 Number of BSC successfully sent GTTP message under DTM
mode ............................................................................................................. 62-5
62.8 C901560007 Number of DTM attempts in mobile.............................................. 62-5
62.9 C901560008 Number of DTM uplink attempt failure .......................................... 62-6
62.10 C901560009 Number of UL DTM database resource assignment success in
dedicated mode ............................................................................................. 62-6
62.11 C901560010 Number of UL DTM database resource assignment failure in
dedicated mode ............................................................................................. 62-7
62.12 C901560011 Number of handover(intra-cell) attempts due to UL DTM ............. 62-8
62.13 C901560012 Number of handover(intra-cell) success due to uplink DTM ......... 62-8
62.14 C901560013 Number of handover(intra-cell) failure due to uplink DTM ............ 62-9
62.15 C901560014 Number of DTM failure due to handover..................................... 62-9
62.16 C901560015 Number of UL DTM link establishment success .........................62-10
62.17 C901560016 Attempt number of sending LLC packet on FACCH in dedicated
mode ...........................................................................................................62-10
62.18 C901560017 Number of successfully sent LLC packet on FACCH in
dedicated mode ............................................................................................ 62-11
62.19 C901560018 Attempt Number of DTM established due to SGSN sent LLC
packets ......................................................................................................... 62-11
62.20 C901560019 Number of DTM attempts failure ...............................................62-12
62.21 C901560020 Number of DL DTM resource assignment success.....................62-13
62.22 C901560021 Number of DL DTM resource assignment failure........................62-13
62.23 C901560022 Number of handover(intra-cell) attempts due to DL DTM ............62-14
62.24 C901560023 Number of successfully handover occurs due to DL DTM ...........62-14
62.25 C901560024 Number of handover failure occurs due to DL DTM....................62-15
62.26 C901560025 Number of DL DTM failure occurs due to handover....................62-15
62.27 C901560026 Number of successfully DL DTM establishment .........................62-16
Chapter 63 LAPD Measurement .............................................................. 63-1

63.1 Overview ....................................................................................................... 63-1
CI
63.2 C901570001 Number of Application Data Package from CMP........................... 63-2
63.3 C901570002 Number of BTS Application Data Package Sent to MP.................. 63-2
63.4 C901570003 Number of Data Package Ack Sent to Application......................... 63-2
63.5 C901570004 Number of Application Data Package Ack from BTS ..................... 63-3
63.6 C901570005 Number of Application Nack Data Package sent to BTS................ 63-3
63.7 C901570006 Number of BTS Application Nack Data Package Receive by
BTS ............................................................................................................... 63-4
63.8 C901570007 Number of Sending Frame .......................................................... 63-4
63.9 C901570008 Number of Received Frame ........................................................ 63-4
63.10 C901570009 Number of High Priority Queue overflow .................................... 63-5
63.11 C901570010 Number of Low Priority Queue overflow ..................................... 63-5
63.12 C901570011 Number of Success in High Priority Queue ................................. 63-6
63.13 C901570012 Number of Success in Low Priority Queue.................................. 63-6
63.14 C901570013 Number of in Queue Request UB Fail ........................................ 63-6
63.15 C901570014 Resend Number ....................................................................... 63-7
63.16 C901570015 Resend Request Number.......................................................... 63-7
63.17 C901570016 Establish Link Number .............................................................. 63-8
63.18 C901570017 Broken Number ........................................................................ 63-9
63.19 C901570018 Protocol Error Number .............................................................. 63-9
63.20 C901570019 Number of T200 Overtime ........................................................63-10
63.21 C901570020 Number of T201 Overtime ........................................................63-10
63.22 C901570021 Number of T203 Overtime ........................................................ 63-11
63.23 C901570022 Number of T204 Overtime ........................................................ 63-11
63.24 C901570023 Number of abnormal hop frame ................................................ 63-11
63.25 C901570024 Number of normal hop frame....................................................63-12
63.26 C901570025 Multi Channel Link Lose Frame ................................................63-12
63.27 C901570026 No useful channel....................................................................63-13
63.28 C901570027 Max Up Flow ...........................................................................63-13
63.29 C901570028 Max Down Flow.......................................................................63-13
63.30 C901570029 Current Up Flow ......................................................................63-14
63.31 C901570030 Current Down Flow ..................................................................63-14
Chapter 64 LCS Measurement................................................................. 64-1

64.1 Overview ....................................................................................................... 64-2
64.2 C901580001 Number of receiving location request in CS .................................. 64-2
64.3 C901580002 Number of receiving location abort in CS ..................................... 64-3
64.4 C901580003 Number of TA Request in CS ...................................................... 64-3
64.5 C901580004 Number of TA Response in CS.................................................... 64-4
CII
64.6 C901580005 Number of MS Position Command in CS...................................... 64-5
64.7 C901580006 Number of MS Position Response in CS ...................................... 64-5
64.8 C901580007 Number of location success in CS ............................................... 64-6
64.9 C901580008 Number of location failure due to abnormal status of Lb interface
in CS ............................................................................................................. 64-7
64.10 C901580009 Number of location failure due to radio Timer expiration in CS ..... 64-8
64.11 C901580010 Number of sending BSSLAP RESET message due to Intra-BSS
handover in CS .............................................................................................. 64-9
64.12 C901580011 Number of location failure due to Intra-BSS handover expiration
in CS ............................................................................................................. 64-9
64.13 C901580012 Number of location failure due to location Timer expiration in
CS................................................................................................................64-10
64.14 C901580013 Number of location failure due to Inter-BSS handover in CS ....... 64-11
64.15 C901580014 Number of location failure due to call drop in CS........................64-12
64.16 C901580015 Number of location failure due to other BSC's cause in CS.........64-13
64.17 C901580016 Number of receiving location request in PS ...............................64-13
64.18 C901580017 Number of receiving location abort in PS...................................64-14
64.19 C901580018 Number of TA Request in PS....................................................64-15
64.20 C901580019 Number of TA Response in PS .................................................64-15
64.21 C901580020 Number of MS Position Command in PS ...................................64-16
64.22 C901580021 Number of MS Position Response in PS ...................................64-17
64.23 C901580022 Number of location success in PS.............................................64-17
64.24 C901580023 Number of location failure due to abnormal status of Lb interface
in PS ............................................................................................................64-18
64.25 C901580024 Number of location failure due to radio Timer expiration in
PS ................................................................................................................64-19
64.26 C901580025 Number of location failure due to Inter-CMP cell reselection in
PS ................................................................................................................64-20
64.27 C901580026 Number of sending LOCATION INFORMATION message to
SMLC due to Intra-CMP cell reselection in PS .................................................64-21
64.28 C901580027 Number of location failure due to location Timer expiration in
PS ................................................................................................................64-22
64.29 C901580028 Number of location failure due to other BSC's cause in PS .........64-22
Chapter 65 LB Global Msg Measurement............................................... 65-1

65.1 Overview ....................................................................................................... 65-1
65.2 C901590001 Number of receiving RESET message from SMLC ....................... 65-1
65.3 C901590002 Number of sending RESET ACK message to SMLC ..................... 65-2
65.4 C901590003 Number of sending RESET message to SMLC............................. 65-3
65.5 C901590004 Number of receiving RESET ACK message from SMLC ............... 65-4
CIII
Chapter 66 Ater Interface Relays Measurement .................................... 66-1
66.1 Overview ....................................................................................................... 66-1
66.2 C901600001 Number of configured 16 K relay circuits of Ater interface.............. 66-1
66.3 C901600002 Average of unavailable 16K relay circuits of Ater interface............. 66-2
66.4 C901600003 Average of available 16 K relay circuits of Ater interface ............... 66-3
66.5 C901600004 Maximum of busy 16 K relay circuits of Ater interface ................... 66-4
66.6 C901600005 Maximum of busy 8 K relay circuits of Ater interface ..................... 66-5
66.7 C901600006 Total busy time of 16 K relay circuits of Ater interface.................... 66-7
66.8 C901600007 Total busy time of 8 K relay circuits of Ater interface ..................... 66-8
Chapter 67 Ater Interface SCCP Connections Measurement............... 67-1

67.1 Overview ....................................................................................................... 67-1
67.2 C901610001 Number of SCCP establishment requests (BSC to TC) ................. 67-1
67.3 C901610002 Number of SCCP establishments success (BSC to TC) ................ 67-2
67.4 C901610003 Number of SCCP establishment failure due to timeout (BSC to
TC) ................................................................................................................ 67-3
67.5 C901610004 Number of SCCP establishment refused (BSC to TC) ................... 67-4
Chapter 68 Measurement Report Serving Cell Measurement .............. 68-1

68.1 MR Serving Cell Measurement ........................................................................ 68-5
68.2 C901620001 Number of samples of UL RQ=0 and receive level between 0
and 10 ........................................................................................................... 68-5
and 15 ........................................................................................................... 68-6
and 20 ........................................................................................................... 68-7
and 30 ........................................................................................................... 68-8
and 40 ........................................................................................................... 68-8
and 63 ........................................................................................................... 68-9
and 10 ..........................................................................................................68-10
and 15 .......................................................................................................... 68-11
and 20 .......................................................................................................... 68-11
and 30 ..........................................................................................................68-12
CIV
and 40 ..........................................................................................................68-13
and 63 ..........................................................................................................68-14
and 10 ..........................................................................................................68-15
and 15 ..........................................................................................................68-15
and 20 ..........................................................................................................68-16
and 30 ..........................................................................................................68-17
and 40 ..........................................................................................................68-18
and 63 ..........................................................................................................68-19
and 10 ..........................................................................................................68-19
and 15 ..........................................................................................................68-20
and 20 ..........................................................................................................68-21
and 30 ..........................................................................................................68-22
and 40 ..........................................................................................................68-23
and 63 ..........................................................................................................68-23
and 10 ..........................................................................................................68-24
and 15 ..........................................................................................................68-25
and 20 ..........................................................................................................68-26
and 30 ..........................................................................................................68-27
and 40 ..........................................................................................................68-27
and 63 ..........................................................................................................68-28
CV
and 10 ..........................................................................................................68-29
and 15 ..........................................................................................................68-30
and 20 ..........................................................................................................68-31
and 30 ..........................................................................................................68-31
and 40 ..........................................................................................................68-32
and 63 ..........................................................................................................68-33
and 10 ..........................................................................................................68-34
and 15 ..........................................................................................................68-35
and 20 ..........................................................................................................68-35
and 30 ..........................................................................................................68-36
and 40 ..........................................................................................................68-37
and 63 ..........................................................................................................68-38
and 10 ..........................................................................................................68-39
and 15 ..........................................................................................................68-39
and 20 ..........................................................................................................68-40
and 30 ..........................................................................................................68-41
and 40 ..........................................................................................................68-42
and 63 ..........................................................................................................68-43
68.50 C901620049 Number of samples of DL RQ=0 and receive level between 0
and 10 ..........................................................................................................68-43
and 15 ..........................................................................................................68-44
CVI
and 20 ..........................................................................................................68-45
and 30 ..........................................................................................................68-46
and 40 ..........................................................................................................68-47
and 63 ..........................................................................................................68-47
and 10 ..........................................................................................................68-48
and 15 ..........................................................................................................68-49
and 20 ..........................................................................................................68-50
and 30 ..........................................................................................................68-51
and 40 ..........................................................................................................68-51
and 63 ..........................................................................................................68-52
and 10 ..........................................................................................................68-53
and 15 ..........................................................................................................68-54
and 20 ..........................................................................................................68-55
and 30 ..........................................................................................................68-55
and 40 ..........................................................................................................68-56
and 63 ..........................................................................................................68-57
and 10 ..........................................................................................................68-58
and 15 ..........................................................................................................68-59
and 20 ..........................................................................................................68-59
and 30 ..........................................................................................................68-60
CVII
and 40 ..........................................................................................................68-61
and 63 ..........................................................................................................68-62
and 10 ..........................................................................................................68-63
and 15 ..........................................................................................................68-63
and 20 ..........................................................................................................68-64
and 30 ..........................................................................................................68-65
and 40 ..........................................................................................................68-66
and 63 ..........................................................................................................68-67
and 10 ..........................................................................................................68-67
and 15 ..........................................................................................................68-68
and 20 ..........................................................................................................68-69
and 30 ..........................................................................................................68-70
and 40 ..........................................................................................................68-71
and 63 ..........................................................................................................68-71
and 10 ..........................................................................................................68-72
and 15 ..........................................................................................................68-73
and 20 ..........................................................................................................68-74
and 30 ..........................................................................................................68-75
and 40 ..........................................................................................................68-75
and 63 ..........................................................................................................68-76
CVIII
and 10 ..........................................................................................................68-77
and 15 ..........................................................................................................68-78
and 20 ..........................................................................................................68-79
and 30 ..........................................................................................................68-79
and 40 ..........................................................................................................68-80
and 63 ..........................................................................................................68-81
Chapter 69 Measurement Report Adjacent Cell Measurement ............ 69-1

69.1 MR Adjacent Cell Measurement ...................................................................... 69-1
69.2 C901630001 Number of samples with C/I < -10db ............................................ 69-2
69.3 C901630002 Number of samples with C/I between -9db and -5db ..................... 69-2
69.4 C901630003 Number of samples with C/I between -4db and 0db ...................... 69-3
69.5 C901630004 Number of samples with C/I between 1db and 5db ....................... 69-4
69.6 C901630005 Number of samples with C/I between 6db and 10db ..................... 69-5
69.7 C901630006 Number of samples with C/I between 11db and 15db .................... 69-5
69.8 C901630007 Number of samples with C/I between 16db and 20db.................... 69-6
69.9 C901630008 Number of samples with C/I > 20db ............................................. 69-7
Chapter 70 TRX Paging Measurement.................................................... 70-1

70.1 Overview ....................................................................................................... 70-1
70.2 C901640001 Number of PS paging message discarded due to full of the
queue ............................................................................................................ 70-2
70.3 C901640002 Number of CS paging message discarded due to full of the
queue ............................................................................................................ 70-2
70.4 C901640003 Average length of PCH queue: 9*9 .............................................. 70-3
70.5 C901640004 Average length of PCH queue: 9*64 ............................................ 70-3
Chapter 71 TRX Temperature Power Measurement .............................. 71-1

71.1 Overview ....................................................................................................... 71-1
71.2 C901650001 Maximum value of TRX power (db).............................................. 71-1
71.3 C901650002 Minimum value of TRX power (db)............................................... 71-1
71.4 C901650003 Mean value of TRX power (db) .................................................... 71-2
71.5 C901650004 Maximum of TRX temperature (Celsius)....................................... 71-2
71.6 C901650005 Minimum of TRX temperature (Celsius) ....................................... 71-3
71.7 C901650006 Mean of TRX temperature (Celsius)............................................. 71-3
CIX
Chapter 72 Terminal Ability Statistic ...................................................... 72-1
72.1 Terminal Ability Statistics................................................................................. 72-2
72.2 C901660001 Number of mobile support single TS DTM ability .......................... 72-3
72.3 C901660002 Number of mobile support DTM GPRS multi TS ability 5 ............... 72-3
72.4 C901660003 Number of mobile support DTM GPRS multi TS ability 9 ............... 72-4
72.5 C901660004 Number of mobile support DTM GPRS multi TS ability 11 ............. 72-5
72.6 C901660005 Number of mobile support DTM EGPRS multi TS ability 5............. 72-6
72.7 C901660006 Number of mobile support DTM EGPRS multi TS ability 9............. 72-7
72.8 C901660007 Number of mobile support DTM EGPRS multi TS ability 11 ........... 72-8
72.9 C901660008 Number of mobile support extend DTM GPRS multi TS ability 5 ..... 72-9
72.10 C901660009 Number of mobile support extend DTM GPRS multi TS ability
6...................................................................................................................72-10
9................................................................................................................... 72-11
10.................................................................................................................72-12
11 .................................................................................................................72-13
72.14 C901660013 Number of mobile support extend DTM EGPRS multi TS ability
5...................................................................................................................72-14
6...................................................................................................................72-15
9...................................................................................................................72-16
10.................................................................................................................72-17
11 .................................................................................................................72-18
72.19 C901660018 Number of mobile of GPRS multi TS ability 1.............................72-19
72.28 C901660027 Number of mobile of GPRS multi TS ability 10...........................72-33
72.29 C901660028 Number of mobile of GPRS multi TS ability 11 ...........................72-34
CX
72.36 C901660035 Number of mobile of EGPRS multi TS ability 1 ..........................72-45
72.45 C901660044 Number of mobile of EGPRS multi TS ability 10.........................72-58
72.53 C901660052 Number of mobile support FR...................................................72-70
72.54 C901660053 Number of mobile support HR ..................................................72-71
72.55 C901660054 Number of mobile support EFR ................................................72-72
72.56 C901660055 Number of mobile support AMRFR ...........................................72-72
72.57 C901660056 Number of mobile support AMRHR ...........................................72-73
72.58 C901660057 Number of mobile support wideband AMROFR .........................72-74
72.59 C901660058 Number of mobile support wideband AMRFR ............................72-75
72.60 C901660059 Number of mobile support wideband AMROHR .........................72-76
72.61 C901660060 Number of mobile support AMROHR ........................................72-77
72.62 C901660061 Number of mobile support extend uplink TBF ............................72-78
72.63 C901660062 Number of mobile support NACC..............................................72-79
72.64 C901660063 Number of mobile support GPRS extend dynamic allocation ......72-80
72.65 C901660064 Number of mobile support EGPRS extend dynamic
allocation ......................................................................................................72-82
72.66 C901660065 Number of sampling received Classmark3.................................72-83
CXI
72.67 C901660066 Number of sampling received radio access ability ......................72-84
72.68 C901660069 Num of MS supporting PS handover .........................................72-85
72.69 C901660070 The Number of MS which Support SAIC ...................................72-86
72.70 C901660071 The Number of MS which not Support SAIC ..............................72-87
Chapter 73 MAC Port Flow Statistics ..................................................... 73-1

73.1 Overview ....................................................................................................... 73-1
73.2 C901820001 receive bytes number (high 4 bytes) ............................................ 73-1
73.3 C901820002 receive bytes number (low 4 bytes).............................................. 73-2
73.4 C901820003 transmit bytes number (high 4 bytes) ........................................... 73-2
73.5 C901820004 transmit bytes number (low 4 bytes) ............................................ 73-3
73.6 C901820005 physical band width .................................................................... 73-3
73.7 C901820006 mean receiving bit rate................................................................ 73-3
73.8 C901820007 max receiving bit rate.................................................................. 73-4
73.9 C901820008 mean transmitting bit rate............................................................ 73-4
73.10 C901820009 max transmitting bit rate ............................................................ 73-5
Chapter 74 AMR Rate Statistics .............................................................. 74-1

74.1 Overview ....................................................................................................... 74-1
74.2 C901830001 Total Num of DL AFS12.2k frame ................................................ 74-2
74.10 C901830009 Total Num of DL AHS7.95k frame .............................................. 74-6
74.16 C901830015 Total Num of UL AFS12.2k frame .............................................. 74-9
74.17 C901830016 Total Num of UL AFS10.2k frame .............................................74-10
74.19 C901830018 Total Num of UL AFS7.40k frame ............................................. 74-11
74.20 C901830019 Total Num of UL AFS6.70k frame ............................................. 74-11
CXII
74.24 C901830023 Total Num of UL AHS7.95k frame .............................................74-13
Chapter 75 UMAC Measurement ............................................................. 75-1

75.1 Overview ....................................................................................................... 75-3
75.2 C901850001 receive discard packets flag ........................................................ 75-3
75.3 C901850002 receive discard packets low 32bits............................................... 75-4
75.4 C901850003 receive discard packets high 32bits ............................................. 75-4
75.5 C901850004 receive bytes flag ....................................................................... 75-4
75.6 C901850005 receive bytes low 32bits .............................................................. 75-5
75.7 C901850006 receive bytes high 32bits............................................................. 75-5
75.8 C901850007 receive packets flag.................................................................... 75-5
75.9 C901850008 receive packets low 32bits .......................................................... 75-6
75.10 C901850009 receive packets high 32bits ....................................................... 75-6
75.11 C901850010 receive broadcast packets flag................................................... 75-6
75.12 C901850011 receive broadcast packets low 32bits ......................................... 75-7
75.13 C901850012 receive broadcast packets high 32bits........................................ 75-7
75.14 C901850013 receive multicast packets flag .................................................... 75-8
75.15 C901850014 receive multicast packets low 32bits .......................................... 75-8
75.16 C901850015 receive multicast packets high 32bits ......................................... 75-8
75.17 C901850016 receive CRC or align error packets flag ...................................... 75-9
75.18 C901850017 receive CRC or align error packets low 32bits............................. 75-9
75.19 C901850018 receive CRC or align error packets high 32bits ..........................75-10
75.20 C901850019 receive small than 64 bytes packets flag ...................................75-10
75.21 C901850020 receive small than 64 bytes packets low 32bits ..........................75-10
75.22 C901850021 receive small than 64 bytes packets high 32bits......................... 75-11
75.23 C901850022 receive large than 1518 bytes packets flag ................................ 75-11
75.24 C901850023 receive large than 1518 bytes packets low 32bits.......................75-12
75.25 C901850024 receive large than 1518 bytes packets high 32bits .....................75-12
75.26 C901850025 The flag of received fragment packets.......................................75-12
75.27 C901850026 Number of fragment packets received (low 32 bit)......................75-13
75.28 C901850027 Number of received fragment packets (high 32 bit) ....................75-13
CXIII
75.29 C901850028 receive Jabber packets flag......................................................75-14
75.30 C901850029 receive Jabber packets low 32bits ............................................75-14
75.31 C901850030 receive Jabber packets high 32bits ...........................................75-14
75.32 C901850031 receive Collision count flag.......................................................75-15
75.33 C901850032 receive Collision count low 32bits .............................................75-15
75.34 C901850033 receive Collision count high 32bits ............................................75-15
75.35 C901850034 receive 64 bytes packets flag ...................................................75-16
75.36 C901850035 receive 64 bytes packets low 32bits ..........................................75-16
75.37 C901850036 receive 64 bytes packets high 32bits.........................................75-16
75.38 C901850037 receive 65 to 127 bytes packets flag .........................................75-17
75.39 C901850038 receive 65 to 127 bytes packets low 32bits................................75-17
75.40 C901850039 receive 65 to 127 bytes packets high 32bits ..............................75-18
75.41 C901850040 receive 128 to 255 bytes packets flag .......................................75-18
75.42 C901850041 receive 128 to 255 bytes packets low 32bits ..............................75-18
75.43 C901850042 receive 128 to 255 bytes packets high 32bits.............................75-19
75.44 C901850043 receive 256 to 511 bytes packets flag........................................75-19
75.45 C901850044 receive 256 to 511 bytes packets low 32bits ..............................75-20
75.46 C901850045 receive 256 to 511 bytes packets high 32bits .............................75-20
75.47 C901850046 receive 512 to 1023 bytes packets flag......................................75-20
75.48 C901850047 receive 512 to 1023 bytes packets low 32bits ............................75-21
75.49 C901850048 receive 512 to 1023 bytes packets high 32bits...........................75-21
75.50 C901850049 receive 1024 to 1518 bytes packets flag....................................75-22
75.51 C901850050 receive 1024 to 1518 bytes packets low 32bits ..........................75-22
75.52 C901850051 receive 1024 to 1518 bytes packets high 32bits .........................75-22
75.53 C901850052 send discard packets flag.........................................................75-23
75.54 C901850053 send discard packets low 32bits ...............................................75-23
75.55 C901850054 send discard packets high 32bits ..............................................75-24
75.56 C901850055 send packet bytes flag .............................................................75-24
75.57 C901850056 send packet bytes low 32bits....................................................75-24
75.58 C901850057 send packets bytes high 32bits.................................................75-25
75.59 C901850058 send packets flag ....................................................................75-25
75.60 C901850059 send packets low 32bits ...........................................................75-25
75.61 C901850060 send packets high 32bits..........................................................75-26
75.62 C901850061 send broadcast packets flag .....................................................75-26
75.63 C901850062 send broadcast packets low 32bits ...........................................75-26
75.64 C901850063 send broadcast packets high 32bits ..........................................75-27
75.65 C901850064 send multicast packets flag ......................................................75-27
CXIV
75.66 C901850065 send multicast packets low 32bits .............................................75-27
75.67 C901850066 send multicast packets high 32bits............................................75-28
75.68 C901850067 send CRC or Align error packets flag ........................................75-28
75.69 C901850068 send CRC or Align error packets low 32bits...............................75-28
75.70 C901850069 send CRC or Align error packets high 32bits .............................75-29
75.71 C901850070 send small than 64 bytes packets flag.......................................75-29
75.72 C901850071 send small than 64 bytes packets low 32bits .............................75-30
75.73 C901850072 send small than 64 bytes packets high 32bits ............................75-30
75.74 C901850073 send large than 1518 bytes packets flag ...................................75-30
75.75 C901850074 send large than 1518 bytes packets low 32bits ..........................75-31
75.76 C901850075 send large than 1518 bytes packets high 32bits.........................75-31
75.77 C901850076 The flag of sent fragment packets .............................................75-32
75.78 C901850077 Number of sent fragment packets (low 32 bit) ............................75-32
75.79 C901850078 Number of sent fragment packets (high 32 bit)...........................75-32
75.80 C901850079 send Jabber packets flag .........................................................75-33
75.81 C901850080 send Jabber packets low 32bits ................................................75-33
75.82 C901850081 send Jabber packets high 32bits...............................................75-33
75.83 C901850082 send Collision count flag ..........................................................75-34
75.84 C901850083 send Collision count low 32bits.................................................75-34
75.85 C901850084 send Collision count high 32bits................................................75-35
75.86 C901850085 send 64 bytes packets flag .......................................................75-35
75.87 C901850086 send 64 bytes packets low 32bits .............................................75-35
75.88 C901850087 send 64 bytes packets high 32bits ............................................75-36
75.89 C901850088 send 65 to 127 bytes packets flag.............................................75-36
75.90 C901850089 send 65 to 127 bytes packets low 32bits ...................................75-36
75.91 C901850090 send 65 to 127 bytes packets high 32bits ..................................75-37
75.92 C901850091 send 128 to 255 bytes packets flag ...........................................75-37
75.93 C901850092 send 128 to 255 bytes packets low 32bits .................................75-38
75.94 C901850093 send 128 to 255 bytes packets high 32bits ................................75-38
75.95 C901850094 send 256 to 511 bytes packets flag ...........................................75-38
75.96 C901850095 send 256 to 511 bytes packets low 32bits..................................75-39
75.97 C901850096 send 256 to 511 bytes packets high 32bits ................................75-39
75.98 C901850097 send 512 to 1023 bytes packets flag .........................................75-39
75.99 C901850098 send 512 to 1023 bytes packets low 32bits................................75-40
75.100 C901850099 send 512 to 1023 bytes packets high 32bits ............................75-40
75.101 C901850100 send 1024 to 1518 bytes packets flag .....................................75-41
75.102 C901850101 send 1024 to 1518 bytes packets low 32bits ............................75-41
CXV
75.103 C901850102 send 1024 to 1518 bytes packets high 32bits...........................75-41
Chapter 76 PS Handover Cause Measurement...................................... 76-1

76.1 Overview ....................................................................................................... 76-1
76.2 C901880001 Number of handover attempts due to uplink received strength ....... 76-1
76.3 C901880002 Number of handover attempts due to downlink received
strength ......................................................................................................... 76-2
76.4 C901880003 Number of handover attempts due to uplink quality....................... 76-3
76.5 C901880004 Number of handover attempts due to downlink quality................... 76-4
76.6 C901880005 Number of handover attempts due to uplink interference............... 76-4
76.7 C901880006 Number of handover attempts due to downlink interference........... 76-5
76.8 C901880007 Number of handover attempts due to PBGT ................................. 76-6
76.9 C901880008 Number of handover attempts due to large TA.............................. 76-6
76.10 C901880009 Number of handover attempts due to uplink break up quickly ...... 76-7
76.11 C901880010 Number of handover attempts due to macro-micro switch............ 76-8
76.12 C901880011 Number of handover attempts due to high traffic ......................... 76-9
76.13 C901880012 Number of handover attempts due to a good standard level in
FDD adjacent cell ........................................................................................... 76-9
76.14 C901880013 Number of handover attempts due to a good standard level in
TDD adjacent cell ..........................................................................................76-10
76.15 C901880014 Number of handover attempts due to PCCN.............................. 76-11
Chapter 77 PS General Handover Measurement ................................... 77-1

77.1 Overview ....................................................................................................... 77-2
77.2 C901890001 Number of synchronous handover executions .............................. 77-2
77.3 C901890002 Number of successful synchronous handovers ............................. 77-3
77.4 C901890003 Number of pre-synchronous handover executions ........................ 77-4
77.5 C901890004 Number of successful pre-synchronous handovers ....................... 77-5
77.6 C901890005 Number of asynchronous handover executions ............................ 77-6
77.7 C901890006 Number of successful asynchronous handovers ........................... 77-7
77.8 C901890007 Number of normal handover executions ....................................... 77-8
77.9 C901890008 Number of successful normal handovers...................................... 77-9
77.10 C901890009 Number of optimised handover executions ................................77-10
77.11 C901890010 Number of successful optimised handovers ............................... 77-11
77.12 C901890011 Number of Intra-BSC inter-cell handover out attempts ................77-12
77.13 C901890012 Number of Intra-BSC inter-cell handover out executions.............77-12
77.14 C901890013 Number of successful Intra-BSC inter-cell handover out .............77-13
77.15 C901890014 Number of Inter-BSC handover out attempts .............................77-14
77.16 C901890015 Number of Inter-BSC handover out executions ..........................77-15
CXVI
77.17 C901890016 Number of successful Inter-BSC handover out ..........................77-16
77.18 C901890017 Number of handover in attempts...............................................77-17
77.19 C901890018 Number of handover in executions............................................77-17
77.20 C901890019 Number of successful handover in ............................................77-18
77.21 C901890020 Number of Intra-cell handover attempts.....................................77-19
77.22 C901890021 Number of Intra-Cell handover executions.................................77-19
77.23 C901890022 Number of successful Intra-cell handovers ................................77-20
77.24 C901890023 Number of invalid Intra-cell handovers ......................................77-20
77.25 C901890024 Number of 2G to FDD handover attempts .................................77-21
77.26 C901890025 Number of 2G to FDD handover executions ..............................77-21
77.27 C901890026 Number of successful 2G to FDD handovers .............................77-22
77.28 C901890027 Number of 2G to TDD handover attempts .................................77-23
77.29 C901890028 Number of 2G to TDD handover executions ..............................77-24
77.30 C901890029 Number of successful 2G to TDD handovers .............................77-24
77.31 C901890030 Number of 3G to 2G handover attempts ....................................77-25
77.32 C901890031 Number of 3G to 2G handover executions.................................77-26
77.33 C901890032 Number of successful 3G to 2G handovers ...............................77-27
77.34 C901890033 Number of T12 expiry ..............................................................77-27
77.35 C901890034 Number of PCCF received .......................................................77-28
received with cause Create PFC Failure..........................................................77-29
received with cause PS Handover Target not allowed ......................................77-29
received with cause PS Handover not Supported in Target BSS or Target
System .........................................................................................................77-30
received with cause other reasons ..................................................................77-31
77.40 C901890039 Number of failure in optimised handover due to failure alloc
resource .......................................................................................................77-32
77.41 C901890040 Number of failure in optimised handover due to PS handover
not supported in target cell .............................................................................77-33
Chapter 78 IURG Measurement............................................................... 78-1

78.1 Overview ....................................................................................................... 78-1
78.2 C901900001 Number of relocation requests (on Iur-g) ...................................... 78-1
78.3 C901900002 Number of relocation executions (on Iur-g)................................... 78-2
78.4 C901900003 Number of relocation successes (on Iur-g) ................................... 78-4
78.5 C901900004 Number of relocation failures due to no valid radio resource (on
Iur-g) ............................................................................................................. 78-5
CXVII
78.6 C901900005 Number of relocation failures due to no valid terrestrial circuit
resource (on Iur-g) .......................................................................................... 78-6
78.7 C901900006 Number of relocation failures due to loss of UE handover
complete message (on Iur-g) ........................................................................... 78-7
78.8 C901900007 Number of relocation failures due to MS returning to original
channel (on Iur-g) ........................................................................................... 78-8
78.9 C901900008 Number of relocation failures due to other causes (on Iur-g).......... 78-9
Chapter 79 RTCP Measurement .............................................................. 79-1

79.1 Overview ....................................................................................................... 79-1
79.2 C901910001 local jitter (CS) ........................................................................... 79-1
79.3 C901910002 distant jitter (CS) ........................................................................ 79-2
79.4 C901910003 average one-way delay (CS) ....................................................... 79-3
79.5 C901910004 maximal one-way delay (CS)....................................................... 79-5
79.6 C901910005 local cumulative fraction lost (CS)................................................ 79-6
79.7 C901910006 distant cumulative fraction lost (CS)............................................. 79-7
79.8 C901910007 local jitter (PS)............................................................................ 79-9
79.9 C901910008 distant jitter (PS)........................................................................79-10
79.10 C901910009 average one-way delay (PS) .................................................... 79-11
79.11 C901910010 maximal one-way delay (PS) ....................................................79-13
79.12 C901910011 local cumulative fraction lost (PS) .............................................79-14
79.13 C901910012 distant cumulative fraction lost (PS) ..........................................79-15
Chapter 80 DSP Measurement ................................................................ 80-1

80.1 Overview ....................................................................................................... 80-1
80.2 C901920001 the times of loss of TRAU frame synchronization in BIPB .............. 80-1
Chapter 81 Access Control Measurement ............................................. 81-1

81.1 Overview ....................................................................................................... 81-1
81.2 C901930001 Number of CS Call Denied for Lack of IPAbis BandWidth
UpLink ........................................................................................................... 81-1
81.3 C901930002 Number of CS Call Denied for Lack of IPAbis BandWidth
DownLink....................................................................................................... 81-2
81.4 C901930003 Number of PS Call Denied for Lack of IPAbis BandWidth
UpLink ........................................................................................................... 81-3
81.5 C901930004 Number of PS Call Denied for Lack of IPAbis BandWidth
DownLink....................................................................................................... 81-3
Chapter 82 PS Adjacent Cell Handover Measurement.......................... 82-1

82.1 Overview ....................................................................................................... 82-2
82.2 C901950001 Number of handover attempts on the adjacent cell........................ 82-2
CXVIII
82.3 C901950002 Number of successful handovers from selected cell to the
adjacent cell ................................................................................................... 82-3
82.4 C901950003 Number of handover attempts from adjacent cell to the selected
cell ................................................................................................................ 82-4
82.5 C901950004 Number of successful handovers from adjacent cell to the
selected cell ................................................................................................... 82-5
cell due to better uplink quality......................................................................... 82-6
cell due to better downlink quality .................................................................... 82-7
adjacent cell due to better uplink quality ........................................................... 82-9
adjacent cell due to better downlink quality......................................................82-10
cell due to better uplink strength ..................................................................... 82-11
cell due to better downlink strength .................................................................82-12
adjacent cell due to better uplink strength........................................................82-13
adjacent cell due to better downlink strength ...................................................82-14
cell due to PBGT ...........................................................................................82-16
adjacent cell due to PBGT..............................................................................82-17
cell due to large TA ........................................................................................82-18
adjacent cell due to large TA ..........................................................................82-19
cell due to high traffic .....................................................................................82-20
adjacent cell due to high traffic .......................................................................82-21
Appendix A Corresponding Relationship between Basic

Measurement Counters and General Measurement Counters ......... A-1
Glossary .......................................................................................................... I
CXIX
CXX
About This Manual
Purpose
This manual explain the definition, description, measurement point of each performance
counter in ZXG10 iBSC Subsystem.
Intended Audience
l System engineer
l Test engineer
l Planning engineer
What Is in This Manual

This manual contains the following chapters.
Chapter Description
Chapter 1, PS Basic Introduces the detailed information about counters related to PS

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

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

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

Management Information configuration management information basic measurement.
Basic Measurement
Chapter 6, Downlink Data Introduces the detailed information about counters related to downlink
TBF Measurement data TBF measurement.
Chapter 7, Uplink Data TBF Introduces the detailed information about counters related to uplink
Measurement data TBF measurement.
Chapter 8, Data Flow Introduces the detailed information about counters related to data
Measurement flow.
Chapter 9, Uplink-Downlink Introduces the detailed information about counters related to

RLC Statistic Measurement uplink/downlink RLC statistic measurement.
Chapter 10, PS Resource Introduces the detailed information about counters related to PS
Used Statistic Measurement resource used statistic measurement.
Chapter 11, RMM Introduces the detailed information about counters related to RMM
Assignment Measurement assignment measurement.
I
Chapter Description
Chapter 12, Handover Cause Introduces the detailed information about counters related to
Measurement handover cause measurement.
Chapter 13, RMM Call Drop Introduces the detailed information about counters related to RMM
Measurement call drop measurement
Chapter 14, Radio Resource Introduces the detailed information about counters related to radio
Availability Measurement resource availability measurement
Chapter 15, General Introduces the detailed information about counters related to general
Handover Measurement handover measurement.
Chapter 16, Adjacent Cell Introduces the detailed information about counters related to adjacent
Handover Measurement cell handover measurement.
Chapter 17, Radio Access Introduces the detailed information about counters related to radio
Measurement access measurement.
Chapter 18, Radio Introduces the detailed information about counters related to radio
Measurement measurement.
Chapter 19, Sub Cell Introduces the detailed information about counters related to sub
Statistics cell statistics.
Chapter 20, MS TA Introduces the detailed information about counters related to MS TA

Chapter 21, SAPI3 Introduces the detailed information about counters related to SAPI3
Chapter 22, Uplink and Introduces the detailed information about counters related to uplink
Downlink PACCH Statistics and downlink PACCH statistics.
Chapter 23, Downlink GPRS Introduces the detailed information about counters related to downlink
data TBF Statistics GPRS data TBF statistic.
Chapter 24, Downlink Introduces the detailed information about counters related to downlink
EGPRS data TBF Statistics EGPRS data TBF statistic.
Chapter 25, Uplink GPRS Introduces the detailed information about counters related to uplink
data TBF Statistics GPRS data TBF statistics.
Chapter 26, Uplink EGPRS Introduces the detailed information about counters related to uplink
Data TBF Statistics EGPRS data TBF statistics.
Chapter 27, BSSGP Flow Introduces the detailed information about counters related to BSSGP
Statistics flow statistic.
Chapter 28, Gb Interface Introduces the detailed information about counters related to Gb
Message Statistics interface message statistics
Chapter 29, TRX Introduces the detailed information about counters related to TRX
II
Chapter Description
Chapter 30, Timeslot Introduces the detailed information about counters related to timeslot
Chapter 31, SDCCH Introduces the detailed information about counters related to SDCCH
Chapter 32, TCH/F Introduces the detailed information about counters related to TCH/F
Chapter 33, TCH/H Introduces the detailed information about counters related to TCH/H
Chapter 34, Abis Interface Introduces the detailed information about counters related to Abis
Message Counter interface message counter measurement.
Measurement
Chapter 35, Gb Message Introduces the detailed information about counters related to Gb
Statistics (BVC Cell) interface message statistics (BVC cell).
Chapter 36, NSVC Statistic Introduces the detailed information about counters related to NSVC
Measurement statistic measurement.
Chapter 37, NSE Statistic Introduces the detailed information about counters related to NSE
Measurement statistic measurement.
Chapter 38, BTS TRX Introduces the detailed information about counters related to BTS
Measurement TRX measurement.
Chapter 39, NSVC on IPGB Introduces the detailed information about counters related to NSVC
HOST Measurement on IPGB HOST measurement.
Chapter 40, GB Message on Introduces the detailed information about counters related to GB
IPGB HOST Measurement message on IPGB HOST measurement.
Chapter 41, NSE on IPGB Introduces the detailed information about counters related to NSE
HOST Measurement on IPGB HOST measurement.
Chapter 42, BSSMAP Introduces the detailed information about counters related to
Message Measurement BSSMAP message measurement.
Chapter 43, A-Interface Introduces the detailed information about counters related to
Message Measurement A-Interface message measurement.
Chapter 44, Terrestrial Introduces the detailed information about counters related to
Resource Availability terrestrial resource availability measurement.
Measurement
Chapter 45, Ater Message Introduces the detailed information about counters related to Ater
Measurement message measurement.
Chapter 46, MTP2 Signal Introduces the detailed information about counters related to MTP2
Link Measurement signal link measurement.
III
Chapter Description
Chapter 47, CPU/MEM Introduces the detailed information about counters related to
Measurement CPU/MEM measurement.
Chapter 48, SCTP AS Introduces the detailed information about counters related to SCTP
Measurement AS measurement.
Chapter 49, IP Port Introduces the detailed information about counters related to IP port
Performance Statistics performance statistics.
Chapter 50, GTRUNK Introduces the detailed information about counters related to
Resource Statistics GTRUNK resource statistics.
Chapter 51, Other Process Introduces the detailed information about counters related to other
Statistics process statistics.
Chapter 52, FR Carried Links Introduces the detailed information about counters related to FR
Statistics carried links statistics.
Chapter 53, OMP PS Service Introduces the detailed information about counters related to OMP
Statistics PS service statistics.
Chapter 54, SNS on OMP Introduces the detailed information about counters related to SNS
Statistics on OMP statistics.
Chapter 55, IPGB Introduces the detailed information about counters related to IPGB
StrongARM NSVC Statistics StrongARM NSVC statistics.
Chapter 56, IPGB Introduces the detailed information about counters related to IPGB
StrongARM Gb Statistics StrongARM Gb statistics.
Chapter 57, Queue Introduces the detailed information about counters related to queue
Chapter 58, Handover Introduces the detailed information about counters related to
Synchronization Mode handover synchronization mode measurement.
Measurement
Chapter 59, Paging Message Introduces the detailed information about counters related to paging
Measurement message measurement.
Chapter 60, Reserved Introduces the detailed information about counters related to reserved
Channel Measurement channel measurement.
Chapter 61, SCCP Introduces the detailed information about counters related to SCCP
Connection Measurement connection measurement.
Chapter 62, DTM Cell Introduces the detailed information about counters related to DTM
Measurement cell measurement.
Chapter 63, LAPD Introduces the detailed information about counters related to LAPD
Chapter 64, LCS Introduces the detailed information about counters related to LCS
IV
Chapter Description
Chapter 65, LB Global Introduces the detailed information about counters related to LB
Message Measurement global message measurement.
Chapter 66 Ater Interface Introduces the detailed information about counters related to Ater
Relays Measurement interface relays measurement.
Chapter 67, Ater Interface Introduces the detailed information about counters related to Ater
SCCP Connections interface SCCP connections measurement.
Measurement
Chapter 68, Measurement Introduces the detailed information about counters related to
Report Serving Cell measurement report serving cell measurement.
Measurement
Chapter 69, Measurement Introduces the detailed information about counters related to
Report Adjacent Cell measurement report adjacent cell measurement.
Measurement
Chapter 70, TRX Paging Introduces the detailed information about counters related to TRX
Measurement paging measurement.
Chapter 71, TRX Introduces the detailed information about counters related to TRX
Temperature Power temperature power measurement.
Measurement
Chapter 72, Terminal Ability Introduces the detailed information about counters related to terminal
Statistics ability statistics.
Chapter 73, MAC Port Flow Introduces the detailed information about counters related to MAC
Statistics port flow statistics.
Chapter 74, AMR Rate Introduces the detailed information about counters related to AMR
Statistics rate statistics.
Chapter 75, UMAC Introduces the detailed information about counters related to UMAC
Chapter 76, PS Handover Introduces the detailed information about counters related to PS
Cause Measurement handover cause measurement.
Chapter 77, PS General Introduces the detailed information about counters related to PS
Handover Measurement general handover measurement.
Chapter 78, IURG Introduces the detailed information about counters related to IURG
Chapter 79, RTCP Introduces the detailed information about counters related to RTCP
Chapter 80, DSP Introduces the detailed information about counters related to DSP
V
Chapter Description
Chapter 81, Access Control Introduces the detailed information about counters related to access
Measurement control measurement.
Chapter 82, PS Adjacent Cell Introduces the detailed information about counters related to PS
Handover Measurement adjacent cell handover measurement.
VI
Chapter 1
PS Basic Measurement (BSC)
Table of Contents
Overview ....................................................................................................................1-1
C900030001 Number of bytes received from data link................................................1-1
C900030002 Number of bytes sent to data link .........................................................1-1
1.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.
1.2 C900030001 Number of bytes received from data

link
Description
This counter counts the total number of bytes received from all BRCHs on FR sub-layer.
Usage
This counter is used to find out the bytes received from BRCH and to observe BSC load
status.
Measurement Point
FR accumulates all the bytes received from Gb interface BRCH.
Unit
Byte
1.3 C900030002 Number of bytes sent to data link

Description
This counter counts the total number of bytes sent from all BRCHs on FR sub-layer.
1-1
SJ-20100414142254-015|20101115(R1.2) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference
Usage
This counter is used to find out the bytes sent from BRCH and to observe BSC load status.
Measurement Point
FR accumulates all the bytes sent from Gb interface BRCH.
Unit
Byte
1-2

Chapter 2
PS Basic Measurement (Cell)
Table of Contents
Overview ....................................................................................................................2-7
C900040001 Number of GPRS DL TBF establishment success on PACCH ...............2-7
C900040002 Number of GPRS DL TBF release due to N3105 overflow.....................2-8
C900040003 Number of GPRS DL TBF release due to other reasons........................2-9
C900040004 Number of GPRS DL TBF forcing release by control plane..................2-10
C900040005 Number of GPRS DL TBF release due to instance suspension ...........2-11
C900040006 Number of GPRS DL TBF release due to inner abnormal....................2-12
C900040007 Number of GPRS DL signaling TBF establishment ..............................2-12
C900040008 Number of GPRS DL data TBF establishment .....................................2-13
C900040009 Number of EGPRS DL TBF establishment success on PACCH ...........2-13
C900040010 Number of EGPRS DL TBF release due to N3105 overflow ................2-15
C900040011 Number of EGPRS DL TBF release due to other reasons....................2-16
C900040012 Number of EGPRS DL TBF forcing release by control plane ...............2-16
C900040013 Number of EGPRS DL TBF release due to instance suspension .........2-17
C900040014 Number of EGPRS DL TBF release due to inner abnormal .................2-18
C900040015 Number of EGPRS DL signaling TBF establishment............................2-19
C900040016 Number of EGPRS DL data TBF establishment...................................2-19
C900040017 Average number of GPRS DL TBF simultaneous establishment .........2-19
C900040018 Average number of EGPRS DL TBF simultaneous establishment ......2-20
C900040019 Number of GPRS UL data TBF establishment success on PACCH .....2-20
C900040020 Number of GPRS UL TBF release due to N3101 overflow...................2-21
C900040021 Number of GPRS UL TBF release due to N3103 overflow...................2-22
C900040022 Number of GPRS UL TBF forcing release by control plane..................2-22
C900040023 Number of GPRS UL TBF release due to instance suspension ...........2-23
C900040024 Number of GPRS UL TBF release due to inner abnormal....................2-24
C900040025 Number of GPRS UL signaling TBF establishment ..............................2-24
C900040026 Number of GPRS UL data TBF establishment .....................................2-26
C900040027 Number of EGPRS UL TBF establishment success on PACCH ...........2-27
C900040028 Number of EGPRS UL TBF release due to N3101 overflow ................2-28
C900040029 Number of EGPRS UL TBF release due to N3103 overflow ................2-29
C900040030 Number of EGPRS UL TBF forcing release by control plane ...............2-29
C900040031 Number of EGPRS UL TBF release due to instance suspension .........2-30
C900040032 Number of EGPRS UL TBF release due to inner abnormal .................2-30
C900040033 Number of EGPRS UL signaling TBF establishment............................2-31
C900040034 Number of EGPRS UL data TBF establishment...................................2-31
C900040035 Average number of GPRS UL TBF simultaneous establishment .........2-31
C900040036 Average number of EGPRS UL TBF simultaneous establishment ......2-32
2-1

C900040037 Number of GPRS UL signaling TBF release due to N3101 overflow ....2-32
C900040038 Number of GPRS UL signaling TBF release due to N3103 overflow ....2-33
C900040039 Number of GPRS UL signaling TBF forcing release by control plane...2-33
C900040040 Number of GPRS UL signaling TBF release due to instance
suspension...............................................................................................................2-34
C900040041 Number of GPRS UL signaling TBF release due to inner abnormal .....2-34
C900040042 Number of EGPRS UL signaling TBF release due to N3101 overflow..2-35
C900040043 Number of EGPRS UL signaling TBF release due to N3103 overflow..2-35
C900040044 Number of EGPRS UL signaling TBF forcing release by control plane .2-36
C900040045 Number of EGPRS UL signaling TBF release due to instance
suspension...............................................................................................................2-36
C900040046 Number of EGPRS UL signaling TBF release due to inner abnormal...2-37
C900040047 Number of EGPRS DL LLC frames .....................................................2-37
C900040048 Number of discarded EGPRS DL LLC frames due to buffer overflow...2-38
C900040049 Number of discarded EGPRS DL LLC frames due to life time
expiration .................................................................................................................2-38
C900040050 Number of discarded EGPRS DL LLC frames due to other reasons ...2-39
C900040051 Number of DL signaling LLC frames ....................................................2-40
C900040052 Number of discarded EGPRS DL signaling LLC frames due to buffer
overflow ...................................................................................................................2-40
C900040053 Number of discarded EGPRS DL signaling LLC frames due to life
time expiration..........................................................................................................2-41
C900040054 Number of discarded EGPRS DL signaling LLC frames due to other
reasons ....................................................................................................................2-42
C900040055 Number of data blocks transmitted according to given Abis bandwidth .2-43
C900040056 Bytes of effective upper layer protocol data sent on DL PDCH ...........2-43
C900040057 Bytes of effective upper layer protocol data received on UL PDCH .....2-44
C900040058 Bytes of LLC frame on GPRS UL data TBF ........................................2-45
C900040059 Duration of GPRS UL data TBF...........................................................2-45
C900040060 Bytes of LLC frame on GPRS DL data TBF ........................................2-47
C900040061 Duration of GPRS DL data TBF...........................................................2-48
C900040062 Number of effective data blocks received on GPRS UL TBF................2-49
C900040063 Number of NACK blocks received on GPRS UL TBF ..........................2-50
C900040064 Number of effective data blocks sent on GPRS DL TBF .....................2-51
C900040065 Number of NACK blocks sent on GPRS DL TBF ................................2-52
C900040066 Bytes of LLC frame on EGPRS UL data TBF ......................................2-53
C900040067 Duration of EGPRS UL data TBF ........................................................2-54
C900040068 Bytes of LLC frame on EGPRS DL data TBF ......................................2-55
C900040069 Duration of EGPRS DL data TBF ........................................................2-56
C900040070 Number of effective data blocks received on EGPRS UL TBF .............2-57
C900040071 Number of NACK blocks received on EGPRS UL TBF .......................2-58
C900040072 Number of effective data blocks sent on EGPRS DL TBF ...................2-59
C900040073 Number of NACK blocks sent on EGPRS DL TBF ..............................2-60
C900040074 Number of GPRS DL LLC frames........................................................2-61
C900040075 Number of discarded GPRS DL LLC frames due to buffer overflow .....2-62
2-2

Chapter 2 PS Basic Measurement (Cell)
C900040076 Number of discarded GPRS DL LLC frames due to life time expiration .2-63
C900040077 Number of discarded GPRS DL LLC frames due to other reasons.......2-63
C900040078 Number of DL dummy control blocks on PACCH .................................2-64
C900040079 Number of UL dummy control blocks on PACCH .................................2-65
C900040080 Number of DL RLC blocks on PACCH (excluding dummy block) .........2-65
C900040081 Number of DL RLC pending blocks in CS1 on PDTCH ........................2-66
C900040085 Number of DL RLC NACK blocks in CS1 on PDTCH...........................2-70
C900040089 Number of DL RLC new blocks in CS1 on PDTCH ..............................2-74
C900040093 Number of UL RLC blocks excluding dummy blocks on PACCH ..........2-77
C900040094 Number of UL RLC pending blocks in CS1 on PDTCH ........................2-78
C900040098 Number of UL RLC NACK blocks in CS1 on PDTCH...........................2-82
C900040102 Number of UL RLC new blocks in CS1 on PDTCH ..............................2-86
C900040106 Number of UL data blocks received on PDTCH ...................................2-90
C900040107 Number of DL data blocks sent on PDTCH..........................................2-90
C900040108 Number of GPRS DL TBF establishment requests .............................2-91
C900040109 Number of GPRS DL TBF establishment failure due to database
allocation failure .......................................................................................................2-91
C900040110 Number of GPRS DL TBF resource reallocation requests due to UL
TBF establishment ..................................................................................................2-93
C900040111 Number of GPRS DL TBF resource reallocation failure due to UL TBF
establishment ..........................................................................................................2-93
C900040112 Number of GPRS DL TBF resource reallocation requests due to LLC
transmission .............................................................................................................2-94
C900040113 Number of GPRS DL TBF resource reallocation failure due to LLC
transmission ............................................................................................................2-95
C900040114 Number of EGPRS DL TBF establishment requests ...........................2-96
2-3

C900040115 Number of EGPRS DL TBF establishment failure due to database

allocation failure .......................................................................................................2-96
C900040116 Number of EGPRS DL TBF resource reallocation requests due to UL
C900040117 Number of EGPRS DL TBF resource reallocation failure due to UL
C900040118 Number of EGPRS DL TBF resource reallocation requests due to
LLC transmission .....................................................................................................2-99
C900040119 Number of EGPRS DL TBF resource reallocation failure due to LLC
transmission ..........................................................................................................2-100
C900040120 Number of GPRS UL TBF establishment requests ...........................2-100
C900040121 Number of GPRS UL TBF establishment failure due to database
allocation failure .....................................................................................................2-101
C900040122 Number of GPRS UL TBF resource reallocation requests due to DL
TBF establishment .................................................................................................2-102
C900040123 Number of GPRS UL TBF resource reallocation failure due to DL TBF
establishment .........................................................................................................2-103
C900040124 Number of GPRS UL TBF resource reallocation requests due to LLC
transmission ...........................................................................................................2-104
C900040125 Number of GPRS UL TBF resource reallocation failure due to LLC
transmission ...........................................................................................................2-105
C900040126 Number of GPRS UL TBF resource reallocation requests for resource
request...................................................................................................................2-106
C900040127 Number of GPRS UL TBF resource reallocation failure due to
database allocation failure for resource request......................................................2-106
C900040128 Number of EGPRS UL TBF establishment requests ..........................2-107
C900040129 Number of EGPRS UL TBF establishment failure due to database
allocation failure .....................................................................................................2-108
C900040130 Number of EGPRS UL TBF resource reallocation requests due to DL
C900040131 Number of EGPRS UL TBF resource reallocation failure due to DL
TBF establishment ................................................................................................. 2-110
C900040132 Number of EGPRS UL TBF resource reallocation requests due to
LLC transmission ................................................................................................... 2-110
C900040133 Number of EGPRS UL TBF resource reallocation failure due to LLC
transmission ........................................................................................................... 2-111
C900040134 Number of EGPRS UL TBF resource reallocation requests for
resource request .................................................................................................... 2-112
C900040135 Number of EGPRS UL TBF resource reallocation failure due to
database allocation failure for resource request...................................................... 2-113
C900040136 Average number of available PDCH .................................................. 2-113
C900040137 Number of forcing conversation dynamic from PDCH to TCH by
BSC ....................................................................................................................... 2-114
C900040138 Number of PDCH used by TBF in each cell ....................................... 2-114
C900040139 Maximum number of used PDCH ...................................................... 2-115
2-4

C900040140 Average number of used PDCH ........................................................ 2-115

C900040141 Number of GPRS DL TBF establishment requests before T3192
expiration ............................................................................................................... 2-116
C900040142 Number of GPRS DL TBF establishment using existing DL TBF
resource ................................................................................................................. 2-117
C900040143 Number of GPRS DL TBF establishment requests on PACCH .......... 2-117
C900040144 Number of GPRS DL TBF establishment requests on
CCCH/PCCCH ....................................................................................................... 2-118
C900040145 Number of EGPRS DL TBF establishment requests before T3192
expiration ............................................................................................................... 2-119
C900040146 Number of EGPRS DL TBF establishment using existing DL TBF
resource .................................................................................................................2-120
C900040147 Number of EGPRS DL TBF establishment requests on PACCH ........2-121
C900040148 Number of EGPRS DL TBF establishment requests on
CCCH/PCCCH .......................................................................................................2-122
C900040149 Number of GPRS DL signaling TBF release due to N3105 overflow ..2-123
C900040150 Number of GPRS DL signaling TBF release due to other reasons .....2-124
C900040151 Number of GPRS DL signaling TBF forcing release by control plane .2-124
C900040152 Number of GPRS DL signaling TBF release due to instance
suspension.............................................................................................................2-125
C900040153 Number of GPRS DL signaling TBF release due to inner abnormal ...2-126
C900040154 Number of EGPRS DL signaling TBF release due to N3105 overflow .2-127
C900040155 Number of EGPRS DL signaling TBF release due to other reasons...2-128
C900040156 Number of EGPRS DL signaling TBF forcing release by control
plane ......................................................................................................................2-128
C900040157 Number of EGPRS DL signaling TBF release due to instance
suspension.............................................................................................................2-129
C900040158 Number of EGPRS DL signaling TBF release due to inner abnormal .2-130
C900040159 Number of GPRS UL TBF establishments in release state ................2-131
C900040160 Number of GPRS UL TBF establishment with existing UL resource...2-132
C900040161 Number of GPRS UL TBF establishment requests on PACCH ..........2-132
C900040162 Number of EGPRS UL data TBF establishments on PACCH .............2-133
C900040163 Number of EGPRS UL TBF establishments in release state ..............2-134
C900040164 Number of EGPRS UL TBF establishment with existing UL resource .2-135
C900040165 Number of EGPRS UL TBF establishment requests on PACCH ........2-135
C900040166 Number of EGPRS UL TBF establishment requests on
CCCH/PCCCH .......................................................................................................2-136
C900040167 Number of dynamic PDCH preemption for CS service.......................2-137
C900040168 Number of GPRS UL TBF establishment requests on
CCCH/PCCCH .......................................................................................................2-137
C900040169 Number of GPRS DL TBF establishment requests on PACCH ..........2-138
C900040170 Number of EGPRS DL TBF establishment requests on PACCH ........2-139
C900040171 Number of GPRS UL TBF establishment requests on PACCH ..........2-139
C900040172 Number of DL RLC pending blocks in MCS1 on PDTCH ...................2-140
2-5


C900040181 Number of DL RLC NACK blocks in MCS1 on PDTCH ......................2-149
C900040190 Number of DL RLC new blocks in MCS1 on PDTCH .........................2-158
C900040199 Number of UL RLC pending blocks in MCS1 on PDTCH ...................2-167
C900040208 Number of UL RLC NACK blocks in MCS1 on PDTCH ......................2-176
C900040217 Number of UL RLC new blocks in MCS1 on PDTCH .........................2-185
2-6


2.1 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.
2.2 C900040001 Number of GPRS DL TBF establishment

success on PACCH
Description
This counter counts the number of successful DL GPRS TBF establishments on the UL/DL
GPRS TBF PACCH.
Measurement Point
When the DL GPRS TBF is established on the UL/DL GPRS TBF PACCH and a message
indicating assignment success is sent, this counter increments. The measurement points
are A as shown in Figure 2-1 and Figure 2-2, and A2 as shown in Figure 2-3.
Figure 2-1 Measurement Point of Number of Requests for Establishing GPRS Downlink
Data TBF Before T3192 Overtime
2-7

Figure 2-2 Measurement Point of Number of Established GPRS Downlink Data TBF
Using Existing Resources
Data TBF on Uplink GPRS TBF PACCH
Unit
Times
2.3 C900040002 Number of 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.
2-8

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

Figure 2-5 Measurement Point of Number of GPRS DL TBF Release due to Other
Reasons
Unit
Times
2.5 C900040004 Number of GPRS DL TBF forcing

release by control plane
Description
When the user plane is transmitting the DL TBF, if a release request comes from the control
plane, then the DL TBF will stop and be released abnormally.
Measurement Point
When the user plane receives the release request from the control plane, this counter
increments. The measurement point is A, as shown in Figure 2-6.
Figure 2-6 Measurement Point of Number of GPRS DL TBF Forcing Release by Control
Plane
2-10

Unit
Times

to instance suspension
Description
When the user plane is transmitting the DL TBF, at least one block must be transmitted in
every 5 seconds. After a DL TBF block is transmitted, BSC will start or restart a 5-second
DL block assigning timer. If the timer expires, it is considered that the user plane has an
instance suspension and the DL TBF is released abnormally.
Measurement Point
When the DL block assigning timer expires, this counter increments. The measurement
point is A, as shown in Figure 2-7.
Figure 2-7 Measurement Point of Number of GPRS DL TBF Release due to Instance
Suspension
Unit
Times
2-11


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

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

2.9 C900040008 Number of GPRS DL data TBF

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

establishment success on PACCH
Description
This counter counts the number of successful DL EGPRS TBF establishments on the
UL/DL EGPRS TBF PACCH.
Measurement Point
When the DL EGPRS TBF is established on the UL/DL EGPRS TBF PACCH and
a message indicating assignment success is sent, this counter increments. The
measurement points are A as shown in Figure 2-8 and Figure 2-9, and A2 as shown in
Figure 2-10.
2-13

Data TBF Before T3192 Overtime
Figure 2-9 Measurement Point of Number of Established GPRS Downlink Data TBF
Using Existing Resources
Figure 2-10 Measurement Point of Number of Requests for Establishing GPRS

Downlink Data TBF on Uplink GPRS TBF PACCH
Unit
Times
2-14

2.11 C900040010 Number of 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
Measurement Point
Figure 2-11 Measurement Point of Number of EGPRS DL TBF Release due to N3105
Overflow
Unit
Times
2-15


due to other reasons
Description
When BSC is transmitting the last DL TBF RLC block, set FBI to 1, set RRBP to ask the
MS to respond with a Packet Downlink Ack/Nack message, and at the same time, activate
T3191. If the specified block receives the MS response, then T3191 will stop and the
DL transmission ends normally. If T3191 overflows, then it is considered that the radio
transmission fails and the DL TBF is released abnormally.
Measurement Point
Figure 2-12 Measurement Point of Number of EGPRS DL TBF Release due to Other
Reasons
Unit
Times
2.13 C900040012 Number of 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 released abnormally.
2-16

Measurement Point
Figure 2-13 Measurement Point of Number of EGPRS DL TBF Forcing Release by

Control Plane
Unit
Times

due to instance suspension
Description
When the user plane is transmitting the DL TBF, at least one block must be transmitted in
every 5 seconds. After a DL TBF block is transmitted, BSC will start or restart a 5-second
DL block assigning timer. If the timer expires, it is considered that the user plane has an
instance suspension and the DL TBF is released abnormally.
Measurement Point
point is A1, as shown in Figure 2-14.
2-17

Figure 2-14 Measurement Point of Number of EGPRS DL TBF Release due to Instance
Suspension
Unit
Times

due 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 released abnormally.
Measurement Point
During the DL TBF transmission, if the message fails to be sent at the radio interface,
the RLC instance fails to be created, or the resource reassignment fails, this counter
increments.
Unit
Times
2-18

2.16 C900040015 Number of EGPRS DL signaling TBF

establishment
Description
and data TBF.
This counter counts the number of establishments of EGPRS DL TBF for UL signaling
transmission. The UL signaling involves some UL processes such as ATTACH, PDP
activation, and routing area update.
Measurement Point
When the DL TBF is created successfully and the TBF type is signaling TBF, the counter
Unit
Times
2.17 C900040016 Number of EGPRS DL data TBF

establishment
Description
and data TBF.
This counter counts the number of establishments of EGPRS DL TBF for user data
(no-UL-signaling) transmission.
Measurement Point
When the DL TBF is created successfully and the TBF type is data TBF, the counter
Unit
Times
2.18 C900040017 Average number of GPRS DL TBF

simultaneous establishment
Description
This counter counts the average number of DL GPRS TBF establishments in a cell.
2-19

Measurement Point
The counter acquires the measurement value regularly. The number of GPRS TBFs
existing in the cell is considered the average number.
Unit
Times
2.19 C900040018 Average number of EGPRS DL TBF

Description
This counter counts the average number of DL EGPRS TBF establishments in a cell.
Measurement Point
The counter acquires the measurement value regularly. The number of EGPRS TBFs
existing in the cell is considered the average number.
Unit
Times
2.20 C900040019 Number of GPRS UL data TBF

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

Figure 2-15 Measurement Point of Number of GPRS UL Data TBF Establishment

Success on PACCH
Unit
Times
2.21 C900040020 Number of 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 Point
The measurement point is N3101 overflow, as A shown in Figure 2-16.
Figure 2-16 Measurement Point of Number of GPRS UL TBF Release due to N3101
Overflow
Unit
Times
2-21


to N3103 overflow
Description
When BSS receives all UL RLC blocks, it will send MS a Packet Uplink Ack message in
which FAI and RRBP are set. MS will report Packet Control Ack to the corresponding UL
block. If BSS fails to receive it, N3103 increments. When N3103 exceeds the maximum
value, BSS will release UL TBF.
Usage
The counter counts the number of abnormal releases of GPRS UL TBF due to N3103
overflow.
Measurement Point
The measurement point is N3103 overflow, as A shown in Figure 2-17.
Figure 2-17 Measurement Point of Number of GPRS UL TBF Release due to N3103
Overflow
Unit
Times
2.23 C900040022 Number of 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.
2-22

Measurement Point
The measurement point is arrival of the release request, as A shown in Figure 2-18.
Figure 2-18 Measurement Point of Number of GPRS UL TBF Forcing Release by

Control Plane
Unit
Times

to instance suspension
Description
BSS creates an instance for an UL TBF. If the instance is suspended for some reason,
then BSS should release this UL TBF.
Usage
The counter counts the number of abnormal releases of GPRS UL TBF due to suspension
of the instance.
Measurement Point
The measurement point is that UPPB detects suspension of the instance, as A shown in
Figure 2-19.
Figure 2-19 Measurement Point of Number of GPRS UL TBF Release due to Instance
Suspension
Unit
Times
2-23


to inner abnormal
Description
TBF is abnormally released due to UPPB internal error.
Usage
The counter counts the number of abnormal releases of GPRS UL TBF due to internal
error.
Measurement Point
The measurement point is abnormal UPPB suspension, as B shown in Figure 2-20.
Figure 2-20 Measurement Point of Number of GPRS UL TBF Release due to Instance
Suspension
Unit
Times
2.26 C900040025 Number of GPRS UL signaling TBF

establishment
Description
For different purpose, MS may establish two types of TBF: signaling TBF and data TBF.
Usage
The counter counts the number of GPRS UL signaling TBF link establishments.
Measurement Point
The measurement point is that UPPB access type is signaling TBF. For all 1-step
accesses, their type is considered signaling TBF, as A1 shown in Figure 2-21. For the
2-step accesses, the TBF type is detected as SIGNAL_TBF, as A1 shown in Figure 2-22.
2-24

Figure 2-21 UL TBF Flow of 1-Step Access
2-25

Unit
Times

establishment
Description
Usage
The counter counts the number of GPRS UL data TBF link establishments.
2-26

Measurement Point
The measurement point is when UPPB access type is data TBF. For example, the TBF
type is detected as DATA_TBF, as A1 shown in Figure 2-23.
Unit
Times
2.28 C900040027 Number of EGPRS UL TBF

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
2-27

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 establishments on PACCH.
Measurement Point
Figure 2-24 Measurement Point of Number of EGPRS UL TBF Establishment Success

on PACCH
Unit
Times
2.29 C900040028 Number of EGPRS UL TBF release

Description
TBF.
Usage
The counter counts the number of abnormal releases of EGPRS UL TBF due to N3101
overflow.
Measurement Point
The measurement point is when N3101 overflow.
Unit
Times
2-28


Description
Usage
The counter counts the number of abnormal releases of EGPRS UL TBF due to N3103
overflow.
Measurement Point
The measurement point is when N3103 overflow.
Unit
Times
2.31 C900040030 Number of EGPRS UL TBF forcing

Description
Usage
The counter counts the number of forced releases of EGPRS UL TBF due to release
request from the control plane.
Measurement Point
The measurement point is arrival of the release request.
Unit
Times
2-29


due to instance suspension
Description
Usage
The counter counts the number of abnormal releases of EGPRS UL TBF due to suspension
of the instance.
Measurement Point
The measurement point is that UPPB detects suspension of the instance.
Unit
Times

due to inner abnormal
Description
Usage
The counter counts the number of abnormal releases of EGPRS UL TBF due to internal
error.
Measurement Point
The measurement point is abnormal UPPB suspension.
Unit
Times
2-30

2.34 C900040033 Number of EGPRS UL signaling TBF

establishment
Description
Usage
The counter counts the number of EGPRS UL signaling TBF link establishments.
Measurement Point
The measurement point is that UPPB access type is signaling TBF.
Unit
Times
2.35 C900040034 Number of EGPRS UL data TBF

establishment
Description
Usage
The counter counts the number of EGPRS UL data TBF link establishments.
Measurement Point
The measurement point is that UPPB access type is data TBF.
Unit
Times
2.36 C900040035 Average number of GPRS UL TBF

Description
There may be more than one TBF in the system during the sampling period. Average
number of uplink GPRS TBF establishing simultaneously = Number of UL GPRS TBFs
established simultaneously in the sampling period / Times of sampling
2-31

Usage
This counter counts the average number of UL GPRS TBF establishing simultaneously.
Measurement Point
When UPPB receives the message informing UL GPRS TBF establishment, the number
of TBFs is refreshed and the times of sampling accumulates.
Unit
Times
2.37 C900040036 Average number of EGPRS UL TBF

Description
There may be more than one TBF in the system during the sampling period. Average
number of uplink EGPRS TBF establishing simultaneously = Number of UL EGPRS TBFs
established simultaneously in the sampling period / Times of sampling
Usage
This counter counts the average number of UL EGPRS TBF establishing simultaneously.
Measurement Point
When UPPB receives the message informing UL EGPRS TBF establishment, the number
of TBFs is refreshed and the times of sampling accumulates.
Unit
Times

release due to N3101 overflow
Description
TBF.
2-32

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

Description
Usage
N3103 overflow.
Measurement Point
Unit
Times

forcing release by control plane
Description
Usage
The counter counts the number of forced releases of GPRS signaling UL TBF due to
release request from the control plane.
2-33

Measurement Point
Unit
Times

release due to instance suspension
Description
Usage
suspension of the instance.
Measurement Point
Unit
Times

release due to inner abnormal
Description
Usage
internal error.
Measurement Point
Unit
Times
2-34


Description
TBF.
Usage
The counter counts the number of abnormal releases of EGPRS signaling UL TBF due to
N3101 overflow.
Measurement Point
Unit
Times

Description
Usage
N3103 overflow.
Measurement Point
Unit
Times
2-35


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

Description
Usage
suspension of the instance.
Measurement Point
Unit
Times
2-36


Description
Usage
internal error.
Measurement Point
Unit
Times
2.48 C900040047 Number of 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.
Measurement Point
Figure 2-25 Measurement Point of Number of EGPRS DL LLC Frames
2-37

Unit
Times
2.49 C900040048 Number of discarded EGPRS DL LLC

frames due to buffer overflow
Description
The DL GIPB sends DL UnitData to UPPB through IP packets. If UPPB fails to acquire
buffer, then it will send the LLC Discard message to SGSN.
Usage
The counter counts the number of discarded EGPRS DL LLC frames due to buffer overflow.
Measurement Point
Figure 2-26 Measurement Point of Number of Discarded EGPRS DL LLC Frames due
to Buffer Overflow
Unit
Times

frames due to life time expiration
Description
The DL GIPB sends DL UnitData to UPPB through IP packets. If 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.
2-38

Measurement Point
to Life Time Expiration
Unit
Times

frames due to other reasons
Description
for reasons other than the above two in C900040048 and C900040049, then it will send
the LLC Discard message to SGSN.
Usage
The counter counts the number of discarded EGPRS DL LLC frames due to other reasons
than the above two in C900040048 and C900040049.
Measurement Point
to Other Reasons
2-39

Unit
Times
2.52 C900040051 Number of DL signaling LLC frames

Description
UnitData identifies whether data or signaling 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.
Measurement Point
Figure 2-29 Measurement Point of Number of DL Signaling LLC Frames
Unit
Times
2.53 C900040052 Number of discarded EGPRS DL

signaling LLC frames due to buffer overflow
Description
2-40

Usage
The counter counts the number of discarded EGPRS DL signaling LLC frames due to
buffer overflow.
Measurement Point
Figure 2-30 Measurement Point of Number of Discarded EGPRS DL Signaling LLC

Frames due to Buffer Overflow
Unit
Times

signaling LLC frames due to life time expiration
Description
Usage
The counter counts the number of discarded EGPRS DL signaling LLC frames due to life
time expiration.
Measurement Point
2-41


Frames due to Life Time Expiration
Unit
Times

signaling LLC frames due to other reasons
Description
Usage
The counter counts the number of discarded EGPRS DL signaling LLC frames due to other
reasons than the above two in C900040052 and C900040053.
Measurement Point

Frames due to Other Reasons
Unit
Times
2-42

2.56 C900040055 Number of data blocks transmitted

according to given Abis bandwidth
Description
Because the bandwidth carrying the Abis-interface (TS) timeslot is limited, PS may need
1 or more Abis TSs for specific RLC coding modes. If the number of Abis TSs bond to the
channel is definite, the RLC coding mode is also definite for the channel.
Usage
The counter counts the number of data blocks transmitted according to given Abis
bandwidth.
Measurement Point
During the DL PCU frame transmission, if the number of Abis TSs required by the coding
mode equals that of Abis TSs bond to the channel, the counter increments.
Unit
Times
2.57 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.
header.
Usage
The counter counts the bytes of effective upper layer protocol data sent on DL PDCH.
Measurement Point
2-43

Figure 2-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
2.58 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.
header.
Usage
The counter counts the bytes of effective upper layer protocol data received on UL PDCH.
Measurement Point
Figure 2-34 Measurement Point of Total Bytes of Effective Upper Layer Protocol Data
Received on UL PDCH
2-44

Unit
Byte
Related Features
ZGB-06-01-005 BSC Supervision
2.59 C900040058 Bytes of LLC frame on GPRS UL data

TBF
Description
by a certain rule.
header.
Usage
The counter counts the bytes carried by GPRS UL data TBF LLC frame.
Measurement Point
Figure 2-35 Measurement Point of Bytes of LLC Frame on GPRS UL Data TBF
Unit
Byte
2.60 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 extended uplink status is subtracted.
2-45

Usage
The counter counts the duration of GPRS UL data TBF.
Measurement Point
The duration lasts from UPPBs reception of UL TBF establishment request to transmission
of Packet Uplink Ack with FAI set. The measurement point is A, as shown in Figure 2-36.
For extended UL TBF, the measurement point is A and B, as shown in Figure 2-37.
Figure 2-36 Measurement Point of Duration of GPRS UL Data TBF
2-46

Figure 2-37 Measurement Point of Duration of GPRS UL Data TBF (Extended UL TBF)
Unit
ms
2.61 C900040060 Bytes of LLC frame on GPRS DL data

TBF
Description
UPPB divides the DL LLC frame into RLC blocks and sends them to MS. Besides. UPPB
sets RRBP by a certain rule. Then MS reports Packet Downlink Ack/EGPRS Packet
Downlink Ack in the specific UL block.
header.
Usage
The counter counts the bytes of LLC frame on GPRS DL data TBF.
Measurement Point
2-47

Figure 2-38 Measurement Point of Bytes of LLC Frame on GPRS DL Data TBF
Unit
Byte
2.62 C900040061 Duration of GPRS DL data TBF

Description
The duration lasts from BSSs reception of the DL TBF establishment request to its
reception of Packet Downlink Ack/EGPRS Packet Downlink Ack (Packet Control Ack in
non-reply mode) with FAI=1 sent from MS, and the duration of downlink delay status is
subtracted.
Usage
The counter counts the duration of GPRS DL data TBF.
Measurement Point
The counter starts counting when UPPB receives DL TBF establishment request until BSS
finishes sending all current data and MS returns acknowledgement response for all. During
the delay, after the new DL data from SGSN is received, data transmission is initiated
again, and the counter restarts counting until the Packet Downlink Ack/EGPRS Packet
Downlink Ack (Packet Control Ack in non-reply mode) with FAI=1 is received from MS.
The measurement point is A and B, as shown in Figure 2-39.
2-48

Figure 2-39 Measurement Point of Duration of GPRS DL Data TBF
Unit
ms
2.63 C900040062 Number of effective data blocks

received on GPRS UL TBF
Description
During the TBF transmission, MS divides the UL LLC frame into RLC blocks and sends
them to BSS. Only when BSS receives all these RLC blocks can it recompose the LLC
frame.
This counter performs statistics for RLC layer, and the statistic result is the number of data
blocks.
Usage
The counter counts the number of effective data blocks received on GPRS UL TBF.
Measurement Point
2-49

Figure 2-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
2.64 C900040063 Number of NACK blocks received on

GPRS UL TBF
Description
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.
blocks.
Usage
The counter counts the number of NACK blocks received on GPRS UL TBF
Measurement Point
Then counter increments when BSS correctly receives a NACK block. The measurement
2-50

Figure 2-41 Measurement Point of Number of NACK Blocks Received on GPRS UL TBF
Unit
Times
Related Features
2.65 C900040064 Number of effective data blocks sent

on GPRS DL TBF
Description
During the TBF transmission, BSS divides the UL LLC frame into RLC blocks and sends
them to MS. Only when MS correctly receives all these RLC blocks can it recompose
the LLC frame. MS informs BSS of the RLC block reception through Packet DownLink
Ack/EGPRS Packet Downlink Ack.
blocks.
Usage
The counter counts the number of effective data blocks sent on GPRS DL TBF
Measurement Point
Then counter increments when Packet DownLink Ack/EGPRS Packet Downlink Ack
indicates that MS have correctly received the RLC block. The measurement point is A1,
as shown in Figure 2-42.
2-51

Figure 2-42 Measurement Point of Number of Effective Data Blocks Sent on GPRS DL
TBF
Unit
Times
Related Features
2.66 C900040065 Number of NACK blocks sent on

GPRS DL TBF
Description
blocks.
Usage
The counter counts the number of NACK blocks sent on GPRS DL TBF.
Measurement Point
Then counter increments when Packet DownLink Ack/EGPRS Packet Downlink Ack
indicates that MS fails to receive the RLC block. The measurement point is A2, as shown
in Figure 2-43.
2-52

Figure 2-43 Measurement Point of Number of NACK Blocks Sent on GPRS DL TBF
Unit
Times
Related Features
2.67 C900040066 Bytes of LLC frame on EGPRS UL

data TBF
Description
by a certain rule.
header.
Usage
The counter counts the bytes of LLC frame on EGPRS UL data TBF.
Measurement Point
2-53

Figure 2-44 Measurement Point of Bytes of LLC Frame on EGPRS UL Data TBF
Unit
Byte
2.68 C900040067 Duration of 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 extended uplink status is subtracted.
Usage
The counter counts the duration of EGPRS UL data TBF.
Measurement Point
The duration lasts from UPPBs reception of UL TBF establishment request to transmission
of Packet Uplink Ack with FAI=1. The measurement point is A, as shown in Figure 2-45.
For extended UL TBF, the measurement point is A and B, as shown in Figure 2-46.
Figure 2-45 Measurement Point of Duration of EGPRS UL Data TBF
2-54

Figure 2-46 Measurement Point of Duration of EGPRS UL Data TBF (Extended UL TBF)
Unit
ms
2.69 C900040068 Bytes of LLC frame on EGPRS DL

data TBF
Description
UPPB divides the DL LLC frame into RLC blocks and sends them to MS. Besides. UPPB
sets RRBP by a certain rule. Then MS reports Packet Downlink Ack/EGPRS Packet
Downlink Ack in the specific UL block.
header.
Usage
The counter counts the bytes of LLC frame on EGPRS DL data TBF.
Measurement Point
2-55

Figure 2-47 Measurement Point of Bytes of LLC Frame on EGPRS DL Data TBF
Unit
Byte
2.70 C900040069 Duration of EGPRS DL data TBF

Description
The duration lasts from BSSs reception of the DL TBF establishment request to its
reception of Packet Downlink Ack/EGPRS Packet Downlink Ack (Packet Control Ack in
non-reply mode) with FAI=1 sent from MS, and the duration of downlink delay status is
subtracted.
Usage
The counter counts the duration of EGPRS DL data TBF.
Measurement Point
The counter starts counting when UPPB receives DL TBF establishment request until BSS
finishes sending all current data and MS returns acknowledgement response for all. During
the delay, after the new DL data from SGSN is received, data transmission is initiated
again, and the counter restarts counting until the Packet Downlink Ack/EGPRS Packet
Downlink Ack (Packet Control Ack in non-reply mode) with FAI=1 is received from MS.
The measurement point is A and B, as shown in Figure 2-48.
2-56

Figure 2-48 Measurement Point of Duration of EGPRS DL Data TBF
Unit
ms
2.71 C900040070 Number of effective data blocks

received on EGPRS UL TBF
Description
them to BSS. Only when BSS receives all these RLC blocks can it recompose the LLC
frame.
blocks.
Usage
The counter counts the number of effective data blocks received on EGPRS UL TBF.
Measurement Point
2-57

Figure 2-49 Measurement Point of Number of Effective Data Blocks Received on

EGPRS UL TBF
Unit
Times
Related Features
2.72 C900040071 Number of NACK blocks received on

EGPRS UL TBF
Description
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.
blocks.
Usage
The counter counts the number of NACK blocks received on EGPRS UL TBF.
Measurement Point
Then counter increments when BSS correctly receives a NACK block. The measurement
2-58

Figure 2-50 Measurement Point of Number of NACK Blocks Received on EGPRS UL TBF
Unit
Times
Related Features
2.73 C900040072 Number of effective data blocks sent

on EGPRS DL TBF
Description
blocks.
Usage
The counter counts the number of effective data blocks sent on EGPRS DL TBF.
Measurement Point
The counter increments when Packet DownLink Ack/EGPRS Packet Downlink Ack
indicates that MS have correctly received the RLC block. The measurement point is A1,
2-59

Figure 2-51 Measurement Point of Number of Effective Data Blocks Sent on EGPRS DL
TBF
Unit
Times
Related Features
2.74 C900040073 Number of NACK blocks sent on

EGPRS DL TBF
Description
blocks.
Usage
The counter counts the number of NACK blocks sent on EGPRS DL TBF.
Measurement Point
The counter increments when Packet DownLink Ack/EGPRS Packet Downlink Ack
indicates that MS fails to receive the RLC block. The measurement point is A2, as shown
in Figure 2-52.
2-60

Figure 2-52 Measurement Point of Number of Nack Blocks Sent on EGPRS DL TBF
Unit
Times
Related Features
2.75 C900040074 Number of GPRS DL LLC frames

Description
establish DL TBF (radio access capacity to carry MS) and according to the CMP request,
Usage
The counter counts the number of GPRS DL LLC frames.
Measurement Point
2-61

Figure 2-53 Measurement Point of Number of GPRS DL LLC Frames
Unit
Times
2.76 C900040075 Number of discarded GPRS DL LLC

frames due to buffer overflow
Description
Usage
The counter counts the number of discarded GPRS DL LLC frames due to buffer overflow.
Measurement Point
Figure 2-54 Measurement Point of Number of Discarded GPRS DL LLC Frames due
to Buffer Overflow
Unit
Times
2-62


frames due to life time expiration
Description
Usage
The counter counts the number of discarded GPRS DL LLC frames due to life time
expiration.
Measurement Point
to Life Time Expiration
Unit
Times

frames due to other reasons
Description
Usage
The counter counts the number of discarded GPRS DL LLC frames due to other reasons
than the above two in C900040075 and C900040076.
2-63

Measurement Point
to Other Reasons
Unit
Times
2.79 C900040078 Number of DL dummy control blocks

on PACCH
Description
If there is no other RLC/MAC block available in the network, BSS will transmit the DUMMY
blocks to MS for UL transmission.
Usage
The counter counts the number of DL dummy control blocks sent by BSC on PACCH in
the packet transmission mode.
Measurement Point
If the DL control block sent from BTS to MS is a DL Dummy control block, the counter
Figure 2-57 Measurement Point of Number of DL Dummy Control Blocks on PACCH
2-64

Unit
Times
2.80 C900040079 Number of UL dummy control blocks

on PACCH
Description
Similar to C900040078, this counter counts the number of UL dummy control blocks sent
by BSC on PACCH in the packet transmission mode.
Measurement Point
If the DL control block sent from BTS to MS is an UL Dummy control block, the counter
Figure 2-58 Measurement Point of Number of UL Dummy Control Blocks on PACCH
Unit
Times
2.81 C900040080 Number of 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.
blocks.
Usage
The counter counts the number of DL RLC blocks expect DUMMY blocks sent by BSC on
PACCH.
2-65

Measurement Point
When BSC sends a DL control block (except DUMMY block) to MS through BTS, the
counter increments. The measurement point is A, as shown in Figure 2-59.
Figure 2-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
2.82 C900040081 Number of DL 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.
blocks.
Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding
method of CS1.
Measurement Point
When BSC sends a pending RLC block whose coding method is CS1 to MS, the counter
2-66

Figure 2-60 Measurement Point of Number of DL RLC Pending Blocks on PDTCH
Unit
Times
Related Features

in CS2 on PDTCH
Description
blocks.
Usage
method of CS2.
Measurement Point
When BSC sends a pending RLC block whose coding method is CS2 to MS via BTS, the
2-67

Unit
Times
Related Features

in CS3 on PDTCH
Description
blocks.
Usage
method of CS3.
Measurement Point
Unit
Times
Related Features
2-68


in CS4 on PDTCH
Description
blocks.
Usage
method of CS4.
Measurement Point
Unit
Times
Related Features
2-69

2.86 C900040085 Number of DL RLC NACK blocks in

CS1 on PDTCH
Description
of DL retransmitted RLC blocks from BSC to MS, with coding method of CS1.
blocks.
Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with
coding method of CS1.
Measurement Point
When BSC sends retransmitted RLC block whose coding method is CS1 to MS via BTS,
the counter increments. The measurement point is A, as shown in Figure 2-64.
Figure 2-64 Measurement Point of Number of DL RLC NACK Blocks on PDTCH
Unit
Times
Related Features
2-70


CS2 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-71


CS3 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-72


CS4 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-73

2.90 C900040089 Number of DL RLC new blocks in

CS1 on PDTCH
Description
of DL first-transmitted RLC blocks from BSC to MS, with coding method of CS1.
blocks.
Usage
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC
on PDTCH, with coding method of CS1.
Measurement Point
When BSC sends first-transmitted RLC block (with coding method of CS1) to MS via BTS,
Figure 2-68 Measurement Point of Number of DL RLC New Blocks on PDTCH
Unit
Times
Related Features
2-74


CS2 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-75


CS3 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-76


CS4 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2.94 C900040093 Number of 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.
2-77

blocks.
Usage
The counter counts the number of uplink RLC blocks expect DUMMY blocks received by
BSC on PACCH.
Measurement Point
When BSC receives an UL control block (except the DUMMY block) from MS, the counter
Figure 2-72 Measurement Point of Number of UL RLC Blocks Excluding Dummy

Blocks on PACCH
Unit
Times
Related Features
2.95 C900040094 Number of UL RLC pending blocks

in CS1 on PDTCH
Description
After receiving UL data block, BSC decides whether it is retransmitted RLC block,
first-transmitted RLC block or pending RLC block. This counter counts the number of
useful UL CS1-coded pending RLC blocks received on PDTCH.
blocks.
Usage
This counter counts the number of useful UL CS1-coded pending RLC blocks received by
BSC on PDTCH.
2-78

Measurement Point
When BSC receives CS1-coded UL pending RLC block, the counter increments. The
measurement point is A, as shown in Figure 2-73.
Figure 2-73 Measurement Point of Number of UL RLC Pending Blocks on PDTCH
Unit
Times
Related Features

in CS2 on PDTCH
Description
blocks.
Usage
BSC on PDTCH.
Measurement Point
2-79

Unit
Times
Related Features

in CS3 on PDTCH
Description
blocks.
Usage
BSC on PDTCH.
Measurement Point
2-80

Unit
Times
Related Features

in CS4 on PDTCH
Description
blocks.
Usage
BSC on PDTCH.
Measurement Point
Unit
Times
Related Features
2-81

2.99 C900040098 Number of UL RLC NACK blocks in

CS1 on PDTCH
Description
useful UL CS1-coded retransmitted RLC blocks received on PDTCH.
blocks.
Usage
This counter counts the number of useful UL CS1-coded retransmitted RLC blocks
received by BSC on PDTCH.
Measurement Point
When BSC receives CS1-coded UL retransmitted RLC block, the counter increments. The
Figure 2-77 Measurement Point of Number of UL RLC NACK Blocks on PDTCH
Unit
Times
Related Features
2-82

2.100 C900040099 Number of UL RLC NACK blocks

in CS2 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-83


in CS3 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-84


in CS4 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-85

2.103 C900040102 Number of UL RLC new blocks in

CS1 on PDTCH
Description
useful UL CS1-coded first-transmitted RLC blocks received on PDTCH.
blocks.
Usage
This counter counts the number of useful UL CS1-coded first-transmitted RLC blocks
Measurement Point
When BSC receives CS1-coded UL first-transmitted RLC block, the counter increments.
Figure 2-81 Measurement Point of Number of UL RLC New Blocks on PDTCH
Unit
Times
Related Features
2-86


CS2 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-87


CS3 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-88


CS4 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-89

2.107 C900040106 Number of 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.
blocks.
Usage
The counter counts the number of data blocks received by UL PDTCH.
Measurement Point
When MS transmits an UL RLC block to BSC through BTS (including the retransmitted RLC
blocks, blocks to be confirmed and the first-transmitted blocks), this counter increments.
Unit
Times
Related Features
2.108 C900040107 Number of DL data blocks sent on

PDTCH
Description
When BSC transmits DL RLC blocks to BTS, this counter counts the number of data blocks
sent from BSC, including the retransmitted RLC blocks, blocks to be confirmed and the
first-transmitted blocks.
blocks.
Usage
The counter counts the number of data blocks sent by DL PDTCH.
Measurement Point
When BSC transmits a DL RLC block to BTS (including the retransmitted RLC blocks,
blocks to be confirmed and the first-transmitted blocks), this counter increments.
2-90

Unit
Times
Related Features
2.109 C900040108 Number of GPRS DL TBF

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

plane, this counter increments.
l When UL GPRS TBF exists and DL GPRS TBF is to be established, if PS control
plane receives the DL assignment message from PS user plane, this counter
increments.
Unit
Times

establishment failure due to database allocation
failure
Description
The counter counts the number of GPRS DL TBF establishment failure due to database
allocation failure.
2-91

Usage
The counter collects information about the frequency of channel allocation failures when
BSC attempts to establish DL GPRS TBFs.
Measurement Point
l When PS control plane receives the DL TBF establishment request from PS user
plane, it will apply to database for resources. If it fails to obtain the resources, this
Figure 2-85 Measurement Point of Allocation Failures after Receiving DL TBF

Establishment Request
l 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 2-86.

Assignment Message
Unit
Times
2-92

2.111 C900040110 Number of GPRS DL TBF resource

reallocation requests due to UL TBF establishment
Description
The counter counts the number of GPRS DL TBF resource reallocation requests due to
UL TBF establishment.
Usage
The counter collects information about the frequency of GPRS DL TBF resource
reallocation requests.
Measurement Point
When MS has already established a DL GPRS TBF, if PS control plane receives an UL
TBF assignment message from PS user plane, this counter increments. The measurement
Figure 2-87 Measurement Point of Number of GPRS DL TBF Resource Reallocation

Requests due to UL TBF Establishment
Unit
Times

reallocation failure due to UL TBF establishment
Description
If MS has already established a DL GPRS TBF and it needs to establish an UL TBF on
PACCH, PS control plane should apply to database for resources. The counter counts
the number of DL resource reallocation failures caused by failed UL TBF establishment
allocation.
2-93

Usage
The counter collects information about the frequency of GPRS DL resource reallocation
failures caused by failed UL TBF establishment allocation.
Measurement Point
When MS has already established a DL GPRS TBF, if PS control plane receives an UL
TBF assignment message from PS user plane, 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 2-88.

Failure due to UL TBF Establishment
Unit
Times

reallocation requests due to LLC transmission
Description
This counter counts the number of resource reallocation requests that PS control plane
receives from PS user plane caused by UL/DL LLC frame changes during the DL GPRS
TBF transmission.
Usage
This counter collects information about the frequency of resource reallocation requests
received by PS control plane during the DL GPRS TBF transmission.
Measurement Point
When PS control plane receives a resource reallocation request from PS user plane, if the
current DL GPRS TBF exists, this counter increments. The measurement point is A, as
2-94


Requests due to LLC Transmission
Unit
Times

reallocation failure due 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 resource allocations during
the DL GPRS TBF transmission after PS control plane receives the resource reallocation
request and applies to database for resources.
Measurement Point
After PS control plane receives a resource reallocation request from PS user plane and
applies to database for resources, if it fails to obtain the resources, this counter increments,
as A shown in Figure 2-90.

Failure due to LLC Transmission
2-95

Unit
Times

Description
The counter counts the number of EGPRS downlink TBF establishment requests received
by control plane. It is the sum of CCCH/PCCCH requests (C901180002) and PACCH
requests (C901180003).
Usage
The counter collects information about the frequency of DL establishment requests
received by the control plane when BSC attempts to establish DL EGPRS TBFs.
Measurement Point
l When PS control plane receives a DL TBF establishment request from PS user
plane, this counter increments.
l When UL EGPRS TBF exists and DL EGPRS TBF is to be established, if PS control
plane receives the DL assignment message from PS user plane, this counter
increments.
Unit
Times

failure
Description
The counter counts the number of channel allocation failures when BSC attempts to
establish DL EGPRS TBFs and RANPS applies to database for resources.
Usage
The counter collects information about the frequency of channel allocation failures
when BSC attempts to establish DL EGPRS TBFs and RANPS applies to database for
resources.
2-96

Measurement Point
l When PS control plane receives the DL TBF establishment request from PS user
plane, it will apply to database for resources. If it fails to obtain the resources, this

Establishment Request
l When UL EGPRS TBF exists and DL EGPRS TBF is to be established, if PS control

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

Assignment Message
Unit
Times
2.117 C900040116 Number of EGPRS DL TBF resource

reallocation requests due to UL TBF establishment
Description
The counter counts the number of EGPRS downlink TBF resource reallocation requests
(concurrent PACCH UL TBF establishment request).
2-97

Usage
The counter collects information about the frequency of EGPRS downlink TBF resource
Measurement Point
When MS has already established a DL EGPRS TBF, if PS control plane receives an UL

Requests due to UL TBF Establishment
Unit
Times

Description
If MS has already established a DL EGPRS TBF and it needs to establish an UL TBF on
the number of DL resource reallocation failures caused by failed UL TBF establishment
allocation.
Usage
The counter collects information about the frequency of EGPRS DL resource reallocation
failures caused by failed UL TBF establishment allocation.
Measurement Point
When MS has already established a DL EGPRS TBF, if PS control plane receives an UL
2-98


Failure due to UL TBF Establishment
Unit
Times

Description
receives from PS user plane caused by UL/DL LLC frame changes during the DL EGPRS
TBF transmission.
Usage
received by PS control plane during the DL EGPRS TBF transmission.
Measurement Point
current DL EGPRS TBF exists, this counter increments, as A shown in Figure 2-95.

Unit
Times
2-99


Description
During the DL EGPRS TBF transmission, because UL/DL LLC frame changes, PS user
Usage
the DL EGPRS TBF transmission after PS control plane receives the resource reallocation
Measurement Point

Unit
Times
2.121 C900040120 Number of GPRS UL TBF

Description
The counter counts the number of all channel requests when MS attempts to establish
GPRS UL TBFs. It is the sum of CCCH requests (C901190002), PCCCH requests
(C901190004) and PACCH requests (C901190006).
2-100

Usage
The counter collects information about the frequency of channel requests when MS
attempts to establish GPRS services.
Measurement Point
This counter increments in the following three cases:
l When BSC receives a CCCH request originated by MS, this counter increments.
l When BSC receives a PCCCH request originated by MS, this counter increments.
l When BSC receives a PACCH request originated by MS and user plane sends a
resource request to control plane, this counter increments.
Unit
Times

failure
Description
The counter counts the number of GPRS UL TBF establishment channel allocation failures.
Usage
the system attempts to establish UL GPRS TBFs.
Measurement Point
l 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
Figure 2-97 Measurement Point of Allocation Failures after Receiving CCCH

Request
2-101

l When PS control plane receives a PCCCH request from MS, it will apply to database
Figure 2-98 Measurement Point of Allocation Failures after Receiving PCCCH

Request
l 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
Figure 2-99 Measurement Point of Allocation Failures (DL GPRS TBF Exists)
Unit
Times
2.123 C900040122 Number of GPRS UL TBF resource

reallocation requests due to 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 TBF resource
2-102

Measurement Point
When MS has already established an UL GPRS TBF, if PS control plane receives a DL
Figure 2-100 Measurement Point of Number of GPRS UL TBF Resource Reallocation

Requests due to DL TBF Establishment
Unit
Times

reallocation failure due to DL TBF establishment
Description
If MS has already established an UL GPRS TBF and it needs to establish a DL TBF on
the number of UL resource reallocation failures caused by failed DL TBF establishment
allocation.
Usage
The counter collects information about the frequency of GPRS UL resource reallocation
failures caused by failed DL TBF establishment allocation.
Measurement Point
When MS has already established an UL GPRS TBF, if PS control plane receives a DL
2-103


Assignment Message
Unit
Times

Description
receives from PS user plane caused by UL/DL LLC frame changes during the UL GPRS
TBF transmission.
Usage
received by PS control plane during the UL GPRS TBF transmission.
Measurement Point
current UL GPRS TBF exists, this counter increments. The measurement point is A, as

2-104

Unit
Times

Description
During the UL GPRS TBF transmission, because UL/DL LLC frame changes, PS user
Usage
the UL GPRS TBF transmission after PS control plane receives the resource reallocation
Measurement Point

Unit
Times
2-105


reallocation requests for resource request
Description
This counter counts the number of resource allocation requests that PS control plane
receives from MS during the UL GPRS TBF transmission.
Usage
This counter collects information about the frequency of resource allocation requests
received by PS control plane during the UL GPRS TBF transmission (including 2-step UL
access and UL TBF transmission).
Measurement Point
When PS control plane receives a resource allocation request from PS user plane, this
counter increments, as A shown in Figure 2-104.

Requests for Resource Request
Unit
Times

reallocation failure due to database allocation
failure 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
2-106

Usage
the UL GPRS TBF transmission (including 2-step UL access and UL TBF transmission)
after PS control plane receives the resource allocation request from MS and applies to
database for resources.
Measurement Point
After PS control plane receives a resource reallocation request from MS and applies to
database for resources, if it fails to obtain the resources, this counter increments, as A
Figure 2-105 Failing to Request for Resource from Database
Unit
Times

Description
The counter counts the number of all channel requests when MS attempts to establish
EDGE UL TBFs. It is the sum of CCCH requests (C901200003), PCCCH requests
(C901200005) and PACCH requests (C901200006).
Usage
The counter collects information about the frequency of channel requests when MS
attempts to establish EDGE services.
Measurement Point
l When BSC receives an EDGE CCCH request originated by MS, this counter
increments.
l When BSC receives an EDGE PCCCH request originated by MS, this counter
increments.
2-107

l 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

failure
Description
The counter counts the number of EGPRS UL TBF establishment channel allocation
failures.
Usage
the system attempts to establish UL EGPRS TBFs.
Measurement Point
l When PS control plane receives an EGPRS channel request on CCCH or an EGPRS
Packet channel request on PCCCH from MS, 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 2-106.
Figure 2-106 Measurement Point of Number of EGPRS Uplink TBF Establishment

Channel Allocation Failures
l 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
2-108

Figure 2-107 Measurement Point of Allocation Failures (DL GPRS TBF Exists)
Unit
Times
2.131 C900040130 Number of EGPRS UL TBF resource

reallocation requests due to DL TBF establishment
Description
The counter counts the number of EGPRS UL TBF resource reallocation requests due to
DL TBF establishment.
Usage
The counter collects information about the frequency of EGPRS UL TBF resource
Measurement Point
When MS has already established an UL EGPRS TBF, if PS control plane receives a DL

Requests due to DL TBF Establishment
Unit
Times
2-109


Description
If MS has already established an UL EGPRS TBF and it needs to establish a DL TBF on
the number of UL resource reallocation failures caused by failed DL TBF establishment
allocation.
Usage
The counter collects information about the frequency of EGPRS UL resource reallocation
failures caused by failed DL TBF establishment allocation.
Measurement Point
When MS has already established an UL EGPRS TBF, if PS control plane receives a DL

Assignment Message
Unit
Times

Description
receives from PS user plane caused by UL/DL LLC frame changes during the UL EGPRS
TBF transmission.
2-110

Usage
received by PS control plane during the UL EGPRS TBF transmission.
Measurement Point
When PS control plane receives a resource reallocation request from PS user plane, this

Unit
Times

Description
During the UL EGPRS TBF transmission, because UL/DL LLC frame changes, PS user
Usage
the UL EGPRS TBF transmission after PS control plane receives the resource reallocation
Measurement Point
2-111


Unit
Times

Description
This counter counts the number of resource allocation requests that PS control plane
receives from MS during the UL EGPRS TBF transmission.
Usage
This counter collects information about the frequency of resource allocation requests
received by PS control plane during the UL EGPRS TBF transmission (including 2-step
UL access and UL TBF transmission).
Measurement Point
When PS control plane receives a resource allocation request from PS user plane, this

Requests for Resource Request
Unit
Times
2-112


reallocation failure due to database allocation
failure for resource request
Description
During the UL EGPRS TBF transmission, after receiving the resource allocation request
from MS, PS control plane applies to database for resources. This counter counts the
Usage
the UL EGPRS TBF transmission (including 2-step UL access and UL TBF transmission)
after PS control plane receives the resource allocation request from MS and applies to
database for resources.
Measurement Point
After PS control plane receives a resource reallocation request from MS and applies to
database for resources, if it fails to obtain the resources, this counter increments, as A
Figure 2-113 Failing to Request for Resource from Database
Unit
Times
2.137 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.
2-113

Measurement Point
The counter's value can be obtained by querying the database when periodic
measurement data is reported.
Unit
Times
Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface
2.138 C900040137 Number of forcing conversation

dynamic from PDCH to TCH by BSC
Description
iBSC supports dynamic radio channel function. The counter records number of times of
reclaiming dynamic PDCH in idle state so as to use them as TCH/F.
Usage
This counter is used to find out the busy level and density of PS service in the serving cell
and use it as reference to decide whether to set static PDCH or not.
Measurement Point
The counter increments when dynamic PDCH is idle and the database starts reclaiming
dynamic PDCH.
Unit
Times
Related Features
ZGO-03-02-002 Enhancement on Channel Allocation
2.139 C900040138 Number of PDCH used by TBF in

each cell
Description
This counter counts the sum of PDCH used by all TBF in the serving cell.
2-114

Usage
This counter is used to find out the condition of multi-timeslot allocation in the serving cell.
Measurement Point
The counter's value can be obtained by querying the database when periodic
measurement data is reported.
Unit
Times
2.140 C900040139 Maximum number of used PDCH

Description
This counter records the maximum number of used PDCH in a cell within the measurement
period. It reflects the occupancy and busy level of PDCH.
Usage
This counter is used to find out the busy level of the cell TCH/F channel. It could be used
as a reference for whether to increase PDCH channel configuration.
Measurement Point
l Request for database
l Release database
l Report periodic measurement data
Unit
Times
2.141 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.
2-115

Measurement Point
l Request for database
l Release database
l Report periodic measurement data
Unit
Times

establishment requests before T3192 expiration
Description
During the running of T3193 of DL GPRS TBF, BSC receives DL LLC frame again, then it
performs DL assignment on PACCH of the DL TBF.
Usage
This counter counts the number of times of establishing new DL TBF.
Measurement Point
After the DL GPRS TBF transmits all LLC frames and the DL RLC block with FBI = 1,
T3193 is started. During T3193 running, when BSC receives new LLC frame and sends
DL assignment, this counter increments.
Figure 2-114 Measurement Point of Number of GPRS DL TBF Establishment Requests

Before T3192 Expiration
2-116

Unit
Times

establishment using existing DL TBF resource
Description
When establishing EGPRS DL TBF under UL transmission status, the user plane needs
not to request control plane for DL resource if having saved DL TBF resource of last time.
It uses the existing resource for DL assignment. This counter records the number of GPRS
DL TBF establishment using existing DL TBF resource.
Measurement Point
During the UL GPRS TBF transmission, when BSC receives the DL LLC frame, it uses the
existing resource to establish DL GPRS TBF. The measurement point is A, as shown in
Figure 2-115.
Figure 2-115 Measurement Point of GPRS DL TBF Establishment Using Existing DL

TBF Resource
Unit
Times

establishment requests on PACCH
Description
Under UL transmission status, it is necessary to establish DL TBF transmission when user
plane receives DL LLC Frame from SGSN. If user plane has not saved DL TBF resource,
then user plane requests control plane for resource.
2-117

This counter counts the number of times of requesting control plane for resource to
establish GPRS DL TBF on PACCH.
Note
Here, user plane refers to the UPPB of iBSC, and control plane refers to the CMP of iBSC.
Measurement Point

on PACCH
Unit
Times

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


on CCCH/PCCCH
Unit
Times

establishment requests before T3192 expiration
Description
During the running of T3193 of DL EGPRS TBF, BSC receives DL LLC frame again, then
it performs DL assignment on PACCH of the DL TBF.
This counter counts the number of times of establishing new DL TBF.
Measurement Point
After the DL EGPRS TBF transmits all LLC frames and the DL RLC block with FBI = 1,
T3193 is started. During T3193 running, when BSC receives new LLC frame and sends
DL assignment, this counter increments.
2-119

Figure 2-118 Measurement Point of Number of EGPRS DL TBF Establishment Requests

Before T3192 Expiration
Unit
Times

establishment using existing DL TBF resource
Description
When establishing EGPRS DL TBF under UL transmission status, the user plane needs
not to request control plane for DL resource if having saved DL TBF resource of last time. It
uses the existing resource for DL assignment. This counter records the number of EGPRS
DL TBF establishment using existing DL TBF resource.
Measurement Point
During the UL EGPRS TBF transmission, when BSC receives the DL LLC frame, it uses
the existing resource to establish DL GPRS TBF.
2-120

Figure 2-119 Measurement Point of Number of EGPRS DL TBF Establishment Using

Existing DL TBF Resource
Unit
Times

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

on PACCH
2-121

Unit
Times

Description
When MS is in packet idle status, after BSC receives DL LLC frame from SGSN, BSC
initiates the process of establishing DL TBF which is assigned on CCCH or PCCCH. BSC
user plane first sends the request for DL establishment to BSC control plane.
Measurement Point
Under MSs packet idle status, when BSC sends the request for DL resource to BSC control
plane after receiving LLC frame from SGSN, the counter increments. The measurement
Figure 2-121 Normal CCCH/PCCCH DL TBF Establishment Process
Unit
Times
2-122


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; if the
N3105 counter reaches its maximum value, it is considered that the radio transmission
fails and the GPRS signaling DL TBF is released abnormally.
Measurement Point
Figure 2-122 Measurement Point of Number of GPRS DL Signaling TBF Release due
to N3105 Overflow
Unit
Times
2-123


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, activate T3191. If the specified block receives the MS response, then T3191
will stop and the DL transmission ends normally. If T3191 overflows, then it is considered
that the radio transmission fails and the GPRS signaling DL TBF is released abnormally.
Measurement Point
Figure 2-123 Measurement Point of Number of GPRS DL TBF Release due to Other
Reasons
Unit
Times

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

Measurement Point
Figure 2-124 Measurement Point of Number of GPRS DL TBF Forcing Release by

Control Plane
Unit
Times

Description
When the user plane is transmitting the GPRS signaling DL TBF, at least one block must
be transmitted in every 5 seconds. After a DL TBF block is transmitted, BSC will start
or restart a 5-second DL block assigning timer. If the timer expires, it is considered that
the user plane has an instance suspension and the GPRS signaling DL TBF is released
abnormally.
Measurement Point
2-125

Figure 2-125 Measurement Point of Number of GPRS DL TBF Release due to Instance
Suspension
Unit
Times

Description
When the user plane is transmitting the GPRS signaling DL TBF, if the message fails
to be sent at the radio interface, the RLC instance fails to be created, or the resource
reassignment fails, the GPRS signaling DL TBF will be released abnormally.
Measurement Point
During the transmission of GPRS signaling DL TBF, if the message fails to be sent at the
radio interface, the RLC instance fails to be created, or the resource reassignment fails,
this counter increments.
Unit
Times
2-126


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; if
the N3105 counter reaches its maximum value, it is considered that the radio transmission
Measurement Point
Figure 2-126 Measurement Point of Number of EGPRS DL Signaling TBF Release

due to N3105 Overflow
Unit
Times
2-127


release due to other reasons
Description
When BSC is transmitting the last RLC block of EGPRS signaling DL TBF, set FBI to 1,
set RRBP to ask the MS to respond with a Packet Downlink Ack/Nack message, and at
the same time, activate T3191.
If the specified block receives the MS response, then T3191 will stop and the DL
transmission ends normally. If T3191 overflows, then it is considered that the radio
transmission fails and the EGPRS signaling DL TBF is released abnormally.
Measurement Point
Figure 2-127 Measurement Point of Number of EGPRS DL TBF Release due to Other
Reasons
Unit
Times

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

Measurement Point
Figure 2-128 Measurement Point of Number of EGPRS DL TBF Forcing Release by

Control Plane
Unit
Times

Description
When the user plane is transmitting the EGPRS signaling DL TBF, at least one block must
be transmitted in every 5 seconds. After a DL TBF block is transmitted, BSC will start
or restart a 5-second DL block assigning timer. If the timer expires, it is considered that
the user plane has an instance suspension and the EGPRS signaling DL TBF is released
abnormally.
Measurement Point
2-129

Figure 2-129 Measurement Point of Number of EGPRS DL TBF Release due to Instance
Suspension
Unit
Times

Description
When the user plane is transmitting the EGPRS signaling DL TBF, if the message fails
to be sent at the radio interface, the RLC instance fails to be created, or the resource
reassignment fails, the EGPRS signaling DL TBF will be released abnormally.
Measurement Point
During the transmission of EGPRS signaling DL TBF, if the message fails to be sent at the
radio interface, the RLC instance fails to be created, or the resource reassignment fails,
Unit
Times
2-130


establishments in release state
Description
If both MS and BSS support reestablishment in released state, BSS sets RRBP and sends
Packet UL Ack message (FAI =1 and TBF Est = 1) to MS after receiving all RLC blocks
from MS.
If MS has no new data to send, MS returns Packet Ctrl Ack message to BSS.
If MS has new data to send but no DL TBF is available, then TBF should be reestablished,
with the following two cases to be considered:
l 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.
l 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
Usage
This counter records the number of reestablishment times of MS in released state.
Measurement Point
The measurement point is A, as shown in Figure 2-130 and Figure 2-131.
Figure 2-130 Measurement Point on Number of GPRS UL TBF Reestablishments in

Released State (1)
Figure 2-131 Measurement Point on Number of GPRS UL TBF Reestablishments in

Released State (2)
2-131

Unit
Times

establishment with existing UL resource
Description
To accelerate TBF establishment, UPPB caches MSs UL/DL resource within a period of
time. When MS attempts to establish new UL TBF on PACCH, relevant resource is directly
assigned to MS if there is resource as indicated by UPPB; otherwise, MS sends request
for resource to CMP.
Usage
This counter records the number of reestablishing UL GPRS TBF in released state without
having to request for resource.
Measurement Point
Figure 2-132 Measurement Point of GPRS UL TBF Establishments with Existing UL

Resource
Unit
Times

Description
When MS has DL TBF and the TBF is in transmission status, if MS has UL data to send
but no UL TBF is available, MS sends Packet DL Ack message together with UL TBF
establishment request. This counter counts the number of resource re-applications after
receiving this request.
2-132

Usage
This counter records the number of requests for establishing UL GPRS TBF on PACCH.
Measurement Point
Figure 2-133 Measurement Point of Number of Requests for Establishing UL GPRS

TBF on PACCH
Unit
Times

establishments on PACCH
Description
When there is available DL TBF, MS sends Packet DL Ack message with UL TBF
establishment request. When there is a request to establish UL TBF on PACCH and the
TBF type is EGPRS, the counter increments.
Usage
This counter records the number of times of establishing EGPRS UL TBF on PACCH.
Measurement Point
When Packet DL Ack message with UL TBF establishment request is received, and the
TBF type is EGPRS, the counter increments.
Unit
Times
2-133


establishments in release state
Description
If both MS and BSS support reestablishment in released state, BSS sets RRBP and sends
Packet UL Ack message (FAI =1 and TBF Est = 1) to MS after receiving all RLC blocks
from MS.
If MS has no new data to send, MS returns Packet Ctrl Ack message to BSS.
If MS has new data to send but no DL TBF is available, then TBF should be reestablished,
with the following two cases to be considered:
l 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
l 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
Usage
This counter records the number of reestablishment times of MS in released state.
Measurement Point
The measurement point is A, as shown in Figure 2-134 and Figure 2-135.
Figure 2-134 Measurement Point on Number of EGPRS UL TBF Reestablishments in

Released State (1)
Figure 2-135 Measurement Point on Number of EGPRS UL TBF Reestablishments in

Released State (2)
2-134

Unit
Times

establishment with existing UL resource
Description
To accelerate TBF establishment, UPPB caches MSs UL/DL resource within a period of
time. When MS attempts to establish new UL TBF on PACCH, relevant resource is directly
assigned to MS if there is resource as indicated by UPPB; otherwise, MS sends request
for resource to CMP.
Usage
This counter records the number of reestablishing UL EGPRS TBF in released state
without having to request for resource.
Measurement Point
Figure 2-136 Measurement Point of EGPRS UL TBF Establishments with Existing UL

Resource
Unit
Times

Description
When MS has DL TBF and the TBF is in transmission status, if MS has UL data to send
but no UL TBF is available, MS sends Packet DL Ack message together with UL TBF
establishment request. This counter counts the number of resource re-applications after
receiving this request.
2-135

Usage
This counter records the number of requests for establishing UL EGPRS TBF on PACCH.
Measurement Point
Figure 2-137 Measurement Point of Number of Requests for Establishing UL EGPRS

TBF on PACCH
Unit
Times

Description
When MS has new data to transmit but no corresponding UL/DL TBF is available, MS
initiates UL TBF establishment flow, depending on whether the cell configures PBCCH on
CCCH/PCCCH.
Usage
This counter records the number of requests for establishing EGPRS UL TBF on
CCCH/PCCCH.
Measurement Point
Figure 2-138 Measurement Point of Number of EGPRS UL TBF Establishment Requests

on CCCH/PCCCH
2-136

Unit
Times
2.168 C900040167 Number of dynamic PDCH

preemption for CS service
Description
This counter counts the number of times of PDCH being preempted when the service
instance is performing CS service but fails to request for the radio channel.
Usage
This counter is used to find out the busy extent of PS service and CS service in the current
cell. It can be used as reference for expanding radio channel configuration, so as to meet
requirements of both CS and PS services.
Measurement Point
The counter increments when the following conditions are satisfied:
l When the service instance is performing CS service but fails to request for the radio
channel
l The database initiates the dynamic PDCH collection
Unit
Times
Related Features

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

Usage
This counter records the number of requests for establishing GPRS UL TBF on
CCCH/PCCCH.
Measurement Point
Figure 2-139 Measurement Point of Number of GPRS UL TBF Establishment Requests

on CCCH/PCCCH
Unit
Times

Description
When UL TBF exists, and there is DL data to be sent through SGSN, a request will be sent
to establish DL TBF on PACCH. This counter increments upon the request and the TBF
type is GPRS.
Usage
This counter counts the number of requests to establish GPRS DL TBF on PACCH.
Measurement Point
When a request is sent to establish DL TBF on PACCH and the TBF type is GPRS, this
counter increments.
Unit
Times
2-138


Description
When UL TBF exists, and there is DL data to be sent through SGSN, a request will be sent
to establish DL TBF on PACCH. This counter increments upon the request and the TBF
type is EGPRS.
Usage
This counter counts the number of requests to establish EGPRS DL TBF on PACCH.
Measurement Point
When a request is sent to establish DL TBF on PACCH and the TBF type is EGPRS, this
counter increments.
Unit
Times

Description
When there is available DL TBF, MS sends Packet DL Ack message with UL TBF
establishment request. When there is a request to establish UL TBF on PACCH and the
TBF type is GPRS, the counter increments.
Usage
This counter records the number of requests to establish GPRS UL TBF on PACCH.
Measurement Point
When Packet DL Ack message with UL TBF establishment request is received, and the
TBF type is GPRS, this counter increments.
Unit
Times
2-139


in MCS1 on PDTCH
Description
of DL pending RLC blocks from BSC to MS, with coding method of MCS1.
blocks.
Usage
method of MCS1.
Measurement Point
When BSC sends a pending RLC block whose coding method is MCS1 to MS, the counter
Unit
Times
Related Features
ZGO-03-05-001 Modulation and Coding Scheme #1~#9
2-140


in MCS2 on PDTCH
Description
blocks.
Usage
method of MCS2.
Measurement Point
When BSC sends a pending RLC block whose coding method is MCS2 to MS via BTS,
Unit
Times
Related Features
2-141


in MCS3 on PDTCH
Description
blocks.
Usage
method of MCS3.
Measurement Point
Unit
Times
Related Features
2-142


in MCS4 on PDTCH
Description
blocks.
Usage
method of MCS4.
Measurement Point
the counter increments. The measurement point is A, as shown inFigure 2-143.
Unit
Times
Related Features
2-143


in MCS5 on PDTCH
Description
blocks.
Usage
method of MCS5.
Measurement Point
Unit
Times
Related Features
2-144


in MCS6 on PDTCH
Description
blocks.
Usage
method of MCS6.
Measurement Point
Unit
Times
Related Features
2-145


in MCS7 on PDTCH
Description
blocks.
Usage
method of MCS7.
Measurement Point
Unit
Times
Related Features
2-146


in MCS8 on PDTCH
Description
blocks.
Usage
method of MCS8.
Measurement Point
Unit
Times
Related Features
2-147


in MCS9 on PDTCH
Description
blocks.
Usage
method of MCS9.
Measurement Point
Unit
Times
Related Features
2-148

2.182 C900040181 Number of DL RLC NACK blocks

in MCS1 on PDTCH
Description
of DL retransmitted RLC blocks from BSC to MS, with coding method of MCS1.
blocks.
Usage
coding method of MCS1.
Measurement Point
When BSC sends retransmitted RLC block whose coding method is MCS1 to MS via BTS,
Unit
Times
Related Features
2-149


in MCS2 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-150


in MCS3 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-151


in MCS4 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-152


in MCS5 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-153


in MCS6 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-154


in MCS7 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-155


in MCS8 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-156


in MCS9 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-157


MCS1 on PDTCH
Description
of DL first-transmitted RLC blocks from BSC to MS, with coding method of MCS1.
blocks.
Usage
on PDTCH, with coding method of MCS1.
Measurement Point
When BSC sends first-transmitted RLC block (with coding method of MCS1) to MS via
BTS, the counter increments. The measurement point is A, as shown in Figure 2-158.
Unit
Times
Related Features
2-158


MCS2 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-159


MCS3 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-160


MCS4 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-161


MCS5 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-162


MCS6 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-163


MCS7 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-164


MCS8 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-165


MCS9 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-166


in MCS1 on PDTCH
Description
useful UL MCS1-coded pending RLC blocks received on PDTCH.
blocks.
Usage
This counter counts the number of useful UL MCS1-coded pending RLC blocks received
by BSC on PDTCH.
Measurement Point
When BSC receives MCS1-coded UL pending RLC block, the counter increments. The
Unit
Times
Related Features
2-167


in MCS2 on PDTCH
Description
blocks.
Usage
by BSC on PDTCH.
Measurement Point
Unit
Times
Related Features
2-168


in MCS3 on PDTCH
Description
blocks.
Usage
by BSC on PDTCH.
Measurement Point
Unit
Times
Related Features
2-169


in MCS4 on PDTCH
Description
blocks.
Usage
by BSC on PDTCH.
Measurement Point
Unit
Times
Related Features
2-170


in MCS5 on PDTCH
Description
blocks.
Usage
by BSC on PDTCH.
Measurement Point
Unit
Times
Related Features
2-171


in MCS6 on PDTCH
Description
blocks.
Usage
by BSC on PDTCH.
Measurement Point
Unit
Times
Related Features
2-172


in MCS7 on PDTCH
Description
blocks.
Usage
by BSC on PDTCH.
Measurement Point
Unit
Times
Related Features
2-173


in MCS8 on PDTCH
Description
blocks.
Usage
by BSC on PDTCH.
Measurement Point
Unit
Times
Related Features
2-174


in MCS9 on PDTCH
Description
blocks.
Usage
by BSC on PDTCH.
Measurement Point
Unit
Times
Related Features
2-175


in MCS1 on PDTCH
Description
useful UL MCS1-coded retransmitted RLC blocks received on PDTCH.
blocks.
Usage
This counter counts the number of useful UL MCS1-coded retransmitted RLC blocks
Measurement Point
When BSC receives MCS1-coded UL retransmitted RLC block, the counter increments.
Unit
Times
Related Features
2-176


in MCS2 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-177


in MCS3 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-178


in MCS4 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-179


in MCS5 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-180


in MCS6 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-181


in MCS7 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-182


in MCS8 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-183


in MCS9 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-184


MCS1 on PDTCH
Description
useful UL MCS1-coded first-transmitted RLC blocks received on PDTCH.
blocks.
Usage
This counter counts the number of useful UL MCS1-coded first-transmitted RLC blocks
Measurement Point
When BSC receives MCS1-coded UL first-transmitted RLC block, the counter increments.
Unit
Times
Related Features
2-185


MCS2 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-186


MCS3 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-187


MCS4 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-188


MCS5 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-189


MCS6 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-190


MCS7 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-191


MCS8 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-192


MCS9 on PDTCH
Description
blocks.
Usage
Measurement Point
Unit
Times
Related Features
2-193

This page intentionally left blank.
2-194

Chapter 3
CPU Load Measurement
Table of Contents
Overview ....................................................................................................................3-1
C900050001 Average load of the processor ...............................................................3-1
C900050002 Peak value of the processor load...........................................................3-1
3.1 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.
3.2 C900050001 Average load of the processor

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

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

Unit
Percent
3-2

Chapter 4
CS Basic Measurement
Table of Contents
Overview ....................................................................................................................4-8
C900060001 Number of MTC access attempts ..........................................................4-8
C900060002 Number of MTC access success ...........................................................4-9
C900060003 Number of SDCCH seizure attempts for assignment ...........................4-10
C900060004 Number of SDCCH seizure success for assignment ............................4-11
C900060005 Number of SDCCH seizure failure for assignment ...............................4-12
C900060006 Number of SDCCH seizure attempts for handover ..............................4-13
C900060007 Number of SDCCH seizure failure for handover ..................................4-15
C900060008 Number of SDCCH allocation success for assignment ........................4-17
C900060009 Number of SDCCH allocation failure for assignment............................4-18
C900060010 Number of signaling TCH/F seizure attempts for assignment...............4-19
C900060011 Number of signaling TCH/F seizure failure for assignment...................4-20
C900060012 Number of signaling TCH/F seizure attempts for handover..................4-21
C900060013 Number of signaling TCH/F seizure failure for handover......................4-24
C900060014 Number of signaling TCH/F allocation success for assignment............4-25
C900060015 Number of signaling TCH/F allocation failure for assignment ...............4-26
C900060016 Number of signaling TCH/F allocation failure for handover ..................4-27
C900060017 Number of signaling TCH/F assignment success for assignment.........4-28
C900060018 Number of signaling TCH/F assignment failure for assignment............4-29
C900060019 Number of voice TCH/F seizure attempts for assignment ....................4-30
C900060020 Number of voice TCH/F seizure failure for assignment ........................4-32
C900060021 Number of voice TCH/F seizure attempts for handover .......................4-33
C900060022 Number of voice TCH/F seizure failure for handover ...........................4-36
C900060023 Number of TCH/F allocation success for assignment (speech
version1) ..................................................................................................................4-37
C900060024 Number of TCH/F allocation failure due to channel activation failure
for assignment (speech version1).............................................................................4-38
version2) ..................................................................................................................4-39
version3) ..................................................................................................................4-40
for assignment (speech version3).............................................................................4-42
C900060028 Number of voice TCH/F assignment success ......................................4-43
C900060029 Number of voice TCH/F assignment failure for assignment .................4-44
C900060030 Number of data TCH/F seizure attempts for assignment......................4-45
C900060031 Number of data TCH/F seizure failure for assignment .........................4-47
4-1

C900060032 Number of data TCH/F seizure attempts for handover.........................4-48

C900060033 Number of data TCH/F seizure failure for handover.............................4-51
C900060034 Number of data TCH/F allocation success for assignment...................4-52
C900060035 Number of data TCH/F allocation failure due to channel activation
failure for assignment ...............................................................................................4-53
C900060036 Number of data TCH/F assignment success........................................4-54
C900060037 Number of data TCH/F assignment failure...........................................4-56
C900060038 Number of signaling TCH/H seizure attempts for assignment ..............4-57
C900060039 Number of signaling TCH/H seizure failure for assignment ..................4-58
C900060040 Number of signaling TCH/H seizure attempts for handover .................4-59
C900060041 Number of signaling TCH/H seizure failure for handover .....................4-62
C900060042 Number of voice TCH/H seizure attempts for assignment....................4-63
C900060043 Number of voice TCH/H seizure failure for assignment........................4-65
C900060044 Number of voice TCH/H seizure attempts for handover .......................4-66
C900060045 Number of voice TCH/H seizure failure for handover ...........................4-69
C900060046 Number of data TCH/H seizure attempts for assignment .....................4-70
C900060047 Number of data TCH/H seizure failure for assignment .........................4-72
C900060048 Number of data TCH/H seizure attempts for handover ........................4-73
C900060049 Number of data TCH/H seizure failure for handover ............................4-76
C900060050 Number of SAPI3 link establishment requests on SDCCH (MO-SM) ...4-77
C900060051 Number of SAPI3 link establishment requests on SDCCH (MT-SM) ....4-79
C900060052 Number of SDCCH drops due to handover failure ...............................4-80
C900060053 Number of SDCCH drops ....................................................................4-82
C900060054 Number of TCH/F drops ......................................................................4-83
C900060055 Number of TCH/H drops......................................................................4-83
C900060056 Average number of idle TCH/F with interference band 1......................4-84
C900060061 Average number of idle TCH/H with interference band 1 .....................4-86
C900060066 Number of samples with UL RQ = 0 ....................................................4-89
C900060074 Number of samples with DL RQ = 0 ....................................................4-93
4-2

Chapter 4 CS Basic Measurement

C900060082 Number of TCH/F handover attempts due to UL strength ....................4-97
C900060083 Number of TCH/F handover attempts due to DL strength ....................4-98
C900060084 Number of TCH/F handover attempts due to UL quality.......................4-99
C900060085 Number of TCH/F handover attempts due to DL quality.......................4-99
C900060086 Number of TCH/F handover attempts due to UL interference ............4-100
C900060087 Number of TCH/F handover attempts due to DL interference ............4-101
C900060088 Number of TCH/F handover attempts due to good C/I .......................4-102
C900060089 Number of TCH/F handover attempts due to bad C/I .........................4-103
C900060090 Number of TCH/F handover attempts due to PBGT...........................4-104
C900060091 Number of TCH/F handover attempts due to large TA .......................4-105
C900060092 Number of TCH/F handover attempts due to other reasons...............4-106
C900060093 Number of BSC-controlled inter-cell outgoing handover ....................4-106
C900060094 Number of BSC-controlled inter-cell outgoing handover success .......4-107
C900060095 Number of MSC-controlled outgoing handover ..................................4-108
C900060096 Number of MSC-controlled outgoing handover success ....................4-109
C900060097 Number of BSC-controlled inter-cell incoming handover .................... 4-110
C900060098 Number of BSC-controlled inter-cell incoming handover success ...... 4-111
C900060099 Number of MSC-controlled incoming handover.................................. 4-112
C900060100 Number of MSC-controlled incoming handover due to forced release . 4-113
C900060101 Number of MSC-controlled incoming handover due to queue ............ 4-114
C900060102 Number of MSC-controlled incoming handover success .................... 4-115
C900060103 Number of incoming handover from undefined layer (GSM900) to
current layer(GSM1800) ......................................................................................... 4-115
C900060104 Number of incoming handover success from undefined
layer(GSM900) to current layer (GSM1800) ........................................................... 4-116
C900060105 Number of incoming handover from undefined layer (GSM1800) to
current layer (GSM900) .......................................................................................... 4-117
C900060106 Number of incoming handover success from undefined
layer(GSM1800) to current layer(GSM900) ............................................................ 4-118
C900060107 Number of incoming handover from the same layer GSM900 to
GSM1800............................................................................................................... 4-119
C900060108 Number of incoming handover success from the same layer GSM900
to GSM1800 ...........................................................................................................4-120
C900060109 Number of incoming handover from GSM900 to GSM1800 from the
upper layer .............................................................................................................4-121
C900060110 Number of incoming handover success from GSM900 to GSM1800 in
the upper layer .......................................................................................................4-122
C900060111 Number of incoming handover from GSM900 to GSM1800 in the
lower layer..............................................................................................................4-123
4-3

C900060112 Number of incoming handover success from GSM900 to GSM1800 in

the lower layer........................................................................................................4-124
same layer .............................................................................................................4-125
C900060114 Number of incoming handover success from GSM1800 to GSM900
from the same layer................................................................................................4-126
upper layer .............................................................................................................4-127
from the upper layer ...............................................................................................4-128
lower layer..............................................................................................................4-129
from the lower layer................................................................................................4-130
C900060119 Number of Intra-cell handover ...........................................................4-131
C900060120 Number of Intra-cell handover success..............................................4-132
C900060121 Maximum number of busy TCH/H......................................................4-133
C900060122 Average number of available SDCCH................................................4-134
C900060123 Average number of unavailable SDCCH............................................4-135
C900060124 SDCCH busy time .............................................................................4-136
C900060125 Average number of available radio channel .......................................4-137
C900060126 Average number of unavailable radio channel ...................................4-137
C900060127 TCH/H busy time...............................................................................4-138
C900060128 Maximum number of busy TCH/F ......................................................4-139
C900060129 TCH/F busy time ...............................................................................4-140
C900060130 Number of healthy TRXs ...................................................................4-141
C900060131 Number of CM service requests of MOC ...........................................4-142
C900060132 Number of SAPI3 link establishment success on SDCCH (MT-SM) ...4-143
C900060133 Number of available defined SDCCH ................................................4-144
C900060134 Number of available defined TCH/F...................................................4-145
C900060135 Number of signaling TCH/H assignment failure .................................4-146
C900060136 Number of MOC access attempts......................................................4-147
C900060137 Number of wireless access due to paging responses ........................4-148
C900060138 Number of TCH/F allocation failure due to BTS connection failure for
assignment (speech version1)................................................................................4-149
C900060139 Number of TCH/F allocation failure due to BIU connection failure for
C900060140 Number of TCH/F allocation failure due to TCU connection failure for
for assignment (speech version2)...........................................................................4-152
4-4

C900060148 Number of data TCH/F allocation failure due to BTS connection
failure for assignment) ............................................................................................4-159
C900060149 Number of data TCH/F allocation failure due to BIU connection failure
for assignment........................................................................................................4-160
C900060150 Number of data TCH/F allocation failure due to TCU connection
failure for assignment .............................................................................................4-161
C900060151 Number of voice TCH/H drops due to handover failure......................4-162
C900060152 Number of Abis interface paging command messages ......................4-164
C900060153 Number of Abis CS paging messages ...............................................4-165
C900060154 Number of Abis PS paging messages ...............................................4-166
C900060155 Number of available defined TCH/H ..................................................4-166
for handover(speech version1) ...............................................................................4-167
handover (speech version1) ...................................................................................4-169
for handover(speech version2) ...............................................................................4-172
for handover (speech version3) ..............................................................................4-177
C900060168 Number of Voice TCH/F handover success .......................................4-182
4-5

C900060169 Number of data TCH/F allocation failure due to channel activation

failure for handover ................................................................................................4-184
C900060170 Number of data TCH/F allocation failure due to BTS connection
C900060171 Number of data TCH/F allocation failure due to BIU connection failure
for handover ...........................................................................................................4-186
C900060172 Number of data TCH/F allocation failure due to TCU connection
C900060173 Number of data TCH/F handover success .........................................4-189
C900060174 Number of signaling TCH/H allocation failure for assignment.............4-191
C900060175 Number of TCH/H allocation failure due to channel activation failure
C900060176 Number of TCH/H allocation failure due to BTS connection failure for
C900060177 Number of TCH/H allocation failure due to BIU connection failure for
C900060178 Number of TCH/H allocation failure due to TCU connection failure for
4-6

assignment (speech version3)................................................................................ 4-211
C900060199 Number of Voice TCH/H assignment success ...................................4-218
C900060200 Number of Voice TCH/H assignment failure.......................................4-220
C900060201 Number of Voice TCH/H handover success.......................................4-221
C900060202 Number of data TCH/H allocation failure due to channel activation
C900060203 Number of data TCH/H allocation failure due to BTS connection
C900060204 Number of data TCH/H allocation failure due to BIU connection failure
for assignment........................................................................................................4-225
C900060205 Number of data TCH/H allocation failure due to TCU connection
C900060206 Number of data TCH/H allocation failure due to channel activation
C900060207 Number of data TCH/H allocation failure due to BTS connection
C900060208 Number of data TCH/H allocation failure due to BIU connection failure
for handover ...........................................................................................................4-229
C900060209 Number of data TCH/H allocation failure due to TCU connection
C900060210 Number of data TCH/H assignment success .....................................4-232
C900060211 Number of data TCH/H assignment failure.........................................4-233
C900060212 Number of data TCH/H handover success.........................................4-234
C900060213 Number of BSC-controlled incoming handover due to forced release .4-237
C900060214 Number of BSC-controlled incoming handover due to queues ...........4-238
C900060215 Number of BSC-controlled incoming handover due to forced
handover ................................................................................................................4-239
C900060216 Number of MSC-controlled incoming handover due to forced
handover ................................................................................................................4-241
C900060217 Number of unavailable defined TCH/H ..............................................4-242
C900060218 Number of unavailable defined TCH/F...............................................4-243
C900060219 Number of signaling TCH/F drops due to handover failure.................4-244
4-7

C900060220 Number of voice TCH/F drops due to handover failure ......................4-246

C900060221 Number of data TCH/F drops due to handover failure........................4-248
C900060222 Number of signaling TCH/H drops due to handover failure ................4-250
C900060223 Number of data TCH/H drops due to handover failure .......................4-252
C900060224 Number of TCH/H handover attempts due to UL strength..................4-254
C900060225 Number of TCH/H handover attempts due to DL strength..................4-255
C900060226 Number of TCH/H handover attempts due to UL quality ....................4-256
C900060227 Number of TCH/H handover attempts due to DL quality ....................4-256
C900060228 Number of TCH/H handover attempts due to UL interference ............4-257
C900060229 Number of TCH/H handover attempts due to DL interference ............4-258
C900060230 Number of TCH/H inter-subcell handover attempts due to good C/I...4-259
C900060231 Number of TCH/H inter-subcell handover attempts due to bad C/I.....4-260
C900060232 Number of TCH/H handover attempts due to PBGT ..........................4-261
C900060233 Number of TCH/H handover attempts due to large TA .......................4-262
C900060234 Number of TCH/H handover attempts due to other reasons ..............4-263
C900060235 Number of signaling TCH/H assignment success ..............................4-264
C900060236 Number of MOC access success.......................................................4-265
C900060237 Number of dual band outgoing handover...........................................4-266
C900060238 Number of dual band outgoing handover success .............................4-267
C900060239 Number of dual band incoming handover ..........................................4-268
C900060240 Number of dual band incoming handover success.............................4-269
C900060241 Number of SDCCH assignment attempts ..........................................4-269
C900060242 Number of SDCCH assignments success .........................................4-271
C900060243 Number of SDCCH assignment failure ..............................................4-272
C900060244 Number of voice TCH/F drops due to radio link failure.......................4-273
C900060245 Number of voice TCH/H drops due to radio link failure ......................4-274
4.1 Overview
CS basic measurement involves counters that are used to evaluate the circuit switching
service performance and status. These counters are often used in measurement related to
radio access, SDCCH, TCH, SAPI3, call drop, handover, Abis interface message statistics,
and radio resource availability.
4.2 C900060001 Number of 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.
4-8

Usage
This counter is used to find out the frequency of channel request due to MTC.
Measurement Point
The counter counts when MS requests for channel from BSC and TA does not exceed the
cell range. The measurement point is A1, as shown in Figure 4-1.
Figure 4-1 Radio Access Flow
Unit
Times
4.3 C900060002 Number of MTC access success

Description
This counter counts the number of MS successfully accessing the channel assigned in
the immediate assignment message (the access reason is due to MTC). The counter
increments when the following two conditions are satisfied:
l MS receives the IMM_ASS message from BSC and successfully accesses the
channel.
l 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.
4-9

Measurement Point
This counter counts when BSC receives the EST_IND message. The measurement point
is A4, as shown in Figure 4-2.
Unit
Times
4.4 C900060003 Number of 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.
l If allocation and occupation succeed, C900060003 and C900060004 accumulate

simultaneously.
l If occupation fails and the failure is due to transceiver fault, C900060003,
C900060004, and C900060005 do not change.
l For failures in other cases, C900060003 and C900060005 accumulate
simultaneously.
4-10

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 Point
This counter counts when BSC completes requesting for channel (due to assignment)
(C900060004 + C900060005). The measurement point is A1, as shown in Figure 4-3.
Figure 4-3 Immediate Assignment Flow
Unit
Times
Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH
ZGB-06-01-007 Cell Traffic Statistics
4.5 C900060004 Number of SDCCH seizure success

for assignment
Description
request. This counter accumulates when allocation and occupation succeed.
4-11

Usage
This counter counts the number of successful SDCCH channel occupations during
assignment.
Measurement Point
This counter counts when BSC requests for channel (due to assignment) and occupies
the channel successfully. The measurement point is A1, as shown in Figure 4-4.
Unit
Times
Related Features
4.6 C900060005 Number of SDCCH seizure failure for

assignment
Description
request.
l If allocation succeeds but occupation fails, this counter accumulates.
l If the request returns that the transceiver is faulty, this counter does not change.
4-12

l For failures in other cases, this counter accumulates.
Usage
This counter counts the number of SDCCH channel occupation failures during assignment.
Measurement Point
This counter counts when BSC requests for channel (due to assignment) but fails to occupy
the channel. The measurement point is A1, as shown in Figure 4-5.
Unit
Times
Related Features
4.7 C900060006 Number of SDCCH seizure attempts

for handover
Description
SDCCH channel allocation attempt is activated by the channel request message
RADIO_APPLY from other channel instances. After BSC receives this message, it
attempts to allocate channel for the request.
4-13


simultaneously.
l If occupation fails, C900060006 and C900060007 accumulate simultaneously.
l If the request returns no channel available but queuing or forced release is possible,
enter the state of waiting for resource.
If the waiting for resource succeeds, C900060006 and C901250005 accumulate
simultaneously.
If the waiting for resource fails and the failure is due to transceiver fault,
C900060006, C901250005, and C900060007 do not change.

simultaneously.
Usage
This counter counts the number of SDCCH channel occupation attempts during handover,
including the number of occupation success (C900060006) and the number of occupation
failure (C900060007).
Measurement Point
BSC completes requesting for channel (due to handover), or BSC receives the internal
message of waiting for resource successfully or waiting for resource failed (C901250005
+ C900060007). The measurement point is B1 as shown in Figure 4-6 and C1 as shown
in Figure 4-7.
Figure 4-6 Internal Handover Flow (Intra-Cell Handover)
4-14

Figure 4-7 External Handover Flow
Unit
Times
Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover
4.8 C900060007 Number of SDCCH seizure failure for

handover
Description
SDCCH channel allocation attempt is activated by the channel request message
RADIO_APPLY from other channel instances. After BSC receives this message, it
attempts to allocate channel for the request.
l If occupation fails, this counter accumulates.

enter the state of waiting for resource. If the waiting for resource fails, this counter
accumulates.
Usage
This counter counts the number of SDCCH occupation failure.
4-15

Measurement Point
BSC requests for channel (due to handover) but fails to occupy the channel, or BSC fails
to wait for internal resource. The measurement point is B1 as shown in Figure 4-8 and C1
Figure 4-8 Internal Handover Flow (Intra-Cell Handover)
Figure 4-9 External Handover Flow
Unit
Times
Related Features
4-16

4.9 C900060008 Number of 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 message to BTS to activate this SDCCH.
If the SDCCH is activated successfully (that is, when BSC receives the CHL_ACT_ACK
message from BTS), this counter accumulates.
Usage
This counter counts the number of successful SDCCH channel allocations during
assignment.
Measurement Point
This counter counts when BSC receives the CHL_ACT_ACK message from BTS and the
cause is assignment. The measurement point is A2, as shown in Figure 4-10.
Unit
Times
Related Features
4-17

4.10 C900060009 Number of SDCCH allocation failure

for assignment
Description
channel successfully, BSC sends the CHL_ACT message to BTS to activate this SDCCH.
If channel activation fails due to receiving channel activation failure message, incorrect
channel activation response message, T9103 being timeout, channel instance being
released or channel being forcibly released, this counter accumulates.
Usage
This counter counts the number of SDCCH channel allocation failure during assignment.
Measurement Point
BSC activates SDCCH channel due to assignment, but receives channel activation failure
message, incorrect channel activation response message, T9103 being timeout, channel
instance being released, or channel being forcibly released. The measurement point is
A2, as shown in Figure 4-11.
Unit
Times
4-18

Related Features
4.11 C900060010 Number of signaling TCH/F seizure

attempts for assignment
Description
This counter counts the number of TCH/F channel occupation attempts during assigning
signaling channels, including the number of occupation success (C901260002) and the
number of occupation failure (C900060011).
Usage
After BSC receives the channel request, it attempts to allocate channel for the request.
simultaneously.
l If the request returns that the transceiver is faulty, C900060010, C901260002, and
C900060011 do not change.
l For other cases, C900060010 and C900060011 accumulate simultaneously.
Measurement Point
This counter counts when BSC completes requesting for channel (due to assignment
and the channel is used as signaling channel) (C901260002 + C900060011). The
Unit
Times
4-19

Related Features
ZGB-03-01-004 Immediate TCH Assignment
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

failure for assignment
Description
This counter counts the number of TCH/F channel occupation failures during assigning
signaling channels.
Measurement Point
BSC requests for channel (due to assignment and the channel is used as signaling
channel) but fails to occupy the channel, or BSC fails to wait for internal resource. The
Figure 4-13 Immediate Assignment Occupation Failure Flow 1
Unit
Times
Related Features
4-20


attempts for handover
Description
This counter counts the number of TCH/F channel occupation attempts during signaling
channel handover, including the number of occupation success (C901260005) and the
number of occupation failure (C900060013).

simultaneously.
simultaneously.
If the waiting for resource fails, C900060012 and C900060013 accumulate
simultaneously.
simultaneously.
Measurement Point
BSC completes requesting for channel (due to handover and the channel is used
as signaling channel), or BSC receives the internal message of waiting for resource
successfully or waiting for resource failed (C901260002 + C900060011). The
measurement point is C1 as shown in Figure 4-14 and Figure 4-15, and D1 as shown in
Figure 4-16 and Figure 4-17.
4-21

Figure 4-14 Internal Handover Flow (Intra-Cell Handover, TC Is Internal)
Figure 4-15 Internal Handover Flow (Intra-Cell Handover, Channel Type Changed, TC Is
External)
4-22

Figure 4-16 External Handover Flow (TC Is Internal)
Figure 4-17 External Handover Flow (TC Is External)
Unit
Times
Related Features
ZGB-02-02-001 Basic Handover
4-23


failure for handover
Description
This counter counts the number of TCH/F channel occupation failures during signaling
channel handover.
accumulates.
Measurement Point
BSC requests for channel (due to handover and the channel is used as signaling channel)
but fails to occupy the channel, or BSC fails to wait for internal resource. The measurement
point is C1 as shown in Figure 4-18 and D1 as shown in Figure 4-19.
Figure 4-18 Intra-BSC Handover Occupation Failure Flow
Figure 4-19 Inter-BSC Handover Occupation Failure Flow
Unit
Times
Related Features
4-24

4.15 C900060014 Number of 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 message to BTS to activate this TCH/F channel.
If the activation succeeds (that is, when BSC receives the CHL_ACT_ACK message from
BTS), the counter accumulates.
Measurement Point
The counter increments when BSC receives the CHL_ACT_ACK message from BTS,
the cause is due to assignment and the channel is used as signaling channel. The
Unit
Times
Related Features
4-25


Description
This counter counts the number of TCH/F channel allocation failures during signaling
channel assignment.
After BSC responds to the channel request message to allocate and occupy TCH/F
channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F
channel.
If the channel activation fails due to receiving channel activation failure message, incorrect
channel activation response message, T9103 timeout, channel instance being released or
channel being released forcibly, this counter accumulates.
Measurement Point
BSC activates TCH/F channel due to assignment and uses it as signaling channel,
but receives channel activation failure message, incorrect channel activation response
message, T9103 being timeout, channel instance being released, or channel being
forcibly released. The measurement point is A2, as shown in Figure 4-21.
Figure 4-21 Immediate Assignment Allocation Failure Flow 2
Unit
Times
Related Features
4-26


Description
This counter counts the number of TCH/F channel allocation failures during signaling
channel handover.
successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F channel.
channel being released forcibly, this counter will accumulate.
Measurement Point
BSC activates TCH/F channel due to handover and uses it as signaling channel, but
receives channel activation failure message, incorrect channel activation response
forcibly released.
The measurement point is C3 as shown in Figure 4-22 and D3 as shown in Figure 4-23.
Figure 4-22 Internal Handover Failure Flow 1 (Intra-Cell Handover, TC Is Internal)
Figure 4-23 External Handover Failure Flow 2 (TC Is Internal)
4-27

Unit
Times
Related Features
4.18 C900060017 Number of signaling TCH/F

assignment success for assignment
Description
This counter counts the number of successful assignments of TCH/F as signaling channel.
successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. For
immediate assignment, after the TCH/F activation succeeds, BTS finds the MS accessed
and sends the EST_IND message to BSC, this counter accumulates when BSC receives
the message correctly.
Measurement Point
For immediate assignment, this counter counts when BSC receives the EST_IND message
correctly. The measurement point is A3, as shown in Figure 4-24.
Unit
Times
Related Features
4-28


assignment failure for assignment
Description
This counter counts the number of failing to assign TCH/F channel as signaling channel.
channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F.
If BSC does not receive the MS access notification within a certain time, this assignment
fails.
Measurement Point
For immediate assignment, this counter counts when BSC receives incorrect EST_IND
message or T3101 is timeout. The measurement point is A3, as shown in Figure 4-25.
Figure 4-25 Immediate Assignment Failure Flow 3
Unit
Times
Related Features
4-29

4.20 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.
simultaneously.
simultaneously.
simultaneously.
Measurement Point
BSC completes requesting for channel (due to assignment and the channel is used as
voice channel), or BSC receives the internal message of waiting for resource successfully
or waiting for resource failed (C901260021 + C900060020). The measurement point is
B1, as shown in Figure 4-26 and Figure 4-27.
.
4-30

Figure 4-26 Common Assignment Flow (TC Is Internal)
Figure 4-27 Common Assignment Flow (TC Is External)
Unit
Times
Related Features
4-31

4.21 C900060020 Number of voice TCH/F seizure failure

for assignment
Description
This counter counts the number of TCH/F channel occupation failure during voice channel
assignment.
After BSC receives the channel request message, it attempts to allocate channel for the
request.

accumulates.
Measurement Point
BSC requests for channel (due to assignment and the channel is used as voice channel)
point is B1, as shown in Figure 4-28.
Figure 4-28 Common Assignment Failure Flow 1 (TC Is Internal)
Unit
Times
Related Features
4-32


Description
voice channel handover, including the number of occupation success (C901260024) and
request.

simultaneously.
simultaneously.
simultaneously.
simultaneously.
Measurement Point
BSC completes requesting for channel (due to handover and the channel is used as voice
channel), or BSC receives the internal message of waiting for resource successfully or
waiting for resource failed (C901260024 + C900060022). The measurement point is C1
as shown in Figure 4-29 and Figure 4-30, and D1 as shown in Figure 4-31 and Figure 4-32.
4-33

External)
4-34

Unit
Times
Related Features
4-35

4.23 C900060022 Number of voice TCH/F seizure failure

for handover
Description
This counter counts the number of TCH/F channel occupation failure during voice channel
handover.
request.
l If allocation or occupation fails, this counter accumulates.

accumulates.
Measurement Point
BSC requests for channel (due to handover and the channel is used as voice channel) but
fails to occupy the channel, or BSC fails to wait for internal resource. The measurement
Unit
Times
Related Features
4-36


4.24 C900060023 Number of 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).
successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If the
TCH/F is activated successfully (that is, when BSC receives the CHL_ACT_ACK message
from BTS), this counter accumulates.
Measurement Point
This counter counts when BSC receives the CHL_ACT_ACK message from BTS, the
cause is assignment and the channel is used as voice channel (speech version 1). The
measurement point is B3, as shown in Figure 4-35 and Figure 4-36.
4-37

Unit
Times
Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec
4.25 C900060024 Number of TCH/F allocation failure

due to channel activation failure for assignment
(speech 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).
successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If channel
activation fails due to receiving channel activation failure message, incorrect channel
activation response message, T9103 being timeout, channel instance being released or
channel being forcibly released, this counter accumulates.
Measurement Point
BSC activates TCH/F channel due to assignment and uses the channel as voice channel
(speech version 1), but receives channel activation failure message, incorrect channel
activation response message, T9103 being timeout, channel instance being released, or
channel being forcibly released. The measurement point is B3, as shown in Figure 4-37.
4-38

Unit
Times
Related Features

Description
Measurement Point
4-39

Unit
Times
Related Features

Description
4-40

Measurement Point
Unit
Times
4-41

Related Features
ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

(speech version3)
Description
activation failure during voice channel assignment (speech version 3).
successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If channel
activation fails due to receiving channel activation failure message, incorrect channel
activation response message, T9103 being timeout, channel instance being released or
channel being forcibly released, this counter accumulates.
Measurement Point
BSC activates TCH/F channel due to assignment and uses the channel as voice channel
(speech version 3), 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 4-42.
Unit
Times
Related Features
4-42

4.29 C900060028 Number of voice TCH/F assignment

success
Description
This counter counts the number of successful assignments of TCH/F as voice channel.
successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. For
assignment from A-interface, after BSC receives the assignment success message, the
counter accumulates.
Measurement Point
For assignment from A-interface, the counter accumulates when BSC receives the
assignment success message. The measurement point is B5, as shown in Figure 4-43
and Figure 4-44.
4-43

Unit
Times
Related Features

Description
This counter counts the number of failing to assign TCH/F channel as voice channel.
fails.
Measurement Point
This counter counts when BSC receives assignment failure message, abnormal message,
channel instance being released, channel instance being released forcibly, or timer timeout
message. The measurement point is B5, as shown in Figure 4-45.
4-44

Unit
Times
Related Features
4.31 C900060030 Number of data TCH/F seizure

Description
data channel assignment, including the number of occupation success (C901260070) and
request.

simultaneously.

simultaneously.

simultaneously.
4-45

simultaneously.
Measurement Point
data channel), or BSC receives the internal message of waiting for resource successfully
Unit
Times
4-46

Related Features
ZGB-01-03-002 Data Traffic Channels
4.32 C900060031 Number of data TCH/F seizure failure

for assignment
Description
This counter counts the number of TCH/F channel occupation failure during data channel
assignment.
request.
accumulates.
Measurement Point
BSC requests for channel (due to assignment and the channel is used as data channel) but
Unit
Times
4-47

Related Features

Description
data channel handover, including the number of occupation success (C901260073) and
request.
simultaneously.
simultaneously.
simultaneously.
simultaneously.
Measurement Point
BSC completes requesting for channel (due to handover and the channel is used as data
4-48

External)
4-49

Unit
Times
Related Features
4-50

4.34 C900060033 Number of data TCH/F seizure failure

for handover
Description
This counter counts the number of TCH/F channel occupation failure during data channel
handover.
request.

accumulates.
Measurement Point
BSC requests for channel (due to handover and the channel is used as data channel) but
Unit
Times
Related Features
4-51


4.35 C900060034 Number of data TCH/F allocation

Description
This counter counts the number of TCH/F channel being allocated successfully during data
channel assignment.
Measurement Point
cause is assignment and the channel is used as data channel. The measurement point is
4-52

Unit
Times
Related Features

failure due to channel activation failure for
assignment
Description
activation failure during data channel assignment.
successfully, if connection succeeds, BSC sends the CHL_ACT message to BTS to
activate this TCH/F. If channel activation fails due to receiving channel activation failure
instance being released or channel being forcibly released, this counter accumulates.
Measurement Point
BSC activates TCH/F channel due to assignment and uses the channel as data channel,
message, T9103 being timeout, channel instance being released, or channel being forcibly
released. The measurement point is B3, as shown in Figure 4-57.
4-53

Unit
Times
Related Features
4.37 C900060036 Number of data TCH/F assignment

success
Description
This counter counts the number of successful assignments of TCH/F as data channel.
For assignment from A-interface, after BSC receives the assignment success message,
the counter accumulates.
Measurement Point
and Figure 4-59.
4-54

Unit
Times
Related Features
4-55


failure
Description
This counter counts the number of failing to assign TCH/F channel as data channel.
fails.
Measurement Point
Unit
Times
Related Features
4-56

4.39 C900060038 Number of 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 number of occupation success (C901270002)
and the number of occupation failure (C900060039).
request.
simultaneously.
l For other cases, C900060038 and C900060039 accumulate simultaneously.
Measurement Point
This counter counts when BSC completes requesting for channel (due to assignment
and the channel is used as signaling channel) (C901270002 + C900060039). The
Unit
Times
Related Features
ZGO-01-01-001 Half Rate
4-57


ZGO-03-02-005 Dynamic Half Rate Allocation

Description
This counter counts the number of TCH/H channel occupation failure during signaling
channel assignment.
request.

Measurement Point
BSC requests for channel (due to assignment and the channel is used as signaling
channel) but fails to occupy the channel, or BSC fails to wait for internal resource. The
Figure 4-62 Immediate Assignment Occupation Failure Flow 1
Unit
Times
Related Features
4-58


Description
signaling channel handover, including the number of occupation success (C901270005)
and the number of occupation failure (C900060041).

simultaneously.
simultaneously.
simultaneously.
simultaneously.
Measurement Point
BSC completes requesting for channel (due to handover and the channel is used
as signaling channel), or BSC receives the internal message of waiting for resource
successfully or waiting for resource failed (C901270005 + C900060041). The
measurement point is C1 as shown in Figure 4-63 and Figure 4-64, and D1 as shown in
4-59

External)
4-60

Unit
Times
Related Features
4-61


Description
This counter counts the number of TCH/H channel occupation failures during signaling
channel handover.
accumulates.
Measurement Point
BSC requests for channel (due to handover and the channel is used as signaling channel)
Unit
Times
Related Features
4-62


4.43 C900060042 Number of voice TCH/H seizure

Description
voice channel assignment, including the number of occupation success (C901270021) and
request.

simultaneously.
simultaneously.

simultaneously.
simultaneously.
Measurement Point
voice channel), or BSC receives the internal message of waiting for resource successfully
4-63

Unit
Times
Related Features
4-64


Description
This counter counts the number of TCH/H channel occupation failure during voice channel
assignment.
request.

accumulates.
Measurement Point
BSC requests for channel (due to assignment and the channel is used as voice channel)
Unit
Times
Related Features
4-65


Description
voice channel handover, including the number of occupation success (C901270024) and
request.

simultaneously.
simultaneously.
simultaneously.
simultaneously.
Measurement Point
BSC completes requesting for channel (due to handover and the channel is used as voice
4-66

External)
4-67

Unit
Times
Related Features
4-68


Description
This counter counts the number of TCH/H channel occupation failure during voice channel
handover.
request.
l If allocation or occupation fails, this counter accumulates.

accumulates.
Measurement Point
BSC requests for channel (due to handover and the channel is used as voice channel) but
Unit
Times
Related Features
4-69



4.47 C900060046 Number of data TCH/H seizure

Description
data channel assignment, including the number of occupation success (C901270070) and
request.
simultaneously.
simultaneously.
simultaneously.
simultaneously.
Measurement Point
data channel), or BSC receives the internal message of waiting for resource successfully
4-70

Unit
Times
Related Features
4-71

4.48 C900060047 Number of data TCH/H seizure failure

for assignment
Description
This counter counts the number of TCH/H channel occupation failure during data channel
assignment.
request.

accumulates.
Measurement Point
BSC requests for channel (due to assignment and the channel is used as data channel) but
Unit
Times
Related Features
4-72


Description
data channel handover, including the number of occupation success (C901270073) and
request.

simultaneously.
simultaneously.
simultaneously.
simultaneously.
Measurement Point
BSC completes requesting for channel (due to handover and the channel is used as data
4-73

External)
4-74

Unit
Times
Related Features
4-75

4.50 C900060049 Number of data TCH/H seizure failure

for handover
Description
This counter counts the number of TCH/H channel occupation failure during data channel
handover.
request.

accumulates.
Measurement Point
BSC requests for channel (due to handover and the channel is used as data channel) but
Unit
Times
Related Features
4-76



4.51 C900060050 Number of SAPI3 link establishment

requests on SDCCH (MO-SM)
Description
This counter counts the number of short message link establishments of mobile originating
call on SDCCH. On SDCCH, BSC receives the EST_IND message sent by BTS. If the
layer-3 information in this message is SAPI = 3, this counter increments.
Usage
This counter is used to find out the frequency of SAPI 3 link establishment on SDCCH.
Measurement Point
This counter counts when BSC receives the EST_IND message (SAPI = 3) from BTS. The
measurement point is B1, as shown in Figure 4-87.
4-77

Figure 4-87 Idle-State MO Short Message Flow
Unit
Times
Related Features
ZGB-01-03-003 Short Message Service (SMS)
4-78


requests on SDCCH (MT-SM)
Description
This counter counts the number of short message link establishments of mobile terminating
call on SDCCH. On SDCCH, if BSC receives the DTAP_IND message (SAPI = 3) sent by
MSC and the short message link between BSC and MS is not established, BSC initiates
the link establishment flow, this counter increments.
Usage
This counter is used to find out the frequency of SAPI 3 link establishment request on
SDCCH.
Measurement Point
This counter counts when BSC sends the EST_REQ message (SAPI = 3) to BTS and the
short message link is not established between BSC and MS. The measurement point is
D1, as shown in Figure 4-88.
4-79

Figure 4-88 Idle-State MT Short Message Flow
Unit
Times
Related Features
4.53 C900060052 Number of SDCCH drops due to

handover failure
Description
This counter counts the number of call drops due to handover failure on SDCCH. Call
drop occurs after MS requests for SDCCH successfully. If the problem is due to handover
failure, this counter increments.
4-80

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 sending the inter-cell handover command HOINTER_CMD to
receiving the assignment completion message HOINTER_COM. The external handover
timer indicates the duration from sending the inter-cell external handover command to
receiving the handover completion message.
Usage
This counter is used to find out the frequency of call drop due to handover failure on
SDCCH.
Measurement Point
SDCCH is activated after BSC initiates the handover flow. After that:
l 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 4-89.
Figure 4-89 Call Drop due to T3107 Timeout During Intra-Cell Handover
l If RANCS is in the status of RADIO_APPLY and sends the inter-cell handover

Figure 4-90.
4-81

Figure 4-90 Call Drop due to T3103 Timeout During Inter-Cell Handover
l If RANCS is in the status of RADIO_APPLY and sends the external handover

command, then the external handover timer is started. If RANCS is in the status of
ASSIGN and the external handover timer is timeout, then the counter increments.
Unit
Times
Related Features
4.54 C900060053 Number of SDCCH drops

Description
This counter counts the number of call drops on SDCCH channel due to radio link failure,
LAPD link break, or handover failure. Call drop occurs after MS requests for TCH/H
channel successfully. The counter increments if call drop is due to the above causes.
Usage
This counter is used to find out the frequency of call drop on SDCCH channel due to radio
link failure, LAPD link break, or handover failure.
Measurement Point
This counter increments when call drop occurs on SDCCH channel due to radio link failure,
LAPD link failure, or handover failure.
Unit
Times
4-82

Related Features
4.55 C900060054 Number of TCH/F drops

Description
This counter counts the number of call drops on TCH/F channel due to radio link failure,
Usage
This counter is used to find out the frequency of call drop on TCH/F channel due to radio
Measurement Point
The counter increments when call drop occurs on TCH/F channel due to radio link failure,
Unit
Times
Related Features
4.56 C900060055 Number of TCH/H drops

Description
This counter counts the number of call drops on TCH/H channel due to radio link failure,
Usage
This counter is used to find out the frequency of call drop on TCH/H channel due to radio
Measurement Point
The counter increments when call drop occurs on TCH/H channel due to radio link failure,
4-83

Unit
Times
Related Features
4.57 C900060056 Average number of idle TCH/F with

interference band 1
Description
This counter counts the number of idle TCH/Fs with interference band 1 in the carrier.
Usage
This counter is used to find out the number of idle TCH/Fs with interference band 1.
Measurement Point
This counter counts when querying the database periodically.
Unit
Times
Related Features
ZGO-03-02-001 Idle Channel Measurement

interference band 2
Description
Usage
4-84

Measurement Point
Unit
Times
Related Features

interference band 3
Description
Usage
Measurement Point
Unit
Times
Related Features

interference band 4
Description
Usage
4-85

Measurement Point
Unit
Times
Related Features

interference band 5
Description
Usage
Measurement Point
Unit
Times
Related Features
4.62 C900060061 Average number of idle TCH/H with

interference band 1
Description
This counter counts the number of idle TCH/Hs with interference band 1 in the carrier.
Usage
This counter is used to find out the number of idle TCH/Hs with interference band 1.
4-86

Measurement Point
Unit
Times
Related Features


interference band 2
Description
Usage
Measurement Point
Unit
Times
Related Features

interference band 3
Description
4-87

Usage
Measurement Point
Unit
Times
Related Features

interference band 4
Description
Usage
Measurement Point
Unit
Times
Related Features
4-88


interference band 5
Description
Usage
Measurement Point
Unit
Times
Related Features
4.67 C900060066 Number of samples with UL RQ = 0

Description
This counter counts the number of samples with Uplink (UL) Receiving Quality (RQ) = 0.
After BSC receives the measurement report or preprocessing measurement report, if the
UL RQ = 0, the counter increments.
Usage
This counter is used to count the number of samples with UL RQ = 0.
Measurement Point
The counter increments if UL RQ = 0 in the measurement report or preprocessing
measurement report that BSC receives.
Unit
Times
4-89


Description
This counter counts the number of samples with UL RQ = 1. After BSC receives the
measurement report or preprocessing measurement report, if the UL RQ = 1, the counter
increments.
Usage
Measurement Point
Unit
Times

Description
increments.
Usage
Measurement Point
Unit
Times
4-90


Description
increments.
Usage
Measurement Point
Unit
Times

Description
increments.
Usage
Measurement Point
Unit
Times
4-91


Description
increments.
Usage
Measurement Point
Unit
Times

Description
increments.
Usage
Measurement Point
Unit
Times
4-92


Description
increments.
Usage
Measurement Point
Unit
Times
4.75 C900060074 Number of samples with DL RQ = 0

Description
This counter counts the number of samples with Downlink (DL) RQ = 0. After BSC receives
the measurement report or preprocessing measurement report, if the DL RQ = 0, the
counter increments.
Usage
This counter is used to count the number of samples with DL RQ = 0.
Measurement Point
The counter increments if DL RQ = 0 in the measurement report or preprocessing
Unit
Times
4-93


Description
This counter counts the number of samples with DL RQ = 1. After BSC receives the
measurement report or preprocessing measurement report, if the DL RQ = 1, the counter
increments.
Usage
Measurement Point
Unit
Times

Description
increments.
Usage
Measurement Point
Unit
Times
4-94


Description
increments.
Usage
Measurement Point
Unit
Times

Description
increments.
Usage
Measurement Point
Unit
Times
4-95


Description
increments.
Usage
Measurement Point
Unit
Times

Description
increments.
Usage
Measurement Point
Unit
Times
4-96


Description
increments.
Usage
Measurement Point
Unit
Times
4.83 C900060082 Number of 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 Point
BSC performs handover decision after receiving measurement report on TCH/F channel.
If handover decision succeeds and the handover is due to UL strength, this counter
Figure 4-91 Handover Decision
4-97

Unit
Times
Related Features
ZGB-02-02-002 Basic Handover Decision Criteria

due to DL strength
Description
This counter counts the number of times of handover attempts due to DL receiving strength
too low on TCH/F channel.
Usage
This counter is used to find out the frequency of handover due to DL receiving strength
on TCH/F channel. If the counter's value is too large, it indicates poor DL level on TCH/F
channel.
Measurement Point
If handover decision succeeds and the handover is due to DL strength, this counter
Unit
Times
Related Features
4-98


due to UL quality
Description
This counter counts the number of handover attempts due to UL quality too poor on TCH/F
channel.
Usage
This counter is used to find out the frequency of handover due to UL quality on TCH/F
channel. If the counter's value is too large, it indicates poor UL quality on TCH/F channel.
Measurement Point
If handover decision succeeds and the handover is due to UL quality, this counter
Unit
Times
Related Features

due to DL quality
Description
This counter counts the number of handover attempts due to DL quality too poor on TCH/F
channel.
4-99

Usage
This counter is used to find out the frequency of handover due to DL quality on TCH/F
channel. If the counter's value is too large, it indicates poor DL quality on TCH/F channel.
Measurement Point
If handover decision succeeds and the handover is due to DL quality, this counter
Unit
Times
Related Features

due to UL interference
Description
This counter counts the number of handover attempts due to UL interference too large on
TCH/F channel.
Usage
This counter is used to find out the frequency of handover due to UL interference on TCH/F
channel. If the counter's value is too large, it indicates large UL interference on TCH/F
channel.
4-100

Measurement Point
If handover decision succeeds and the handover is due to UL interference, this counter
Unit
Times
Related Features

due to DL interference
Description
This counter counts the number of handover attempts due to DL interference too large on
TCH/F channel.
Usage
This counter is used to find out the frequency of handover due to DL interference on TCH/F
channel. If the counter's value is too large, it indicates large DL interference on TCH/F
channel.
Measurement Point
If handover decision succeeds and the handover is due to DL interference, this counter
4-101

Unit
Times
Related Features

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 counters value is too large, it indicates that, after MS accesses the
external circle, MS performs handover to the internal circle many times due to good C/I
ratio and the internal circle absorbs the traffic.
Measurement Point
If handover decision succeeds and the handover is due to too large C/I ratio, this counter
4-102

Unit
Times
Related Features

due to bad C/I
Description
This counter counts the number of MS handover attempts due to too low C/I ratio on TCH/F
channel. The handover only occurs during sub-cell configuration; when C/I algorithm is
adopted, MS performs handover from internal circle to external circle.
Usage
This counter is used to find out the frequency of MS handover due to too low C/I ratio on
TCH/F channel. If the counters value is too large, it indicates that, when MS calls within
the internal circle, MS performs handover to the external circle many times due to poor C/I
ratio. Interference within the internal circle is big, and C/I ratio of the internal circle can be
improved by adjusting the carrier power.
Measurement Point
If handover decision succeeds and the handover is due to too low C/I ratio, this counter
4-103

Unit
Times
Related Features

due to PBGT
Description
This counter counts the number of MS handover attempts due to PBGT value on TCH/F
channel. If PBGT value is larger than zero, it indicates the adjacent cell has better radio
environment than the current cell. If the number of times that PBGT value is larger than
zero reaches the threshold, PBGT handover occurs.
Usage
This counter is used to find out the frequency of MS handover due to PBGT value on TCH/F
channel. If the counter's value is too large, it indicates that signal on TCH/F channel within
the current cell is poorer than that in the adjacent cell.
Measurement Point
If handover decision succeeds and the handover is due to PBGT value, this counter
4-104

Unit
Times
Related Features

due to large TA
Description
This counter counts the number of MS handover attempts due to too large TA on TCH/F
channel. Increasing TA indicates that MS is moving away from the current cell. When the
distance reaches a certain value, handover will occur due to too large TA.
Usage
This counter is used to find out the frequency of MS handover due to too large TA on
TCH/F channel. The counter's value reflects the mobility of subscribers in the current cell
to a certain extent.
Measurement Point
If handover decision succeeds and the handover is due to too large TA, this counter
Unit
Times
Related Features
4-105


Description
This counter counts the number of handover attempts due to any other reason beyond the
handover reasons mentioned previously.
Usage
This counter is used to find out the frequency of handover due to any other reason.
Measurement Point
If handover decision succeeds and the handover is due to any other reason beyond the
handover reasons mentioned previously, this counter increments. The measurement point
is A, as shown in Figure 4-101.
Unit
Times
Related Features
4.94 C900060093 Number of 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.
4-106

Usage
This counter is used to find out the frequency of intra-BSC inter-cell outgoing handover
execution. It is one of the parameters that evaluate radio environment, and it reflects the
handover situation.
Measurement Point
During the handover process, if the target cell requests for channel successfully, it
sends the message of radio resource available back to the source cell. The source
cell performs judgment after receiving the message. If the request is due to intra-BSC
inter-cell handover, this counter increments. The measurement point is A, as shown in
Figure 4-102.
Figure 4-102 BSC-Controlled Inter-Cell Outgoing Handover Execution
Unit
Times
Related Features

outgoing handover success
Description
This counter counts the number of successful intra-BSC inter-cell outgoing handovers.
4-107

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 Point
During the handover process, when the source cell receives the handover completion
message from the target cell, it indicates that MS has accessed the target channel and
handover succeeds. In this case, this counter increments. The measurement point is A,
Figure 4-103 BSC-Controlled Inter-Cell Outgoing Handover Success
Unit
Times
Related Features
4.96 C900060095 Number of MSC-controlled outgoing

handover
Description
This counter counts the number of MSC-controlled inter-BSC outgoing handover
executions.
4-108

Usage
This counter is used to find out the frequency of MSC-controlled inter-BSC outgoing
handover execution, and it reflects the handover situation.
Measurement Point
BSC performs handover decision after receiving MS measurement report. If the handover
decision indicates inter-cell handover and the currently attempted cell is a cell under
another BSC, the source BSC sends the handover request message A_HO_RQD to
MSC to trigger inter-BSC handover. If the source BSC receives the handover command
returned from MSC, the counter increments. The measurement point is A, as shown in
Figure 4-104.
Figure 4-104 MSC-Controlled Outgoing Handover Execution
Unit
Times
Related Features

handover success
Description
This counter counts the number of successful MSC-controlled inter-BSC outgoing
handovers.
Usage
This counter is used to find out the frequency of successful MSC-controlled inter-BSC
outgoing handover, and it reflects the handover situation.
4-109

Measurement Point
BSC performs handover decision after receiving MS measurement report. If the handover
decision indicates inter-cell handover and the currently attempted cell is a cell under
another BSC, the source BSC sends the handover request message A_HO_RQD to MSC
to trigger inter-BSC handover. If MS successfully accesses the target cell, the source cell
receives the release command issued by MSC. In this case, this counter increments. The
Figure 4-105 MSC-Controlled Outgoing Handover Success
Unit
Times
Related Features

incoming handover
Description
This counter counts the number of BSC-controlled inter-cell incoming handover
executions.
Usage
This counter is used to find out the frequency of BSC-controlled inter-cell incoming
handover execution. It is one of the parameters that evaluate radio environment, and it
reflects the handover situation.
Measurement Point
If channel activation succeeds in the target cell within BSC and the request is due to
inter-cell handover, the counter increments. The measurement point is A, as shown in
Figure 4-106.
4-110

Figure 4-106 BSC-Controlled Inter-Cell Incoming Handover Execution
Unit
Times
Related Features

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 inter-cell incoming
handover, and it reflects the handover situation.
Measurement Point
When the target cell within BSC receives the handover completion message, if the request
is due to BSC-controlled inter-cell handover, the counter increments. The measurement
Figure 4-107 BSC-Controlled Inter-Cell Incoming Handover Success
4-111

Unit
Times
Related Features
4.100 C900060099 Number of MSC-controlled incoming

handover
Description
This counter counts the number of MSC-controlled inter-BSC incoming handover
executions.
Usage
This counter is used to find out the frequency of MSC-controlled inter-BSC incoming
handover executions. It is one of the parameters that evaluate radio environment, and it
reflects the handover situation.
Measurement Point
After the target cell receives the handover request message issued by MSC, the counter
increments if the channel is allocated and activated successfully. The measurement point
Figure 4-108 MSC-Controlled Incoming Handover Execution
Unit
Times
Related Features
4-112


handover due to forced release
Description
During MSC-controlled inter-BSC incoming handover process, the counter counts the
number of forced release executions due to no available radio resource in the target cell.
Usage
This counter is used to find out the frequency of forced release executions during
MSC-controlled inter-BSC incoming handover process. It reflects the handover situation.
Measurement Point
The target cell receives the radio channel request message. If the request is due
to MSC-controlled inter-BSC incoming handover and the target cell has no available
radio channels, forced release is attempted. If the target cell receives the message of
resource available returned by the forced release instance, the counter increments. The
Figure 4-109 Forced Release Execution
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
4-113


handover due to queue
Description
number of queuing executions due to no available radio resource in the target cell.
Usage
This counter is used to find out the frequency of queuing executions during MSC-controlled
inter-BSC incoming handover process, and it reflects the handover situation.
Measurement Point
The target cell receives the radio channel request message. If the request is due to
MSC-controlled inter-BSC incoming handover and the target cell has no available radio
channels, the target instance is added to the waiting queue. When the target cell receives
the message of resource available, the counter increments. The measurement point is A,
Figure 4-110 Queuing Execution
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
4-114


handover success
Description
This counter counts the number of successful MSC-controlled inter-BSC incoming
handovers.
Usage
incoming handover, and it reflects the handover situation.
Measurement Point
When the target cell receives the handover completion message, if the request is due to
MSC-controlled inter-BSC incoming handover, the counter increments. The measurement
Figure 4-111 MSC-Controlled Incoming Handover Success
Unit
Times
Related Features
4.104 C900060103 Number of incoming handover

from undefined layer (GSM900) to current
layer(GSM1800)
Description
This counter counts the number of incoming handover executions from the undefined layer
cell (GSM900) to the target cell (GSM1800) during BSC-controlled inter-cell handover.
4-115

Usage
This counter is used to find out the frequency of incoming handover executions from the
undefined layer cell (GSM900) to target cell (GSM1800). It reflects the handover situation.
Measurement Point
When the target cell (GSM1800) within BSC receives the channel activation response
message, if the request is due to BSC-controlled inter-cell handover and the source cell
(GSM900) is the undefined layer cell, the counter increments. The measurement point is
Unit
Times
Related Features
ZGO-05-02-010 Multi-band Networking

ZGO-05-02-008 Multi-layer Cell Structure

success from undefined layer(GSM900) to current
layer (GSM1800)
Description
This counter counts the number of successful incoming handover from the undefined layer
Usage
This counter is used to find out the frequency of successful incoming handover from the
undefined layer cell (GSM900) to the target cell (GSM1800). It reflects the handover
situation.
4-116

Measurement Point
When the target cell (GSM1800) within BSC receives the handover completion message,
if the request is due to BSC-controlled inter-cell handover and the source cell (GSM900) is
the undefined layer cell, the counter increments. The measurement point is A, as shown
in Figure 4-113.
Unit
Times
Related Features

from undefined layer (GSM1800) to current layer
(GSM900)
Description
This counter counts the number of incoming handover executions from the undefined layer
Usage
undefined layer cell (GSM1800) to target cell (GSM900). It reflects the handover situation.
Measurement Point
When the target cell (GSM900) within BSC receives the channel activation response
message, if the request is due to BSC-controlled inter-cell handover and the source cell
4-117

(GSM1800) is the undefined layer cell, the counter increments. The measurement point
Unit
Times
Related Features

success from undefined layer(GSM1800) to current
layer(GSM900)
Description
This counter counts the number of successful incoming handover from the undefined layer
Usage
undefined layer cell (GSM1800) to the target cell (GSM900). It reflects the handover
situation.
Measurement Point
When the target cell (GSM900) within BSC receives the handover completion message, if
the request is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is
the undefined layer cell, the counter increments. The measurement point is A, as shown
in Figure 4-115.
4-118

Unit
Times
Related Features
4.108 C900060107 Number of incoming handover from

the same layer GSM900 to GSM1800
Description
This counter counts the number of incoming handover executions from the cell (GSM900)
to the target cell (GSM1800) in the same layer during BSC-controlled inter-cell handover.
Usage
cell (GSM900) to the target cell (GSM1800) in the same layer. It reflects the handover
situation.
Measurement Point
When the target cell (GSM1800) receives the channel activation response message, if the
request is due to BSC-controlled inter-cell handover and the source cell (GSM900) is in
the same layer, the counter increments. The measurement point is A, as shown in Figure
4-116.
4-119

Unit
Times
Related Features


success from the same layer GSM900 to GSM1800
Description
This counter counts the number of successful incoming handovers from the cell (GSM900)
Usage
situation.
Measurement Point
When the target cell (GSM1800) receives the handover completion message, if the request
is due to BSC-controlled inter-cell handover and the source cell (GSM900) is in the same
layer, the counter increments. The measurement point is A, as shown in Figure 4-117.
4-120

Unit
Times
Related Features

GSM900 to GSM1800 from the upper layer
Description
This counter counts the number of incoming handover executions from the upper layer cell
(GSM900) to the target cell (GSM1800) during BSC-controlled inter-cell handover.
Usage
upper layer cell (GSM900) to the target cell (GSM1800). It reflects the handover situation.
Measurement Point
the upper layer, the counter increments. The measurement point is A, as shown in Figure
4-118.
4-121

Unit
Times
Related Features


success from GSM900 to GSM1800 in the upper
layer
Description
This counter counts the number of successful incoming handovers from the upper layer
Usage
Measurement Point
is due to BSC-controlled inter-cell handover and the source cell (GSM900) is in the upper
4-122

Unit
Times
Related Features

GSM900 to GSM1800 in the lower layer
Description
This counter counts the number of incoming handover executions from the lower layer cell
Usage
lower layer cell (GSM900) to the target cell (GSM1800). It reflects the handover situation.
Measurement Point
the lower layer, the counter increments. The measurement point is A, as shown in Figure
4-120.
4-123

Unit
Times
Related Features


success from GSM900 to GSM1800 in the lower
layer
Description
This counter counts the number of successful incoming handovers from the lower layer
Usage
Measurement Point
is due to BSC-controlled inter-cell handover and the source cell (GSM900) is in the lower
4-124

Unit
Times
Related Features

GSM1800 to GSM900 from the same layer
Description
This counter counts the number of incoming handover executions from the cell (GSM1800)
Usage
situation.
Measurement Point
the same layer, the counter increments. The measurement point is A, as shown in Figure
4-122.
4-125

Unit
Times
Related Features


success from GSM1800 to GSM900 from the same
layer
Description
This counter counts the number of successful incoming handovers from the cell
(GSM1800) to the target cell (GSM900) in the same layer during BSC-controlled inter-cell
handover.
Usage
situation.
Measurement Point
is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is in the same
4-126

Unit
Times
Related Features

GSM1800 to GSM900 from the upper layer
Description
This counter counts the number of incoming handover executions from the upper layer cell
Usage
Measurement Point
the upper layer, the counter increments. The measurement point is A, as shown in Figure
4-124.
4-127

Unit
Times
Related Features


success from GSM1800 to GSM900 from the upper
layer
Description
This counter counts the number of successful incoming handovers from the upper layer
Usage
Measurement Point
is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is in the upper
4-128

Unit
Times
Related Features

GSM1800 to GSM900 from the lower layer
Description
This counter counts the number of incoming handover executions from the lower layer cell
Usage
Measurement Point
the lower layer, the counter increments. The measurement point is A, as shown in Figure
4-126.
4-129

Unit
Times
Related Features


success from GSM1800 to GSM900 from the lower
layer
Description
This counter counts the number of successful incoming handovers from the lower layer
Usage
Measurement Point
is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is in the lower
4-130

Unit
Times
Related Features
4.120 C900060119 Number of 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 message 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 Point
During the handover process, if the target channel request succeeds, the message of
radio resource available is returned to BSC. BSC then performs judgment after receiving
the message. If the request is due to intra-cell handover, this counter increments. The
4-131

Figure 4-128 Intra-Cell Handover Execution
Unit
Times
Related Features

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 Point
During the intra-cell handover process, if the source instance receives the handover
completion message returned by the target instance, it indicates MS accesses the target
channel and handover succeeds. In this case, this counter increments. The measurement
Figure 4-129 Intra-Cell Handover Success
4-132

Unit
Times
Related Features
4.122 C900060121 Maximum number of busy TCH/H

Description
This counter counts the maximum number of occupied TCH/Hs in a cell during a
measurement period.
The system records the TCH/Hs occupied in the cell. If a TCH/H is successfully occupied,
the number of occupied TCH/Hs increases by 1; if a TCH/H is released, the number of
occupied TCH/Hs decreases by 1. After a TCH/H is occupied, before a TCH/H is released,
or when the system reports the periodical measurement data, if this counter's value is less
than the number of actual occupied TCH/Hs, this counter's value will be replaced by the
actual number of occupied TCH/Hs.
In consideration of the TCH/H channel occupation situation in the last measurement period,
the number of occupied TCH/Hs is updated before the release of a TCH/H.
Usage
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 Point
The counter counts at the following three time points:
l After the TCH/H is occupied successfully, if the maximum number of busy TCH/Hs
exceeds the counter's recorded value;
l Before the TCH/H is released, if the maximum number of busy TCH/Hs exceeds
the counter's recorded value;
l When the system reports the periodical measurement data, if the maximum number
of busy TCH/Hs exceeds the counter's recorded value.
4-133

Figure 4-130 Reporting Measurement Data
Unit
Times
Related Features
4.123 C900060122 Average number of available SDCCH

Description
This counter counts the number of SDCCHs which can be assigned normally, including
idle SDCCH and occupied SDCCH.
Usage
This counter is used to find out the number of available SDCCHs in the current cell.
Measurement Point
Query the database when periodic measurement data is reported to get the value of the
counter. The measurement point is A, as shown in Figure 4-131.
4-134

Unit
Times
Related Features
4.124 C900060123 Average number of unavailable

SDCCH
Description
This counter counts the number of SDCCHs that can not be assigned normally, including
those SDCCHs blocked due to various reasons.
Usage
This counter is used to find out the number of unavailable SDCCHs to facilitate
troubleshooting.
Measurement Point
Unit
Times
Related Features
4-135

4.125 C900060124 SDCCH busy time

Description
This counter counts the busy time of SDCCHs, which reflects the traffic volume of SDCCH.
Usage
This counter is used to find out the busy level and the average occupation time of the
signaling channel. It can be used as a reference for judging whether to increase the number
of SDCCHs.
Measurement Point
l When an SDCCH is acquired successfully, this counter calculates time and
accumulates.
l When an SDCCH is released, this counter calculates time and accumulates.
l When the system reports the periodical measurement data, this counter calculates
time and accumulates.
The measurement formula is as follows:

l Measurement value = (Current time Last measurement time point) Number of
MSs that are occupying the channels
l The reported measurement value is accumulated by each measurement value.
After each accumulation, the last measurement time point is updated to the current
time. If an SDCCH is acquired successfully, Number of MSs that are occupying
the channels increases by 1; if an SDCCH is released, Number of MSs that are
occupying the channels decreases by 1.
Unit
Second
4-136

4.126 C900060125 Average number of available radio

channel
Description
This counter counts the number of radio channel which can be assigned normally, including
idle radio channel and occupied radio channel.
Usage
This counter is used to find out the number of available radio channel in the current cell. It
helps understand the current resource usage situation of the cell.
Measurement Point
Unit
Times
Related Features
ZGO-04-04-002 Intelligent TRX Shutdown
4.127 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.
4-137

Usage
This counter is used to find out the number of unavailable radio channels in the current
cell. It helps understand the current resource usage situation of the cell.
Measurement Point
Unit
Times
Related Features
4.128 C900060127 TCH/H busy time

Description
This counter counts the busy time of TCH/Hs, which reflects the traffic volume of TCH/H.
Usage
This counter is used to find out the busy level and the average occupation time of TCH/H.
It can be used as a reference for judging whether to increase the number of TCH/Hs.
Measurement Point
l When a TCH/H is acquired successfully, this counter calculates time and

accumulates.
l When a TCH/H is released, this counter calculates time and accumulates.
4-138


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
Unit
Second
Related Features
4.129 C900060128 Maximum number of busy TCH/F

Description
This counter counts the maximum number of occupied TCH/Fs in a cell during a
measurement period.
The system records the TCH/Fs occupied in the cell. If a TCH/F is successfully occupied,
the number of occupied TCH/Fs increases by 1; if a TCH/F is released, the number of
occupied TCH/Hs decreases by 1. After a TCH/F is occupied, before a TCH/F is released,
or when the system reports the periodical measurement data, if this counter's value is less
than the number of actual occupied TCH/Fs, this counter's value will be replaced by the
actual number of occupied TCH/Fs.
In consideration of the TCH/F channel occupation situation in the last measurement period,
the number of occupied TCH/Fs is updated before the release of a TCH/F.
4-139

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.
Measurement Point
l After the TCH/F is occupied successfully, if the maximum number of busy TCH/Fs
exceeds the counters recorded value;
l Before the TCH/F is released, if the maximum number of busy TCH/Hs exceeds
the counters recorded value;
l When the system reports the periodical measurement data, if the maximum number
of busy TCH/Fs exceeds the counter's recorded value.
Unit
Times
Related Features
4.130 C900060129 TCH/F busy time

Description
This counter counts the busy time of TCH/Fs, which reflects the traffic volume of TCH/F.
Usage
This counter is used to find out the busy level and the average occupation time of TCH/F.
It can be used as a reference for judging whether to increase the number of TCH/Fs.
4-140

Measurement Point
l When a TCH/F is acquired successfully, this counter calculates time and
accumulates.
l When a TCH/F is released, this counter calculates time and accumulates.

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
Unit
Second
Related Features
4.131 C900060130 Number of healthy TRXs

Description
This counter counts the number of the TRXs that can be used normally.
4-141

Usage
This counter is used to find out the number of available TRXs and resource usage in the
current cell to facilitate troubleshooting.
Measurement Point
Unit
Times
4.132 C900060131 Number of CM service requests of

MOC
Description
This counter counts the number of accesses due to CM SERVICE REQ of MOC. After
BSC receives the EST_IND message, if the access cause in the layer-3 information in this
message is CM SERVICE REQ, this counter increments.
Usage
This counter is used to find out the frequency of the access due to CM SERVICE REQ of
MOC.
Measurement Point
4-142

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 Point
This counter counts when BSC receives the EST_CONF message (SAPI = 3) from BTS.
The measurement point is D2, as shown in Figure 4-141.
4-143

Figure 4-141 Idle-State MT Short Message Flow
Unit
Times
Related Features
4.134 C900060133 Number of 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.
4-144

Usage
This counter is used to find out the number of available SDCCH in the current cell to
facilitate eliminating fault in the cell.
Measurement Point
Unit
Times
Related Features
4.135 C900060134 Number of 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.
Measurement Point
4-145

Unit
Times
Related Features

4.136 C900060135 Number of signaling TCH/H

assignment failure
Description
This counter counts the number of failing to assign TCH/H channel as a signaling channel.
Usage
After BSC responds to the channel request message to allocate and occupy TCH/H
successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. If BSC
does not receive the MS access notification within a certain time, this assignment fails.
Measurement Point
For immediate assignment, this counter counts when BSC receives incorrect EST_IND
message or T3101 is timeout. The measurement point is A3, as shown in Figure 4-144.
4-146

Unit
Times
Related Features
4.137 C900060136 Number of MOC access attempts

Description
This counter counts the number of channel requests due to Mobile Originated Call
(MOC). When MS sends the CHL_REQ message through BTS to BSC to request for
radio channel, if TA does not exceed the cell range and the access cause is MOC, this
counter increments.
Usage
This counter is used to find out the frequency of channel requests due to the access cause
MOC.
Measurement Point
This counter counts when MS requests for channel from BSC and TA does not exceed the
cell range. The measurement point is A1, as shown in Figure 4-145.
4-147

Unit
Times
4.138 C900060137 Number of wireless access due to

paging responses
Description
This counter counts the number of accesses due to paging responses. After BSC receives
the EST_IND message, if the access cause in the layer-3 information in this message is
paging responses, this counter increments.
Usage
This counter is used to find out the frequency of the access due to paging responses.
Measurement Point
4-148

Unit
Times
Related Features
ZGB-02-01-001 Paging

due to BTS connection failure for assignment
(speech 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).
channel successfully, BSC sends the CMM connection request to BTS. If BTS connection
fails due to receiving CMM connection failure message, incorrect CMM connection
response message, or timer timeout, this counter accumulates.
Measurement Point
BSC uses TCH/F for assignment, but the problem such as receiving connection failure
message, incorrect connection response message, or timer timeout occurs during CMM
connection process. The measurement point is B2, as shown in Figure 4-147.
4-149

Figure 4-147 Common Assignment Flow 3 (TC Is Internal)
Unit
Times
Related Features

due to BIU connection failure for assignment
(speech version1)
Description
This counter counts the number of failing to allocate TCH/F channel due to BIU connection
channel successfully, BSC sends the BIU connection request to BIPB. If BIU connection
fails due to receiving BIU connection failure message, incorrect BIU connection response
message, or timer timeout, this counter accumulates.
Measurement Point
message, incorrect connection response message, or timer timeout occurs during BIU
4-150

Unit
Times
Related Features

due to TCU connection failure for assignment
(speech version1)
Description
This counter counts the number of failing to allocate TCH/F channel due to TCU connection
channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection
fails due to receiving TCU connection failure message, incorrect TCU connection
Measurement Point
message, incorrect connection response message, or timer timeout occurs during TCU
4-151

Unit
Times
Related Features

(speech version2)
Description
activation failure when assigning speech channel (using speech version 2).
channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If
the channel activation fails due to receiving channel activation failure message, incorrect
channel activation response message, T9103 timeout, channel instance being released
or channel being released forcibly, this counter accumulates.
Measurement Point
BSC activates TCH/F as voice channel (using speech version 2) for assignment, but the
problem such as receiving channel activation failure message, incorrect channel activation
response message, T9103 timeout, channel instance being released, or channel being
forcibly released occurs. The measurement point is B3, as shown in Figure 4-150.
4-152

Unit
Times
Related Features

(speech version2)
Description
Measurement Point
4-153

Unit
Times
Related Features

(speech version2)
Description
Measurement Point
4-154

Unit
Times
Related Features

(speech version2)
Description
Measurement Point
4-155

Unit
Times
Related Features

(speech version3)
Description
Measurement Point
4-156

Unit
Times
Related Features

(speech version3)
Description
Measurement Point
4-157

Unit
Times
Related Features

(speech version3)
Description
Measurement Point
4-158

Unit
Times
Related Features

failure due to BTS connection failure for
assignment)
Description
failure when assigning data channel.
response message or timer timeout, this counter accumulates.
Measurement Point
message, incorrect connection response message or timer timeout occurs during CMM
4-159

Unit
Times
Related Features

failure due to BIU connection failure for assignment
Description
message or timer timeout, this counter accumulates.
Measurement Point
BSC uses TCH/F for assignment, but receives connection failure message, incorrect
connection response message or timer timeout during BIU connection process. The
4-160

Unit
Times
Related Features

failure due to TCU connection failure for
assignment
Description
Measurement Point
BSC uses TCH/F for assignment, but receiving connection failure message, incorrect
connection response message or timer timeout during TCU connection process. The
4-161

Unit
Times
Related Features
4.152 C900060151 Number of voice TCH/H drops due

to handover failure
Description
This counter counts the number of call drops due to handover failure on TCH/H voice
channel. Call drop occurs after MS requests for TCH/H voice channel successfully. If the
problem is due to handover failure, the counter increments.
Usage
This counter is used to find out the frequency of call drop due to handover failure on TCH/H
voice channel.
Measurement Point
TCH/H voice channel is activated after BSC initiates the handover flow. After that:

Figure 4-160.
4-162


Figure 4-161.

4-163

Figure 4-162 Call Drop due to Inter-BSC Handover Failure
Unit
Times
Related Features
4.153 C900060152 Number of Abis interface paging

command messages
Description
This counter counts the number of paging command messages from A-interface. These
messages are part of Abis interface messages sent from BSC.
Usage
This counter is used to find out the frequency of transmitting paging command messages
at Abis interface. These messages are from A-interface.
Measurement Point
When BSC sends ABIS_INTER_PAGING_CMD message to BTS, this counter increments.
4-164

Figure 4-163 Measurement Point of Number of Abis Interface Messages Sent to BTS
from BSC
Unit
Times
Related Features
4.154 C900060153 Number of Abis CS paging

messages
Description
This counter counts the number of CS paging command messages from Gb interface.
These messages are part of Abis interface messages sent from BSC.
Usage
This counter is used to find out the frequency of transmitting CS paging command
messages at Abis interface. These messages are from Gb interface.
Measurement Point
When BSC sends ABIS_INTER_CSPAGING_CMD message to BTS, this counter
from BSC
Unit
Times
4-165

Related Features
4.155 C900060154 Number of Abis PS paging

messages
Description
This counter counts the number of PS paging command messages from Gb interface.
These messages are part of Abis interface messages sent from BSC.
Usage
This counter is used to find out the frequency of transmitting PS paging command
messages at Abis interface. These messages are from Gb interface.
Measurement Point
When BSC sends ABIS_INTER_PSPAGING_CMD message to BTS, this counter
from BSC
Unit
Times
Related Features
4.156 C900060155 Number of available defined TCH/H

Description
of available TCH/H channel configured by OMCR in the current cell.
4-166

Usage
This counter is used to find out the number of available TCH/H channel in the current cell
to eliminate the fault in the cell.
Measurement Point
Unit
Times
Related Features
4.157 C900060156 Number of TCH/F allocation

handover(speech version1)
Description
This counter counts the number of failing to allocate TCH/F channel due to channel
activation failure during voice channel handover (using speech version 1).
channel successfully, if the connection succeeds, BSC sends the channel activation
message CHL_ACT to BTS to activate this TCH/F. If channel activation fails due to
receiving channel activation failure message, incorrect channel activation response
4-167

message, T9103 being timeout, channel instance being released or channel being forcibly
released, this counter accumulates.
Measurement Point
BSC activates TCH/F channel as voice channel due to handover, but receives channel
activation failure message, incorrect channel activation response message, T9103
being timeout, channel instance being released, or channel being forcibly released. The
measurement point is C3 as shown in Figure 4-167 and D3 as shown in Figure 4-168.
Unit
Times
Related Features
4-168


due to BTS connection failure for handover (speech
version1)
Description
failure during voice channel handover (using speech version 1).
Measurement Point
BSC uses TCH/F channel for handover, but receives connection failure message, incorrect
connection response message, or timer timeout during CMM connection process. The
Unit
Times
4-169

Related Features

due to BIU connection failure for handover (speech
version1)
Description
Measurement Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect
connection response message, or timer timeout during BIU connection process. The
4-170

Unit
Times
Related Features

due to TCU connection failure for handover
(speech version1)
Description
Measurement Point
connection response message, or timer timeout during TCU connection process. The
4-171

Unit
Times
Related Features


handover(speech version2)
Description
Measurement Point
4-172

Unit
Times
Related Features

version2)
Description
4-173

Measurement Point
Unit
Times
Related Features

version2)
Description
4-174

Measurement Point
Unit
Times
Related Features
4-175


(speech version2)
Description
Measurement Point
Unit
Times
4-176

Related Features

due to channel activation failure for handover
(speech version3)
Description
Measurement Point
4-177

Unit
Times
Related Features

version3)
Description
Measurement Point
4-178

Unit
Times
Related Features

version3)
Description
4-179

Measurement Point
Unit
Times
Related Features

(speech version3)
Description
4-180

Measurement Point
Unit
Times
Related Features
4-181

4.169 C900060168 Number of Voice TCH/F handover

success
Description
This counter counts the number of successful TCH/F channel handover during voice
channel handover.
When BSC detects the successful handover message sent by MS on newly-allocated

TCH/F channel, this counter accumulates. The ASS_COM message indicates successful
intra-cell handover, and the HO_COM message indicates successful inter-cell handover
and external handover.
For intra-cell handover and inter-cell handover, the counter accumulates on source
instances. For external handover, the counter accumulates on target instances because
the source instance is not under this BSC.
Measurement Point
The counter counts when BSC receives the ASS_COM/HO_COM message. The
measurement point is C4 as shown in Figure 4-191 and Figure 4-192, and D4 as shown
in Figure 4-193 and Figure 4-194.
4-182

Figure 4-192 Internal Handover Flow (Intra-Cell Handover, Channel Type Changed,
TC Is External)
4-183

Unit
Times
Related Features

handover
Description
activation failure during data channel handover.
message CHL_ACT to BTS to activate this TCH/F. If the channel activation fails due
to receiving channel activation failure message, incorrect channel activation response
forcibly released, this counter accumulates.
Measurement Point
BSC activates TCH/F as data channel for handover, but receives channel activation failure
instance being released, or channel being forcibly released. The measurement point is C3
as shown in Figure 4-195 and D3 as shown in Figure 4-196.
4-184

Unit
Times
Related Features

failure due to BTS connection failure for handover
Description
failure during data channel handover.
4-185

Measurement Point
Unit
Times
Related Features

failure due to BIU connection failure for handover
Description
4-186

Measurement Point
Unit
Times
Related Features
4-187


failure due to TCU connection failure for handover
Description
Measurement Point
Unit
Times
Related Features
4-188


4.174 C900060173 Number of data TCH/F handover

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

Measurement Point
4-189

TC Is External)
4-190

Unit
Times
Related Features

allocation failure for assignment
Description
This counter counts the number of TCH/H channel allocation failures during signaling
channel assignment.
channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H
channel.
channel being released forcibly, this counter accumulates.
Measurement Point
BSC activates TCH/H channel due to assignment and uses it as signaling channel,
forcibly released. The measurement point is A2, as shown in Figure 4-207.
4-191

Figure 4-207 Immediate Assignment Allocation Failure Flow 2
Unit
Times
Related Features
4.176 C900060175 Number of TCH/H allocation failure

(speech version1)
Description
This counter counts the number of TCH/H channel allocation failure due to channel
activation failure when assigning voice channel (using speech version 1).
channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. If
Measurement Point
BSC activates TCH/H as voice channel (using speech version 1) for assignment, but the
4-192

Unit
Times
Related Features

(speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection
Measurement Point
BSC uses TCH/H for assignment, but the problem such as receiving connection failure
4-193

Unit
Times
Related Features

(speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to BIU connection
Measurement Point
4-194

Unit
Times
Related Features

(speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection
Measurement Point
4-195

Unit
Times
Related Features

(speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to channel
message CHL_ACT to BTS to activate this TCH/H. If channel activation fails due to
Measurement Point
BSC activates TCH/H channel as voice channel due to handover, but receives channel
4-196

Unit
Times
Related Features

version1)
Description
4-197

Measurement Point
BSC uses TCH/H channel for handover, but receives connection failure message, incorrect
Unit
Times
Related Features

version1)
Description
4-198

Measurement Point
BSC uses TCH/H for handover, but receives connection failure message, incorrect
Unit
Times
Related Features
4-199


(speech version1)
Description
Measurement Point
Unit
Times
4-200

Related Features

(speech version2)
Description
Measurement Point
Unit
Times
4-201

Related Features

(speech version2)
Description
Measurement Point
Unit
Times
Related Features
4-202


(speech version2)
Description
Measurement Point
Unit
Times
Related Features
4-203


(speech version2)
Description
Measurement Point
Unit
Times
Related Features
4-204


(speech version2)
Description
Measurement Point
4-205

Unit
Times
Related Features

version2)
Description
Measurement Point
4-206

Unit
Times
Related Features


version2)
Description
Measurement Point
4-207

Unit
Times
Related Features

(speech version2)
Description
4-208

Measurement Point
Unit
Times
Related Features
4-209


(speech version3)
Description
Measurement Point
Unit
Times
Related Features
4-210


(speech version3)
Description
Measurement Point
Unit
Times
Related Features
4-211


(speech version3)
Description
Measurement Point
Unit
Times
Related Features
4-212


(speech version3)
Description
Measurement Point
Unit
Times
Related Features
4-213


(speech version3)
Description
Measurement Point
4-214

Unit
Times
Related Features

version3)
Description
Measurement Point
4-215

Unit
Times
Related Features


version3)
Description
Measurement Point
4-216

Unit
Times
Related Features

(speech version3)
Description
4-217

Measurement Point
Unit
Times
Related Features
4.200 C900060199 Number of Voice TCH/H assignment

success
Description
This counter counts the number of successful assignments of TCH/H as voice channel.
4-218

After BSC responds the channel request message to allocate and occupy TCH/H channel
successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. For
assignment from A-interface, after BSC receives the assignment success message, the
Measurement Point
and Figure 4-245.
Unit
Times
4-219

Related Features

failure
Description
This counter counts the number of failing to assign TCH/H channel as voice channel.
channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H.
fails.
Measurement Point
Unit
Times
Related Features
4-220

4.202 C900060201 Number of Voice TCH/H handover

success
Description
This counter counts the number of successful TCH/H channel handover during voice
channel handover.

Measurement Point
4-221

TC Is External)
4-222

Unit
Times
Related Features
4.203 C900060202 Number of data TCH/H allocation

assignment
Description
activation failure during data channel assignment.
After BSC responds the channel request message to allocate and 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
instance being released or channel being forcibly released, this counter accumulates.
Measurement Point
BSC activates TCH/H channel due to assignment and uses the channel as data channel,
4-223

message, T9103 being timeout, channel instance being released, or channel being forcibly
released. The measurement point is B3, as shown in Figure 4-251.
Unit
Times
Related Features

failure due to BTS connection failure for
assignment
Description
Measurement Point
message, incorrect connection response message or timer timeout occurs during CMM
4-224

Unit
Times
Related Features

failure due to BIU connection failure for assignment
Description
Measurement Point
BSC uses TCH/H for assignment, but receives connection failure message, incorrect
connection response message or timer timeout during BIU connection process. The
4-225

Unit
Times
Related Features

failure due to TCU connection failure for
assignment
Description
Measurement Point
BSC uses TCH/H for assignment, but receiving connection failure message, incorrect
connection response message or timer timeout during TCU connection process. The
4-226

Unit
Times
Related Features

handover
Description
activation failure during data channel handover.
message CHL_ACT to BTS to activate this TCH/H. If the channel activation fails due
to receiving channel activation failure message, incorrect channel activation response
forcibly released, this counter accumulates.
Measurement Point
BSC activates TCH/H as data channel for handover, but receives channel activation failure
instance being released, or channel being forcibly released. The measurement point is C3
as shown in Figure 4-255 and D3 as shown in Figure 4-256.
4-227

Unit
Times
Related Features

failure due to BTS connection failure for handover
Description
4-228

Measurement Point
Unit
Times
Related Features

failure due to BIU connection failure for handover
Description
4-229

Measurement Point
Unit
Times
Related Features
4-230


failure due to TCU connection failure for handover
Description
Measurement Point
Unit
Times
Related Features
4-231


4.211 C900060210 Number of data TCH/H assignment

success
Description
This counter counts the number of successful assignments of TCH/H as data channel.
For assignment from A-interface, after BSC receives the assignment success message,
Measurement Point
and Figure 4-264.
4-232

Unit
Times
Related Features

failure
Description
This counter counts the number of failing to assign TCH/H channel as data channel.
fails.
Measurement Point
4-233

Unit
Times
Related Features
4.213 C900060212 Number of data TCH/H handover

success
Description
This counter counts the number of successful TCH/H channel handover during data
channel handover.
TCH/H channel, this counter accumulates. The ASS_COM message indicates successful
Measurement Point
4-234

TC Is External)
4-235

Unit
Times
Related Features
4-236

4.214 C900060213 Number of BSC-controlled incoming

handover due to forced release
Description
During BSC-controlled inter-cell incoming handover process, the counter counts the
number of forced release executions due to no available radio resource in the target cell.
Usage
This counter is used to find out the frequency of forced release execution during
BSC-controlled inter-cell incoming handover process. It reflects the status of the handover
flow.
Measurement Point
The target cell within BSC receives the radio channel request message. If the request is
due to BSC-controlled inter-cell incoming handover and the target cell has no available
radio channels, forced release is performed. When the target cell receives the message
of resource available returned by the forced release instance, the counter increments. The
Figure 4-270 Forced Release Execution
Unit
Times
4-237

Related Features
ZGO-01-03-001 eMLPP

handover due to queues
Description
number of queuing executions due to no available radio resource in the target cell.
Usage
This counter is used to find out the frequency of queuing execution during BSC-controlled
inter-cell incoming handover process. It reflects the status of the handover flow.
Measurement Point
radio channels, the target instance is added to the waiting queue. When the target cell
receives the message of resource available, the counter increments. The measurement
4-238

Figure 4-271 Queuing Execution
Unit
Times
Related Features
ZGO-01-03-001 eMLPP

handover due to forced handover
Description
number of forced handover executions due to no available radio resource in the target
cell.
4-239

Usage
This counter is used to find out the frequency of forced handover execution during
BSC-controlled inter-cell incoming handover process. It reflects the status of the handover
flow.
Measurement Point
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
Figure 4-272 Forced Handover Execution
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
4-240


handover due to forced handover
Description
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 Point
The target cell receives the radio channel request message. If the request is due to
MSC-controlled inter-BSC incoming handover and the target cell has no available radio
channels, the forced handover message is sent to the forced handover instance and the
target instance is added to the waiting queue. When the target cell receives the message
of resource available, the counter increments. The measurement point is A, as shown in
Figure 4-273.
Figure 4-273 Forced Handover Execution
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
4-241

4.218 C900060217 Number of unavailable defined

TCH/H
Description
of unavailable TCH/H channel configured by OMCR in the current cell.
Usage
This counter is used to find out the number of unavailable TCH/H channel in the current
cell to facilitate eliminating the fault.
Measurement Point
Unit
Times
Related Features
4-242


TCH/F
Description
iBSC supports the function of full dynamic wireless channel. This counter counts the
number of unavailable TCH/F channel configured by OMCR in the current cell.
Usage
This counter is used to find out the number of unavailable TCH/F channel in the current
cell to facilitate eliminating the fault.
Measurement Point
Unit
Times
Related Features
4-243

4.220 C900060219 Number of signaling TCH/F drops

due to handover failure
Description
This counter counts the number of call drops due to handover failure on TCH/F signaling
channel. Call drop occurs after MS requests for TCH/F signaling channel successfully. If
the problem is due to handover failure, the counter increments.
Usage
This counter is used to find out the frequency of call drop due to handover failure on TCH/F
signaling channel.
Measurement Point
TCH/F signaling channel is activated after BSC initiates the handover flow. After that:
Figure 4-276.

Figure 4-277.
4-244


Unit
Times
Related Features
4-245

4.221 C900060220 Number of voice TCH/F drops due

to handover failure
Description
This counter counts the number of call drops on TCH/F voice channel due to handover
failure. Call drop occurs after MS requests for TCH/F voice channel successfully. The
counter increments if call drop is due to handover failure.
Usage
This counter is used to find out the frequency of call drop on TCH/F voice channel due to
handover failure.
Measurement Point
TCH/F voice channel is activated after BSC initiates the handover flow. After that:
Figure 4-279.

Figure 4-280.
4-246


Unit
Times
Related Features
4-247

4.222 C900060221 Number of data TCH/F drops due

to handover failure
Description
This counter counts the number of call drops on TCH/F data channel due to handover
failure. Call drop occurs after MS requests for TCH/F data channel successfully. The
counter increments if call drop is due to handover failure.
Usage
This counter is used to find out the frequency of call drop on TCH/F data channel due to
handover failure.
Measurement Point
TCH/F data channel is activated after BSC initiates the handover flow. After that:
Figure 4-282.

Figure 4-283.
4-248


Unit
Times
Related Features
4-249

4.223 C900060222 Number of signaling TCH/H drops

due to handover failure
Description
This counter counts the number of call drops due to handover failure on TCH/H signaling
channel. Call drop occurs after MS requests for TCH/H signaling channel successfully. If
the problem is due to handover failure, the counter increments.
Usage
signaling channel.
Measurement Point
TCH/H signaling channel is activated after BSC initiates the handover flow. After that:
Figure 4-285.

Figure 4-286.
4-250


Unit
Times
Related Features
4-251

4.224 C900060223 Number of data TCH/H drops due

to handover failure
Description
This counter counts the number of call drops due to handover failure on TCH/H data
channel. Call drop occurs after MS requests for TCH/H data channel successfully. If the
problem is due to handover failure, the counter increments.
Usage
data channel.
Measurement Point
TCH/H data channel is activated after BSC initiates the handover flow. After that:
Figure 4-288.

Figure 4-289.
4-252


Unit
Times
Related Features
4-253

4.225 C900060224 Number of TCH/H handover attempts

due to UL strength
Description
This counter counts the number of handover attempts due to UL receiving strength too low
on TCH/H channel.
Usage
This counter is used to find out the frequency of handover due to UL receiving strength
on TCH/H channel. If the counter's value is too large, it indicates poor UL level on TCH/H
channel.
Measurement Point
BSC performs handover decision after receiving measurement report on TCH/H channel.
If handover decision succeeds and the handover is due to UL strength, this counter
Unit
Times
Related Features
4-254


due to DL strength
Description
This counter counts the number of handover attempts due to DL receiving strength too low
on TCH/H channel.
Usage
This counter is used to find out the frequency of handover due to DL receiving strength
on TCH/H channel. If the counter's value is too large, it indicates poor DL level on TCH/H
channel.
Measurement Point
If handover decision succeeds and the handover is due to DL strength, this counter
Unit
Times
Related Features
4-255


due to UL quality
Description
This counter counts the number of handover attempts due to UL quality too poor on TCH/H
channel.
Usage
This counter is used to find out the frequency of handover due to UL quality on TCH/H
channel. If the counters value is too large, it indicates poor UL quality on TCH/H channel.
Measurement Point
If handover decision succeeds and the handover is due to UL quality, this counter
Unit
Times
Related Features

due to DL quality
Description
This counter counts the number of handover attempts due to DL quality too poor on TCH/H
channel.
4-256

Usage
This counter is used to find out the frequency of handover due to DL quality on TCH/H
channel. If the counters value is too large, it indicates poor DL quality on TCH/H channel.
Measurement Point
If handover decision succeeds and the handover is due to DL quality, this counter
Unit
Times
Related Features

Description
This counter counts the number of handover attempts due to UL interference too large on
TCH/H channel.
Usage
This counter is used to find out the frequency of handover due to UL interference on TCH/H
channel. If the counter's value is too large, it indicates large UL interference on TCH/H
channel.
4-257

Measurement Point
If handover decision succeeds and the handover is due to UL interference, this counter
Unit
Times
Related Features

Description
This counter counts the number of handover attempts due to DL interference too large on
TCH/H channel.
Usage
This counter is used to find out the frequency of handover due to DL interference on TCH/H
channel. If the counter's value is too large, it indicates large DL interference on TCH/H
channel.
Measurement Point
If handover decision succeeds and the handover is due to DL interference, this counter
4-258

Unit
Times
Related Features

4.231 C900060230 Number of TCH/H inter-subcell

handover attempts due to good C/I
Description
This counter counts the number of MS handover attempts due to too large C/I ratio on
TCH/H channel. The handover only occurs during sub-cell configuration and when C/I
algorithm is adopted; MS performs handover from external circle to internal circle.
Usage
This counter is used to find out the frequency of MS handover due to too large C/I ratio on
TCH/H channel. If the counter's value is too large, it indicates that, after MS accesses the
external circle, MS performs handover to the internal circle many times due to good C/I
ratio and the internal circle absorbs the traffic.
Measurement Point
If handover decision succeeds and the handover is due to too large C/I ratio, this counter
4-259

Unit
Times
Related Features
4.232 C900060231 Number of TCH/H inter-subcell

handover attempts due to bad C/I
Description
This counter counts the number of MS handover attempts due to too low C/I ratio on TCH/H
channel. The handover only occurs during sub-cell configuration and when C/I algorithm
is adopted; MS performs handover from internal circle to external circle.
Usage
This counter is used to find out the frequency of MS handover due to too low C/I ratio on
TCH/H channel. If the counter's value is too large, it indicates that, when MS calls within
the internal circle, MS performs handover to the external circle many times due to poor C/I
ratio. Interference within the internal circle is big, and C/I ratio of the internal circle can be
improved by adjusting the carrier power.
Measurement Point
If handover decision succeeds and the handover is due to too low C/I ratio, this counter
4-260

Unit
Times
Related Features

due to PBGT
Description
This counter counts the number of MS handover attempts due to PBGT value on TCH/H
channel. If PBGT value is larger than zero, it indicates the adjacent cell has better radio
environment than the current cell. If the number of times that PBGT value is larger than
zero reaches the threshold, PBGT handover occurs.
Usage
This counter is used to find out the frequency of MS handover due to PBGT value on
TCH/H channel. If the counter's value is too large, it indicates that signal on TCH/H channel
within the current cell is poorer than that in the adjacent cell.
Measurement Point
If handover decision succeeds and the handover is due to PBGT value, this counter
4-261

Unit
Times
Related Features


due to large TA
Description
This counter counts the number of MS handover attempts due to too large TA on TCH/H
channel. Increasing TA indicates that MS is moving away from the current cell. When the
distance reaches a certain value, handover will occur due to too large TA.
Usage
This counter is used to find out the frequency of MS handover due to too large TA on
TCH/F channel. The counter's value reflects the mobility of subscribers in the current cell
to a certain extent.
Measurement Point
If handover decision succeeds and the handover is due to too large TA, this counter
4-262

Unit
Times
Related Features


Description
This counter counts the number of handover attempts due to any other reason beyond the
handover reasons mentioned previously.
Usage
This counter is used to find out the frequency of handover due to any other reason.
Measurement Point
If handover decision succeeds and the handover is due to any other reason beyond the
handover reasons mentioned previously, this counter increments. The measurement point
4-263

Unit
Times
Related Features

assignment success
Description
This counter counts the number of successfully assigning TCH/H channel as signaling
channel.
After BSC responds the channel request and successfully allocates and occupies the
channel, BSC sends channel activation message CHL_ACT to activate the TCH/H.
For immediate assignment, after the channel activation succeeds, BTS receives the
MS access message and sends EST_IND to BSC. The counter increments when BSC
receives the message correctly.
Measurement Point
For immediate assignment, the counter increments when BSC receives the EST_IND
message correctly. The measurement point is A3, as shown in Figure 4-302.
Unit
Times
4-264

Related Features
4.237 C900060236 Number of 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 Point
The counter increments when BSC receives the EST_IND message. The measurement
Unit
Times
4-265

4.238 C900060237 Number of dual band outgoing

handover
Description
This counter counts the number of MSC-controlled inter-BSC outgoing handovers that
are initiated by MS in the source cell (the source cell and the target cell are of different
frequency bands).
Usage
handover that is initiated by MS. The source cell and the target cell are of different
frequency bands.
Measurement Point
BSC performs handover decision after receiving the measurement report sent by MS. If
the decision indicates that inter-cell handover is necessary and if the current cell to which
the handover is attempted is a cell under different BSC, then BSC sends the handover
request A_HO_RQD to MSC to trigger inter-BSC handover. If BSC receives the handover
command returned from MSC and if the source cell and the target cell are of different
frequency bands, then this counter increments. The measurement point is A, as shown in
Figure 4-304.
Figure 4-304 MSC-Controlled Outgoing Handover Execution
Unit
Times
Related Features
4-266

4.239 C900060238 Number of dual band outgoing

handover success
Description
This counter counts the number of successful MSC-controlled inter-BSC outgoing
handovers that are initiated by MS in the source cell (the source cell and the target cell
are of different frequency bands).
Usage
outgoing handover that is initiated by MS. The source cell and the target cell are of different
frequency bands.
Measurement Point
BSC performs handover decision after receiving the measurement report sent by MS. If
the decision indicates that inter-cell handover is necessary and if the current cell to which
the handover is attempted is a cell under different BSC, then BSC sends the handover
request A_HO_RQD to MSC to trigger inter-BSC handover. If MS accesses the target cell
successfully, the source cell receives the release command issued by MSC, if the source
cell and the target cell are of different frequency bands, then this counter increments. The
Figure 4-305 MSC-Controlled Outgoing Handover Success
Unit
Times
Related Features
4-267

4.240 C900060239 Number of dual band incoming

handover
Description
This counter counts the number of inter-BSC incoming handovers to the current cell that
are initiated by MSC (the source cell and the target cell are of different frequency bands).
Usage
This counter is used to find out the frequency of inter-BSC incoming handover that is
initiated by MSC. The source cell and the target cell are of different frequency bands.
Measurement Point
After the target cell receives the handover request issued by MSC, if the target cell occupies
and activates the channel successfully and if the source cell and the target cell are of
different frequency bands, then this counter increments. The measurement point is A, as
Figure 4-306 MSC-Controlled Incoming Handover Execution
Unit
Times
Related Features
4-268


handover success
Description
This counter counts the number of successful MSC-controlled inter-BSC incoming
handovers that are initiated by MS (the source cell and the target cell are of different
frequency bands).
Usage
This counter is used to find out the frequency of MSC-controlled inter-cell handover that is
initiated by MS. The source cell and the target cell are of different frequency bands.
Measurement Point
After the target cell receives the handover completion message, if the request is due to
MSC-controlled inter-BSC incoming handover and if the source cell and the target cell are
of different frequency bands, then this counter increments. The measurement point is A,
Unit
Times
Related Features
4.242 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.
4-269

l If BSC receives the correct EST_IND message within specified time, it indicates
that the SDCCH channel assignment succeeds, C900060241 and C900060242
accumulate simultaneously.
l If BSC receives the incorrect EST_IND message or T3101 is timeout, it indicates that
the SDCCH channel assignment fails, C900060241 and C900060243 accumulate
simultaneously.
Usage
This counter counts the number of SDCCH channel assignment attempts when BSC
sends the IMM_ASS message to notify MS to use the allocated SDCCH channel. The
counter's value includes the number of assignment success (C900060242) and the
number of assignment failure (C900060243).
Measurement Point
This counter counts when BSC receives the EST_IND message or the assignment
completion message, or when T3101 is timeout (C900060242 + C900060243). The
Unit
Times
Related Features
4-270

4.243 C900060242 Number of SDCCH assignments

success
Description
If BSC receives the correct EST_IND message within specified time, it indicates that the
SDCCH channel assignment succeeds, then this counter increments.
Usage
This counter counts the number of MS successfully accessing SDCCH channel when BSC
sends the IMM_ASS message.
Measurement Point
This counter counts when BSC receives the correct EST_IND message or the assignment
completion message. The measurement point is A3, as shown in Figure 4-309.
Unit
Times
4-271

Related Features

failure
Description
If BSC receives the incorrect EST_IND message or T3101 is timeout, it indicates that the
SDCCH channel assignment fails, then this counter increments.
Usage
This counter counts the number of MS failing to access SDCCH channel when BSC sends
the IMM_ASS message.
Measurement Point
This counter counts when BSC receives the incorrect EST_IND message or when T3101
is timeout. The measurement point is A3, as shown in Figure 4-310.
4-272

Unit
Times
Related Features

to radio link failure
Description
This counter counts the number of voice TCH/F drops due to radio link failure. After MS
applies for TCH/F voice channel, call drops. If this problem is caused by radio link failure,
then this counter increments.
Usage
This counter is used to learn the call drop frequency caused by raio link failure on TCH/F
voice channel.
Measurement Point
On TCH/F voice channel, when BSC receives Connection Failure Indication message at
Abis interface, this counter counts. The measurement point is A, as shown in Figure 4-311.
4-273

Figure 4-311 Call Drops Caused by Radio Link Failure During Assignment
Unit
Times
Related Features
ZGB-06-01-001 Monitoring Um Interface

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

Usage
This counter is used to learn the call drop frequency caused by raio link failure on TCH/H
voice channel.
Measurement Point
On TCH/H voice channel, when BSC receives Connection Failure Indication message at
Abis interface, this counter counts. The measurement point is A, as shown in Figure 4-312.
Figure 4-312 Call Drops Caused by Radio Link Failure During Assignment
Unit
Times
Related Features
4-275

4-276

Chapter 5
Configuration Management
Infomation Basic
Measurement
Table of Contents
Overview ....................................................................................................................5-1
C900090001 Cell frequency band ..............................................................................5-1
C900090002 Number of TRX .....................................................................................5-2
C900090003 Number of TCH .....................................................................................5-2
C900090004 Number of SDCCH................................................................................5-2
C900090005 Radio capacity (call loss 1) ....................................................................5-3
C900090006 Radio capacity (call loss 2) ....................................................................5-3
C900090007 Radio capacity (based on TRX) .............................................................5-3
C900090008 Number of static PDTCH .......................................................................5-4
C900090009 Number of dynamic PDTCH ..................................................................5-4
5.1 Overview
Configuration management information basic measurement records the cell's basic
configuration information of each measurement period.
Statistic unit in this measurement is cell.
5.2 C900090001 Cell frequency band

Description
This counter records frequency bands set in the cell. Refer to configuration information for
frequency band values.
Usage
This counter is used to find out frequency bands set at specific time segment in the cell.
Unit
None
5-1

5.3 C900090002 Number of 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
5.4 C900090003 Number of 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
5.5 C900090004 Number of 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
5-2

Chapter 5 Configuration Management Infomation Basic Measurement
5.6 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
5.7 C900090006 Radio capacity (call loss 2)

Description
This counter records the cell's maximum traffic capacity in theory, and it gets the radio
capacity (call loss 2) from the Erlang table according to the number of voice channels.
Usage
segment.
Unit
5.8 C900090007 Radio capacity (based on TRX)

Description
This counter records the cell's maximum traffic capacity in theory. The radio capacity is
calculated according to the number of carriers: 2.28 for a single carrier, 8.25 for dual
carriers, 14.04 for three carriers, and 21.04 for four carriers.
Usage
segment.
Unit
5-3

5.9 C900090008 Number of 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
5.10 C900090009 Number of 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
5-4

Chapter 6
Downlink Data TBF
Measurement
Table of Contents
Overview ....................................................................................................................6-2
C901000001 Number of GPRS DL TBF resumption in delay state .............................6-2
C901000005 Number of GPRS DL TBF establishment failure on PACCH due to
time out ......................................................................................................................6-3
other reasons .............................................................................................................6-4
C901000009 Number of GPRS DL TBF establishment failure on CCCH/PCCCH
due to time out ...........................................................................................................6-5
due to other reasons ..................................................................................................6-6
C901000011 Number of GPRS DL TBF establishment execution on CCCH/PCCCH..6-6
C901000012 Number of GPRS DL TBF establishment execution failure on
CCCH/PCCCH due to polling failed............................................................................6-8
C901000013 Number of GPRS DL TBF establishment execution success on
CCCH/PCCCH due to polling succeeded .................................................................6-10
C901000014 Number of GPRS DL TBF establishment success on CCCH/PCCCH..6-12
C901000015 Number of GPRS DL TBF normal release ...........................................6-14
C901000023 Number of EGPRS DL TBF resumption in delay state .........................6-15
C901000027 Number of EGPRS DL TBF establishment failure on PACCH due to
time out ....................................................................................................................6-16
other reasons ...........................................................................................................6-17
C901000031 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH
due to time out .........................................................................................................6-18
due to other reasons ................................................................................................6-19
C901000033 Number of EGPRS DL TBF establishment execution on
CCCH/PCCCH .........................................................................................................6-19
C901000034 Number of EGPRS DL TBF establishment execution failure on
CCCH/PCCCH due to polling failed..........................................................................6-21
C901000035 Number of EGPRS DL TBF establishment execution success on
CCCH/PCCCH due to polling succeeded .................................................................6-23
C901000036 Number of EGPRS DL TBF establishment success on
CCCH/PCCCH .........................................................................................................6-25
6-1

C901000037 Number of EGPRS DL TBF normal release.........................................6-27

C901000045 Time of GPRS DL TBF connection ......................................................6-28
C901000046 Time of EGPRS DL TBF connection....................................................6-29
C901000047 Time of DL signaling TBF connection ..................................................6-30
C901000048 Max number of GPRS DL TBF simultaneous establishment ................6-30
C901000050 Max number of EGPRS DL TBF simultaneous establishment..............6-31
C901000052 Number of GPRS DL signaling TBF normal release ............................6-31
C901000058 Number of EGPRS DL signaling TBF normal release ..........................6-33
6.1 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.
6.2 C901000001 Number of 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 Point
When the DL GPRS TBF transmits all LLC frames and receives new LLC frames before
transmitting the DL RLC block (FBI=1), this counter increments. The measurement point
6-2

Chapter 6 Downlink Data TBF Measurement
Figure 6-1 - 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

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

Measurement Point
When the BSC sends DL Assign Request, the timer waiting for response is triggered. The
counter increments if the timer expires. The measurement point is A, as shown in Figure
6-2.
Figure 6-2 Number Of Request Failures For Establishing GPRS On PACCH (No
Response From Control Plane)
Unit
Times

failure on PACCH due to other reasons
Definition
Number of GPRS DL TBF establishment failure on PACCH due to other reasons
Description
This counter counts the number of TBF establishment failures caused by other reasons
than non-responses from the control plane when PACCH of GPRS TBF tries to establish
DL TBF. The other reasons here include failed transmission of assignment messages and
failed creation of DL RLC instances.
Measurement Point
When PACCH fails to send the assignment messages or fails to create DL RLC instances,
the counter increments.
Unit
Times
6-4


failure on CCCH/PCCCH due to time out
Definition
Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to time out
Description
When MS is in the idle state, after BSC receives DL LLC frames from SGSN, BSC should
originate DL TBF establishment assigned on CCCH/PCCCH. The user plane asks the
control plane for radio resources. If the user plane fails to receive the resources within
the specified time or it receives the message of assignment failure, it indicates that the DL
TBF establishment fails.
Measurement Point
During the DL GPRS TBF establishment on CCCH/PCCCH, if there is no radio resource
assigned by the control plane within the specified time, this counter increments. The
measurement point is A, as shown in Figure 6-3 and Figure 6-4.
Figure 6-3 Failures For Establishing DL GPRS TBF On CCCH/PCCCH (1)
Unit
Times
6-5


failure on CCCH/PCCCH due to other reasons
Definition
Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons
Description
originate DL TBF establishment assigned on CCCH/PCCCH. The user plane sends a DL
establishment request to the control plane. If it receives the instance release message from
the control plane or fails to create DL RLC instance after receiving the resource assignment
message, it indicates that the DL TBF establishment fails.
Measurement Point
During the DL GPRS TBF establishment on CCCH/PCCCH, after the user plane sends the
request to the control plane, if it receives the instance release message from the control
plane or fails to create DL RLC instance after receiving the resource assignment message,
Unit
Times

execution on CCCH/PCCCH
Definition
Number of GPRS DL TBF establishment execution on CCCH/PCCCH
Description
originate DL TBF establishment assigned on 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 assignment, the user plane is informed too and it
believes the DL TBF establishment has started.
6-6

Measurement Point
During the DL GRPS TBF establishment on CCCH/PCCCH, after the user plane sends
the request to the control plane, receives the resource assignment message, successfully
creates the DL RLC instance and sends the Packet Polling Request message to MS, this
counter increments. The measurement point is A2, as shown inFigure 6-5 .
Figure 6-5 Normal Establishment Of DL GPRS TBF On CCCH/PCCCH
l In the DTM mode, this counter increments when the user plane receives the DTM
sent message (the LLC frame has been sent). The measurement point is A, as
Figure 6-6 LLC Frame Transmits GTTP Message In DTM Mode
assignment message. The measurement point is A, as shown in Figure 6-7.
6-7

Figure 6-7 DTM Assignment In DTM Mode
Unit
Times

execution failure on CCCH/PCCCH due to polling
failed
Definition
Number of Number of GPRS DL TBF establishment execution on CCCH/PCCCH
DL TBF establishment execution failure on CCCH/PCCCH due to polling failed
Description
originate DL TBF establishment assigned on CCCH/PCCCH. After receiving the resource
assigned by the control plane, the user plane sends the packet polling request message
through the assigned channel. When the MS responds with the AB form of packet control
ack message, the MS initial timing advance is acquired then. If the MS does not respond,
it indicates the DL establishment has failed.
Measurement Point
l While waiting for MSs responding with the AB form of packet control ack message,
if timeout occurs or messages informing control block loss exceed the specified
number, this counter increments. The measurement point is A, as shown in Figure
6-8.
if the release request is received from control plane, this counter increments. The
6-8

Figure 6-8 Measurement Point Of Number Of Times For Establishing GPRS DL TBF
With Polling Failed On CCCH/PCCCH
Figure 6-9 Measurement Point Of Number Of Times For Establishing GPRS DL TBF With Polling
Failed On CCCH/PCCCH
Unit
Times
6-9


execution success on CCCH/PCCCH due to polling
succeeded
Definition
DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded
Description
l 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. After receiving
the resource assigned by the control plane, the user plane sends the packet polling
request message through the assigned channel. When the MS responds with the
AB form of packet control ack message, the MS initial timing advance is acquired
then. If the BSC receives the packet control ack message and sends the message of
timing advance setting, it indicates that the operation is successful.
l In the DTM mode, if the user plane receives the DTM assignment message from the
control plane, the operation is considered to be successful.
l Besides, in the DTM mode, if the user plane receives the DTM sent message
from the control plane, to keep the consistency of DL TBF establishment attempts
and successful establishments, the DL TBF establishment is also considered to
be successful.
Measurement Point
When BSC receives the packet control ack message from MS after sending the packet
polling request message, or when in the DTM mode, the user plane receives the
DTM sent/assignment message from the control plane, this counter increments. The
measurement points are A3 as shown in Figure 6-10, A as shown in Figure 6-11, and A
6-10

Unit
Times
6-11


establishment success on CCCH/PCCCH
Definition
DL TBF establishment success on CCCH/PCCCH
Description
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.
l Besides, in the DTM mode, if the user plane receives the DTM sent message from
the control plane, to keep the consistency of DL TBF establishment attempts and
successful establishments, the GPRS DL TBF establishment is also considered
to be successful.
Measurement Point
l If the assignment is on PCCCH, after the user plane sends the packet polling
request message and receives the packet control ack message from MS, the
counter increments.
l 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.
l In the DTM mode, when the user plane receives the DTM sent/assignment message
from the control plane, the counter increments.
l The measurement points are A3 (PCCCH) and A4 (CCCH), as shown in Figure 6-13,
A as shown in Figure 6-14, and A as shown in Figure 6-15.
6-12

Unit
Times
6-13

6.11 C901000015 Number of GPRS DL TBF normal

release
Definition
DL TBF normal release
Description
When the DL GPRS TBF sends the last data block, it sets FBI to 1 and sets the RRBP
bit to let MS send the DL response message. After BSC receives the last response
message (FAI=1), it is considered that the DL transmission is executed normally. In the
DTM mode, if the user plane receives the data sent message from the control plane, to
keep measurement consistency, it is considered that the DL TBF is released normally.
Measurement Point
After the DL GPRS TBF transmits the last data block (FBI=1) and when BSC receives the
last DL response message (FAI=1), this counter increments. The measurement points are
A, as shown in Figure 6-16and Figure 6-17.
Figure 6-16 Normal Release Of DL TBF
6-14

Unit
Times

resumption in delay state
Definition
Number of EGPRS DL TBF resumption in delay state
Description
This counter counts the number of retransmissions after the DL EGPRS TBF finishes LLC
frame transmission and receives new LLC frames.
Measurement Point
After the DL EGPRS TBF transmits all LLC frames and before the DL RLC block with FBI
= 1 is transmitted, if the DL TBF receives new LLC frames, this counter increments. The
6-15

Figure 6-18 - 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

establishment failure on 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.
6-16

Measurement Point
When the BSC sends DL Assignment Request, the timer waiting for response is triggered.
The counter increments if the timer expires. The measurement point is A, as shown in
Figure 6-19.
Figure 6-19 Number Of Request Failures For Establishing GPRS On PACCH (No
Response From Control Plane)
Unit
Times

establishment failure on PACCH due to other
reasons
Definition
Number of EGPRS DL TBF establishment failure on PACCH due to other reasons
Description
This counter counts the number of TBF establishment failures caused by other reasons
than non-responses from the control plane when PACCH of EGPRS TBF tries to establish
DL TBF. The other reasons here include failed transmission of assignment messages and
failed creation of DL RLC instances.
Measurement Point
When PACCH fails to send the assignment messages or fails to create DL RLC instances,
Unit
Times
6-17


establishment failure on CCCH/PCCCH due to time
out
Definition
Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to time out
Description
originate DL TBF establishment assigned on CCCH/PCCCH. The user plane asks the
control plane for radio resources. If the user plane fails to receive the resources within
the specified time or it receives the message of assignment failure, it indicates that the DL
TBF establishment fails.
Measurement Point
During the DL EGPRS TBF establishment on CCCH/PCCCH, if there is no radio resource
assigned by the control plane within the specified time, this counter increments. The
measurement points are A, as shown in Figure 6-20 and Figure 6-21.
6-18

Unit
Times

establishment failure on CCCH/PCCCH due to
other reasons
Definition
Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons
Description
originate DL TBF establishment assigned on CCCH/PCCCH. The user plane sends a DL
establishment request to the control plane. If it receives the instance release message from
the control plane or fails to create DL RLC instance after receiving the resource assignment
message, it indicates that the DL TBF establishment fails.
Measurement Point
During the DL EGRPS TBF establishment on CCCH/PCCCH, after the user plane sends
the request to the control plane, if it receives the instance release message from the control
plane or fails to create DL RLC instance after receiving the resource assignment message,
Unit
Times

establishment execution on CCCH/PCCCH
Definition
Number of EGPRS DL TBF establishment execution on CCCH/PCCCH
Description
originate DL TBF establishment assigned on 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.
6-19

In the DTM mode, if the control plane has transmitted LLC frames through the dedicated
channel or has transmitted the DTM assignment, the user plane is informed too and it
believes the DL TBF establishment has started.
Measurement Point
l During the DL EGRPS TBF establishment on CCCH/PCCCH, after the user plane
sends the request to the control plane, receives the resource assignment message,
successfully creates the DL RLC instance and sends the Packet Polling Request
message to MS, this counter increments. The measurement point is A2, as shown in
Figure 6-22.
sent message (the LLC frame has been sent). The measurement point is A, as
6-20

assignment message. The measurement point is A, as shown in Figure 6-24.
Unit
Times

establishment execution failure on CCCH/PCCCH
due to polling failed
Definition
Number of EGPRS DL TBF establishment execution failure on CCCH/PCCCH due to
polling failed
Description
originate DL TBF establishment assigned on CCCH/PCCCH. After receiving the resource
assigned by the control plane, the user plane sends the packet polling request message
through the assigned channel. When the MS responds with the AB form of packet control
ack message, the MS initial timing advance is acquired then. If the MS does not respond,
it indicates the DL establishment fails.
Measurement Point
if timeout occurs or messages informing control block loss exceed the specified
number, this counter increments. The measurement point is A, as shown in Figure
6-25.
if the release request is received from control plane, this counter increments. The
6-21

Figure 6-25 Measurement Point Of Number Of Times For Establishing EGPRS DL

TBF With Polling Failed On CCCH/PCCCH
Figure 6-26 Measurement Point Of Number Of Times For Establishing EGPRS DL TBF With Polling
Failed On CCCH/PCCCH
Unit
Times
6-22


establishment execution success on CCCH/PCCCH
due to polling succeeded
Definition
Number of EGPRS DL TBF establishment execution success on CCCH/PCCCH due to
polling succeeded
Description
then. If the BSC receives the packet control ack message and sends the message of
timing advance setting, it indicates that the operation is successful.
l Besides, in the DTM mode, if the user plane receives the DTM sent message
from the control plane, to keep the consistency of DL TBF establishment attempts
and successful establishments, the DL TBF establishment is also considered to
be successful.
Measurement Point
When BSC receives the packet control ack message from MS after sending the packet
polling request message, or when in the DTM mode, the user plane receives the
DTM sent/assignment message from the control plane, this counter increments. The
measurement points are A3, as shown inFigure 6-27, A as shown in Figure 6-28 and A
6-23

Unit
Times
6-24


Definition
Number of EGPRS DL TBF establishment success on CCCH/PCCCH
Description
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.
l Besides, in the DTM mode, if the user plane receives the DTM sent message from
the control plane, to keep the consistency of DL TBF establishment attempts and
successful establishments, the EGPRS DL TBF establishment is also considered
to be successful.
Measurement Point
l If the assignment is on PCCCH, after the user plane sends the packet polling
request message and receives the packet control ack message from MS, the
counter increments.
l 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.
l In the DTM mode, when the user plane receives the DTM sent/assignment message
from the control plane, the counter increments.
l The measurement points are A3 (PCCCH) and A4 (CCCH), as shown in Figure 6-30,
A as shown in Figure 6-31, and A as shown in Figure 6-32.
6-25

Unit
Times
6-26

6.21 C901000037 Number of 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
Measurement Point
After the DL EGPRS TBF transmits the last data block (FBI=1) and when BSC receives
the last DL response message (FAI=1), this counter increments. The measurement points
are A, as shown in Figure 6-33andFigure 6-34.
6-27

Unit
Times
6.22 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 Point
l (1) When GPRS TBF RLC transmission starts, this counter accumulates.
l (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.
l (3) When GPRS TBF RLC transmission is released abnormally (including N3105
overflow and T3191 timeout), this counter accumulates.
l (4) When the measurement value is acquired regularly, this counter accumulates.
l 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 6-35.
6-28

Figure 6-35 Measurement Of Cumulated Overall DL Connecting Time
Unit
Second
6.23 C901000046 Time of EGPRS DL TBF connection

Definition
Time of EGPRS DL TBF connection
Description
This counter counts the cumulated overall DL connecting time of EGPRS TBF within a cell.
Measurement Point
The measurement point and the formulas are as shown in Figure 6-36. EGPRS TBF is
the measurement prerequisite.
Unit
Second
6-29

6.24 C901000047 Time of DL signaling TBF connection

Definition
Time of DL signaling TBF connection
Description
This counter counts the cumulated overall DL connecting time of signaling TBF within a
cell.
Measurement Point
The measurement point and the formulas are as shown in Figure 6-37. Signaling TBF is
the measurement prerequisite.
Unit
Seconds
6.25 C901000048 Max number of GPRS DL TBF

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 Point
l When GPRS TBF RLC transmission starts, the GPRS TBFs in the cell increments
by 1 and compares with the saved maximum value.
6-30

l 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
6.26 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 Point
l When EGPRS TBF RLC transmission starts, the EGPRS TBFs in the cell increments
by 1 and compares with the saved maximum value.
l 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
6-31

Measurement Point
After the DL GPRS signaling TBF transmits the last data block (FBI=1) and when
BSC receives the last DL response message (FAI=1), this counter increments. The
measurement points are A, as shown in Figure 6-38and Figure 6-39.
Unit
Times
6-32


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

Unit
Times
6-34

Chapter 7
Uplink Data TBF
Measurement
Table of Contents
Overview ....................................................................................................................7-2
C901010001 Number of GPRS UL TBF resumption in extend uplink state .................7-2
C901010002 Number of GPRS UL TBF resource reassign in delay uplink state.........7-3
C901010006 Number of GPRS establishment failure on PACCH due to time out .......7-4
C901010007 Number of GPRS establishment failure on PACCH due to other
reasons ......................................................................................................................7-5
C901010010 Number of GPRS UL TBF establishment failure on CCCH/PCCCH
due to competition solving failed.................................................................................7-6
due to not receive resource request ...........................................................................7-7
due to other reasons ..................................................................................................7-8
C901010013 Number of GPRS UL TBF establishment success on CCCH/PCCCH....7-9
C901010014 Number of GPRS UL TBF normal release ...........................................7-11
C901010022 Number of EGPRS UL TBF resumption in extend uplink state.............7-12
C901010023 Number of EGPRS UL TBF resource reassign in delay uplink state ....7-13
C901010027 Number of EGPRS establishment failure on PACCH due to time out ...7-13
C901010028 Number of EGPRS establishment failure on PACCH due to other
reasons ....................................................................................................................7-14
C901010031 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH
due to competition solving failed...............................................................................7-15
due to not receive resource request .........................................................................7-16
due to other reasons ................................................................................................7-17
C901010034 Number of EGPRS UL TBF establishment success on
CCCH/PCCCH .........................................................................................................7-18
C901010035 Number of EGPRS UL TBF normal release.........................................7-20
C901010043 Time of GPRS UL TBF connection ......................................................7-21
C901010044 Time of EGPRS UL TBF connection....................................................7-22
C901010045 Time of UL signaling TBF connection ..................................................7-22
C901010046 Max number of GPRS UL TBF simultaneous establishment ................7-23
C901010048 Max number of EGPRS UL TBF simultaneous establishment..............7-23
C901010050 Number of GPRS UL signaling TBF normal release ............................7-24
7-1

C901010056 Number of EGPRS UL signaling TBF normal release ..........................7-25
7.1 Overview
Uplink (UL) data TBF measurement mainly involves processes of establishing TBF,
keeping TBF and releasing TBF on cells.
7.2 C901010001 Number of 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 Point
This counter increments when a new data block is received in GPRS extended UL state.
7-2

Chapter 7 Uplink Data TBF Measurement
Figure 7-1 Measurement Point On Receiving New Data Block In GPRS Extended UL
State
Unit
Times

reassign in delay uplink state
Definition
Number of GPRS UL TBF resource reassign in delay uplink state
Description
If either MS or network does not support extended UL, after receiving RLC block (CV = 0)
from MS, network will enter in delayed UL state, and meanwhile stop allocating blocks.
Usage
This counter is used to record number of resource reassignment for GPRS UL TBF in
delayed UL state.
Measurement Point
This counter increments when UPPB receives UL resource reassign for GPRS UL TBF in
delayed UL state, A, as shown in Figure 7-2.
7-3

Figure 7-2 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
7.4 C901010006 Number of GPRS establishment failure

on PACCH due to time out
Definition
Number of GPRS establishment failure on PACCH due to time out
Description
During TBF transmission of an MS with downlink TBF, if MS has UL data to transmit but no
corresponding TBF is available, UL TBF establishment request will be sent out by Packet
Downlink Ack. UPPB will request CMP for resources if it does not have UL resource
records, and meanwhile, UPPB starts the timer. The request fails if the timer gets no
response till timeout.
Usage
This counter is used to record number of request failures caused by timeout for establishing
GPRS on PACCH.
Measurement Point
7-4

Figure 7-3 Measurement Point On Number Of Request Failures Caused By Timeout

For Establishing GPRS On PACCH GPRS
Unit
Times
7.5 C901010007 Number of GPRS establishment failure

on PACCH due to other reasons
Definition
Number of GPRS establishment failure on PACCH due to other reasons
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. Generally, network will assign resources to MS; However, UL
TBF establishment request fails if there is any condition abnormal.
Usage
This counter is used to record number of request failures caused by other reasons for
establishing GPRS on PACCH.
Measurement Point
This counter increments when the request for establishing GPRS on PACCH fails because
of other reasons except timer is timeout.
Unit
Times
7-5

7.6 C901010010 Number of GPRS UL TBF establishment

failure on CCCH/PCCCH due to competition solving
failed
Definition
Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to competition
solving failed
Description
When MS has new data to transmit but no corresponding UL/downlink TBF is available,
MS initiates UL TBF establishment flow, depending on whether the cell configures PBCCH
on CCCH/PCCCH.
If two-step access is not compulsory at network side, in the case of request for
one-step access, MS sends RLC block with TLLI or Packet Resource Request/
Additional MS Radio Access Capabilities on the UL block allocated after
receiving assignment message from network so that solution by competition can be
completed. Meanwhile, network sends Packet UL Ack with TLLI as well.
After sending out assignment message, if network does not receive RLC block or Packet
Resource Request/ Additional MS Radio Access Capabilities from MS till
timeout, solution for one-step access by competition fails.
Usage
This counter is used to record number of failed GPRS UL TBF establishment on
CCCH/PCCCH due to the failure of one-step success competition solution.
Measurement Point
Figure 7-4 Measurement Point On Number Of Establishment Failures Of GPRS UL TBF

Caused By Competition Solution Failure
7-6

Unit
Times
Related Features
ZGB-03-05-007 One Phase Access

establishment failure on CCCH/PCCCH due to not
receive resource request
Definition
Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to not receive
resource request
Description
on CCCH/PCCCH.
If two-step access is compulsory at network side, in the case of request for two-step
access, network assigns to MS single block resource, by which MS then reports Packet
Resource Request. After that, network assigns new resource for MS by Packet UL
Assignment according to MSs radio access capability.
After assigning single block resource to MS, if network does not receive Packet
Resource Request from MS, the request to establish GPRS UL TBF fails.
Usage
CCCH/PCCCH caused by not receiving resource request.
Measurement Point
7-7

Figure 7-5 Measurement Point On Number Of Establishment Failures Of GPRS UL TBF

Caused By Not Receiving Resource Request
Unit
Times
Related Features
ZGB-03-05-008 Two Phase Access

failure on CCCH/PCCCH due to other reasons
Definition
Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons
Description
on CCCH/PCCCH.
receiving assignment message from network so that solution by competion can be
Assignment according to MSs wireless radio access capability.
7-8

Usage
CCCH/PCCCH caused by any other reasons.
Measurement Point
This counter increments when GPRS UL TBF establishment fails because of other
reasons, except that one-step access competition solution fails or two-step access does
not receive resource request.
Unit
Times

success on CCCH/PCCCH
Definition
Number of GPRS UL TBF establishment success on CCCH/PCCCH
Description
on CCCH/PCCCH.
Usage
This counter is used to record number of successful GPRS UL TBF establishment on
CCCH/PCCCH.
Measurement Point
This counter increments when GPRS UL TBF establishment on CCCH/PCCCH succeeds
in the cases of both one-step access and two-step access. The measurement points are
A, as shown in Figure 7-6 and Figure 7-7.
7-9

Figure 7-6 Measurement Point On Number Of SuccessfuL GPRS UL TBF Establishment

On CCCH/PCCCH (I)
Figure 7-7 Measurement Point On Number Of Successful GPRS UL TBF Establishment

On CCCH/PCCCH (II)
7-10

Unit
Times
7.10 C901010014 Number of GPRS UL TBF normal

release
Definition
Number of GPRS UL TBF normal release
Description
If having received all data blocks, BSS sends Packet UL Ack with FAI to MS and sets
RRBP when receiving RLC block (CV = 0). MS then reports Packet Control Ack on
corresponding UL block, notifying BSS to release TBF normally.
Usage
This counter is used to record number of normal GPRS UL TBF releases.
Measurement Point
Figure 7-8 Measurement Point On Number Of Normal GPRS UL TBF Release
Unit
Times
7-11


resumption in extend uplink state
Definition
Number of EGPRS UL TBF resumption in extend uplink state
Description
MS notifies BSS whether extended GPRS UL TBF is supported by reporting its radio
access capability. If extended GPRS UL TBF is supported, BSS will not stop allocating
resources within a certain period of time after receiving RLC block (CV = 0) from MS.
During this period, if MS has new data to transmit, the data is transmitted directly by the
block allocated, and after the network receives a new block, TBF will be resumed to be in
normal transmission state. If MS has no new data to transmit, the message Packet UL
Dummy Control Block is transmitted by the block allocated.
Usage
This counter is used to record number of resumptions for EGPRS UL TBF in extended UL
state.
Measurement Point
Figure 7-9 Measurement Point On Number Of Resumptions For EGPRS UL TBF In

Extended UL State
Unit
Times
7-12


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.
Measurement Point
Figure 7-10 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
7.13 C901010027 Number of EGPRS establishment

failure on PACCH due to time out
Definition
Number of EGPRS establishment failure on PACCH due to time out
7-13

Description
no corresponding UL TBF is available, UL TBF establishment request will be sent out by
Packet Downlink Ack. UPPB will request CMP for resources if having no UL resource
records, and meanwhile, UPPB starts the timer. The request fails if the timer gets no
response till timeout.
Usage
This counter is used to record number of request failures caused by timeout for establishing
EGPRS on PACCH.
Measurement Point
Figure 7-11 Measurement Point On Number Of Request Failures Caused By Timeout

For Establishing EGPRS On PACCH
Unit
Times
7.14 C901010028 Number of EGPRS establishment

failure on PACCH due to other reasons
Definition
Number of EGPRS establishment failure on PACCH due to other reasons
Description
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.
7-14

Usage
This counter is used to record number of request failures caused by other reasons for
establishing GPRS on PACCH.
Measurement Point
This counter increments when request for establishing EGPRS on PACCH fails because
of other reasons except timer is timeout.
Unit
Times

competition solving failed
Definition
Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to competition
solving failed
Description
on CCCH/PCCCH.
After sending out assignment message, if network does not receive RLC block or Packet
Resource Request/ Additional MS Radio Access Capabilities from MS till
timer is timeout, solution for one-step access by competition fails.
Usage
This counter is used to record number of failed EGPRS UL TBF establishment on
CCCH/PCCCH caused by competition solving failed.
Measurement Point
7-15

Figure 7-12 Measurement Point On Number Of Establishment Failures Of EGPRS UL

TBF Caused By Competition Solving Failed
Unit
Times
Related Features

receive resource request
Definition
Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to not receive
resource request
Description
on CCCH/PCCCH.
Assignment according to MSs radio access capability.
After assigning single block resource to MS, if network does not receive Packet
Resource Request from MS, the request to establish GPRS UL TBF fails.
Usage
CCCH/PCCCH caused by not receiving resource request.
7-16

Measurement Point
Figure 7-13 Measurement Point On Number Of Establishment Failures Of EGPRS UL

TBF Caused By Not Receiving Resource Request
Unit
Times
Related Features
ZGB-03-05-008 Two Phase Access

other reasons
Definition
Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons
Description
on CCCH/PCCCH.
receiving assignment message from network so that solution by competition can be
7-17

Usage
CCCH/PCCCH caused by any other reasons.
Measurement Point
This counter increments when EGPRS UL TBF establishment fails because of other
reasons except that one-step access competition solution fails or two-step access does
not receive resource request.
Unit
Times

Definition
Number of EGPRS UL TBF establishment success on CCCH/PCCCH
Description
on CCCH/PCCCH.
Usage
This counter is used to record number of successful EGPRS UL TBF establishment on
CCCH/PCCCH.
7-18

Measurement Point
This counter increments when EGPRS UL TBF establishment on CCCH/PCCCH succeeds
in the cases of both one-step access and two-step access. The measurement points are
A, as shown in Figure 7-14 and Figure 7-15.
Figure 7-14 Measurement Point On Number Of Successful EGPRS UL TBF

Establishment On CCCH/PCCCH (I)
7-19

Figure 7-15 Measurement Point On Number Of Successful EGPRS UL TBF

Establishment On CCCH/PCCCH (II)
Unit
Times
7.19 C901010035 Number of EGPRS UL TBF normal

release
Definition
Number of EGPRS UL TBF normal release
Description
Usage
This counter is used to record number of normal EGPRS UL TBF releases.
Measurement Point
7-20

Figure 7-16 Measurement Point On Number Of Normal EGPRS UL TBF Release
Unit
Times
7.20 C901010043 Time of GPRS UL TBF connection

Definition
Time of GPRS UL TBF connection
Description
MS establishes two types of TBF for different purposes. They are signaling TBF and data
TBF.
Usage
This counter is used to find out cumulated overall UL connecting time of GPRS TBF.
Measurement Point
The counter starts to accumulate when UPPB receives the UL GPRS TBF establishment
indication, and stops when UL GPRS TBF on UPPB ends normally.
Unit
Second
7-21

7.21 C901010044 Time of EGPRS UL TBF connection

Definition
Time of EGPRS UL TBF connection
Description
TBF.
Usage
This counter is used to find out cumulated overall UL connecting time of EGPRS TBF.
Measurement Point
The counter starts to accumulate when UPPB receives the UL EGPRS TBF establishment
indication, and stops when UL EGPRS TBF on UPPB ends normally.
Unit
Second
7.22 C901010045 Time of UL signaling TBF connection

Definition
Time of UL signaling TBF connection
Description
TBF.
Usage
This counter is used to find out cumulated overall UL connecting time of signaling TBF.
Measurement Point
The counter starts to accumulate when UPPB receives the UL signaling TBF establishment
indication, and stops when UL signaling TBF on UPPB ends normally.
Unit
Second
7-22

7.23 C901010046 Max number of GPRS UL TBF

Definition
Max number of GPRS UL TBF simultaneous establishment
Description
During the measurement period, there might be several TBFs existing simultaneously.
This counter is used to find out the maximum number of UL GPRS TBF established
simultaneously within the measurement period.
Usage
This counter is used to find out the maximum number of UL GPRS TBF established
Measurement Point
This counter increments when UPPB receives UL GPRS TBF establishment indication,
and decrements when the UL GPRS TBF releases.
Unit
Times
7.24 C901010048 Max number of EGPRS UL TBF

Definition
Max number of EGPRS UL TBF simultaneous establishment
Description
During the measurement period, there might be several TBFs existing simultaneously.
This counter is used to find out the maximum number of UL EGPRS TBF established
simultaneously within the measurement period
Usage
This counter is used to find out the maximum number of UL EGPRS TBF established
7-23

Measurement Point
This counter increments when UPPB receives UL EGPRS TBF establishment indication,
and decrements when the UL EGPRS TBF releases.
Unit
Times

normal release
Definition
Number of GPRS UL signaling TBF normal release
Description
Usage
This counter is used to record number of normal GPRS signaling UL TBF releases.
Measurement Point
The measurement point is A, as shown inFigure 7-17.
Figure 7-17 Measurement Point On Number Of Normal GPRS Signaling UL TBF Release
7-24

Unit
Times

normal release
Definition
Number of EGPRS UL signaling TBF normal release
Description
Usage
This counter is used to record number of normal EGPRS signaling UL TBF releases.
Measurement Point
Figure 7-18 Measurement Point On Number Of Normal GPRS Signaling UL TBF Release
Unit
Times
7-25

7-26

Chapter 8
Data Flow Measurement
Table of Contents
Overview ....................................................................................................................8-1
C901020001 Number of Kbytes of IP packet sent to BIPB..........................................8-2
C901020002 Number of packets sent to BIPB............................................................8-2
C901020003 Number of Kbytes of IP packet received from BIPB ...............................8-3
C901020004 Number of packets received from BIPB .................................................8-4
C901020005 Number of Kbytes of IP packet sent to GIPB .........................................8-5
C901020006 Number of packets sent to GIPB ...........................................................8-6
C901020007 Number of Kbytes of IP packet received from GIPB...............................8-7
C901020008 Number of packets received from GIPB.................................................8-7
C901020009 Number of Kbytes carried by EGPRS DL LLC frame .............................8-8
C901020014 Number of Kbytes carried by DL signaling LLC frame............................8-9
C901020019 Number of Kbytes carried by UL LLC frame ........................................8-10
C901020020 Number of UL LLC frames...................................................................8-11
C901020021 Number of Bytes of GPRS DL TBF LLC frame ....................................8-11
C901020022 Number of Bytes of EGPRS DL TBF LLC frame ..................................8-12
C901020023 Number of Bytes of DL signaling TBF LLC frame ................................8-13
C901020024 Number of Bytes of UL GPRS TBF LLC frame ....................................8-14
C901020025 Number of Bytes of EGPRS UL TBF LLC frame ..................................8-15
C901020026 Number of Bytes of UL signaling TBF LLC frame ................................8-16
C901020031 Number of GPRS UL data TBF completion..........................................8-16
C901020034 Number of GPRS DL data TBF completion..........................................8-17
C901020041 Number of EGPRS UL data TBF completion .......................................8-18
C901020044 Number of EGPRS DL data TBF completion .......................................8-19
C901020050 Number of Kbytes carried by GPRS DL LLC frame .............................8-20
8.1 Overview
Data flow measurement focuses on the flow related information, including the LLC frames,
RLC blocks and TBF connecting time.
8-1

8.2 C901020001 Number of 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 measurement unit is Byte.
Measurement Point
Figure 8-1 Measurement Point Of Size Of IP Packets Sent To BIPB
Unit
Byte
8.3 C901020002 Number of packets sent to BIPB

Definition
Number of packets sent to BIPB
8-2

Chapter 8 Data Flow Measurement
Description
Usage
The counter counts the number of IP packets sent to BIPB.
Measurement Point
Figure 8-2 Measurement Point Of Number Of IP Packets Sent To BIPB
Unit
Times
8.4 C901020003 Number of Kbytes of IP packet

received from BIPB
Definition
Number of Kbytes of IP packet received from BIPB
Description
This counter counts the payload received within iBSC.
8-3

Usage
The counter counts the size of IP packets received from BIPB. The measurement unit is
Byte.
Measurement Point
Figure 8-3 Measurement Point Of Size Of IP Packets Received From BIPB
Unit
Byte
8.5 C901020004 Number of packets received from BIPB

Definition
Number of packets received from BIPB
Description
Usage
The counter counts the number of packets received from BIPB.
Measurement Point
8-4

Figure 8-4 Measurement Point Of Number Of IP Packets Received From BIPB
Unit
Times
8.6 C901020005 Number of 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 received RLC blocks, composes UL UnitData, and sends it to GIPB
through IP packet.
This counter performs statistics for BSSGP layer, and the statistic data contains BSSGP
header but does not contain IP header.
Usage
The counter counts the size of IP packets sent to GIPB. The measurement unit is Byte.
Measurement Point
8-5

Figure 8-5 Measurement Point Of Size Of IP Packets Sent To GIPB
Unit
Byte
8.7 C901020006 Number of packets sent to GIPB

Definition
Number of packets sent to GIPB
Description
through IP packet.
Usage
The counter counts the number of IP packets sent to GIPB.
Measurement Point
Figure 8-6 Measurement Point Of Number Of IP Packets Sent To GIPB
Unit
Times
8-6

8.8 C901020007 Number of Kbytes of IP packet

received from GIPB
Definition
Number of Kbytes of IP packet received from GIPB
Description
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.
Measurement Point
Figure 8-7 Measurement Point Of Size Of IP Packets Received From GIPB
Unit
Byte
8.9 C901020008 Number of packets received from GIPB

Definition
Number of packets received from GIPB
8-7

Description
through IP packet.
Usage
The counter counts the number of IP packets received from GIPB.
Measurement Point
Figure 8-8 Measurement Point Of Number Of IP Packets Received From GIPB
Unit
Times
8.10 C901020009 Number of Kbytes carried by EGPRS

DL LLC frame
Definition
Number of Kbytes carried by EGPRS DL LLC frame
Description
establish DL TBF (radio access capacity to carry MS) and according to the CMP command,
header.
Usage
The counter counts the number of Kbytes carried by DL EGPRS LLC frame.
8-8

Measurement Point
Figure 8-9 Measurement Point Of Number Of Kbytes Carried By DL EGPRS LLC Frame
Unit
Byte
8.11 C901020014 Number of Kbytes carried by DL

signaling LLC frame
Definition
Number of Kbytes carried by DL signaling LLC frame
Description
UnitData identifies whether data or signaling 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.
header.
Usage
The counter counts the number of Kbytes carried by DL signaling LLC frame.
Measurement Point
8-9

Figure 8-10 Measurement Point Of Number Of Kbytes Carried By DL Signaling LLC

Frame
Unit
Byte
8.12 C901020019 Number of 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.
header.
Usage
The counter counts the number of Kbytes carried by UL LLC frame.
Measurement Point
Figure 8-11 Measurement Point Of Number Of Kbytes Carried By UL LLC Frame
8-10

Unit
Byte
8.13 C901020020 Number of UL 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 result is the number of
frames.
Usage
The counter counts the number of UL LLC frames.
Measurement Point
Figure 8-12 Measurement Point Of Number Of UL LLC Frames
Unit
Times
8.14 C901020021 Number of Bytes of GPRS DL TBF

LLC frame
Definition
Number of Bytes of GPRS DL TBF LLC frame
8-11

Description
information about MS reception by setting RRBP to let MS report Packet DL Ack.
header.
Usage
The counter counts the number of bytes of DL GPRS TBF LLC frame.
Measurement Point
Figure 8-13 Measurement Point Of Number Of Bytes Of DL GPRS TBF LLC Frame
Unit
Byte
8.15 C901020022 Number of Bytes of EGPRS DL TBF

LLC frame
Definition
Number of Bytes of EGPRS DL TBF LLC frame
Description
8-12

information about MS reception by setting RRBP to let MS report EGPRS Packet DL

Ack.
header.
Usage
The counter counts the number of bytes of DL EGPRS TBF LLC frame.
Measurement Point
Figure 8-14 Measurement Point Of Number Of Bytes Of DL EGPRS TBF LLC Frame
Unit
Byte
8.16 C901020023 Number of Bytes of DL signaling TBF

LLC frame
Definition
Number of Bytes of DL signaling TBF LLC frame
Description
information about MS reception by setting RRBP to let MS report EGPRS Packet DL Ack.
header.
8-13

Usage
The counter counts the number of bytes of DL signaling TBF LLC frame.
Measurement Point
Figure 8-15 Measurement Point Of Number Of Bytes Of DL Signaling TBF LLC Frame
Unit
Byte
8.17 C901020024 Number of Bytes of UL GPRS TBF

LLC frame
Definition
Number of Bytes of UL GPRS TBF LLC frame
Description
and sends it to SGSN.
header.
Usage
The counter counts the number of bytes of UL GPRS TBF LLC frame.
8-14

Measurement Point
Figure 8-16 Measurement Point Of Number Of Bytes Of UL GPRS TBF LLC Frame
Unit
Byte
8.18 C901020025 Number of Bytes of EGPRS UL TBF

LLC frame
Definition
Number of Bytes of EGPRS UL TBF LLC frame
Description
header.
Usage
The counter counts the number of bytes of UL EGPRS TBF LLC frame.
Measurement Point
Figure 8-17 Measurement Point Of Number Of Bytes Of UL EGPRS TBF LLC Frame
8-15

Unit
Byte
8.19 C901020026 Number of Bytes of UL signaling TBF

LLC frame
Definition
Number of Bytes of UL signaling TBF LLC frame
Description
header.
Usage
The counter counts the number of bytes of UL signaling TBF LLC frame.
Measurement Point
Figure 8-18 Measurement Point Of Number Of Bytes Of UL Signaling TBF LLC Frame
Unit
Byte

completion
Definition
Number of GPRS UL data TBF completion
8-16

Description
After the network side receives the data blocks (CV=0) from MS and if all the other blocks
have been received successfully, then it will send the Packet UL Ack message (FAI=1)
to MS. By this time, the UL data transmission is completed.
Usage
The counter counts the number of completion of GPRS UL data TBF.
Measurement Point
Figure 8-19 Measurement Point Of Total Number Of Completion Of GPRS UL Data TBF
Unit
Times
8.21 C901020034 Number of GPRS DL data TBF

completion
Definition
Number of GPRS DL data TBF completion
Description
After MS receives the FBI-set data blocks (RRBP is set at the network side) from the
network side and if all the other blocks have been received successfully, then it will send
the Packet DL Ack/EGPRS Packet DL Ack message (FAI=1) to the network side.
8-17

Usage
The counter counts the number of completion of GPRS DL data TBF.
Measurement Point
Figure 8-20 Measurement Point Of Total Number Of Completion Of GPRS DL Data TBF
Unit
Times

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.
Measurement Point
8-18

Figure 8-21 Measurement Point Of Total Number Of Completion Of EGPRS UL Data TBF
Unit
Times
8.23 C901020044 Number of EGPRS DL data TBF

completion
Definition
Number of EGPRS DL data TBF completion
Description
After MS receives the FBI-set data blocks (RRBP is set at the network side) from the
network side and if all the other blocks have been received successfully, then it will send
the Packet DL Ack/EGPRS Packet DL Ack message (FAI=1) to the network side.
Usage
The counter counts the number of completion of EGPRS DL data TBF.
Measurement Point
8-19

Figure 8-22 Measurement Point Of Total Number Of Completion Of EGPRS DL Data TBF
Unit
Times
8.24 C901020050 Number of Kbytes carried by GPRS

DL LLC frame
Definition
Number of Kbytes carried by GPRS DL LLC frame
Description
establish DL TBF (radio access capacity to carry MS) and according to the CMP command,
header.
Usage
The counter counts the number of Kbytes carried by DL GPRS LLC frame.
Measurement Point
8-20

Figure 8-23 Measurement Point Of Number Of Kbytes Carried By DL GPRS LLC Frame
Unit
Byte
8-21

8-22

Chapter 9
Uplink-Downlink RLC
Statistic Measurement
Table of Contents
Overview ....................................................................................................................9-1
C901030041 Bytes of GPRS DL RLC lost on PDTCH ................................................9-3
C901030042 Bytes of EGPRS DL RLC lost on PDTCH ..............................................9-4
C901030083 Number of UL RLC Blocks lost ..............................................................9-4
C901030084 Bytes of GPRS UL RLC lost on PDTCH ................................................9-5
C901030085 Bytes of EGPRS UL RLC lost on PDTCH ..............................................9-5
C901030086 Number of standstill of GPRS UL TBF receiving window .......................9-6
C901030087 Number of standstill of EGPRS UL TBF receiving window.....................9-7
C901030088 Number of standstill of GPRS DL TBF sending window .........................9-8
C901030089 Number of standstill of EGPRS DL TBF sending window.......................9-8
C901030090 Number of increment of DL coding mode ..............................................9-9
C901030091 Number of decrement of DL coding mode ...........................................9-11
C901030092 Number of increment of UL coding mode ............................................9-12
C901030093 Number of decrement of UL coding mode ...........................................9-13
C901030094 Number of conversion from GMSK to 8PSK ........................................9-14
C901030095 Number of conversion from 8PSK to GMSK ........................................9-16
C901030153 Number of increment of GPRS DL coding mode..................................9-17
C901030154 Number of decrement of GPRS DL coding mode ................................9-18
C901030155 Number of increment of GPRS UL coding mode..................................9-19
C901030156 Number of decrement of GPRS UL coding mode ................................9-20
C901030157 Number of increment of EGPRS DL coding mode ...............................9-20
C901030158 Number of decrement of EGPRS DL coding mode ..............................9-21
C901030159 Number of increment of EGPRS UL coding mode ...............................9-22
C901030160 Number of decrement of EGPRS UL coding mode ..............................9-22
9.1 Overview
RLC blocks are classified into control block and data block based on the content. Data
block includes RLC block waiting to be acknowledged (Pending block), retransmitted block
(NACK block), and first-transmitted block (new blocks excluding retransmitted RLC block
and pending RLC blocks).
RLC coding scheme includes CS1 ~ CS4 and MCS1 ~ MCS9. Coding scheme is set at
background and can be adjusted by BSC according to the link quality.
9-1

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 9-1 shows the measurement point of DL pending RLC block.
Figure 9-1 Measurement Point Of DL Pending RLC Block
Figure 9-2 shows the measurement point of DL retransmitted RLC block.
Figure 9-2 Measurement Point Of DL Retransmitted RLC Block
Figure 9-3shows the measurement point of DL first-transmitted RLC block.
Figure 9-3 Measurement Point Of DL First-Transmitted RLC Block
Figure 9-4 shows the measurement point of UL pending RLC block.
9-2

Chapter 9 Uplink-Downlink RLC Statistic Measurement
Figure 9-4 Measurement Point Of UL Pending RLC Block
Figure 9-5 shows the measurement point of UL retransmitted RLC block.
Figure 9-5 Measurement Point Of UL Retransmitted RLC Block
Figure 9-6 shows the measurement point of UL first-transmitted RLC block.
Figure 9-6 Measurement Point Of UL First-Transmitted RLC Block
9.2 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.
9-3

9.3 C901030042 Bytes of EGPRS DL RLC lost on

PDTCH
Definition
Bytes of EGPRS DL RLC lost on PDTCH
Description
9.4 C901030083 Number of UL 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 transmission.
Usage
This counter is used to find out the number of RLC data blocks lost on PDTCH.
Measurement Point
The counter increments when UL RLC data blocks from BTS get lost. The measurement
Figure 9-7 Measurement Point Of Number Of UL RLC Blocks Lost
Unit
Times
9-4

9.5 C901030084 Bytes of GPRS UL RLC lost on PDTCH

Definition
Bytes of GPRS UL RLC lost on PDTCH
Description
CS-coded RLC bytes lost on PDTCH in non-ack mode.
Usage
This counter is used to find out the number of CS-coded RLC bytes on UL PDTCH in
non-ack mode.
Measurement Point
The counter increments when CS-coded UL RLC block from BTS gets lost. The
Unit
Byte
9.6 C901030085 Bytes of EGPRS UL RLC lost on

PDTCH
Definition
Bytes of EGPRS UL RLC lost on PDTCH
Description
MCS-coded RLC bytes lost on PDTCH in non-ack mode.
9-5

Usage
This counter is used to find out the number of MCS-coded RLC bytes on UL PDTCH in
non-ack mode.
Measurement Point
The counter increments when MCS-coded UL RLC block from BTS gets lost. The
Unit
Byte
9.7 C901030086 Number of 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 window after UL GPRS TBF
establishment.
Usage
This counter is used to find out the number of standstill of UL GPRS TBF receiving window.
Measurement Point
The counter increments when receiving window is found to come to a standstill in RLC
layer after UL GPRS TBF establishment. The measurement point is A, as shown in Figure
9-10.
9-6

Figure 9-10 Measurement Point Of Number Of Standstill Of GPRS UL TBF Receiving

Window
Unit
Times
9.8 C901030087 Number of standstill of EGPRS UL TBF

receiving window
Definition
Number of standstill of EGPRS UL TBF receiving window
Description
This counter counts the number of standstill of UL receiving window after UL EGPRS TBF
establishment.
Usage
This counter is used to find out the number of standstill of UL EGPRS TBF receiving
window.
Measurement Point
The counter increments when receiving window is found to come to a standstill in RLC
layer after UL EGPRS TBF establishment.
Unit
Times
9-7

9.9 C901030088 Number of 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 Point
The counter increments when sending window is detected to stagnate during RLC block
sending to BTS from BSC. The measurement point is A, as shown in Figure 9-11.
Figure 9-11 Measurement Point Of Number Of Standstill Of GPRS DL TBF Sending

Window
Unit
Times
9.10 C901030089 Number of standstill of EGPRS DL

TBF sending window
Definition
Number of standstill of EGPRS DL TBF sending window
9-8

Description
This counter counts the number of standstill of DL sending window after DL EGPRS TBF
establishment.
Usage
This counter is used to find out the number of standstill of DL EGPRS TBF sending window.
Measurement Point
The counter increments when sending window is detected to standstill during RLC block
sending to BTS from BSC. The measurement point is A, as shown in Figure 9-12.
Figure 9-12 Measurement Point Of Number Of Standstill Of GPRS DL TBF Sending

Window
Unit
Times
9.11 C901030090 Number of increment of DL coding

mode
Definition
Number of increment of DL coding mode
Description
BSC will adjust DL coding scheme based on measurement report when sending DL RLC
blocks to BTS. This counter counts the number of DL coding scheme increase.
Usage
This counter is used to find out the increase of DL RLC block coding scheme.
9-9

Measurement Point
The counter increments when coding scheme of DL RLC blocks sending to BTS from BSC
is increased. The measurement point is A as shown in Figure 9-13 (for EDGE) and Figure
9-14 (for GPRS).
Figure 9-13 Measurement Point Of Number Of Increment Of DL Coding Mode (EDGE

RLC Block)
Figure 9-14 Measurement Point Of Number Of Increment Of DL Coding Mode (GPRS

RLC Block)
Unit
Times
Related Features
ZGB-03-05-012 GPRS Link Adaptation
ZGO-03-05-002 EGPRS Link Adaptation
9-10

9.12 C901030091 Number of 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 number of DL coding scheme decrease.
Usage
This counter is used to find out the decrease of DL RLC block coding scheme.
Measurement Point
The counter increments when coding scheme of DL RLC blocks sending to BTS from BSC
is decreased. The measurement point is A as shown in Figure 9-15 (for EDGE) and Figure
9-16 (for GPRS).

RLC Block)
9-11


RLC Block)
Unit
Times
Related Features
9.13 C901030092 Number of increment of UL coding

mode
Definition
Number of increment of UL coding mode
Description
BSC will adjust UL coding scheme based on measurement report when sending UL RLC
blocks to BTS. This counter counts the number of UL coding scheme increase.
Usage
This counter is used to find out the increase of UL RLC block coding scheme.
Measurement Point
The counter increments when coding scheme of UL RLC blocks is increased. The
9-12

Figure 9-17 Measurement Point Of Number Of Increment Of UL Coding Mode
Unit
Times
Related Features
9.14 C901030093 Number of 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 number of UL coding scheme decrease.
Usage
This counter is used to find out the decrease of UL RLC block coding scheme.
Measurement Point
The counter increments when coding scheme of UL RLC blocks sending to BTS from BSC
is decreased. The measurement point is A, as shown in Figure 9-18.
9-13

Unit
Times
Related Features
9.15 C901030094 Number of conversion from GMSK

to 8PSK
Definition
Number of conversion from GMSK to 8PSK
Description
This counter counts the number of the handover of modulation mode from GMSK to 8PSK.
Usage
This counter is used to find out the number of the handover from GMSK to 8PSK of RLC
data block .
Measurement Point
The counter increments When coding scheme of RLC block is changed from GMSK to
8PSK (MCS5~MCS9). The measurement point is A, as shown in Figure 9-19, Figure 9-20,
and Figure 9-21.
9-14


RLC Block)

RLC Block)
9-15

Unit
Times
Related Features
9.16 C901030095 Number of conversion from 8PSK to

GMSK
Definition
Number of conversion from 8PSK to GMSK
Description
This counter counts the number of the handover of modulation mode from 8PSK to GMSK.
Usage
This counter is used to find out the number of the handover from 8PSK to GMSK of RLC
data block.
Measurement Point
The counter increments when coding scheme of RLC block is changed from 8PSK to
GMSK (from MCS5~MCS9 to other). The measurement point is A, as shown in Figure
9-22, Figure 9-23, and Figure 9-24.

RLC Block)
9-16


RLC Block)
Unit
Times
Related Features
9.17 C901030153 Number of 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
9-17

data blocks are received correctly, then the coding mode is upgraded by one level. This
counter counts the number of times that the downlink GPRS coding mode is upgraded.
Usage
This counter is used to find out the condition of downlink RLC block's coding mode being
upgraded.
This counter is supported in version V6.20.200a or above.
Measurement Point
When the coding mode of downlink RLC block sent to BTS from BSC is upgraded, the
Figure 9-25 Measurement Point of Downlink GPRS RLC Block Coding Mode Adjustment
Unit
Times
9.18 C901030154 Number of decrement of GPRS DL

coding mode
Description
In GPRS service, when BSC sends the downlink RLC block to BTS, the downlink coding
mode (Cn Xn Nn) is adjusted according to the receiving condition. In Nn data blocks, if Xn
data blocks are lost, then the coding mode is degraded by one level. This counter counts
the number of times that the downlink GPRS coding mode is degraded.
Usage
degraded.
9-18

Measurement Point
When the coding mode of downlink RLC block sent to BTS from BSC is degraded, the
counter increments.
Unit
Times
9.19 C901030155 Number of 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 Point
When the coding mode of uplink RLC block received by BSC is upgraded, the counter
Figure 9-26 Measurement Point of Uplink RLC Block Coding Mode Adjustment
Unit
Times
9-19

9.20 C901030156 Number of decrement of GPRS UL

coding mode
Description
uplink coding mode is degraded.
Usage
This counter is used to find out the condition of uplink coding mode being degraded.
Measurement Point
When the coding mode of uplink RLC block received by BSC is degraded, the counter
increments.
Unit
Times
9.21 C901030157 Number of increment of EGPRS DL

coding mode
Description
When BSC sends the downlink RLC block to BTS, the downlink coding mode is adjusted
downlink coding mode is upgraded.
Usage
upgraded.
Measurement Point
When the coding mode of downlink RLC block sent to BTS from BSC is upgraded, the
9-20

Figure 9-27 Measurement Point of Downlink EDGE RLC Block Coding Mode Adjustment
Unit
Times
9.22 C901030158 Number of decrement of EGPRS DL

coding mode
Description
When BSC sends the downlink RLC block to BTS, the downlink coding mode is adjusted
downlink coding mode is degraded.
Usage
degraded.
Measurement Point
When the coding mode of downlink RLC block sent to BTS from BSC is degraded, the
counter increments.
Unit
Times
9-21

9.23 C901030159 Number of increment of EGPRS UL

coding mode
Description
uplink coding mode is upgraded.
Usage
This counter is used to find out the condition of uplink coding mode being upgraded.
Measurement Point
When the coding mode of uplink RLC block received by BSC is upgraded, the counter
Figure 9-28 Measurement Point of Uplink RLC Block Coding Mode Adjustment
Unit
Times
9.24 C901030160 Number of decrement of EGPRS UL

coding mode
Description
uplink coding mode is degraded.
9-22

Usage
This counter is used to find out the condition of uplink coding mode being degraded.
Measurement Point
When the coding mode of uplink RLC block received by BSC is degraded, the counter
increments.
Unit
Times
9-23

9-24

Chapter 10
PS Resource Used Statistic
Measurement
Table of Contents
Overview ..................................................................................................................10-2
C901040001 Maximum number of Abis TS used......................................................10-2
C901040002 Average number of Abis TS used ........................................................10-3
C901040004 Average number of unavailable PDCH ................................................10-3
C901040005 Number of available static PDCH ........................................................10-3
C901040006 Number of unavailable static PDCH ....................................................10-4
C901040009 Time of DL PDCH congestion..............................................................10-5
C901040010 Time of UL PDCH congestion..............................................................10-5
C901040011 Time of PDCH used at least one UL/DL TBF exists .............................10-6
C901040012 Time of PDCH used at least one UL/DL EGPRS TBF exists................10-7
C901040013 Time of PDCH used at least one DL TBF exists ..................................10-8
C901040014 Time of PDCH used at least one UL TBF exists ..................................10-9
C901040018 Number of immediate assignment on AGCH .......................................10-9
C901040019 Number of paging PS requests on PCH ............................................ 10-11
C901040020 Number of paging CS requests on PCH ............................................ 10-11
C901040021 Number of immediate assignment on PCH ........................................10-12
C901040022 Number of immediate assignment on PAGCH ...................................10-13
C901040023 Number of paging PS requests on PPCH ..........................................10-14
C901040024 Number of paging CS requests on PPCH ..........................................10-15
C901040025 Number of immediate assignment on PPCH......................................10-16
C901040026 Number of Packet Channel Request on PRACH ...............................10-17
C901040027 Sum of Abis TS used sampling..........................................................10-18
C901040028 Number of Abis TS used sampling ....................................................10-18
C901040029 Sum of PDCH used sampling ............................................................10-19
C901040030 Number of PDCH used sampling.......................................................10-19
C901040031 Maximum value of Abis TS used to CS..............................................10-20
C901040032 Minimum value of Abis TS used to CS...............................................10-20
C901040033 Total value of the regular sampling used to CS ..................................10-21
C901040034 Number of sampling of CS ................................................................10-21
C901040035 Maximum value of Abis TS used to PS..............................................10-22
C901040036 Minimum value of Abis TS used to PS...............................................10-22
C901040037 Total value of the regular sampling used to PS ..................................10-23
C901040038 Number of sampling of PS.................................................................10-24
C901040039 MAX CS used number of exclusive ABIS ..........................................10-24
10-1

C901040040 MIN CS used number of exclusive ABIS............................................10-25

C901040041 MAX PS used number of exclusive ABIS...........................................10-25
C901040042 MIN PS used number of exclusive ABIS............................................10-26
C901040043 Average Number of GPRS User ........................................................10-26
C901040044 Maximum number of GPRS User ......................................................10-27
C901040045 Average Number of EGPRS User......................................................10-27
C901040046 Maximum number of EDGE User ......................................................10-28
C901040047 Number of assigned uplink radio channels ........................................10-28
C901040048 Number of assigned downlink radio channels....................................10-29
C901040049 Number of requested uplink radio channels.......................................10-29
C901040050 Number of requested downlink radio channels ..................................10-30
C901040051 Number of PS channel expand..........................................................10-30
C901040052 Number of PS channel expand perform.............................................10-30
C901040053 Number of PS channel expand success ............................................10-31
10.1 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.
10.2 C901040001 Maximum number of Abis TS used

Description
This counter counts the maximum number of Abis TS used under TDM connection
between cell and site during measurement period. The counter value reflects the instant
Abis resource occupation and maximum busyness.
Usage
This counter is used to find out the current cells requirements for Abis resource, which
helps to adjust or expand Abis resource.
Measurement Point
Inquire the database when periodic measurement data report to get the counter value.
Unit
Times
10-2

Chapter 10 PS Resource Used Statistic Measurement
10.3 C901040002 Average number of Abis TS used

Definition
Average number of Abis TS used
Description
This counter counts the average number of Abis TS used under TDM connection between
cell and site during measurement period.
Usage
This counter is used to find out the Abis resource occupation by the current cell, which
helps to adjust or expand Abis resource.
Measurement Point
Unit
Times
10.4 C901040004 Average number of unavailable PDCH

Description
This counter counts the number of PDCHs that are not assigned normally, including
blocked dynamic PDCHs due to various causes and static PDCHs.
Usage
This counter is used to find out the number of unavailable PDCHs, which helps to find out
the trouble cause and make troubleshooting in time.
Measurement Point
Unit
Times
10.5 C901040005 Number of available static PDCH

Definition
Number of available static PDCH
10-3

Description
iBSC supports dynamic wireless channels. This counter counts the number of available
PDCHs configured through OMCR in the current cell.
Usage
This counter is used to find out the number of available static PDCHs in the current cell,
which helps to make troubleshooting.
Measurement Point
Unit
Times
Related Features
ZGB-03-02-005 GPRS-only (without voice) Timeslots Configurable
ZGO-03-02-010 GPRS and EGPRS Channels Allocated Separately
10.6 C901040006 Number of unavailable static PDCH

Definition
Number of unavailable static PDCH
Description
iBSC supports dynamic wireless channels. This counter counts the number of unavailable
PDCHs configured via OMCR in the current cell.
Usage
This counter is used to find out the number of unavailable static PDCHs in the current cell,
which helps to make troubleshooting.
Measurement Point
Unit
Times
Related Features
ZGB-03-02-005 GPRS-only (without voice) Timeslots Configurable
10-4


10.7 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 calculation repeats.
When getting the periodic measurement value, if the congestion label is set, such
calculation repeats. The accumulation of these calculations makes the total time of DL
PDCH congestion.
Usage
This counter is used to find out the busyness of DL PDCH, which may be used as a
reference for whether more PDCHs should be configured.
Measurement Point
The measurement is taken at three time points listed below:
l Before DL PDCH attempts to occupy, if the congestion label is set, this counter
calculates the congestion time and accumulates them.
l Before DL PDCH is released, if the congestion label is set, this counter calculates
the congestion time and accumulates them.
l When reporting the measurement data periodically, if the congestion label is set, this
counter calculates the congestion time and accumulates them.
Unit
Second
10.8 C901040010 Time of UL PDCH congestion

Definition
Time of UL PDCH congestion
10-5

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 calculation repeats.
When getting the periodic measurement value, if the congestion label is set, such
calculation repeats. The accumulation of these calculations makes the total time of UL
PDCH congestion.
Usage
This counter is used to find out the busyness of UL PDCH, which may be used as a
Measurement Point
l Before UL PDCH attempts to occupy, if the congestion label is set, this counter
calculates the congestion time and accumulates them.
l Before UL PDCH is released, if the congestion label is set, this counter calculates
the congestion time and accumulates them.
l When reporting the measurement data periodically, if the congestion label is set, this
counter calculates the congestion time and accumulates them.
Unit
Second
10.9 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.
10-6

Usage
This counter is used to find out the using of PDCHs, which may be used as a reference
for whether more PDCHs should be configured.
Measurement Point
l When PDCH resource is acquired successfully, this counter calculates and
accumulates.
l When PDCH resource is released, this counter calculates and accumulates.
l When reporting the measurement data periodically, this counter calculates and
accumulates.
Unit
Second
Related Features
10.10 C901040012 Time of PDCH 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 may be used as a
Measurement Point
accumulates.
accumulates.
10-7

Unit
Second
Related Features
10.11 C901040013 Time of PDCH used at least one DL

TBF exists
Definition
Time of PDCH used at least one DL TBF exists
Description
When there is at least one DL TBF in one PDCH, this PDCH is regarded to be used. This
counter counts the time of PDCH used by DL. The value of the counter reflects the PDCH
traffic.
Usage
Measurement Point
accumulates.
accumulates.
Unit
Second
Related Features
10-8

10.12 C901040014 Time of PDCH used at least one UL

TBF exists
Definition
Time of PDCH used at least one UL TBF exists
Description
When there is at least one UL TBF in one PDCH, this PDCH is regarded to be used. This
counter counts the time of PDCH used by UL. The value of the counter reflects the PDCH
traffic.
Usage
Measurement Point
accumulates.
accumulates.
Unit
Second
Related Features
10.13 C901040018 Number of 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.
10-9

Usage
This counter is used to find out the frequency of sending Imm Assign message on AGCH
by BSC in the current cell.
Measurement Point
If BSC starts UL single block or UL TBF channel assignment, when non-DRX MS assigns
DL TBF, the counter increments. The measurement points are A1 and A2 as shown in
Figure 10-1 Sending Instant Assignment Message By AGCH Channel (1)
Figure 10-2 Sending Instant Assignment Message By AGCH Channel (2)
Unit
Times
10-10

10.14 C901040019 Number of paging PS requests on

PCH
Definition
Number of paging PS requests on PCH
Description
This counter counts the number of Paging PS message sent on PCH by BSC.
Usage
This counter is used to find out the frequency of sending Paging PS message on PCH by
BSC in the current cell.
Measurement Point
When BSC sends Paging PS message on PCH, the counter increments. The
measurement point is A as shown in Figure 10-3.
Figure 10-3 Sending PS Paging By PCH Channel
Unit
Times
Related Features
10.15 C901040020 Number of paging CS requests on

PCH
Definition
Number of paging CS requests on PCH
10-11

Description
This counter counts the number of Paging CS message sent on PCH by BSC.
Usage
This counter is used to find out the frequency of sending Paging CS message on PCH by
BSC in the current cell.
Measurement Point
When BSC sends Paging CS message on PCH, the counter increments. The
measurement point is A as shown in Figure 10-4.
Figure 10-4 SENDING CS PAGING BY PCH CHANNEL
Unit
Times
Related Features

on PCH
Definition
Number of immediate assignment on PCH
Description
This counter counts the number of Imm Assign message sent on PCH by BSC.
10-12

Usage
This counter is used to find out the frequency of sending Imm Assign message on PCH
Measurement Point
If BSC starts to establish DL TBF, when DRX MS sends Imm Assign message on PCH,
the counter increments. The measurement point is A2, as shown in Figure 10-5.
Figure 10-5 Sending Instant Assignment Message By AGCH Channel
Unit
Times

on PAGCH
Definition
Number of immediate assignment on PAGCH
Description
This counter counts the number of Imm Assign message sent on PAGCH by BSC.
Usage
This counter is used to find out the frequency of sendingImm Assign message on PAGCH
Measurement Point
If BSC starts UL single block or UL TBF channel assignment, when non-DRX MS assigns
DL TBF, the counter increments. The measurement points are A1 and A2, as shown in
Figure 10-6and Figure 10-7.
10-13

Figure 10-6 Sending Assignment Message By PAGCH Channel (1)
Figure 10-7 Sending Assignment Message By PAGCH Channel (2)
Unit
Times
10.18 C901040023 Number of 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.
10-14

Usage
This counter is used to find out the frequency of sending Paging PS message on PPCH
Measurement Point
When BSC sends Paging PS message on PPCH, the counter increments. The
Figure 10-8 Sending PS Paging By PCH ChanneL
Unit
Times
Related Features
10.19 C901040024 Number of paging CS requests on

PPCH
Definition
Number of CS paging requests on PPCH
Description
This counter counts the number of Paging CS message sent on PPCH by BSC.
Usage
This counter is used to find out the frequency of sending Paging CS message on PPCH
Measurement Point
When BSC sends Paging CS message on PPCH, the counter increments. The
10-15

Figure 10-9 Sending CS Paging By PCH Channel
Unit
Times
Related Features

on PPCH
Definition
Number of immediate assignment on PPCH
Description
This counter counts the number of Imm Assign message sent on PPCH by BSC.
Usage
This counter is used to find out the frequency of sending Imm Assign message on PPCH
Measurement Point
If BSC starts to establish DL TBF, when DRX MS sends Imm Assign message on PPCH,
the counter increments. The measurement point is A2, as shown in Figure 10-10.
10-16

Figure 10-10 Sending Assignment Message By PAGCH Channel
Unit
Times
10.21 C901040026 Number of 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 Point
When BSC receives EGPRS Packet Channel Request message or Packet Channel
Request message, the counter increments. The measurement point is A, as shown in
Figure 10-11.
Figure 10-11 Number Of Packet Channel Requests On PRACH
10-17

Unit
Times
10.22 C901040027 Sum of Abis TS used sampling

Definition
Sum of Abis TS used sampling
Description
This counter counts the total number of used Abis TS under TDM connection between
BSC and BS.
Usage
This counter is used to find out the sum of Abis TS used sampling. It is one of the
parameters to observe the Abis TS using.
Measurement Point
When the database of BSC starts to assign Abis TS, the counter accumulates.
Unit
Times
10.23 C901040028 Number of Abis TS used sampling

Definition
Number of Abis TS used sampling
Description
This counter counts the number of Abis TS assignments by database.
Usage
This counter is used to find out the frequency of Abis TS assignment sampling. It is one
of the parameters to observe the Abis TS using.
Measurement Point
When the database assigns Abis TS, the counter increments.
Unit
Times
10-18

10.24 C901040029 Sum of PDCH used sampling

Definition
Sum of PDCH used sampling
Description
This counter counts the sum of PDCHs assigned by database when service processing
module starts PS channel request.
Usage
This counter is used to find out the sum of PDCHs assigned by database when service
processing module starts PS channel request. It is one of the parameters to observe
multi-TS using when assigning PS channels in the current cell.
Measurement Point
When service processing module starts PS channel request and database assigns PDCH,
Unit
Times
10.25 C901040030 Number of PDCH used sampling

Definition
Number of PDCH used sampling
Description
This counter counts the number of PDCH assigning attempts by database when service
processing module starts PS channel request.
Usage
This counter is used to find out the frequency of PDCH assigning by database when service
processing module starts PS channel request. It is one of the parameters to observe
multi-TS using when assigning PS channels in the current cell.
Measurement Point
When service processing module starts PS channel request and database assigns PDCH,
10-19

Unit
Times
10.26 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-access sites, it counts the maximum bandwidth occupied
by CS service. This counter reflects the transcient occupation and the busiest level of Abis
resource in the cell's CS service.
Usage
This counter is used to find out the Abis resource occupation in the cell's CS service, which
helps adjust the usage of Abis resource.
Measurement Point
The counter counts when CS user requests for the Abis resource successfully.
Unit
Number of (TDM access)/kbps (IP access)
10.27 C901040032 Minimum value of Abis TS used to

CS
Definition
Minimum value of Abis TS used to CS
Description
This counter counts the minimum value of Abis timeslot used in CS service in the cell within
the measurement period; for IP-access sites, it counts the minimum bandwidth occupied
by CS service.
Usage
This counter is used to find out the Abis resource occupation in the cell's CS service, which
10-20

Measurement Point
The counter counts when CS user requests for the Abis resource successfully or releases
the Abis resource successfully.
Unit
10.28 C901040033 Total value of the regular sampling

used to CS
Definition
Total value of the regular sampling used to CS
Description
The counter accumulates at each measurement point. It counts the accumulated Abis
timeslot used by CS service within the measurement period; for IP-access sites, it counts
the accumulated bandwidth occupied by CS service. With this counter and C901040034,
the system can get the average usage of Abis resource occupied by CS service within the
measurement period.
Usage
This counter reflects the average occupation of Abis resource in CS service.
Measurement Point
The counter accumulates when CS user requests for the Abis resource successfully or
releases the Abis resource successfully.
Unit
10.29 C901040034 Number of 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.
10-21

Usage
This counter reflects the average occupation of Abis resource in CS service.
Measurement Point
The counter accumulates when CS user requests for the Abis resource successfully or
Unit
10.30 C901040035 Maximum value of Abis TS used to

PS
Definition
Maximum value of Abis TS used to PS
Description
This counter counts the maximum value of Abis timeslot used in PS service in the cell within
the measurement period; for IP-access sites, it counts the maximum bandwidth occupied
by PS service. This counter reflects the transcient occupation and the busiest level of Abis
resource in the cell's PS service.
Usage
This counter is used to find out the Abis resource occupation in the cell's PS service, which
Measurement Point
The counter counts when PS user requests for the Abis resource successfully.
Unit
10.31 C901040036 Minimum value of Abis TS used to

PS
Definition
Minimum value of Abis TS used to PS
10-22

Description
This counter counts the minimum value of Abis timeslot used in PS service in the cell within
the measurement period; for IP-access sites, it counts the minimum bandwidth occupied
by PS service.
Usage
This counter is used to find out the Abis resource occupation in the cell's PS service, which
Measurement Point
The counter counts when PS user requests for the Abis resource successfully or releases
the Abis resource successfully.
Unit
10.32 C901040037 Total value of the regular sampling

used to PS
Definition
Total value of the regular sampling used to PS
Description
The counter accumulates at each measurement point. It counts the accumulated Abis
timeslot used by PS service within the measurement period; for IP-access sites, it counts
the accumulated bandwidth occupied by PS service. With this counter and C901040038,
the system can get the average usage of Abis resource occupied by PS service within the
measurement period.
Usage
This counter reflects the average occupation of Abis resource in PS service.
Measurement Point
The counter accumulates when PS user requests for the Abis resource successfully or
Unit
10-23

10.33 C901040038 Number of sampling of PS

Definition
Number of sampling of PS
Description
C901040037 reflect the average occupation of Abis resource in the cell's PS service.
Usage
This counter reflects the average occupation of Abis resource in PS service.
Measurement Point
The counter accumulates when PS user requests for the Abis resource successfully or
Unit
10.34 C901040039 MAX CS used number of exclusive

ABIS
Description
This counter counts the maximum number of Abis timeslots occupied by CS service in the
cell. Upon the request of releasing CS channel, the system checks the total number of
Abis timeslots occupied by CS service in the cell. If the number is larger than the current
value, then update the value.
Usage
This counter is used to find out the usage of Abis timeslots occupied by CS service in the
cell.
Measurement Point
The counter counts upon channel conversion due to request of releasing CS channel and
refreshing dynamic CS channel.
10-24

10.35 C901040040 MIN CS used number of exclusive

ABIS
Description
This counter counts the minimum number of Abis timeslots occupied by CS service in the
cell. Upon the request of releasing CS channel, the system checks the total number of
Abis timeslots occupied by CS service in the cell. If the number is less than the current
Usage
This counter is used to find out the usage of Abis timeslots occupied by CS service in the
cell.
Measurement Point
The counter counts upon channel conversion due to request of releasing CS channel and
refreshing dynamic CS channel.
10.36 C901040041 MAX PS used number of exclusive

ABIS
Description
This counter counts the maximum number of Abis timeslots occupied by PS service in the
cell. Upon the request of releasing PS channel, the system checks the total number of
Abis timeslots occupied by PS service in the cell. If the number is larger than the current
Usage
This counter is used to find out the usage of Abis timeslots occupied by PS service in the
cell.
Measurement Point
The counter counts upon channel conversion due to request of releasing PS channel and
refreshing dynamic PS channel.
10-25

10.37 C901040042 MIN PS used number of exclusive

ABIS
Description
This counter counts the minimum number of Abis timeslots occupied by PS service in the
cell. Upon the request of releasing PS channel, the system checks the total number of
Abis timeslots occupied by PS service in the cell. If the number is less than the current
Usage
This counter is used to find out the usage of Abis timeslots occupied by PS service in the
cell.
Measurement Point
The counter counts upon channel conversion due to request of releasing PS channel and
refreshing dynamic PS channel.
10.38 C901040043 Average Number of GPRS User

Description
This counter counts the average number of GPRS users in the cell and site within the
measurement period.
Usage
This counter is used to find out the average number of GPRS users in current cell.
Measurement Point
The counter counts in the four following cases.
1. The counter increments after one phase access receives the indication message.
2. The counter increments after two phase access sends the resource request to user
plane.
3. The counter increments after it receives downlink assignment requests.
4. The counter decrements while RANPS instance is released.
Unit
Times
10-26

10.39 C901040044 Maximum number of GPRS User

Description
This counter counts the maximum number of GPRS users in the cell and site within the
measurement period.
Usage
This counter is used to find out the maximum number of GPRS users in current cell within
the measurement period.
Measurement Point
For the counter C901040043, if the maximum number of users is less than the average
number of users, use the average number of users to update the maximum number of
users. Otherwise, it is kept unchanged.
Unit
Times
10.40 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 users in current cell within
Measurement Point
1. The counter increments after one phase access receives the indication message.
2. The counter increments after two phase access sends the resource request to user
plane.
3. The counter increments after it receives downlink assignment requests.
4. The counter decrements while RANPS instance is released.
Unit
Times
10-27

10.41 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 users in current cell within
Measurement Point
For the counter C901040043, if the maximum number of users is less than the average
number of users, use the average number of users to update the maximum number of
users. Otherwise, it is kept unchanged.
Unit
Times
10.42 C901040047 Number of assigned uplink radio

channels
Description
This counter counts the number of assigned uplink radio channels in the cell and site within
Usage
This counter counts the number of assigned uplink radio channels in the cell and site within
Measurement Point
1. Counts in single allocated resource block
2. Counts in allocated radio resource
3. Counts in uplink DTM assignment
4. Counts in downlink DTM assignment
Unit
Times
10-28

10.43 C901040048 Number of assigned downlink radio

channels
Description
This counter counts the number of assigned downlink radio channels in the cell and site
within the measurement period.
Usage
This counter counts the number of assigned downlink radio channels in the cell and site
Measurement Point
The counter counts in the following three cases.
1. Counts in allocated radio resource

2. Counts in uplink DTM assignment
3. Counts in downlink DTM assignment
Unit
Times
10.44 C901040049 Number of requested uplink radio

channels
Description
This counter counts the number of requested uplink radio channels in the cell and site
Usage
This counter counts the number of requested uplink radio channels in the cell and site
Measurement Point
Consistent with that for C901040047.
Unit
Times
10-29

10.45 C901040050 Number of requested downlink radio

channels
Description
This counter counts the number of requested downlink radio channels in the cell and site
Usage
This counter counts the number of requested downlink radio channels in the cell and site
Measurement Point
Consistent with that for C901040048.
Unit
Times
10.46 C901040051 Number of PS channel expand

Description
This counter counts the number of attempts of channel expansion in PS service.
Usage
This counter is used to find out the frequency of channel expansion initiated by database.
Measurement Point
The counter counts when the RANUMC module receives the EV_DBS_PSCHANEXPAND
message.
Unit
Times

perform
Description
This counter counts the number of channel expansions in PS service.
10-30

Usage
This counter is used to find out the number of channel expansions executed by RANPS.
Measurement Point
This counter counts when the RANPS module receives the
EV_RANUMC_PSCHANEXPAND message.
Unit
Times

success
Description
This counter counts the number of successful channel expansions in PS service.
Usage
This counter is used to find out the number of successful channel expansions executed by
RANPS.
Measurement Point
This counter counts when the RANPS module successfully requests the resource for
expansion from database.
Unit
Times
10-31

10-32

Chapter 11
RMM Assignment
Measurement
Table of Contents
Overview ..................................................................................................................11-3
C901050001 Number of general assignment executions for voice channel...............11-3
C901050002 Number of assignments attempts for voice due to forced release ........11-4
C901050003 Number of assignment executions for voice channel due to forced
release .....................................................................................................................11-5
C901050004 Number of handover attempts for voice due to forced release .............11-6
C901050005 Number of handover executions for voice channel due to forced
release .....................................................................................................................11-7
C901050006 Number of assignments for voice channel due to queuing ...................11-8
C901050007 Number of assignments for execution for voice channel due to
queuing .................................................................................................................. 11-10
C901050008 Duration of assignment success voice channel due to queuing ......... 11-11
C901050009 Number of assignments success for voice channel due to queuing ... 11-12
C901050010 Number of assignments for directed retry attempts for voice channel . 11-13
C901050011 Number of assignments for execution for voice channel due to
directed retry .......................................................................................................... 11-14
C901050012 Number of general assignments for execution for data ...................... 11-15
C901050013 Number of assignments attempts for data due to forced release ....... 11-16
C901050014 Number of assignment executions for data due to forced release ...... 11-17
C901050015 Number of handover attempts for data due to forced release ............ 11-18
C901050016 Number of handover executions for data due to forced release ......... 11-19
C901050017 Number of assignments attempts for data due to queuing ................. 11-20
C901050018 Number of assignments for execution for data due to queuing........... 11-22
C901050019 Total duration of successful assignments for data due to queuing...... 11-23
C901050020 Number of assignments success for data due to queuing .................. 11-24
C901050021 Number of assignments attempts for data due to directed retry ......... 11-24
C901050022 Number of assignment executions for data due to directed retry........ 11-26
C901050023 Number of assignment for retry attempts FDD cell for voice channel . 11-27
C901050024 Number of assignment executions for data due to directed retry to
FDD cell for voice channel...................................................................................... 11-28
C901050025 Number of assignment for retry attempts FDD cell for data................ 11-29
FDD cell for data .................................................................................................... 11-30
C901050027 Number of assignment for retry attempts TDD cell for voice channel . 11-31
11-1


TDD cell for voice channel...................................................................................... 11-33
C901050029 Number of assignment for retry attempts TDD cell for data................ 11-34
TDD cell for data .................................................................................................... 11-35
C901050031 Assignment unsuccessful due to circuit obstruction ........................... 11-36
C901050032 Assignment unsuccessful due to circuit obstruction unmatched......... 11-37
C901050033 Assignment unsuccessful due to no valid radio resource ................... 11-38
C901050034 Assignment unsuccessful due to other causes .................................. 11-39
C901050035 Number of assignments attempts due to forced release (emergency
service) .................................................................................................................. 11-40
C901050036 Number of assignment executions channel due to forced release
(emergency service)............................................................................................... 11-41
C901050037 Number of assignment attempts due to forced handover (emergency
service) .................................................................................................................. 11-42
C901050038 Number of assignment executions channel due to forced handover
C901050039 Number of assignments channel due to queuing (emergency
service) .................................................................................................................. 11-44
C901050040 Number of assignments for execution channel due to queuing
C901050041 Number of forced handover target not found (assignment forced
handover)............................................................................................................... 11-46
C901050042 Number of send forced handover request to lower PRI user
(assignment forced handover) ................................................................................ 11-47
C901050043 Number of received failure from lower PRI user request resource for
forced handover (assignment forced handover)...................................................... 11-49
C901050044 Number of lower PRI user handover failure (assignment forced
handover)............................................................................................................... 11-50
C901050045 Number of time out for wait resource (assignment forced handover) . 11-51
C901050046 Number of forced release target not found (assignment forced
release) .................................................................................................................. 11-52
C901050047 Number of time out for wait resource (assignment forced release)..... 11-53
C901050048 Number of get before grab released channel (assignment forced
handover)............................................................................................................... 11-54
C901050049 Number of get before grab released channel(assignment forced
release) .................................................................................................................. 11-55
C901050050 The count of Assignment using FULL IP A-Interface.......................... 11-56
C901050051 The count of Assignment using PCM over IP A-Interface................... 11-57
C901050052 The count of Assignment using PCM over TDM A-Interface ............. 11-58
C901050053 The count of Assignment Failure caused by "Requested Codec Type
or Codec Configuration not supported" ................................................................... 11-59
C901050054 The count of Assignment Failure caused by "Requested Codec Type
or Codec Configuration unavailable"....................................................................... 11-60
11-2

Chapter 11 RMM Assignment Measurement
C901050055 The count of Assignment Failure caused by "Requested A-Interface

Type not supported" ............................................................................................... 11-61
C901050056 The count of Assignment Failure caused by "Requested A-Interface
Type unavailable" ................................................................................................... 11-62
C901050057 The count of Assignment Failure caused by "Call Identifier already
allocated" ............................................................................................................... 11-63
C901050058 The count of Assignment Failure caused by "Requested Redundancy
Level not supported"............................................................................................... 11-64
C901050059 The count of Assignment Failure caused by "Call Access Control" .... 11-65
C901050060 Attempt Number of mode modify for assignment ............................... 11-66
C901050061 Success Number of mode modify for assignment .............................. 11-67
11.1 Overview
RMM assignment counter describers the assignment process. As many attempts can be
made if no channel is available in the first assignment attempt, it is necessary to make
a completed description of the whole assignment process instead of the assignment
processes of TCH/F or TCH/H. These counters are used to analyze influences of forced
release, queuing and directed retry, to assignment success rate from the viewpoint of
calling.
11.2 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 resource.
Measurement Point
In voice channel assignment flow, the counter increments when source cell receives
message that resource is available from target cell after sending channel request, and
successfully sends assignment command. The measurement point is A, as shown in
Figure 11-1.
11-3

Figure 11-1 Measurement Point Of General Assignment Executions
Unit
Times
11.3 C901050002 Number of assignments attempts for

voice due to forced release
Definition
Number of assignments attempts for voice due to forced release
Description
BSC attempts to allocate voice channel after receiving Radio App message in
assignment flow; if there is no proper channel available and the system allows forced
release, then BSC carries out forced release to other channels. This counter counts the
number of forced release.
Usage
This counter is used to find out the number of assignments for forced release attempts in
MS accessing process.
Measurement Point
BSC fails in allocating channel due to no available resource. It releases other channels
forcedly when the system allows.
l 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.
l 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 11-2.
11-4

Figure 11-2 Measurement Point Of Assignments For Forced Release Attempts
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
11.4 C901050003 Number of assignment executions

for voice channel due to forced release
Definition
Number of assignment executions for voice channel due to forced release
Description
BSC fails in allocating voice channel due to no available resource and carries out forced
release; if BCS gets required channel in time, then the forced release succeeds. This
counter counts the number of assignment executions for voice channel due to forced
release.
Usage
This counter is used to find out the number of assignment executions for voice channel
due to forced release in MS accessing process.
Measurement Point
The counter increments if radio resource request fails in voice channel assignment, forced
released can be carried out and instance of forcing release sends forced release
11-5

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
11-3.
Figure 11-3 Measurement point of assignment executions for voice channel due to
forced release
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
11.5 C901050004 Number of 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 channel for forced release
when it fails in voice channel allocation due to no available resource. The counter counts
the number of handover for forced release attempts for voice channel.
Usage
This counter is used to find out the number of handover for forced release attempts for
voice channel in MS accessing process.
11-6

Measurement Point
The counter increments when BSC fails in general voice channel assignment and the
system allows forced release and there is proper instance of forcing release that sends
forced release message to instance of forced release. The measurement point is A,
Figure 11-4 Measurement point of handover for forced release attempts
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
11.6 C901050005 Number of handover executions for

voice channel due to forced release
Definition
Number of handover executions for voice channel due to forced release
Description
BSC attempts to operate outgoing handover to the cell voice channel for forced release
when it fails in voice channel allocation due to no available resource. The counter counts
the number of handover executions for voice channel due to forced release.
11-7

Usage
This counter is used to find out the number of handover executions for voice channel due
to forced release in MS accessing process.
Measurement Point
The counter increments if radio resource request fails in voice channel assignment,
handover for voice channel due to forced release can be carried out and instance of
forcing handover sends forced handover message to instance of forced handover,
and resource available message is received and channel is obtained successfully.
The measurement point is B, as shown in Figure 11-5.
Figure 11-5 Measurement Point Of Handover Executions For Voice Channel Due To
Forced Release
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
11.7 C901050006 Number of assignments for voice

channel due to queuing
Definition
Number of assignments for voice channel due to queuing
11-8

Description
BSC attempts to assign voice channel after receiving Radio App message in assignment
flow; if there is no proper channel available and the system doesnt allow forced release or
cant find instance of forcing release but allows queuing, then the present instance queues
and waits till other resource releases. This counter counts the number of assignments for
queuing attempts for voice channel.
Usage
This counter is used to find out the number of assignments for queuing attempts for voice
channel in MS accessing process.
Measurement Point
The counter increments when BSC fails in general voice channel assignment and the
system allows queuing and the instance queues. The measurement point is A, as shown
in Figure 11-6.
Figure 11-6 Measurement Point Of Assignments For Queuing Attempts
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
11-9

11.8 C901050007 Number of assignments for execution

for voice channel due to queuing
Definition
Number of assignments for execution for voice channel due to queuing
Description
BSC fails in allocating voice channel due to no available resource and carries out queuing;
if BCS gets required channel in time, then the queuing succeeds. This counter counts the
number of assignments for execution for voice channel due to queuing.
Measurement Point
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 11-7.
Figure 11-7 Measurement Point Of Assignments for Execution for Voice Channel due to
Queuing
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
11-10

11.9 C901050008 Duration of assignment success

voice channel due to queuing
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 channel is the time when
channel is obtained minus the time when the instance began to queue. The counter
accumulates the total durations of successful assignment for queuing for voice channel.
Usage
This counter is used to check the intra-cell queuing status and represents whether queuing
can relieve traffic congestion effectively.
Measurement Point
The counter accumulates duration of successful assignment for queuing for voice channel
if radio resource request fails in voice channel assignment, queuing can be carried out
and instance of queuing receives resource available message and obtains channel
successfully. The measurement points are A and B, as shown in Figure 11-8.
Figure 11-8 Measurement Point Of Assignments For Execution For Voice Channel
Due To Queuing
Unit
Times
11-11

11.10 C901050009 Number of assignments success for

voice channel due to queuing
Definition
Number of assignments success for voice channel due to queuing
Description
This counter counts the number of successful assignments of queuing for voice channel.
Usage
Measurement Point
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 11-9.
Due To Queuing
Unit
Times
11-12

11.11 C901050010 Number of assignments for directed

retry attempts for voice channel
Definition
Number of assignments for directed retry attempts for voice channel
Description
If BSC fails in voice channel request, and source cell allows directed retry and target
cell that meets the directed retry demand can be selected from adjacent cells, then BSC
carries out directed retry. This counter counts the number of assignments for directed retry
attempts for voice channel.
Usage
This counter is used to find out the number of assignments for directed retry attempts
for voice channel and check whether the cells radio environment can satisfy the traffic
demand.
Measurement Point
The counter increments when source cell receives no available radio resource
message from target cell and source cell supports directed retry and target cell that meets
the directed retry demand can be found and Radio_App message is sent to target cell.
Figure 11-10 Measurement Point of Assignments for Directed Retry Attempts
Unit
Times
11-13

Related Features
ZGB-03-01-002 Directed Retry
ZGO-02-03-003 GERAN/UTRAN Load Sharing
11.12 C901050011 Number of assignments for

execution for voice channel due to directed retry
Definition
Number of assignments for execution for voice channel due to directed retry
Description
This counter counts the number of assignments for execution for voice channel due to
directed retry
Usage
This counter is used to check the process and result of directed retry.
Measurement Point
The counter increments when directed retry is carried out and target cell obtains channel
successfully and source cell receives radio resource available message from
target cell in voice channel assignment process. The measurement point is B, as shown
in Figure 11-11.
Figure 11-11 Measurement Point of Assignments for Execution for Voice Channel Due
to Directed Retry
11-14

Unit
Times
Related Features
11.13 C901050012 Number of 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 Point
In data channel assignment flow, the counter increments when source cell receives
resource is available message from target cell after sending channel request,
and successfully sends assignment command. The measurement point is A, as shown
in Figure 11-12.
Figure 11-12 Measurement Point Of General Assignment Executions
11-15

Unit
Times
11.14 C901050013 Number of assignments attempts

for data due to forced release
Definition
Number of assignments attempts for data due to forced release
Description
BSC attempts to allocate data channel after receiving Radio App message in assignment
flow; if there is no proper channel available and the system allows forced release, then BSC
carries out forced release to other channels. This counter counts the number of forced
release.
Usage
This counter is used to find out the number of assignments for forced release attempts in
MS accessing process.
Measurement Point
BSC fails in allocating channel due to no available resource and releases other channel
forcedly when the system allows.
l 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.
l 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 11-13.
11-16

Figure 11-13 Measurement Point Of Assignments For Forced Release Attempts
Unit
Times
Related Features
ZGO-01-03-001 eMLPP

for data due to forced release
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.
Usage
This counter is used to find out the number of assignment executions for data channel due
Measurement Point
The counter increments if radio resource request fails in data channel assignment, forced
released can be carried out and instance of forcing release sends forced release
11-17

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
11-14.
Figure 11-14 Measurement Point of Assignment Executions for Voice Channel due
to Forced Release
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
11.16 C901050015 Number of handover attempts for

data due to forced release
Definition
Number of handover attempts for data due to forced release
Description
BSC attempts to operate outgoing handover to the cell data channel for forced release
when it fails in data channel allocation due to no available resource. The counter counts
the number of handover for forced release attempts for data channel.
Usage
This counter is used to find out the number of handover for forced release attempts for
data channel in MS accessing process.
11-18

Measurement Point
The counter increments when BSC fails in general data channel assignment and the
system allows forced release and there is proper instance of forcing release that sends
forced release message to instance of forced release. The measurement point is A,
Figure 11-15 Measurement Point of Handover for Forced Release Attempts
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
11.17 C901050016 Number of handover executions for

data due to forced release
Definition
Number of handover executions for data due to forced release
Description
BSC attempts to operate outgoing handover to the cell data channel for forced release
when it fails in data channel allocation due to no available resource. The counter counts
the number of handover executions for data channel due to forced release.
11-19

Usage
This counter is used to find out the number of handover executions for data channel due
Measurement Point
The counter increments if radio resource request fails in data channel assignment,
handover for data channel due to forced release can be carried out and instance of
forcing handover sends forced handover message to instance of forced handover,
and resource availablemessage is received and channel is obtained successfully.
Figure 11-16 Measurement Point Of Handover Executions For Voice Channel Due
To Forced Release
Unit
Times
Related Features
ZGO-01-03-001 eMLPP

for data due to queuing
Definition
Number of assignments attempts for data due to queuing
11-20

Description
BSC attempts to assign data channel after receiving Radio App message in assignment
flow; if there is no proper channel available and the system doesnt allow forced release or
cant find instance of forcing release but allows queuing, then the present instance queues
and waits till other resource releases. This counter counts the number of assignments for
queuing attempts for data channel.
Usage
This counter is used to find out the number of assignments for queuing attempts for data
channel in MS accessing process.
Measurement Point
The counter increments when BSC fails in general data channel assignment and the
system allows queuing and the instance queues. The measurement point is A, as shown
in Figure 11-17.
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
11-21


execution 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.
Measurement Point
The counter increments if radio resource request fails in data channel assignment, queuing
can be carried out and instance of queuing receives resource available message
and obtains channel successfully. The measurement point is B, as shown in Figure 11-18.
Due To Queuing
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
11-22

11.20 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 channel is the time when
channel is obtained minus the time when the instance began to queue. The counter
accumulates the total durations of successful assignment for queuing for data channel.
Usage
Measurement Point
The counter accumulates duration of successful assignment for queuing for data channel
if radio resource request fails in data channel assignment, queuing can be carried out
and instance of queuing receives resource available message and obtains channel
successfully. The measurement points are A and B, as shown in Figure 11-19.
Due To Queuing
Unit
Times
11-23

11.21 C901050020 Number of assignments success

for data due to queuing
Description
This counter counts the number of successful assignments of queuing for data channel.
Usage
Measurement Point
The counter increments if radio resource request fails in data channel assignment, queuing
can be carried out and instance of queuing receives resource available message
and obtains channel successfully. The measurement point is B, as shown in Figure 11-20.
Due To Queuing
Unit
Times

for data due to directed retry
Definition
Number of assignments attempts for data due to directed retry
11-24

Description
If BSC fails in data channel request, and source cell allows directed retry and target cell that
meets the directed retry demand can be selected from adjacent cells, then BSC carries out
directed retry. This counter counts the number of assignments for directed retry attempts
for data channel.
Usage
This counter is used to find out the number of assignments for directed retry attempts for
data channel and check whether the cells radio environment can satisfy the traffic demand.
Measurement Point
The counter increments when source cell receives no available radio resource
message from target cell and source cell supports directed retry and target cell that meets
the directed retry demand can be found and Radio_App message is sent to target cell.
Unit
Times
Related Features
11-25


for 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 Point
The counter increments when directed retry is carried out and target cell successfully
obtains channel and source cell receives radio resource available message from
target cell in data channel assignment process. The measurement point is B, as shown in
Figure 11-22.
Figure 11-22 Measurement Point of Assignments for Execution for Voice Channel due
to Directed Retry
Unit
Times
Related Features
11-26

11.24 C901050023 Number of assignment for retry

attempts FDD cell for voice channel
Definition
Number of assignment for retry attempts FDD cell for voice channel
Description
This counter counts the number of assignment for retry attempts FDD cell for voice
channel.
Usage
This counter is used to find out the number of assignment for retry attempts FDD cell for
voice channel and represent FDD cell traffic sharing status in voice channel assignment.
Measurement Point
The counter increments in voice channel assignment when source cell receives no
available radio resource message from FDD cell and source cell supports
directed retry and FDD cell that meets the directed retry demand can be found and
Radio_App message is sent to FDD cell. The measurement point is A, as shown in
Figure 11-23.
Unit
Times
11-27

Related Features
ZGO-02-02-014 IMSI Based Handover
ZGO-02-03-002 GSM/WCDMA Interworking

for 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.
Usage
This counter is used to find out the number of assignment executions due to directed retry
to FDD cell for voice channel and represent FDD cell directed retry status.
Measurement Point
The counter increments in voice channel assignment when target cell in directed retry
is FDD cell and successfully obtains channel and source cell receives resource
available message from target cell. The measurement point is B, as shown in Figure
11-24.
11-28

to Directed Retry
Unit
Times
Related Features

attempts FDD cell for data
Definition
Number of assignment for retry attempts FDD cell for data
Description
This counter counts the number of assignment for retry attempts FDD cell for data channel.
Usage
This counter is used to find out the number of assignment for retry attempts FDD cell for
data channel and represent FDD cell traffic sharing status in data channel assignment.
11-29

Measurement Point
The counter increments in data channel assignment when source cell receives no
available radio resource message from FDD cell and source cell supports
directed retry and FDD cell that meets the directed retry demand can be found and
Radio_App message is sent to FDD cell. The measurement point is A, as shown
inFigure 11-25.
Unit
Times
Related Features

for data due to directed retry to FDD cell for data
Definition
Number of assignment executions for data due to directed retry to FDD cell for data
Description
This counter counts the number of assignment executions due to directed retry to FDD cell
for data channel.
11-30

Usage
to FDD cell for data channel and represent FDD cell directed retry status.
Measurement Point
The counter increments in data channel assignment when target cell in directed retry is
FDD cell and successfully obtains channel and source cell receives radio resource
11-26.
to Directed Retry
Unit
Times
Related Features

attempts TDD cell for voice channel
Definition
Number of assignment for retry attempts TDD cell for voice channel
11-31

Description
This counter counts the number of assignment for retry attempts TDD cell for voice
channel.
Usage
This counter is used to find out the number of assignment for retry attempts TDD cell for
voice channel and represent TDD cell traffic sharing status in voice channel assignment.
Measurement Point
The counter increments in voice channel assignment when source cell receives no
available radio resource message from TDD cell and source cell supports
directed retry and TDD cell that meets the directed retry demand can be found and
Radio_App message is sent to TDD cell. The measurement point is A, as shown in
Figure 11-27.
Unit
Times
Related Features
11-32


for data due to directed retry to TDD cell for voice
channel
Definition
Number of assignment executions for data due to directed retry to TDD cell for voice
channel
Description
This counter counts the number of assignment executions due to directed retry to TDD cell
for voice channel.
Usage
to TDD cell for voice channel and represent TDD cell directed retry status.
Measurement Point
The counter increments in voice channel assignment when target cell in directed retry is
TDD cell and successfully obtains channel and source cell receives radio resource
79.
to Directed Retry
Unit
Times
11-33

Related Features

attempts TDD cell for data
Definition
Number of assignment for retry attempts TDD cell for data
Description
This counter counts the number of assignment for retry attempts TDD cell for data channel.
Usage
This counter is used to find out the number of assignment for retry attempts TDD cell for
data channel and represent TDD cell traffic sharing status in data channel assignment.
Measurement Point
The counter increments in data channel assignment when source cell receives no
available radio resource message from TDD cell and source cell supports
directed retry and TDD cell that meets the directed retry demand can be found and
Radio_App message is sent to TDD cell. The measurement point is A, as shown in
Figure 11-29.
11-34

Unit
Times
Related Features

for data due to directed retry to TDD cell for data
Definition
Number of assignment executions for data due to directed retry to TDD cell for data
Description
This counter counts the number of assignment executions due to directed retry to TDD cell
for data channel.
Usage
to TDD cell for data channel and represent TDD cell directed retry status.
Measurement Point
The counter increments in data channel assignment when target cell in directed retry is
TDD cell and successfully obtains channel and source cell receives radio resource
11-30.
11-35

to Directed Retry
Unit
Times
Related Features
11.32 C901050031 Assignment unsuccessful due to

circuit obstruction
Definition
Assignment unsuccessful due to circuit obstruction
Description
This counter counts the number of the assignment failure due to circuit obstruction on
A-interface.
Usage
This counter is used to find out the number of assignment failure due to circuit obstruction
on A-interface and to check circuit obstruction status on A-interface in assignment flow.
11-36

Measurement Point
Target cell checks circuit after receiving assignment request message sent by MSC;
the counter increments if the circuit is obstructed. The measurement point is A, as shown
in Figure 11-31.
Figure 11-31 Measurement Point of Assignment Failure due to Circuit Obstruction

on A-Interface
Unit
Times

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.
Usage
This counter is used to find out the number of assignment failure due to circuit unmatched
on A-interface and to check circuit unmatched status on A-interface in assignment flow.
11-37

Measurement Point
Target cell checks circuit after receiving assignment request message sent by MSC;
the counter increments if the circuit is unmatched. The measurement point is A, as shown
in Figure 11-32.

on A-Interface
Unit
Times

no valid radio resource
Definition
Assignment unsuccessful due to no valid radio resource
Description
This counter counts the number assignment failure due to no valid radio resource.
Usage
This counter is used to find out the number of assignment failure due to no valid radio
resource and to check radio resource assignment status in assignment flow.
11-38

Measurement Point
l Source cell sends channel request to target cell after receiving assignment
request message; the counter increments if channel request fails due to no valid
radio resource. The measurement point is A, as shown in Figure 11-33.
l Source cell sends channel request to target cell after receiving assignment
request message; the counter increments if Radio_App is overtime due to no
responding message. The measurement point is A, as shown inFigure 11-33.

on A-Interface
Unit
Times

other causes
Definition
Assignment unsuccessful due to other causes
Description
This counter counts the number assignment failure due to other causes on A-interface.
Usage
This counter is used to find out the number of assignment failure due to other causes and
to check A-interface status in assignment flow.
11-39

Measurement Point
Target cell receives assignment request message sent by MSC; the counter
increments if assignment failure on A-interface is caused by other causes (instead of
the causes mentioned above, such as circuit obstruction, circuit unmatched and no valid
radio resource). The measurement point is A, as shown in Figure 11-34.

on A-Interface
Unit
Times

due to forced release (emergency service)
Definition
Number of assignment attempts due to forced release (emergency service)
Description
In the assignment flow, after BSC receives the RADIO_APPLY message, it attempts to
assign the voice channel. If there is no suitable channel and forced release is allowed,
then it releases other channels forcibly, if this call is an emergency call, then this counter
counts the number of forced release attempts.
11-40

Usage
This counter is used to find out the number of assignment attempts due to forced release
during the MS access process of an emergency call.
Measurement Point
BSC fails to assign channel due to no available resource, if forced release is allowed, BSC
will forcibly release other channels.
During an emergency call, BSC fails to assign voice channel. If forced release is allowed
and there is suitable forced release instance, then the counter increments when the forcing
release instance sends the forced release message to the forced release instance. The
Figure 11-35 Measurement Point Of Number Of Assignment Attempts Due To Forced

Release (Emergency Service)
Unit
Times

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
11-41

is considered successful. If the call is an emergency call, the counter counts the number
of successful forced releases (emergency service).
Usage
This counter is used to find out the number of successful assignments due to forced release
Measurement Point
During the voice channel assignment process, if the radio resource request fails and
forced release is allowed, the forcing release instance sends the forced release
message to the forced release instance. If the message of resource available is received,
then the resource is obtained successfully, and in this case, the counter increments. The
measurement point is B, as shown in Figure 11-36.

Unit
Times
11.38 C901050037 Number of assignment attempts due

to forced handover (emergency service)
Definition
Number of assignment attempts due to forced handover (emergency service)
11-42

Description
When BSC fails to assign voice channel due to no available resource, it attempts forced
handover towards external cell. If the call is an emergency call, the counter counts the
number of forced handover attempts.
Usage
This counter is used to find out the number of assignment attempts due to forced handover
Measurement Point
During an emergency call, BSC fails to assign voice channel. If forced handover is allowed
and there is suitable forcing handover instance, then the counter increments when the
forcing handover instance sends the forced handover message to the forced handover
instance. The measurement point is A, as shown in Figure 11-37.
Unit
Times

channel due to forced handover (emergency
service)
Definition
Number of assignment executions channel due to forced handover(emergency service)
11-43

Description
handover towards external cell. If the call is an emergency call, the counter counts the
number of successful forced handover.
Usage
This counter is used to find out the number of successful assignments due to forced
handover during the MS access process of an emergency call.
Measurement Point
During the voice channel assignment process for emergency call, if the radio resource
request fails and forced handover is allowed, the forcing handover instance sends the
forced handover message to the forced handover instance. If the message of resource
available is received, then the resource is obtained successfully, and in this case, the
counter increments. The measurement point is B, as shown in Figure 11-38.
To Forced Release
Unit
Times
11.40 C901050039 Number of assignments channel

due to queuing (emergency service)
Definition
Number of assignments channel due to queuing (emergency service)
11-44

Description
assign the voice channel. If there is no suitable channel and queuing is allowed, then the
instance enters the queuing state and waits for other resource to be released, if this call is
an emergency call, then this counter counts the number of queuing attempts (emergency
service).
Usage
This counter is used to find out the number of assignment attempts due to queuing during
the MS access process of an emergency call.
Measurement Point
During an emergency call, BSC fails to assign voice channel. If queuing is allowed, then
the instance is added to the queue and the counter increments. The measurement point
Unit
Times

execution channel due to queuing (emergency
service)
Definition
Number of assignments for execution channel due to queuing (emergency service)
11-45

Description
During an emergency call, BSC fails to assign voice channel due to no available resource
but obtains needed channel within specified time after the queuing is performed (no
forced handover or forced release is performed). In this case, the queuing is considered
successful, the counter counts the number of successful assignments due to queuing
(emergency service).
Usage
This counter is used to find out the number of successful assignments due to queuing
Measurement Point
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, as shown in Figure 11-40.
Due To Queuing
Unit
Times
11.42 C901050041 Number of forced handover target

not found (assignment forced handover)
Definition
Number of forced handover target not found (assignment forced handover)
11-46

Description
handover towards external cell. If no forcing handover instance is found in the cell, the
counter counts the number of times that forcing handover target instance is not found.
Usage
During forced handover for voice channel assignment, this counter is used to find out the
number of times that forced handover target instance is not found.
Measurement Point
During an emergency call, BSC fails to assign voice channel. If forced handover is
allowed but there is no suitable forced handover instance, then the counter increments.
Figure 11-41 Measurement Point Of Number Of Forced Handover Target Not Found
(Assignment Forced Handover)
Unit
Times
11.43 C901050042 Number of send forced handover

request to lower PRI user (assignment forced
handover)
Definition
Number of send forced handover request to lower PRI user (assignment forced handover)
11-47

Description
handover towards external cell. If forced handover target instance is found in the cell, the
counter counts the number of forced handover requests sent to low priority users during
the force handover.
Usage
During the voice channel assignment of MS access process, this counter is used to find
out the number of forced handover requests when the forcing handover instance is found.
Measurement Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable
forcing handover instance, then the counter increments when the forcing handover
instance sends the forced handover message to the forced handover instance. The
Unit
Times
11-48

11.44 C901050043 Number of received failure from

lower PRI user request resource for forced
handover (assignment forced handover)
Definition
Number of received failure from lower PRI user request resource for forced handover
(assignment forced handover)
Description
handover towards external cell. If forcing handover target instance is found in the cell, the
forced handover is initiated. Then, if the forced handover fails due to resource request
failure, the counter counts the number of receiving resource request failure message from
low priority user during the forced handover.
Usage
During the forced handover for voice channel assignment in MS access process, this
counter is used to find out the number of receiving the forced handover failure message
due to resource request failure.
Measurement Point
forcing handover instance, then the counter increments in the following case: the forcing
handover instance sends the forced handover message to the forced handover
instance and simultaneously receives the forced handover failure message which
is due to resource request failure. The measurement point is B, as shown in Figure 11-43.
11-49

Figure 11-43 Measurement Point Of Number Of Receiving Forced Handover Failure

Message From Low Priority User During Forced Handover
Unit
Times
11.45 C901050044 Number of lower PRI user handover

failure (assignment forced handover)
Definition
Number of lower PRI user handover failure (assignment forced handover)
Description
handover towards external cell. If forcing handover target instance is found in the cell, the
forced handover is initiated. Then, if the forced handover fails due to handover execution
failure, the counter counts the number of receiving handover execution failure message
from low priority user during the forced handover.
Usage
counter is used to find out the number of receiving the forced handover failure message
due to handover execution failure.
Measurement Point
forced handover target instance, then the counter increments in the following case: the
forcing handover instance sends the forced handover message to the forced handover
11-50

target instance and simultaneously receives the forced handover failure message which is
due to handover execution failure. The measurement point is B, as shown in Figure 11-44.
Figure 11-44 Measurement Point Of Number Of Receiving Forced Handover Failure

Message From Low Priority User During Forced Handover
Unit
Times
11.46 C901050045 Number of time out for wait resource

(assignment forced handover)
Definition
Number of time out for wait resource (assignment forced handover)
Description
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
counter is used to find out the number of timeout due to waiting for forced handover target
instance resource.
11-51

Measurement Point
forced handover target instance, then the counter increments when the waiting for forced
handover target instance resource is timeout. The measurement point is B, as shown in
Figure 11-45.
Figure 11-45 Measurement Point Of Number Of Timeout For Wait Resource (Assignment
Forced Handover)
Unit
Times
11.47 C901050046 Number of forced release target not

found (assignment forced release)
Definition
Number of forced release target not found (assignment forced release)
Description
then it releases other 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.
11-52

Measurement Point
During an emergency call, BSC fails to assign voice channel. If forced release is allowed
but there is no suitable forced release instance, then the counter increments. The
Figure 11-46 Measurement Point Of Number Of Forced Release Target Not Found
(Assignment Forced Release)
Unit
Times
11.48 C901050047 Number of time out for wait resource

(assignment forced release)
Description
then it releases other channels forcibly. After the forced release is initiated, if time is out
due to waiting for forced release target to release resource, then this counter counts the
number of timeout due to waiting for resource during the forced release.
Usage
During the forced release for voice channel assignment in MS access process, this counter
is used to find out the number of timeout due to waiting for forced release target instance
resource.
11-53

Measurement Point
When BSC fails to assign voice channel, if forced release is allowed and there is suitable
forced release target instance, then the counter increments when the waiting for forced
release target instance resource is timeout. The measurement point is B, as shown in
Figure 11-47.
Figure 11-47 Measurement Point Of Number Of Timeout For Wait Resource (Assignment
Forced Release
Unit
Times
11.49 C901050048 Number of get before grab released

channel (assignment forced handover)
Definition
Number of get before grab released channel (assignment forced handover)
Description
handover towards external cell. If the handover succeeds in getting the forced handover
target resource, the counter counts the number of preempting the released channel during
the forced handover.
Usage
counter is used to find out the number of preempting the released channel.
11-54

Measurement Point
During the voice channel assignment process for emergency call, if the radio resource
request fails and forced handover is allowed, the forcing handover instance sends the
forced handover message to the forced handover instance. If the message of resource
available is received, then the resource is obtained successfully, and in this case, the
counter increments. The measurement point is B, as shown in Figure 11-48.
To Forced Release
Unit
Times

channel(assignment forced release)
Definition
Number of get before grab released channel (assignment forced release)
Description
BSC fails to assign voice channel due to no available resource, if it obtains needed
channel within specified time after the forced release is performed, then the forced
release is considered successful, and the counter counts the number of successful forced
releases (emergency service).
Usage
This counter is used to find out the number of successful assignments due to forced release
during the MS access process.
11-55

Measurement Point
forced release is allowed, the forcing release instance sends the forced release
message to the forced release instance. If the message of resource available is received,
then the resource is obtained successfully, and in this case, the counter increments. The
measurement point is B, as shown in Figure 11-49.

Unit
Times
11.51 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 transmission mode according to the assignment request's content.
After MS assignment is completed, BSC decides the A-interface transmission mode
for the service before sending the assignment completion message. If the A-interface
transmission mode is all-IP A-interface transmission, the counter increments. The
11-56

Figure 11-50 Measurement Point of the Count of Assignment Using FULL IP A-Interface
Unit
Times
11.52 C901050051 The count of Assignment using PCM

over IP A-Interface
Statistics object
CELL
Description
transmission mode is PCMoIP transmission, the counter increments. The measurement
11-57

Figure 11-51 Measurement Point of the Count of Assignment Using PCM over IP A-Interface
Unit
Times
11.53 C901050052 The count of Assignment using PCM

over TDM A-Interface
Statistics object
CELL
Description
transmission mode is TDM transmission, the counter increments. The measurement
11-58

Figure 11-52 Measurement Point of the Count of Assignment Using PCM over TDM A-Interface
Unit
Times
11.54 C901050053 The count of Assignment Failure

caused by "Requested Codec Type or Codec
Configuration not supported"
Statistics object
CELL
Description
selects the voice version according to the field Codec List (MSC Preferred) in the
assignment request. In the field Codec List (MSC Preferred), if the voice coding type
or combination is not the voice version supported by BSC, then the assignment failure
message is sent to MSC, and the counter increments. (At present, there is no voice
coding type or combination not supported by BSC. Thus the counter does not have
counting value. ) The measurement point is A, as shown in Figure 11-53.
11-59

Figure 11-53 Measurement Point of the Count of Assignment Failure Caused by "Requested Codec
Type or Codec Configuration not supported"
Unit
Times

caused by "Requested Codec Type or Codec
Configuration unavailable"
Statistics object
CELL
Description
selects the voice version according to the field Codec List (MSC Preferred) in the
assignment request. According to the voice coding type or combination in the field Codec
List (MSC Preferred), if it fails to request corresponding radio channel (i.e. the radio
channel type available in the current cell is not consistent with the requested channel
type), then the assignment failure message is sent to MSC, and the counter increments.
11-60

Figure 11-54 Measurement Point of the Count of Assignment Failure Caused by "Requested Codec
Type or Codec Configuration unavailable"
Unit
Times

caused by "Requested A-Interface Type not
supported"
Statistics object
CELL
Description
selects voice version as well as A-interface transmission mode according to the field
Codec List (MSC Preferred) in the assignment request. In the field Codec List (MSC
Preferred), if the A-interface transmission mode is not consistent with that supported by
BSC, then the assignment failure message is sent to MSC, and the counter increments.
11-61

Figure 11-55 Measurement Point of the Count of Assignment Failure Caused by "Requested
A-Interface Type not supported"
Unit
Times
11.57 C901050056 The count of Assignment

Failure caused by "Requested A-Interface Type
unavailable"
Statistics object
CELL
Description
selects voice version as well as A-interface transmission mode according to the field Codec
List (MSC Preferred) in the assignment request. After the system selects an A-interface
transmission mode, if such a transmission mode can not be used in the current cases (for
example, in the case of IP resource request failure or access failure), then the assignment
failure message is sent to MSC, and the counter increments. The measurement point is
C, as shown in Figure 11-56.
11-62

A-Interface Type unavailable"
Unit
Times

caused by "Call Identifier already allocated"
Statistics object
CELL
Description
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
11-63

Figure 11-57 Measurement Point of the Count of Assignment Failure Caused by "Call Identifier
already allocated"
Unit
Times

caused by "Requested Redundancy Level not
supported"
Statistics object
CELL
Description
request, which is of data type or fax service type, is received, the system selects voice
version as well as transmission redundancy mode according to the field Codec List
(MSC Preferred) in the assignment request. If the transmission redundancy mode is not
supported by BSC, then the assignment failure message is sent to MSC, and the counter
11-64

Redundancy Level not supported"
Unit
Times

caused by "Call Access Control"
Statistics object
CELL
Description
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 11-59.
11-65

Figure 11-59 Measurement Point of the Count of Assignment Failure Caused by "Call Access
Control"
Unit
Times
11.61 C901050060 Attempt Number of mode modify

for assignment
Description
This counter counts the number of attempts for mode modification.
Usage
This counter counts the number of attempts for mode modification in the process of
assignment.
Measurement Point
1. The channel type requested by the assignment is same as the actual channel type, the
channel mode is changed, the type of actual channel is voice channel or the channel
type requested by the assignment is voice channel, and the voice version requested
by the assignment is unmatched with that actually occupied.
2. On re-assignment, the channel type for re-assignment is related to actual channel

type, the actual channel type is a voice channel or the channel type requested by the
assignment is a voice channel, and the voice version requested by the assignment is
unmatched with that actually occupied.
11-66

Unit
Times
11.62 C901050061 Success Number of mode modify

for assignment
Description
This counter counts the number of successes for mode modification.
Usage
This counter counts the number of successes for mode modification in the process of
assignment.
Measurement Point
This counter increments while receiving the response message about Abis channel mode
modified or Um channel mode modified in the process of modifying the mode.
Unit
Times
11-67

11-68

Chapter 12
Handover Cause
Measurement
Table of Contents
Overview ..................................................................................................................12-3
C901060001 Number of handover attempts due to directed retry .............................12-3
C901060002 Number of SDCCH handover attempts due to UL received strength ...12-4
C901060003 Number of SDCCH handover attempts due to DL received strength....12-5
C901060004 Number of SDCCH Handover attempt due to UL quality .....................12-6
C901060005 Number of SDCCH Handover attempt due to DL quality......................12-7
C901060006 Number of SDCCH handover attempts due to UL interference ............12-8
C901060007 Number of SDCCH handover attempts due to DL interference ............12-9
C901060008 Number of SDCCH inter-subcell handover attempts due to good C/I .12-10
C901060009 Number of SDCCH inter-subcell handover attempts due to bad C/I ... 12-11
C901060010 Number SDCCH of handover attempts due to PBGT.........................12-12
C901060011 Number of SDCCH handover attempts due to large TA ....................12-13
C901060012 Number of SDCCH handover attempts due to quick break up of UL ..12-14
C901060013 Number of SDCCH handover attempts due to macro-micro switch ...12-15
C901060014 Number of SDCCH handover attempts due to MSC request .............12-16
C901060015 Number of SDCCH handover attempts due to traffic..........................12-17
C901060016 Number of SDCCH handover attempts due to large TA and wastage .12-18
C901060017 Number of SDCCH handover attempts due to small TA and wastage .12-19
C901060018 Number of SDCCH Handover attempt due to a preferable electricity
level of 3G adjacent cell .........................................................................................12-20
C901060019 Number SDCCH handover attempts due to forced transfer ...............12-21
C901060020 Number of SDCCH handover during assignment due to forced
transfer...................................................................................................................12-22
C901060021 Number of SDCCH handover during handover due to forced transfer
..............................................................................................................................12-23
C901060022 Number of SDCCH handover attempts due to increased TA .............12-25
C901060023 Number of SDCCH handover attempts due to TA decrease...............12-26
C901060024 Number of SDCCH Handover attempt due to other factors ...............12-27
C901060035 Number of TCH/F handover attempts due to quick break up of UL ....12-27
C901060036 Number of TCH/F handover attempts due to macro-micro switch ......12-28
C901060037 Number of TCH/F handover attempts due to MSC request................12-29
C901060038 Number of TCH/F handover attempts due to traffic............................12-30
C901060039 Number of TCH/F handover attempts due to large TA and wastage ..12-31
C901060040 Number of TCH/F handover attempts due to small TA and wastage ..12-32
12-1

C901060041 Number of TCH/F handover attempts due to preferable electricity

level in 3G adjacent cell .........................................................................................12-33
C901060042 Number of TCH/F handover attempts due to forced transfer..............12-34
C901060043 Number of TCH/F handover during assignment due to forced
transfer...................................................................................................................12-35
C901060044 Number of TCH/F handover attempts during handover due to forced
transfer...................................................................................................................12-36
C901060045 Number of TCH/F handover attempts due to TA increase..................12-38
C901060046 Number of TCH/F handover attempts due to TA decrease.................12-39
C901060058 Number of TCH/H handover attempts due to quick break up of UL....12-40
C901060059 Number of TCH/H handover attempts due to macro-micro switch......12-41
C901060060 Number of TCH/H handover attempts due to MSC request ...............12-42
C901060061 Number of TCH/H handover attempts due to traffic ...........................12-43
C901060062 Number of TCH/H handover attempts due to large TA and wastage ..12-44
C901060063 Number of TCH/H handover attempts due to small TA and wastage..12-45
C901060064 Number of TCH/H handover attempts due to a preferable electricity
level in 3G adjacent cell..........................................................................................12-46
C901060065 Number of TCH/H handover attempts due to forced transfer .............12-47
C901060066 Number of TCH/H handover attempts during assignment due to
forced transfer ........................................................................................................12-48
C901060067 Number of TCH/H handover attempts during handover due to forced
transfer...................................................................................................................12-49
C901060068 Number of TCH/H handover attempts during handover due to TA
increase .................................................................................................................12-51
C901060069 Number of TCH/H handover attempts during handover due to TA
decrease ................................................................................................................12-52
C901060070 Number of TCH/H handover attempts due to other reasons ..............12-53
C901060071 Number of TCH/F handover attempts due to CS channel transfer .....12-53
C901060072 Number of TCH/H handover attempts due to CS channel transfer .....12-54
C901060073 Number of TCH/H handover attempts due to Fragment
reorganization ........................................................................................................12-56
C901060074 Number of TCH/F handover attempts due to energy conservation.....12-57
C901060075 Number of TCH/F handover attempts due to energy conservation.....12-58
C901060076 Number of TCH/F handover attempts due to CS channel is forced
release ...................................................................................................................12-59
C901060077 Number of TCH/H handover attempts due to CS channel is forced
release ...................................................................................................................12-60
C901060078 Number of TCH/F handover attempts due to FR to HR during cell
busy .......................................................................................................................12-61
C901060079 Number of SDCCH handover attempts due to downlink rapid drop....12-62
C901060080 Number of TCH/F handover attempts due to downlink rapid drop ......12-62
C901060081 Number of TCH/H handover attempts due to downlink rapid drop......12-63
12-2

Chapter 12 Handover Cause Measurement
12.1 Overview
Handover cause counter is used for checking MS handover causes. According to cell
radio environment and BSC settings, handover algorithm judgment module can carry out
handover due to several different handover causes, so as to realize functions such as
optimizing resource usage, improving call quality and rescuing calls.
12.2 C901060001 Number of handover attempts due to

directed retry
Definition
Number of handover attempts due to directed retry
Description
During the process of MS requests channel, if radio resource is congested, then it will
attempt to request an available channel from adjacent cell for this call. This is called direct
retry, which is a kind of handover. This counter counts the number of handover attempts
due to direct retry.
Usage
This counter is used to find out MS access process and to check cell channel utilizing
status. If the statistic number counted by the counter is relative high, then it means the cell
does not have enough radio resource and capacity expansion shall be taken into account.
Measurement Point
In assignment process, the counter increments if source instance receives message that
no available radio resource replied by target instance, then it chooses cell list successfully
and try to attempt cells in the list. This counter is handover cause counter and used for
finding out cell channel congestion status, so the counter only counts in the initial judgment.
12-3

Figure 12-1 Directed Retry Judgment
Unit
Times
Related Features
12.3 C901060002 Number of SDCCH handover attempts

due to UL received strength
Definition
Number of SDCCH handover attempts due to UL received strength
Description
This counter counts the number of handover attempts due to too low uplink received
strength (on SDCCH).
Usage
This counter is used to find out frequency of handover attempts due to uplink received
strength (on SDCCH); high number means SDCCH uplink signal strength is low.
Measurement Point
BSC carries out handover judgment after receiving SDDCH measurement report; the
counter increments if judgment result is yes and handover cause is uplink signal strength.
12-4

Unit
Times
Related Features

due to DL received strength
Definition
Number of SDCCH handover attempts due to DL received strength
Description
This counter counts the number of handover attempts due to too low downlink received
strength (on SDCCH).
Usage
This counter is used to find out frequency of handover attempts due to downlink received
strength (on SDCCH); high number means SDCCH downlink signal strength is low.
Measurement Point
counter increments if judgment result is yes and handover cause is downlink signal
strength. The measurement point is A, as shown in Figure 12-3.
12-5

Unit
Times
Related Features
12.5 C901060004 Number of SDCCH Handover attempt

due to UL quality
Definition
Number of SDCCH Handover attempt due to UL quality.
Description
This counter counts the number of handover attempts due to too bad uplink quality (on
SDCCH).
Usage
This counter is used to find out frequency of handover attempts due to uplink quality (on
SDCCH); high number means SDCCH uplink quality is bad.
Measurement Point
counter increments if judgment result is yes and handover cause is uplink quality. The
12-6

Unit
Times
Related Features
12.6 C901060005 Number of SDCCH Handover attempt

due to DL quality
Definition
Number of SDCCH Handover attempt due to DL quality.
Description
This counter counts the number of handover attempts due to too bad downlink quality (on
SDCCH).
Usage
This counter is used to find out frequency of handover attempts due to downlink quality
(on SDCCH); high number means SDCCH downlink quality is bad.
Measurement Point
counter increments if judgment result is yes and handover cause is downlink quality. The
12-7

Unit
Times
Related Features

Definition
Number of SDCCH handover attempts due to UL interference.
Description
This counter counts the number of handover attempts due to too high uplink interference
(on SDCCH).
Usage
This counter is used to find out frequency of handover attempts due to uplink interference
(on SDCCH); high number means SDCCH uplink interference is high.
Measurement Point
counter increments if judgment result is yes and handover cause is uplink interference.
12-8

Unit
Times
Related Features

Definition
Number of SDCCH handover attempts due to DL interference.
Description
This counter counts the number of handover attempts due to too high downlink interference
(on SDCCH).
Usage
This counter is used to find out frequency of handover attempts due to downlink
interference (on SDCCH); high number means SDCCH downlink interference is high.
Measurement Point
counter increments if judgment result is yes and handover cause is downlink interference.
12-9

Unit
Times
Related Features
12.9 C901060008 Number of SDCCH inter-subcell

handover attempts due to good C/I
Definition
Number of SDCCH inter-subcell handover attempts due to good C/I
Description
This counter counts the number of handover attempts due to too 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.
Usage
This counter is used to find out frequency of handover attempts due to too high C/I RATIO
(on SDCCH); high number means the number of MS handover to second cell after MS has
been accessed into first cell due to too high C/I RATIO is high and second cell absorbs
traffic.
Measurement Point
counter increments if judgment result is yes and handover cause is C/I RATIO (on
SDCCH) (Good C/I). The measurement point is A, as shown in Figure 12-8.
12-10

Unit
Times
Related Features
12.10 C901060009 Number of SDCCH inter-subcell

handover attempts due to bad C/I
Definition
Number of SDCCH inter-subcell handover attempts due to bad C/I
Description
This counter counts the number of handover attempts due to too low C/I RATIO (on
SDCCH). This handover only happens in sub-cell configuration and C/I algorithm is used;
MS is handed over from second cell to first cell.
Usage
This counter is used to find out frequency of handover attempts due to too low C/I RATIO
(on SDCCH); high number means when MS is on the call in second cell, the number of
handover to first cell is high due to too low C/I RATIO; interference in second cell is high
and some measures like TRX power adjustment shall be done to improve second cell C/I
ratio.
Measurement Point
counter increments if judgment result is yes and handover cause is C/I RATIO (on
SDCCH) (Bad C/I). The measurement point is A, as shown in Figure 12-9.
12-11

Unit
Times
Related Features
12.11 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.
Usage
This counter is used to find out frequency of handover attempts due to PBGT (on SDCCH);
high number means present cells SDCCH signal is worse than that of the adjacent cell.
Measurement Point
counter increments if judgment result is yes and handover cause is PBGT (on SDCCH).
12-12

Unit
Times
Related Features
12.12 C901060011 Number of SDCCH handover

attempts due to large TA
Definition
Number of SDCCH handover attempts due to large TA
Description
This counter counts the number of handover attempts due to large TA (on SDCCH).
Increase of TA means MS is moving far away from the cell; when the distance between
MS and the cell reaches a certain value, then handover attempts due to large TA may
occur.
Usage
This counter is used to find out frequency of handover attempts due to large TA (on
SDCCH); its value can represent mobility of the subscriber in the cell in a certain extent.
Measurement Point
counter increments if judgment result is yes and handover cause is large TA (on SDCCH).
12-13

Unit
Times
Related Features

attempts due to quick break up of UL
Definition
Number of SDCCH handover attempts due to quick break up of UL
Description
This counter counts the number of handover attempts due to uplink break up quickly (on
SDCCH). If SDCCH uplink level decreases abruptly in several continuous measurement
reports, handover attempts due to uplink break up quickly may occur.
Usage
This counter is used to find out frequency of handover attempts due to uplink break up
quickly (on SDCCH); its value can represent stability of the current radio environment in a
certain extent.
Measurement Point
counter increments if judgment result is yes and handover cause is uplink break up
quickly (on SDCCH). The measurement point is A, as shown in Figure 12-12.
12-14

Unit
Times
Related Features
ZGO-02-02-006 Rapid Level Drop Handover
ZGO-02-02-015 Enhanced Cell Reselection Procedure

attempts 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.
Usage
This counter is used to find out frequency of handover attempts due to macro-micro switch
(on SDCCH); its value can represent the status of micro cell absorbing traffic.
Measurement Point
counter increments if judgment result is yes and handover cause is macro-micro switch
(on SDCCH). The measurement point is A, as shown in Figure 12-13.
12-15

Unit
Times
Related Features
ZGO-02-02-001 Handover between Macro- and Micro-cells

attempts due to MSC request
Definition
Number of SDCCH handover attempts due to MSC request.
Description
This counter counts the number of handover attempts due to MSC request (on SDCCH).
Handover is originated by MSC, some calls are handed over from the present cell to target
cell for alleviating the present cell traffic load.
Usage
This counter is used to find out frequency of handover attempts due to MSC request (on
SDCCH); its value can represent the status that MSC adjusts the present cell traffic.
Measurement Point
BSC carries out handover judgment after receiving HO_ENQUIRY message sent by MSC;
the counter increments if judgment result is yes. The measurement point is A, as shown
inFigure 12-14.
12-16

Figure 12-14 Ho_Enquiry Handover
Unit
Times
Related Features

attempts due to traffic
Definition
Number of SDCCH handover attempts due to traffic.
Description
This counter counts the number of handover attempts due to traffic (on SDCCH). Handover
is originated by BSC, some calls are handed over from the present cell to target cell for
alleviating the present cell traffic load.
Usage
This counter is used to find out frequency of handover attempts due to traffic (on SDCCH);
its value can represent the status that BSC adjusts the present cell traffic.
Measurement Point
BSC carries out handover judgment after receiving SDCCH traffic alarm, the counter
increments if judgment result is yes. The measurement point is A, as shown in Figure
12-15. DBS, UMC and RANCS are all instances of BSC and they take part in handover
due to traffic.
12-17

Figure 12-15 Traffic Handover
Unit
Times
Related Features
ZGO-02-02-007 Traffic Based Handover

attempts due to large TA and wastage
Definition
Number of SDCCH handover attempts due to large TA and wastage.
Description
This counter counts the number of handover attempts due to large 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.
Usage
This counter is used to find out frequency of handover attempts due to large TA and
wastage (on SDCCH); its value can represent the mobility of subscriber among sub-cells
in the cell.
12-18

Measurement Point
counter increments if judgment result is yes and handover cause is large TA and wastage
Unit
Times
Related Features

attempts 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-cell configuration and TA & PassLoss
algorithm is used; when both TA and PassLoss are lower than set threshold, MS is
handed over from first cell to second cell.
Usage
This counter is used to find out frequency of handover attempts due to small TA and
wastage (on SDCCH); its value can represent the mobility of subscriber among sub-cells
in the cell.
12-19

Measurement Point
counter increments if judgment result is yes and handover cause is small TA and wastage
Unit
Times
Related Features
12.19 C901060018 Number of SDCCH Handover

attempt due to a preferable electricity level of 3G
adjacent cell
Definition
Number of SDCCH handover attempt due to a preferable electricity level of FDD adjacent
cell.
Description
This counter counts the number of handover attempts due to a good standard level in FDD
adjacent cell (on SDCCH).
Usage
This counter is used to find out frequency of handover attempts due to a good standard
level in FDD adjacent cell (on SDCCH); its value can represent status that 3G network
absorbs traffic.
12-20

Measurement Point
counter increments if judgment result is yes and handover cause is good standard level in
FDD adjacent cell (on SDCCH). The measurement point is A, as shown in Figure 12-18.
Unit
Times
Related Features
12.20 C901060019 Number SDCCH handover attempts

due to forced transfer
Definition
Number SDCCH handover attempts due to forced transfer.
Description
This counter counts the number of forced transfer handover attempts (on SDCCH). If the
TCH utilizing rate of the present cell reaches a set percentage of the threshold, BSC will
try to handover subscriber whose path loss and TA are small from the present cell to some
set cells. This kind of handover is called forced transfer handover.
Usage
This counter is used to find out frequency of forced transfer handover attempts (on
SDCCH); its value can represent the present cells channel utilizing status and traffic
sharing status.
12-21

Measurement Point
counter increments if judgment result is yes and handover cause is forced transfer
handover attempts (on SDCCH). The measurement point is A, as shown in Figure 12-19.
Unit
Times
Related Features
ZGO-02-02-003 Directed-Shift Handover
12.21 C901060020 Number of 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 assignment (on SDCCH). If
all TCH of the present cell are occupied and MS priority is high enough, BSC will try to
handover services whose priority are low from the present cell to adjacent cells. This kind
of handover is called forced handover. Forced handover and forced release are two forms
of occupation.
Usage
This counter is used to find out frequency of forced handovers during assignment (on
SDCCH); its value can represent the present cells TCH utilizing status and traffic sharing
status.
12-22

Measurement Point
BSC has no available TCH to allocate during the assignment process and it carries out
forced handover judgment; the counter increments if judgment result is yes and the channel
type of forced handover instance is SDCCH. The measurement point is A, as shown in
Figure 12-20.
Figure 12-20 Forced Handover Judgment
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
12.22 C901060021 Number of SDCCH handover during

handover due to forced transfer
Definition
Number of SDCCH handover during handover due to forced transfer.
12-23

Description
This counter counts the number of forced handovers during handover (on SDCCH).
Usage
This counter is used to find out frequency of forced handovers during handover (on
SDCCH); its value can represent the present cells TCH utilizing status and traffic sharing
status.
Measurement Point
BSC has no available TCH to allocate during the handover process and it carries out forced
handover judgment; the counter increments if judgment result is yes and the channel type
of forced handover instance is SDCCH. The measurement point is A, as shown in Figure
12-21.
Unit
Times
Related Features
12-24


attempts 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 increased TA (on SDCCH).
This handover only happens in expanding cell configuration, present BSC version does
not use expanded cell and expanded TRX configuration any more after being introduced
the concept of sub-cell. This counter is equal to the counter that counts the number of MS
handover from second cell to first cell during sub-cell configuration.
Usage
This counter is used to find out frequency of MS handover from second cell to first cell in
sub-cell.
Measurement Point
counter increments if judgment result is yes and handover is from second cell to first cell.
Unit
Times
Related Features
12-25


attempts due to TA decrease
Definition
Number of SDCCH handover attempts due to TA decrease.
Description
This counter counts the number of handover attempts due to decreased TA (on SDCCH).
handover from first cell to second cell during sub-cell configuration.
Usage
This counter is used to find out frequency of MS handover from first cell to second cell in
sub-cell.
Measurement Point
counter increments if judgment result is yes and handover is from first cell to second cell.
Unit
Times
Related Features
12-26

12.25 C901060024 Number of SDCCH Handover

attempt due to other factors
Definition
Number of SDCCH Handover attempt due to other factors.
Description
This counter counts the number of handover attempts due to any other reason except
reasons mentioned above (on SDCCH).
Usage
This counter is used to find out frequency of handover attempts due to any other reason
(on SDCCH).
Measurement Point
counter increments if judgment result is yes and handover cause is any other reason.
Unit
Times
Related Features

due to quick break up of UL
Definition
Number of TCH/F handover attempts due to quick break up of UL.
12-27

Description
TCH/F). If TCH/F uplink level decreases abruptly in several continuous measurement
Usage
quickly (on TCH/F); its value can represent stability of the current radio environment in a
certain extent.
Measurement Point
BSC carries out handover judgment after receiving TCH/F measurement report; the
quickly (on TCH/F). The measurement point is A, as shown in Figure 12-25.
Unit
Times
Related Features

due to macro-micro switch
Definition
Number of TCH/F handover attempts due to macro-micro switch.
12-28

Description
TCH/F). If adjacent cell level is not lower than the threshold and the adjacent cell is
Usage
(on TCH/F); its value can represent the status of micro cell absorbing traffic.
Measurement Point
(on TCH/F). The measurement point is A, as shown in Figure 12-26.
Unit
Times
Related Features

due to MSC request
Definition
Number of TCH/F handover attempts due to MSC request.
Description
This counter counts the number of handover attempts due to MSC request (on TCH/F).
12-29

Usage
TCH/F); its value can represent the status that MSC adjusts the present cell traffic.
Measurement Point
BSC carries out handover judgment after receiving HO_ENQUIRY message sent by
MSC; the counter increments if judgment result is yes. The measurement point is A, as
Figure 12-27 HO_Enquiry Handover
Unit
Times
Related Features

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
Usage
This counter is used to find out frequency of handover attempts due to traffic (on TCH/F);
12-30

Measurement Point
BSC carries out handover judgment after receiving TCH/F traffic alarm, the counter
12-28.
Unit
Times
Related Features

due to large TA and wastage
Definition
Number of TCH/F handover attempts due to large TA and wastage.
Description
(on TCH/F). This handover only happens in sub-cell configuration and TA & PassLoss
12-31

Usage
wastage (on TCH/F); its value can represent the mobility of subscriber among sub-cells in
the cell.
Measurement Point
Unit
Times
Related Features

due to small TA and wastage
Definition
Number of TCH/F handover attempts due to small TA and wastage.
Description
(on TCH/F). This handover only happens in sub-cell configuration and TA & PassLoss
12-32

Usage
wastage (on TCH/F); its value can represent the mobility of subscriber among sub-cells in
the cell.
Measurement Point
Unit
Times
Related Features

due to preferable electricity level in 3G adjacent cell
Definition
Number of TCH/F handover attempts due to preferable electricity level in 3G adjacent cell.
Description
This counter counts the number of handover attempts due to a good standard level in 3G
adjacent cell (on TCH/F).
Usage
level in 3G adjacent cell (on TCH/F); its value can represent status that 3G network absorbs
traffic.
12-33

Measurement Point
counter increments if judgment result is yes and handover cause is good standard level
in 3G adjacent cell (on TCH/F). The measurement point is A, as shown in Figure 12-31.
Unit
Times
Related Features

Definition
Number of TCH/F handover attempts due to forced transfer.
Description
This counter counts the number of forced transfer handover attempts (on TCH/F). If the
Usage
This counter is used to find out frequency of forced transfer handover attempts (on TCH/F);
its value can represent the present cells channel utilizing status and traffic sharing status.
12-34

Measurement Point
handover attempts (on TCH/F). The measurement point is A, as shown in Figure 12-32.
Unit
Times
Related Features
12.34 C901060043 Number of TCH/F handover during

assignment due to forced transfer
Definition
Number of TCH/F handover during assignment due to forced transfer.
Description
This counter counts the number of forced handovers during assignment (on TCH/F). If
of handover is called forced handover.
Usage
TCH/F); its value can represent the present cells TCH utilizing status and traffic sharing
status.
12-35

Measurement Point
type of forced handover instance is TCH/F. The measurement point is A, as shown in Figure
12-33.
Unit
Times
Related Features

during handover due to forced transfer
Definition
Number of TCH/F handover attempts during handover due to forced transfer.
12-36

Description
This counter counts the number of forced handovers during handover (on TCH/F).
Usage
This counter is used to find out frequency of forced handovers during handover (on TCH/F);
its value can represent the present cells TCH utilizing status and traffic sharing status.
Measurement Point
of forced handover instance is TCH/F. The measurement point is A, as shown in Figure
12-34.
Unit
Times
Related Features
12-37


due to TA increase
Definition
Number of TCH/F handover attempts due to TA increase.
Description
This counter counts the number of handover attempts due to increased TA (on TCH/F).
Usage
sub-cell.
Measurement Point
Unit
Times
Related Features
12-38


due to TA decrease
Definition
Number of TCH/F handover attempts due to TA decrease.
Description
This counter counts the number of handover attempts due to decreased TA (on TCH/F).
Usage
sub-cell.
Measurement Point
Unit
Times
Related Features
12-39


due to quick break up of UL
Definition
Number of TCH/H handover attempts due to quick break up of UL.
Description
TCH/H). If TCH/H uplink level decreases abruptly in several continuous measurement
Usage
quickly (on TCH/H); its value can represent stability of the current radio environment in a
certain extent.
Measurement Point
BSC carries out handover judgment after receiving TCH/H measurement report; the
quickly (on TCH/H). The measurement point is A, as shown in Figure 12-37.
Unit
Times
Related Features
12-40


due to macro-micro switch
Definition
Number of TCH/H handover attempts due to macro-micro switch.
Description
TCH/H). If adjacent cell level is not lower than the threshold and the adjacent cell is
Usage
(on TCH/H); its value can represent the status of micro cell absorbing traffic.
Measurement Point
(on TCH/H). The measurement point is A, as shown in Figure 12-38.
Unit
Times
Related Features
12-41


due to MSC request
Definition
Number of TCH/H handover attempts due to MSC request.
Description
This counter counts the number of handover attempts due to MSC request (on TCH/H).
Usage
TCH/H); its value can represent the status that MSC adjusts the present cell traffic.
Measurement Point
BSC carries out handover judgment after receiving HO_ENQUIRY message sent by MSC;
the counter increments if judgment result is yes. The measurement point is A, as shown
in Figure 12-39.
Figure 12-39 HO_Enquiry Handover
Unit
Times
Related Features
12-42


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
Usage
This counter is used to find out frequency of handover attempts due to traffic (on TCH/H);
Measurement Point
BSC carries out handover judgment after receiving TCH/H traffic alarm, the counter
12-40.
Unit
Times
Related Features
12-43



due to large TA and wastage
Definition
Number of TCH/H handover attempts due to large TA and wastage.
Description
(on TCH/H). This handover only happens in sub-cell configuration and TA & PassLoss
Usage
wastage (on TCH/H); its value can represent the mobility of subscriber among sub-cells in
the cell.
Measurement Point
Unit
Times
Related Features
12-44


due to small TA and wastage
Definition
Number of TCH/H handover attempts due to small TA and wastage.
Description
(on TCH/H). This handover only happens in sub-cell configuration and TA & PassLoss
Usage
wastage (on TCH/H); its value can represent the mobility of subscriber among sub-cells in
the cell.
Measurement Point
Unit
Times
Related Features
12-45


due to a preferable electricity level in 3G adjacent
cell
Definition
Number of TCH/H handover attempts due to a preferable electricity level in 3G adjacent
cell.
Description
This counter counts the number of handover attempts due to a good standard level in 3G
adjacent cell (on TCH/H).
Usage
level in 3G adjacent cell (on TCH/H); its value can represent status that 3G network absorbs
traffic.
Measurement Point
counter increments if judgment result is yes and handover cause is good standard level
in 3G adjacent cell (on TCH/H). The measurement point is A, as shown in Figure 12-43.
Unit
Times
Related Features
12-46


Definition
Number of TCH/H handover attempts due to forced transfer.
Description
This counter counts the number of forced transfer handover attempts (on TCH/H). If the
Usage
This counter is used to find out frequency of forced transfer handover attempts (on TCH/H);
its value can represent the present cells channel utilizing status and traffic sharing status.
Measurement Point
handover attempts (on TCH/H). The measurement point is A, as shown in Figure 12-44.
Unit
Times
Related Features
12-47


during assignment due to forced transfer
Definition
Number of TCH/H handover attempts during assignment due to forced transfer.
Description
This counter counts the number of forced handovers during assignment (on TCH/H). If
of handover is called forced handover.
Usage
TCH/H); its value can represent the present cells TCH utilizing status and traffic sharing
status.
Measurement Point
type of forced handover instance is TCH/H. The measurement point is A, as shown in
Figure 12-45.
12-48

Unit
Times
Related Features

during handover due to forced transfer
Definition
Number of TCH/H handover attempts during handover due to forced transfer.
Description
This counter counts the number of forced handovers during handover (on TCH/H).
12-49

Usage
This counter is used to find out frequency of forced handovers during handover (on TCH/H);
its value can represent the present cells TCH utilizing status and traffic sharing status.
Measurement Point
of forced handover instance is TCH/H. The measurement point is A, as shown in Figure
12-46.
Unit
Times
Related Features
12-50


during handover due to TA increase
Definition
Number of TCH/H handover attempts during handover due to TA increase.
Description
This counter counts the number of handover attempts due to increased TA (on TCH/H).
Usage
sub-cell.
Measurement Point
Unit
Times
Related Features
12-51


during handover due to TA decrease
Definition
Number of TCH/H handover attempts during handover due to TA decrease.
Description
This counter counts the number of handover attempts due to decreased TA (on TCH/H).
Usage
sub-cell.
Measurement Point
Unit
Times
Related Features
12-52


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.
Measurement Point
counter increments if judgment result is yes and handover is caused by other reasons.
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 handover caused by this reason is intra-cell handover.
12-53

Usage
This counter is used to find out handover frequency due to CS channel transfer on TCH/F.
Measurement Point
During call service, due to other call services released, CS service channel transfer is
issued to do intra-cell handover. The service occupying middle timeslot can be migrated
to edge timeslot, providing available sustainable channels for PS. This counter increments
if the channel type of instance is TCH/F. The measurement point is A, as shown in Figure
12-50.
Figure 12-50 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
12-54

Description
This counter counts the number of handover due to CS channel transfer by BSC, which
is useful for continuity of available PS channel on TCH/H. This may lead to intra-cell
handover.
Usage
This counter is used to find out handover frequency due to CS channel handover on TCH/H
by BSC.
Measurement Point
During call service, due to other call service released, CS service channel transfer is issued
to do intra-cell handover. The service occupying middle timeslot service can be migrated to
edge timeslot, providing available continual channel. This counter increments if channel
type for handover instance is TCH/H. The measurement point is A, as shown in Figure
12-51.
Unit
Times
Related Features
12-55


due to Fragment reorganization
Definition
Number of TCH/H handover attempts due to Fragment reorganization
Description
BSC carries out fragment reorganization for one of two half-rate service occupying different
timeslot, combining these two half-rate service into one timeslot by intra-cell handover, so
one full-rate channel can be idle. This couner counts the number of handover attempts
due to fragment reorganization.
Usage
This counter is used to find out handover frequency due to combining two half-rate channel
on TCH/H by BSC.
Measurement Point
New call service instance does not apply for full-rate channel, or due to other call service
released, fragment reorganization is issued to do intra-cell handover. It will combine two
half-rate service into one timeslot. The couner increments while one full-rate channel is
idle. The measurement point is A, as shown in Figure 12-52.
Unit
Times
12-56

Related Features

due to energy conservation
Definition
Number of TCH/F handover attempts due to energy conservation
Description
Carrier is powered off intelligently by energy conservation, BSC migrates the service on the
carrier to other carrier by intra-cell handover. This counter counts the number of handover
attempts due to energy conservation on TCH/F by BSC.
Usage
This counter is used to find out handover frequency due to energy conservation on TCH/F
by BSC.
Measurement Point
Carrier is intelligently powered off by energy conservation, do intra-cell handover for the
call service on the carrier to be powered off and migrated to other carrier. If channel type
of handover instance is TCH/F, this counter increments. The measurement point is A, as
12-57

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 Point
Carrier is intelligently powered off by energy conservation, do intra-cell handover for the
call service on the carrier to be powered off and migrated to other carrier. If channel type
of handover instance is TCH/H, this counter increments. The measurement point is A, as
12-58

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 channel
forcedly released.
Usage
This counter is used to find out handover frequency due to CS service seizured by PS on
TCH/F.
12-59

Measurement Point
After PS service channel application is failed, do intra-cell handover for CS service that
occupies PDTCH channel, available PS channel is used by PS service. If channel type of
CS handover instance is TCH/F, this counter increments. The measurement point is A, as
Unit
Times
Related Features

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

Usage
This counter is used to find out handover frequency due to CS service seizured by PS on
TCH/H.
Measurement Point
After PS service channel application is failed, do intra-cell handover for CS service that
occupies PDTCH channel, available PS channel is used by PS service. If channel type of
CS handover instance is TCH/H, this counter increments. The measurement point is A,
Unit
Times
Related Features

due to FR to HR during cell busy
Definition
Number of TCH/F handover attempts due to FR to HR during cell busy
12-61

Description
This counter counts the number of handover attempts due to FR transferred to HR on busy,
it can connect more services.
Usage
This counter is used to find out handover frequency due to FR transferred to HR on busy.
Measurement Point
N/A
Unit
Times

attempts due to downlink rapid drop
Description
This counter counts the number of handover attempts due to too high downlink level on
SDCCH.
Usage
This counter measures the frequency of handover due to the downlink level on SDCCH.
The higher value indicates the higher downlink level on SDCCH.
Measurement Point
This counter increments if the handover decision is done after receiving the measurement
report on SDCCH by BSC and the handover is caused by the rapid downlink drop.
Unit
Times

due to downlink rapid drop
Description
TCH/F.
12-62

Usage
This counter measures the frequency of handover due to the downlink level on TCH/F. The
higher value indicates the higher downlink level on TCH/F.
Measurement Point
report on TCH/F by BSC and the handover is caused by the rapid downlink drop.
Unit
Times

due to downlink rapid drop
Description
TCH/H.
Usage
This counter measures the frequency of handover due to the downlink level on TCH/H.
The higher value indicates the higher downlink level on TCH/H.
Measurement Point
report on TCH/H by BSC and the handover is caused by the rapid downlink drop.
Unit
Times
12-63

12-64

Chapter 13
RMM Call Drop Measurement
Table of Contents
Overview ..................................................................................................................13-3
C901070001 Number of SDCCH drops due to loss of contact with RANA ................13-3
C901070002 Number of SDCCH drops due to radio link failure................................13-4
C901070003 Number of SDCCH drops due to LAPD link failure ..............................13-5
C901070004 Number of SDCCH drops due to OMC-R forced release .....................13-6
C901070005 Number of SDCCH drops due to forced release by other calls.............13-7
C901070007 Number of SDCCH drops due to other failure......................................13-8
C901070008 Number of signaling TCH/F drops due to loss of contact with RANA ...13-9
C901070009 Number of signaling TCH/F drops due to radio link failure .................13-10
C901070010 Number of signaling TCH/F drops due to LAPD link failure................ 13-11
C901070011 Number of signaling TCH/F drops due to OMC-R forced release .......13-12
C901070012 Number of signaling TCH/F drops due to forced release by other
calls........................................................................................................................13-13
C901070014 Number of signaling TCH/F drops due to other failure .......................13-14
C901070015 Number of voice TCH/F drops due to loss of contact with RANA .......13-15
C901070017 Number of voice TCH/F drops due to LAPD link failure .....................13-17
C901070018 Number of voice TCH/F drops due to OMC-R forced release ............13-19
C901070019 Number of voice TCH/F drops due to forced release by other calls....13-20
C901070021 Number of voice TCH/F drops due to other failure.............................13-22
C901070022 Number of data TCH/F drops due to loss of contact with RANA ........13-23
C901070023 Number of data TCH/F drops due to radio link failure ........................13-24
C901070024 Number of data TCH/F drops due to LAPD link failure.......................13-26
C901070025 Number of data TCH/F drops due to OMC-R forced release..............13-27
C901070026 Number of data TCH/F drops due to forced release by other calls .....13-29
C901070028 Number of data TCH/F drops due to other failure ..............................13-30
C901070029 Number of signaling TCH/H drops due to loss of contact with RANA .13-31
C901070030 Number of signaling TCH/H drops due to radio link failure.................13-33
C901070031 Number of signaling TCH/H drops due to LAPD link failure ...............13-34
C901070032 Number of signaling TCH/H drops due to OMC-R forced release ......13-35
C901070033 Number of signaling TCH/H drops due to forced release by other
calls........................................................................................................................13-36
C901070035 Number of signaling TCH/H drops due to other failure.......................13-37
C901070036 Number of voice TCH/H drops due to loss of contact with RANA.......13-38
C901070038 Number of voice TCH/H drops due to LAPD link failure .....................13-39
C901070039 Number of voice TCH/H drops due to OMC-R forced release ............13-41
C901070040 Number of voice TCH/H drops due to forced release by other calls ...13-42
C901070042 Number of voice TCH/H drops due to other failure ............................13-44
13-1

C901070043 Number of data TCH/H drops due to loss of contact with RANA ........13-45
C901070044 Number of data TCH/H drops due to radio link failure........................13-46
C901070045 Number of data TCH/H drops due to LAPD link failure ......................13-48
C901070046 Number of data TCH/H drops due to OMC-R forced release .............13-49
C901070047 Number of data TCH/H drops due to forced release by other calls.....13-51
C901070049 Number of data TCH/H drops due to other failure..............................13-52
C901070053 Number of SDCCH link failures .........................................................13-54
C901070054 Number of TCH/F link failures ...........................................................13-55
C901070055 Number of TCH/H link failures ...........................................................13-57
C901070056 Number of RANA link releases due to other cause on SDCCH..........13-58
C901070057 Number of RANA link releases due to other cause on TCH/F ............13-59
C901070058 Number of RANA link releases due to other cause on TCH/H............13-60
C901070059 Number of SDCCH short messages drops ........................................13-61
C901070060 Number of TCH/F short messages drops ..........................................13-62
C901070061 Number of TCH/H short messages drops ..........................................13-62
C901070062 Number of TCH/F drops due to CS channel is forced release by PS .13-63
C901070063 Number of TCH/H drops due to CS channel is forced release by PS .13-64
C901070064 Number of SDCCH drops due to eMLPP forced handover.................13-64
C901070065 Number of signaling TCH/F drops due to eMLPP forced handover ....13-65
C901070066 Number of voice TCH/F drops due to eMLPP forced handover..........13-66
C901070067 Number of data TCH/F drops due to eMLPP forced handover ...........13-67
C901070068 Number of sigaling TCH/H drops due to eMLPP forced handover......13-68
C901070069 Number of voice TCH/H drops due to eMLPP forced handover .........13-69
C901070070 Number of data TCH/H drops due to eMLPP forced handover...........13-70
C901070071 Bad quality of UL receiving (On SDCCH) ..........................................13-71
C901070072 Bad quality of DL receiving (On SDCCH) ..........................................13-72
C901070073 Lower electrical level of UL (On SDCCH) ..........................................13-73
C901070074 Lower electrical level of DL (On SDCCH) ..........................................13-74
C901070075 Number of signaling drops due to TA too far (On SDCCH) ................13-75
C901070076 Reasons of the other radios (On SDCCH) .........................................13-76
C901070077 Bad quality of UL receiving (On TCH/F).............................................13-77
C901070078 Bad quality of DL receiving (On TCH/F).............................................13-78
C901070079 Lower electrical level of UL (On TCH/F) ............................................13-79
C901070080 Lower electrical level of DL (On TCH/F) ............................................13-81
C901070081 Number of signaling drops due to TA too far (On TCH/F)...................13-82
C901070082 Reasons of the other radios (On TCH/F) ...........................................13-84
C901070083 Bad quality of UL receiving (On TCH/H) ............................................13-85
C901070084 Bad quality of DL receiving (On TCH/H) ............................................13-87
C901070085 Lower electrical level of UL (On TCH/H) ............................................13-88
C901070086 Lower electrical level of DL (On TCH/H) ............................................13-90
C901070087 Number of signaling drops due to TA too far (On TCH/H) ..................13-91
C901070088 Reasons of the other radios (On TCH/H) ...........................................13-93
C901070089 The Count of Drop Call caused by "IP Resource Reset" ....................13-94
C901070090 Number of FR_V1 radio link fail .........................................................13-95
13-2

Chapter 13 RMM Call Drop Measurement

C901070093 Number of HR_V1 radio link fail ........................................................13-97
C901070094 Number of HR_V3 radio link fail ........................................................13-97
13.1 Overview
Channels that take part in the measurement statistic include SDCCH, TCH/F and TCH/H.
Service types include signaling, voice and data. Counted call drop causes include RMM
losses contact with SMM, BTS radio link failure, LAPD link failure, OMCR forced release,
forced release by other calls, handover failure, as well as other failure.
13.2 C901070001 Number of 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 Point
The counter counts the number of failures due to loss of contact with SMM in the following
two cases:
l 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
13-3

Figure 13-1 Call Drop Due To A-Interface Failure In Immediate Assignment Process
l 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
Unit
Times
13.3 C901070002 Number of SDCCH drops due to radio

link failure
Definition
Number of SDCCH drops due to radio link failure
Description
This counter counts the number of call drop due to radio link failures (On SDCCH). The
counter increments if the phenomenon that call drops after MS has obtained SDCCH is
caused by radio link failures.
Usage
This counter is used to find out the frequency of call drop due to radio link failures (On
SDCCH).
Measurement Point
The counter increments when BSC receives CONNectiOn FAILure INDicatiOn
message on Abis interface on SDCCH. The measurement point is A, as shown in Figure
13-2.
13-4

Figure 13-2 Call Drop Due To Radio Link Failure In Immediate Assignment Process
Unit
Times
Related Features
ZGO-04-02-007 AMR Radio Link Timers

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 failures (On SDCCH). The
counter increments if the phenomenon that call drops after MS has obtained SDCCH is
caused by LAPD link failures.
Usage
This counter is used to find out the frequency of call drop due to LAPD link failures (On
SDCCH).
Measurement Point
The counter increments when BSC receives DLREL_IND message from LAPD on SDCCH.
13-5

Figure 13-3 Call Drop Due To Lapd Link Failure In Immediate Assignment Process
Unit
Times

OMC-R forced release
Definition
Number of SDCCH drops due to OMC-R forced release
Description
This counter counts the number of call drop due to OMC-R forced releases (on SDCCH).
The counter increments if the phenomenon that call drops after MS has obtained SDCCH
is caused by OMC-R forced releases.
Usage
This counter is used to find out the frequency of call drop due to OMC-R forced releases
(on SDCCH).
Measurement Point
The counter increments when BSC receives OMC-R forced release message from
database on SDCCH. The measurement point is A, as shown in Figure 13-4.
13-6

Figure 13-4 Call Drop Due To OMC-R Forced Release In Immediate Assignment Process
Unit
Times

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 phenomenon that call drops after MS has obtained
SDCCH is caused by forced releases by other calls.
Usage
This counter is used to find out the frequency of call drop due to forced releases by other
calls (On SDCCH).
Measurement Point
The counter increments when BSC receives forced release message from other calls on
SDCCH. The measurement point is A, as shown inFigure 13-5.
13-7

Figure 13-5 Call Drop Due To Forced Release By Other Calls In Immediate Assignment
Process
Unit
Times
13.7 C901070007 Number of 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 T3101 is overtime under WAIT_ACCESS status. Timer
that waits for access indicates the time from radio resource available message is sent to
assignment/handover is finished. T3101 indicates the time from IMM_ASS message is sent
to EST_IND message is received from MS.
Usage
This counter is used to find out the frequency of call drop due to other failures (On SDCCH).
13-8

Measurement Point
The counter increments when T3107 is overtime under ASSIGN status on SDCCH, or
when timer that waits for access is overtime or T3101 is overtime under WAIT_ACCESS
status. The measurement point is A, as shown in Figure 13-6.
Figure 13-6 Call Drop Due To T3101 Overtime In Intra-Cell Handover
Unit
Times

due 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 increments if the phenomenon that call drops after
MS has obtained TCH/F signaling channel is caused by failures due to RANCS losing
contact with RANA.
Usage
This counter is used to find out the frequency of failures due to RANCS losing contact with
RANA (on TCH/F signaling channel).
Measurement Point
The counter counts the number of failures due to loss of contact with RANA (On TCH/F
signaling) in the following two cases:
13-9

l After link between RANCS and RANA has been established on 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 13-7.
l RANCS forwards EST_IND message to RANA after receiving it on TCH/F signaling;
if no link establishment message on A-interface from RANA is received, the counter
increments; meanwhile, BSC releases the channel and instance, the measurement
point is A2, as shown inFigure 13-7.
Unit
Times
Related Features

due to radio link failure
Definition
Number of signaling TCH/F drops due to radio link failure
Description
This counter counts the number of call drop due to radio link failures (On TCH/F signaling).
The counter increments if the phenomenon that call drops after MS has obtained TCH/F
signaling channel is caused by radio link failures.
Usage
This counter is used to find out the frequency of call drop due to radio link failures (On
TCH/F signaling).
13-10

Measurement Point
message on Abis interface on TCH/F signaling channel. The measurement point is A, as
shown inFigure 13-8.
Unit
Times
Related Features

due 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 failures (on TCH/F signaling
channel). The counter increments if the phenomenon that call drops after MS has obtained
TCH/F signaling channel is caused by LAPD link failures.
13-11

Usage
This counter is used to find out the frequency of call drop due to LAPD link failures (on
TCH/F signaling channel).
Measurement Point
The counter increments when BSC receives DLREL_IND message from LAPD on TCH/F
signaling channel. The measurement point is A, as shown in Figure 13-9.
Figure 13-9 Call Drop Due To LAPD Link Failure In Immediate Assignment Process
Unit
Times
Related Features

due to OMC-R forced release
Definition
Number of signaling TCH/F drops due to OMC-R forced release
Description
This counter counts the number of call drop due to OMC-R forced 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.
13-12

Usage
(on TCH/F signaling channel).
Measurement Point
database on TCH/F signaling channel. The measurement point is A, as shown in Figure
13-10.
Figure 13-10 Call Drop Due To OMC-R Forced Release In Immediate Assignment
Process
Unit
Times
Related Features

due to forced release by other calls
Definition
Number of signaling TCH/F 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 TCH/F
has obtained TCH/F signaling channel is caused by forced releases by other calls.
13-13

Usage
calls (on TCH/F signaling channel).
Measurement Point
TCH/F signaling channel. The measurement point is A, as shown in Figure 13-11.
Process
Unit
Times
Related Features

due to other failure
Definition
Number of signaling TCH/F drops due to other failure
Description
This counter counts the number of call drop due to other failures (on TCH/F signaling
TCH/F signaling channel is caused by other failures except the causes mentioned above
(loss of contact with RANA, radio link failure, LAPD link failure, OMCR forced release,
forced release by other calls, handover failure).
13-14

At present, other failure causes are that T3107 is overtime under ASSIGN status, timer that
waits for access is overtime and T3101 is overtime under WAIT_ACCESS status. Timer
that waits for access indicates the time from radio resource available message is sent to
assignment/handover is finished. T3101 indicates the time from IMM_ASS message is sent
to EST_IND message is received from MS.
Usage
This counter is used to find out the frequency of call drop due to other failures (on TCH/F
signaling channel).
Measurement Point
The counter increments when T3107 is overtime under ASSIGN status on TCH/F
signaling channel, or when timer that waits for access is overtime or T3101 is overtime
under WAIT_ACCESS status. The measurement point is A, as shown in Figure 13-12.
Unit
Times
Related Features

to loss of contact with RANA
Definition
Number of voice TCH/F drops due to loss of contact with RANA
13-15

Description
TCH/F voice channel). The counter increments if the phenomenon that call drops after
MS has obtained TCH/F voice channel is caused by failures due to RANCS losing contact
with RANA (on TCH/F voice channel).
Usage
RANA (on TCH/F voice channel).
Measurement Point
The counter counts the number of failures due to loss of contact with RANA (on TCH/F
voice channel) in the following two cases:
l After link between RANCS and RANA has been established on TCH/F voice 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.
l 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
13-16

Figure 13-13 Call Drop Due To A-Interface Failure In Assignment Process
Unit
Times
Related Features

to LAPD link failure
Definition
Number of voice TCH/F drops due to LAPD link failure
Description
This counter counts the number of call drop due to LAPD link failures (on TCH/F voice
TCH/F voice channel is caused by LAPD link failures.
13-17

Usage
TCH/F voice channel).
Measurement Point
The counter increments when BSC receives DLREL_INDmessage from LAPD on TCH/F
voice channel. The measurement point is A, as shown in Figure 13-14.
Figure 13-14 Call Drop Due To LAPD Link Failure In Assignment Process
Unit
Times
Related Features
13-18


to OMC-R forced release
Definition
Number of voice TCH/F drops due to OMC-R forced release
Description
voice channel). The counter increments if the phenomenon that call drops after MS has
obtained TCH/F voice channel is caused by OMC-R forced releases.
Usage
(on TCH/F voice channel).
Measurement Point
database on TCH/F voice channel. The measurement point is A, as shown in Figure
13-15.
13-19

Figure 13-15 Call Drop Due To OMC-R Forced Release In Assignment Process
Unit
Times
Related Features

to forced release by other calls
Definition
Number of voice TCH/F drops due to forced release by other calls
13-20

Description
obtained TCH/F voice channel is caused by forced releases by other calls.
Usage
calls (on TCH/F voice channel).
Measurement Point
TCH/F voice channel. The measurement point is A, as shown in Figure 13-16.
Figure 13-16 Call Drop Due To Forced Release By Other Calls In Assignment Process
Unit
Times
13-21

Related Features

to other failure
Definition
Number of voice TCH/F drops due to other failure
Description
This counter counts the number of call drop due to other failures (on TCH/F voice channel).
It indicates the call drop case at call establishment phase due to assignment failure. The
counter increments if the phenomenon that call drops after MS has obtained TCH/F voice
channel is caused by other failures except the causes mentioned above (loss of contact
with RANA, radio link failure, LAPD link failure, OMCR forced release, forced release by
other calls, handover failure).
At present, other failure causes are that T3107 is overtime under ASSIGN status, timer
that waits for access is overtime and T3101 is overtime under WAIT_ACCESS status.
This counter does not count the call drops due to intra-cell handover failure.
Usage
voice channel).
Measurement Point
The counter increments when T3107 is overtime under ASSIGN status on TCH/F voice
channel, or when timer that waits for access is overtime or T3101 is overtime under
WAIT_ACCESS status. The measurement point is A, as shown in Figure 13-17.
13-22

Unit
Times
Related Features
13.19 C901070022 Number of data TCH/F drops due to

loss of contact with RANA
Definition
Number of data TCH/F drops due to loss of contact with RANA
Description
TCH/F data channel). The counter increments if the phenomenon that call drops after MS
has obtained TCH/F data channel is caused by failures due to RANCS losing contact with
RANA (on TCH/F data channel).
Usage
RANA (on TCH/F data channel).
Measurement Point
The counter counts the number of failures due to loss of contact with RANA (on TCH/F
data channel) in the following two cases:
l After link between RANCS and RANA has been established on TCH/F data channel,
13-23

l RANCS forwards EST_IND message to RANA after receiving it on TCH/F data
channel; if no link establishment message on A-interface from RANA is received, the
counter increments; meanwhile, BSC releases the channel and instance.
Unit
Times
Related Features

Definition
Number of data TCH/F drops due to radio link failure
13-24

Description
This counter counts the number of call drop due to radio link failures (on TCH/F data
TCH/F data channel is caused by radio link failures.
Usage
This counter is used to find out the frequency of call drop due to radio link failures (on
TCH/F data channel).
Measurement Point
message on Abis interface on TCH/F data channel. The measurement point is A, as
Figure 13-19 Call Drop Due To Radio Link Failure In Assignment Process
Unit
Times
13-25

Related Features

Definition
Number of data TCH/F drops due to LAPD link failure
Description
This counter counts the number of call drop due to LAPD link failures (on TCH/F data
TCH/F data channel is caused by LAPD link failures.
Usage
TCH/F data channel).
Measurement Point
The counter increments when BSC receives DLREL_IND message from LAPD on TCH/F
data channel. The measurement point is A, as shown in Figure 13-20.
13-26

Figure 13-20 Call Drop Due To Lapd Link Failure In Assignment Process
Unit
Times
Related Features

Definition
Number of data TCH/F drops due to OMC-R forced release
13-27

Description
data channel). The counter increments if the phenomenon that call drops after MS has
obtained TCH/F data channel is caused by OMC-R forced releases.
Usage
(on TCH/F data channel).
Measurement Point
database on TCH/F data channel. The measurement point is A, as shown in Figure 13-21.
Unit
Times
13-28

Related Features

Definition
Number of data TCH/F drops due to forced release by other calls
Description
obtained TCH/F data channel is caused by forced releases by other calls.
Usage
calls (on TCH/F data channel).
Measurement Point
TCH/F data channel. The measurement point is A, as shown in Figure 13-22.
13-29

Unit
Times
Related Features

to other failure
Definition
Number of data TCH/F drops due to other failure
Description
This counter counts the number of call drop due to other failures (on TCH/F data channel).
The counter increments if the phenomenon that call drops after MS has obtained TCH/F
13-30

data channel is caused by other failures except the causes mentioned above (loss of
contact with RANA, radio link failure, LAPD link failure, OMCR forced release, forced
release by other calls, handover failure).
Usage
data channel).
Measurement Point
The counter increments when T3107 is overtime under ASSIGN status on TCH/F data
Unit
Times
Related Features

due to loss of contact with RANA
Definition
Number of signaling TCH/H drops due to loss of contact with RANA
13-31

Description
TCH/H signaling channel). The counter increments if the phenomenon that call drops after
MS has obtained TCH/H signaling channel is caused by failures due to RANCS losing
contact with RANA (on TCH/H signaling channel).
Usage
RANA (on TCH/H signaling channel).
Measurement Point
The counter counts the number of failures due to loss of contact with RANA (on TCH/H
signaling channel) in the following two cases:
l After link between RANCS and RANA has been established on TCH/H signaling
channel, heartbeat handshake is carried out. If RANCS or RANA can not receive
heartbeat message from each other during 4 unit times, then it is regarded as link
failure and the counter increments; meanwhile, BSC releases the channel and
instance, the measurement point is A1, as shown in Figure 13-24.
l RANCS forwards EST_IND message to RANA after receiving it on TCH/H signaling;
if no link establishment message on A-interface from RANA is received, the counter
increments; meanwhile, BSC releases the channel and instance, the measurement
Unit
Times
Related Features
13-32


due to radio link failure
Definition
Number of signaling TCH/H drops due to radio link failure
Description
This counter counts the number of call drop due to radio link failures (on TCH/H signaling
TCH/H signaling channel is caused by radio link failures.
Usage
TCH/H signaling channel).
Measurement Point
message on Abis interface on TCH/H signaling channel. The measurement point is A, as
Unit
Times
Related Features
13-33



due to LAPD link failure
Definition
Number of signaling TCH/H drops due to LAPD link failure
Description
This counter counts the number of call drop due to LAPD link failures (on TCH/H signaling
TCH/H signaling channel is caused by LAPD link failures.
Usage
TCH/H signaling channel).
Measurement Point
The counter increments when BSC receives DLREL_IND message from LAPD on TCH/H
signaling channel. The measurement point is A, as shown in Figure 13-26.
Figure 13-26 Call Drop Due To LAPD Link Failure In Immediate Assignment Process
Unit
Times
13-34

Related Features

due to OMC-R forced release
Definition
Number of signaling TCH/H drops due to OMC-R forced release
Description
This counter counts the number of call drop due to OMC-R forced releases (on TCH/H
has obtained TCH/H signaling channel is caused by OMC-R forced releases.
Usage
(on TCH/H signaling channel).
Measurement Point
database on TCH/H signaling channel. The measurement point is A, as shown in Figure
13-27.
Figure 13-27 Call Drop Due To OMC-R Forced Release In Immediate Assignment
Process
Unit
Times
13-35

Related Features

due to forced release by other calls
Definition
Number of signaling TCH/H 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 TCH/H
has obtained TCH/H signaling channel is caused by forced releases by other calls.
Usage
calls (on TCH/H signaling channel).
Measurement Point
TCH/H signaling channel. The measurement point is A, as shown in Figure 13-28.
Process
Unit
Times
13-36

Related Features

due to other failure
Definition
Number of signaling TCH/H drops due to other failure
Description
This counter counts the number of call drop due to other failures (on TCH/H signaling
TCH/H signaling channel is caused by other failures except the causes mentioned above
(loss of contact with RANA, radio link failure, LAPD link failure, OMCR forced release,
forced release by other calls, handover failure).
Usage
This counter is used to find out the frequency of call drop due to other failures (on TCH/H
signaling channel).
Measurement Point
The counter increments when T3107 is overtime under ASSIGN status on TCH/H
signaling channel, or when timer that waits for access is overtime or T3101 is overtime
under WAIT_ACCESS status. The measurement point is A, as shown in Figure 13-29.
13-37

Unit
Times
Related Features

to loss of contact with RANA
Definition
Number of voice TCH/H drops due to loss of contact with RANA
Description
TCH/H voice channel). The counter increments if the phenomenon that call drops after
MS has obtained TCH/H voice channel is caused by failures due to RANCS losing contact
with RANA (on TCH/H voice channel).
Usage
RANA (on TCH/H voice channel).
Measurement Point
voice channel) in the following two cases:
l After link between RANCS and RANA has been established on TCH/H voice channel,
l RANCS forwards EST_INDmessage to RANA after receiving it on TCH/H voice
13-38

Unit
Times
Related Features

Definition
Number of voice TCH/H drops due to LAPD link failure
Description
This counter counts the number of call drop due to LAPD link failures (on TCH/H voice
TCH/H voice channel is caused by LAPD link failures.
13-39

Usage
TCH/H voice channel).
Measurement Point
voice channel. The measurement point is A, as shown in Figure 13-31.
Unit
Times
Related Features
13-40


Definition
Number of voice TCH/H drops due to OMC-R forced release
Description
obtained TCH/H voice channel is caused by OMC-R forced releases.
Usage
(on TCH/H voice channel).
Measurement Point
database on TCH/H voice channel. The measurement point is A, as shown in Figure
13-32.
13-41

Unit
Times
Related Features

to forced release by other calls
Definition
Number of voice TCH/H drops due to forced release by other calls
13-42

Description
obtained TCH/H voice channel is caused by forced releases by other calls.
Usage
calls (on TCH/H voice channel).
Measurement Point
TCH/H voice channel. The measurement point is A, as shown in Figure 13-33.
Unit
Times
13-43

Related Features

to other failure
Definition
Number of voice TCH/H drops due to other failure
Description
This counter counts the number of call drop due to other failures (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 other failures except the causes mentioned above (loss of
Usage
voice channel).
Measurement Point
The counter increments when T3107 is overtime under ASSIGN status on TCH/H voice
13-44

Unit
Times
Related Features
13.36 C901070043 Number of data TCH/H drops due to

loss of contact with RANA
Definition
Number of data TCH/H drops due to loss of contact with RANA
Description
TCH/H data channel). The counter increments if the phenomenon that call drops after MS
has obtained TCH/H data channel is caused by failures due to RANCS losing contact with
RANA (on TCH/H data channel).
Usage
RANA (on TCH/H data channel).
Measurement Point
data channel) in the following two cases:
l After link between RANCS and RANA has been established on TCH/H data channel,
l RANCS forwards EST_IND message to RANA after receiving it on TCH/H data
13-45

Unit
Times
Related Features

Definition
Number of data TCH/H drops due to radio link failure
Description
This counter counts the number of call drop due to radio link failures (on TCH/H data
TCH/H data channel is caused by radio link failures.
13-46

Usage
TCH/H data channel).
Measurement Point
message on Abis interface on TCH/H data channel. The measurement point is A, as
Unit
Times
Related Features
13-47


Definition
Number of data TCH/H drops due to LAPD link failure
Description
This counter counts the number of call drop due to LAPD link failures (on TCH/H data
TCH/H data channel is caused by LAPD link failures.
Usage
TCH/H data channel).
Measurement Point
data channel. The measurement point is A, as shown in Figure 13-37.
13-48

Unit
Times
Related Features

Definition
Number of data TCH/H drops due to OMC-R forced release
13-49

Description
obtained TCH/H data channel is caused by OMC-R forced releases.
Usage
(on TCH/H data channel).
Measurement Point
The counter increments when BSC receives OMCR forced release message from
database on TCH/H data channel. The measurement point is A, as shown in Figure
13-38.
Figure 13-38 Call Drop Due To Omc-R Forced Release In Assignment Process
Unit
Times
13-50

Related Features

Definition
Number of data TCH/H drops due to forced release by other calls
Description
obtained TCH/H data channel is caused by forced releases by other calls.
Usage
calls (on TCH/H data channel).
Measurement Point
TCH/H data channel. The measurement point is A, as shown in Figure 13-39.
13-51

Unit
Times
Related Features

to other failure
Definition
Number of data TCH/H drops due to other failure
13-52

Description
This counter counts the number of call drop due to other failures (on TCH/H data channel).
The counter increments if the phenomenon that call drops after MS has obtained TCH/H
data channel is caused by other failures except the causes mentioned above (loss of
Usage
data channel).
Measurement Point
The counter increments when T3107 is overtime under ASSIGN status on TCH/H data
Unit
Times
Related Features
13-53

13.42 C901070053 Number of SDCCH link failures

Definition
Number of SDCCH link failures
Description
This counter counts the number of SDCCH link failures. The counter increments when
RANA launches abnormal release flow to RANCS due to SCCP link failure after MS has
obtained SDCCH.
Usage
This counter is used to find out the frequency of SDCCH link failures.
Measurement Point
The counter counts the number of abnormal release flow launched by RANA to RANCS
due to SCCP link failure on SDCCH, including the following cases:
l T9105 is overtime, the measurement point is A2, as shown in Figure 13-41.
Figure 13-41 Call Drop Due To Sccp Failure In Immediate Assignment Process
13-54

l T9104 is overtime and the number of maximum failure times is reached, the
l 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
l BSC receives MSC reset message.
l CONNECT_ID requested by RANA is failed.
l BSC receives link release command from MSC.
Unit
Times
13.43 C901070054 Number of 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
obtained TCH/F.
Usage
This counter is used to find out the frequency of TCH/F link failures.
Measurement Point
due to SCCP link failure on TCH/F in the following cases:
13-55

Figure 13-42 Call Drop Due To Sccp Failure In Immediate Assignment Process
l T9101 is overtime, the measurement point is A4, as shown inFigure 13-42.
Unit
Times
Related Features
13-56

13.44 C901070055 Number of 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
obtained TCH/H.
Usage
This counter is used to find out the frequency of TCH/H link failures.
Measurement Point
due to SCCP link failure on TCH/H in the following cases:
Figure 13-43 Call Drop Due To SCCP Failure In Immediate Assignment Process
13-57

Unit
Times
Related Features
13.45 C901070056 Number of RANA link releases due

to other cause on SDCCH
Definition
Number of RANA link releases due to other cause on SDCCH
Description
This counter counts the number of RANA link releases by other cause on SDCCH (except
that SCCP link release command message is received). The counter increments if RANA
link release occurs after MS has obtained SDCCH.
Usage
This counter is used to find out the frequency of RANA link releases by other cause on
SDCCH.
Measurement Point
The counter increments when the content of HO_REQ message is incorrect. The
13-58

Figure 13-44 Call Drop Due To Inter-BSC Handover Failure
Unit
Times

to other cause on TCH/F
Definition
Number of RANA link releases due to other cause on TCH/F
Description
This counter counts the number of RANA link releases by other cause on TCH/F (except
link release occurs after MS has obtained TCH/F.
Usage
TCH/F.
Measurement Point
13-59

Unit
Times
Related Features

to other cause on TCH/H
Definition
Number of RANA link releases due to other cause on TCH/H
Description
This counter counts the number of RANA link releases by other cause on TCH/H (except
link release occurs after MS has obtained TCH/H.
Usage
TCH/H.
Measurement Point
13-60

Unit
Times
Related Features
13.48 C901070059 Number of 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 messages drops.
Measurement Point
The counter increments when call drops due to radio link failure or LAPD link release or
handover failure while doing short message service.
Unit
Times
13-61

13.49 C901070060 Number of 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. The counter increments
when call drops after MS has obtained TCH/F for short message service.
Usage
This counter is used to find out the frequency of TCH/F short messages drops.
Measurement Point
Unit
Times
Related Features

13.50 C901070061 Number of 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. The counter increments
when call drops after MS has obtained TCH/H for short message service.
Usage
This counter is used to find out the frequency of TCH/H short messages drops.
13-62

Measurement Point
Unit
Times
Related Features
13.51 C901070062 Number of TCH/F drops due to CS

channel is forced release by PS
Definition
Number of TCH/F drops due to CS channel is forced release by PS
Description
When CS service channel is forcibly released due to PS service, handover is initiated, and
call drop will occur if TCH/F channel request fails. In such a case, the counter increments.
Usage
This counter is used to find out the frequency of call drops due to TCH/F channel request
failure when CS service channel is forcedly released due to PS service.
Measurement Point
The counter increments when call drops due to TCH/F channel request failure when CS
service is forcedly released due to PS service.
Unit
Times
Related Features
13-63

13.52 C901070063 Number of TCH/H drops due to CS

channel is forced release by PS
Definition
Number of TCH/H drops due to CS channel is forced release by PS
Description
When CS service channel is forcibly released due to PS service, handover is initiated, and
call drop will occur if TCH/H channel request fails. In such a case, the counter increments.
Usage
This counter is used to find out the frequency of call drops due to TCH/H channel request
failure when CS service channel is forcedly released due to PS service.
Measurement Point
The counter increments when call drops due to TCH/H channel request failure when CS
service is forcedly released due to PS service.
Unit
Times
Related Features

eMLPP forced handover
Definition
Number of SDCCH drops due to eMLPP forced handover
Description
This counter counts the number of call drops on SDCCH due to eMLPP forced handover.
After MS obtains SDCCH, call drop occurs. If the problem is caused by eMLPP forced
handover, the counter increments.
Usage
This counter is used to find out the frequency of call drop on SDCCH due to eMLPP forced
handover.
13-64

Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on SDCCH.
Figure 13-47 Measurement Point Of Number Of SDCCH Drops Due To eMLPP Forced
Handover
Unit
Times

due to eMLPP forced handover
Definition
Number of signaling TCH/F drops due to eMLPP forced handover
Description
This counter counts the number of call drops on signaling TCH/F due to eMLPP forced
handover. After MS obtains signaling TCH/F, call drop occurs. If the problem is caused by
eMLPP forced handover, the counter increments.
Usage
This counter is used to find out the frequency of call drop on signaling TCH/F due to eMLPP
forced handover
Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on signaling
TCH/F. The measurement point is A, as shown in Figure 13-48.
13-65

Handover
Unit
Times

to eMLPP forced handover
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
Usage
This counter is used to find out the frequency of call drop on voice TCH/F due to eMLPP
forced handover.
Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on voice
13-66

Handover
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 occurs. If the problem is caused by
Usage
This counter is used to find out the frequency of call drop on data TCH/F due to eMLPP
forced handover.
Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on data
13-67

Handover
Unit
Times
13.57 C901070068 Number of sigaling TCH/H drops

due to eMLPP forced handover
Definition
Number of signaling TCH/H drops due to eMLPP forced handover
Description
This counter counts the number of call drops on signaling TCH/H due to eMLPP forced
handover. After MS obtains signaling TCH/H, call drop occurs. If the problem is caused
by eMLPP forced handover, the counter increments.
Usage
This counter is used to find out the frequency of call drop on signaling TCH/H due to eMLPP
forced handover.
Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on signaling
TCH/H. The measurement point is A, as shown in Figure 13-51.
13-68

Handover
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 occurs. If the problem is caused by
Usage
This counter is used to find out the frequency of call drop on voice TCH/H due to eMLPP
forced handover.
Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on voice
13-69

Handover
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 occurs. If the problem is caused by
Usage
This counter is used to find out the frequency of call drop on data TCH/H due to eMLPP
forced handover.
Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on data
13-70

Handover
Unit
Times
13.60 C901070071 Bad quality of UL receiving (On

SDCCH)
Definition
Bad quality of UL receiving (On SDCCH)
Description
This counter counts the number of call drops on SDCCH due to radio link failure. After MS
obtains SDCCH, call drop occurs. If the problem is caused by bad uplink receiving quality,
Usage
This counter is used to find out the frequency of call drop on SDCCH due to radio link
failure which is caused by bad uplink receiving quality.
Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn
message at Abis interface on SDCCH. The measurement point is A, as shown in Figure
13-54.
13-71

Unit
Times
13.61 C901070072 Bad quality of DL receiving (On

SDCCH)
Definition
Bad quality of DL receiving (On SDCCH)
Description
This counter counts the number of call drops on SDCCH due to radio link failure. After
MS obtains SDCCH, call drop occurs. If the problem is caused by bad downlink receiving
quality, the counter increments.
Usage
failure which is caused by bad downlink receiving quality.
Measurement Point
13-55.
13-72

Unit
Times
13.62 C901070073 Lower electrical level of UL (On

SDCCH)
Definition
Lower electrical level of UL (On SDCCH)
Description
obtains SDCCH, call drop occurs. If the problem is caused by low uplink receiving level,
Usage
failure which is caused by low uplink receiving level.
Measurement Point
13-56.
13-73

Unit
Times
13.63 C901070074 Lower electrical level of DL (On

SDCCH)
Definition
Lower electrical level of DL (On SDCCH)
Description
This counter counts the number of call drops on SDCCH due to radio link failure. After
MS obtains SDCCH, call drop occurs. If the problem is caused by low downlink receiving
level, the counter increments.
Usage
failure which is caused by low downlink receiving level.
Measurement Point
13-57.
13-74

Unit
Times
13.64 C901070075 Number of signaling drops due to

TA too far (On SDCCH)
Definition
Number of signaling drops due to TA too far (On SDCCH)
Description
obtains SDCCH, call drop occurs. If the problem is caused by TA being too far, the counter
increments.
Usage
failure which is caused by TA being too far.
Measurement Point
13-58.
13-75

Unit
Times
13.65 C901070076 Reasons of the other radios (On

SDCCH)
Definition
Reasons of the other radios (On SDCCH)
Description
obtains SDCCH, call drop occurs. If the problem is not due to the above five causes (i.e.
bad uplink receiving quality, bad downlink receiving quality, low uplink receiving level, low
downlink receiving level, and TA being too far), the counter increments.
Usage
failure which is caused by other radio problems.
Measurement Point
13-59.
13-76

Unit
Times

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 radio link failure. After MS
obtains TCH/F, call drop occurs. If the problem is caused by bad uplink receiving quality,
Usage
This counter is used to find out the frequency of call drop on TCH/F due to radio link failure
which is caused by bad uplink receiving quality.
Measurement Point
message at Abis interface on TCH/F. The measurement point is A, as shown in Figure
13-60.
13-77

Unit
Times

TCH/F)
Definition
Bad quality of DL receiving (On TCH/F)
Description
obtains TCH/F, call drop occurs. If the problem is caused by bad downlink receiving quality,
Usage
which is caused by bad downlink receiving quality.
Measurement Point
13-61.
13-78

Unit
Times

TCH/F)
Definition
Lower electrical level of UL (On TCH/F)
Description
obtains TCH/F, call drop occurs. If the problem is caused by low uplink receiving level, the
counter increments.
13-79

Usage
which is caused by low uplink receiving level.
Measurement Point
13-62.
Unit
Times
13-80


TCH/F)
Definition
Lower electrical level of DL (On TCH/F)
Description
obtains TCH/F, call drop occurs. If the problem is caused by low downlink receiving level,
Usage
which is caused by low downlink receiving level.
Measurement Point
13-63.
13-81

Unit
Times

TA too far (On TCH/F)
Definition
Number of signaling drops due to TA too far (On TCH/F)
Description
obtains TCH/F, call drop occurs. If the problem is caused by TA being too far, the counter
increments.
13-82

Usage
which is caused by TA being too far.
Measurement Point
13-64.
Unit
Times
13-83


TCH/F)
Definition
Reasons of the other radios (On TCH/F)
Description
obtains TCH/F, call drop occurs. If the problem is not due to the above five causes (i.e.
Usage
which is caused by other radio problems.
Measurement Point
13-65.
13-84

Unit
Times

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,
13-85

Usage
This counter is used to find out the frequency of call drop on TCH/H due to radio link failure
which is caused by bad uplink receiving quality.
Measurement Point
message at Abis interface on TCH/H. The measurement point is A, as shown in Figure
13-66.
Unit
Times
13-86


TCH/H)
Definition
Bad quality of DL 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 downlink receiving
quality, the counter increments.
Usage
which is caused by bad downlink receiving quality.
Measurement Point
13-67.
13-87

Unit
Times

TCH/H)
Definition
Lower electrical level of UL (On TCH/H)
Description
obtains TCH/H, call drop occurs. If the problem is caused by low uplink receiving level,
13-88

Usage
which is caused by low uplink receiving level.
Measurement Point
13-68.
Unit
Times
13-89


TCH/H)
Definition
Lower electrical level of DL (On TCH/H)
Description
obtains TCH/H, call drop occurs. If the problem is caused by low downlink receiving level,
Usage
which is caused by low downlink receiving level.
Measurement Point
13-69.
13-90

Unit
Times

TA too far (On TCH/H)
Definition
Number of signaling drops due to TA too far (On TCH/H)
Description
obtains TCH/H, call drop occurs. If the problem is caused by TA being too far, the counter
increments.
13-91

Usage
which is caused by TA being too far.
Measurement Point
13-70.
Unit
Times
13-92


TCH/H)
Definition
Reasons of the other radios (On TCH/H)
Description
obtains TCH/H, call drop occurs. If the problem is not due to the above five causes (i.e.
Usage
which is caused by other radio problems.
Measurement Point
13-71.
13-93

Unit
Times
13.78 C901070089 The Count of Drop Call caused by

"IP Resource Reset"
Statistics object
CELL
Description
On the premise that the 3GPP IPA function is implemented, during the IP resource resetting
process (initiated at MSC or at BSC), BSC releases relevant calls when it receives the IP
resource resetting request or the IP resource resetting response from MSC. The counter
increments upon each released call. The measurement point is A, as shown in Figure
13-72.
13-94

Figure 13-72 Measurement Point of the Count of Drop Call Caused by "IP Resource Reset"
Unit
Times
13.79 C901070090 Number of FR_V1 radio link fail

Description
This counter counts the number of full-rate version 1 radio link failures on TCH/F. When
BSC receives the AbisConnectFailureIndication message from BTS, it judges the voice
version. If the voice version is full-rate version 1, then the counter increments.
Usage
This counter is used to find out the number of call drops due to full-rate version 1 radio link
failures on TCH/F.
13-95

Measurement Point
When BSC receives the AbisConnectFailureIndication message from BTS, if the voice
version used is full-rate voice version 1, then the counter counts.
Unit
Times

Description
Usage
failures on TCH/F.
Measurement Point
Unit
Times

Description
Usage
failures on TCH/F.
13-96

Measurement Point
Unit
Times
13.82 C901070093 Number of HR_V1 radio link fail

Description
This counter counts the number of half-rate version 1 radio link failures on TCH/F. When
version. If the voice version is half-rate version 1, then the counter increments.
Usage
This counter is used to find out the number of call drops due to half-rate version 1 radio
link failures on TCH/F.
Measurement Point
version used is half-rate voice version 1, then the counter counts.
Unit
Times
13.83 C901070094 Number of HR_V3 radio link fail

Description
This counter counts the number of half-rate version 3 radio link failures on TCH/F. When
version. If the voice version is half-rate version 3, then the counter increments.
Usage
This counter is used to find out the number of call drops due to half-rate version 3 radio
link failures on TCH/F.
13-97

Measurement Point
version used is half-rate voice version 3, then the counter counts.
Unit
Times
13-98

Chapter 14
Radio Resource Availability
Measurement
Table of Contents
Overview ..................................................................................................................14-1
C901080003 Maximum Number of Busy SDCCHs ...................................................14-1
C901080004 Average processor load.......................................................................14-3
C901080006 SDCCH congestion time......................................................................14-4
C901080008 Number of unavailable defined SDCCH...............................................14-5
C901080011 Maximum number of busy radio channel .............................................14-6
C901080012 Average number of busy radio channel ...............................................14-7
C901080014 Average number of busy TCH/H..........................................................14-8
C901080016 TCH/H busy time(SpeechVer1) ...........................................................14-9
C901080017 TCH/H busy time(SpeechVer3) .........................................................14-10
C901080018 TCH/H congestion time .....................................................................14-12
C901080022 Average number of busy TCH/F ........................................................14-13
C901080024 TCH/F busy time(SpeechVer1)..........................................................14-14
C901080027 TCH/F congestion time......................................................................14-18
C901080030 Number of TRXs ...............................................................................14-20
C901080032 Reserved TCH/F busy time ...............................................................14-21
C901080033 Maximum number of busy TCH/F ......................................................14-22
C901080034 Cell down time...................................................................................14-22
14.1 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.
14.2 C901080003 Maximum Number of Busy SDCCHs

Definition
Maximum Number of Busy SDCCHs
14-1

Description
This counter counts the maximum number of busy SDCCHs in the cell within measurement
period; its value represents SDDCH instantaneous occupation status and the busiest
extent.
System records SDCCH occupation number in cells. The occupation number increments
after SDCCH has been occupied successfully; the occupation number decrements before
SDCCH has been released. The counter value updates as occupation number if BSC
judges that the counter value is smaller than the occupation number after SDCCH has
been occupied successfully and before SDCCH has been released, as well as when
measurement data are reported periodically.
Update occupation number before SDCCH has been released is because SDCCH status
in the previous measurement period has been taken into account.
Usage
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 Point
The counter counts in the following three cases:
l The counter updates if the maximum busy number exceeds the recorded value after
SDCCH has been occupied successfully;
l The counter updates if the maximum busy number exceeds the recorded value
before SDCCH has been released;
l The counter updates if the maximum busy number exceeds the recorded value
when measurement data are reported periodically. The measurement point is A, as
14-2

Chapter 14 Radio Resource Availability Measurement
Unit
Times
14.3 C901080004 Average processor load

Definition
Average processor load.
Description
This counter counts the mean number of busy SDCCHs in the cell within measurement
period. The occupation number in measurement data reported periodically in the system
is the mean number of busy SDCCH.
Usage
Measurement Point
The counter counts when measurement data are reported periodically. The measurement
Unit
Times
14-3

14.4 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.
Usage
Measurement Point
l If congestion mark is set before SDCCH has been occupied, the counter counts
congestion time and accumulates.
l If congestion mark is set before SDCCH has been released, the counter counts
l If congestion mark is set when measurement values are reported periodically, the
counter counts congestion time and accumulates. The measurement point is A, as
14-4

Unit
Second

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 Point
The counter value is inquired from database when periodical measurement data are
reported. The measurement point is A, as shown in Figure 14-4.
14-5

Unit
Times
Related Features
14.6 C901080011 Maximum number of busy radio

channel
Definition
Maximum number of busy radio channel
Description
This counter counts the maximum number of busy radio channel in the cell within
measurement period; its value represents radio channel instantaneous occupation status
and the busiest extent.
Usage
This counter is used to find out the busy extent of radio channel in cells; its value can be
used as the reference for whether to increase TRXs.
Measurement Point
14-6

Unit
Times
Related Features
14.7 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
is the mean number of busy radio channel.
Usage
This counter is used to find out the busy extent of radio channel in cells; its value can be
used as the reference for whether to increase TRXs.
Measurement Point
14-7

Unit
Times
Related Features
14.8 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 within measurement
is the mean number of busy TCH/Hs.
Usage
This counter is used to find out the busy extent of TCH/Hs in cells; its value can be used
as the reference for whether to increase TCH/Hs.
Measurement Point
Occupation number updates after TCH/H has been occupied and released successfully,
the counter value is reported when measurement data are reported periodically. The
14-8

Unit
Times
Related Features
14.9 C901080016 TCH/H busy 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 occupation time of TCH/H in
cells; its value can be used as the reference for whether to increase TCH/Hs.
Measurement Point
l The counter counts time and accumulates when TCH/H is obtained successfully
14-9

l The counter counts time and accumulates when TCH/H is released

l The counter counts time and accumulates when measurement data are reported
periodically. The measurement point is A, as shown in Figure 14-8.
The measurement formula is:

(Present time previous measurement time) Number of MS that are occupying
channels
The reported measurement value is the accumulation of each measurement value.
After each accumulation, the previous measurement time is updated as the present
time. The number of MS that are occupying channels increments when TCH/H is
obtained successfully after accumulation. The number of MS that are occupying
channels decrements when TCH/H is released after accumulation.
Unit
Second
Related Features
14.10 C901080017 TCH/H busy time(SpeechVer3)

Definition
TCH/H busy time(SpeechVer3).
14-10

Description
This counter counts the total TCH/H busy time (SpeechVer3) in cells; its value represents
traffic on TCH/H (SpeechVer3).
Usage
This counter is used to find out the busy extent and mean occupation time of TCH/H in
cells; its value can be used as the reference for whether to increase TCH/Hs.
Measurement Point
l The counter counts time and accumulates when TCH/H is obtained successfully
l The counter counts time and accumulates when TCH/H is released

channels

time. The number of MS that are occupying channels increments when TCH/H is
channels decrements when TCH/H is released after accumulation.
Unit
Second
14-11

Related Features
14.11 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 of congestion time is
recorded.
BSC clear congestion mark when TCH/H request succeeds. If congestion mark is set
when requiring TCH/H, then this period of congestion time is to use the present time minus
the previous recorded congestion time.
If congestion mark is set before TCH/H has been released or when measurement values
time is the total time of 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.
Measurement Point
l If congestion mark is set before TCH/H has been occupied, the counter counts
l If congestion mark is set before TCH/H has been released, the counter counts
14-12

Unit
Second
Related Features
14.12 C901080022 Average number of busy TCH/F

Definition
Average number of busy TCH/F
Description
This counter counts the mean number of busy TCH/Fs in the cell within measurement
is the mean number of busy TCH/Fs.
Usage
This counter is used to find out the busy extent of TCH/Fs in cells; its value can be used
as the reference for whether to increase TCH/Fs.
14-13

Measurement Point
Occupation number updates after TCH/F has been occupied and released successfully,
the counter value is reported when measurement data are reported periodically. The
Unit
Times
Related Features
14.13 C901080024 TCH/F busy 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 occupation time of TCH/F in cells;
its value can be used as the reference for whether to increase TCH/Fs and the proportion
of using SpeechVer1.
14-14

Measurement Point
l The counter counts time and accumulates when TCH/F is obtained successfully
l The counter counts time and accumulates when TCH/F is released

channels
time. The number of MS that are occupying channels increments when TCH/F is
channels decrements when TCH/F is released after accumulation.
Unit
Second
Related Features
14-15


Definition
TCH/F busy time (SpeechVer2)
Description
Usage
Measurement Point

channels
14-16

Unit
Second
Related Features

Definition
TCH/F busy time(SpeechVer3)
Description
Usage
Measurement Point
14-17


channels
Unit
Second
Related Features
14.16 C901080027 TCH/F congestion time

Definition
TCH/F congestion time
Description
This counter counts the total time of TCH/F congestion.
14-18

BSC sets congestion mark when TCH/F request fails, and the start of congestion time is
recorded.
BSC clear congestion mark when TCH/F request succeeds. If congestion mark is set when
requiring TCH/F, then this period of congestion time is to use the present time minus the
previous recorded congestion time.
If congestion mark is set before TCH/F has been released or when measurement values
time is the total time of 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.
Measurement Point
l If congestion mark is set before TCH/F has been occupied, the counter counts
l If congestion mark is set before TCH/F has been released, the counter counts
Unit
Second
14-19

Related Features
14.17 C901080030 Number of TRXs

Definition
Number of TRX s
Description
This counter counts the total number of TRXs in all status configured in the cell.
Usage
This counter is used to find out the configured TRX number and resource utilizing status
in the present cell.
Measurement Point
Unit
Times
14-20

14.18 C901080032 Reserved TCH/F busy time

Definition
Reserved TCH/F busy time
Description
Reserved TCH is the channel that can only be occupied by subscribers with high priority.
This counter counts the total busy time for reserved TCH/F; its value represents traffic of
reserved TCH/F.
Usage
This counter is used to find out the utilizing status of reserved TCH/F to facilitate the
configuration adjustment of reserved TCH/F.
Measurement Point
l The counter counts when reserved TCH/F is obtained successfully
l The counter counts when reserved TCH/F is released;
l The counter counts when measurement values are reported periodically. The

channels
14-21

Unit
Second
14.19 C901080033 Maximum number of busy TCH/F

Description
This counter counts the maximum number of TCHs being occupied during the
measurement period.
The system records the number of TCHs being occupied in the cell. After a TCH is
occupied successfully, the counter increments; after a TCH is released, the counter
decrements. After TCH is successfully occupied or before TCH is released or when the
measurement data is reported periodically, if BSC finds that the counter's value is smaller
than the number of TCHs actually being occupied, then the counter's value is updated to
be the actual number of TCHs being occupied.
Considering the TCH usage in the last measurement period, the number of TCH being
occupied is updated before TCH is released.
Measurement Point
The counter counts at the following time points.
1. After TCH is occupied successfully, if the maximum number of busy TCHs exceeds
the recorded value, the counter counts.
2. Before TCH is released, if the maximum number of busy TCHs exceeds the recorded
value, the counter counts.
3. When the measurement data is reported periodically, if the maximum number of busy
TCHs exceeds the recorded value, the counter counts.
Unit
Times
14.20 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.
14-22

Usage
This counter is used to find out the duration of cell interruption on BCCH.
Measurement Point
When the confirmation message (tGetCellDownTimeAck.wResult) of cell's interruption
duration obtained from database is true, the counter counts.
Unit
Second
14-23

14-24

Chapter 15
General Handover
Measurement
Table of Contents
Overview ..................................................................................................................15-8
C901090001 Number of BSC-controlled inter-cell outgoing handover attempts ........15-8
C901090004 Number of MSC-controlled outgoing handover attempts......................15-9
C901090005 Number of MSC-controlled outgoing handover request failures due to
unclear factors........................................................................................................15-10
unavailable ground resource .................................................................................. 15-11
unavailable radio resource .....................................................................................15-12
other factors ...........................................................................................................15-13
C901090011 Number of BSC-controlled inter-cell incoming handover attempts......15-14
C901090013 Number of BSC-controlled incoming handover attempts due to forced
release ...................................................................................................................15-15
C901090015 Number of BSC-controlled incoming handover attempts due to
queue.....................................................................................................................15-16
C901090017 Number of BSC-controlled incoming handover attempts due to forced
handover ................................................................................................................15-17
C901090020 BSC-controlled incoming handover time due to queue ......................15-18
C901090021 Number of BSC-controlled incoming handover due to queue.............15-20
C901090022 BSC-controlled incoming handover success time due to queue.........15-22
C901090023 Number of BSC-controlled incoming handover success due to
queue.....................................................................................................................15-23
C901090024 Number of MSC-controlled incoming handover attempts ...................15-24
C901090025 Number of incoming handover failure due to circuit block ..................15-25
C901090026 Number of incoming handover failure due to circuit group mismatch .15-26
C901090027 Number of incoming handover failure due to unavailable radio
resource .................................................................................................................15-27
C901090028 Number of incoming handover failure due to other factors .................15-28
C901090030 Number of MSC-controlled incoming handover attempts due to forced
release ...................................................................................................................15-29
C901090032 Number of MSC-controlled incoming handover attempts due to
queue.....................................................................................................................15-30
15-1


release ...................................................................................................................15-31
C901090037 MSC-controlled incoming handover time due to queue......................15-32
C901090038 Number of MSC-controlled incoming handover due to queue ............15-35
C901090039 MSC-controlled incoming handover success time due to queue ........15-37
C901090040 Number of MSC-controlled incoming handover success due to
queue.....................................................................................................................15-38
C901090041 Number of incoming handover attempts from the same layer and
frequency ...............................................................................................................15-39
C901090042 Number of incoming handover success from the same layer and
frequency ...............................................................................................................15-40
C901090043 Number of outgoing handover attempts to the same layer and
frequency ...............................................................................................................15-41
C901090044 Number of outgoing handover success to the same layer and
frequency ...............................................................................................................15-42
C901090045 Number of incoming handover attempts from undefined layer to the
same frequency......................................................................................................15-43
C901090046 Number of incoming handover success from undefined layer to the
same frequency......................................................................................................15-44
C901090047 Number of outgoing handover attempts from undefined layer to the
same frequency......................................................................................................15-45
C901090048 Number of outgoing handover success from undefined layer to the
same frequency......................................................................................................15-46
C901090049 Number of incoming handover attempts from undefined layer
(GSM900) to current layer (GSM1800) ...................................................................15-47
C901090052 Number of outgoing handover attempts from current layer (GSM900)
to undefined layer (GSM1800)................................................................................15-48
C901090053 Number of outgoing handover from current layer (GSM900) to
undefined layer (GSM1800)....................................................................................15-49
C901090054 Number of outgoing handover success from current layer (GSM900)
to undefined layer (GSM1800)................................................................................15-50
C901090055 Number of incoming handover attempts from undefined layer
C901090058 Number of outgoing handover attempts from undefined layer
C901090059 Number of outgoing handover from undefined layer (GSM1800) to
current layer (GSM900) ..........................................................................................15-53
C901090060 Number of outgoing handover success from undefined layer
C901090061 Number of incoming handover attempts from upper layer to the same
frequency ...............................................................................................................15-55
C901090062 Number of incoming handover success from upper layer to the same
frequency ...............................................................................................................15-56
C901090063 Number of outgoing handover attempts from the same frequency to
upper layer .............................................................................................................15-57
15-2

Chapter 15 General Handover Measurement
C901090064 Number of outgoing handover success from the same frequency to

upper layer .............................................................................................................15-58
C901090065 Number of incoming handover attempts from lower layer to the same
frequency ...............................................................................................................15-59
C901090066 Number of incoming handover success from lower layer to the same
frequency ...............................................................................................................15-60
C901090067 Number of outgoing handover attempts from the same frequency to
lower layer..............................................................................................................15-61
C901090068 Number of outgoing handover success from the same frequency to
lower layer..............................................................................................................15-62
C901090069 Number of incoming handover attempts from the same layer GSM900
to GSM1800 ...........................................................................................................15-63
C901090072 Number of outgoing handover attempts to the same layer GSM900 to
GSM1800...............................................................................................................15-64
C901090073 Number of outgoing handover to the same layer GSM900 to
GSM1800...............................................................................................................15-65
C901090074 Number of outgoing handover success to the same layer GSM900 to
GSM1800...............................................................................................................15-66
C901090075 Number of incoming handover attempts from GSM900 to GSM1800
C901090078 Number of outgoing handover attempts from GSM900 to GSM1800
to the upper layer ...................................................................................................15-68
C901090079 Number of outgoing handover from GSM900 to GSM1800 to the
upper layer .............................................................................................................15-69
C901090080 Number of outgoing handover success from GSM900 to GSM1800 to
the upper layer .......................................................................................................15-70
C901090085 Number of outgoing handover from GSM900 to GSM1800 in the
lower layer..............................................................................................................15-73
C901090086 Number of outgoing handover success from GSM900 to GSM1800 in
the lower layer........................................................................................................15-74
C901090091 Number of outgoing handover from GSM1800 to GSM900 from the
same layer .............................................................................................................15-77
C901090092 Number of outgoing handover success from GSM1800 to GSM900
15-3


to the upper layer ...................................................................................................15-80
upper layer .............................................................................................................15-81
the upper layer .......................................................................................................15-82
to the lower layer ....................................................................................................15-84
lower layer..............................................................................................................15-85
the lower layer........................................................................................................15-86
C901090105 Number of intra-cell handover attempts .............................................15-87
C901090108 Number of intra-cell inner-circle-to-outer-circle handover attempts ....15-88
C901090109 Number of intra-cell inner-circle-to-outer-circle handover success .....15-89
C901090110 Number of intra-cell outer-circle-to-inner-circle handover attempts.....15-90
C901090111 Number of intra-cell outer-circle-to-inner-circle handover success......15-91
C901090112 Number of intra-cell inner-circle-to-inner-circle handover attempts.....15-92
C901090113 Number of intra-cell inner-circle-to-inner-circle handover success......15-93
C901090114 Number of intra-cell outer-circle-to-outer-circle handover attempts ....15-94
C901090115 Number of intra-cell outer-circle-to-outer-circle handover success .....15-95
C901090116 Number of handover attempts from 2G to 3G ....................................15-96
C901090117 Number of handover from 2G to 3G...................................................15-97
C901090118 Number of handover success from 2G to 3G .....................................15-98
C901090119 Number of handover attempts from 3G to 2G ....................................15-99
C901090120 Number of handover from 3G to 2G ................................................15-100
C901090121 Number of handover success from 3G to 2G...................................15-100
C901090122 Number of intra-cell handover attempts from TCH/F........................15-101
C901090123 Number of intra-cell TCH/F-to-TCH/F handover...............................15-102
C901090124 Number of intra-cell TCH/F-to-TCH/F handover success .................15-103
C901090125 Number of intra-cell TCH/F-to-TCH/H handover ..............................15-104
C901090126 Number of intra-cell TCH/F-to-TCH/H handover success.................15-105
C901090127 Number of intra-cell handover attempts from TCH/H .......................15-106
C901090128 Number of intra-cell TCH/H-to-TCH/F handover ..............................15-107
C901090129 Number of intra-cell TCH/H-to-TCH/F handover success.................15-108
C901090130 Number of intra-cell TCH/H-to-TCH/H handover..............................15-109
C901090131 Number of intra-cell TCH/H-to-TCH/H handover success ................ 15-110
C901090132 Number of inter-cell handover attempts from TCH/F........................ 15-111
C901090133 Number of inter-cell TCH/F-to-TCH/F handover............................... 15-112
C901090134 Number of inter-cell TCH/F-to-TCH/F handover success ................. 15-113
C901090135 Number of inter-cell TCH/F-to-TCH/H handover .............................. 15-114
C901090136 Number of inter-cell TCH/F-to-TCH/H handover success................. 15-115
C901090137 Number of inter-cell handover attempts from TCH/H ....................... 15-116
15-4

C901090138 Number of inter-cell TCH/H-to-TCH/F handover .............................. 15-117

C901090139 Number of inter-cell TCH/H-to-TCH/F handover success................. 15-118
C901090140 Number of inter-cell TCH/H-to-TCH/H handover.............................. 15-119
C901090141 Number of inter-cell TCH/H-to-TCH/H handover success ................15-120
C901090142 Total dual-band outgoing handover attempts ...................................15-121
C901090145 Number of dual band incoming handover attempts ..........................15-122
C901090148 Number of intra-cell invalid handovers.............................................15-123
C901090149 Number of BSC-controlled inter-cell incoming handover attempts due
to forced release (emergency service)..................................................................15-124
C901090150 Number of BSC-controlled inter-cell incoming handover (forced
release) (emergency service) ...............................................................................15-125
to forced handover (emergency service)...............................................................15-126
C901090152 Number of BSC-controlled inter-cell incoming handover (forced
handover) (emergency service) ............................................................................15-127
to queue (emergency service) ..............................................................................15-129
C901090154 Number of BSC-controlled inter-cell incoming handover (queue)
(emergency service).............................................................................................15-130
release (emergency service) ................................................................................15-131
C901090156 Number of MSC-controlled incoming handover (forced release)
C901090157 Number of MSC-controlled inter-cell incoming handover attempts due
to forced handover (emergency service)...............................................................15-133
C901090158 Number of MSC-controlled incoming handover (forced release)
C901090159 Number of MSC-controlled incoming handover attempts due to queue
C901090160 Number of MSC-controlled incoming handover (queue) (emergency
service) ................................................................................................................15-136
C901090161 Number of forced handover target not found (BSC-controlled inter-cell
handover due to forced handover)........................................................................15-137
(BSC-controlled inter-cell handover due to forced handover) ................................15-138
C901090163 Number of recv failure from lower PRI user request resource for
forced handover (BSC-controlled inter-cell handover due to forced handover)......15-139
C901090164 Number of lower PRI user handover failure (BSC-controlled inter-cell
C901090165 Number of high PRI user time out for wait resource (BSC-controlled
inter-cell handover due to forced handover)..........................................................15-142
C901090166 Number of forced release target not found (BSC-controlled inter-cell
handover due to forced release) ...........................................................................15-143
C901090167 Number of high PRI user time out for wait resource (BSC-controlled
inter-cell handover due to forced release).............................................................15-145
15-5

C901090168 Number of HO Target not found (MSC-controlled incoming handover

due to forced handover) .......................................................................................15-146
(MSC-controlled incoming handover due to forced handover)...............................15-147
C901090170 Number of failure to lower PRI user request resource for forced
handover (MSC-controlled incoming handover due to forced handover) ...............15-148
C901090171 Number of lower PRI user handover failure (MSC-controlled incoming
C901090172 Number of high PRI user time out for wait resource (MSC-controlled
incoming handover due to forced handover).........................................................15-149
C901090173 Number of forced release target not found (MSC-controlled incoming
handover due to forced release) ...........................................................................15-150
C901090174 Number of high PRI user time out for wait resource (MSC-controlled
incoming handover due to forced release) ............................................................15-150
handover).............................................................................................................15-151
release) ................................................................................................................15-152
C901090177 Number of handover attempts due to eMLPP forced handover........15-152
C901090178 Number of handover due to eMLPP forced handover ......................15-153
C901090179 Number of handover success due to eMLPP forced handover.........15-153
C901090180 Number of BSC-controlled inter-cell outgoing handover attempts
between PLMN.....................................................................................................15-154
C901090181 Number of BSC-controlled inter-cell outgoing handover between
PLMN...................................................................................................................15-154
C901090182 Number of BSC-controlled inter-cell outgoing handover success
between PLMN.....................................................................................................15-154
C901090183 Number of MSC-controlled outgoing handover attempts between
PLMN...................................................................................................................15-154
C901090184 Number of MSC-controlled outgoing handover request fail between
PLMN due to unknown reason .............................................................................15-154
PLMN due to unavailable ground resource ..........................................................15-155
PLMN due to unavailable radio resource ..............................................................15-156
PLMN due to other reasons..................................................................................15-156
C901090188 Number of MSC-controlled outgoing handover between PLMN .......15-156
C901090189 Number of MSC-controlled outgoing handover success between
PLMN...................................................................................................................15-158
C901090190 Number of BSC-controlled inter-cell incoming handover attempt
between PLMN.....................................................................................................15-158
C901090191 Number of BSC-controlled inter-cell incoming handover between
PLMN...................................................................................................................15-158
15-6

C901090192 Number of BSC-controlled inter-cell incoming handover force-release

attempt between PLMN ........................................................................................15-158
PLMN due to force release ...................................................................................15-159
C901090194 Number of BSC-controlled inter-cell incoming handover queue
PLMN due to queue .............................................................................................15-159
C901090196 Number of BSC-controlled inter-cell incoming handover
force-handover attempt between PLMN ...............................................................15-159
PLMN due to force handover................................................................................15-159
C901090198 Number of BSC-controlled inter-cell incoming handover success
between PLMN.....................................................................................................15-159
C901090199 Number of MSC-controlled incoming handover attempt between
PLMN ..................................................................................................................15-160
C901090200 A interface incoming handover fail between PLMN due to circuit
block ....................................................................................................................15-161
C901090201 A interface incoming handover fail between PLMN due to circuit
unmatch ...............................................................................................................15-162
C901090202 A interface incoming handover fail between PLMN due to unavailable
radio resource ......................................................................................................15-162
C901090203 A interface incoming handover fail between PLMN due to other
reason..................................................................................................................15-163
C901090204 Number of MSC-controlled incoming handover between PLMN.......15-163
C901090205 Number of MSC-controlled incoming handover force-release attempt
between PLMN.....................................................................................................15-163
C901090206 Number of MSC-controlled incoming handover between PLMN due
to force release ....................................................................................................15-164
C901090207 Number of MSC-controlled incoming handover queue attempt
between PLMN.....................................................................................................15-164
to queue ...............................................................................................................15-165
C901090209 Number of MSC-controlled incoming handover force-handover
to force handover .................................................................................................15-167
C901090211 Number of MSC-controlled incoming handover success between
PLMN ..................................................................................................................15-167
C901090212 Number of handover due to Fragment reorganization......................15-167
C901090213 Number of handover success due to Fragment reorganization ........15-167
15-7

15.1 Overview
General handover counter is used to find out MS handover successes, failures, and
frequency of abnormal events during handover. After configured with inter-system
handover or concentric circle, general handover counter is also used to find out inter-cell
traffic sharing to improve the wireless planning.

outgoing handover attempts
Definition
Number of BSC-controlled inter-cell outgoing handover attempts
Description
This counter counts the Number of BSC-controlled inter-cell outgoing handover attempts
originated from the source cell by MS.
Usage
This counter is used to find out the frequency of intra-BSC inter-cell outgoing handover. It
is one of the parameters to measure the wireless environment.
Measurement Point
BSC starts the handover decision after it receives the measurement report from MS. If
inter-cell handover is necessary and the current attempt cells are intra-BSC, the counter
Figure 15-1 BSC-Controlled Inter-Cell Outgoing Handover Attempt
15-8

Unit
Times
Related Features

handover attempts
Definition
Number of MSC-controlled outgoing handover attempts
Description
This counter counts the number of MSC-controlled inter-BSC outgoing handover attempts
originated from the source cell by MS.
Usage
handover attempts. It is one of the parameters to measure the wireless environment.
Measurement Point
inter-cell handover is necessary and the current attempt cells are governed by different
BSCs, the source BSC will send MSC the handover request A_HO_RQD to trigger
inter-BSC handover, and the counter increments. The measurement point is A, as shown
in Figure 15-2.
Figure 15-2 MSC-Controlled Outgoing Handover Attempts
15-9

Unit
Times
Related Features

handover request failures due to unclear factors
Definition
Number of MSC-controlled outgoing handover request failures due to unclear factors
Description
This counter counts the number of MSC-controlled inter-BSC outgoing handover request
failures due to unclear factors originated from the source cell by MS.
Usage
This counter is used to find out the frequency of MSC-controlled outgoing handover request
failures due to unclear reasons, and to find out the MSC-originated handover status.
Measurement Point
inter-BSC handover. If BSC fails to receive any feedback from MSC before the protection
timer expires, the counter increments. The measurement point is A, as shown in Figure
15-3.
Figure 15-3 MSC-Controlled Outgoing Handover Request Failures Due To Unclear

Factors
Unit
Times
15-10

Related Features

handover request failures due to unavailable
ground resource
Definition
Number of MSC-controlled outgoing handover request failures due to unavailable ground
resource
Description
failures due to unavailable ground resource originated from the source cell by MS.
Usage
This counter is used to find out the frequency of MSC-controlled outgoing handover request
failures due to unavailable ground resource, and to find out the MSC-originated handover
status.
Measurement Point
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.
Figure 15-4 MSC-Controlled Handover Request Failures
Unit
Times
15-11

Related Features

handover request failures due to unavailable radio
resource
Definition
Number of MSC-controlled outgoing request failures due to unavailable radio resource
Description
failures due to unavailable radio resource originated from the source cell by MS.
Usage
This counter is used to find out the frequency of MS-originated MSC-controlled outgoing
handover request failures due to unavailable radio resource, and to find out the
MSC-originated handover status.
Measurement Point
inter-BSC handover. If the source BSC receives the feedback from MSC that the
handover request is rejected due to unavailable radio resource, the counter increments.
Unit
Times
15-12

Related Features

handover request failures due to other factors
Definition
Number of MSC-controlled outgoing handover request failures due to other factors
Description
failures due to other factors excluding unavailable ground resource and 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 other factors, and to find out the MSC-originated handover
status.
Measurement Point
inter-BSC handover. If the source BSC receives the feedback from MSC that the handover
request is rejected due to other factors, the counter increments. The measurement point
Unit
Times
15-13

Related Features

incoming handover attempts
Definition
Number of BSC-controlled inter-cell incoming handover attempts
Description
This counter counts the Number of BSC-controlled inter-cell incoming handover attempts
from MS to target cell.
Usage
This counter is used to find out the frequency of intra-BSC inter-cell incoming handover
attempts originated by MS. It is one of the parameters to measure the wireless
environment.
Measurement Point
When intra-BSC target cell receives the channel request from the source cell, if the request
is due to inter-cell handover, the counter increments. The measurement point is A, as
Figure 15-7 BSC-Controlled Inter-Cell Incoming Handover Attempts
Unit
Times
Related Features
15-14


handover attempts due to forced release
Definition
Number of BSC-controlled incoming handover attempts due to forced release
Description
This counter counts the number of forced release attempts originated by target cell due to
unavailable radio resource during the process of MS -originated BSC-controlled inter-cell
incoming handover. When target instance fails to allocate the channel, forced release
attempts could be originated referring to the MS priority and MSC & BSC settings.
Usage
This counter is used to find out the frequency of MS-originated BSC-controlled inter-cell
incoming handover attempts due to forced release, which reflects the handover status.
Measurement Point
When intra-BSC target cell receives the wireless channel application request, if the
application cause is BSC-controlled inter-cell incoming handover and wireless channel is
unavailable to target cell, forced release attempt decision starts. If forced release attempt
is feasible, the counter increments before the target cell sends forced release message to
the instance that is to be released. The measurement point is A, as shown in Figure 15-8.
Figure 15-8 Forced Release Attempts
Unit
Times
15-15

Related Features
ZGO-01-03-001 eMLPP

handover attempts due to queue
Definition
Number of BSC-controlled incoming handover attempts due to queue
Description
This counter counts the number of queuing attempts originated by target cell due to
unavailable radio resource during the process of MS-originated BSC-controlled inter-cell
incoming handover.
Usage
incoming handover attempts due to queue, which reflects the handover status.
Measurement Point
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, the counter increments.
Figure 15-9 Queuing Attempts
15-16

Unit
Times
Related Features
ZGO-01-03-001 eMLPP

handover attempts due to forced handover
Definition
Number of BSC-controlled incoming handover attempts due to forced handover
Description
This counter counts the number of forced-handover attempts originated by target cell due
to unavailable radio resource during the process of MS-originated BSC-controlled inter-cell
incoming handover.
Usage
incoming handover attempts due to forced handover, which reflects the handover status.
Measurement Point
application cause is BSC-controlled inter-cell incoming handover and wireless channel
is unavailable to target cell, forced-handover attempt decision starts. If forced-handover
attempt is feasible, the counter increments before the target cell sends forced-handover
message to the instance that is to be forced. The measurement point is A, as shown
inFigure 15-10.
15-17

Figure 15-10 Forced-Handover Attempts
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
15.12 C901090020 BSC-controlled incoming handover

time due to queue
Definition
BSC-controlled incoming handover time due to queue
Description
This counter counts the total time of call queuing that participate in BSC-controlled intra-cell
incoming handover due to queue. Queuing time refers to a period of an instance from
entering to quitting the queuing.
Usage
This counter is used to find out the total time of BSC-controlled intra-cell incoming handover
due to queue, which helps to understand the traffic status and the situation of the queuing
for resource.
15-18

Measurement Point
l Under the condition that database acquires resource via dynamic channel
conversion or MS releases resource and queuing instance receives usable message,
if the application cause is BSC-controlled incoming handover, the queuing time
accumulates. The measurement point is A, as shown in Figure 15-11.
Figure 15-11 Execution In Queuing
l If the instance queuing timer expires, and the application cause is BSC-controlled
incoming handover, the queuing time accumulates. The measurement point is A, as
Figure 15-12 Incoming Handover Queuing Expires
l 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. The measurement point is A, as shown in Figure 15-13.
15-19

Figure 15-13 Instance Release During Queuing
Unit
Second
Related Features

Definition
Number of BSC-controlled incoming handover due to queue
Description
This counter counts the total number of calls that participate in BSC-controlled intra-cell
incoming handover due to queue.
Usage
This counter is used to find out the total number of calls that participate in BSC-controlled
intra-cell incoming handover due to queue, which helps to understand the traffic status.
Measurement Point
l Under the condition that database acquires resource via dynamic channel conversion
or MS releases resource and queuing instance receives usable message, if the
application cause is BSC-controlled incoming handover, the counter increments.
15-20

l If the instance queuing timer expires, and the application cause is BSC-controlled
incoming handover, the counter increments. The measurement point is A, as shown
in Figure 15-15.
l During the process of instance queuing, when the instance is released due to certain
causes, if the application cause is BSC-controlled incoming handover, the counter
15-21

Unit
Times
Related Features
15.14 C901090022 BSC-controlled incoming handover

success time due to queue
Definition
BSC-controlled incoming handover success time due to queue
Description
This counter counts the total time of calls that participate in successful BSC-controlled
intra-cell incoming handover due to queue and acquiring resource.
Usage
This counter is used to find out the total queuing time of calls that participate in successful
BSC-controlled intra-cell incoming handover due to queue and acquiring resource, and to
find out the valid queuing time.
Measurement Point
Under the condition that database acquires resource via dynamic channel conversion or
MS releases resource, when queuing instance receives resource usable message, if the
15-22

application cause is BSC-controlled incoming handover, the queuing time accumulates.

Unit
Times
Related Features

handover success due to queue
Definition
Number of BSC-controlled incoming handover success due to queue
Description
incoming handover due to queue and successfully acquiring resource.
Usage
This counter is used to find out the total number of calls that participate in BSC-controlled
intra-cell incoming handover due to queue and successfully acquiring resource, and to find
out the success ratio of queuing.
15-23

Measurement Point
MS releases resource and queuing instance receives resource usable message, if the
application cause is BSC-controlled incoming handover, the counter increments. The
Unit
Times
Related Features

handover attempts
Definition
Number of MSC-controlled incoming handover attempts
Description
This counter counts the number of MSC-originated inter-BSC incoming handover attempts.
Usage
This counter is used to find out the frequency of MSC-originated inter-BSC incoming
15-24

Measurement Point
When the target cell receives the channel application, if the application cause is external
incoming handover, the counter increments. The measurement point is A, as shown in
Figure 15-19.
Figure 15-19 MSC-Controlled Incoming Handover Attempts
Unit
Times
Related Features

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 circuit block, and is used to observe the external
handover flow.
15-25

Measurement Point
When the target cell receives the handover request from MSC, it checks the ground circuit.
If the requested ground circuit is blocked, the counter increments. The measurement point
Figure 15-20 Unsuccessful MSC-Controlled External Incoming Handover
Unit
Times
Related Features

failure due to circuit group mismatch
Definition
Number of incoming handover failure due to circuit group mismatch
Description
handover due to ground circuit group mismatch.
Usage
incoming handover due to ground circuit group mismatch, and is used to observe the
external handover flow.
Measurement Point
When the target cell receives the handover request from MSC, it checks the ground circuit.
If the requested ground circuit does not match, the counter increments. The measurement
15-26

Unit
Times
Related Features

failure due to unavailable radio resource
Definition
Number of incoming handover failure requests due to unavailable radio resource
Description
handover due to unavailable radio resource.
Usage
incoming handover due to unavailable radio resource, and is used to observe the external
handover flow.
Measurement Point
When the target cell receives the handover request from MSC, it allocates the wireless
channels and attempts to activate and connect. If one link fails and the target cell sends
MSC the handover failure message, the counter increments. The measurement point is
15-27

Unit
Times
Related Features

failure due to other factors
Definition
Number of incoming handover failure due to other factors
Description
handover due to other factors excluding circuit block, circuit group mismatch and
unavailable radio resource.
Usage
incoming handover due to other factors, and is used to observe the external handover flow.
Measurement Point
When the target cell receives the handover request from MSC, it sends MSC the handover
failure message. If the failure is due to other factors, the counter increments. The
15-28

Unit
Times
Related Features

Definition
Number of MSC-controlled incoming handover attempts due to forced release
Description
This counter counts the number of forced release attempts originated by target cell due to
unavailable radio resource during the process of MS-originated MSC-controlled inter-BSC
incoming handover. When target instance fails to allocate the channel, forced release
attempts could be originated referring to the MS priority and MSC & BSC settings.
Usage
This counter is used to find out the frequency of MS-originated MSC-controlled inter-BSC
incoming handover attempts due to forced release, which reflects the handover status.
Measurement Point
When the target cell receives the wireless channel application request, if the application
cause is MSC-controlled inter-BSC incoming handover and wireless channel is unavailable
to target cell, forced release attempt decision starts. If forced release attempt is feasible,
the counter increments before the target cell sends forced release message to the instance
that is to be force-released. The measurement point is A, as shown in Figure 15-24.
15-29

Unit
Times
Related Features
ZGO-01-03-001 eMLPP

handover attempts due to queue
Definition
Number of MSC-controlled incoming handover attempts due to queue
Description
This counter counts the number of queuing attempts originated by target cell due to
unavailable radio resource during the process of MS-originated MSC-controlled inter-BSC
incoming handover.
Usage
incoming handover attempts due to queue, which reflects the handover status.
Measurement Point
cause is MSC-controlled inter-BSC incoming handover and wireless channel is
15-30

unavailable to target cell, queuing attempt decision starts. If queuing attempt is feasible,
the target cell has the target instance waiting in the queuing, and the counter increments.
Unit
Times
Related Features
ZGO-01-03-001 eMLPP

Definition
Number of MSC-controlled incoming handover attempts due to forced handovers
Description
This counter counts the number of forced-handover attempts originated by target cell
due to unavailable radio resource during the process of MS-originated MSC-controlled
inter-BSC incoming handover.
Usage
incoming handover attempts due to forced handover, which reflects the handover status.
15-31

Measurement Point
cause is MSC-controlled inter-BSC incoming handover and wireless channel is
unavailable to target cell, forced-handover attempt decision starts. If forced-handover
attempt is feasible, the counter increments before the target cell sends forced-handover
message to the instance that is to be forced handover. The measurement point is A, as
Unit
Times
Related Features
ZGO-01-03-001 eMLPP
15.24 C901090037 MSC-controlled 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.
15-32

Usage
This counter is used to find out the total time of MSC-controlled intra-cell incoming
handover due to queue, which helps to understand the traffic status and the situation of
the queuing for resource.
Measurement Point
or MS releases resource, and queuing instance receives usable message, if
the application cause is MSC-controlled incoming handover, the queuing time
accumulates. The measurement point is A, as shown in Figure 15-27.
l If the instance queuing timer expires, and the application cause is MSC-controlled
incoming handover, the queuing time accumulates. The measurement point is A, as
15-33

causes, if the application cause is MSC-controlled incoming handover, the queuing
time accumulates. The measurement point is A, as shown in Figure 15-29.
Unit
Second
Related Features
15-34


Definition
Number of MSC-controlled incoming handover due to queue
Description
incoming handover due to queue.
Usage
This counter is used to find out the total number of calls that participate in MSC-controlled
intra-cell incoming handover due to queue, which helps to understand the traffic status.
Measurement Point
or MS releases resource, and queuing instance receives usable message, if the
application cause is MSC-controlled incoming handover, the counter increments.
l If the instance queuing timer expires, and the application cause is MSC-controlled
incoming handover, the counter increments. The measurement point is A, as shown
in Figure 15-31.
15-35

causes, if the application cause is MSC-controlled incoming handover, the counter
Unit
Times
Related Features
15-36

15.26 C901090039 MSC-controlled incoming handover

success time due to queue
Definition
MSC-controlled incoming handover success time due to queue
Description
This counter counts the total time of calls that participate in successful MSC-controlled
intra-cell incoming handover due to queue and acquiring resource.
Usage
This counter is used to find out the total queuing time of calls that participate in successful
MSC-controlled intra-cell incoming handover due to queue and acquiring resource, and to
find out the valid queuing time.
Measurement Point
MS releases resource, when queuing instance receives resource usable message, if the
application cause is MSC-controlled incoming handover, the queuing time accumulates.
Unit
Second
Related Features
15-37


handover success due to queue
Definition
Number of MSC-controlled incoming handover success due to queue
Description
This counter counts the total number of calls that participate in MSC-controlled intra-cell
incoming handover due to queue and successfully acquires resource.
Usage
This counter is used to find out the total number of calls that participate in MSC-controlled
intra-cell incoming handover due to queue and successfully acquires resource, and to find
out the success ratio of queuing.
Measurement Point
MS releases resource, and queuing instance receives resource usable message, if the
application cause is MSC-controlled incoming handover, the counter increments. The
Unit
Times
Related Features
15-38


attempts from the same layer and frequency
Definition
Number of incoming handover attempts from the same layer and frequency
Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts
the target cell receives from the same layer and frequency.
Usage
This counter is used to find out the frequency of BSC-controlled incoming handover
attempts from the same layer and frequency, which helps to make the network planning.
Measurement Point
When intra-BSC target cell receives the channel application request from the source cell,
if the application cause is inter-cell incoming handover and the source cell is at the same
layer and frequency, the counter increments. The measurement point is A, as shown in
Figure 15-35.
Unit
Times
Related Features
15-39


success from the same layer and frequency
Definition
Number of incoming handover success from the same layer and frequency
Description
This counter counts the number of successful BSC-controlled inter-cell incoming handover
the target cell receives from the same layer and frequency.
Usage
success from the same layer and frequency, and is used to observe the handover flow.
Measurement Point
When intra-BSC target cell receives the handover completed message, if the application
cause is BSC-controlled inter-cell handover and the source cell is at the same layer and
frequency, the counter increments. The measurement point is A, as shown inFigure 15-36.
Figure 15-36 Successful BSC-Controlled Inter-Cell Incoming Handover
Unit
Times
Related Features
15-40

15.30 C901090043 Number of outgoing handover

attempts to the same layer and frequency
Definition
Number of outgoing handover attempts to the same layer and frequency
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts
the target cell sends to the same layer and frequency.
Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover
attempts to the same layer and frequency, which helps to make the network planning.
Measurement Point
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 point is
Unit
Times
Related Features
15-41


success to the same layer and frequency
Definition
Number of outgoing handover success to the same layer and frequency
Description
This counter counts the number of successful BSC-controlled inter-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, which helps to make the network planning.
Measurement Point
During the process of BSC-controlled handover, if the source cell receives the handover
completed message from the target cell, and the target cell is at the same layer and
frequency, the counter increments. The measurement point is A, as shown in Figure 15-38.
Figure 15-38 Successful BSC-Controlled Inter-Cell Outgoing Handover
Unit
Times
Related Features
15-42


attempts from undefined layer to the same
frequency
Definition
Number of incoming handover attempts from undefined layer to the same frequency
Description
the target cell receives from undefined layer to the same frequency.
Usage
attempts from undefined layer to the same frequency, which helps to make the network
planning.
Measurement Point
When intra-BSC target cell receives the channel application request from the source cell, if
the application cause is inter-cell incoming handover and the source cell is at the undefined
layer and the same frequency, the counter increments. The measurement point is A, as
Unit
Times
Related Features
15-43


success from undefined layer to the same
frequency
Definition
Number of incoming handover success from undefined layer to the same frequency
Description
the target cell receives from undefined layer to the same frequency.
Usage
success from undefined layer to the same frequency, which helps to observe the handover
flow.
Measurement Point
cause is BSC-controlled inter-cell handover, and the source cell is at undefined layer and
the same frequency, the counter increments. The measurement point is A, as shown in
Figure 15-40.
Unit
Times
Related Features
15-44


attempts from undefined layer to the same
frequency
Definition
Number of outgoing handover attempts from undefined layer to the same frequency
Description
the source cell sends from undefined layer to the same frequency.
Usage
attempts from undefined layer to the same frequency, which helps to make the network
planning.
Measurement Point
BSC starts the handover decision after it receives the measurement report from MS.
If inter-cell handover is necessary, and the current attempt cells are BSC-controlled
internal cells at undefined layer and the same frequency, the counter increments. The
Unit
Times
15-45

Related Features

success from undefined layer to the same
frequency
Definition
Number of outgoing handover success from undefined layer to the same frequency
Description
the source cell sends from undefined layer to the same frequency.
Usage
handover from undefined layer to the same frequency, which helps to make the network
planning.
Measurement Point
completed message from the target cell, and the target cell is at undefined layer and the
same frequency, the counter increments. The measurement point is A, as shown inFigure
15-42.
Unit
Times
15-46

Related Features

attempts from undefined layer (GSM900) to current
layer (GSM1800)
Definition
Number of incoming handover attempts from undefined layer (GSM900) to current layer
(GSM1800)
Description
the target cell (GSM1800) receives from undefined layer (GSM900).
Usage
attempts from undefined layer (GSM900) to current layer (GSM1800), which helps to
make the network planning.
Measurement Point
When intra-BSC target cell (GSM1800) receives the channel application request from the
source cell (GSM900), if the application cause is inter-cell incoming handover and the
source cell is at undefined layer, the counter increments. The measurement point is A, as
Unit
Times
15-47

Related Features

attempts from current layer (GSM900) to undefined
layer (GSM1800)
Definition
Number of outgoing handover attempts from current layer (GSM900) to undefined layer
(GSM1800)
Description
the source cell (GSM900) sends to undefined layer (GSM1800).
Usage
Measurement Point
cells at undefined layer (GSM1800) and the current serving cell is GSM900, the counter
15-48

Unit
Times
Related Features

from current layer (GSM900) to undefined layer
(GSM1800)
Definition
Number of outgoing handover from current layer (GSM900) to undefined layer (GSM1800)
Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source
cell (GSM900) sends to undefined layer (GSM1800).
Usage
Measurement Point
During the process of BSC-controlled handover, if the source cell (GSM900) receives the
radio resource unavailable message from the target cell (GSM1800), and the target cell
is at undefined layer and the same frequency, the counter increments. The measurement
Figure 15-45 BSC-Controlled Inter-Cell Outgoing Handover Execution Flow
Unit
Times
15-49

Related Features

success from current layer (GSM900) to undefined
layer (GSM1800)
Definition
Number of outgoing handover success from current layer (GSM900) to undefined layer
(GSM1800)
Description
the source cell (GSM900) sends from undefined layer to the same frequency (GSM1800).
Usage
handover from undefined layer to the same frequency (GSM900) to current layer
(GSM1800), which helps to make the network planning.
Measurement Point
handover completed message from the target cell (GSM1800), and the target cell is at
undefined layer and the same frequency, the counter increments. The measurement point
Unit
Times
15-50

Related Features

attempts from undefined layer (GSM1800) to
current layer (GSM900)
Definition
Number of incoming handover attempts from undefined layer (GSM1800) to current layer
(GSM900)
Description
the target cell (GSM900) receives from undefined layer (GSM1800).
Usage
Measurement Point
source cell (GSM1800), if the application cause is inter-cell incoming handover and the
source cell is at undefined layer, the counter increments. The measurement point is A, as
Unit
Times
15-51

Related Features

attempts from undefined layer (GSM1800) to
current layer (GSM900)
Definition
Number of outgoing handover attempts from undefined layer (GSM1800) to current layer
(GSM900)
Description
the source cell (GSM1800) sends to undefined layer (GSM900).
Usage
Measurement Point
inter-cell handover is necessary, and the current attempted cell is BSC-controlled internal
cell at undefined layer (GSM900) or lower-layer cell at same frequency (GSM1800), the
15-52

Unit
Times
Related Features

from undefined layer (GSM1800) to current layer
(GSM900)
Definition
Number of outgoing handover from undefined layer (GSM1800) to current layer (GSM900)
Description
cell (GSM1800) sends to undefined layer (GSM900).
Usage
Measurement Point
radio resource unavailable message from the target cell (GSM900), and the target cell is
at undefined layer and the same frequency, the counter increments. The measurement
Unit
Times
15-53

Related Features

success from undefined layer (GSM1800) to current
layer (GSM900)
Definition
Number of outgoing handover success from undefined layer (GSM1800) to current layer
(GSM900)
Description
the source cell (GSM1800) sends from undefined layer to the same frequency (GSM900).
Usage
handover from undefined layer to the same frequency (GSM1800) to current layer
(GSM900), which helps to make the network planning.
Measurement Point
During the process of BSC-controlled handover, if the source cell (GSM1800) receives
the handover completed message from the target cell (GSM900), and the target cell is at
undefined layer and the same frequency, the counter increments. The measurement point
Unit
Times
15-54

Related Features

attempts from upper layer to the same frequency
Definition
Number of incoming handover attempts from upper layer to the same frequency
Description
the target cell receives from upper layer to the same frequency.
Usage
attempts from upper layer to the same frequency, which helps to make the network
planning.
Measurement Point
if the application cause is inter-cell incoming handover and the source cell is at upper layer
and the same frequency, the counter increments. The measurement point is A, as shown
in Figure 15-51.
Unit
Times
Related Features
15-55


success from upper layer to the same frequency
Definition
Number of incoming handover success from upper layer to the same frequency
Description
the target cell receives from upper layer to the same frequency.
Usage
success from upper layer to the same frequency, and is used to observe the handover
flow.
Measurement Point
cause is BSC-controlled inter-BSC handover and the source cell is at upper and the same
Unit
Times
Related Features
15-56


attempts from the same frequency to upper layer
Definition
Number of outgoing handover attempts from the same frequency to upper layer
Description
the source cell sends from upper layer to the same frequency.
Usage
attempts from upper layer to the same frequency, which helps to make the network
planning.
Measurement Point
cells at upper layer and the same frequency, the counter increments. The measurement
Unit
Times
Related Features
15-57


success from the same frequency to upper layer
Definition
Number of outgoing handover success from the same frequency to upper layer
Description
the source cell sends from upper layer to the same frequency.
Usage
handover from upper layer to the same frequency, which helps to make the network
planning.
Measurement Point
completed message from the target cell, it means that MS has accessed the target channel,
handover successful. If the target cell is at upper layer and the same frequency, the counter
Unit
Times
Related Features
15-58


attempts from lower layer to the same frequency
Definition
Number of incoming handover attempts from lower layer to the same frequency
Description
the target cell receives from lower layer to the same frequency.
Usage
attempts from lower layer to the same frequency, which helps to make the network
planning.
Measurement Point
if the application cause is inter-cell incoming handover and the source cell is at lower layer
and the same frequency, the counter increments. The measurement point is A, as shown
in Figure 15-55.
Unit
Times
Related Features
15-59


success from lower layer to the same frequency
Definition
Number of incoming handover success from lower layer to the same frequency
Description
the target cell receives from lower layer to the same frequency.
Usage
success from lower layer to the same frequency, and is used to observe the handover
flow.
Measurement Point
cause is BSC-controlled inter-BSC handover and the source cell is at lower and the same
Unit
Times
Related Features
15-60


attempts from the same frequency to lower layer
Definition
Number of outgoing handover attempts from the same frequency to lower layer
Description
the source cell sends from the same frequency to lower layer.
Usage
attempts from the same frequency to lower layer, which helps to make the network
planning.
Measurement Point
cells at lower layer and the same frequency, the counter increments. The measurement
Unit
Times
Related Features
15-61


success from the same frequency to lower layer
Definition
Number of outgoing handover success from the same frequency to lower layer
Description
the source cell sends from the same frequency to lower layer.
Usage
handover from the same frequency to lower layer, which helps to make the network
planning.
Measurement Point
completed message from the target cell, and the target cell is at lower layer and the same
Unit
Times
Related Features
15-62


attempts from the same layer GSM900 to GSM1800
Definition
Number of incoming handover attempts from the same layer GSM900 to GSM1800
Description
the target cell (GSM1800) receives from the same layer (GSM900).
Usage
attempts from the same layer GSM900 to GSM1800, which helps to make the network
planning.
Measurement Point
source cell (GSM900), if the application cause is inter-cell handover and the source cell
is at the same layer, the counter increments. The measurement point is A, as shown in
Figure 15-59.
Unit
Times
Related Features
15-63


attempts to the same layer GSM900 to GSM1800
Definition
Number of outgoing handover attempts to the same layer GSM900 to GSM1800
Description
the source cell (GSM900) sends to the same layer (GSM1800).
Usage
attempts to the same layer GSM900 to GSM1800, which helps to make the network
planning.
Measurement Point
cells at the same layer (GSM1800) and the current serving cell is GSM900, the counter
Unit
Times
Related Features
15-64

15.54 C901090073 Number of outgoing handover to the

same layer GSM900 to GSM1800
Definition
Number of outgoing handover to the same layer GSM900 to GSM1800
Description
cell (GSM900) sends to the same layer (GSM1800).
Usage
attempts to the same layer GSM900 to GSM1800, which helps to make the network
planning.
Measurement Point
at the same layer and frequency, the counter increments. The measurement point is A, as
Unit
Times
Related Features
15-65


success to the same layer GSM900 to GSM1800
Definition
Number of outgoing handover success to the same layer GSM900 to GSM1800
Description
the source cell (GSM900) sends to the same layer and frequency (GSM1800).
Usage
handover to the same layer and frequency from GSM900 to GSM1800, which helps to
Measurement Point
the same layer and frequency, the counter increments. The measurement point is A, as
Unit
Times
Related Features
15-66


attempts from GSM900 to GSM1800 from the upper
layer
Definition
Number of incoming handover attempts from GSM900 to GSM1800 from the upper layer
Description
the target cell (GSM1800) receives from upper layer (GSM900).
Usage
attempts at upper layer and from GSM900 to GSM1800, which helps to make the network
planning.
Measurement Point
source cell (GSM900), if the application cause is inter-cell handover and the source cell is
at upper layer, the counter increments. The measurement point is A, as shown in Figure
15-63.
Unit
Times
Related Features
15-67


attempts from GSM900 to GSM1800 to the upper
layer
Definition
Number of outgoing handover attempts from GSM900 to GSM1800 to the upper layer
Description
the source cell (GSM900) sends to upper layer (GSM1800).
Usage
attempts from GSM900 to GSM1800 to the upper layer, which helps to make the network
planning.
Measurement Point
cells at upper layer (GSM1800) and the current serving cell is GSM900, the counter
Unit
Times
15-68

Related Features
15.58 C901090079 Number of outgoing handover from

GSM900 to GSM1800 to the upper layer
Definition
Number of outgoing handover from GSM900 to GSM1800 to the upper layer
Description
cell (GSM900) sends to upper layer (GSM1800).
Usage
planning.
Measurement Point
at upper layer and the same frequency, the counter increments. The measurement point
Unit
Times
Related Features
15-69


success from GSM900 to GSM1800 to the upper
layer
Definition
Number of outgoing handover success from GSM900 to GSM1800 to the upper layer
Description
the source cell (GSM900) sends from upper layer to the same frequency (GSM1800).
Usage
handover from upper layer to the same frequency from GSM900 to GSM1800, which
helps to make the network planning.
Measurement Point
upper layer and the same frequency, the counter increments. The measurement point is
Unit
Times
Related Features
15-70


attempts from GSM900 to GSM1800 from the lower
layer
Definition
Number of incoming handover attempts from GSM900 to GSM1800 from the lower layer
Description
the target cell (GSM1800) receives from lower layer (GSM900).
Usage
attempts at lower layer and from GSM900 to GSM1800, which helps to make the network
planning.
Measurement Point
source cell (GSM900), if the application cause is inter-cell handover and the source cell is
at lower layer, the counter increments. The measurement point is A, as shown in Figure
15-67.
Unit
Times
Related Features
15-71


layer
Definition
Number of outgoing handover attempts from GSM900 to GSM1800 from the lower layer
Description
the source cell (GSM900) sends to lower layer (GSM1800).
Usage
attempts to lower layer and from GSM900 to GSM1800, which helps to make the network
planning.
Measurement Point
cells at lower layer (GSM1800) and the current serving cell is GSM900, the counter
Unit
Times
15-72

Related Features

GSM900 to GSM1800 in the lower layer
Definition
Number of outgoing handover from GSM900 to GSM1800 in the lower layer
Description
cell (GSM900) sends to lower layer (GSM1800).
Usage
attempts to lower layer and from GSM900 to GSM1800, which helps to make the network
planning.
Measurement Point
at lower layer and the same frequency, the counter increments. The measurement point
Unit
Times
Related Features
15-73


success from GSM900 to GSM1800 in the lower
layer
Definition
Number of outgoing handover success from GSM900 to GSM1800 in the lower layer
Description
the source cell (GSM900) sends from the same frequency to lower layer (GSM1800).
Usage
handover from the same frequency to lower layer from GSM900 to GSM1800, which
Measurement Point
lower layer and the same frequency, the counter increments. The measurement point is
Unit
Times
Related Features
15-74


attempts from GSM1800 to GSM900 from the same
layer
Definition
Number of incoming handover attempts from GSM1800 to GSM900 from the same layer
Description
the target cell (GSM900) receives from the same layer (GSM1800).
Usage
attempts at the same layer and from GSM1800 to GSM900, which helps to make the
network planning.
Measurement Point
is at the same layer, the counter increments. The measurement point is A, as shown in
Figure 15-71.
Unit
Times
Related Features
15-75


attempts from GSM1800 to GSM900 from the same
layer
Definition
Number of outgoing handover attempts from GSM1800 to GSM900 from the same layer
Description
the source cell (GSM1800) sends to the same layer (GSM900).
Usage
attempts to the same layer and from GSM1800 to GSM900, which helps to make the
network planning.
Measurement Point
cells at the same layer (GSM900) and the current serving cell is GSM1800, the counter
Unit
Times
15-76

Related Features

GSM1800 to GSM900 from the same layer
Definition
Number of outgoing handover from GSM1800 to GSM900 from the same layer
Description
cell (GSM1800) sends to the same layer (GSM900).
Usage
attempts to the same layer and from GSM1800 to GSM900, which helps to make the
network planning.
Measurement Point
at the same layer and frequency, the counter increments. The measurement point is A, as
Unit
Times
Related Features
15-77


success from GSM1800 to GSM900 from the same
layer
Definition
Number of outgoing handover success from GSM1800 to GSM900 from the same layer
Description
the source cell (GSM1800) sends to the same layer and frequency (GSM900).
Usage
handover to the same layer and frequency and from GSM1800 to GSM900, which helps
to make the network planning.
Measurement Point
handover completed message from the target cell (GSM900), and the target cell is at the
same layer and frequency, the counter increments. The measurement point is A, as shown
in Figure 15-74.
Unit
Times
Related Features
15-78


attempts from GSM1800 to GSM900 from the upper
layer
Definition
Number of incoming handover attempts from GSM1800 to GSM900 from the upper layer
Description
the target cell (GSM900) receives from upper layer (GSM1800).
Usage
attempts at upper layer and from GSM1800 to GSM900, which helps to make the network
planning.
Measurement Point
is at upper layer, the counter increments. The measurement point is A, as shown in Figure
15-75.
Unit
Times
Related Features
15-79


attempts from GSM1800 to GSM900 to the upper
layer
Definition
Number of outgoing handover attempts from GSM1800 to GSM900 to the upper layer
Description
the source cell (GSM1800) sends to upper layer (GSM900).
Usage
planning.
Measurement Point
cells at upper layer (GSM900) and the current serving cell is GSM1800, the counter
Unit
Times
15-80

Related Features

GSM1800 to GSM900 to the upper layer
Definition
Number of outgoing handover from GSM1800 to GSM900 to the upper layer
Description
cell (GSM1800) sends to upper layer (GSM900).
Usage
planning.
Measurement Point
at upper layer and the same frequency, the counter increments. The measurement point
Unit
Times
Related Features
15-81


success from GSM1800 to GSM900 to the upper
layer
Definition
Number of outgoing handover success from GSM1800 to GSM900 to the upper layer
Description
the source cell (GSM1800) sends from upper layer to the same frequency (GSM900).
Usage
handover from upper layer to the same frequency and from GSM1800 to GSM900, which
Measurement Point
During the process of BSC-controlled handover, if the source cell (GSM1800) receives
the handover completed message from the target cell (GSM900), and the target cell is at
upper layer and the same frequency, the counter increments. The measurement point is
Unit
Times
Related Features
15-82


layer
Definition
Number of incoming handover attempts from GSM1800 to GSM900 from the lower layer
Description
the target cell (GSM900) receives from lower layer (GSM1800).
Usage
attempts from GSM1800 to GSM900 from the lower layer, which helps to make the
network planning.
Measurement Point
is at lower layer, the counter increments. The measurement point is A, as shown in Figure
15-79.
Unit
Times
Related Features
15-83


attempts from GSM1800 to GSM900 to the lower
layer
Definition
Number of outgoing handover attempts from GSM1800 to GSM900 to the lower layer
Description
the source cell (GSM1800) sends to lower layer (GSM900).
Usage
attempts from GSM1800 to GSM900 to the lower layer, which helps to make the network
planning.
Measurement Point
cells at lower layer (GSM900) and the current serving cell is GSM1800, the counter
Unit
Times
15-84

Related Features

GSM1800 to GSM900 to the lower layer
Definition
Number of outgoing handover from GSM1800 to GSM900 to the lower layer
Description
cell (GSM1800) sends to lower layer (GSM900).
Usage
attempts from GSM1800 to GSM900 to the lower layer, which helps to make the network
planning.
Measurement Point
at lower layer and the same frequency, the counter increments. The measurement point
Unit
Times
Related Features
15-85


success from GSM1800 to GSM900 to the lower
layer
Definition
Number of outgoing handover success from GSM1800 to GSM900 to the lower layer
Description
the source cell (GSM1800) sends from the same frequency to lower layer (GSM900).
Usage
handover from the same frequency from GSM1800 to GSM900 to the lower layer, which
Measurement Point
handover completed message from the target cell (GSM900), and the target cell is at lower
layer and the same frequency, the counter increments. The measurement point is A, as
Unit
Times
Related Features
15-86

15.76 C901090105 Number of intra-cell handover

attempts
Definition
Number of intra-cell handover attempts
Description
This counter counts the number of intra-cell handover attempts originated from the source
cell by MS.
Usage
This counter is used to find out the frequency of intra-cell handover attempts. It is one of
the parameters to measure the wireless environment.
Measurement Point
intra-cell handover is necessary, the counter increments. The measurement point is A, as
Figure 15-83 Intra-Cell Handover Attempt
Unit
Times
Related Features
15-87

15.77 C901090108 Number of intra-cell

inner-circle-to-outer-circle handover attempts
Definition
Number of intra-cell inner-circle-to-outer-circle handover attempts
Description
This counter counts the number of inner-circle-to-outer-circle handover attempts originated
by MS when configuring the sub cell.
Usage
This counter is used to find out the frequency of inter-sub cell inner-circle-to-outer-circle
handover attempts. It is one of the parameters to measure the sub cell operation status.
Measurement Point
If inner-circle-to-outer-circle handover is necessary, the counter increments. The
Unit
Times
Related Features
15-88


inner-circle-to-outer-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 Point
During handover, if the source instance receives the handover completed message from
the target instance, and the application cause is inner-circle-to-outer-circle handover, the
Figure 15-85 Successful Intra-Cell Handover
Unit
Times
Related Features
15-89


outer-circle-to-inner-circle handover attempts
Definition
Number of intra-cell outer-circle-to-inner-circle handover attempts
Description
This counter counts the number of outer-circle-to-inner-circle handover attempts originated
Usage
This counter is used to find out the frequency of inter-sub cell outer-circle-to-inner-circle
Measurement Point
If outer-circle-to-inner-circle handover is necessary, the counter increments. The
Unit
Times
Related Features
15-90


outer-circle-to-inner-circle handover success
Definition
Number of intra-cell outer-circle-to-inner-circle handover success
Description
This counter counts the number of successful outer-circle-to-inner-circle handovers
Usage
outer-circle-to-inner-circle handovers, and is to find out the success ratio of intra-sub
cell handovers.
Measurement Point
the target instance, and the application cause is outer-circle-to-inner-circle handover, the
Unit
Times
Related Features
15-91


inner-circle-to-inner-circle handover attempts
Definition
Number of intra-cell inner-circle-to-inner-circle handover attempts
Description
This counter counts the number of inner-circle-to-inner-circle handover attempts originated
Usage
This counter is used to find out the frequency of inter-sub cell inner-circle-to-inner-circle
Measurement Point
If inner-circle-to-inner-circle handover is necessary, the counter increments. The
Unit
Times
Related Features
15-92


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
Usage
inner-circle-to-inner-circle handovers.
Measurement Point
the target instance, and the application cause is inner-circle-to-inner-circle handover, the
Unit
Times
Related Features
15-93


outer-circle-to-outer-circle handover attempts
Definition
Number of intra-cell outer-circle-to-outer-circle handover attempts
Description
This counter counts the number of outer-circle-to-outer-circle handover attempts originated
Usage
This counter is used to find out the frequency of inter-sub cell outer-circle-to-outer-circle
Measurement Point
If outer-circle-to-outer-circle handover is necessary, the counter increments. The
Unit
Times
Related Features
15-94


outer-circle-to-outer-circle handover success
Definition
Number of intra-cell outer-circle-to-outer-circle handover success
Description
This counter counts the number of successful outer-circle-to-outer-circle handovers
Usage
outer-circle-to-outer-circle handovers.
Measurement Point
the target instance, and the application cause is outer-circle-to-outer-circle handover, the
Unit
Times
Related Features
15-95

15.85 C901090116 Number of handover attempts from

2G to 3G
Definition
Number of handover attempts from 2G to 3G
Description
This counter counts the number of inter-system 2G to 3G handover attempts originated by
MS.
Usage
This counter is used to find out the frequency of handover attempts from 2G to 3G. It is
one of the parameters to measure the wireless environment.
Measurement Point
If inter-cell handover is necessary, and the current attempt cells are 3G cells, BSC
sends MSC the handover request message A_HO_RQD, the counter increments. The
measurement point is A, as shown inFigure 15-92.
Unit
Times
Related Features
15-96

15.86 C901090117 Number of handover from 2G to 3G

Definition
Number of handover from 2G to 3G
Description
This counter counts the number of inter-system 2G to 3G handover originated by MS.
Usage
This counter is used to find out the frequency of handover from 2G to 3G. It is one of the
parameters to measure the wireless environment.
Measurement Point
inter-cell handover is necessary, and the 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 counter increments. The
Figure 15-93 MSC-Controlled Outgoing Handover
Unit
Times
Related Features
15-97

15.87 C901090118 Number of 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 from 2G to 3G. It is one
of the parameters to measure the wireless environment.
Measurement Point
inter-cell handover is necessary, and the current attempt cells are governed by various
BSCs, BSC sends MSC the handover request message A_HO_RQD to trigger the inter-BSC
handover. If MS accesses the target 3G cell successfully and the source 2G cell receives
the release command from MSC, the counter increments. The measurement point is A,
Figure 15-94 Successful MSC-Controlled Outgoing Handover
Unit
Times
Related Features
15-98


3G to 2G
Definition
Number of handover attempts from 3G to 2G
Description
This counter counts the number of inter-system 3G to 2G handover attempts originated by
MS.
Usage
This counter is used to find out the frequency of handover attempts from 3G to 2G. It is
Measurement Point
When 2G cell receives the channel application request, if the application cause is
external incoming handover and the source cell is 3G cell, the counter increments. The
Unit
Times
Related Features
15-99

15.89 C901090120 Number of 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
Measurement Point
When 2G cell receives the channel handover request from MSC, if the channel is
successfully allocated and activated, and the source cell is 3G cell, the counter
Figure 15-96 MSC-Controlled Incoming Handover
Unit
Times
Related Features

3G to 2G
Definition
Number of handover success from 3G to 2G
15-100

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 from 3G to 2G. It is one
of the parameters to measure the wireless environment.
Measurement Point
When 2G cell receives the handover completed message, if the application cause is
MSC-controlled inter-BSC incoming handover and the source cell is 3G cell, the counter
Unit
Times
Related Features

attempts from TCH/F
Definition
Number of intra-cell handover attempts from TCH/F
Description
This counter counts the number of intra-cell incoming handover attempts from TCH/F
originated by MS.
Usage
This counter is used to find out the frequency of intra-cell incoming handover attempts from
TCH/F. It is one of the parameters to measure the wireless environment.
15-101

Measurement Point
When BSC receives the channel application request, if the application cause is intra-cell
handover, and the source channel is TCH/F, the counter increments. The measurement
Figure 15-98 Intra-Cell Incoming Handover Attempt
Unit
Times
Related Features
15.92 C901090123 Number of 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 incoming handover
originated by MS.
Usage
This counter is used to find out the frequency of intra-cell TCH/F-to-TCH/F incoming
Measurement Point
handover, and the source channel is TCH/F; if the new channel is successfully applied and
activated, the counter increments. The measurement point is A, as shown in Figure 15-99.
15-102

Figure 15-99 Intra-Cell Incoming Handover
Unit
Times
Related Features
15.93 C901090124 Number of 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.
Usage
This counter is used to find out the frequency of successful intra-cell TCH/F-to-TCH/F
incoming handover. It is one of the parameters to measure the wireless environment.
Measurement Point
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
15-103

Unit
Times
Related Features
15.94 C901090125 Number of intra-cell TCH/F-to-TCH/H

handover
Definition
Number of intra-cell TCH/F-to-TCH/H handover
Description
This counter counts the number of intra-cell TCH/F-to-TCH/H incoming handover
originated by MS.
Usage
This counter is used to find out the frequency of intra-cell TCH/F-to-TCH/H incoming
Measurement Point
handover, and the source channel is TCH/H; if the new channel is successfully applied
and activated, the counter increments. The measurement point is A, as shown in Figure
15-101.
15-104

Unit
Times
Related Features
15.95 C901090126 Number of 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
Usage
This counter is used to find out the frequency of successful intra-cell TCH/F-to-TCH/H
Measurement Point
and the new channel is TCH/H, the counter increments. The measurement point is A, as
15-105

Unit
Times
Related Features

attempts 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 measure the wireless environment.
Measurement Point
handover, and the source channel is TCH/H, the counter increments. The measurement
15-106

Unit
Times
Related Features
15.97 C901090128 Number of 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 incoming handover
originated by MS.
Usage
This counter is used to find out the frequency of intra-cell TCH/H-to-TCH/F incoming
Measurement Point
and activated and the new channel is TCH/F, the counter increments. The measurement
15-107

Unit
Times
Related Features
15.98 C901090129 Number of 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-TCH/F incoming
Usage
This counter is used to find out the frequency of successful intra-cell TCH/H-to-TCH/F
Measurement Point
handover, and the source channel is TCH/H; if MS successfully accesses the new channel
and the new channel is TCH/F, the counter increments. The measurement point is A,
15-108

Unit
Times
Related Features
15.99 C901090130 Number of 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 incoming handover
originated by MS.
Usage
This counter is used to find out the frequency of intra-cell TCH/H-to-TCH/H incoming
Measurement Point
and activated and the new channel is TCH/H, the counter increments. The measurement
15-109

Unit
Times
Related Features

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-TCH/H incoming
Usage
This counter is used to find out the frequency of successful intra-cell TCH/H-to-TCH/H
Measurement Point
15-110

Unit
Times
Related Features
15.101 C901090132 Number of inter-cell handover

attempts from TCH/F
Definition
Number of inter-cell handover attempts from TCH/F
Description
This counter counts the number of inter-cell incoming handover attempts from TCH/F
originated by MS.
Usage
This counter is used to find out the frequency of inter-cell incoming handover attempts from
TCH/F. It is one of the parameters to measure the wireless environment.
Measurement Point
When BSC receives the channel application request, if the application cause is inter-cell
handover, and the source channel is TCH/F, the counter increments. The measurement
15-111

Unit
Times
Related Features
15.102 C901090133 Number of inter-cell

TCH/F-to-TCH/F handover
Definition
Number of inter-cell TCH/F-to-TCH/F handover
Description
This counter counts the number of inter-cell TCH/F-to-TCH/F incoming handover
originated by MS.
Usage
This counter is used to find out the frequency of inter-cell TCH/F-to-TCH/F incoming
Measurement Point
handover, and the source channel is TCH/F; if the new channel is successfully applied
and activated, the counter increments. The measurement point is A, as shown in Figure
15-109.
15-112

Unit
Times
Related Features

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-TCH/F incoming
Usage
This counter is used to find out the frequency of successful inter-cell TCH/F-to-TCH/F
Measurement Point
15-113

Figure 15-110 BSC-Controlled Inter-Cell Incoming Handover
Unit
Times
Related Features

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 incoming handover
originated by MS.
Usage
This counter is used to find out the frequency of inter-cell TCH/F-to-TCH/H incoming
Measurement Point
handover, and the source channel is TCH/F; if the new channel is successfully applied and
activated and the new channel is TCH/H, the counter increments. The measurement point
15-114

Unit
Times
Related Features

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-TCH/H incoming
Usage
This counter is used to find out the frequency of successful inter-cell TCH/F-to-TCH/H
Measurement Point
15-115

Unit
Times
Related Features
15.106 C901090137 Number of 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 measure the wireless environment.
Measurement Point
handover, and the source channel is TCH/H, the counter increments. The measurement
15-116

Unit
Times
Related Features

TCH/H-to-TCH/F handover
Definition
Number of inter-cell TCH/H-to-TCH/F handover
Description
This counter counts the number of inter-cell TCH/H-to-TCH/F incoming handover
originated by MS.
Usage
This counter is used to find out the frequency of inter-cell TCH/H-to-TCH/F incoming
Measurement Point
and activated and the new channel is TCH/F, the counter increments. The measurement
15-117

Unit
Times
Related Features

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-TCH/F incoming
Usage
This counter is used to find out the frequency of successful inter-cell TCH/H-to-TCH/F
Measurement Point
15-118

Unit
Times
Related Features

TCH/H-to-TCH/H handover
Definition
Number of inter-cell TCH/H-to-TCH/H handover
Description
This counter counts the number of inter-cell TCH/H-to-TCH/H incoming handover
originated by MS.
Usage
This counter is used to find out the frequency of inter-cell TCH/H-to-TCH/H incoming
Measurement Point
and activated and the new channel is TCH/H, the counter increments. The measurement
15-119

Unit
Times
Related Features

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-TCH/H incoming
Usage
This counter is used to find out the frequency of successful inter-cell TCH/H-to-TCH/H
Measurement Point
15-120

Unit
Times
Related Features
15.111 C901090142 Total dual-band outgoing handover

attempts
Definition
Total dual band outgoing handover attempts
Description
This counter counts the number of MSC-controlled inter-BSC (the source cell and the target
cell are at different bands) outgoing handover attempts originated from the source cell by
MS.
Usage
This counter is used to find out the frequency of MSC-controlled inter-BSC (the source
cell and the target cell are at different bands) outgoing handover attempts. It is one of the
Measurement Point
inter-cell handover is necessary, and the current attempt cells are governed by different
BSCs, BSC will send MSC the handover request A_HO_RQD to trigger inter-BSC
15-121

handover. If the source cell and the target cell that are at different bands, the counter
Unit
Times

handover 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 wireless environment.
Measurement Point
When the target cell receives the channel application request, if the application cause is
external incoming handover, and the source cell and the target cell that are at different
bands, the counter increments. The measurement point is A, as shown in Figure 15-119.
15-122

Unit
Times
15.113 C901090148 Number of intra-cell invalid

handovers
Definition
Number of intra-cell invalid handovers
Description
This counter counts the number of intra-cell invalid handovers. Invalid handover refers
to that: handovers continue to happen in a cell where there is UL /DL interference; if the
number of the handovers exceeds the pre-set threshold, intra-cell handover punishment
will be triggered to stop the continuous handovers; if there is no new interference handover
during sending the measurement report of pre-set number, then the next handover will be
considered valid.
Usage
This counter is used to find out the frequency of intra-cell invalid handover attempts. It is
Measurement Point
interference handover, and such interference handover has already occurred in the
pre-defined scope of time, the counter increments. The measurement point is A, as
15-123

Unit
Times
Related Features
ZGO-02-02-005 Handover Failure Penalty
15.114 C901090149 Number of BSC-controlled

inter-cell incoming handover attempts due to
forced release (emergency service)
Definition
Number of BSC-controlled inter-cell incoming handover attempts due to forced release
(emergency service)
Description
This counter counts the number of forced release attempts due to unavailable radio
resource in target cell in the process of BSC-controlled inter-cell incoming handover
initiated by a MS on emergency service. Target instance can initiate forced release
attempt based on MS priority and MSC & BSC settings during channel allocation failure.
Usage
This counter counts the frequency of forced release attempts occurred during
BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover
process.
Measurement Point
Intra-BSC target cell receives radio channel request to determine whether to do forced
release attempt if the request reason is BSC-controlled inter-cell incoming handover and
15-124

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

inter-cell incoming handover (forced release)
(emergency service)
Definition
Number of BSC-controlled inter-cell incoming handover (forced release) (emergency
service)
Description
This counter counts the number of forced release due to unavailable radio resource in
target cell in the process of BSC-controlled inter-cell incoming handover initiated by a MS
on emergency service.
Usage
This counter counts the frequency of forced release occurred during BSC-controlled
inter-cell incoming handover initiated by a MS. It can reflect the handover process.
15-125

Measurement Point
Intra-BSC target cell receives radio channel request to do forced release if the request
reason is BSC-controlled inter-cell incoming handover and the target cell has not available
radio channel. This counter increments if target cell receives available resource message
sent from forced instance. The measurement point is A2, as shown in Figure 15-122.
Figure 15-122 BSC-Controlled Forced Release On Incoming Handover
Unit
Times

forced handover (emergency service)
Definition
Number of BSC-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 BSC-controlled inter-cell incoming handover
initiated by a MS on emergency service.
15-126

Usage
This counter counts the frequency of forced handover attempts occurred during
process.
Measurement Point
Intra-BSC target cell receives radio channel request to determine 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. The measurement point is
Unit
Times

inter-cell incoming handover (forced handover)
(emergency service)
Definition
Number of BSC-controlled inter-cell incoming handover (forced handover) (emergency
service)
15-127

Description
This counter counts the number of forced handover due to unavailable radio resource in
Usage
This counter counts the frequency of forced handover occurred during BSC-controlled
Measurement Point
Intra-BSC target cell receives radio channel request and adds it into a queue after
sending forced handover message to forced handover instance if the request reason is
BSC-controlled inter-cell incoming handover and the target cell has not available radio
channel. This counter increments if target cell receives available resource message. The
Figure 15-124 BSC-Controlled Forced Handover On Incoming Handover
Unit
Times
15-128


queue (emergency service)
Definition
Number of BSC-controlled inter-cell incoming handover attempts due to queue
(emergency service)
Description
This counter counts the number of queue attempts due to unavailable radio resource in
Usage
This counter counts the frequency of queue attempts occurred during BSC-controlled
Measurement Point
Intra-BSC target cell receives radio channel request to determine 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 15-125.
Unit
Times
15-129


inter-cell 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 Point
Intra-BSC target cell receives radio channel request and adds target instance into a queue
if the request reason is BSC-controlled inter-cell incoming handover and the target cell
has not available radio channel. Thereafter, this counter increments if target cell receives
available resource message. The measurement point is A2, as shown in Figure 15-126.
15-130

Figure 15-126 BSC-Controlled Queue On Incoming Handover
Unit
Times
15.120 C901090155 Number of MSC-controlled

incoming handover attempts due to forced release
(emergency service)
Definition
Number of MSC-controlled incoming handover attempts 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 MSC-controlled inter-BSC incoming handover
initiated by a MS on emergency service. Target instance can initiate forced release
attempt based on MS priority and MSC & BSC settings during channel allocation failure.
15-131

Usage
This counter counts the frequency of forced release attempts occurred during
BSC-controlled inter-BSC incoming handover initiated by a MS. It can reflect the handover
process.
Measurement Point
Target cell receives radio channel request to determine whether to do forced release
attempt if the request reason is MSC-controlled inter-BSC incoming handover and the
target cell has not available radio channel. This counter increments before target cell
sends forced release message to forced release instance. The measurement point is A
Figure 15-127 MSC-Controlled Forced Release Attempt On Incoming Handover
Unit
Times

incoming handover (forced release) (emergency
service)
Definition
Number of MSC-controlled incoming handover (forced release) (emergency service)
Description
target cell in the process of MSC-controlled inter-BSC incoming handover initiated by a
MS on emergency service.
15-132

Usage
inter-BSC incoming handover initiated by a MS. It can reflect the handover process.
Measurement Point
MSC-controlled inter-BSC incoming handover and the target cell has not available radio
Figure 15-128 MSC-Controlled Forced Release On Incoming Handover
Unit
Times

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 emergency service.
15-133

Usage
This counter counts the frequency of forced handover attempt occurred during
MSC-controlled inter-BSC incoming handover initiated by a emergent MS. It can reflect
the handover process.
Measurement Point
Target cell receives radio channel request to determine whether to do forced handover
attempt if the request reason is MSC-controlled inter-BSC incoming handover and the
target cell has not available radio channel. This counter increments before target cell
sends forced handover message to forced handover instance. The measurement point is
Figure 15-129 MSC-Controlled Forced Handover Attempt On Incoming Handover
Unit
Times

incoming handover (forced release) (emergency
service)
Definition
Number of MSC-controlled incoming handover (forced release) (emergency service)
Description
15-134

Usage
Measurement Point
MSC-controlled inter-BSC incoming handover and the target cell has not available radio
Figure 15-130 MSC-Controlled Forced Handover On Incoming Handover
Unit
Times

incoming handover attempts due to queue
(emergency service)
Definition
Number of MSC-controlled incoming handover attempts due to queue (emergency service)
Description
This counter counts the number of queue attempts due to unavailable radio resource in
Usage
This counter counts the frequency of queue attempts occurred during BSC-controlled
15-135

Measurement Point
Target cell receives radio channel request to determine whether to do a queue if the
request reason is MSC-controlled inter-BSC incoming handover and the target cell has
not available radio channel. This counter increments if target cell adds target instance
into a queue. The measurement point is A, as shown in Figure 15-131.
Figure 15-131 MSC-Controlled Queue Attempt On Incoming Handover
Unit
Times

incoming handover (queue) (emergency service)
Definition
Number of MSC-controlled incoming handover (queue) (emergency service)
Description
This counter counts the number of queue due to unavailable radio resource in target
cell in the process of MSC-controlled inter-BSC incoming handover initiated by a MS on
emergency service.
Usage
This counter counts the frequency of queue occurred during BSC-controlled inter-BSC
incoming handover initiated by a MS. It can reflect the handover process.
Measurement Point
Target cell receives radio channel request and adds target instance into a queue if the
request reason is MSC-controlled inter-BSC incoming handover and the target cell has not
available radio channel. Thereafter, this counter increments if target cell receives available
resource message. The measurement point is A, as shown in Figure 15-132.
15-136

Figure 15-132 MSC-Controlled Queue On Incoming Handover
Unit
Times
15.126 C901090161 Number of 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
process.
Measurement Point
Intra-BSC target cell receives radio channel request if the request reason is BSC-controlled
inter-cell incoming handover and the target cell has not available radio channel. This
counter increments if the forced handover target is not found after initiating forced handover
attempt. The measurement point is A, as shown inFigure 15-133.
15-137

Figure 15-133 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 due to forced handover)
Definition
Number of send forced handover request to lower PRI user (BSC-controlled inter-cell
Description
This counter counts the number of sending forced handover request to lower priority user
on forced handover attempt due to unavailable radio resource in target cell in the process
of BSC-controlled inter-cell incoming handover initiated by a MS.
Usage
This counter counts the frequency of sending forced handover request to a lower priority
user during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect
Measurement Point
15-138

counter increments if sending forced handover request to a lower priority user after
initiating forced handover attempt. The measurement point is A, as shown in Figure
15-134.
Figure 15-134 Send Forced Handover Request To Lower Pri User (BSC-Controlled
Inter-Cell Handover Due To Forced Handover)
Unit
Times
15.128 C901090163 Number of recv failure from lower

PRI user request resource for forced handover
(BSC-controlled inter-cell handover due to 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 priority user due to failure
of resource while forced handover attempt is initiated due to unavailable radio resource in
target cell in the process of BSC-controlled inter-cell incoming handover initiated by a MS.
15-139

Usage
This counter counts the frequency of receiving failure of forced handover request from a
lower priority user during BSC-controlled inter-cell incoming handover initiated by a MS. It
can reflect the handover process.
Measurement Point
counter increments if receiving failure of forced handover request from a lower priority
user after initiating forced handover attempt. The measurement point is A, as shown in
Figure 15-135.
Figure 15-135 Recv Failure From Lower Pri User Request Resource For Forced
Handover (BSC-Controlled Inter-Cell Handover Due To Forced Handover)
Unit
Times
15-140


failure (BSC-controlled inter-cell handover due to
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 priority 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 incoming handover initiated by a MS. It can reflect the
handover process.
Measurement Point
counter increments if receiving handover failure from a lower priority user after initiating
forced handover attempt. The measurement point is A, as shown in Figure 15-136.
15-141

Figure 15-136 Recv Failure From Lower Pri User Request Resource For Forced
Handover (BSC-Controlled Inter-Cell Handover Due To Forced Handover)
Unit
Times
15.130 C901090165 Number of high PRI user time

out for wait resource (BSC-controlled inter-cell
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.
15-142

Measurement Point
counter increments if timeout for waiting resource occurs after initiating forced handover.
Figure 15-137 - High Pri User Time Out For Wait Resource (BSC-Controlled Inter-Cell
Handover Due To Forced Handover)
Unit
Times
15.131 C901090166 Number of forced release target

not found (BSC-controlled inter-cell handover due
to forced release)
Definition
Number of forced release target not found (BSC-controlled inter-cell handover due to
forced release)
15-143

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
Measurement Point
counter increments if the forced release target is not found after initiating forced release
attempt. The measurement point is A, as shown in Figure 15-138.
Figure 15-138 Forced Release Target Not Found (BSC-Controlled Inter-Cell Handover
Due To Forced Release)
Unit
Times
15-144


out for wait resource (BSC-controlled inter-cell
handover due to forced release)
Definition
Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover
due to forced release)
Description
This counter counts the number of timeout for waiting resource while initiating forced
release due to unavailable radio resource in target cell in the process of BSC-controlled
inter-cell incoming handover initiated by a MS.
Usage
This counter counts the frequency of timeout for waiting resource while initiating forced
release during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect
Measurement Point
counter increments if timeout for waiting resource occurs after initiating forced release.
15-145

Figure 15-139 High Pri User Time Out For Wait Resource (BSC-Controlled Inter-Cell
Handover Due To Forced Release)
Unit
Times
15.133 C901090168 Number of HO Target not found

(MSC-controlled incoming handover due to forced
handover)
Definition
Number of HO Target not found (MSC-controlled incoming handover due to forced
handover)
Description
This counter counts the number of HO Target not found (MSC-controlled incoming
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.
15-146

Measurement Point
l This counter increments after BSC receives incoming handover message and does
forced handover attempt due to unavailable resource.
l This counter increments if the interval timer to search for handover target is timeout
on handover.
l This counter increments if waiting for handover resource and handover attempt fails.
l 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 due to forced handover)
Definition
Number of send forced handover request to lower PRI user (MSC-controlled incoming
Description
This counter counts the number of sending forced handover request to lower PRI user
(MSC-controlled incoming handover due to forced handover).
Usage
This counter counts the frequency of sending handover request to a lower priority user
on MSC-controlled incoming handover due to forced handover. It is one of parameters to
measure radio environment.
Measurement Point
l This counter increments after BSC receives incoming handover message and does
forced handover attempt due to unavailable resource.
l This counter increments if the interval timer to search for handover target is timeout
on handover.
l This counter increments if waiting for handover resource and handover attempt fails.
forced handover.
Unit
Times
15-147

15.135 C901090170 Number of failure to lower PRI

user request resource for forced handover
(MSC-controlled incoming handover due to forced
handover)
Definition
Number of failure to lower PRI user request resource for forced handover (MSC-controlled
incoming handover due to forced handover)
Description
This counter counts the number of failure to lower PRI user request resource for forced
handover (MSC-controlled incoming handover due to forced handover).
Usage
This counter counts the frequency of failure request resource for lower priority user on
MSC-controlled incoming handover due to forced handover. It is one of parameters to
Measurement Point
This counter increments if BSC receives forced handover failure and incoming handover
fails due to failure of resource request.
Unit
Times

failure (MSC-controlled incoming handover due to
forced handover)
Definition
Number of lower PRI user handover failure (MSC-controlled incoming handover due to
forced handover)
Description
This counter counts the number of handover failure to lower PRI user for forced handover
(MSC-controlled incoming handover due to forced handover).
15-148

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
Measurement Point
This counter increments if BSC receives forced handover failure and incoming handover
fails due to failure of forced handover.
Unit
Times

out for wait resource (MSC-controlled incoming
Definition
Number of high PRI user time out for wait resource (MSC-controlled incoming handover
due to forced handover)
Description
This counter counts the number of high PRI user time out for wait resource (MSC-controlled
incoming handover due to forced handover).
Usage
This counter counts the frequency of timeout for waiting resource for higher priority user
on MSC-controlled incoming handover due to forced handover. It is one of parameters to
Measurement Point
This counter increments if the timer of waiting for resource after initiating forced handover.
Unit
Times
15-149

15.138 C901090173 Number of forced release target

not found (MSC-controlled incoming handover due
to forced release)
Definition
Number of forced release target not found (MSC-controlled incoming handover due to
forced release)
Description
This counter counts the number of forced release target not found (MSC-controlled
incoming handover due to forced handover).
Usage
This counter counts the frequency of forced release target not found on MSC-controlled
incoming handover due to forced handover. It is one of parameters to measure radio
environment.
Measurement Point
l This counter increments after BSC receives incoming forced release message and
does forced release due to unavailable resource.
l This counter increments if the interval timer to search for forced release target is
timeout on handover.
l This counter increments if waiting for handover resource and forced release fails.
forced handover.
l This counter increments if the timer to initiate forced release is timeout on handover.
forced release.
Unit
Times

out for wait resource (MSC-controlled incoming
handover due to forced release)
Definition
Number of high PRI user time out for wait resource (MSC-controlled incoming handover
due to forced release)
15-150

Description
This counter counts the number of high PRI user time out for wait resource (MSC-controlled
incoming handover due to forced release).
Usage
This counter counts the frequency of timeout for waiting resource for higher priority user
on MSC-controlled incoming handover due to forced release. It is one of parameters to
Measurement Point
This counter increments if the timer of waiting for resource is timeout after initiating forced
release.
Unit
Times

channel (assignment forced handover)
Definition
Number of get before grab released channel (assignment forced handover)
Description
This counter counts the number of getting previous grab released channel (assignment
forced handover).
Usage
This counter counts the frequency of getting the channel released by grabbing on forced
handover. It is one of parameters to measure radio environment.
Measurement Point
This counter increments if BSC receives effective messages in resource message on
forced handover and the messages hold database resource.
Unit
Times
15-151


channel (assignment forced release)
Definition
Number of get before grab released channel (assignment forced release)
Description
This counter counts the number of getting previous grab released channel (assignment
forced release).
Usage
This counter counts the frequency of getting the channel released by grabbing on forced
release. It is one of parameters to measure radio environment.
Measurement Point
This counter increments if BSC receives effective messages in resource message on
forced release and the messages hold database resource.
Unit
Times
15.142 C901090177 Number of handover attempts due

Definition
Number of handover attempts due to eMLPP forced handover
Description
This counter counts the number of handover attempts due to eMLPP forced handover.
Usage
This counter counts the frequency of handover attempts due to eMLPP forced handover.
It is one of parameters to measure radio environment.
Measurement Point
This counter increments if it is forced handover on intra-cell handover.
This counter increments if it is forced handover based on hierarchy and frequency
relationship on BSC-controlled inter-cell or MSC-controlled outgoing handover.
15-152

Unit
Times
15.143 C901090178 Number of handover due to eMLPP

forced handover
Definition
Number of handover due to eMLPP forced handover
Description
This counter counts the number of handover due to eMLPP forced handover.
Usage
This counter counts the frequency of handover due to eMLPP forced handover. It is one
of parameters to measure radio environment.
Measurement Point
This counter increments if it is forced handover on intra-cell handover.
relationship on BSC-controlled inter-cell or MSC-controlled outgoing handover.
Unit
Times
15.144 C901090179 Number of handover success due

Definition
Number of handover success due to eMLPP forced handover
Description
This counter counts the number of handover success due to eMLPP forced handover.
Usage
This counter counts the frequency of handover success due to eMLPP forced handover.
It is one of parameters to measure radio environment.
15-153

Measurement Point
This counter increments if it is intra-cell forced handover on handover success.
relationship on BSC-controlled inter-cell or MSC-controlled outgoing handover success.
Unit
Times

outgoing handover attempts between PLMN

inter-cell outgoing handover between PLMN

outgoing handover success between PLMN

outgoing handover attempts between PLMN

outgoing handover request fail between PLMN due
to unknown reason
15-154


to unavailable ground resource
Description
This counter counts the number of failures of MSC-controlled inter-PLMN outgoing
handover requests due to no available ground resource. When MSC receives the
handover request rejection message from BSC on TCH, it queries the rejection cause. If
the rejection cause is CAUSE_REQ_CIC_UNAVAIL, then the counter increments.
Usage
This counter is used to find out the frequency of failure of MSC-controlled inter-PLMN
outgoing handover request initiated by MS due to no available ground resource. It also
helps study the condition of handover initiated by MSC.
Measurement Point
When MSC receives the handover request rejection message from BSC, it queries the
rejection cause. If the rejection cause is CAUSE_REQ_CIC_UNAVAIL, then the counter
counts. The measurement point is A1, as shown in Figure 15-140.
Figure 15-140 MSC-Controlled Inter-PLMN Handover Flow
Unit
Times
15-155


to unavailable radio resource

to other reasons
Description
This counter counts the number of failures of MSC-controlled inter-PLMN outgoing
handover requests due to other reasons. When MSC receives the handover request
rejection message from BSC on TCH, it queries the rejection cause. If the rejection
cause is not CAUSE_REQ_CIC_UNAVAIL or CAUSE_NO_RR_AVAIL, then the counter
increments.
Usage
This counter is used to find out the frequency of failure of MSC-controlled inter-PLMN
outgoing handover request initiated by MS due to other reasons. It also helps study the
condition of handover initiated by MSC.
Measurement Point
When MSC receives the handover request rejection message from BSC, it queries
the rejection cause. If the rejection cause is not CAUSE_REQ_CIC_UNAVAIL or
CAUSE_NO_RR_AVAIL, then the counter counts.
Unit
Times

outgoing 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.
15-156

Usage
This counter is used to study the MSC-controlled inter-PLMN outgoing handover initiated
by MS. It also helps study the condition of handover initiated by MSC.
Measurement Point
1. When BSC receives the command Clear Cmd from A-interface, if the cause in this
command is CAUSE_HO_SUCCESSFUL, then the counter counts.
2. The counter counts when BSC fails to wait for the handover response message
returned from MS. The measurement point is shown in Figure 15-141.
Figure 15-141 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 15-142.
Figure 15-142 MSC-Controlled Inter-PLMN Outgoing Handover Execution and No Abnormal Release
Unit
Times
15-157


outgoing handover success between PLMN
Description
This counter counts the number of successful MSC-controlled inter-PLMN outgoing
handovers. When BSC receives the command Clear Cmd from MSC on TCH,
the timer THOOUTGO is timeout. If the cause in the command Clear Cmd is
CAUSE_HO_SUCCESSFUL, then the counter increments.
Usage
This counter is used to find out the number of successful MSC-controlled inter-PLMN
outgoing handovers. It also helps study the handover initiated by MSC.
Measurement Point
When BSC receives the command Clear Cmd from MSC, the timer THOOUTGO is timeout.
If the cause in the command Clear Cmd is CAUSE_HO_SUCCESSFUL, then the counter
counts.
Unit
Times

incoming handover attempt between PLMN

inter-cell incoming handover between PLMN

inter-cell incoming handover force-release attempt
between PLMN
15-158


inter-cell incoming handover between PLMN due
to force release

incoming handover queue attempt between PLMN

incoming handover between PLMN due to queue

inter-cell incoming handover force-handover
attempt between PLMN

inter-cell incoming handover between PLMN due
to force handover

incoming handover success between PLMN
15-159


incoming handover attempt between PLMN
Description
This counter counts the number of MSC-controlled inter-PLMN incoming handover
attempts. When BSC receives the RadioApply message from MSC, it queries the cause.
If AppCause is INCOME_HO, then the counter increments.
Usage
This counter is used to find out the number of MSC-controlled inter-PLMN incoming
handover attempts. It also helps study the handover initiated by MSC.
Measurement Point
When BSC receives the RadioApply message from MSC, it queries the cause. If
AppCause is INCOME_HO, then the counter counts. The measurement point is A1, as
Figure 15-143 MSC-Controlled Inter-PLMN Incoming Handover Flow
Unit
Times
15-160

15.165 C901090200 A interface incoming handover fail

between PLMN due to circuit block
Description
This counter counts the number of A-interface inter-PLMN incoming handover failures
due to circuit's being blocked. When MSC receives the Handover Failure message, if
the handover fails due to CAUSE_REQ_CIC_UNAVAIL and the handover is inter-PLMN
handover, then the counter increments.
Usage
This counter is used to find out the number of A-interface inter-PLMN incoming handover
failures due to circuit's being blocked. It also helps study the handover initiated by MSC.
Measurement Point
When MSC receives the Handover Failure message, if the handover failiure cause in this
message is CAUSE_REQ_CIC_UNAVAIL and the handover is inter-PLMN handover, then
the counter counts. The measurement point is A1, as shown in Figure 15-144.
Figure 15-144 A-Interface Inter-PLMN Incoming Handover Failure
Unit
Times
15-161


between PLMN due to circuit unmatch
Description
due to circuit mismatching. When MSC receives the Handover Failure message, if
the handover fails due to CAUSE_CIRCUIT_POOL_MISMATCH and the handover is
inter-PLMN handover, then the counter increments.
Usage
failures due to circuit mismatching. It also helps study the handover initiated by MSC.
Measurement Point
When MSC receives the Handover Failure message, if the handover failiure cause in
this message is CAUSE_CIRCUIT_POOL_MISMATCH and the handover is inter-PLMN
handover, then the counter counts.
Unit
Times

between PLMN due to unavailable radio resource
Description
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, the counter increments.
Usage
failures due to no available radio resource. It also helps study the handover initiated by
MSC.
15-162

Measurement Point
1. When MSC receives the Handover Failure message, if the handover failiure cause
in this message is CAUSE_NO_RR_AVAI and the handover is inter-PLMN handover,
then the counter counts.
2. When RanA receives the Handover Failure message, if the handover failiure cause
in this message is CAUSE_NO_RR_AVAI and the handover is inter-PLMN handover,
Unit
Times

between PLMN due to other reason

incoming handover between PLMN

incoming handover force-release attempt between
PLMN
Description
This counter counts the number of attempts of MSC-controlled inter-PLMN incoming
handover force-release. After BSC initiates the forced release, the counter counts the
number of force-release attempts during the assignment (or handover). If the cause of
channel request is INCOME_HO and the handover is inter-PLMN incoming handover,
then the counter increments.
Usage
This counter is used to find out the number of attempts of MSC-controlled inter-PLMN
incoming handover force-release. It also helps study the inter-PLMN incoming handover
force-release initiated by MSC.
15-163

Measurement Point
When BSC receives the command HoReq from MSC, if no radio resource is available and
forced release is allowed, then the counter counts.
Unit
Times

incoming handover between PLMN due to force
release
Description
This counter counts the number of MSC-controlled inter-PLMN incoming handover due to
forced release. After BSC initiates the forced release, the counter counts the number of
assignments (or handovers) due to forced release (or queuing). If the cause of channel
request is INCOME_HO and forced release is allowed and the handover is inter-PLMN
incoming handover, then the counter increments.
Usage
handover due to forced release. It also helps study the inter-PLMN incoming handover
initiated by MSC due to forced release.
Measurement Point
When BSC receives the command HoReq from MSC, if the CS instance carries the
RADIO_AVAILABLE message and forced release is allowed, then the counter counts.
Unit
Times

incoming handover queue attempt between PLMN
Description
handover queuing. When BSC receives the command Ho Req from MSC, it sends the
15-164

command Chan Act to BTS. If channel requests fails but queuing is allowed, the counter
increments.
Usage
incoming handover queuing. It also helps study the inter-PLMN incoming handover, which
is initiated by MSC, in case of no channel resource.
Measurement Point
When BSC receives the command Ho Req from MSC, it sends the command Chan Act
to BTS. If no channel request fails but queuing is allowed, then the counter counts. The
Figure 15-145 Inter-MSC Handover
Unit
Times

incoming handover between PLMN due to queue
Description
This counter counts the number of MSC-controlled inter-PLMN incoming handover due to
queuing. After BSC receives the handover command, it requests for channel resource. If
the request fails, the cause of channel request is INCOME_HO, queuing is allowed, and
the handover is inter-PLMN incoming handover, then the counter increments.
15-165

Usage
handover due to queuing. It also helps study the inter-PLMN incoming handover, which
is initiated by MSC, in case of no channel resource.
Measurement Point
When BSC receives the command HoReq from MSC, if the CS instance carries the
RADIO_AVAILABLE message and queuing is allowed, then the counter counts.
Unit
Times

incoming handover force-handover attempt
between PLMN
Description
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
incoming handover force-handover. It also helps study the inter-PLMN incoming handover,
which is initiated by MSC, in case of no channel resource.
Measurement Point
When BSC receives the command Ho Req from MSC, it sends the command Chan Act to
BTS. If no channel request fails but forced handover is allowed, then the counter counts.
Unit
Times
15-166


incoming handover between PLMN due to force
handover

incoming handover success between PLMN
15.177 C901090212 Number of 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 the counter increments.
Usage
This counter is used to find out the number of handovers due to HR fragment reorganization
in the cell. It helps study the CS service migration.
Measurement Point
When Rancs receives the CS service migration sent from DBS, if byCsMoveCause ==
HR_DEFRAG, then the counter counts.
Unit
Times
15.178 C901090213 Number of handover success due

to 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
15-167

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 Point
When BSC receives the CS service migration command from DBS, it sends the command
Chan Act to BTS. After the command Chan Act Ack is received, if the assignment at Um
interface succeeds and byCsMoveCause == HR_DEFRAG, then the counter counts. The
Figure 15-146 Handover Success due to CS Service Migration
Unit
Times
15-168

Chapter 16
Adjacent Cell Handover
Measurement
Table of Contents
Overview ..................................................................................................................16-2
C901100001 Number of handover attempts on the adjacent cell. .............................16-2
C901100002 Number of handover success from selected cell to the adjacent cell. ...16-3
C901100003 Number of handover attempts from adjacent cell to the selected cell. ..16-4
C901100004 Number of handover success from adjacent cell to the selected cell. ...16-6
C901100005 Number of handover attempts from selected cell to the adjacent cell
due to better UL quality.............................................................................................16-7
due to better DL quality.............................................................................................16-8
C901100007 Number of handover success from selected cell to the adjacent cell
due to better UL quality...........................................................................................16-10
due to better DL quality........................................................................................... 16-11
due to better UL strength........................................................................................16-12
due to better DL strength........................................................................................16-14
due to better UL strength........................................................................................16-15
due to better DL strength........................................................................................16-16
due to PBGT ..........................................................................................................16-18
due to PBGT ..........................................................................................................16-19
due to other factors. ...............................................................................................16-20
C901100016 Number of successful handover from selected cell to the adjacent cell
due to other factors. ...............................................................................................16-21
C901100017 Number of pingpong handover (handover to source cell) ...................16-23
C901100018 The max of RTD ................................................................................16-24
C901100019 The sum of RTD ................................................................................16-25
C901100020 The number of RTD ...........................................................................16-26
16-1

16.1 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.
16.2 C901100001 Number of handover attempts on the

adjacent cell.
Definition
Number of handover attempts on the adjacent cell.
Description
This counter counts the number of attempts of handover from the selected cell to the
adjacent cell.
Usage
This counter is used to find out the number of attempts of handover from the selected cell
to the adjacent cell so as to know the handover situation.
Measurement Point
l When handover happens between cells inside one BSC, and source cell sends radio
channel request message to target cell, the counter increments. The measurement
16-2

Chapter 16 Adjacent Cell Handover Measurement
l When external handover happens inside one MSC, and source cell sends handover
request message to MSC, the counter increments. The measurement point is A, as
Unit
Times
Related Features

selected cell to the adjacent cell.
Definition
This counter counts the number of success of handover from the selected cell to the
adjacent cell.
Usage
This counter is used to find out the number of success of handover from the selected cell
to the adjacent cell so as to know the handover situation.
Measurement Point
l When handover happens between cells inside one BSC, and source cell receives
handover completion message from target cell, the counter increments. The
16-3

l When external handover happens inside one MSC, source cell receives release
command from MSC and the release is due to handover success, the counter
Unit
Times
Related Features

adjacent cell to the selected cell.
Definition
Number of handover attempts from adjacent cell to the selected cell.
16-4

Usage
This counter is used to find out the number of attempts of handover from adjacent cell to
the selected cell so as to know the handover situation.
Measurement Point
l When handover happens between cells inside one BSC, target cell receives
radio channel request message from source cell, the counter increments. The
l When external handover happens inside one MSC, and target cell receives handover
request message from MSC, the counter increments. The measurement point is A,
Unit
Times
Related Features
16-5


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.
Measurement Point
l When handover happens between cells inside one BSC, and target cell receives
handover completion message from MS, the counter increments. The measurement
completion message from MS, the counter increments. The measurement point
Unit
Times
16-6

Related Features

selected cell to the adjacent cell due to better UL
quality.
Definition
Number of handover attempts from selected cell to the adjacent cell due to better UL quality
Usage
This counter is used to find out the number of attempts of handover from a selected cell to
the adjacent cell so as to know the handover situation.
Measurement Point
radio channel request message from source cell due to better UL quality, the counter
increments. The measurement point is A, as shown inFigure 16-9.
l When external handover happens inside one MSC, target cell receives handover
request message from MSC due to better UL quality, the counter increments. The
16-7

Unit
Times
Related Features

selected cell to the adjacent cell due to better DL
quality.
Definition
Number of handover attempts from selected cell to the adjacent cell due to better DL quality
Usage
This counter is used to find out the number of attempts of handover from selected cell to
the adjacent cell so as to know the handover situation.
Measurement Point
radio channel request message from source cell due to better DL quality, the counter
16-8

request message from MSC due to better DL quality, the counter increments. The
Unit
Times
Related Features
16-9


quality.
Definition
Number of successful handover from the selected cell to the adjacent 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 as to know the handover situation.
Measurement Point
handover completion message from target cell due to better UL quality, the counter
l When external handover happens inside one MSC, and source cell receives
release command from MSC due to better UL quality, the counter increments. The
16-10

Unit
Times
Related Features

quality.
Definition
Number of handover success from selected cell to the adjacent cell due to better DL quality
Usage
the adjacent cell due to better DL quality so as to know the handover situation.
Measurement Point
handover completion message from target cell due to better DL quality, the counter
16-11

l When external handover happens inside one MSC, source cell receives release
command from MSC due to better DL quality, the counter increments. The
Unit
Times
Related Features

strength.
Definition
Number of handover attempts from selected cell to the adjacent cell due to better UL
strength.
16-12

Usage
the adjacent cell due to better UL strength so as to know the handover situation.
Measurement Point
radio channel request message from source cell due to better UL strength, the
request message from MSC due to better UL strength, the counter increments. The
measurement point is A, as shown in Figure 16-18
Unit
Times
Related Features
16-13


strength.
Definition
Number of handover attempts from selected cell to the adjacent cell due to better DL
strength.
Usage
the adjacent cell due to better DL strength so as to know the handover situation.
Measurement Point
radio channel request message from source cell due to better DL strength, the
request message from MSC due to better DL strength, the counter increments. The
16-14

Unit
Times
Related Features

strength.
Definition
Number of successful handover from selected cell to the adjacent cell due to better UL
strength
Usage
the adjacent cell due to better UL strength so as to know the handover situation.
Measurement Point
handover completion message from target cell due to better UL strength, the counter
16-15

l When external handover happens inside one MSC, and source cell receives release
command from MSC due to better UL strength, the counter increments. The
Unit
Times
Related Features

strength.
Definition
Number of successful handover from the selected cell to the adjacent cell due to better DL
strength
16-16

Usage
the adjacent cell due to better DL strength so as to know the handover situation.
Measurement Point
handover completion message from target cell due to better DL strength, the counter
command from MSC due to better UL strength, the counter increments, as shown in
Figure 16-24.
Unit
Times
Related Features
16-17


selected cell to the adjacent cell due to PBGT
Definition
Number of handover attempts from the selected cell to the adjacent cell due to better PBGT
Usage
the adjacent cell due to PBGT, so as to know the handover situation.
Measurement Point
radio channel request message from source cell due to better PBGT, the counter
request message from MSC due to better PBGT, the counter increments. The
16-18

Unit
Times
Related Features

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 to know the handover situation.
Measurement Point
handover completion message from target cell due to better PBGT, the counter
command from MSC due to better PBGT, the counter increments. The measurement
16-19

Unit
Times
Related Features

selected cell to the adjacent cell due to other
factors.
Definition
Number of handover attempts from the selected cell to the adjacent cell due to other
factors.
Usage
the adjacent cell due to other factors, so as to know the handover situation.
Measurement Point
radio channel request message from source cell due to other factors, the counter
increments, as shown in Figure 16-29.
16-20

request message from MSC due to other factors, the counter increments, as shown
in Figure 16-30.
Unit
Times
16.17 C901100016 Number of successful handover

from selected cell to the adjacent cell due to other
factors.
Definition
Number of successful handover from the selected cell to the adjacent cell due to other
factors
16-21

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 to know the handover situation.
Measurement Point
handover completion message from target cell due to other factors, the counter
increments, as shown in Figure 16-31.
command from MSC due to other factors, the counter increments, as shown in
Figure 16-32.
Unit
Times
16-22

16.18 C901100017 Number of pingpong handover

(handover to source cell)
Definition
Number of pingpong handover (handover to source cell)
Description
MS performs handover from cell 1 to cell 2, this counter counts the number of MS's
attempting handover back from cell 2 to cell 1 within specified time.
Usage
This counter is used to find out the number of MS's attempting pingpong handover due to
network coverage problems or inappropriate parameter setting.
Measurement Point
l 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
l 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
16-23

Unit
Times
16.19 C901100018 The max of RTD

Description
This counter counts the maximum reference time difference between two cells. When BSC
receives the Assign Complete message from MS, if it contains the mobile time difference
and dwRTDMa is smaller than the temporary variable dwRTD, then update dwRTDMa.
Usage
This counter is used to find out the maximum reference time difference between two cells.
Measurement Point
When BSC receives the Assign Complete message, if it contains the mobile time
difference, then the counter counts. The measurement point is A1, as shown in Figure
16-35.
16-24

Figure 16-35 Handover Flow
Unit
Second
16.20 C901100019 The sum of RTD

Description
This counter counts the sum of sampled reference time differences between two cells.
When BSC receives the Assign Complete message from MS, if it contains the mobile time
difference, then update dwRTDSum.
Usage
This counter is used to find out the sum of sampled reference time differences between
two cells.
Measurement Point
difference, then the counter counts.
16-25

Unit
Times
16.21 C901100020 The number of RTD

Description
This counter counts the number of sampled reference time differences between two cells.
difference, then the counter increments.
Usage
This counter is used to find out the number of sampled reference time differences between
two cells.
Measurement Point
difference, then the counter counts.
Unit
Times
16-26

Chapter 17
Radio Access Measurement
Table of Contents
Overview ..................................................................................................................17-1
C901110001 Number of invalid access requests.......................................................17-2
C901110003 Number of MOC access success for processes ...................................17-3
C901110006 Number of MTC access success for processes....................................17-3
C901110008 Number of call re-establishment access attempts ................................17-4
C901110009 Number of call re-establishment access success for processes ...........17-5
C901110010 Number of call re-establishment access success .................................17-5
C901110011 Number of emergency calls access attempts .......................................17-6
C901110012 Number of emergency calls access success for processes ..................17-6
C901110013 Number of emergency calls access success ........................................17-7
C901110014 Number of LOC access attempts .........................................................17-8
C901110015 Number of LOC access success for processes ....................................17-8
C901110016 Number of LOC access success ..........................................................17-9
C901110017 Number of other causes access attempts ............................................17-9
C901110018 Number of successful random access processes for other causes.....17-10
C901110019 Number of other causes access success ...........................................17-10
C901110020 Number of LMU Establishment Access attempts................................ 17-11
C901110021 Number of LMU Establishment access success for processes ...........17-12
C901110022 Number of LMU Establishment access success .................................17-12
C901110023 Number of accesses due to location update.......................................17-13
C901110024 Number of Access due to CM SERVICE REQ ...................................17-13
C901110026 Number of CM service requests of Emergency Call ...........................17-14
C901110027 Number of CM service requests of SMS ............................................17-15
C901110028 Number of CM service requests of Supplement .................................17-15
C901110029 Number of CM service requests of LCS .............................................17-16
C901110031 Number of wireless access due to call re-establishments...................17-16
C901110032 Number of wireless accesses due to IMSI detachment ......................17-17
C901110033 Number of wireless accesses due to other causes.............................17-17
17.1 Overview
Radio access counter is mainly used to observe MS radio random access process as the
reference of radio access parameter adjustment, signaling channel allocation strategy, etc.
Several possible causes of radio access are listed here. Access statistics related to GPRS
is not listed here but in the category of other access request temporarily.
17-1

The number of access request is that of receiving Channel Required message; the
number of successful access process is that of sending Immediate Assignment
message.
The slot-aloha protocol used in radio access allows many access requests in one access.
We can use the percentage of the number of successful access process to the number of
access request to describe access success rate. This value represents signaling channel
congestion extent. The percentage of the number of successful access to the number
of access request represents the collision status in radio access request. If this value is
low, we shall consider factors such as the interval between access requests, and check
whether it is reasonable.
Radio access flow and related counters locations are shown in Figure 17-1.
Figure 17-1 Radio Access Process
17.2 C901110001 Number of 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.
17-2

Chapter 17 Radio Access Measurement
Usage
This counter is used to find out the frequency of invalid access request.
Measurement Point
The counter increments when MS fails in requiring radio channel from BSC because TA
exceeds cell scope. The measurement point is A2, as shown in Figure Radio Access
Process .
Unit
Times
17.3 C901110003 Number of MOC access success for

processes
Definition
Number of MOC access success for processes
Description
This counter counts the Number of MOC access success for processes. The counter
increments when BSC allows MS to be accessed into the network due to MOC attempts
and accepts channel request sent by MS and allocates and activates channel successfully.
Meanwhile, BSC sends message IMM_ASS to MS.
Usage
This counter is used to find out the frequency of successful random access processes due
to MOC attempts.
Measurement Point
The counter increments when channel is activated successfully. The measurement point
is A3, as shown in Figure Radio Access Process .
Unit
Times
17.4 C901110006 Number of MTC access success for

processes
Definition
Number of MTC access success for processes
17-3

Description
This counter counts the Number of MTC access success for processes. The counter
increments when BSC allows MS to be accessed into the network due to MTC attempts
and accepts channel request sent by MS and allocates and activates channel successfully.
Meanwhile, BSC sends IMM_ASS message to MS.
Usage
This counter is used to find out the frequency of successful random access processes due
to MTC attempts.
Measurement Point
is A3, as shown in Figure Radio Access Process.
Unit
Times
17.5 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 attempts. The counter
increments when MS sends CHL_REQ message through BTS to BSC for requiring radio
channel, if TA does not exceed cell scope and the access cause is call re-establishment.
Usage
This counter is used to find out the frequency of random access attempts due to call
re-establishment.
Measurement Point
The counter increments when MS requires channel from BSC and TA does not exceed the
scope. The measurement point is A1, as shown in Figure Radio Access Process.
Unit
Times
17-4


access success for processes
Definition
Number of call re-establishment access success for processes
Description
This counter counts the Number of call re-establishment access success for processes.
The counter increments when BSC allows MS to be accessed into the network due to call
re-establishment and accepts channel request sent by MS and allocates and activates
channel successfully. Meanwhile, BSC sends IMM_ASS message to MS.
Usage
This counter is used to find out the frequency of random access processes due to call
re-establishment.
Measurement Point
Unit
Times

access success
Definition
Number of call re-establishment access success.
Description
This counter counts the Number of call re-establishment access success. The counter
increments when MS receives IMM_ASS message sent by BSC and successfully accesses
corresponding channel and BSC receives EST_IND message sent by MS.
Usage
This counter is used to find out the frequency of successful access of call re-establishment.
17-5

Measurement Point
The counter increments when BSC receives EST_IND message. The measurement point
Unit
Times
17.8 C901110011 Number of emergency calls access

attempts
Definition
Number of emergency calls access attempts
Description
This counter counts the Number of emergency calls access attempts. The counter
channel, if TA does not exceed cell scope and the access cause is emergency calls.
Usage
This counter is used to find out the frequency of random access attempts due to emergency
calls.
Measurement Point
Unit
Times
Related Features
ZGB-01-03-001 Emergency Call Handling

success for processes
Definition
Number of emergency calls access success for processes
17-6

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
Usage
This counter is used to find out the frequency of random access processes due to
emergency calls.
Measurement Point
Unit
Times
Related Features

success
Definition
Number of emergency calls access success
Description
This counter counts the Number of emergency calls access success. The counter
increments when MS receives IMM_ASS message sent by BSC and successfully
accesses corresponding channel and BSC receives EST_IND message sent by MS.
Usage
This counter is used to find out the frequency of successful access of emergency calls.
Measurement Point
Unit
Times
17-7

Related Features
17.11 C901110014 Number of LOC access attempts

Definition
Number of LOC access attempts
Description
This counter counts the Number of LOC access attempts. The counter increments when
MS sends CHL_REQ message through BTS to BSC for requiring radio channel, if TA does
not exceed cell scope and the access cause is LOC.
Usage
This counter is used to find out the frequency of random access attempts due to LOC.
Measurement Point
Unit
Times
17.12 C901110015 Number of LOC access success for

processes
Definition
Number of LOC access success for processes
Description
This counter counts the number of successful random access processes due to LOC.
emergency calls and accepts channel request sent by MS and allocates and activates
Usage
This counter is used to find out the frequency of random access processes due to LOC.
17-8

Measurement Point
Unit
Times
17.13 C901110016 Number of LOC access success

Definition
Number of LOC access success
Description
This counter counts the number of access success. The counter increments when MS
receives IMM_ASS message sent by BSC and successfully accesses corresponding
channel and BSC receives EST_IND message sent by MS.
Usage
This counter is used to find out the frequency of LOC access success.
Measurement Point
Unit
Times
17.14 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.
17-9

Usage
This counter is used to find out the frequency of random access attempts due to other
causes.
Measurement Point
Unit
Times
17.15 C901110018 Number of successful random

access processes for other causes
Definition
Number of successful random access processes for other causes
Description
This counter counts the number of successful random access processes for other causes.
other causes and accepts channel request sent by MS and allocates and activates channel
successfully. Meanwhile, BSC sends IMM_ASS message to MS.
Usage
This counter is used to find out the frequency of random access processes due to other
causes.
Measurement Point
Unit
Times
17.16 C901110019 Number of other causes access

success
Definition
Number of other causes access success
17-10

Description
This counter counts the Number of other causes access success. The counter increments
when MS receives IMM_ASS message sent by BSC and successfully accesses
corresponding channel and BSC receives EST_IND message sent by MS.
Usage
This counter is used to find out the frequency of other successful access requests.
Measurement Point
Unit
Times
17.17 C901110020 Number of LMU Establishment

Access attempts
Definition
Number of LMU Establishment Access attempts
Description
This counter counts the Number of LMU Establishment Access attempts. The counter
channel, if TA does not exceed cell scope and the access cause is LMU establishment.
Usage
This counter is used to find out the frequency of LMU establishment access request.
Measurement Point
Unit
Times
17-11


access success for processes
Definition
Number of LMU Establishment access success for processes
Description
This counter counts the Number of LMU Establishment access success for processes.
The counter increments when MS sends CHL_REQ message through BTS to BSC for
requiring radio channel, if TA does not exceed cell scope and the access cause is LMU
establishment.
Usage
This counter is used to find out the frequency of LMU establishment access request
successfully.
Measurement Point
Unit
Times

access success
Definition
Number of LMU Establishment access success
Description
This counter counts the Number of LMU Establishment access success. The counter
channel, if TA does not exceed cell scope and the access cause is LMU establishment.
Usage
This counter is used to find out the frequency of LMU establishment access successfully.
17-12

Measurement Point
Unit
Times
17.20 C901110023 Number of accesses due to location

update
Definition
Number of wireless accesses due to location update
Description
This counter counts the Number of wireless accesses due to location update. The counter
increments when the access cause in Layer3 information carried in EST_IND message
received by BSC is location update.
Usage
This counter is used to find out the frequency of radio channel accesses due to location
update.
Measurement Point
Unit
Times
17.21 C901110024 Number of 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 information carried in EST_IND message
received by BSC is CM SERVICE REQ.
17-13

Usage
This counter is used to find out the frequency of access caused by CM SERVICE REQ.
Measurement Point
Unit
Times

Emergency Call
Definition
Number of access of CM SERVICE REQ's emergency call
Description
This counter counts the number of access of CM SERVICE REQ's emergency call. The
counter increments when it is emergency call and the access cause in Layer3 information
carried in EST_IND message received by BSC is CM SERVICE REQ.
Usage
This counter is used to find out the frequency of access of CM SERVICE REQ's emergency
call.
Measurement Point
Unit
Times
Related Features
17-14


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

Supplement
Definition
Number of access of supplement's CM SERVICE REQ
Description
This counter counts the number of access of supplement's CM SERVICE REQ. The
counter increments when it is supplement access among other accesses and the access
cause in Layer3 information carried in EST_IND message received by BSC is CM
SERVICE REQ.
Usage
This counter is used to find out the frequency of access of supplement's CM SERVICE
REQ.
17-15

Measurement Point
Unit
Times

LCS
Definition
Number of access of LCS's CM SERVICE REQ
Description
This counter counts the number of access of supplement's CM SERVICE REQ. The
counter increments when it is LCS access among other accesses and the access cause in
Layer3 information carried in EST_IND. message received by BSC is CM SERVICE REQ.
Usage
This counter is used to find out the frequency of access of LCS's CM SERVICE REQ.
Measurement Point
Unit
Times
17.26 C901110031 Number of 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.
17-16

Usage
This counter is used to find out the frequency of radio channel accesses due to call
re-establishments.
Measurement Point
Unit
Times
17.27 C901110032 Number of wireless accesses due

to IMSI detachment
Definition
Number of wireless accesses due to IMSI detachment
Description
This counter counts the Number of wireless accesses due to IMSI detachment. The
counter increments when the access cause in Layer3 information carried in EST_IND
message received by BSC is IMSI detachment.
Usage
This counter is used to find out the frequency of radio channel accesses due to IMSI
detachment.
Measurement Point
Unit
Times
17.28 C901110033 Number of wireless accesses due

to other causes
Definition
Number of wireless accesses due to other causes
17-17

Description
This counter counts the Number of wireless accesses due to other causes (except location
update, call establishment, paging response, call re-establishment and IMSI detachment).
The counter increments when the access cause in Layer3 information carried in EST_IND
message received by BSC is other causes.
Usage
This counter is used to find out the frequency of radio channel accesses due to other
causes.
Measurement Point
Unit
Times
17-18

Chapter 18
Radio Measurement
Table of Contents
Overview ..................................................................................................................18-2
C901120001 Number of UL signal quality samples in wireless channels ..................18-2
C901120002 Level of worst UL signal quality in wireless channels ...........................18-3
C901120003 Total value of UL quality level values in wireless channels ...................18-3
C901120004 Number of DL signal quality samples in wireless channels ..................18-4
C901120005 Level of worst DL signal quality in wireless channels ...........................18-4
C901120006 Total value of DL quality strength values in wireless channels..............18-5
C901120007 Number of received UL signal strength samples in wireless channels..18-6
C901120008 Maximum received UL signal strength in wireless channels .................18-6
C901120009 Minimum received UL signal strength in wireless channels ..................18-7
C901120010 Total value of UL signal strength in wireless channels..........................18-7
C901120011 Number of received DL signal strength samples in wireless channels ..18-8
C901120012 Maximum received DL signal strength in wireless channels .................18-9
C901120013 Minimum DL received signal strength in radio channels.......................18-9
C901120014 Total value of DL signal strength in wireless channels........................18-10
C901120015 Number of TA samples in wireless channels ......................................18-10
C901120016 Maximum TA in wireless channels ..................................................... 18-11
C901120017 Total number of TAs in wireless channels .......................................... 18-11
C901120018 Mean number of idle TCH/Fs with interference band 0 ......................18-12
C901120024 Mean number of idle TCH/Hs with interference band 0 ......................18-13
C901120030 Mean number of idle SDCCHs with interference band 0 ....................18-13
C901120052 Number of TFO initiations ..................................................................18-16
C901120053 Number of using noise suppression ...................................................18-17
C901120054 Number of mode changes for establishing TFO .................................18-17
C901120055 Number of mode changes for optimizing TFO....................................18-18
C901120056 Number of active collection changes for establishing TFO .................18-18
C901120057 Number of active collection changes for optimizing TFO....................18-18
C901120058 Number of samples with voice quality is excellent..............................18-19
C901120059 Number of samples with voice quality is good....................................18-19
C901120060 Number of samples with voice quality is medium ...............................18-20
C901120061 Number of samples with voice quality is bad......................................18-20
C901120062 Number of samples with voice quality is awfully.................................18-21
18-1

C901120063 Number of uplink error frame on FR_V1 ............................................18-22

C901120064 Total Number of uplink frame on FR_V1 ............................................18-22
C901120069 Number of uplink error frame on HR_V1 ............................................18-24
C901120070 Total Number of uplink frame on HR_V1 ............................................18-24
C901120071 Number of uplink error frame on HR_V3 ............................................18-25
C901120072 Total Number of uplink frame on HR_V3 ............................................18-25
18.1 Overview
Cell radio measurement items mainly include UL/DL quality, signal strength, TA,
interference band and RQ value of radio channels. The UL/DL quality, signal strength,
TA and RQ value are counted after measurement report or pre-processing measurement
report sent by BTS is received; BSC updates interference band status in database after
receiving measurement report or pre-processing measurement report. The value of
interference band can be inquired in database when periodical measurement is reported.
18.2 C901120001 Number of UL signal quality samples

in wireless channels
Definition
Number of UL signal quality samples in radio channels
Description
This counter counts the number of received UL radio measurement report or
pre-processing measurement report. The counter increments when BSC receives UL
radio measurement report or pre-processing measurement report.
Usage
This counter is used to find out the frequency of UL signal quality samples in radio
channels.
Measurement Point
The counter increments when BSC receives UL measurement report or pre-processing
measurement report.
18-2

Chapter 18 Radio Measurement
Unit
Times
18.3 C901120002 Level of worst UL signal quality in

wireless channels
Definition
Level of worst UL signal quality in radio channels
Description
This counter counts the number of radio channels with the worst UL signal quality in UL
measurement report or pre-processing measurement report. If the level of UL signal
quality in radio channel in UL measurement report or pre-processing measurement report
received by BSC is worse than the recorded worst level of UL signal quality, then the new
worst level of UL signal quality will be recorded.
Usage
This counter is used to find out status of the level of the worst UL signal quality in radio
channels.
Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing
measurement report.
Unit
None
18.4 C901120003 Total value of UL quality level values

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

Usage
This counter is used to find out status of total value of UL quality level values in radio
channels.
Measurement Point
measurement report.
Unit
None
18.5 C901120004 Number of DL signal quality samples

Definition
Number of DL signal quality samples in radio channels
Description
This counter counts the number of received DL radio measurement report or
pre-processing measurement report. The counter increments when BSC receives DL
radio measurement report or pre-processing measurement report.
Usage
This counter is used to find out the frequency of DL signal quality samples in radio
channels.
Measurement Point
The counter increments when BSC receives DL measurement report or pre-processing
measurement report.
Unit
Times
18.6 C901120005 Level of worst DL signal quality in

wireless channels
Definition
Level of worst DL signal quality in radio channels
18-4

Description
This counter counts the number of radio channels with the worst DL signal quality in DL
measurement report or pre-processing measurement report. If the level of DL signal
quality in radio channel in DL measurement report or pre-processing measurement report
received by BSC is worse than the recorded worst level of DL signal quality, then the new
worst level of DL signal quality will be recorded.
Usage
This counter is used to find out status of the level of the worst DL signal quality in radio
channels.
Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing
measurement report.
Unit
None
18.7 C901120006 Total value of DL quality strength

values in wireless channels
Definition
Total value of DL quality level values in radio channels
Description
This counter counts the number of total value of DL quality level values in radio channels
in radio measurement reports. The counter accumulates DL quality level values in radio
channels in DL measurement report or pre-processing measurement report received by
BSC.
Usage
This counter is used to find out status of total value of DL quality level values in radio
channels.
Measurement Point
measurement report.
Unit
None
18-5

18.8 C901120007 Number of received UL signal

strength samples in wireless channels
Definition
Number of received UL signal strength samples in radio channels
Description
This counter counts the number of received UL signal strength samples in radio channels
in UL measurement report. The counter increments when BSC receives UL measurement
report or pre-processing measurement report.
Usage
This counter is used to find out frequency of received UL signal strength samples in radio
channels.
Measurement Point
The counter increments when BSC receives UL measurement report or pre-processing
measurement report.
Unit
Times
18.9 C901120008 Maximum received UL signal strength

Definition
Maximum received UL signal strength in radio channels
Description
This counter counts the maximum received UL signal strength in radio channels in UL
measurement report. If the UL signal strength in radio channel in UL measurement report
or pre-processing measurement report received by BSC is higher than the recorded
highest UL signal strength, then the new highest UL signal strength will be recorded.
Usage
This counter is used to find out status of maximum received UL signal strength in radio
channels.
18-6

Measurement Point
measurement report.
Unit
None
18.10 C901120009 Minimum received UL signal

strength in wireless channels
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 measurement report received by BSC is lower than the recorded lowest
UL signal strength, then the new lowest UL signal strength will be recorded.
Usage
This counter is used to find out status of minimum received UL signal strength in radio
channels.
Measurement Point
measurement report.
Unit
None
18.11 C901120010 Total value of UL signal strength in

wireless channels
Definition
Total value of UL signal strength in radio channels
Description
This counter counts the number of total value of UL signal strength in radio channels in
radio measurement reports. The counter accumulates values of UL signal strength in radio
18-7

channels in UL measurement report or pre-processing measurement report received by

BSC.
Usage
This counter is used to find out status of total value of UL signal strength in radio channels.
Measurement Point
measurement report.
Unit
None
18.12 C901120011 Number of received DL signal

strength samples in wireless channels
Definition
Number of received DL signal strength samples in radio channels
Description
This counter counts the number of received DL signal strength samples in radio channels
in DL measurement report. The counter increments when BSC receives DL measurement
report or pre-processing measurement report.
Usage
This counter is used to find out frequency of received DL signal strength samples in radio
channels.
Measurement Point
The counter increments when BSC receives DL measurement report or pre-processing
measurement report.
Unit
Times
18-8

18.13 C901120012 Maximum received DL signal

strength in wireless channels
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 measurement report received by BSC is higher than the recorded
highest DL signal strength, then the new highest DL signal strength will be recorded.
Usage
This counter is used to find out status of maximum received DL signal strength in radio
channels.
Measurement Point
measurement report.
Unit
None
18.14 C901120013 Minimum DL received signal

strength in radio channels
Definition
Minimum DL received signal strength in radio channels
Description
This counter counts the minimum received DL signal strength in radio channels in DL
measurement report. If the DL signal strength in radio channel in DL measurement report
or pre-processing measurement report received by BSC is lower than the recorded lowest
DL signal strength, then the new lowest DL signal strength will be recorded.
Usage
This counter is used to find out status of minimum received DL signal strength in radio
channels.
18-9

Measurement Point
measurement report.
Unit
None
18.15 C901120014 Total value 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 accumulates values of DL signal strength in radio
channels in DL measurement report or pre-processing measurement report received by
BSC.
Usage
This counter is used to find out status of total value of DL signal strength in radio channels.
Measurement Point
measurement report.
Unit
None
18.16 C901120015 Number of TA samples in wireless

channels
Definition
Number of TA samples in radio channels
Description
This counter counts the number of TA samples in radio channels in radio measurement
reports. The counter increments when BSC receives measurement report or
pre-processing measurement report.
18-10

Usage
This counter is used to find out frequency of TA samples in radio channels.
Measurement Point
The counter increments when BSC receives measurement report or pre-processing
measurement report.
Unit
Times
18.17 C901120016 Maximum TA in wireless channels

Definition
Maximum TA in radio channels
Description
This counter counts the maximum TA in radio measurement reports. If the value of TA in
radio channels in measurement report or pre-processing measurement report received by
BSC is larger than the recorded highest value of TA, then the new largest value of TA will
be recorded.
Usage
This counter is used to find out status of maximum TA in radio channels.
Measurement Point
The counter counts when BSC receives measurement report or pre-processing
measurement report.
Unit
Second
18.18 C901120017 Total number of TAs in wireless

channels
Definition
Total number of TAs in radio channels
18-11

Description
This counter counts the number of TAs in radio channels in radio measurement reports.
The counter accumulates values of TA in radio channels in measurement report or
pre-processing measurement report received by BSC.
Usage
This counter is used to find out status of total value of TA in radio channels.
Measurement Point
The counter counts when BSC receives measurement report or pre-processing
measurement report.
Unit
Second
18.19 C901120018 Mean number of idle TCH/Fs with

interference band 0
Definition
Mean number of idle TCH/Fs with interference band 0
Description
This counter counts the mean number of idle TCH/Fs with interference band 0.
Usage
This counter is used to find out number of idle TCH/Fs with interference band 0.
Measurement Point
The counter increments when timed database inquiry is carried out.
Unit
Times
Related Features
18-12

18.20 C901120024 Mean number 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 interference band 0.
Usage
This counter is used to find out number of idle TCH/Hs with interference band 0.
Measurement Point
Unit
Times
Related Features
18.21 C901120030 Mean number of idle SDCCHs with

interference band 0
Definition
Mean number of idle SDCCHs with interference band 0
Description
This counter counts the mean number of idle SDCCHs with interference band 0.
Usage
This counter is used to find out number of idle SDCCHs with interference band 0.
Measurement Point
18-13

Unit
Times
Related Features

interference band 1
Definition
Description
Usage
Measurement Point
Unit
Times
Related Features

interference band 2
Definition
Description
Usage
18-14

Measurement Point
Unit
Times
Related Features

interference band 3
Definition
Description
Usage
Measurement Point
Unit
Times
Related Features

interference band 4
Definition
Mean number of idle SDCCHs with interference band 4.
Description
18-15

Usage
Measurement Point
Unit
Times
Related Features

interference band 5
Definition
Description
Usage
Measurement Point
Unit
Times
Related Features
18.27 C901120052 Number of TFO initiations

Definition
Number of TFO initiations
18-16

Description
This counter counts the number of TFOs established by BSC.
Measurement Point
When the RANCS service process of BSC receives TFO status message and TFO has
been established, the counter increments.
Unit
Times
Related Features
ZGO-04-02-006 TFO
18.28 C901120053 Number of using noise suppression

Definition
Number of using noise suppression
Description
This counter does not count for the time being.
18.29 C901120054 Number of mode changes for

establishing TFO
Definition
Number of mode changes for establishing TFO
Description
Related Features
ZGO-04-02-006 TFO
18-17

18.30 C901120055 Number of mode changes for

optimizing TFO
Definition
Number of mode changes for optimizing TFO
Description
Related Features
ZGO-04-02-006 TFO
18.31 C901120056 Number of active collection changes

for establishing TFO
Definition
Number of active collection changes for establishing TFO
Description
Related Features
ZGO-04-02-006 TFO
18.32 C901120057 Number of active collection changes

for optimizing TFO
Definition
Number of active collection changes for optimizing TFO
Description
Related Features
ZGO-04-02-006 TFO
18-18

18.33 C901120058 Number of samples with voice

quality is excellent
Definition
Number of samples with voice quality is excellent
Description
This counter counts the number of voice quality being excellent. When the UL
measurement report, preprocessing measurement report, or enhanced preprocessing
measurement report is received, if the voice quality is excellent, the counter increments.
Usage
This counter is used to find out the UL voice quality on the radio channel.
Measurement Point
When BSCreceives the UL measurement report, preprocessing measurement report, or
enhanced preprocessing measurement report, if the voice quality is excellent, the counter
increments.
Unit
Times

quality is good
Definition
Number of samples with voice quality is good
Description
This counter counts the number of voice quality being good. When the UL measurement
report, preprocessing measurement report, or enhanced preprocessing measurement
report is received, if the voice quality is good, the counter increments.
Usage
18-19

Measurement Point
When BSC receives the UL measurement report, preprocessing measurement report, or
enhanced preprocessing measurement report, if the voice quality is good, the counter
increments.
Unit
Times

quality is medium
Definition
Number of samples with voice quality is medium
Description
This counter counts the number of voice quality being medium. When the UL
measurement report, preprocessing measurement report, or enhanced preprocessing
measurement report is received, if the voice quality is medium, the counter increments.
Usage
Measurement Point
enhanced preprocessing measurement report, if the voice quality is medium, the counter
increments.
Unit
Times

quality is bad
Definition
Number of samples with voice quality is bad
18-20

Description
This counter counts the number of voice quality being bad. When the UL measurement
report is received, if the voice quality is bad, the counter increments.
Usage
Measurement Point
When BSC receives the UL measurement report, preprocessing measurement report,
or enhanced preprocessing measurement report, if the voice quality is bad, the counter
increments.
Unit
Times

quality is awfully
Definition
Number of samples with voice quality is awfully
Description
This counter counts the number of voice quality being awful. When the UL measurement
report is received, if the voice quality is awful, the counter increments.
Usage
Measurement Point
enhanced preprocessing measurement report, if the voice quality is awful, the counter
increments.
Unit
Times
18-21

18.38 C901120063 Number of uplink error frame on

FR_V1
Description
This counter counts the number of uplink error frames of full-rate version 1.
Usage
This counter is used to find out the number of incorrect uplink voice frames of full-rate
version 1. The counter increments when uplink decoding error occurs.
Measurement Point
The counter's value is obtained from the periodic measurement report.
18.39 C901120064 Total Number of uplink frame on

FR_V1
Description
This counter counts the number of uplink frames of full-rate version 1.
Usage
This counter is used to find out the number of uplink voice frames of full-rate version 1.
The counter increments every 20 ms.
Measurement Point

FR_V2
Description
Usage
18-22

Measurement Point

FR_V2
Description
This counter counts the number of uplink voice frames of full-rate version 2.
Usage
Measurement Point

FR_V3
Description
Usage
Measurement Point

FR_V3
Description
This counter counts the number of uplink voice frames of full-rate version 3.
18-23

Usage
Measurement Point

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
Measurement Point

HR_V1
Description
This counter counts the number of uplink voice frames of half-rate version 1.
Usage
This counter is used to find out the number of uplink voice frames of half-rate version 1.
Measurement Point
18-24


HR_V3
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
Measurement Point

HR_V3
Description
This counter counts the number of uplink voice frames of half-rate version 3.
Usage
This counter is used to find out the number of uplink voice frames of half-rate version 3.
Measurement Point
18-25

18-26

Chapter 19
Sub Cell Statistics
Table of Contents
Overview ..................................................................................................................19-3
C901130001 Number of available TCH/Fs in the second sub cell .............................19-4
C901130002 Number of unavailable TCH/Fs in the second sub cell .........................19-4
C901130003 Number of available TCH/Hs in the second sub cell.............................19-5
C901130004 Number of unavailable TCH/Hs in the second sub cell.........................19-5
C901130005 Number of handover attempts from the first sub cell to the second
sub cell.....................................................................................................................19-6
C901130006 Number of handover execution from the first sub cell to the second
sub cell.....................................................................................................................19-7
C901130007 Number of handover success from the first sub cell to the second sub
cell ...........................................................................................................................19-8
C901130008 Number of handover attempts from the second sub cell to the first
sub cell.....................................................................................................................19-9
C901130009 Number of handover execution from the second sub cell to the first
sub cell...................................................................................................................19-10
C901130010 Number of handover success from the second sub cell to the first sub
cell ......................................................................................................................... 19-11
C901130011 Number of handover attempts in the second sub cell .........................19-12
C901130012 Number of handover execution in the second sub cell .......................19-13
C901130013 Number of handover success in the second sub cell..........................19-14
C901130014 Number of outgoing inter-cell handover attempts of the second sub
cell .........................................................................................................................19-15
C901130015 Number of outgoing inter-cell handover execution of the second sub
cell .........................................................................................................................19-16
C901130016 Number of outgoing inter-cell handover success of the second sub
cell .........................................................................................................................19-17
C901130017 Handover attempts due to UL receiving strength of the full rate
second sub cell ......................................................................................................19-18
C901130018 Handover attempts due to DL receiving strength of the full rate
second sub cell ......................................................................................................19-19
C901130019 Handover attempts due to UL quality of the full rate second sub cell..19-20
C901130020 Handover attempts due to DL quality of the full rate second sub cell..19-21
C901130021 Handover attempts due to PBGT of the full rate second sub cell........19-22
C901130022 Handover attempts due to traffic of the full rate second sub cell.........19-23
C901130023 Handover attempts due to UL interference of the full rate second sub
cell (on TCH/F).......................................................................................................19-24
19-1

C901130024 Handover attempts due to DL interference of the full rate second sub
cell (on TCH/F).......................................................................................................19-25
C901130025 Handover attempts due to good CI of the full rate second sub cell (on
TCH/F) ...................................................................................................................19-26
C901130026 Handover attempts due to bad CI of the full rate second sub cell (on
TCH/F) ...................................................................................................................19-27
C901130027 Handover attempts due to path loss and too large TA of the full rate
second sub cell (on TCH/F) ....................................................................................19-28
C901130028 Handover attempts due to path loss and too small TA of the full rate
second sub cell (on TCH/F) ....................................................................................19-29
C901130029 Number of forced transfer handover attempts of the full rate second
sub cell (on TCH/F) ................................................................................................19-30
C901130030 Handover attempts due to other causes of the full rate second sub
cell .........................................................................................................................19-32
C901130031 Handover attempts due to UL receiving strength of the half rate
second sub cell ......................................................................................................19-33
C901130032 Handover attempts due to DL receiving strength of the half rate
second sub cell ......................................................................................................19-34
C901130033 Handover attempts due to UL quality of the half rate second sub cell .19-35
C901130034 Handover attempts due to DL quality of the half rate second sub cell .19-36
C901130035 Handover attempts due to PBGT of the half rate second sub cell.......19-37
C901130036 Handover attempts due to traffic of the half rate second sub cell........19-38
C901130037 Handover attempts due to UL interference of the half rate second sub
cell .........................................................................................................................19-39
C901130038 Handover attempts due to DL interference of the half rate second sub
cell .........................................................................................................................19-40
C901130039 Handover attempts due to C/I of the half rate second sub cell............19-41
C901130040 Handover attempts due to C/I of the half rate second sub cell............19-42
C901130041 Handover attempts due to path loss and too large TA of the half rate
second sub cell ......................................................................................................19-43
C901130042 Handover attempts due to path loss and too small TA of the half rate
second sub cell ......................................................................................................19-44
C901130043 Number of forced transfer handover attempts of the half rate second
sub cell...................................................................................................................19-45
C901130044 Handover attempts due to other causes of the half rate second sub
cell .........................................................................................................................19-46
C901130045 Number of attempts of TCH/F seizure of the second sub cell (used for
assignment) ...........................................................................................................19-47
C901130046 Number of TCH/F seizure success of the second sub cell (used for
assignment) ...........................................................................................................19-48
C901130047 Number of TCH/F seizure failure of the second sub cell (used for
assignment) ...........................................................................................................19-49
C901130048 Number of attempts of TCH/F seizure of the second sub cell (used for
handover)...............................................................................................................19-49
19-2

Chapter 19 Sub Cell Statistics
C901130049 Number of TCH/F seizure success of the second sub cell (used for
handover)...............................................................................................................19-50
C901130050 Number of TCH/F seizure failure of the second sub cell (used for
handover)...............................................................................................................19-51
C901130051 Number of TCH/H seizure attempts of the second sub cell (used for
assignment) ...........................................................................................................19-52
C901130052 Number of TCH/H seizure success of the second sub cell (used for
assignment) ...........................................................................................................19-53
C901130053 Number of TCH/H seizure failure of the second sub cell (used for
assignment) ...........................................................................................................19-54
C901130054 Number of TCH/H seizure attempts of the second sub cell (used for
handover)...............................................................................................................19-55
C901130055 Number of TCH/H seizure success of the second sub cell (used for
handover)...............................................................................................................19-56
C901130056 Number of TCH/H seizure failure of the second sub cell (used for
handover)...............................................................................................................19-56
C901130057 Number of TCH/F call drops in the second sub cell............................19-57
C901130058 Number of TCH/H call drops in the second sub cell ...........................19-58
C901130059 TCH/F busy time in the second sub cell .............................................19-59
C901130060 TCH/H busy time in the second sub cell ............................................19-60
C901130061 Number of TCH/F assignment attempts of the second sub cell ..........19-60
C901130062 Number of TCH/F assignment success of the second sub cell...........19-61
C901130063 Number of TCH/F handover attempts of the second sub cell .............19-62
C901130064 Number of TCH/F handover success of the second sub cell ..............19-63
C901130065 Number of TCH/H assignment attempts of the second sub cell..........19-64
C901130066 Number of TCH/H assignment success of the second sub cell ..........19-64
C901130067 Number of TCH/H handover attempts of the second sub cell .............19-65
C901130068 Number of TCH/H handover success of the second sub cell..............19-66
C901130069 TCH/F of the first sub cell seizure success when prefer the second
sub cell (used for assignment)................................................................................19-67
C901130070 TCH/F of the first sub cell seizure success when prefer the second
sub cell (used for handover) ...................................................................................19-68
C901130071 TCH/H of the first sub cell seizure success when prefer the second
sub cell (used for assignment)................................................................................19-68
C901130072 TCH/H of the first sub cell seizure success when prefer the second
sub cell (used for handover) ...................................................................................19-69
19.1 Overview
Sub cell statistics counter is used to find out operation status of the sub cell in radio
environment. It focuses on inter-sub-cell handover and relevant counting at the second
sub cell so as to check traffic absorption condition by the second sub cell.
The measurement takes sub cell as the statistics unit.
19-3

19.2 C901130001 Number of available TCH/Fs in the

second sub cell
Definition
Number of available TCH/Fs in the second sub cell
Description
This counter counts the number of available TCH/F channels in the second sub cell.
Usage
This counter is used to find out the number of available TCH/F channels in the second sub
cell, to learn the traffic of the second sub cell.
Measurement Point
Call database interface to count promptly.
Unit
Times
Related Features
ZGO-05-02-009 Concentric Circle Technology
19.3 C901130002 Number of 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 channels in the second sub
Measurement Point
19-4

Unit
Times
Related Features
19.4 C901130003 Number of available TCH/Hs in the

second sub cell
Definition
Number of available TCH/Hs in the second sub cell
Description
This counter counts the number of available TCH/H channels in the second sub cell.
Usage
This counter is used to find out the number of available TCH/H channels in the second sub
Measurement Point
Unit
Times
Related Features
19.5 C901130004 Number of unavailable TCH/Hs in the

second sub cell
Definition
Number of unavailable TCH/Hs in the second sub cell
19-5

Description
This counter counts the number of unavailable TCH/H channels in the second sub cell.
Usage
This counter is used to find out the number of available TCH/H channels in the second sub
Measurement Point
Unit
Times
Related Features

the first sub cell to the second sub cell
Definition
Number of handover attempts from the first sub cell to the second sub cell
Description
This counter counts the number of intra-cell handover attempts from the first sub cell to
the second sub cell.
Usage
This counter is used to find out the frequency of intra-cell handover attempts from the first
sub cell to the second sub cell, as one of the parameters to measure radio environment.
Measurement Point
When BSC receives measurement reports from MS, it makes handover decision. If
it is decided to do intra-cell handover, and current sub cell is the first sub cell, and if
handover reason is 'too small Ta&PassLoss' or 'too large C/I', this counter increments.
The measurement point is A, as shown inFigure 19-1 .
19-6

Figure 19-1 - Intra-Cell Handover Attempt
Unit
Times
Related Features
ZGO-04-02-005 Co-BCCH
19.7 C901130006 Number of handover execution from

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 from the first sub cell to
the second sub cell.
Usage
This counter is used to find out the frequency of intra-cell handover execution from the first
Measurement Point
During inter-sub-cell handover within a cell, this counter increments when following
conditions are met:
l The channel of target sub cell is successfully activated

l Current channel is in the second sub cell
l Source channel is in the first sub cell
19-7

Figure 19-2 - Intra-Cell Incoming Handover
Unit
Times
Related Features

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 from the first sub cell to the
second sub cell.
Usage
This counter is used to find out the frequency of intra-cell handover success from the first
Measurement Point
During inter-sub-cell handover within a cell, target sub cell will receive handover completion
message, indicating that MS successfully accesses to new channel. If target channel is
in the second sub cell, and source channel is in the first sub cell, this counter increments.
The measurement point is A, as shownFigure 19-3 .
19-8

Figure 19-3 - Successful Intra-Cell Handover
Unit
Times
Related Features

the second sub cell to the first sub cell
Definition
Number of handover attempts from the second sub cell to the first sub cell
Description
This counter counts the number of intra-cell handover attempts from the second sub cell
to the first sub cell.
Usage
This counter is used to find out the frequency of intra-cell handover attempts from the
second sub cell to the first sub cell, as one of the parameters to measure radio environment.
Measurement Point
When BSC receives measurement reports from MS, it makes handover decision. If it
is decided to do intra-cell handover, and current sub cell is the second sub cell, and if
handover reason is 'too small Ta&PassLoss' or 'too large C/I', this counter increments.
19-9

Unit
Times
Related Features
19.10 C901130009 Number of handover execution from

Definition
Number of handover execution from the second sub cell to the first sub cell
Description
This counter counts the number of intra-cell handover execution from the second sub cell
Usage
This counter is used to find out the frequency of intra-cell handover execution from the
Measurement Point
conditions are met:

l Current channel is in the second sub cell
l Source channel is in the first sub cell
19-10

Unit
Times
Related Features

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 from the second sub cell
Usage
This counter is used to find out the frequency of intra-cell handover ins success from the
Measurement Point
conditions are met:
l Target sub cell receives handover completion message

l Target channel is in the first sub cell
l Source channel is in the second sub cell
19-11

Unit
Times
Related Features
19.12 C901130011 Number of handover attempts in the

second sub cell
Definition
Number of handover attempts in the second sub cell
Description
This counter counts the number of intra-cell handover attempts within the second sub cell.
Usage
This counter is used to find out the frequency of intra-cell handover attempts within the
second sub cell, as one of the parameters to measure radio environment.
Measurement Point
is decided to do intra-cell handover, and current sub cell is the second sub cell, and if
handover reason is interference handover, this counter increments. The measurement
point is A, as shown inFigure 19-7.
19-12

Unit
Times
Related Features
19.13 C901130012 Number of handover execution in

the second sub cell
Definition
Number of handover execution in the second sub cell
Description
This counter counts the number of intra-cell handover execution within the second sub cell.
Usage
This counter is used to find out the frequency of intra-cell handover execution within the
second sub cell, as one of the parameters to measure radio environment.
Measurement Point
conditions are met:

l Current channel is in the first sub cell
l Source channel is in the second sub cell
19-13

Unit
Times
Related Features
19.14 C901130013 Number of 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 within the second sub cell.
Usage
This counter is used to find out the frequency of successful handover from the second sub
cell to the second sub cell, as one of the parameters to measure radio environment.
Measurement Point
conditions are met:
l Target sub cell receives handover completion message

l Target channel is in the second sub cell
l Source channel is in the first sub cells
19-14

Unit
Times
Related Features
19.15 C901130014 Number of 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 handover attempts originated
from the second sub cell, as one of the parameters to measure radio environment.
Measurement Point
is decided to do inter-cell handover, and source cell is the second sub cell, this counter
19-15

Unit
Times
Related Features

handover 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 originated from the second
sub cell.
Usage
This counter is used to find out the frequency of inter-cell successful handover originated
Measurement Point
During inter-sub-cell handover within a cell, source instance receives the handover
completion message returned from target instance, indicating the MS has accessed to
target channel. If source sub cell is the second sub cell, this counter increments. The
19-16

Figure 19-11 - Inter-Cell Handover Execution
Unit
Times
Related Features

handover 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 originated from the second
sub cell.
Usage
This counter is used to find out the frequency of inter-cell successful handover originated
Measurement Point
During inter-sub-cell handover within a cell, source instance receives the handover
completion message returned from target instance, indicating the MS has accessed to
target channel. If source sub cell is the second sub cell, this counter increments. The
19-17

Usage
Times
Related Features
19.18 C901130017 Handover attempts due to UL

receiving strength of the full rate second sub cell
Definition
Handover attempts due to UL receiving strength of the full rate second sub cell
Description
This counter counts the number of handover attempts, caused by too low UL receiving
strength and originated from full rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by UL
receiving strength and originated from full rate channel in the second sub cell, as one of
the references for radio environment in the second sub cell.
Measurement Point
Make handover decision after BSC receives measurement reports. This counter
increments when following conditions are met:
l Decision is made
l Source sub cell is the second sub cell
l Handover is caused by UL strength
19-18

l Current channel is full rate one

The measurement point is A, as shown in .
Figure 19-13 - Handover Decision
Unit
Times
Related Features
19.19 C901130018 Handover attempts due to DL

receiving strength of the full rate second sub cell
Definition
Handover attempts due to DL receiving strength of the full rate second sub cell
Description
This counter counts the number of handover attempts, caused by too low DL receiving
strength and originated from full rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by DL
Measurement Point
l Decision is made
l Handover is caused by DL strength
19-19

Usage
Times
Related Features
19.20 C901130019 Handover attempts due to UL quality

of the full rate second sub cell
Definition
Handover attempts due to UL quality of the full rate second sub cell
Description
This counter counts the number of handover attempts, caused by too poor UL quality and
originated from full rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by UL quality
and originated from full rate channel in the second sub cell, as one of the references for
radio environment in the second sub cell.
Measurement Point
l Decision is made
l Handover is caused by UL quality
19-20

Unit
Times
Related Features
19.21 C901130020 Handover attempts due to DL quality

of the full rate second sub cell
Definition
Handover attempts due to DL quality of the full rate second sub cell
Description
This counter counts the number of handover attempts, caused by too poor DL quality and
Usage
This counter is used to find out the frequency of handover attempts, caused by DL quality
Measurement Point
l Decision is made
l Handover is caused by DL quality
19-21

Unit
Times
Related Features
19.22 C901130021 Handover attempts due to PBGT of

the full rate second sub cell
Definition
Handover attempts due to PBGT of the full rate second sub cell
Description
This counter counts the number of handover attempts, caused by PBGT and originated
from full rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by PBGT and
originated from full rate channel in the second sub cell, as one of the references for radio
environment in the second sub cell.
Measurement Point
l Decision is made
l Handover is caused by PBGT
19-22

Unit
Times
Related Features
19.23 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
Description
This counter counts the number of handover attempts, caused by traffic and originated
from full rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by traffic and
originated from full rate channel in the second sub cell, as one of the references for radio
Measurement Point
l Decision is made
l Handover is caused by traffic
l Current channel is full rate one, this counter increments
19-23

Units
Times
Related Features

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)
Description
This counter counts the number of handover attempts, caused by UL interference and
Usage
interference and originated from full rate channel in the second sub cell, as one of the
references for radio environment in the second sub cell.
Measurement Point
l Decision is made
19-24


Unit
Times
Related Features

interference of the full rate second sub cell (on
TCH/F)
Definition
Handover attempts due to DL interference of the full rate second sub cell (on TCH/F)
Description
This counter counts the number of handover attempts, caused by DL interference and
Usage
interference and originated from full rate channel in the second sub cell, as one of the
Measurement Point
l Decision is made
19-25


l Handover is caused by DL interference
Unit
Times
Related Features
19.26 C901130025 Handover attempts due to good CI

of the full rate second sub cell (on TCH/F)
Definition
Handover attempts due to good CI of the full rate second sub cell (on TCH/F)
Description
This counter counts the number of handover attempts, caused by too good C/I and
Usage
This counter is used to find out the frequency of handover attempts, caused by too good
C/I and originated from full rate channel in the second sub cell, as one of the references
for radio environment in the second sub cell.
Measurement Point
l Decision is made
19-26


l Handover is caused by too good C/I
Unit
Times
Related Features
19.27 C901130026 Handover attempts due to bad CI of

the full rate second sub cell (on TCH/F)
Definition
Handover attempts due to bad C/I of the full rate second sub cell (on TCH/F)
Description
This counter counts the number of handover attempts, caused by too bad C/I and
Usage
This counter is used to find out the frequency of handover attempts, caused by too bad
C/I and originated from full rate channel in the second sub cell, as one of the references
Measurement Point
l Decision is made
19-27


l Handover is caused by too bad C/I
Unit
Times
Related Features
19.28 C901130027 Handover attempts due to path loss

and too large TA of the full rate second sub cell
(on TCH/F)
Definition
Handover attempts due to path loss and too large GSMBSS-TA of the full rate second sub
cell (on TCH/F)
Description
This counter counts the number of handover attempts, caused by too large path loss and
TA and originated from full rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by too large
path loss and TA and originated from full rate channel in the second sub cell, as one of the
19-28

Measurement Point
l Decision is made
l Handover is caused by too large path loss and TA
Unit
Times
Related Features

and too small TA of the full rate second sub cell
(on TCH/F)
Definition
Handover attempts due to path loss and too small GSMBSS-TA of the full rate second sub
cell (on TCH/F)
Description
This counter counts the number of handover attempts, caused by too small path loss and
TA and originated from full rate channel in the second sub cell.
19-29

Usage
This counter is used to find out the frequency of handover attempts, caused by too small
path loss and TA and originated from full rate channel in the second sub cell, as one of the
Measurement Point
l Decision is made
l Handover is caused by too small path loss and TA
Unit
Times
Related Features
19.30 C901130029 Number of forced transfer handover

attempts of the full rate second sub cell (on TCH/F)
Definition
Number of forced transfer handover attempts of the full rate second sub cell (on TCH/F)
19-30

Description
This counter counts the number of handover attempts, caused by forced transfer handover
and originated from full rate channel in the second sub cell
Usage
This counter is used to find out the frequency of handover attempts, caused by forced
transfer handover and originated from full rate channel in the second sub cell, as one of
Measurement Point
l Decision is made
l Handover is caused by forced transfer
Unit
Times
Related Features
19-31

19.31 C901130030 Handover attempts due to other

causes of the full rate second sub cell
Definition
Handover attempts due to other causes of the full rate second sub cell
Description
This counter is used to find out the frequency of handover attempts, caused by other
causes and originated from full rate channel in the second sub cell, as one of the references
Usage
Measurement Point
l Decision is made
l Handover is caused by other reasons
Unit
Times
Related Features
19-32



receiving strength of the half rate second sub cell
Definition
Handover attempts due to UL receiving strength of the half rate second sub cell
Description
This counter counts the number of handover attempts, caused by too low UL receiving
strength and originated from half rate channel in the second sub cell.
Usage
Measurement Point
l Decision is made
l Handover is caused by UL strength
l Current channel is half rate one
Unit
Times
19-33

Related Features

receiving strength of the half rate second sub cell
Definition
Handover attempts due to DL receiving strength of the half rate second sub cell
Description
This counter counts the number of handover attempts, caused by too low DL receiving
strength and originated from half rate channel in the second sub cell.
Usage
receiving strength and originated from half rate channel in the second sub cell, as one of
Measurement Point
l Decision is made
l Handover is caused by DL strength
Unit
Times
19-34

Related Features
19.34 C901130033 Handover attempts due to UL quality

of the half rate second sub cell
Definition
Handover attempts due to UL quality of the half rate second sub cell
Description
This counter counts the number of handover attempts, caused by too poor UL quality and
originated from half full rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by UL quality
and originated from half rate channel in the second sub cell, as one of the references for
Measurement Point
l Decision is made
l Handover is caused by UL quality
Unit
Times
19-35

Related Features
19.35 C901130034 Handover attempts due to DL quality

of the half rate second sub cell
Definition
Handover attempts due to DL quality of the half rate second sub cell
Description
This counter counts the number of handover attempts, caused by too poor DL quality and
originated from half rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by DL quality
Measurement Point
l Decision is made
l Handover is caused by DL quality
Unit
Times
19-36

Related Features
19.36 C901130035 Handover attempts due to PBGT of

the half rate second sub cell
Definition
Handover attempts due to PBGT of the half rate second sub cell
Description
This counter counts the number of handover attempts, caused by PBGT and originated
from half rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by PBGT and
originated from half rate channel in the second sub cell, as one of the references for radio
Measurement Point
l Decision is made
l Handover is caused by PBGT
Unit
Times
19-37

Related Features
19.37 C901130036 Handover attempts due to traffic of

the half rate second sub cell
Definition
Handover attempts due to traffic of the half rate second sub cell
Description
This counter counts the number of handover attempts, caused by traffic and originated
from half rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by traffic and
originated from half rate channel in the second sub cell, as one of the references for radio
Measurement Point
l Decision is made
Unit
Times
19-38

Related Features

interference of the half rate second sub cell
Definition
Handover attempts due to UL interference of the half rate second sub cell
Description
This counter counts the number of handover attempts, caused by UL interference and
Usage
interference and originated from half rate channel in the second sub cell, as one of the
Measurement Point
l Decision is made
l Handover is caused by UL interference
19-39

Unit
Times
Related Features

interference of the half rate second sub cell
Definition
Handover attempts due to DL interference of the half rate second sub cell (on TCH/F)
Description
This counter counts the number of handover attempts, caused by DL interference and
Usage
interference and originated from half rate channel in the second sub cell, as one of the
Measurement Point
l Decision is made
l Handover is caused by DL interference
19-40

Unit
Times
Related Features
19.40 C901130039 Handover attempts due to C/I of the

half rate second sub cell
Definition
Handover attempts due to C/I of the half rate second sub cell
Description
This counter counts the number of handover attempts, caused by too good C/I and
Usage
This counter is used to find out the frequency of handover attempts, caused by too good
C/I and originated from half rate channel in the second sub cell, as one of the references
Measurement Point
l Decision is made
l Handover is caused by too good C/I
The measurement point is A, as shown in Figure 19-35
19-41

Unit
Times
Related Features
19.41 C901130040 Handover attempts due to C/I of the

half rate second sub cell
Definition
Handover attempts due to C/I of the half rate second sub cell
Description
This counter counts the number of handover attempts, caused by too bad C/I and
Usage
This counter is used to find out the frequency of handover attempts, caused by too bad C/I
and originated from half rate channel in the second sub cell, as one of the references for
Measurement Point
l Decision is made
l Handover is caused by too bad C/I
19-42

Unit
Times
Related Features

and too large TA of the half rate second sub cell
Definition
Handover attempts due to path loss and too large GSMBSS-TA of the half rate second sub
cell
Description
This counter counts the number of handover attempts, caused by too large path loss and
TA and originated from half rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by too large
path loss and TA and originated from half rate channel in the second sub cell, as one of
Measurement Point
l Decision is made
l Handover is caused by too large path loss and TA
19-43

Unit
Times
Related Features

and too small TA of the half rate second sub cell
Definition
Handover attempts due to path loss and too small GSMBSS-TA of the half rate second
sub cell (on TCH/F)
Description
This counter counts the number of handover attempts, caused by too small path loss and
TA and originated from half rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by too small
path loss and TA and originated from half rate channel in the second sub cell, as one of
Measurement Point
l Decision is made
l Handover is caused by too small path loss and TA
19-44

Unit
Times
Related Features
19.44 C901130043 Number of forced transfer handover

attempts of the half rate second sub cell
Definition
Number of forced transfer handover attempts of the half rate second sub cell (on TCH/F)
Description
This counter counts the number of handover attempts, caused by forced transfer handover
and originated from half rate channel in the second sub cell.
Usage
This counter is used to find out the frequency of handover attempts, caused by forced
transfer handover and originated from half rate channel in the second sub cell, as one of
Measurement Point
l Decision is made
l Handover is caused by forced transfer
19-45

Unit
Times
Related Features
19.45 C901130044 Handover attempts due to other

causes of the half rate second sub cell
Definition
Handover attempts due to other causes of the half rate second sub cell
Description
This counter counts the number of handover attempts, caused by other causes and
Usage
This counter is used to find out the frequency of handover attempts, caused by other
causes and originated from half rate channel in the second sub cell, as one of the
Measurement Point
l Decision is made
l Handover is caused by other reasons
19-46

Unit
Times
Related Features
19.46 C901130045 Number of attempts of TCH/F seizure

of the second sub cell (used for assignment)
Definition
Number of attempts of TCH/F seizure of the second sub cell (used for assignment).
Description
This counter counts the number of seizure attempts in TCH/F channel in the second sub
cell.
Usage
This counter is used to find out the frequency of seizure attempts in TCH/F channel in the
second sub cell, as one of the references for radio environment in the second sub cell.
Measurement Point
Measurement points of this counter include two types.
l 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 channel conversion
l 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
19-47

Unit
Times
Related Features
19.47 C901130046 Number of TCH/F seizure success

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 in TCH/F channel in
the second sub cell, as one of the references for radio environment in the second sub cell.
Measurement Point
This counter increments when following conditions are met:
l Successfully applying for channel

l Channel type is TCH/F
l Application reason is assignment
Successful application includes: successful resource application; resource acquisition by

queuing, seizure, or dynamic channel conversion.
Unit
Times
Related Features
19-48

19.48 C901130047 Number of 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 in the second sub cell.
Usage
This counter is used to find out the frequency of seizure failure in TCH/F channel in the
Measurement Point
When channel application is failed, if channel type is TCH/F, and application reason is
l Receive release command while waiting for resource state
l Failed to configure instance number while seizing channel
l Timeout while queuing or seizure, or waiting for resource timer
l No available radio resource
Unit
Times
Related Features
19.49 C901130048 Number of attempts of TCH/F

seizure of the second sub cell (used for handover)
Description
This counter counts the number of seizure attempts in TCH/F channel in the second sub
cell.
19-49

Usage
This counter is used to find out the frequency of seizure attempts in TCH/F channel in the
Measurement Point
Measurement points of this counter include two types.
l When channel is successfully applied, if channel type is TCH/F, and application

reason is handover, this counter increments. Successful application includes:
successful resource application; resource acquisition by queuing, seizure, or
dynamic channel conversion.
l When channel application is failed, if channel type is TCH/F, and application reason
is handover, 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
Related Features
19.50 C901130049 Number of TCH/F seizure success

of the second sub cell (used for 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 channel in the second sub
cell.
19-50

Usage
This counter is used to find out the frequency of successful seizure in TCH/F channel in
Measurement Point
This counter increments when following conditions are met:
l Channel is successfully applied
l Channel type is TCH/F
l Application reason is handover
Unit
Times
Related Features
19.51 C901130050 Number of TCH/F seizure failure of

the second sub cell (used for handover)
Definition
Number of TCH/F seizure failure of the second sub cell (used for handover)
Description
Usage
This counter is used to find out the frequency of seizure failure in TCH/F channel in the
Measurement Point
When channel application is failed, if channel type is TCH/F, and application reason is
handover, this counter increments. Failure reasons of application channel include:
19-51


Unit
Times
Related Features
19.52 C901130051 Number of TCH/H seizure attempts

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 channel in the second sub
cell.
Usage
This counter is used to find out the frequency of seizure attempts in TCH/H channel in the
Measurement Point
Measurement points of this counter include two types:
l When channel is successfully applied, if channel type is TCH/H, and application
reason is assignment, this counter increments. Successful application includes:
l When channel application is failed, if channel type is TCH/H, and application reason
is assignment, this counter increments. Failure reasons of application channel
include:
19-52


Unit
Times
Related Features
19.53 C901130052 Number of TCH/H seizure success

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 channel in the second sub
cell.
Usage
This counter is used to find out the frequency of successful seizure in TCH/H channel in
Measurement Point
When successfully applying for channel, if channel type is TCH/H, and application reason
is assignment, this counter increments. Successful application includes: successful
resource application; resource acquisition by queuing, seizure, or dynamic channel
conversion.
Unit
Times
Related Features
19-53


19.54 C901130053 Number of TCH/H seizure failure of

the second sub cell (used for assignment)
Definition
Number of TCH/H seizure failure of the second sub cell (used for assignment)
Description
Usage
This counter is used to find out the frequency of seizure failure in TCH/H channel in the
Measurement Point
When channel application is failed, if channel type is TCH/H, and application reason is
Unit
Times
Related Features
19-54

19.55 C901130054 Number of TCH/H seizure attempts

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 channel in the second sub
cell.
Usage
This counter is used to find out the frequency of seizure attempts in TCH/H channel in the
Measurement Point
Measurement points of this counter include two types:
l When channel is successfully applied, if channel type is TCH/H, and application
reason is handover, this counter increments. Successful application includes:
l When channel application is failed, if channel type is TCH/H, and application reason
is handover, this counter increments. Failure reasons of application channel include:
Unit
Times
Related Features
19-55

19.56 C901130055 Number of TCH/H seizure success

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 channel in the second sub
cell.
Usage
This counter is used to find out the frequency of successful seizure in TCH/H channel in
Measurement Point
When channel is successfully applied, if channel type is TCH/H, and application reason is
handover, this counter increments. Successful application includes: successful resource
application; resource acquisition by queuing, seizure, or dynamic channel conversion.
Unit
Times
Related Features
19.57 C901130056 Number of TCH/H seizure failure of

the second sub cell (used for 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 in the second sub cell.
19-56

Usage
This counter is used to find out the frequency of seizure failure in TCH/H channel in the
Measurement Point
When channel application is failed, if channel type is TCH/H and application reason is
handover, this counter increments. Failure reasons of application channel include:
Unit
Times
Related Features
19.58 C901130057 Number of 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 the second sub cell.
Usage
This counter is used to find out the frequency of call drops in TCH/F channel in the second
sub cell, as one of the references for radio environment in the second sub cell.
Measurement Point
During call drops, if current channel is TCH/F, this counter increments. Call drops include
following cases:
19-57

l After handover and deliver assignment command in cell, call drops occur due to
3107 timer timeout
l After inter-cell handover delivers handover command, call drops occur due to 3103
timer timeout
l After handover and deliver external handover command, call drops occur due to
outgoing protection timer timeout
l BSC receives radio link failure message
Unit
Times
Related Features
19.59 C901130058 Number of 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 the second sub cell.
Usage
This counter is used to find out the frequency of call drops in TCH/H channel in the second
sub cell, as one of the references for radio environment in the second sub cell.
Measurement Point
During call drops, if current channel is TCH/H, this counter increments. Call drops include
following cases:
l After handover and deliver assignment command in cell, call drops occur due to
3107 timer timeout
l After inter-cell handover delivers handover command, call drops occur due to 3103
timer timeout
l After handover and deliver external handover command, call drops occur due to
outgoing protection timer timeout
l BSC receives radio link failure message
19-58

Unit
Times
Related Features
19.60 C901130059 TCH/F busy time in the second sub

cell
Definition
TCH/F busy time in the second sub cell
Description
This counter counts the seizure time in TCH/F channel in the second sub cell.
Usage
This counter is used to find out the seizure time in TCH/F channel in the second sub cell,
as one of the references for traffic condition in the second sub cell.
Measurement Point
This counter will count at following two cases:
l 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.
l When promptly report measurement data.
Unit
Times
Related Features
19-59

19.61 C901130060 TCH/H busy time in the second sub

cell
Definition
TCH/H busy time in the second sub cell
Description
This counter counts the seizure time in TCH/H channel in the second sub cell.
Usage
This counter is used to find out the seizure time in TCH/H channel in the second sub cell,
as one of the references for traffic condition in the second sub cell.
Measurement Point
This counter will count at following two cases:
l 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.
l When promptly report measurement data.
Unit
Times
Related Features
19.62 C901130061 Number of TCH/F assignment

attempts of the second sub cell
Description
This counter counts the number of attempts of TCH/F assignment for the second sub
cell. When BSC receives the release command, the Um interface assignment completion
message or handover completion message, or the message of waiting for MS access being
19-60

timeout, if the sub cell ID is 2, the channel is full-rate channel, and the channel request is
due to assignment, then the counter increments.
Usage
This counter is used to find out the number of attempts of TCH/F assignment for the second
sub cell. It helps study the access condition of the second sub cell.
This counter is supported in version V6.20.200f or above.
Measurement Point
1. When BSC receives the release command in the WaitAccess status, if the sub cell ID
is 2, the channel is full-rate channel, and the channel request is due to assignment,
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 WaitAccess status, if the
sub cell ID is 2, the channel is full-rate channel, and the channel request is due to
Unit
Times

success of the second sub cell
Description
This counter counts the number of successful TCH/F assignments for the second sub
timeout, if the sub cell ID is 2, the channel is full-rate channel, and the channel request is
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.
19-61

Measurement Point
2. When the handover completion message is processed in the WaitAccess status, if the
sub cell ID is 2, the channel is full-rate channel, and the channel request is due to
Unit
Times

of the second sub cell
Description
This counter counts the number of attempts of TCH/F handover of the second sub cell.
In the WaitAccess status, when BSC receives the release command, the Um interface
assignment completion message or handover completion message, or the message of
waiting for MS access being timeout, if the sub cell ID is 2, the channel is full-rate channel,
and the channel request is due to intra-cell handover, inter-cell handover, external incoming
handover, or internal directed retry, then the counter increments.
Usage
This counter is used to find out the number of attempts of TCH/F handover of the second
Measurement Point
1. When BSC receives the release command in the WaitAccess status, if the sub cell
ID is 2, the channel is full-rate channel, and the channel request is due to intra-cell
handover, inter-cell handover, external incoming handover, or internal directed retry,
channel request is due to intra-cell handover, inter-cell handover, external incoming
handover, or internal directed retry, 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 intra-cell handover, inter-cell handover, external incoming handover, or internal
directed retry, then the counter counts.
19-62

4. When BSC receives the TWaitMSAccessOut 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 intra-cell handover, inter-cell handover, external incoming handover, or internal
Unit
Times
19.65 C901130064 Number of TCH/F handover success

Description
This counter counts the number of successful TCH/F handovers of the second sub cell.
When BSC receives the release command, the Um interface assignment completion
message or handover completion message, or the message of waiting for MS access
being timeout, if the sub cell ID is 2, the channel is full-rate channel, and the channel
request is due to intra-cell handover, inter-cell handover, external incoming handover, or
internal directed retry, then the counter increments.
Usage
This counter is used to find out the number of successful TCH/F handovers of the second
Measurement Point
2. When the handover completion message is processed in the WaitAccess status, if
the sub cell ID is 2, the channel is full-rate channel, and the channel request is due
Unit
Times
19-63

19.66 C901130065 Number of TCH/H assignment

attempts of the second sub cell
Description
This counter counts the number of attempts of TCH/H assignment for the second sub
timeout, if the sub cell ID is 2, the channel is half-rate channel, and the channel request is
Usage
This counter is used to find out the number of attempts of TCH/H assignment for the second
Measurement Point
1. When BSC receives the release command in the WaitAccess status, if the sub cell ID
is 2, the channel is half-rate channel, and the channel request is due to assignment,
WaitAccess status, if the sub cell ID is 2, the channel is half-rate channel, and the
3. When BSC receives the handover completion message in the WaitAccess status, if
the sub cell ID is 2, the channel is half-rate channel, and the channel request is due
to assignment, then the counter counts.
4. When BSC receives the TWaitMSAccessOut message in the WaitAccess status, if the
sub cell ID is 2, the channel is half-rate channel, and the channel request is due to
Unit
Times

success of the second sub cell
Description
This counter counts the number of successful TCH/H assignments for the second sub
19-64

timeout, if the sub cell ID is 2, the channel is half-rate channel, and the channel request is
Usage
This counter is used to find out the number of successful TCH/H assignments for the
second sub cell. It helps study the access condition of the second sub cell.
Measurement Point
2. When the handover completion message is processed in the WaitAccess status, if the
sub cell ID is 2, the channel is half-rate channel, and the channel request is due to
Unit
Times

Description
This counter counts the number of attempts of TCH/H handover of the second sub cell.
In the WaitAccess status, when BSC receives the release command, the Um interface
assignment completion message or handover completion message, or the message of
waiting for MS access being timeout, if the sub cell ID is 2, the channel is half-rate channel,
and the channel request is due to intra-cell handover, inter-cell handover, external incoming
handover, or internal directed retry, then the counter increments.
Usage
This counter is used to find out the number of attempts of TCH/H handover of the second
Measurement Point
1. When BSC receives the release command in the WaitAccess 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,
19-65


3. When BSC receives the handover completion message in the WaitAccess 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
4. When BSC receives the TWaitMSAccessOut message in the WaitAccess status, if
Unit
Times
19.69 C901130068 Number of TCH/H handover success

Description
This counter counts the number of successful TCH/H handovers of the second sub cell.
When BSC receives the release command, the Um interface assignment completion
message or handover completion message, or the message of waiting for MS access
being timeout, if the sub cell ID is 2, the channel is half-rate channel, and the channel
request is due to intra-cell handover, inter-cell handover, external incoming handover, or
internal directed retry, then the counter increments.
Usage
This counter is used to find out the number of successful TCH/H handovers of the second
Measurement Point
2. When the handover completion message is processed in the WaitAccess status, if

19-66


Unit
Times
19.70 C901130069 TCH/F of the first sub cell seizure

success when prefer the second sub cell (used for
assignment)
Description
This counter counts the number of assigning TCH/F to the first sub cell when the second
sub cell has higher priority (used for assignment). When BSC requests radio resource
from DBS, if the request succeeds and the following conditions are satisfied, the counter
increments: the sub cell selection mode is the second cell being preferred, the sub cell ID
is 1, the channel is full-rate channel, and the channel request is due to assignment.
Usage
This counter is used to find out the number of assigning TCH/F to the first sub cell when
the second sub cell has higher priority (used for assignment). It helps study the access
condition of the first sub cell when the second sub cell has higher priority.
Measurement Point
In the RadioApply status, when BSC requests radio resource from DBS, if the request
succeeds and the following conditions are satisfied, the counter counts: the sub cell
selection mode is the second cell being preferred, the sub cell ID is 1, the channel is
full-rate channel, and the channel request is due to assignment.
Unit
Times
19-67

19.71 C901130070 TCH/F of the first sub cell seizure

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
is 1, the channel is full-rate channel, and the channel request is due to handover.
Usage
This counter is used to find out the number of assigning TCH/F to the first sub cell when the
second sub cell has higher priority (used for handover). It helps study the access condition
of the first sub cell when the second sub cell has higher priority.
Measurement Point
full-rate channel, and the channel request is due to handover.
Unit
Times
19.72 C901130071 TCH/H of the first sub cell seizure

assignment)
Description
This counter counts the number of assigning TCH/H to the first sub cell when the second
sub cell has higher priority (used for assignment). When BSC requests radio resource
is 1, the channel is half-rate channel, and the channel request is due to assignment.
19-68

Usage
This counter is used to find out the number of assigning TCH/H to the first sub cell when
the second sub cell has higher priority (used for assignment). It helps study the access
condition of the first sub cell when the second sub cell has higher priority.
Measurement Point
half-rate channel, and the channel request is due to assignment.
Unit
Times
19.73 C901130072 TCH/H of the first sub cell seizure

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
is 1, the channel is half-rate channel, and the channel request is due to handover.
Usage
This counter is used to find out the number of assigning TCH/H to the first sub cell when the
second sub cell has higher priority (used for handover). It helps study the access condition
of the first sub cell when the second sub cell has higher priority.
Measurement Point
half-rate channel, and the channel request is due to handover.
19-69

Unit
Times
19-70

Chapter 20
MS TA Measurement
Table of Contents
Overview ..................................................................................................................20-2
C901140001 Number of TA=0 ..................................................................................20-2
C901140002 Number of 0<TA<= 2 ...........................................................................20-2
C901140003 Number of 2<TA<=4 ............................................................................20-3
C901140004 Number of 4<TA<=6 ............................................................................20-4
C901140005 Number of 6<TA<=8 ............................................................................20-5
C901140006 Number of 8<TA<=10 ..........................................................................20-5
C901140007 Number of 10<TA<=12 ........................................................................20-6
C901140008 Number of 12<TA<=14 ........................................................................20-7
C901140009 Number of 14<TA<=16 ........................................................................20-7
C901140010 Number of 16<TA<=18 ........................................................................20-8
C901140011 Number of 18<TA<=20.........................................................................20-9
C901140012 Number of 20<TA<=22 ........................................................................20-9
C901060013 Number of 22<TA<=24 ......................................................................20-10
C901140014 Number of 24<TA<=26 ...................................................................... 20-11
C901140015 Number of 26<TA<=28 ......................................................................20-12
C901140016 Number of 28<TA<=30 ......................................................................20-12
C901140017 Number of 30<TA<=32 ......................................................................20-13
C901140018 Number of 32<TA<=34 ......................................................................20-14
C901140019 Number of 34<TA<=36 ......................................................................20-14
C901140020 Number of 36<TA<=38 ......................................................................20-15
C901140021 Number of 38<TA<=40 ......................................................................20-16
C901140022 Number of 40<TA<=42 ......................................................................20-17
C901140023 Number of 42<TA<=44 ......................................................................20-17
C901140024 Number 44<TA<=46 ..........................................................................20-18
C901140025 Number of 46<TA<=48 ......................................................................20-19
C901140026 Number of 48<TA<=50 ......................................................................20-19
C901140027 Number of 50<TA<=52 ......................................................................20-20
C901140028 Number of 52<TA<=54 ......................................................................20-21
C901140029 Number of 54<TA<=56 ......................................................................20-22
C901140030 Number of 56<TA<=58 ......................................................................20-22
C901140031 Number of 58<TA<=60 ......................................................................20-23
C901140032 Number of 60<TA<=63 ......................................................................20-24
C901140033 Number of TA>63 ..............................................................................20-24
20-1

20.1 Overview
MS TA counters are used to check the value of TA in MS measurement reports. TA can
reflect the relative location of MS in the cell. If most of the TAs are in very high level,
network planning should be remade, such as, increasing the site density.
20.2 C901140001 Number of TA=0

Description
This counter counts the number of times of TA=0 in the MS measurement reports.
Usage
This counter is used to find out the frequency of TA=0 in the MS measurement reports. It
can be one of the parameters that are used to evaluate the cell radio environment.
Measurement Point
This counter increments when BSC receives the MS measurement report with TA=0. The
Figure 20-1 MS Measurement Report
Unit
Times
20.3 C901140002 Number of 0<TA<= 2

Definition
Number of 0<TA<= 2
Description
This counter counts the number of times of 0<TA<=2.
20-2

Chapter 20 MS TA Measurement
Usage
This counter is used to find out the frequency of 0<TA<=2 in the MS measurement reports.
It can be one of the parameters that are used to evaluate the cell radio environment.
Measurement Point
This counter increments when BSC receives the MS measurement report with 0<TA<=2.
Unit
Times
20.4 C901140003 Number of 2<TA<=4

Definition
Number of 2<TA<=4.
Description
This counter counts the number of times of 2<TA<=4 in the MS measurement reports.
Usage
Measurement Point
20-3

Figure 20-3 - MS Measurement Report
Unit
Times
20.5 C901140004 Number of 4<TA<=6

Definition
Number of 4<TA<=6.
Description
Usage
Measurement Point
Unit
Times
20-4

20.6 C901140005 Number of 6<TA<=8

Definition
Number of 6<TA<=8.
Description
Usage
Measurement Point
Unit
Times
20.7 C901140006 Number of 8<TA<=10

Definition
Number of 8<TA<=10.
Description
Usage
20-5

Measurement Point
Unit
Times
20.8 C901140007 Number of 10<TA<=12

Definition
Number of 10<TA<=12.
Description
Usage
This counter is used to find out the frequency of 10<TA<=12 in the MS measurement
reports. It can be one of the parameters that are used to evaluate the cell radio
environment.
Measurement Point
20-6

Unit
Times
20.9 C901140008 Number of 12<TA<=14

Description
Usage
environment.
Measurement Point
Unit
Times
20.10 C901140009 Number of 14<TA<=16

Description
Usage
environment.
20-7

Measurement Point
Unit
Times
20.11 C901140010 Number of 16<TA<=18

Definition
Description
Usage
environment.
Measurement Point
20-8

Unit
Times
20.12 C901140011 Number of 18<TA<=20

Definition
Description
Usage
environment.
Measurement Point
Unit
Times
20.13 C901140012 Number of 20<TA<=22

Definition
Description
20-9

Usage
environment.
Measurement Point
Unit
Times
20.14 C901060013 Number of 22<TA<=24

Definition
Description
Usage
environment.
Measurement Point
20-10

Unit
Times
20.15 C901140014 Number of 24<TA<=26

Definition
Description
Usage
environment.
Measurement Point
Unit
Times
20-11

20.16 C901140015 Number of 26<TA<=28

Definition
Description
Usage
environment.
Measurement Point
Unit
Times
20.17 C901140016 Number of 28<TA<=30

Definition
Description
Usage
environment.
20-12

Measurement Point
Unit
Times
20.18 C901140017 Number of 30<TA<=32

Definition
Description
Usage
environment.
Measurement Point
20-13

Unit
Times
20.19 C901140018 Number of 32<TA<=34

Definition
Description
Usage
environment.
Measurement Point
Unit
Times
20.20 C901140019 Number of 34<TA<=36

Definition
Description
20-14

Usage
environment.
Measurement Point
Unit
Times
20.21 C901140020 Number of 36<TA<=38

Definition
Description
Usage
environment.
Measurement Point
20-15

Unit
Times
20.22 C901140021 Number of 38<TA<=40

Definition
Number of 38<TA<=40
Description
Usage
environment.
Measurement Point
Unit
Times
20-16

20.23 C901140022 Number of 40<TA<=42

Definition
Description
Usage
environment.
Measurement Point
Unit
Times
20.24 C901140023 Number of 42<TA<=44

Definition
Description
Usage
environment.
20-17

Measurement Point
Unit
Times
20.25 C901140024 Number 44<TA<=46

Definition
Description
Usage
environment.
Measurement Point
20-18

Unit
Times
20.26 C901140025 Number of 46<TA<=48

Definition
Description
Usage
environment.
Measurement Point
Unit
Times
20.27 C901140026 Number of 48<TA<=50

Definition
Description
20-19

Usage
environment.
Measurement Point
Unit
Times
20.28 C901140027 Number of 50<TA<=52

Definition
Description
Usage
environment.
Measurement Point
20-20

Unit
Times
20.29 C901140028 Number of 52<TA<=54

Definition
Description
Usage
environment.
Measurement Point
Unit
Times
20-21

20.30 C901140029 Number of 54<TA<=56

Definition
Description
Usage
environment.
Measurement Point
Unit
Times
20.31 C901140030 Number of 56<TA<=58

Definition
Description
Usage
environment.
20-22

Measurement Point
Unit
Times
20.32 C901140031 Number of 58<TA<=60

Definition
Number of 58<TA<=60
Description
Usage
environment.
Measurement Point
20-23

Unit
Times
20.33 C901140032 Number of 60<TA<=63

Definition
Description
Usage
environment.
Measurement Point
Unit
Times
20.34 C901140033 Number of TA>63

Definition
Number of TA > 63
Description
This counter counts the number of times of TA>63 in the MS measurement reports.
20-24

Usage
This counter is used to find out the frequency of TA>63 in the MS measurement reports.
Measurement Point
This counter increments when BSC receives the MS measurement report with TA>63. The
Unit
Times
20-25

20-26

Chapter 21
SAPI3 Measurement
Table of Contents
Overview ..................................................................................................................21-2
C901150001 Number of SAPI3 link establishments on SACCH/F (MO-SM) .............21-2
C901150002 Number of SAPI3 link establishments on SACCH/H (MO-SM) .............21-3
C901150004 Number of SAPI3 link establishments on FACCH/F (MO-SM)..............21-4
C901150005 Number of SAPI3 link establishments on FACCH/H (MO-SM) .............21-5
C901150006 Number of SAPI3 link establishment requests on SACCH/F (MT-SM)..21-6
C901150007 Number of SAPI3 link establishment requests on SACCH/H (MT-SM) .21-7
C901150009 Number of SAPI3 link establishment requests on FACCH/F (MT-SM) ..21-8
C901150010 Number of SAPI3 link establishment requests on FACCH/H (MT-SM)..21-9
C901150011 Number of successful SAPI3 link establishments on SACCH/F
(MT-SM) ...................................................................................................................21-9
C901150012 Number of successful SAPI3 link establishments on SACCH/H
(MT-SM) ................................................................................................................. 21-11
C901150014 Number of successful SAPI3 link establishments on FACCH/F
(MT-SM) .................................................................................................................21-12
C901150015 Number of successful SAPI3 link establishments on FACCH/H
(MT-SM) .................................................................................................................21-12
C901150016 Number of DTAP messages used as SDCCH UL point-to-point short
messages (SMs) ....................................................................................................21-13
C901150017 Number of DTAP messages used as SDCCH DL point-to-point short
messages (SMs) ....................................................................................................21-15
C901150018 Number of DTAP messages on FACCH/F UL for point-to-point short
messages...............................................................................................................21-17
C901150019 Number of DTAP messages on FACCH/F DL for point-to-point short
messages...............................................................................................................21-18
C901150020 Number of DTAP messages on FACCH/H UL for point-to-point short
messages...............................................................................................................21-19
C901150021 Number of DTAP messages on FACCH/H DL for point-to-point short
messages...............................................................................................................21-19
C901150022 Number of DTAP messages on SACCH/F DL for point-to-point short
messages...............................................................................................................21-20
C901150023 Number of DTAP messages on SACCH/F DL for point-to-point short
messages...............................................................................................................21-22
C901150024 Number of DTAP messages on SACCH/H UL for point-to-point short
messages...............................................................................................................21-22
C901150025 Number of DTAP messages on SACCH/H DL for point-to-point short
messages...............................................................................................................21-24
21-1

21.1 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.
21.2 C901150001 Number of SAPI3 link establishments

on SACCH/F (MO-SM)
Definition
Number of SAPI3 link establishments on SACCH/F (MO-SM)
Description
This counter counts the number of short message link establishment of mobile originating
call through SACCH/F. On SDCCH/F, BSC receives EST_IND message sent by BTS. If
the layer 3 information in this message is SAPI=3, the counter increments.
Usage
This counter is used to find out the frequency of SAPI3 link establishments on SACCH/F.
Measurement Point
This counter counts the number of BSC receiving EST_IND message sent by BTS with
SAPI=3. The measurement point is A, as shown inFigure 21-1.
21-2

Chapter 21 SAPI3 Measurement
Figure 21-1 - Flow of MO Short Messages during Conversation
Unit
Times
Related Features

on SACCH/H (MO-SM)
Definition
Number of SAPI3 link establishments on SACCH/H (MO-SM)
Description
call through SACCH/H. On SDCCH/H, BSC receives EST_IND message sent by BTS. If
21-3

Usage
This counter is used to find out the frequency of SAPI3 link establishments on SACCH/H.
Measurement Point
This counter counts the number of BSC receiving EST_IND message sent by BTS with
SAPI=3. The measurement point is A1, as shown in Figure 21-2.
Unit
Times
Related Features

on FACCH/F (MO-SM)
Definition
Number of SAPI3 link establishments on FACCH/F (MO-SM)
21-4

Description
call through FACCH/F. On FACCH/F, BSC receives EST_IND message sent by BTS. If the
layer 3 information in this message is SAPI=3, the counter increments.
Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/F.
Measurement Point
This counter is not realized at present in the system.
Unit
Times
Related Features

on FACCH/H (MO-SM)
Definition
Number of SAPI3 link establishments on FACCH/H (MO-SM)
Description
call through FACCH/H. On FACCH/H, BSC receives EST_IND message sent by BTS. If
Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/H.
Measurement Point
Unit
Times
Related Features
21-5


requests on SACCH/F (MT-SM)
Definition
Number of SAPI3 link establishments on SACCH/F (MT-SM)
Description
call through SACCH/F. On SDCCH/F, if BSC receives DTAP_IND message sent by MSC
with SAPI=3 while the short message link between BSC and MS is not established, BSC
initiates link establishment flow and the counter increments.
Usage
This counter is used to find out the frequency of SAPI3 link establishment requests on
SACCH/F.
Measurement Point
This counter counts the number of BSC sending EST_REQ message to BTS with SAPI=3
while the short message link between BSC and MS is not established. The measurement
point is C1, as shown in Figure 21-3.
Figure 21-3 - Flow of MT Short Message during Conversation
21-6

Unit
Times
Related Features

requests on SACCH/H (MT-SM)
Definition
Number of SAPI3 link establishments on SACCH/H (MT-SM)
Description
call through SACCH/H. On SACCH/H, if BSC receives DTAP_IND message sent by MSC
Usage
SACCH/H.
Measurement Point
This counter counts the number of BSC sending EST_REQ message to BTS with SAPI=3
while the short message link between BSC and MS is not established. The measurement
point is C1, as shown in Figure 21-4.
21-7

Unit
Times
Related Features

requests on FACCH/F (MT-SM)
Definition
Number of SAPI3 link establishments on FACCH/F (MT-SM)
Description
This counter counts the number of short message link establishment of mobile terminating
call through FACCH/F. On FACCH/F, BSC receives DTAP_IND message sent by MSC
Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/F.
21-8

Measurement Point
Unit
Times
Related Features

requests on FACCH/H (MT-SM)
Definition
Number of SAPI3 link establishments on FACCH/H (MT-SM)
Description
call through FACCH/H. On FACCH/H, BSC receives DTAP_IND message sent by MSC
Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/H.
Measurement Point
Unit
Times
Related Features
21.10 C901150011 Number of successful SAPI3 link

establishments on SACCH/F (MT-SM)
Definition
Number of successful SAPI3 link establishments on SACCH/F (MT-SM)
21-9

Description
terminating call through SACCH/F. On SACCH/F, if BSC receives EST_CONF message
sent by BTS after it initiates short message link establishment flow, this link establishment
succeeds, and the counter increments.
Usage
This counter is used to find out the frequency of successful SAPI3 link establishments on
SACCH/F.
Measurement Point
This counter counts the number of BSC receiving EST_IND message send by BTS with
SAPI=3. The measurement point is C2, as shown in Figure 21-5.
Unit
Times
Related Features
21-10


establishments on SACCH/H (MT-SM)
Definition
Number of SAPI3 link establishments on SACCH/H (MT-SM)
Description
call through SACCH/H. On SDCCH/H, if BSC receives EST_CONF message sent by BTS
after it initiates short message link establishment flow, this link establishment succeeds,
and the counter increments.
Usage
SACCH/H.
Measurement Point
This counter counts the number of BSC sending EST_CONF message send by BTS with
SAPI=3 while the short message link between BSC and MS is not established. The
measurement point is C2, as shown inFigure 21-6 .
21-11

Unit
Times
Related Features

establishments on FACCH/F (MT-SM)
Definition
Number of successful SAPI3 link establishments on FACCH/F (MT-SM)
Description
terminating call through FACCH/F. On FACCH/F, if BSC receives EST_CONF message
Usage
SACCH/F.
Measurement Point
Unit
Times
Related Features

establishments on FACCH/H (MT-SM)
Definition
Number of successful SAPI3 link establishments on FACCH/H (MT-SM)
21-12

Description
terminating call through FACCH/H. On FACCH/H, if BSC receives EST_CONF message
Usage
This counter is used to find out the frequency of successful SAPI3 link establishments on
FACCH/H.
Measurement Point
Unit
Times
Related Features
21.14 C901150016 Number of DTAP messages used as

SDCCH UL point-to-point short messages (SMs)
Definition
Number of DTAP messages used as SDCCH UL point-to-point short messages (SMs)
Description
This counter counts the number of DTAP packet sent by MS to the network side through
SDCCH.
Usage
This counter is used to find out the frequency of DTAP message of point-to-point message
on SDCCH UL.
Measurement Point
This counter counts the number of BSC receiving DTAP packet sent by BTS on SDCCH
with SAPI=3. The measurement points are D4 and D5 as shown inFigure 21-7 , and B2
and B5 as shown inFigure 21-8 .
21-13

Figure 21-7 - Flow of MT Short Message in Idle Status
21-14

Figure 21-8 - Flow of MO Short Message in Idle Status
Unit
Times
Related Features
21.15 C901150017 Number of 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 .
21-15

Usage
This counter is used to find out the frequency of DTAP message of point-to-point message
on SDCCH DL.
Measurement Point
This counter counts the number of BSC receiving DTAP packet toBTS on SDCCH with
SAPI=3. The measurement points are D3 and D6 as shown inFigure 21-9 , and B3 and
B4 as shown in Figure 21-10.
Figure 21-9 - Flow of MT Short Message in Idle Status
21-16

Figure 21-10 - Flow of MO Short Message in Idle Status
Unit
Times
Related Features
21.16 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.
21-17

Usage
This counter is used to find out the frequency of DTAP message of point-to-point short
messages on FACCH/F UL.
Measurement Point
Unit
Times
Related Features

FACCH/F DL for point-to-point short messages
Definition
Number of DTAP messages on FACCH/F DL for point-to-point short messages.
Description
This counter counts the number of DTAP packet of short messages sent by network side
to MS through FACCH/F.
Usage
messages on FACCH/F UL.
Measurement Point
Unit
Times
Related Features
21-18


FACCH/H UL for point-to-point short messages
Definition
Number of DTAP messages on FACCH/H UL for point-to-point short messages.
Description
This counter counts the number of DTAP packet of short messages sent by MS to network
side through FACCH/H.
Usage
messages on FACCH/H UL.
Measurement Point
Unit
Times
Related Features

FACCH/H DL for point-to-point short messages
Definition
Number of DTAP messages on FACCH/H DL for point-to-point short messages.
Description
to MS through FACCH/H.
Usage
messages on FACCH/H DL.
Measurement Point
21-19

Unit
Times
Related Features

SACCH/F DL for point-to-point short messages
Definition
Number of DTAP messages on SACCH/F UL for point-to-point short messages.
Description
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.
Measurement Point
with SAPI=3. The measurement points are C4 and C5 as shown in Figure 21-11, and A2
and A5 as shown inFigure 21-12 .
21-20

21-21

Unit
Times
Related Features

SACCH/F DL for point-to-point short messages
Definition
Number of DTAP messages on SACCH/F DL for point-to-point short messages.
Description
to MS through SACCH/F.
Usage
messages on SACCH/F DL.
Measurement Point
Unit
Times
Related Features

SACCH/H UL for point-to-point short 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.
21-22

Usage
messages on SACCH/H UL.
Measurement Point
with SAPI=3. The measurement points are C4 and C5 as shown inFigure 21-13 , and A2
and A5 as shown in Figure 21-14.
Figure 21-13 - Flow Of MT Short Message During Conversation
21-23

Figure 21-14 - Flow Of MO Short Messages During Conversation
Unit
Times
Related Features

SACCH/H DL for point-to-point short messages
Definition
Number of DTAP messages on SACCH/H DL for point-to-point short messages.
Description
to MS through SACCH/H.
21-24

Usage
messages on SACCH/H DL.
Measurement Point
This counter counts the number of BSC sending DTAP packet to BTS on SACCH/H
withSAPI=3. The measurement points are C3 and C6 as shown in Figure 21-15, and A3
and A4 as shown inFigure 21-16.
21-25

Unit
Times
Related Features
21-26

Chapter 22
Uplink and Downlink PACCH
Statistics
Table of Contents
Overview ..................................................................................................................22-1
C901160001 Number of Packet access reject message ...........................................22-2
C901160002 Number of Packet resource request message .....................................22-2
C901160003 Number of Packet UL Assignment message ........................................22-3
C901160004 Number of Additional MS access capabilities message........................22-4
C901160005 Number of Packet DL Assignment message ........................................22-5
C901160006 Number of Packet TBF release message.............................................22-6
C901160007 Number of Packet DL Ack/Nack message ...........................................22-7
C901160008 Number of EGPRS Packet DL Ack/Nack message ..............................22-8
C901160009 Number of Packet UL Ack/Nack message ...........................................22-9
C901160010 Number of Packet Control Acknowledgement message.....................22-10
C901160011 Number of Packet Cell Change Continue message............................ 22-11
C901160012 Number of Packet Cell Change Failure message...............................22-12
C901160013 Number of Packet Cell Change Notification message ........................22-13
C901160014 Number of Packet Cell Change Order message ................................22-14
C901160017 Number of packet mobile TBF status messages ................................22-15
C901160018 Number of packet neighbor cell data messages.................................22-16
C901160019 Number of packet PDCH release messages ......................................22-17
C901160020 Number of packet polling request messages .....................................22-18
C901160021 Number of packet power control/timing advance messages...............22-18
C901160022 Number of packet PSI status message ..............................................22-19
C901160023 Number of packet serving cell data messages ...................................22-20
C901160024 Number of packet SI status messages...............................................22-21
C901160025 Number of packet timeslot reconfigure messages..............................22-22
C901160026 Number of packet paging request message.......................................22-23
C901160027 Number of PSI message....................................................................22-24
22.1 Overview
In transmitting GPRS data service, UL and DL PACCH statistics is used to count the
number of receiving and sending controlled messages on PACCH, including packet access
reject, packet resource request, packet UL assignment, and so on.
22-1

22.2 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 Point
When the UPPB of BSC sends packet access reject messages to MS, the counter
increments. The measurement point is A2, as shown inFigure 22-1 .
Figure 22-1 - Measurement Point of Packet Resource Request and Packet Access Reject
Unit
Times
22.3 C901160002 Number of Packet resource request

message
Definition
Number of Packet access reject message
22-2

Chapter 22 Uplink and Downlink PACCH Statistics
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
transmission mode.
Measurement Point
When the UPPB of BSC receives packet resource request messages, the counter
Figure 22-2 - Measurement Point of Packet Resource Request and Packet Access Reject
Unit
Times
22.4 C901160003 Number of 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 assignment needs to be sent on PCCH, other packet
UL assignments such as DL TBF or resource redistribution initiated by MS will be sent on
PACCH by BSC.
22-3

This counter counts the number of packet UL assignment messages sent by BSC on
PACCH.
Measurement Point
When the type of DL control block sent by BSC is packet UL assignment, the counter
Figure 22-3 - Measurement of Packet UL Assignment Message
Unit
Times
22.5 C901160004 Number of Additional MS access

capabilities message
Definition
Number of Additional MS access capabilities messages.
Description
This counter counts the number of additional MS access capabilities messages received
by BSC on PACCH in packet transmission mode.
Usage
transmission mode.
22-4

Measurement Point
When the type of UL control block received by BSC is additional MS access capabilities,
Figure 22-4 - Measurement Point Of Additional MS Access Capabilities Message
Unit
Times
22.6 C901160005 Number of Packet DL Assignment

message
Definition
Number of packet DL assignment messages.
Description
This counter counts the number of packet DL assignment messages sent by BSC on
PACCH in packet transmission mode.
Measurement Point
When the type of DL control block sent by BSC is packet DL assignment, the counter
increments. The measurement point is A, as shown inFigure 22-5 .
22-5

Figure 22-5 - DL Sent on PACCH in Packet Transmission Mode
Unit
Times
22.7 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 Point
When the type of DL control block sent by BSC is packet TBF release, the counter
22-6

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

Measurement Point
When the type of UL control block sent by BSC is packet DL Ack/Nack, the counter
increments. The measurement points are A, A1, as shown inFigure 22-7 .
Figure 22-7 - DL Sent on PACCH IN Packet Transmission Mode
Unit
Times
22.9 C901160008 Number of 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.
22-8

This counter counts the number of EGPRS packet DL Ack/Nack messages received by
BSC on PACCH in EGPRS packet transmission mode.
Measurement Point
When the type of UL control block sent by BSC is EGPRS packet DL Ack/Nack, the counter
increments. The measurement points are A and A1, as shown inFigure 22-8.
Unit
Times
22.10 C901160009 Number of Packet UL Ack/Nack

message
Definition
Number of Packet UL Ack/Nack message
22-9

Description
This counter counts the number of packet UL Ack/Nack messages sent by BSC on PACCH
in packet transmission mode.
Measurement Point
When the type of DL control block sent by BSC is packet UL Ack/Nack, the counter
Figure 22-9 - Signaling Transmission on PACCH
Unit
Times
22.11 C901160010 Number of Packet Control

Acknowledgement message
Definition
Number of Packet Control Acknowledgement message
Description
This counter counts the number of packet control acknowledgement messages received
by BSC on PACCH in packet transmission mode.
Measurement Point
When the type of UL control block received by BSC is packet control acknowledgement,
the counter increments. The measurement point is B, as shown inFigure 22-10.
22-10

Figure 22-10 - Signaling Transmission on PACCH
Unit
Times
22.12 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 system message of destination under the condition that
the network and MS support NACC.
After BSC receives packet cell change messages, it will send packet cell change
continues messages to MS on PACCH or packet cell changes command to inform MS
to switch to the new cell.
This counter counts the number of packet cell change continues messages sent
by BSC on PACCH.
Measurement Point
BSC initiates timer after receiving PACKET NEIGHBOR CELL CHANGE NOTIFICATION.
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 22-11.
22-11

Figure 22-11 - 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 doesnt receive the packet system
message of destination cell, BSC sends the PACK CELL CHANGE CONTINUE message
directly, the counter increments. The measurement point is A1, as shown inFigure 22-12 .
Figure 22-12 - Measurement Point of Packet-Cell-Change-Related Counter (II)
Unit
Times

Failure message
Definition
Number of Packet Cell Change Failure message
22-12

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 messages received by BSC
on PACCH in packet transmission mode.
Measurement Point
When the type of UL control block sent by BSC is packet cell change failure, the counter
Figure 22-13 - Measurement Point of Packet Cell Change Order and Packet Cell Change
Failure
Unit
Times

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 system message of destination under the condition that
the network and MS support NACC.
22-13

This counter counts the number of packet cell change notification messages received by
BSC on PACCH in packet transmission mode.
Measurement Point
When the type of UL control block received by BSC is packet cell change notification, the
counter increments. The measurement point is A1, as shown inFigure 22-14.
Figure 22-14 - Measurement Point of Packet-Cell-Change-Related Counter (I)
Unit
Times

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 sent by BSC on PACCH in packet transmission
mode.
Measurement Point
When BSC sends packet cell change order messages, the counter increments. The
measurement point is A2, as shown inFigure 22-15.
22-14

Figure 22-15 - Measurement Point of Packet Cell Change Order and Packet Cell Change
Failure
Unit
Times
22.16 C901160017 Number of packet mobile TBF status

messages
Definition
Number of packet mobile TBF status messages
Description
This counter counts the number of packet mobile TBF status messages sent by BSC on
PACCH in packet service.
Measurement Point
When the type of UL control block received by BSC is packet mobile TBF, the counter
22-15

Figure 22-16 - Measurement Point of Packet Mobile Status Message on PACCH
Unit
Times
22.17 C901160018 Number of 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 sent by BSC on PACCH
in packet transmission mode.
Measurement Point
When the type of DL control block sent by BSC is packet neighboring cell data, the counter
increments. The measurement point is A2, as shown inFigure 22-17.
22-16

Figure 22-17 - Measurement Point of Packet-Cell-Change-Related Counter
Unit
Times
22.18 C901160019 Number of packet PDCH release

messages
Definition
Number of packet PDCH release messages.
Description
This counter counts the number of packet PDCH release messages sent by BSC on
PACCH.
Measurement Point
When the type of DL control block sent by BSC is packet PDCH release, the counter
increments.
Unit
Times
22-17

22.19 C901160020 Number of packet polling request

messages
Definition
Number of packet polling request messages.
Description
This counter counts the number of packet polling request messages sent by BSC on
Measurement Point
When the type of DL control block sent by BSC is packet polling request, counter
Figure 22-18 - Measurement Point of DL TBF Establishes Execution Polling
Unit
Times
22.20 C901160021 Number of packet power

control/timing advance messages
Definition
Number of packet power control/timing advance messages.
22-18

Description
This counter counts the number of packet power control/timing advance messages sent
by BSC on PACCH.
Measurement Point
When the type of DL control block sent by BSC is packet power control/timing advance
message, counter increments. The measurement point is A, as shown inFigure 22-19.
Figure 22-19 - Measurement Point of Packet Power Control/Timing Advance Message

Sent on PACCH
Unit
Times
22.21 C901160022 Number of 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.
22-19

Measurement Point
When the type of UL control block sent by BSC is packet PSI Status message, counter
Figure 22-20 - Measurement Point of Packet-Service-Cell-Data-Related Counter
Unit
Times
22.22 C901160023 Number of packet serving cell data

messages
Definition
Number of packet serving cell data messages.
Description
Network uses packet serving cell data to send the system messages and packet messages
of serving cell to MS, this counter counts the number of packet serving cell data messages
received by BSC on PACCH.
Usage
This counter is used to check packet serving cell data messages sent by BSC on PACCH.
Measurement Point
When the type of DL control block sent by BSC is packet serving cell data messages, the
counter increments. The measurement point is A2, as shown inFigure 22-21 .
22-20

Unit
Times
22.23 C901160024 Number of 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 received by BSC on PACCH.
Measurement Point
When the type of UL control block sent by BSC is packet SI status message, counter
22-21

Unit
Times
22.24 C901160025 Number of 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 Point
When the type of DL control block sent by BSC is packet timeslot reconfigure messages,
counter increments. The measurement point is A, as shown inFigure 22-23 andFigure
22-24 .
22-22

Figure 22-23 - Flow of Establishing UL on PACCH under DL Transmission Status
Figure 22-24 - Flow of Establishing DL on PACCH under UL Transmission Status
Unit
Times
22.25 C901160026 Number of packet paging request

message
Definition
Number of packet paging request message.
22-23

Description
If MS is in packet transmission status or attached by GPRS, BSC will send packet paging
request messages.
This counter counts the number of packet paging request messages sent by BSC on
PACCH.
Measurement Point
When the type of DL control block sent by BSC to MS through BTS is packet paging request
messages, the counter increments. The measurement point is A, as shown inFigure 22-25
.
Figure 22-25 - Measurement Point of BSC Issuing Packet Paging Request Message
Unit
Times
Related Features
22.26 C901160027 Number of PSI message

Definition
Number of packet PSI message.
22-24

Description
This counter counts the number of PSI messages sent by BSC on PACCH in packet
service.
Measurement Point
When the type of DL control block sent by BSC to MS through BTS is packet system
message, the counter increments. The measurement point is A, as shown inFigure 22-26.
Figure 22-26 - Measurement Point of BSC Issuing Packet System Message
Unit
Times
22-25

22-26

Chapter 23
Downlink GPRS Data TBF
Statistics
Table of Contents
Overview ..................................................................................................................23-3
C901170002 Number of GPRS DL TBF establishment requests on CCCH/PCCCH .23-3
C901170003 Number of GPRS DL TBF establishment requests on PACCH.............23-4
C901170004 Number of GPRS DL TBF establishment failure due to CPU ...............23-5
C901170005 Number of GPRS DL TBF establishment failure due to not support
DTM .........................................................................................................................23-5
C901170007 Number of GPRS DL TBF establishment failure due to Abis
congestion................................................................................................................23-5
C901170008 Number of GPRS DL TBF establishment failure due to RR congestion .23-6
C901170009 Number of GPRS DL TBF establishment failure due to UPPB-DSP
channel congestion ..................................................................................................23-8
C901170010 Number of GPRS DL TBF establishment channel allocate success .....23-9
C901170011 Number of allocated PDCH for GPRS DL TBF establishment ............23-10
C901170012 Number of GPRS DL TBF establishment failure due to channel
activate failed ......................................................................................................... 23-11
C901170013 Number of GPRS DL TBF establishment failure due to BTS
connection failed ....................................................................................................23-12
C901170014 Number of GPRS DL TBF establishment failure due to BIU connection
failed ......................................................................................................................23-13
C901170015 Number of GPRS DL TBF channel activate establishment success ...23-14
due to not receive PIA ............................................................................................23-15
due to UPPB-DSP congestion ................................................................................23-16
UPPB-DSP congestion...........................................................................................23-16
C901170019 Number of GPRS DL TBF establishment success on PCCCH/CCCH .23-17
C901170020 Number of GPRS DL TBF establishment success on PACCH ...........23-17
C901170023 Number of GPRS DL TBF resource reallocation failure due to Abis
congestion for UL TBF establishment .....................................................................23-18
C901170024 Number of GPRS DL TBF resource reallocation failure due to RR
C901170025 Number of GPRS DL TBF resource reallocation failure due to
UPPB-DSP channel congestion for UL TBF establishment.....................................23-20
23-1

C901170026 Number of GPRS DL TBF resource reallocation success due to UL

C901170027 Number of allocated PDCH for GPRS DL TBF resource reallocation
due to UL TBF establishment .................................................................................23-22
C901170028 Number of GPRS DL TBF resource reallocation failure due to channel
activate failure for UL TBF establishment ...............................................................23-23
C901170029 Number of GPRS DL TBF resource reallocation failure due to BTS
connection failure for UL TBF establishment ..........................................................23-24
C901170030 Number of GPRS DL TBF resource reallocation failure due to BIU
C901170031 Number of GPRS DL TBF resource reallocation success of channel
activate and connection for UL TBF establishment .................................................23-26
C901170032 Number of GPRS DL TBF resource reallocation failure due to UL TBF
establishment .........................................................................................................23-27
C901170033 Number of GPRS DL TBF resource reallocation success due to UL
C901170036 Number of GPRS DL TBF resource reallocation failure due to Abis
congestion for LLC transmission.............................................................................23-27
C901170037 Number of GPRS DL TBF resource reallocation failure due to RR
C901170038 Number of GPRS DL TBF resource reallocation failure due to
UPPB-DSP channel congestion for LLC transmission ............................................23-30
C901170039 Number of GPRS DL TBF resource reallocation success due to LLC
transmission ...........................................................................................................23-31
C901170040 Number of allocated PDCH for GPRS DL TBF resource reallocation
due to LLC transmission.........................................................................................23-32
C901170041 Number of GPRS DL TBF resource reallocation failure due to channel
activate failure for LLC transmission .......................................................................23-33
C901170042 Number of GPRS DL TBF resource reallocation failure due to BTS
connection failure for LLC transmission ..................................................................23-34
C901170043 Number of GPRS DL TBF resource reallocation failure due to BIU
C901170044 Number of GPRS DL TBF resource reallocation success of channel
activate and connection for LLC transmission.........................................................23-36
C901170045 Number of GPRS DL TBF resource reallocation failure due to LLC
transmission ...........................................................................................................23-36
C901170046 Number of GPRS DL TBF resource reallocation success due to LLC
transmission ...........................................................................................................23-37
C901170047 Number of GPRS DL TBF release due to flush LL .............................23-37
C901170048 Number of GPRS DL TBF release due to GPRS suspend requests...23-38
C901170049 Number of GPRS DL TBF forcing release by CS ...............................23-38
C901170050 Number of GPRS DL TBF normal release due to user plane
requests .................................................................................................................23-39
C901170051 Number of GPRS DL TBF abnormal release due to user plane
requests .................................................................................................................23-40
23-2

Chapter 23 Downlink GPRS Data TBF Statistics
C901170052 Number of GPRS DL TBF release due to NSVC unavailability...........23-41

C901170053 Number of GPRS DL TBF release due to BVC unavailability .............23-42
C901170054 Number of GPRS DL TBF release due to other reasons ....................23-42
C901170055 Number of DL GPRS TBF grab resources .........................................23-43
C901170056 Number of grab instance by DL GPRS TBF.......................................23-44
C901170057 Number of DL GPRS TBF queuing ....................................................23-45
C901170058 Number of DL GPRS TBF queuing success ......................................23-46
C901170059 Number of DL GPRS TBF release TBF during queuing .....................23-47
23.1 Overview
DL GPRS data TBF statistics is used to observe the process of GPRS DL TBF
establishment, maintenance and release.

Definition
Number of GPRS DL TBF establishment requests on CCCH/PCCCH.
Description
This counter counts the number of DL establishment requests received by control plane
when BSC initially attempts to establish GPRS DL TBF.
Usage
This counter is used to find out the frequency of DL establishment requests sent from
CCCH/PCCCH and received by control plane when BSC establishes GPRS DL TBF.
Measurement Point
When RANPS module receives the DL request (EV_RANUMC_DLASS_REQ) sent from
RANUMC module, the counter increments. The measurement point is A, as shown in
Figure 23-1.
Figure 23-1 - DL Request
23-3

Unit
Times

Definition
Number of GPRS DL TBF establishment requests on PACCH.
Description
This counter counts the number of establishing GPRS DL TBF on PACCH by MS.
Usage
This counter is used to find out the frequency of establishing DL TBF in PACCH after MS
has established GPRS UL TBF.
Measurement Point
After MS has established GPRS UL TBF, RANPS module receives
EV_MAC_DL_ASSIGN_REQ message sent from RANU module, the counter increments.
Figure 23-2 - DL Assignment Request
Unit
Times
23-4


establishment failure due to CPU
Description
No statistics temporarily.

establishment failure due to not support DTM
Description

establishment failure due to Abis congestion
Definition
Number of GPRS DL TBF establishment failure due to Abis congestion.
Description
This counter counts the number of failures that RANPS applies to database for resource
and the cause of failures is Abis congestion when BSC attempts to establish GPRS DL
TBF.
Usage
This counter is used to find out the frequency of failures that RANPS applies to database
for resource and the cause of failures is Abis congestion when BSC attempts to establish
GPRS DL TBF.
Measurement Point
The measurement is taken at two time points listed below:
l 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 shown
inFigure 23-3 .
23-5

Figure 23-3 - Database Application Failure due to Abis Congestion (I)
l After MS establishes GPRS UL TBF, RANPS module receives

EV_MAC_DL_ASSIGN_REQ message sent from RANU module, if resource
application fails and the cause of failure is Abis congestion, the counter increments.
Figure 23-4 - Database Application Failure due to Abis Congestion (II)
Unit
Times
Related Features

establishment failure due to RR congestion
Definition
Number of GPRS DL TBF establishment failure due to RR congestion.
Description
and the cause of failures is RR congestion when BSC attempts to establish GPRS DL TBF.
23-6

There are three causes for RR congestion: MS per channel (number of MS reaches the
peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel).
Usage
for resource and the cause of failures is RR congestion when BSC attempts to establish
GPRS DL TBF.
Measurement Point

RR congestion, the counter increments. The measurement point is A, as shown
inFigure 23-5.
Figure 23-5 - Database Application Failure Due To RR Congestion (I)

application fails and the cause of failure is RR congestion, the counter increments.
Figure 23-6 - Database Application Failure Due To RR Congestion (II)
Unit
Times
23-7

Related Features

establishment failure due to UPPB-DSP channel
congestion
Definition
Number of GPRS DL TBF establishment failure due to UPPB-DSP channel congestion.
Description
and the cause of failures is UPPB-DSP channel 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 UPPB-DSP channel congestion when BSC attempts
to establish GPRS DL TBF.
Measurement Point
l 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
UPPB-DSP channel congestion, the counter increments. The measurement point
is A, as shown inFigure 23-7.
Figure 23-7 - Database Application Failure due to UPPB-DSP Channel Congestion

(I)

23-8

application fails and the cause of failure is UPPB-DSP channel congestion, the
counter increments. The measurement point is A, as shown inFigure 23-8.

(II)
Unit
Times
Related Features

establishment channel allocate success
Definition
Number of GPRS DL TBF establishment channel allocate success
Description
This counter counts the number of channel allocate success applied by RANPS when BSC
attempts to establish GPRS DL TBF.
Usage
This counter is used to find out the frequency of successful resource application that
RANPS sends when BSC attempts to establish GPRS DL TBF.
Measurement Point
After RANPS module receives DL request message (EV_RANUMC_DLASS_REQ) sent from
RANUMC module, when resource application succeeds, the counter increments. The
23-9

Figure 23-9 - Successful Resource Application
Unit
Times
Related Features
23.10 C901170011 Number of allocated PDCH for GPRS

DL TBF establishment
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.
Measurement Point
After RANPS module receives DL request message (EV_RANUMC_DLASS_REQ) sent
from RANUMC module, when resource application succeeds, the counter accumulates
the PDCH number. The measurement point is A, as shown inFigure 23-10.
23-10

Unit
Times

establishment failure due to channel activate failed
Definition
Number of GPRS DL TBF establishment failure due to channel activate failed
Description
This counter counts the number of PDCH activate failure when BSC establishes GPRS
DL TBF.
Usage
This counter is used to find out the frequency of PDCH activate failure when BSC
establishes GPRS DL TBF (including establishing DL TBF initially and establishing DL
TBF while UL TBF already exists).
Measurement Point
l When BSC receives PDCH activation failure message reported by BTS, the counter
23-11

Figure 23-11 - PDCH Activation Failure
l 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

establishment failure due to BTS connection failed
Definition
Number of GPRS DL TBF establishment failure due to BTS connection failed.
Description
This counter counts the number of connection failure due to BTS connection failed when
BSC establishes GPRS DL TBF.
Usage
This counter is used to find out the frequency of connection failure due to BTS connection
failed when BSC establishes GPRS DL TBF (including establishing DL TBF initially and
establishing DL TBF while UL TBF already exists).
Measurement Point
l If RANPS module receives connection failed message reported by connection

module, and the cause of failure is BTS connection failed, the counter increments.
23-12

Figure 23-12 - Connection Failed due to BTS Connection Failure
l If 'wait for PDCH activate & connection response' timer expires, and BSC has not
received connection success response message reported by connection module,
Unit
Times

establishment failure due to BIU connection failed
Definition
Number of GPRS DL TBF establishment failed due to BIU connection failure.
Description
This counter counts the number of connection failure due to BIU connection failed when
BSC establishes GPRS DL TBF.
Usage
This counter is used to find out the frequency of connection failure due to BIU connection
failed when BSC establishes GPRS DL TBF (including establishing DL TBF initially and
Measurement Point
If RANPS module receives connection failed message reported by connection module, and
the cause of failure is BIU connection failed, the counter increments. The measurement
23-13

Figure 23-13 - Connection Failed Due To BIU Connection Failure
Unit
Times
23.14 C901170015 Number of GPRS DL TBF channel

activate establishment success
Definition
Number of GPRS DL TBF channel activate establishment success.
Description
This counter counts the number of channel activate establishment success when BSC
establishes GPRS DL TBF.
Usage
This counter is used to find out the frequency of channel activate establishment success
when BSC establishes GPRS DL TBF.
Measurement Point
When RANPS module receives channel activate response message reported by BTS
and connection success response message reported by connection module, the counter
increments. The measurement point is A as shown inFigure 23-14.
23-14

Figure 23-14 - DL GPRS TBF Establishes Channel Activation And Access Success
Unit
Times

receive PIA
Definition
Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA
Description
This counter counts the number of DL immediate assignment message sending failures
Usage
This counter is used to find out the frequency of DL immediate assignment message
sending failures when BSC establishes GPRS DL TBF.
Measurement Point
l When RANPS module receives immediate assignment sending failure message

(EV_PACKET_PIA_DEL_IND) reported by BTS, the counter increments. The
23-15

Figure 23-15 - Immediate Assignment Sending Failure
l If 'wait for immediate assignment sending indication' timer expires, and BSC has not
received immediate assignment sending message, the counter increments.
Unit
Times

UPPB-DSP congestion
Definition
Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to UPPB-DSP
congestion.
Description
No statistics for this counter is meaningless to GPRS DL TBF.
Related Features

establishment failure on PACCH due to UPPB-DSP
congestion
Definition
Number of GPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion.
Description
23-16

Related Features

establishment success on PCCCH/CCCH
Definition
Number of GPRS DL TBF establishment success on PCCCH/CCCH.
Description
This counter counts the number of successful DL immediate assignment message sending
Usage
This counter is used to find out the frequency of GPRS DL TBF establishment success.
Measurement Point
When RANPS module receives successful immediate assignment sending message
(SPS_ABIS_PACKET_SEND_PIA_IND) reported by BTS, the counter increments. The
Figure 23-16 - Successful Immediate Assignment Sending
Unit
Times

Definition
Number of GPRS DL TBF establishment success on PACCH.
23-17

Description

reallocation failure due to 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 reallocation failure. This counter counts the
number of DL resource reallocation failure due to Abis congestion.
Usage
This counter is used to find out the frequency of GPRS DL TBF resource reallocation failure
due to Abis congestion.
Measurement Point
MS has established GPRS DL TBF, and after RANPS module receives
EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if resource application
fails due to Abis congestion, the counter increments. The measurement point is A, as
shown inFigure 23-17 .
Figure 23-17 - Resource Application Failure Due To Abis Congestion (Assigned By UL)
23-18

Unit
Times
Related Features

reallocation failure due to RR congestion for UL
TBF establishment
Description
Number of GPRS DL TBF resource reallocation failure due to RR congestion for UL TBF
establishment.
Definition
After MS establishes GPRS DL TBF, it shall establish UL TBF on PACCH. But resource
number of DL resource reallocation failure due to RR congestion.
Usage
due to RR congestion.
Measurement Point
fails due to RR congestion, the counter increments. The measurement point is A, as
23-19

Figure 23-18 - Resource Application Failure Due To RR Congestion (Assigned By UL)
Unit
Times
Related Features

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
Description
After MS establishes GPRS DL TBF, it shall establish UL TBF in PACCH. But resource
number of DL resource reallocation failures due to UPPB-DSP channel congestion.
Usage
due to UPPB-DSP channel congestion.
Measurement Point
23-20

fails due to UPPB-DSP channel congestion, the counter increments. The measurement
Figure 23-19 - Resource Application Failure Due To UPPB-DSP Channel Congestion

(Assigned By UL)
Unit
Times
Related Features

reallocation success due to UL TBF establishment
Definition
Number of GPRS DL TBF resource reallocation success due to UL TBF establishment.
Description
After MS establishes GPRS DL TBF, it shall establish UL TBF in PACCH. This counter
counts the number of DL resource application success.
Usage
This counter is used to find out the frequency of GPRS DL TBF resource reallocation
success.
Measurement Point
23-21

succeeds, the counter increments. The measurement point is A, as shown inFigure

23-20.
Figure 23-20 - Successful Resource Application (Assigned By UL)
Unit
Times
Related Features
23.24 C901170027 Number of allocated PDCH for

GPRS DL TBF resource 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 allocated PDCH when GPRS
DL TBF resource is reallocated.
Measurement Point
EV_MAC_UL_ASSIGN_REQ message sent from RANU module, when resource application
23-22

succeeds, the counter accumulates the PDTCH number. The measurement point is A,
as shown inFigure 23-21.
Unit
Times
Related Features

reallocation failure due to channel activate failure
for UL TBF establishment
Definition
Number of GPRS DL TBF resource reallocation failure due to channel activate failure for
UL TBF establishment
Description
This counter counts the number of PDCH activate failure during the process of GPRS DL
TBF resource reallocation.
Usage
This counter is used to find out the frequency of PDCH activate failure during the process
of GPRS DL TBF resource reallocation.
Measurement Point
23-23

l When BSC receives PDCH activate failure message reported by BTS, the counter
increments.
Unit
Times

reallocation failure due to BTS connection failure
Definition
Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for
Description
This counter counts the number of connection failure due to BTS connection failure during
the process of GPRS DL TBF resource reallocation.
Usage
failure during the process of GPRS DL TBF resource reallocation.
Measurement Point
l If RANPS module receives connection failure message reported by connection

module, and the cause of failure is BTS connection failure, the counter increments.
23-24

Figure 23-23 - Connection Failure Due To BTS Connection Failure
l If 'wait for PDCH activation & connection response' timer expires, and BSC has not
Unit
Times

reallocation failure due to BIU connection failure
Definition
Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for
Description
This counter counts the number of connection failure due to BIU connection failure during
the process of GPRS DL TBF resource reallocation.
Usage
failure during the process of GPRS DL TBF resource reallocation.
Measurement Point
If RANPS module receives connection failure message reported by connection module,
and the cause of failure is BIU connection failure, the counter increments. The
23-25

Unit
Times

reallocation success of channel activate and
connection for UL TBF establishment
Definition
Number of GPRS DL TBF resource reallocation success of channel activate and
Description
This counter counts the number of channel activate success during the process of GPRS
DL TBF resource reallocation.
Usage
This counter is used to find out the frequency of channel activate success during the
process of GPRS DL TBF resource reallocation.
Measurement Point
23-26

Figure 23-25 - Successful Activation And Connection
Unit
Times

Definition
Number of GPRS DL TBF resource reallocation failure due to UL TBF establishment.
Description

Definition
Number of GPRS DL TBF resource reallocation success due to UL TBF establishment.
Description

reallocation failure due to Abis congestion for LLC
transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to Abis congestion for LLC
transmission.
23-27

Description
During GPRS DL TBF transmission, MAC sends resource adjustment message
(EV_MAC_RESOURCE_ADJU_REQ) to RANPS due to UL/DL LLC changes. RANPS applies
for resource after it receives the message. This counter counts the number of resource
application failures after RANPS receives resource adjustment request during GPRS DL
TBF transmission (the cause of database application failure is Abis congestion).
Usage
This counter is used to find out the frequency of resource application failures after RANPS
receives resource adjustment request during GPRS DL TBF transmission (the cause of
database application failure is Abis congestion).
Measurement Point
After RANPS module receives EV_MAC_RESOURCE_ADJU_REQ message sent from
MAC, if resource application fails due to Abis congestion, the counter increments. The
Figure 23-26 - Resource Application Failure Due To Abis Congestion (Resource

Adjustment)
Unit
Times
Related Features
23-28


reallocation failure due to RR congestion for LLC
transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to RR congestion for LLC
transmission.
Description
(EV_MAC_RESOURCE_ADJU_REQ) to RANPS due to UL/DL LLC changes. RANPS
applies for resource after it receives the message. This counter counts the number of
resource application failures after RANPS receives resource adjustment request during
GPRS DL TBF transmission (the cause of database application failure is RR congestion).
Usage
Measurement Point
MAC, if resource application fails due to RR congestion, the counter increments. The
Figure 23-27 - Resource Application Failure Due To RR Congestion (Resource

Adjustment)
Unit
Times
Related Features
23-29


congestion for LLC transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel
congestion for LLC transmission.
Description
resource reallocation failure after RANPS receives resource adjustment request during
GPRS DL TBF transmission (the cause of database application failure is UPPB-DSP
channel congestion).
Usage
This counter is used to find out the frequency of resource reallocation failure after RANPS
receives resource adjustment request during GPRS DL TBF transmission (the cause of
database application failure is UPPB-DSP channel congestion).
Measurement Point
After RANPS module receives EV_MAC_RESOURCE_ADJU_REQ message sent from MAC,
if resource application fails due to UPPB-DSP channel congestion, the counter increments.

(Resource Adjustment)
Unit
Times
23-30

Related Features

reallocation success due to LLC transmission
Definition
Number of GPRS DL TBF resource reallocation success due to LLC transmission.
Description
resource reallocation success after RANPS receives resource adjustment request during
GPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of resource reallocation success after RANPS
receives resource adjustment request during GPRS DL TBF transmission.
Measurement Point
if resource application succeeds, the counter increments. The measurement point is A, as
Figure 23-29 - Successful Resource Application (Resource Adjustment)
Unit
Times
23-31

Related Features

GPRS DL TBF resource reallocation due to LLC
transmission
Definition
Number of allocated PDCH for GPRS DL TBF resource reallocation due to LLC
transmission.
Description
successfully allocated PDCH after RANPS receives resource adjustment request during
GPRS DL TBF transmission.
Usage
This counter is used to find out the number of successfully allocated PDCH after RANPS
Measurement Point
MAC, if resource application succeeds, the counter accumulates the PDTCH number.
Unit
Times
23-32

Related Features

for LLC transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to channel activate failure for
LLC transmission.
Description
This counter counts the number of PDCH activate failure after BSC receives resource
adjustment request during GPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of PDCH activate failure after BSC receives
resource adjustment request during GPRS DL TBF transmission.
Measurement Point
increments.
Unit
Times
23-33


Definition
Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for
LLC transmission.
Description
This counter counts the number of connection failure due to BTS connection failure after
BSC receives resource adjustment request during GPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of connection failure due to BTS
connection failure after BSC receives resource adjustment request during GPRS DL TBF
transmission.
Measurement Point
measurement is taken at two time points listed below:
Figure 23-32 - Connection Failed Due To BTS Connection Failure
Unit
Times
23-34


Definition
Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for
LLC transmission.
Description
This counter counts the number of connection failure due to BIU connection failure after
BSC receives resource adjustment request during GPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of connection failure due to BIU
connection failure after BSC receives resource adjustment request during GPRS DL TBF
transmission.
Measurement Point
Unit
Times
23-35


connection for LLC transmission
Definition
Number of GPRS DL TBF resource reallocation success of channel activate and
Description
This counter counts the number of channel activate success after BSC receives resource
adjustment request during GPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of channel activate success after BSC
Measurement Point
Unit
Times

Definition
Number of GPRS DL TBF resource reallocation failure due to LLC transmission.
23-36

Description

Definition
Number of GPRS DL TBF resource reallocation success due to LLC transmission.
Description
23.42 C901170047 Number of GPRS DL TBF release

due to flush LL
Definition
Number of GPRS DL TBF release due to flush LL.
Description
This counter counts the number of GPRS DL TBF release due to flush LL.
Usage
This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests
due to flush LL received by RANPS.
Measurement Point
When RANPS module receives Release Request message (EV_RANUMC_REL_CMD)
reported by RANUMC, if the cause of release is flush LL, and GPRS DL TBF exists, the
Figure 23-35 - Release Request Due To Flush LL
23-37

Unit
Times

due to GPRS suspend requests
Definition
Number of GPRS DL TBF release due to GPRS suspend requests.
Description
This counter counts the number of GPRS DL TBF release due to GPRS suspend requests.
Usage
due to suspend requests received by RANPS.
Measurement Point
reported by RANUMC, if the cause of release is SUSPEND, and GPRS DL TBF exists,
Figure 23-36 - Release Request Due To Suspend Request
Unit
Times
23.44 C901170049 Number of GPRS DL TBF forcing

release by CS
Definition
Number of GPRS DL TBF forcing release by CS.
23-38

Description
This counter counts the number of GPRS DL TBF forcing release by CS due to PDCH
REL.
Usage
(EV_RANCCM_PDCH_REL) received by RANPS.
Measurement Point
When RANPS module receives Release Request message (EV_RANCCM_PDCH_REL)
reported by RANCCM module, if GPRS DL TBF exists, the counter increments. The
Figure 23-37 - Release Request Due To PDCH REL
Unit
Times
23.45 C901170050 Number of GPRS DL TBF normal

release due to user plane requests
Definition
Number of GPRS DL TBF normal release due to user plane requests.
Description
This counter counts the number of GPRS DL TBF normal release due to normal Release
Request by MAC.
Usage
due to normal Release Request by MAC received by RANPS.
23-39

Measurement Point
When RANPS module receives Release Request message (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 increments. The measurement point is A, as shown in Figure 23-38.
Figure 23-38 - Release Request Due To Normal Release Request By MAC
Unit
Times
23.46 C901170051 Number of GPRS DL TBF abnormal

Definition
Number of GPRS DL TBF abnormal release due to user plane requests.
Description
This counter counts the number of GPRS DL TBF abnormal release due to abnormal
Release Request by MAC.
Usage
due to abnormal Release Request by MAC received by RANPS.
Measurement Point
by MAC, if the cause of release is abnormal Release Request by MAC, and GPRS DL TBF
exists, the counter increments. The measurement point is A, as shown inFigure 23-39.
23-40

Figure 23-39 - Release Request Due To Abnormal Release Request By MAC
Unit
Times

due to NSVC unavailability
Definition
Number of GPRS DL TBF release due to NSVC unavailability.
Description
This counter counts the number of GPRS DL TBF release due to NSVC unavailability.
Usage
due to NSVC unavailability received by RANPS.
Measurement Point
reported by RANUMC, if the cause of release is NSVC unavailability, and GPRS DL TBF
Figure 23-40 - Release Request Due To NSVC Unavailability
Unit
Times
23-41


due to BVC unavailability
Definition
Number of GPRS DL TBF release due to BVC unavailability.
Description
This counter counts the number of GPRS DL TBF release due to BVC unavailability.
Usage
due to BVC unavailability received by RANPS.
Measurement Point
reported by RANUMC, if the cause of release is BVC unavailability, and GPRS DL TBF
exists, the counter increments. The measurement point is A, as shown inFigure 23-41 .
Figure 23-41 - Release Request Due To BVC Unavailability
Unit
Times

Definition
Number of GPRS DL TBF release due to other reasons.
Description
This counter counts the number of GPRS DL TBF release due to other reasons.
23-42

Usage
due to other reasons received by RANPS.
Measurement Point
reported by RANUMC, if the reason of release is others, and GPRS DL TBF exists, the
Figure 23-42 - Release Request Due To Other Reasons
Unit
Times
23.50 C901170055 Number of DL 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 Point
This counter increments while DL GPRS TBF is established during resource adjustment,
resource request is successful, and other TBF resource is grabbed. Measurement point
is A as shown in Figure 23-43.
23-43

Figure 23-43 - DL GPRS Resource Request Success
Unit
Times
Related Features
l ZGO-01-02-003 Service Based QoS
l ZGO-01-02-004 Streaming Service Policies
23.51 C901170056 Number of grab instance by DL

GPRS TBF
Definition
Number of grab instance by DL GPRS TBF
Description
This counter counts the number of grab instance by DL GPRS TBF.
Usage
This counter is used to find out the frequency for DL GPRS TBF grabbing other TBF
resource.
Measurement Point
is A as shown inFigure 23-44.
23-44

Unit
Times
Related Features
23.52 C901170057 Number of DL GPRS TBF queuing

Definition
Number of DL GPRS TBF queuing.
Description
This counter counts the number of DL GPRS TBF queuing.
Usage
This counter is used to find out the frequency for DL GPRS TBF queuing.
Measurement Point
resource request is successful but queuing is required due to incompliant to QoS rate.
Measurement point is A as shown inFigure 23-45.
23-45

Unit
Times
Related Features
23.53 C901170058 Number of DL GPRS TBF queuing

success
Definition
Number of DL GPRS TBF queuing success.
Description
This counter counts the number of DL GPRS TBF queuing success.
Usage
This counter is used to find out the frequency for DL GPRS TBF queuing success.
Measurement Point
the instance to be queued successfully assigns resource for user plane, and database is
successfully registered. Measurement point is A as shown in Figure 23-46.
23-46

Figure 23-46 - Resource Assignment Success
Unit
Times
Related Features
23.54 C901170059 Number of DL GPRS TBF release

TBF during queuing
Definition
Number of DL GPRS TBF release TBF during queuing.
Description
This counter counts the number of DL GPRS TBF release during queuing.
Usage
This counter is used to find out the frequency for DL GPRS TBF release during queuing.
Measurement Point
This counter increments while DL GPRS TBF is released and instance still in queuing
state. The measurement point is A as shown inFigure 23-47.
23-47

Figure 23-47 - Release DL GPRS TBF
Unit
Times
Related Features
23-48

Chapter 24
Downlink EGPRS Data TBF
Statistics
Table of Contents
Overview ..................................................................................................................24-3
C901180002 Number of EGPRS DL TBF establishment requests on
CCCH/PCCCH .........................................................................................................24-3
C901180003 Number of EGPRS DL TBF establishment requests on PACCH ..........24-4
C901180004 Number of EGPRS DL TBF establishment failure due to CPU .............24-5
C901180005 Number of EGPRS DL TBF establishment failure due to not support
DTM .........................................................................................................................24-5
C901180007 Number of EGPRS DL TBF establishment failure due to Abis
congestion................................................................................................................24-5
C901180008 Number of EGPRS DL TBF establishment failure due to RR
congestion................................................................................................................24-7
C901180009 Number of EGPRS DL TBF establishment failure due to UPPB-DSP
channel congestion ..................................................................................................24-8
C901180010 Number of EGPRS DL TBF establishment channel allocate success...24-9
C901180011 Number of allocated PDCH for EGPRS DL TBF establishment ..........24-10
C901180012 Number of EGPRS DL TBF establishment failure due to channel
activate failed ......................................................................................................... 24-11
C901180013 Number of EGPRS DL TBF establishment failure due to BTS
C901180014 Number of EGPRS DL TBF establishment failure due to BIU
C901180015 Number of EGPRS DL TBF channel activate establishment success .24-14
due to not receive PIA ............................................................................................24-15
C901180019 Number of EGPRS DL TBF establishment success on
PCCCH/CCCH .......................................................................................................24-17
C901180020 Number of EGPRS DL TBF establishment success on PACCH .........24-17
C901180023 Number of EGPRS DL TBF resource reallocation failure due to Abis
24-1

C901180024 Number of EGPRS DL TBF resource reallocation failure due to RR

C901180025 Number of EGPRS DL TBF resource reallocation failure due to
UPPB-DSP channel congestion for UL TBF establishment.....................................24-20
C901180026 Number of EGPRS DL TBF resource reallocation success due to UL
C901180027 Number of allocated PDCH for EGPRS DL TBF resource reallocation
due to UL TBF establishment .................................................................................24-22
channel activate failure for UL TBF establishment ..................................................24-23
C901180029 Number of EGPRS DL TBF resource reallocation failure due to BTS
C901180030 Number of EGPRS DL TBF resource reallocation failure due to BIU
C901180031 Number of EGPRS DL TBF resource reallocation success of channel
activate and connection for UL TBF establishment .................................................24-26
C901180032 Number of EGPRS DL TBF resource reallocation failure due to UL
C901180033 Number of EGPRS DL TBF resource reallocation success due to UL
C901180036 Number of EGPRS DL TBF resource reallocation failure due to Abis
C901180037 Number of EGPRS DL TBF resource reallocation failure due to RR
C901180039 Number of EGPRS DL TBF resource reallocation success due to LLC
transmission ...........................................................................................................24-31
C901180040 Number of allocated PDCH for EGPRS DL TBF resource reallocation
channel activate failure for LLC transmission..........................................................24-33
C901180042 Number of EGPRS DL TBF resource reallocation failure due to BTS
C901180043 Number of EGPRS DL TBF resource reallocation failure due to BIU
C901180044 Number of EGPRS DL TBF resource reallocation success of channel
activate and connection for LLC transmission.........................................................24-36
C901180045 Number of EGPRS DL TBF resource reallocation failure due to LLC
transmission ...........................................................................................................24-37
C901180046 Number of EGPRS DL TBF resource reallocation success due to LLC
transmission ...........................................................................................................24-37
C901180047 Number of EGPRS DL TBF release due to flush LL...........................24-38
C901180048 Number of EGPRS DL TBF release due to EGPRS suspend
requests .................................................................................................................24-38
24-2

Chapter 24 Downlink EGPRS Data TBF Statistics
C901180049 Number of EGPRS DL TBF forcing release by CS.............................24-39

C901180050 Number of EGPRS DL TBF normal release due to user plane
requests .................................................................................................................24-40
C901180051 Number of EGPRS DL TBF abnormal release due to user plane
requests .................................................................................................................24-41
C901180052 Number of EGPRS DL TBF release due to NSVC unavailability ........24-41
C901180053 Number of EGPRS DL TBF release due to BVC unavailability...........24-42
C901180054 Number of EGPRS DL TBF release due to other reasons..................24-43
C901180055 Number of DL EGPRS TBF grab resources.......................................24-44
C901180056 Number of grab instance by DL EGPRS TBF ....................................24-44
C901180057 Number of DL EGPRS TBF queuing..................................................24-45
C901180058 Number of DL EGPRS TBF queuing success ....................................24-46
C901180059 Number of DL EGPRS TBF release TBF during queuing ...................24-47
24.1 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.

Definition
Number of EGPRS DL TBF establishment requests on CCCH/PCCCH.
Description
This counter counts the number of DL establishment requests received by control plane
when BSC initially attempts to establish EGPRS DL TBF.
Usage
This counter is used to find out the frequency of DL establishment requests sent from
CCCH/PCCCH and received by control plane when BSC establishes EGPRS DL TBF.
Measurement Point
When RANPS module receives the DL request (EV_RANUMC_DLASS_REQ) sent from
RANUMC module, the counter increments. This measurement point is A, as shown in
Figure 24-1.
24-3

Figure 24-1 - DL Request
Unit
Times

Definition
Number of EGPRS DL TBF establishment requests on PACCH.
Description
This counter counts the number of establishing EGPRS DL TBF on PACCH by MS.
Usage
This counter is used to find out the frequency of establishing DL TBF in PACCH after MS
has established EGPRS UL TBF.
Measurement Point
After MS has established EGPRS UL TBF, RANPS module receives
EV_MAC_DL_ASSIGN_REQ message sent from RANU module, the counter increments.
This measurement point is A, as shown inFigure 24-2.
Figure 24-2 - DL Assignment Request
24-4

Unit
Times

establishment failure due to CPU
Definition
Number of EGPRS DL TBF establishment failure due to CPU.
Description

establishment failure due to not support DTM
Definition
Number of EGPRS DL TBF establishment failure due to not support DTM.
Description

Definition
Number of EGPRS DL TBF establishment failure due to Abis congestion.
Description
and the cause of failures is Abis congestion when BSC attempts to establish EGPRS DL
TBF.
Usage
for resource and the cause of failures is Abis congestion when BSC attempts to establish
EGPRS DL TBF.
24-5

Measurement Point
l 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 shown in
Figure 24-3.
Figure 24-3 - Database Application Failure Due To Abis Congestion (I)
l After MS establishes EGPRS UL TBF, RANPS module receives

application fails and the cause of failure is Abis congestion, the counter increments.
Figure 24-4 - Database Application Failure Due To Abis Congestion (II)
Unit
Times
Related Features
24-6


Definition
Number of EGPRS DL TBF establishment failure due to RR congestion.
Description
and the cause of failures is RR congestion when BSC attempts to establish GPRS DL TBF.
GPRS DL TBF.
Usage
GPRS DL TBF.
Measurement Point

RR congestion, the counter increments. The measurement point is A, as shown
inFigure 24-5.
Figure 24-5 - Database Application Failure Due To RR Congestion (I)

application fails and the cause of failure is RR congestion, the counter increments.
24-7

Figure 24-6 - Database Application Failure Due To RR Congestion (II)
Unit
Times
Related Features

congestion
Definition
Number of EGPRS DL TBF establishment failure due to UPPB-DSP channel congestion.
Description
and the cause of failures is UPPB-DSP channel congestion when BSC attempts to
establish EGPRS 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 UPPB-DSP channel congestion when BSC attempts
to establish EGPRS DL TBF.
Measurement Point
24-8


(I)
l After MS establishes EGPRS UL TBF, RANPS module receives

application fails and the cause of failure is UPPB-DSP channel congestion, the

(II)
Unit
Times
Related Features

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

Usage
This counter is used to find out the frequency of successful resource application that
RANPS sends when BSC attempts to establish EGPRS DL TBF.
Measurement Point
After RANPS module receives DL request message (EV_RANUMC_DLASS_REQ) sent from
RANUMC module, when resource application succeeds, the counter increments. The
Unit
Times
Related Features

EGPRS DL TBF establishment
Definition
Number of allocated PDCH for EGPRS DL TBF establishment.
Description
This counter counts the number of successful allocated PDCH when BSC attempts to
establish EGPRS DL TBF.
Usage
This counter is used to find out the number of successful allocated PDCH when BSC
attempts to establish EGPRS DL TBF.
24-10

Measurement Point
After RANPS module receives DL request message EV_RANUMC_DLASS_REQ sent from
RANUMC module, when resource application succeeds, the counter accumulates the
PDCH number. The measurement point is A, as shown inFigure 24-10.
Unit
Times
Related Features

Definition
Number of EGPRS DL TBF establishment failure due to channel activate failed.
Description
This counter counts the number of PDCH activate failure when BSC establishes EGPRS
DL TBF.
Usage
This counter is used to find out the frequency of PDCH activate failure when BSC
establishes EGPRS DL TBF (including establishing DL TBF initially and establishing DL
TBF while UL TBF already exists).
Measurement Point
l When BSC receives PDCH activation failure message reported by BTS, the counter
24-11

increments.
Unit
Times

Definition
Number of EGPRS DL TBF establishment failed due to BTS connection failure.
Description
This counter counts the number of connection failure due to BTS connection failed when
BSC establishes EGPRS DL TBF.
Usage
failed when BSC establishes EGPRS DL TBF (including establishing DL TBF initially and
Measurement Point

24-12

Unit
Times

Definition
Number of EGPRS DL TBF establishment failed due to BIU connection failure.
Description
This counter counts the number of connection failure due to BIU connection failed when
BSC establishes EGPRS DL TBF.
Usage
failed when BSC establishes EGPRS DL TBF (including establishing DL TBF initially and
Measurement Point
If RANPS module receives connection failed message reported by connection module, and
the cause of failure is BIU connection failed, the counter increments. The measurement
24-13

Unit
Times
24.14 C901180015 Number of EGPRS DL TBF channel

Definition
Number of EGPRS DL TBF channel activate establishment success.
Description
This counter counts the number of channel activate establishment success when BSC
establishes EGPRS DL TBF.
Usage
This counter is used to find out the frequency of channel activate establishment success
when BSC establishes EGPRS DL TBF.
Measurement Point
24-14

Figure 24-14 - Immediate Assignment Sending Failure
Unit
Times

receive PIA
Definition
Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA
Description
This counter counts the number of DL immediate assignment message sending failures
when BSC establishes EGPRS DL TBF.
Usage
This counter is used to find out the frequency of DL immediate assignment message
sending failures when BSC establishes EGPRS DL TBF.
Measurement Point
l When RANPS module receives immediate assignment sending failure message

EV_PACKET_PIA_DEL_IND reported by BTS, the counter increments. The
24-15

l If 'wait for immediate assignment sending indication' timer expires, and BSC has not
received immediate assignment sending message, the counter increments.
Unit
Times

UPPB-DSP congestion
Definition
Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to UPPB-DSP
congestion.
Description
No statistics for this counter is meaningless to EGPRS DL TBF.

congestion
Definition
Number of EGPRS DL TBF establishment failure on PACCH due to UPPB-DSP
congestion.
Description
24-16


Definition
Number of EGPRS DL TBF establishment success on PCCCH/CCCH.
Description
This counter counts the number of successful DL immediate assignment message
sendings when BSC establishes EGPRS DL TBF.
Usage
This counter is used to find out the frequency of EGPRS DL TBF establishment success.
Measurement Point
When RANPS module receives successful immediate assignment sending message
(SPS_ABIS_PACKET_SEND_PIA_IND) reported by BTS, the counter increments. The
Figure 24-16 - Resource Application Failure Due To Abis Congestion (Assigned By UL)
Unit
Times

Definition
Number of EGPRS DL TBF establishment success on PACCH.
24-17

Description

reallocation failure due to 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 PACCH. But resource
number of DL resource reallocation failure due to Abis congestion.
Usage
This counter is used to find out the frequency of EGPRS DL TBF establishment success.
Measurement Point
MS has established EGPRS DL TBF, and after RANPS module receives
fails due to Abis congestion, the counter increments. The measurement point is A, as
Figure 24-17 - Resource Application Failure Due To Abis Congestion (Assigned by UL)
Unit
Times
24-18

Related Features

reallocation failure due to RR congestion for UL
TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation failure due to RR congestion for UL TBF
establishment.
Description
After MS establishes EGPRS DL TBF, it shall establish UL TBF on PACCH. But resource
number of DL resource reallocation failure due to RR congestion.
Usage
This counter is used to find out the frequency of EGPRS DL TBF resource reallocation
failure due to RR congestion.
Measurement Point
fails due to RR congestion, the counter increments. The measurement point is A, as
Figure 24-18 - Resource Application Failure Due To RR Congestion (Assigned By UL)
24-19

Unit
Times
Related Features

Definition
Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel
Description
After MS establishes EGPRS DL TBF, it shall establish UL TBF in PACCH. But resource
number of DL resource reallocation failures due to UPPB-DSP channel congestion.
Usage
failure due to UPPB-DSP channel congestion.
Measurement Point
fails due to UPPB-DSP channel congestion, the counter increments. The measurement
24-20

Figure 24-19 - Resource Application Failure Due To UPPB-DSP Congestion (Assigned

By UL)
Unit
Times
Related Features

Definition
Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment
Description
After MS establishes EGPRS DL TBF, it shall establish UL TBF in PACCH. This counter
counts the number of DL resource application success.
Usage
success.
Measurement Point
succeeds, the counter increments. The measurement point is A, as shown in Figure
24-20.
24-21

Unit
Times
Related Features

EGPRS DL TBF resource 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 allocated PDCH when EGPRS
DL TBF resource is reallocated.
Measurement Point
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,
24-22

Unit
Times
Related Features

Definition
Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for
Description
This counter counts the number of PDCH activate failure during the process of EGPRS
Usage
This counter is used to find out the frequency of PDCH activate failure during the process
of EGPRS DL TBF resource reallocation.
Measurement Point
increments. The measurement point is A, as shown in
24-23

increments.
Unit
Times

Definition
Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for
Description
This counter counts the number of connection failure due to BTS connection failure during
the process of EGPRS DL TBF resource reallocation.
Usage
failure during the process of EGPRS DL TBF resource reallocation.
Measurement Point

24-24

Unit
Times

Definition
Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for
UL TBF establishment.
Description
This counter counts the number of connection failure due to BIU connection failure during
the process of EGPRS DL TBF resource reallocation.
Usage
failure during the process of EGPRS DL TBF resource reallocation.
Measurement Point
24-25

Unit
Times

Definition
Number of EGPRS DL TBF resource reallocation success of channel activate and
Description
This counter counts the number of channel activate success during the process of EGPRS
Usage
This counter is used to find out the frequency of channel activate success during the
process of EGPRS DL TBF resource reallocation.
Measurement Point
24-26

Unit
Times

Definition
Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment.
Description
Related Features

Definition
Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment.
Description
Related Features
24-27


transmission
Definition
Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for LLC
transmission.
Description
During EGPRS DL TBF transmission, MAC sends resource adjustment message
application failures after RANPS receives resource adjustment request during EGPRS
DL TBF transmission (the cause of database application failure is Abis congestion).
Usage
receives resource adjustment request during EGPRS DL TBF transmission (the cause of
database application failure is Abis congestion).
Measurement Point
MAC, if resource application fails due to Abis congestion, the counter increments. The
measurement point is A, as shown inFigure 24-26 .

Adjustment)
Unit
Times
24-28

Related Features

transmission
Definition
Number of EGPRS DL TBF resource reallocation failure due to RR congestion for LLC
transmission.
Description
application failures after RANPS receives resource adjustment request during EGPRS
DL TBF transmission (the cause of database application failure is RR congestion).
Usage
database application failure is RR congestion).
Measurement Point
MAC, if resource application fails due to RR congestion, the counter increments. The

Adjustment)
24-29

Unit
Times
Related Features

Definition
Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel
Description
resource reallocation failure after RANPS receives resource adjustment request during
EGPRS DL TBF transmission (the cause of database application failure is UPPB-DSP
channel congestion).
Usage
This counter is used to find out the frequency of resource reallocation failure after RANPS
database application failure is UPPB-DSP channel congestion).
Measurement Point
if resource application fails due to UPPB-DSP channel congestion, the counter increments.
24-30


Unit
Times
Related Features

Definition
Number of EGPRS DL TBF resource reallocation success due to LLC transmission.
Description
applies for resource after receiving the message. This counter counts the number of
resource reallocation success after RANPS receives resource adjustment request during
EGPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of resource reallocation success after RANPS
receives resource adjustment request during EGPRS DL TBF transmission.
Measurement Point
if resource application succeeds, the counter increments. The measurement point is A, as
24-31

Unit
Times
Related Features

EGPRS DL TBF resource reallocation due to LLC
transmission
Definition
Number of allocated PDCH for EGPRS DL TBF resource reallocation due to LLC
transmission.
Description
successfully allocated PDCH after RANPS receives resource adjustment request during
EGPRS DL TBF transmission.
Usage
This counter is used to find out the number of successfully allocated PDCH after RANPS
Measurement Point
MAC, if resource application succeeds, the counter accumulates the PDTCH number.
24-32

Unit
Times
Related Features

Definition
Number of Number of EGPRS DL TBF resource reallocation failure due to channel activate
failure for LLC transmission.
Description
This counter counts the number of PDCH activate failure after BSC receives resource
adjustment request during EGPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of PDCH activate failure after BSC receives
resource adjustment request during EGPRS DL TBF transmission.
Measurement Point
24-33

increments.
Unit
Times
Related Features

Definition
Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for
LLC transmission.
Description
This counter counts the number of connection failure due to BTS connection failure after
BSC receives resource adjustment request during EGPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of connection failure due to BTS
connection failure after BSC receives resource adjustment request during EGPRS DL
TBF transmission.
Measurement Point
24-34


Unit
Times

Definition
Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for
LLC transmission.
Description
This counter counts the number of connection failure due to BIU connection failure after
BSC receives resource adjustment request during EGPRS DL TBF transmission.
Usage
failure after BSC receives resource adjustment request during EGPRS DL TBF
transmission.
Measurement Point
24-35

Unit
Times

Definition
Number of EGPRS DL TBF resource reallocation success of channel activate and
Description
This counter counts the number of channel activate success after BSC receives resource
adjustment request during EGPRS DL TBF transmission.
Usage
This counter is used to find out the frequency of channel activate success after BSC
Measurement Point
24-36

Unit
Times

Definition
Number of EGPRS DL TBF resource reallocation failure due to LLC transmission.
Description
Related Features

Definition
Number of EGPRS DL TBF resource reallocation success due to LLC transmission.
Description
Related Features
24-37


due 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.
Usage
This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests
due to flush LL received by RANPS.
Measurement Point
reported by RANUMC, if the cause of release is flush LL, and EGPRS DL TBF exists, the
Unit
Times

due to EGPRS suspend requests
Definition
Number of EGPRS DL TBF release due to EGPRS suspend requests.
Description
This counter counts the number of EGPRS DL TBF release due to EGPRS suspend
requests.
24-38

Usage
due to suspend requests received by RANPS.
Measurement Point
reported by RANUMC, if the cause of release is SUSPEND, and EGPRS DL TBF exists,
Figure 24-36 - Release Request Due To Suspend Request
Unit
Times
24.44 C901180049 Number of EGPRS DL TBF forcing

release by CS
Definition
Number of EGPRS DL TBF forcing release by CS.
Description
This counter counts the number of EGPRS DL TBF forcing release by CS due to PDCH
REL.
Usage
(EV_RANCCM_PDCH_REL) received by RANPS.
Measurement Point
When RANPS module receives Release Request message (EV_RANCCM_PDCH_REL)
reported by RANCCM module, if EGPRS DL TBF exists, the counter increments. The
24-39

Figure 24-37 - Release Request Due To PDCH REL
Unit
Times
24.45 C901180050 Number of EGPRS DL TBF normal

Definition
Number of EGPRS DL TBF normal release due to user plane requests.
Description
This counter counts the number of EGPRS DL TBF abnormal release due to abnormal
Usage
Measurement Point
by MAC, if the cause of release is abnormal Release Request by MAC, and EGPRS DL
TBF exists, the counter increments. The measurement point is A, as shown inFigure 24-38.
Figure 24-38 - Release Request due to Normal Release Request by MAC
Unit
Times
24-40

24.46 C901180051 Number of EGPRS DL TBF abnormal

Definition
Number of EGPRS DL TBF abnormal release due to user plane requests
Description
This counter counts the number of EGPRS DL TBF abnormal release due to abnormal
Usage
Measurement Point
by MAC, if the cause of release is abnormal Release Request by MAC, and EGPRS DL
Figure 24-39 - Release Request due to Abnormal Release Request by MAC
Unit
Times

Definition
Number of EGPRS DL TBF release due to NSVC unavailability.
Description
This counter counts the number of EGPRS DL TBF release due to NSVC unavailability.
24-41

Usage
due to NSVC unavailability received by RANPS.
Measurement Point
reported by RANUMC, if the cause of release is NSVC unavailability, and EGPRS DL TBF
exists, the counter increments. The measurement point is A, as shown inFigure 24-40.
Figure 24-40 - Release Request due to NVSC Unavailability
Unit
Times

Definition
Number of EGPRS DL TBF release due to BVC unavailability.
Description
This counter counts the number of EGPRS DL TBF release due to BVC unavailability.
Usage
due to BVC unavailability received by RANPS.
Measurement Point
reported by RANUMC, if the cause of release is BVC unavailability, and EGPRS DL TBF
24-42

Unit
Times

Definition
Number of EGPRS DL TBF release due to other reasons.
Description
This counter counts the number of EGPRS DL TBF release due to other reasons.
Usage
due to other reasons received by RANPS.
Measurement Point
reported by RANUMC, if the reason of release is others, and EGPRS DL TBF exists, the
counter increments. The measurement point is A, as shown inFigure 24-42 .
Unit
Times
24-43

24.50 C901180055 Number of DL 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 Point
During the downlink EGPRS TBF establishment and resource adjustment process, if
the resource request succeeds and the other TBF resources is grabbed, the counter
Figure 24-43 Downlink EGPRS Requesting Resource Successfully
Unit
Times
Related Features
24.51 C901180056 Number of grab instance by DL

EGPRS TBF
Description
This counter counts the number of instances grabbed by downlink EGRPS TBF.
24-44

Usage
The counter is used to find out the frequency of downlink EGPRS TBF grabbing other TBF
resources.
Measurement Point
During the downlink EGPRS TBF establishment and resource adjustment process, if the
resource request succeeds and the other TBF resources is grabbed, the counter counts
the number of grabbed instances. The measurement point is A, as shown in Figure 24-44.
Unit
Times
Related Features
24.52 C901180057 Number of DL EGPRS TBF queuing

Description
This counter counts the number of downlink EGRPS TBF's queuing.
Usage
The counter is used to find out the frequency of downlink EGPRS TBF's queuing.
Measurement Point
During the downlink EGPRS TBF establishment and resource adjustment process, if the
resource request succeeds but it can not guarantee queuing at the QoS rate, the counter
24-45

Unit
Times
Related Features
24.53 C901180058 Number of DL EGPRS TBF queuing

success
Description
This counter counts the number of downlink EGRPS TBF's queuing success.
Usage
The counter is used to find out the frequency of downlink EGPRS TBF's queuing success.
Measurement Point
During the downlink EGPRS TBF establishment and resource adjustment process, when
the queuing instance assigns resource to the user plane successfully and registers in
database successfully, the counter increments. The measurement point is A, as shown
in Figure 24-46.
Figure 24-46 Assigning Resource Successfully
24-46

Unit
Times
Related Features
24.54 C901180059 Number of DL EGPRS TBF release

TBF during queuing
Description
This counter counts the number of downlink EGRPS TBF's releasing TBF during queuing.
Usage
The counter is used to find out the frequency of downlink EGPRS TBF's releasing TBF
during queuing.
Measurement Point
When the downlink EGPRS TBF releases TBF, if the instance is still in queuing status, the
Figure 24-47 Releasing Downlink EGPRS TBF
Unit
Times
Related Features
24-47

24-48

Chapter 25
Uplink GPRS Data TBF
Statistics
Table of Contents
Overview ..................................................................................................................25-4
C901190002 Number of GPRS UL TBF establishment requests on CCCH...............25-4
C901190003 Number of EGPRS UL TBF establishment requests on CCCH ............25-5
C901190004 Number of GPRS UL TBF establishment requests on PCCCH ............25-5
C901190005 Number of EGPRS UL TBF establishment requests on PCCCH ..........25-6
C901190006 Number of GPRS UL TBF establishment requests on PACCH.............25-6
C901190007 Number of cell attempts for UL assignment due to ONE PHASE
access......................................................................................................................25-7
C901190008 Number of cell attempts for UL assignment due to single block packet
access......................................................................................................................25-9
C901190009 Number of cell attempts for UL assignment due to response paging ....25-9
C901190010 Number of cell attempts for UL assignment due to cell updating ........25-10
C901190011 Number of cell attempts for UL assignment due to mobility
management .......................................................................................................... 25-11
C901190012 Number of cell attempts for UL assignment due to TWO PHASE
access....................................................................................................................25-12
C901190013 Number of cell attempts for UL assignment due to short access ........25-13
C901190015 Number of GPRS UL TBF establishment failure due to Abis
congestion..............................................................................................................25-14
C901190016 Number of GPRS UL TBF establishment failure due to RR
congestion..............................................................................................................25-16
C901190017 Number of GPRS UL TBF establishment failure due to UPPB-DSP
channel congestion ................................................................................................25-17
C901190018 Number of GPRS UL TBF establishment channel allocate success ...25-19
C901190019 Number of cell success for GPRS UL assignment due to ONE PHASE
access....................................................................................................................25-20
C901190020 Number of cell success for GPRS UL assignment due to single block
packet access ........................................................................................................25-22
C901190021 Number of cell success for GPRS UL assignment due to response
paging ....................................................................................................................25-23
C901190022 Number of cell success for GPRS UL assignment due to cell
updating .................................................................................................................25-23
C901190023 Number of cell success for GPRS UL assignment due to mobility
management ..........................................................................................................25-24
25-1

C901190024 Number of cell success for GPRS UL assignment due to TWO

PHASE access.......................................................................................................25-25
C901190025 Number of cell success for GPRS UL assignment due to short
access....................................................................................................................25-26
C901190026 Number of allocated PDCH for GPRS UL TBF establishment ............25-27
C901190027 Number of GPRS UL TBF establishment failure due to channel
activate failed .........................................................................................................25-29
C901190028 Number of GPRS UL TBF establishment failure due to BTS
C901190029 Number of GPRS UL TBF establishment failure due to BIU connection
failed ......................................................................................................................25-31
C901190030 Number of GPRS UL TBF channel activate establishment success ...25-32
C901190031 Number of GPRS UL TBF establishment failure due to not receive
PIA .........................................................................................................................25-32
C901190032 Number of GPRS UL TBF establisment failure on PCCCH/CCCH due
to UPPB-DSP congestion.......................................................................................25-33
C901190033 Number of GPRS UL TBF establisment failure on PACCH due to
C901190034 Number of GPRS UL TBF establishment success on PCCCH/CCCH .25-34
C901190035 Number of GPRS UL TBF establishment success on PACCH ...........25-36
C901190038 Number of GPRS UL TBF resource reallocation failure due to Abis
congestion for DL TBF establishment .....................................................................25-36
C901190039 Number of GPRS UL TBF resource reallocation failure due to RR
UPPB-DSP channel congestion for DL TBF establishment.....................................25-38
C901190041 Number of GPRS UL TBF resource reallocation success due to DL
C901190042 Number of allocated PDCH for GPRS UL TBF resource reallocation
due to DL TBF establishment .................................................................................25-40
C901190043 Number of GPRS UL TBF resourse reallocation failure due to channel
activate failure for DL TBF establishment ...............................................................25-41
C901190044 Number of GPRS UL TBF resourse reallocation failure due to BTS
connection failure for DL TBF establishment ..........................................................25-42
C901190045 Number of GPRS UL TBF resourse reallocation failure due to BIU
C901190046 Number of GPRS UL TBF resource reallocation success of channel
activate and connection for DL TBF establishment .................................................25-44
C901190047 Number of GPRS UL TBF resourse reallocation failure due to DL TBF
establishment .........................................................................................................25-45
C901190048 Number of GPRS UL TBF resourse reallocation success due to DL
25-2

Chapter 25 Uplink GPRS Data TBF Statistics

C901190054 Number of GPRS UL TBF resource reallocation success due to LLC
transmission ...........................................................................................................25-49
activate failure for LLC transmission .......................................................................25-51
C901190059 Number of GPRS UL TBF resourse reallocation success of channel
activate for LLC transmission .................................................................................25-54
C901190060 Number of GPRS UL TBF resourse reallocation failure due to LLC
transmission ...........................................................................................................25-54
C901190061 Number of GPRS UL TBF resourse reallocation success due to LLC
transmission ...........................................................................................................25-55
C901190062 Number of GPRS UL TBF resource reallocation requests for resource
request...................................................................................................................25-55
congestion for resource request .............................................................................25-55
UPPB-DSP channel congestion for resource request .............................................25-58
C901190067 Number of GPRS UL TBF resource reallocation success due to
resource request ....................................................................................................25-59
due to resource request..........................................................................................25-60
activate failure for resource request........................................................................25-61
connection failure for resource request...................................................................25-62
C901190072 Number of GPRS UL TBF resource reallocation success of channel
activate and connection for resource request .........................................................25-64
C901190073 Number of GPRS UL TBF resourse reallocation failure due to
C901190074 Number of GPRS UL TBF resourse reallocation success due to
C901190075 Number of GPRS UL TBF release due to flush LL .............................25-65
25-3

C901190076 Number of GPRS UL TBF release due to GPRS suspend requests...25-66

C901190077 Number of GPRS UL TBF forcing release by CS ...............................25-67
C901190078 Number of GPRS UL TBF normal release due to user plane
requests .................................................................................................................25-68
C901190079 Number of GPRS UL TBF abnormal release due to user plane
requests .................................................................................................................25-68
C901190080 Number of GPRS UL TBF release due to NSVC unavailability...........25-69
C901190081 Number of GPRS UL TBF release due to BVC unavailability .............25-70
C901190082 Number of GPRS UL TBF release due to other reasons ....................25-71
C901190083 Number of UL GPRS TBF grab resources .........................................25-71
C901190084 Number of grab instance by UL GPRS TBF.......................................25-72
C901190085 Number of UL GPRS TBF queuing ....................................................25-73
C901190086 Number of UL GPRS TBF queuing success ......................................25-74
C901190087 Number of UL GPRS TBF release TBF during queuing .....................25-75
25.1 Overview
UL GPRS data TBF statistics collects the information about the establishment, maintain
and release of UL GPRS TBF. The statistic unit is cell.

establishment requests 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.
Usage
This counter is used to find out the frequency of channel requests on CCCH when MS
attempts using GPRS service.
Measurement Point
When BSC receives channel requests on CCCH from MS, the counter increments. The
25-4

Figure 25-1 - Channel Request
Usage
Times

Definition
Number of EGPRS UL TBF establishment requests on CCCH.
Description
This counter is not meaningful in UL GPRS TBF and is not used.

establishment requests on PCCCH
Definition
Number of GPRS UL TBF establishment requests on PCCCH.
Description
This counter counts the number of packet channel requests on PCCCH when MS attempts
using GPRS service.
Usage
This counter is used to find out the frequency of channel requests on PCCCH when MS
attempts using GPRS service.
25-5

Measurement Point
When BSC receives channel requests on PCCCH from MS, the counter increments. The
Figure 25-2 - Packet Channel Request
Unit
Times

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.

Definition
Number of GPRS UL TBF establishment requests on PACCH.
Description
The counter counts the number of UL GPRS TBF establishment attempts on PACCH.
25-6

Usage
This counter is used to find out the number of UL GPRS TBF establishment attempts on
PACCH under the situation when DL GPRS TBF is already established.
Measurement Point
In the situation when DL GPRS TBF is established, PS control plane receives UL
assignment request message from PS user plane, the counter increments. The
Figure 25-3 - Packet Channel Request
Unit
Times
25.7 C901190007 Number of cell attempts for UL

assignment due to ONE PHASE access
Definition
Number of cell attempts for UL assignment due to ONE PHASE access
Description
This counter counts the number of channel requests on CCCH when MS attempting UL
GPRS TBF establishment or the number of packet channel requests on PCCCH due to
one phase access.
Usage
This counter is used to find out the number of UL GPRS TBF establishment attempts due
to one phase access.
25-7

Measurement Point
The counter accumulates at the following two time points:
l If BSC receives channel requests from MS on CCCH due to one phase access, the
Figure 25-4 - Channel Requests on CCCH due to One Phase Access
Figure 25-5 - Packet Channel Requests on CCCH due to One Phase Access
Unit
Times
Related Features
25-8


assignment due to single block packet access
Definition
Number of cell attempts for UL assignment due to single block packet access.
Description
UL GPRS TBF establishment due to single block packet access.
Usage
This counter is used to find out the number of packet channel requests when MS attempting
UL GPRS TBF establishment due to single block packet access.
Measurement Point
If BSC receives channel requests on PCCCH from MS due to single block packet access.
Figure 25-6 - Channel Request due to Single Block Packet Access
Unit
Times

assignment due to response paging
Definition
Number of cell attempts for UL assignment due to response paging.
25-9

Description
This counter counts the number of packet channel requests when MS attempting UL GPRS
TBF establishment due to response paging.
Usage
UL GPRS TBF establishment due to response paging.
Measurement Point
When BSC receives channel requests on PCCCH from MS due to response paging, the
Figure 25-7 - Channel Request Due To Response Paging
Unit
Times

assignment due to cell updating
Definition
Number of cell attempts for UL assignment due to cell updating.
Description
This counter counts the number of packet channel requests when MS attempting UL GPRS
TBF establishment due to cell update.
Usage
UL GPRS TBF establishment due to cell update.
25-10

Measurement Point
When BSC receives channel requests on PCCCH from MS duet to cell update, the counter
Figure 25-8 - Channel Requests due to Cell Update
Unit
Times

assignment due to mobility management
Definition
Number of cell attempts for UL assignment due to mobility management
Description
The counter counts the number of packet channel requests on PCCCH when MS
attempting UL GPRS TBF establishment due to mobile management.
Usage
UL GPRS TBF establishment due to mobile management.
Measurement Point
If BSC receives channel requests on PCCCH from MS due to mobile management, the
25-11

Figure 25-9 - Channel Request Due To Mobile Management
Unit

assignment due to TWO PHASE access
Definition
Number of cell attempts for UL assignment due to TWO PHASE access
Description
GPRS TBF establishment or the number of packet channel requests on PCCCH due to
two phase access.
Usage
to two phase access.
Measurement Point
l If BSC receives channel requests from MS on CCCH due to two phase access, the
25-12

Figure 25-10 - Channel Requests On PCCCH Due To Two Phase Access
Figure 25-11 - Packet Channel Requests On PCCCH Due To Two Phase Access
Unit
Times
Related Features
GB-03-05-008 Two Phase Access

assignment due to short access
Definition
Number of cell attempts for UL assignment due to short access.
Description
This counter counts the number of packet channel requests on PCCCH when MS
attempting UL GPRS TBF establishment due to short access.
25-13

Usage
to short access.
Measurement Point
If BSC receives packet channel requests on PCCCH from MS on PCCCH due to short
access, the counter increments. The measurement point is A, as shown inFigure 25-12.
Figure 25-12 - Packet Channel Requests On PCCCH Due To Short Access
Unit
Times

Definition
Number of GPRS UL TBF establishment failure due to Abis congestion.
Description
The counter records the number of DB resource application failure when attempting UL
GPRS TBF establishment due to Abis congestion.
Usage
This counter is used to find out the number of DB resource application failure when
attempting UL GPRS TBF establishment due to Abis congestion.
Measurement Point
The counter accumulates at the following three time points:
25-14

l If PS control plane receives channel requests from MS on CCCH and fails to apply
for DB resource due to Abis congestion, the counter increments. The measurement
Figure 25-13 - DB Resource Requests Failure Due To Abis Congestion (CCCH)
l If PS control panel receives channel requests from MS on CCCH and fails to apply
for DB resource due to Abis congestion, the counter increments. The measurement
Figure 25-14 - DB Resource Requests Failure Due To Abis Congestion (PCCCH)
l 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
Figure 25-15 - DB Resource Requests Failure Due To Abis Congestion (DL GPRS
TBF Already Established)
Unit
Times
25-15

Related Features

Definition
Number of GPRS UL TBF establishment failure due to RR congestion.
Description
The counter records the number of DB resource request failure when attempting UL GPRS
TBF establishment due to radio resource congestion. There are three causes that lead
to radio resource congestion: MS per channel (MS number on each channel reaches its
maximum), no TAI/TFI, and no PDCH.
Usage
attempting UL GPRS TBF establishment due to RR congestion.
Measurement Point
for DB resource due to RR congestion, the counter increments. The measurement
Figure 25-16 - DB Resource Requests Failure Due To RR Congestion (CCCH)
l If PS control panel receives channel requests from MS on CCCH and fails to apply
for DB resource due to RR congestion, the counter increments. The measurement
25-16

Figure 25-17 - DB Resource Requests Failure Due To RR Congestion (PCCCH)

on CCCH and fails to apply for DB resource due to RR congestion, the counter
Unit
Times
Related Features

congestion
Definition
Number of GPRS UL TBF establishment failure due to UPPB-DSP channel congestion.
Description
GPRS TBF establishment due to UPPB-DSP channel congestion.
25-17

Usage
attempting UL GPRS TBF establishment due to UPPB-DSP channel congestion.
Measurement Point
for DB resource due to UPPB-DSP channel congestion, the counter increments. The
Figure 25-19 DB Resource Requests Failure Due To UPPB-DSP Channel

Congestion (CCCH)
l If PS control panel receives channel requests from MS on PCCCH and fails to apply
for DB resource due to UPPB-DSP channel congestion, the counter increments. The
Figure 25-20 - DB Resource Requests Failure Due To Abis Congestion (PCCCH)

on CCCH (DL GPRS TBF already established) and fails to apply for DB resource
due to UPPB-DSP congestion, the counter increments. The measurement point
25-18

Figure 25-21 - DB Resource Requests Failure Due To DPPB-DSP Congestion (DL

GPRS TBF Already Established)
Unit
Times
Related Features

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.
Measurement Point
l If PS control plane receives channel requests from MS on CCCH and succeeds in

applying for DB resource, the counter increments. The measurement point is A, as
25-19

Figure 25-22 - DB Resource Request Successes (CCCH)
l If PS control panel receives channel requests from MS on PCCCH and succeed in

applying for DB resource, the counter increments. The measurement point is A, as
Figure 25-23 - DB Resource Request Successes (PCCCH)
l If only GPRS is supported in the network, PS control plane receives EGPRS channel
request on CCCH or on PCCCH from MS, and DB resource request succeeds,
Unit
Times
Related Features
25.18 C901190019 Number of 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.
25-20

Description
This counter counts the number of successful UL GPRS TBF establishment due to one
phase access.
Usage
This counter is used to find out the number of UL GPRS TBF establishment successes
due to one phase access.
Measurement Point
l If PS control plane receives channel requests from MS on CCCH due to one

phase access and DB resource requests succeeds, the counter increments. The
Figure 25-24 - Channel Request Successes On CCCH Due To One Phase Access
Figure 25-25 - Packet Channel Request Successes On CCCH Due To One Phase
Access
25-21

Unit
Times
Related Features
ZGB-03-05-007One Phase Access

UL assignment due to single block packet access
Definition
Number of cell success for GPRS UL assignment due to single block packet access.
Description
The counter counts the number of successful UL GPRS TBF establishment due to single
block packet access.
Usage
This counter is used to find out the number of successful UL GPRS TBF establishment
due to single block packet access.
Measurement Point
If PS control plane receives channel requests on PCCCH from MS due to single
block packet access and DB resource request succeeds, the counter increments. The
Figure 25-26 - Channel Requests Successes Due To Single Block Packet Access
Unit
Times
25-22


UL assignment due to response paging
Definition
Number of cell success for GPRS UL assignment due to response paging.
Description
The counter counts the number of successful UL GPRS TBF establishment due to
response paging.
Usage
due to response paging.
Measurement Point
When PS control plane receives channel requests on PCCCH from MS due to response
paging and DB resource request succeeds, the counter increments. The measurement
Figure 25-27 - DB Resource Request Successes Due To Response Paging
Unit
Times

UL assignment due to cell updating
Definition
Number of cell success for GPRS UL assignment due to cell updation.
25-23

Description
The counter counts the number of successful UL GPRS TBF establishment due to cell
update
Usage
due to cell update.
Measurement Point
When PS control plane receives channel requests on PCCCH from MS due to cell update
and DB resource request succeeds, the counter increments. The measurement point is
A, as shown inFigure 25-28.
Figure 25-28 - DB Resource Request Successes Due To Cell Update
Unit
Times

UL assignment due to mobility management
Definition
Number of cell success for GPRS UL assignment due to mobility management.
Description
The counter counts the number of successful UL GPRS TBF establishment due to mobile
management.
Usage
due to mobile management.
25-24

Measurement Point
If PS control plane receives channel requests on PCCCH from MS due to mobile
management and DB resource request succeeds, the counter increments. The
Figure 25-29 - DB Resource Request Successes Due To Mobile Management (PCCCH)
Unit
Times

UL assignment due to TWO PHASE access
Definition
Number of cell success for GPRS UL assignment due to TWO PHASE access.
Description
This counter counts the number of successful UL GPRS TBF establishment due to two
phase access.
Usage
due to two phase access.
Measurement Point
l If BSC receives channel requests from MS on CCCH due to two phase access and
DB resource request succeeds, the counter increments. The measurement point
25-25

Figure 25-30 - DB Resource Request Successes Due To Two Phase Access (CCCH)
l If BSC receives channel requests from MS on PCCCH due to two phase access and
DB resource request succeeds, the counter increments. The measurement point
Figure 25-31 - DB Resource Request Successes On PCCCH Due To Two Phase

Access
Unit
Times
Related Features
ZGB-03-05-008Two Phase Access

UL assignment due to short access
Definition
Number of cell success for GPRS UL assignment due to short access.
25-26

Description
This counter counts the number of successful UL GPRS TBF establishment due to short
access.
Usage
due to short access.
Measurement Point
l If BSC receives channel requests from MS on CCCH due to short access and DB
resource request succeeds, the counter increments. The measurement point is A,
Figure 25-32 - DB Resource Request Successes Due To Short Access (PCCCH)
l If only GPRS is supported in the network, PS control plane receives GPRS channel
Unit
Times

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

Usage
This counter is used to find out the number of successfully assigned PDTCH when UL
GPRS TBF successfully established.
Measurement Point
l When PS control plane receives channel requests on CCCH from MS and DB

resource requests succeed, the counter increments. The measurement point is A,
Figure 25-33 - DB Resource Request Successes Due To Short Access (PCCCH)
l When PS control plane receives packet channel requests on PCCCH from MS, the
Figure 25-34 - UL GPRS TBF Establishment On PCCCH/CCCH
25-28

Unit
Times
Related Features

Definition
Number of GPRS UL TBF establishment failure due to channel activate failed.
Description
This counter counts the number of PDTCH activate failure when establishing UL GPRS
TBF.
Usage
This counter is used to find out the number of PDTCH activate failure when establishing
UL GPRS TBF (including initially establish UL TBF and establish UL TBF when DL TBF
exists).
Measurement Point
l When BSC receives PDTCH channel activate failure message reported by BTS, the
l When 'wait for PDTCH channel activation and connection response' counter times
out and BSC fails to receive PDTCH activate response message reported by BTS,
25-29

Unit
Times

Definition
Number of GPRS UL TBF establishment failure due to BTS connection failed.
Description
This counter counts the number of failure to establish UL GPRS TBF due to BTS
connection failure.
Usage
This counter is used to find out the number of UL GPRS TBF establishment failure
(including initially establish UL TBF and establish UL TBF when DL TBF exists) due to
BTS connection failure.
Measurement Point
l When PS control plane receives connection failure message reported by connection

module due to BTS connection failure, the counter increments. The measurement
l When 'wait for PDTCH channel activate and connection response' counter times
out and BSC fails to receive connection success response message reported by
connection module, this counter increments.
Unit
Times
25-30


Definition
Number of GPRS UL TBF establishment failure due to BIU connection failed.
Description
This counter counts the number of failure to establish UL GPRS TBF due to BIU connection
failure.
Usage
This counter is used to find out the number of UL GPRS TBF establishment failure
BIU connection failure.
Measurement Point
When PS control plane receives connection failure message reported by connection
modules due to BIU connection failure, the counter increments. The measurement point
Usage
Times
25-31

25.29 C901190030 Number of GPRS UL TBF channel

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 Point
When PS control plane receives channel activate response message reported by BTS
and connection successes acknowledgement message reported by connection module,

Adjustment)
Unit
Times

establishment failure due to not receive PIA
Definition
Number of GPRS UL TBF establishment failure due to not receive PIA.
25-32

Description
This counter counts the number of failure to send immediate assignment message to MS
when establishing UL GPRS TBF.
Usage
This counter is used to find out the number of failure to send immediate assignment
message to MS when establishing UL GPRS TBF.
Measurement Point
l When PS control plane receives immediate assignment failure message reported by
BTS, the counter increments.
l When 'wait for immediate assignment and sending indication' counter times out
and BSC fails to receive immediate assignment and sending indication message,
Usage
Times

establisment failure on PCCCH/CCCH due to
UPPB-DSP congestion
Definition
Number of GPRS UL TBF establishment failure on PCCCH/CCCH due to UPPB-DSP
congestion.
Description
This counter counts the number of failure to establish UL GPRS TBF.
Usage
This counter is used to find out the number of failure to establish UL GPRS TBF.
Measurement Point
When PS control plane assigns single block through two phase access from PS user plane,
or gets access to PS user plane through one phase access and starts assignment timer.
If the timer times out, resource request from PS user plane (two phase access) is not
received or indication (one phase access) is not established, the counter increments. The
25-33

Unit
Times

establisment failure on PACCH due to UPPB-DSP
congestion
Definition
Number of GPRS UL TBF establishment failure on PACCH due to UPPB-DSP congestion.
Description
This counter is not used currently.

Definition
Number of GPRS UL TBF establishment success on PCCCH/CCCH
Description
This counter counts the number of successful UL GPRS TBF establishment and receiving
MS TLL1.
25-34

Usage
and receiving MS TLL1.
Measurement Point
l 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
Figure 25-40 - UL One-Phase-Access Resource Assignment Successes
l PS control plane receives resource request message from PS user plane in the
premise of two phase access, the counter increments. The measurement point is
A, as shown inFigure 25-41 .
Figure 25-41 - UL Two-Phase-Access Single Block Assignment Successes
Unit
Times
25-35


Definition
Number of GPRS UL TBF establishment success on PACCH.
Description

reallocation failure due to 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 reallocation failure due to
Abis congestion.
Measurement Point
In the situation when UL GPRS TBF is established, PS control plane receives DL
assignment request message from PS user plane, and DB resource request fails due to
Abis congestion, the counter increments. The measurement point is A, as shown inFigure
25-42 .
25-36

Figure 25-42 - Database Application Failure Due To Abis Congestion
Unit
Times
Related Features

reallocation failure due to RR congestion for DL
TBF establishment
Definition
Number of GPRS UL TBF resource reallocation failure due to RR congestion for DL TBF
establishment.
Description
failure. The counter 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.
Usage
RR congestion.
25-37

Measurement Point
RR congestion, the counter increments. The measurement point is A, as shown inFigure
25-43.
Figure 25-43 - Database Application Failure due to RR Congestion
Unit
Times
Related Features

congestion for DL TBF establishment
Definition
Number of GPRS UL TBF resource reallocation failure due to UPPB -DSP channel
congestion for DL TBF establishment.
Description
failure. The counter records the number of UL resource reallocation failure due to
UPPB-DSP channel resource congestion.
Usage
UPPB-DSP channel congestion.
25-38

Measurement Point
UPPB-DSP channel congestion, the counter increments. The measurement point is A, as
Unit
Times
Related Features

reallocation success due to DL TBF establishment
Definition
Number of GPRS UL TBF resource reallocation success due to DL TBF establishment.
Description
The counter records the number of successful DL TBF establishment on PACCH when UL
GPRS TBF is already established.
Usage
This counter is used to find out the number of DL GPRS TBF reallocation successes.
Measurement Point
assignment request message from PS user plane, and DB resource request succeeds,
25-39

Unit
Times
Related Features

GPRS UL TBF resource reallocation due to DL TBF
establishment
Definition
Number of allocated PDCH for GPRS UL TBF resource reallocation success due to DL
TBF establishment.
Description
The counter records the number of successful allocated PDTCH when UL GPRS TBF is
successfully reallocated.
Usage
This counter is used to find out the number of successful allocated PDTCH when UL GPRS
TBF is successfully reallocated.
Measurement Point
25-40

Unit
Times
Related Features
25.40 C901190043 Number of GPRS UL TBF resourse

for DL TBF establishment
Definition
Number of GPRS UL TBF resource reallocation failure due to channel activate failure for
Description
The counter records the number of PDTCH activate failure during UL GPRS TBF resource
reallocation.
Usage
This counter is used to find out the number of PDTCH activate failure during UL GPRS
Measurement Point
l When BSC receives PDTCH channel activate failure message from BTS, the counter
25-41

Figure 25-47 - PDTCH Activation Failure
l When 'Wait for PDTCH channel activation and connection response' timer times
out, and BSC fails to receive PDTCH channel activate response message from
Unit
Times

Definition
Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for
Description
The counter records the number of BTS connection failure during UL GPRS TBF resource
reallocation.
Usage
This counter is used to find out the number of BTS connection failure during UL GPRS
Measurement Point
l When PS control plane receives connection failure message from connection

point is A, as shown inFigure 25-48 .
25-42

l When 'Wait for PDTCH channel activation and connection response' timer times out,
and BSC fails to receive connection success message from connection module,
Unit
Times

Definition
Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for
Description
The counter records the number of BIU connection failure during UL GPRS TBF resource
reallocation.
Usage
This counter is used to find out the number of BIU connection failure during UL GPRS TBF
resource reallocation.
Measurement Point
When PS control plane receives connection failure message from connection module due
to BIU connection failure, the counter increments. The measurement point is A, as shown
inFigure 25-49.
25-43

Unit
Times

connection for DL TBF establishment
Definition
Number of GPRS UL TBF resource reallocation success of channel activate and
Description
The counter records the number of channel activate and connection successes during UL
GPRS TBF resource reallocation.
Usage
during UL GPRS TBF resource reallocation.
Measurement Point
When PS control plane receives channel activate ack message and connection success
ack message from connection module due to BIU connection failure, the counter
25-44


Adjustment)
Unit
Times

Definition
Number of GPRS UL TBF resource reallocation failure due to DL TBF establishment.
Description
Related Features

Definition
Number of GPRS UL TBF resource reallocation success due to DL TBF establishment.
Description
Related Features
25-45


transmission
Definition
Number of GPRS UL TBF resource reallocation failure due to Abis congestion for LLC
transmission
Description
During UL GPRS TBF transmission process, PS user plane sends resource reallocation
message to PS control plane due to LLC frame change; PS control plane requests DB
resource after receiving the message. The counter records the number of DB resource
request failure due to Abis resource congestion after PS control plane receiving resource
reallocation request during UL GPRS TBF transmission process.
Usage
This counter is used to find out DB resource request failure due to Abis resource
congestion after PS control plane receiving resource reallocation request during UL
GPRS TBF transmission process.
Measurement Point
When PS control plane receives resource reallocation message from PS user plane,
and DB resource request fails due to Abis congestion, the counter increments. The
Figure 25-51 - Resource Application Failure Due To Abis Congestion
Unit
Times
Related Features
25-46


transmission
Definition
Number of GPRS UL TBF resource reallocation failure due to RR congestion for LLC
transmission
Description
During UL GPRS TBF transmission process, PS user plane sends resource reallocation
request failure due to radio resource congestion after PS control plane receiving resource
reallocation request during UL EGPRS TBF transmission process.
There are three causes leading to RR congestion: MS per channel (reaches its maximum),
TAI/TFI (not available), and no PDTCH.
Usage
This counter is used to find out DB resource request failure due to RR congestion after PS
control plane receiving resource reallocation request during UL EGPRS TBF transmission
process.
Measurement Point
and DB resource request fails due to RR congestion, the counter increments. The

Adjustment)
Unit
Times
25-47

Related Features

Definition
Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel
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 message. The counter records the number of DB resource
request failure due to UPPB-DSP channel congestion after PS control plane receiving
resource reallocation request during UL GPRS TBF transmission process.
Usage
This counter is used to find out DB resource request failure due to UPPB-DSP channel
congestion after PS control plane receiving resource reallocation request during UL GPRS
TBF transmission process.
Measurement Point
When PS control plane receives resource reallocation message from PS user plane, and
DB resource request fails due to UPPB-DSP channel congestion, the counter increments.
Figure 25-53 - Resource Application Failure Due To UPPPB-DSP Channel Congestion

25-48

Unit
Times
Related Features

Definition
Number of GPRS UL TBF resource reallocation success due to LLC transmission
Description
request successes after PS control plane receiving resource reallocation request during
UL EGPRS TBF transmission process.
Usage
This counter is used to find out DB resource request success due after PS control plane
receiving resource reallocation request during UL EGPRS TBF transmission process.
Measurement Point
DB resource request succeeds, the counter increments. The measurement point is A, as
Unit
Times
25-49

Related Features

GPRS UL TBF resource reallocation due to LLC
transmission
Definition
Number of allocated PDTCH for GPRS UL TBF resource reallocation due to LLC
transmission.
Description
resource after receiving the message. The counter records the number of successfully
allocated PDTCH after PS control plane receiving resource reallocation requests during
UL GPRS TBF.
Usage
This counter is used to find out the number of successful allocated PDTCH when UL GPRS
TBF is successfully reallocated.
Measurement Point
Unit
Times
Related Features
25-50


Definition
DL TBF establishment
Description
The counter records the number of PDTCH activate failure after BSC receiving resource
reallocation request during UL GPRS TBF resource reallocation.
Usage
This counter is used to find out the number of PDTCH activate failure during UL GPRS
Measurement Point
Unit
Times
25-51


Definition
Number of GPRS UL TBF resource reallocation failure due to BTS connection failure for
LLC transmission
Description
The counter records the number of connection failure due to BTS connection failure after
BSC receiving resource reallocation request during UL GPRS TBF transmission.
Usage
This counter is used to find out the number of BTS connection failure during UL GPRS
TBF resource transmission.
Measurement Point
Unit
Times
25-52


Definition
Number of GPRS UL TBF resource reallocation failure due to BIU connection failure for
LLC transmission.
Description
The counter records the number of BIU connection failure during UL GPRS TBF
transmission.
Usage
This counter is used to find out the number of BIU connection failure during UL GPRS TBF
transmission.
Measurement Point
inFigure 25-58.
Figure 25-58 - Connection Failed due to BIU Connection Failure
Unit
Times
25-53


reallocation success of channel activate for LLC
transmission
Definition
Number of GPRS UL TBF resource reallocation success of channel activate for LLC
transmission.
Description
GPRS TBF transmission.
Usage
during UL GPRS TBF tranmission.
Measurement Point
Unit
Times

Definition
Number of GPRS UL TBF resource reallocation failure due to LLC transmission.
25-54

Description
Related Features

Definition
Number of GPRS UL TBF resource reallocation success due to LLC transmission.
Description
Related Features

Definition
Number of GPRS UL TBF resource reallocation requests for resource request.
Description

reallocation failure due to Abis congestion for
resource request
Definition
Number of GPRS UL TBF resource reallocation failure due to Abis congestion for resource
request
25-55

Description
The counter records the number of DB resource request failure due to Abis congestion
after PS control plane resource request from MS during UL GPRS TBF.
Usage
This counter is used to find out the number of DB resource request failure after PS control
plane receives resource request from MS during UL GPRS TBF process (including UL
two-phase access and UL TBF transmission).
Measurement Point
PS control plane receives resource request message from PS user plane, and DB resource
request fails due to Abis congestion, the counter increments. The measurement point is
Figure 25-60 - DB Resource Requests Failure Due To Abis Congestion (Resource

Request)
Unit
Times
Related Features

reallocation failure due to RR congestion for
resource request
Definition
Number of GPRS UL TBF resource reallocation failure due to RR congestion for resource
request.
25-56

Description
The counter records the number of DB resource request failure after PS control plane
receives resource request from MS due to RR congestion during UL GPRS TBF.
There are three cause leading to radio resource congestion: MS per channel (MS number
per channel reaches its maximum), TAI/TFI (no TAI/TFI available), no PDCH (no PS
service channel available)
Usage
plane receives resource request from MS due to RR congestion during UL GPRS TBF
process (including UL two-phase access and UL TBF transmission).
Measurement Point
request fails due to RR congestion, the counter increments. The measurement point is A,
Figure 25-61 - DB Resource Requests Failure Due To RR Congestion
Unit
Times
Related Features
25-57


congestion for resource request
Description
receives resource request from MS due to UPPB-DSP channel congestion during UL
GPRS TBF.
Usage
plane receives resource request from MS due to UPPB-DSP channel congestion during
UL GPRS TBF process (including UL two-phase access and UL TBF transmission).
Measurement Point
Figure 25-62 DB Resource Requests Failure due to UPPB-DSP Channel Congestion

(Resource Request)
Unit
Times
Related Features
25-58


reallocation success due to resource request
Description
The counter records the number of successful DB resource request after PS control plane
receives resource request message from MS during UL GPRS TBF process.
Usage
This counter is used to find out the number of DB resource request successes after PS
control plane receives resource request from MS during UL GPRS TBF process (including
UL two-phase access and UL TBF transmission).
Measurement Point
request succeeds, the counter increments. The measurement point is A, as shown in
Figure 25-63.
Figure 25-63 DB Resource Requests Successes (Resource Request)
Unit
Times
Related Features
25-59


UL TBF resource reallocation due to resource
request
Description
The counter records the number of successful allocated PDTCH after PS control plane
receives resource request message from MS during UL GPRS TBF process.
Usage
This counter is used to find out the number of successful allocated PDTCH after PS control
plane receives resource request from MS during UL GPRS TBF process (including UL
Measurement Point
Figure 25-64.
Figure 25-64 DB Resource Requests Successes (Resource Request)
Unit
Times
Related Features
25-60


for resource request
Definition
resource request.
Description
reallocation after PS control plane receives resource request message.
Usage
reallocation after PS control plane receives resource request message in UL GPRS TBF
process (including UL two-phase access and one-phase TBF transmission).
Measurement Point
Unit
Times
25-61


Definition
Number of GPRS UL TBF resource reallocation failure due to BTS connection failure for
resource request.
Description
The counter records the number of connection failure due to BTS connection failure during
UL GPRS TBF resource reallocation after PS control plane receives resource request
message.
Usage
message in UL GPRS TBF process (including UL two-phase access and one-phase TBF
transmission).
Measurement Point
point is A, as shown inFigure 25-66 .
Unit
Times
25-62


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 connection failure during
message.
Usage
transmission).
Measurement Point
inFigure 25-67.
Unit
Times
25-63


connection for resource request
Definition
Number of GPRS UL TBF resource reallocation success of channel activate and
Description
The counter records the number of channel activate and connection successes during
message.
Usage
The counter records the number of channel activate and connection failure during UL
GPRS TBF resource reallocation after PS control plane receives resource request
transmission).
Measurement Point

Adjustment)
Unit
Times
25-64


reallocation failure due to resource request
Definition
Number of GPRS UL TBF resource reallocation failure due to resource request.
Description
Related Features

Definition
Number of GPRS UL TBF resource reallocation failure due to reallocation success due to
resource request.
Description
Related Features
25.69 C901190075 Number of GPRS UL TBF release

due 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.
25-65

Usage
This counter is used to find out the number of UL GPRS TBF release after PS control plane
receiving request due to flush LL.
Measurement Point
When PS control plane of BSC receives FLUSH message from SGSN and release is
executed when UL GPRS TBF is established, the counter increments. The measurement
Unit
Times

Definition
Number of GPRS UL TBF release due to GPRS suspend requests.
Description
This counter counts the number of UL GPRS TBF release after PS control plane receiving
request due to GPRS suspend requests.
Usage
This counter is used to find out the number of UL GPRS TBF release due to GPRS suspend
requests.
Measurement Point
When PS control plane of BSC receives SUSPEND message from SGSN and release is
executed when UL GPRS TBF is established, the counter increments. The measurement
25-66

Figure 25-70 - Release Request due to Suspend Request
Unit
Times
25.71 C901190077 Number of GPRS UL TBF forcing

release by CS
Definition
Number of GPRS UL TBF forcing release by CS.
Description
This counter counts the number of UL GPRS TBF forcing release by CS.
Usage
This counter is used to find out the number of UL GPRS TBF forcing release by CS.
Measurement Point
When PS control plane of BSC receives PDCH RELEASE message from CS control plane
when UL GPRS TBF is established, the counter increments. The measurement point is A,
Figure 25-71 - Release Request due to PDCH REL
Unit
Times
25-67

25.72 C901190078 Number of GPRS UL TBF normal

Definition
Number of GPRS UL TBF normal release due to user plane requests.
Description
This counter counts the number of UL GPRS TBF normal release due to user plane
requests.
Usage
This counter is used to find out the number of UL GPRS TBF normal release due to user
plane requests.
Measurement Point
When PS control plane of BSC receives NORMAL RELEASE REQUEST message from PS
user plane when UL GPRS TBF exists, the counter increments. The measurement point
Figure 25-72 - Normal Release Request
Unit
Times
25.73 C901190079 Number of GPRS UL TBF abnormal

Definition
Number of GPRS UL TBF abnormal release due to user plane requests.
Description
This counter counts the number of UL GPRS TBF abnormal release due to user plane
requests.
25-68

Usage
This counter is used to find out the number of UL GPRS TBF abnormal release due to user
plane requests.
Measurement Point
When PS control plane receives ABNORMAL RELEASE REQUEST message from PS user
plane when UL GPRS TBF exists, the counter increments. The measurement point is A,
Figure 25-73 - Release Request due to Abnormal Release Request 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 NSVC unavailability.
Usage
This counter is used to find out the number of UL GPRS TBF release after receiving forcing
release request due to NSVC unavailability.
Measurement Point
When PS control plane receives NSVC unavailability command to release PS control plane
module from DB when UL GPRS TBF exists, the counter increments. The measurement
25-69

Figure 25-74 - 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.
Usage
release request due to BVC unavailability.
Measurement Point
When PS control plane receives BVC unavailability command to release PS control plane
module from DB when UL GPRS TBF exists, the counter increments. The measurement
Unit
Times
25-70


Definition
Number of GPRS UL TBF release due to other reasons.
Description
This counter counts the number of UL GPRS TBF forcing release due to other reasons.
Usage
release request due to other reasons.
Measurement Point
When PS control plane receives release message due to other reasons when UL GPRS
Unit
Times
25.77 C901190083 Number of UL GPRS TBF grab

resources
Definition
Number of UL GPRS TBF grab resources.
25-71

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 Point
This counter increments while UL GPRS TBF is established during resource adjustment,
Figure 25-77 - UL GPRS Resource Request Success
Unit
Times
Related Features
25.78 C901190084 Number of 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.
25-72

Usage
This counter is used to find out the frequency for UL GPRS TBF grabbing other TBF
resource.
Measurement Point
Unit
Times
Related Features
25.79 C901190085 Number of UL GPRS TBF queuing

Definition
Number of UL GPRS TBF queuing.
Description
This counter counts the number of UL GPRS TBF queuing.
Usage
This counter is used to find out the frequency for UL GPRS TBF grabbing other TBF
resource.
25-73

Measurement Point
Measurement point is A as shown inFigure 25-79.
Unit
Times
Related Features
25.80 C901190086 Number of UL GPRS TBF queuing

success
Definition
Number of UL GPRS TBF queuing success.
Description
This counter counts the number of UL GPRS TBF queuing success.
Usage
This counter is used to find out the frequency for UL GPRS TBF queuing success.
Measurement Point
the instance to be queued successfully assigns resource for user plane, and database is
successfully registered. Measurement point is A as shown inFigure 25-80.
25-74

Figure 25-80 - Resource Assignment Success
Unit
Times
Related Features
25.81 C901190087 Number of UL GPRS TBF release

TBF during queuing
Definition
Number of UL GPRS TBF release TBF during queuing.
Description
This counter counts the number of UL GPRS TBF release during queuing.
Usage
This counter is used to find out the frequency for UL GPRS TBF release during queuing.
Measurement Point
This counter increments while UL GPRS TBF is released and instance still in queuing
state. The measurement point is A as shown inFigure 25-81.
25-75

Figure 25-81 - Release UL GPRS TBF
Unit
Times
Related Features
25-76

Chapter 26
Uplink EGPRS Data TBF
Statistics
Table of Contents
Overview ..................................................................................................................26-4
C901200002 Number of GPRS UL TBF establishment requests on CCCH ..............26-4
C901200003 Number of EGPRS UL TBF establishment requests on CCCH ............26-4
C901200004 Number of GPRS UL TBF establishment requests on PCCCH ............26-5
C901200005 Number of EGPRS UL TBF establishment requests on PCCCH..........26-5
C901200006 Number of GPRS UL TBF establishment requests on PACCH ............26-6
C901200007 Number of cell attempts for UL assignment due to ONE PHASE
access......................................................................................................................26-7
C901200008 Number of cell attempts for UL assignment due to single block packet
access......................................................................................................................26-8
C901200009 Number of cell attempts for UL assignment due to response paging....26-9
C901200010 Number of cell attempts for UL assignment due to cell updating..........26-9
C901200011 Number of cell attempts for UL assignment due to mobility
management ............................................................................................................26-9
C901200012 Number of cell attempts for UL assignment due to TWO PHASE
access....................................................................................................................26-10
C901200013 Number of cell attempts for UL assignment due to short access........ 26-11
C901200015 Number of EGPRS UL TBF establishment failure due to Abis
congestion..............................................................................................................26-12
C901200016 Number of EGPRS UL TBF establishment failure due to RR
congestion..............................................................................................................26-14
C901200017 Number of EGPRS UL TBF establishment failure due to UPPB-DSP
channel congestion ................................................................................................26-15
C901200018 Number of EGPRS UL TBF establishment channel allocate success .26-16
C901200019 Number of cell success for EGPRS UL assignment due to ONE
PHASE access.......................................................................................................26-17
C901200020 Number of cell success for EGPRS UL assignment due to single
block packet access ...............................................................................................26-19
C901200021 Number of cell success for EGPRS UL assignment due to response
paging ....................................................................................................................26-19
C901200022 Number of cell success for EGPRS UL assignment due to cell
updating .................................................................................................................26-19
C901200023 Number of cell success for EGPRS UL assignment due to mobility
management ..........................................................................................................26-20
26-1

C901200024 Number of cell success for EGPRS UL assignment due to TWO

PHASE access.......................................................................................................26-20
C901200025 Number of cell success for EGPRS UL assignment due to short
access....................................................................................................................26-21
C901200026 Number of allocated PDCH for EGPRS UL TBF establishment .........26-23
C901200027 Number of EGPRS UL TBF establishment failure due to channel
activate failed .........................................................................................................26-24
C901200028 Number of EGPRS UL TBF establishment failure due to BTS
C901200029 Number of EGPRS UL TBF establishment failure due to BIU
connection failed ...................................................................................................26-26
C901200030 Number of EGPRS UL TBF channel activate establishment success .26-27
C901200031 Number of EGPRS UL TBF establishment failure due to not receive
PIA .........................................................................................................................26-27
C901200032 Number of EGPRS UL TBF establishment failure on PCCCH/CCCH
C901200033 Number of EGPRS UL TBF establishment failure on PACCH due to
C901200034 Number of EGPRS UL TBF establishment success on
PCCCH/CCCH .......................................................................................................26-30
C901200035 Number of EGPRS UL TBF establishment success on PACCH .........26-31
C901200038 Number of EGPRS UL TBF resource reallocation failure due to Abis
C901200039 Number of EGPRS UL TBF resource reallocation failure due to RR
UPPB-DSP channel congestion for DL TBF establishment.....................................26-34
C901200041 Number of EGPRS UL TBF resource reallocation success due to DL
C901200042 Number of allocated PDCH for EGPRS UL TBF resource reallocation
due to DL TBF establishment .................................................................................26-36
channel activate failure for DL TBF establishment ..................................................26-37
C901200044 Number of EGPRS UL TBF resource reallocation failure due to BTS
C901200045 Number of EGPRS UL TBF resource reallocation failure due to BIU
C901200046 Number of EGPRS UL TBF resource reallocation success of channel
activate and connection for DL TBF establishment .................................................26-40
C901200047 Number of EGPRS UL TBF resource reallocation failure due to DL
C901200048 Number of EGPRS UL TBF resource reallocation success due to DL
26-2

Chapter 26 Uplink EGPRS Data TBF Statistics

C901200054 Number of EGPRS UL TBF resource reallocation success due to LLC
transmission ...........................................................................................................26-45
due to LLC transmission ........................................................................................26-46
channel activate failure for LLC transmission..........................................................26-47
activate for LLC transmission .................................................................................26-50
C901200060 Number of EGPRS UL TBF resource reallocation failure due to LLC
transmission ...........................................................................................................26-51
C901200061 Number of EGPRS UL TBF resource reallocation success due to LLC
transmission ...........................................................................................................26-51
C901200062 Number of EGPRS UL TBF resource reallocation requests for
UPPB-DSP channel congestion for resource request .............................................26-54
C901200067 Number of EGPRS UL TBF resource reallocation success due to
database allocation for resource request ................................................................26-55
due to resource request..........................................................................................26-56
channel activate failure for resource request ..........................................................26-57
activate and connection for resource request .........................................................26-60
C901200074 Number of EGPRS UL TBF resource reallocation success due to
C901200075 Number of EGPRS UL TBF release due to flush LL...........................26-61
26-3

C901200076 Number of EGPRS UL TBF release due to GPRS suspend requests .26-62
C901200077 Number of EGPRS UL TBF forcing release by CS ............................26-63
C901200078 Number of EGPRS UL TBF normal release due to user plane
requests .................................................................................................................26-63
C901200079 Number of EGPRS UL TBF abnormal release due to user plane
requests .................................................................................................................26-64
C901200080 Number of EGPRS UL TBF release due to NSVC unavailability ........26-65
C901200081 Number of EGPRS UL TBF release due to BVC unavailability...........26-65
C901200082 Number of EGPRS UL TBF release due to other reasons .................26-66
C901200083 Number of UL EGPRS TBF grab resources.......................................26-67
C901200084 Number of grab instance by UL EGPRS TBF ....................................26-68
C901200085 Number of UL EGPRS TBF queuing .................................................26-69
C901200086 Number of UL EGPRS TBF queuing success....................................26-70
C901200087 Number of UL EGPRS TBF release TBF during queuing...................26-71
26.1 Overview
UL EGPRS data TBF statistics collects the information about the establishment, maintain
and release of UL EGPRS TBF. The statistic unit is cell.

Definition
Number of GPRS UL TBF establishment requests on CCCH
Description

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

Usage
This counter is used to find out the frequency of channel requests on CCCH when MS
attempts using EGPRS service.
Measurement Point
When BSC receives channel requests on CCCH from MS, the counter increments. The
Figure 26-1 - EGPRS Channel Request
Unit
Times
Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

Definition
Number of GPRS UL TBF establishment requests on PCCCH.
Description
The counter is not used.

Definition
Number of EGPRS UL TBF establishment requests on PCCCH.
26-5

Description
using EGPRS service.
Usage
This counter is used to find out the frequency of channel requests on PCCCH when MS
attempts using EGPRS service.
Measurement Point
When BSC receives channel requests on PCCCH from MS, the counter increments. The
Figure 26-2 - EGPRS Packet Channel Request
Unit
Times

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 establishment attempts on
PACCH under the situation when DL GPRS TBF is already established.
26-6

Measurement Point
In the situation when DL EGPRS TBF is established, PS control plane receives UL
assignment request message from PS user plane, the counter increments. The
Figure 26-3 - UL Assignment Request (DL GPRS TBF ALREADY Established)
Unit
Times

assignment due to ONE PHASE access
Definition
Number of cell attempts for UL assignment due to ONE PHASE access.
Description
EGPRS TBF establishment or the number of packet channel requests on PCCCH due to
one phase access.
Usage
This counter is used to find out the number of UL EGPRS TBF establishment attempts due
to one phase access.
Measurement Point
26-7

Figure 26-4 - EGPRS Channel Requests On CCCH Due To One Phase Access
l If BSC receives EGPRS Packet channel request from MS on PCCCH due to one
phase access, the counter increments. The measurement point is A, as shown in
Figure 26-5.
Figure 26-5 - EGPRS Packet Channel Requests On CCCH Due To One Phase
Access
Unit
Times
Related Features
l ZGB-03-05-007 One Phase Access
l ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

assignment due to single block packet access
Definition
Number of cell attempts for UL assignment due to single block packet access
Description
26-8

Related Features

assignment due to response paging
Definition
Number of cell attempts for UL assignment due to response paging.
Description
Related Features

assignment due to cell updating
Definition
Number of cell attempts for UL assignment due to cell updating.
Description
Related Features

assignment due to mobility management
Definition
Number of cell attempts for UL assignment due to mobility management
Description
The counter is not used currently.
26-9

Related Features

assignment due to TWO PHASE access
Definition
Number of cell attempts for UL assignment due to TWO PHASE access.
Description
EGPRS TBF establishment or the number of packet channel requests on PCCCH due to
two phase access.
Usage
to two phase access.
Measurement Point
l If BSC receives EGPRS channel requests from MS on CCCH due to two phase
access, the counter increments. The measurement point is A, as shown in Figure
26-6.
Figure 26-6 - EGPRS Channel Requests On CCCH Due To Two Phase Access
l If BSC receives EGPRS Packet channel request from MS on CCCH due to one
phase access, the counter increments. The measurement point is A, as shown
inFigure 26-7.
26-10

Figure 26-7 - EGPRS Packet Channel Requests On PCCCH Due To Two Phase
Access
Unit
Times
Related Features

assignment 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.
Usage
to short access.
Measurement Point
l If BSC receives EGPRS channel requests from MS on CCCH due to short access,
26-11

Figure 26-8 - EGPRS Channel Requests On CCCH Due To Short Access
l If BSC receives EGPRS Packet channel request from MS on PCCCH due to short
access, the counter increments. The measurement point is A, as shown in Figure
26-9.
Figure 26-9 - EGPRS Packet Channel Requests On PCCCH Due To Short Access
Unit
Times
Related Features

Definition
Number of EGPRS UL TBF establishment failure due to Abis congestion.
Description
EGPRS TBF establishment due to Abis congestion.
26-12

Usage
attempting UL EGPRS TBF establishment due to Abis congestion.
Measurement Point
l 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 increments. The measurement point is A, as shown in
Figure 26-10.
Figure 26-10 - DB Resource Requests Failure Due To Abis Congestion (EGPRS)
l If PS control panel receives UL channel requests from PS user plane when DL

EGPRS TBF exists and fails to apply for DB resource due to Abis congestion, the
Unit
Times
Related Features
l ZGO-03-02-002 Enhancement on Channel Allocation
26-13


Definition
Number of EGPRS UL TBF establishment failure due to RR congestion.
Description
The counter records the number of DB resource request failure when attempting UL
EGPRS TBF establishment due to radio resource congestion. There are three causes
that lead to radio resource congestion: MS per channel (MS number on each channel
reaches its maximum), no TAI/TFI and no PDCH.
Usage
attempting UL EGPRS TBF establishment due to RR congestion.
Measurement Point
l 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
26-12.
Figure 26-12 - DB Resource Requests Failure Due To RR Congestion (EGPRS)
l If PS control panel receives UL channel requests from PS user plane when DL

EGPRS TBF exists and fails to apply for DB resource due to RR congestion, the
26-14

Unit
Times
Related Features

congestion
Definition
Number of EGPRS UL TBF establishment failure due to UPPB-DSP channel congestion
Description
EGPRS TBF establishment due to UPPB-DSP channel congestion.
Usage
attempting UL EGPRS TBF establishment due to UPPB-DSP channel congestion.
Measurement Point
Packet channel request on PCCCH and fails to apply for DB resource due to
UPPB-DSP channel congestion, the counter increments. The measurement point is
Figure 26-14 - DB Resource Requests Failure Due To UPPB-DSP Channel

Congestion (EGPRS)
26-15


due to UPPB-DSP congestion, the counter increments. The measurement point is
Figure 26-15 - DB Resource Requests Failure Due To UPPB-DSP Congestion (DL

Unit
Times
Related Features

Definition
Number of EGPRS UL TBF establishment channel allocate success.
Description
This counter counts the number of DB resource request successes when attempting UL
EGPRS TBF establishment.
Usage
This counter is used to find out the number of DB resource request successes when
attempting UL GPRS TBF establishment.
26-16

Measurement Point
If PS control plane receives EGPRS channel requests from MS on CCCH or EGPRS
Packet channel request on PCCCH and succeeds in applying for DB resource, the counter
Figure 26-16 - DB Resource Request Successes (EGPRS)
Unit
Times
Related Features
26.18 C901200019 Number of cell success for EGPRS

UL assignment due to ONE PHASE access
Definition
Number of EGPRS UL TBF establishment failure due to UPPB-DSP channel congestion.
Description
EGPRS TBF establishment due to UPPB-DSP channel congestion.
Usage
attempting UL EGPRS TBF establishment due to UPPB-DSP channel congestion.
Measurement Point
26-17


Packet channel request on PCCCH and fails to apply for DB resource due to
is A, as shown inFigure 26-17
Figure 26-17 - DB Resource Requests Failure Due To UPPB-DSP Channel

Congestion (EGPRS)

due to UPPB-DSP congestion, the counter increments. The measurement point
is A, as shown inFigure 26-18
Figure 26-18 - DB Resource Requests Failure Due To DPPB-DSP Congestion (DL

Unit
Times
Related Features
l ZGB-03-05-007 One Phase Access
26-18


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

UL assignment due to response paging
Definition
Number of cell success for EGPRS UL assignment due to response paging
Description
Related Features

UL assignment due to cell updating
Definition
Number of cell success for EGPRS UL assignment due to cell updating.
Description
Related Features
26-19


UL assignment due to mobility management
Definition
Number of cell success for EGPRS UL assignment due to mobility management.
Description
Related Features

UL assignment due to TWO PHASE access
Definition
Number of cell success for EGPRS UL assignment due to TWO PHASE access.
Description
This counter counts the number of successful UL EGPRS TBF establishment due to two
phase access.
Usage
This counter is used to find out the number of successful UL EGPRS TBF establishment
due to two phase access.
Measurement Point
l If BSC receives EGPRS channel requests from MS on CCCH due to two phase
access and DB resource request succeeds, the counter increments. The
26-20

Figure 26-19 - EGPRS DB Resource Request Successes Due To Two Phase Access
(CCCH)
l If BSC receives EGPRS packet channel requests from MS on PCCCH due to two
phase access and DB resource request succeeds, the counter increments. The
Figure 26-20 - DB Resource Request Successes On PCCCH Due To Two Phase

Access
Unit
Times
Related Features
l ZGB-03-05-008 Two Phase Access

UL assignment due to short access
Definition
Number of cell success for EGPRS UL assignment due to short access.
26-21

Description
This counter counts the number of successful UL EGPRS TBF establishment due to short
access.
Usage
due to short access.
Measurement Point
l If BSC receives EGPRS channel requests from MS on CCCH due to short access
and DB resource request succeeds, the counter increments. The measurement
Figure 26-21 - EGPRS DB Resource Request Successes Due To Short Access

(CCCH)
l If BSC receives EGPRS packet channel requests from MS on PCCCH due to

short access and DB resource request succeeds, the counter increments. The
Figure 26-22 - EGPRS DB Resource Request Successes Due To Short Access

(PCCCH)
Unit
Times
26-22

Related Features

EGPRS UL TBF establishment
Definition
Number of allocated PDTCH for EGPRS UL TBF establishment.
Description
This counter counts the number of successfully assigned PDTCH when UL EGPRS TBF
successfully established.
Usage
This counter is used to find out the number of successfully assigned PDTCH when UL
EGPRS TBF successfully established.
Measurement Point
When PS control plane receives EGPRS channel requests on CCCH from MS or EGPRS
Packet channel request on PCCCH and DB resource requests succeed, the counter
Figure 26-23 - DB Resource Request Successes (EGPRS)
Unit
Times
Related Features
26-23


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 failure when establishing
UL EGPRS TBF (including initially establish UL TBF and establish UL TBF when DL TBF
exists).
Measurement Point
l When BSC receives PDTCH channel activate failure message reported by BTS, the
l When 'wait for PDTCH channel activation and connection response' counter times
out and BSC fails to receive PDTCH activate response message reported by BTS,
Unit
Times
Related Features
26-24


Definition
Number of EGPRS UL TBF establishment failure due to BTS connection failed.
Description
This counter counts the number of failure to establish UL EGPRS TBF due to BTS
connection failure.
Usage
This counter is used to find out the number of UL EGPRS TBF establishment failure
BTS connection failure.
Measurement Point
l When PS control plane receives connection failure message reported by connection
l When 'wait for PDTCH channel activate and connection response' counter times
out and BSC fails to receive connection success response message reported by
connection module, this counter increments.
Unit
Times
Related Features
26-25


Definition
Number of EGPRS UL TBF establishment failure due to BIU connection failed.
Description
This counter counts the number of failure to establish UL EGPRS TBF due to BIU
connection failure.
Usage
This counter is used to find out the number of UL EGPRS TBF establishment failure
BIU connection failure.
Measurement Point
When PS control plane receives connection failure message reported by connection
modules due to BIU connection failure, the counter increments. The measurement point
Unit
Times
Related Features
26-26

26.29 C901200030 Number of EGPRS UL TBF channel

Definition
Number of EGPRS UL TBF channel activate establishment success.
Description
This counter counts the number of channel activate and connection successes when
establishing UL EGPRS TBF.
Usage
when establishing UL EGPRS TBF.
Measurement Point
When PS control plane receives channel activate response message reported by BTS
and connection successes acknowledgement message reported by connection module,
Figure 26-27 - UL EGPRS TBF Establishes Channel Activation And Access Success
Unit
Times
Related Features

establishment failure due to not receive PIA
Definition
Number of EGPRS UL TBF establishment failure due to not receive PIA.
26-27

Description
This counter counts the number of failure to send immediate assignment message to MS
when establishing UL EGPRS TBF.
Usage
This counter is used to find out the number of failure to send immediate assignment
message to MS when establishing UL EGPRS TBF.
Measurement Point
l When PS control plane receives immediate assignment failure message reported by

l When 'wait for immediate assignment and sending indication' counter times out
and BSC fails to receive immediate assignment and sending indication message,
Unit
Times
Related Features

establishment failure on PCCCH/CCCH due to
UPPB-DSP congestion
Definition
Number of EGPRS UL TBF establishment failure on PCCCH/CCCH due to UPPB-DSP.
26-28

Description
This counter counts the number of failure to establish UL EGPRS TBF.
Usage
This counter is used to find out the number of failure to establish UL EGPRS TBF.
Measurement Point
When PS control plane assigns single block through two phase access from PS user plane,
or gets access to PS user plane through one phase access and starts assignment timer.
If the timer times out, resource request from PS user plane (two phase access) is not
received or indication (one phase access) is not established, the counter increments. The
Unit
Times
Related Features
26-29


congestion
Definition
Number of EGPRS UL TBF establishment failure on PACCH due to UPPB-DSP
congestion.
Description

Definition
Number of EGPRS UL TBF establishment success on PCCCH/CCCH.
Description
This counter counts the number of successful UL EGPRS TBF establishment and receiving
MS TLL1.
Usage
This counter is used to find out the number of successful UL EGPRS TBF establishment
and receiving MS TLL1.
Measurement Point
l 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
26-30

Figure 26-30 - UL One-Phase-Access Resource Assignment Successes
l PS control plane receives resource request message from PS user plane in the
premise of two phase access, the counter increments. The measurement point is
Figure 26-31 - UL Two-Phase-Access Single Block Assignment Successes
Unit
Times
Related Features

Definition
Number of EGPRS UL TBF establishment success on PACCH.
26-31

Description

reallocation failure due to Abis congestion for DL
TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for DL
TBF
Description
In the situation when UL EGPRS TBF is already established, DL TBF is needed to be
failure. The counter records the number of UL EGPRS TBF reallocation failure due to Abis
Usage
Abis congestion.
Measurement Point
In the situation when UL EGPRS TBF is established, PS control plane receives DL
Abis congestion, the counter increments. The measurement point is A, as shown inFigure
26-32.
Figure 26-32 - Database Application Failure Due To Abis Congestion
Unit
Times
26-32

Related Features

reallocation failure due to RR congestion for DL
TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to RR congestion for DL TBF
establishment.
Description
failure. The counter records the number of UL resource reallocation failure due to RR
There are three causes which lead to radio resource congestion: MS per channel (MS
number per channel reaches its maximum), TAI/TFI (no TAI or TFI available) and no PDCH
available.
Usage
This counter is used to find out the number of UL EGPRS TBF reallocation failure due to
RR congestion.
Measurement Point
RR congestion, the counter increments. The measurement point is A, as shown inFigure
26-33.
Figure 26-33 - Database Application Failure due to RR Congestion
26-33

Unit
Times
Related Features

congestion for DL TBF 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 TBF is needed to be
failure. The counter records the number of EGPRS UL resource reallocation failure due
to UPPB-DSP channel resource congestion.
Usage
This counter is used to find out the number of UL EGPRS TBF reallocation failure due to
UPPB-DSP channel congestion.
Measurement Point
UPPB-DSP channel congestion, the counter increments. The measurement point is A, as
26-34

Unit
Times
Related Features

Definition
Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment.
Description
The counter records the number of successful DL TBF establishment on PACCH when UL
EGPRS TBF is already established.
Usage
This counter is used to find out the number of DL EGPRS TBF reallocation successes.
Measurement Point
Unit
Times
Related Features
26-35


EGPRS UL TBF resource reallocation due to DL
TBF establishment
Definition
Number of allocated PDTCH for EGPRS UL TBF resource reallocation due to DL TBF
establishment.
Description
The counter records the number of successful allocated PDTCH when UL EGPRS TBF is
successfully reallocated.
Usage
This counter is used to find out the number of successful allocated PDTCH when UL
EGPRS TBF is successfully reallocated.
Measurement Point
l 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 increments. The measurement point is A, as shown inFigure
26-36.
Unit
Times
Related Features
26-36


Definition
Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for
Description
reallocation.
Usage
This counter is used to find out the number of PDTCH activate failure during UL EGPRS
Measurement Point
Unit
Times
26-37


Definition
Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for
Description
The counter records the number of BTS connection failure during UL EGPRS TBF resource
reallocation.
Usage
This counter is used to find out the number of BTS connection failure during UL EGPRS
Measurement Point
Unit
Times
26-38


Definition
Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for
Description
The counter records the number of BIU connection failure during UL EGPRS TBF resource
reallocation.
Usage
This counter is used to find out the number of BIU connection failure during UL EGPRS
Measurement Point
in Figure 26-39.
Unit
Times
26-39


Definition
Number of EGPRS UL TBF resource reallocation success of channel activate and
Description
EGPRS TBF resource reallocation.
Usage
during UL EGPRS TBF resource reallocation.
Measurement Point
Figure 26-40 - Resource Application Failure Due To ABIS Congestion (Resource

Adjustment)
Unit
Times
26-40


Definition
Number of EGPRS UL TBF resource reallocation failure due to DL TBF establishment.
Description
Related Features

Definition
Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment.
Description
Related Features

transmission
Definition
Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for LLC
transmission.
Description
26-41

request failure due to Abis resource congestion after PS control plane receiving resource
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 EGPRS TBF
transmission process.
Measurement Point
and DB resource request fails due to Abis congestion, the counter increments. The

Adjustment)
Unit
Times
Related Features

transmission
Definition
Number of EGPRS UL TBF resource reallocation failure due to RR congestion for LLC
transmission.
26-42

Description
request failure due to radio resource congestion after PS control plane receiving resource
There are three causes leading to RR congestion: MS per channel (reaches its maximum),
TAI/TFI (not available), and no PDTCH.
Usage
This counter is used to find out DB resource request failure due to RR congestion after PS
control plane receiving resource reallocation request during UL EGPRS TBF transmission
process.
Measurement Point
and DB resource request fails due to RR congestion, the counter increments. The

Adjustment)
Unit
Times
Related Features
26-43


Definition
Description
request failure due to UPPB-DSP channel congestion after PS control plane receiving
resource reallocation request during UL EGPRS TBF transmission process.
Usage
This counter is used to find out DB resource request failure due to UPPB-DSP channel
congestion after PS control plane receiving resource reallocation request during UL
EGPRS TBF transmission process.
Measurement Point
DB resource request fails due to UPPB-DSP channel congestion, the counter increments.

Unit
Times
Related Features
26-44


Definition
Number of EGPRS UL TBF resource reallocation failure due to LLC transmission.
Description
request successes after PS control plane receiving resource reallocation request during
UL EGPRS TBF transmission process.
Usage
This counter is used to find out DB resource request success due after PS control plane
receiving resource reallocation request during UL EGPRS TBF transmission process.
Measurement Point
Unit
Times
Related Features
26-45


EGPRS UL TBF resource reallocation due to LLC
transmission
Definition
Number of allocated PDTCH for EGPRS UL TBF resource reallocation due to LLC
transmission.
Description
resource after receiving the message. The counter records the number of successfully
allocated PDTCH after PS control plane receiving resource reallocation requests during
UL EGPRS TBF.
Usage
This counter is used to find out the number of successful allocated PDTCH when UL
EGPRS TBF is successfully reallocated.
Measurement Point
Unit
Tines
Related Features
26-46


Definition
LLC transmission.
Description
This counter counts the number of PDTCH activate failure after BSC receiving resource
reallocation request during UL EGPRS TBF resource reallocation.
Usage
This counter is used to find out the number of PDTCH activate failure during UL EGPRS
Measurement Point
Unit
Times
26-47


Definition
LLC transmission.
Description
The counter records the number of connection failure due to BTS connection failure after
BSC receiving resource reallocation request during UL EGPRS TBF transmission.
Usage
This counter is used to find out the number of BTS connection failure during UL EGPRS
TBF resource transmission.
Measurement Point
point is A, as shown in
Unit
Times
26-48


Definition
LLC transmission.
Description
The counter records the number of BIU connection failure during UL EGPRS TBF
transmission.
Usage
This counter is used to find out the number of BIU connection failure during UL EGPRS
TBF transmission.
Measurement Point
in Figure 26-48.
Unit
Times
26-49


reallocation success of channel activate for LLC
transmission
Definition
Number of EGPRS UL TBF resource reallocation success of channel activate for LLC
transmission
Description
EGPRS TBF transmission.
Usage
during UL EGPRS TBF tranmission.
Measurement Point
increments. The measurement point is A, as shown in .
Figure 26-49
Unit
Times
26-50


Definition
Number of EGPRS UL TBF resource reallocation failure due to LLC transmission.
Description
Related Features

Definition
Number of EGPRS UL TBF resource reallocation success due to LLC transmission.
Description
Related Features

Definition
Number of EGPRS UL TBF resource reallocation requests for resource request.
Description
26-51


reallocation failure due to Abis congestion for
resource request
Definition
Number of EGPRS UL TBF resource reallocation failure due to 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.
Usage
plane receives resource request from MS during UL EGPRS TBF process (including UL
Measurement Point
request fails due to Abis congestion, the counter increments. The measurement point is
Figure 26-50 - DB Resource Requests Failure Due To Abis Congestion (Resource

Request)
Unit
Times
Related Features
26-52


reallocation failure due to RR congestion for
resource request
Definition
Number of EGPRS UL TBF resource reallocation failure due to RR congestion for resource
request.
Description
receives resource request from MS due to 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).
Usage
plane receives resource request from MS due to RR congestion during UL EGPRS TBF
process (including UL two-phase access and UL TBF transmission).
Measurement Point
PS control plane receives resource request message from MS, and DB resource request
fails due to RR congestion, the counter increments. The measurement point is A, as shown
in Figure 26-51.
Figure 26-51 - DB Resource Requests Failure Due To RR Congestion
Unit
Times
26-53

Related Features

congestion for resource request
Definition
congestion for resource request.
Description
receives resource request from MS due to UPPB-DSP channel congestion during UL
EGPRS TBF.
Usage
plane receives resource request from MS due to UPPB-DSP channel congestion during
UL EGPRS TBF process (including UL two-phase access and UL TBF transmission).
Measurement Point
Figure 26-52 - DB Resource Requests Failure Due To UPPB-DSP Channel Congestion

(Resource Request)
Unit
Times
26-54

Related Features

reallocation success due to database allocation
Definition
Number of EGPRS UL TBF resource reallocation success due to database allocation for
resource request
Description
The counter records the number of successful DB resource request after PS control plane
receives resource request message from MS during UL EGPRS TBF process.
Usage
This counter is used to find out the number of DB resource request successes after
PS control plane receives resource request from MS during UL EGPRS TBF process
(including UL two-phase access and UL TBF transmission).
Measurement Point
Figure 26-53.
Figure 26-53 - DB Resource Requests Successes (Resource Request)
Unit
Times
26-55

Related Features

EGPRS UL TBF resource reallocation due to
resource request
Definition
Number of allocated PDTCH for EGPRS UL TBF resource reallocation due to resource
request.
Description
The counter records the number of successful allocated PDTCH after PS control plane
receives resource request message from MS during UL EGPRS TBF process.
Usage
This counter is used to find out the number of successful allocated PDTCH after PS control
plane receives resource request from MS during UL EGPRS TBF process (including UL
Measurement Point
Figure 26-54.
Figure 26-54 - DB Resource Requests Successes (Resource Request)
Unit
Times
26-56

Related Features

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).
increments. The measurement point is A, as shown in .
Unit
Times
26-57


Definition
resource request.
Description
UL EGPRS TBF resource reallocation after PS control plane receives resource request
message.
Usage
transmission).
Measurement Point
Unit
Times
26-58


Definition
resource request.
Description
message.
Usage
message in UL EGPRS TBF process (including UL two-phase access and one-phase TBF
transmission).
Measurement Point
inFigure 26-57.
Unit
Times
26-59


Definition
Number of EGPRS UL TBF resource reallocation success of channel activate and
Description
The counter records the number of channel activate and connection successes during
message.
Usage
The counter records the number of channel activate and connection failure during UL
EGPRS TBF resource reallocation after PS control plane receives resource request
message in UL EGPRS TBF process (including UL two-phase access and one-phase
TBF transmission).
Measurement Point

Adjustment)
Unit
Times
26-60


reallocation failure due to resource request
Description
Related Features

Description
Related Features

due to flush LL
Description
This counter counts the number of UL EGPRS TBF release after PS control plane receiving
request due to flush LL.
Usage
This counter is used to find out the number of UL EGPRS TBF release after PS control
plane receiving request due to flush LL.
Measurement Point
When PS control plane of BSC receives FLUSH message from SGSN and release is
executed when UL EGPRS TBF is established, the counter increments. The measurement
26-61

Figure 26-59 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.
Usage
This counter is used to find out the number of UL EGPRS TBF release due to GPRS
suspend requests.
Measurement Point
When PS control plane of BSC receives SUSPEND message from SGSN and release is
executed when UL EGPRS TBF is established, the counter increments. The measurement
Figure 26-60 Release Request due to Suspend Request
Unit
Times
26-62

26.71 C901200077 Number of EGPRS UL TBF forcing

release by CS
Description
This counter counts the number of UL EGPRS TBF forcing release by CS.
Usage
This counter is used to find out the number of UL EGPRS TBF forcing release by CS.
Measurement Point
When PS control plane of BSC receives PDCH RELEASE message from CS control plane
when UL EGPRS TBF is established, the counter increments. The measurement point is
Figure 26-61 Release Request due to PDCH REL
Unit
Times
26.72 C901200078 Number of EGPRS UL TBF normal

Description
This counter counts the number of UL EGPRS TBF normal release due to user plane
requests.
Usage
This counter is used to find out the number of UL EGPRS TBF normal release due to user
plane requests.
Measurement Point
When PS control plane of BSC receives NORMAL RELEASE REQUEST message from
PS user plane when UL EGPRS TBF exists, the counter increments. The measurement
26-63

Figure 26-62 Release Request due to Normal Release Request by MAC
Unit
Times
26.73 C901200079 Number of EGPRS UL TBF abnormal

Description
This counter counts the number of UL EGPRS TBF abnormal release due to user plane
requests.
Usage
This counter is used to find out the number of UL EGPRS TBF abnormal release due to
user plane requests.
Measurement Point
When PS control plane receives ABNORMAL RELEASE REQUEST message from PS
user plane when UL EGPRS TBF exists, the counter increments. The measurement point
Figure 26-63 Release Request due to Abnormal Release Request by MAC
Unit
Times
26-64


Definition
Number of EGPRS UL TBF release due to NSVC unavailability.
Description
This counter counts the number of UL EGPRS TBF release due to NSVC unavailability.
Usage
This counter is used to find out the number of UL EGPRS TBF release after receiving
forcing release request due to NSVC unavailability.
Measurement Point
When PS control plane receives NSVC unavailability command to release PS control plane
module from DB when UL EGPRS TBF exists, the counter increments. The measurement
Figure 26-64 - 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.
26-65

Usage
forcing release request due to BVC unavailability.
Measurement Point
When PS control plane receives BVC unavailability command to release PS control plane
module from DB when UL EGPRS TBF exists, the counter increments. The measurement
Unit
Times

Definition
Number of EGPRS UL TBF release due to other reasons.
Description
This counter counts the number of UL EGPRS TBF forcing release due to other reasons.
Usage
forcing release request due to other reasons.
Measurement Point
When PS control plane receives release message due to other reasons when UL EGPRS
26-66

Unit
Times
26.77 C901200083 Number of UL 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 grabbing other TBF
resource.
Measurement Point
This counter increments while UL EGPRS TBF is established during resource adjustment,
is A as shown inFigure 26-67.
26-67

Figure 26-67 - UL EGPRS Resource Request Success
Unit
Times
Related Features
26.78 C901200084 Number of grab instance by UL

EGPRS TBF
Definition
Number of grab instance by UL EGPRS TBF.
Description
This counter counts the number of grab instance by UL EGPRS TBF.
Usage
This counter is used to find out the frequency for UL EGPRS TBF grabbing other TBF
resource.
Measurement Point
is A as shown in Figure 26-68.
26-68

Unit
Times
Related Features
26.79 C901200085 Number of UL EGPRS TBF queuing

Definition
Number of UL EGPRS TBF queuing.
Description
This counter counts the number of UL EGPRS TBF queuing.
Usage
This counter is used to find out the frequency for UL EGPRS TBF queuing.
Measurement Point
Measurement point is A as shown in Figure 26-69.
26-69

Unit
Times
Related Features
26.80 C901200086 Number of UL EGPRS TBF queuing

success
Definition
Number of UL EGPRS TBF queuing success.
Description
This counter counts the number of UL EGPRS TBF queuing success.
Usage
This counter is used to find out the frequency for UL EGPRS TBF queuing success.
Measurement Point
the instance to be queued successfully assigns resource for user, and database is
successfully registered. Measurement point is A as shown inFigure 26-70.
26-70

Unit
Times
Related Features
26.81 C901200087 Number of UL EGPRS TBF release

TBF during queuing
Definition
Number of UL EGPRS TBF release TBF during queuing.
Description
This counter counts the number of UL EGPRS TBF release during queuing.
Usage
This counter is used to find out the frequency for UL EGPRS TBF release during queuing.
Measurement Point
This counter increments while UL EGPRS TBF is released and instance still in queuing
state. The measurement point is A as shown in Figure 26-71.
26-71

Figure 26-71 - Release UL EGPRS TBF
Unit
Times
Related Features
26-72

Chapter 27
BSSGP Flow Statistic
Table of Contents
Overview ..................................................................................................................27-2
C901210001 Number of paging PS message ...........................................................27-2
C901210002 Number of paging CS message...........................................................27-2
C901210003 Number of Flush-LL Message received ...............................................27-3
C901210004 Number of Flush-LL-ACK Message sent .............................................27-4
C901210005 Number of BVC-BLOCK message sent ...............................................27-5
C901210006 Number of BVC-BLOCK-ACK message received ...............................27-5
C901210007 Number of BVC-UNBLOCK message sent ..........................................27-6
C901210008 Number of BVC-UNBLOCK-ACK message received ..........................27-7
C901210009 Number of BVC-RESET message sent ...............................................27-8
C901210010 Number of BVC-RESET-ACK message received ................................27-9
C901210011 Number of BVC-RESET message received .......................................27-10
C901210012 Number of BVC-RESET-ACK message sent ..................................... 27-11
C901210013 Number of PERFORM-LOCATION-REQUEST message received ....27-12
C901210014 Number of PERFORM-LOCATION-RESPONSE message sent ........27-13
C901210015 Number of PERFORM-LOCATION-ABORT message received .........27-14
C901210016 Number of POSITION-COMMAND message sent .............................27-15
C901210017 Number of POSITION-RESPONSE message received .....................27-16
C901210018 Number of Flush-LL received if UL/DL TBF exist ...............................27-17
C901210019 Number of Flush-LL received if DL TBF exist ....................................27-18
C901210020 Number of Flush-LL received if UL TBF exist ....................................27-19
C901210021 Number of reroute intra NSE .............................................................27-20
C901210022 Number of reroute inter NSE intra BSS cell .......................................27-21
C901210023 Number of reroute inter NSE inter BSS cell .......................................27-21
C901210024 LLC transfer bytes .............................................................................27-22
C901210025 LLC transfer frames...........................................................................27-23
C901210026 LLC transfer failed bytes....................................................................27-23
C901210027 LLC transfer failed frames .................................................................27-24
C901210028 LLC transfer failed num .....................................................................27-24
C901210029 LLC transfer succeeded num.............................................................27-25
C901210030 LLC transfer via cell reselection.........................................................27-25
C901210031 LLC transfer not via cell reselection...................................................27-26
C901210032 LLC transfer fail Num via cell reselection ...........................................27-27
C901210033 LLC transfer fail Num not via cell reselection .....................................27-27
27-1

27.1 Overview
TRX measurement is to measure the success or failure condition of channel activation,
assignment, and handover in the unit of carrier. It also can measure carrier interference
band, maximum and minimum UL & DL level condition, to learn the status of different
carriers, providing evidence for adjustment and maintenance.
27.2 C901210001 Number of paging PS message

Description
SGSN sending packet paging message indicates that BSC originates packet paging for
MS in designated cell. This counter counts the number of receiving this message.
Measurement Point
When BSC receives a PAGING PS message, this counter increments. The measurement
Figure 27-1 PAGING PS Process
Unit
Times
Related Features
27.3 C901210002 Number of 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.
27-2

Chapter 27 BSSGP Flow Statistic
Measurement Point
When BSC receives a PAGING CS message, this counter increments. The measurement
Figure 27-2 - Paging CS Process
Unit
Times
Related Features
27.4 C901210003 Number of Flush-LL Message

received
Definition
Number of Flush-LL Message received
Description
SGSN sends FLUSH-LL message to notify of BSS MS to do inter-cell handover, and this
counter counts the number of receiving this message by BSC.
Usage
By viewing the number of receiving this message by BSC, to check the MS handover
condition.
Measurement Point
When BSC receives a FLUSH-LL message, this counter increments. The measurement
27-3

Figure 27-3 - FLUSH-LL Message
Unit
Times
27.5 C901210004 Number of Flush-LL-ACK Message

sent
Definition
Number of Flush-LL Message sent
Description
BSC sends FLUSH-LL-ACK message to notify SGSN: LLC PDU buffered for this MS by
pervious cell has been removed or transferred to new cell under same routing area. This
counter counts the number of sending this message by BSC.
Measurement Point
When BSC receives a FLUSH-LL-ACK message, this counter increments. The
Unit
Times
27-4

27.6 C901210005 Number of 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 Point
When BSC sends a BVC-BLOCK message, this counter increments. The measurement
Figure 27-5 - BVC Blocking Process
Unit
Times
27.7 C901210006 Number of BVC-BLOCK-ACK

message received
Definition
Number of BVC-BLOCK-ACK message received
Description
SGSN sends BVC blocking confirmation message to notify of designated BVC blocked by
BSC, and this counter counts the number of receiving this message by BSC.
27-5

Measurement Point
When BSC receives a BVC-BLOCK-ACK message, this counter increments. The
measurement point is A2, as shown inFigure 27-6 .
Figure 27-6 - BVC Blocking Process
Unit
Times
27.8 C901210007 Number of BVC-UNBLOCK message

sent
Definition
Number of BVC-UNBLOCK message sent
Description
BSC sends BVC unblocking message indicates BVC designated by SGSN unblocking,
and this counter counts the number of unblocking designated BVC by BSC.
Measurement Point
When BSC sends a BVC-UNBLOCK message, this counter increments. The measurement
point is A1, as shown inFigure 27-7 .
27-6

Figure 27-7 - BVC Unblocking Process
Unit
Times
27.9 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 Point
When BSC receives a BVC-UNBLOCK-ACK message, this counter increments. The
27-7

Figure 27-8 - BVC Unblocking Process
Unit
Times
27.10 C901210009 Number of BVC-RESET message

sent
Definition
Number of BVC-RESET message sent
Description
BSC sends BVC reset message indicates SGSN resets designated BVC, and this counter
counts the number of resetting designated BVC by BSC actively.
Measurement Point
When BSC sends a BVC-RESET message, this counter increments. The measurement
point is A1, as shown inFigure 27-9 .
27-8

Figure 27-9 - BVC Reset Process
Unit
Times
27.11 C901210010 Number of BVC-RESET-ACK

message received
Definition
Number of BVC-RESET-ACK message received.
Description
SGSN sends BVC reset confirmation message to notify of designated BVC reset by BSC,
and this counter counts the number of receiving this message by BSC.
Measurement Point
When BSC receives a BVC-RESET-ACK essage, this counter increments. The
27-9

Unit
Times

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
27-10

Unit
Times

message sent
Definition
Number of BVC-RESET-ACK message sent.
Description
BSC sends BVC reset confirmation message to notify of designated BVC reset by SGSN,
and this counter counts the number of sending this message by BSC.
Measurement Point
When BSC sends a BVC-RESET-ACK message, this counter increments. The
27-11

Unit
Times
27.14 C901210013 Number of PERFORM-LOCATION-R

EQUEST message received
Definition
Number of PERFORM-LOCATION-REQUEST message received.
Description
SGSN sends location request message to request BSC to do a locating process for MS.
This counter counts the number of receiving this message by BSC.
Usage
By viewing the number of receiving locating request message by BSC, you can view the
frequency of locating service.
Measurement Point
When BSC receives a PERFORM-LOCATION-REQUEST message, this counter increments.
The measurement point is A1, as shown inFigure 27-13 .
27-12

Figure 27-13 - Perform Location Process
Unit
Times

ESPONSE message sent
Definition
Number of PERFORM-LOCATION-RESPONSE message sent
Description
After BSC finishes locating process, send locating response message to notify SGSN of
locating result for MS. This counter counts the number of sending this message by BSC.
Usage
By viewing the number of sending this message by BSC, you can view the frequency of
locating service.
Measurement Point
When BSC sends a PERFORM-LOCATION- RESPONSE message, this counter
27-13

Unit
Times
27.16 C901210015 Number of PERFORM-LOCATION-A

BORT 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 Point
When BSC receives a PERFORM-LOCATION-ABORT message, this counter increments.
The measurement point is A1, as shown inFigure 27-15.
27-14

Unit
Times
27.17 C901210016 Number of 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 sending this message by BSC.
Measurement Point
BSC sends a POSITION-COMMAND message, this counter increments. The measurement
27-15

Unit
Times
27.18 C901210017 Number of 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 number of receiving this message by BSC.
Measurement Point
When BSC receives a POSITION-RESPONSE message, this counter increments. The
27-16

Unit
Times
27.19 C901210018 Number of Flush-LL received if

UL/DL TBF exist
Definition
Number of Flush-LL received if UL/DL TBF exist
Description
SGSN sends FLUSH-LL message to notify of BSC MS passed inter-cell handover. This
counter counts the number of receiving FLUSH-LL message during data service made by
MS.
Measurement Point
Each time BSC receives a FLUSH-LL message and MS is conducting DL data service,
this counter increments. The measurement point is A, as shown inFigure 27-18.
27-17

Figure 27-18 - Receive FLUSH-LL For UL & DL TBF
Unit
Times
27.20 C901210019 Number of Flush-LL received if DL

TBF exist
Definition
Number of Flush-LL received if DL TBF exist
Description
counter counts the number of receiving FLUSH-LL message during DL data service made
by MS.
Measurement Point
When BSC receives a FLUSH-LL message and MS is conducting UL data service, this
27-18

Figure 27-19 - Receive FLUSH-LL For DL TBF
Unit
Times
27.21 C901210020 Number of Flush-LL received if UL

TBF exist
Definition
Number of Flush-LL received if UL TBF exist
Description
counter counts the number of receiving FLUSH-LL message during UL data service made
by MS.
Measurement Point
When BSC receives a FLUSH-LL message and MS is conducting UL data service, this
27-19

Figure 27-20 - Receive FLUSH-LL For UL TBF
Unit
Times
27.22 C901210021 Number of reroute intra NSE

Definition
Number of reroute intra NSE.
Description
SGSN sends FLUSH-LL message to notify of BSS MS passed inter-cell handover. This
counter counts the number of receiving this message by BSC, and the number of same
NSE for new and previous cells.
Measurement Point
When BSC receives a FLUSH-LL message and new and previous cells are same NSE,
this counter increments. The measurement point is A1, as shown inFigure 27-21.
27-20

Unit
Times
27.23 C901210022 Number of reroute inter NSE intra

BSS cell
Definition
Number of reroute inter NSE intra BSS cell.
Description
counter counts the number of receiving this message by BSC, and the number of same
BSS and different NSEs for new and previous cells.
Measurement Point
When BSC receives a FLUSH-LL message and new and previous cells are same BSS or
different NSEs, this counter increments. The measurement point is A1, as shown inFigure
27-22.
Unit
Times
27.24 C901210023 Number of reroute inter NSE inter

BSS cell
Definition
Number of reroute inter NSE inter BSS cell.
27-21

Description
counter counts the number of receiving this message by BSC, and the number of different
BSSs and NSEs for new and previous cells.
Measurement Point
When BSC receives a FLUSH-LL message, and new and previous cells are different BSSs
or NSEs, this counter increments. The measurement point is A1, as shown inFigure 27-23.
Unit
Times
27.25 C901210024 LLC transfer bytes

Description
If LLC frame transferring is supported, then this counter counts the number of bytes of LLC
frames successfully transferred within BSC when cell reselection or LLC frame transferring
due to uplink and downlink TBFs being established simultaneously occurs.
Usage
This counter is used to find out the number of bytes of LLC frames successfully transferred
after LLC frame transferring is initiated.
Measurement Point
When PS control plane receives the indication of LLC frame transferring success or
failure from PS user plane, the number of bytes of LLC frames successfully transferred
is accumulated.
27-22

Unit
Byte
27.26 C901210025 LLC transfer frames

Description
If LLC frame transferring is supported, then this counter counts the number of LLC frames
successfully transferred within BSC when cell reselection or LLC frame transferring due to
uplink and downlink TBFs being established simultaneously occurs.
Usage
This counter is used to find out the number of LLC frames successfully transferred after
LLC frame transferring is initiated.
Measurement Point
When PS control plane receives the indication of LLC frame transferring success or failure
from PS user plane, the number of LLC frames successfully transferred is accumulated.
Unit
Times
27.27 C901210026 LLC transfer 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
Measurement Point
When PS control plane receives the indication of LLC frame transferring failure from PS
user plane, the number of bytes of LLC frames failed to be transferred is accumulated.
27-23

Unit
Byte
27.28 C901210027 LLC transfer 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.
Measurement Point
When PS control plane receives the indication of LLC frame transferring failure from PS
user plane, the number of LLC frames failed to be transferred is accumulated.
Unit
Times
27.29 C901210028 LLC transfer failed num

1. V6.20.200a ~ V6.20.200e
2. V6.20.200f
a. 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.
b. Usage
This counter is used to find out the number of LLC frames failed to be transferred
c. Measurement Point
When PS control plane receives the indication of LLC frame transferring
completion from PS user plane, if the transferring fails, then the counter
increments.
27-24

d. Unit
Times
27.30 C901210029 LLC transfer succeeded num

1. V6.20.200a ~ V6.20.200e
2. V6.20.200f
a. Description
If LLC frame transferring is supported, then this counter counts the number of LLC
frames successfully transferred within BSC when cell reselection or LLC frame
transferring due to uplink and downlink TBFs being established simultaneously
occurs.
b. Usage
This counter is used to find out the number of LLC frames successfully transferred
When PS control plane receives the indication of LLC frame transferring
completion from PS user plane, if the transferring succeeds, then the counter
increments.
d. Unit
Times
27.31 C901210030 LLC transfer via cell reselection

Description
1. V6.20.200a ~ V6.20.200e
frames successfully transferred within BSC when cell reselection occurs.
2. V6.20.200f
If LLC frame transferring is supported, then this counter counts the number of attempts
of self-recovered TBF link reestablishment in downlink within BSC.
Usage
1. V6.20.200a ~ V6.20.200e
after LLC frame transferring is initiated due to cell reselection.
2. V6.20.200f
27-25

If LLC frame transferring is supported, then this counter is used to find out the number
of attempts of self-recovered TBF link reestablishment in downlink within BSC.
Measurement Point
1. V6.20.200a ~ V6.20.200e
When PS control plane receives the indication of LLC frame transferring success from
PS user plane, if the LLC frame transferring is due to cell reselection, then the counter
increments.
2. V6.20.200f
When PS control plane processes the downlink TBF link establishment request sent
from PS user plane, if the link establishment request is due to self-recovery in downlink,
Unit
Times
27.32 C901210031 LLC transfer not via cell reselection

Description
1. V6.20.200a ~ V6.20.200e
frames successfully transferred within BSC when no cell reselection occurs (such as
when uplink and downlink TBFs are established simultaneously).
2. V6.20.200f
If LLC frame transferring is supported, then this counter counts the number of
successful self-recovered TBF link reestablishments in downlink within BSC.
Usage
1. V6.20.200a ~ V6.20.200e
after LLC frame transferring is initiated not due to cell reselection.
2. V6.20.200f
If LLC frame transferring is supported, then this counter is used to find out the number
of successful self-recovered TBF link reestablishments in downlink within BSC.
Measurement Point
1. V6.20.200a ~ V6.20.200e
27-26

When PS control plane receives the indication of LLC frame transferring success from
PS user plane, if the LLC frame transferring is not due to cell reselection, then the
counter increments.
2. V6.20.200f
When BSC receives the PIA_SEND_IND message from BTS, if the downlink TBF
establishment is due to downlink self-recovered reestablishment, then the counter
increments.
Unit
Times
27.33 C901210032 LLC transfer fail Num via cell

reselection
1. V6.20.200a ~ V6.20.200e
a. Description
frames failed to be transferred within BSC when cell reselection occurs.
b. Usage
after LLC frame transferring is initiated due to cell reselection.
When PS control plane receives the indication of LLC frame transferring failure
from PS user plane, if the LLC frame transferring is due to cell reselection, then
d. Unit
Times
2. V6.20.200f
27.34 C901210033 LLC transfer fail Num not via cell

reselection
1. V6.20.200a ~ V6.20.200e
a. Description
frames failed to be transferred within BSC when no cell reselection occurs (such
as when uplink and downlink TBFs are established simultaneously).
27-27

b. Usage
after LLC frame transferring is initiated not due to cell reselection.
When PS control plane receives the indication of LLC frame transferring failure
from PS user plane, if the LLC frame transferring is not due to cell reselection,
d. Unit
Times
2. V6.20.200f
27-28

Chapter 28
Gb Interface Message
Statistics
Table of Contents
Overview ..................................................................................................................28-2
C901220001 Sum of UL UNITDATA messages handled at BSSGP level..................28-2
C901220002 Sum of DL UNITDATA messages handled at BSSGP level..................28-3
C901220003 Number of receiving RA-CAPABILITY message ..................................28-4
C901220004 Number of PTP packet paging received by BSC..................................28-5
C901220005 Number of PTP circuit paging received by BSC...................................28-6
C901220006 Number of RA-CAPABILITY-UPDATE message sent...........................28-6
C901220007 Number of RA-CAPABILITY-UPDATE-ACK message received............28-7
C901220008 Number of wireless status PDU messages sent by BSC......................28-8
C901220009 Number of wireless status messages sent by BSC due to losing
wireless association with MS ....................................................................................28-9
C901220010 Number of wireless status messages sent by BSC due to bad link
quality ....................................................................................................................28-10
C901220011 Number of wireless status messages sent by BSC due to cell
reselection command .............................................................................................28-10
C901220012 Number of FLOW-CONTROL-BVC messages sent by BSC .............. 28-11
C901220013 Number of FLOW-CONTROL-BVC-ACK messages received by
BSC ....................................................................................................................... 28-11
C901220014 Number of FLOW-CONTROL-MS messages sent by BSC ................28-12
C901220015 Number of FLOW-CONTROL-MS-ACK messages received by BSC .28-13
C901220016 Number of FLOW-CONTROL-PFC messages sent by BSC ..............28-14
C901220017 Number of FLOW-CONTROL-PFC-ACK messages received by
BSC .......................................................................................................................28-15
C901220018 Number of status messages sent by BSC .........................................28-16
C901220019 Number of status messages received by BSC ...................................28-17
C901220020 Number of status messages sent with BVCI Unknown ......................28-18
C901220021 Number of Status messages sent with cell service congestion ..........28-19
C901220022 Number of status messages sent with protocol error .........................28-19
C901220023 Number of status messages sent with Processor overload ................28-19
C901220024 Number of status messages received with BVCI Unknown................28-20
C901220025 Number of status messages received with cell service congestion ....28-20
C901220026 Number of status messages received with protocol error...................28-20
C901220027 Number of status messages received with processor overload..........28-21
C901220028 Number of DOWNLOAD-BSS-PFC messages sent by BSC ..............28-21
28-1

C901220029 Number of BVCCREATE-BSS-PFC messages received by BSC.......28-22

C901220030 Number of CREATE-BSS-PFC-ACK messages sent by BSC ............28-23
C901220031 Number of CREATE-BSS-PFC-NACK messages sent by BSC..........28-24
C901220032 Number of MODIFY-BSS-PFC messages sent by BSC .....................28-25
C901220033 Number of MODIFY-BSS-PFC-ACK messages received by BSC ......28-26
C901220034 Number of DELETE-BSS-PFC messages received by BSC ..............28-27
C901220035 Number of DELETE-BSS-PFC-ACK messages sent by BSC.............28-28
C901220036 Number of DELETE-BSS-PFC-REQ messages received by BSC......28-29
C901220037 Number of PS-HANDOVER-REQUIRED messages sent by BSC......28-29
C901220038 Number of PS-HANDOVER-REQUIRED-ACK messages received by
BSC .......................................................................................................................28-30
C901220039 Number of PS-HANDOVER-REQUIRED-NACK messages received
by BSC...................................................................................................................28-31
C901220040 Number of PS-HANDOVER-REQUEST messages received by BSC .28-32
C901220041 Number of PS-HANDOVER-REQUEST-ACK messages sent by
BSC .......................................................................................................................28-33
C901220042 Number of PS-HANDOVER-REQUEST-NACK messages sent by
BSC .......................................................................................................................28-34
C901220043 Number of PS-HANDOVER-COMPLETE messages sent by BSC.....28-36
C901220044 Number of PS-HANDOVER-CANCEL messages sent by BSC..........28-37
C901220045 Number of PS-HANDOVER-REQUEST messages with Service
UTRAN CCO received by BSC...............................................................................28-38
C901220046 Number of CREATE-BSS-PFC messages with Service UTRAN CCO
received by BSC ....................................................................................................28-39
28.1 Overview
Gb interface message statistics mainly measures transmission number of different
PTP messages at Gb BSSGP level in GPRS service (such as RA-CAPABILITY,
RADIO-STATUS, DOWNLOAD-BSS-PFC).
28.2 C901220001 Sum of UL UNITDATA messages

handled at BSSGP level
Description
This counter counts the number of sending UL-UNITDATA PDU to SGSN by BSC.
Measurement Point
This counter increments each time BSC sends a UL-UNITDATA message. The
28-2

Chapter 28 Gb Interface Message Statistics
Figure 28-1 Measurement Point of sum of UL UNITDATA message handled at BSSGP

level
Unit
Times
28.3 C901220002 Sum of DL UNITDATA messages

Description
SGSN sends DL-UNITDATA PDU to BSC, and this counter counts the number of receiving
this message by BSC.
Measurement Point
This counter increments each time BSC receives a DL-UNITDATA message. The
28-3

Figure 28-2 Measurement point of sum of DL UNITDATA message handled at BSSGP

level
Unit
Times
28.4 C901220003 Number of receiving RA-CAPABILITY

message
Description
SGSN sends RA-CAPABILITY message to BSC, to indicate wireless capability of MS. This
counter counts the number of receiving this message.
Measurement Point
When BSC receives a RA-CAPABILITY message, this counter increments. The
28-4

Figure 28-3 Measurement Point of Number of RA-CAPABILITY message recevied
Unit
Times
28.5 C901220004 Number of PTP packet paging

received by BSC
Description
SGSN sends PTP packet paging message, to indicate BSC originate PTP packet paging
for MS. This counter counts the number of receiving this message by BSC.
Measurement Point
Figure 28-4 PTP Packet Paging Process
28-5

Unit
Times
28.6 C901220005 Number of PTP circuit paging

received by BSC
Description
SGSN sends the PTP circuit paging message to indicate BSC to initiate PTP circuit paging
for MS. This counter counts the number of BSC's receiving this message.
Measurement Point
Figure 28-5 PTP Circuit Paging Process
Unit
Times
28.7 C901220006 Number of RA-CAPABILITY-UPDATE

message sent
Description
BSC sends the RA-CAPABILITY-UPDATE message to SGSN to request for the current
wireless capability of MS. This counter counts the number of BSC's sending this message.
28-6

Measurement Point
When BSC sends a RA-CAPABILITY-UPDATE message to SGSN, this counter
increments. The measurement point is A1, as shown in Figure 28-6.
Figure 28-6 RA-CAPABILITY-UPDATE Process
Unit
Times
28.8 C901220007 Number of RA-CAPABILITY-UPDATE-

ACK message received
Description
SGSN sends RA-CAPABILITY-UPDATE-ACK message to BSC, to indicate current
wireless capability of MS. This counter counts the number of receiving this message by
BSC.
Measurement Point
When BSC receives a RA-CAPABILITY-UPDATE-ACK message from SGSN, this
counter increments. The measurement point is A2, as shown in Figure 28-7.
28-7

Unit
Times
28.9 C901220008 Number of wireless status PDU

messages sent by BSC
Description
BSC sends the wireless status PDU message to indicate SGSN that abnormality occurs
at radio interface. This counter counts the number of BSC's sending this message.
Usage
The radio interface status can be checked by counting this message.
Measurement Point
When BSC sends a RADIO-STATUS message to SGSN, this counter increments. The
28-8

Figure 28-8 RADIO-STATUS Process
Unit
Times
28.10 C901220009 Number of wireless status messages

sent by BSC due to losing wireless association
with MS
Description
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio
interface. This counter counts the number of BSC's sending this message due to Losing
wireless association with MS.
Usage
Measurement Point
When BSC sends a RADIO-STATUS message to SGSN due to Losing wireless
association with MS, this counter increments.
Unit
Times
28-9


sent by BSC due to bad link quality
Description
interface. This counter counts the number of BSC's sending this message due to bad link
quality.
Usage
Measurement Point
When BSC sends a RADIO-STATUS message to SGSN due to bad link quality, this
counter increments.
Unit
Times

sent by BSC due to cell reselection command
Description
interface. This counter counts the number of BSC's sending this message due to cell
reselection command.
Usage
Measurement Point
When BSC sends a RADIO-STATUS message to SGSN due to cell reselection
command, this counter increments.
Unit
Times
28-10

28.13 C901220012 Number of FLOW-CONTROL-BVC

Description
BSC sends the FLOW-CONTROL-BVC message to notify SGSN of the current BVC flow
control policy. This counter counts the number of BSC's sending this message.
Measurement Point
When BSC sends a FLOW-CONTROL-BVC message, this counter increments. The
Figure 28-9 FLOW-CONTROL-BVC Process
Unit
Times
28.14 C901220013 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 counts the number of BSC's receiving
this message.
28-11

Measurement Point
When BSC receives a FLOW-CONTROL-BVC-ACK message, this counter increments.
Unit
Times
28.15 C901220014 Number of FLOW-CONTROL-MS

Description
BSC sends the FLOW-CONTROL-MS message to notify SGSN of the current MS flow
Measurement Point
When BSC sends the FLOW-CONTROL-MS message, this counter increments. The
28-12

Figure 28-11 FLOW-CONTROL-MS Process
Unit
Times
28.16 C901220015 Number of FLOW-CONTROL-MS-AC

K 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 counts the number of BSC's receiving this
message.
Measurement Point
When BSC receives a FLOW-CONTROL-MS-ACK message, this counter increments. The
28-13

Unit
Times
28.17 C901220016 Number of FLOW-CONTROL-PFC

Description
BSC sends the FLOW-CONTROL-PFC message to notify SGSN of the flow control policy
for one or multiple PFCs of designated MS. This counter counts the number of BSC's
sending this message.
Measurement Point
When BSC sends the FLOW-CONTROL-PFC message, this counter increments. The
28-14

Figure 28-13 FLOW-CONTROL-PFC Process
Unit
Times
28.18 C901220017 Number of FLOW-CONTROL-PFC-

Description
SGSN sends the FLOW-CONTROL-PFC-ACK message to notify BSC that the PFC flow
control policy for designated MS is accepted. This counter counts the number of BSC's
receiving this message.
Measurement Point
When BSC receives a FLOW-CONTROL-PFC-ACK message, this counter increments.
28-15

Unit
Times
28.19 C901220018 Number of status messages sent

by BSC
Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter
counts the number of BSC's sending this message.
Measurement Point
When BSC sends the STATUS message, this counter increments. The measurement point
28-16

Figure 28-15 STATUS Process
Unit
Times
28.20 C901220019 Number of status messages

received by BSC
Description
SGSN sends the status message to BSC to indicate that abnormality occurs. This counter
counts the number of BSC's receiving this message.
Measurement Point
When BSC receives the STATUS message, this counter increments. The measurement
28-17

Unit
Times

with BVCI Unknown
Description
counts the number of BSC's sending this message due to BVCI Unknown.
Measurement Point
When BSC sends a "STATUS" message due to BVCI Unknown, this counter increments.
Unit
Times
28-18

28.22 C901220021 Number of Status messages sent

with cell service congestion
Description
counts the number of BSC's sending this message due to cell service congestion.
Measurement Point
When BSC sends a STATUS message due to cell service congestion, this counter
increments.
Unit
Times

with protocol error
Description
counts the number of BSC's sending this message due to protocol error.
Measurement Point
When BSC sends a STATUS message due to protocol error, this counter increments.
Unit
Times

with Processor overload
Description
BSC sends status message to SGSN, to indicate exception occurred. This counter counts
the number of sending this message by BSC due to processor overload.
Measurement Point
When BSC sends a STATUS message due to processor overload, this counter
increments.
28-19

Unit
Times

received with BVCI Unknown
Description
SGSN sends status message to BSC, to indicate exception occurred. This counter counts
the number of receiving this message by BSC due to BVCI Unknown.
Measurement Point
When BSC receives a STATUS message due to BVCI Unknown, this counter increments.
Unit
Times

received with cell service congestion
Description
the number of receiving this message by BSC due to cell service congestion.
Measurement Point
When BSC receives a STATUS message due to cell service congestion, this counter
increments.
Unit
Times

received with protocol error
Description
the number of receiving this message by BSC due to protocol error.
28-20

Measurement Point
When BSC receives a STATUS message due to protocol error, this counter increments.
Unit
Times

received with processor overload
Description
the number of receiving this message by BSC due to processor overload.
Measurement Point
When BSC receives a STATUS message due to processor overload, this counter
increments.
Unit
Times
28.29 C901220028 Number of 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 number of BSC's sending this
message.
Measurement Point
When BSC sends the DOWNLOAD-BSS-PFC message, this counter increments. The
28-21

Figure 28-17 CREATE-BSS-PFC Process
Unit
Times
28.30 C901220029 Number of BVCCREATE-BSS-PFC

messages received by BSC
Description
SGSN sends the CREATE-BSS-PFC message to request BSC to create or modify a packet
flow control context. This counter counts the number of BSC's receiving this message.
Measurement Point
When BSC receives a CREATE-BSS-PFC message, this counter increments. The
28-22

Unit
Times
28.31 C901220030 Number of 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 context. This counter counts the number of
BSC's sending this message.
Measurement Point
When BSC sends a CREATE-BSS-PFC-ACK message, this counter increments. The
28-23

Unit
Times
28.32 C901220031 Number of CREATE-BSS-PFC-NACK

Description
BSC sends the CREATE-BSS-PFC-NACK message to deny the request of SGSN creating
or modifying a packet flow control context. This counter counts the number of BSC's
Measurement Point
When BSC sends a CREATE-BSS-PFC-NACK message, this counter increments. The
28-24

Unit
Times
28.33 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 number of BSC's sending this message.
Measurement Point
When BSC sends the MODIFY-BSS-PFC message, this counter increments. The
28-25

Figure 28-21 MODIFY-BSS-PFC Process
Unit
Times
28.34 C901220033 Number of MODIFY-BSS-PFC-ACK

Description
SGSN sends the MODIFY-BSS-PFC-ACK message to BSC to confirm the modification
of packet flow control context. This counter counts the number of BSC's receiving this
message.
Measurement Point
When BSC receives a MODIFY-BSS-PFC-ACK message, this counter increments. The
28-26

Unit
Times
28.35 C901220034 Number of DELETE-BSS-PFC

Description
SGSN sends the DELETE-BSS-PFC message to request BSC to delete a packet flow
control context. This counter counts the number of BSC's receiving this message.
Measurement Point
When BSC receives a DELETE-BSS-PFC message, this counter increments. The
28-27

Figure 28-23 DELETE-BSS-PFC Process
Unit
Times
28.36 C901220035 Number of 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 Point
When BSC sends a DELETE-BSS-PFC-ACK message, this counter increments. The
28-28

Unit
Times
28.37 C901220036 Number of DELETE-BSS-PFC-REQ

Description
28.38 C901220037 Number of PS-HANDOVER-REQUIR

ED 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 measurement point is A, as shown in Figure 28-25.
28-29

Figure 28-25 Measurement Point of Number of PS-HANDOVER-REQUIRED messages

sent by BSC
Unit
Times

ED-ACK messages received by BSC
Statistics object
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
28-30

Figure 28-26 Measurement Point of Number of PS-HANDOVER-REQUIRED-ACK

Unit
Times

ED-NACK messages received by BSC
Statistics object
BSC
Description
If SGSN receives the non-acknowledgement message for PS handover request from
BSC, then SGSN sends the PS-HANDOVER-REQUIRED-NACK message back to
BSC. This counter counts the number of PS-HANDOVER-REQUIRED-NACK messages
received by BSC from SGSN. The counter increments when BSC receives the
PS-HANDOVER-REQUIRED-NACK message. The measurement point is A, as shown in
Figure 28-27.
28-31

Figure 28-27 Measurement Point of Number of PS-HANDOVER-REQUIRED-NACK

Unit
Times
28.41 C901220040 Number of PS-HANDOVER-REQUES

T messages received by BSC
Statistics object
BSC
Description
This counter counts the number of PS-HANDOVER-REQUEST messages
received by BSC from SGSN. The counter increments when BSC receives the
PS-HANDOVER-REQUEST message. The measurement point is A2, as shown in Figure
28-28.
28-32

Figure 28-28 Measurement Point of Number of PS-HANDOVER-REQUEST messages

received by BSC
Unit
Times
28.42 C901220041 Number of PS-HANDOVER-REQUE

ST-ACK messages sent by BSC
Statistics object
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 point is A3, as shown in Figure 28-29.
28-33

Figure 28-29 Measurement Point of Number of PS-HANDOVER-REQUEST-ACK

Unit
Times

T-NACK messages sent by BSC
Statistics object
BSC
28-34

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 failure of creating MS or PS instance, sent by BSC. The counter increments
when BSC sends the PS-HANDOVER-REQUEST-NACK message. The measurement
Figure 28-30 Measurement Point of Number of PS-HANDOVER-REQUEST-NACK

Unit
Times
28-35

28.44 C901220043 Number of PS-HANDOVER-COMPLE

TE messages sent by BSC
Statistics object
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.
Figure 28-31 Measurement Point of Number of PS-HANDOVER-COMPLETE messages

sent by BSC
Unit
Times
28-36

28.45 C901220044 Number of PS-HANDOVER-CANCEL

Statistics object
BSC
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-HANDOVER-CANCEL message. The measurement point is A, as shown
in Figure 28-32.
Figure 28-32 Measurement Point of Number of PS-HANDOVER-CANCEL messages

sent by BSC
Unit
Times
28-37


ST messages with Service UTRAN CCO received
by BSC
Statistics object
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 decodes the message to decide
whether the message contains the field Service UTRAN CCO. If the message contains
the field, the counter increments. The measurement point is A, as shown in Figure 28-33.

with Service UTRAN CCO received by BSC
Unit
Times
28-38

28.47 C901220046 Number of CREATE-BSS-PFC

messages with Service UTRAN CCO received by
BSC
Statistics object
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 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 28-34 Measurement Point of Number of CREATE-BSS-PFC messages with

Service UTRAN CCO received by BSC
Unit
Times
28-39

28-40

Chapter 29
TRX Measurement
Table of Contents
Overview ..................................................................................................................29-2
C901230001 Number of intra-cell handover in attempts ...........................................29-3
C901230002 Number of intra-cell handover ins success ..........................................29-4
C901230003 Number of Intra-BSC inter-cell handover in attempts ...........................29-5
C901230004 Number of Intra-BSC intra-cell handover ins success ..........................29-5
C901230005 Number of Intra-MSC inter-cell handover in attempts ..........................29-6
C901230006 Number of Intra-MSC inter-cell handover ins success .........................29-7
C901230007 TCH busy time ....................................................................................29-8
C901230008 Number of TCH seizures (including handover) ....................................29-9
C901230009 Number of call drops due to TCH LAPD breakage...............................29-9
C901230010 Number of call drops due to TCH radio link failure...............................29-9
C901230011 Number of TCH handover call drops..................................................29-10
C901230012 Number of TCH/F activation attempts (including handover) ............... 29-11
C901230013 Number of TCH/F activation success (including handover)................29-12
C901230014 Number of TCH/F assignment attempts.............................................29-13
C901230015 Number of TCH/F assignment success .............................................29-14
C901230016 Number of TCH/H activation attempts (including handover)...............29-15
C901230017 Number of TCH/H activation success (including handover) ...............29-16
C901230018 Number of TCH/H assignment attempts ............................................29-17
C901230019 Number of TCH/H assignment success .............................................29-18
C901230020 SDCCH busy time .............................................................................29-19
C901230021 Number of attempts for SDCCH ........................................................29-20
C901230022 Number of SDCCH call drops............................................................29-20
C901230023 Number of SDCCH activation attempts (including handover) .............29-22
C901230024 Number of SDCCH activation success (including handover)..............29-22
C901230025 Number of SDCCH assignment attempts ..........................................29-23
C901230026 Number of SDCCH assignment success ...........................................29-24
C901230027 Number of samples with UL RQ = 0 ..................................................29-25
C901230035 Number of samples with DL RQ = 0 ..................................................29-30
29-1


C901230049 Mean number of idle TCH/Hs with interference band 0......................29-38
C901230061 Number of TRX poweroff...................................................................29-44
C901230062 Duration of TRX poweroff ..................................................................29-44
C901230069 Number of uplink error frame on HR_V1............................................29-47
C901230070 Total Number of uplink frame on HR_V1............................................29-47
C901230071 Number of uplink error frame on HR_V3............................................29-48
C901230072 Total Number of uplink frame on HR_V3............................................29-48
29.1 Overview
TRX measurement is to measure the success or failure condition of channel activation,
assignment, and handover in the unit of carrier. It also can measure carrier interference
band, maximum and minimum UL & DL level condition, to learn the status of different
carriers, providing evidence for adjustment and maintenance.
29-2

Chapter 29 TRX Measurement
29.2 C901230001 Number of intra-cell handover in

attempts
Definition
Number of intra-cell handover in attempts.
Description
Normally, intra-cell handover is triggered by receiving level, receiving quality, interference,
and concentric circle, its source cell is same as target cell. During intra-cell handover,
first send CHANNEL ACTIVATE message to target channel, and BTS responds CHANNEL
ACTIVATE ACK message.
Measurement Point
During intra-cell handover, measurement point will be counted after BSC receives
CHANNEL ACTIVATE ACK. The measurement point is A, as shown in Figure 29-1.
Figure 29-1 - Intra-cell Handover
Unit
Times
Related Features
29-3

29.3 C901230002 Number of intra-cell handover ins

success
Definition
Number of intra-cell handover ins success.
Description
During intra-cell handover, after target channel is successfully activated, BSC will send
ASSIGNMENT COMMAND message to MS through source channel. After BSC receives
ASSIGNMENT COMPLETE of MS from target channel, intra-cell handover is successfully
completed.
Measurement Point
During intra-cell handover, the measurement point will be counted after receive
ASSIGNMENT COMPLETE. The measurement point is A2, as shown in Figure 29-2.
Figure 29-2 - Intra-cell Handover
Unit
Times
Related Features
29-4

29.4 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 handover, first send CHANNEL ACTIVATE message to
target channel.
Measurement Point
During inter-cell handover controlled by BSC, measurement point will be counted after
BSC receives CHANNEL ACTIVATE ACK message. The measurement point is A1, as
Figure 29-3 - Inter-Cell Handover Controlled By BSC
Unit
Times
Related Features
29.5 C901230004 Number of Intra-BSC intra-cell

handover ins success
Definition
Number of Intra-BSC intra-cell handover ins success.
29-5

Description
During inter-cell handover controlled by BSC, after target channel is successfully
activated, BSC will send handover command to MS through source channel. After BSC
receives HANDOVER COMPLETE message of MS from target channel, inter-cell handover
is successfully completed.
Measurement Point
During inter-cell handover controlled by BSC, measurement point will be counted after
BSC receives HANDOVER COMPLETE message. The measurement point is A2, as shown
in Figure 29-4.
Unit
Times
Related Features
29.6 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 receives HANDOVER
REQUEST message from MSC. After BSC receives handover request message, first send
CHANNEL ACTIVATE to acquisition target channel.
29-6

Measurement Point
During inter-cell handover (incoming) controlled by MSC, measurement point will be
counted after BSC receives CHANNEL ACTIVATE ACK. The measurement point is A1,
Unit
Times
Related Features
29.7 C901230006 Number of Intra-MSC inter-cell

handover ins success
Definition
Number of Intra-MSC inter-cell handover ins success.
Description
During inter-cell handover controlled by MSC, after target channel is successfully activated
and target channel receives HANDOVER COMPLETE message sent by MS, handover is
successfully done.
Measurement Point
During inter-cell handover controlled by MSC, measurement point will be counted after
BSC receives HANDOVER COMPLETE message from MS. The measurement point is A2,
29-7

Unit
Times
Related Features
29.8 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 Point
There are 3 measurement points:
l Accumulate while successfully acquire voice channel resource
l Accumulate while release voice channel resource
l Accumulate by regular measurement and acquisition
Unit
Second
29-8

29.9 C901230008 Number of 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 Point
Count while successfully acquire voice channel service.
Unit
Times
29.10 C901230009 Number of call 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 interrupted, and this counter
will record call interruption condition caused by disconnected LAPD.
Measurement Point
Count while receive LAPD Disconnected message.
Unit
Times
29.11 C901230010 Number of call drops due to TCH

radio link failure
Definition
Number of call drops due to TCH radio link failure.
29-9

Description
When radio link quality is poor or level is low, and unable to change to other cells, the call
on carrier will be interrupted. This counter records the call interruption condition caused
by radio link failure.
Measurement Point
Count while receiving radio link failure message. The measurement point is A, as shown
in Figure 29-7.
Figure 29-7 - BSC Receives Radio Link Failure Message Reported By BTS
Unit
Times
29.12 C901230011 Number of 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 doesnt 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 Point
This counter will count at following cases:
l When receiving T3013 timer timeout message. The measurement point is A2, as
29-10

Figure 29-8 - Inter-Cell Handover Failure
l When receiving T3107 timer timeout message. The measurement point is A2, as
shown in .Figure 29-9.
Figure 29-9 - Intra-Cell Handover Failure
Unit
Times
29.13 C901230012 Number of 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.
29-11

Measurement Point
Count after BSC sends CHANNEL ACTIVATE message to BTS. The measurement point
is A1, as shown inFigure 29-10.
Figure 29-10 - Channel Activation Measurement Point
Unit
Times
Related Features
29.14 C901230013 Number of TCH/F activation success

(including handover)
Definition
Number of TCH/F activation success (including handover)
Description
Count the number of successful activation from carrier TCH/F channel.
Measurement Point
Count after BSC receives CHANNEL ACTIVATE ACK message. The measurement point
is A2, as shown inFigure 29-11 .
29-12

Unit
Times
Related Features

attempts
Definition
Number of TCH/F assignment attempts.
Description
Count the number of sending ASSIGNMENT COMMAND by BSC while assigning TCH/F
channel.
Measurement Point
Count after BSC sends ASSIGNMENT COMMAND message to BTS. The measurement point
is A1, as shownFigure 29-12.
29-13

Figure 29-12 - TCH/F Channel Assignment Measurement Point
Unit
Times
Related Features

success
Definition
Number of TCH/F assignment success
Description
When assign TCH/F channel, BSC sends ASSIGNMENT COMMAND message to
assignment channel, after BSC receives EST IND or ASSIGNMENT COMPLETE message,
channel assignment is successful.
Measurement Point
Count after BSC receives EST IND or ASSIGNMENT COMPLETE message. The
29-14

Unit
Times
Related Features
29.17 C901230016 Number of TCH/H activation

Definition
Number of TCH/H activation attempts (including handover).
Description
Count the number of originating channel activation from carrier TCH/H channel.
Measurement Point
is A1, as shown inFigure 29-14.
29-15

Unit
Times
Related Features
l ZGO-01-01-001 Half Rate
l ZGO-03-02-005 Dynamic Half Rate Allocation
29.18 C901230017 Number of TCH/H activation success

(including handover)
Definition
Number of TCH/H activation success (including handover).
Description
Count the number of successful activation from carrier TCH/H channel.
Measurement Point
29-16

Unit
Times
Related Features

attempts
Definition
Number of TCH/H assignment attempts
Description
Count the number of sending ASSIGNMENT COMMAND by BSC while assigning TCH/H
channel.
Measurement Point
Count after BSC sends ASSIGNMENT COMMAND message to BTS. The measurement point
29-17

Unit
Times
Related Features

success
Definition
Number of TCH/H assignment success
Description
When assign TCH/H channel, BSC sends ASSIGNMENT COMMAND message to
assignment channel, after BSC receives EST IND or ASSIGNMENT COMPLETE message,
channel assignment is successful.
Measurement Point
Count after BSC receives EST IND or ASSIGNMENT COMPLETE message. The
measurement point is A2, as shown inFigure 29-17 .
29-18

Unit
Related Features
29.21 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 measured time will be changed to current time;
when SDCCH channel is seized, the number of MS seizing channel will be incremented
after accumulation; when SDCCH channel is released, the number of MS seizing channel
will be decremented after accumulation.
Measurement Point
There are 3 measurement points as follows.
l Accumulate while successfully acquire SDCCH channel resource
l Accumulate while release SDCCH channel resource
l Accumulate by regular measurement and acquisition
29-19

Unit
Times
29.22 C901230021 Number of attempts for SDCCH

Definition
Number of attempts for SDCCH
Description
Count the number of successful and failed SDCCH application during assignment and
handover.
Measurement Point
Count after BSC applying for SDCCH is successful or failed.
Unit
Times
29.23 C901230022 Number of SDCCH call drops

Definition
Number of SDCCH call drops
Description
During assignment and handover, ASSIGNMENT COMPLETE or HANDOVER COMPLETE is
not received after send ASSIGNMENT COMMAND or HANDOVER COMMAND message. After
T3103 or T3107 timer times out, it is considered as SDCCH failure, see Figure 29-18
andFigure 29-19.
Figure 29-18 - Inter-Cell Handover Failure
29-20

Figure 29-19 - 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 29-20 .
Figure 29-20 - THoOutGo Timeout
In addition, when LAPD is broken or disconnected, if channel is SDCCH, it will be recorded

as SDCCH call drops.
Measurement Point
This counter will count at following cases:
l When BSC receives LAPD breakage message and channel is SDCCH.

l When BSC connection faults and channel is SDCCH.
l After THoOutGo timer times out.
l After T3103 timer times out.
l After T3107 timer times out.
Unit
Times
29-21

29.24 C901230023 Number of SDCCH activation

Definition
Number of SDCCH activation attempts (including handover)
Description
Count the number of originating CHANNEL ACTIVATE messages from carrier SDCCH
channel.
Measurement Point
Unit
Times
29.25 C901230024 Number of SDCCH activation

success (including handover)
Definition
Number of SDCCH activation success (including handover)
Description
Count the number of successful activation from carrier SDCCH channel.
29-22

Measurement Point
Unit
Times

attempts
Definition
Number of SDCCH assignment attempts
Description
When assign SDCCH channel, BSC assigns SDCCH channels by sending IMMEDIATE
ASSIGNMENT message or ASSIGNMENT COMMAND message. This counter counts the
number of SDCCH assignment attempts.
Measurement Point
Count after BSC sends IMMEDIATE ASSIGNMENT message or ASSIGNMENT COMMAND
to BTS. The measurement point is A1, as shown in Figure 29-23.
29-23

Figure 29-23 - Channel Assignment Measurement Point
Unit
Times

success
Definition
Number of SDCCH assignment success
Description
When assign SDCCH channel, BSC sends IMMEDIATE ASSIGNMENT message or
ASSIGNMENT COMMAND message to assignment channel, after BSC receives EST IND
(CM SERV REQ), channel assignment is successful.
Measurement Point
Count after BSC receives EST IND (CM SERV REQ) message. The measurement point
29-24

Figure 29-24 - Channel Assignment Measurement Point
Unit
Times

Definition
Number of samples with UL RQ = 0
Description
BTS measures the level, quality, and interference of UL signal received in channel, and
reports it to BSC, in combination with measurement report of DL signal reported by MS.
Interval between BTS measurement and report is consistent with that of MS, that is, one
measurement report is reported to BSC per 480 ms.
Measurement mechanism of following counter C901230028 ~ C901230042 is same as
that of this measurement value.
This measurement value is the sample number with UL RQ=0 in measurement report.
Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=0 in measurement
report, this counter increments. The measurement point is A, as shown in Figure 29-25.
29-25

Figure 29-25 - BSC Receives the Measurement Report Submitted BY BTS
Unit
Times

Definition
Description
Measurement Point
Unit
Times

Definition
29-26

Description
Measurement Point
Unit
Times

Definition
Description
Measurement Point
report, this counter increments. The measurement point is A, as shown inFigure 29-28.
29-27

Unit
Times

Definition
Description
Measurement Point
Unit
Times

Definition
Description
Measurement Point
29-28

Unit
Times

Definition
Description
Measurement Point
Unit
Times

Description
29-29

Measurement Point
Figure 29-32 BSC Receives the Measurement Report Submitted by BTS
Unit
Times

Definition
Number of samples with DL RQ = 0
Description
This measurement value is the sample number with DL RQ=1 in measurement report.
Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=0 in measurement
Unit
Times
29-30


Definition
Description
Measurement Point
Unit
Times

Definition
Description
Measurement Point
29-31

Unit
Times

Definition
Description
Measurement Point
Unit
Times

Definition
29-32

Description
Measurement Point
Figure 29-37 - BSC Receives the Measurement Report Submitted By BTS
Unit
Times

Definition
Description
Measurement Point
29-33

Unit
Times

Definition
Description
Measurement Point
Unit
Times

Definition
Description
Measurement Point
29-34

Unit
Times

interference band 0
Definition
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.
Measurement mechanism of following counter C901230044 ~ 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 Point
Count when regularly query database.
Unit
Times
Related Features
29-35


interference band 1
Definition
Description
This measurement value is idle TCH/F number when interference band is 1 in carrier.
Measurement Point
Unit
Times
Related Features

interference band 2
Definition
Description
Measurement Point
Unit
Times
Related Features
29-36


interference band 3
Definition
Description
Measurement Point
Unit
Times
Related Features

interference band 4
Definition
Description
Measurement Point
Unit
Times
Related Features
29-37


interference band 5
Definition
Description
Measurement Point
Unit
Times
Related Features

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 band is 0 in carrier.
Measurement Point
Unit
Times
Related Features
29-38


interference band 1
Definition
Description
Measurement Point
Unit
Times
Related Features

interference band 2
Definition
Description
Measurement Point
Unit
Times
Related Features
29-39


interference band 3
Definition
Description
Measurement Point
Unit
Times
Related Features

interference band 4
Definition
Description
Measurement Point
Unit
Times
Related Features
29-40


interference band 5
Definition
Description
Measurement Point
Unit
Times
Related Features

interference band 0
Definition
Description
This measurement value is idle SDCCH number when interference band is 0 in carrier.
Measurement Point
Unit
Times
29-41


interference band 1
Definition
Description
Measurement Point
Unit
Times

interference band 2
Definition
Description
Measurement Point
Unit
Times

interference band 3
Definition
29-42

Description
Measurement Point
Unit
Times

interference band 4
Definition
Description
Measurement Point
Unit
Times

interference band 5
Definition
Description
Measurement Point
Unit
Times
29-43

29.62 C901230061 Number of TRX poweroff

Definition
Number of TRX power off.
Description
This counter counts the number of TRX smart power off, excluding normal POWER OFF.
Measurement Point
This counter increments during smart power on.
Unit
Times
Related Features
29.63 C901230062 Duration of TRX poweroff

Definition
Duration of TRX power off.
Description
This counter counts the duration of TRX power off.
Measurement Point
This counter increments during smart power on.
Unit
Times
Related Features
29-44


FR_V1
Description
Enable the function of reporting voice quality information, and count the number of error
frames of voice version 1 in the measurement report received on the FR channel.
Measurement Point
The counter counts when the measurement report (preprocessing measurement report or
enhanced measurement report) is received.
Unit
Times

FR_V1
Description
Enable the function of reporting voice quality information, and count the number of voice
Measurement Point
Unit
Times

FR_V2
Description
Measurement Point
29-45

Unit
Times

FR_V2
Description
Measurement Point
Unit
Times

FR_V3
Description
Measurement Point
Unit
Times

FR_V3
Description
29-46

Measurement Point
Unit
Times

HR_V1
Description
frames of voice version 1 in the measurement report received on the HR channel.
Measurement Point
Unit
Times

HR_V1
Description
Measurement Point
Unit
Times
29-47


HR_V3
Description
Measurement Point
Unit
Times

HR_V3
Description
Measurement Point
Unit
Times
29-48

Chapter 30
Timeslot Measurement
Table of Contents
Overview ..................................................................................................................30-2
C901240001 Maximum value of UL RQ ...................................................................30-2
C901240002 Minimum value of UL RQ ....................................................................30-3
C901240003 Value of UL RQ ...................................................................................30-3
C901240004 Number of scans of UL RQ .................................................................30-4
C901240005 Maximum value of DL RQ ...................................................................30-5
C901240006 Minimum value of DL RQ ....................................................................30-6
C901240007 Value of DL RQ ...................................................................................30-6
C901240008 Number of scans of DL RQ .................................................................30-7
C901240009 Maximum value of received UL signal strength....................................30-8
C901240010 Minimum value of received UL signal strength.....................................30-8
C901240011 Total value of received UL signal strength............................................30-9
C901240012 Number of received UL signal strength samples................................30-10
C901240013 Maximum value of received DL signal strength.................................. 30-11
C901240014 Minimum value of received DL signal strength...................................30-12
C901240015 Total value of received DL signal strength .........................................30-12
C901240016 Number of received DL signal strength samples................................30-13
C901240017 Value of power scans of MS transmitting power.................................30-14
C901240018 Number of power scans of MS transmitting power.............................30-15
C901240019 Value of power scans of BTS power ..................................................30-15
C901240020 Number of power scans of BTS power ..............................................30-16
C901240021 Number of immediate assignment failure...........................................30-17
C901240022 Number of assignment failure............................................................30-18
C901240023 Number of handovers failure .............................................................30-19
C901240024 Maximum interference value..............................................................30-20
C901240025 Minimum interference value...............................................................30-21
C901240026 Interference value .............................................................................30-21
C901240027 Number of regular scanning and sampling of interference value........30-22
C901240028 Number of call drop ...........................................................................30-23
C901240029 Maximum value of path balance ........................................................30-24
C901240030 Minimum value of path balance .........................................................30-24
C901240031 Value of path balance ........................................................................30-25
C901240032 Number of regular scanning and sampling of path balance................30-26
C901240033 Value of UL loss ................................................................................30-27
C901240034 Number of regular scanning and sampling of UL loss ........................30-27
C901240035 Total value of DL loss ........................................................................30-28
C901240036 Number of regular scanning and sampling of DL loss ........................30-29
30-1

C901240037 Number of drops due to the bad quality of UL receive .......................30-30

C901240038 Number of drops due to the bad quality of DL receive .......................30-31
C901240039 Number of drops due to the low electric level of UL ...........................30-33
C901240040 Number of drops due to the low electric level of DL ...........................30-35
C901240041 Number of drops due to the TA too far...............................................30-37
C901240042 Number of drops due to the other radio reasons................................30-39
C901240043 The valid time of the used voice channel ...........................................30-41
C901240044 Number of activated voice channel....................................................30-42
30.1 Overview
Timeslot counters are used to view the radio transceiver environment of a MS in a particular
timeslot, including the link quality and strength in the timeslot. These data is sent to
Network side through measurement report. If signal strength in some timeslots is weak,
then it can be improved by changing send and receive power.
The measurement takes cell as statistics unit.
30.2 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 Point
After BSC receives the measurement report from BTS, if UL RQ in the report is bigger than
the value in the counter, the UL RQ in the counter is replaced. The measurement point is
Figure 30-1 BSC Receives the measurement report submitted by BTS
30-2

Chapter 30 Timeslot Measurement
Unit
NA
30.3 C901240002 Minimum value 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 of a cell. It is one of the
Measurement Point
After BSC receives the measurement report from BTS, if UL RQ in the report is less than
the value in the counter, the UL RQ in the counter is replaced. The measurement point is
Unit
NA
30.4 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.
30-3

Usage
This counter is used to find out the Total value of UL RQ in a timeslot of a cell. It is one of
the parameters that evaluate timeslot radio environment.
Measurement Point
After BSC receives the measurement report from BTS, the counter accumulates UL RQ
value for relevant timeslot. The measurement point is A, as shown in Figure 30-3.
Unit
NA
30.5 C901240004 Number of 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
Measurement Point
The counter increments after BSC receives the measurement report from BTS. The
30-4

Unit
Times
30.6 C901240005 Maximum value of DL RQ

Definition
Maximum value of DL RQ
Description
This counter counts Maximum DL RQ in the measurement report of a timeslot in a cell.
Usage
This counter is used to find out the Maximum DL RQ in a timeslot of a cell. It is one of the
Measurement Point
After BSC receives the measurement report from BTS, if DL RQ in the report is bigger than
the value in the counter, the DL RQ is in the counter replaced. The measurement point is
A, as shown in Figure 30-5
Unit
NA
30-5

30.7 C901240006 Minimum value of DL RQ

Definition
Minimum DL RQ
Description
This counter counts Minimum DL RQ in the measurement report of a timeslot in a cell.
Usage
This counter is used to find out the Minimum DL RQ in a timeslot of a cell. It is one of the
Measurement Point
After BSC receives the measurement report from BTS, if DL RQ in the report is less than
the value in the counter, the DL RQ in the counter is replaced. The measurement point is
Unit
NA
30.8 C901240007 Value of DL RQ

Definition
Total value of DL RQ
Description
This counter counts the total value of DL RQ of a timeslot of a cell in the measurement
report.
Usage
This counter is used to find out the Total value of DL RQ in a timeslot of a cell. It is one of
30-6

Measurement Point
After BSC receives the measurement report from BTS, the counter accumulates DL RQ
Unit
NA
30.9 C901240008 Number of 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 in a cell. It is one of the
Measurement Point
30-7

Unit
Times
30.10 C901240009 Maximum value of received UL

signal strength
Definition
Maximum value of received UL signal strength
Description
This counter counts Maximum value of received UL signal strength in the measurement
report of a timeslot in a cell.
Usage
This counter is used to find out the Maximum value of received UL signal strength in a
timeslot of a cell. It is one of the parameters that evaluate timeslot radio environment.
Measurement Point
After BSC receives the measurement report from BTS, if received UL signal strength in
the report is bigger than the value in the counter, the received UL signal strength in the
counter is replaced. The measurement point is A, as shown in Figure 30-9.
Unit
dBm
30.11 C901240010 Minimum value of received UL

signal strength
Definition
Minimum value of received UL signal strength
30-8

Description
This counter counts Minimum value of received UL signal strength in the measurement
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 that evaluate timeslot radio environment.
Measurement Point
After BSC receives the measurement report from BTS, if the value of received UL signal
strength in the report is less than the value in the counter, the received UL signal strength
in the counter is replaced. The measurement point is A, as shown in Figure 30-10.
Unit
dBm
30.12 C901240011 Total value of received UL signal

strength
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.
30-9

Measurement Point
After BSC receives the measurement report from BTS, the counter accumulates UL
reception strength value for relevant timeslot. The measurement point is A, as shown in
Figure 30-11.
Unit
dBm
30.13 C901240012 Number of received UL signal

strength samples
Definition
Number of received UL signal strength samples
Description
This counter counts the number of times of sampling UL signal strength in a timeslot in a
cell.
Usage
This counter shows the frequency of sampling UL signal strength in a timeslot in a cell. It
is one of the parameters that evaluate timeslot radio environment.
Measurement Point
30-10

Unit
Times
30.14 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 in the measurement
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 that evaluate timeslot radio environment.
Measurement Point
After BSC receives the measurement report from BTS, if DL reception strength in the report
is bigger than the value in the counter, the DL reception strength in the counter is replaced.
Unit
dBm
30-11

30.15 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 in the measurement
Usage
This counter is used to find out the Minimum value of received DL signal strength in a
Measurement Point
After BSC receives the measurement report from BTS, if DL reception strength in the report
is less than the value in the counter, the DL reception strength in the counter is replaced.
Unit
dBm
30.16 C901240015 Total value of received DL signal

strength
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.
30-12

Usage
This counter is used to find out the total value of received DL signal strength in a timeslot
in a cell. It is one of the parameters that evaluate timeslot radio environment.
Measurement Point
After BSC receives the measurement report from BTS, the counter accumulates DL
reception strength value for relevant timeslot. The measurement point is A, as shown in
Figure 30-15.
Unit
dBm
30.17 C901240016 Number of received DL signal

strength 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 strength in a timeslot in
a cell. It is one of the parameters that evaluate timeslot radio environment.
Measurement Point
30-13

Unit
Times
30.18 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 evaluate timeslot radio environment.
Measurement Point
After BSC receives the measurement report from BTS, the counter accumulates MS power
Unit
dBm
30-14

30.19 C901240018 Number of power scans of MS

transmitting power
Definition
Number of power scans of MS transmitting power
Description
This counter counts the number of times of sampling MS transmitting power in a timeslot
in a cell.
Usage
This counter shows the frequency of sampling MS transmitting power in a timeslot in a cell.
It is one of the parameters that evaluate timeslot radio environment.
Measurement Point
Unit
Times
30.20 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.
30-15

Usage
This counter is used to find out the total value of BTS power in a timeslot in a cell. It is one
of the parameters that evaluate timeslot radio environment.
Measurement Point
After BSC receives the measurement report from BTS, the counter accumulates BTS
power value for relevant timeslot. The measurement point is A, as shown in Figure 30-19.
Unit
dBm
30.21 C901240020 Number of 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 in a timeslot in a cell. It
is one of the parameters that evaluate timeslot radio environment.
Measurement Point
30-16

Unit
dBm

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 in a timeslot in a cell.
Measurement Point
After BSC sent immediate assignment to MS, if access Timer overtimes, the counter
increments in relevant timeslot. The measurement point is A2, as shown in Figure 30-21.
In the waiting state, case release caused by any reason, leads immediate assignment
failure, then the counter increments in relevant timeslot. The measurement point is A1, as
30-17

Figure 30-21 Immediate Assignment Failure Measurement Point
Unit
Times
30.23 C901240022 Number of assignment failure

Definition
Number of assignment failure
Description
This counter counts the number of times of assignment failure in a timeslot in a cell.
Usage
This counter shows the frequency of assignment failure in a timeslot in a cell. It is one of
Measurement Point
After BSC sent assignment to MS, if access Timer overtimes, the counter increments in
relevant timeslot. The measurement point is A2, as shown in Figure 30-22.
In the waiting state, case release caused by any reason, leads assignment failure, then
the counter increments in relevant timeslot. The measurement point is A1, as shown in
Figure 30-22.
30-18

Figure 30-22 Assignment Failure Measurement Point
Unit
Times
30.24 C901240023 Number of 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 in a cell. It is one of the
Measurement Point
After BSC sent handover to MS, if access Timer overtimes, the counter increments in
relevant timeslot. The measurement point is A2, as shown in Figure 30-23.
In the waiting state, case release caused by any reason, leads handover failure, then the
counter increments in relevant timeslot. The measurement point is A1, as shown in Figure
30-23.
30-19

Figure 30-23 Handovers Failure Measurement Point
Unit
Times
30.25 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
Measurement Point
When BSC received resource indication from BTS updating interference band, if
interference band reported is bigger than the value in the counter, the value in the counter
is replaced. The measurement point is A, as shown in Figure 30-24.
Figure 30-24 Resource Indication Measurement Point
30-20

Unit
NA
30.26 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
Measurement Point
When BSC received resource indication from BTS updating interference band, if
interference band reported is less than the value in the counter, the value in the counter
is replaced. The measurement point is A, as shown in Figure 30-25.
Unit
NA
30.27 C901240026 Interference value

Definition
Total value of interference
Description
This counter counts the total value of interference band in a timeslot in a cell.
30-21

Usage
This counter is used to find out the total value of interference band in a timeslot in a cell.
Measurement Point
When BSC received resource indication from BTS updating interference band, the counter
accumulates interference value for relevant timeslot. The measurement point is A, as
Unit
NA
30.28 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
Measurement Point
The counter increments in relevant timeslot after BSC receives resource indication from
BTS updating interference band. The measurement point is A, as shown in Figure 30-27.
30-22

Unit
Times
30.29 C901240028 Number of call 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
Measurement Point
The counter increments in relevant timeslot after BSC receives radio link failure from BTS.
Unit
Times
30-23

30.30 C901240029 Maximum value of path balance

Definition
Maximum value of path balance
Description
This counter counts the Maximum value of path balance in a timeslot in a cell. Path balance
is the path loss margin of UL and DL path.
Usage
This counter shows the Maximum value of path balance in a timeslot in a cell. It is one of
Measurement Point
When BSC receives measurement report from BTS, calculate the current path loss. Then
path balance is calculated according UL and DL path loss. If the path balance calculated
is more than the value in the counter, then the value in the counter is replaced. The
Unit
dBm
30.31 C901240030 Minimum value of path balance

Definition
Minimum value of path balance
Description
This counter counts the Minimum value of path balance in a timeslot in a cell. Path balance
is the path loss margin of UL and DL path.
30-24

Usage
This counter shows the Minimum value of path balance in a timeslot in a cell. It is one of
Measurement Point
path balance is calculated according UL 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
30.32 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 timeslot in a cell. It is
one of the parameters that evaluate timeslot radio environment.
Measurement Point
path balance is calculated according UL and DL path loss. The counter accumulates the
path balance for relevant timeslot. The measurement point is A, as shown in Figure 30-31.
30-25

Unit
dBm

sampling of path balance
Definition
Number of path balance sampling
Description
This counter counts the number of path balance sampling in a timeslot in a cell.
Usage
This counter is used to find out the frequency of path balance sampling in a timeslot in a
cell. It is one of the parameters that evaluate timeslot radio environment.
Measurement Point
The counter increments in relevant timeslot when BSC receives measurement point from
BTS and calculates path balance. The measurement point is A, as shown in Figure 30-32.
Unit
Times
30-26

30.34 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 timeslot in a cell. It is one of
Measurement Point
path balance is calculated according UL and DL path loss. The counter accumulates the
path balance for relevant timeslot. The measurement point is A, as shown in Figure 30-33.
Unit
dBm

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

Usage
This counter is used to find out the frequency of sampling in UL path in a timeslot in a cell.
It is one of the parameters that evaluate radio environment.
Measurement Point
When BSC receives measurement report from BTS, calculate the current UL path loss.
The counter increments if UL path loss is valid. The measurement point is A, as shown in
Figure 30-34.
Unit
Times
30.36 C901240035 Total value of 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.
Measurement Point
When BSC receives measurement report from BTS, calculate the current DL path loss.
The counter increments if DL path loss is valid. The measurement point is A, as shown in
Figure 30-35.
30-28

Unit
dB

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.
Measurement Point
When BSC receives measurement report from BTS, calculate the current UL path loss.
The counter increments if DL path loss is valide. The measurement point is A, as shown
in Figure 30-36.
Unit
Times
30-29

30.38 C901240037 Number of drops due to the bad

quality of UL receive
Definition
Number of drops due to the bad quality of UL receive
Description
This counter counts the number of call drops on some timeslot in the cell due to radio link
failure. After MS obtains SDCCH or TCH, call drop occurs. If the problem is caused by
bad uplink receiving quality, the counter increments.
Usage
This counter is used to find out the frequency of call drop on some timeslot due to radio
link failure which is caused by bad uplink receiving quality. It is one of the radio parameters
that evaluate the timeslot.
Measurement Point
l The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn
message at Abis interface on SDCCH. The measurement point is A, as shown in
Figure 30-37.
Figure 30-37 Call Drop due to Radio Link Failure during Immediate Assignment
Process
message at Abis interface on TCH. The measurement point is A, as shown in
Figure 30-38.
30-30

Figure 30-38 Call Drop due to Radio Link Failure during Assignment Process
Unit
Times
30.39 C901240038 Number of drops due to the bad

quality of DL receive
Definition
Number of drops due to the bad quality of DL receive
Description
bad downlink receiving quality, the counter increments.
30-31

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 downlink receiving quality. It is one of the radio parameters
Measurement Point
Figure 30-39.
Process
Figure 30-40.
30-32

Unit
Times
30.40 C901240039 Number of drops due to the low

electric level of UL
Definition
Number of drops due to the low electric level of UL
Description
low uplink receiving level, the counter increments.
30-33

Usage
link failure which is caused by low uplink receiving level. It is one of the radio parameters
Measurement Point
Figure 30-41.
Process
Figure 30-42.
30-34

Unit
Times
30.41 C901240040 Number of drops due to the low

electric level of DL
Definition
Number of drops due to the low electric level of DL
Description
low downlink receiving level, the counter increments.
30-35

Usage
failure which is caused by low downlink receiving level. It is one of the radio parameters
Measurement Point
Figure 30-43.
Process
Figure 30-44.
30-36

Unit
Times
30.42 C901240041 Number of drops due to the TA too

far
Definition
Number of drops due to the TA too far
Description
failure. After MS obtains SDCCH or TCH, call drop occurs. If the problem is caused by TA
being too far, the counter increments.
30-37

Usage
failure which is caused by TA being too far. It is one of the radio parameters that evaluate
the timeslot.
Measurement Point
Figure 30-45.
Process
Figure 30-46.
30-38

Unit
Times
30.43 C901240042 Number of drops due to the other

radio reasons
Definition
Number of drops due to the other radio reasons
Description
failure. After MS obtains SDCCH or TCH, 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.
30-39

Usage
link failure which is caused by other radio problems. It is one of the radio parameters that
evaluate the timeslot.
Measurement Point
Figure 30-47.
Process
l counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message
at Abis interface on TCH. The measurement point is A, as shown in Figure 30-48.
30-40

Unit
Times
30.44 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.
30-41

Usage
This counter is used to find out the sum of valid occupation time of a timeslot's voice
channel in the cell. It is one of the radio parameters that evaluate the timeslot.
Measurement Point
When BSC receives the measurement report from BTS, the counter is accumulated with a
time value. Different measurement report type corresponds to different value, for common
measurement report, the time value is 480 ms. The measurement point is A, as shown in
Figure 30-49.
Figure 30-49 BSC Receives Measurement Report from BTS
Unit
ms
30.45 C901240044 Number of activated voice channel

Definition
Number of activated voice channel
Description
This counter counts the number of a timeslot's voice channel being activated in the cell.
Usage
This counter is used to find out the frequency of a timeslot's voice channel being activated
in the cell. It is one of the radio parameters that evaluate the timeslot.
Measurement Point
When BSC receives the CHANNEL ACTIVATE ACK message, the counter increments.
30-42

Figure 30-50 Measurement Point when Channel Is Activated
Unit
Times
30-43

30-44

Chapter 31
SDCCH Measurement
Table of Contents
Overview ..................................................................................................................31-1
C901250005 Number of SDCCH seizure success for Handover...............................31-3
C901250007 Number of SDCCH allocation attempts for Assignment .......................31-5
C901250010 Number of SDCCH allocation attempts for handover ...........................31-6
C901250011 Number of SDCCH allocation success for handover ............................31-8
C901250012 Number of SDCCH allocation failure for handover...............................31-9
C901250016 Number of SDCCH handover failure.................................................. 31-11
C901250017 Number of SDCCH handover success...............................................31-12
C901250018 Number of SDCCH handover failure with Reconnection ....................31-14
C901250019 Number of SDCCH handover failure without Reconnection ...............31-14
31.1 Overview
SDCCH counters describe allocation, occupation, assignment, use of resources related
to SDCCH, which as SDCCH configuration and parameters adjustment basis. Allocation
of SDCCH is mainly in the process of immediate assignment and handover. Handover
includes internal and external handover. The statistic unit in this measurement is cell.
The Measurement point Of SDCCH counters in the process of immediate assignment is
31-1

Figure 31-1 The Process Of Immediate Assignment
The Measurement point Of SDCCH counters in the process of internal handover (like
intra-cell handover) is shown in Figure 31-2.
Figure 31-2 The Process Of Internal Handover (like intra-cell handover)
The Measurement point Of SDCCH counters in the process of external handover is shown
in Figure 31-3.
31-2

Chapter 31 SDCCH Measurement
Figure 31-3 The Process Of External Handover
31.2 C901250005 Number of SDCCH seizure success

for Handover
Definition
Number of SDCCH seizure success for Handover
Description
SDCCH allocation attempt is triggered by the channel request message RADIO_APPLY
from other channel instances. BSC attempts to allocate SDCCH after receiving the
message. If SDCCH allocation and seizure succeed, the counter increments. If
application response shows no SDCCH available but queuing or forced release is
possible, enter the state of waiting for resource. If SDCCH is available after waiting, then
the counter increments. If application response shows transceiver is faulty, the three
counters do not change.
Usage
This counter records the number of SDCCH seizure success for handover.
Measurement Point
When BSC requesting for SDCCH (due to handover) is completed and SDCCH seizure
succeeds, or BSC gets valid response of waiting resource. The measurement point is B1
as shown in Figure 31-4, and C1 as shown in Figure 31-5.
31-3

Unit
Times
Related Features
l ZGB-03-02-003 Dynamic Configuration of SDCCH
l ZGO-02-02-004 SDCCH/SDCCH Handover
31-4

31.3 C901250007 Number of 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
channel successfully, BSC sends the CHL_ACT message to BTS to activate this SDCCH
channel. If the activation succeeds (that is, when BSC receives the CHL_ACT_ACK
message from BTS), this counter and C900060008 increment simultaneously. Otherwise,
if the channel could not be activated due to receiving channel activation failure message,
incorrect channel activation response message, T9103 timeout, channel instance being
released or channel being released forcibly, this counter and C900060009 increment
simultaneously.
Measurement Point
BSC activates SDCCH due to assignment (C900060008+C900060009). The
measurement point is A2 as shown in Figure 31-6.
Figure 31-6 The Process Of Immediate Assignment
31-5

Unit
Times
Related Features
31.4 C901250010 Number of SDCCH allocation

Definition
Number of SDCCH allocation attempts for handover
Description
channel successfully, BSC sends the CHL_ACT message to BTS to activate this SDCCH
channel. If the activation succeeds (that is, when BSC receives the CHL_ACT_ACK
message from BTS), this counter and C901250011 increment simultaneously. Otherwise,
if the channel could not be activated due to receiving channel activation failure message,
released or channel being released forcibly, this counter and C901250012 increment
simultaneously.
Usage
This counter records the number of SDCCH allocations attempts for handover, including
successful allocations (C901250011) and unsuccessful allocations (C901250012).
Measurement Point
BSC activates SDCCH due to handover (C901250011+C901250012). The measurement
point is B2 as shown in Figure 31-7and C2 as shown in Figure 31-8.
31-6

Unit
Times
Related Features
31-7

31.5 C901250011 Number of SDCCH allocation success

for handover
Definition
Number of SDCCH allocation success for handover
Description
After BSC responds the channel request message to allocate and occupy SDCCH channel
successfully, BSC sends the CHL_ACT message to BTS to activate this SDCCH channel.
If the activation succeeds (that is, when BSC receives the CHL_ACT_ACK message from
BTS), it means SDCCH allocation succeeds completely and this counter increments.
Usage
This counter records the number of SDCCH allocations success for handover.
Measurement Point
When BSC receives the CHL_ACT_ACK message from BTS due to handover. The
measurement point is B2 as shown in Figure 31-9, and C2 as shown in Figure 31-10.
31-8

Unit
Times
Related Features
31.6 C901250012 Number of SDCCH allocation failure

for handover
Definition
Number of SDCCH allocation failure for handover
Description
After BSC responds the channel request message to allocate and occupy SDCCH channel
successfully, BSC sends the CHL_ACT message to BTS to activate this SDCCH channel.
If the channel could not be activated due to receiving channel activation failure message,
released or channel being released forcibly, this counter increments.
Usage
This counter records the number of SDCCH allocations failure for handover.
31-9

Measurement Point
BSC activates SDCCH for handover, but encounters the following situation: receives
channel activation failed message, channel activation response message is incorrect,
T9103 is time-out, channel instance is released, or channel is released forcibly. The
measurement point is B2 as shown in Figure 31-11 and C2 as shown in Figure 31-12.
Unit
Times
Related Features
31-10

31.7 C901250016 Number of 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.
Otherwise, handover fails and same time BSC has not received any failure message, this
counter and C901250019 increment simultaneously.
Usage
This counter records the attempts number of MS accesses SDCCH newly allocated
in the process of handover, including successful handover times (C901250017), failed
handover times (C901250018) with HO_FAILURE message and failed handover times
(C901250019) without HO_FAILURE message.
Measurement Point
When BSC receives ASS_COM message (intra-cell handover), HO_COM message
(inter-cell handover), HO_FAILURE message or HO_FAILURE abnormally, time-out
message, channel instance is released, or channel is released forcibly. The measurement
point is B3 as shown in Figure 31-13and C3 as shown in Figure 31-14.
31-11

Unit
Times
Related Features
31.8 C901250017 Number of 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 SDCCH newly allocated in
the process of handover.
31-12

Measurement Point
BSC receives ASS_COM message (intra-cell handover) or HO_COM message (inter-cell
handover). The measurement point is B3 as shown in Figure 31-15and C3 as shown in
Figure 31-16.
Unit
Times
Related Features
31-13


with Reconnection
Definition
Number of SDCCH handover failure with Reconnection
Description
In the process of handover, when BSC receives ASSIGN_FAIL message or HO_FAIL
message, this counter increments.
Usage
This counter records the number of MS accesses unsuccessfully SDCCH newly allocated
in the process of handover and BSC receives handover failure message.
Measurement Point
BSC receives HO_FAILURE message.
Unit
Times
Related Features

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

Measurement Point
When BSC has not received any HO_FAILURE message, time-out message, channel
instance is released, or channel is released forcibly.
Unit
Times
Related Features
31-15

31-16

Chapter 32
TCH/F Measurement
Table of Contents
Overview ..................................................................................................................32-4
C901260002 Number of signaling TCH/F seizure success for assignment ...............32-7
C901260005 Number of signaling TCH/F seizure success for handover...................32-8
C901260007 Number of signaling TCH/F allocation attempts for assignment ......... 32-11
C901260010 Number of signaling TCH/F allocation attempts for handover ............32-12
C901260011 Number of signaling TCH/F allocation success for handover .............32-15
C901260013 Number of signaling TCH/F assignment attempts for assignment ......32-17
C901260016 Number of signaling TCH/F handover attempt ...................................32-18
C901260017 Number of signaling TCH/F handover success ..................................32-21
C901260018 Number of signaling TCH/F handover failure with reconnection.........32-23
C901260019 Number of signaling TCH/F handover failure without reconnection ....32-25
C901260021 Number of voice TCH/F seizure success for assignment ...................32-26
C901260024 Number of voice TCH/F seizure success for handover ......................32-27
C901260026 Number of TCH/F allocation attempts for assignment (speech version
1) ...........................................................................................................................32-30
C901260032 Number of TCH/F allocation attempts by BSC for handover (speech
version 1) ...............................................................................................................32-31
C901260033 Number of TCH/F allocation success by BSC for handover (speech
version 1) ...............................................................................................................32-34
C901260038 Number of TCH/F allocation attempts for assignment (speech version
2) ...........................................................................................................................32-36
version 2) ...............................................................................................................32-38
version 2) ...............................................................................................................32-40
C901260050 Number of TCH/F allocation attempts by BSC for assignment (speech
version 3) ...............................................................................................................32-43
version 3) ...............................................................................................................32-44
version 3) ...............................................................................................................32-47
C901260062 Number of voice TCH/F assignment attempts by BSC.......................32-49
C901260065 Number of voice TCH/F handover attempts.......................................32-51
C901260067 Number of Voice TCH/F handover failure ..........................................32-54
C901260068 Number of Voice TCH/F handover failure messages do not received
by BSC...................................................................................................................32-55
C901260070 Number of data TCH/F seizure success for assignment ....................32-56
32-1

C901260073 Number of data TCH/F seizure success for handover........................32-58

C901260075 Number of data TCH/F allocation attempts for assignment ................32-60
C901260081 Number of data TCH/F allocation attempts by BSC for handover ......32-62
C901260082 Number of data TCH/F allocation success for handover ....................32-64
C901260087 Number of data TCH/F assignment attempts.....................................32-67
C901260090 Number of data TCH/F handover attempts ........................................32-68
C901260092 Number of data TCH/F handover failure ............................................32-71
C901260093 Number of data TCH/F handover failure messages do not received
by BSC...................................................................................................................32-72
C901260094 Number of data TCH/F allocation failure for assignment due to TIPB
connection failure (Speech version 1).....................................................................32-73
C901260095 Number of data TCH/F allocation failure for assignment due to
Resource request to iTC failure (Speech version 1)................................................32-74
C901260096 Number of data TCH/F allocation failure for handover due to TIPB
C901260097 Number of data TCH/F allocation failure for handover due to
C901260106 Number of TCH/F allocation failure due to request AIPB resource
failure for assignment (speech version 1) ...............................................................32-88
C901260107 Number of TCH/F allocation failure due to request UDP port failure
for assignment (speech version 1)..........................................................................32-89
C901260108 Number of TCH/F allocation failure due to AIPB connection failure for
assignment (speech version 1)...............................................................................32-90
failure for handover (speech version 1)...................................................................32-91
for handover (speech version 1) .............................................................................32-92
handover (speech version 1) ..................................................................................32-93
32-2

Chapter 32 TCH/F Measurement

for assignment (speech version 2)..........................................................................32-95
assignment (speech version 2)...............................................................................32-96
failure for handover (speech version 2)...................................................................32-97
for handover (speech version 2) .............................................................................32-98
handover (speech version 2) ..................................................................................32-99
failure for assignment (speech version 3) .............................................................32-100
for assignment (speech version 3)........................................................................32-101
assignment (speech version 3).............................................................................32-102
failure for handover (speech version 3).................................................................32-103
for handover (speech version 3) ...........................................................................32-104
handover (speech version 3) ................................................................................32-105
failure for assignment (data) .................................................................................32-106
for assignment (data) ...........................................................................................32-107
assignment (data) ................................................................................................32-108
failure for handover (data) ....................................................................................32-109
for handover (data)............................................................................................... 32-110
handover (data).................................................................................................... 32-111
C901260130 Number of assign TCH/F release by forced handover to forced
handover source .................................................................................................. 32-112
C901260131 Number of assign TCH/F release by forced handover to queuing
user...................................................................................................................... 32-113
C901260132 Number of restore TCH/F release by forced handover to DBS......... 32-113
C901260133 Number of assign TCHF release by forced release to forced release
source .................................................................................................................. 32-114
C901260134 Number of assign TCH/F release by forced release to queuing
user...................................................................................................................... 32-114
32-3

C901260135 Number of restore TCH/F release by forced release to DBS............ 32-115

C901260136 Number of signaling TCH/F seizure failure for assignment
(cause:Abis) ......................................................................................................... 32-116
C901260137 Number of signaling TCH/F seizure failure for handover
(cause:Abis) ......................................................................................................... 32-116
C901260138 Number of voice TCH/F seizure failure for assignment (cause:Abis) . 32-117
C901260139 Number of voice TCH/F seizure failure for handover (cause:Abis ) .. 32-117
C901260140 Number of data TCH/F seizure failure for assignment (cause:Abis) . 32-118
C901260141 Number of data TCH/F seizure failure for handover (cause:Abis) .... 32-118
C901260142 Number of signaling TCH/F seizure failure for assignment
(cause:radio resource) ......................................................................................... 32-119
C901260143 Number of signaling TCH/F seizure failure for handover (cause:radio
resource).............................................................................................................. 32-119
C901260144 Number of voice TCH/F seizure failure for assignment (cause:radio
resource)..............................................................................................................32-120
C901260145 Number of voice TCH/F seizure failure for handover (cause:radio
resource)..............................................................................................................32-120
C901260146 Number of data TCH/F seizure failure for assignment (cause:radio
resource)..............................................................................................................32-121
C901260147 Number of data TCH/F seizure failure for handover (cause:radio
resource)..............................................................................................................32-121
C901260148 Number of FR_V1 assignment attempts ..........................................32-122
C901260149 Number of FR_V1 assignment success...........................................32-122
C901260154 Number of FR_V1 handover............................................................32-125
C901260155 Number of FR_V1 handover success ..............................................32-125
32.1 Overview
In GSM BSC signaling system, allocation and usage of TCH/F channel mainly exist in
assignment and handover flow, where assignment flow includes immediate assignment
and common assignment; handover flow includes internal and external handover.
For the measurement positions of TCH/F counter in immediate assignment flow, see Figure
32-1.
32-4

Figure 32-1 Immediate assignment flow
During internal and external TC, for the measurement positions of TCH/F counter in
common assignment flow, see Figure 32-2and Figure 32-3.
Figure 32-2 Common assignment flow (internal TC)
Figure 32-3 Common assignment flow (external TC)
32-5

During internal and external TC, for the measurement positions of TCH/F counter in internal
handover flow (like intra-cell handover), see Figure 32-4and Figure 32-5.
Figure 32-4 Internal handover (like intra-cell handover) flow (internal TC)
Figure 32-5 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 32-6and Figure 32-7
32-6

Figure 32-6 External handover flow (internal TC)
Figure 32-7 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.
32-7

After BSC receives channel request message, it will try to allocate channel for this request.
If allocation and seizure succeed, this counter accumulates.
Measurement Point
BSC successfully applies for channel (due to assignment, used for signaling channel) and
does successful assignment. The measurement point is A1, as shown in Figure 32-8
Unit
Times
Related Features

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.
If allocation and seizure succeed, this counter accumulates. If no channel is returned after
application but queuing or force release can be conducted, it will enter into the state to wait
for resource, this counter accumulates when corresponding resource occurs.
32-8

Measurement Point
BSC successfully applies for channel (due to handover, used for signaling channel) and
does successful seizure, or BSC receives internal waiting resource effective message.
The measurement points are C1 and D1, as shown in Figure 32-9, Figure 32-10, Figure
32-11, and Figure 32-12.
32-9

Unit
Times
Related Features
l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
l ZGO-03-02-011 Channel Repacking
32-10


Definition
Number of signaling TCH/F allocation attempts for assignment
Description
This counter counts the number of signaling TCH/F allocation attempts when assigning
signaling channel, including the number of allocation success (C900060014) and failure
(C900060014).
After BSC responds channel request message allocation and successfully seizes TCH/F
channel, BSC sends channel activation message CHL_ACT to activate this TCH/F. if
activation success, CHL_ACT_ACK message sent by BTS will be received, indicating
TCH/F allocation success, this counter and C900060014 accumulate simultaneously;
reversely, if channel activation failure due to receive channel activation failure
message, incorrect channel activation response message, timer T9103 timeout, channel
instance released, channel force-released, this counter and C900060015 accumulate
simultaneously.
Measurement Point
After BSC activates TCH/F (due to assignment, used for signaling channel), this counter
accumulates when CHL_ACT_ACK message sent by BTS is received correctly, channel
activation failure message is received, channel activation response message is not
correct, timer T9103 times out, channel instance is released, or channel is forcibly
released. (C900060014+C900060015) The measurement point is A2, as shown in Figure
32-13.
32-11

Unit
Times
Related Features

Definition
Number of signaling TCH/F allocation attempts for handover
Description
This counter counts the number of signaling TCH/F allocation attempts during handover
of signaling channel, including the number of allocation success (C901260011) and failure
(C900060016).
After BSC responds channel request message allocation and successfully seizes
TCH/F channel, BSC sends channel activation message CHL_ACT to BTS to activate
this TCH/F. if activation success, CHL_ACT_ACK message sent by BTS will be
received, indicating TCH/F allocation success, this counter and C901260011 accumulate
simultaneously; reversely, if channel activation failure due to receive channel activation
failure message, incorrect channel activation response message, timer T9103 timeout,
channel instance released, channel force-released, this counter and C900060016
Measurement Point
After BSC activates TCH/F (due to handover, used for signaling channel), this counter
accumulates when CHL_ACT_ACK message sent by BTS is received correctly, channel
activation failure message is received, channel activation response message is not
correct, timer T9103 times out, channel instance is released, or channel is forcibly
released. (C901260011+C900060016) The measurement points are C3 and D3, as
shown in Figure 32-14, Figure 32-15,Figure 32-16 and Figure 32-17.
32-12

32-13

Unit
Times
Related Features
32-14


Definition
Number of signaling TCH/F allocation success for handover
Description
This counter counts the number of signaling TCH/F allocation success during handover of
signaling channel.
After BSC responds channel request message allocation and successfully seizes channel,
BSC sends channel activation message CHL_ACT to BTS to activate this TCH/F. if
TCH/F allocation success, this counter accumulates.
Measurement Point
This counter accumulates when CHL_ACT_ACK correctly receives CHL_ACT_ACK
message sent by BTS due to handover and used for signaling channel. The measurement
points are C3 and D3, as shown in Figure 32-18, Figure 32-19, Figure 32-20, and Figure
32-21.
32-15

32-16

Unit
Times
Related Features

assignment attempts for assignment
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.
BSC sends channel activation message CHL_ACT to BTS to activate this TCH/F. For
immediate assignment, after activation success, BTS receives MS access and sends
EST_IND message to BSC, this counter accumulates while BSC correctly receives this
message; if MS access cant be received within specified duration, this assignment is
failed.
Measurement Point
For immediate assignment, this counter accumulates when BSC correctly receives
EST_IND message or T3101 times out (that is, MS access notice cant be received within
specified duration). The measurement point is A3, as shown in Figure 32-22.
32-17

Unit
Times
Related Features
32.8 C901260016 Number of 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 channel; this counter and C901260018
accumulate when handover failure message is received; this counter and C901260019
accumulate when it receives the message of exception, released instance, force-released
instance, or timer timeout.
For intra-cell handover, handover success symbolic message is ASS_COM; for inter-cell
handover and external handover, handover success symbolic message is HO_COM.
For intra-cell and inter-cell handover, this counter accumulates on the basis of source
instance; for external handover, this counter accumulates on target instance because
source instance doesnt at this BSC side.
32-18

Measurement Point
This counter accumulates when BSC detects handover success message,
ASS_COM/HO_COM, sent from reallocated TCH/F channel, or receives failure
message, ASS_FAIL/HO_FAIL,, or receives message of exception, released instance,
force-released instance, or timer timeout. The measurement points are C4 and D4, as
shown in Figure 32-23, Figure 32-24, Figure 32-25, and Figure 32-26.
32-19

Unit
Times
Related Features
32-20

32.9 C901260017 Number of signaling TCH/F handover

success
Definition
Number of signaling TCH/F handover success
Description
his counter counts the number of signaling TCH/F handover success during handover of
signaling channel.
This counter accumulates when handover success message sent from MS is detected on
reallocated TCH/F channel.
For intra-cell handover, handover success symbolic message is ASS_COM; for inter-cell
handover and external handover, handover success symbolic message is HO_COM.
Measurement Point
BSC receives ASS_COM or HO_COM message. The measurement points are C4 and
D4, as shown in Figure 32-27, Figure 32-28, Figure 32-29, and Figure 32-30.
32-21

32-22

Unit
Times
Related Features

handover failure with reconnection
Definition
Number of signaling TCH/F handover failure with reconnection
Description
This counter counts the number of signaling TCH/F handover failure during handover of
signaling channel.
This counter accumulates when MS conducts handover on TCH/F channel, returns to

previous channel after failed to access to new channel, receives assignment failure or
handover failure from previous channel.
Measurement Point
BSC receives ASS_FAIL or HO_FAIL message. The measurement points are C4 and D4,
as shown in Figure 32-31, Figure 32-32.
32-23

Figure 32-31 Internal handover (internal TC intra-cell handover) failure flow 1
Figure 32-32 External handover failure flow (internal TC)
Unit
Times
Related Features
32-24


handover failure without reconnection
Definition
Number of signaling TCH/F handover failure without reconnection
Description
This counter counts the number of signaling TCH/F handover failure without reconnection
during handover of signaling channel.
This counter accumulates when MS handover fails or it cant return to previous channel
after BSC sends assignment command or handover command to MS.
Measurement Point
This counter accumulates when BSC receives messages of exception, released instance,
force-released instance, or timer timeout. The measurement point is C4, as shown in
Figure 32-33, Figure 32-34.
32-25

Unit
Times
Related Features

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.
Measurement Point
BSC successfully applies for channel (due to assignment, used for voice channel) and
The measurement point is B1, as shown in Figure 32-35, Figure 32-36.
32-26

Unit
Times
Related Features
l ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

Definition
Number of voice TCH/F seizure success for handover
Description
This counter counts the number of voice TCH/F seizure success during handover of
signaling channel.
Measurement Point
BSC successfully applies for channel (due to handover, used for voice channel) and does
successful seizure, or BSC receives internal waiting resource effective message. The
measurement points are C1 and D1, as shown in Figure 32-37, Figure 32-38, Figure 32-39,
and Figure 32-40.
32-27

32-28

Unit
Times
Related Features
32-29


attempts for assignment (speech version 1)
Definition
Number of TCH/F allocation attempts for assignment (speech version 1)
Description
This counter counts the number of TCH/F allocation attempts when assigning voice
channel (for speech version 1), including the number of allocation success (C900060023)
and failure (C900060024+C900060138+ C900060139+ C900060140).
TCH/F channel, BSC firstly finishes connection, then sends channel activation message
CHL_ACT to BTS to activate this TCH/F. if activation succeeds, BSC will receive
CHL_ACT_ACK message sent by BTS, indicating TCH/F allocation success, this counter
and C900060023 accumulate simultaneously; reversely, if failed, this counter and the
counter that corresponds to failure will accumulate simultaneously.
Measurement Point
This counter accumulates when allocation succeeds or fails (due to assignment, used for
voice channel, using speech version 1). The measurement points are B2 and B3, as shown
in Figure 32-41, Figure 32-42.
32-30

Unit
Times
Related Features
l ZGB-01-01-001 Full Rate (FR) Speech Codec

attempts by BSC for handover (speech version 1)
Definition
Number of TCH/F allocation attempts by BSC for handover (speech version 1)
Description
This counter counts the number of TCH/F allocation attempts during handover of voice
and failure (C900060156+C900060157+C900060158+C900060159).
32-31

Measurement Point
This counter accumulates when allocation succeeds or fails (due to handover, used for
voice channel, using speech version 1). The measurement points are C3 and D3, as
32-32

Unit
Times
Related Features
32-33


by BSC for handover (speech version 1)
Definition
Number of TCH/F allocation success by BSC for handover(speech version 1)
Description
This counter counts the number of TCH/F allocation success during handover of voice
channel (for speech version 1).
Measurement Point
This counter accumulates when BSC correctly receives CHL_ACT_ACK message sent by
BTS due to handover and used for voice channel (for speech version 1). The measurement
32-50.
32-34

32-35

Unit
Times
Related Features

Definition
Description
and failure (C900060141+C900060142+C900060143+C900060144).
32-36

Measurement Point
Unit
Times
Related Features
32-37


Definition
Description
and failure (C900060160+C900060161+C900060162+C900060163).
Measurement Point
32-38

32-39

Unit
Times
Related Features

Definition
Number of TCH/F allocation success by BSC for handover (speech version 2)
Description
Measurement Point
32-60.
32-40

32-41

Unit
Times
Related Features
32-42


attempts by BSC for assignment (speech version 3)
Definition
Description
and failure (C900060027+C900060145+C900060146+C900060147).
Measurement Point
32-43

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

Definition
Description
and failure (C900060164+C900060165+C900060166+C900060167).
32-44

Measurement Point
32-45

Unit
Times
Related Features
32-46


Definition
Number of TCH/F allocation success by BSC for handover (speech version 3)
Description
Measurement Point
32-70.
32-47

32-48

Unit
Times
Related Features

attempts by BSC
Definition
Number of voice TCH/F assignment attempts by BSC
Description
This counter counts the number of voice TCH/F assignment attempts when assigning
TCH/F channel as voice channel, including the number of assignment success
(C900060028) and failure (C900060029).
the assignment form port A, this counter and C900060028 accumulate simultaneously
after receiving assignment success message. This counter and C900060029 accumulate
simultaneously if MS access notice cant be received within specified duration, that is, this
assignment failed at this time.
32-49

Measurement Point
For the assignment from port A, BSC receives the messages of assignment success,
assignment failure, timer timeout, exception, released instance, or force-released
instance. The measurement point is B5, as shown in Figure 32-71, Figure 32-72.
Unit
Times
Related Features
32-50

32.24 C901260065 Number of 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 duration, it indicates

handover success, this counter and C900060168 accumulate simultaneously; if BSC
receives HO_FAILURE, it is handover failure with response, this counter and C901260067
accumulate; if handover is failed and BSC cant receive HO_FAILURE, it is handover
failure without response, this counter and C901260068 accumulate simultaneously.
Measurement Point
This counter accumulates when BSC receives ASS_COM/HO_COM message,
ASS_FAIL/HO_FAIL message, or messages of exception, released instance,
32-51

32-52

Unit
Times
Related Features
32-53


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.
This counter accumulates when MS conducts handover on TCH/F channel, fails to access
to new channel and returns to previous channel, receives assignment failure or handover
failure from previous channel.
Measurement Point
32-54

Unit
Times
Related Features

failure messages do not received by BSC
Definition
Number of Voice TCH/F handover failure messages do not received by BSC
Description
This counter counts the number of voice TCH/F handover failure without response during
handover of voice channel.
This counter accumulates when handover fails or it cant return to source channel after
BSC sends assignment / handover command to MS.
Measurement Point
This counter accumulates when BSC receives messages of exception, timer timeout,
released instance, or force-released instance. The measurement points are C4 and D4,
32-55

Unit
Times
Related Features

Definition
Number of data TCH/F seizure success for assignment
Description
This counter counts the number of data TCH/F seizure success during assignment of
signaling channel.
32-56

Measurement Point
BSC successfully applies for channel (due to assignment, used for data channel) and
The measurement point is B1, as shown in Figure 32-81, Figure 32-82.
Unit
Times
Related Features
32-57


Definition
Number of data TCH/F seizure success for handover
Description
This counter counts the number of data TCH/F seizure success during handover of
signaling channel.
Measurement Point
BSC successfully applies for channel (due to handover, used for 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 32-83, Figure 32-84, Figure 32-85,
and Figure 32-86.
32-58

32-59

Unit
Times
Related Features

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
32-60

Measurement Point
data channel). The measurement points are B2 and B3, as shown in Figure 32-87, Figure
32-88.
Unit
Times
Related Features
32-61


attempts 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).
Measurement Point
data channel). The measurement points are C3 and D3, as shown in Figure 32-89, Figure
32-90, Figure 32-91, and Figure 32-92.
32-62

32-63

Unit
Times
Related Features

Definition
Number of data TCH/F allocation success for handover
Description
This counter counts the number of data TCH/F allocation success during handover of
signaling channel.
Measurement Point
This counter accumulates when CHL_ACT_ACK correctly receives CHL_ACT_ACK
message sent by BTS due to handover and used for data channel. The measurement
32-96.
32-64

32-65

Unit
Times
Related Features
32-66


attempts
Definition
Number of data TCH/F assignment attempts
Description
This counter counts the number of voice TCH/F assignment attempts when assigning
TCH/F channel as data channel, including the number of assignment success
(C900060036) and failure (C900060037).
the assignment form port A, this counter and C900060036 accumulate simultaneously
after receiving assignment success message. This counter and C900060037 accumulate
simultaneously if MS access notice cant be received within specified duration, that is, this
assignment failed at this time.
Measurement Point
For the assignment from port A, BSC receives the messages of assignment success,
assignment failure, timer timeout, exception, released instance, or force-released
instance. The measurement point is B5, as shown in Figure 32-97, Figure 32-98.
32-67

Unit
Times
Related Features

attempts
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 response-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 duration, it indicates
handover success, this counter and C901260091 accumulate simultaneously; if BSC
receives HO_FAILURE, it is handover failure with response, this counter and C901260092
accumulate; if handover is failed and BSC cant receive HO_FAILURE, it is handover
failure without response, this counter and C901260093 accumulate simultaneously.
32-68

Measurement Point
This counter accumulates when BSC receives ASS_COM/HO_COM message,
ASS_FAIL/HO_FAIL message, or messages of exception, released instance,
32-69

Unit
Times
Related Features
32-70


failure
Definition
Number of data TCH/F handover failure
Description
his counter counts the number of data TCH/F handover failure during handover of data
channel.
This counter accumulates when MS conducts handover on TCH/F channel, fails to access
to new channel and returns to previous channel, receives assignment failure or handover
failure from previous channel.
Measurement Point
32-71

Unit
Times
Related Features

Definition
Number of data TCH/F handover failure messages do not received by BSC
Description
This counter counts the number of data TCH/F handover failure without response during
handover of data channel.
This counter accumulates when handover fails or it cant return to source channel after
BSC sends assignment / handover command to MS.
Measurement Point
This counter accumulates when BSC receives messages of exception, released instance,
force-released instance, or timer timeout. The measurement point is C4, as shown in
32-72

Unit
Times
Related Features

failure 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)
32-73

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.
channel, BSC sends TIU connection requests to TIPB. This counter accumulates when
it receives the messages of TIU connection failure, incorrect TIU connection response
message, or timer timeout.
Measurement Point
BSC uses TCH/F due to assignment; this counter accumulates when it receives connection
failure message, incorrect connection response message, or timer timeout during TIU
connection. The measurement point is B2, as shown in Figure 32-107.
Figure 32-107 General Assignment Failure Flow 1 (external TC)
Unit
Times
Related Features

failure for assignment due to Resource request to
iTC failure (Speech version 1)
Definition
Number of data TCH/F allocation failure for assignment due to Resource request to iTC
32-74

Description
resource request to iTC failure (speech version 1) when assigning voice channel.
channel, BSC requests resource from iTC. If application of iTC resource fails due to receive
the messages of unavailable iTC resource, incorrect response message, or timer timeout,
this leads to TCH/F assignment failure, and this counter accumulates.
Measurement Point
BSC uses TCH/F due to assignment; this counter accumulates when it receives the
messages of unavailable iTC, incorrect response message, or timer timeout during iTC
resource application. The measurement point is B1, as shown in Figure 32-108.
Unit
Times
Related Features

failure for handover due to TIPB connection failure
(Speech version 1)
Definition
Number of data TCH/F allocation failure for handover due to TIPB connection failure
(Speech version 1)
32-75

Description
This counter counts the number of data TCH/F allocation failure for handover due to TIPB
connection failure (speech version 1) during handover.
Measurement Point
BSC uses TCH/F due to assignment; this counter accumulates when it receives
messages of connection failure, incorrect connection response, or timer timeout during
TIU connection. The measurement points are C2 and D2, as shown in Figure 32-109and
Figure 32-110.
Figure 32-109 Internal handover (external TC intra-cell handover, and channel types are
changed) failure flow 1
Unit
Times
32-76

Related Features

failure for handover due to Resource request to
Definition
Number of data TCH/F allocation failure for handover due to Resource request to iTC
Description
This counter counts the number of data TCH/F allocation failure for handover due to
resource request to iTC failure (speech version 1) during handover of voice channel.
channel, BSC requests TC resource after determining channel types are changed. If
application of iTC resource fails due to receive the messages of unavailable iTC resource,
incorrect response, or timer timeout, this leads to TCH/F assignment failure, and this
Measurement Point
BSC uses TCH/F due to handover; this counter accumulates when it receives the
messages of unavailable iTC, incorrect response, or timer timeout during iTC resource
application. The measurement points are C1 and D1, as shown in Figure 32-111and
Figure 32-112.
32-77

Figure 32-112 External handover failure flow 2 (external TC)
Unit
Times
Related Features

Definition
(Speech version 2)
Description
Measurement Point
32-78

Unit
Times
Related Features

Definition
Number of data TCH/F allocation failure for assignment due to Resource request to iTC
Description
Measurement Point
messages of unavailable iTC, incorrect response message, or timer timeout during iTC
resource application. The measurement point is B1, as shown in Figure 32-114.
32-79

Unit
Times
Related Features

(Speech version 2)
Definition
(Speech version 2)
Description
Measurement Point
Figure 32-116.
32-80

Unit
Times
Related Features

Definition
32-81

Description
Measurement Point
messages of unavailable iTC resource, incorrect response message, or timer timeout
during iTC resource application. The measurement points are C1 and D1, as shown in
Unit
Times
Related Features
32-82


Definition
(Speech version 3)
Description
Measurement Point
Unit
Times
Related Features
32-83


Definition
Number of data TCH/F allocation failure for assignment due to resource request to iTC
Description
Measurement Point
during iTC resource application. The measurement point is B1, as shown in Figure
32-120.
Unit
Times
Related Features
32-84


(Speech version 3)
Definition
(Speech version 3)
Description
Measurement Point
Figure 32-122.
32-85

Unit
Times
Related Features

Definition
Description
32-86

Measurement Point
during iTC resource application. The measurement points are C1 and D1, as shown in
Unit
Times
Related Features
32-87


failure due to request AIPB resource failure for
assignment (speech version 1)
Definition
Number of TCH/F allocation failure due to request AIPB resource failure for assignment
(speech version 1)
Description
This counter counts the number of TCH/F allocation failure due to request AIPB resource
failure for assignment.
This counter increments while BSC receives assignment requests (speech version 1) to
apply for AIPB board resource from database, failed request (including database return
failure or no AIPB board resource) indicates TCH/F allocation failure.
Usage
This counter is used to find out the frequency of TCH/F allocation failure due to request
AIPB resource failure for assignment.
Measurement Point
This counter increments while BSC correctly receives database return failure or no AIPB
board resource, and the reason to apply for channel is assignment and purpose is voice
channel. The measurement point is A as shown in Figure 32-125.
Figure 32-125 Request Resource Failure
Unit
Times
Related Features
ZGO-05-04-003 A over IP
32-88


due to request UDP port failure for assignment
(speech version 1)
Definition
Number of TCH/F allocation failure due to request UDP port failure for assignment (speech
version 1)
Description
This counter counts the number of TCH/F channel allocation failure due to UDP port failure
during assigning voice channel.
This counter increments while BSC receives assignment requests (speech version 1),
access request is sent to access module, if access module returns access failure due
to UDP port request failure.
Usage
UDP port failure.
Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK
message returned by access module, and the reason is request UDP port failure for
assignment. The measurement point is A as shown in Figure 32-126.
Figure 32-126 Channel allocation failure
Unit
Times
Related Features
32-89


due to AIPB connection failure for assignment
(speech version 1)
Definition
Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech
version 1)
Description
Usage
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB
access failure.
Measurement Point
message returned by access module (the reason is AIPB access failure) or TwaitConn
timer timeout for assignment. The measurement point is A as shown in Figure 32-127.
Unit
Times
Related Features
32-90


due to request AIPB resource failure for handover
(speech version 1)
Definition
Number of TCH/F allocation failure due to request AIPB resource failure for handover
(speech version 1)
Description
When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 1), the
reason to request channel is handover, to request AIPB resource from database. This
counter increments if failed to request AIPB (including database returning failure or no
AIPB resource), indicating TCH/F allocation failure.
Usage
Measurement Point
board resource, and the reason to apply for channel is handover and purpose is voice
Unit
Times
Related Features
32-91

l ZGO-05-04-003 A over IP

due to request UDP port failure for handover
(speech version 1)
Definition
Number of TCH/F allocation failure due to request UDP port failure for handover (speech
version 1)
Description
during handover.
reason to request channel is handover, to request access request for access module.
This counter increments while access module returns failure and the reason is failed to
request UDP port.
Usage
UDP port failure.
Measurement Point
handover. The measurement point is A as shown in Figure 32-129.
Unit
Times
Related Features
32-92


due to AIPB connection failure for handover
(speech version 1)
Definition
Number of TCH/F allocation failure due to AIPB connection failure for handover (speech
version 1)
Description
This counter counts the number of TCH/F channel allocation failure due to AIPB access
failure during handover.
access AIPB.
Usage
access failure.
Measurement Point
timer timeout for handover. The measurement point is A as shown in Figure 32-130.
Unit
Times
Related Features
32-93


Definition
(speech version 2)
Description
Usage
Measurement Point
Unit
Times
32-94

Related Features

(speech version 2)
Definition
version 2)
Description
Usage
UDP port failure.
Measurement Point
Unit
Times
32-95

Related Features

(speech version 2)
Definition
version 2)
Description
Usage
access failure.
Measurement Point
Unit
Times
32-96

Related Features

(speech version 2)
Definition
(speech version 2)
Description
AIPB resource), indicating TCH/F allocation failure.
Usage
Measurement Point
Unit
Times
32-97

Related Features

(speech version 2)
Definition
version 2)
Description
during handover.
This counter increments while BSC receives EV_RANUMC_RADIO_APPLY message
(speech version 2) to request channel due to handover, access request is sent to access
module, if access module returns access failure due to UDP port request failure.
Usage
UDP port failure.
Measurement Point
Unit
Times
32-98

Related Features

(speech version 2)
Definition
version 2)
Description
access AIPB.
Usage
access failure.
Measurement Point
Unit
Times
32-99

Related Features

Definition
(speech version 3)
Description
Usage
Measurement Point
Unit
Times
32-100

Related Features

(speech version 3)
Definition
version 3)
Description
Usage
UDP port failure.
Measurement Point
Unit
Times
32-101

Related Features

(speech version 3)
Definition
version 3)
Description
Usage
access failure.
Measurement Point
Unit
Times
32-102

Related Features

(speech version 3)
Definition
(speech version 3)
Description
(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
resource), indicating TCH/F allocation failure.
Usage
Measurement Point
32-103

Unit
Times
Related Features

(speech version 3)
Definition
version 3)
Description
during handover.
request UDP port.
Usage
UDP port failure.
Measurement Point
32-104

Unit
Times
Related Features

(speech version 3)
Definition
version 3)
Description
access AIPB.
Usage
access failure.
Measurement Point
32-105

Unit
Times
Related Features

assignment (data)
Definition
(data)
Description
This counter increments while BSC receives assignment requests (data) to apply for AIPB
board resource from database, failed request (including database return failure or no AIPB
resource) indicates TCH/F allocation failure.
Usage
Measurement Point
32-106

Unit
Times
Related Features

(data)
Definition
Number of TCH/F allocation failure due to request UDP port failure for assignment (data)
Description
This counter increments while BSC receives assignment requests (data), access request
is sent to access module, if access module returns access failure due to UDP port request
failure.
Usage
UDP port failure.
Measurement Point
32-107

Unit
Times
Related Features

(data)
Definition
Number of TCH/F allocation failure due to AIPB connection failure for assignment (data)
Description
failure.
Usage
access failure.
Measurement Point
32-108

Unit
Times
Related Features

(data)
Definition
(data)
Description
When BSC receives EV_RANUMC_RADIO_APPLY message (data), the reason to
request channel is handover, to request AIPB resource from database. This counter
increments if failed to request AIPB (including database returning failure or no AIPB
resource), indicating TCH/F allocation failure.
Usage
Measurement Point
32-109

Unit
Times
Related Features

due to request UDP port failure for handover (data)
Definition
Number of TCH/F allocation failure due to request UDP port failure for handover (data)
Description
during handover.
request channel is handover, to request access request for access module. This counter
increments while access module returns failure and the reason is failed to request UDP
port.
Usage
UDP port failure.
Measurement Point
32-110

Unit
Times
Related Features

due to AIPB connection failure for handover (data)
Definition
Number of TCH/F allocation failure due to AIPB connection failure for handover (data)
Description
increments while access module returns failure and the reason is failed to access AIPB.
Usage
access failure.
Measurement Point
32-111

Unit
Times
Related Features
32.72 C901260130 Number of assign TCH/F release by

forced handover to forced handover source
Definition
Number of assign TCH/F release by forced handover to forced handover source
Description
When the BSC CS service instance is forcibly handover, this counter counts the number
of times that the released TCH/F resource is assigned to the forced handover source.
The BSC CS service instance is forcibly handover to release resource, if the released
TCH/F resource is assigned to the forced handover source, the counter accumulates.
Usage
This counter is used to find out the frequency of the TCH/F released by forced handover
being assigned to the forced handover source.
Measurement Point
TCH/F resource is assigned to the forced handover source, the counter accumulates.
Unit
Times
32-112


forced handover to queuing user
Definition
Number of assign TCH/F release by forced handover to queuing user
Description
of times that the released TCH/F resource is assigned to the queuing user.
TCH/F resource is assigned to the queuing user, the counter accumulates.
Usage
being assigned to the queuing user.
Measurement Point
Unit
Times
32.74 C901260132 Number of restore TCH/F release by

forced handover to DBS
Definition
Number of restore TCH/F release by forced handover to DBS
Description
of times that the released TCH/F resource is assigned to the queuing user.
Usage
being restored to DBS.
32-113

Measurement Point
TCH/F resource is just released instead of being assigned to other users, the counter
accumulates.
Unit
Times
32.75 C901260133 Number of assign TCHF release by

forced release to forced release source
Definition
Number of assign TCH/F release by forced release to forced release source
Description
When the BSC CS service instance is forcibly released, this counter counts the number of
times that the released TCH/F resource is assigned to the forced release source.
The BSC CS service instance is forcibly released to release resource, if the released
TCH/F resource is assigned to the forced release source, the counter accumulates.
Usage
This counter is used to find out the frequency of the TCH/F released by forced release
being assigned to the forced release source.
Measurement Point
TCH/F resource is assigned to the forced release source, the counter accumulates.
Unit
Times

forced release to queuing user
Definition
Number of assign TCH/F release by forced release to queuing user
32-114

Description
times that the released TCH/F resource is assigned to the queuing user.
Usage
Measurement Point
Unit
Times
32.77 C901260135 Number of restore TCH/F release

by forced release to DBS
Definition
Number of restore TCH/F release by forced release to DBS
Description
When the BSC CS service instance is forcibly released, this counter counts the number
of times that the released TCH/F resource is restored to the database instead of being
assigned to other users.
accumulates.
Usage
Measurement Point
accumulates.
32-115

Unit
Times

failure for assignment (cause:Abis)
Description
This counter counts the number of failed signaling TCH/F seizure attempts during the
process of signaling channel assignment. When BSC receives the channel request, it
attempts to allocate channel for the request. If the channel occupation fails due to no
available Abis resource, the counter accumulates. If the request is responded with the
message that the transceiver is faulty, the counter does not count.
Measurement Point
The counter counts when the request for channel is sent to BSC (due to assignment, used
for signaling channel) and the channel is occupied successfully.
Unit
Times

failure for handover (cause:Abis)
Description
process of signaling channel handover. When BSC receives the channel request, it
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
32-116

request is responded with the message that the transceiver is faulty, the counter does not
count. For channel occupation failures in other cases, the counter accumulates.
Measurement Point
The counter counts when the request for channel is sent to BSC (due to handover, used
for signaling channel) but the channel occupation fails or waiting for resource inside BSC
fails.
Unit
Times

Description
This counter counts the number of failed voice TCH/F seizure attempts during the process
of voice 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 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 counter does not count. For channel
occupation failures in other cases, the counter accumulates.
Measurement Point
for voice channel) but the channel occupation fails or waiting for resource inside BSC fails.
Unit
Times

failure for handover (cause:Abis )
Description
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
32-117

state. If the queuing fails, the counter accumulates. If the request is responded with the
message that the transceiver is faulty, the counter does not count. For channel occupation
failures in other cases, the counter accumulates.
Measurement Point
Unit
Times

Description
This counter counts the number of failed data TCH/F seizure attempts during the process of
data channel assignment. When BSC receives the channel request, it attempts to allocate
Measurement Point
for data channel) but the channel occupation fails or waiting for resource inside BSC fails.
Unit
Times

Description
This counter counts the number of failed data TCH/F seizure attempts during the process
of data channel handover. When BSC receives the channel request, it attempts to allocate
32-118

Measurement Point
Unit
Times

failure for assignment (cause:radio resource)
Description
available radio resource, the counter accumulates. If the request is responded with the
Measurement Point
Unit
Times

failure for handover (cause:radio resource)
Description
32-119

Measurement Point
fails.
Unit
Times

Description
allocate channel for the request. If the channel occupation fails due to no available radio
Measurement Point
Unit
Times

Description
channel for the request. If the channel occupation fails due to no available radio resource,
32-120

Measurement Point
Unit
Times

Description
This counter counts the number of failed data TCH/F seizure attempts during the process of
data channel assignment. When BSC receives the channel request, it attempts to allocate
Measurement Point
Unit
Times

Description
This counter counts the number of failed data TCH/F seizure attempts during the process
32-121

Measurement Point
Unit
Times
32.90 C901260148 Number of FR_V1 assignment

attempts
Description
This counter counts the number of attempts of assigning TCH/F of voice version 1 as the
voice channel. After BSC responds the channel request message, allocates channel,
and the channel is occupied successfully, BSC sends the channel activation message
CHL_ACT to BTS to activate the TCH/F. For the assignment from A-interface, this counter
and C901260149 accumulate simultaneously after the assignment success message
is received. If the MS access message can not be received within specified time, the
assignment fails, and the counter accumulates.
Measurement Point
For the assignment from A-interface, the counter accumulates in the following cases:
BSC receives the message of assignment success, assignment failure, timer timeout, or
exception, instance being released, or instance being forcibly released.
Unit
Times

success
Description
This counter counts the number of successes of assigning TCH/F of voice version 1 as
the voice channel. After BSC responds the channel request message, allocates channel,
accumulates after the assignment success message is received.
32-122

Measurement Point
For the assignment from A-interface, this counter accumulates after BSC receives the
assignment success message.
Unit
Times

attempts
Description
Measurement Point
Unit
Times

success
Description
32-123

Measurement Point
Unit
Times

attempts
Description
Measurement Point
Unit
Times

success
Description
32-124

Measurement Point
Unit
Times
32.96 C901260154 Number of FR_V1 handover

Description
This counter counts the number of handover attempts that the destination voice channel
is of full-rate voice version 1. During handover, after MS is successfully accessed on the
new channel, BSC will receive the assignment completion message ASS_COM (intra-cell
handover) or HO_COM message (inter-cell handover and external handover). If BSC
correctly receives the above messages within specified time, the handover succeeds, this
counter and C901260155 accumulate simultaneously. If BSC receives the HO_FAILURE
message, then it is considered as handover failure with return, the counter accumulates. If
handover fails but BSC does not receives the HO_FAILURE message, then it is considered
as handover failure without return, the counter accumulates. For intra-cell handover and
inter-cell handover, the counter accumulates on the basis of source instances. For external
handover, because the source instance is not at the BSC, the counter accumulates on the
basis of destination instances.
Measurement Point
This counter accumulates when BSC receives the ASS_COM/HO_COM message,
the ASS_FAIL/HO_FAIL message, or message of exception, instance being released,
instance being forcibly released, or timer timeout.
Unit
Times
32.97 C901260155 Number of FR_V1 handover success

Description
This counter counts the number of successful handovers that the destination voice
channel is of full-rate voice version 1. This counter accumulates when BSC detects
the handover success message sent from MS on the newly allocated TCH/F channel.
For intra-cell handover, the handover success message is ASS_COM; for inter-cell
handover and external handover, the handover success message is HO_COM. For
intra-cell handover and inter-cell handover, the counter accumulates on the basis of
32-125

source instances. For external handover, because the source instance is not at the BSC,
the counter accumulates on the basis of destination instances.
Measurement Point
The counter counts when BSC receives the ASS_COM message or the HO_COM
message.
Unit
Times

Description
Measurement Point
Unit
Times
32.99 C901260157 Number of FR_V2 handover success

Description
32-126

Measurement Point
message.
Unit
Times

Description
Measurement Point
Unit
Times
32-127


success
Description
Measurement Point
message.
Unit
Times
32-128

Chapter 33
TCH/H Measurement
Table of Contents
Overview ..................................................................................................................33-5
C901270002 Number of signaling TCH/H seizure success for assignment ...............33-8
C901270005 Number of signaling TCH/H seizure success for handover ..................33-9
C901270007 Number of signaling TCH/H allocation attempts by BSC for
assignment.............................................................................................................33-12
C901270008 Number of signaling TCH/H allocation success for assignment .........33-13
C901270010 Number of signaling TCH/H allocation attempts by BSC due to
handover ................................................................................................................33-14
C901270011 Number of signaling TCH/H allocation success due to handover .......33-17
C901270012 Number of signaling TCH/H allocation failure due to handover ..........33-19
C901270013 Number of signaling TCH/H assignment attempts by BSC.................33-20
C901270016 Number of signaling TCH/H handover attempts.................................33-21
C901270017 Number of signaling TCH/H handover success..................................33-24
C901270018 Number of signaling TCH/H handover failure.....................................33-27
C901270019 Number of signaling TCH/H handover failure messages do not
received by BSC ....................................................................................................33-28
C901270021 Number of voice TCH/H seizure success for assignment...................33-29
C901270024 Number of voice TCH/H seizure success for handover......................33-31
C901270026 Number of TCH/H allocation attempts for assignment by BSC
(speech version 1)..................................................................................................33-34
C901270027 Number of TCH/H allocation success for assignment (speech
version1) ................................................................................................................33-35
C901270032 Number of TCH/H allocation attempts by BSC during handover
(speech version 1)..................................................................................................33-37
C901270033 Number of TCH/H allocation success during handover (speech
version 1) ...............................................................................................................33-39
C901270038 Number of TCH/H allocation attempts by BSC for assignment
(speech version 2)..................................................................................................33-41
C901270039 Number of TCH/H allocation success by BSC for assignment (speech
version 2) ...............................................................................................................33-43
C901270044 Number of TCH/H allocation attempts for handover by BSC (speech
version 2) ...............................................................................................................33-44
C901270045 Number of TCH/H allocation success for handover (speech version
2) ...........................................................................................................................33-47
C901270050 Number of TCH/H allocation attempts for assignment (speech version
3) ...........................................................................................................................33-49
33-1

C901270051 Number of TCH/H allocation success for assignment (speech version

3) ...........................................................................................................................33-51
C901270056 Number of TCH/H allocation attempts by BSC for handover (speech
version 3) ...............................................................................................................33-52
C901270057 Number of TCH/H allocation success for handover (speech version
3) ...........................................................................................................................33-55
C901270062 Number of Voice TCH/H assignment attempts by BSC......................33-57
C901270065 Number of Voice TCH/H handover attempts ......................................33-59
C901270067 Number of Voice TCH/H handover failure ..........................................33-62
C901270068 Number of Voice TCH/H handover failure messages do not received
by BSC...................................................................................................................33-63
C901270070 Number of data TCH/H seizure success for assignment ....................33-64
C901270073 Number of data TCH/H seizure success for handover .......................33-66
C901270075 Number of data TCH/H allocation attempts for assignment by BSC...33-68
C901270076 Number of data TCH/H allocation success for assignment ................33-70
C901270081 Number of data TCH/H allocation attempts by BSC...........................33-71
C901270082 Number of data TCH/H allocation success for handover....................33-74
C901270087 Number of data TCH/H assignment attempts by BSC........................33-76
C901270090 Number of data TCH/H handover attempts........................................33-78
C901270092 Number of data TCH/H handover failure............................................33-81
C901270093 Number of data TCH/H handover failure do not received by BSC ......33-82
C901270094 Number of TCH/H allocation failure for assignment due to TIPB
C901270095 Number of TCH/H allocation failure for assignment due to Resource
request to iTC failure (Speech version 1)................................................................33-85
C901270096 Number of TCH/H allocation failure for handover due to TIPB
C901270097 Number of TCH/H allocation failure for handover due to Resource
33-2

Chapter 33 TCH/H Measurement
C901270106 Number of TCH/H allocation failure due to request AIPB resource

C901270107 Number of TCH/H allocation failure due to request UDP port failure
C901270108 Number of TCH/H allocation failure due to AIPB connection failure for
handover (speech version 1) ................................................................................33-104
failure for assignment (speech version 2) .............................................................33-105
handover (speech version 2) ................................................................................ 33-110
failure for assignment (speech version 3) ............................................................. 33-111
for assignment (speech version 3)........................................................................ 33-112
assignment (speech version 3)............................................................................. 33-113
failure for handover (speech version 3)................................................................. 33-114
for handover (speech version 3) ........................................................................... 33-115
handover (speech version 3) ................................................................................ 33-116
failure for assignment (data) ................................................................................. 33-117
for assignment (data) ........................................................................................... 33-118
assignment (data) ................................................................................................ 33-119
failure for handover (data) ....................................................................................33-120
33-3

for handover (data)...............................................................................................33-121
handover (data)....................................................................................................33-122
C901270130 Number of assign TCH/H release by forced handover to forced
handover source ..................................................................................................33-123
C901270131 Number of assign TCH/H release by forced handover to queuing
user......................................................................................................................33-123
C901270132 Number of restore TCH/H release by forced handover to DBS ........33-124
C901270133 Number of assign TCH/H release by forced release to forced release
source ..................................................................................................................33-124
C901270134 Number of assign TCH/H release by forced release to queuing
user......................................................................................................................33-125
C901270135 Number of restore TCH/H release by forced release to DBS ...........33-126
C901270136 Number of signaling TCH/H seize failure for assign due to Abis
lack ......................................................................................................................33-126
C901270137 Number of signaling TCH/H seize failure for handover due to Abis
lack ......................................................................................................................33-127
C901270138 Number of voice TCH/H seizure failure for assignment
(cause:Abis) .........................................................................................................33-127
C901270139 Number of voice TCH/H seizure failure for handover (cause:Abis )..33-128
C901270140 Number of data TCH/H seizure failure for assignment (cause:Abis) .33-128
C901270141 Number of data TCH/H seizure failure for handover (cause:Abis) ....33-129
C901270142 Number of signaling TCH/H seize failure for assign due to radio
resource lack........................................................................................................33-129
C901270143 Number of signaling TCH/H seize failure for handover due to radio
resource lack........................................................................................................33-130
C901270144 Number of voice TCH/H seizure failure for assignment (cause:radio
resource)..............................................................................................................33-130
C901270145 Number of voice TCH/H seizure failure for handover (cause:radio
resource)..............................................................................................................33-131
C901270146 Number of data TCH/H seizure failure for assignment (cause:radio
resource)..............................................................................................................33-131
C901270147 Number of data TCH/H seizure failure for handover (cause:radio
resource)..............................................................................................................33-132
C901270148 Number of HR_V1 assignment attempts..........................................33-132
C901270149 Number of HR_V1 assignment success ..........................................33-133
C901270150 Number of HR_V3 assignment attempts..........................................33-133
C901270151 Number of HR_V3 assignment success ..........................................33-134
C901270152 Number of HR_V1 handover ...........................................................33-134
C901270153 Number of HR_V1 handover success..............................................33-135
C901270154 Number of HR_V3 handover ...........................................................33-135
C901270155 Number of HR_V3 handover success..............................................33-136
33-4

33.1 Overview
During GSM BSC signaling system, the allocation uses of TCH/H channel mainly exist
in assignment and handover processes. The assignment processes include immediate
assignment, general assignment; handover processes include inner handover and outer
handover.
The measurement point of TCH/H counters in immediate assignment process is shown in
Figure 33-1.
When TC is internal and external, the measurement point of TCH/H counter in general
assignment processes is shown in Figure 33-2and Figure 33-3.
33-5

When TC is internal and external, the measurement point of TCH/H counter in inner
handover process is shown in Figure 33-4 and Figure 33-5.
33-6

When TC is internal and external, the measurement point of TCH/H counter in outer
handover process is shown in Figure 33-6 and Figure 33-7.
33-7


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 Point
BSC applies for channel (due to assignment, it is used for signaling channels) and seizure
succeeds. The measurement point is A1, as shown in Figure 33-8.
33-8

Unit
Times
Related Features
l ZGO-03-02-003 Full dynamic channel allocation on Um interface

Definition
Number of signaling TCH/H seizure success for handover.
Description
This counter counts the number of TCH/H seizure success in signaling channel handover.
After BSC receives channel request message, it tries to assign channel for the request.
This counter will accumulate if assignment and seizure succeed; if application returns no
signaling but it is possible to queue or being forced to disconnect, it will enter the state of
waiting for resource. This counter will accumulate if waiting succeeds.
Measurement Point
BSC applies for channel (because handover, usage are signaling channels) and seizure
succeeds, or it receives inner waiting resource valid message. The measurement points
are C1, D1, as shown in Figure 33-9, Figure 33-10, Figure 33-11, and Figure 33-12.
33-9

33-10

Unit
Times
Related Features
33-11

33.4 C901270007 Number of signaling TCH/H allocation

attempts by BSC for assignment
Definition
Number of signaling TCH/H assignment attempts by BSC for assignment
Description
This counter counts the number of TCH/H channel attempts being assigned on allocating
signaling channel, including the number of assignment success (C901270008) and
assignment failure (900060174).
After BSC responds channel request message assignment and successfully seizes
TCH/H channel, BSC send channel activation message CHL_ACT to BTS to activate the
TCH/H. If activation succeeds, it will receive the CHL_ACT_ACK message sent by BTS,
it indicates TCH/H assignment succeeds, this counter and C901270008 will accumulate
simultaneously. On the contrary, if channel activation fails due to receiving channel
activation failure message, wrong channel activation response message, timer T9103
timeout, channel instance being released, channel being forced to disconnect etc, this
counter and C900060174 will accumulate simultaneously.
Measurement Point
After BSC activates TCH/H (because allocation, usage are signaling channels), it receives
the CHL_ACK message sent by BTS, or receives channel activation failure message,
wrong channel activation response message, timer T9013 timeout, channel instance
being released, channel being forced to disconnect etc. (C901270008+C900060174).
33-12

Unit
Times
Related Features

Definition
Number of signaling TCH/H allocation success for assignment
Description
This counter counts the number of TCH/H channel success assignment on allocating
signaling channel.
After BSC responds channel request messages assignment and successfully seizures
channel, BSC sends channel activation message CHL_ACT to activate the TCH/H. If
activated successfully, it will receive CHL_ACT_ACK message sent by BTS, it indicates
that TCH/H assigns successfully and the counter accumulates.
Measurement Point
BSC receives correctly CHL_ACT_ACK message sent by BTS and the reason is that
allocation and usage are signaling channel. The measurement point is A2, as shown in
Figure 33-14.
33-13

Unit
Times
Related Features

attempts by BSC due to handover
Definition
Number of signaling TCH/H allocation attempts by BSC due to handover
Description
This counter counts the number of TCH/H channel attempt being allocated in signaling
channel handover, including successful allocation times (C901270011) and failed
allocation times (C901270012).
After BSC responds channel request message assignment and successfully occupies
TCH/H channel, BSC send channel activation message CHL_ACT to BTS to activate
the TCH/H. If activation is successful, it will receive the CHL_ACT_ACK message sent
by BTS, it indicates TCH/H assignment is successful, this counter and C901270011 will
accumulate simultaneously. On the contrary, if channel activation fails due to receiving
channel activation failure message, wrong channel activation response message, timer
T9103 timeout, channel instance being released, channel being forced to disconnection
etc, this counter and C901270012 will accumulate simultaneously.
Measurement Point
After BSC activates TCH/H (because allocation, usage are signaling channel),
receives correctly the CHL_ACK_ACK message sent by BTS, or receives channel
activation failure message, wrong channel activation response message, timer T9013
timeout, channel instance being released, channel being forced to disconnection etc.
(C901270011+C901270012). The measurement points are C3, C4, as shown in Figure
33-15, Figure 33-16, Figure 33-17, and Figure 33-18.
33-14

33-15

Unit
Times
Related Features
33-16


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 assignment in signaling
channel handover.
After BSC responds channel request messages assignment and successfully occupies
channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/H.
If activated successfully, it will receive CHL_ACT_ACK message sent by BTS, it indicates
that TCH/H assigns successfully and the counter accumulates.
Measurement Point
BSC receives correctly CHL_ACT_ACK message sent by BTS and the reason is that
allocation and usage are signaling channel. The measurement points are C3, D3, as
33-17

33-18

Unit
Times
Related Features

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 failure.
TCH/H channel, BSC send channel activation message CHL_ACT to BTS to activate the
TCH/H. If channel activation fails due to receiving channel activation failure message,
wrong channel activation response message, timer T9103 timeout, channel instance
being released, channel being forced to disconnection etc, this counter will increment.
Measurement Point
BSC activates TCH/H to be used as signaling channel because of handover, but receiving
channel activation failure message, wrong channel activation response message, timer
33-19

T9103 timeout, channel instance being released, channel being forced to disconnection
etc. The measurement points are C3, D3, as shown in Figure 33-23, Figure 33-24.
Figure 33-24 External handover failure flow 2 (internal TC)
Unit
Times
Related Features

assignment attempts by BSC
Definition
Number of signaling TCH/H assignment attempts by BSC
Description
This counter counts the number of attempt allocating TCH/H channel to be signaling
channel.
33-20

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 accumulates;
if it is impossible to receive the MS access notification in the certain time, this allocation
fails.
Measurement Point
For immediate allocation, this counter counts the number when BSC receives EST_IND
message correctly or T31.3 timeout (not receive the MS access notification in the certain
time). The measurement point is A3, as shown in Figure 33-25.
Unit
Times
Related Features

handover attempts
Definition
Number of signaling TCH/H handover attempts
33-21

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 Point
On newly assigned TCH/H channel, BSC check the handover success
ASS_COM/HO_FAIL message sent by MS, or receives handover failure
ASS_FAIL/HO_FAIL message, receives abnormal message, instance being released,
instance being forced to disconnection, timer timeout, this counter will accumulate. The
measurement points are C4, D4, as shown in Figure 33-26, Figure 33-27, Figure 33-28,
and Figure 33-29.
33-22

33-23

Unit
Times
Related Features

handover success
Definition
Number of signaling TCH/H handover success
Description
This counter counts the number of TCH/H channel success in signaling channel handover.
When BSC check the handover success message sent by MS in newly assigned TCH/H
channel, this counter will accumulate.
For handover in cell, the symbol message of handover success is ASS_COM. For
handover between cells and outer handover, the symbol message of handover success
is HO_COM. For handover in cell and between cells, the counter accumulates based on
the resource instance; for the outer handover, because the resource instance is not in
present BSC, the counter accumulates based on the object instance.
33-24

Measurement Point
BSC receives ASS_COM or HO_COM message. The measurement points are C4, D4,
as shown in Figure 33-30, Figure 33-31, Figure 33-32 and Figure 33-33.
33-25

Unit
Times
Related Features
33-26


handover 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 channel, receives allocation failure on original channel
or handover failure.
Measurement Point
BSC receives ASS_FAIL or HO_FAIL message. The measurement points are C4, D4, as
shown in Figure 33-34, Figure 33-35.
33-27

Unit
Times
Related Features

handover failure messages do not received by BSC
Definition
Number of signaling TCH/H handover failure messages do not received by BSC
Description
This counter counts the number of TCH/H channel return no handover failure.
This counter accumulates when BSC sends allocation request to MS or handover request,
MS does not handover successfully and does not return original channel.
Measurement Point
BSC receives abnormal message, or instance being released, instance being forced to
disconnection, timer timeout message. The measurement point is C4, as shown in Figure
33-36, Figure 33-37.
33-28

Unit
Times
Related Features

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

After BSC receives channel request message, it attempts to assign channel for the request.
This counter will accumulate if assignment and occupation succeed. If application returns
no channel but possible to queue or force to disconnect, it enters the state of waiting for
resource. This counter accumulates if waiting succeeds.
Measurement Point
BSC applies for channel (because allocation, usage are voice channel) and occupation
succeeds or BSC receives inner waiting resource valid message. The measurement point
is B1, as shown in Figure 33-38, Figure 33-39.
33-30

Unit
Times
Related Features

Definition
Number of voice TCH/H seizure success for handover
Description
This counter counts the number of TCH/H channel being occupied on voice channel
handover.
This counter will accumulate if assignment and occupation succeed. If application returns
no channel but possible to queue or force to disconnect, it enters the state of waiting for
resource. This counter accumulates if waiting succeeds.
Measurement Point
BSC applies for channel (because handover, usage are voice channel) and occupation
succeeds or BSC receives inner waiting resource valid message. The measurement points
are C1, D1, as shown in Figure 33-40, Figure 33-41, Figure 33-42, and Figure 33-43.
33-31

33-32

Unit
Times
Related Features
33-33

33.16 C901270026 Number of TCH/H allocation

attempts for assignment by BSC (speech version 1)
Definition
Number of TCH/H allocation attempts for assignment by BSC (speech version 1)
Description
This counter counts the number of TCH/H channel being attempt to assign on allocation
voice channel (used for voice version 1), including assignment success (C901270027) and
assignment failure (C900060175+C900060176+900060177+C900060178)
After BSC respond channel request message assignment and successfully occupied
TCH/H channel, BSC first finishes connection, then sends channel activation message
CHL_ACT to BTS to activate the the TCH/H. If activation succeeds, BSC will receive
the CHL_ACT_ACK message sent by BTS. It indicated that assignment succeeds, this
counter and C901270027 accumulate simultaneously; on the contrary, if failed, this
counter and another counter related the failure reason accumulate siulataneously.
Measurement Point
Assignment succeeds or fails (because allocation and usage are voice channel, use voice
version 1). The measurement points are B2, B3, as shown in Figure 33-44, Figure 33-45.
33-34

Unit
Times
Related Features
33.17 C901270027 Number of TCH/H allocation success

Definition
Number of TCH/H allocation success for assignment (speech version1)
Description
voice channel (used for voice version 1).
channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/F.
If activation succeeds, BSC will receive the CHL_ACT_ACK message sent by BTS. It
indicated that TCH/H assignment succeeds, this counter accumulate.
Measurement Point
BSC correctly receives the CHL_ACT_ACK message sent by BTS, and because allocation
and usage are voice channel (use voice version 1). The measurement point is B3, as
33-35

Unit
Times
Related Features
33-36


attempts by BSC during handover (speech version
1)
Definition
Number of TCH/H allocation attempts by BSC during handover (speech version 1)
Description
This counter counts the number of TCH/H channel being attempt to assign on voice
channel (use voice version 1) handover, including assignment success (C901270033)
and assignment failure (C900060179+C900060180+900060181+C900060182)
CHL_ACT to BTS to activate the the TCH/H. If activation succeeds, BSC will receive
the CHL_ACT_ACK message sent by BTS. It indicated that assignment succeeds, this
counter and related C901270033 accumulate simultaneously; on the contrary, if failed,
this counter and another counter related the failure reason accumulate simultaneously.
Measurement Point
Assignment succeeds or fails (because handover, usage are voice channel, use voice
version 1). The measurement points are C3, D3, as shown in Figure 33-48, Figure 33-49,
and Figure 33-50.
33-37

Unit
Times
Related Features
33-38


during handover (speech version 1)
Definition
Number of TCH/H allocation success during handover (speech version 1)
Description
This counter counts the number of TCH/H channel success assignment on voice channel
(use voice version 1).
If activation succeeds, it will receive CHL_ACT_ACK message sent by BTS. It indicated
that TCH/H assignment succeeds, this counter accumulate.
Measurement Point
BSC correctly receives the CHL_ACT_ACK message sent by BTS, and because handover
and usage are voice channel (use voice version 1). The measurement points are C3, D3,
as shown in Figure 33-51, Figure 33-52, Figure 33-53, and Figure 33-54.
33-39

33-40

Unit
Times
Related Features

attempts by BSC for assignment (speech version 2)
Definition
Number of TCH/H allocation attempts by BSC for assignment (speech version 2)
Description
voice channel (use voice version 2), including assignment success (C901270039) and
CHL_ACT to BTS to activate the TCH/H. If activation succeeds, it will receive the
CHL_ACT_ACK message sent by BTS. It indicated that TCH/H assignment succeeds,
this counter and C901270039 accumulate simultaneously; on the contrary, if failed, this
counter and another counter related the failure reason accumulate simultaneously.
33-41

Measurement Point
Assignment succeeds or fails (because allocation, usage are voice channel, use voice
version 2). The measurement points are B2, B3, as shown in Figure 33-55, Figure 33-56.
Unit
Times
Related Features
33-42


by BSC for assignment (speech version 2)
Definition
Number of TCH/H allocation success by BSC for assignment (speech version 2)
Description
This counter counts the number of TCH/H channel success assignment on allocation voice
channel (use voice version 2).
After BSC responds channel request message assignment and successfully occupied
Measurement Point
33-43

Unit
Times
Related Features
l

attempts for handover by BSC (speech version 2)
Definition
Number of TCH/H allocation attempts for handover by BSC (speech version 2)
Description
channel (use voice version 2) handover, including assignment success (C901270045)
and assignment failure (C900060187+C900060188+900060189+C900060190)
33-44

Measurement Point
Figure 33-61, and Figure 33-62.
33-45

Unit
Times
Related Features
33-46


for handover (speech version 2)
Definition
Number of TCH/H allocation success for handover (speech version 2)
Description
Measurement Point
33-47

33-48

Unit
Times
Related Features

Definition
Number of TCH/H allocation attempts for assignment (speech version 3)
Description
voice channel (use voice version 3), including assignment success (C901270051) and
33-49

Measurement Point
Assignment succeeds or fails (because allocation, usage are voice channel, use voice
version 3). The measurement points are B2, B3, as shown in Figure 33-67and Figure
33-68.
Unit
Times
Related Features
33-50


for assignment (speech version 3)
Definition
Number of TCH/H allocation success for assignment (speech version 3)
Description
This counter counts the number of TCH/H channel success assignment on allocation voice
channel (use voice version 3).
Measurement Point
shown in Figure 33-69 and Figure 33-70.
33-51

Unit
Times
Related Features

Definition
Number of TCH/H allocation attempts by BSC for handover (speech version 3)
Description
channel (use voice version 3), including assignment success (C901270057) and
33-52

Measurement Point
Figure 33-73, and Figure 33-74.
33-53

Unit
Times
Related Features
33-54


for handover (speech version 3)
Definition
Number of TCH/H allocation success for handover (speech version 3)
Description
TCH/H. If activation succeeds, it will receive CHL_ACT_ACK message sent by BTS. It
indicated that TCH/H assignment succeeds, this counter accumulate.
Measurement Point
33-55

33-56

Unit
Times
Related Features

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).
TCH/H. For allocation from A-interface, after receiving allocation success message, this
counter and C900060199 accumulate simultaneously. If it is impossible to receive MS
access notification in the certain time, the assignment fails, this counter and C900060200
33-57

Measurement Point
For allocation from A-interface, BSC correctly receives the allocation success message,
allocation failure message, timer timeout message, or abnormal message, the instance
being released, the instance being forced to disconnection, this counter accumulates. The
measurement point is B5, as shown in Figure 33-79and Figure 33-80.
Unit
Times
Related Features
33-58


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 handover success (C900060201), TCH/H handover failure
with return (C901270067) and TCH/H handover failure without return (C901270068).
During handover, when MS is accessed successfully on the new channel, BSC will
receive allocation finishing message ASS_COM (handover in cell) or HO_COM message
(handover between cells and outer handover).
If BSC correctly receives the message above in the certain time, it indicated that handover
succeed, the related counter and C900060201 will accumulate simultaneously; if BSC
receives HO_FAILURE, it returns handover failure, this counter and C901270067 will
accumulate simultaneously; if handover fails, BSC does not receive HO_FAILURE, then
no return handover fails. This counter and C901270068 will accumulate simultaneously.
For handover in cell and between cells, this counter accumulates based on the resource
instance; for outer handover, because the resource instance is not in local BSC, the object
instance accumulates.
Measurement Point
BSC receives ASS_COM/HO_COM message, ASS_FAIL/HO_FAIL message or
receive abnormal message, the instance being released, the instance being forced to
disconnection, timer timeout. The measurement points are C4, D4, as shown in Figure
33-59

33-60

Unit
Times
Related Features
33-61


failure
Definition
Number of Voice TCH/H handover failure
Description
This counter counts the number of TCH/H channel returning handover failure on voice
channel handover.
MS is in handover on TCH/H channel, accesses new channel failure and returns original
channel. This counter accumulates when receiving allocation failure/handover failure on
original channel.
Measurement Point
BSC receives the ASS_FAIL/HO_FAIL message. The measurement points are C4, D4,
as shown in Figure 33-85and Figure 33-86.
33-62

Unit
Times
Related Features

Definition
Number of Voice TCH/H handover failure messages do not received by BSC
Description
This counter counts the number of TCH/H channel returning no handover failure on voice
channel handover.
BSC sends allocation request/handover request to MS, MS does not handover
successfully, not return resource channel, and then accumulates.
Measurement Point
BSC receives abnormal message, timer timeout message or the instance being released,
the instance being forced to disconnection. The measurement points are C4, D4, as shown
in Figure 33-87and Figure 33-88.
33-63

Unit
Times
Related Features

Definition
Number of data TCH/H seizure success for assignment
Description
This counter counts the number of TCH/H channel being occupied successfully on
allocation data channel.
33-64

If assignments and occupation succeed, this counter will accumulate; If application returns
no channel but possible to queue or force to disconnect, it enters the status of waiting
resource. This counter will also accumulate until waiting succeeds.
Measurement Point
BSC applies for channel (because allocation, usage are data channels) and occupies
successfully, or BSC receives inner waiting resource valid message. The measurement
points is B1, as shown in Figure 33-89and Figure 33-90.
Unit
Times
Related Features
33-65



Definition
Number of data TCH/H seizure success for handover
Description
This counter counts the number of TCH/H channel being occupied successfully on data
channel handover.
If assignments and occupation succeed, this counter will accumulate; If application returns
no channel but possible to queue or force to disconnect, it enters the status of waiting
resource. This counter will also accumulate until waiting succeeds.
Measurement Point
BSC applies for channel (because handover, usage are data channels) and occupies
successfully, or BSC receives inner waiting resource valid message. The measurement
points are C1, D1, as shown in Figure 33-91, Figure 33-92, Figure 33-93, and Figure
33-94.
33-66

33-67

Unit
Times
Related Features

attempts for assignment by BSC
Definition
Number of data TCH/H allocation attempts for assignment by BSC
Description
This counter counts the number of TCH/H channel being assigned on allocation
data channel, including assignment success (C901270076) and assignment failure
(C900060202 + C900060203 + C900060204 + C900060205).
Usage
33-68

this related counter and C901270076 accumulate simultaneously; on the contrary, if fails,
Measurement Point
Assignment succeeds or fails (because allocation, usage are data channel). The
measurement points are B2, B5, as shown in Figure 33-95and Figure 33-96.
Unit
Times
Related Features
33-69


Definition
Number of data TCH/H allocation success for assignment
Description
This counter counts the number of TCH/H channel being assigned successfully.
TCH/H. If activation succeeds, it will receive the CHL_ACT_ACK message sent by BTS.
It indicated that TCH/H assignment succeeds, This counter accumulates.
Measurement Point
and usage are data channel. The measurement points is B3, as shown in Figure 33-97and
Figure 33-98.
33-70

Unit
Times
Related Features

attempts by BSC
Definition
Number of data TCH/H allocation attempts by BSC
Description
This counter counts the number of TCH/H channel being attempted to assign on data
channel handover, including assignment success (C901270082) and assignment failure
(C900060206 + C900060207 + C900060208 + C900060209).
this related counter and C901270082 accumulate simultaneously; on the contrary, if fails,
33-71

Measurement Point
Assignment succeeds or fails (because handover, usage are data channels). The
measurement points are C3, D3, as shown in Figure 33-99, Figure 33-100, Figure 33-101,
and Figure 33-102.
33-72

Unit
Times
Related Features
33-73


Definition
Number of data TCH/H allocation success for handover
Description
This counter counts the number of TCH/H channel assignment successfully on data
channel handover.
TCH/H. If activation succeeds, it will receive the CHL_ACT_ACK message sent by BTS
and indicate that TCH/H assignment succeeds. This counter accumulates.
Measurement Point
and usage are data channel. The measurement points are C3, D3, as shown in Figure
33-74

33-75

Unit
Times
Related Features

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).
TCH/H. For allocation from A-interface, after receiving allocation success message, this
counter and C900060210 accumulate simultaneously. If it is impossible to receive MS
access notification in the certain time, the assignment fails, this counter and C900060211
33-76

Measurement Point
For allocation from A-interface, BSC correctly receives the allocation success message,
allocation failure message, timer timeout message, or abnormal message, the instance
being released, the instance being forced to disconnect, this counter accumulates. The
measurement point is B5, as shown in Figure 33-107and Figure 33-108.
Unit
Times
Related Features
33-77


attempts
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
receives HO_FAILURE, it returns handover failure, this counter and C901270092 will
accumulate simultaneously; if handover fails, BSC does not receive HO_FAILURE,
then no returning handover fails. This counter and C901270093 will accumulate
simultaneously.
For handover in cell and between cells, this counter accumulates based on the resource
instance; for outer handover, because the resource instance is not in local BSC, the object
instance accumulates.
Measurement Point
BSC receives ASS_COM/HO_COM message, ASS_FAIL/HO_FAIL message or
receive abnormal message, the instance being released, the instance being forced to
disconnection, timer timeout. The measurement points are C4, D4, as shown in Figure
33-78

33-79

Unit
Times
Related Features
33-80


failure
Definition
Number of data TCH/H handover failure
Description
This counter counts the number of TCH/H channel returning handover failure on data
channel handover.
MS is under handover on TCH/H channel, access new channel fails then returns original
channel. This counter accumulates when receiving allocation failure/handover failure on
original channel.
Measurement Point
BSC receives the ASS_FAIL/HO_FAIL message. The measurement points are C4, D4,
as shown in Figure 33-113and Figure 33-114.
33-81

Unit
Times
Related Features

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 channel, then accumulate.
33-82

Measurement Point
BSC receives abnormal message, the instance being released, the instance being forced
to disconnect or timer timeout message. The measurement point is C4, as shown in Figure
33-115and Figure 33-116.
Unit
Times
Related Features
33-83


for assignment due to TIPB connection failure
(Speech version 1)
Definition
Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech
version 1)
Description
This counter counts the number of TCH/H channel assignment failure due to TIPB
connection failure when allocating voice channel (use voice version 1).
TCH/H channel, BSC sends TIU connection request to TIPB. If TIU connection fails due
to receiving TIU connection failure, or wrong TIU connection respond message, timer
timeout, then this counter will accumulate.
Measurement Point
Due to allocation BSC uses TCH/H. Receive connection failure message, wrong
connection respond message, or timer timeout when in TIU connection. The measurement
Unit
Times
Related Features
33-84


for assignment due to Resource request to iTC
Definition
Number of TCH/H allocation failure for assignment due to Resource request to iTC failure
(Speech version 1)
Description
This counter counts the number of TCH/H channel assignment failure due to iTC
application resource failure when allocating voice channel (use voice version 1).
TCH/H channel, BSC apply for resource to iTC. If iTC application resource fails due to
receiving iTC resource unavailability, or wrong response message, or timer timeout, then
it contributes to TCH/H assignment failure and this counter will accumulate.
Measurement Point
Due to allocation BSC uses TCH/H. Receive iTC resource unabailability, wrong respond
message, or timer timeout when in iTC application resource. The measurement point is
B1, as shown in Figure 33-118.
Unit
Times
Related Features
33-85


for handover due to TIPB connection failure
(Speech version 1)
Definition
Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech
version 1)
Description
This counter counts the number of TCH/H channel assignment failure due to TIU
connection failure when in voice channel handover (use voice version 1).
to receiving TIU connection failure, or wrong TIU connection response message, timer
Measurement Point
Due to handover BSC uses TCH/H. Receive connection failure message, wrong
connection response message, or timer timeout when in TIU connection. The
measurement points are C2, D2, as shown in Figure 33-119and Figure 33-120.
33-86

Unit
Times
Related Features

for handover due to Resource request to iTC failure
(Speech version 1)
Definition
Number of TCH/H allocation failure for handover due to Resource request to iTC failure
(Speech version 1)
Description
application resource failure when voice channel handover (use voice version 1).
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
33-87

Measurement Point
Due to allocation BSC uses TCH/H. Receive iTC resource unabailability, wrong response
message, or timer timeout when in iTC application resource. The measurement points are
C1, D1, as shown in Figure 33-121and Figure 33-122.
Unit
Times
Related Features
33-88


(Speech version 2)
Definition
version 2)
Description
This counter counts the number of TCH/H channel assignment failure due to TIPB
Measurement Point
Unit
Times
Related Features
33-89


Definition
(Speech version 2)
Description
Measurement Point
Due to allocation BSC uses TCH/H. Receive iTC resource unabailability, wrong response
Unit
Times
Related Features
33-90


(Speech version 2)
Definition
version 2)
Description
connection failure when voice channel handover (use voice version 2).
Measurement Point
33-91

Unit
Times
Related Features

(Speech version 2)
Definition
(Speech version 2)
Description
application resource failure when voice channel (use voice version 2).
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
33-92

Measurement Point
Due to handover BSC uses TCH/H. Receive iTC resource un availability, wrong response
C1, D1, as shown in Figure 33-127and Figure 33-128.
Unit
Times
Related Features
33-93


(Speech version 3)
Definition
version 3)
Description
Measurement Point
Unit
Times
Related Features
33-94


Definition
(Speech version 3)
Description
Measurement Point
Due to allocation BSC uses TCH/H. Receive iTC resource unavailability, wrong response
Unit
Times
Related Features
33-95


(Speech version 3)
Definition
version 3)
Description
connection failure when voice channel (use voice version 3) handover.
Measurement Point
33-96

Unit
Times
Related Features

(Speech version 3)
Definition
(Speech version 3)
Description
application resource failure when voice channel (use voice version 3) handover.
TCH/H channel, BSC applies for resource to iTC. If iTC application resource fails due to
33-97

Measurement Point
Due to allocation BSC uses TCH/H. Receive iTC resource unavailability, wrong response
C1, D1, as shown in Figure 33-133 and Figure 33-134.
Unit
Times
Related Features
33-98


Definition
Number of TCH/H allocation failure due to request AIPB resource failure for assignment
(speech version 1)
Description
This counter counts the number of TCH/H allocation failure due to request AIPB resource
failure or no AIPB board resource) indicates TCH/H allocation failure.
Usage
This counter is used to find out the frequency of TCH/H allocation failure due to request
Measurement Point
Unit
Times
33-99


(speech version 1)
Definition
Number of TCH/H allocation failure due to request UDP port failure for assignment (speech
version 1)
Description
This counter counts the number of TCH/H channel allocation failure due to UDP port failure
Usage
UDP port failure.
Measurement Point
Unit
Times
33-100


(speech version 1)
Definition
Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech
version 1)
Description
Usage
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB
access failure.
Measurement Point
Unit
Times
33-101


(speech version 1)
Definition
Number of TCH/H allocation failure due to request AIPB resource failure for handover
(speech version 1)
Description
AIPB resource), indicating TCH/H allocation failure.
Usage
Measurement Point
Unit
Times
Related Features
ZGO-03-02-011 Channel Repacking
33-102


(speech version 1)
Definition
Number of TCH/H allocation failure due to request UDP port failure for handover (speech
version 1)
Description
during handover.

request UDP port.
Usage
UDP port failure.
Measurement Point
Unit
Times
Related Features
33-103


(speech version 1)
Definition
Number of TCH/H allocation failure due to AIPB connection failure for handover (speech
version 1)
Description
This counter counts the number of TCH/H channel allocation failure due to AIPB access

access AIPB.
Usage
access failure.
Measurement Point
Unit
Times
Related Features
33-104


Definition
(speech version 2)
Description
Usage
Measurement Point
Unit
Times
33-105


(speech version 2)
Definition
version 2)
Description
Usage
UDP port failure.
Measurement Point
Unit
Times
33-106


(speech version 2)
Definition
version 2)
Description
Usage
access failure.
Measurement Point
Unit
Times
33-107


(speech version 2)
Definition
(speech version 2)
Description
AIPB resource), indicating TCH/H allocation failure.
Usage
Measurement Point
Unit
Times
Related Features
33-108


(speech version 2)
Definition
version 2)
Description
during handover.

(speech version 2) to request channel due to handover, access request is sent to access
module, if access module returns access failure due to UDP port request failure.
Usage
UDP port failure.
Measurement Point
Unit
Times
Related Features
33-109


(speech version 2)
Definition
version 2)
Description

access AIPB.
Usage
access failure.
Measurement Point
Unit
Times
Related Features
33-110


Definition
(speech version 3)
Description
Usage
Measurement Point
Unit
Times
Related Features
33-111


(speech version 3)
Definition
version 3)
Description
Usage
UDP port failure.
Measurement Point
Unit
Times
Related Features
33-112


(speech version 3)
Definition
version 3)
Description
Usage
access failure.
Measurement Point
Unit
Times
Related Features
33-113


(speech version 3)
Definition
(speech version 3)
Description
(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
resource), indicating TCH/H allocation failure.
Usage
Measurement Point
Unit
Times
Related Features
33-114


(speech version 3)
Definition
version 3)
Description
during handover.
request UDP port.
Usage
UDP port failure.
Measurement Point
Unit
Times
Related Features
33-115


(speech version 3)
Definition
version 3)
Description
access AIPB.
Usage
access failure.
Measurement Point
Unit
Times
Related Features
33-116


assignment (data)
Definition
(data)
Description
This counter increments while BSC receives assignment requests (data) to apply for AIPB
board resource from database, failed request (including database return failure or no AIPB
resource) indicates TCH/H allocation failure.
Usage
Measurement Point
Unit
Times
33-117


(data)
Definition
Number of TCH/H allocation failure due to request UDP port failure for assignment (data)
Description
failure.
Usage
UDP port failure.
Measurement Point
Unit
Times
33-118


(data)
Definition
Number of TCH/H allocation failure due to AIPB connection failure for assignment (data)
Description
failure.
Usage
access failure.
Measurement Point
Unit
Times
33-119


(data)
Definition
(data)
Description
request channel is handover, to request AIPB resource from database. This counter
increments if failed to request AIPB (including database returning failure or no AIPB
resource), indicating TCH/H allocation failure.
Usage
Measurement Point
Unit
Times
Related Features
33-120


due to request UDP port failure for handover (data)
Definition
Number of TCH/H allocation failure due to request UDP port failure for handover (data)
Description
during handover.

increments while access module returns failure and the reason is failed to request UDP
port.
Usage
UDP port failure.
Measurement Point
Unit
Times
Related Features
33-121


due to AIPB connection failure for handover (data)
Definition
Number of TCH/H allocation failure due to AIPB connection failure for handover (data)
Description

increments while access module returns failure and the reason is failed to access AIPB.
Usage
access failure.
Measurement Point
Unit
Times
Related Features
33-122

33.78 C901270130 Number of assign TCH/H release by

forced handover to forced handover source
Definition
Number of assign TCH/H release by forced handover to forced handover source
Description
of times that the released TCH/H resource is assigned to the forced handover source.
TCH/H resource is assigned to the forced handover source, the counter accumulates.
Usage
This counter is used to find out the frequency of the TCH/H released by forced handover
being assigned to the forced handover source.
Measurement Point
TCH/H resource is assigned to the forced handover source, the counter accumulates.
Unit
Times

forced handover to queuing user
Definition
Number of assign TCH/H release by forced handover to queuing user
Description
of times that the released TCH/H resource is assigned to the queuing user.
TCH/H resource is assigned to the queuing user, the counter accumulates.
Usage
33-123

Measurement Point
Unit
Times
33.80 C901270132 Number of restore TCH/H release by

forced handover to DBS
Definition
Number of restore TCH/H release by forced handover to DBS
Description
of times that the released TCH/H resource is restored to the database instead of being
TCH/H resource is just released instead of being assigned to other users, the counter
accumulates.
Usage
Measurement Point
accumulates.
Unit
Times

forced release to forced release source
Definition
Number of assign TCH/H release by forced release to forced release source
33-124

Description
times that the released TCH/H resource is assigned to the forced release source.
TCH/H resource is assigned to the forced release source, the counter accumulates.
Usage
This counter is used to find out the frequency of the TCH/H released by forced release
being assigned to the forced release source.
Measurement Point
TCH/H resource is assigned to the forced release source, the counter accumulates.
Unit
Times

forced release to queuing user
Definition
Number of assign TCH/H release by forced release to queuing user
Description
times that the released TCH/H resource is assigned to the queuing user.
Usage
Measurement Point
Unit
Times
33-125

33.83 C901270135 Number of restore TCH/H release

by forced release to DBS
Definition
Number of restore TCH/H release by forced release to DBS
Description
When the BSC CS service instance is forcibly released, this counter counts the number
of times that the released TCH/H resource is restored to the database instead of being
accumulates.
Usage
Measurement Point
accumulates.
Unit
Times
33.84 C901270136 Number of signaling TCH/H seize

failure for assign due to Abis lack
Description
This counter counts the number of failed signaling TCH/H seizure attempts during the
Measurement Point
33-126

Unit
Times

failure for handover due to Abis lack
Description
Measurement Point
fails.
Unit
Times

Description
This counter counts the number of failed voice TCH/H seizure attempts during the process
Measurement Point
33-127

Unit
Times

failure for handover (cause:Abis )
Description
Measurement Point
Unit
Times

Description
This counter counts the number of failed data TCH/H seizure attempts during the process
of data channel assignment. When BSC receives the channel request, it attempts to
Measurement Point
33-128

Unit
Times

Description
Measurement Point
Unit
Times

failure for assign due to radio resource lack
Description
Measurement Point
Unit
Times
33-129


failure for handover due to radio resource lack
Description
Measurement Point
fails.
Unit
Times

Description
Measurement Point
Unit
Times
33-130


Description
Measurement Point
Unit
Times

Description
of data channel assignment. When BSC receives the channel request, it attempts to
Measurement Point
Unit
Times
33-131


Description
Measurement Point
Unit
Times
33.96 C901270148 Number of HR_V1 assignment

attempts
Description
This counter counts the number of attempts of assigning TCH/H of voice version 1 as
CHL_ACT to BTS to activate the TCH/H. For the assignment from A-interface, this counter
Measurement Point
Unit
Times
33-132


success
Description
This counter counts the number of successes of assigning TCH/H of voice version 1 as
Measurement Point
Unit
Times

attempts
Description
This counter counts the number of attempts of assigning TCH/H of voice version 3 as
Measurement Point
Unit
Times
33-133


success
Description
This counter counts the number of successes of assigning TCH/H of voice version 3 as
Measurement Point
Unit
Times
33.100 C901270152 Number of HR_V1 handover

Description
is of half-rate voice version 1. During handover, after MS is successfully accessed on the
Measurement Point
Unit
Times
33-134


success
Description
channel is of half-rate voice version 1. This counter accumulates when BSC detects
the handover success message sent from MS on the newly allocated TCH/H channel.
Measurement Point
message.
Unit
Times

Description
is of half-rate voice version 3. During handover, after MS is successfully accessed on the
Measurement Point
33-135

Unit
Times

success
Description
channel is of half-rate voice version 3. This counter accumulates when BSC detects
the handover success message sent from MS on the newly allocated TCH/H channel.
Measurement Point
message.
Unit
Times
33-136

Chapter 34
Abis Interface Message
Counter Measurement
Table of Contents
Overview ..................................................................................................................34-3
C901280001 Number of DATA REQUEST messages...............................................34-4
C901280002 Number of DATA INDICATION messages ...........................................34-5
C901280003 Number of ERROR INDICATION messages........................................34-5
C901280004 Number of ESTABLISH REQUEST messages ....................................34-6
C901280005 Number of ESTABLISH CONFIRM messages .....................................34-7
C901280006 Number of ESTABLISH INDICATION messages .................................34-8
C901280007 Number of RELEASE REQUEST messages .......................................34-9
C901280008 Number of RELEASE CONFIRM messages......................................34-10
C901280009 Number of RELEASE INDICATION messages ..................................34-10
C901280010 Number of UNIT DATA REQUEST messages ................................... 34-11
C901280011 Number of UNIT DATA INDICATION messages.................................34-12
C901280012 Number of CHANNEL ACTIVATION messages .................................34-13
C901280013 Number of CHANNEL ACTIVATION ACK messages .........................34-14
C901280014 Number of CHANNEL ACTIVATION Negative ACK messages ..........34-14
C901280015 Number of CONNECTION FAILURE INDICATION messages ...........34-15
C901280016 Number of DEACTIVATE SACCH messages.....................................34-16
C901280017 Number of ENCRYPTION COMMAND messages .............................34-17
C901280018 Number of HANDOVER DETECTION messages ..............................34-18
C901280019 Number of MEASUREMENT RESULT messages..............................34-19
C901280020 Number of MODE MODIFY REQUEST messages ............................34-20
C901280021 Number of MODE MODIFY ACK messages ......................................34-20
C901280022 Number of MODE MODIFY NACK messages ...................................34-21
C901280023 Number of PHYSICAL CONTEXT REQUEST messages ..................34-22
C901280024 Number of PHYSICAL CONTEXT CONFIRM messages ...................34-23
C901280025 Number of RF CHANNEL RELEASE messages................................34-24
C901280026 Number of MS POWER CONTROL messages..................................34-25
C901280027 Number of BS POWER CONTROL messages ..................................34-25
C901280028 Number of PREPROCESSED CONFIGURE messages ....................34-26
C901280029 Number of PREPROCESSED MEASUREMENT RESULT
messages...............................................................................................................34-27
C901280030 Number of RF CHANNEL RELEASE ACK messages........................34-28
C901280031 Number of SACCH INFO MODIFY messages ...................................34-29
34-1

C901280032 Number of ABIS_PREPROC_ENHANCEMEAS_RESULT

messages...............................................................................................................34-30
C901280033 Number of ABIS_ROUND_TRIP_DELAY_REPORT messages .........34-31
C901280034 Number of ABIS_PRE_HO_NOTIFY messages ................................34-31
C901280035 Number of ABIS_BCCH_INFO messages .........................................34-32
C901280036 Number of ABIS_CCCH_LOAD_IND messages................................34-33
C901280037 Number of ABIS_CHL_RQD messages.............................................34-34
C901280038 Number of ABIS_DELETE_IND messages........................................34-35
C901280039 Number of ABIS_PAGING_CMD messages ......................................34-35
C901280040 Number of ABIS_IMM_ASSIGN_CMD messages .............................34-36
C901280041 Number of ABIS_SMS_BROADCAST_REQ messages ....................34-37
C901280042 Number of ABIS_SMS_BROADCAST_CMD messages ....................34-38
C901280043 Number of ABIS_CBCH_LOAD_IND messages ................................34-39
C901280044 Number of ABIS_EGPRS_CHL_REQ messages...............................34-40
C901280045 Number of ABIS_LOAD_CONTROL messages.................................34-41
C901280046 Number of ABIS_END_LOAD_CONTROL messages .......................34-41
C901280047 Number of ABIS_END_LOAD_CONTROL_ACK messages ..............34-42
C901280048 Number of ABIS_PCCCH_LOAD_IND messages .............................34-43
C901280049 Number of ABIS_RF_RESRC_IND messages ..................................34-44
C901280050 Number of ABIS_SACCH_FILLING messages ..................................34-44
C901280051 Number of ABIS_OVERLOAD messages ..........................................34-45
C901280052 Number of ABIS_ERROR_REPORT messages ................................34-46
C901280053 Number of ABIS_SYSINFO_REQ messages ....................................34-47
C901280054 Number of ABIS_SI_BC_END messages ..........................................34-48
C901280055 Number of ABIS_SI_NACK messages ..............................................34-48
C901280056 Number of ABIS_PWRCTRL_IND messages ....................................34-49
C901280057 Number of ABIS_SYSINFO_ACK messages.....................................34-50
C901280061 Number of ABIS_PACKET_PBCCH_INF messages..........................34-51
C901280062 Number of ABIS_PACKET_CCCH_PARA messages ........................34-51
C901280063 Number of ABIS_PACKET_PBCCH_PARA messages ......................34-52
C901280064 Number of ABIS_PACKET_CHN_REQ messages.............................34-53
C901280065 Number of ABIS_PACKET_PAGING_CMD messages ......................34-54
C901280066 Number of ABIS_PACKET_IMM_ASSIGN_CMD messages..............34-55
C901280067 Number of ABIS_PACKET_CONNECT_FAIL_IND messages ...........34-55
C901280068 Number of ABIS_PACKET_PRACH_OVERLOAD messages ............34-56
C901280069 Number of ABIS_PACKET_PCH_OVERLOAD messages .................34-57
C901280070 Number of ABIS_PACKET_TA_REQUEST messages.......................34-58
C901280071 Number of ABIS_PACKET_TA_REQUEST_ACK messages .............34-58
C901280072 Number of ABIS_PACKET_CHN_CONFIG_CHG messages.............34-59
C901280073 Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages .34-60
C901280074 Number of ABIS_PACKET_PIA_DEL_IND messages .......................34-61
C901280075 Number of ABIS_PACKET_SEND_PIA_IND messages ....................34-62
C901280076 Number of ABIS_PACKET_CHN_CONFIG_REQ messages .............34-62
C901280077 Number of ABIS_EGPRS_PACKET_CHN_REQ messages ..............34-63
C901280078 Number of ABIS_PS_CHANNEL_ACTIVE messages .......................34-64
34-2

Chapter 34 Abis Interface Message Counter Measurement
C901280079 Number of ABIS_PS_CHANNEL_ACTIVE_ACK messages ..............34-65

C901280080 Number of ABIS_PS_CHANNEL_ACTIVE_NACK messages............34-66
C901280081 Number of ABIS_PS_CHANNEL_RELEASE messages ....................34-66
C901280082 Number of ABIS_PS_CHANNEL_RELEASE_ACK messages...........34-67
C901280083 Number of ABIS_PS_CHANNEL_RELEASE_NACK messages ........34-68
C901280084 Number of ABIS_PSCONN_CMM_REQ messages...........................34-69
C901280085 Number of ABIS_PSCONN_CMM_ACK messages ...........................34-70
C901280086 Number of ABIS_PSCONN_CMM_NACK messages ........................34-70
C901280087 Number of ABIS_GLOBAL_RESET messages..................................34-71
C901280088 Number of ABIS_GLOBAL_RESET_ACK messages.........................34-72
C901280089 Number of ABIS_GLOBAL_RESET_NACK messages ......................34-73
C901280090 Number of ABIS_PACKET_UP_ASSIGN messages..........................34-74
C901280091 Number of ABIS_PACKET_DOWN_ASSIGN messages ...................34-74
C901280092 Number of ABIS_CSCONN_CMM_REQ messages ..........................34-75
C901280093 Number of ABIS_CSCONN_CMM_ACK messages...........................34-76
C901280094 Number of ABIS_CSCONN_CMM_NACK messages ........................34-77
C901280095 Number of ABIS_CCMCONN_CMM_REQ messages .......................34-78
C901280096 Number of ABIS_CCMCONN_CMM_ACK messages........................34-78
C901280097 Number of ABIS_CCMCONN_CMM_NACK messages .....................34-79
C901280098 Number ABIS_PACKET_ACCESS_REJ messages...........................34-80
C901280099 Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages....34-81
C901280100 Number of PACKET_DOWNLINK_ASSIGN messages......................34-82
C901280101 Number of PACKET_UPLINK_ASSIGN messages............................34-82
C901280102 Number of ABIS_PACKET_ACCESS_REJ_NEW messages.............34-83
34.1 Overview
Abis interface message measurement is mainly for all kinds of messages of Abis interface
to count. It is convenient to find out the frequency of all kinds of messages transmitting
on Abis interface. When BSC receives the messages sent by BTS, the counter begin to
count. The measurement point is A, as shown in Figure 34-1.
Figure 34-1 BTS sends measurement point of Abis message to BSC
This counter accumulates before sending the message sent to BTS by BSC. The
34-3

Figure 34-2 Measurement Point when BSC Sends Abis Message to BTS
34.2 C901280001 Number of DATA REQUEST

messages
Definition
Number of DATA REQUEST messages
Description
This counter counts the number of data request messages to be confirmed sent by BSC
to LAPD.
Usage
This counter is used to find out the frequency of data request message to be confirmed
transmitting on Abis interface.
Measurement Point
This counter increments when BSC sends DATA REQuest message to BTS. The
Unit
Times
34-4

34.3 C901280002 Number of DATA INDICATION

messages
Definition
Number of DATA INDICATION messages
Description
This counter counts the number of data indication messages received by BSC on Abis
interface.
Usage
This counter is used to find out the frequency of data indication messages transmitting on
Abis interface.
Measurement Point
This counter increments when BSC receives DATA INDication message. The
Unit
Times
34.4 C901280003 Number of ERROR INDICATION

messages
Definition
Number of ERROR INDICATION messages
34-5

Description
When radio channel generates errors (for example radio link fault), BTS sends ERROR
INDication message to notify BSC. This counter counts the number of ERROR INDication
messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of error indication messages transmitting on
Abis interface.
Measurement Point
This counter increments when BSC receives ERROR INDication message. The
Unit
Times
34.5 C901280004 Number of 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 messages transmitting
on Abis interface.
34-6

Measurement Point
This counter increments when BSC sends Establish Request message to BTS. The
Unit
Times
34.6 C901280005 Number of 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 messages transmitting
on Abis interface.
Measurement Point
This counter increments when BSC receives Establish Confirm message. The
34-7

Unit
Times
34.7 C901280006 Number of ESTABLISH INDICATION

messages
Definition
Number of ESTABLISH INDICATION messages
Description
When MS receives assignment command (including immediate assignment) of BSC or
handover command, it sends SABM frame to network, BTS will send Establish Indication
messages to BSC after receiving. This counter counts the number of Establish Indication
Usage
This counter is used to find out the frequency of Establish Indication messages transmitting
on Abis interface.
Measurement Point
This counter increments when BSC receives Establish Indication message. The
34-8

Unit
Times
34.8 C901280007 Number of 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 messages transmitting
on Abis interface.
Measurement Point
This counter increments when BSC sends Release Request message to BTS. The
Unit
Times
34-9

34.9 C901280008 Number of 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
Usage
This counter is used to find out the frequency of Release Confirm messages transmitting
on Abis interface.
Measurement Point
This counter increments when BSC receives Release Confirm messages. The
Unit
Times
34.10 C901280009 Number of RELEASE INDICATION

messages
Definition
Number of RELEASE INDICATION messages
34-10

Description
When BTS receives one DISC frame sent by MS through one link layer of multi-frame
layer, BTS sends one Release Indication message to notify that link layer connection of
BSC radio interface is released. This counter counts the number of Release Indication
Usage
This counter is used to find out the frequency of Release Indication messages transmitting
on Abis interface.
Measurement Point
This counter increments when BSC receives Release Indication messages. The
Unit
Times
34.11 C901280010 Number of UNIT DATA REQUEST

messages
Definition
Number of UNIT DATA REQUEST messages
Description
BTS sends a UNIT DATA REQUEST message to BTS. The message includes complete
L3 message needed to send in uncertain mode. This counter counts the number of UNIT
DATA REQUEST messages sent by BSC to BTS.
Usage
This counter is used to find out the frequency of UNIT DATA REQUEST messages
34-11

Measurement Point
This counter increments when BSC sends UNIT DATA REQUEST messages to BTS. The
Unit
Times
34.12 C901280011 Number of UNIT DATA INDICATION

messages
Definition
Number of UNIT DATA INDICATION messages
Description
BTS sends a UNIT DATA INDICATION message to BTS. The message includes complete
L3 message needed to send in uncertain mode. This counter counts the number of UNIT
DATA INDICATION messages received by BSC.
Usage
This counter is used to find out the frequency of UNIT DATA INDICATION messages
Measurement Point
This counter increments when BSC receives UNIT DATA INDICATION messages. The
34-12

Unit
Times
34.13 C901280012 Number of 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 ACTIVATION messages sent by BSC to BTS.
Usage
This counter is used to find out the frequency of CHANNEL ACTIVATION messages
Measurement Point
This counter increments when BSC sends CHANNEL ACTIVATION messages. The
34-13

Unit
Times

ACK messages
Definition
Number of CHANNEL ACTIVATION ACK messages
Description
After BSC finishes activating channel, it sends CHANNEL ACTIVATION ACK message to
BSC as the response of channel activation message. This counter counts the number of
CHANNEL ACTIVATION ACK messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of CHANNEL ACTIVATION ACK messages
Measurement Point
This counter increments when BSC receives CHANNEL ACTIVATION ACK messages.
Unit
Times

Negative ACK messages
Definition
Number of CHANNEL ACTIVATION Negative ACK messages
34-14

Description
After BSC receives channel activation command, if it is impossible to finish channel
activation due to other reasons (for example TRX fault etc.), it sends CHANNEL
ACTIVATION Negative ACK message to BSC to notify that BSC channel activation fail.
This counter counts the number of CHANNEL ACTIVATION Negative ACK messages of
Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of CHANNEL ACTIVATION Negative ACK
messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives CHANNEL ACTIVATION Negative ACK
messages. The measurement point is A, as shown in Figure 34-16.
Unit
Times
34.16 C901280015 Number of 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 FAILURE INDICATION messages of Abis interface messages
received by BSC.
34-15

Usage
This counter is used to find out the frequency of CONNECTION FAILURE INDICATION
Measurement Point
This counter increments when BSC receives CONNECTION FAILURE INDICATION
Unit
Times
34.17 C901280016 Number of DEACTIVATE SACCH

messages
Definition
Number of DEACTIVATE SACCH messages
Description
When BSC activate SACCH due to certain reason (releasing radio channel), it sends
DEACTIVATE SACCH message to initiate to activate flow. This counter counts the number
of DEACTIVATE SACCH messages sent by BSC to LAPD.
Usage
This counter is used to find out the frequency of DEACTIVATE SACCH messages
Measurement Point
This counter increments when BSC receives DEACTIVATE SACCH messages. The
34-16

Unit
Times
34.18 C901280017 Number of ENCRYPTION COMMAND

messages
Definition
Number of ENCRYPTION COMMAND messages
Description
BSC initiate ENCRYPTION COMMAND message to require encryption. This counter
counts the number of ENCRYPTION COMMAND messages sent by BSC to LAPD.
Usage
This counter is used to find out the frequency of ENCRYPTION COMMAND messages
Measurement Point
This counter increments when BSC sends ENCRYPTION COMMAND messages to BTS.
34-17

Unit
Times
34.19 C901280018 Number of 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 HANDOVER DETCTION messages to notify BSC. This counter
counts the number of HANDOVER DETCTION messages of Abis interface messages
received by BSC.
Usage
This counter is used to find out the frequency of HANDOVER DETCTION messages
Measurement Point
This counter increments when BSC receives HANDOVER DETCTION messages. The
Unit
Times
34-18

34.20 C901280019 Number of MEASUREMENT RESULT

messages
Definition
Number of MEASUREMENT RESULT messages
Description
In general, MS reports a measurement report ( Um interface message MEASUREMENT
messages) to BTS per 102/104 multi-frame through SACCH channel, including DL
measurement information from 102/104 multi-frame. During the period BTS are also
under DL measurement. Therefore every 102/104 multi-frame, BTS will combine these
two information together, send to BSC through Abis message MEASUREMENT RESULT.
For some reasons, BTS does not receive the MS measurement report on time, only put
its UL measurement results into this MEASUREMENT RESULTS messages to send to
BSC. This counter counts the number of MEASUREMENT RESULTS messages of Abis
interface messages received by BSC.
Usage
This counter is used to find out the frequency of MEASUREMENT RESULTS messages
Measurement Point
This counter increments when BSC receives MEASUREMENT RESULTS messages. The
Unit
Times
34-19

34.21 C901280020 Number of MODE MODIFY REQUEST

messages
Definition
Number of MODE MODIFY REQUEST messages
Description
During the allocation or inner handover process, when the channel type of allocation and
current type are in agreement but the channel modes are different, BSC sends MODE
MODIFY REQUEST messages to BTS to notify to change channel mode. This counter
counts the number of MODE MODIFY REQUEST messages of Abis interface messages
sent by BSC.
Usage
This counter is used to find out the frequency of MODE MODIFY REQUEST messages
Measurement Point
This counter increments when BSC sends MODE MODIFY REQUEST messages to BTS.
Unit
Times
34.22 C901280021 Number of MODE MODIFY ACK

messages
Definition
Number of MODE MODIFY ACK messages
34-20

Description
After BTS receives MODE MODIFY ACK messages, finish channel mode change. Then
BTS sends MODE MODIFY ACK messages to BSC as reply. This counter counts the
number of MODE MODIFY ACK messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of MODE MODIFY ACK messages
Measurement Point
This counter increments when BSC receives MODE MODIFY ACK messages. The
Unit
Times
34.23 C901280022 Number of MODE MODIFY NACK

messages
Definition
Number of MODE MODIFY NACK messages
Description
After BTS receives MODE MODIFY REQUEST messages, it is impossible to finish channel
mode change due to certain reason, it will send MODE MODIFY NACK messages to BSC
as reply. This counter counts the number of MODE MODIFY NACK messages of Abis
Usage
This counter is used to find out the frequency of MODE MODIFY NACK messages
34-21

Measurement Point
This counter increments when BSC receives MODE MODIFY NACK messages. The
Unit
Times
34.24 C901280023 Number of PHYSICAL CONTEXT

REQUEST messages
Definition
Number of PHYSICAL CONTEXT REQUEST messages
Description
When BSC needs to know the current channel of MS (physical context), it sends
PHYSICAL CONTEXT REQUEST messages to BTS to apply. This counter counts the
number of PHYSICAL CONTEXT REQUEST messages of Abis interface messages sent
by BSC.
Usage
This counter is used to find out the frequency of PHYSICAL CONTEXT REQUEST
Measurement Point
This counter increments when BSC sends PHYSICAL CONTEXT REQUEST messages
to BTS. The measurement point is A, as shown in Figure 34-25.
34-22

Unit
Times
34.25 C901280024 Number of PHYSICAL CONTEXT

CONFIRM messages
Definition
Number of PHYSICAL CONTEXT CONFIRM messages
Description
After BTS receives PHYSICAL CONTEXT REQUEST messages, report to BSC about
related physical context through PHYSICAL CONTEXT COMFIRM messages. This
counter counts the number of PHYSICAL CONTEXT COMFIRM messages of Abis
Usage
This counter is used to find out the frequency of PHYSICAL CONTEXT COMFIRM
Measurement Point
This counter increments when BSC receives PHYSICAL CONTEXT COMFIRM messages
34-23

Unit
Times
34.26 C901280025 Number of RF CHANNEL RELEASE

messages
Definition
Number of RF CHANNEL RELEASE messages
Description
When the certain logical channel is not used, BSC needs to notify BTS to release the
channel. Therefore it sends RF CHANNEL RELEASE messages to BTS. This counter
counts the number of RF CHANNEL RELEASE messages of Abis interface messages
received by BSC.
Usage
This counter is used to find out the frequency of RF CHANNEL RELEASE messages
Measurement Point
This counter increments when BSC sends RF CHANNEL RELEASE messages to BTS.
Unit
Times
34-24

34.27 C901280026 Number of MS POWER CONTROL

messages
Definition
Number of MS POWER CONTROL messages
Description
BSC can calculate the proper transmitting power used by MS according to measurement
data result. Therefore it notify control parameters to BTS through MS POWER CONTROL
messages. BTS sends the information to MS through L1 frame header of SACCH, then
finish MS POWER CONTROL ultimately. This counter counts the number of MS POWER
CONTROL messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of MS POWER CONTROL messages
Measurement Point
This counter increments when BSC sends MS POWER CONTROL messages to BTS. The
Unit
Times
34.28 C901280027 Number of BS POWER CONTROL

messages
Definition
Number of BS POWER CONTROL messages
34-25

Description
BSC can calculate the proper transmitting power used by BTS side according to
measurement data result. Therefore it notifies control parameters to BTS through BS
POWER CONTROL messages. BTS conducts the corresponding transmission power
adjustment work immediately. This counter counts the number of BS POWER CONTROL
messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of BS POWER CONTROL messages
Measurement Point
This counter increments when BSC sends BS POWER CONTROL messages to BTS. The
Unit
Times
34.29 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 preprocessed 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
34-26

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
Measurement Point
This counter increments when BSC sends PREPROCESSED CONFIGURE messages to
BTS. The measurement point is A, as shown in Figure 34-30.
Unit
Times
34.30 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 preprocessed result to BSC through
PREPROCESSED MEASUREMENT RESULT messages. This counter counts the
number of PREPROCESSED MEASUREMENT RESULT messages of Abis interface
messages received by BSC.
Usage
This counter is used to find out the frequency of PREPROCESSED MEASUREMENT
RESULT messages transmitting on Abis interface.
34-27

Measurement Point
This counter increments when BSC receives PREPROCESSED MEASUREMENT
RESULT messages to BTS. The measurement point is A, as shown in Figure 34-31.
Unit
Times
34.31 C901280030 Number of RF CHANNEL RELEASE

ACK messages
Definition
Number of RF CHANNEL RELEASE ACK messages
Description
After BTS receives RF CHANNEL RELEASE messages and releases this channel, returns
one RF CHANNEL RELEASE ACK messages to BSC. This counter counts the number of
RF CHANNEL RELEASE ACK messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of RF CHANNEL RELEASE ACK messages
Measurement Point
This counter increments when BSC receives RF CHANNEL RELEASE ACK messages to
34-28

Unit
Times
34.32 C901280031 Number of SACCH INFO MODIFY

messages
Definition
Number of SACCH INFO MODIFY messages
Description
On the DL direction of SACCH, BTS will send RR message SI5/5bis/5ter/6 of Um
interface to MS repeatedly, besides informing power control parameters and the latest
time advance of L1 frame header to MS. When BSC want to modify related message on
one SACCH, send one SACCH INFO MODIFY messages to BTS. The message includes
RR message SI5/5bis/5ter/6 of new Um interface. This counter counts the number of
SACCH INFO MODIFY messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of SACCH INFO MODIFY messages
Measurement Point
This counter increments when BSC sends SACCH INFO MODIFY messages to BTS. The
34-29

Unit
Times
34.33 C901280032 Number of ABIS_PREPROC_ENHAN

CEMEAS_RESULT messages
Definition
Number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages
Description
This counter counts the number of ABIS_PREPROC_ENHANCEMEAS_RESULT
Usage
This counter is used to find out the frequency of enhanced preprocessed measurement
report message transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives
ABIS_PREPROC_ENHANCEMEAS_RESULT messages. The measurement point is A,
34-30

Unit
Times
34.34 C901280033 Number of ABIS_ROUND_TRIP_DEL

AY_REPORT messages
Definition
Number of ABIS_ROUND_TRIP_DELAY_REPORT messages
Description
This counter counts the number of ABIS_ROUND_TRIP_DELAY_REPORT messages
received by BSC.
Usage
This counter is used to find out the frequency of ROUND TRIP DELAY REPORT messages
Measurement Point
This counter increments when BSC receives ROUND TRIP DELAY REPORT messages.
Unit
Times
34.35 C901280034 Number of ABIS_PRE_HO_NOTIFY

messages
Definition
Number of ABIS_PRE_HO_NOTIFY messages
34-31

Description
This counter counts the number of ABIS_PRE_HO_NOTIFY messages received by BSC.
Usage
This counter is used to find out the frequency of PRE_HO_NOTIFY messages transmitting
on Abis interface.
Measurement Point
This counter increments when BSC sends PRE-HANDOVER NOFICATION messages.
Unit
Times
34.36 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 messages transmitting
on Abis interface.
34-32

Measurement Point
This counter increments when BSC sends BCCH INFOMATION messages. The
Unit
Times
34.37 C901280036 Number of ABIS_CCCH_LOAD_IND

messages
Definition
Number of ABIS_CCCH_LOAD_IND messages
Description
When BSC checks one CCCH overload, it needs to send one CCCH LOAD INDICATION
message to BSC periodically to notify BSC. This counter counts the number of
ABIS_CCCH_LOAD_IND messages received by BSC.
Usage
This counter is used to find out the frequency of CCCH load indication messages
Measurement Point
This counter increments when BSC receives CCCH LOAD INDICATION messages. The
34-33

Unit
Times
34.38 C901280037 Number of 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 messages transmitting on
Abis interface.
Measurement Point
This counter increments when BSC receives CHANNEL REQUIRED messages. The
34-34

Unit
Times
34.39 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 INDICATION message to notify BSC. This counter
counts the number of ABIS_DELETE_IND messages received by BSC.
Usage
This counter is used to find out the frequency of DELETE INDICATION messages
Measurement Point
This counter increments when BSC receives DELETE INDICATION messages. The
Unit
Times
34.40 C901280039 Number of ABIS_PAGING_CMD

messages
Definition
Number of ABIS_PAGING_CMD messages
34-35

Description
When BSC receives PADING message of BSSMAP protocol sent by MSC from A-interface,
it sends one PAGING COMMAND message to BTS, including MS identity (TMSI or IMSI).
BTS sends to MS on PCH of radio interface through PAGING REQUEST. This counter
counts the number of ABIS_PAGING_CMD messages sent by BSC.
Usage
This counter is used to find out the frequency of PAGING COMMAND messages
Measurement Point
This counter increments when BSC sends PAGING COMMAND messages to BTS. The
Unit
Times
Related Features
34.41 C901280040 Number of 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 IMMEDIATE ASSIGN COMMAND message to BTS.
34-36

This message includes one complete Um interface RR layer IMMEDIATE ASSIGNMENT

or IMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENT REJECT (if
there is no channel) to notify MS.
After BTS receives this message, it is in charge of assigning Um interface RR layer
message of the message on CCCH to MS. This counter counts the number of
ABIS_IMM_ASSIGN_CMD messages sent by BSC.
Usage
This counter is used to find out the frequency of IMMEDIATE ASSIGN COMMAND
Measurement Point
This counter increments when BSC sends IMMEDIATE ASSIGN COMMAND messages
Unit
Times
34.42 C901280041 Number of ABIS_SMS_BROADCAS

T_REQ messages
Definition
Number of ABIS_SMS_BROADCAST_REQ messages
Description
This counter counts the number of ABIS_SMS_BROADCAST_REQ messages sent by
BSC.
Usage
This counter is used to find out the frequency of SMS BROADCAST REQUEST messages
34-37

Measurement Point
This counter increments when BSC sends SMS BROADCAST REQUEST messages to
Unit
Times
Related Features
ZGO-01-03-004 Cell Broadcast SMS
34.43 C901280042 Number of ABIS_SMS_BROADCAS

T_CMD messages
Definition
Number of ABIS_SMS_BROADCAST_CMD messages
Description
This counter counts the number of ABIS_SMS_BROADCAST_CMD messages sent by
BSC.
Usage
This counter is used to find out the frequency of SMS BROADCAST COMMAND messages
Measurement Point
This counter increments when BSC sends MS BROADCAST COMMAND messages to
34-38

Unit
Times
Related Features
ZGO-01-03-004 Cell Broadcast SMS
34.44 C901280043 Number of 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
Usage
This counter is used to find out the frequency of CBCH LOAD INDICATION messages
Measurement Point
This counter increments when BSC receives CBCH LOAD INDICATION messages to BTS.
34-39

Unit
Times
34.45 C901280044 Number of ABIS_EGPRS_CHL_REQ

messages
Definition
Number of ABIS_EGPRS_CHL_REQ messages
Description
This counter counts the number of ABIS_EGPRS_CHL_REQ messages sent by BSC.
Usage
This counter is used to find out the frequency of EGPRS_CHL_REQ messages transmitting
on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_EGPRS_CHL_REQ messages. The
Unit
Times
34-40

34.46 C901280045 Number of ABIS_LOAD_CONTROL

messages
Definition
Number of ABIS_LOAD_CONTROL messages
Description
When BTS checks one CCCH overload, it needs to send CCCHLOAD INDICATION
message periodically to inform BSC. This counter counts the number of
ABIS_LOAD_CONTROL messages receives by BSC.
Usage
This counter is used to find out the frequency of CCCHLOAD INDICATION messages
Measurement Point
This counter increments when BSC receives CCCHLOAD INDICATION messages. The
Unit
Times
34.47 C901280046 Number of ABIS_END_LOAD_CO

NTROL messages
Definition
Number of ABIS_END_LOAD_CONTROL messages
Description
This counter counts the number of ABIS_END_LOAD_CONTROL messages sent by BSC.
34-41

Usage
This counter is used to find out the frequency of END LOAD CONTROL messages
Measurement Point
This counter increments when BSC sends ABIS_END_LOAD_CONTROL messages to
Unit
Times
34.48 C901280047 Number of ABIS_END_LOAD_CO

NTROL_ACK messages
Definition
Number of ABIS_END_LOAD_CONTROL_ACK messages
Description
This counter counts the number of ABIS_END_LOAD_CONTROL_ACK messages
received by BSC.
Usage
This counter is used to find out the frequency of END LOAD CONTROL RETURN
Measurement Point
This counter increments when BSC receives ABIS_END_LOAD_CONTROL_ACK
messages to BTS. The measurement point is A, as shown in Figure 34-49.
34-42

Unit
Times
34.49 C901280048 Number of ABIS_PCCCH_LOAD_IND

messages
Definition
Number of ABIS_PCCCH_LOAD_IND messages
Description
This counter counts the number of PCCH flow control control command messages of Abis
Usage
This counter is used to find out the frequency of PCCH flow control control command
Measurement Point
This counter increments when BSC receives ABIS_PCCCH_LOAD_CONTROL_IND
34-43

Unit
Times
34.50 C901280049 Number of ABIS_RF_RESRC_IND

messages
Definition
Number of ABIS_RF_RESRC_IND messages
Description
BTS sends RF RESOURCE INDICATION messages periodically to inform BSC of
interference on idle channel belonging to one TRX. This counter counts the number of
ABIS_RF_RESRC_ IND messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of RF RESOURCE INDICATION messages
Measurement Point
This counter increments when BSC receives RF RESOURCE INDICATION messages.
Unit
Times
34.51 C901280050 Number of ABIS_SACCH_FILLING

messages
Definition
Number of ABIS_SACCH_FILLING messages
34-44

Description
When BSC modifies SI1/5bis/6/EXTENDED MEASUREMENT ORDER message sent on
SACCH, it sends one SACCH FILLING message to BTS. This counter counts the number
of SACCH FILLING INFORMATION CHANGE messages of Abis interface messages sent
by BSC.
Usage
This counter is used to find out the frequency of SACCH FILLING INFORMATION
CHANGE messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC sends SACCH FILLING messages. The measurement
Unit
Times
34.52 C901280051 Number of ABIS_OVERLOAD

messages
Definition
Number of ABIS_OVERLOAD messages
Description
This counter counts the number of flow control messages of Abis interface messages
received by BSC.
Usage
This counter is used to find out the frequency of flow control messages transmitting on
Abis interface.
34-45

Measurement Point
This counter increments when BSC receives overload messages. The measurement point
Unit
Times
34.53 C901280052 Number of 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 messages received by BSC.
Usage
This counter is used to find out the frequency of error report messages transmitting on
Abis interface.
Measurement Point
This counter increments when BSC receives error report messages. The measurement
34-46

Unit
Times
34.54 C901280053 Number of 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 information requirement
Measurement Point
This counter increments when BSC receives ABIS_SYSINFO_REQ messages. The
Unit
Times
34-47

34.55 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 messages sent by BSC.
Usage
This counter is used to find out the frequency of systems information broadcast end
indication messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC sends ABIS_SI_BC_END messages to BTS. The
Unit
Times
34.56 C901280055 Number of ABIS_SI_NACK

messages
Definition
Number of ABIS_SI_NACK messages
Description
This counter counts the number of ABIS_SI_NACK messages received by BSC.
34-48

Usage
This counter is used to find out the frequency of SI_NACK messages transmitting on Abis
interface.
Measurement Point
This counter increments when BSC receives ABIS_SI_NACK messages to BTS. The
Unit
Times
34.57 C901280056 Number of 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
Measurement Point
This counter increments when BSC receives ABIS_PWRCTRL_IND messages. The
34-49

Unit
Times
34.58 C901280057 Number of ABIS_SYSINFO_ACK

messages
Definition
Number of ABIS_SYSINFO_ACK messages
Description
This counter counts the number of ABIS_SYSINFO_ACK messages received by BSC.
Usage
This counter is used to find out the frequency of SYSTEM INFORMATION
ACKNOWLEDGE messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_SYSINFO_ACK messages. The
Unit
Times
34-50

34.59 C901280061 Number of ABIS_PACKET_PBCCH_I

NF messages
Definition
Number of ABIS_PACKET_PBCCH_INF messages
Description
This counter counts the number of ABIS_PACKET_PBCCH_INF messages received by
BSC.
Usage
This counter is used to find out the frequency of PACKET PBCCH INFORMATION
Measurement Point
This counter increments when BSC sends ABIS_PACKET_PBCCH_INF messages. The
Unit
Times
34.60 C901280062 Number of ABIS_PACKET_CCCH

_PARA messages
Definition
Number of ABIS_PACKET_CCCH_PARA messages
Description
This counter counts the number of ABIS_PACKET_CCCH_PARA messages sent by BSC.
34-51

Usage
This counter is used to find out the frequency of CCCH INFORMATION messages
Measurement Point
This counter increments when BSC sends ABIS_PACKET_CCCH_PARA messages. The
Unit
Times
34.61 C901280063 Number of ABIS_PACKET_PBCCH

_PARA messages
Definition
Number of ABIS_PACKET_PBCCH_PARA messages
Description
This counter counts the number of ABIS_PACKET_PBCCH_PARA messages sent by
BSC.
Usage
This counter is used to find out the frequency of PBCCH PATAMETER messages
Measurement Point
This counter increments when BSC sends ABIS_PACKET_PBCCH_PARA messages to
34-52

Unit
Times
34.62 C901280064 Number of ABIS_PACKET_CHN_R

EQ messages
Definition
Number of ABIS_PACKET_CHN_REQ messages
Description
This counter counts the number of ABIS_PACKET_CHN_REQ messages received by
BSC.
Usage
This counter is used to find out the frequency of UL PACKET CHANNEL REQUIREMENT
Measurement Point
This counter increments when BSC receives ABIS_PACKET_CHN_REQ messages to
34-53

Unit
Times
34.63 C901280065 Number of ABIS_PACKET_PAGIN

G_CMD messages
Definition
Number of ABIS_PACKET_PAGING_CMD messages
Description
This counter counts the number of ABIS_PACKET_PAGING_CMD messages received by
BSC.
Usage
This counter is used to find out the frequency of PACKET PAGING COMMAND messages
Measurement Point
This counter increments when BSC sends ABIS_PACKET_PAGING_CMD messages to
Unit
Times
Related Features
34-54

34.64 C901280066 Number of ABIS_PACKET_IMM_A

SSIGN_CMD messages
Definition
Number of ABIS_PACKET_IMM_ASSIGN_CMD messages
Description
This counter counts the number of PACKET IMMEDIATE ASSIGNMENT messages of Abis
interface messages sent by BSC.
Usage
This counter is used to find out the frequency of PACKET IMMEDIATE ASSIGNMENT
Measurement Point
This counter increments when BSC sends ABIS_PACKET_IMM_ASSIGN_CMD
Unit
Times
34.65 C901280067 Number of ABIS_PACKET_CONNEC

T_FAIL_IND messages
Definition
Number of ABIS_PACKET_CONNECT_FAIL_IND messages
Description
This counter counts the number of PACKET CONNECT FAILURE INDICATION messages
of Abis interface messages received by BSC.
34-55

Usage
This counter is used to find out the frequency of PACKET CONNECT FAILURE
INDICATION messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_PACKET_CONNECT_FAIL_IND
Unit
Times
34.66 C901280068 Number of ABIS_PACKET_PRACH_

OVERLOAD messages
Definition
Number of ABIS_PACKET_PRACH_OVERLOAD messages
Description
This counter counts the number of PRACH OVERLOAD messages of Abis interface
Usage
This counter is used to find out the frequency of PRACH OVERLOAD messages
Measurement Point
This counter increments when BSC receives ABIS_PACKET_PRACH_OVERLOAD
34-56

Unit
Times
34.67 C901280069 Number of ABIS_PACKET_PCH_OV

ERLOAD messages
Definition
Number of ABIS_PACKET_PCH_OVERLOAD messages
Description
This counter counts the number of PCH OVERLOAD messages of Abis interface
Usage
This counter is used to find out the frequency of PCH OVERLOAD messages transmitting
on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_PACKET_PCH_OVERLOAD
34-57

Unit
Times
34.68 C901280070 Number of ABIS_PACKET_TA_RE

QUEST messages
Definition
Number of ABIS_PACKET_TA_REQUEST messages
Description
This counter counts the number of TIME ADVANCE REQUEST messages of Abis interface
Usage
This counter is used to find out the frequency of TIME ADVANCE REQUEST messages
Measurement Point
This counter increments when BSC sends ABIS_PACKET_TA_REQUEST messages.
Unit
Times
34.69 C901280071 Number of ABIS_PACKET_TA_RE

QUEST_ACK messages
Definition
Number of ABIS_PACKET_TA_REQUEST_ACK messages
34-58

Description
This counter counts the number of TIME ADVANCE REQUEST ACKNOWLEDGE
Usage
This counter is used to find out the frequency of TIME ADVANCE REQUEST
ACKNOWLEDGE messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_PACKET_TA_REQUEST_ACK
Unit
Times
34.70 C901280072 Number of ABIS_PACKET_CHN_C

ONFIG_CHG messages
Definition
Number of ABIS_PACKET_CHN_CONFIG_CHG messages
Description
This counter counts the number of CHANNEL CONFIGURATION CHANGE messages of
Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of CHANNEL CONFIGURATION CHANGE
34-59

Measurement Point
This counter increments when BSC sends ABIS_PACKET_CHG_CONFIG_CHG
Unit
Times
34.71 C901280073 Number of ABIS_PACKET_CHN_CO

NFIG_CHG_RESP messages
Definition
Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages
Description
This counter counts the number of CHANNEL CONFIGURATION CHANGE RESPONSE
Usage
This counter is used to find out the frequency of CHANNEL CONFIGURATION CHANGE
RESPONSE messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives
ABIS_PACKET_CHG_CONFIG_CHG_RESP messages. The measurement point is A,
34-60

Unit
Times
34.72 C901280074 Number of ABIS_PACKET_PIA_D

EL_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 messages received by BSC.
Usage
This counter is used to find out the frequency of IMMEDIATE ASSIGNMENT
TRANSMISSION FAILURE INDICATION messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_PACKET_PIA_DEL_IND messages.
34-61

Unit
Times
34.73 C901280075 Number of ABIS_PACKET_SEND_P

IA_IND messages
Definition
Number of ABIS_PACKET_SEND_PIA_IND messages
Description
This counter counts the number of IMMEDIATE ASSIGNMENT TRANSMISSION
SUCCESS INDICATION messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of IMMEDIATE ASSIGNMENT
TRANSMISSION SUCCESS INDICATION messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_PACKET_SEND_PIA_IND messages.
Unit
Times
34.74 C901280076 Number of ABIS_PACKET_CHN_C

ONFIG_REQ messages
Definition
Number of ABIS_PACKET_CHN_CONFIG_REQ messages
34-62

Description
This counter counts the number of PS PARAMETER CONFIGURATION REQUEST
Usage
This counter is used to find out the frequency of PS PARAMETER CONFIGURATION
REQUEST messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_PACKET_CHN_CONFIG_REQ
Unit
Times
34.75 C901280077 Number of ABIS_EGPRS_PACKE

T_CHN_REQ messages
Definition
Number of ABIS_EGPRS_PACKET_CHN_REQ messages
Description
This counter counts the number of UL EGPRS PACKET REQUEST messages of Abis
Usage
This counter is used to find out the frequency of UL EGPRS PACKET REQUEST messages
34-63

Measurement Point
This counter increments when BSC receives ABIS_EGPRS_PACKET _CHN_REQ
Unit
Times
34.76 C901280078 Number of ABIS_PS_CHANNEL_AC

TIVE messages
Definition
Number of ABIS_PS_CHANNEL_ACTIVE messages
Description
This counter counts the number of PS CHANNEL ACTIVE COMMAND messages of Abis
Usage
This counter is used to find out the frequency of PS CHANNEL ACTIVE COMMAND
Measurement Point
This counter increments when BSC sends ABIS_PS_CHANNEL _ACTIVE messages. The
34-64

Unit
Times
34.77 C901280079 Number of ABIS_PS_CHANNEL_A

CTIVE_ACK messages
Definition
Number of ABIS_PS_CHANNEL_ACTIVE_ACK messages
Description
This counter counts the number of PS CHANNEL ACTIVE ACKNOWLEDGEMENT
COMMAND messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of PS CHANNEL ACTIVE
ACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_PS_CHANNEL _ACTIVE_ACK
34-65

Unit
Times
34.78 C901280080 Number of ABIS_PS_CHANNEL_AC

TIVE_NACK messages
Definition
Number of ABIS_PS_CHANNEL_ACTIVE_NACK messages
Description
This counter counts the number of PS CHANNEL ACTIVE UNACKNOWLEDGEMENT
COMMAND messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of PS CHANNEL ACTIVE
UNACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_PS_CHANNEL _ACTIVE_NACK
Unit
Times
34.79 C901280081 Number of ABIS_PS_CHANNEL_RE

LEASE messages
Definition
Number of ABIS_PS_CHANNEL_RELEASE messages
34-66

Description
This counter counts the number of PS CHANNEL RELEASE COMMAND messages of
Usage
This counter is used to find out the frequency of PS CHANNEL RELEASE COMMAND
Measurement Point
This counter increments when BSC sends ABIS_PS_CHANNEL_RELEASE messages to
Unit
Times

LEASE_ACK messages
Definition
Number of ABIS_PS_CHANNEL_RELEASE_ACK messages
Description
This counter counts the number of PS CHANNEL RELEASE ACKNOWLEDGEMENT
Usage
This counter is used to find out the frequency of PS CHANNEL RELEASE
ACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface.
34-67

Measurement Point
This counter increments when BSC receives ABIS_PS_CHANNEL_RELEASE_ACK
Unit
Times

LEASE_NACK messages
Definition
Number of ABIS_PS_CHANNEL_RELEASE_NACK messages
Description
This counter counts the number of PS CHANNEL RELEASE UNACKNOWLEDGEMENT
Usage
This counter is used to find out the frequency of PS CHANNEL RELEASE
Measurement Point
This counter increments when BSC receives ABIS_PS_CHANNEL_RELEASE_NACK
34-68

Unit
Times
34.82 C901280084 Number of ABIS_PSCONN_CMM_R

EQ messages
Definition
Number of ABIS_PSCONN_CMM_REQ messages
Description
This counter counts the number of PS CONNECTION COMMAND messages of Abis
Usage
This counter is used to find out the frequency of PS CONNECTION COMMAND messages
Measurement Point
This counter increments when BSC sends ABIS_PSCONN_CMM_REQ messages to BTS.
34-69

Unit
Times
34.83 C901280085 Number of ABIS_PSCONN_CMM_A

CK messages
Definition
Number of ABIS_PSCONN_CMM_ACK messages
Description
This counter counts the number of PS CONNECTION SUCCESS COMMAND
ACKNOWLEDGEMENT messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of PS CONNECTION SUCCESS COMMAND
ACKNOWLEDGEMENT messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_PSCONN_CMM_ACK messages. The
Unit
Times
34.84 C901280086 Number of ABIS_PSCONN_CMM_N

ACK messages
Definition
Number of ABIS_PSCONN_CMM_NACK messages
34-70

Description
This counter counts the number of PS CONNECTION FAILURE COMMAND
ACKNOWLEDGEMENT messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of PS CONNECTION FAILURE COMMAND
Measurement Point
This counter increments when BSC receives ABIS_PSCONN_CMM_NACK messages.
Unit
Times
34.85 C901280087 Number of ABIS_GLOBAL_RESET

messages
Definition
Number of ABIS_GLOBAL_RESET messages
Description
This counter counts the number of GLOBAL RESET COMMAND messages of Abis
Usage
This counter is used to find out the frequency of GLOBAL RESET COMMAND messages
34-71

Measurement Point
This counter increments when BSC sends ABIS_GLOBAL_RESET messages to BTS. The
Unit
Times
34.86 C901280088 Number of ABIS_GLOBAL_RESE

T_ACK messages
Definition
Number of ABIS_GLOBAL_RESET_ACK messages
Description
This counter counts the number of GLOBAL RESET ACKNOWLEDGEMENT COMMAND
messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of GLOBAL RESET ACKNOWLEDGEMENT
COMMAND messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_GLOBAL_RESET_ACK messages.
34-72

Unit
Times
34.87 C901280089 Number of ABIS_GLOBAL_RESET

_NACK messages
Definition
Number of ABIS_GLOBAL_RESET_NACK messages
Description
This counter counts the number of GLOBAL RESET UNACKNOWLEDGEMENT
COMMAND messages of Abis interface messages sent by BSC.
Usage
This counter is used to find out the frequency of GLOBAL RESET
Measurement Point
This counter increments when BSC receives ABIS_GLOBAL_RESET_NACK messages.
34-73

Unit
Times
34.88 C901280090 Number of ABIS_PACKET_UP_ASSI

GN messages
Definition
Number of ABIS_PACKET_UP_ASSIGN messages
Description
This counter counts the number of PS UL ASSIGNMENT COMMAND messages of Abis
Usage
This counter is used to find out the frequency of PS UL ASSIGNMENT COMMAND
Measurement Point
This counter increments when BSC sends ABIS_PACKET_UP_ASSIGN messages to
Unit
Times
34.89 C901280091 Number of ABIS_PACKET_DOWN_

ASSIGN messages
Definition
Number of ABIS_PACKET_DOWN_ASSIGN messages
34-74

Description
This counter counts the number of PS DL ASSIGNMENT COMMAND messages of Abis
Usage
This counter is used to find out the frequency of PS DL ASSIGNMENT COMMAND
Measurement Point
This counter increments when BSC sends ABIS_PACKET_DOWN_ASSIGN messages to
Unit
Times
34.90 C901280092 Number of ABIS_CSCONN_CMM_R

EQ messages
Definition
Number of ABIS_CSCONN_CMM_REQ messages
Description
This counter counts the number of CS CONNECTION COMMAND messages of Abis
Usage
This counter is used to find out the frequency of CS CONNECTION COMMAND messages
34-75

Measurement Point
This counter increments when BSC sends ABIS_CSCONN_CMM_REQ messages to
Unit
Times
34.91 C901280093 Number of ABIS_CSCONN_CMM_A

CK messages
Definition
Number of ABIS_CSCONN_CMM_ACK messages
Description
This counter counts the number of CS CONNECTION SUCCESS COMMAND
ACKNOWLEDGEMENT messages of Abis interface messages received by BSC.
Usage
This counter is used to find out the frequency of CS CONNECTION SUCCESS COMMAND
Measurement Point
This counter increments when BSC receives ABIS_CSCONN_CMM_ACK messages. The
34-76

Unit
Times
34.92 C901280094 Number of 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
Usage
This counter is used to find out the frequency of CS CONNECTION FAILURE COMMAND
Measurement Point
This counter increments when BSC receives ABIS_CSCONN_CMM_NACK messages.
34-77

Unit
Times
34.93 C901280095 Number of ABIS_CCMCONN_CMM_

REQ messages
Definition
Number of ABIS_CCMCONN_CMM_REQ messages
Description
This counter counts the number of CCM CONNECTION COMMAND messages of Abis
Usage
This counter is used to find out the frequency of CCM CONNECTION COMMAND
Measurement Point
This counter increments when BSC sends ABIS_CCMCONN_CMM_REQ messages to
Unit
Times
34.94 C901280096 Number of ABIS_CCMCONN_CMM_

ACK messages
Definition
Number of ABIS_CCMCONN_CMM_ACK messages
34-78

Description
This counter counts the number of CCM CONNECTION SUCCESS COMMAND
Usage
This counter is used to find out the frequency of CCM CONNECTION SUCCESS
COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface.
Measurement Point
This counter increments when BSC receives ABIS_CCMCONN_CMM_ACK messages.
Unit
Times
34.95 C901280097 Number of ABIS_CCMCONN_CMM

_NACK messages
Definition
Number of ABIS_CCMCONN_CMM_NACK messages
Description
This counter counts the number of CCM CONNECTION FAILURE COMMAND
Usage
This counter is used to find out the frequency of CCM CONNECTION FAILURE
COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface.
34-79

Measurement Point
This counter increments when BSC receives ABIS_CCMCONN_CMM_NACK messages.
Unit
Times
34.96 C901280098 Number ABIS_PACKET_ACCESS_R

EJ messages
Definition
Number ABIS_PACKET_ACCESS_REJ messages
Description
This counter counts the number of PS ACCESS REJECT messages of Abis interface
Usage
This counter is used to find out the frequency of PS ACCESS REJECT messages
Measurement Point
This counter increments when BSC sends ABIS_PACKET_ACCESS_REJ messages to
BSC. The measurement point is A, as shown in Figure 34-97.
34-80

Unit
Times
34.97 C901280099 Number of ABIS_PACKET_IMM_AS

SIGN_CMD_NEW messages
Definition
Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages
Description
This counter counts the number of new packet immediate assignment messages in the
Usage
The counter is used to find out the frequency of new packet immediate assignment
messages transmitted at Abis interface.
Measurement Point
When BSC sends the ABIS_PACKET_IMM_ASSIGN_CMD_NEW message to BTS, the
34-81

Unit
Times
34.98 C901280100 Number of PACKET_DOWNLINK_

ASSIGN messages
Definition
Number of PACKET_DOWNLINK_ASSIGN messages
Description
This counter counts the number of packet downlink assignment messages in the Abis
Usage
The counter is used to find out the frequency of packet downlink assignment messages
transmitted at Abis interface.
Measurement Point
When BSC sends the PACKET_DOWNLINK_ASSIGN message to BTS, the counter
Unit
Times
34.99 C901280101 Number of PACKET_UPLINK_ASSI

GN messages
Definition
Number of PACKET_UPLINK_ASSIGN messages
34-82

Description
This counter counts the number of packet uplink assignment messages in the Abis
Usage
The counter is used to find out the frequency of packet uplink assignment messages
Measurement Point
When BSC sends the PACKET_UPLINK_ASSIGN message to BTS, the counter
Unit
Times
34.100 C901280102 Number of ABIS_PACKET_ACCES

S_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
Usage
The counter is used to find out the frequency of new PS access reject messages
34-83

Measurement Point
When BSC sends the ABIS_PACKET_ACCESS_REJ_NEW message to BTS, the counter
Unit
Times
34-84

Chapter 35
Gb Message Statistics (BVC
Cell)
Table of Contents
Overview ..................................................................................................................35-2
C901290003 Number of RA-CAPABILITY message received...................................35-4
C901290008 Number of Wireless Status PDU messages sent by BSC ....................35-7
C901290009 Number of Wireless Status messages sent by BSC due to Losing
Wireless Association with MS...................................................................................35-8
C901290010 Number of wireless status messages sent by BSC due to Bad Link
Quality......................................................................................................................35-9
C901290011 Number of Wireless status messages sent by BSC due to Cell
reselection command ...............................................................................................35-9
C901290012 Number of FLOW-CONTROL-BVC messages sent by BSC ..............35-10
C901290013 Number of FLOW-CONTROL-BVC-ACK messages received by
BSC .......................................................................................................................35-10
C901290014 Number of FLOW-CONTROL-MS messages sent by BSC ................ 35-11
C901290015 Number of FLOW-CONTROL-MS-ACK messages received by BSC .35-12
BSC .......................................................................................................................35-13
C901290018 Number of Status messages sent by BSC .........................................35-14
C901290019 Number of Status messages received by BSC ..................................35-15
C901290020 Number of Status messages sent with BVCI Unknown......................35-15
C901290021 Number of Status messages sent with Cell service congestion..........35-16
C901290022 Number of Status messages sent with protocol error.........................35-16
C901290023 Number of Status messages sent with Processor overload ...............35-17
C901290024 Number of Status messages received with BVCI Unknown ...............35-17
C901290025 Number of Status messages received with Cell service congestion ...35-18
C901290026 Number of Status messages received with protocol error ..................35-18
C901290027 Number of Status messages received with Processor overload.........35-19
35-1


C901290035 Number of DELETE -BSS-PFC-ACK messages sent by BSC............35-25
C901290036 Number of DELETE -BSS-PFC-REQ messages received by BSC.....35-26
35.1 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.

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 Point
When BSC sends a UL-UNITDATA message, this counter increments. The measurement
35-2

Chapter 35 Gb Message Statistics (BVC Cell)
Figure 35-1 Measurement point of sum of UL UNITDATA message handled at BSSGP

level
Unit
Times

Definition
Sum of DL UNITDATA messages handled at BSSGP level
Description
SGSN sends DL-UNITDATA PDU to BSC, and this counter counts the number of receiving
this message by BSC.
Measurement Point
When BSC receives a DL-UNITDATA message, this counter increments. The
Figure 35-2 Measurement point of sum of DL UNITDATA message handled at BSSGP

level
35-3

Unit
Times
35.4 C901290003 Number of RA-CAPABILITY message

received
Definition
Number of RA-CAPABILITY message received
Description
SGSN sends RA-CAPABILITY message to BSC, to indicate wireless capability of MS. This
counter counts the number of receiving this message.
Measurement Point
Figure 35-3 Measurement point of the number of RA-CAPABILITY message received
Unit
Times

received 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
35-4

Measurement Point
Figure 35-4 PTP Packet Paging Process
Unit
Times

received 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
Measurement Point
Figure 35-5 PTP Circuit Paging Process
Unit
Times
35-5


message sent
Definition
Number of RA-CAPABILITY-UPDATE message sent
Description
SGSN sends RA-CAPABILITY-UPDATE message to SGSN, to indicate current wireless
capability of MS. This counter counts the number of sending this message by BSC.
Measurement Point
Unit
Times

Definition
Number of RA-CAPABILITY-UPDATE-ACK message received
Description
SGSN sends RA-CAPABILITY-UPDATE-ACK message to BSC, to indicate current
wireless capability of MS. This counter counts the number of receiving this message by
BSC.
35-6

Measurement Point
When BSC sends a RA-CAPABILITY-UPDATE-ACK message from SGSN, this counter
Unit
Times
35.9 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 this message by BSC.
Usage
View the status at radio interface by counting this message.
Measurement Point
35-7

Unit
Times
35.10 C901290009 Number of Wireless Status

messages sent by BSC due to Losing Wireless
Association with MS
Definition
Number of Wireless Status messages sent by BSC due to Losing Wireless Association
with MS
Description
BSC sends wireless status message, to indicate exception occurred at SGSN radio
interface. This counter counts the number of sending this message by BSC due to Losing
Usage
Measurement Point
When BSC sends a RADIO-STATUS message due to Losing wireless association with
MS, this counter increments.
Unit
Times
35-8


sent by BSC due to Bad Link Quality
Definition
Number of wireless status messages sent by BSC due to Bad Link Quality
Description
interface. This counter counts the number of sending this message by BSC due to bad
link quality.
Usage
Measurement Point
counter increments.
Unit
Times
35.12 C901290011 Number of Wireless status

messages sent by BSC due to Cell reselection
command
Definition
Number of Wireless status messages sent by BSC due to Cell reselection command
Description
interface. This counter counts the number of sending this message by BSC due to cell
Usage
35-9

Measurement Point
Unit
Times

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 sending this message by BSC.
Measurement Point
When BSC sends a FLOW-CONTROL-BVC message, this counter increments, as A1
measurement position shown in Figure 35-9.
Unit
Times

Definition
Number of FLOW-CONTROL-BVC-ACK messages received by BSC
35-10

Description
BSC sends FLOW-CONTROL-BVC-ACK message to notify BSC of accepted flow control
policy for current BVC. This counter counts the number of receiving this message by BSC.
Measurement Point
Unit
Times

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 sending this message by BSC.
Measurement Point
When BSC sends a FLOW-CONTROL-MS message, this counter increments. The
35-11

Unit
Times

Definition
Number of FLOW-CONTROL-MS-ACK messages received by BSC
Description
BSC sends FLOW-CONTROL-MS-ACK message to notify BSC of accepted flow control
policy for current MS. This counter counts the number of receiving this message by BSC.
Measurement Point
When BSC receives a FLOW-CONTROL-MS-ACK message, this counter increments.
Unit
Times
35-12


Definition
Number of FLOW-CONTROL- PFC messages sent by BSC
Description
BSC sends FLOW-CONTROL-PFC message to notify SGSN of flow control policy for one
or more PFC for designated MS. This counter counts the number of sending this message
by BSC.
Measurement Point
When BSC sends a FLOW-CONTROL-PFC message, this counter increments. The
Unit
Times

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

Measurement Point
Unit
Times

by BSC
Definition
Number of Status messages sent by BSC
Description
the number of sending this message by BSC.
Measurement Point
When BSC sends a STATUS message, this counter increments. The measurement point
35-14

Unit
Times
35.20 C901290019 Number of Status messages

received by BSC
Definition
Number of Status messages received by BSC
Description
the number of receiving this message by BSC.
Measurement Point
When BSC receives a STATUS message, this counter increments. The measurement
Unit
Times

with BVCI Unknown
Definition
Number of Status messages sent with BVCI Unknown
Description
the number of sending this message by BSC due to BVCI Unknown.
35-15

Measurement Point
When BSC sends a STATUS message due to BVCI Unknown, this counter increments.
Unit
Times

with Cell service congestion
Definition
Number of Status messages sent with Cell service congestion
Description
the number of sending this message by BSC due to cell service congestion.
Measurement Point
When BSC sends a STATUS message due to cell service congestion, this counter
increments.
Unit
Times

with protocol error
Definition
Number of Status messages sent with protocol error
Description
the number of sending this message by BSC due to protocol error.
Measurement Point
When BSC sends a STATUS message due to protocol error, this counter increments.
Unit
Times
35-16


Definition
Number of Status messages sent with Processor overload
Description
the number of sending this message by BSC due to processor overload.
Measurement Point
When BSC sends a STATUS message due to processor overload, this counter
increments.
Unit
Times

Definition
Number of Status messages received with BVCI Unknown
Description
the number of receiving this message by BSC due to BVCI Unknown.
Measurement Point
When BSC receives a STATUS message due to BVCI Unknown, this counter increments.
Unit
Times
35-17


received with Cell service congestion
Definition
Number of Status messages received with Cell service congestion
Description
the number of receiving this message by BSC due to cell service congestion.
Measurement Point
When BSC receives a STATUS message due to cell service congestion, this counter
increments.
Unit
Times

Definition
Number of Status messages received with protocol error
Description
the number of receiving this message by BSC due to protocol error.
Measurement Point
When BSC receives a STATUS message due to protocol error, this counter increments.
Unit
Times
35-18


received with Processor overload
Definition
Number of Status messages received with cause Processor overload
Description
the number of receiving this message by BSC due to processor overload.
Measurement Point
When BSC receives a STATUS message due to processor overload, this counter
increments.
Unit
Times

Definition
Number of DOWNLOAD-BSS-PFC messages sent by BSC
Description
BSC sends DOWNLOAD-BSS-PFC message, to request SGSN originate
CREATE-BSS-PFC process. This counter counts the number of sending this message
by BSC.
Measurement Point
When BSC sends a DOWNLOAD-BSS-PFC message, this counter increments. The
35-19

Unit
Times

Definition
Number of BVCCREATE-BSS-PFC messages received by BSC
Description
SGSN sends CREATE-BSS-PFC message to request BSC create or modify a packet flow
control context. This counter counts the number of receiving this message by BSC.
Measurement Point
35-20

Unit
Times

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 counts the number of sending this message
by BSC.
Measurement Point
35-21

Unit
Times

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 counts the number of sending this message
by BSC.
Measurement Point
35-22

Unit
Times

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 sending this message by BSC.
Measurement Point
When BSC sends a MODIFY-BSS-PFC message, this counter increments. The
35-23

Unit
Times

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 the number of receiving this message
by BSC.
Measurement Point
Unit
Times

Definition
Number of DELETE-BSS-PFC messages received by BSC
35-24

Description
SGSN sends DELETE-BSS-PFC message to request BSC delete a packet flow control
context. This counter counts the number of receiving this message by BSC.
Measurement Point
Unit
Times
35.36 C901290035 Number of DELETE -BSS-PFC-ACK

Definition
Number of DELETE -BSS-PFC-ACK messages sent by BSC
Description
BSC sends DELETE-BSS-PFC-ACK message to SGSN to confirm the deletion of packet
flow control context. This counter counts the number of sending this message by BSC.
Measurement Point
35-25

Unit
Times
35.37 C901290036 Number of DELETE -BSS-PFC-REQ

Definition
Number of DELETE-BSS-PFC-REQ messages received by BSC
Description
35-26

Chapter 36
NSVC Statistic Measurement
Table of Contents
Overview ..................................................................................................................36-2
C901300001 Time of PVC unavailable .....................................................................36-2
C901300002 Time of PVC congestion frame relay ...................................................36-3
C901300003 Time of PVC congestion of level 1 .......................................................36-4
C901300004 Number of bytes received from SGSN.................................................36-4
C901300005 Number of bytes sent to SGSN ...........................................................36-5
C901300006 Number of PDU data sent by NS sub layer..........................................36-5
C901300007 Number of PDU data received by NS sub layer ...................................36-6
C901300008 Number of PDU data discarded by NS sub layer .................................36-7
C901300009 Number of reset messages send to opposite end by NS sub layer ......36-8
C901300010 Number of received reset messages sent by opposite end ..................36-8
C901300011 Number of reset confirm messages send to opposite end by NS sub
layer .........................................................................................................................36-9
C901300012 Number of received reset confirm messages sent by opposite end....36-10
C901300013 Number of blocking messages send to opposite end by NS sub
layer ....................................................................................................................... 36-11
C901300014 Number of received blocking messages sent by opposite end ........... 36-11
C901300015 Number of blocking confirm messages send to opposite end by NS
sub layer ................................................................................................................36-12
C901300016 Number of received blocking confirm messages sent by opposite
end.........................................................................................................................36-13
C901300017 Number of unblocking messages send to opposite end by NS sub
layer .......................................................................................................................36-14
C901300018 Number of received unblocking messages sent by opposite end .......36-14
C901300019 Number of unblocking confirm messages send to opposite end by NS
sub layer ................................................................................................................36-15
C901300020 Number of received unblocking acknowledge messages replied by
opposite end ..........................................................................................................36-16
C901300021 Number of abnormal cases in NS transmission due to network fault..36-17
C901300022 Number of abnormal cases in NS transmission due to O&M
interference ............................................................................................................36-17
C901300023 Number of abnormal cases in NS transmission due to equipment
fault ........................................................................................................................36-18
C901300024 Number of abnormal cases in NS transmission due to NSVC block...36-19
C901300025 Number of abnormal cases in NS transmission due to unknown
NSVC.....................................................................................................................36-20
C901300026 Number of abnormal cases in NS transmission due to protocol error .36-20
36-1

C901300027 Number of test failure (while over max) .............................................36-21

C901300028 Number of blocking procedure failure (after exceeding the maximum
times) .....................................................................................................................36-22
C901300029 Number of unblocking procedure failure (after exceeding the
maximum times).....................................................................................................36-23
C901300030 Number of congestion occurrence of level 1 ......................................36-24
C901300031 Number of congestion recovery of level 1 ..........................................36-24
C901300036 Number of BECN ..............................................................................36-26
C901300037 Number of FECN...............................................................................36-26
36.1 Overview
The NSVC statistic measurement is used to measure signaling interaction and data
transmission at NS layer of Gb interface for GPRS service. It counts the number of
various messages, such as blocking, unblocking, resetting, and ALIVE.
Statistic unit in this measurement is NSVC.
36.2 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 Point
The counter starts counting when NSVC link becomes abnormal and stops counting when
NSVC link becomes normal. The duration between the two time points is the time during
which NSVC is unavailable.
36-2

Chapter 36 NSVC Statistic Measurement
Figure 36-1 TIME OF PVC UNAVAILABLE
Unit
Second
36.3 C901300002 Time of PVC congestion frame relay

Definition
Time of PVC congestion frame relay
Description
The time during which BECN in the data sent by SGSN is set is the total time of PVC
congestion bit being set. The counter counts the total time of PVC congestion bit being
set.
Measurement Point
The counter starts counting when SGSN receives data in which BECN is set and stops
counting when BECN is not set. The duration between the two time points is the total time
of PVC congestion bit being set.
Figure 36-2 TIME OF PVC CONGESTION FRAME RELAY
Unit
Second
36-3

36.4 C901300003 Time of PVC congestion of level 1

Definition
Time of PVC congestion of level 1
Description
36.5 C901300004 Number of 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 Point
FR accumulates the number of bytes received from Gb interface. The measurement point
is A1.
Figure 36-3 UPLINK/DOWNLINK NS DATA
Unit
Byte
36-4

36.6 C901300005 Number of 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.
Usage
Measurement Point
FR accumulates the number of bytes sent each time. The measurement point is A2.
Figure 36-4 UPLINK/DOWNLINK NS DATA
Unit
Byte
36.7 C901300006 Number of 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.
36-5

'
Measurement Point
The counter increments each time BSC's FR sends a PDU data to SGSN. The
measurement point is A1.
Figure 36-5 SENDING AND RECEIVING PDU DATA
Unit
Times
36.8 C901300007 Number of 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.
Usage
'
Measurement Point
The counter increments each time BSC's FR receives a PDU data from SGSN. The
Figure 36-6 SENDING AND RECEIVING PDU DATA
36-6

Unit
Times
36.9 C901300008 Number of 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.
Usage
'
Measurement Point
l The counter increments when NS sub layer receives an illegal PDU data.
l The counter increments when FR fails to send a PDU data.
Figure 36-7 PDU DATA DISCARDED BY NS SUB LAYER
Unit
Times
36-7

36.10 C901300009 Number of 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 resetting messages sent to opposite end by NS
sub layer.
Usage
The counter counts the number of BSC resetting specified NSVC.
'
Measurement Point
Each time BSC sends the NS-RESET message, this counter increments. The
Figure 36-8 NSVC RESETTING PROCESS
Unit
Times
36.11 C901300010 Number of received reset messages

sent by opposite end
Definition
Number of received reset messages sent by opposite end
36-8

Description
SGSN sends the NSVC resetting message to indicate BSC to reset specified NSVC. This
counter counts the number of resetting messages received by BSC from the opposite end.
Usage
The counter counts the number of SGSN resetting specified NSVC.
'
Measurement Point
Each time BSC receives the NS-RESET message, this counter increments. The
Unit
Times
36.12 C901300011 Number of 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 number of sending this message by BSC.
Measurement Point
Each time BSC sends the NS-RESET-ACK message, this counter increments. The
36-9

Unit
Times
36.13 C901300012 Number of received reset confirm

messages sent by opposite end
Definition
Number of received reset confirm messages sent by opposite end
Description
SGSN sends NSVC reset confirmation message to notify BSC that specified NSVC is
reset. This counter counts the number of BSC's receiving this message.
Measurement Point
Each time BSC receives the NS-RESET-ACK message, this counter increments. The
Unit
Times
36-10

36.14 C901300013 Number of blocking messages send

to opposite end by NS sub layer
Definition
Number of blocking messages send to opposite end by NS sub layer
Description
BSC's NS sub layer sends the NSVC blocking message to indicate SGSN to block specified
NSVC. This counter counts the number of BSC's blocking specified NSVC.
Measurement Point
Each time BSC sends the NS-BLOCK message, this counter increments. The
Figure 36-12 NSVC BLOCKING PROCESS
Unit
Times
36.15 C901300014 Number of received blocking

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 blocking specified NSVC.
36-11

Measurement Point
Each time BSC receives the NS-BLOCK message, this counter increments. The
Unit
Times
36.16 C901300015 Number of 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 the number of sending this message
by BSC.
Measurement Point
Each time BSC sends the NS-BLOCK-ACK message, this counter increments. The
36-12

Unit
Times
36.17 C901300016 Number of received blocking

confirm messages sent by opposite end
Definition
Number of received blocking confirm messages sent by opposite end
Description
SGSN sends NSVC blocking confirmation message to notify BSC that specified NSVC is
reset. This counter counts the number of BSC's receiving this message.
Measurement Point
Each time BSC receives the NS-BLOCK-ACK message, this counter increments. The
36-13

Unit
Times
36.18 C901300017 Number of 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 indicate SGSN to unblock
specified NSVC. This counter counts the number of BSC's unblocking specified NSVC.
Measurement Point
Each time BSC sends the NS-UNBLOCK message, this counter increments. The
Figure 36-16 NSVC UNBLOCKING PROCESS
Unit
Times
36.19 C901300018 Number of received unblocking

Definition
Number of received unblocking messages sent by opposite end
36-14

Description
SGSN sends the NSVC unblocking message to indicate BSC to unblock specified NSVC.
This counter counts the number of SGSN's unblocking specified NSVC.
Measurement Point
Each time BSC receives the NS-UNBLOCK message, this counter increments. The
Unit
Times
36.20 C901300019 Number of unblocking confirm

messages send to opposite end by NS sub layer
Definition
Number of unblocking confirm messages send to opposite end by NS sub layer
Description
NS sub layer sends NSVC unblocking confirmation message to notify SGSN that specified
NSVC is unblocked. This counter counts the number of sending this message by BSC.
Measurement Point
Each time BSC sends the NS-UNBLOCK-ACK message, this counter increments. The
36-15

Unit
Times
36.21 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 of BSC's receiving this message.
Measurement Point
Each time BSC receives the NS-UNBLOCK-ACK message, this counter increments. The
36-16

Unit
Times
36.22 C901300021 Number of abnormal cases in NS

transmission due to network fault
Definition
Number of abnormal cases in NS transmission due to network fault
Description
This counter counts the number of abnormal cases in NS sub layer transmission due to
transmission network fault.
Measurement Point
When NS sub layer receives reported fault from frame relay and the fault is due to
transmission network fault, the counter increments. The measurement point is A1.
Figure 36-20 FR REPORTING TRANSMISSION NETWORK FAULT
Unit
Times

transmission due to O&M interference
Definition
Number of abnormal cases in NS transmission due to O&M interference
36-17

Description
This counter counts the number of abnormal cases in NS sub layer transmission due to O
interference.
Measurement Point
When NS sub layer receives the blocking request from background, the counter
increments. The measurement point is A1.
Figure 36-21 BLOCKING NSVC BY BACKGROUND
Unit
Times

transmission due to equipment fault
Definition
Number of abnormal cases in NS transmission due to equipment fault
Description
equipment fault.
Measurement Point
When NS sub layer receives reported fault from frame relay and the fault is due to
equipment fault, the counter increments. The measurement point is A1.
36-18

Figure 36-22 FR REPORTING EQUIPMENT FAULT
Unit
Times

transmission due to NSVC block
Definition
Number of abnormal cases in NS transmission due to NSVC block
Description
NSVC block.
Measurement Point
When NS sub layer sends the status message which is due to NSVC BLOCKED, the
counter increments. The measurement point is A1.
Figure 36-23 NSVC BLOCKED
36-19

Unit
Times

transmission due to unknown NSVC
Definition
Number of abnormal cases in NS transmission due to unknown NSVC
Description
unknown NSVC.
Measurement Point
When NS sub layer sends the status message which is due to unknown NSVC, the counter
Figure 36-24 NSVC UNKNOWN
Unit
Times

transmission due to protocol error
Definition
Number of abnormal cases in NS transmission due to protocol error
36-20

Description
protocol error.
Measurement Point
When NS sub layer sends the status message which is due to protocol error, including PDU
semantic error, PDU being incompatible with protocol, protocol error, invalid necessary IE,
and missing necessary IE, the counter increments. The measurement point is A1.
Figure 36-25 NS PROTOCOL ERROR
Unit
Times
36.28 C901300027 Number of test failure (while over

max)
Definition
Number of test failure (while over max)
Description
This counters counts the number of test failure due to the maximum retransmission times
being exceeded during the NS sub layer test procedure.
Measurement Point
When the number of NS sub layer's sending NS-ALIVE PDU exceeds the maximum
retransmission times NS-ALIVE-RETRIES and there is no response, the counter
36-21

Figure 36-26 TEST PROCEDURE BEING ABNORMAL
Unit
Times
36.29 C901300028 Number of blocking procedure

failure (after exceeding the maximum times)
Definition
Number of blocking procedure failure (after exceeding the maximum times)
Description
being exceeded during the NS sub layer blocking procedure.
Measurement Point
When the number of NS sub layer's sending NS-BLOCK PDU exceeds the maximum
retransmission times NS-BLOCK-RETRIES and there is no response, the counter
36-22

Figure 36-27 BLOCKING PROCEDURE BEING ABNORMAL
Unit
Times
36.30 C901300029 Number of unblocking procedure

failure (after exceeding the maximum times)
Definition
Number of unblocking procedure failure (after exceeding the maximum times)
Description
being exceeded during the NS sub layer unblocking procedure.
Measurement Point
When the number of NS sub layer's sending NS-UNBLOCK PDU exceeds the maximum
retransmission times NS-UNBLOCK-RETRIES and there is no response, the counter
36-23

Figure 36-28 UNBLOCKING PROCEDURE BEING ABNORMAL
Unit
Times
36.31 C901300030 Number of congestion occurrence

of level 1
Definition
Number of congestion occurrence of level 1
Description
36.32 C901300031 Number of congestion recovery of

level 1
Definition
Number of congestion recovery of level 1
Description
36-24


of level 2
Definition
Description

level 2
Definition
Description

of level 3
Definition
Description

level 3
Definition
Description
36-25

36.37 C901300036 Number of 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 Point
When BECN in the data received by FR from SGSN is set, the counter accumulates. The
Figure 36-29 UPLINK/DOWNLINK DATA BECN BEING SET
Unit
Times
36.38 C901300037 Number of 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.
36-26

Measurement Point
When FECN in the data received by FR from SGSN is set, the counter accumulates. The
Figure 36-30 UPLINK/DOWNLINK DATA BECN BEING SET
Unit
Times
36-27

36-28

Chapter 37
NSE Statistic Measurement
Table of Contents
Overview ..................................................................................................................37-2
C901310001 Number of CS Paging received by BSS...............................................37-2
C901310002 Number of PS Paging received by BSS...............................................37-3
C901310003 Number of SUSPEND message sent ..................................................37-4
C901310004 Number of SUSPEND-ACK message received....................................37-4
C901310005 Number of SUSPEND-NACK message received .................................37-5
C901310006 Number of RESUME message sent ....................................................37-6
C901310007 Number of RESUME-ACK message received .....................................37-7
C901310008 Number of RESUME-NACK message received ...................................37-7
C901310009 Number of FLUSH-LL message received ............................................37-8
C901310010 Number of FLUSH-LL-ACK message sent...........................................37-9
C901310011 Number of LLC-DISCARDED message sent .....................................37-10
C901310012 Number of BVC-BLOCK message sent .............................................37-10
C901310013 Number of BVC_BLOCK_ACK message received............................. 37-11
C901310014 Number of BVC-UNBLOCK message sent ........................................37-12
C901310015 Number of BVC-UNBLOCK-ACK message received .........................37-13
C901310016 Number of BVC-RESET message sent .............................................37-13
C901310017 Number of BVC-RESET message received.......................................37-14
C901310018 Number of BVC-RESET-ACK message sent .....................................37-15
C901310019 Number of BVC-RESET-ACK message received...............................37-16
C901310020 Number of PERFORM_LOCATION_REQUEST message received ...37-16
C901310021 Number of PERFORM_LOCATION_RESPONSE message sent .......37-17
C901310022 Number of PERFORM_LOCATION_ABORT message received........37-18
C901310023 Number of POSITION_COMMAND message sent ............................37-19
C901310024 Number of POSITION_RESPONSE message received.....................37-19
C901310025 Number of status messages sent ......................................................37-20
C901310026 Number of status messages received................................................37-21
C901310028 Number of status messages sent with cell service congestion ...........37-22
C901310030 Number of status messages sent with processor overload ................37-24
C901310031 Number of status messages sent with semantically incorrect PDU ....37-24
C901310032 Number of status messages sent with invalid mandatory information
element ..................................................................................................................37-25
C901310033 Number of status messages sent with missing mandatory IE.............37-25
C901310034 Number of status messages sent with missing conditional IE ............37-26
C901310035 Number of status messages sent with unexpected conditional IE ......37-26
37-1

C901310036 Number of status messages sent with conditional IE error.................37-27

C901310037 Number of status messages sent with protocol status incompatible
error .......................................................................................................................37-27
C901310038 Number of status messages received with BVCI unknown ................37-28
C901310042 Number of status messages received with BVC blocking...................37-30
C901310043 Number of status messages received with semantically incorrect
PDU .......................................................................................................................37-31
C901310044 Number of status messages received with invalid mandatory IE........37-31
C901310045 Number of status messages received with missing mandatory IE ......37-32
C901310046 Number of status messages received with missing conditional IE......37-32
C901310047 Number of status messages received with unexpected conditional
IE ...........................................................................................................................37-33
C901310048 Number of status messages received with conditional IE error ..........37-34
C901310049 Number of status messages received with protocol status
incompatible error ..................................................................................................37-34
C901310050 Number of status messages received with SGSN congestion............37-35
37.1 Overview
The NSE statistic measurement takes a single NSE as the measurement entity. It performs
statistics for paging message, status indication message, and signaling BVC resetting
message received by NSE at BSS.
Statistic unit in this measurement is the single NSE.
37.2 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.
37-2

Chapter 37 NSE Statistic Measurement
Measurement Point
When BSS receives a message of which the type is GB_PAGING_CS, the counter
increments. The measurement point is A.
Figure 37-1 MEASUREMENT POINT OF BSS RECEIVING CS PAGING MESSAGE
Unit
Times
37.3 C901310002 Number of PS Paging received by

BSS
Definition
Number of PS Paging received by BSS
Description
This counter counts the number of PAGING PS messages received by NSE at BSC from
SGSN.
Usage
The counter is used to find out the frequency of SGSN's PS paging to MS.
Measurement Point
When BSS receives a message of which the type is GB_PAGING_PS, the counter
Figure 37-2 MEASUREMENT POINT OF BSS RECEIVING PS PAGING MESSAGE
Unit
Times
37-3

37.4 C901310003 Number of SUSPEND message sent

Definition
Number of SUSPEND message sent
Description
When BSS receives the suspending GPRS service message from MS, BSS will send the
SUSPEND message to SGSN. This counter counts the number of sending SUSPEND
message from NSE.
Usage
The counter is used to find out the frequency of MS's terminating GPRS service.
Measurement Point
When BSS sends the SUSPEND message, the counter increments. The measurement
point is A1.
Figure 37-3 SUSPEND PROCESS
Unit
Times
37.5 C901310004 Number of 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.
37-4

Usage
The counter is used to find out cases in which SGSN has response when MS requests for
terminating GPRS service.
Measurement Point
When BSS receives the SUSPEND_ACK message, the counter increments. The
Figure 37-4 SUSPEND PROCESS
Unit
Times
37.6 C901310005 Number of SUSPEND-NACK message

received
Definition
Number of SUSPEND-NACK message received
Description
When SGSN receives the SUSPEND message from BSS, it checks the SUSPEND
message content. If the message content is incorrect or fault occurs at SGSN, SGSN
will send the SUSPEND_NACK message to BSS. This counter counts the number of
SUSPEND_NACK messages received by NSE.
Usage
The counter is used to find out cases in which SGSN has no response when MS requests
for terminating GPRS service.
Measurement Point
When BSS receives the SUSPEND_NACK message, the counter increments. The
37-5

Figure 37-5 MEASUREMENT POINT OF BSS RECEIVING SUSPEND_NACK MESSAGE
Unit
Times
37.7 C901310006 Number of RESUME message sent

Definition
Number of RESUME message sent
Description
When problems that cause MS to suspend disappear, BSS might send the RESUME
message to SGSN to notify it to resume GPRS service of MS. This counter counts the
number of sending RESUME message by BSS.
Usage
The counter is used to find out the frequency of MS's resuming GPRS service.
Measurement Point
When BSS sends the RESUME message, the counter increments. The measurement
point is A1.
Figure 37-6 RESUME PROCESS
Unit
Times
37-6

37.8 C901310007 Number of 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
Usage
The counter is used to find out causes due to which SGSN has no response when MS
requests for resuming GPRS service.
Measurement Point
When BSS receives the RESUME_ACK message, the counter increments. The
Figure 37-7 RESUME PROCESS
Unit
Times
37.9 C901310008 Number of 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
37-7

is, unknown MS. At this moment, BSS will terminate the RESUME process and ask MS
to update routing area. This counter counts the number of RESUME_NACK messages
received by NSE.
Usage
for resuming GPRS service.
Measurement Point
When BSS receives the RESUME_NACK message, the counter increments. The
Figure 37-8 MEASUREMENT POINT OF BSS RECEIVING RESUME_NACK MESSAGE
Unit
Times
37.10 C901310009 Number of FLUSH-LL message

received
Definition
Number of FLUSH-LL message received
Description
When SGSN detects that a MS changes cell through cell update or routing area update,
SGSN will send the FLUSH_LL message to the old BVC to initiate the cell update process
on NSE. This counter counts the number of FLUSH_LL messages received by NSE.
Usage
The counter is used to find out the frequency of MS's changing cell.
Measurement Point
When BSS receives the FLUSH_LL message, the counter increments. The measurement
point is A1.
37-8

Figure 37-9 FLUSH_LL PROCESS
Unit
Times
37.11 C901310010 Number of 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 Point
When BSS sends the FLUSH_LL_ACK message, the counter increments. The
Figure 37-10 FLUSH_LL PROCESS
37-9

Unit
Times
37.12 C901310011 Number of 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 sending LLC_DISCARDED message from NSE.
Usage
The counter is used to find out the storage of LLC PDU in BSS.
Measurement Point
When BSS sends the LLC_DISCARDED message, the counter increments. The
measurement point is A.
Figure 37-11 MEASUREMENT POINT OF BSS SENDING LLC_DISCARDED MESSAGE
Unit
Times

sent
Definition
Description
When BSS blocks a BVC, it will send the BVC_BLOCK message to SGSN to start the
timer T1. BSS will identify the blocked BVC and stop sending uplink data of the BVC.
37-10

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 Point
When BSS sends the BVC_BLOCK message, the counter increments. The measurement
point is A1.
Figure 37-12 BVC_BLOCK PROCESS
Unit
Times
37.14 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 identifies the BVC to be
blocked and stops sending data to the BVC, and replies the BVC_BLOCK_ACK message
to BSS. This counter counts the number of BVC_BLOCK_ACK messages received by
NSE.
Usage
The counter is used to find out cases when BVC is blocked.
Measurement Point
When BSS receives the BVC_BLOCK_ACK message, the counter increments. The
37-11

Figure 37-13 BVC_BLOCK PROCESS
Unit
Times

sent
Definition
Description
When BSS unblocks the blocked BVC, it will send the BVC_UNBLOCK message to SGSN.
This counter counts the number of sending BVC_UNBLOCK message from NSE.
Usage
The counter is used to find out the frequency of BSS's requesting to unblock BVC.
Measurement Point
When BSS sends the BVC_UNBLOCK message, the counter increments. The
Figure 37-14 BVC_UNBLOCK PROCESS
Unit
Times
37-12


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_UNBLOCK_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 Point
When BSS receives the BVC_UNBLOCK_ACK message, the counter increments. The
Figure 37-15 BVC_UNBLOCK PROCESS
Unit
Times

sent
Definition
Description
This counter counts the number of PCU sending signaling BVC resetting message through
Gb interface.
37-13

Usage
The counter is used to find out the frequency of requesting to restart BVC due to BVC
failure.
Measurement Point
When NSE at BSC sends message of which the type is BVC_RESET and BVCI is zero,
the counter increments. The measurement point is A1.
Figure 37-16 PROCESS OF SENDING BVC_RESET
Unit
Times

received
Definition
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 Point
When NSE at BSC receives message of which the type is BVC_RESET and BVCI is zero,
37-14

Figure 37-17 PROCESS OF RECEIVING BVC_RESET
Unit
Times

message 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 message. 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 Point
When NSE at BSC sends message of which the type is BVC_RESET_ACK and BVCI is
zero, the counter increments. The measurement point is A2.
Figure 37-18 PROCESS OF RECEIVING BVC_RESET
Unit
Times
37-15


message received
Definition
Number of BVC_RESET_ACK message received
Description
Number of PCU's receiving the signaling BVC resetting acknowledge message. This
counter counts the number of NSE's receiving signaling BVC resetting acknowledge
message.
Usage
The counter is used to find out cases of BVC initialization.
Measurement Point
When NSE at BSC receives message of which the type is BVC_RESET_ACK and BVCI
is zero, the counter increments. The measurement point is A2.
Figure 37-19 PROCESS OF SENDING BVC_RESET
Unit
Times
37.21 C901310020 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_LOCATION_REQUEST message to BSS. This
counter counts the number of BSS's receiving the location request message.
37-16

Usage
The counter is used to find out the frequency of SGSN's sending location request to BSS.
Measurement Point
When BSS receives the PERFORM_LOCATION_REQUEST message, the counter
Figure 37-20 PERFORM_LOCATION_REQUEST PROCESS
Unit
Times

RESPONSE message sent
Definition
Number of PERFORM_LOCATION_RESPONSE message sent
Description
After BSS receives the PERFORM_LOCATION_REQUEST message, it will send the
location request to SMLC and wait for SMLC's response, and then send the result in
the PERFORM_LOCATION_RESPONSE message to SGSN. This counter counts the
number of BSS's sending the location request response message.
Usage
The counter is used to find out BSS's response to the location request from SGSN.
Measurement Point
When BSS sends the PERFORM_LOCATION_RESPONSE message, the counter
37-17

Figure 37-21 PERFORM_LOCATION_REQUEST PROCESS
Unit
Times

ABORT message received
Definition
Number of PERFORM_LOCATION_ABORT message received
Description
When SGSN initiates the location request before interruption occurs, it sends the
PERFORM_LOCATION_ABORT message to BSS. This counter counts the number of
BSS's receiving the PERFORM_LOCATION_ABORT message.
Usage
The counter is used to find out the frequency of SGSN's terminating location towards BSS.
Measurement Point
When BSS receives the PERFORM_LOCATION_ABORT message, the counter
Figure 37-22 MEASUREMENT POINT OF BSS RECEIVING

PERFORM_LOCATION_ABORT MESSAGE
Unit
Times
37-18

37.24 C901310023 Number of POSITION_COMMAND

message sent
Definition
Number of POSITION_COMMAND message sent
Description
BSS triggers the positioning command process by sending POSITION_COMMAND
message to SGSN. This process is valid only when positioning a MS. This counter counts
the number of BSS's sending POSITION_COMMAND message.
Usage
The counter is used to find out the frequency of BSS's requesting to implement positioning
command to SGSN.
Measurement Point
When BSS sends the POSITION_COMMAND message, the counter increments. The
Figure 37-23 POSITION_COMMAND PROCESS
Unit
Times
37.25 C901310024 Number of POSITION_RESPONSE

message received
Definition
Number of POSITION_RESPONSE message received
Description
When SGSN receives the TOM message, SGSN will send the POSITION_RESPONSE
message to BSS to trigger the position response process. The TOM message is
37-19

contained in LLC PDU, and the LLC PDU contains the RRLP message of a MS. This
position response process is valid only when positioning a MS. This counter counts the
number of BSS's receiving the POSITION_RESPONSE message.
Usage
The counter is used to find out the frequency of SGSN's requesting to implement
positioning command to BSS.
Measurement Point
When BSS receives the POSITION_RESPONSE message, the counter increments. The
Figure 37-24 POSITION_COMMAND PROCESS
Unit
Times

Definition
Number of status messages sent
Description
When NSE receives downlink BSSGP PDU, if there is any abnormality, NSE will send
the STATUS message to the opposite end entity. The STATUS message sent indicates
causes of the abnormality: BVCI unknown, cell traffic congestion, Protocol error, Processor
overload, Semantically incorrect PDU, Invalid mandatory information, Missing mandatory
IE, or Missing conditional IE. This counter counts the number of abnormality that occurs.
Usage
The counter is used to find out abnormality occurring when NSE receives downlink BSSGP
PDU.
37-20

Measurement Point
When NSE at BSC sends message of which the type is STATUS to opposite end entity,
Figure 37-25 STATUS PROCESS
Unit
Times

received
Definition
Number of status messages received
Description
If the BSSGP PDU sent by NSE to SGSN is abnormal, NSE will receive the STATUS
message returned from the opposite end. The STATUS message returned indicates
causes of the abnormality: BVCI unknown, cell traffic congestion, Protocol error,
Processor overload, Semantically incorrect PDU, Invalid mandatory information, Missing
mandatory IE, or Missing conditional IE. This counter counts teh number of STATUS
messages returned from SGSN.
Usage
The counter is used to find out abnormality occurring when SGSN receives downlink
BSSGP PDU.
Measurement Point
When NSE receives the STATUS message, the counter increments. The measurement
point is A2.
37-21

Unit
Times

with BVCI Unknown
Definition
Number of status messages sent with BVCI Unknown
Description
This counter counts the number of NSE's sending STATUS message to opposite end entity,
the message indicating "BVCI unknown".
Usage
The counter is used to find out the frequency of abnormality due to "BVCI unknown"
occurring when NSE receives downlink BSSGP PDU.
Measurement Point
When NSE sends the STATUS message to opposite end entity and the message indicates
that the abnormality is due to "BVCI unknown", the counter increments.
Unit
Times

Definition
Number of status messages sent with cell service congestion
37-22

Description
the message indicating "cell traffic congestion".
Usage
The counter is used to find out the frequency of abnormality due to "cell traffic congestion"
Measurement Point
that the abnormality is due to "cell traffic congestion", the counter increments.
Unit
Times

with protocol error
Definition
Number of status messages sent with protocol error
Description
the message indicating "Protocol error".
Usage
The counter is used to find out the frequency of abnormality due to "Protocol error"
Measurement Point
that the abnormality is due to "Protocol error", the counter increments.
Unit
Times
37-23


with processor overload
Definition
Number of status messages sent with processor overload
Description
the message indicating "Processor overload".
Usage
The counter is used to find out the frequency of abnormality due to "Processor overload"
Measurement Point
that the abnormality is due to "Processor overload", the counter increments.
Unit
Times

with semantically incorrect PDU
Definition
Number of status messages sent with semantically incorrect PDU
Description
the message indicating "Semantically incorrect PDU".
Usage
The counter is used to find out the frequency of abnormality due to "Semantically incorrect
PDU" occurring when NSE receives downlink BSSGP PDU.
Measurement Point
that the abnormality is due to "Semantically incorrect PDU", the counter increments.
37-24

Unit
Times

with invalid mandatory information element
Definition
Number of status messages sent with invalid mandatory information element
Description
the message indicating "Invalid mandatory information".
Usage
The counter is used to find out the frequency of abnormality due to "Invalid mandatory
information" occurring when NSE receives downlink BSSGP PDU.
Measurement Point
that the abnormality is due to "Invalid mandatory information", the counter increments.
Unit
Times

with missing mandatory IE
Definition
Number of status messages sent with missing mandatory IE
Description
the message indicating "Missing mandatory IE".
Usage
The counter is used to find out the frequency of abnormality due to "Missing mandatory
IE" occurring when NSE receives downlink BSSGP PDU.
37-25

Measurement Point
that the abnormality is due to "Missing mandatory IE", the counter increments.
Unit
Times

with missing conditional IE
Definition
Number of status messages sent with missing conditional IE
Description
the message indicating "Missing conditional IE".
Usage
The counter is used to find out the frequency of abnormality due to "Missing conditional
Measurement Point
that the abnormality is due to "Missing conditional IE", the counter increments.
Unit
Times

with unexpected conditional IE
Definition
Number of status messages sent with unexpected conditional IE
Description
the message indicating "Unexpected conditional IE".
37-26

Usage
The counter is used to find out the frequency of abnormality due to "Unexpected conditional
Measurement Point
that the abnormality is due to "Unexpected conditional IE", the counter increments.
Unit
Times

with conditional IE error
Definition
Number of status messages sent with conditional IE error
Description
the message indicating "Conditional IE error".
Usage
The counter is used to find out the frequency of abnormality due to "Conditional IE error"
Measurement Point
that the abnormality is due to "Conditional IE error", the counter increments.
Unit
Times

with protocol status incompatible error
Definition
Number of status messages sent with protocol status incompatible error
37-27

Description
the message indicating "PDU not compatible with the protocol state".
Usage
The counter is used to find out the frequency of abnormality due to "PDU not compatible
with the protocol state" occurring when NSE receives downlink BSSGP PDU.
Measurement Point
that the abnormality is due to "PDU not compatible with the protocol state", the counter
increments.
Unit
Times

received 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".
Usage
occurring when SGSN receives downlink BSSGP PDU.
Measurement Point
When PCU receives STATUS message which indicates "BVCI unknown", the counter
increments.
Unit
Times
37-28


Definition
Number of status messages received with cell service congestion
Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the
message indicating "cell traffic congestion".
Usage
Measurement Point
When PCU receives STATUS message which indicates "cell traffic congestion", the
counter increments.
Unit
Times

Definition
Number of status messages received with protocol error
Description
This counter counts the number of received STATUS messages which indicate "Protocol
error".
Usage
Measurement Point
When PCU receives STATUS message which indicates "Protocol error", the counter
increments.
37-29

Unit
Times

Definition
Number of status messages received with processor overload
Description
message indicating "Processor overload".
Usage
Measurement Point
When PCU receives STATUS message which indicates "Processor overload", the counter
increments.
Unit
Times

received with BVC blocking
Definition
Number of status messages received with BVC blocking
Description
message indicating "BVCI-blocked".
Usage
The counter is used to find out the frequency of abnormality due to "BVCI-blocked"
37-30

Measurement Point
When PCU receives STATUS message which indicates "BVCI-blocked", the counter
increments.
Unit
Times

received with semantically incorrect PDU
Definition
Number of status messages received with semantically incorrect PDU
Description
This counter counts the number of received STATUS messages which indicate
"Semantically incorrect PDU".
Usage
PDU" occurring when SGSN receives downlink BSSGP PDU.
Measurement Point
When PCU receives STATUS message which indicates "Semantically incorrect PDU", the
counter increments.
Unit
Times

received with invalid mandatory IE
Definition
Number of status messages received with invalid mandatory IE
Description
This counter counts the number of received STATUS messages which indicate "Invalid
mandatory information".
37-31

Usage
information" occurring when SGSN receives downlink BSSGP PDU.
Measurement Point
When PCU receives STATUS message which indicates "Invalid mandatory information",
Unit
Times

received with missing mandatory IE
Definition
Number of status messages received with missing mandatory IE
Description
This counter counts the number of received STATUS messages which indicate "Missing
mandatory IE".
Usage
IE" occurring when SGSN receives downlink BSSGP PDU.
Measurement Point
When PCU receives STATUS message which indicates "Missing mandatory IE", the
counter increments.
Unit
Times

received with missing conditional IE
Definition
Number of status messages received with missing conditional IE
37-32

Description
conditional IE".
Usage
Measurement Point
When PCU receives STATUS message which indicates "Missing conditional IE", the
counter increments.
Unit
Times

received with unexpected conditional IE
Definition
Number of status messages received with unexpected conditional IE
Description
"Unexpected conditional IE".
Usage
Measurement Point
When PCU receives STATUS message which indicates "Unexpected conditional IE", the
counter increments.
Unit
Times
37-33


received with conditional IE error
Definition
Number of status messages received with conditional IE error
Description
"Conditional IE error".
Usage
Measurement Point
When PCU receives STATUS message which indicates "Conditional IE error", the counter
increments.
Unit
Times

received with protocol status incompatible error
Definition
Number of status messages received with protocol status incompatible error
Description
This counter counts the number of received STATUS messages which indicate "PDU not
compatible with the protocol state".
Usage
with the protocol state" occurring when SGSN receives downlink BSSGP PDU.
Measurement Point
When PCU receives STATUS message which indicates "PDU not compatible with the
protocol state", the counter increments.
37-34

Unit
Times

received with SGSN congestion
Definition
Number of status messages received with SGSN congestion
Description
message indicating "SGSN congestion".
Usage
The counter is used to find out the frequency of abnormality due to "SGSN congestion"
Measurement Point
When PCU receives STATUS message which indicates "SGSN congestion", the counter
increments.
Unit
Times
37-35

37-36

Chapter 38
BTS TRX Measurement
Table of Contents
Overview ..................................................................................................................38-2
C901320001 Number of normal increases of MS power due to UL signal level ........38-3
C901320002 Number of rapid increase in MS power due to UL signal level .............38-4
C901320003 Number of normal decrease of MS power due to UL signal level .........38-5
C901320004 Number of rapid decrease in MS power due to UL signal level ............38-6
C901320005 Number of normal increases of BS power due to DL signal level .........38-7
C901320006 Number of rapid increase in BS power due to DL signal level ..............38-8
C901320007 Number of normal decrease of BS power due to DL signal level..........38-9
C901320008 Number of rapid decrease in BS power due to DL signal level...........38-10
C901320009 Number of normal increases of MS power due to UL signal quality.... 38-11
C901320010 Number of rapid increase in MS power due to UL signal quality ........38-12
C901320011 Number of normal decrease of MS power due to UL signal quality ....38-13
C901320012 Number of rapid decrease in MS power due to UL signal quality .......38-14
C901320013 Number of normal increases of BS power due to DL signal quality ....38-15
C901320014 Number of rapid increase in BTS power due to DL signal quality .......38-16
C901320015 Number of normal decrease of BS power due to DL signal quality.....38-17
C901320016 Number of rapid decrease in BTS power due to DL signal quality......38-18
C901320017 Total value of each result of regular scanning of MS utilization power .38-19
C901320018 Number of regular scanning and sampling of MS utilization power ....38-20
C901320019 Total value of each result of regular scanning of BS utilization power .38-21
C901320020 Number of regular scanning and sampling of BS utilization power .....38-22
C901320021 Total value of power scans of DL signal level.....................................38-23
C901320022 Number of power scans of DL signal level .........................................38-24
C901320023 Total value of power scans of UL signal level.....................................38-25
C901320024 Number of power scans of UL signal level .........................................38-26
C901320025 Total value of power scans of DL signal quality..................................38-27
C901320026 Number of power scans of DL signal quality ......................................38-28
C901320027 Total value of power scans of UL signal quality..................................38-29
C901320028 Number of power scans of UL signal quality ......................................38-30
C901320029 Maximum value of UL signal level in regular scan .............................38-31
C901320030 Minimum value of UL signal level in regular scan ..............................38-32
C901320031 Maximum value obtained in regular scan of DL signal level ...............38-33
C901320032 Minimum value obtained in regular scan of DL signal level ................38-34
C901320033 Sum of Periodic BS Power (TCH/F) Search Result............................38-35
C901320034 Periodic BS Power (TCH/F) Search Times ........................................38-35
C901320035 Sum of Periodic BS Power (TCH/H) Search Result ...........................38-36
C901320036 Number of Periodic BS Power (TCH/H) Search .................................38-36
38-1

C901320037 Sum of Periodic BS Power (SDCCH) Search Result..........................38-37

C901320038 Number of Periodic BS Power (SDCCH) Search ...............................38-37
C901320039 Sum of Periodic DL Signal Level (TCH/F) Search Result...................38-38
C901320040 Number of Periodic DL Signal Level (TCH/F) Search ........................38-38
C901320041 Sum of Periodic DL Signal Level (TCH/H) Search Result ..................38-39
C901320042 Number of Periodic DL Signal Level (TCH/H) Search ........................38-39
C901320043 Sum of Periodic DL Signal Level (SDCCH) Search Result.................38-40
C901320044 Number of Periodic DL Signal Level (SDCCH) Search ......................38-40
38.1 Overview
According to the receiving level and receiving quality in MS measurement report and the
receiving level and receiving quality in BTS measurement, BTS decides whether to perform
power control for MS or BTS. BTS also performs statistics according to different reasons
for power control.
There are two ways for power control: common control and rapid control. The power
control amplitude in rapid control is larger than that in common control. Besides, BTS
periodically samples the power of MS and BTS to get the average power.
After the power control measurement task is customized, BTS periodically reports the
power control statistic result to BSC through the PC TEST RPT message. The power
control measurement result can be used to analyze coverage quality and power control
effect and frequency.
The power control measurement mechanism is shown as below. The measurement point
for MS power control is A1, which is after BTS sending the power control message to
MS. The measurement point for BTS power control is A2, which is after BTS sending the
power control message to itself. The measurement point for periodical power sampling is
A3. BSC collects the power control measurement counter information after it receives the
PC TEST RPT message, which is at B1 as shown in below.
Figure 38-1 POWER CONTROL MEASUREMENT
38-2

Chapter 38 BTS TRX Measurement
Statistic unit in this measurement is TRX.
38.2 C901320001 Number of normal increases of MS

power due to UL signal level
Definition
Number of normal increases of MS power due to UL signal level
Description
In common power control, after BTS measures the uplink level and quality of MS, it
compares the MS's uplink level with the configured uplink receiving level threshold
according to the power control algorithm and makes decision. If BTS decides to increase
MS's transmission power, it sends the message of increasing transmission power to MS,
Measurement Point
The counter counts when BTS sends the message of increasing transmission power to
MS. The measurement point is A1
Unit
Times
Related Features
ZGO-04-02-002 Dynamic MS Power Control
38-3

38.3 C901320002 Number of rapid increase in MS

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 quality of MS, it compares
the MS's uplink level with the configured uplink receiving level threshold according to the
power control algorithm and makes decision. If BTS decides to increase MS's transmission
power, it sends the message of increasing transmission power to MS, and the counter
increments.
Measurement Point
MS. The measurement point is A1.
Unit
Times
Related Features
38-4

38.4 C901320003 Number of normal decrease of MS

Definition
Number of normal decrease of MS power due to UL signal level
Description
compares the MS's uplink level with the configured uplink receiving level threshold
according to the power control algorithm and makes decision. If BTS decides to decrease
MS's transmission power, it sends the message of decreasing transmission power to MS,
Measurement Point
The counter counts when BTS sends the message of decreasing transmission power to
Unit
Times
Related Features
38-5

38.5 C901320004 Number of rapid decrease in MS

Definition
Number of rapid decrease in MS power due to UL signal level
Description
the MS's uplink level with the configured uplink receiving level threshold according to
the power control algorithm and makes decision. If BTS decides to decrease MS's
transmission power, it sends the message of decreasing transmission power to MS, and
Measurement Point
Unit
Times
Related Features
38-6

38.6 C901320005 Number of normal increases of BS

power due to DL signal level
Definition
Number of normal increases of BS power due to DL signal level
Description
In common power control, after BTS receives the MS measurement report, it compares
the MS's downlink receiving level with the configured downlink receiving level threshold
BTS's transmission power, it sends the message of increasing transmission power to BTS,
Measurement Point
itself. The measurement point is A2.
Unit
Times
Related Features
ZGO-04-02-001 Dynamic BTS Power Control
38-7

38.7 C901320006 Number of rapid increase in BS

Definition
Number of rapid increase in BS power due to DL signal level
Description
In rapid power control, after BTS receives the MS measurement report, it compares
the MS's downlink receiving level and quality with the configured downlink receiving
level threshold and downlink receiving quality threshold according to the power control
algorithm and makes decision. If BTS decides to increase BTS's transmission power, it
sends the message of increasing transmission power to BTS, and the counter increments.
Measurement Point
Unit
Times
Related Features
38-8

38.8 C901320007 Number of normal decrease of BS

Definition
Number of normal decrease of BS power due to DL signal level
Description
BTS's transmission power, it sends the message of decreasing transmission power to BTS,
Measurement Point
Unit
Times
Related Features
38-9

38.9 C901320008 Number of rapid decrease in BS

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
BTS's transmission power, it sends the message of decreasing transmission power to
BTS, and the counter increments.
Measurement Point
Unit
Times
Related Features
38-10

38.10 C901320009 Number of normal increases of MS

power due to UL signal quality
Definition
Number of normal increases of MS power due to UL signal quality
Description
compares the MS's uplink quality with the configured uplink receiving quality threshold
MS's transmission power, it sends the message of increasing transmission power to MS,
Measurement Point
Unit
Times
Related Features
38-11

38.11 C901320010 Number of rapid increase in MS

Definition
Number of rapid increase in MS power due to UL signal quality
Description
the MS's uplink quality with the configured uplink receiving quality threshold according
to the power control algorithm and makes decision. If BTS decides to increase MS's
transmission power, it sends the message of increasing transmission power to MS, and
Measurement Point
Unit
Times
Related Features
38-12

38.12 C901320011 Number of normal decrease of MS

Definition
Number of normal decrease of MS power due to UL signal quality
Description
compares the MS's uplink quality with the configured uplink receiving quality threshold
MS's transmission power, it sends the message of decreasing transmission power to MS,
Measurement Point
Unit
Times
Related Features
38-13

38.13 C901320012 Number of rapid decrease in MS

Definition
Number of rapid decrease in MS power due to UL signal quality
Description
the MS's uplink quality with the configured uplink receiving quality threshold according
to the power control algorithm and makes decision. If BTS decides to decrease MS's
transmission power, it sends the message of decreasing transmission power to MS, and
Measurement Point
Unit
Times
Related Features
38-14

38.14 C901320013 Number of normal increases of BS

power due to DL signal quality
Definition
Number of normal increases of BS power due to DL signal quality
Description
the MS's downlink receiving quality with the configured downlink receiving quality threshold
Measurement Point
Unit
Times
Related Features
38-15

38.15 C901320014 Number of rapid increase in BTS

Definition
Number of rapid increase in BTS power due to DL signal quality
Description
In rapid power control, after BTS receives the MS measurement report, it compares the
MS's downlink receiving quality with the configured downlink receiving quality threshold
Measurement Point
Unit
Times
Related Features
38-16

38.16 C901320015 Number of normal decrease of BS

Definition
Number of normal decrease of BS power due to DL signal quality
Description
the MS's downlink receiving quality with the configured downlink receiving quality threshold
Measurement Point
Unit
Times
Related Features
38-17

38.17 C901320016 Number of rapid decrease in BTS

Definition
Number of rapid decrease in BTS power due to DL signal quality
Description
In rapid power control, after BTS receives the MS measurement report, it compares the
MS's downlink receiving quality with the configured downlink receiving quality threshold
Measurement Point
Unit
Times
Related Features
38-18

38.18 C901320017 Total value of each result of regular

scanning of MS utilization power
Definition
Total value of each result of regular scanning of MS utilization power
Description
To get the average MS utilization power on TRX, BTS periodically scans the MS utilization
power on channels of TRX and accumulates the value. During the period of reporting
measurement result to BSC, BTS may perform multiple periodical scannings. This counter
accumulates the MS utilization power value of each scanning.
Measurement Point
The counter accumulates when BTS performs periodical scanning. The measurement
point is A3.
Unit
Grade
Related Features
38-19


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 accumulates the value. Each time a MS utilization power
value is accumulated, the counter increments. During the period of reporting measurement
result to BSC, BTS may perform multiple periodical scannings. This counter accumulates
the number of periodical scannings.
Measurement Point
The counter counts when BTS performs periodical scanning. The measurement point is
A3.
Unit
Times
Related Features
38-20

38.20 C901320019 Total value 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
the BTS utilization power value of each scanning.
Measurement Point
The counter accumulates when BTS performs periodical scanning. The measurement
point is A3.
Unit
Grade
Related Features
38-21


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 accumulated, the counter increments. During the period of reporting measurement
the number of periodical scannings.
Measurement Point
A3.
Unit
Times
Related Features
38-22

38.22 C901320021 Total value of 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 measurement result to BSC, BTS may perform multiple periodical
scannings. This counter accumulates the MS downlink signal level value of each scanning.
Measurement Point
A3.
Unit
Grade
Related Features
38-23

38.23 C901320022 Number of power scans of DL signal

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 number of periodical scannings.
Measurement Point
A3.
Unit
Times
Related Features
38-24

38.24 C901320023 Total value of power scans of UL

signal level
Definition
Total value of power scans of UL signal level
Description
To get the average uplink signal level received by TRX, BTS periodically scans the
uplink signal level on channels of TRX and accmulates. During the period of reporting
measurement result to BSC, BTS may perform multiple periodical scannings. This
counter accumulates the uplink signal level value of each scanning.
Measurement Point
A3.
Unit
Grade
Related Features
38-25

38.25 C901320024 Number of power scans of UL signal

level
Definition
Number of power scans of UL signal level
Description
To get the average uplink signal level received by TRX, BTS periodically scans the uplink
signal level on channels of TRX and accmulates. Each time a uplink signal level is
accumulated, the counter increments. During the period of reporting measurement result
to BSC, BTS may perform multiple periodical scannings. This counter accumulates the
number of periodical scannings.
Measurement Point
A3.
Unit
Times
Related Features
38-26

38.26 C901320025 Total value of power scans of DL

signal 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 measurement result to BSC, BTS may perform multiple
periodical scannings. This counter accumulates the MS downlink signal quality value of
each scanning.
Measurement Point
A3.
Unit
Grade
Related Features
38-27

38.27 C901320026 Number of power scans of DL signal

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 downlink signal quality is accumulated, the counter increments. During
the period of reporting measurement result to BSC, BTS may perform multiple periodical
scannings. This counter accumulates the number of periodical scannings.
Measurement Point
A3.
Unit
Times
Related Features
38-28

38.28 C901320027 Total value of power scans of UL

signal quality
Definition
Total value of power scans of UL signal quality
Description
To get the average uplink signal quality received by TRX, BTS periodically scans the
uplink signal quality on channels of TRX and accmulates. During the period of reporting
measurement result to BSC, BTS may perform multiple periodical scannings. This
counter accumulates the uplink signal quality value of each scanning.
Measurement Point
A3.
Unit
Grade
Related Features
38-29

38.29 C901320028 Number of power scans of UL signal

quality
Definition
Number of power scans of UL signal quality
Description
To get the average uplink signal quality received by TRX, BTS periodically scans the uplink
signal quality on channels of TRX and accmulates. Each time a uplink signal quality is
accumulated, the counter increments. During the period of reporting measurement result
to BSC, BTS may perform multiple periodical scannings. This counter accumulates the
number of periodical scannings.
Measurement Point
A3.
Unit
Times
Related Features
38-30

38.30 C901320029 Maximum value of UL signal level

in regular scan
Definition
Maximum value of UL signal level in regular scan
Description
When BSC collects information of power control measurement counters, this counter
records the maximum uplink signal level value.
Measurement Point
The counter counts when BSC receives the reported power control measurement message
PC TEST RPT. The measurement point is B1.
Unit
Grade
Related Features
38-31

38.31 C901320030 Minimum value of UL signal level

in regular scan
Definition
Minimum value of UL signal level in regular scan
Description
records the minimum uplink signal level value.
Measurement Point
Unit
Grade
Related Features
38-32

38.32 C901320031 Maximum value obtained in regular

scan of DL signal level
Definition
Maximum value obtained in regular scan of DL signal level
Description
records the maximum downlink signal level value.
Measurement Point
Unit
Grade
Related Features
38-33

38.33 C901320032 Minimum value obtained in regular

scan of DL signal level
Definition
Minimum value obtained in regular scan of DL signal level
Description
records the minimum downlink signal level value.
Measurement Point
Unit
Grade
Related Features
38-34

38.34 C901320033 Sum of Periodic BS Power (TCH/F)

Search Result
Definition
Sum of Periodic BS Power (TCH/F) Search Result
Description
This counter records the total value of BS power (TCH/F) of periodical scannings.
Measurement Point
When the power control message is received and if the channel is TCH/F, then obtain the
BS power in the message and accumulate.
Unit
Grade
Related Features
38.35 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 Point
When the power control message is received, if the channel is TCH/F and the message
contains BS power information, then the counter increments.
Unit
Times
Related Features
38-35

38.36 C901320035 Sum of Periodic BS Power (TCH/H)

Search Result
Definition
Sum of Periodic BS Power (TCH/H) Search Result
Description
This counter records the total value of BS power (TCH/H) of periodical scannings.
Measurement Point
When the power control message is received and if the channel is TCH/H, then obtain the
BS power in the message and accumulate.
Unit
Grade
Related Features
38.37 C901320036 Number of Periodic BS Power

(TCH/H) Search
Definition
Number of Periodic BS Power (TCH/H) Search
Description
This counter counts the number of periodical scanning of BS power (TCH/H).
Measurement Point
When the power control message is received, if the channel is TCH/H and the message
Unit
Times
Related Features
38-36

38.38 C901320037 Sum of Periodic BS Power (SDCCH)

Search Result
Definition
Sum of Periodic BS Power (SDCCH) Search Result
Description
This counter records the total value of BS power (SDCCH) of periodical scannings.
Measurement Point
When the power control message is received and if the channel is SDCCH, then obtain
the BS power in the message and accumulate.
Unit
Grade
Related Features
38.39 C901320038 Number of Periodic BS Power

(SDCCH) Search
Definition
Number of Periodic BS Power (SDCCH) Search
Description
This counter counts the number of periodical scanning of BS power (SDCCH).
Measurement Point
When the power control message is received, if the channel is SDCCH and the message
Unit
Times
Related Features
38-37

38.40 C901320039 Sum of Periodic DL Signal Level

(TCH/F) Search Result
Definition
Sum of Periodic DL Signal Level (TCH/F) Search Result
Description
This counter records the total value of downlink signal level (TCH/F) of periodical
scannings.
Measurement Point
When the power control message is received and if the channel is TCH/F, then obtain the
downlink signal level in the message and accumulate.
Unit
Grade
Related Features
38.41 C901320040 Number of Periodic DL Signal Level

(TCH/F) Search
Definition
This counter counts the number of periodical scanning of downlink signal level (TCH/F).
Description
This counter records the total value of downlink signal level (TCH/F) of periodical
scannings.
Measurement Point
When the power control message is received, if the channel is TCH/F and the message
contains downlink signal level information, then the counter increments.
Unit
Times
Related Features
38-38


(TCH/H) Search Result
Definition
Sum of Periodic DL Signal Level (TCH/H) Search Result
Description
This counter records the total value of downlink signal level (TCH/H) of periodical
scannings.
Measurement Point
When the power control message is received and if the channel is TCH/H, then obtain the
downlink signal level in the message and accumulate.
Unit
Grade
Related Features

(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).
Measurement Point
When the power control message is received, if the channel is TCH/H and the message
Unit
Times
Related Features
38-39


(SDCCH) Search Result
Definition
Sum of Periodic DL Signal Level (SDCCH) Search Result
Description
This counter records the total value of downlink signal level (SDCCH) of periodical
scannings.
Measurement Point
When the power control message is received and if the channel is SDCCH, then obtain
the downlink signal level in the message and accumulate.
Unit
Grade
Related Features

(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 Point
When the power control message is received, if the channel is SDCCH and the message
Unit
Times
Related Features
38-40

Chapter 39
NSVC on IPGB HOST
Measurement
Table of Contents
Overview ..................................................................................................................39-1
C901330001 Time of PVC unavailable .....................................................................39-1
C901330002 Number of abnormal cases in NS transmission due to network fault....39-2
C901330003 Number of abnormal cases in NS transmission due to O&M
interference ..............................................................................................................39-2
C901330004 Number of abnormal cases in NS transmission due to equipment
fault ..........................................................................................................................39-2
C901330005 Number of abnormal cases in NS transmission due to unknown
NSVC.......................................................................................................................39-3
C901330006 Number of abnormal cases in NS transmission due to protocol error...39-3
C901330007 Number of unsuccess test due to over max .........................................39-4
39.1 Overview
The NSVC statistic measurement on IPGB HOST is used to measure signaling interaction
and data transmission at NS layer of Gb interface in GPRS service. It also performs
statistics for abnormalities in various flows.
39.2 C901330001 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 Point
The counter starts counting when NSVC link becomes abnormal and stops counting when
NSVC link becomes normal. The duration between the two time points is the time during
which NSVC is unavailable.
39-1

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
Description
Related Features

transmission due to O&M interference
Definition
Number of abnormal cases in NS transmission due to O&M interference
Description
Related Features

transmission due to equipment fault
Definition
Number of abnormal cases in NS transmission due to equipment fault
39-2

Chapter 39 NSVC on IPGB HOST Measurement
Description
Related Features

transmission due to unknown NSVC
Definition
Number of abnormal cases in NS transmission due to unknown NSVC
Description
unknown NSVC.
Measurement Point
During the NS sub layer signaling interaction, the counter accumulates the number of
signaling transmitted by unknown NSVC.
Unit
Times
Related Features

transmission due to protocol error
Definition
Number of abnormal cases in NS transmission due to protocol error
Description
protocol error.
39-3

Measurement Point
When the field in NS signaling is inconsistent with that defined in protocol, the counter
accumulates.
Unit
Times
Related Features
39.8 C901330007 Number of unsuccess test due to

over max
Definition
Number of unsuccess test due to over max
Description
being exceeded during the NS sub layer test procedure.
Measurement Point
When the number of NS sub layer's sending NS-ALIVE PDU exceeds the maximum
retransmission times NS-ALIVE-RETRIES and there is no response, the counter
Figure 39-1 TEST PROCEDURE BEING ABNORMAL
Unit
Times
39-4

Chapter 39 NSVC on IPGB HOST Measurement
Related Features
39-5

39-6

Chapter 40
GB Message on IPGB HOST
Measurement
Table of Contents
Overview ..................................................................................................................40-2
C901340001 Number of RA-CAPABILITY message recevied...................................40-2
C901340006 Number of wireless status PDU messages sent by BSC......................40-6
C901340007 Number of wireless status messages sent by BSC due to losing
wireless association with MS ....................................................................................40-7
C901340008 Number of wireless status messages sent by BSC due to bad link
quality ......................................................................................................................40-7
C901340009 Number of wireless status messages sent by BSC due to cell
reselection command ...............................................................................................40-8
C901340010 Number of FLOW-CONTROL-BVC messages sent by BSC ................40-9
C901340011 Number of FLOW-CONTROL-BVC-ACK messages received by BSC .40-9
C901340012 Number of FLOW-CONTROL-MS messages sent by BSC ................40-10
C901340013 Number of FLOW-CONTROL-MS-ACK messages received by BSC . 40-11
BSC .......................................................................................................................40-12
C901340016 Number of status messages sent by BSC .........................................40-13
C901340017 Number of status messages received by BSC ...................................40-14
C901340021 Number of status messages sent with Processor overload ................40-16
C901340022 Number of status messages received with BVCI Unknown................40-17
40-1


C901340033 Number of DELETE-BSS-PFC-ACK messages sent by BSC.............40-24
C901340034 Number of DELETE-BSS-PFC-REQ messages received by BSC......40-25
C901340035 Number of PS-HANDOVER-REQUIRED messages sent by BSC......40-25
C901340036 Number of PS-HANDOVER-REQUIRED-ACK messages received by
BSC .......................................................................................................................40-26
by BSC...................................................................................................................40-27
C901340038 Number of PS-HANDOVER-REQUEST messages received by BSC .40-28
C901340039 Number of PS-HANDOVER-REQUEST-ACK messages sent by
BSC .......................................................................................................................40-29
C901340040 Number of PS-HANDOVER-REQUEST-NACK messages sent by
BSC .......................................................................................................................40-30
C901340041 Number of PS-HANDOVER-COMPLETE messages sent by BSC.....40-32
C901340042 Number of PS-HANDOVER-CANCEL messages sent by BSC..........40-32
C901340043 Number of PS-HANDOVER-REQUEST messages with Service
UTRAN CCO received by BSC...............................................................................40-33
C901340044 Number of CREATE-BSS-PFC messages with Service UTRAN CCO
received by BSC ....................................................................................................40-34
40.1 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.
40.2 C901340001 Number of RA-CAPABILITY message

recevied
Definition
Number of RA-CAPABILITY message received
Description
SGSN sends the RA-CAPABILITY message to BSC to indicate the wireless capability of
MS. This counter counts the number of BSC's receiving this message.
Measurement Point
40-2

Chapter 40 GB Message on IPGB HOST Measurement
Figure 40-1 MEASUREMENT POINT OF THE NUMBER OF RECEIVING RA-CAPABILITY

MESSAGE
Unit
Times
Related Features

received 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 of BSC's receiving this message.
Measurement Point
point is A.
Figure 40-2 PTP PACKET PAGING PROCESS
Unit
Times
Related Features
40-3


received 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 of BSC's receiving this message.
Measurement Point
point is A.
Figure 40-3 PTP CIRCUIT PAGING PROCESS
Unit
Times
Related Features

message sent
Definition
Number of RA-CAPABILITY-UPDATE message sent
Description
BSC sends the RA-CAPABILITY-UPDATE message to SGSN to request for the current
wireless capability of MS. This counter counts the number of BSC's sending this message.
40-4

Measurement Point
Figure 40-4 RA-CAPABILITY-UPDATE PROCESS
Unit
Times
Related Features

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 the number of BSC's receiving this message.
Measurement Point
When BSC receives a RA-CAPABILITY-UPDATE-ACK message from SGSN, this
Figure 40-5 RA-CAPABILITY-UPDATE PROCESS
40-5

Unit
Times
Related Features
40.7 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 number of BSC's sending this message.
Usage
Measurement Point
Figure 40-6 RADIO-STATUS PROCESS
Unit
Times
Related Features
40-6


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
interface. This counter counts the number of BSC's sending this message due to Losing
Usage
Measurement Point
When BSC sends a RADIO-STATUS message to SGSN due to Losing wireless
association with MS, this counter increments.
Unit
Times
Related Features

sent by BSC due to bad link quality
Definition
Number of wireless status messages sent by BSC due to bad link quality
Description
interface. This counter counts the number of BSC's sending this message due to bad link
quality.
40-7

Usage
Measurement Point
counter increments.
Unit
Times
Related Features

sent by BSC due to cell reselection command
Definition
Number of wireless status messages sent by BSC due to cell reselection command
Description
interface. This counter counts the number of BSC's sending this message due to cell
Usage
Measurement Point
Unit
Times
Related Features
40-8


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
Measurement Point
When BSC sends a FLOW-CONTROL-BVC message, this counter increments. The
measuremnt point is A1.
Figure 40-7 FLOW-CONTROL-BVC PROCESS
Unit
Times
Related Features

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 counts the number of BSC's receiving
this message.
40-9

Measurement Point
The measurement point is A2.
Figure 40-8 FLOW-CONTROL-BVC PROCESS
Unit
Times
Related Features

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
Measurement Point
When BSC sends the FLOW-CONTROL-MS message, this counter increments. The
Figure 40-9 FLOW-CONTROL-MS PROCESS
40-10

Unit
Times
Related Features

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 counts the number of BSC's receiving this
message.
Measurement Point
When BSC receives a FLOW-CONTROL-MS-ACK message, this counter increments.
Figure 40-10 FLOW-CONTROL-MS PROCESS
Unit
Times
Related Features
40-11


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. This counter counts the number of BSC's
Measurement Point
When BSC sends the FLOW-CONTROL-PFC message, this counter increments. The
Figure 40-11 FLOW-CONTROL-PFC PROCESS
Unit
Times
Related Features

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

Measurement Point
Figure 40-12 FLOW-CONTROL-PFC PROCESS
Unit
Times
Related Features

by BSC
Definition
Number of status messages sent by BSC
Description
counts the number of BSC's sending this message.
Measurement Point
When BSC sends the STATUS message, this counter increments. The measurement
point is A1.
40-13

Unit
Times
Related Features

received by BSC
Definition
Number of status messages received by BSC
Description
counts the number of BSC's receiving this message.
Measurement Point
When BSC receives the STATUS message, this counter increments. The measurement
point is A2.
Unit
Times
Related Features
40-14


with BVCI Unknown
Definition
Description
counts the number of BSC's sending this message due to BVCI Unknown.
Measurement Point
When BSC sends a "STATUS" message due to BVCI Unknown, this counter increments.
Unit
Times
Related Features

Definition
Description
counts the number of BSC's sending this message due to cell service congestion.
Measurement Point
When BSC sends a "STATUS" message due to cell service congestion, this counter
increments.
Unit
Times
Related Features
40-15


with protocol error
Definition
Description
counts the number of BSC's sending this message due to protocol error.
Measurement Point
When BSC sends a "STATUS" message due to protocol error, this counter increments.
Unit
Times
Related Features

Definition
Number of status messages sent with Processor overload
Description
counts the number of BSC's sending this message due to processor overload.
Measurement Point
When BSC sends a "STATUS" message due to processor overload, this counter
increments.
Unit
Times
Related Features
40-16


Definition
Number of status messages received with BVCI Unknown
Description
counts the number of BSC's receiving this message due to BVCI Unknown.
Measurement Point
When BSC receives a "STATUS" message due to BVCI Unknown, this counter
increments.
Unit
Times
Related Features

Definition
Description
counts the number of BSC's receiving this message due to cell service congestion.
Measurement Point
When BSC receives a "STATUS" message due to cell service congestion, this counter
increments.
Unit
Times
Related Features
40-17


Definition
Description
counts the number of BSC's receiving this message due to protocol error.
Measurement Point
When BSC receives a "STATUS" message due to protocol error, this counter increments.
Unit
Times
Related Features

Definition
Description
counts the number of BSC's receiving this message due to processor overload.
Measurement Point
When BSC receives a "STATUS" message due to processor overload, this counter
increments.
Unit
Times
Related Features
40-18


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 number of BSC's sending this
message.
Measurement Point
When BSC sends the DOWNLOAD-BSS-PFC message, this counter increments. The
Figure 40-15 CREATE-BSS-PFC PROCESS
Unit
Times
Related Features

Definition
Number of BVCCREATE-BSS-PFC messages received by BSC
40-19

Description
SGSN sends the CREATE-BSS-PFC message to request BSC to create or modify a packet
flow control context. This counter counts the number of BSC's receiving this message.
Measurement Point
Unit
Times
Related Features

Definition
Number of CREATE-BSS-PFC-ACK messages sent by BSC
Description
BSC sends the CREATE-BSS-PFC-ACK message to acknowledge the request of SGSN
creating or modifying a packet flow control context. This counter counts the number of
BSC's sending this message.
Measurement Point
40-20

Unit
Times
Related Features

Definition
Number of CREATE-BSS-PFC-NACK messages sent by BSC
Description
BSC sends the CREATE-BSS-PFC-NACK message to deny the request of SGSN creating
or modifying a packet flow control context. This counter counts the number of BSC's
Measurement Point
40-21

Unit
Times
Related Features

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 number of BSC's sending this message.
Measurement Point
When BSC sends the MODIFY-BSS-PFC message, this counter increments. The
Figure 40-19 MODIFY-BSS-PFC PROCESS
40-22

Unit
Times
Related Features

Definition
Number of MODIFY-BSS-PFC-ACK messages received by BSC
Description
SGSN sends the MODIFY-BSS-PFC-ACK message to BSC to confirm the modification
of packet flow control context. This counter counts the number of BSC's receiving this
message.
Measurement Point
Figure 40-20 MODIFY-BSS-PFC PROCESS
Unit
Times
Related Features
40-23


Definition
Number of DELETE-BSS-PFC messages received by BSC
Description
SGSN sends the DELETE-BSS-PFC message to request BSC to delete a packet flow
control context. This counter counts the number of BSC's receiving this message.
Measurement Point
Figure 40-21 DELETE-BSS-PFC PROCESS
Unit
Times
Related Features
40.34 C901340033 Number of 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.
40-24

Measurement Point
Figure 40-22 DELETE-BSS-PFC PROCESS
Unit
Times
Related Features
40.35 C901340034 Number of DELETE-BSS-PFC-REQ

Definition
Number of DELETE-BSS-PFC-REQ messages received by BSC
Description
Related Features

ED messages sent by BSC
Statistics object
BSC
40-25

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
40-23.
Figure 40-23 Measurement Point of Number of PS-HANDOVER-REQUIRED messages

sent by BSC
Times

ED-ACK messages received by BSC
Statistics object
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. The measurement point is A, as shown in Figure 40-24.
40-26

Figure 40-24 Measurement Point of Number of PS-HANDOVER-REQUIRED-ACK

Times

ED-NACK messages received by BSC
Statistics object
BSC
Description
If SGSN receives the non-acknowledgement message for PS handover request from
BSC, then SGSN sends the PS-HANDOVER-REQUIRED-NACK message back to
BSC. This counter counts the number of PS-HANDOVER-REQUIRED-NACK messages
received by BSC in IP transmission mode. The counter increments when BSC receives
the PS-HANDOVER-REQUIRED-NACK message. The measurement point is A, as
40-27


Times

T messages received by BSC
Statistics object
BSC
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 messages received by BSC from SGSN. The
counter increments when BSC receives the PS-HANDOVER-REQUEST message. The
40-28


received by BSC
Times

ST-ACK messages sent by BSC
Statistics object
BSC
Description
After BSC receives the PS-HANDOVER-REQUEST message from SGSN, it implements
PS handover flow and sends the PS-HANDOVER-REQUEST message back to
SGSN. This counter counts the number of PS-HANDOVER-REQUEST messages
sent by BSC in IP transmission mode. The counter increments when BSC sends the
PS-HANDOVER-REQUEST-ACK message. The measurement point is A3, as shown in
Figure 40-27.
40-29

Figure 40-27 Measurement Point of Number of PS-HANDOVER-REQUEST-ACK

Times

T-NACK messages sent by BSC
Statistics object
BSC
40-30

Description
After BSC receives the PS-HANDOVER-REQUEST message from SGSN, it implements
PS handover flow. During the handover, if the channel request fails or the cell does
not support PS handover, then creating MS or PS instance will fail. This counter
counts the number of messages, which indicate failure of creating MS or PS instance,
sent by BSC in IP transmission mode. The counter increments when BSC sends the
PS-HANDOVER-REQUEST-NACK message. The measurement point is A3, as shown
in Figure 40-28.
Figure 40-28 Measurement Point of Number of PS-HANDOVER-REQUEST-NACK

Times
40-31

40.42 C901340041 Number of PS-HANDOVER-COMPLE

TE messages sent by BSC
Statistics object
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 increments when BSC sends the
PS-HANDOVER-REQUEST-COMPLETE message. The measurement point is A, as
Figure 40-29 Measurement Point of Number of PS-HANDOVER-COMPLETE messages

sent by BSC
Times
40.43 C901340042 Number of PS-HANDOVER-CANCEL

Statistics object
BSC
40-32

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
Figure 40-30 Measurement Point of Number of PS-HANDOVER-CANCEL messages

sent by BSC
Times

ST messages with Service UTRAN CCO received
by BSC
Statistics object
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 in IP transmission mode.
After BSC receives the PS-HANDOVER-REQUEST message from SGSN, it decodes the
40-33

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

Times
40.45 C901340044 Number of CREATE-BSS-PFC

messages with Service UTRAN CCO received by
BSC
Statistics object
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
40-34

Figure 40-32 Measurement Point of Number of CREATE-BSS-PFC messages with

Service UTRAN CCO received by BSC
Times
40-35

40-36

Chapter 41
NSE on IPGB HOST
Measurement
Table of Contents
Overview ..................................................................................................................41-2
C901350001 Number of CS Paging received by BSS...............................................41-2
C901350002 Number of PS Paging received by BSS...............................................41-3
C901350009 Number of FLUSH-LL message received ............................................41-7
C901350010 Number of FLUSH-LL-ACK message sent...........................................41-8
C901350011 Number of LLC-DISCARDED message sent .......................................41-8
C901350012 Number of BVC-BLOCK message sent ...............................................41-9
C901350013 Number of BVC_BLOCK_ACK message received.............................41-10
C901350014 Number of BVC-UNBLOCK message sent ........................................41-10
C901350015 Number of BVC-UNBLOCK-ACK message received ......................... 41-11
C901350016 Number of BVC-RESET message sent ............................................. 41-11
C901350017 Number of BVC-RESET message received.......................................41-12
C901350018 Number of BVC-RESET-ACK message sent .....................................41-13
C901350019 Number of BVC-RESET-ACK message received...............................41-13
C901350020 Number of PERFORM LOCATION-REQUEST message received...41-14
C901350021 Number of PERFORM-LOCATION-RESPONSE message sent ........41-15
C901350022 Number of PERFORM-LOCATION-ABORT message received .........41-15
C901350023 Number of POSITION-COMMAND message sent .............................41-16
C901350024 Number of POSITION-RESPONSE message received .....................41-17
C901350025 Number of status messages sent ......................................................41-17
C901350026 Number of status messages received................................................41-18
C901350030 Number of status messages sent with processor overload ................41-21
C901350031 Number of status messages sent with semantically incorrect PDU ....41-21
C901350032 Number of status messages sent with invalid mandatory information
element ..................................................................................................................41-22
41-1

C901350033 Number of status messages sent with missing mandatory IE.............41-23

C901350034 Number of status messages sent with missing conditional IE ............41-23
C901350035 Number of status messages sent with unexpected conditional IE ......41-24
C901350036 Number of status messages sent with conditional IE error.................41-25
C901350037 Number of status messages sent with protocol status incompatible
error .......................................................................................................................41-25
C901350038 Number of status messages received with BVCI unknown ................41-26
C901350042 Number of status messages received with BVC blocking...................41-29
C901350043 Number of status messages received with semantically incorrect
PDU .......................................................................................................................41-29
C901350044 Number of status messages received with invalid mandatory IE........41-30
C901350045 Number of status messages received with missing mandatory IE ......41-31
C901350046 Number of status messages received with missing conditional IE......41-31
C901350047 Number of status messages received with unexpected conditional
IE ...........................................................................................................................41-32
C901350048 Number of status messages received with conditional IE error ..........41-33
C901350049 Number of status messages received with protocol status
incompatible error ..................................................................................................41-33
C901350050 Number of status messages received with SGSN congestion............41-34
41.1 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.
Statistic unit in this measurement is the single NSE.
41.2 C901350001 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.
41-2

Chapter 41 NSE on IPGB HOST Measurement
Measurement Point
When BSS receives a message of which the type is GB_PAGING_CS, the counter
increments.
Unit
Times
Related Features
41.3 C901350002 Number of PS Paging received by

BSS
Definition
Number of PS Paging received by BSS
Description
This counter counts the number of PAGING PS messages received by NSE at BSC from
SGSN.
Usage
The counter is used to find out the frequency of SGSN's PS paging to MS.
Measurement Point
When BSS receives a message of which the type is GB_PAGING_PS, the counter
increments.
Unit
Times
Related Features

Definition
Number of SUSPEND message sent
41-3

Description
When BSS receives the suspending GPRS service message from MS, BSS will send the
SUSPEND message to SGSN. This counter counts the number of sending SUSPEND
message from NSE.
Usage
The counter is used to find out the frequency of MS's terminating GPRS service.
Measurement Point
When BSS sends the SUSPEND message, the counter increments.
Unit
Times
Related Features

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
Usage
The counter is used to find out cases in which SGSN has response when MS requests for
terminating GPRS service.
Measurement Point
When BSS sends the SUSPEND_ACK message, the counter increments.
Unit
Times
41-4

Related Features

received
Definition
Number of SUSPEND-NACK message received
Description
When SGSN receives the SUSPEND message from BSS, it checks the SUSPEND
message content. If the message content is incorrect or fault occurs at SGSN, SGSN
will send the SUSPEND_NACK message to BSS. This counter counts the number of
SUSPEND_NACK messages received by NSE.
Usage
for terminating GPRS service.
Measurement Point
When BSS sends the SUSPEND_NACK message, the counter increments.
Unit
Times
Related Features

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

Usage
The counter is used to find out the frequency of MS's resuming GPRS service.
Measurement Point
When BSS sends the RESUME message, the counter increments.
Unit
Times
Related Features

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
Usage
The counter is used to find out causes due to which SGSN has no response when MS
requests for resuming GPRS service.
Measurement Point
When BSS sends the RESUME_ACK message, the counter increments.
Unit
Times
Related Features
41-6


received
Definition
Number of RESUME-NACK message received
Description
If the MS in the RESUME PDU message sent from BSS is not found at SGSN, SGSN willl
send the RESUME_NACK message to BSS. This message contains the failure cause, that
is, unknown MS. At this moment, BSS will terminate the RESUME process and ask MS
to update routing area. This counter counts the number of RESUME_NACK messages
received by NSE.
Usage
for resuming GPRS service.
Measurement Point
When BSS receives the RESUME_NACK message, the counter increments.
Unit
Times
Related Features
41.10 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.
41-7

Measurement Point
When BSS receives the FLUSH_LL message, the counter increments.
Unit
Times
Related Features
41.11 C901350010 Number of 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 Point
When BSS sends the FLUSH_LL_ACK message, the counter increments.
Unit
Times
Related Features
41.12 C901350011 Number of LLC-DISCARDED

message sent
Definition
Number of LLC-DISCARDED message sent
41-8

Description
When the LLC PDU stored in BSS is deleted, the LLC_DISCARDED message is sent to
SGSN. This counter counts the number of sending LLC_DISCARDED message from NSE.
Usage
The counter is used to find out the storage of LLC PDU in BSS.
Measurement Point
When BSS sends the LLC_DISCARDED message, the counter increments.
Unit
Times
Related Features

sent
Definition
Description
When BSS blocks a BVC, it will send the BVC_BLOCK message to SGSN to start the
timer T1. BSS will identify the blocked BVC and stop sending uplink data of the BVC.
Meanwhile, cells associated with the BVC do not receive downlink data any more. This
counter counts the number of sending BVC_BLOCK message from NSE.
Usage
The counter is used to find out the frequency of BSS's requesting to block BVC.
Measurement Point
When BSS sends the BVC_BLOCK message, the counter increments.
Unit
Times
Related Features
41-9

41.14 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 identifies the BVC to be
blocked and stops sending data to the BVC, and replies the BVC_BLOCK_ACK message
to BSS. This counter counts the number of BVC_BLOCK_ACK messages received by
NSE.
Usage
The counter is used to find out cases when BVC is blocked.
Measurement Point
When BSS receives the BVC_BLOCK_ACK message, the counter increments.
Unit
Times
Related Features

sent
Definition
Description
When BSS unblocks the blocked BVC, it will send the BVC_UNBLOCK message to SGSN.
This counter counts the number of sending BVC_UNBLOCK message from NSE.
Usage
The counter is used to find out the frequency of BSS's requesting to unblock BVC.
Measurement Point
When BSS sends the BVC_UNBLOCK message, the counter increments.
41-10

Unit
Times
Related Features

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_UNBLOCK_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 Point
When BSS receives the BVC_BLOCK_ACK message, the counter increments.
Unit
Times
Related Features

sent
Definition
Description
This counter counts the number of PCU sending signaling BVC resetting message through
Gb interface.
41-11

Usage
The counter is used to find out the frequency of requesting to restart BVC due to BVC
failure.
Measurement Point
When NSE at BSC sends message of which the type is BVC_RESET and BVCI is zero,
Unit
Times
Related Features

received
Definition
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 Point
When NSE at BSC receives message of which the type is BVC_RESET and BVCI is zero,
Unit
Times
Related Features
41-12


message 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 signaling BVC resetting acknowledgement message.
Usage
The counter is used to find out cases of SGSN initializing BVC.
Measurement Point
When NSE at BSC sends message of which the type is BVC_RESET_ACK and BVCI is
zero, the counter increments.
Unit
Times
Related Features

message received
Definition
Number of BVC-RESET-ACK message received
Description
Number of PCU's receiving the signaling BVC resetting acknowledgement message. This
counter counts the number of NSE's receiving signaling BVC resetting acknowledgement
message.
Usage
The counter is used to find out cases of BVC initialization.
41-13

Measurement Point
When NSE at BSC receives message of which the type is BVC_RESET_ACK and BVCI
is zero, the counter increments.
Unit
Times
Related Features
41.21 C901350020 Number of PERFORM

LOCATION-REQUEST message received
Definition
Number of PERFORMLOCATION-REQUEST message received
Description
When SGSN receives the location request and BSS supports LCS, SGSN will start the
locating process and send PERFORM_LOCATION_REQUEST message to BSS. This
counter counts the number of BSS's receiving the location request message.
Usage
The counter is used to find out the frequency of SGSN's sending location request to BSS.
Measurement Point
increments.
Unit
Times
Related Features
41-14


ESPONSE message sent
Definition
Number of PERFORM_LOCATION_RESPONSE message sent
Description
After BSS receives the PERFORM_LOCATION_REQUEST message, it will send the
location request to SMLC and wait for SMLC's response, and then send the result in
the PERFORM_LOCATION_RESPONSE message to SGSN. This counter counts the
number of BSS's sending the location request response message.
Usage
The counter is used to find out BSS's response to the location request from SGSN.
Measurement Point
increments.
Unit
Times
Related Features
41.23 C901350022 Number of PERFORM-LOCATION-A

BORT message received
Definition
Number of PERFORM_LOCATION_ABORT message received
Description
When SGSN initiates the location request before interruption occurs, it sends the
PERFORM_LOCATION_ABORT message to BSS. This counter counts the number of
BSS's receiving the PERFORM_LOCATION_ABORT message.
Usage
The counter is used to find out the frequency of SGSN's terminating location towards BSS.
41-15

Measurement Point
increments.
Unit
Times
Related Features
41.24 C901350023 Number of POSITION-COMMAND

message sent
Definition
Number of POSITION_COMMAND message sent
Description
BSS triggers the positioning command process by sending POSITION_COMMAND
message to SGSN. This process is valid only when positioning a MS. This counter counts
the number of BSS's sending POSITION_COMMAND message.
Usage
The counter is used to find out the frequency of BSS's requesting to implement positioning
command to SGSN.
Measurement Point
When BSS sends the POSITION_COMMAND message, the counter increments.
Unit
Times
Related Features
41-16

41.25 C901350024 Number of POSITION-RESPONSE

message received
Definition
Number of POSITION_RESPONSE message received
Description
When SGSN receives the TOM message, SGSN will send the POSITION_RESPONSE
message to BSS to trigger the position response process. The TOM message is
contained in LLC PDU, and the LLC PDU contains the RRLP message of a MS. This
position response process is valid only when positioning a MS. This counter counts the
number of BSS's receiving the POSITION_RESPONSE message.
Usage
The counter is used to find out the frequency of SGSN's requesting to implement
positioning command to BSS.
Measurement Point
When BSS receives the POSITION_RESPONSE message, the counter increments.
Unit
Times
Related Features

Definition
Number of status messages sent
Description
When NSE receives downlink BSSGP PDU, if there is any abnormality, NSE will send
the STATUS message to the opposite end entity. The STATUS message sent indicates
causes of the abnormality: BVCI unknown, cell traffic congestion, Protocol error, Processor
overload, Semantically incorrect PDU, Invalid mandatory information, Missing mandatory
IE, or Missing conditional IE. This counter counts the number of abnormality that occurs.
41-17

Usage
The counter is used to find out abnormality occurring when NSE receives downlink BSSGP
PDU.
Measurement Point
When NSE at BSC sends message of which the type is STATUS to the opposite end entity,
Unit
Times
Related Features

received
Definition
Number of status messages received
Description
If the BSSGP PDU sent by NSE to SGSN is abnormal, NSE will receive the STATUS
message returned from the opposite end. The STATUS message returned indicates
causes of the abnormality: BVCI unknown, cell traffic congestion, Protocol error,
Processor overload, Semantically incorrect PDU, Invalid mandatory information, Missing
mandatory IE, or Missing conditional IE. This counter counts the number of STATUS
messages returned from SGSN.
Usage
The counter is used to find out abnormality occurring when SGSN receives downlink
BSSGP PDU.
Measurement Point
When NSE receives the STATUS message, the counter increments.
Unit
Times
Related Features
41-18


with BVCI Unknown
Definition
Description
the message indicating "BVCI unknown".
Usage
Measurement Point
that the abnormality is due to "BVCI unknown", the counter increments.
Unit
Times
Related Features

Definition
Description
the message indicating "cell traffic congestion".
Usage
41-19

Measurement Point
that the abnormality is due to "cell traffic congestion", the counter increments.
Unit
Times
Related Features

with protocol error
Definition
Description
the message indicating "Protocol error".
Usage
Measurement Point
that the abnormality is due to "Protocol error", the counter increments.
Unit
Times
Related Features
41-20


with processor overload
Definition
Number of status messages sent with processor overload
Description
the message indicating "Processor overload".
Usage
Measurement Point
that the abnormality is due to "Processor overload", the counter increments.
Unit
Times
Related Features

with semantically incorrect PDU
Definition
Number of status messages sent with semantically incorrect PDU
Description
the message indicating "Semantically incorrect PDU".
Usage
PDU" occurring when NSE receives downlink BSSGP PDU.
41-21

Measurement Point
that the abnormality is due to "Semantically incorrect PDU", the counter increments.
Unit
Times
Related Features

with invalid mandatory information element
Definition
Number of status messages sent with invalid mandatory information element
Description
the message indicating "Invalid mandatory information".
Usage
information" occurring when NSE receives downlink BSSGP PDU.
Measurement Point
that the abnormality is due to "Invalid mandatory information", the counter increments.
Unit
Times
Related Features
41-22


with missing mandatory IE
Definition
Number of status messages sent with missing mandatory IE
Description
the message indicating "Missing mandatory IE".
Usage
Measurement Point
that the abnormality is due to "Missing mandatory IE", the counter increments.
Unit
Times
Related Features

with missing conditional IE
Definition
Number of status messages sent with missing conditional IE
Description
the message indicating "Missing conditional IE".
Usage
41-23

Measurement Point
that the abnormality is due to "Missing conditional IE", the counter increments.
Unit
Times
Related Features

with unexpected conditional IE
Definition
Number of status messages sent with unexpected conditional IE
Description
the message indicating "Unexpected conditional IE".
Usage
Measurement Point
that the abnormality is due to "Unexpected conditional IE", the counter increments.
Unit
Times
Related Features
41-24


with conditional IE error
Definition
Number of status messages sent with conditional IE error
Description
the message indicating "Conditional IE error".
Usage
Measurement Point
that the abnormality is due to "Conditional IE error", the counter increments.
Unit
Times
Related Features

with protocol status incompatible error
Definition
Number of status messages sent with protocol status incompatible error
Description
the message indicating "PDU not compatible with the protocol state".
Usage
with the protocol state" occurring when NSE receives downlink BSSGP PDU.
41-25

Measurement Point
that the abnormality is due to "PDU not compatible with the protocol state", the counter
increments.
Unit
Times
Related Features

received 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".
Usage
Measurement Point
When PCU receives STATUS message which indicates "BVCI unknown", the counter
increments.
Unit
Times
Related Features
41-26


Definition
Description
message indicating "cell traffic congestion".
Usage
Measurement Point
When PCU receives STATUS message which indicates "cell traffic congestion", the
counter increments.
Unit
Times
Related Features

Definition
Description
This counter counts the number of received STATUS messages which indicate "Protocol
error".
Usage
41-27

Measurement Point
When PCU receives STATUS message which indicates "Protocol error", the counter
increments.
Unit
Times
Related Features

Definition
Description
message indicating "Processor overload".
Usage
Measurement Point
When PCU receives STATUS message which indicates "Processor overload", the counter
increments.
Unit
Times
Related Features
41-28


received with BVC blocking
Definition
Number of status messages received with BVC blocking
Description
message indicating "BVCI-blocked".
Usage
The counter is used to find out the frequency of abnormality due to "BVCI-blocked"
Measurement Point
When PCU receives STATUS message which indicates "BVCI-blocked", the counter
increments.
Unit
Times
Related Features

received with semantically incorrect PDU
Definition
Number of status messages received with semantically incorrect PDU
Description
"Semantically incorrect PDU".
Usage
PDU" occurring when SGSN receives downlink BSSGP PDU.
41-29

Measurement Point
When PCU receives STATUS message which indicates "Semantically incorrect PDU", the
counter increments.
Unit
Times
Related Features

received with invalid mandatory IE
Definition
Number of status messages received with invalid mandatory IE
Description
This counter counts the number of received STATUS messages which indicate "Invalid
mandatory information".
Usage
information" occurring when SGSN receives downlink BSSGP PDU.
Measurement Point
When PCU receives STATUS message which indicates "Invalid mandatory information",
Unit
Times
Related Features
41-30


received with missing mandatory IE
Definition
Number of status messages received with missing mandatory IE
Description
mandatory IE".
Usage
Measurement Point
When PCU receives STATUS message which indicates "Missing mandatory IE", the
counter increments.
Unit
Times
Related Features

received with missing conditional IE
Definition
Number of status messages received with missing conditional IE
Description
conditional IE".
Usage
41-31

Measurement Point
When PCU receives STATUS message which indicates "Missing conditional IE", the
counter increments.
Unit
Times
Related Features

received with unexpected conditional IE
Definition
Number of status messages received with unexpected conditional IE
Description
"Unexpected conditional IE".
Usage
Measurement Point
When PCU receives STATUS message which indicates "Unexpected conditional IE", the
counter increments.
Unit
Times
Related Features
41-32


received with conditional IE error
Definition
Number of status messages received with conditional IE error
Description
"Conditional IE error".
Usage
Measurement Point
When PCU receives STATUS message which indicates "Conditional IE error", the counter
increments.
Unit
Times
Related Features

received with protocol status incompatible error
Definition
Number of status messages received with protocol status incompatible error
Description
This counter counts the number of received STATUS messages which indicate "PDU not
compatible with the protocol state".
Usage
with the protocol state" occurring when SGSN receives downlink BSSGP PDU.
41-33

Measurement Point
When PCU receives STATUS message which indicates "PDU not compatible with the
protocol state", the counter increments.
Unit
Times
Related Features

received with SGSN congestion
Definition
Number of status messages received with SGSN congestion
Description
message indicating "SGSN congestion".
Usage
The counter is used to find out the frequency of abnormality due to "SGSN congestion"
Measurement Point
When PCU receives STATUS message which indicates "SGSN congestion", the counter
increments.
Unit
Times
Related Features
41-34

Chapter 42
BSSMAP Message
Measurement
Table of Contents
Overview ..................................................................................................................42-3
C901360001 Number of ASSIGNMENT REQUEST messages ................................42-4
C901360002 Number of ASSIGNMENT COMPLETE messages ..............................42-4
C901360003 Number of ASSIGNMENT FAILURE messages...................................42-5
C901360004 Number of RESOURCE REQUEST messages....................................42-6
C901360005 Number of RESOURCE INDICATION messages ................................42-7
C901360006 Number of PAGING messages ............................................................42-8
C901360007 Number of CIPHER MODE COMMAND messages .............................42-8
C901360008 Number of CIPHER MODE COMPLETE messages ............................42-9
C901360009 Number of CIPHER MODE REJECT messages ................................42-10
C901360010 Number of sent CLASSMARK UPDATE messages ........................... 42-11
C901360011 Number of received CLASSMARK UPDATE messages.....................42-12
C901360012 Number of QUEUING INDICATION messages ..................................42-12
C901360013 Number of COMPLETE LAYER 3 INFORMATION messages............42-13
C901360014 Number of CLASSMARK REQUEST messages................................42-14
C901360015 Number of uplink LOAD INDICATION messages...............................42-15
C901360016 Number of downlink LOAD INDICATION messages ..........................42-16
C901360017 Number of HANDOVER REQUEST messages..................................42-16
C901360018 Number of HANDOVER REQUIRED messages ................................42-17
C901360019 Number of HANDOVER COMMAND messages ................................42-18
C901360020 Number of HANDOVER REQUEST ACK messages .........................42-19
C901360021 Number of HANDOVER COMPLETE messages ...............................42-20
C901360022 Number of HANDOVER SUCCEEDED messages ............................42-21
C901360023 Number of HANDOVER CANDIDATE ENQUIRE messages..............42-22
C901360024 Number of HANDOVER CANDIDATE RESPONSE messages ..........42-23
C901360025 Number of HANDOVER FAILURE messages ....................................42-24
C901360026 Number of HANDOVER PERFORMED messages ............................42-25
C901360027 Number of HANDOVER REQUIRED REJECT messages .................42-25
C901360028 Number of HANDOVER DETECT messages ....................................42-26
C901360029 Number of CLEAR COMMAND messages ........................................42-27
C901360030 Number of CLEAR COMPLETE messages .......................................42-28
C901360031 Number of CLEAR REQUEST messages..........................................42-28
C901360032 Number of SAPI "N" REJECT messages...........................................42-29
C901360033 Number of UL CONFUSION messages.............................................42-30
42-1

C901360034 Number of DL CONFUSION messages.............................................42-31

C901360035 Number of UL RESET messages ......................................................42-32
C901360036 Number of DL RESET messages ......................................................42-32
C901360037 Number of UL RESET ACKNOWLEDGE messages..........................42-33
C901360038 Number of DL RESET ACKNOWLEDGE messages..........................42-34
C901360039 Number of UL OVERLOAD messages ..............................................42-35
C901360040 Number of DL OVERLOAD messages ..............................................42-35
C901360041 Number of MSC INVOKE TRACE messages ....................................42-36
C901360042 Number of sent BSS INVOKE TRACE messages..............................42-37
C901360043 Number of received BSS INVOKE TRACE messages .......................42-38
C901360044 Number of sent CONNECTIONLESS INFORMATION messages ......42-39
C901360045 Number of received CONNECTIONLESS INFORMATION
messages...............................................................................................................42-39
C901360046 Number of SUSPEND messages ......................................................42-40
C901360047 Number of RESUME messages ........................................................42-41
C901360048 Number of Common ID messages.....................................................42-42
C901360049 Number of LSA INFORMATION messages .......................................42-42
C901360050 Number of PERFORM LOCATION REQUEST messages .................42-43
C901360051 Number of PERFORM LOCATION RESPONSE messages...............42-44
C901360052 Number of PERFORM LOCATION ABORT messages ......................42-45
C901360053 Number of sent BLOCK messages....................................................42-45
C901360054 Number of received BLOCK ACK messages .....................................42-46
C901360055 Number of sent UNBLOCK messages...............................................42-47
C901360056 Number of received UNBLOCK ACK messages ................................42-48
C901360057 Number of received BLOCK messages .............................................42-49
C901360058 Number of sent BLOCK ACK messages............................................42-49
C901360059 Number of received UNBLOCK messages ........................................42-50
C901360060 Number of sent UNBLOCK ACK messages.......................................42-51
C901360061 Number of UL RESET CIRCUIT messages .......................................42-52
C901360062 Number of DL RESET CIRCUIT messages .......................................42-53
C901360063 Number of UL RESET CIRCUIT ACK messages...............................42-53
C901360064 Number of DL RESET CIRCUIT ACK messages...............................42-54
C901360065 Number of UL CIRCUIT GROUP BLOCK messages .........................42-55
C901360066 Number of DL CIRCUIT GROUP BLOCK messages .........................42-56
C901360067 Number of UL CIRCUIT GROUP BLOCKING ACKNOWLEDGE
messages...............................................................................................................42-57
C901360068 Number of DL CIRCUIT GROUP BLOCKING ACKNOWLEDGE
messages...............................................................................................................42-58
C901360069 Number of UL CIRCUIT GROUP UNBLOCK messages ....................42-58
C901360070 Number of DL CIRCUIT GROUP UNBLOCK messages ....................42-59
C901360071 Number of UL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE
messages...............................................................................................................42-60
C901360072 Number of DL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE
messages...............................................................................................................42-61
C901360073 Number of UL UNEQUIPPED CIRCUIT messages ...........................42-62
42-2

Chapter 42 BSSMAP Message Measurement
C901360074 Number of DL UNEQUIPPED CIRCUIT messages ...........................42-63

C901360075 Number of CHANGE CIRCUIT messages .........................................42-63
C901360076 Number of CHANGE CIRCUIT ACK messages .................................42-64
C901360077 Number of HANDOVER PERFORMED ACK messages ....................42-65
C901360078 The count of Sending INTERNAL HANDOVER REQUIRED..............42-66
C901360079 The count of Receiving INTERNAL HANDOVER COMMAND ...........42-68
C901360080 The count of Receiving INTERNAL HANDOVER REJECT ................42-70
C901360081 Number of INTERNAL HANDOVER ENQUIRY messages ................42-70
C901360082 Number of UL RESET IP RESOURCE messages .............................42-71
C901360083 Number of UL RESET IP RESOURCE ACKOWNLEDGE messages .42-72
C901360084 Number of DL RESET IP RESOURCE messages .............................42-73
C901360085 Number of DL RESET IP RESOURCE ACKNOWLEDGE messages .42-73
42.1 Overview
The BSSMAP message measurement performs statistics for various BSSMAP messages
at A-interface. It is used to find out the frequency of various BSSMAP messages
transmitted at A-interface. When BSC receives the correct BSSMAP message from MSC,
the counter counts. The measurement point is A
Figure 42-1 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 42-2 MEASUREMENT POINT OF BSC SENDING BSSMAP MESSAGE TO MSC
Statistic unit in this measurement is Control Main Processor (CMP).
42-3

42.2 C901360001 Number of 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. During the paging process, MSC can also
change mode at radio interface through the ASSIGNMENT REQUEST message. This
counter counts the number of assignment request messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of assignment request messages transmitted
at A-interface.
Measurement Point
When BSC receives the ASSIGNMENT REQUEST message, the counter increments. The
Figure 42-3 MEASUREMENT POINT OF BSC RECEIVING ASSIGNMENT REQUEST

MESSAGE FROM MSC
Unit
Times
42.3 C901360002 Number of ASSIGNMENT COMPLETE

messages
Definition
Number of ASSIGNMENT COMPLETE messages
42-4

Description
During the mode modification (assignment) flow, after BSC receives the RR message
ASSIGNMENT COMPLETE from Um interface, it sends an ASSIGNMENT COMPLETE
message of A-interface BSSMAP protocol to MSC. This counter counts the number of
assignment completion messages in A-interface BSSMAP messages sent to MSC from
BSC.
Usage
The counter is used to find out the frequency of assignment completion messages
transmitted at A-interface.
Measurement Point
When BSC sends the ASSIGNMENT COMPLETE message to MSC, the counter
Figure 42-4 MEASUREMENT POINT OF BSC SENDING ASSIGNMENT COMPLETE

MESSAGE TO MSC
Unit
Times
42.4 C901360003 Number of 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.
42-5

Measurement Point
When BSC sends the ASSIGNMENT FAILURE message to MSC, the counter increments.
The measurement point is A
Figure 42-5 MEASUREMENT POINT OF BSC SENDING ASSIGNMENT FAILURE

MESSAGE TO MSC
Unit
Times
42.5 C901360004 Number of RESOURCE REQUEST

messages
Definition
Number of RESOURCE REQUEST messages
Description
MSC sends the RESOURCE REQUEST message to BSC, the message indicating the
mode of reporting resource condition to BSC and relevant cell IDs. This counter counts
the number of resource request messages in A-interface BSSMAP messages received by
BSC.
Usage
The counter is used to find out the frequency of resource request messages transmitted
at A-interface.
Measurement Point
When BSC receives the RESOURCE REQUEST message, the counter increments. The
42-6

Figure 42-6 MEASUREMENT POINT OF MSC SENDING RESOURCE REQUEST

MESSAGE TO BSC
Unit
Times
42.6 C901360005 Number of RESOURCE INDICATION

messages
Definition
Number of RESOURCE INDICATION messages
Description
After BSC receives the RESOURCE REQUEST message from MSC, it sends the
RESOURCE INDICATION message to MSC according to MSC's requirement. The
message contains the current resource usage of relevant cells. This counter counts the
number of resource indication messages in A-interface BSSMAP messages sent to MSC
from BSC.
Usage
The counter is used to find out the frequency of resource indication messages transmitted
at A-interface.
Measurement Point
When BSC sends the RESOURCE INDICATION message to MSC, the counter
Figure 42-7 MEASUREMENT POINT OF BSC SENDING RESOURCE INDICATION

MESSAGE TO MSC
42-7

Unit
Times
42.7 C901360006 Number of PAGING messages

Definition
Number of PAGING messages
Description
When MSC needs to page a MS, it sends a PAGING message to BSC through A-interface.
This counter counts the number of paging messages in A-interface BSSMAP messages
received by BSC.
Usage
The counter is used to find out the frequency of paging messages transmitted at
A-interface.
Measurement Point
When BSC receives the PAGING message, the counter increments. The measurement
point is A.
Figure 42-8 MEASUREMENT POINT OF MSC SENDING PAGING MESSAGE TO BSC
Unit
Times
42.8 C901360007 Number of CIPHER MODE COMMAND

messages
Definition
Number of CIPHER MODE COMMAND messages
42-8

Description
When MSC decides to modify the cipher mode of channel, it sends a CIPHER MODE
COMMAND message to BSC through A-interface. This counter counts the number of
CIPHER MODE COMMAND messages in A-interface BSSMAP messages received by
BSC.
Usage
The counter is used to find out the frequency of CIPHER MODE COMMAND messages
Measurement Point
When BSC receives the CIPHER MODE COMMAND message, the counter increments.
The measurement point is A.
Figure 42-9 MEASUREMENT POINT OF MSC SENDING CIPHER MODE COMMAND

MESSAGE TO BSC
Unit
Times
42.9 C901360008 Number of 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 in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of CIPHER MODE COMPLETE messages
42-9

Measurement Point
When BSC sends the CIPHER MODE COMPLETE message to MSC, the counter
Figure 42-10 MEASUREMENT POINT OF BSC SENDING CIPHER MODE COMPLETE

MESSAGE TO MSC
Unit
Times
42.10 C901360009 Number of CIPHER MODE REJECT

messages
Definition
Number of CIPHER MODE REJECT messages
Description
After BSC receives the CIPHERing MODE REJECT message (RR message at Um
interface) from MS , it sends the CIPHER MODE REJECT message at A-interface to MSC
as response. This counter counts the number of CIPHER MODE REJECT messages in
A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of CIPHER MODE REJECT messages
Measurement Point
When BSC sends the CIPHER MODE REJECT message to MSC, the counter increments.
42-10

Figure 42-11 MEASUREMENT POINT OF BSC SENDING CIPHER MODE REJECT

MESSAGE TO MSC
Unit
Times
42.11 C901360010 Number of 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
Usage
The counter is used to find out the sending frequency of CLASSMARK UPDATE messages
Measurement Point
When BSC sends the CLASSMARK UPDATE message to MSC, the counter increments.
Figure 42-12 MEASUREMENT POINT OF BSC SENDING CLASSMARK UPDATE

MESSAGE TO MSC
42-11

Unit
Times
42.12 C901360011 Number of received CLASSMARK

UPDATE messages
Definition
Number of received CLASSMARK UPDATE messages
Description
This counter counts the number of CLASSMARK UPDATE messages in A-interface
BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of receiving CLASSMARK UPDATE
messages transmitted at A-interface.
Measurement Point
When BSC receives the CLASSMARK UPDATE message, the counter increments. The
Figure 42-13 MEASUREMENT POINT OF MSC SENDING CLASSMARK UPDATE

MESSAGE TO BSC
Unit
Times
42.13 C901360012 Number of QUEUING INDICATION

messages
Definition
Number of QUEUING INDICATION messages
42-12

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 A-interface BSSMAP messages sent to
MSC from BSC.
Usage
The counter is used to find out the frequency of QUEUING INDICATION messages
Measurement Point
When BSC sends the QUEUING INDICATION message to MSC, the counter increments.
Figure 42-14 MEASUREMENT POINT OF BSC SENDING QUEUING INDICATION

MESSAGE TO MSC
Unit
Times
42.14 C901360013 Number of COMPLETE LAYER 3

INFORMATION messages
Definition
Number of COMPLETE LAYER 3 INFORMATION messages
Description
This counter counts the number of COMPLETE LAYER 3 INFORMATION messages in
Usage
The counter is used to find out the frequency of COMPLETE LAYER 3 INFORMATION
42-13

Measurement Point
When BSC sends the COMPLETE LAYER 3 INFORMATION message to MSC, the counter
Figure 42-15 MEASUREMENT POINT OF BSC SENDING COMPLETE LAYER 3

INFORMATION MESSAGE TO MSC
Unit
Times
42.15 C901360014 Number of CLASSMARK REQUEST

messages
Definition
Number of CLASSMARK REQUEST messages
Description
When MSC wants MS classmark information, it sends a CLASSMARK REQUEST
message to BSC. This counter counts the number of CLASSMARK REQUEST messages
in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of CLASSMARK REQUEST messages
Measurement Point
When BSC receives the CLASSMARK REQUEST message, the counter increments. The
42-14

Figure 42-16 MEASUREMENT POINT OF MSC SENDING CLASSMARK REQUEST

MESSAGE TO BSC
Unit
Times
42.16 C901360015 Number of uplink LOAD INDICATION

messages
Definition
Number of uplink LOAD INDICATION messages
Description
According to certain principle, such as reporting periodically or reporting when triggered
by threshold being exceeded, BSC reports the current load of cells under it to MSC. After
MSC receives the message, it forwards the message to other relevant BSCs. This counter
counts the number of load indication messages in A-interface BSSMAP messages sent to
MSC from BSC.
Usage
The counter is used to find out the frequency of uplink load indication messages transmitted
at A-interface.
Measurement Point
When BSC sends the LOAD INDICATION message to MSC, the counter increments. The
Figure 42-17 MEASUREMENT POINT OF BSC SENDING LOAD INDICATION MESSAGE

TO MSC
42-15

Unit
Times
42.17 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
Usage
The counter is used to find out the frequency of downlink load indication messages
Measurement Point
When BSC receives the LOAD INDICATION message, the counter increments. The
Figure 42-18 MEASUREMENT POINT OF MSC SENDING LOAD INDICATION MESSAGE

TO BSC
Unit
Times
42.18 C901360017 Number of HANDOVER REQUEST

messages
Definition
Number of HANDOVER REQUEST messages
42-16

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 messages received by BSC.
Usage
The counter is used to find out the frequency of handover request messages transmitted
at A-interface.
Measurement Point
When BSC receives the HANDOVER REQUEST message, the counter increments. The
Figure 42-19 MEASUREMENT POINT OF MSC SENDING HANDOVER REQUEST

MESSAGE TO BSC
Unit
Times
42.19 C901360018 Number of HANDOVER REQUIRED

messages
Definition
Number of HANDOVER REQUIRED messages
Description
When BSC decides to initiate an inter-BSC handover, it sends a HANDOVER REQUIRED
message to the MSC to which it belongs, the message containing information of the target
cell of handover. This counter counts the number of HANDOVER REQUIRED messages
in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of HANDOVER REQUIRED messages
42-17

Measurement Point
When BSC sends the HANDOVER REQUIRED message to MSC, the counter increments.
Figure 42-20 INTER-BSC HANDOVER PROCESS INITIATED BY BSC
Unit
Times
42.20 C901360019 Number of 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 HANDOVER COMMAND messages in A-interface
Usage
The counter is used to find out the frequency of HANDOVER COMMAND messages
42-18

Measurement Point
When BSC receives the HANDOVER COMMAND message, the counter increments. The
Unit
Times
42.21 C901360020 Number of HANDOVER REQUEST

ACK messages
Definition
Number of HANDOVER REQUEST ACK messages
Description
MSC sends a HANDOVER REQUEST message to the target BSS to request channel
resource for handover. If the target BSS successfully allocates and activates channel,
then BSC puts a Um interface RR message HANDOVER COMMAND in the HANDOVER
REQUEST ACK message and returns the message to MSC. This counter counts the
number of HANDOVER REQUEST ACK messages in A-interface BSSMAP messages
sent to MSC from BSC.
Usage
The counter is used to find out the frequency of HANDOVER REQUEST ACK messages
42-19

Measurement Point
When BSC sends the HANDOVER REQUEST ACK message to MSC, the counter
Unit
Times
42.22 C901360021 Number of 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
Usage
The counter is used to find out the frequency of HANDOVER COMPLETE messages
Measurement Point
When BSC sends the HANDOVER COMPLETE message to MSC, the counter increments.
42-20

Unit
Times
42.23 C901360022 Number of 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
Usage
The counter is used to find out the frequency of HANDOVER SUCCEEDED messages
Measurement Point
When BSC receives the HANDOVER SUCCEEDED message, the counter increments.
42-21

Unit
Times
42.24 C901360023 Number of HANDOVER CANDIDATE

ENQUIRE messages
Definition
Number of HANDOVER CANDIDATE ENQUIRE messages
Description
MSC sends a HANDOVER CANDIDATE ENQUIRY message to the BSC to which the
cell belongs. The message contains the maximum number of handover requests that
can be triggered and candidate cells that can be used for handover. This counter counts
the number of HANDOVER CANDIDATE ENQUIRE messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of HANDOVER CANDIDATE ENQUIRE
Measurement Point
When BSC receives the HANDOVER CANDIDATE ENQUIRE message, the counter
42-22

Figure 42-25 PROCESS OF MSC SENDING HANDOVER CANDIDATE ENQUIRE

MESSAGE TO BSC
Unit
Times
42.25 C901360024 Number of HANDOVER CANDIDATE

RESPONSE messages
Definition
Number of HANDOVER CANDIDATE RESPONSE messages
Description
After BSC receives the HANDOVER CANDIDATE ENQUIRE message, it initiates
handover process for specified calls of the cell, that is, BSC sends corresponding
HANDOVER REQUIRED messages to MSC. After all HANDOVER REQUIRED messages
are sent, BSC notifies MSC of the number of triggered handover through the HANDOVER
CANDIDATE RESPONSE message.
This counter counts the number of HANDOVER CANDIDATE RESPONSE messages in
Usage
The counter is used to find out the frequency of HANDOVER CANDIDATE RESPONSE
Measurement Point
When BSC sends the HANDOVER CANDIDATE RESPONSE message to MSC, the
42-23

Figure 42-26 PROCESS OF MSC SENDING HANDOVER CANDIDATE ENQUIRE

MESSAGE TO BSC
Unit
Times
42.26 C901360025 Number of HANDOVER FAILURE

messages
Definition
Number of HANDOVER FAILURE messages
Description
This counter counts the number of HANDOVER FAILURE messages in A-interface
BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of HANDOVER FAILURE messages
Measurement Point
When BSC sends the HANDOVER FAILURE message to MSC, the counter increments.
Figure 42-27 MEASUREMENT POINT OF BSC SENDING HANDOVER FAILURE

MESSAGE TO MSC
Unit
Times
42-24

42.27 C901360026 Number of HANDOVER PERFORMED

messages
Definition
Number of HANDOVER PERFORMED messages
Description
After BSC performs a handover (intra-cell or inter-cell) within itself, it sends a HANDOVER
PERFORMED messge to MSC. This counter counts the number of HANDOVER
PERFORMED messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of HANDOVER PERFORMED messages
Measurement Point
When BSC sends the HANDOVER PERFORMED message to MSC, the counter
Figure 42-28 MEASUREMENT POINT OF BSC SENDING HANDOVER PERFORMED

MESSAGE TO MSC
Unit
Times
42.28 C901360027 Number of HANDOVER REQUIRED

REJECT messages
Definition
Number of HANDOVER REQUIRED REJECT messages
Description
This counter counts the number of HANDOVER REQUIRED REJECT messages in
42-25

Usage
The counter is used to find out the frequency of HANDOVER REQUIRED REJECT
Measurement Point
When BSC receives the HANDOVER REQUIRED REJECT message, the counter
Figure 42-29 MEASUREMENT POINT OF MSC SENDING HANDOVER REQUIRED

REJECT MESSAGE TO BSC
Unit
Times
42.29 C901360028 Number of HANDOVER DETECT

messages
Definition
Number of HANDOVER DETECT messages
Description
This counter counts the number of HANDOVER DETECT messages in A-interface
Usage
The counter is used to find out the frequency of HANDOVER DETECT messages
Measurement Point
When BSC sends the HANDOVER DETECT message to MSC, the counter increments.
42-26

Figure 42-30 MEASUREMENT POINT OF BSC SENDING HANDOVER DETECT

MESSAGE TO MSC
Unit
Times
42.30 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
Usage
The counter is used to find out the frequency of CLEAR COMMAND messages transmitted
at A-interface.
Measurement Point
When BSC receives the CLEAR COMMAND message, the counter increments. The
Figure 42-31 CLEAR PROCESS
Unit
Times
42-27

42.31 C901360030 Number of CLEAR COMPLETE

messages
Definition
Number of CLEAR COMPLETE messages
Description
After BSC receives the CLEAR COMMAND message, it starts corresponding release
process and returns the CLEAR COMPLETE message to MSC. This counter counts the
number of CLEAR COMPLETE messages in A-interface BSSMAP messages sent to
MSC from BSC.
Usage
The counter is used to find out the frequency of CLEAR COMPLETE messages transmitted
at A-interface.
Measurement Point
When BSC sends the CLEAR COMPLETE message to MSC, the counter increments. The
Figure 42-32 CLEAR PROCESS
Unit
Times
42.32 C901360031 Number of CLEAR REQUEST

messages
Definition
Number of CLEAR REQUEST messages
42-28

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
Usage
The counter is used to find out the frequency of CLEAR REQUEST messages transmitted
at A-interface.
Measurement Point
When BSC sends the CLEAR REQUEST message to MSC, the counter increments. The
Figure 42-33 MEASUREMENT POINT OF BSC SENDING CLEAR REQUEST MESSAGE

TO MSC
Unit
Times
42.33 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 A-interface BSSMAP
Usage
The counter is used to find out the frequency of SAPI "N" REJECT messages transmitted
at A-interface.
42-29

Measurement Point
When BSC sends the SAPI "N" REJECT message to MSC, the counter increments. The
Figure 42-34 MEASUREMENT POINT OF BSC SENDING SAPI "N" REJECT MESSAGE
TO MSC
Unit
Times
42.34 C901360033 Number of UL 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
Usage
The counter is used to find out the frequency of uplink CONFUSION messages transmitted
at A-interface.
Measurement Point
When BSC sends the CONFUSION message to MSC, the counter increments. The
42-30

Figure 42-35 MEASUREMENT POINT OF BSC SENDING CONFUSION MESSAGE TO

MSC
Unit
Times
42.35 C901360034 Number of DL 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
Usage
The counter is used to find out the frequency of downlink CONFUSION messages
Measurement Point
When BSC receives the CONFUSION message, the counter increments. The
Figure 42-36 MEASUREMENT POINT OF MSC SENDING CONFUSION MESSAGE TO

BSC
Unit
Times
42-31

42.36 C901360035 Number of UL 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 messages in A-interface BSSMAP messages
sent to MSC from BSC.
Usage
The counter is used to find out the frequency of uplink RESET messages transmitted at
A-interface.
Measurement Point
When BSC sends the RESET message to MSC, the counter increments. The
Figure 42-37 UPLINK RESET PROCESS
Unit
Times
42.37 C901360036 Number of DL 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 messages in A-interface BSSMAP messages
received by BSC.
42-32

Usage
The counter is used to find out the frequency of downlink RESET messages transmitted
at A-interface.
Measurement Point
When BSC receives the RESET message, the counter increments. The measurement
point is A1.
Figure 42-38 DOWNLINK RESET PROCESS
Unit
Times
42.38 C901360037 Number of UL RESET

ACKNOWLEDGE messages
Definition
Number of UL RESET ACKNOWLEDGE messages
Description
When MSC detects that it has serious global fault, it will send a RESET message to
BSC. After BSC receives the message, it releases all calls and relevant information, and
after a period of time, it returns the RESET ACKNOWLEDGE message as response.
This counter counts the number of RESET ACKNOWLEDGE messages in A-interface
Usage
The counter is used to find out the frequency of uplink RESET ACKNOWLEDGE messages
Measurement Point
When BSC sends the RESET ACKNOWLEDGE message to MSC, the counter increments.
42-33

Figure 42-39 DOWNLINK RESET PROCESS
Unit
Times
42.39 C901360038 Number of DL RESET

Definition
Number of DL RESET ACKNOWLEDGE messages
Description
When BSC detects that it has serious global fault, it will send a RESET message to
MSC. After MSC receives the message, it releases all calls and relevant information, and
after a period of time, it returns the RESET ACKNOWLEDGE message as response.
This counter counts the number of RESET ACKNOWLEDGE messages in A-interface
Usage
The counter is used to find out the frequency of downlink RESET ACKNOWLEDGE
Measurement Point
When BSC receives the RESET ACKNOWLEDGE message, the counter increments. The
Figure 42-40 UPLINK RESET PROCESS
42-34

Unit
Times
42.40 C901360039 Number of UL 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
Usage
The counter is used to find out the frequency of uplink OVERLOAD messages transmitted
at A-interface.
Measurement Point
When BSC sends the OVERLOAD message to MSC, the counter increments. The
Figure 42-41 MEASUREMENT POINT OF BSC SENDING OVERLOAD MESSAGE TO MSC
Unit
Times
42.41 C901360040 Number of DL OVERLOAD

messages
Definition
Number of DL OVERLOAD messages
42-35

Description
When MSC detects that its processor is overloaded, it will send the OVERLOAD message
to the BSC under it. If the overload problem persists, MSC will send the OVERLOAD
message to BSC periodically. This counter counts the number of OVERLOAD messages
Usage
The counter is used to find out the frequency of downlink OVERLOAD messages
Measurement Point
When BSC receives the OVERLOAD message, the counter increments. The
Figure 42-42 MEASUREMENT POINT OF MSC SENDING OVERLOAD MESSAGE TO BSC
Unit
Times
42.42 C901360041 Number of 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 corresponding BSC to trigger tracing actions. This
counter counts the number of MSC INVOKE TRACE messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of MSC INVOKE TRACE messages
42-36

Measurement Point
When BSC receives the MSC INVOKE TRACE message, the counter increments. The
Figure 42-43 MEASUREMENT POINT OF MSC SENDING MSC INVOKE TRACE

MESSAGE TO BSC
Unit
Times
42.43 C901360042 Number of sent BSS INVOKE TRACE

messages
Definition
Number of sent BSS INVOKE TRACE messages
Description
When BSC needs to generate tracing records of specified calls for MSC, it will send a
BSS INVOKE TRACE message to the corresponding MSC to trigger tracing actions. This
counter counts the number of BSS INVOKE TRACE messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of sending BSS INVOKE TRACE messages
Measurement Point
When BSC sends the BSS INVOKE TRACE message to MSC, the counter increments.
42-37

Figure 42-44 MEASUREMENT POINT OF BSC SENDING BSS INVOKE TRACE

MESSAGE TO MSC
Unit
Times
42.44 C901360043 Number of received BSS INVOKE

TRACE messages
Definition
Number of received BSS INVOKE TRACE messages
Description
This counter counts the number of BSS INVOKE TRACE messages in A-interface
Usage
The counter is used to find out the frequency of receiving BSS INVOKE TRACE messages
Measurement Point
When BSC receives the BSS INVOKE TRACE message, the counter increments. The
Figure 42-45 MEASUREMENT POINT OF MSC SENDING BSS INVOKE TRACE

MESSAGE TO BSC
Unit
Times
42-38

42.45 C901360044 Number of sent CONNECTIONLESS

INFORMATION messages
Definition
Number of sent CONNECTIONLESS INFORMATION messages
Description
This counter counts the number of CONNECTIONLESS INFORMATION messages in
A-interface BSSMAP messages sent by BSC.
Usage
The counter is used to find out the frequency of sending CONNECTIONLESS
INFORMATION messages transmitted at A-interface.
Measurement Point
When BSC sends the CONNECTIONLESS INFORMATION message to MSC, the counter
Figure 42-46 MEASUREMENT POINT OF BSC SENDING CONNECTIONLESS

INFORMATION MESSAGE TO MSC
Unit
Times
42.46 C901360045 Number of received

CONNECTIONLESS INFORMATION messages
Definition
Number of received CONNECTIONLESS INFORMATION messages
Description
This counter counts the number of CONNECTIONLESS INFORMATION messages in
42-39

Usage
The counter is used to find out the frequency of receiving CONNECTIONLESS
INFORMATION messages transmitted at A-interface.
Measurement Point
When BSC receives the CONNECTIONLESS INFORMATION message, the counter
Figure 42-47 MEASUREMENT POINT OF MSC SENDING CONNECTIONLESS

INFORMATION MESSAGE TO BSC
Unit
Times
42.47 C901360046 Number of 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
Usage
The counter is used to find out the frequency of SUSPEND messages transmitted at
A-interface.
Measurement Point
When BSC sends the SUSPEND message to MSC, the counter increments. The
42-40

Figure 42-48 MEASUREMENT POINT OF BSC SENDING SUSPEND MESSAGE TO MSC
Unit
Times
42.48 C901360047 Number of 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 transmitted at
A-interface.
Measurement Point
When BSC sends the RESUME message to MSC, the counter increments. The
Figure 42-49 MEASUREMENT POINT OF BSC SENDING RESUME MESSAGE TO MSC
Unit
Times
42-41

42.49 C901360048 Number of Common ID messages

Definition
Number of Common ID messages
Description
This counter counts the number of Common ID messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of Common ID messages transmitted at
A-interface.
Measurement Point
When BSC receives the Common ID message, the counter increments. The measurement
point is A.
Figure 42-50 MEASUREMENT POINT OF MSC SENDING COMMON ID MESSAGE TO

BSC
Unit
Times
42.50 C901360049 Number of LSA INFORMATION

messages
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
42-42

Usage
The counter is used to find out the frequency of LSA INFORMATION messages transmitted
at A-interface.
Measurement Point
When BSC receives the LSA INFORMATION message, the counter increments. The
Figure 42-51 MEASUREMENT POINT OF MSC SENDING LSA INFORMATION MESSAGE

TO BSC
Unit
Times
42.51 C901360050 Number of PERFORM LOCATION

REQUEST messages
Definition
Number of PERFORM LOCATION REQUEST messages
Description
This counter counts the number of PERFORM LOCATION REQUEST messages in
Usage
The counter is used to find out the frequency of PERFORM LOCATION REQUEST
Measurement Point
When BSC receives the PERFORM LOCATION REQUEST message, the counter
42-43

Figure 42-52 PROCESS OF MSC SENDING PERFORM LOCATION REQUEST MESSAGE

TO BSC
Unit
Times

RESPONSE messages
Definition
Number of PERFORM LOCATION RESPONSE messages
Description
This counter counts the number of PERFORM LOCATION RESPONSE messages in
Usage
The counter is used to find out the frequency of PERFORM LOCATION RESPONSE
Measurement Point
When BSC sends the PERFORM LOCATION RESPONSE message to MSC, the counter
Figure 42-53 PROCESS OF MSC SENDING PERFORM LOCATION REQUEST MESSAGE

TO BSC
42-44

Unit
Times

ABORT messages
Definition
Number of PERFORM LOCATION ABORT messages
Description
This counter counts the number of PERFORM LOCATION ABORT messages in
Usage
The counter is used to find out the frequency of PERFORM LOCATION ABORT messages
Measurement Point
When BSC receives the PERFORM LOCATION ABORT message, the counter
Figure 42-54 MEASUREMENT POINT OF MSC SENDING PERFORM LOCATION ABORT

MESSAGE TO BSC
Unit
Times
42.54 C901360053 Number of sent BLOCK messages

Definition
Number of sent BLOCK messages
42-45

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
Usage
The counter is used to find out the frequency of sending BLOCK messages transmitted at
A-interface.
Measurement Point
When BSC sends the BLOCK message to MSC, the counter increments. The
Figure 42-55 PROCESS OF BSC SENDING BLOCK MESSAGE TO MSC
Unit
Times
42.55 C901360054 Number of received BLOCK ACK

messages
Definition
Number of received BLOCK ACK messages
Description
When BSC decides to block a terrestrial circuit of A-interface, it sends a BLOCK message
to MSC. MSC performs appropriate handling and returns a BLOCK ACK message as
response. This counter counts the number of BLOCK ACK messages in A-interface
Usage
The counter is used to find out the frequency of receiving BLOCK ACK messages
42-46

Measurement Point
When BSC receives the BLOCK ACK message, the counter increments. The
Figure 42-56 PROCESS OF BSC SENDING BLOCK MESSAGE TO MSC
Unit
Times
42.56 C901360055 Number of sent 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
Usage
The counter is used to find out the frequency of sending UNBLOCK messages transmitted
at A-interface.
Measurement Point
When BSC sends the UNBLOCK message to MSC, the counter increments. The
42-47

Figure 42-57 PROCESS OF BSC SENDING UNBLOCK MESSAGE TO MSC
Unit
Times
42.57 C901360056 Number of 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
Usage
The counter is used to find out the frequency of receiving UNBLOCK ACK messages
Measurement Point
When BSC receives the UNBLOCK ACK message, the counter increments. The
Figure 42-58 PROCESS OF BSC SENDING UNBLOCK MESSAGE TO MSC
42-48

Unit
Times
42.58 C901360057 Number of 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
Usage
The counter is used to find out the frequency of receiving BLOCK messages transmitted
at A-interface.
Measurement Point
When BSC receives the BLOCK message, the counter increments. The measurement
point is A1.
Figure 42-59 PROCESS OF MSC SENDING BLOCK MESSAGE TO BSC
Unit
Times
42.59 C901360058 Number of sent BLOCK ACK

messages
Definition
Number of sent BLOCK ACK messages
42-49

Description
When MSC decides to block a terrestrial circuit of A-interface, it sends a BLOCK message
to BSC. BSC performs appropriate handling and returns a BLOCK ACK message as
response. This counter counts the number of BLOCK ACK messages in A-interface
Usage
The counter is used to find out the frequency of sending BLOCK ACK messages
Measurement Point
When BSC sends the BLOCK ACK message to MSC, the counter increments. The
Figure 42-60 PROCESS OF MSC SENDING BLOCK MESSAGE TO BSC
Unit
Times
42.60 C901360059 Number of received UNBLOCK

messages
Definition
Number of received UNBLOCK messages
Description
When MSC decides to unblock a terrestrial circuit of A-interface, it sends a UNBLOCK
message to BSC. This counter counts the number of UNBLOCK messages in A-interface
Usage
The counter is used to find out the frequency of receiving UNBLOCK messages transmitted
at A-interface.
42-50

Measurement Point
When BSC receives the UNBLOCK message, the counter increments. The measurement
point is A1.
Figure 42-61 PROCESS OF MSC SENDING UNBLOCK MESSAGE TO BSC
Unit
Times
42.61 C901360060 Number of sent 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
Usage
The counter is used to find out the frequency of sending UNBLOCK ACK messages
Measurement Point
When BSC sends the UNBLOCK ACK message to MSC, the counter increments. The
42-51

Figure 42-62 PROCESS OF MSC SENDING UNBLOCK MESSAGE TO BSC
Unit
Times
42.62 C901360061 Number of UL RESET CIRCUIT

messages
Definition
Number of UL RESET CIRCUIT messages
Description
When BSC detects that an abnormal SCCP connection release causes a circuit to become
idle, it sends a RESET CIRCUIT message to MSC. This counter counts the number of
RESET CIRCUIT messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of uplink RESET CIRCUIT messages
Measurement Point
When BSC sends the RESET CIRCUIT message to MSC, the counter increments. The
Figure 42-63 PROCESS OF BSC SENDING RESET CIRCUIT MESSAGE TO MSC
42-52

Unit
Times
42.63 C901360062 Number of DL RESET CIRCUIT

messages
Definition
Number of DL RESET CIRCUIT messages
Description
When MSC detects that an abnormal SCCP connection release causes a circuit to become
idle, it sends a RESET CIRCUIT message to BSC. This counter counts the number of
RESET CIRCUIT messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of downlink RESET CIRCUIT messages
Measurement Point
When BSC receives the RESET CIRCUIT message, the counter increments. The
Figure 42-64 PROCESS OF MSC SENDING RESET CIRCUIT MESSAGE TO BSC
Unit
Times
42.64 C901360063 Number of UL RESET CIRCUIT ACK

messages
Definition
Number of UL RESET CIRCUIT ACK messages
42-53

Description
When MSC detects that an abnormal SCCP connection release causes a circuit to become
idle, it sends a RESET CIRCUIT message to BSC. After BSC receives the message, it
clears relevant calls and makes corresponding circuits to become idle, and sends a RESET
CIRCUIT ACK message to MSC. This counter counts the number of RESET CIRCUIT ACK
Usage
The counter is used to find out the frequency of uplink RESET CIRCUIT ACK messages
Measurement Point
When BSC sends the RESET CIRCUIT ACK message to MSC, the counter increments.
Figure 42-65 PROCESS OF MSC SENDING RESET CIRCUIT MESSAGE TO BSC
Unit
Times
42.65 C901360064 Number of DL RESET CIRCUIT ACK

messages
Definition
Number of DL RESET CIRCUIT ACK messages
Description
When BSC detects that an abnormal SCCP connection release causes a circuit to become
idle, it sends a RESET CIRCUIT message to MSC. After MSC receives the message, it
clears relevant calls and makes corresponding circuits to become idle, and sends a RESET
CIRCUIT ACK message to BSC. This counter counts the number of RESET CIRCUIT ACK
messages in A-interface BSSMAP messages received by BSC.
42-54

Usage
The counter is used to find out the frequency of downlink RESET CIRCUIT ACK messages
Measurement Point
When BSC receives the RESET CIRCUIT ACK message, the counter increments. The
Figure 42-66 PROCESS OF BSC SENDING RESET CIRCUIT MESSAGE TO MSC
Unit
Times
42.66 C901360065 Number of UL 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
Measurement Point
When BSC sends the CIRCUIT GROUP BLOCK message to MSC, the counter
42-55

Figure 42-67 PROCESS OF BSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO MSC
Unit
Times
42.67 C901360066 Number of DL CIRCUIT GROUP

BLOCK messages
Definition
Number of DL CIRCUIT GROUP BLOCK messages
Description
When MSC decides to block some terrestrial circuits of A-interface and these terrestrial
circuits can be described in one message, 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
Measurement Point
When BSC receives the CIRCUIT GROUP BLOCK message, the counter increments. The
Figure 42-68 PROCESS OF MSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO BSC
42-56

Unit
Times

BLOCKING ACKNOWLEDGE messages
Definition
Number of UL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages
Description
When MSC decides to block some terrestrial circuits of A-interface and these terrestrial
circuits can be described in one message, 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 messages in A-interface BSSMAP
Usage
The counter is used to find out the frequency of uplink CIRCUIT GROUP BLOCKING
ACKNOWLEDGE messages transmitted at A-interface.
Measurement Point
When BSC sends the CIRCUIT GROUP BLOCKING ACKNOWLEDGE message to MSC,
Figure 42-69 PROCESS OF MSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO BSC
Unit
Times
42-57


BLOCKING ACKNOWLEDGE messages
Definition
Number of DL CIRCUIT GROUP BLOCKING ACKNOWLEDGE 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. 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 messages in A-interface
Usage
The counter is used to find out the frequency of downlink CIRCUIT GROUP BLOCKING
Measurement Point
When BSC receives the CIRCUIT GROUP BLOCKING ACKNOWLEDGE message, the
Figure 42-70 PROCESS OF BSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO MSC
Unit
Times

UNBLOCK messages
Definition
Number of UL CIRCUIT GROUP UNBLOCK messages
42-58

Description
When BSC decides to unblock some terrestrial circuit of A-interface, it sends a CIRCUIT
GROUP UNBLOCK message to MSC. This counter counts the number of CIRCUIT
GROUP UNBLOCK messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter is used to find out the frequency of uplink CIRCUIT GROUP UNBLOCK
Measurement Point
When BSC sends the CIRCUIT GROUP UNBLOCK message to MSC, the counter
Figure 42-71 PROCESS OF BSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE

TO MSC
Unit
Times

UNBLOCK messages
Definition
Number of DL CIRCUIT GROUP UNBLOCK messages
Description
When MSC decides to unblock some terrestrial circuit of A-interface, it sends a CIRCUIT
GROUP UNBLOCK message to BSC. This counter counts the number of CIRCUIT
GROUP UNBLOCK messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of downlink CIRCUIT GROUP UNBLOCK
42-59

Measurement Point
When BSC receives the CIRCUIT GROUP UNBLOCK message, the counter increments.
Figure 42-72 PROCESS OF MSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE

TO BSC
Unit
Times

UNBLOCKING ACKNOWLEDGE messages
Definition
Number of UL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages
Description
When MSC decides to unblock some terrestrial circuit of A-interface, it sends a CIRCUIT
GROUP UNBLOCK message to BSC. After BSC performs appropriate handlings, it
returns a CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message as response.
This counter counts the number of CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE
Usage
The counter is used to find out the frequency of uplink CIRCUIT GROUP UNBLOCKING
Measurement Point
When BSC sends the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message to
MSC, the counter increments. The measurement point is A2.
42-60

Figure 42-73 PROCESS OF MSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE

TO BSC
Unit
Times

UNBLOCKING ACKNOWLEDGE messages
Definition
Number of DL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages
Description
When BSC decides to unblock some terrestrial circuit of A-interface, it sends a CIRCUIT
GROUP UNBLOCK message to MSC. After MSC performs appropriate handlings, it
returns a CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message as response.
This counter counts the number of CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE
messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of downlink CIRCUIT GROUP UNBLOCKING
Measurement Point
When BSC receives the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message,
42-61

Figure 42-74 PROCESS OF BSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE

TO MSC
Unit
Times
42.74 C901360073 Number of UL 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 messages in A-interface BSSMAP messages sent to MSC from
BSC.
Usage
The counter is used to find out the frequency of uplink UNEQUIPPED CIRCUIT messages
Measurement Point
When BSC sends the UNEQUIPPED CIRCUIT message to MSC, the counter increments.
Figure 42-75 MEASUREMENT POINT OF BSC SENDING UNEQUIPPED CIRCUIT

MESSAGE TO MSC
42-62

Unit
Times
42.75 C901360074 Number of DL 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 messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of downlink UNEQUIPPED CIRCUIT
Measurement Point
When BSC receives the UNEQUIPPED CIRCUIT message, the counter increments. The
Figure 42-76 MEASUREMENT POINT OF MSC SENDING UNEQUIPPED CIRCUIT

MESSAGE TO BSC
Unit
Times
42.76 C901360075 Number of CHANGE CIRCUIT

messages
Definition
Number of CHANGE CIRCUIT messages
42-63

Description
When A-interface terrestrial circuits are allocated only by BSC, if MSC wants to perform
circuit handover for a call connection, MSC will send a CHANGE CIRCUIT message to
BSC and release the circuit at the same time. This counter counts the number of CHANGE
CIRCUIT messages in A-interface BSSMAP messages received by BSC.
Usage
The counter is used to find out the frequency of CHANGE CIRCUIT messages transmitted
at A-interface.
Measurement Point
When BSC receives the CHANGE CIRCUIT message, the counter increments. The
Figure 42-77 PROCESS OF MSC SENDING CHANGE CIRCUIT MESSAGE TO BSC
Unit
Times
42.77 C901360076 Number of 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 circuit at the same time. After BSC receives the message, it selects
a new circuit being occupied that satisfies requirement, sends the circuit information in the
CHANGE CIRCUIT ACK message to MSC, and releases the circuit.
This counter counts the number of CHANGE CIRCUIT ACK messages in A-interface
42-64

Usage
The counter is used to find out the frequency of CHANGE CIRCUIT ACK messages
Measurement Point
When BSC sends the CHANGE CIRCUIT ACK message to MSC, the counter increments.
Figure 42-78 PROCESS OF MSC SENDING CHANGE CIRCUIT MESSAGE TO BSC
Unit
Times
42.78 C901360077 Number of 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 messages in A-interface
Usage
The counter is used to find out cases of BSC receiving the HANDOVER PERFORMED
ACK message from MSC.
Measurement Point
When BSC receives the HANDOVER PERFORMED ACK message from MSC, the counter
increments.
42-65

Unit
Times
42.79 C901360078 The count of Sending INTERNAL

HANDOVER REQUIRED
Statistics object
CELL
Description
This counter counts the number of internal handover requests sent to MSC from BSC. The
Times
42-66

Figure 42-79 Measurement Point of the Count of Sending INTERNAL HANDOVER

REQUIRED
Reference
3GPP TS 48008
42-67

42.80 C901360079 The count of Receiving INTERNAL

HANDOVER COMMAND
Statistics object
CELL
Description
This counter counts the number of internal handover commands sent to BSC from MSC.
Times
42-68

Figure 42-80 Measurement Point of the Count of Receiving INTERNAL HANDOVER

COMMAND
Reference
3GPP TS 48008
42-69

42.81 C901360080 The count of Receiving INTERNAL

HANDOVER REJECT
Statistics object
CELL
Description
This counter counts the number of internal handover rejections sent to BSC from MSC.
Times
Figure 42-81 Measurement Point of the Count of Receiving INTERNAL HANDOVER

REJECT
Reference
3GPP TS 48008
42.82 C901360081 Number of INTERNAL HANDOVER

ENQUIRY messages
Statistics object
CELL
42-70

Description
This counter counts the number of INTERNAL HANDOVER ENQUIRY messages sent by
MSC. On TCH/F or TCH/H, when BSC receives the INTERNAL HANDOVER ENQUIRY
message from MSC, the counter increments. The measurement point is A1, as shown in
Figure 42-82.
Figure 42-82 OMCR Initiating IP Resource Resetting Flow
Unit
Times
42.83 C901360082 Number of UL RESET IP RESOURCE

messages
Statistics object
CELL
Description
This counter counts the number of IP resource resettings initiated by BSC towards MSC.
OMCR initiates the IP resource resetting request, and the IPRSCRST module initiates
the IP resource resetting request towards MSC through the ADispatch module. When the
ADispatch module receives the IP resource resetting request from the IPRSCRST module,
42-71

Unit
Times
42.84 C901360083 Number of UL RESET IP RESOURCE

ACKOWNLEDGE messages
Statistics object
CELL
Description
This counter counts the number of IP resource resetting response messages sent to MSC
from BSC. MSC initiates IP resource resetting towards BSC, and the IPRSCRST module
at OMP sends IP resource resetting response to MSC through the ADispatch module.
When the ADispatch module receives the IP resource resetting response, the counter
Figure 42-84 MSC Initiating IP Resource Resetting Flow
Unit
Times
42-72

42.85 C901360084 Number of DL RESET IP RESOURCE

messages
Statistics object
CELL
Description
This counter counts the number of IP resource resetting requests initiated by MSC towards
BSC. MSC initiates the IP resource resetting requests towards the IPRSCRST module
through the ADispatch module. When the ADispatch module receives the IP resource
resetting request from MSC, the counter increments. The measurement point is A, as
Figure 42-85 MSC Initiating IP Resource Resetting Flow
Unit
Times
Reference
3GPP TS 48008
42.86 C901360085 Number of DL RESET IP RESOURCE

Statistics object
CELL
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
42-73

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
42-74

Chapter 43
A-Interface Message
Measurement
Table of Contents
Overview ..................................................................................................................43-1
C901370001 Number of UL DTAP messages...........................................................43-1
C901370002 Number of DL DTAP messages...........................................................43-2
C901370003 Number of UL BSSMAP messages .....................................................43-3
C901370004 Number of DL BSSMAP messages .....................................................43-3
C901370005 Number of DL BSSMAP messages received with error .......................43-4
C901370006 Number of chosen for MSC Load share by NULL_NRI ........................43-5
C901370007 Number of chosen for MSC Load share by the NRI not in the MSC
pool ..........................................................................................................................43-5
43.1 Overview
The A-interface message measurement performs statistics for uplink/downlink DTAP
message, BSSMAP message, and received incorrect BSSMAP message. Statistic unit
in this measurement is CMP.
43.2 C901370001 Number of UL 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 RESPONSE messages in

Usage
The counter analyzes the frequency of uplink DTAP messages transmitted at A-interface.
43-1

Measurement Point
The counter counts when BSC sends the DTAP message to MSC. The measurement point
is A.
Figure 43-1 MEASUREMENT POINT OF BSC SENDING A-INTERFACE DTAP MESSAGE

TO MSC
Unit
Times
43.3 C901370002 Number of DL 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 transmitted at
A-interface.
Measurement Point
The counter counts when BSC receives the Connection Indication message, Connection
Confirm message, Disconnection Indication message, or Data Indication message, these
messages containing DTAP message. The measurement point is A.
Figure 43-2 MEASUREMENT POINT OF MSC SENDING A-INTERFACE DTAP MESSAGE

TO BSC
43-2

Chapter 43 A-Interface Message Measurement
Unit
Times
43.4 C901370003 Number of UL BSSMAP messages

Definition
Number of UL BSSMAP messages
Description
This counter counts the number of messages containing BSSMAP message sent to
MSC from BSC. BSC can carry the uplink BSSMAP message in the Connection Request
message, Data Request message, or UnitData Request message.
Usage
The counter analyzes the frequency of uplink BSSMAP messages transmitted at
A-interface.
Measurement Point
The counter counts when BSC sends the Connection Request message, Data Request
message, or UnitData Request message to MSC, these messages containing BSSMAP
message. The measurement point is A.
Figure 43-3 MEASUREMENT POINT OF BSC SENDING A-INTERFACE BSSMAP

MESSAGE TO MSC
Unit
Times
43.5 C901370004 Number of DL BSSMAP messages

Definition
Number of DL BSSMAP messages
43-3

Description
This counter counts the number of BSSMAP messages received by BSC from MSC.
MSC can carry the BSSMAP message in the Connection Indication message, Connection
Confirm message, Data Indication message, and UnitData Indication message.
Usage
The counter analyzes the frequency of downlink BSSMAP messages transmitted at
A-interface.
Measurement Point
The counter counts when BSC receives the Connection Indication message, Connection
Confirm message, Data Indication message, or UnitData Indication message, these
messages containing BSSMAP message. The measurement point is A.
Figure 43-4 MEASUREMENT POINT OF BSC RECEIVING A-INTERFACE BSSMAP

MESSAGE FROM MSC
Unit
Times
43.6 C901370005 Number of DL BSSMAP messages

received with error
Definition
Number of DL BSSMAP messages received with error
Description
This counter counts the number of incorrect BSSMAP messages received by BSC from
MSC. Such incorrect BSSMAP messages include L3 message with zero length, BSSMAP
message of which the length does not match the length of its contained L3 message,
decoding error, or messge type error.
Usage
The counter analyzes the frequency of received incorrect BSSMAP messages transmitted
at A-interface.
43-4

Chapter 43 A-Interface Message Measurement
Measurement Point
The counter counts when BSC receives incorrect BSSMAP message.
Unit
Times
43.7 C901370006 Number of 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
Usage
This counter is used to find out the frequency that the original serving MSC in the pool
allocates NULL_NRI to MS to make a MSC actively shares the load.
Measurement Point
The counter counts when iBSC chooses an appropriate MSC route for MS access.
Unit
Times
43.8 C901370007 Number of 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
43-5

Usage
This counter is used to find out the frequency of a MSC's sharing load due to MS accessing
the network through NRI which is not of the MSC.
Measurement Point
The counter counts when iBSC chooses an appropriate MSC route for MS access.
Unit
Times
43-6

Chapter 44
Terrestrial Resource
Availability Measurement
Table of Contents
Overview ..................................................................................................................44-1
C901380001 Mean number of available trunk circuits...............................................44-2
C901380002 Mean number of unavailable trunk circuits...........................................44-2
C901380003 Maximum number of busy trunk circuits...............................................44-3
C901380004 Busy time of trunk circuit .....................................................................44-3
C901380005 Congestion time of trunk circuit ...........................................................44-4
C901380006 Mean number of available UDP port ....................................................44-4
C901380007 Mean number of unavailable UDP port ................................................44-5
C901380008 Number of allocation AIPB board success ...........................................44-5
C901380009 Number of allocation AIPB board failure ..............................................44-6
C901380010 Maximum number of seizure UDP port ................................................44-7
C901380011 Number of successful one time request UDP port to AIPB...................44-8
C901380012 Number of successful two time request UDP port to AIPB ...................44-9
C901380013 Number of successful three time request UDP port to AIPB ..............44-10
C901380014 Number of failure request UDP port to AIPB...................................... 44-11
C901380015 Seizure duration of UDP port.............................................................44-12
C901380019 Mean number of busy trunk circuits ...................................................44-12
C901380020 Mean number of seizure UDP port ....................................................44-14
44.1 Overview
The terrestrial resource availability measurement performs statistics for the availability of
terrestrial resource at A-interface, including the average number of available BSC trunk
circuits, the average number of unavailable BSC trunk circuits, the maximum number of
busy trunk circuits, the total busy time of BSC trunk circuits, 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.
44-1

44.2 C901380001 Mean number 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 Point
The counter counts when system periodically queries database for circuit information.
Unit
Times
44.3 C901380002 Mean number 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 occupied and the number of circuits being blocked.
Usage
The counter reflects the current trunk circuit usage.
Measurement Point
Unit
Times
44-2

Chapter 44 Terrestrial Resource Availability Measurement
44.4 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 Point
There are three measurement points for the maximum number of busy trunk circuits.
l 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.
l 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.
l During periodical measurement, if the maximum number of busy trunk circuits
exceeds the recorded value, then the counter's value is updated.
Unit
Times
44.5 C901380004 Busy time of trunk circuit

Definition
Busy time of trunk circuit
Description
This counter counts the total time of all trunk circuits being occupied during the
measurement period.
Usage
The counter reflects the busy condition of trunk circuits.
Measurement Point
There are three measurement points for the busy time of trunk circuits.
44-3

l Before the trunk circuit is occupied successfully, the counter calculates the
occupation time and accumulates.
l Before the trunk circuit is released, the counter calculates the occupation time and
accumulates.
l During periodical measurement, the counter calculates the occupation time and
accumulates.
Unit
Second
44.6 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 Point
There are three measurement points for the congestion time of trunk circuits.
l Before the trunk circuit is attempted to be occupied, if the congestion identifier is set,
then the counter calculates the congestion time and accumulates.
l Before the trunk circuit is released, if the congestion identifier is set, then the counter
calculates the congestion time and accumulates.
l During periodical measurement, if the congestion identifier is set, then the counter
calculates the congestion time and accumulates.
Unit
Second
44.7 C901380006 Mean number of available UDP port

Definition
Mean number of available UDP port
Description
This counter counts the average number of available UDP ports.
44-4

Usage
The counter is used to find out the average number of available UDP ports.
Measurement Point
Unit
Times
Related Features
44.8 C901380007 Mean number 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.
Measurement Point
Unit
Times
Related Features
44.9 C901380008 Number of allocation AIPB board

success
Definition
Number of allocation AIPB board success
44-5

Description
This counter counts the number of allocating AIPB board successfully. The RANCS
module receives the EV_RANUMC_RADIO_APPLY message and requests AIPB
resource from database. If the request succeeds, the counter accumulates.
Usage
The counter is used to find out the frequency of allocating AIPB board successfully.
Measurement Point
When the request of AIPB board from database is returned successfully, the counter
accumulates. The measurement point is A.
Figure 44-1 REQUESTING RESOURCE FROM DATABASE SUCCESSFULLY
Unit
Times
Related Features
44.10 C901380009 Number of allocation AIPB board

failure
Definition
Number of allocation AIPB board failure
Description
This counter counts the number of AIPB board allocation failure. The RANCS module
receives the EV_RANUMC_RADIO_APPLY messge and requests AIPB resource from
database. If the request fails, the counter accumulates.
Usage
The counter is used to find out the frequency of AIPB board allocation failure.
44-6

Measurement Point
When the request of AIPB board from database fails, the counter accumulates. The
Figure 44-2 REQUESTING RESOURCE FROM DATABASE FAILURE
Unit
Times
Related Features
44.11 C901380010 Maximum number of seizure UDP

port
Definition
Maximum number of seizure UDP port
Description
This counter counts the maximum number of UDP ports being occupied.
Usage
The counter is used to find out the maximum number of UDP ports being occupied.
Measurement Point
l 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.
l 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.
l During periodical measurement, if the maximum number of busy UDP ports exceeds
the recorded value, then the counter's value is updated.
44-7

Unit
Times
Related Features
44.12 C901380011 Number of 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 message, and after
requesting database for AIPB resource successfully, it sends the connection request to
the connection module.
When BSC receives the correct EV_RANCONN_IPA_CONN_ACK message from the
connection module, if the number of times of requesting UDP port is only one, then the
Usage
The counter is used to find out the frequency of successfully requesting AIPB board for
UDP port through only one request.
Measurement Point
When the connection succeeds and the requesting AIPB board for UDP port succeeds
through only one request, the counter accumulates. The measurement point is A
44-8

Unit
Times
Related Features
44.13 C901380012 Number of successful two time

Definition
Number of successful two time request UDP port to AIPB
Description
through two requests.
connection module, if the number of times of requesting UDP port is two, then the counter
accumulates.
Usage
UDP port through two requests.
Measurement Point
after two requests, the counter accumulates. The measurement point is A.
44-9

Unit
Times
Related Features
44.14 C901380013 Number of successful three time

Definition
Number of successful three time request UDP port to AIPB
Description
through three requests.
connection module, if the number of times of requesting UDP port is three, then the
Usage
UDP port through three requests.
Measurement Point
after three requests, the counter accumulates. The measurement point is A.
44-10

Unit
Times
Related Features
44.15 C901380014 Number of 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 requesting UDP port failure, the counter
accumulates.
Usage
The counter is used to find out the frequency of failing to request AIPB board for UDP port.
Measurement Point
When the connection failure message is returned, the counter accumulates. The
Figure 44-6 REQUESTING RESOURCE FROM DATABASE FAILURE
Unit
Times
44-11

Related Features
44.16 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.
Measurement Point
l Before UDPPort is occupied successfully, the counter calculates the occupation
l Before UDPPort is released, the counter calculates the occupation time and
accumulates.
l During periodical measurement, the counter calculates the occupation time and
accumulates.
Unit
Second
Related Features
44.17 C901380019 Mean number 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 active-standby changeover, the ranumc process calls the function to
release the standby umc database. In the above two cases, if obtaining the instance
occupying circuit fails, then the counter decrements.
44-12

Usage
This counter is used to find out the occupation of trunk circuits.
Measurement Point
1. When BSC receives the release command and releases the terrestrial circuit, it
attempts to obtain the instance currently occupying circuit. If the instance obtaining
fails, the counter counts. The measurement point is shown in Figure 44-7.
Figure 44-7 Common Release Flow
2. When the standby umc releases database and A-interface terrestrial circuit, the
counter counts. The measurement point is shown in Figure 44-8.
Figure 44-8 Standby umc Database Being Released
44-13

Unit
Times
44.18 C901380020 Mean number 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 Point
IPA performance statistics is implemented when Oms reports data. If the time when UDP
port becomes busy is the current system time, then the average number of occupied UDP
ports is counted. The measurement point is A1, as shown in Figure 44-9.
Figure 44-9 OMS Reporting Data to Database
Unit
Times
44-14

Chapter 45
Ater Message Measurement
Table of Contents
Overview ..................................................................................................................45-2
C901390001 Number of UL BLOCK Ater single CIRCUIT messages .......................45-3
C901390002 Number of DL BLOCKING Ater single CIRCUIT ACKNOWLEDGE
messages.................................................................................................................45-3
C901390003 Number of UL UNBLOCK Ater single CIRCUIT messages ..................45-4
C901390004 Number of DL UNBLOCKING Ater single CIRCUIT ACKNOWLEDGE
messages.................................................................................................................45-4
C901390005 Number of DL BLOCK Ater single CIRCUIT messages .......................45-5
C901390006 Number of UL BLOCKING Ater single CIRCUIT ACKNOWLEDGE
messages.................................................................................................................45-5
C901390007 Number of DL UNBLOCK Ater single CIRCUIT messages ..................45-6
C901390008 Number of UL UNBLOCKING Ater single CIRCUIT ACKNOWLEDGE
messages.................................................................................................................45-6
C901390009 Number of UL RESET Ater CIRCUIT messages..................................45-7
C901390010 Number of DL RESET Ater CIRCUIT messages..................................45-7
C901390011 Number of UL RESET Ater CIRCUIT ACKNOWLEDGE messages .....45-8
C901390012 Number of DL RESET Ater CIRCUIT ACKNOWLEDGE messages .....45-8
C901390013 Number of UL BLOCK Ater GROUP CIRCUIT messages....................45-9
C901390014 Number of DL BLOCK Ater GROUP CIRCUIT messages....................45-9
C901390015 Number of UL BLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE
messages...............................................................................................................45-10
C901390016 Number of DL BLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE
messages...............................................................................................................45-10
C901390017 Number of UL UNBLOCK GROUP CIRCUIT messages on Ater........ 45-11
C901390018 Number of DL UNBLOCK Ater GROUP CIRCUIT messages............. 45-11
C901390019 Number of UL UNBLOCKING Ater GROUP CIRCUIT
ACKNOWLEDGE messages ..................................................................................45-12
C901390020 Number of DL UNBLOCKING Ater GROUP CIRCUIT
ACKNOWLEDGE messages ..................................................................................45-12
C901390021 Number of UL UNEQUIPPED Ater CIRCUIT messages ....................45-13
C901390022 Number of DL UNEQUIPPED Ater CIRCUIT messages ....................45-13
C901390023 Number of UL BLOCK A CIRCUIT messages ...................................45-14
C901390024 Number of DL BLOCKING A CIRCUIT ACKNOWLEDGE messages .45-14
C901390025 Number of UL UNBLOCK A CIRCUIT messages ..............................45-14
C901390026 Number of DL UNBLOCKING A CIRCUIT ACKNOWLEDGE
messages...............................................................................................................45-15
C901390027 Number of DL BLOCK A CIRCUIT messages ...................................45-15
45-1

C901390028 Number of UL BLOCKING A CIRCUIT ACKNOWLEDGE messages .45-16

C901390029 Number of DL UNBLOCK A CIRCUIT messages ..............................45-16
C901390030 Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE
messages...............................................................................................................45-17
C901390031 Number of UL BLOCK A CIRCUIT GROUP messages......................45-17
C901390032 Number of DL BLOCK A CIRCUIT GROUP messages......................45-18
C901390033 Number of UL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE
messages...............................................................................................................45-18
C901390034 Number of DL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE
messages...............................................................................................................45-19
C901390035 Number of UL UNBLOCK A CIRCUIT GROUP messages.................45-19
C901390036 Number of DL UNBLOCK A CIRCUIT GROUP messages.................45-20
C901390037 Number of UL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE
messages...............................................................................................................45-20
C901390038 Number of DL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE
messages...............................................................................................................45-21
C901390039 Number of UL UNEQUIPPED A CIRCUIT messages ........................45-21
C901390040 Number of DL UNEQUIPPED A CIRCUIT messages ........................45-22
C901390041 Number of UL Ater RESET messages...............................................45-22
C901390042 Number of DL Ater RESET messages...............................................45-22
C901390043 Number of UL Ater RESET ACKNOWLEDGE messages ..................45-23
C901390044 Number of DL Ater RESET ACKNOWLEDGE messages ..................45-23
C901390045 Number of UL Ater CONFUSION messages .....................................45-24
C901390046 Number of DL Ater CONFUSION messages .....................................45-24
C901390047 Number of RESOURCE REQUEST messages..................................45-25
C901390048 Number of RESOURCE INDICATION messages ..............................45-25
C901390049 Number of RESOURCE NON-INDICATION messages......................45-26
C901390050 Number of resource release request messages.................................45-26
C901390051 Number of resource release acknowledge messages........................45-27
C901390052 Number of resource failure messages ...............................................45-27
C901390053 Number of TFO status messages ......................................................45-28
C901390054 Number of TFO common voice type messages .................................45-28
C901390055 Number of TFO control messages.....................................................45-28
45.1 Overview
Ater interface message counters are used to collect statistics on messages transceived
on Ater interface. It is counted by AterDispatch according to iTC office.
45-2

Chapter 45 Ater Message Measurement
45.2 C901390001 Number of UL 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 Point
When BSC sends a BLOCK message, this counter increments.
Unit
Times
Related Features
ZGO-05-02-005 Flex Ater
45.3 C901390002 Number of DL BLOCKING Ater single

CIRCUIT ACKNOWLEDGE messages
Definition
Number of DL BLOCKING Ater single CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING ACKNOWLEDGE messages received by
BSC from iTC.
Measurement Point
When BSC receives a BLOCKING ACKNOWLEDGE message, this counter increments.
Unit
Times
Related Features
45-3

45.4 C901390003 Number of UL UNBLOCK Ater single

CIRCUIT messages
Definition
Number of UL UNBLOCK Ater single CIRCUIT messages
Description
This counter counts the number of UNBLOCK messages sent by BSC to iTC.
Measurement Point
When BSC sends an UNBLOCK message, this counter increments.
Unit
Times
Related Features
45.5 C901390004 Number of DL 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 messages received
by BSC from iTC.
Measurement Point
When BSC receives an UNBLOCKING ACKNOWLEDGE message, this counter
increments.
Unit
Times
Related Features
45-4

45.6 C901390005 Number of DL 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 Point
When BSC receives a BLOCK message, this counter increments.
Unit
Times
Related Features
45.7 C901390006 Number of UL BLOCKING Ater single

Definition
Number of UL BLOCKING Ater single CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING ACKNOWLEDGE messages sent by BSC
to iTC.
Measurement Point
When BSC sends a BLOCKING ACKNOWLEDGE message, this counter increments.
Unit
Times
Related Features
45-5

45.8 C901390007 Number of DL UNBLOCK Ater single

CIRCUIT messages
Definition
Number of DL UNBLOCK Ater single CIRCUIT messages
Description
This counter counts the number of UNBLOCK messages received by BSC from iTC.
Measurement Point
When BSC receives an UNBLOCK message, this counter increments.
Unit
Times
Related Features
45.9 C901390008 Number of UL 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 messages sent by
BSC to iTC.
Measurement Point
When BSC sends an UNBLOCKING ACKNOWLEDGE message, this counter
increments.
Unit
Times
Related Features
45-6

45.10 C901390009 Number of UL RESET Ater CIRCUIT

messages
Definition
Number of UL RESET Ater CIRCUIT messages
Description
This counter counts the number of RESET CIRCUIT messages sent by BSC to iTC.
Measurement Point
When BSC sends a RESET CIRCUIT message, this counter increments.
Unit
Times
Related Features
45.11 C901390010 Number of 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 Point
When BSC receives a RESET CIRCUIT message, this counter increments.
Unit
Times
Related Features
45-7

45.12 C901390011 Number of UL RESET Ater CIRCUIT

Definition
Number of UL RESET Ater CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of RESET CIRCUIT ACKNOWLEDGE messages sent
by BSC to iTC.
Measurement Point
When BSC sends a RESET CIRCUIT ACKNOWLEDGE message, this counter
increments.
Unit
Times
Related Features
45.13 C901390012 Number of DL RESET Ater CIRCUIT

Definition
Number of DL RESET Ater CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of RESET CIRCUIT ACKNOWLEDGE messages
received by BSC from iTC.
Measurement Point
When BSC receives a RESET CIRCUIT ACKNOWLEDGE message, this counter
increments.
Unit
Times
Related Features
45-8

45.14 C901390013 Number of UL BLOCK Ater GROUP

CIRCUIT messages
Definition
Number of UL BLOCK Ater GROUP CIRCUIT messages
Description
This counter counts the number of BLOCK CIRCUIT GROUP messages sent by BSC to
iTC.
Measurement Point
When BSC sends a BLOCK CIRCUIT GROUP message, this counter increments.
Unit
Times
Related Features
45.15 C901390014 Number of DL BLOCK Ater GROUP

CIRCUIT messages
Definition
Number of DL BLOCK Ater GROUP CIRCUIT messages
Description
This counter counts the number of BLOCK CIRCUIT GROUP messages received by
BSC from iTC.
Measurement Point
When BSC receives a BLOCK CIRCUIT GROUP message, this counter increments.
Unit
Times
Related Features
45-9

45.16 C901390015 Number of UL 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 Point
When BSC sends a BLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this
counter increments.
Unit
Times
Related Features
45.17 C901390016 Number of DL BLOCKING Ater

Definition
Number of DL BLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING CIRCUIT GROUP ACKNOWLEDGE
messages received by BSC from iTC.
Measurement Point
When BSC receives a BLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this
counter increments.
Unit
Times
Related Features
45-10

45.18 C901390017 Number of UL UNBLOCK GROUP

CIRCUIT messages on Ater
Definition
Number of UL UNBLOCK GROUP CIRCUIT messages on Ater
Description
This counter counts the number of UL UNBLOCK GROUP CIRCUIT messages on Ater
sent by BSC to iTC.
Measurement Point
When BSC sends an UL UNBLOCK GROUP CIRCUIT messages on Ater, this counter
increments.
Unit
Times
Related Features
45.19 C901390018 Number of DL UNBLOCK Ater

GROUP CIRCUIT messages
Definition
Number of DL UNBLOCK Ater GROUP CIRCUIT messages
Description
This counter counts the number of UNBLOCK CIRCUIT GROUP messages received by
BSC from iTC.
Measurement Point
When BSC receives an UNBLOCK CIRCUIT GROUP message, this counter increments.
Unit
Times
Related Features
45-11

45.20 C901390019 Number of UL UNBLOCKING Ater

Definition
Number of UL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE
Measurement Point
When BSC sends an UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this
counter increments.
Unit
Times
Related Features
45.21 C901390020 Number of DL UNBLOCKING Ater

Definition
Number of DL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE
Measurement Point
When BSC receives an UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE message,
Unit
Times
Related Features
45-12

45.22 C901390021 Number of UL UNEQUIPPED Ater

CIRCUIT messages
Definition
Number of UL UNEQUIPPED Ater CIRCUIT messages
Description
This counter counts the number of UNEQUIPPED CIRCUIT messages sent by BSC to
iTC.
Measurement Point
When BSC sends an UNEQUIPPED CIRCUIT message, this counter increments.
Unit
Times
Related Features
45.23 C901390022 Number of DL UNEQUIPPED Ater

CIRCUIT messages
Definition
Number of DL UNEQUIPPED Ater CIRCUIT messages
Description
This counter counts the number of UNEQUIPPED CIRCUIT messages received by BSC
from iTC.
Measurement Point
When BSC receives an UNEQUIPPED CIRCUIT message, this counter increments.
Unit
Times
Related Features
45-13

45.24 C901390023 Number of UL BLOCK A CIRCUIT

messages
Definition
Number of UL BLOCK A CIRCUIT messages
Description
This counter counts the number of BLOCK A CIRCUIT messages sent by BSC to iTC.
Measurement Point
When BSC sends a BLOCK A CIRCUIT message, this counter increments.
Unit
Times
45.25 C901390024 Number of DL BLOCKING A CIRCUIT

Definition
Number of DL BLOCKING A CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING A CIRCUIT ACKNOWLEDGE messages
Measurement Point
When BSC receives a BLOCKING A CIRCUIT ACKNOWLEDGE message, this counter
increments.
Unit
Times
45.26 C901390025 Number of UL UNBLOCK A CIRCUIT

messages
Definition
Number of UL UNBLOCK A CIRCUIT messages
45-14

Description
This counter counts the number of UNBLOCK A CIRCUIT messages sent by BSC to iTC.
Measurement Point
When BSC sends an UNBLOCK A CIRCUIT message, this counter increments.
Unit
Times
45.27 C901390026 Number of DL UNBLOCKING A

Definition
Number of DL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of UNBLOCKING A CIRCUIT ACKNOWLEDGE
Measurement Point
When BSC receives an UNBLOCKING A CIRCUIT ACKNOWLEDGE message, this
counter increments.
Unit
Times
45.28 C901390027 Number of DL BLOCK A CIRCUIT

messages
Definition
Number of DL BLOCK A CIRCUIT messages
Description
This counter counts the number of BLOCK A CIRCUIT messages received by BSC from
iTC.
Measurement Point
When BSC receives a BLOCK A CIRCUIT message, this counter increments.
45-15

Unit
Times
45.29 C901390028 Number of UL BLOCKING A CIRCUIT

Definition
Number of UL BLOCKING A CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING A CIRCUIT ACKNOWLEDGE messages
sent by BSC to iTC.
Measurement Point
When BSC sends a BLOCKING A CIRCUIT ACKNOWLEDGE message, this counter
increments.
Unit
Times
45.30 C901390029 Number of DL UNBLOCK A CIRCUIT

messages
Definition
Number of DL UNBLOCK A CIRCUIT messages
Description
This counter counts the number of UNBLOCK A CIRCUIT messages received by BSC
from iTC.
Measurement Point
When BSC receives an UNBLOCK A CIRCUIT message, this counter increments.
Unit
Times
45-16

45.31 C901390030 Number of UL UNBLOCKING A

Definition
Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages
Description
This counter counts the number of UNBLOCKING A CIRCUIT ACKNOWLEDGE
Measurement Point
When BSC sends an UNBLOCKING A CIRCUIT ACKNOWLEDGE message, this
counter increments.
Unit
Times
45.32 C901390031 Number of UL 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 messages sent by BSC
to iTC.
Measurement Point
When BSC sends a BLOCK A CIRCUIT GROUP message, this counter increments.
Unit
Times
45-17

45.33 C901390032 Number of DL 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 messages received by
BSC from iTC.
Measurement Point
When BSC receives a BLOCK A CIRCUIT GROUP message, this counter increments.
Unit
Times
45.34 C901390033 Number of UL BLOCKING A CIRCUIT

GROUP ACKNOWLEDGE messages
Definition
Number of UL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING A CIRCUIT GROUP ACKNOWLEDGE
Measurement Point
When BSC sends a BLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this
counter increments.
Unit
Times
45-18

45.35 C901390034 Number of DL BLOCKING A CIRCUIT

GROUP ACKNOWLEDGE messages
Definition
Number of DL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages
Description
This counter counts the number of BLOCKING A CIRCUIT GROUP ACKNOWLEDGE
Measurement Point
When BSC receives a BLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this
counter increments.
Unit
Times
45.36 C901390035 Number of 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 messages sent by
BSC to iTC.
Measurement Point
When BSC sends an UNBLOCK A CIRCUIT GROUP message, this counter increments.
Unit
Times
45-19

45.37 C901390036 Number of 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 messages received
by BSC from iTC.
Measurement Point
When BSC receives an UNBLOCK A CIRCUIT GROUP message, this counter
increments.
Unit
Times
45.38 C901390037 Number of UL UNBLOCKING A

CIRCUIT 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
Measurement Point
When BSC sends an UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE message,
Unit
Times
45-20

45.39 C901390038 Number of DL UNBLOCKING A

CIRCUIT 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
Measurement Point
When BSC receives an UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE message,
Unit
Times
45.40 C901390039 Number of UL UNEQUIPPED A

CIRCUIT messages
Definition
Number of UL UNEQUIPPED A CIRCUIT messages
Description
This counter counts the number of UNEQUIPPED A CIRCUIT messages sent by BSC
to iTC.
Measurement Point
When BSC sends an UNEQUIPPED A CIRCUIT message, this counter increments.
Unit
Times
45-21

45.41 C901390040 Number of DL UNEQUIPPED A

CIRCUIT messages
Definition
Number of DL UNEQUIPPED A CIRCUIT messages
Description
This counter counts the number of UNEQUIPPED A CIRCUIT messages received by
BSC from iTC.
Measurement Point
When BSC receives an UNEQUIPPED A CIRCUIT message, this counter increments.
Unit
Times
45.42 C901390041 Number of UL 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 Point
When BSC sends a RESET message, this counter increments.
Unit
Times
Related Features
45.43 C901390042 Number of DL Ater RESET messages

Definition
Number of DL Ater RESET messages
45-22

Description
This counter counts the number of RESET messages received by BSC from iTC.
Measurement Point
When BSC receives a RESET message, this counter increments.
Unit
Times
Related Features
45.44 C901390043 Number of UL Ater RESET

Definition
Number of UL Ater RESET ACKNOWLEDGE messages
Description
This counter counts the number of RESET ACKNOWLEDGE messages sent by BSC to
iTC.
Measurement Point
When BSC sends a RESET ACKNOWLEDGE message, this counter increments.
Unit
Times
Related Features
45.45 C901390044 Number of DL Ater RESET

Definition
Number of DL Ater RESET ACKNOWLEDGE messages
45-23

Description
This counter counts the number of RESET ACKNOWLEDGE messages received by BSC
from iTC.
Measurement Point
When BSC receives a RESET ACKNOWLEDGE message, this counter increments.
Unit
Times
Related Features
45.46 C901390045 Number of 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 Point
When BSC sends a CONFUSION message, this counter increments.
Unit
Times
Related Features
45.47 C901390046 Number of DL Ater CONFUSION

messages
Definition
Number of DL Ater CONFUSION messages
45-24

Description
This counter counts the number of CONFUSION messages received by BSC from iTC.
Measurement Point
When BSC receives a CONFUSION message, this counter increments.
Unit
Times
Related Features
45.48 C901390047 Number of RESOURCE REQUEST

messages
Definition
Number of RESOURCE REQUEST messages
Description
This counter counts the number of RESOURCE REQUEST messages sent by BSC to
iTC.
Measurement Point
When BSC sends a RESOURCE REQUEST message, this counter increments.
Unit
Times
45.49 C901390048 Number of RESOURCE INDICATION

messages
Definition
Number of RESOURCE INDICATION messages
Description
This counter counts the number of RESOURCE REQUEST ACKNOWLEDGE messages
45-25

Measurement Point
When BSC receives a RESOURCE REQUEST ACKNOWLEDGE message, this counter
increments.
Unit
Times
45.50 C901390049 Number of RESOURCE

NON-INDICATION messages
Definition
Number of RESOURCE NON-INDICATION messages
Description
This counter counts the number of RESOURCE REQUEST NEGTIVE ACKNOWLEDGE
Measurement Point
When BSC receives a RESOURCE REQUEST NEGTIVE ACKNOWLEDGE message,
Unit
Times
45.51 C901390050 Number of resource release request

messages
Definition
Number of resource release request messages
Description
This counter counts the number of RESOURCE RELEASE REQUEST messages sent
by BSC to iTC.
Measurement Point
When BSC sends a RESOURCE RELEASE REQUEST message, this counter
increments.
45-26

Unit
Times
45.52 C901390051 Number of resource release

acknowledge messages
Definition
Number of resource release acknowledge messages
Description
This counter counts the number of RESOURCE RELEASE ACKNOWLEDGE messages
Measurement Point
When BSC receives a RESOURCE RELEASE ACKNOWLEDGE message, this counter
increments.
Unit
Times
45.53 C901390052 Number of resource failure

messages
Definition
Number of resource failure messages
Description
This counter counts the number of RESOURCE FAILURE messages received by BSC
from iTC.
Measurement Point
When BSC receives a RESOURCE FAILURE message, this counter increments.
Unit
Times
45-27

45.54 C901390053 Number of 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 Point
When BSC receives a TFO STATE message, this counter increments
Unit
Times
45.55 C901390054 Number of TFO common voice type

messages
Definition
Number of TFO common voice type messages
Description
This counter counts the number of TFO CONMMONTYPE messages received by BSC
from iTC.
Measurement Point
When BSC receives a TFO CONMMONTYPE message, this counter increments.
Unit
Times
45.56 C901390055 Number of TFO control messages

Definition
Number of TFO control messages
Description
This counter counts the number of TFO CONTROL INFORMATION messages sent by
BSC to iTC.
45-28

Measurement Point
When BSC sends a TFO CONTROL INFORMATION message, this counter increments.
Unit
Times
45-29

45-30

Chapter 46
MTP2 Signal Link
Measurement
Table of Contents
Overview ..................................................................................................................46-1
C901400001 Number of error SU due to Abnormal Flag...........................................46-1
C901400002 Number of error SU Length Error.........................................................46-2
C901400003 Number of Out of Alignment ................................................................46-3
C901400004 Number of error SU due not to Octet ...................................................46-3
C901400005 Number of error SU due to CRC Error .................................................46-4
C901400006 Number of Other error .........................................................................46-4
C901400007 Number of Negative Acknowledgement Received ...............................46-5
C901400008 Octets of MSU Retransmitted ..............................................................46-5
C901400009 Number of MSU Resend .....................................................................46-6
C901400010 Number of Align Error..........................................................................46-6
C901400011 Number of Error SU.............................................................................46-6
C901400012 Number of MSU discarded due to congestion......................................46-7
C901400013 Number of SL failure due to Abnormal FIBR BSNR .............................46-7
C901400014 Number of SL failure due to Excessive delay of ack ............................46-8
C901400015 Number of SL failure due to Excessive error rate.................................46-8
C901400016 Number of SL failure due to Excessive duration of congestion.............46-9
46.1 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.
46.2 C901400001 Number of error SU due to Abnormal

Flag
Definition
Number of error SU due to Abnormal Flag
46-1

Description
This counter counts the number of SUs with seven consecutive 1s in message code stream
received by an MTP2 link. According to the protocol, the valid flag is 01111110 and a
flag with seven consecutive 1s is invalid. If this message carries 1111111, this counter
increments.
Usage
This counter is used to find out the occurrence of SUs carrying seven consecutive 1s in
message code stream received by an MTP2 link.
Measurement Point
When an MTP2 link receives a message code stream carrying 1111111, this counter
increments.
Unit
Times
46.3 C901400002 Number of error SU Length Error

Definition
Number of error SU Length Error
Description
This counter counts the number of SUs with overlong or too short messages received by
an MTP2 link. According to the protocol, a signal unit (SU) contains at least six octets and
at most 279 octets. If the number of octets is smaller than 6 or bigger than 279, the length
of the signal unit is wrong. and this counter increments.(Note: an octet is equal to a byte,
that is 8 bits.)
Usage
This counter is used to find out the occurrence of SUs carrying overlong or too short
messages received by an MTP2 link.
Measurement Point
When a message octet is shorter than 6 or longer than 127, this counter increments.
Unit
Times
46-2

Chapter 46 MTP2 Signal Link Measurement
46.4 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, there is an eight-bit flag each at the head and tail
of a signal unit to identify the signal unit. When the flag is invalid or the length of the signal
unit exceeds the maximum value, location is lost. In this case, this counter increments.
Usage
This counter is used to find out the occurrence of message code streams out of alignment
received by an MTP2 link.
Measurement Point
When the flag is invalid or the length of the signal unit exceeds the maximum value, this
counter increments.
Unit
Times
46.5 C901400004 Number of 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 Point
When an octet composed of non-8 bits occurs, this counter increments.
46-3

Unit
Times
46.6 C901400005 Number of error SU due to CRC Error

Definition
Number of error SU due to CRC Error
Description
This counter counts the number of CRC errors received by an MTP2 link. According to
the protocol, a signal unit has a 16-bit check code at its tail, which is generated when the
signal unit is sent. The check code is checked at the receiving end. When a CRC error
occurs, this counter increments.
Usage
This counter is used to find out the occurrence of CRC errors received by an MTP2 link.
Measurement Point
When a CRC error occurs, this counter increments.
Unit
Times
46.7 C901400006 Number of Other error

Definition
Number of Other error
Description
This counter counts the number of other message errors received by an MTP2 link. When
errors other than the above four types occur, this counter increments.
Usage
This counter is used to find out the occurrence of message errors other than the above
four types received by an MTP2 link.
Measurement Point
When errors other than the above four types occur, this counter increments.
46-4

Unit
Times
46.8 C901400007 Number of Negative

Acknowledgement Received
Definition
Number of Negative Acknowledgement Received
Description
This counter counts the number of negative acknowledgements received by an MTP2 link.
Usage
This counter is used to find out the occurrence of negative acknowledgements received
by an MTP2 link.
Measurement Point
When an MTP2 link receives a negative acknowledgement, this counter increments.
Unit
Times
46.9 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 Point
When an MTP2 link is retransmitted, this counter increments by the corresponding octet.
Unit
octet
46-5

46.10 C901400009 Number of MSU Resend

Definition
Number of MSU Resend
Description
This counter counts the number of MSU packets resent by MTP2.
Usage
This counter is used to find out the frequency of MTP2 resending.
Measurement Point
When an MTP2 link is resent, this counter increments by the corresponding number of
resent packets.
Unit
Packet
46.11 C901400010 Number of Align Error

Definition
Number of Align Error
Description
This counter counts the number of alignment or check error of an MTP2 link.
Usage
This counter is used to find out the frequency of alignment failures of an MTP2 link.
Measurement Point
When an MTP2 link receives AlignNtpsbl during alignment, this counter increments.
Unit
Times
46.12 C901400011 Number of Error SU

Definition
Number of Error SU
46-6

Description
This counter counts the number of error SUs received by an MTP2 link.
Usage
This counter is used to find out the frequency of receiving error SUs received by an MTP2
link.
Measurement Point
When an MTP2 link receives an error SU, this counter increments.
Unit
Times
46.13 C901400012 Number of MSU discarded due to

congestion
Definition
Number of MSU discarded due to congestion
Description
This counter counts the number of MSUs discarded due to congestion resulted from full
buffer on an MTP2 link.
Usage
This counter is used to find out the frequency discarding MSUs due to congestion resulted
from full buffer on an MTP2 link.
Measurement Point
When an MTP2 link discards MSU due to congestion, this counter increments.
Unit
Times
46.14 C901400013 Number of SL failure due to

Abnormal FIBR BSNR
Definition
Number of SL failure due to Abnormal FIBR/BSNR
46-7

Description
This counter counts the number of SL failures due to abnormal FIBR/BSNR.
Usage
This counter is used to find out the occurrence of SL failures due to abnormal FIBR/BSNR.
Measurement Point
When an MTP2 link is broken due to abnormal FIBBSN, this counter increments.
Unit
Times

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.
Usage
This counter is used to find out the occurrence of SL failures due to excessive delay of
acknowledgement.
Measurement Point
When an MTP2 link is broken due to excessive delay of acknowledgement, this counter
increments.
Unit
Times

Excessive error rate
Definition
Number of SL failure due to Excessive error rate
46-8

Description
This counter counts the number of SL failures due to excessive error rate.
Usage
This counter is used to find out the occurrence of SL failures due to excessive error rate.
Measurement Point
When an MTP2 link is broken due to excessive error rate, this counter increments.
Unit
Times

Excessive duration of congestion
Definition
Number of SL failure due to Excessive duration of congestion
Description
This counter counts the number of SL failures due to excessive duration of congestion.
Usage
This counter is used to find out the occurrence of SL failures due to excessive duration of
congestion.
Measurement Point
When an MTP2 link is broken due to congestion, this counter increments.
Unit
Times
46-9

46-10

Chapter 47
CPU MEM Measurement
Table of Contents
Overview ..................................................................................................................47-1
C901410001 Peak memory usage of the main processor.........................................47-1
C901410002 Mean value of the memory usage........................................................47-2
C901410003 Peak load of CPU usage of the main processor...................................47-2
C901410004 Mean ratio of the CPU usage ..............................................................47-3
C901410005 Duration of the main processor keeping in peak state..........................47-3
C901410006 The time when peak load CPU usage occurred ...................................47-4
C901410007 peak kilo-bytes of the rest UB..............................................................47-4
C901410008 Mean kilo-bytes of the rest UB.............................................................47-5
47.1 Overview
To explicate CPU and memory usages during platform running procedure and provide
reference for future upgrade and maintenance, the system enables users to view peak
CPU usage, remaining memory, and peak of the rest UB in the specified period. Eight
counters are provided, as shown in the following sections.
47.2 C901410001 Peak memory usage of the main

processor
Definition
Peak memory usage of the main processor
Description
This counter compares the memory usages of all measurement points measured at an
interval of 2 seconds in the measurement period and specifies the maximum measurement
point as the peak load.
Usage
This counter is used to view the peak memory usage of the main processor in measurement
period.
Measurement Point
In the sampling period, sample a memory usage every 2 seconds.
47-1

Unit
Percent
47.3 C901410002 Mean value of the memory usage

Definition
Mean value of the memory usage
Description
This counter averages the memory usages of all measurement points at an interval of 2
seconds in the measurement period and outputs the mean value.
Usage
This counter is used to find out the mean memory usage of the system.
Measurement Point
In the sampling period, sample a memory usage every 2 seconds.
Unit
Percent
47.4 C901410003 Peak load of CPU usage of the main

processor
Definition
Peak load of CPU usage of the main processor
Description
This counter samples CPU usage at an interval of 2 seconds and specifies the maximum
memory usage in the measurement period as the peak load of CPU usage of the main
processor.
Usage
This counter is used to view the peak load of CPU usage in the specified measurement
period.
Measurement Point
In the sampling period, sample a CPU usage every 2 seconds and use the peak value as
the maximum value of the measurement point.
47-2

Chapter 47 CPU MEM Measurement
Unit
Percent
47.5 C901410004 Mean ratio of the CPU usage

Definition
Mean ratio of the CPU usage
Description
This counter samples CPU usage at an interval of 2 seconds, averages the CPU usages
of all measurement points, and outputs the mean value.
Usage
This counter is used to find out the mean CPU usage in the specified period.
Measurement Point
In the sampling period, sample a CPU usage every 2 seconds. Divide the sum of the
values of all measurement points by the number of measurement points.
Unit
Percent
47.6 C901410005 Duration of the main processor

keeping in peak state
Definition
Duration of the main processor keeping in peak state
Description
This counter counts the duration of the main processor in peak state.
Usage
This counter is used to find out the duration of CPU peak status, which can serve as a
reference for knowing system operating conditions.
Measurement Point
In the sampling period, count and record the maximum values of main processor peak at
all measurement points, and accumulate the duration of the maximum measurement point.
47-3

Unit
Second
47.7 C901410006 The time when peak load CPU usage

occurred
Definition
The time when peak load CPU usage occurred
Description
This counter records the time when peak load of main processor occurred for the first
time in the measurement period. The time is the number of seconds relative to 00:00:00
January 1, 2000.
Usage
This counter is used to find out the time when CPU peak occurred, which provides a basis
for system performance analysis.
Measurement Point
In the sampling period, trace the time when the load of main processor reaches peak. At
the end of collection period, output the traced time point.
Unit
Second
47.8 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.
47-4

Chapter 47 CPU MEM Measurement
Measurement Point
In the sampling period, do sampling at an interval of 2 seconds and get the maximum
kilo-bytes of the rest UB.
Unit
Byte
47.9 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 Point
At the end of a collection period, average the bytes of the rest UB sampled every 2 seconds.
Unit
Byte
47-5

47-6

Chapter 48
SCTP AS Measurement
Table of Contents
Overview ..................................................................................................................48-1
C901420001 Number of IP packets dropped by SCTP due to some reasons ...........48-2
C901420002 Number of received SCTP packets......................................................48-2
C901420003 Bytes of packets received from ip ........................................................48-3
C901420004 Number of packets sent to ip ...............................................................48-3
C901420005 Bytes of packets sent to ip...................................................................48-4
C901420006 Number of messages sent to ulp .........................................................48-4
C901420007 Bytes of messages sent to ulp.............................................................48-5
C901420008 Number of messages received from ulp ..............................................48-5
C901420009 Bytes of messages received from........................................................48-6
C901420010 Number of Congestion ........................................................................48-6
C901420011 Duration of congestion.........................................................................48-7
C901420012 Chunk number of fast retransmission ..................................................48-7
C901420013 Chunk number of time-out retransmission ...........................................48-8
C901420014 RTT is lower than T1 ...........................................................................48-8
C901420015 RTT is between T1 and T2 ..................................................................48-9
C901420016 RTT is higher than T2..........................................................................48-9
C901420017 Number of network transmission dropped packets ............................48-10
C901420018 Maximum delay of network transmission ...........................................48-10
C901420019 Minimum delay of network transmission ............................................ 48-11
C901420020 Total delay of network transmission(high 4 bytes)..............................48-12
C901420021 Total delay of network transmission(low 4 bytes) ...............................48-12
C901420022 Number of delay samples of network transmission ............................48-13
C901420023 Maximum dithering of network transmission ......................................48-13
C901420024 Minimum dithering of network transmission .......................................48-14
C901420025 Total dithering of network transmission(high 4 bytes).........................48-15
C901420026 Total dithering of network transmission(low 4 bytes) ..........................48-15
C901420027 Number of dithering samples of network transmission .......................48-16
C901420028 Chunks Lost On Send Dirction ..........................................................48-17
C901420029 Chunks Trans On Send Dirction ........................................................48-17
48.1 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).
48-1

48.2 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, this counter increments.
Usage
This counter is used to find out the number of packets dropped by SCTP.
Measurement Point
When SCTP drops packets, this counter will count.
Unit
Times
48.3 C901420002 Number of 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 packets, this counter increments.
Usage
This counter is used to find out the number of packets received by SCTP.
Measurement Point
When SCTP receives packets, this counter will count.
Unit
Times
48-2

Chapter 48 SCTP AS Measurement
48.4 C901420003 Bytes of packets received from ip

Definition
Bytes of packets received from ip
Description
This counter counts the number of packet bytes received by the SCTP. The length of only
valid data in DATA CHUNK is counted. When SCTP receives DATA packets, this counter
accumulates.
Usage
This counter is used to find out the number of DATA packet bytes received by SCTP.
Measurement Point
When SCTP receives DATA packets, this counter will count.
Unit
Times
48.5 C901420004 Number of 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, this counter increments.
Usage
This counter is used to find out the number of packets sent by SCTP.
Measurement Point
When SCTP sends packets, this counter will count.
Unit
Times
48-3

48.6 C901420005 Bytes of packets sent to ip

Definition
Bytes of packets sent to ip
Description
This counter counts the number of packet bytes sent by the SCTP. The length of only
valid data in DATA CHUNK is counted. When SCTP sends DATA packets, this counter
accumulates.
Usage
This counter is used to find out the number of DATA packet bytes sent by SCTP.
Measurement Point
When SCTP sends DATA packets, this counter will count.
Unit
Times
48.7 C901420006 Number of messages sent to ulp

Definition
Number of messages sent to ulp
Description
This counter counts the number of messages sent by the SCTP to ULP. When SCTP sends
messages to ULP, this counter increments.
Usage
This counter is used to find out the number of messages sent by SCTP to ULP.
Measurement Point
When SCTP sends messages to ULP, this counter will count.
Unit
Times
48-4

48.8 C901420007 Bytes of messages sent to ulp

Definition
Bytes of messages sent to ulp
Description
This counter counts the number of message bytes sent by the SCTP to ULP. When SCTP
sends messages to ULP, this counter accumulates.
Usage
This counter is used to find out the number of message bytes sent by SCTP to ULP.
Measurement Point
When SCTP sends messages to ULP, this counter will count.
Unit
Times
48.9 C901420008 Number of 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 counter accumulates.
Usage
This counter is used to find out the number of messages received by SCTP from ULP.
Measurement Point
When SCTP receives ULP messages, this counter will count.
Unit
Times
48-5

48.10 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 counter accumulates.
Usage
This counter is used to find out the number of message bytes received by SCTP from ULP.
Measurement Point
When SCTP receives ULP messages, this counter will count.
Unit
Times
48.11 C901420010 Number of Congestion

Definition
Number of Congestion
Description
This counter counts the number of congestion control module zooming out congestion
windows. When congestion control module zooms out congestion windows, this counter
accumulates.
Usage
This counter is used to find out the number of SCTP congestions.
Measurement Point
When congestion control module zooms out congestion windows, this counter will count.
Unit
Times
48-6

48.12 C901420011 Duration of 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 Point
SCTP congestion control.
Unit
ms
48.13 C901420012 Chunk number of fast retransmission

Definition
Chunk number of fast retransmission
Description
This counter counts the number of chunks fast transmitted by the SCTP. If the data sending
end receives three SACKs indicating loss of a DATA chunk, SCTP fast transmits chunks
and this counter increments.
Usage
This counter is used to find out the number of chunks fast transmitted by SCTP.
Measurement Point
When SCTP fast transmits chunks, this counter will count.
Unit
Times
48-7

48.14 C901420013 Chunk number of time-out

retransmission
Definition
Chunk number of time-out retransmission
Description
This counter counts the number of chunks retransmitted by the SCTP due to timeout. If
the timeout retransmission timer times out, SCTP fast retransmits chunks and this counter
increments.
Usage
This counter is used to find out the number of chunks fast transmitted by SCTP.
Measurement Point
When SCTP retransmits chunks due to timeout, this counter will count.
Unit
Times
48.15 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
Usage
This counter is used to find out the statistics of RTT lower than T1.
Measurement Point
When the sampled RTT is lower than T1, this counter will counts.
Unit
None
48-8

48.16 C901420015 RTT is between T1 and T2

Definition
RTT is between T1 and T2
Description
This counter counts the statistics of RTT between T1 and T2. When RTT is between T1
and T2, this counter accumulates.
Usage
This counter is used to find out the statistics of RTT between T1 and T2.
Measurement Point
When the sampled RTT is between T1 and T2, this counter will count.
Unit
None
48.17 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
Usage
This counter is used to find out the statistics of RTT higher than T2.
Measurement Point
When the sampled RTT is higher than T2, this counter will count.
Unit
None
48-9

48.18 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 retransmission.
Usage
This counter is used to find out the statistics of packets dropped during network
transmission.
Measurement Point
If SCTP receives no response after sending packets, this counter will count during
retransmission.
Unit
Times
Related Features
ZGO-05-04-005 IP SLA Monitoring
48.19 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.
48-10

Measurement Point
When RTT is calculated based on RTO sampling, determine the maximum delay of network
transmission.
Unit
ms
Related Features
48.20 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.
Measurement Point
When RTT is calculated based on RTO sampling, determine the minimum delay of network
transmission.
Unit
ms
Related Features
48-11

48.21 C901420020 Total delay of network

transmission(high 4 bytes)
Definition
Total delay of network transmission (high 4 bytes)
Description
This counter counts the high 4 bytes of total delay of network transmission for processing
SCTP packets.
Usage
This counter is used to find out the total delay of network transmission for processing SCTP
packets.
Measurement Point
When RTT is calculated based on RTO sampling, delay of network transmission is
accumulated.
Unit
ms
Related Features
48.22 C901420021 Total delay of network

transmission(low 4 bytes)
Definition
Total delay of network transmission(low 4 bytes)
Description
This counter counts the low 4 bytes of total delay of network transmission for processing
SCTP packets.
Usage
This counter is used to find out the total delay of network transmission for processing SCTP
packets.
48-12

Measurement Point
When RTT is calculated based on RTO sampling, delay of network transmission is
accumulated.
Unit
ms
Related Features
48.23 C901420022 Number of delay samples of network

transmission
Definition
Number of delay samples of network transmission
Description
This counter counts the number of delay samples of network transmission. In
measurement internal, each time delay is sampled, this counter accumulates.
Usage
This counter is used to find out the number of delay samples in measurement interval.
Measurement Point
When a delay sampling is done in measurement interval, this counter will count.
Unit
Times
Related Features
48.24 C901420023 Maximum dithering of network

transmission
Definition
Maximum dithering of network transmission
48-13

Description
This counter counts the maximum dithering of network transmission of SCTP packets in
an interval. When the actual network transmission dithering is greater than maximum
dithering of network transmission, the actual one prevails.
Usage
This counter is used to find out the maximum dithering of network transmission.
Measurement Point
When RTT is calculated based on RTO sampling, determine the maximum dithering of
network transmission.
Unit
ms
Related Features
48.25 C901420024 Minimum dithering of network

transmission
Definition
Minimum dithering of network transmission
Description
This counter counts the minimum dithering of network transmission of SCTP packets in
an interval. When the actual network transmission dithering is smaller than maximum
dithering of network transmission, it replaces the minimum dithering of network
transmission.
Usage
This counter is used to find out the minimum dithering of network transmission.
Measurement Point
When RTT is calculated based on RTO sampling, determine the minimum dithering of
network transmission.
Unit
ms
48-14

Related Features
48.26 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 transmission for
processing SCTP packets.
Usage
This counter is used to find out the total dithering of network transmission for processing
SCTP packets.
Measurement Point
When RTT is calculated based on RTO sampling, dithering of network transmission is
accumulated.
Unit
ms
Related Features
48.27 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 transmission for processing
SCTP packets.
48-15

Usage
This counter is used to find out the total dithering of network transmission for processing
SCTP packets.
Measurement Point
When RTT is calculated based on RTO sampling, dithering of network transmission is
accumulated.
Unit
ms
Related Features
48.28 C901420027 Number of dithering samples of

network transmission
Definition
Number of dithering samples of network transmission
Description
This counter counts the number of delay samples of network transmission. In
measurement internal, each time dithering is sampled, this counter accumulates.
Usage
This counter is used to find out the number of dithering samples in measurement interval.
Measurement Point
When a dithering sampling is done in measurement interval, this counter will count.
Unit
Times
Related Features
48-16

48.29 C901420028 Chunks Lost On Send Dirction

Description
This counter counts the number of data blocks retransmitted by SCTP.
Usage
This counter is used to study the link quality and whether the two parties of the
communication are normal. If the counter's value keeps increasing, it might be due to lost
packets or large network delay.
Measurement Point
The counter counts when the data block marked as lost by SCTP (due to retransmission
timer being timeout or determined by rapid retransmission algorithm) is sent.
Unit
Number of data blocks
48.30 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 Point
The counter counts when the data block is sent. Here, the data block is the one sent for
the first time.
Unit
Number of data blocks
48-17

48-18

Chapter 49
IP Port Performance
Statistics
Table of Contents
Overview ..................................................................................................................49-1
C901430001 Packets number received ....................................................................49-1
C901430002 Packets number transmitted ................................................................49-2
C901430003 Packets number discarded at rx end ...................................................49-2
C901430004 Packets number discarded at tx end....................................................49-3
49.1 Overview
IP port performance statistics performs measurement for the number of messages
received, transmitted, and discarded at the external physical port of IP interface board.
IP port performance statistics involves debugging performance data and performance
data that are useful for module debugging and commissioning. Periodical statistics of IP
port performance data can reflect the characteristic of the port's history flow, such as the
average number of messages transmitted/received per second at the port, flow burst,
and bidirectional flow symmetry, etc. At present, physical boards it supports include BIPI
and GIPI.
Statistic unit in this measurement is times that the message is counted. The measurement
obtains the average number of received/transmitted messages per second (PPS) at the
port by controlling the period of sampling IP port performance data.
49.2 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.
49-1

Measurement Point
The counter accumulates when there is message received at IP port.
Unit
Times
49.3 C901430002 Packets number transmitted

Definition
Packets number transmitted
Description
This counter counts the number of messages sent at IP port. The counter increments
when a message is sent.
Usage
This counter is used to observe the number of messages sent at IP port.
Measurement Point
The counter accumulates when there is message sent at IP port.
Unit
Times
49.4 C901430003 Packets number discarded at rx end

Definition
Packets number discarded at rx end
Description
This counter counts the number of messages discarded at the receiving end of IP port.
The counter increments when an incorrect message is discarded at the receiving end.
Usage
This counter is used to observe the number of messages discarded at the receiving end
of IP port.
49-2

Chapter 49 IP Port Performance Statistics
Measurement Point
The counter accumulates when there is incorrect message discarded at the receiving end
of IP port.
Unit
Times
49.5 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 incorrect message is discarded at the transmitting end.
Usage
This counter is used to observe the number of messages discarded at the transmitting end
of IP port.
Measurement Point
The counter accumulates when there is incorrect message discarded at the transmitting
end of IP port.
Unit
Times
49-3

49-4

Chapter 50
GTRUNK Resource Statistics
Table of Contents
Overview ..................................................................................................................50-1
C901440001 Maximum of used DSP TS ..................................................................50-1
C901440002 Maximum of the used sampling according to DSP TS .........................50-2
C901440003 Amount of used DSP TS .....................................................................50-2
C901440004 Number of regular scanning and sampling...........................................50-3
50.1 Overview
GTRUNK refers to the timeslot resource on UPU DSP. GTRUNK resource statistics is used
to monitor the GTRUNK resource usage, which helps implement Gb interface capacity
expansion.
Statistic unit in this measurement is UPU DSP.
50.2 C901440001 Maximum of used DSP TS

Definition
Maximum of used DSP TS
Description
This counter counts the maximum number of each UPU DSP timeslot resource being
occupied within the measurement period.
Usage
This counter is used to find out the occupation of UPU DSP timeslot resource by PS
service, which helps optimize the UPU DSP resource.
Measurement Point
The counter counts when PS user requests for the UPU DSP timeslot resource
successfully.
Unit
Times
50-1

50.3 C901440002 Maximum of the used sampling

according to DSP TS
Description
This counter counts the number of available UPU DSP timeslot resource at the
measurement point of C901440001, which is the sum of the number of occupied timeslots
and the number of idle timeslots.
Usage
This counter is used to find out the availability of UPU DSP timeslot resource when PS
service occupies the UPU DSP timeslot resource the most.
Measurement Point
successfully.
Unit
Times
50.4 C901440003 Amount of used DSP TS

Definition
Amount of used DSP TS
Description
This counter accumulates at each measurement point to get the sum of UPU DSP timeslot
resource used by PS service within the measurement period.
Usage
This counter reflects the average occupation of UPU DSP resource in PS service.
Measurement Point
successfully.
Unit
Times
50-2

Chapter 50 GTRUNK Resource Statistics

sampling
Definition
Number of regular scanning and sampling
Description
C901440003 reflect the average occupation of UPU DSP resource in PS service.
Usage
This counter reflects the average occupation of UPU DSP resource in PS service.
Measurement Point
successfully.
Unit
Times
50-3

50-4

Chapter 51
Other Process Statistics
Table of Contents
Overview ..................................................................................................................51-2
C901450001 Max time of NACC cell reselection ......................................................51-3
C901450002 Minimum time of NACC cell reselection...............................................51-4
C901450003 Total time of NACC cell reselection......................................................51-5
C901450004 Number of NACC cell reselection (PCCN to flush LL)..........................51-6
C901450005 Number of NACC cell reselection without receiving flush LL ................51-7
C901450006 Number of UL packet channel frame adjustment .................................51-8
C901450007 Number of DL packet channel frame adjustment .................................51-8
C901450008 Sum of C .............................................................................................51-8
C901450009 Sum of RxQual....................................................................................51-9
C901450010 Sum of GMSK-MEAN-BEP................................................................51-10
C901450011 Sum of GMSK-CV-BEP ..................................................................... 51-11
C901450012 Sum of 8PSK-MEAN-BEP .................................................................51-12
C901450013 Sum of 8PSK-CV-BEP ......................................................................51-13
C901450014 Number of sampling of C...................................................................51-14
C901450015 Number of sampling of RxQual..........................................................51-15
C901450016 Number of sampling of GMSK-MEAN-BEP........................................51-16
C901450017 Number of sampling of GMSK-CV-BEP .............................................51-17
C901450018 Number of sampling of 8PSK-MEAN-BEP .........................................51-18
C901450019 Number of sampling of 8PSK-CV-BEP ..............................................51-19
C901450020 Number of RLC uplink ACK TBF .......................................................51-20
C901450021 Number of RLC uplink NACK TBF.....................................................51-21
C901450022 Number of DL-UNITDATA messages with Service UTRAN CCO
received by BSC ....................................................................................................51-22
C901450023 Total Block Num ................................................................................51-22
C901450024 UL Idle Block Num.............................................................................51-22
C901450025 DL Idle Block Num.............................................................................51-22
C901450026 The max length of packet latency period in Abis ................................51-22
C901450027 The min length of packet latency period in Abis .................................51-23
C901450028 The average length of packet latency period in Abis ..........................51-23
C901450029 The latest length of packet latency period in Abis ..............................51-24
C901450030 The length of packet latency period between 0 and 20 ms (20
included) in Abis.....................................................................................................51-24
C901450031 The length of packet latency period between 20 ms and 40 ms (40
included) in Abis.....................................................................................................51-25
included) in Abis.....................................................................................................51-25
51-1


included) in Abis.....................................................................................................51-26
included) in Abis.....................................................................................................51-26
C901450035 The length of packet latency period between 100 ms and 120 ms
(120 included) in Abis.............................................................................................51-27
(140 included) in Abis.............................................................................................51-27
(160 included) in Abis.............................................................................................51-28
(180 included) in Abis.............................................................................................51-28
C901450039 The length of packet latency period larger than 180 ms in Abis .........51-29
C901450040 The max length of downlink packet latency period in Gb....................51-29
C901450041 The min length of downlink packet latency period in Gb ....................51-30
C901450042 The average length of downlink packet latency period in Gb .............51-30
C901450043 The length of downlink packet latency period between 0 and 100 ms
(100 included) in Gb ...............................................................................................51-31
C901450044 The length of downlink packet latency period between 100 ms and
200 ms (200 included) in Gb...................................................................................51-31
300 ms (300 included) in Gb...................................................................................51-32
400 ms (400 included) in Gb...................................................................................51-32
600 ms (600 included) in Gb...................................................................................51-33
1000 ms (1000 included) in Gb...............................................................................51-33
C901450049 The length of downlink packet latency period larger than 1000 ms in
Gb..........................................................................................................................51-34
C901450050 The max length of uplink packet latency period in Gb ........................51-34
C901450051 The min length of uplink packet latency period in Gb .........................51-35
C901450052 The average length of uplink packet latency period in Gb ..................51-35
C901450053 LLC Stall Num ...................................................................................51-35
C901450054 MAC Resource Congestion ...............................................................51-36
C901450055 BSSGP Resource Congestion...........................................................51-36
51.1 Overview
Other process measurements contain the measurement on adjustments of frame number
and NACC processes.
51-2

Chapter 51 Other Process Statistics
51.2 C901450001 Max time of NACC cell reselection

Description
Do NACC after receiving the Packet Cell Change Notification message sent by MS at
network side. SGSN sends Flush LL to BSS after receiving the uplink frame sent by the
MS in reselection cell, to notify cell reselection has been successfully done by the BSS
MS.
Usage
It is used to measure the max duration of NACC.
Measurement Point
The NACC duration is a sampling period, starting with BSS receiving the Packet Cell
Change Notification message sent by MS and ending with BSS receiving the Flush LL
message sent by SGSN. The measurement point is A, as shown in Figure 51-1.
Figure 51-1 NACC Duration
51-3

51.3 C901450002 Minimum time of NACC cell

reselection
Description
MS.
Usage
It is used to measure the minimum duration of NACC.
Measurement Point
Minimum time of this NACC is the minimum of all NACC periods in a sampling period.
51-4

51.4 C901450003 Total time of NACC cell reselection

Description
MS.
Usage
It is used to measure the total time of all successful NACCs in this cell.
Measurement Point
Total time of this NACC is the sum of all NACC periods in a sampling period.
51-5

51.5 C901450004 Number of NACC cell reselection

(PCCN to flush LL)
Description
MS.
Usage
It is used to measure the number of NACC success.
Measurement Point
Figure 51-4 Measurement point of number of NACC success
51-6

51.6 C901450005 Number of NACC cell reselection

without receiving flush LL
Description
network side. The MS decides whether to do cell reselection after the MS gets the system
message about adjacent cell at network side.
Usage
It is used to measure the number of NACC without receiving flush LL.
Measurement Point
Figure 51-5 Measurement point of number of NACCs
51-7

51.7 C901450006 Number of UL packet channel frame

adjustment
Description
This counter increments every 20 ms while recording a uplink frame number on packet
channel to locate the received MAC block. BTS maintains an absolute frame number and
reports it through PCU frame. Adjust the frame number in uplink channel if these two
values are different.
Usage
It is used to measure the number of UL packet channel frame adjustment.
Measurement Point
Do the measurement while the uplink frame number carried in uplink PCU frame is
inconsistent with the uplink frame number recorded on the channel.
51.8 C901450007 Number of 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 adjustment value is not 0.
Usage
It is used to measure the number of DL packet channel frame adjustment.
Measurement Point
Do the measurement while the adjustment value of downlink frame number carried in uplink
PCU frame is not 0 and not located in the protection period.
51.9 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.
51-8

Usage
This counter measures the C value about the channel quality.
Measurement Point
For GPRS or EGPRS, this counter increments while receiving PACKET DOWNLINK ACK.
Figure 51-6 Measurement point for the sum of C
Unit
None
51.10 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 Point
This counter increments while GPRS receives PACKET DOWNLINK ACK. The
51-9

Unit
None
51.11 C901450010 Sum of GMSK-MEAN-BEP

Description
This counter counts the GMSK-MEAN-BEP value in channel quality report while DRLC
receives EGPRS PACKET DOWNLINK ACK.
Usage
This counter measures the GMSK-MEAN-BEP value about the channel quality.
Measurement Point
This counter increments when EGPRS receives PACKET DOWNLINK ACK and the
GMSK_MEAN_BEP indication bit is 1 in the channel quality report. The measurement
51-10

Unit
None
51.12 C901450011 Sum of GMSK-CV-BEP

Description
This counter counts the GMSK-CV-BEP value in channel quality report while DRLC
Usage
This counter measures the GMSK-CV-BEP value about the channel quality.
Measurement Point
51-11

Unit
None
51.13 C901450012 Sum of 8PSK-MEAN-BEP

Description
This counter counts the 8PSK-MEAN-BEP value in channel quality report while DRLC
Usage
This counter measures the 8PSK-MEAN-BEP value about the channel quality.
Measurement Point
8PSK_MEAN_BEP indication bit is 1 in the channel quality report. The measurement
51-12

Unit
None
51.14 C901450013 Sum of 8PSK-CV-BEP

Description
This counter counts the 8PSK-CV-BEP value in channel quality report while DRLC receives
EGPRS PACKET DOWNLINK ACK.
Usage
This counter measures the 8PSK-CV-BEP value about the channel quality.
Measurement Point
51-13

Unit
None
51.15 C901450014 Number of sampling of C

Description
This counter counts the number of C sampling points in channel quality report while DRLC
receives GPRS PACKET DOWNLINK ACK or EGPRS PACKET DOWNLINK ACK.
Usage
This counter measures the number of C sampling points about the channel quality.
Measurement Point
For GPRS or EGPRS, this counter increments while receiving PACKET DOWNLINK ACK.
51-14

Unit
Times
51.16 C901450015 Number of sampling of RxQual

Description
This counter counts the number of RxQual sampling points in channel quality report while
DRLC receives GPRS PACKET DOWNLINK ACK.
Usage
This counter measures the number of RxQual sampling points about the channel quality.
Measurement Point
This counter increments while GPRS receives PACKET DOWNLINK ACK. The
51-15

Unit
Times
51.17 C901450016 Number of sampling of

GMSK-MEAN-BEP
Description
This counter counts the number of GMSK-MEAN-BEP sampling points in channel quality
report when DRLC receives EGPRS PACKET DOWNLINK ACK.
Usage
This counter measures the number of GMSK-MEAN-BEP sampling points about the
channel quality.
Measurement Point
51-16

Unit
None

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 points about the channel
quality.
Measurement Point
51-17

Unit
Times

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 points about the
channel quality.
Measurement Point
51-18

Unit
None

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 points about the channel
quality.
Measurement Point
51-19

Unit
Times
51.21 C901450020 Number of RLC uplink ACK TBF

Description
This counter counts the number of TBFs while URLC receives the uplink assginment or
DTM assignment and the resource assignment message shall be recorded under the
acknowledgement mode.
Usage
This counter measures the number of uplink TBFs under the acknowledgement mode.
Measurement Point
This counter measures the number of TBFs when URLC receives the uplink assginment
or DTM assignment and the resource assignment message shall be recorded under the
acknowledgement mode. The measurement point is A, as shown in Figure 51-18.
51-20

Figure 51-18 Measurement point of Number of RLC uplink ACK TBF
Unit
Times
51.22 C901450021 Number of RLC uplink NACK TBF

Description
This counter counts the number of TBFs while URLC receives the uplink assginment or
DTM assignment and the resource assignment message shall be recorded under the
unacknowledgement mode.
Usage
This counter measures the number of uplink TBFs under the unacknowledgement mode.
Measurement Point
This counter measures the number of TBFs when URLC receives the uplink assginment
or DTM assignment and the resource assignment message shall be recorded under the
unacknowledgement mode. The measurement point is A, as shown in Figure 51-19.
51-21

Figure 51-19 Measurement point of Number of RLC uplink ACK TBF
Unit
Times
51.23 C901450022 Number of DL-UNITDATA messages

51.24 C901450023 Total Block Num

51.25 C901450024 UL Idle Block Num

51.26 C901450025 DL Idle Block Num

51.27 C901450026 The max length of packet latency

period in Abis
Statistics object
Cell
51-22

Description
This counter counts the maximum delay of the cell's PS service at Abis interface within the
measurement period. When the uplink frame number and downlink frame number of PS
service at BSC are synchronized, the counter gets the difference between the uplink frame
number and downlink frame number, thus to get the delay of PS service at Abis interface.
After comparison, the counter records the maximum delay.
Unit
ms
51.28 C901450027 The min length of packet latency

period in Abis
Statistics object
Cell
Description
This counter counts the minimum delay of the cell's PS service at Abis interface within the
After comparison, the counter records the minimum delay.
Unit
ms
51.29 C901450028 The average length of packet latency

period in Abis
Statistics object
Cell
Description
This counter counts the average delay of the cell's PS service at Abis interface within the
After adding all delays and dividing the sum by the number of measurements, the counter
records the average delay.
51-23

Unit
ms
51.30 C901450029 The latest length of packet latency

period in Abis
Statistics object
Cell
Description
This counter counts the latest delay of the cell's PS service at Abis interface within the
The counter records the latest delay.
Unit
ms
51.31 C901450030 The length of packet latency period

between 0 and 20 ms (20 included) in Abis
Statistics object
Cell
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
51-24


between 20 ms and 40 ms (40 included) in Abis
Statistics object
Cell
Description
Abis interface is in the range of (20 ms, 40 ms] within the measurement period. When the
uplink frame number and downlink frame number of PS service at BSC are synchronized,
the counter gets the difference between the uplink frame number and downlink frame
number, thus to get the delay of PS service at Abis interface. If the delay is in the range,
Unit
Times

Statistics object
Cell
Description
Unit
Times
51-25


Statistics object
Cell
Description
Unit
Times

Statistics object
Cell
Description
Unit
Times
51-26


Statistics object
Cell
Description
Unit
Times

Statistics object
Cell
Description
Unit
Times
51-27


Statistics object
Cell
Description
Unit
Times

Statistics object
Cell
Description
Unit
Times
51-28


larger than 180 ms in Abis
Statistics object
Cell
Description
Abis interface is in the range of (180 ms, +] within the measurement period. When the
Unit
Times
51.41 C901450040 The max length of downlink packet

latency period in Gb
Statistics object
Cell
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 downlink 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
51-29

51.42 C901450041 The min length of downlink packet

Statistics object
Cell
Description
This counter counts the minimum 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
sent time to get the downlink delay at Gb interface. After comparison, the counter records
the minimum delay.
Unit
ms
51.43 C901450042 The average length of downlink

packet latency period in Gb
Statistics object
Cell
Description
This counter counts the average 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
sent time to get the downlink delay at Gb interface. Add the subtraction result with all
downlink delays at Gb interface to get the total delay. Divide the sum by the number of
measurements, and the counter records the average delay.
Unit
ms
51-30

51.44 C901450043 The length of downlink packet

latency period between 0 and 100 ms (100 included)
in Gb
Statistics object
Cell
Description
This counter counts the number of samples of which the delay of 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

latency period between 100 ms and 200 ms (200
included) in Gb
Statistics object
Cell
Description
Unit
Times
51-31


included) in Gb
Statistics object
Cell
Description
Unit
Times

included) in Gb
Statistics object
Cell
Description
Unit
Times
51-32


included) in Gb
Statistics object
Cell
Description
Unit
Times

included) in Gb
Statistics object
Cell
Description
Unit
Times
51-33


latency period larger than 1000 ms in Gb
Statistics object
Cell
Description
in downlink transmission at Gb interface is in the range of (1000 ms, +) within the
Unit
Times
51.51 C901450050 The max length of uplink packet

Statistics object
Cell
Description
This counter counts the maximum delay of the cell's PS service in uplink transmission at Gb
interface within the measurement period. At BSC, when IP packet is sent at Gb interface,
the uplink sent time is recorded; when IP packet is received at Gb interface, the uplink
received time is recorded. Subtract the uplink sent time from the uplink received time to
get the uplink delay at Gb interface. After comparison, the counter records the maximum
delay.
Unit
ms
51-34

51.52 C901450051 The min length of uplink packet

Statistics object
Cell
Description
This counter counts the minimum delay of the cell's PS service in uplink transmission at Gb
get the uplink delay at Gb interface. After comparison, the counter records the minimum
delay.
Unit
ms
51.53 C901450052 The average length of uplink packet

Statistics object
Cell
Description
This counter counts the average delay of the cell's PS service in uplink transmission at Gb
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
51.54 C901450053 LLC Stall Num

51-35

51.55 C901450054 MAC Resource Congestion

Description
This counter counts the number of failures in requesting for MAC instance resource.
If obtaining MAC instance fails in requesting for MAC instance resource, the counter
increments.
Usage
This counter is used to find out the number of failures in creating MAC instance.
Measurement Point
1. When BSC receives the Channel Request message from MS, if BSC fails to create
the MAC instance, then the counter counts.
2. When BSC receives the downlink data from SGSN, if BSC fails to create the MAC
instance, then the counter counts.
Unit
Times
51.56 C901450055 BSSGP Resource Congestion

Description
This counter counts the number of failures in requesting for BSSGP instance resource. If
obtaining BSSGP instance fails in requesting for BSSGP instance resource, the counter
increments.
Usage
This counter is used to find out the number of failures in creating BSSGP instance.
Measurement Point
When BSC receives the downlink data from SGSN, if BSC fails to create the BSSGP
instance, then the counter counts.
Unit
Times
51-36

Chapter 52
FR Carried Links Statistics
Table of Contents
Overview ..................................................................................................................52-1
C901460001 Number of Status enquiry Message sent .............................................52-1
C901460002 Number of Status ACK Message received...........................................52-2
C901460003 Number of link exception .....................................................................52-3
C901460004 Number of bytes received on BRCH ....................................................52-4
C901460005 Number of bytes sent on BRCH ..........................................................52-4
52.1 Overview
FR carrier links statistics measures the message transceiving information at FR sublayer
of NS layer at Gb interface in GPRS service, including the number of status queries, the
number of status responses, the number of bytes sent/received on BRCH, and the number
of abnormalities on BRCH. It helps check the running status and load of BRCH.
Statistic unit in this measurement is BRCH.
52.2 C901460001 Number of Status enquiry Message

sent
Description
BSC sends the "Status Enquiry" message to query BRCH's status. This counter counts
the number of "Status Enquiry" messages sent by BSC.
Measurement Point
When BSC sends the "Status Enquiry" message, this counter increments. The
52-1

Figure 52-1 Status Query Process
52.3 C901460002 Number of 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"
Measurement Point
When BSC receives the "Status" message, this counter increments. The measurement
52-2

Chapter 52 FR Carried Links Statistics
52.4 C901460003 Number of link exception

Description
During the process of querying BRCH's status between BSC and SGSN, this counter
counts the number of errors occurred at N392 every N393.
Usage
Check the counter's value to observe the running status of BRCH.
Measurement Point
During the process of querying BRCH's status, this counter increments when error occurs
at N392 every N393. The measurement point is A3, as shown in Figure 52-3.
52-3

52.5 C901460004 Number of bytes received on BRCH

Description
This counter counts the number of bytes received on BRCH of FR sublayer.
Usage
Check the number of bytes received on BRCH to observe the load of BRCH.
Measurement Point
FR accumulates the number of bytes received on BRCH from Gb interface.
52.6 C901460005 Number of bytes sent on BRCH

Description
This counter counts the number of bytes sent on BRCH of FR sublayer.
Usage
Check the number of bytes sent on BRCH to observe the load of BRCH.
52-4

Chapter 52 FR Carried Links Statistics
Measurement Point
FR accumulates the number of bytes sent on BRCH from Gb interface.
52-5

52-6

Chapter 53
OMP PS Service Statistics
Table of Contents
Overview ..................................................................................................................53-1
53.1 Overview
Counters of OMP-PS service statistics counts messages related to PS service on OMP,
including messages of suspension and resuming. These counters are used to observe the
frequency of MS's requesting for terminating GPRS service and resuming GPRS service.

Description
This counter counts the number of SUSPEND messages sent to an SGSN from site or cell
Usage
This counter counts the number of SUSPEND messages sent to an SGSN from site or cell
in downlink within the measurement period.
Measurement Point
The counter counts when the GB_SUSPEND message is sent.
Unit
Times
53-1


received
Description
This counter counts the number of SUSPEND-ACK messages received by site or cell from
an SGSN within the measurement period.
Usage
This counter counts the number of SUSPEND-ACK messages received by site or cell from
Measurement Point
The counter counts when the GB_SUSPEND_ACK message is received from SGSN.
Unit
Times

received
Description
This counter counts the number of SUSPEND-NACK messages received by site or cell
from an SGSN within the measurement period.
Usage
This counter counts the number of SUSPEND-NACK messages received by site or cell
from an SGSN within the measurement period.
Measurement Point
The counter counts when the GB_SUSPEND_NACK message is received from SGSN.
Unit
Times
53-2

Chapter 53 OMP PS Service Statistics

Description
This counter counts the number of RESUME messages sent to an SGSN from site or cell
Usage
This counter counts the number of RESUME messages sent to an SGSN from site or cell
in downlink within the measurement period.
Measurement Point
The counter counts when the GB_RESUME message is sent.
Unit
Times

received
Description
This counter counts the number of RESUME-ACK messages received by site or cell from
Usage
This counter counts the number of RESUME-ACK messages received by site or cell from
Measurement Point
The counter counts when the GB_RESUME_ACK message is received from SGSN.
Unit
Times
53-3


received
Description
This counter counts the number of RESUME-NACK messages received by site or cell from
Usage
This counter counts the number of RESUME-NACK messages received by site or cell from
Measurement Point
The counter counts when the GB_RESUME_NACK message is received from SGSN.
Unit
Times
53-4

Chapter 54
SNS on OMP Statistics
Table of Contents
Overview ..................................................................................................................54-2
C901480001 Number of SNS-SIZE initiations ..........................................................54-2
C901480002 Number of SNS-SIZE received successful acknowledgements............54-3
C901480003 Number of SNS-SIZE failures..............................................................54-3
C901480004 Number of SNS-SIZE initiated by BSC without response.....................54-4
C901480005 Number of SNS-CONFIG initiated by BSC ..........................................54-4
C901480006 Number of SNS-CONFIG initiated by BSC received successful
acknowledgements...................................................................................................54-4
C901480007 Number of SNS-CONFIG initiated by BSC received failed
C901480008 Number of SNS-CONFIG initiated by BSC without response ...............54-5
C901480009 Number of SNS-CONFIG initiated by SGSN received successful
C901480010 Number of SNS-CONFIG initiated by SGSN received failed
C901480011 Number of SNS-ADD initiated by BSC.................................................54-7
C901480012 Number of SNS-ADD initiated by BSC received successful
C901480013 Number of SNS-ADD initiated by BSC received failed
C901480014 Number of SNS-ADD initiated by BSC without response .....................54-9
C901480015 Number of SNS-ADD initiated by SGSN received successful
C901480016 Number of SNS-ADD initiated by SGSN received failed
acknowledgements.................................................................................................54-10
C901480017 Number of SNS-DELETE initiated by BSC ........................................54-10
C901480018 Number of SNS-DELETE initiated by BSC received successful
acknowledgements................................................................................................. 54-11
C901480019 Number of SNS-DELETE initiated by BSC received failed
C901480020 Number of SNS-DELETE initiated by BSC without response .............54-12
C901480021 Number of SNS-DELETE initiated by SGSN received successful
C901480022 Number of SNS-DELETE initiated by SGSN received failed
C901480023 Number of SNS-CHANGEWEIGHT initiated by BSC .........................54-14
54-1

C901480024 Number of SNS-CHANGEWEIGHT initiated by BSC received

successful acknowledgements ...............................................................................54-14
C901480025 Number of SNS-CHANGEWEIGHT initiated by BSC received failed
C901480026 Number of SNS-CHANGEWEIGHT initiated by BSC without
response ................................................................................................................54-15
C901480027 Number of SNS-CHANGEWEIGHT initiated by SGSN received
successful acknowledgements ...............................................................................54-16
C901480028 Number of SNS-CHANGEWEIGHT initiated by SGSN received failed
54.1 Overview
These counters are used when Gb interface adopts IP transmission mode and the
transmission link's IP address and PORT are configured dynamically. They count
messages involved in the flow of port negotiation and port's weight negotiation between
iBSC and sgsnce. Statistic unit in this measurement is NSE.
54.2 C901480001 Number of 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 NSE within the
measurement period.
Measurement Point
The counter counts in the following two cases:
1. The configuration at background is modified, and the database triggers the counting.
2. The SNS process timer expires, triggering the counting.
Unit
Times
Related Features
54-2

Chapter 54 SNS on OMP Statistics
54.3 C901480002 Number of SNS-SIZE received

successful acknowledgements
Description
This counter counts the number of acknowledged responses from NSE after NSE receives
the SNS-SIZE message within the measurement period.
Usage
SNS-SIZE within the measurement period.
Measurement Point
The counter counts when the EV_NSCTRL_SIZE_ACK message from SGSN is received.
Unit
Times
Related Features
54.4 C901480003 Number of 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
receives SNS-SIZE within the measurement period.
Measurement Point
After the SNS-SIZE message is received, this counter counts when NSE sends response
message with the cause of unavailable NSVC or unavailable IPV4.
Unit
Times
Related Features
54-3

54.5 C901480004 Number of SNS-SIZE initiated by BSC

without response
Related Features
54.6 C901480005 Number of SNS-CONFIG initiated by

BSC
Description
This counter counts the number of SNS-CONFIG messages sent by NSE within the
measurement period.
Usage
This counter counts the number of SNS-CONFIG messages sent by NSE within the
measurement period.
Measurement Point
The counter counts after NSE sends the SNS-CONFIG message.
Unit
Times
Related Features

BSC received successful acknowledgements
Description
the SNS-CONFIG message within the measurement period.
Usage
the SNS-CONFIG message successfully within the measurement period.
54-4

Measurement Point
The counter counts when NSE returns the acknowledged response after receiving the
SNS-CONFIG message.
Unit
Times
Related Features

BSC received failed acknowledgements
Description
receives the SNS-CONFIG message within the measurement period.
Usage
receives the SNS-CONFIG message within the measurement period.
Measurement Point
The counter counts when NSE returns the unacknowledged response after receiving the
SNS-CONFIG message.
Unit
Times
Related Features

BSC without response
Description
This counter counts the number of SNS-CONFIG messages initiated by BSC but without
any response within the measurement period.
54-5

Usage
This counter counts the number of SNS-CONFIG messages initiated by BSC but without
Measurement Point
The counter counts when it is timeout during the process of waiting for NSE's response for
the SNS-CONFIG message.
Unit
Times
Related Features

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
Measurement Point
The counter counts when the EV_NSCTRL_CONFIG_IND message is received which
indicates that the IP endpoint at SGSN is recorded successfully.
Unit
Times
Related Features
54-6


SGSN received failed acknowledgements
Description
This counter counts the number of failures of the SNS-CONFIG message initiated by
SGSN within the measurement period.
Usage
This counter counts the number of failures of the SNS-CONFIG message initiated by
SGSN within the measurement period.
Measurement Point
The counter counts when the EV_NSCTRL_CONFIG_IND message is received which
indicates that the IP endpoint at SGSN fails to be recorded.
Unit
Times
Related Features
54.12 C901480011 Number of 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 by BSC within the
measurement period.
Measurement Point
The counter counts when BSC sends the EV_NSOAM_ADD_REQ message.
Unit
Times
54-7

Related Features

Description
This counter counts the number of acknowledged responses of the SNS-ADD message
initiated by BSC within the measurement period.
Usage
This counter counts the number of acknowledged responses of the SNS-ADD message
Measurement Point
When BSC receives the EV_NSCTRL_SNSACK_IND message with acknowledgement,
Unit
Times
Related Features

Description
This counter counts the number of unacknowledged responses of the SNS-ADD message
Usage
This counter counts the number of unacknowledged responses of the SNS-ADD message
Measurement Point
When BSC receives the EV_NSCTRL_SNSACK_IND message with unacknowledgement,
54-8

Unit
Times
Related Features

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 by BSC but without any
response within the measurement period.
Measurement Point
The counter counts when it is timeout during the process of BSC's waiting for the response
for the SNS-ADD message.
Unit
Times
Related Features

Description
This counter counts the number of acknowledged responses of SNS-ADD messages
Usage
This counter counts the number of acknowledged responses of SNS-ADD messages
54-9

Measurement Point
The counter counts when the EV_NSCTRL_ADD_IND message is received which
Unit
Times
Related Features

Description
This counter counts the number of unacknowledged responses of SNS-ADD messages
Usage
This counter counts the number of unacknowledged responses of SNS-ADD messages
Measurement Point
The counter counts when the EV_NSCTRL_ADD_IND message is received which
Unit
Times
Related Features
54.18 C901480017 Number of SNS-DELETE initiated

by BSC
Description
This counter counts the number of SNS-DELETE messages initiated by BSC within the
measurement period.
54-10

Usage
This counter counts the number of SNS-DELETE messages initiated by BSC within the
measurement period.
Measurement Point
The counter counts when the EV_NSOAM_DELETE_REQ message is sent.
Unit
Times
Related Features
54.19 C901480018 Number of SNS-DELETE initiated by

Description
This counter counts the number of acknowledged responses of the SNS-DELETE
message initiated by BSC within the measurement period.
Usage
This counter counts the number of acknowledged responses of the SNS-DELETE
Measurement Point
The counter counts when BSC receives the SNS-ACK message with acknowledgement.
Unit
Times
Related Features
54-11


Description
This counter counts the number of unacknowledged responses of the SNS-DELETE
Usage
This counter counts the number of unacknowledged responses of the SNS-DELETE
Measurement Point
The counter counts when BSC receives the SNS-ACK message with unacknowledgement.
Unit
Times
Related Features

Description
This counter counts the number of SNS-DELETE messages initiated by BSC but without
Usage
This counter counts the number of SNS-DELETE messages initiated by BSC but without
Measurement Point
of SNS-DELETE message.
Unit
Times
54-12

Related Features

Description
This counter counts the number of acknowledged responses of SNS-DELETE messages
Usage
This counter counts the number of acknowledged responses of SNS-DELETE messages
Measurement Point
The counter counts when the EV_NSCTRL_DELETE_IND message is received which
Unit
Times
Related Features

Description
This counter counts the number of unacknowledged responses of SNS-DELETE
messages initiated by SGSN within the measurement period.
Usage
This counter counts the number of unacknowledged responses of SNS-DELETE
messages initiated by SGSN within the measurement period.
Measurement Point
The counter counts when the EV_NSCTRL_DELETE_IND message is received which
54-13

Unit
Times
Related Features
54.24 C901480023 Number of SNS-CHANGEWEIGHT

initiated by BSC
Description
This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC
Usage
Measurement Point
The counter counts when BSC receives the EV_NSOAM_CHANGEWEIGHT_REQ
message.
Unit
Times
Related Features

initiated by BSC received successful
acknowledgements
Description
This counter counts the number of acknowledged responses of the
SNS-CHANGEWEIGHT message initiated by BSC within the measurement period.
Usage
54-14

Measurement Point
When BSC receives the EV_NSCTRL_SNSACK_IND message with acknowledgement,
Unit
Times
Related Features

initiated by BSC received failed acknowledgements
Description
This counter counts the number of unacknowledged responses of the
Usage
Measurement Point
When BSC receives the EV_NSCTRL_SNSACK_IND message with unacknowledgement,
Unit
Times
Related Features

initiated by BSC without response
Description
but without any response within the measurement period.
54-15

Usage
but without any response within the measurement period.
Measurement Point
for the SNS-CHANGEWEIGHT message.
Unit
Times
Related Features

initiated by SGSN received successful
acknowledgements
Description
SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period.
Usage
Measurement Point
The counter counts when the EV_NSCTRL_CHANGEWEIGHT_IND message is received
which indicates that the IP endpoint at SGSN is recorded successfully.
Unit
Times
Related Features
54-16


initiated by SGSN received failed
acknowledgements
Description
Usage
Measurement Point
The counter counts when the EV_NSCTRL_CHANGEWEIGHT_IND message is received
which indicates that the IP endpoint at SGSN fails to be recorded.
Unit
Times
Related Features
54-17

54-18

Chapter 55
IPGB StrongARM NSVC
Statistics
Table of Contents
Overview ..................................................................................................................55-1
C901490001 Number of bytes received from SGSN.................................................55-1
C901490002 Number of bytes sent to SGSN ...........................................................55-1
C901490003 Number of PDU data sent by NS sub layer..........................................55-2
C901490004 Number of PDU data received by NS sub layer ...................................55-2
C901490005 Number of PDU data discarded by NS sub layer .................................55-3
55.1 Overview
IPGB StrongARM NSVC statistics measures the signaling interaction and data
transmission at NS layer of Gb interface in GPRS service.
55.2 C901490001 Number of bytes received from SGSN

Related Features
55.3 C901490002 Number of bytes sent to SGSN

Description
This counter counts the number of bytes sent to SGSN from NS sub layer.
Usage
55-1

Measurement Point
IP accumulates the number of bytes sent each time. The measurement point is A1, as
Figure 55-1 Uplink NS Data
Unit
Byte
Related Features
55.4 C901490003 Number of PDU data sent by NS sub

layer
Related Features
55.5 C901490004 Number of PDU data received by NS

sub layer
Related Features
55-2

Chapter 55 IPGB StrongARM NSVC Statistics
55.6 C901490005 Number of PDU data discarded by

NS sub layer
Related Features
55-3

55-4

Chapter 56
IPGB StrongARM Gb
Statistics
Table of Contents
Overview ..................................................................................................................56-1
56.1 Overview
IPGB StrongARM Gb message statistics measures the number of transceiving
uplink/downlink data at BSSGP layer of Gb interface in GPRS service.

Related Features

Related Features
56-1

56-2

Chapter 57
Queue Measurement
Table of Contents
Overview ..................................................................................................................57-1
C901510001 Average length of queue .....................................................................57-1
C901510002 Duration of queuing .............................................................................57-2
C901510003 Number of queuing..............................................................................57-4
C901510004 Duration of queuing success ...............................................................57-6
C901510005 Number of queuing success ................................................................57-7
57.1 Overview
Queue measurement counters reflect the following information: the number of queuing
users in a cell, the total queuing time, the number of queuing successes, and the duration
of queuing success. These counters are used to find out how busy the channels are in a
cell.
The measurement unit is cell.
57.2 C901510001 Average length of queue

Description
This counter counts the average queue length that a user has to wait for after entering the
queue during the assignment or handover process.
Usage
The counter's value is calculated by dividing the total queue length by the number of
queues.
Measurement Point
When the measurement period expires, divide the total queue length by the number of
queues to calculate the counter's value. The measurement point is shown in Figure 57-1.
57-1

Figure 57-1 Measurement Point of Average length of queue
Unit
Times
57.3 C901510002 Duration of 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
57-2

Chapter 57 Queue Measurement
time is recorded; when the user exits the queue, the total queuing time is calculated by
subtracting the start queuing time from the current time.
Usage
The counter is used to find out how busy the channels are in a cell.
Measurement Point
This counter counts the total queuing time of a user in the cell. When the user enters
the queue, the start queuing time is recorded; when the user exits the queue, the total
queuing time is calculated by subtracting the start queuing time from the current time. The
Figure 57-2 Measurement Point of Queuing Duration when Queuing Fails
57-3

Figure 57-3 Measurement Point of Queuing Duration when Queuing Succeeds
Unit
Times
57.4 C901510003 Number of queuing

Description
This counter counts the number of users entering the queue during the assignment or
handover process. The counter increments every time a user exits the queue.
Usage
This counter is used to find out how many queuing users there are in a cell.
Measurement Point
This counter counts the number of queuing users in a cell. The counter increments every
time a user exits the queue. The measurement point is B2, as shown in Figure 57-4 and
Figure 57-5.
57-4

Figure 57-4 Measurement Point of Queuing Duration when Queuing Fails
57-5

Unit
Times
57.5 C901510004 Duration of queuing success

Description
This counter counts the total queuing time of a user from entering the queue to acquiring
the resource. When the user enters the queue, the start queuing time is recorded; when
the user exits the queue and acquires the resource, the total queuing time is calculated by
subtracting the start queuing time from the current time.
Usage
This counter is used to find out how long it takes a user to queue in the cell before acquiring
the resource.
Measurement Point
This counter counts the total queuing time of a user in the cell before acquiring the
resource. When the user enters the queue, the start queuing time is recorded; when the
user exits the queue and acquires the resource, the total queuing time is calculated by
subtracting the start queuing time from the current time. The measurement point is B2,
57-6

Unit
Second
57.6 C901510005 Number of 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 acquiring resource after
queuing in a cell.
Measurement Point
This counter counts the number of users acquiring resource after queuing in a cell.
The counter increments every time a user exits the queue and acquires resource. The
Unit
Times
57-7

57-8

Chapter 58
Handover Synchronization
Mode Measurement
Table of Contents
Overview ..................................................................................................................58-1
C901520001 Number of synchronous handover executions .....................................58-2
C901520002 Number of synchronous handover successes .....................................58-3
C901520003 Number of pre-synchronous handover executions...............................58-3
C901520004 Number of pre-synchronous handover successes ...............................58-4
C901520005 Number of pseudo-synchronous handover executions ........................58-4
C901520006 Number of pseudo-synchronous handover successes.........................58-5
C901520007 Number of asynchronous handover executions ...................................58-5
C901520008 Number of asynchronous handover successes....................................58-6
58.1 Overview
Counters of handover synchronization mode measurement count in the following two
cases: execution of different handover modes and successes of different handover
modes. If the uplink channel activation is completed, the counter counts the number
of handover executions. If the uplink handover (assignment) is completed, the counter
counts the number of handover successes. The measurement point of counting handover
executions is A, and the measurement point of counting handover successes is B.
Figure 58-1 Measurement Point of BTS Sending Channel Activation Completion

Message to BSC
58-1

Figure 58-2 Measurement Point of MS Sending Assignment/Handover Completion

Message to BSC
58.2 C901520001 Number of synchronous handover

executions
Description
This counter counts the number of synchronous handover executions after the uplink
channel activation completion message is received.
Usage
This counter is used to find out the number of synchronous handover executions in the
cell.
Measurement Point
After BSC receives the channel activation completion message from BTS, if the handover
is synchronous handover, the counter increments.
Unit
Times
58-2

Chapter 58 Handover Synchronization Mode Measurement

successes
Description
This counter counts the number of successful synchronous handovers after the uplink
handover(assignment) completion message is received.
Usage
This counter is used to find out the number of successful synchronous handovers in the
cell.
Measurement Point
After BSC receives the uplink handover (assignment) completion message from BTS, if
the handover is synchronous handover, the counter increments.
Unit
Times
58.4 C901520003 Number of pre-synchronous

handover executions
Description
This counter counts the number of pre-synchronous handover executions after the uplink
Usage
This counter is used to find out the number of pre-synchronous handover executions in
the cell.
Measurement Point
is pre-synchronous handover, the counter increments.
Unit
Times
58-3


handover successes
Description
This counter counts the number of successful pre-synchronous handovers after the uplink
Usage
This counter is used to find out the number of successful pre-synchronous handovers in
the cell.
Measurement Point
the handover is pre-synchronous handover, the counter increments.
Unit
Times
58.6 C901520005 Number of pseudo-synchronous

handover executions
Description
This counter counts the number of pseudo-synchronous handover executions after the
uplink channel activation completion message is received.
Usage
This counter is used to find out the number of pseudo-synchronous handover executions
in the cell.
Measurement Point
is pseudo-synchronous handover, the counter increments.
Unit
Times
58-4

Chapter 58 Handover Synchronization Mode Measurement
58.7 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.
Measurement Point
the handover is pseudo-synchronous handover, the counter increments.
Unit
Times
58.8 C901520007 Number of asynchronous handover

executions
Description
This counter counts the number of asynchronous handover executions after the uplink
Usage
This counter is used to find out the number of asynchronous handover executions in the
cell.
Measurement Point
is asynchronous handover, the counter increments.
Unit
Times
58-5


successes
Description
This counter counts the number of successful asynchronous handovers after the uplink
Usage
This counter is used to find out the number of successful asynchronous handovers in the
cell.
Measurement Point
the handover is asynchronous handover, the counter increments.
Unit
Times
58-6

Chapter 59
Paging Message
Measurement
Table of Contents
Overview ..................................................................................................................59-1
C901530001 Number of paging messages...............................................................59-2
C901530002 Number of paging messages from PS of Gb interface .........................59-3
C901530003 Number of paging messages from CS of Gb interface .........................59-4
59.1 Overview
Counters of paging message measurement count the number of paging messages from
A-interface and the number of PS paging messages and CS paging messages from Gb
interface. Measurement points of paging message measurement counters are A, as shown
Figure 59-1 Measurement Point of BSC Receiving Paging Message from A-Interface
59-1

Figure 59-2 Measurement Point of BSC Receiving PS/CS Paging Message from Gb
Interface
59.2 C901530001 Number of paging messages

Description
This counter counts the number of paging messages received by BSC from A-interface.
Usage
This counter is used to find out the number of paging messages received by BSC from
A-interface.
Measurement Point
When BSC receives the paging message from A-interface, the counter increments. The
59-2

Chapter 59 Paging Message Measurement
Figure 59-3 Measurement Point of BSC Receiving Paging Message from A-Interface
Unit
Times
59.3 C901530002 Number of 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 counter increments.
59-3

Interface
Measurement Point
When BSC receives the PS paging message from Gb interface, the counter increments.
Unit
Times
59.4 C901530003 Number of 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 counter increments.
59-4

Chapter 59 Paging Message Measurement
Interface
Measurement Point
When BSC receives the CS paging message from Gb interface, the counter increments.
Unit
Times
59-5

59-6

Chapter 60
Reserved Channel
Measurement
Table of Contents
Overview ..................................................................................................................60-1
C901540001 Number of voice allocations of reserved full rate channel in
assignment...............................................................................................................60-1
C901540002 Number of data allocations of reserved full rate channel in
assignment...............................................................................................................60-2
C901540003 Number of voice allocations of reserved full rate channel in handover .60-2
C901540004 Number of data allocations of reserved full rate channel in handover ..60-3
C901540005 Reserved seizure duration of reserved full rate channel ......................60-3
60.1 Overview
Counters of reserved channel measurement describe the occupation condition of reserved
channels in the cell. If the channel resource request to the database succeeds and the
acquired resource is reserved channel, then the counter counts.
60.2 C901540001 Number of voice allocations of

reserved full rate channel in assignment
Description
During the channel assignment process, when the voice channel resource request to the
database succeeds and the acquired resource is reserved channel, the counter counts.
Usage
This counter is used to find out the occupation condition of reserved channels.
Measurement Point
During the channel assignment process, when the voice channel resource request to
the database succeeds and the acquired resource is reserved channel, the counter
increments.
60-1

Unit
Times
60.3 C901540002 Number of data allocations of

reserved full rate channel in assignment
Description
During the channel assignment process, when the data channel resource request to the
Usage
Measurement Point
During the channel assignment process, when the data channel resource request to
increments.
Unit
Times
60.4 C901540003 Number of voice allocations of

reserved full rate channel in handover
Description
During the channel handover process, when the voice channel resource request to the
Usage
Measurement Point
During the channel handover process, when the voice channel resource request to
increments.
Unit
Times
60-2

Chapter 60 Reserved Channel Measurement
60.5 C901540004 Number of data allocations of

reserved full rate channel in handover
Description
During the channel handover process, when the data channel resource request to the
Usage
Measurement Point
During the channel handover process, when the data channel resource request to
increments.
Unit
Times
60.6 C901540005 Reserved seizure duration of

reserved full rate channel
Description
This counter counts the total duration of reserved channels being occupied in the cell.
Usage
This counter is used to find out the occupation condition of reserved channels in the cell.
Measurement Point
BSC performs statistics every 15 minutes.
Unit
Second
60-3

60-4

Chapter 61
SCCP Connection
Measurement
Table of Contents
Overview ..................................................................................................................61-1
C901550001 Number of BSC originated SCCP Connection attempts .......................61-1
C901550002 Number of BSC originated SCCP Connection success........................61-2
C901550003 Number of BSC originated SCCP Connection failure due to timeout....61-4
C901550004 Number of negative replies for SCCP connection request ...................61-4
C901550005 Number of MSC originated SCCP Connection Requests .....................61-5
C901550006 Number of MSC originated SCCP Connection success .......................61-6
61.1 Overview
Counters of SCCP connection measurement count the following information: the number
of SCCP link establishment requests initiated by BSC, the number of successful SCCP
link establishments initiated by BSC, the number of link establishment failure due to
timeout, the number of link esablishment being rejected, the number of SCCP link
establishment requests initiated by MSC, and the number of successful SCCP link
establishments initiated by MSC.
Statistic unit in this measurement is office.
61.2 C901550001 Number of BSC originated SCCP

Connection attempts
Description
This counter counts the number of SCCP link establishment requests initiated by BSC
towards MSC, that is, the number of BSC's sending the ConnectRequest message to MSC.
Usage
This counter is used to find out the number of BSC's sending the SCCP link establishment
requests to MSC.
61-1

Measurement Point
When BSC sends the Connect Req message to MSC, the counter increments. The
Figure 61-1 Measurement Point of Number of BSC originated SCCP Connection

attempts
Unit
Times

Connection success
Description
This counter counts the number of successful SCCP link establishments initiated by BSC
towards MSC.
61-2

Chapter 61 SCCP Connection Measurement
Usage
This counter is used to find out the number of successful SCCP link establishments initiated
by BSC towards MSC.
Measurement Point
When BSC receives the SCCP connection confirmation message from MSC, the counter
Figure 61-2 Measurement Point of Number of BSC originated SCCP Connection

attempts
Unit
Times
61-3


Connection failure due to timeout
Description
This counter counts the number of SCCP link establishment failures due to timeout, and
the SCCP link establishment is initiated by BSC towards MSC.
Usage
This counter is used to find out the number of SCCP link establishment failures due to
timeout, and the SCCP link establishment is initiated by BSC towards MSC.
Measurement Point
When the timer T9105 expires, the counter increments.
Unit
Times
61.5 C901550004 Number of negative replies for SCCP

connection request
Description
This counter counts the number of SCCP link establishment requests being rejected, and
the SCCP link establishment is initiated by BSC towards MSC.
Usage
This counter is used to find out the number of SCCP link establishment requests being
rejected, and the SCCP link establishment is initiated by BSC towards MSC.
Measurement Point
When the Rana process receives the DISCONNECT IND message from the ADispatch
process, the counter increments. The measurement point is A, as shown in Figure 61-3.
61-4

Figure 61-3 Measurement Point of Number of negative replies for SCCP connection
request
Unit
Times
61.6 C901550005 Number of MSC originated SCCP

Connection Requests
Description
This counter counts the number of SCCP link establishment requests initiated by MSC.
Usage
This counter is used to find out the number of SCCP link establishment requests initiated
by MSC.
Measurement Point
When BSC receives the Connect Indication message from MSC, the counter increments.
61-5

Figure 61-4 Measurement Point of Number of MSC originated SCCP Connection

Requests
Unit
Times
61.7 C901550006 Number of MSC originated SCCP

Connection success
Description
This counter counts the number of successful SCCP link establishments initiated by MSC.
Usage
This counter is used to find out the number of successful SCCP link establishments initiated
by MSC.
Measurement Point
When BSC sends the Connect Response message to MSC, the counter increments. The
61-6

Figure 61-5 Measurement Point of Number of MSC originated SCCP Connection

success
Unit
Times
61-7

61-8

Chapter 62
DTM Cell Measurement
Table of Contents
Overview ..................................................................................................................62-2
C901560001 Number of voice access in mobile with DTM ability .............................62-2
C901560002 Number of packet access in mobile with DTM ability ...........................62-2
C901560003 Number of received IMSI when link establish ......................................62-3
C901560004 Number of RANCS module received IMSI when handover ..................62-4
C901560005 Number of mobile sent GTTP message under DTM mode...................62-4
C901560006 Number of BSC successfully sent GTTP message under DTM mode ..62-5
C901560007 Number of DTM attempts in mobile .....................................................62-5
C901560008 Number of DTM uplink attempt failure .................................................62-6
C901560009 Number of UL DTM database resource assignment success in
dedicated mode .......................................................................................................62-6
C901560010 Number of UL DTM database resource assignment failure in
dedicated mode .......................................................................................................62-7
C901560011 Number of handover(intra-cell) attempts due to UL DTM .....................62-8
C901560012 Number of handover(intra-cell) success due to uplink DTM .................62-8
C901560013 Number of handover(intra-cell) failure due to uplink DTM ....................62-9
C901560014 Number of DTM failure due to handover..............................................62-9
C901560015 Number of UL DTM link establishment success.................................62-10
C901560016 Attempt number of sending LLC packet on FACCH in dedicated
mode .....................................................................................................................62-10
C901560017 Number of successfully sent LLC packet on FACCH in dedicated
mode ..................................................................................................................... 62-11
C901560018 Attempt Number of DTM established due to SGSN sent LLC
packets .................................................................................................................. 62-11
C901560019 Number of DTM attempts failure........................................................62-12
C901560020 Number of DL DTM resource assignment success ............................62-13
C901560021 Number of DL DTM resource assignment failure ...............................62-13
C901560022 Number of handover(intra-cell) attempts due to DL DTM ...................62-14
C901560023 Number of successfully handover occurs due to DL DTM..................62-14
C901560024 Number of handover failure occurs due to DL DTM ...........................62-15
C901560025 Number of DL DTM failure occurs due to handover ...........................62-15
C901560026 Number of successfully DL DTM establishment.................................62-16
62-1

62.1 Overview
DTM cell measurement studies the DTM service condition of mobile phones that have
DTM capability, including resource request for DTM service, intra-cell handover due to
DTM service, and DTM service establishment. The measurement unit is cell.
62.2 C901560001 Number of voice access in mobile

with DTM ability
Description
This counter counts the number of accessing voice service by mobile phone that has the
DTM capability in the cell within the measurement period.
Usage
This counter is used to find out the number of accessing voice service by mobile phone
that has the DTM capability in the cell.
Measurement Point
1. When BSC receives the Classmark Change message from MS, if Classmark3 carries
the information that the MS has DTM 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 destination cell receives
the Radio Apply message, if Classmark3 carries the information that the MS has DTM
multi-timeslot capability, the counter increments.
Unit
Times
Related Features
62.3 C901560002 Number of 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.
62-2

Chapter 62 DTM Cell Measurement
Usage
This counter is used to find out the number of accessing packet service by mobile phone
that has the DTM capability in the cell.
Measurement Point
1. During uplink two-step access, when BSC receives the resource request which
indicates that MS has DTM multi-timeslot capability, the counter increments.
2. During downlink access, when BSC receives the downlink assignment request which
indicates that MS has DTM multi-timeslot capability, the counter increments.
Unit
Times
Related Features
62.4 C901560003 Number of received IMSI when link

establish
Description
This counter counts the number of IMSIs received during link establishment in the cell
Usage
This counter is used to find out the number of IMSIs received during link establishment in
the cell.
Measurement Point
When BSC receives the COMMON ID message from MSC, if no IMSI information is saved
originally, then the IMSI information carried in the COMMON ID message is saved, and
Unit
Times
Related Features
62-3

62.5 C901560004 Number of RANCS module received

IMSI when handover
Description
This counter counts the number of IMSIs received by the RANCS module during intra-cell
handover within the measurement period.
Usage
This counter is used to find out the number of IMSIs received by the RANCS module during
intra-cell handover.
Measurement Point
During inter-cell handover or external handover, when the destination cell receives the
Radio Apply message which carries the IMSI information, the counter increments.
Unit
Times
Related Features
62.6 C901560005 Number of mobile sent GTTP

message under DTM mode
Description
This counter counts the number of GTTP messages sent by MS in dedicated mode in the
cell within the measurement period.
Usage
This counter is used to find out the number of GTTP messages sent by MS in dedicated
mode in the cell.
Measurement Point
During BSC's voice service process, the counter increments when the GTTP message
(GPRS information) is received from MS.
Unit
Times
62-4

Related Features
62.7 C901560006 Number of 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 Point
During BSC's voice service process, when the GTTP message is received from MS and
then is successfully sent to SGSN, the counter increments.
Unit
Times
Related Features
62.8 C901560007 Number of DTM attempts in mobile

Description
This counter counts the number of attempts of uplink DTM service initiated by MS in
dedicated mode in the cell within the measurement period.
Usage
This counter is used to find out the number of attempts of uplink DTM service initiated by
MS in dedicated mode in the cell.
Measurement Point
During BSC's voice service process, the counter increments when the DTM request
message is received from MS.
62-5

Unit
Times
Related Features
62.9 C901560008 Number of DTM uplink attempt failure

Description
This counter counts the number of failed attempts of uplink DTM service in the cell within
Usage
This counter is used to find out the number of failed attempts of uplink DTM service in the
cell.
Measurement Point
1. When BSC receives the DTM request from MS but does not process due to MS not
on SDCCH, the counter increments.
2. When BSC receives the DTM request from MS but does not process because there is
no Classmark3 information of the MS, the counter increments.
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
Related Features
62.10 C901560009 Number of UL 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 within the measurement period.
62-6

Usage
This counter is used to find out the number of uplink DTM service requesting for database
resource successfully in dedicated mode in the cell.
Measurement Point
During BSC's voice service process, when the DTM request is received from MS and the
resource is acquired successfully, the counter increments.
Unit
Times
Related Features
62.11 C901560010 Number of UL DTM database

resource assignment failure in dedicated mode
Description
This counter counts the number of failed uplink DTM service requesting for database
resource in dedicated mode in the cell within the measurement period.
Usage
This counter is used to find out the number of failed uplink DTM service requesting for
database resource in dedicated mode in the cell.
Measurement Point
During BSC's voice service process, when the DTM request is received from MS and the
resource request fails, the counter increments.
Unit
Times
Related Features
62-7

62.12 C901560011 Number of handover(intra-cell)

attempts due to UL DTM
Description
This counter counts the number of attempts of intra-cell handover due to uplink DTM
service in dedicated mode in the cell within the measurement period.
Usage
This counter is used to find out the number of attempts of intra-cell handover due to uplink
DTM service in dedicated mode in the cell.
Measurement Point
During BSC's voice service process, when the DTM request is received from MS, the voice
channel is reallocated for the resource request, if intra-cell handover is required and the
DTM resource assignment is in uplink, the counter increments.
Unit
Times
Related Features

success due to uplink DTM
Description
This counter counts the number of successful intra-cell handovers due to uplink DTM
Usage
This counter is used to find out the number of successful intra-cell handovers due to uplink
Measurement Point
After the intra-cell handover is completed, if BSC judges that the MS is implementing DTM
service, the counter increments.
Unit
Times
62-8

Related Features

failure due to uplink DTM
Description
This counter counts the number of failed intra-cell handovers due to uplink DTM service in
Usage
This counter is used to find out the number of failed intra-cell handovers due to uplink DTM
service in dedicated mode in the cell.
Measurement Point
During intra-cell handover, when the handover fails due to BSC assignment failure or
T3107 timeout, if BSC judges that the MS is implementing DTM service, the counter
increments.
Unit
Times
Related Features
62.15 C901560014 Number of DTM failure due to

handover
Description
This counter counts the number of failed uplink DTM service due to handover in dedicated
Usage
This counter is used to find out the number of failed uplink DTM service due to handover
in dedicated mode in the cell within the measurement period.
Measurement Point
During BSC's voice service process, when the DTM request is received and the DTM
service fails due to MS being in the handover status, the counter increments.
62-9

Unit
Times
Related Features
62.16 C901560015 Number of UL DTM link

establishment success
Description
This counter counts the number of successful uplink DTM service establishments in
Usage
This counter is used to find out the number of successful uplink DTM service
establishments in dedicated mode in the cell.
Measurement Point
During the uplink establishment process, the ranps module on CMP inside BSC receives
the establishment indication message from the MAC module on UPPB, if it is judged that
MS is implementing DTM service, the counter increments.
Unit
Times
Related Features
62.17 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
Usage
This counter is used to find out the number of attempts of sending LLC frame on FACCH
62-10

Measurement Point
During BSC's voice service process, when the downlink LLC data frame is received in
GTTP mode, the counter increments.
Unit
Times
Related Features
62.18 C901560017 Number of successfully sent LLC

packet on FACCH in dedicated mode
Description
This counter counts the number of successfully sending LLC frame on FACCH in dedicated
Usage
This counter is used to find out the number of successfully sending LLC frame on FACCH
Measurement Point
During BSC's voice service process, when the LLC frame is sent on FACCH in GTTP
mode, the counter increments.
Unit
Times
Related Features
62.19 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.
62-11

Usage
This counter is used to find out the number of attempts of SGSN's sending LLC frame to
trigger DTM service establishment in dedicated mode in the cell within the measurement
period.
Measurement Point
During BSC's voice service process, when DTM service is intiated due to receiving LLC
data frame sent by SGSN, the counter increments.
Unit
Times
Related Features
62.20 C901560019 Number of DTM attempts failure

Description
This counter counts the number of failed attempts of downlink DTM service in the cell within
Usage
This counter is used to find out the number of failed attempts of downlink DTM service in
the cell.
Measurement Point
During BSC's voice service process, when DTM service is initiated due to receiving LLC
data frame sent by SGSN, if the system judges that the rancs module on CMP is not in
stable service status, then the following messages are not processed: DTM assignment
message, PS assignment message, and LLC frame sending message. In this case, the
counter increments.
Unit
Times
Related Features
62-12

62.21 C901560020 Number of DL DTM resource

assignment success
Description
This counter counts the number of downlink DTM service requesting for database resource
successfully in dedicated mode in the cell within the measurement period.
Usage
This counter is used to find out the number of downlink DTM service requesting for
database resource successfully in dedicated mode in the cell.
Measurement Point
During BSC's voice service process, when DTM service is intiated due to receiving
LLC data frame sent by SGSN and the resource is acquired successfully, the counter
increments.
Unit
Times
Related Features
62.22 C901560021 Number of DL 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 within the measurement period.
Usage
This counter is used to find out the number of failed downlink DTM service requesting for
database resource in dedicated mode in the cell.
Measurement Point
During BSC's voice service process, when DTM service is intiated due to receiving LLC
data frame sent by SGSN and the resource request fails, the counter increments.
62-13

Unit
Times
Related Features

attempts due to DL DTM
Description
This counter counts the number of attempts of intra-cell handover due to downlink DTM
Usage
This counter is used to find out the number of attempts of intra-cell handover due to
downlink DTM service in dedicated mode in the cell.
Measurement Point
During BSC's voice service process, when the DTM request is received from MS, the voice
channel is reallocated for the resource request, if intra-cell handover is required and the
DTM resource assignment is in downlink, the counter increments.
Unit
Times
Related Features
62.24 C901560023 Number of successfully handover

occurs due to DL DTM
Description
This counter counts the number of successful intra-cell handovers due to downlink DTM
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.
62-14

Measurement Point
After the intra-cell handover is completed, if BSC judges that the MS is implementing DTM
service and the DTM resource assignment is in downlink, the counter increments.
Unit
Times
Related Features
62.25 C901560024 Number of handover failure occurs

due to DL DTM
Description
This counter counts the number of failed intra-cell handovers due to downlink DTM service
Usage
This counter is used to find out the number of failed intra-cell handovers due to downlink
Measurement Point
During intra-cell handover, when the handover fails due to BSC assignment failure or
T3107 timeout, if BSC judges that the MS is implementing DTM service and the DTM
resource assignment is in downlink, the counter increments.
Unit
Times
Related Features
62.26 C901560025 Number of DL DTM failure occurs

due to handover
Description
This counter counts the number of failed downlink DTM service due to handover in
62-15

Usage
This counter is used to find out the number of failed downlink DTM service due to handover
Measurement Point
During BSC's voice service process, when the DTM request is received, if DTM service
fails due to MS being in the handover status and if DTM service is in downlink, the counter
increments.
Unit
Times
Related Features
62.27 C901560026 Number of successfully DL DTM

establishment
Description
This counter counts the number of successful downlink DTM service establishments in
Usage
This counter is used to find out the number of successful downlink DTM service
establishments in dedicated mode in the cell.
Measurement Point
During downlink DTM service process, when the RANPS module on CMP inside BSC
receives the instance establishment indication message from the MAC module on UPPB,
Unit
Times
Related Features
62-16

Chapter 63
LAPD Measurement
Table of Contents
Overview ..................................................................................................................63-1
C901570001 Number of Application Data Package from CMP .................................63-2
C901570002 Number of BTS Application Data Package Sent to MP ........................63-2
C901570003 Number of Data Package Ack Sent to Application ...............................63-2
C901570004 Number of Application Data Package Ack from BTS............................63-3
C901570005 Number of Application Nack Data Package sent to BTS ......................63-3
C901570006 Number of BTS Application Nack Data Package Receive by BTS .......63-4
C901570007 Number of Sending Frame ..................................................................63-4
C901570008 Number of Received Frame.................................................................63-4
C901570009 Number of High Priority Queue overflow..............................................63-5
C901570010 Number of Low Priority Queue overflow ..............................................63-5
C901570011 Number of Success in High Priority Queue ..........................................63-6
C901570012 Number of Success in Low Priority Queue...........................................63-6
C901570013 Number of in Queue Request UB Fail..................................................63-6
C901570014 Resend Number ..................................................................................63-7
C901570015 Resend Request Number ....................................................................63-7
C901570016 Establish Link Number ........................................................................63-8
C901570017 Broken Number ...................................................................................63-9
C901570018 Protocol Error Number ........................................................................63-9
C901570019 Number of T200 Overtime .................................................................63-10
C901570020 Number of T201 Overtime .................................................................63-10
C901570021 Number of T203 Overtime ................................................................. 63-11
C901570022 Number of T204 Overtime ................................................................. 63-11
C901570023 Number of abnormal hop frame ......................................................... 63-11
C901570024 Number of normal hop frame.............................................................63-12
C901570025 Multi Channel Link Lose Frame .........................................................63-12
C901570026 No useful channel .............................................................................63-13
C901570027 Max Up Flow .....................................................................................63-13
C901570028 Max Down Flow.................................................................................63-13
C901570029 Current Up Flow ................................................................................63-14
C901570030 Current Down Flow............................................................................63-14
63.1 Overview
LAPD measurement counters reflect the message transceiving condition at Abis interface
between BSC and BTS. The measurement takes each LAPD link (channel cluster) as
63-1

the statistics unit. It measures the transmitted data volume on LAPD link and message
transceiving condition on the link, and records exceptions in LAPD protocol processing.
63.2 C901570001 Number of Application Data Package

from CMP
Description
This counter counts the number of downlink data messages received from CMP on LAPD
link.
Usage
This counter is used to find out the number of service and O&M messages received from
CMP on LAPD link.
Measurement Point
The counter counts when SPB receives the EV_DLDATA_REQ message from CMP.
63.3 C901570002 Number of BTS Application Data

Package 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 Point
The counter counts when CMP receives the EV_DLDATA_IND message from SPB.
63.4 C901570003 Number of Data Package Ack Sent

to Application
Description
This counter counts the number of downlink I frames sent to BTS on LAPD link.
63-2

Chapter 63 LAPD Measurement
Usage
This counter is used to find out the number of LAPD information frames sent to BTS on
LAPD link.
Measurement Point
The counter counts when BTS receives the I frame from SPB.
63.5 C901570004 Number of Application Data Package

Ack from BTS
Description
This counter counts the number of uplink I frames received from BTS on LAPD link.
Usage
This counter is used to find out the number of LAPD information frames received from BTS
on LAPD link.
Measurement Point
The counter counts when SPB receives the I frame from BTS.
63.6 C901570005 Number of 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 frames sent to BTS on
LAPD link.
Measurement Point
The counter counts when BTS receives the UI frame from SPB.
63-3

63.7 C901570006 Number of 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 frames received from
BTS on LAPD link.
Measurement Point
The counter counts when SPB receives the UI frame from BTS.
63.8 C901570007 Number of 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 frames sent to BTS on
LAPD link.
Measurement Point
The counter counts when BTS receives the LAPD message from SPB.
63.9 C901570008 Number of 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 frames received from
BTS on LAPD link.
Measurement Point
The counter counts when SPB receives the LAPD message from BTS.
63-4

63.10 C901570009 Number of High Priority Queue

overflow
Description
This counter counts the number of overflows of high-priority LAPD message entering the
queue.
Each LAPD link has a high-priority message-sending queue, which saves high-priority
messages to be sent. If there are too many messages to be sent, the queue is full, causing
that subsequent messages to be sent are discarded. This counter counts the number of
discarded messages due to the queue being full.
Usage
This counter is used to find out exceptions in receiving high-priority LAPD messages from
CMP on LAPD link.
Measurement Point
The counter counts when a message is discarded due to the high-priority LAPD message
queue being full.
63.11 C901570010 Number of Low Priority Queue

overflow
Description
This counter counts the number of overflows of low-priority LAPD message entering the
queue.
Each LAPD link has a low-priority message-sending queue, which saves low-priority
messages to be sent. If there are too many messages to be sent, the queue is full,
causing that subsequent messages to be sent are discarded. This counter counts the
number of discarded messages due to the queue being full.
Usage
This counter is used to find out exceptions in receiving low-priority LAPD messages from
CMP on LAPD link.
Measurement Point
The counter counts when a message is discarded due to the low-priority LAPD message
queue being full.
63-5

63.12 C901570011 Number of Success in High Priority

Queue
Description
This counter counts the number of high-priority LAPD message entering the queue
successfully.
Usage
This counter is used to find out the number of successfully receiving high-priority LAPD
messages from CMP on LAPD link.
Measurement Point
The counter counts when SPB receives the high-priority message from CMP.
63.13 C901570012 Number of Success in Low Priority

Queue
Description
This counter counts the number of low-priority LAPD message entering the queue
successfully.
Usage
This counter is used to find out the number of successfully receiving low-priority LAPD
messages from CMP on LAPD link.
Measurement Point
The counter counts when SPB receives the low-priority message from CMP.
63.14 C901570013 Number of in Queue Request UB Fail

Description
This counter counts the number of failed UB requests when receiving the high/low-priority
message on LAPD link.
Usage
This counter is used to find out memory request failure when receiving the high/low-priority
LAPD message from CMP on LAPD link.
63-6

Measurement Point
The counter counts when UB request fails during the process of receiving the
high/low-priority message on LAPD link.
63.15 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 Point
The counter counts when I frame is resent on LAPD link due to T200 timeout. The
Figure 63-1 Measurement Point of Resending I Frame on LAPD Link due to T200
Timeout
63.16 C901570015 Resend Request Number

Description
This counter counts the number of resending frame on LAPD link according to the opposite
end's response.
In acknowledgement transmission mode, if the opposite end returns the
unacknowledgement frame after a data frame is sent, it indicates that the data frame is
63-7

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.
Measurement Point
Figure 63-2 Measurement Point of Number of Resending Frame upon Request
63.17 C901570016 Establish Link Number

Description
This counter counts the number of LAPD link establishments.
Before transmitting data on LAPD link, it is necessary to establish the transmission link
through negotiation. Refer to LAPD protocol specification for the link establishment.
Usage
This counter is used to find out the number of LAPD link establishments.
63-8

Measurement Point
LAPD link establishment negotiation is completed, and the system enters multi-frame
establishment status.
63.18 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 Point
The LAPD link is released, and the system enters the status of waiting for link
establishment.
63.19 C901570018 Protocol Error Number

Description
When protocol error occurs on LAPD link, the multi-frame link protocol reports the protocol
error to the layer management entity. This counter counts the number of protocol error
messages received by the layer management entity.
Usage
This counter is used to find out protocol errors on LAPD link.
Measurement Point
63-9

Figure 63-3 Measurement Point of Number of Protocol Errors
63.20 C901570019 Number of T200 Overtime

Description
T200 defines the time limit for the opposite end's acknowledging the information frame.
This counter counts the number of T200 timeout on LAPD link.
Usage
This counter is used to find out the number of T200 timeout on LAPD link. It studies whether
the opposite end acknowledges the information frame. If T200 is timeout, it indicates that
the opposite end does not acknowledge the information frame in time.
Measurement Point
The counter counts when the LAPD process receives the T200 timeout message.

Description
T201 defines the time limit of response for LAPD identification authentication. This counter
counts the number of T201 timeout on LAPD link.
Usage
his counter is used to find out the number of T201 timeout on LAPD link. It studies whether
the LAPD identification authentication request is acknowledged.
Measurement Point
63-10


Description
T203 defines the maximum time allowed for no frame interaction. This counter counts the
number of T203 timeout on LAPD link.
Usage
This counter is used to find out the number of T203 timeout on LAPD link. It studies whether
there is no frame interaction on LAPD link, if the counter's value is large, it indicates that
the LAPD link is idle.
Measurement Point

Description
T204 defines the time limit of sending unacknowledgement due to hop frame in the slide
window. This counter counts the number of T204 timeout on LAPD link.
Usage
This counter is used to find out the number of T204 timeout on LAPD link. It studies the
transmission delay difference between channels in the LAPD channel cluster. The larger
the counter's value is, the more unacknowledgements there are sent to the opposite end
due to hop frame in the slide window, indicating that the transmission delay difference
between different channels is large.
Measurement Point
63.24 C901570023 Number of abnormal hop frame

Description
This counter counts the number of I frames outside of the slide window received by the
slide window of LAPD link during the message receiving process.
Usage
This counter is used to observe abnormal hop frames on LAPD link. It reflects the LAPD
transmission quality, if the counter's value is large, it indicates that the link quality is poor.
63-11

Measurement Point
When an I frame outside of the slide window is received by the slide window of LAPD link
during the message receiving process, the counter increments.
63.25 C901570024 Number of normal hop frame

Description
This counter counts the number of unexpected frames in the slide window received by the
slide window of LAPD link during the message receiving process.
Usage
This counter is used to observe the case that a frame sent later is received earlier on LAPD
link due to different channel and different path.
Measurement Point
When an unexpected frames in the slide window is received by the slide window of LAPD
link during the message receiving process, the counter increments.
63.26 C901570025 Multi Channel Link Lose Frame

Description
During the message receiving process of slide window of LAPD link, if the last frame
number received on each channel exceeds the expected frame number, it indicates that
frame loss occurs at multiple channels.
This counter counts the number of frame numbers received on all channels exceeding the
expected frame number.
Usage
This counter is used to observe the frame loss condition on LAPD link. If the counter's
value is large, it indicates that there are many frames lost on the link.
Measurement Point
During the message receiving process of slide window of LAPD link, the counter counts
when the frame numbers received on all channels exceed the expected frame number.
63-12

63.27 C901570026 No useful channel

Description
When the message is tranmitted on LAPD link, if all channels of the channel cluster are
blocked, then there are no available channels to transmit the LAPD frame.
This counter counts the number of message transmission failure due to no available
channel.
Usage
This counter is used to observe the case that all channels of the channel cluster of LAPD
link are blocked. If the counter's value is large, it indicates that the transmission quality is
poor.
Measurement Point
The counter counts when message transmission on LAPD link fails due to no available
channel.
63.28 C901570027 Max Up Flow

Description
This counter counts the maximum flow of uplink messages on LAPD link. The uplink flow
on LAPD link is counted every 5 minutes, and the maximum flow is recorded.
Usage
This counter is used to find out the maximum flow of LAPD frames received from BTS on
LAPD link within the meaurement period. Such frames include all types of frames in the
LAPD protocol.
Measurement Point
The uplink flow on LAPD link is counted every 5 minutes, and the maximum flow is
recorded.
63.29 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.
63-13

Usage
This counter is used to find out the maximum flow of LAPD frames sent to BTS on LAPD
link within the meaurement period. Such frames include all types of frames in the LAPD
protocol.
Measurement Point
The downlink flow on LAPD link is counted every 5 minutes, and the maximum flow is
recorded.
63.30 C901570029 Current Up Flow

Description
This counter counts the current flow of uplink messages on LAPD link. The uplink flow on
LAPD link is counted every 5 minutes.
Usage
This counter is used to find out the current flow of LAPD frames received from BTS on
LAPD link during the performance measuremnt report process. Such frames include all
types of frames in the LAPD protocol.
Measurement Point
The current flow of uplink messages on LAPD link is recorded every 5 minutes.
63.31 C901570030 Current Down Flow

Description
This counter counts the current flow of downlink messages on LAPD link. The downlink
flow on LAPD link is counted every 5 minutes.
Usage
This counter is used to find out the current flow of LAPD frames sent to BTS on LAPD
link during the performance measuremnt report process. Such frames include all types of
frames in the LAPD protocol.
Measurement Point
The current flow of downlink messages on LAPD link is recorded every 5 minutes.
63-14

Chapter 64
LCS Measurement
Table of Contents
Overview ..................................................................................................................64-2
C901580001 Number of receiving location request in CS .........................................64-2
C901580002 Number of receiving location abort in CS.............................................64-3
C901580003 Number of TA Request in CS ..............................................................64-3
C901580004 Number of TA Response in CS............................................................64-4
C901580005 Number of MS Position Command in CS .............................................64-5
C901580006 Number of MS Position Response in CS .............................................64-5
C901580007 Number of location success in CS .......................................................64-6
C901580008 Number of location failure due to abnormal status of Lb interface in
CS............................................................................................................................64-7
C901580009 Number of location failure due to radio Timer expiration in CS.............64-8
C901580010 Number of sending BSSLAP RESET message due to Intra-BSS
handover in CS ........................................................................................................64-9
C901580011 Number of location failure due to Intra-BSS handover expiration in
CS............................................................................................................................64-9
C901580012 Number of location failure due to location Timer expiration in CS ......64-10
C901580013 Number of location failure due to Inter-BSS handover in CS.............. 64-11
C901580014 Number of location failure due to call drop in CS ...............................64-12
C901580015 Number of location failure due to other BSC's cause in CS................64-13
C901580016 Number of receiving location request in PS .......................................64-13
C901580017 Number of receiving location abort in PS...........................................64-14
C901580018 Number of TA Request in PS.............................................................64-15
C901580019 Number of TA Response in PS ..........................................................64-15
C901580020 Number of MS Position Command in PS ...........................................64-16
C901580021 Number of MS Position Response in PS ...........................................64-17
C901580022 Number of location success in PS .....................................................64-17
C901580023 Number of location failure due to abnormal status of Lb interface in
PS..........................................................................................................................64-18
C901580024 Number of location failure due to radio Timer expiration in PS ...........64-19
C901580025 Number of location failure due to Inter-CMP cell reselection in PS.....64-20
C901580026 Number of sending LOCATION INFORMATION message to SMLC
due to Intra-CMP cell reselection in PS ..................................................................64-21
C901580027 Number of location failure due to location Timer expiration in PS.......64-22
C901580028 Number of location failure due to other BSC's cause in PS................64-22
64-1

64.1 Overview
LCS measurement involves counters used for evaluating performance and status of
location services, such as the number of location requests in CS domain and the number
of location requests in PS domain.
64.2 C901580001 Number of receiving location request

in CS
Description
This counter counts the number of location requests received by CS domain from the core
network.
Measurement Point
The counter counts when CS domain receives the location request from the core network.
Figure 64-1 Measurement Point of Number of receiving location request in CS
Unit
Times
Related Features
l ZGO-01-03-002 LCS with CGI+TA
l ZGO-01-03-003 LCS with AGPS
64-2

Chapter 64 LCS Measurement
64.3 C901580002 Number of receiving location abort

in CS
Description
This counter counts the number of location terminations received by CS domain from the
core network.
Measurement Point
The counter counts when CS domain receives the location termination from the core
network. The measurement point is A, as shown in Figure 64-2.
Figure 64-2 Measurement Point of Number of Location Terminations Received in CS

Domain
Unit
Times
Related Features
64.4 C901580003 Number of TA Request in CS

Description
When SMLC receives the location request from iBSC, if the location request does not
contain TA value, SMLC will send the TA request to iBSC. After iBSC receives the
message, the number of TA requests is counted.
Measurement Point
The counter counts the number of TA requests when iBSC receives the location request
from SMLC. The measurement point is A, as shown in Figure 64-3.
64-3

Figure 64-3 Measurement Point of Number of TA Request in CS
Unit
Times
Related Features
ZGO-01-03-002 LCS with CGI+TA
64.5 C901580004 Number of 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 Point
The counter counts when iBSC sends TA response to SMLC after receiving TA request
correctly from SMLC. The measurement point is A, as shown in Figure 64-4.
Figure 64-4 Measurement Point of Number of TA Responses in CS Domain
Unit
Times
64-4

Related Features
64.6 C901580005 Number of MS Position Command

in CS
Description
iBSC receives the MS position command from SMLC, then the counter counts the number
of MS location requests in CS domain.
Measurement Point
The counter counts when the MS position command in CS domain is received. The
Figure 64-5 Measurement Point of Number of MS Position Commands in CS Domain
Unit
Times
Related Features
ZGO-01-03-003 LCS with AGPS
64.7 C901580006 Number of MS 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.
64-5

Measurement Point
The counter counts when iBSC receives the position response from MS. The measurement
Figure 64-6 Measurement Point of Number of MS Position Response in CS Domain
Unit
Times
Related Features
64.8 C901580007 Number of location success in CS

Description
This counter counts the number of location successes in CS domain.
Measurement Point
The counter counts when iBSC receives the position result from SMLC. The measurement
64-6

Figure 64-7 Measurement Point of Number of Location Successes in CS Domain
Unit
Times
Related Features
64.9 C901580008 Number of location failure due to

abnormal status of Lb interface in CS
Description
When the location request from the core network is received, if the Lb interface link from
iBSC to SMLC is broken, the location will fail. In this case, the counter counts the number
of location failures.
Measurement Point
When the location request from the core network is received, if the Lb interface link is
broken, the counter counts the number of location failures in CS domain due to abnormal
Lb interface status. The measurement point is A, as shown in Figure 64-8.
Figure 64-8 Measurement Point of Number of location failure due to abnormal status of
Lb interface in CS
64-7

Unit
Times
Related Features

radio Timer expiration in CS
Description
After iBSC sends the location command to MS, the radio timer starts. If no response is
received from MS before the timer is timeout, the counter counts the number of location
failures in CS domain due to radio timer timeout.
Measurement Point
After iBSC sends the location command to MS, the radio timer starts. When the timer is
timeout, the counter counts the number of location failures in CS domain due to radio timer
timeout. The measurement point is A, as shown in Figure 64-9.
Figure 64-9 Measurement Point of Number of location failure due to radio Timer
expiration in CS
Unit
Times
Related Features
64-8

64.11 C901580010 Number of 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 Point
During the MS position process, intra-BSC handover occurs, the counter counts the
number of location delays when the handover completion message is received from MS.
Figure 64-10 Measurement Point of Number of Location Delays in CS Domain due

to Intra-BSC Handover
Unit
Times
Related Features

Intra-BSS handover expiration in CS
Description
When iBSC receives the MS position command from SMLC, if iBSC is initiating intra-BSC
inter-cell handover at the moment, the timer starts. This counter counts the number of
location failures due to timer timout.
Measurement Point
The counter counts when the intra-BSC handover timer is timeout in CS domain. The
64-9

Figure 64-11 Measurement Point of Number of Location Failures due to Intra-BSS

Handover Timer Timeout in CS Domain
Unit
Times
Related Features

location Timer expiration in CS
Description
When the location request from the core network is received, the location monitoring timer
starts. If the timer is timeout, this counter counts the number of location failures due to the
timer timout.
Measurement Point
The counter counts when the location monitoring timer is timeout. The measurement point
64-10

Figure 64-12 Measurement Point of Number of Location Failure due to Location

Monitoring Timer Timeout in CS Domain
Unit
Times
Related Features

Inter-BSS handover in CS
Description
When the MS position command is received from SMLC, if the external handover flow is
initiated, the location will fail.
Measurement Point
When the MS position command is received, if the external handover flow is initiated, the
counter counts. The measurement point is A, as shown in Figure 64-13.
Figure 64-13 Measurement Point of Number of Location Failure due to Inter-BSS

handover in CS Domain
64-11

Unit
Times
Related Features

call drop in CS
Description
During the location process, iBSC receives the clear command from the core network.
Measurement Point
During the location process, the counter counts when iBSC receives the clear command
from the core network. The measurement point is A, as shown in Figure 64-14.
Figure 64-14 Measurement Point of Number of Location Failure due to Call Drop
in CS Domain
Unit
Times
Related Features
64-12


other BSC's cause in CS
Description
Location fails due to other causes inside iBSC, such as message sending failure between
modules, requesting SCCP connection failure, and timer setting failure.
Measurement Point
The counter counts when the following problems occur: message sending failure between
Unit
Times
Related Features
64.17 C901580016 Number of receiving location

request in PS
Description
This counter counts the number of location requests received by PS domain from the core
network.
Measurement Point
The counter counts when PS domain receives the location request from the core network.
Figure 64-15 Measurement Point of Number of Location Requests in PS Domain
64-13

Unit
Times
Related Features
64.18 C901580017 Number of receiving location abort

in PS
Description
This counter counts the number of location terminations received by PS domain from the
core network.
Measurement Point
The counter counts when PS domain receives the location termination from the core
network. The measurement point is A, as shown in Figure 64-16.
Figure 64-16 Measurement Point of Number of Location Terminations Received in

PS Domain
Unit
Times
Related Features
64-14

64.19 C901580018 Number of TA Request in PS

Description
When SMLC receives the location request from iBSC, if the location request does not
contain TA value, SMLC will send the TA request to iBSC. After iBSC receives the
message, the number of TA requests is counted.
Measurement Point
The counter counts the number of TA requests when iBSC receives the location request
from SMLC. The measurement point is A, as shown in Figure 64-17.
Figure 64-17 Measurement Point of Number of TA Requests in PS Domain
Unit
Times
Related Features
64.20 C901580019 Number of TA Response in PS

Description
After iBSC receives the TA request correctly from SMLC, iBSC sends the TA response
message to SMLC. In this case, the counter counts the number of TA responses.
Measurement Point
The counter counts when iBSC sends TA response to SMLC after receiving TA request
correctly from SMLC. The measurement point is A, as shown in Figure 64-18.
64-15

Figure 64-18 Measurement Point of Number of TA Responses in PS Domain
Unit
Times
Related Features
64.21 C901580020 Number of MS Position Command

in PS
Description
iBSC receives the MS position command from SMLC, then the counter counts the number
of MS location requests in PS domain.
Measurement Point
The counter counts when BSC receives the MS position command in PS domain. The
Figure 64-19 Measurement Point of Number of MS Position Commands in PS Domain
64-16

Unit
Times
Related Features
64.22 C901580021 Number of MS Position Response

in PS
Description
iBSC sends the position request to the core network. After the position response from the
core network is received, the counter counts the number of MS position responses.
Measurement Point
The counter counts when iBSC receives the position response from the core network. The
Figure 64-20 Measurement Point of Number of MS Position Response in PS Domain
Unit
Times
Related Features
64.23 C901580022 Number of location success in PS

Description
This counter counts the number of location successes in PS domain.
64-17

Measurement Point
The counter counts when iBSC receives the position result from SMLC. The measurement
Figure 64-21 Measurement Point of Number of Location Successes in PS Domain
Unit
Times
Related Features

abnormal status of Lb interface in PS
Description
When the location request from the core network is received, if the Lb interface link from
iBSC to SMLC is broken, the location will fail. In this case, the counter counts the number
of location failures.
Measurement Point
When the location request from the core network is received, if the Lb interface link is
broken, the counter counts the number of location failures in PS domain due to abnormal
Lb interface status. The measurement point is A, as shown in Figure 64-22.
64-18

Figure 64-22 Measurement Point of Number of location failure due to abnormal status
of Lb interface in PS
Unit
Times
Related Features

radio Timer expiration in PS
Description
After iBSC sends the location command to the core network, the radio timer starts. If no
response is received from MS before the timer is timeout, the counter counts the number
of location failures in PS domain due to radio timer timeout.
Measurement Point
After iBSC sends the location command to the core network, the radio timer starts. When
the timer is timeout, the counter counts the number of location failures in PS domain due
to radio timer timeout. The measurement point is A, as shown in Figure 64-23.
64-19

Figure 64-23 Number of Location Failures in PS domain due to Radio Timer Timeout
Unit
Times
Related Features

Inter-CMP cell reselection in PS
Description
During the positioning process in PS domain, if inter-module cell reselection occurs, the
FLUSH LL message is received from the core network, then the location fails.
Measurement Point
During the positioning process in PS domain, if inter-module cell reselection occurs, the
counter counts when the FLUSH LL message is received from the core network. The
Figure 64-24 Measurement Point of Number of Location Failure due to Inter-Module

Cell Reselection in PS Domain
64-20

Unit
Times
Related Features
64.27 C901580026 Number of sending LOCATION

INFORMATION message to SMLC due to Intra-CMP
cell reselection in PS
Description
During the positioning process in PS domain, if intra-module cell reselection occurs, then
the counter counts when the FLUSH LL message is received from the core network.
Measurement Point
During the positioning process in PS domain, if intra-module cell reselection occurs, the
counter counts when the FLUSH LL message is received from the core network. The
Figure 64-25 Measurement Point of Number of Sending Location Information Messages

to LCS due to Intra-Module Cell Reselection in PS Domain
Unit
Times
Related Features
64-21


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 Point
The counter counts when the location monitoring timer is timeout. The measurement point
Figure 64-26 Measurement Point of Number of Location Failure due to Location

Monitoring Timer Timeout in PS Domain
Unit
Times
Related Features

other BSC's cause in PS
Description
Location fails due to other causes inside iBSC, such as message sending failure between
64-22

Measurement Point
The counter counts when the following problems occur: message sending failure between
Unit
Times
Related Features
64-23

64-24

Chapter 65
LB Global Msg Measurement
Table of Contents
Overview ..................................................................................................................65-1
C901590001 Number of receiving RESET message from SMLC..............................65-1
C901590002 Number of sending RESET ACK message to SMLC ...........................65-2
C901590003 Number of sending RESET message to SMLC....................................65-3
C901590004 Number of receiving RESET ACK message from SMLC......................65-4
65.1 Overview
LB interface global message measurement involve counters used for evaluating the global
performance and status of LB interface.
65.2 C901590001 Number of receiving RESET message

from SMLC
Description
The RESET message is received at BSC from SMLC.
Measurement Point
The counter counts when the RESET message is received at BSC from SMLC. The
65-1

Figure 65-1 Measurement Point of Number of RESET Messages Received from SMLC
Unit
Times
65.3 C901590002 Number of sending RESET ACK

message to SMLC
Description
BSC receives the RESET message from SMLC. This counter counts the number of the
RESET ACK messages sent to SMLC from BSC.
Measurement Point
The counter counts when the RESET ACK message is sent to SMLC from BSC. The
65-2

Chapter 65 LB Global Msg Measurement
Figure 65-2 Measurement Point of Number of RESET ACK Messages Sent to SMLC
Unit
Times
65.4 C901590003 Number of sending RESET message

to SMLC
Description
This counter counts the number of RESET messages sent to SMLC from BSC.
Measurement Point
The counter counts when the RESET message is sent to SMLC from BSC. The
65-3

Figure 65-3 Measurement Point of Number of RESET Messages Sent to SMLC
Unit
Times
65.5 C901590004 Number of receiving RESET ACK

message from SMLC
Description
This counter counts the number of RESET ACK messages received at BSC from SMLC.
Measurement Point
The counter counts when the RESET ACK message is received at BSC from SMLC. The
65-4

Chapter 65 LB Global Msg Measurement
Figure 65-4 Measurement Point of Number of RESET ACK Messages Received from
SMLC
Unit
Times
65-5

65-6

Chapter 66
Ater Interface Relays
Measurement
Table of Contents
Overview ..................................................................................................................66-1
C901600001 Number of configured 16 K relay circuits of Ater interface....................66-1
C901600002 Average of unavailable 16K relay circuits of Ater interface...................66-2
C901600003 Average of available 16 K relay circuits of Ater interface......................66-3
C901600004 Maximum of busy 16 K relay circuits of Ater interface..........................66-4
C901600005 Maximum of busy 8 K relay circuits of Ater interface............................66-5
C901600006 Total busy time of 16 K relay circuits of Ater interface ..........................66-7
C901600007 Total busy time of 8 K relay circuits of Ater interface ............................66-8
66.1 Overview
Ater interface relay measurement (office) involves measurement of the following
information: the number of 16 K relay circuits configured at Ater interface, the average
number of unavailable 16 K relay circuits (blocked) configured at Ater interface, the
average number of available 16 K relay circuits (unblocked) configured at Ater interface,
the maximum number of busy 16 K relay circuits at Ater interface, the maximum number
of busy 8 K relay circuits at Ater interface, the total busy time of 16 K relay circuits at Ater
interface, and the total busy time of 8 K relay circuits at Ater interface.
66.2 C901600001 Number of 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.
66-1

Measurement Point
iBSC queries the database periodically, and saves the value obtained from the database
in this counter. The measurement point is A, as shown in Figure 66-1.
Figure 66-1 Measurement Point of Number of configured 16 K relay circuits of Ater

interface
Unit
16 K
66.3 C901600002 Average of unavailable 16K relay

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.
Measurement Point
66-2

Chapter 66 Ater Interface Relays Measurement
Figure 66-2 Measurement Point of Average of unavailable 16K relay circuits of Ater
interface
Unit
16 K
66.4 C901600003 Average of available 16 K relay

Description
This counter counts the average number of available 16 K relay circuits at Ater interface.
Usage
This counter is used to find out the average number of available 16 K relay circuits at Ater
interface.
Measurement Point
66-3

Figure 66-3 Measurement Point of Average of available 16 K relay circuits of Ater

interface
Unit
16 K
66.5 C901600004 Maximum of busy 16 K relay circuits

of Ater interface
Description
This counter counts the maximum number of busy 16 K relay circuits at Ater interface.
Usage
This counter is used to find out the maximum number of busy 16 K relay circuits at Ater
interface.
Measurement Point
iBSC queries the database periodically and saves the value obtained from the database
in this counter, or the counter counts when Ater interface terrestrial circuit is released. The
measurement point is A in Figure 66-4 and B in Figure 66-5. (Note: Figure 66-5 only gives
one case of Ater interface terrestrial circuit being released.)
66-4

Figure 66-4 Measurement Point of Maximum of busy 16 K relay circuits of Ater interface
- (1)
Figure 66-5 Measurement Point of Maximum of busy 16 K relay circuits of Ater interface
- (2)
Unit
Times
66.6 C901600005 Maximum of busy 8 K relay circuits

of Ater interface
Description
This counter counts the maximum number of busy 8 K relay circuits at Ater interface.
Usage
This counter is used to find out the maximum number of busy 8 K relay circuits at Ater
interface.
66-5

Measurement Point
Figure 66-6 Measurement Point of Maximum of busy 8K relay circuits of Ater interface
- (1)
Figure 66-7 Measurement Point of Maximum of busy 8K relay circuits of Ater interface
- (2)
Unit
Times
66-6

66.7 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 circuits at Ater interface.
Measurement Point
Figure 66-8 Measurement Point of Total busy time of 16 K relay circuits of Ater interface
- (1)
66-7

Figure 66-9 Measurement Point of Total busy time of 16 K relay circuits of Ater interface
- (2)
Unit
Second
66.8 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 circuits at Ater interface.
Measurement Point
measurement point is A in Figure 66-10 and B in Figure 66-11. (Note: Figure 66-11 only
gives one case of Ater interface terrestrial circuit being released.)
66-8

Figure 66-10 Measurement Point of Total busy time of 8K relay circuits of Ater interface
- (1)
Figure 66-11 Measurement Point of Total busy time of 8K relay circuits of Ater interface
- (2)
Unit
Second
66-9

66-10

Chapter 67
Ater Interface SCCP
Connections Measurement
Table of Contents
Overview ..................................................................................................................67-1
C901610001 Number of SCCP establishment requests (BSC to TC) .......................67-1
C901610002 Number of SCCP establishments success (BSC to TC) ......................67-2
C901610003 Number of SCCP establishment failure due to timeout (BSC to TC) ....67-3
C901610004 Number of SCCP establishment refused (BSC to TC) .........................67-4
67.1 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.
67.2 C901610001 Number of SCCP establishment

requests (BSC to TC)
Description
This counter counts the number of link establishment requests initiated by BSC towards
TC.
Usage
This counter is used to find out the number of link establishment requests initiated by BSC
towards TC.
Measurement Point
Rancs sends the TC resource request to Ater interface. The counter increments when
Ater interface sends the SCCP link establishment request to iTC. The measurement point
67-1

Figure 67-1 Measurement Point of Number of SCCP establishment requests (BSC to TC)
Unit
Times
67.3 C901610002 Number of 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 establishments initiated
by BSC towards TC. The BSC-to-TC link establishment success rate can be calculated
according to this counter's value and the number of link establishment requests.
Measurement Point
When the Ater process receives the Connect Conf message from iTC, the counter
67-2

Chapter 67 Ater Interface SCCP Connections Measurement
Figure 67-2 Measurement Point of Number of SCCP Connection Successes
Unit
Times

failure due to timeout (BSC to TC)
Description
This counter counts the number of failed link establishments, which is due to timer timeout,
initiated by BSC towards TC.
Measurement Point
When the Ater process expires at the timer TAterWaitConn, the counter increments. The
67-3

Figure 67-3 Measurement Point of Number of SCCP Connection Failure due to Timeout
Unit
Times

refused (BSC to TC)
Description
This counter counts the number of rejected link establishment requests initiated by BSC
towards TC.
Measurement Point
When the Ater process receives the Disconnect Ind message from the AterDispatch
process, the counter increments. The measurement point is A, as shown in Figure 67-4.
67-4

Chapter 67 Ater Interface SCCP Connections Measurement
Figure 67-4 Measurement Point of Number of SCCP Connection Request Being

Rejected
Unit
Times
67-5

67-6

Chapter 68
Measurement Report Serving
Cell Measurement
Table of Contents
MR Serving Cell Measurement .................................................................................68-5
C901620001 Number of samples of UL RQ=0 and receive level between 0 and 10..68-5
C901620002 Number of samples of UL RQ=0 and receive level between 11 and 15 .68-6
C901620008 Number of samples of UL RQ=1 and receive level between 11 and
15........................................................................................................................... 68-11
20........................................................................................................................... 68-11
30...........................................................................................................................68-12
40...........................................................................................................................68-13
63...........................................................................................................................68-14
15...........................................................................................................................68-15
20...........................................................................................................................68-16
30...........................................................................................................................68-17
40...........................................................................................................................68-18
63...........................................................................................................................68-19
15...........................................................................................................................68-20
20...........................................................................................................................68-21
68-1


30...........................................................................................................................68-22
40...........................................................................................................................68-23
63...........................................................................................................................68-23
15...........................................................................................................................68-25
20...........................................................................................................................68-26
30...........................................................................................................................68-27
40...........................................................................................................................68-27
63...........................................................................................................................68-28
15...........................................................................................................................68-30
20...........................................................................................................................68-31
30...........................................................................................................................68-31
40...........................................................................................................................68-32
63...........................................................................................................................68-33
15...........................................................................................................................68-35
20...........................................................................................................................68-35
30...........................................................................................................................68-36
40...........................................................................................................................68-37
63...........................................................................................................................68-38
15...........................................................................................................................68-39
20...........................................................................................................................68-40
68-2

Chapter 68 Measurement Report Serving Cell Measurement

30...........................................................................................................................68-41
40...........................................................................................................................68-42
63...........................................................................................................................68-43
C901620049 Number of samples of DL RQ=0 and receive level between 0 and 10 .68-43
C901620050 Number of samples of DL RQ=0 and receive level between 11 and
15...........................................................................................................................68-44
20...........................................................................................................................68-45
30...........................................................................................................................68-46
40...........................................................................................................................68-47
63...........................................................................................................................68-47
15...........................................................................................................................68-49
20...........................................................................................................................68-50
30...........................................................................................................................68-51
40...........................................................................................................................68-51
63...........................................................................................................................68-52
15...........................................................................................................................68-54
20...........................................................................................................................68-55
30...........................................................................................................................68-55
40...........................................................................................................................68-56
63...........................................................................................................................68-57
15...........................................................................................................................68-59
20...........................................................................................................................68-59
68-3


30...........................................................................................................................68-60
40...........................................................................................................................68-61
63...........................................................................................................................68-62
15...........................................................................................................................68-63
20...........................................................................................................................68-64
30...........................................................................................................................68-65
40...........................................................................................................................68-66
63...........................................................................................................................68-67
15...........................................................................................................................68-68
20...........................................................................................................................68-69
30...........................................................................................................................68-70
40...........................................................................................................................68-71
63...........................................................................................................................68-71
15...........................................................................................................................68-73
20...........................................................................................................................68-74
30...........................................................................................................................68-75
40...........................................................................................................................68-75
63...........................................................................................................................68-76
15...........................................................................................................................68-78
20...........................................................................................................................68-79
68-4


30...........................................................................................................................68-79
40...........................................................................................................................68-80
63...........................................................................................................................68-81
68.1 MR Serving Cell Measurement

Values of MR serving cell measurement counters involve uplink/downlink quality and
receiving level in the measurement report. The measurement point of all counters in this
measurement task is A, as shown in Figure 68-1.
Figure 68-1 Measurement Point of BTS Sending Meaurement Report to BSC
Statistic unit in this measurement is TRX.
68.2 C901620001 Number of samples of UL RQ=0 and

receive level between 0 and 10
Description
This counter counts the number of samples of UL RQ=0 and receive level between 0 and
10 in UL radio measurement report (preprocessing report or enhanced preprocessing
measurement report). This counter increments when BSC receives the UL radio
measurement report (preprocessing report or enhanced preprocessing measurement
report) in which UL RQ=0 and receive level is between 0 and 10.
Usage
This counter is used to find out radio channel's UL quality and receive level.
Measurement Point
This counter counts when BSC receives the UL radio measurement report (preprocessing
report or enhanced preprocessing measurement report) in which UL RQ=0 and receive
level is between 0 and 10. The measurement point is A, as shown in Figure 68-2.
68-5

Unit
Times

Description
This counter counts the number of samples of UL RQ=0 and receive level between 11
and 15 in UL radio measurement report (preprocessing report or enhanced preprocessing
Usage
Measurement Point
68-6

Unit
Times

Description
Usage
Measurement Point
Unit
Times
68-7


Description
Usage
Measurement Point
Unit
Times

Description
68-8

Usage
Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-9

Unit
Times

Description
Usage
Measurement Point
68-10

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-11

Usage
Measurement Point
Unit
Times

Description
Usage
68-12

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-13

Unit
Times

Description
Usage
Measurement Point
68-14

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-15

Usage
Measurement Point
Unit
Times

Description
Usage
68-16

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-17

Unit
Times

Description
Usage
Measurement Point
68-18

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-19

Usage
Measurement Point
Unit
Times

Description
Usage
68-20

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-21

Unit
Times

Description
Usage
Measurement Point
68-22

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-23

Usage
Measurement Point
Unit
Times

Description
Usage
68-24

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-25

Unit
Times

Description
Usage
Measurement Point
68-26

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-27

Usage
Measurement Point
Unit
Times

Description
Usage
68-28

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-29

Unit
Times

Description
Usage
Measurement Point
68-30

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-31

Usage
Measurement Point
Unit
Times

Description
Usage
68-32

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-33

Unit
Times

Description
Usage
Measurement Point
68-34

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-35

Usage
Measurement Point
Unit
Times

Description
Usage
68-36

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-37

Unit
Times

Description
Usage
Measurement Point
68-38

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-39

Usage
Measurement Point
Unit
Times

Description
Usage
68-40

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-41

Unit
Times

Description
Usage
Measurement Point
68-42

Unit
Times

Description
Usage
Measurement Point
Unit
Times
68.50 C901620049 Number of samples of DL RQ=0 and

Description
This counter counts the number of samples of DL RQ=0 and receive level between 0 and
10 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-43

measurement report). This counter increments when BSC receives the DL radio
report) in which DL RQ=0 and receive level is between 0 and 10.
Usage
This counter is used to find out radio channel's DL quality and receive level.
Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing
report or enhanced preprocessing measurement report) in which DL RQ=0 and receive
Unit
Times

Description
This counter counts the number of samples of DL RQ=0 and receive level between 11
and 15 in DL radio measurement report (preprocessing report or enhanced preprocessing
Usage
68-44

Measurement Point
level between 11 and 15. The measurement point is A, as shown in Figure 68-51.
Unit
Times

Description
Usage
Measurement Point
68-45

Unit
Times

Description
Usage
Measurement Point
68-46

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-47

Usage
Measurement Point
Unit
Times

Description
Usage
68-48

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-49

Unit
Times

Description
Usage
Measurement Point
68-50

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-51

Usage
Measurement Point
Unit
Times

Description
Usage
68-52

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-53

Unit
Times

Description
Usage
Measurement Point
68-54

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-55

Usage
Measurement Point
Unit
Times

Description
Usage
68-56

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-57

Unit
Times

Description
Usage
Measurement Point
68-58

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-59

Usage
Measurement Point
Unit
Times

Description
Usage
68-60

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-61

Unit
Times

Description
Usage
Measurement Point
68-62

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-63

Usage
Measurement Point
Unit
Times

Description
Usage
68-64

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-65

Unit
Times

Description
Usage
Measurement Point
68-66

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-67

Usage
Measurement Point
Unit
Times

Description
Usage
68-68

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-69

Unit
Times

Description
Usage
Measurement Point
68-70

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-71

Usage
Measurement Point
Unit
Times

Description
Usage
68-72

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-73

Unit
Times

Description
Usage
Measurement Point
68-74

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-75

Usage
Measurement Point
Unit
Times

Description
Usage
68-76

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-77

Unit
Times

Description
Usage
Measurement Point
68-78

Unit
Times

Description
Usage
Measurement Point
Unit
Times

Description
68-79

Usage
Measurement Point
Unit
Times

Description
Usage
68-80

Measurement Point
Unit
Times

Description
Usage
Measurement Point
68-81

Unit
Times
68-82

Chapter 69
Measurement Report
Adjacent Cell Measurement
Table of Contents
MR Adjacent Cell Measurement ...............................................................................69-1
C901630001 Number of samples with C/I < -10db....................................................69-2
C901630002 Number of samples with C/I between -9db and -5db............................69-2
C901630003 Number of samples with C/I between -4db and 0db.............................69-3
C901630004 Number of samples with C/I between 1db and 5db ..............................69-4
C901630005 Number of samples with C/I between 6db and 10db ............................69-5
C901630006 Number of samples with C/I between 11db and 15db ..........................69-5
C901630007 Number of samples with C/I between 16db and 20db ..........................69-6
C901630008 Number of samples with C/I > 20db.....................................................69-7
69.1 MR Adjacent Cell Measurement

Measurement values of this measurement task involve the downlink level. If the
measurement report contains adjacent cell information, then subtract the adjacent cell's
level from the local cell's downlink level, and perform measurement according to the
value. The measurement point of all counters in this measurement task is A, as shown
in Figure 69-1.
69-1

69.2 C901630001 Number of 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 preprocessing measurement report).
Usage
This counter is used to find out DL level of adjacent cell.
Measurement Point
This counter increments while DL level in this cell in DL radio measurement report
(preprocessing report or enhanced preprocessing measurement report) received by BSC
subtracting the level of adjacent cell is lower than 10dB, as shown in Figure 69-2.
Figure 69-2 Measurement Point of BTS Sending Measurement Report to BSC
Unit
Times
69.3 C901630002 Number of samples with C/I between

-9db and -5db
Description
in adjacent cell within -9dB~-5dB in received DL radio measurement report (preprocessing
report or enhanced preprocessing measurement report).
Usage
69-2

Chapter 69 Measurement Report Adjacent Cell Measurement
Measurement Point
subtracting the level of adjacent cell is within -9dB~-5dB, as shown in Figure 69-3.
Unit
Times

-4db and 0db
Description
in adjacent cell within -4dB~0dB in received DL radio measurement report (preprocessing
Usage
Measurement Point
subtracting the level of adjacent cell is within -4dB~0dB, as shown in Figure 69-4.
69-3

Unit
Times

1db and 5db
Description
in adjacent cell within 1dB~5dB in received DL radio measurement report (preprocessing
Usage
Measurement Point
subtracting the level of adjacent cell is within 1dB~5dB, as shown in Figure 69-5.
Unit
Times
69-4


6db and 10db
Description
in adjacent cell within 6dB~10dB in received DL radio measurement report (preprocessing
Usage
Measurement Point
Unit
Times

11db and 15db
Description
This counter counts the number of samples with DL level in local cell subtracting the level in
adjacent cell within 11dB~15dB in received DL radio measurement report (preprocessing
Usage
69-5

Measurement Point
Unit
Times

16db and 20db
Description
This counter counts the number of samples with DL level in local cell subtracting the level in
adjacent cell within 16dB~20dB in received DL radio measurement report (preprocessing
Usage
Measurement Point
69-6

Unit
Times
69.9 C901630008 Number of samples with C/I > 20db

Description
in adjacent cell > 20dB in received DL radio measurement report (preprocessing report or
enhanced preprocessing measurement report).
Usage
Measurement Point
subtracting the level of adjacent cell is higher than 20dB, as shown in Figure 69-9.
Unit
Times
69-7

69-8

Chapter 70
TRX Paging Measurement
Table of Contents
Overview ..................................................................................................................70-1
C901640001 Number of PS paging message discarded due to full of the queue ......70-2
C901640002 Number of CS paging message discarded due to full of the queue ......70-2
C901640003 Average length of PCH queue: 9*9......................................................70-3
C901640004 Average length of PCH queue: 9*64....................................................70-3
70.1 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 70-1 shows the paging performance measurement flow.
Figure 70-1 Paging Performance Measurement Reporting
70-1

70.2 C901640001 Number of PS paging message

discarded due to full of the queue
Description
This counter counts the number of PS paging messages discarded due to the queue being
full.
Usage
This counter is used to find out the number of failures in receiving PS paging messages
at BTS.
Measurement Point
The counter's value is obtained by querying database when the paging performance
measurement data is reported periodically.
Unit
Times
70.3 C901640002 Number of CS 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.
Measurement Point
Unit
Times
70-2

Chapter 70 TRX Paging Measurement
70.4 C901640003 Average length of PCH queue: 9*9

Description
This counter counts the occupancy of PCH message buffer queue which saves paging
messages according to 2~9 51-multiframe mode at BTS.
Usage
This counter is used to find out the occupancy of PCH message buffer queue which saves
paging messages according to 2~9 51-multiframe mode at BTS.
Measurement Point
Unit
Times
70.5 C901640004 Average length of PCH queue: 9*64

Description
This counter counts the occupancy of PCH message buffer queue which saves paging
messages according to 64 51-multiframe mode at BTS.
Usage
This counter is used to find out the occupancy of PCH message buffer queue which saves
paging messages according to 64 51-multiframe mode at BTS.
Measurement Point
Unit
Times
70-3

70-4

Chapter 71
TRX Temperature Power
Measurement
Table of Contents
Overview ..................................................................................................................71-1
C901650001 Maximum value of TRX power (db) .....................................................71-1
C901650002 Minimum value of TRX power (db) ......................................................71-1
C901650003 Mean value of TRX power (db)............................................................71-2
C901650004 Maximum of TRX temperature (Celsius)..............................................71-2
C901650005 Minimum of TRX temperature (Celsius)...............................................71-3
C901650006 Mean of TRX temperature (Celsius) ....................................................71-3
71.1 Overview
The temperature and power of TRX are measured on TRU and reported to BSC
periodically.
71.2 C901650001 Maximum value of TRX power (db)

Description
This counter counts the maximum value of TRX's power within the measurement period.
SDR base station does not support the measurement.
Measurement Point
TRU is measured and reported periodically.
Unit
dbm
71.3 C901650002 Minimum value of TRX power (db)

Description
This counter counts the minimum value of TRX's power within the measurement period.
71-1

Measurement Point
Unit
dbm
71.4 C901650003 Mean value of TRX power (db)

Description
This counter counts the average value of TRX's power within the measurement period.
Measurement Point
Unit
dbm
71.5 C901650004 Maximum of TRX temperature

(Celsius)
Description
This counter counts the maximum value of TRX's temperature within the measurement
period.
Measurement Point
Unit
Celsius
71-2

Chapter 71 TRX Temperature Power Measurement
71.6 C901650005 Minimum of TRX temperature

(Celsius)
Description
This counter counts the minimum value of TRX's temperature within the measurement
period.
Measurement Point
Unit
Celsius
71.7 C901650006 Mean of TRX temperature (Celsius)

Description
This counter counts the average value of TRX's temperature within the measurement
period.
Measurement Point
Unit
Celsius
71-3

71-4

Chapter 72
Terminal Ability Statistic
Table of Contents
Terminal Ability Statistics ..........................................................................................72-2
C901660001 Number of mobile support single TS DTM ability .................................72-3
C901660002 Number of mobile support DTM GPRS multi TS ability 5 .....................72-3
C901660003 Number of mobile support DTM GPRS multi TS ability 9 .....................72-4
C901660004 Number of mobile support DTM GPRS multi TS ability 11 ...................72-5
C901660005 Number of mobile support DTM EGPRS multi TS ability 5...................72-6
C901660006 Number of mobile support DTM EGPRS multi TS ability 9...................72-7
C901660007 Number of mobile support DTM EGPRS multi TS ability 11 .................72-8
C901660008 Number of mobile support extend DTM GPRS multi TS ability 5..........72-9
C901660009 Number of mobile support extend DTM GPRS multi TS ability 6........72-10
C901660010 Number of mobile support extend DTM GPRS multi TS ability 9........ 72-11
C901660011 Number of mobile support extend DTM GPRS multi TS ability 10 ......72-12
C901660012 Number of mobile support extend DTM GPRS multi TS ability 11 ......72-13
C901660013 Number of mobile support extend DTM EGPRS multi TS ability 5 .....72-14
C901660016 Number of mobile support extend DTM EGPRS multi TS ability 10 ...72-17
C901660017 Number of mobile support extend DTM EGPRS multi TS ability 11....72-18
C901660018 Number of mobile of GPRS multi TS ability 1 ....................................72-19
C901660027 Number of mobile of GPRS multi TS ability 10 ..................................72-33
C901660028 Number of mobile of GPRS multi TS ability 11...................................72-34
C901660035 Number of mobile of EGPRS multi TS ability 1 ..................................72-45
72-1


C901660044 Number of mobile of EGPRS multi TS ability 10 ................................72-58
C901660052 Number of mobile support FR............................................................72-70
C901660053 Number of mobile support HR ...........................................................72-71
C901660054 Number of mobile support EFR .........................................................72-72
C901660055 Number of mobile support AMRFR....................................................72-72
C901660056 Number of mobile support AMRHR ...................................................72-73
C901660057 Number of mobile support wideband AMROFR .................................72-74
C901660058 Number of mobile support wideband AMRFR ....................................72-75
C901660059 Number of mobile support wideband AMROHR.................................72-76
C901660060 Number of mobile support AMROHR.................................................72-77
C901660061 Number of mobile support extend uplink TBF ....................................72-78
C901660062 Number of mobile support NACC ......................................................72-79
C901660063 Number of mobile support GPRS extend dynamic allocation .............72-80
C901660064 Number of mobile support EGPRS extend dynamic allocation...........72-82
C901660065 Number of sampling received Classmark3.........................................72-83
C901660066 Number of sampling received radio access ability .............................72-84
C901660069 Num of MS supporting PS handover .................................................72-85
C901660070 The Number of MS which Support SAIC............................................72-86
C901660071 The Number of MS which not Support SAIC......................................72-87
72.1 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.
72-2

Chapter 72 Terminal Ability Statistic
72.2 C901660001 Number of mobile support single TS

DTM ability
Description
This counter counts the number of mobiles that support the capability of single TS DTM.
Usage
This counter measures the number of mobiles that support the single TS DTM ability.
Measurement Point
This counter increments while Rancs receives the Classmark Update message delivered
by MSC or the Classmark Change message sent by MS and the message indicates the
MS supports the single TS DTM ability. The measurement point is A1 or A2, as shown in
Figure 72-1.
Figure 72-1 Measurement Point of Number of mobile support single TS DTM ability
Unit
Times
72.3 C901660002 Number of 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.
72-3

Measurement Point
MS supports DTM GPRS multi TS ability 5. The measurement point is A1 or A2, as shown
in the figure below.
Figure 72-2 Measurement Point of Number of mobile support DTM GPRS multi TS
ability 5
Unit
Times

GPRS multi TS ability 9
Description
Usage
Measurement Point
MS supports DTM GPRS multi TS ability 9. The measurement point is A1 or A2, as shown
in Figure 72-3.
72-4

ability 9
Unit
Times
72.5 C901660004 Number of mobile support DTM GPRS

multi TS ability 11
Description
Usage
Measurement Point
by MSC or the Classmark Change message sent by MS and the message indicates the MS
supports DTM GPRS multi TS ability 11. The measurement point is A1 or A2, as shown
in Figure 72-4.
72-5

ability 11
Unit
Times

EGPRS multi TS ability 5
Description
This counter counts the number of mobiles that support DTM EGPRS multi TS ability 5.
Usage
It is used to measure the number of mobiles that support DTM EGPRS multi TS ability 5.
Measurement Point
MS supports DTM EGPRS multi TS ability 5. The measurement point is A1 or A2, as
72-6

Figure 72-5 Measurement Point of Number of mobile support DTM EGPRS multi TS
ability 5
Unit
Times

Description
Usage
Measurement Point
72-7

ability 9
Unit
Times

Description
Usage
Measurement Point
72-8

ability 11
Unit
Times
72.9 C901660008 Number of 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 DTM GPRS multi TS
ability 5.
Measurement Point
MS supports extend DTM GPRS multi TS ability 5. The measurement point is A1 or A2,
72-9

Figure 72-8 Measurement Point of Number of mobile support extend DTM GPRS multi
TS ability 5
Unit
Times

Description
6.
Usage
ability 6.
Measurement Point
72-10

Figure 72-9 Measurement Point of Number of mobile support extend DTM GPRS multi
TS ability 6
Unit
Times

Description
9.
Usage
ability 9.
Measurement Point
72-11

Figure 72-10 Measurement Point of Number of mobile support extend DTM GPRS
multi TS ability 9
Unit
Times

Description
10.
Usage
ability 10.
Measurement Point
72-12

multi TS ability 10
Unit
Times

Description
11.
Usage
ability 11.
Measurement Point
72-13

multi TS ability 11
Unit
Times

DTM EGPRS multi TS ability 5
Description
This counter counts the number of mobiles that support extend DTM EGPRS multi TS
ability 5.
Usage
It is used to measure the number of mobiles that support extend DTM EGPRS multi TS
ability 5.
Measurement Point
MS supports extend DTM EGPRS multi TS ability 5. The measurement point is A1 or A2,
72-14

Figure 72-13 Measurement Point of Number of mobile support extend DTM EGPRS
multi TS ability 5
Unit
Times

Description
ability 6.
Usage
ability 6.
Measurement Point
72-15

multi TS ability 6
Unit
Times

Description
ability 9.
Usage
ability 9.
Measurement Point
72-16

multi TS ability 9
Unit
Times

Description
ability 10.
Usage
ability 10.
Measurement Point
72-17

multi TS ability 10
Unit
Times

Description
ability 11.
Usage
ability 11.
Measurement Point
72-18

multi TS ability 11
Unit
Times
72.19 C901660018 Number of 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 Point
This counter increments while PS control plane receives the downlink assignment requests
sent by the user plane, the resource requests sent by the user plane on two-phase access,
or the instance setup indication sent by the user plane and the message indicates the MS
supports GPRS multi TS ability 1. The measurement point is A1, A2, and A3, as shown in
Figure 72-18, Figure 72-19, Figure 72-20.
72-19

Figure 72-18 Measurement Point of Number of mobile of GPRS multi TS ability 1 - (1)
Unit
Times
72-20


TS ability 2
Description
Usage
Measurement Point
72-21

Unit
Times

TS ability 3
Description
Usage
Measurement Point
72-22

Unit
Times
72-23


TS ability 4
Description
Usage
Measurement Point
72-24

Unit
Times

TS ability 5
Description
Usage
This counter is used to measure the number of link setup requests originated from BSC to
TC.
Measurement Point
72-25

Unit
Times
72-26


TS ability 6
Description
Usage
Measurement Point
72-27

Unit
Times

TS ability 7
Description
Usage
Measurement Point
72-28

Unit
Times
72-29


TS ability 8
Description
Usage
Measurement Point
72-30

Unit
Times

TS ability 9
Description
Usage
Measurement Point
72-31

Unit
Times
72-32


TS ability 10
Description
Usage
Measurement Point
supports GPRS multi TS ability 10. The measurement point is A1, A2, and A3, as shown
in Figure 72-45, Figure 72-46, Figure 72-47.
72-33

Unit
Times

TS ability 11
Description
Usage
Measurement Point
72-34

Unit
Times
72-35


TS ability 12
Description
Usage
Measurement Point
72-36

Unit
Times

TS ability 30
Description
Usage
Measurement Point
72-37

Unit
Times
72-38


TS ability 31
Description
Usage
Measurement Point
72-39

Unit
Times

TS ability 32
Description
Usage
Measurement Point
72-40

Unit
Times
72-41


TS ability 33
Description
Usage
Measurement Point
72-42

Unit
Times

TS ability 34
Description
Usage
Measurement Point
72-43

Unit
Times
72-44

72.36 C901660035 Number of 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.
Measurement Point
supports EGPRS multi TS ability 1. The measurement point is A1, A2, and A3, as shown
Figure 72-69 Measurement Point of Number of mobile of EGPRS multi TS ability 1 - (1)
72-45

Unit
Times

TS ability 2
Description
Usage
Measurement Point
72-46

Unit
Times
72-47


TS ability 3
Description
Usage
Measurement Point
72-48

Unit
Times

TS ability 4
Description
Usage
Measurement Point
72-49

Unit
Times
72-50


TS ability 5
Description
Usage
This counter is used to measure the number of link setup requests originated from BSC to
TC.
Measurement Point
72-51

Unit
Times

TS ability 6
Description
Usage
Measurement Point
72-52

72-53

Unit
Times

TS ability 7
Description
Usage
Measurement Point
72-54

Unit
Times

TS ability 8
Description
Usage
Measurement Point
72-55

72-56

Unit
Times

TS ability 9
Description
Usage
Measurement Point
72-57

Unit
Times

TS ability 10
Description
Usage
Measurement Point
72-58

72-59

Unit
Times

TS ability 11
Description
Usage
Measurement Point
72-60

Unit
Times

TS ability 12
Description
Usage
Measurement Point
72-61

72-62

Unit
Times

TS ability 30
Description
Usage
Measurement Point
72-63

Unit
Times

TS ability 31
Description
Usage
Measurement Point
72-64

72-65

Unit
Times

TS ability 32
Description
Usage
Measurement Point
72-66

Unit
Times

TS ability 33
Description
Usage
Measurement Point
72-67

72-68

Unit
Times

TS ability 34
Description
Usage
Measurement Point
72-69

Unit
Times
72.53 C901660052 Number of 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 Point
This counter increments while Rancs process receives the setup (caller) or call confirmed
message (callee) and the voice version contained in this message is FR. The measurement
point is A1 (caller) and A2 (callee), as shown in Figure 72-120.
72-70

Figure 72-120 Measurement Point of Number of mobile support FR
Unit
Times
72.54 C901660053 Number of 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.
Measurement Point
This counter increments while Rancs process receives the setup (caller) or call
confirmed message (callee) and the voice version contained in this message is HR. The
measurement point is A1 (caller) and A2 (callee), as shown in Figure 72-121.
Figure 72-121 Measurement Point of Number of mobile support HR
72-71

Unit
Times
72.55 C901660054 Number of 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.
Measurement Point
message (callee) and the voice version contained in this message is EFR. The
Figure 72-122 Measurement Point of Number of mobile support EFR
Unit
Times
72.56 C901660055 Number of 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.
72-72

Measurement Point
message (callee) and the voice version contained in this message is AMRFR. The
Figure 72-123 Measurement Point of Number of mobile support AMRFR
Unit
Times
72.57 C901660056 Number of mobile support AMRHR

Description
This counter counts the number of mobiles that support AMRHR.
Usage
It is used to measure the number of mobiles that support AMRHR.
Measurement Point
message (callee) and the voice version contained in this message is AMRHR. The
72-73

Figure 72-124 Measurement Point of Number of mobile support AMRHR
Unit
Times
72.58 C901660057 Number of 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.
Measurement Point
message (callee) and the voice version contained in this message is wideband AMROFR.
The measurement point is A1 (caller) and A2 (callee), as shown in Figure 72-125.
72-74

Figure 72-125 Measurement Point of Number of mobile support wideband AMROFR
Unit
Times

AMRFR
Description
This counter counts the number of mobiles that support wideband AMRFR.
Usage
It is used to measure the number of mobiles that support wideband AMRFR.
Measurement Point
message (callee) and the voice version contained in this message is wideband AMRFR.
72-75

Figure 72-126 Measurement Point of Number of mobile support wideband AMRFR
Unit
Times

AMROHR
Description
This counter counts the number of mobiles that support wideband AMROHR.
Usage
It is used to measure the number of mobiles that support wideband AMROHR.
Measurement Point
message (callee) and the voice version contained in this message is wideband AMROHR.
72-76

Figure 72-127 Measurement Point of Number of mobile support wideband AMROHR
Unit
Times
72.61 C901660060 Number of mobile support AMROHR

Description
This counter counts the number of mobiles that support AMROHR.
Usage
It is used to measure the number of mobiles that support AMROHR.
Measurement Point
message (callee) and the voice version contained in this message is AMROHR. The
Figure 72-128 Measurement Point of Number of mobile support AMROHR
72-77

Unit
Times

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 Point
When PS control plane receives the downlink assignment requests sent by the user plane
or the resource requests sent by the user plane on two-phase access, if extended uplink
TBF is supported, the counter increments. The measurement point is A1 and A2, as shown
Figure 72-129 Measurement Point of Number of mobile support extend uplink TBF - (1)
72-78

Figure 72-130 Measurement Point of Number of mobile support extend uplink TBF - (2)
Unit
Times
72.63 C901660062 Number of 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.
Measurement Point
When PS control plane receives the downlink assignment requests sent by the user
plane or the resource requests sent by the user plane on two-phase access, if NACC is
supported, the counter increments. The measurement point is A1 and A2, as shown in
72-79

Figure 72-131 Measurement Point of Number of mobile support NACC - (1)
Figure 72-132 Measurement Point of Number of mobile support NACC - (2)
Unit
Times
72.64 C901660063 Number of mobile support GPRS

extend dynamic allocation
Description
This counter counts the number of mobiles that support GPRS extended dynamic
allocation.
Usage
It is used to measure the number of mobiles that support GPRS extended dynamic
allocation.
72-80

Measurement Point
or the resource requests sent by the user 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 72-133 and Figure 72-134.
Figure 72-133 Measurement Point of Number of mobile support GPRS extend dynamic
allocation - (1)
Figure 72-134 Measurement Point of Number of mobile support GPRS extend dynamic
allocation - (2)
Unit
Times
72-81

72.65 C901660064 Number of mobile support EGPRS

extend dynamic allocation
Description
This counter counts the number of mobiles that support EGPRS extended dynamic
allocation.
Usage
It is used to measure the number of mobiles that support EGPRS extended dynamic
allocation.
Measurement Point
or the resource requests sent by the user 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 72-135 and Figure 72-136.
Figure 72-135 Measurement Point of Number of mobile support EGPRS extend

dynamic allocation - (1)
72-82

Figure 72-136 Measurement Point of Number of mobile support EGPRS extend

dynamic allocation - (2)
Unit
Times
72.66 C901660065 Number of sampling received

Classmark3
Description
This counter counts the number of samples that receive Classmark3.
Usage
It is used to measure the number of samples that receive Classmark3.
Measurement Point
by MSC or the Classmark Change message sent by MS and the message indicates
Classmark3 is received. The measurement point is A1 or A2, as shown in Figure 72-137.
72-83

Figure 72-137 Measurement Point of Number of sampling received Classmark3
Unit
Times
72.67 C901660066 Number of sampling received radio

access ability
Description
This counter counts the number of samples that receive radio access ability.
Usage
It is used to measure the number of samples that receive radio access ability.
Measurement Point
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 72-138 and Figure 72-139.
72-84

Figure 72-138 Measurement Point of Number of sampling received radio access ability
- (1)
Figure 72-139 Measurement Point of Number of sampling received radio access ability
- (2)
Unit
Times
72.68 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
72-85

Figure 72-140 Measurement Point of Number of MS supporting PS handover
Unit
Times
72.69 C901660070 The Number of MS which Support

SAIC
Description
This counter counts the number of mobile phones that support SAIC.
Usage
This counter is used to find out the number of mobile phones that support SAIC. It helps
study the terminal ability of mobile phone.
Measurement Point
1. When BSC receives the handover/assignment failure message after sending the
AssignCmd command, if the classmark is changed or updated, the counter counts.
Figure 72-141 Assignment/Handover Flow
72-86

2. When BSC receives the Hoperformed Ack message, the counter counts. The
Figure 72-142 Handover Flow
Unit
Times
72.70 C901660071 The Number of MS which not

Support SAIC
Description
This counter counts the number of mobile phones that do not support SAIC.
Usage
This counter is used to find out the number of mobile phones that do not support SAIC. It
helps study the terminal ability of mobile phone.
Measurement Point
1. When BSC receives the handover/assignment failure message after sending the
AssignCmd command, if the classmark is changed or updated, the counter counts.
2. When BSC receives the Hoperformed Ack message, the counter counts.
Unit
Times
72-87

72-88

Chapter 73
MAC Port Flow Statistics
Table of Contents
Overview ..................................................................................................................73-1
C901820001 receive bytes number (high 4 bytes) ....................................................73-1
C901820002 receive bytes number (low 4 bytes) .....................................................73-2
C901820003 transmit bytes number (high 4 bytes)...................................................73-2
C901820004 transmit bytes number (low 4 bytes) ....................................................73-3
C901820005 physical band width .............................................................................73-3
C901820006 mean receiving bit rate ........................................................................73-3
C901820007 max receiving bit rate ..........................................................................73-4
C901820008 mean transmitting bit rate ....................................................................73-4
C901820009 max transmitting bit rate ......................................................................73-5
73.1 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.
73.2 C901820001 receive bytes number (high 4 bytes)

Description
This counter counts the number of bytes received at the port. When the message is
received at the port, if the received message's lower 4 bytes' accumulation overflows, the
counter increments.
Usage
This counter is used to find out the transceiving data flow at the port within the
measurement period.
Measurement Point
The counter counts when the message is received at the port.
73-1

Unit
BYTE
73.3 C901820002 receive bytes number (low 4 bytes)

Description
This counter counts the number of bytes received at the port. When the message is
received at the port, the number of bytes of the message is accumulated.
Usage
measurement period.
Measurement Point
The counter counts when the message is received at the port.
Unit
BYTE
73.4 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,
Usage
measurement period.
Measurement Point
The counter counts when the message is transmitted at the port.
Unit
BYTE
73-2

Chapter 73 MAC Port Flow Statistics
73.5 C901820004 transmit bytes number (low 4 bytes)

Description
This counter counts the number of bytes transmitted at the port. When the message is
transmitted at the port, the number of bytes of the message is accumulated.
Usage
measurement period.
Measurement Point
The counter counts when the message is transmitted at the port.
Unit
BYTE
73.6 C901820005 physical band width

Description
This counter counts the port's physical bandwidth when the statistic data is reported.
Usage
This counter is used to find out the port's physical bandwidth. If the port is faulty, then the
bandwidth is 0 Mbit/s by default (meaningless in this case).
Measurement Point
The counter counts when the data is reported.
Unit
Mbit/s
73.7 C901820006 mean receiving bit rate

Description
This counter counts the average receiving rate at the port within the measurement period.
The counter's value = The number of bytes received within the measurement period /
Measurement period * 8
73-3

Usage
This counter is used to find out the average receiving rate at the port.
Measurement Point
The counter's value is calculated when the data is reported.
Unit
bit/s
73.8 C901820007 max receiving bit rate

Description
This counter counts the maximum receiving rate at the port within the measurement period.
The receiving rate at the port is measured every 30 seconds and recorded. When it is time
to report the data, the maximum receiving rate is taken as the counter's value.
Usage
This counter is used to find out the maximum receiving rate at the port.
Measurement Point
Unit
bit/s
73.9 C901820008 mean transmitting bit rate

Description
This counter counts the average transmitting rate at the port within the measurement
period. The counter's value = The number of bytes transmitted within the measurement
period / Measurement period * 8
Usage
This counter is used to find out the average transmitting rate at the port.
Measurement Point
73-4

Chapter 73 MAC Port Flow Statistics
Unit
bit/s
73.10 C901820009 max transmitting bit rate

Description
This counter counts the maximum transmitting rate at the port within the measurement
period. The transmitting rate at the port is measured every 30 seconds and recorded.
When it is time to report the data, the maximum transmitting rate is taken as the counter's
value.
Usage
This counter is used to find out the maximum transmitting rate at the port.
Measurement Point
Unit
bit/s
73-5

73-6

Chapter 74
AMR Rate Statistics
Table of Contents
Overview ..................................................................................................................74-1
C901830001 Total Num of DL AFS12.2k frame ........................................................74-2
C901830009 Total Num of DL AHS7.95k frame........................................................74-6
C901830011 Total Num of DL AHS6.70k frame ........................................................74-7
C901830015 Total Num of UL AFS12.2k frame ........................................................74-9
C901830016 Total Num of UL AFS10.2k frame ......................................................74-10
C901830018 Total Num of UL AFS7.40k frame ...................................................... 74-11
C901830019 Total Num of UL AFS6.70k frame ...................................................... 74-11
C901830023 Total Num of UL AHS7.95k frame......................................................74-13
74.1 Overview
AMR rate statistics counts the total number of uplink/downlink frames of absolute rate at
the cell level.
74-1

AMR rate statistics at baseband counts the total number of uplink/downlink frames of
absolute rate (coding frame) according to cells. The full-rate channel has 8 rates while
the half-rate channel has 6 rates. Each carriers requires 28 counters.
Figure 74-1 shows the AMR rate statistics flow.
Figure 74-1 AMR Rate Statistics Report
74.2 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.
74-2

Chapter 74 AMR Rate Statistics
Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is
reported periodically.
Unit
Number of frames

Description
Usage
within 30 s.
Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
74-3

Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
74-4

Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
74-5

Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
Measurement Point
Unit
Number of frames
74.10 C901830009 Total Num of DL AHS7.95k frame

Description
downlink in AMR half-rate channel service.
Usage
This counter is used to find out the number of coding frames which adopt 7.95 k coding
rate in AMR half-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.
74-6

Measurement Point
Unit
Number of frames

Description
Usage
Measurement Point
Unit
Number of frames

Description
Usage
74-7

Measurement Point
Unit
Number of frames

Description
Usage
Measurement Point
Unit
Number of frames

Description
Usage
74-8

Measurement Point
Unit
Number of frames

Description
Usage
Measurement Point
Unit
Number of frames
74.16 C901830015 Total Num of UL AFS12.2k frame

Description
This counter counts the number of coding frames which adopt 12.2 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.
74-9

Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
74-10

Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
74-11

Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
74-12

Measurement Point
Unit
Number of frames

Description
Usage
within 30 s.
Measurement Point
Unit
Number of frames
74.24 C901830023 Total Num of UL AHS7.95k frame

Description
in AMR half-rate channel service.
Usage
74-13

Measurement Point
Unit
Number of frames

Description
Usage
Measurement Point
Unit
Number of frames

Description
Usage
74-14

Measurement Point
Unit
Number of frames

Description
Usage
Measurement Point
Unit
Number of frames

Description
Usage
74-15

Measurement Point
Unit
Number of frames

Description
Usage
Measurement Point
Unit
Number of frames
74-16

Chapter 75
UMAC Measurement
Table of Contents
Overview ..................................................................................................................75-3
C901850001 receive discard packets flag ................................................................75-3
C901850002 receive discard packets low 32bits ......................................................75-4
C901850003 receive discard packets high 32bits .....................................................75-4
C901850004 receive bytes flag ................................................................................75-4
C901850005 receive bytes low 32bits ......................................................................75-5
C901850006 receive bytes high 32bits .....................................................................75-5
C901850007 receive packets flag.............................................................................75-5
C901850008 receive packets low 32bits...................................................................75-6
C901850009 receive packets high 32bits .................................................................75-6
C901850010 receive broadcast packets flag ............................................................75-6
C901850011 receive broadcast packets low 32bits...................................................75-7
C901850012 receive broadcast packets high 32bits .................................................75-7
C901850013 receive multicast packets flag..............................................................75-8
C901850014 receive multicast packets low 32bits ....................................................75-8
C901850015 receive multicast packets high 32bits ..................................................75-8
C901850016 receive CRC or align error packets flag ...............................................75-9
C901850017 receive CRC or align error packets low 32bits .....................................75-9
C901850018 receive CRC or align error packets high 32bits ..................................75-10
C901850019 receive small than 64 bytes packets flag ...........................................75-10
C901850020 receive small than 64 bytes packets low 32bits..................................75-10
C901850021 receive small than 64 bytes packets high 32bits ................................ 75-11
C901850022 receive large than 1518 bytes packets flag ........................................ 75-11
C901850023 receive large than 1518 bytes packets low 32bits ..............................75-12
C901850024 receive large than 1518 bytes packets high 32bits.............................75-12
C901850025 The flag of received fragment packets ...............................................75-12
C901850026 Number of fragment packets received (low 32 bit) .............................75-13
C901850027 Number of received fragment packets (high 32 bit)............................75-13
C901850028 receive Jabber packets flag ...............................................................75-14
C901850029 receive Jabber packets low 32bits .....................................................75-14
C901850030 receive Jabber packets high 32bits....................................................75-14
C901850031 receive Collision count flag ................................................................75-15
C901850032 receive Collision count low 32bits ......................................................75-15
C901850033 receive Collision count high 32bits.....................................................75-15
C901850034 receive 64 bytes packets flag ............................................................75-16
C901850035 receive 64 bytes packets low 32bits ..................................................75-16
C901850036 receive 64 bytes packets high 32bits .................................................75-16
75-1

C901850037 receive 65 to 127 bytes packets flag..................................................75-17

C901850038 receive 65 to 127 bytes packets low 32bits........................................75-17
C901850039 receive 65 to 127 bytes packets high 32bits ......................................75-18
C901850040 receive 128 to 255 bytes packets flag................................................75-18
C901850041 receive 128 to 255 bytes packets low 32bits......................................75-18
C901850042 receive 128 to 255 bytes packets high 32bits ....................................75-19
C901850043 receive 256 to 511 bytes packets flag ................................................75-19
C901850044 receive 256 to 511 bytes packets low 32bits ......................................75-20
C901850045 receive 256 to 511 bytes packets high 32bits.....................................75-20
C901850046 receive 512 to 1023 bytes packets flag..............................................75-20
C901850047 receive 512 to 1023 bytes packets low 32bits....................................75-21
C901850048 receive 512 to 1023 bytes packets high 32bits ..................................75-21
C901850049 receive 1024 to 1518 bytes packets flag............................................75-22
C901850050 receive 1024 to 1518 bytes packets low 32bits ..................................75-22
C901850051 receive 1024 to 1518 bytes packets high 32bits.................................75-22
C901850052 send discard packets flag ..................................................................75-23
C901850053 send discard packets low 32bits ........................................................75-23
C901850054 send discard packets high 32bits.......................................................75-24
C901850055 send packet bytes flag.......................................................................75-24
C901850056 send packet bytes low 32bits.............................................................75-24
C901850057 send packets bytes high 32bits..........................................................75-25
C901850058 send packets flag ..............................................................................75-25
C901850059 send packets low 32bits ....................................................................75-25
C901850060 send packets high 32bits ...................................................................75-26
C901850061 send broadcast packets flag ..............................................................75-26
C901850062 send broadcast packets low 32bits ....................................................75-26
C901850063 send broadcast packets high 32bits...................................................75-27
C901850064 send multicast packets flag ...............................................................75-27
C901850065 send multicast packets low 32bits......................................................75-27
C901850066 send multicast packets high 32bits ....................................................75-28
C901850067 send CRC or Align error packets flag ................................................75-28
C901850068 send CRC or Align error packets low 32bits.......................................75-28
C901850069 send CRC or Align error packets high 32bits .....................................75-29
C901850070 send small than 64 bytes packets flag ...............................................75-29
C901850071 send small than 64 bytes packets low 32bits .....................................75-30
C901850072 send small than 64 bytes packets high 32bits....................................75-30
C901850073 send large than 1518 bytes packets flag............................................75-30
C901850074 send large than 1518 bytes packets low 32bits..................................75-31
C901850075 send large than 1518 bytes packets high 32bits ................................75-31
C901850076 The flag of sent fragment packets......................................................75-32
C901850077 Number of sent fragment packets (low 32 bit)....................................75-32
C901850078 Number of sent fragment packets (high 32 bit) ..................................75-32
C901850079 send Jabber packets flag...................................................................75-33
C901850080 send Jabber packets low 32bits.........................................................75-33
C901850081 send Jabber packets high 32bits .......................................................75-33
75-2

Chapter 75 UMAC Measurement
C901850082 send Collision count flag....................................................................75-34

C901850083 send Collision count low 32bits..........................................................75-34
C901850084 send Collision count high 32bits ........................................................75-35
C901850085 send 64 bytes packets flag ................................................................75-35
C901850086 send 64 bytes packets low 32bits ......................................................75-35
C901850087 send 64 bytes packets high 32bits.....................................................75-36
C901850088 send 65 to 127 bytes packets flag .....................................................75-36
C901850089 send 65 to 127 bytes packets low 32bits ...........................................75-36
C901850090 send 65 to 127 bytes packets high 32bits ..........................................75-37
C901850091 send 128 to 255 bytes packets flag ...................................................75-37
C901850092 send 128 to 255 bytes packets low 32bits .........................................75-38
C901850093 send 128 to 255 bytes packets high 32bits ........................................75-38
C901850094 send 256 to 511 bytes packets flag....................................................75-38
C901850095 send 256 to 511 bytes packets low 32bits..........................................75-39
C901850096 send 256 to 511 bytes packets high 32bits ........................................75-39
C901850097 send 512 to 1023 bytes packets flag .................................................75-39
C901850098 send 512 to 1023 bytes packets low 32bits........................................75-40
C901850099 send 512 to 1023 bytes packets high 32bits ......................................75-40
C901850100 send 1024 to 1518 bytes packets flag................................................75-41
C901850101 send 1024 to 1518 bytes packets low 32bits......................................75-41
C901850102 send 1024 to 1518 bytes packets high 32bits ....................................75-41
75.1 Overview
UMAC measurement performs measurement for transceiving packets, bytes, and incorrect
packets on the MAC layer of each link.
Statistic unit in this measurement is link.
75.2 C901850001 receive discard packets flag

Description
This counter flags the property of the statistic item.
Usage
l 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.
l 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.
l If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does
not guarantee that all overflows are detected.
75-3

Measurement Point
None
75.3 C901850002 receive discard packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of discarded packet in the
receiving direction.
Usage
This counter is used to find out the amount of packets discarded in the receiving direction.
Measurement Point
The counter counts when the packet is received.
75.4 C901850003 receive discard packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of discarded packet in the
receiving direction.
Usage
This counter is used to find out the amount of packets discarded in the receiving direction.
Measurement Point
75.5 C901850004 receive bytes flag

Description
Usage
75-4

Measurement Point
None
75.6 C901850005 receive bytes low 32bits

Description
This counter records the lower 32 bits of the statistic item of total bytes of received packets.
Usage
This counter is used to find out the total number of bytes received.
Measurement Point
75.7 C901850006 receive bytes high 32bits

Description
This counter records the higher 32 bits of the statistic item of total bytes of received packets.
Usage
This counter is used to find out the total number of bytes received.
Measurement Point
75.8 C901850007 receive packets flag

Description
Usage
75-5

Measurement Point
None
75.9 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.
Measurement Point
75.10 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.
Measurement Point
75.11 C901850010 receive broadcast packets flag

Description
Usage
75-6

Measurement Point
None
75.12 C901850011 receive broadcast packets low

32bits
Description
broadcast packets.
Usage
This counter is used to find out the number of broadcast packets received.
Measurement Point
75.13 C901850012 receive broadcast packets high

32bits
Description
broadcast packets.
Usage
This counter is used to find out the number of broadcast packets received.
Measurement Point
75-7

75.14 C901850013 receive multicast packets flag

Description
Usage
Measurement Point
None
75.15 C901850014 receive multicast packets low 32bits

Description
multicast packets.
Usage
This counter is used to find out the number of multicast packets received.
Measurement Point
75.16 C901850015 receive multicast packets high

32bits
Description
multicast packets.
Usage
This counter is used to find out the number of multicast packets received.
75-8

Measurement Point
75.17 C901850016 receive CRC or align error packets

flag
Description
Usage
Measurement Point
None

low 32bits
Description
This counter records the lower 32 bits of the statistic item of the number of received CRC
or alignment error packets.
Usage
This counter is used to find out the number of received CRC or alignment error packets.
Measurement Point
75-9


high 32bits
Description
This counter records the higher 32 bits of the statistic item of the number of received CRC
or alignment error packets.
Usage
This counter is used to find out the number of received CRC or alignment error packets.
Measurement Point
75.20 C901850019 receive small than 64 bytes packets

flag
Description
Usage
Measurement Point
None

low 32bits
Description
This counter records the lower 32 bits of the statistic item of the number of received packets
of which the size is smaller than 64 bytes.
75-10

Usage
This counter is used to find out the number of received packets of which the size is smaller
than 64 bytes.
Measurement Point

high 32bits
Description
packets of which the size is smaller than 64 bytes.
Usage
This counter is used to find out the number of received packets of which the size is smaller
than 64 bytes.
Measurement Point
75.23 C901850022 receive large than 1518 bytes

packets flag
Description
Usage
Measurement Point
None
75-11


packets low 32bits
Description
of which the size is larger than 1518 bytes.
Usage
This counter is used to find out the number of received packets of which the size is larger
than 1518 bytes.
Measurement Point

packets high 32bits
Description
packets of which the size is larger than 1518 bytes.
Usage
This counter is used to find out the number of received packets of which the size is larger
than 1518 bytes.
Measurement Point
75.26 C901850025 The flag of received fragment

packets
Description
Usage
75-12

Measurement Point
None
75.27 C901850026 Number of fragment packets

received (low 32 bit)
Description
fragment packets.
Usage
This counter is used to find out the number of received fragment packets.
Measurement Point
75.28 C901850027 Number of received fragment

packets (high 32 bit)
Description
fragment packets.
Usage
This counter is used to find out the number of received fragment packets.
Measurement Point
75-13

75.29 C901850028 receive Jabber packets flag

Description
Usage
Measurement Point
None
75.30 C901850029 receive Jabber packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of received Jabber
packets.
Usage
This counter is used to find out the number of received Jabber packets.
Measurement Point
75.31 C901850030 receive Jabber packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received Jabber
packets.
Usage
This counter is used to find out the number of received Jabber packets.
Measurement Point
75-14

75.32 C901850031 receive Collision count flag

Description
Usage
Measurement Point
None
75.33 C901850032 receive Collision count low 32bits

Description
collisions.
Usage
This counter is used to find out the number of received collisions.
Measurement Point
75.34 C901850033 receive Collision count high 32bits

Description
collisions.
Usage
This counter is used to find out the number of received collisions.
Measurement Point
75-15

75.35 C901850034 receive 64 bytes packets flag

Description
Usage
Measurement Point
None
75.36 C901850035 receive 64 bytes packets low 32bits

Description
of which the size is 64 bytes.
Usage
This counter is used to find out the number of received packets of which the size is 64
bytes.
Measurement Point
75.37 C901850036 receive 64 bytes packets high 32bits

Description
packets of which the size is 64 bytes.
Usage
This counter is used to find out the number of received packets of which the size is 64
bytes.
75-16

Measurement Point
75.38 C901850037 receive 65 to 127 bytes packets flag

Description
Usage
Measurement Point
None
75.39 C901850038 receive 65 to 127 bytes packets low

32bits
Description
of which the size is between 65 bytes and 127 bytes.
Usage
This counter is used to find out the number of received packets of which the size is between
65 bytes and 127 bytes.
Measurement Point
75-17

75.40 C901850039 receive 65 to 127 bytes packets high

32bits
Description
packets of which the size is between 65 bytes and 127 bytes.
Usage
Measurement Point

Description
Usage
Measurement Point
None
75.42 C901850041 receive 128 to 255 bytes packets

low 32bits
Description
75-18

Usage
Measurement Point

high 32bits
Description
Usage
Measurement Point

Description
Usage
Measurement Point
None
75-19


low 32bits
Description
Usage
Measurement Point

high 32bits
Description
Usage
Measurement Point

flag
Description
Usage
75-20

Measurement Point
None

low 32bits
Description
Usage
Measurement Point

high 32bits
Description
Usage
Measurement Point
75-21


flag
Description
Usage
Measurement Point
None

low 32bits
Description
Usage
Measurement Point

high 32bits
Description
75-22

Usage
Measurement Point
75.53 C901850052 send discard packets flag

Description
Usage
Measurement Point
None
75.54 C901850053 send discard packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted
packets being discarded.
Usage
This counter is used to find out the number of transmitted packets being discarded.
Measurement Point
The counter counts when the packet is transmitted.
75-23

75.55 C901850054 send discard packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted
packets being discarded.
Usage
This counter is used to find out the number of transmitted packets being discarded.
Measurement Point
75.56 C901850055 send packet bytes flag

Description
Usage
Measurement Point
None
75.57 C901850056 send packet bytes low 32bits

Description
This counter records the lower 32 bits of the statistic item of total bytes of transmitted
packets.
Usage
This counter is used to find out the total number of bytes of transmitted packets.
Measurement Point
75-24

75.58 C901850057 send packets bytes high 32bits

Description
This counter records the higher 32 bits of the statistic item of total bytes of transmitted
packets.
Usage
This counter is used to find out the total number of bytes of transmitted packets.
Measurement Point
75.59 C901850058 send packets flag

Description
Usage
Measurement Point
None
75.60 C901850059 send packets low 32bits

Description
packets.
Usage
This counter is used to find out the total number of transmitted packets.
Measurement Point
75-25

75.61 C901850060 send packets high 32bits

Description
packets.
Usage
This counter is used to find out the total number of transmitted packets.
Measurement Point
75.62 C901850061 send broadcast packets flag

Description
Usage
Measurement Point
None
75.63 C901850062 send broadcast packets low 32bits

Description
broadcast packets.
Usage
This counter is used to find out the number of transmitted broadcast packets.
Measurement Point
75-26

75.64 C901850063 send broadcast packets high 32bits

Description
broadcast packets.
Usage
This counter is used to find out the number of transmitted broadcast packets.
Measurement Point
75.65 C901850064 send multicast packets flag

Description
Usage
Measurement Point
None
75.66 C901850065 send multicast packets low 32bits

Description
multicast packets.
Usage
This counter is used to find out the number of transmitted multicast packets.
Measurement Point
75-27

75.67 C901850066 send multicast packets high 32bits

Description
multicast packets.
Usage
This counter is used to find out the number of transmitted multicast packets.
Measurement Point
75.68 C901850067 send CRC or Align error packets flag

Description
Usage
Measurement Point
None
75.69 C901850068 send CRC or Align error packets

low 32bits
Description
CRC or alignment error packets.
Usage
This counter is used to find out the number of transmitted CRC or alignment error packets.
75-28

Measurement Point
75.70 C901850069 send CRC or Align error packets

high 32bits
Description
CRC or alignment error packets.
Usage
This counter is used to find out the number of transmitted CRC or alignment error packets.
Measurement Point
75.71 C901850070 send small than 64 bytes packets

flag
Description
Usage
Measurement Point
None
75-29


low 32bits
Description
Usage
This counter is used to find out the number of transmitted packets of which the size is
smaller than 64 bytes.
Measurement Point

high 32bits
Description
Usage
smaller than 64 bytes.
Measurement Point
75.74 C901850073 send large than 1518 bytes packets

flag
Description
Usage
75-30

Measurement Point
None

low 32bits
Description
Usage
larger than 1518 bytes.
Measurement Point

high 32bits
Description
Usage
larger than 1518 bytes.
Measurement Point
75-31

75.77 C901850076 The flag of sent fragment packets

Description
Usage
Measurement Point
None
75.78 C901850077 Number of sent fragment packets

(low 32 bit)
Description
fragment packets.
Usage
This counter is used to find out the number of transmitted fragment packets.
Measurement Point
75.79 C901850078 Number of sent fragment packets

(high 32 bit)
Description
fragment packets.
Usage
This counter is used to find out the number of transmitted fragment packets.
75-32

Measurement Point
75.80 C901850079 send Jabber packets flag

Description
Usage
Measurement Point
None
75.81 C901850080 send Jabber packets low 32bits

Description
Jabber packets.
Usage
This counter is used to find out the number of transmitted Jabber packets.
Measurement Point
75.82 C901850081 send Jabber packets high 32bits

Description
Jabber packets.
75-33

Usage
This counter is used to find out the number of transmitted Jabber packets.
Measurement Point
75.83 C901850082 send Collision count flag

Description
Usage
Measurement Point
None
75.84 C901850083 send Collision count low 32bits

Description
collisions.
Usage
This counter is used to find out the number of transmitted collisions.
Measurement Point
75-34

75.85 C901850084 send Collision count high 32bits

Description
collisions.
Usage
This counter is used to find out the number of transmitted collisions.
Measurement Point
75.86 C901850085 send 64 bytes packets flag

Description
Usage
Measurement Point
None
75.87 C901850086 send 64 bytes packets low 32bits

Description
Usage
This counter is used to find out the number of transmitted packets of which the size is 64
bytes.
75-35

Measurement Point
75.88 C901850087 send 64 bytes packets high 32bits

Description
Usage
This counter is used to find out the number of transmitted packets of which the size is 64
bytes.
Measurement Point
75.89 C901850088 send 65 to 127 bytes packets flag

Description
Usage
Measurement Point
None
75.90 C901850089 send 65 to 127 bytes packets low

32bits
Description
75-36

Usage
between 65 bytes and 127 bytes.
Measurement Point
75.91 C901850090 send 65 to 127 bytes packets high

32bits
Description
Usage
Measurement Point

Description
Usage
Measurement Point
None
75-37


32bits
Description
Usage
Measurement Point

32bits
Description
Usage
Measurement Point

Description
Usage
75-38

Measurement Point
None

32bits
Description
Usage
Measurement Point

32bits
Description
Usage
Measurement Point

Description
75-39

Usage
Measurement Point
None

32bits
Description
Usage
Measurement Point
75.100 C901850099 send 512 to 1023 bytes packets

high 32bits
Description
Usage
Measurement Point
75-40


flag
Description
Usage
Measurement Point
None

low 32bits
Description
Usage
Measurement Point

high 32bits
Description
75-41

Usage
Measurement Point
75-42

Chapter 76
PS Handover Cause
Measurement
Table of Contents
Overview ..................................................................................................................76-1
C901880001 Number of handover attempts due to uplink received strength.............76-1
C901880002 Number of handover attempts due to downlink received strength ........76-2
C901880003 Number of handover attempts due to uplink quality .............................76-3
C901880004 Number of handover attempts due to downlink quality.........................76-4
C901880005 Number of handover attempts due to uplink interference .....................76-4
C901880006 Number of handover attempts due to downlink interference ................76-5
C901880007 Number of handover attempts due to PBGT ........................................76-6
C901880008 Number of handover attempts due to large TA.....................................76-6
C901880009 Number of handover attempts due to uplink break up quickly ..............76-7
C901880010 Number of handover attempts due to macro-micro switch ...................76-8
C901880011 Number of handover attempts due to high traffic..................................76-9
C901880012 Number of handover attempts due to a good standard level in FDD
adjacent cell .............................................................................................................76-9
C901880013 Number of handover attempts due to a good standard level in TDD
adjacent cell ...........................................................................................................76-10
C901880014 Number of handover attempts due to PCCN...................................... 76-11
76.1 Overview
Counters of PS handover cause measurement are used to study causes of PS handover
initiated by MS during PS service process. According to the cell's radio environment and
BSC's configuration, the PS handover algorithm's decision module initiates handover due
to vairous handover causes, optimizing the resource usage and improving the PS service
quality.

uplink received strength
Statistics object
BSC
76-1

Description
This counter counts the number of handover attempts initiated by MS due to too low uplink
receiving strength. This counter is used to find out the frequency of handover initiated by
MS due to uplink receiving strength. If the counter's value is large, it indicates that the
uplink level is poor. After BSC receives the measurement report, it performs handover
decision. If the handover decision indicates that handover is required and the handover is
due to uplink receiving strength, the counter increments. The measurement point is A, as
Figure 76-1 Measurement Point of Number of handover attempts due to uplink received
strength
Unit
Times

downlink received strength
Statistics object
BSC
Description
This counter counts the number of handover attempts initiated by MS due to too low
downlink receiving strength. This counter is used to find out the frequency of handover
initiated by MS due to downlink receiving strength. If the counter's value is large, it
indicates that the downlink level is poor. After BSC receives the measurement report, it
performs handover decision. If the handover decision indicates that handover is required
and the handover is due to downlink receiving strength, the counter increments. The
76-2

Chapter 76 PS Handover Cause Measurement
Figure 76-2 Measurement Point of Number of handover attempts due to downlink

received strength
Unit
Times

uplink quality
Statistics object
BSC
Description
This counter counts the number of handover attempts initiated by MS due to too poor
uplink quality. This counter is used to find out the frequency of handover initiated by MS
due to uplink quality. If the counter's value is large, it indicates that the uplink quality is
poor. After BSC receives the measurement report, it performs handover decision. If the
handover decision indicates that handover is required and the handover is due to uplink
quality, the counter increments. The measurement point is A, as shown in Figure 76-3.
Figure 76-3 Measurement Point of Number of handover attempts due to uplink quality
Unit
Times
76-3


to downlink quality
Statistics object
BSC
Description
This counter counts the number of handover attempts initiated by MS due to too poor
downlink quality. This counter is used to find out the frequency of handover initiated by MS
due to downlink quality. If the counter's value is large, it indicates that the downlink quality
is poor. After BSC receives the measurement report, it performs handover decision. If the
handover decision indicates that handover is required and the handover is due to downlink
quality, the counter increments. The measurement point is A, as shown in Figure 76-4.

quality
Unit
Times

uplink interference
Statistics object
BSC
Description
This counter counts the number of handover attempts initiated by MS due to too strong
uplink interference. This counter is used to find out the frequency of handover initiated by
MS due to uplink interference. If the counter's value is large, it indicates that the uplink
interference is strong. After BSC receives the measurement report, it performs handover
76-4

due to uplink interference, the counter increments. The measurement point is A, as shown
in Figure 76-5.
Figure 76-5 Measurement Point of Number of handover attempts due to uplink

interference
Unit
Times

to downlink interference
Statistics object
BSC
Description
This counter counts the number of handover attempts initiated by MS due to too strong
downlink interference. This counter is used to find out the frequency of handover initiated
by MS due to downlink interference. If the counter's value is large, it indicates that the
downlink interference is strong. After BSC receives the measurement report, it performs
handover decision. If the handover decision indicates that handover is required and the
handover is due to downlink interference, the counter increments. The measurement point

interference
76-5

Unit
Times

to PBGT
Statistics object
BSC
Description
This counter counts the number of handover attempts initiated by MS due to PBGT value.
If the PBGT value is larger than zero, it indicates that the radio environment of the adjacent
cell is better than that of the local cell. The PBGT handover will occur when the number of
times that the PBGT value is larger than zero reaches the threshold value. This counter
is used to find out the frequency of handover initiated by MS due to PBGT value. If the
counter's value is large, it indicates that the local cell's signal is weaker than that of the
adjacent cell. After BSC receives the measurement report, it performs handover decision.
If the handover decision indicates that handover is required and the handover is due to
PBGT value, the counter increments. The measurement point is A, as shown in Figure
76-7.
Figure 76-7 Measurement Point of Number of handover attempts due to PBGT
Unit
Times

to large TA
Statistics object
BSC
76-6

Description
This counter counts the number of handover attempts initiated by MS due to too large TA.
Increasing TA indicates that MS is moving away from the local cell. When the distance
between MS and the local cell reaches to a certain value, the handover due to large TA
will occur. This counter is used to find out the frequency of handover due to too large TA.
The counter's value reflects the mobility of users in the local cell. After BSC receives the
measurement report, it performs handover decision. If the handover decision indicates
that handover is required and the handover is due to too large TA, the counter increments.
Figure 76-8 Measurement Point of Number of handover attempts due to large TA
Unit
Times

to uplink break up quickly
Statistics object
BSC
Description
This counter counts the number of handover attempts initiated by MS due to uplink fast
fading. If the uplink level drops suddenly in several consecutive measurement reports, the
handover due to uplink fast fading will occur. This counter is used to find out the frequency
of handover due to uplink fast fading. The counter's value reflects the stability of local
radio environment. After BSC receives the measurement report, it performs handover
due to uplink fast fading, the counter increments. The measurement point is A, as shown
in Figure 76-9.
76-7

Figure 76-9 Measurement Point of Number of handover attempts due to uplink break
up quickly
Unit
Times

to macro-micro switch
Statistics object
BSC
Description
This counter counts the number of handover attempts initiated by MS due to macro-micro
switch. If the adjacent cell's level is larger than or equal to the threshold value and the
adjacnet cell is a lower-level cell, the macro-micro handover will occur. This counter is
used to find out the frequency of handover initiated by MS due to macro-micro switch.
The counter's value reflects the traffic absorption of the micro cell. After BSC receives the
measurement report, it performs handover decision. If the handover decision indicates
that handover is required and the handover is due to macro-micro switch, the counter
Figure 76-10 Measurement Point of Number of handover attempts due to macro-micro

switch
76-8

Unit
Times

to high traffic
Statistics object
BSC
Description
This counter counts the number of MS's handover attempts due to traffic. The handover is
initiated by BSC, some traffic of the local cell is moved to the destination cell, which reduces
the traffic load of the local cell. This counter is used to find out the frequency of MS's
handover due to traffic. The counter's value reflects the local cell's service adjustment by
BSC. After BSC receives the traffic alarm, it performs handover decision. If the handover
decision indicates that handover is required, the counter increments. The measurement
Figure 76-11 Measurement Point of Number of handover attempts due to high traffic
Unit
Times

to a good standard level in FDD adjacent cell
Statistics object
BSC
76-9

Description
This counter counts the number of MS's handover attempts due to good base level in FDD
adjacent cell. This counter is used to find out the frequency of handover due to good base
level in FDD adjacent cell. The counter's value reflects the traffic absorption in the FDD
network. After BSC receives the measurement report, it performs handover decision. If
the handover decision indicates that handover is required and the handover is due to good
base level in FDD adjacent cell, the counter increments. The measurement point is A, as
Figure 76-12 Measurement Point of Number of handover attempts due to a good

standard level in FDD adjacent cell
Unit
Times

to a good standard level in TDD adjacent cell
Statistics object
BSC
Description
This counter counts the number of MS's handover attempts due to good base level in TDD
adjacent cell. This counter is used to find out the frequency of handover due to good base
level in TDD adjacent cell. The counter's value reflects the traffic absorption in the TDD
network. After BSC receives the measurement report, it performs handover decision. If
the handover decision indicates that handover is required and the handover is due to good
base level in TDD adjacent cell, the counter increments. The measurement point is A, as
76-10

Figure 76-13 Measurement Point of Number of handover attempts due to a good

standard level in TDD adjacent cell
Unit
Times

to PCCN
Statistics object
BSC
Description
This counter counts the number of MS's handover attempts due to Packet Cell Change
Notification (PCCN). This counter is used to find out the frequency of handover due to
Packet Cell Change Notification (PCCN). The counter's value reflects that the local cell's
signal is weaker than that of the destination cell specified by PCCN. After BSC receives
PCCN, if both the cell and MS support PS handover and the cell allows handover due to
PCCN, then MS attempts PS handover, and the counter increments. The measurement
Figure 76-14 Measurement Point of Number of handover attempts due to PCCN
Unit
Times
76-11

76-12

Chapter 77
PS General Handover
Measurement
Table of Contents
Overview ..................................................................................................................77-2
C901890001 Number of synchronous handover executions .....................................77-2
C901890002 Number of successful synchronous handovers....................................77-3
C901890003 Number of pre-synchronous handover executions...............................77-4
C901890004 Number of successful pre-synchronous handovers .............................77-5
C901890005 Number of asynchronous handover executions ...................................77-6
C901890006 Number of successful asynchronous handovers..................................77-7
C901890007 Number of normal handover executions ..............................................77-8
C901890008 Number of successful normal handovers .............................................77-9
C901890009 Number of optimised handover executions ........................................77-10
C901890010 Number of successful optimised handovers....................................... 77-11
C901890011 Number of Intra-BSC inter-cell handover out attempts .......................77-12
C901890012 Number of Intra-BSC inter-cell handover out executions....................77-12
C901890013 Number of successful Intra-BSC inter-cell handover out ....................77-13
C901890014 Number of Inter-BSC handover out attempts .....................................77-14
C901890015 Number of Inter-BSC handover out executions..................................77-15
C901890016 Number of successful Inter-BSC handover out ..................................77-16
C901890017 Number of handover in attempts .......................................................77-17
C901890018 Number of handover in executions ....................................................77-17
C901890019 Number of successful handover in.....................................................77-18
C901890020 Number of Intra-cell handover attempts.............................................77-19
C901890021 Number of Intra-Cell handover executions.........................................77-19
C901890022 Number of successful Intra-cell handovers ........................................77-20
C901890023 Number of invalid Intra-cell handovers...............................................77-20
C901890024 Number of 2G to FDD handover attempts .........................................77-21
C901890025 Number of 2G to FDD handover executions ......................................77-21
C901890026 Number of successful 2G to FDD handovers.....................................77-22
C901890027 Number of 2G to TDD handover attempts .........................................77-23
C901890028 Number of 2G to TDD handover executions ......................................77-24
C901890029 Number of successful 2G to TDD handovers.....................................77-24
C901890030 Number of 3G to 2G handover attempts ............................................77-25
C901890031 Number of 3G to 2G handover executions.........................................77-26
C901890032 Number of successful 3G to 2G handovers .......................................77-27
C901890033 Number of T12 expiry........................................................................77-27
77-1

C901890034 Number of PCCF received ................................................................77-28

with cause Create PFC Failure...............................................................................77-29
with cause PS Handover Target not allowed ..........................................................77-29
with cause PS Handover not Supported in Target BSS or Target System ...............77-30
with cause other reasons........................................................................................77-31
C901890039 Number of failure in optimised handover due to failure alloc resource
..............................................................................................................................77-32
C901890040 Number of failure in optimised handover due to PS handover not
supported in target cell ...........................................................................................77-33
77.1 Overview
Counters of PS general handover measurement are used to study the number of various
types of PS handover successes and failures during the PS service process. They also
help study the frequency of different types of abnormal handovers.

executions
Statistics object
Cell
Description
This counter counts the number of synchronous handovers initiated by MS in the source
cell. The source cell and destination cell of the synchronous handover are under the same
site. This counter is used to find out the frequency of the synchronous handover initiated
by MS in the source cell. It is one of the parameters that evaluate the radio environment.
When BSC sends the PS HANDOVER COMMAND message to MS, if the handover is
synchronous handover, then the counter increments. The measurement point is A, as
77-2

Chapter 77 PS General Handover Measurement
Figure 77-1 Measurement Point of Number of synchronous handover executions
Unit
Times
77.3 C901890002 Number of successful synchronous

handovers
Statistics object
Cell
Description
This counter counts the number of successful synchronous handovers initiated by MS in
the source cell. This counter is used to find out the number of successful synchronous
handovers in the source cell. It helps study the synchronous handover condition. If the
handover is synchronous handover and is of normal handover mode, then MS performs
handover to the channel allocated in the new cell after receiving the PS HANDOVER
COMMAND message. After the new cell receives the first correct RLC/MAC block, the
PS HANDOVER COMPLETE message is sent to SGSN, then SGSN sends the DELETE
BSS PFC message to notify the source cell to release radio resource. When the source
cell receives the DELETE BSS PFC message, it indicates that the handover is completed,
and the counter increments. The measurement point is A, as shown in Figure 77-2.
If the handover is synchronous handover and is of optimized handover mode, then
MS performs handover to the channel allocated in the new cell after receiving the PS
HANDOVER COMMAND message. After the new cell receives the first correct RLC/MAC
block, the PS HANDOVER COMPLETE message is sent to SGSN, and the optimized
handover complete command (PS_OPTHO_END) is sent to the source cell. Then, the
source cell considers that the handover succeeds, and the counter increments. The
77-3

Figure 77-2 Measurement Point of Number of successful synchronous handovers - (1)
Figure 77-3 Measurement Point of Number of successful synchronous handovers - (2)
Unit
Times

handover executions
Statistics object
Cell
Description
This counter counts the number of pre-synchronous handovers initiated by MS in the
source cell. The source cell and destination cell of the pre-synchronous handover are not
under the same site. This counter is used to find out the frequency of the pre-synchronous
77-4

handover initiated by MS in the source cell. It is one of the parameters that evaluate
the radio environment. When BSC sends the PS HANDOVER COMMAND message
to MS, if the handover is pre-synchronous handover, then the counter increments. The
Figure 77-4 Measurement Point of Number of pre-synchronous handover executions
Unit
Times
77.5 C901890004 Number of successful

pre-synchronous handovers
Statistics object
Cell
Description
This counter counts the number of successful pre-synchronous handovers initiated
by MS in the source cell. This counter is used to find out the number of successful
pre-synchronous handovers in the source cell. It helps study the pre-synchronous
handover condition. If the handover is pre-synchronous handover and is of normal
handover mode, then, after the new cell receives the first correct RLC/MAC block, the PS
HANDOVER COMPLETE message is sent to SGSN, and SGSN sends the DELETE BSS
PFC message to notify the source cell to release radio resource. When the source cell
receives the DELETE BSS PFC message, it indicates that the handover is completed,
If the handover is pre-synchronous handover and is of optimized handover mode,

then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER
COMPLETE message is sent to SGSN, and the optimized handover complete command
(PS_OPTHO_END) is sent to the source cell. Then, the source cell considers that the
handover succeeds, and the counter increments. The measurement point is A, as shown
in Figure 77-6.
77-5

Figure 77-5 Measurement Point of Number of pre-synchronous handover successes

- (1)
Figure 77-6 Measurement Point of Number of pre-synchronous handover successes

- (2)
Unit
Times

executions
Statistics object
Cell
Description
This counter counts the number of asynchronous handovers initiated by MS in the source
cell. The source cell and destination cell of the synchronous handover are not under the
77-6

same site. This counter is used to find out the frequency of the asynchronous handover
initiated by MS in the source cell. It is one of the parameters that evaluate the radio
environment. When BSC sends the PS HANDOVER COMMAND message to MS, if the
handover is asynchronous handover, then the counter increments. The measurement
Figure 77-7 Measurement Point of Number of asynchronous handover executions
Unit
Times
77.7 C901890006 Number of successful asynchronous

handovers
Statistics object
Cell
Description
This counter counts the number of successful asynchronous handovers initiated by MS in
the source cell. This counter is used to find out the number of successful asynchronous
handovers in the source cell. It helps study the asynchronous handover condition. If the
handover is asynchronous handover and is of normal handover mode, then, after the new
cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message
is sent to SGSN, and SGSN sends the DELETE BSS PFC message to notify the source cell
to release radio resource. When the source cell receives the DELETE BSS PFC message,
it indicates that the handover is completed, and the counter increments. The measurement
If the handover is asynchronous handover and is of optimized handover mode, then,

after the new cell receives the first correct RLC/MAC block, the PS HANDOVER
in Figure 77-9.
77-7

Figure 77-8 Measurement Point of Number of successful asynchronous handovers - (1)
Figure 77-9 Measurement Point of Number of successful asynchronous handovers - (2)
Unit
Times
77.8 C901890007 Number of normal handover

executions
Statistics object
Cell
Description
This counter counts the number of normal handovers initiated by MS in the source cell.
This counter is used to find out the frequency of the normal handover initiated by MS in
the source cell. It is one of the parameters that evaluate the radio environment. When
77-8

BSC sends the PS HANDOVER COMMAND message to MS, if the handover is normal
handover, then the counter increments. The measurement point is A, as shown in Figure
77-10.
Figure 77-10 Measurement Point of Number of normal handover executions
Unit
Times
77.9 C901890008 Number of successful normal

handovers
Statistics object
Cell
Description
This counter counts the number of successful normal handovers initiated by MS in the
source cell. This counter is used to find out the number of successful normal handovers in
the source cell. It helps study the normal handover condition. If the handover is of normal
handover mode, then, after the new cell receives the first correct RLC/MAC block, the
PS HANDOVER COMPLETE message is sent to SGSN, and SGSN sends the DELETE
BSS PFC message to notify the source cell to release radio resource. When the source
cell receives the DELETE BSS PFC message, it indicates that the handover is completed,
77-9

Figure 77-11 Measurement Point of Number of successful normal handovers
Unit
Times
77.10 C901890009 Number of optimised handover

executions
Statistics object
Cell
Description
This counter counts the number of optimized handover executions initiated by MS in
the source cell. During the optimized handover, the source cell and the destination cell
have the same NSE and Routing Area Code (RAC). This counter is used to find out
the frequency of the optimized handover execution in the source cell. It is one of the
parameters that evaluate the radio environment. When BSC sends the PS HANDOVER
COMMAND message to MS, if the handover is optimized handover, then the counter
Figure 77-12 Measurement Point of Number of optimised handover executions
77-10

Unit
Times
77.11 C901890010 Number of successful optimised

handovers
Statistics object
Cell
Description
This counter counts the number of optimized handovers initiated by MS in the source
cell. This counter is used to find out the number of successful optimized handovers in the
source cell. It helps study the optimized handover condition. If the handover is of optimized
handover mode, then, after the new cell receives the first correct RLC/MAC block, the
PS HANDOVER COMPLETE message is sent to SGSN, and the optimized handover
complete command (PS_OPTHO_END) is sent to the source cell. Then, the source cell
considers that the handover succeeds, and the counter increments. The measurement
Figure 77-13 Measurement Point of Number of successful optimised handovers
Unit
Times
77-11


handover out attempts
Statistics object
Cell
Description
This counter counts the number of intra-BSC inter-cell outgoing handover attempts initiated
by MS in the source cell. This counter is used to find out the frequency of the intra-BSC
inter-cell outgoing handover attempt initiated by MS in the source cell. It is one of the
parameters that evaluate the radio environment. When user plane receives the handover
decision PSHO_PSCmd from control plane, if it requires to initiate intra-BSC inter-cell
77-14.
Figure 77-14 Measurement Point of Number of Intra-BSC inter-cell outgoing handover

attempts
Unit
Times

handover out executions
Statistics object
Cell
Description
This counter counts the number of intra-BSC inter-cell outgoing handover executions
initiated by MS in the source cell. This counter is used to find out the frequency of the
77-12

intra-BSC inter-cell outgoing handover execution initiated by MS in the source cell. It is

one of the parameters that evaluate the radio environment. When BSC sends the PS
HANDOVER COMMAND message to MS, if the handover is intra-BSC inter-cell outgoing
77-15.
Figure 77-15 Measurement Point of Number of Intra-BSC inter-cell outgoing handover

executions
Unit
Times
77.14 C901890013 Number of successful Intra-BSC

inter-cell handover out
Statistics object
Cell
Description
This counter counts the number of successful intra-BSC inter-cell outgoing handovers
initiated by MS in the source cell. This counter is used to find out the number of successful
intra-BSC inter-cell outgoing handovers initiated by MS in the source cell. It helps
study the intra-BSC inter-cell outgoing handover condition. If the handover is intra-BSC
inter-cell handover and is of normal handover mode, then, after the new cell receives
the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is sent to
SGSN, and SGSN sends the DELETE BSS PFC message to notify the source cell to
release radio resource. When the source cell receives the DELETE BSS PFC message, it
indicates that the handover is completed, and the counter increments. The measurement
If the handover is intra-BSC inter-cell handover and is of optimized handover mode,
then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER
in Figure 77-17.
77-13

Figure 77-16 Measurement Point of Number of successful Intra-BSC inter-cell outgoing

handovers - (1)
Figure 77-17 Measurement Point of Number of successful Intra-BSC inter-cell outgoing

handovers - (2)
Unit
Times
77.15 C901890014 Number of Inter-BSC handover out

attempts
Statistics object
BSC
Description
This counter counts the number of inter-BSC outgoing handover attempts initiated by MS
in the source cell. This counter is used to find out the frequency of the inter-BSC outgoing
77-14

handover attempt initiated by MS in the source cell. It is one of the parameters that evaluate
the radio environment. When user plane receives the handover decision PSHO_PSCmd
from control plane, if it requires to initiate inter-BSC handover, then the counter increments.
Figure 77-18 Measurement Point of Number of Inter-BSC outgoing handover attempts
Unit
Times
77.16 C901890015 Number of Inter-BSC handover out

executions
Statistics object
BSC
Description
This counter counts the number of inter-BSC outgoing handover executions initiated by
MS in the source cell. This counter is used to find out the frequency of the inter-BSC
outgoing handover execution initiated by MS in the source cell. It is one of the parameters
that evaluate the radio environment. When BSC sends the PS HANDOVER COMMAND
message to MS, if the handover is inter-BSC handover, then the counter increments. The
77-15

Figure 77-19 Measurement Point of Number of Inter-BSC outgoing handover executions
Unit
Times
77.17 C901890016 Number of successful Inter-BSC

handover out
Statistics object
BSC
Description
This counter counts the number of successful inter-BSC handovers. This counter is used
to find out the frequency of the successful inter-BSC handover initiated by MS in the
source cell. It is one of the parameters that evaluate the radio environment. When the
source BSC receives the DELETE BSS PFC message from SGSN, it indicates that the
handover is completed, if the handover is inter-BSC handover, the counter increments.
Figure 77-20 Measurement Point of Number of successful Inter-BSC outgoing

handovers
Unit
Times
77-16

77.18 C901890017 Number of handover in attempts

Statistics object
BSC
Description
This counter counts the number of inter-cell incoming handover attempts initiated by MS
towards the destination cell. This counter is used to find out the frequency of inter-cell
incoming handover attempt initiated by MS. It is one of the parameters that evaluate the
radio environment. When the destination BSC receives the SGSN handover request,
it indicates that the resource request succeeds, and the counter increments. The
Figure 77-21 Measurement Point of Number of incoming handover attempts
Unit
Times
77.19 C901890018 Number of handover in executions

Statistics object
BSC
Description
This counter counts the number of BSC-controlled inter-cell incoming handover executions
initiated by MS towards the destination cell. This counter is used to find out the frequency
of BSC-controlled inter-cell incoming handover attempt initiated by MS. It is one of the
parameters that evaluate the radio environment. When the destination BSC receives the
SGSN handover request, it indicates that the resource request succeeds, and the counter
77-17

Figure 77-22 Measurement Point of Number of incoming handover executions
Unit
Times
77.20 C901890019 Number of successful handover in

Statistics object
BSC
Description
This counter counts the number of successful BSC-controlled inter-cell incoming
handovers initiated by MS towards the destination cell. This counter is used to find out the
frequency of successful BSC-controlled inter-cell incoming handover initiated by MS. It is
one of the parameters that evaluate the radio environment. When the destination BSC
receives the first correct RLC/MAC block from MS, it sends the PS handover completion
message to SGSN, and the counter increments. The measurement point is A, as shown
in Figure 77-23.
Figure 77-23 Measurement Point of Number of successful incoming handovers
77-18

Unit
Times

attempts
Statistics object
Cell
Description
This counter counts the number of intra-cell handover attempts. This counter is used
to find out the frequency of intra-cell handover attempt initiated by MS. It is one of the
parameters that evaluate the radio environment. When BSC receives the measurement
report from MS, it performs handover decision. If the handover decision indicates that
intra-cell handover is required, the counter increments. The measurement point is A, as
Figure 77-24 Measurement Point of Number of Intra-cell handover attempts
Unit
Times
77.22 C901890021 Number of Intra-Cell handover

executions
Statistics object
Cell
77-19

Description
This counter counts the number of intra-cell handover executions initiated by MS. This
counter is used to find out the frequency of intra-cell handover execution initiated by MS.
It is one of the parameters that evaluate the radio environment. After the MAC module in
BSC requests for resource successfully or unsuccessfully, the counter increments.
Unit
Times
77.23 C901890022 Number of successful Intra-cell

handovers
Statistics object
Cell
Description
This counter counts the number of successful intra-cell handovers initiated by MS. This
counter is used to find out the frequency of intra-cell handover executions initiated by MS.
It is one of the parameters that evaluate the radio environment. After the MAC module in
BSC requests for resource successfully, the counter increments.
Unit
Times
77.24 C901890023 Number of invalid Intra-cell

handovers
Statistics object
Cell
Description
This counter counts the number of failed intra-cell handovers initiated by MS. This counter
is used to find out the frequency of intra-cell handover executions initiated by MS. It is one
of the parameters that evaluate the radio environment. After the MAC module in BSC fails
to request for resource, the counter increments.
Unit
Times
77-20

77.25 C901890024 Number of 2G to FDD handover

attempts
Statistics object
BSC
Description
This counter counts the number of 2G-to-FDD handover attempts initiated by MS. This
counter is used to find out the frequency of handover attempt from 2G cell to FDD cell
initiated by MS. It is one of the parameters that evaluate the radio environment. When the
source BSC receives the measurement report from MS, it performs handover decision.
According to the decision result, if the handover is FDD handover, the counter increments.
Figure 77-25 Measurement Point of Number of 2G to FDD handover attempts
Unit
Times
77.26 C901890025 Number of 2G to FDD handover

executions
Statistics object
BSC
Description
This counter counts the number of 2G-to-FDD handover executions initiated by MS. This
counter is used to find out the frequency of handover execution from 2G cell to FDD cell
initiated by MS. It is one of the parameters that evaluate the radio environment. When
the source BSC receives the handover request response message issued by SGSN, it
77-21

forms the PS HANDOVER COMMAND message at Um interface and sends it to MS. If

the handover is FDD handover, the counter increments. The measurement point is A, as
Figure 77-26 Measurement Point of Number of 2G to FDD handover executions
Unit
Times
77.27 C901890026 Number of successful 2G to FDD

handovers
Statistics object
BSC
Description
This counter counts the number of successful 2G-to-FDD handovers initiated by MS. This
counter is used to find out the frequency of successful handover from 2G cell to FDD cell
handover is completed, if the handover is FDD handover, the counter increments. The
77-22

Figure 77-27 Measurement Point of Number of successful 2G to FDD handovers
Unit
Times
77.28 C901890027 Number of 2G to TDD handover

attempts
Statistics object
BSC
Description
This counter counts the number of 2G-to-TDD handover attempts initiated by MS. This
counter is used to find out the frequency of handover attempt from 2G cell to TDD cell
source BSC receives the measurement report from MS, it performs handover decision.
According to the decision result, if the handover is TDD handover, the counter increments.
Figure 77-28 Measurement Point of Number of 2G to TDD handover attempts
77-23

Unit
Times
77.29 C901890028 Number of 2G to TDD handover

executions
Statistics object
BSC
Description
This counter counts the number of 2G-to-TDD handover executions initiated by MS. This
counter is used to find out the frequency of handover execution from 2G cell to TDD cell
initiated by MS. It is one of the parameters that evaluate the radio environment. When
the source BSC receives the handover request response message issued by SGSN, it
forms the PS HANDOVER COMMAND message at Um interface and sends it to MS. If
the handover is TDD handover, the counter increments. The measurement point is A, as
Figure 77-29 Measurement Point of Number of 2G to TDD handover executions
Unit
Times
77.30 C901890029 Number of successful 2G to TDD

handovers
Statistics object
BSC
77-24

Description
This counter counts the number of successful 2G-to-TDD handovers initiated by MS. This
counter is used to find out the frequency of successful handover from 2G cell to TDD cell
handover is completed, if the handover is TDD handover, the counter increments. The
Figure 77-30 Measurement Point of Number of successful 2G to TDD handovers
Unit
Times
77.31 C901890030 Number of 3G to 2G handover

attempts
Statistics object
BSC
Description
This counter counts the number of 3G-to-2G outgoing handover attempts initiated by MS.
This counter is used to find out the frequency of 3G-to-2G handover attempt initiated by MS.
It is one of the parameters that evaluate the radio environment. When the destination BSC
receives the resource assignment, if the access cell is 3G cell, the counter increments. The
77-25

Figure 77-31 Measurement Point of Number of 3G to 2G handover attempts
Unit
Times
77.32 C901890031 Number of 3G to 2G handover

executions
Statistics object
BSC
Description
This counter counts the number of 3G-to-2G outgoing handover executions initiated by
MS. This counter is used to find out the frequency of 3G-to-2G handover execution initiated
by MS. It is one of the parameters that evaluate the radio environment. When the 2G cell
receives the handover request message issued by SGSN, the counter increments when
the following conditions are satisfied: The cell is allocated with channel and the channel is
activated, and the source cell is 3G cell. The measurement point is A, as shown in Figure
77-32.
Figure 77-32 Measurement Point of Number of 3G to 2G handover executions
77-26

Unit
Times
77.33 C901890032 Number of successful 3G to 2G

handovers
Statistics object
BSC
Description
This counter counts the number of successful 3G-to-2G incoming handovers initiated
by MS. This counter is used to find out the frequency of successful 3G-to-2G handover
initiated by MS. It is one of the parameters that evaluate the radio environment.
When the 2G cell receives the handover completion message, if the request is due to
SGSN-controlled inter-BSC incoming handover and the source cell is 3G cell, the counter
Figure 77-33 Measurement Point of Number of successful 3G to 2G handovers
Unit
Times
77.34 C901890033 Number of T12 expiry

Statistics object
BSC
Description
This counter counts the number of T12 being timeout. This counter is used to find out the
frequency of handover failure due to T12 timeout. When T12 is timeout, the MAC instance
in the source cell considers that the handover fails, it records the destination cell of the
failed handover and clears the handover flag. If T12 is timeout before BSC disables it, the
77-27

Figure 77-34 Measurement Point of Number of T12 expiry
Unit
Times
77.35 C901890034 Number of PCCF received

Statistics object
BSC
Description
This counter counts the number of the Packet Cell Change Failure messages received.
When handover fails, MS returns to the original cell and sends the Packet Cell Change
Failure message to BSC, and BSC sends the PS Handover Cancel message to SGSN.
When BSC receives the Packet Cell Change Failure message from MS, the counter
Figure 77-35 Measurement Point of Number of PCCF received
Unit
Times
77-28

77.36 C901890035 Number of PS-HANDOVER-REQUI

RED-NACK messages received with cause Create
PFC Failure
Statistics object
BSC
Description
This counter counts the number of received PS Handover Required Nack messages with
the cause "Create PFC Failure". This counter is used to find out the frequency of handover
failure due to "Create PFC Failure". When BSC receives the PS Handover Required Nack
message from SGSN with the cause of "Create PFC Failure", the counter increments. The

messages received with cause Create PFC Failure
Unit
Times
77.37 C901890036 Number of PS-HANDOVER-REQU

IRED-NACK messages received with cause PS
Handover Target not allowed
Statistics object
BSC
Description
the cause "PS Handover Target not allowed". This counter is used to find out the frequency
of handover failure due to "PS Handover Target not allowed". When BSC receives the PS
77-29

Handover Required Nack message from SGSN with the cause of "PS Handover Target not
allowed", the counter increments. The measurement point is A, as shown in Figure 77-37.

messages received with cause PS Handover Target not allowed
Unit
Times
77.38 C901890037 Number of PS-HANDOVER-REQU

IRED-NACK messages received with cause PS
Handover not Supported in Target BSS or Target
System
Statistics object
BSC
Description
the cause "PS Handover not Supported in Target BSS or Target System". This counter
is used to find out the frequency of handover failure due to "PS Handover not Supported
in Target BSS or Target System". When BSC receives the PS Handover Required Nack
message from SGSN with the cause of "PS Handover not Supported in Target BSS or
Target System", the counter increments. The measurement point is A, as shown in Figure
77-38.
77-30


messages received with cause PS Handover not Supported in Target BSS or Target
System
Unit
Times
77.39 C901890038 Number of PS-HANDOVER-REQUI

RED-NACK messages received with cause other
reasons
Statistics object
BSC
Description
This counter counts the number of received PS Handover Required Nack messages
with the cause of other reasons. This counter is used to find out the frequency of
handover failure due to other reasons. When BSC receives the PS Handover Required
Nack message from SGSN, which is not due to the cause of "Create PFC Failure", "PS
Handover Target not allowed", or "PS Handover not Supported in Target BSS or Target
System", the counter increments. The measurement point is A, as shown in Figure 77-39.

messages received with cause other reasons
77-31

Unit
Times
77.40 C901890039 Number of failure in optimised

handover due to failure alloc resource
Statistics object
BSC
Description
This counter counts the number of handover failure due to resource allocation failure in
the optimized handover mode. This counter is used to find out the frequency of handover
failure due to resource allocation failure in the optimized handover mode. If RANUMC
fails to create MS or RANPS instance, the counter increments. Then, RANUMC sends the
EV_RANU_PS_OPTHO_ACK message to the RANUHPMU module in the source cell, and
the resource allocation result is written as resource allocation failure in the message. The
Figure 77-40 Measurement Point of Number of failure in optimised handover due to

resource allcoation failure
Unit
Times
77-32

77.41 C901890040 Number of failure in optimised

handover due to PS handover not supported in
target cell
Statistics object
BSC
Description
This counter counts the number of handover failures due to that PS handover is not
supported in the destination cell in the optimized handover mode. This counter is
used to find out the frequency of handover failure due to PS handover not supported
in destination cell in the optimized handover mode. When RANPS queries that the
cell does not support PS handover, the counter increments. Then, RANPS sends the
EV_RANU_PS_OPTHO_ACK message to the RANUHPMU module in the source cell,
the resource allocation result is written as destination cell not supporting PS handover in
the message, and RANPS instance is released. The measurement point is A, as shown
in Figure 77-41.
Figure 77-41 Measurement Point of Number of failure in optimized handover due to PS handover
not supported in target cell
77-33

Unit
Times
77-34

Chapter 78
IURG Measurement
Table of Contents
Overview ..................................................................................................................78-1
C901900001 Number of relocation requests (on Iur-g) .............................................78-1
C901900002 Number of relocation executions (on Iur-g) ..........................................78-2
C901900003 Number of relocation successes (on Iur-g) ..........................................78-4
C901900004 Number of relocation failures due to no valid radio resource (on Iur-g) .78-5
C901900005 Number of relocation failures due to no valid terrestrial circuit
resource (on Iur-g)....................................................................................................78-6
C901900006 Number of relocation failures due to loss of UE handover complete
message (on Iur-g) ...................................................................................................78-7
C901900007 Number of relocation failures due to MS returning to original channel
(on Iur-g) ..................................................................................................................78-8
C901900008 Number of relocation failures due to other causes (on Iur-g)................78-9
78.1 Overview
IURG measurement counters measure performance and status of 2G/3G handover service
implemented through Iur-g interface, such as relocation requests received at Iur-g interface
and handover failure causes.
78.2 C901900001 Number of relocation requests (on

Iur-g)
Statistics object
BSC
Description
This counter counts the number of ENHANCED RELOCATION RESOURCE REQUEST
messages received by BSC at Iur-g interface from RNC. The measurement point is A1, as
shown in Figure 78-1. (DBS is the database subsystem of BSC software)
78-1

Figure 78-1 Measurement Point of Relocation (on Iur-g)
Unit
Times
78.3 C901900002 Number of relocation executions (on

Iur-g)
Statistics object
BSC
78-2

Chapter 78 IURG Measurement
Description
After the radio resource is obtained, the handover relocation acknowledgement message
is sent to the opposite end through Iur-g interface. The measurement point is A2, as shown
in Figure 78-2. (DBS is the database subsystem of BSC software)
Unit
Times
78-3

78.4 C901900003 Number of relocation successes (on

Iur-g)
Statistics object
BSC
Description
Connect the link with the core nework and send the handover completion message
successfully to the core network. The measurement point is A3, as shown in Figure 78-3.
(DBS is the database subsystem of BSC software)
78-4

Unit
Times
78.5 C901900004 Number of relocation failures due to

no valid radio resource (on Iur-g)
Statistics object
BSC
78-5

Description
Radio resource request fails. The measurement point is A4, as shown in Figure 78-4.
(DBS is the database subsystem of BSC software)
Figure 78-4 Measurement Point of Number of relocation failures due to no valid radio
resource (on Iur-g)
Unit
Times

no valid terrestrial circuit resource (on Iur-g)
Statistics object
BSC
Description
The terrestrial circuit allocated at A-interface is unavailable. The measurement point is A5,
as shown in Figure 78-5. (DBS is the database subsystem of BSC software)
78-6

Figure 78-5 Measurement Point of Number of relocation failures due to no valid terrestrial circuit
resource (on Iur-g)
Unit
Times

loss of UE handover complete message (on Iur-g)
Statistics object
BSC
Description
Time expires but the handover completion message that indicates MS accesses the
network is not received. The measurement point is A6, as shown in Figure 78-6. (DBS is
the database subsystem of BSC software)
78-7

Figure 78-6 Measurement Point of Number of relocation failures due to loss of UE handover
complete message (on Iur-g)
Unit
Times

MS returning to original channel (on Iur-g)
Statistics object
BSC
Description
BSC receives the handover relocation response message at Iur-g interface, indicating that
MS returns to the original channel. The measurement point is A7, as shown in Figure 78-7.
78-8

(The figure omits the intermediate process, and it only describes the following process:
RNC initiates handover relocation, UE returns to the original channel, and RNC notifies
BSC to release resource.)
Figure 78-7 Measurement Point of Number of relocation failures due to MS returning to

original channel (on Iur-g)
Unit
Times

other causes (on Iur-g)
Statistics object
BSC
Description
Time expires but the handover request or access failure message is not received from the
core network. This counter counts handover failure causes except for those counted by
C901900004 ~ C901900007.
Unit
Times
78-9

78-10

Chapter 79
RTCP Measurement
Table of Contents
Overview ..................................................................................................................79-1
C901910001 local jitter (CS).....................................................................................79-1
C901910002 distant jitter (CS) .................................................................................79-2
C901910003 average one-way delay (CS) ...............................................................79-3
C901910004 maximal one-way delay (CS)...............................................................79-5
C901910005 local cumulative fraction lost (CS)........................................................79-6
C901910006 distant cumulative fraction lost (CS) ....................................................79-7
C901910007 local jitter (PS).....................................................................................79-9
C901910008 distant jitter (PS)................................................................................79-10
C901910009 average one-way delay (PS) ............................................................. 79-11
C901910010 maximal one-way delay (PS) .............................................................79-13
C901910011 local cumulative fraction lost (PS) ......................................................79-14
C901910012 distant cumulative fraction lost (PS)...................................................79-15
79.1 Overview
RTCP measurement collects IP QoS data by directly extracting the realtime monitoring
data of RTP stream. This measurement counts atomic values such as jitter, packet loss,
and accumulated packet loss, at the local end and the opposite end in CS stream and PS
stream.
79.2 C901910001 local jitter (CS)

Statistics object
CELL
Description
This parameter is calculated by IPRB at BSC. Suppose Si is the time stamp of RTP packet
i, and Ri is the local clock time when the packet arrives the local end, then, the relative
transmission time of the two RTP packets i and j received at the local end is:
Relative transmission time = The receiver's clock time when RTP packet arrives - RTP
packet's RTP time stamp
Relative transmission time difference D(j, i) = (Rj - Sj) - (Ri - Si)
79-1

Jitter calculation formula: J(i) = J(i - 1) + (|D(i-1, i)| - J(i - 1))/16

Oms_SlaProc accumulates the value within the statistics granularity. When the statistics
granularity expires, divide the accumulated value by the number of times of the parameter
being received, and fill the average value in the reported data area.
The counter's working flow is shown in Figure 79-1.
Figure 79-1 Measurement Point of local jitter (CS)
Unit
ms
79.3 C901910002 distant jitter (CS)

Statistics object
CELL
Description
This parameter's value is directly extracted from the RTCP SR packet sent from BTS,
saved in IPRB, and reported to Host.
79-2

Chapter 79 RTCP Measurement
Figure 79-2 Measurement Point of local jitter (CS)
Unit
ms
79.4 C901910003 average one-way delay (CS)

Statistics object
CELL
Description
This parameter is calculated by IPRB. Its physical meaning is the delay between the RTP
packet being sent and being received at the opposite end, the calculation formula is: delay
= (Current time - Previous time - DLSR)/2
79-3

Where, Current time and Previous time are obtained from the local clock; Previous time is
the time when SR packet is sent from the local end, Current time is the time when the next
SR packet is received; DLSR is extracted from the SR packet sent from BTS.
Figure 79-3 Measurement Point of average one-way delay (CS)
79-4

Unit
ms
79.5 C901910004 maximal one-way delay (CS)

Statistics object
CELL
Description
Oms_SlaProc records the parameter's peak value within the statistics granularity. When
the statistics granularity expires, fill the peak value in the reported data area.
79-5

Figure 79-4 Measurement Point of maximal one-way delay (CS)
Unit
ms
79.6 C901910005 local cumulative fraction lost (CS)

Statistics object
CELL
Description
udLocalTotalRcvCnt: Number of accumulatively received packets at the local end within
the report interval (the report interval is 5 s in this system)
This parameter is calculated by IPRB. IPRB accumulates the number of received RTP
packets in uplink, when the report interval expires, subtract the number of received packets
5 s ago from the current number of received packets to calculate the parameter's value.
udLocalIntervalLossCnt: Number of accumulatively lost packets at the local end within the
report interval
This parameter is calculated by IPRB. The number of accumulatively lost packets at the
local end is calculated by subtracting the number of actually received packets from the
number of expected received packets. The number of accumulatively lost packets at the
79-6

local end within the report interval is calculated by subtracting the number of lost packets
5 s ago from the current number of accumulatively lost packets at the local end.
Oms_SlaProc accumulates the two parameters respectively within the statistics
granularity, and marks the two values as udRcv and udLoss. The counter's value is
calculated according to the following formula:
If (udRcv + udLoss == 0) C901910005 = 0;
else C901910005 = 10000 udLoss/(udRcv + udLoss)
Figure 79-5 Measurement Point of local cumulative fraction lost (CS)
Unit

79.7 C901910006 distant cumulative fraction lost (CS)

Statistics object
CELL
79-7

Description
report interval
If (udRcv + udLoss == 0) C901910006 = 0;
Figure 79-6 Measurement Point of distant cumulative fraction lost (CS)
79-8

Unit

79.8 C901910007 local jitter (PS)

Statistics object
CELL
Description
This parameter is calculated by IPRB at BSC. Suppose Si is the time stamp of RTP packet
i, and Ri is the local clock time when the packet arrives the local end, then, the relative
transmission time of the two RTP packets i and j received at the local end is:
Relative transmission time = The receiver's clock time when RTP packet arrives - RTP
packet's RTP time stamp
Relative transmission time difference D(j, i) = (Rj - Sj) - (Ri - Si)
Jitter calculation formula: J(i) = J(i - 1) + (|D(i-1, i)| - J(i - 1))/16
79-9

Figure 79-7 Measurement Point of local jitter (PS)
Unit
ms
79.9 C901910008 distant jitter (PS)

Statistics object
CELL
Description
This parameter's value is directly extracted from the RTCP SR packet sent from BTS,
saved in IPRB, and reported to Host.
79-10

Figure 79-8 Measurement Point of distant jitter (PS)
Unit
ms
79.10 C901910009 average one-way delay (PS)

Statistics object
CELL
Description
79-11

Figure 79-9 Measurement Point of average one-way delay (PS)
79-12

Unit
ms
79.11 C901910010 maximal one-way delay (PS)

Statistics object
CELL
Description
Oms_SlaProc records the parameter's peak value within the statistics granularity. When
the statistics granularity expires, fill the peak value in the reported data area.
79-13

Figure 79-10 Measurement Point of maximal one-way delay (PS)
Unit
ms
79.12 C901910011 local cumulative fraction lost (PS)

Statistics object
CELL
Description
report interval
79-14

If (udRcv + udLoss == 0) C901910011 = 0;
Figure 79-11 Measurement Point of local cumulative fraction lost (PS)
Unit

79.13 C901910012 distant cumulative fraction lost (PS)

Statistics object
CELL
79-15

Description
udDistantIntervalLossCnt: Number of accumulatively lost packets at the opposite end
within the report interval
IPRB extracts the number of accumulatively lost packets in downlink from SR packet sent
from BTS. When the report interval expires, subtract the number of lost packets 5 s ago
from the current number of accumulatively lost packets to calculate the parameter's value.
udDistantTotalRcvCnt: Number of accumulatively received packets at the opposite end
within the report interval
This parameter is calculated by IPRB through subtracting the number of lost packets at
the opposite end within 5 s from the number of sent packets at the local end within 5 s.
If (udRcv + udLoss == 0) C901910012 = 0;
Figure 79-12 Measurement Point of distant cumulative fraction lost (PS)
Unit

79-16

Chapter 80
DSP Measurement
Table of Contents
Overview ..................................................................................................................80-1
C901920001 the times of loss of TRAU frame synchronization in BIPB ....................80-1
80.1 Overview
TRAU frame refers to the data frame sent from BTS to BSC.
This data frame comprises of serial data, including the synchronization header that is easy
to search for. After BIPB receives this data frame, BIPB searches according to specific
synchronization header. If BIPB fails to search out the header, it is considered as out of
frame. If the number of TRAU frames that are out of frame reaches the set value, the event
of loss of TRAU frame synchronization is reported, which triggers relevant link release
process.
Statistic unit in this measurement is times.
80.2 C901920001 the times of loss of TRAU frame

synchronization in BIPB
Description
This counter counts the number of loss of TRAU frame synchronization detected by BIPB.
This counter increments if the number of loss of TRAU frame synchronization header
reaches the sett value.
Usage
The counter is used to find out the frequency of search failure of TRAU frame
synchronization header.
Measurement Point
BSC searches the synchronization header after receiving the TRAU frame sent by BTS.
80-1

Figure 80-1 Measurement Point of the times of loss of TRAU frame synchronization in
BIPB
Unit
Second
80-2

Chapter 81
Access Control Measurement
Table of Contents
Overview ..................................................................................................................81-1
C901930001 Number of CS Call Denied for Lack of IPAbis BandWidth UpLink ........81-1
C901930002 Number of CS Call Denied for Lack of IPAbis BandWidth DownLink....81-2
C901930003 Number of PS Call Denied for Lack of IPAbis BandWidth UpLink ........81-3
C901930004 Number of PS Call Denied for Lack of IPAbis BandWidth DownLink ....81-3
81.1 Overview
Access control measurement counters counts the number of service access failure due to
insufficient uplink/downlink Abis bandwidth during the service process in IP transmission
mode.
Statistic unit in this measurement is IP bandwidth resource pool.
81.2 C901930001 Number of CS Call Denied for Lack of

IPAbis BandWidth UpLink
Statistics object
IPAbisPool
Description
This counter counts the number of CS service access being rejected due to insufficient
uplink Abis bandwidth. It reflects whether the uplink bandwidth of IP bandwidth resource
pool, which is related to Abis interface transmission, is appropriate. After BSC receives the
resource request from MS, it will allocate resource for MS. If CS service access is rejected
due to insufficient uplink Abis bandwidth, the counter increments. The measurement point
81-1

Figure 81-1 Measurement Point of Number of CS Call Denied for Lack of IPAbis
BandWidth UpLink
Unit
Times
81.3 C901930002 Number of CS Call Denied for Lack of

IPAbis BandWidth DownLink
Statistics object
IPAbisPool
Description
This counter counts the number of CS service access being rejected due to insufficient
downlink Abis bandwidth. It reflects whether the downlink bandwidth of IP bandwidth
resource pool, which is related to Abis interface transmission, is appropriate. After BSC
receives the resource request from MS, it will allocate resource for MS. If CS service
access is rejected due to insufficient downlink Abis bandwidth, the counter increments.
Figure 81-2 Measurement Point of Number of CS Call Denied for Lack of IPAbis
BandWidth DownLink
Unit
Times
81-2

Chapter 81 Access Control Measurement
81.4 C901930003 Number of PS Call Denied for Lack of

IPAbis BandWidth UpLink
Statistics object
IPAbisPool
Description
This counter counts the number of PS service access being rejected due to insufficient
uplink Abis bandwidth. It reflects whether the uplink bandwidth of IP bandwidth resource
pool, which is related to Abis interface transmission, is appropriate. After BSC receives the
resource request from MS, it will allocate resource for MS. If PS service access is rejected
due to insufficient uplink Abis bandwidth, the counter increments. The measurement point
Figure 81-3 Measurement Point of Number of PS Call Denied for Lack of IPAbis
BandWidth UpLink
Unit
Times
81.5 C901930004 Number of PS Call Denied for Lack of

IPAbis BandWidth DownLink
Statistics object
IPAbisPool
Description
This counter counts the number of PS service access being rejected due to insufficient
downlink Abis bandwidth. It reflects whether the downlink bandwidth of IP bandwidth
resource pool, which is related to Abis interface transmission, is appropriate. After BSC
receives the resource request from MS, it will allocate resource for MS. If PS service
access is rejected due to insufficient downlink Abis bandwidth, the counter increments.
81-3

Figure 81-4 Measurement Point of Number of PS Call Denied for Lack of IPAbis
BandWidth DownLink
Unit
Times
81-4

Chapter 82
PS Adjacent Cell Handover
Measurement
Table of Contents
Overview ..................................................................................................................82-2
C901950001 Number of handover attempts on the adjacent cell ..............................82-2
C901950002 Number of successful handovers from selected cell to the adjacent
cell ...........................................................................................................................82-3
C901950003 Number of handover attempts from adjacent cell to the selected cell...82-4
C901950004 Number of successful handovers from adjacent cell to the selected
cell ...........................................................................................................................82-5
due to better uplink quality........................................................................................82-6
due to better downlink quality ...................................................................................82-7
cell due to better uplink quality .................................................................................82-9
cell due to better downlink quality ...........................................................................82-10
due to better uplink strength ................................................................................... 82-11
due to better downlink strength...............................................................................82-12
cell due to better uplink strength .............................................................................82-13
cell due to better downlink strength ........................................................................82-14
due to PBGT ..........................................................................................................82-16
cell due to PBGT ....................................................................................................82-17
due to large TA.......................................................................................................82-18
due to large TA.......................................................................................................82-19
due to high traffic....................................................................................................82-20
82-1

due to high traffic....................................................................................................82-21
82.1 Overview
Counters of PS adjacent cell handover measurement counts the number of MS's
performing outgoing handover towards specific adjacent cell and the number of MS's
performing incoming handover from specific adjacent cell. It reflects the PS handover
condition between the local cell and adjacent cells and helps improve adjacent cell
planning, thereby improves the PS service in cells through PS handover.
82.2 C901950001 Number of handover attempts on the

adjacent cell
Statistics object
Cell
Description
This counter counts the number of MS's outgoing handover attempts from the local cell
to a specific cell. This counter is used to find out the number of MS's outgoing handover
attempts from the local cell to a specific cell. It helps check the direction of handover
between cells.
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,
Figure 82-1 Measurement Point of Number of handover attempts on the adjacent cell
- (1)
For SGSN-controlled external handover, the counter increments when the source cell
sends the handover request message to SGSN. The measurement point is A, as shown
in Figure 82-2.
82-2

Chapter 82 PS Adjacent Cell Handover Measurement
Figure 82-2 Measurement Point of Number of handover attempts on the adjacent cell
- (2)
Unit
Times
82.3 C901950002 Number of successful handovers

from selected cell to the adjacent cell
Statistics object
Cell
Description
This counter counts the number of MS's successful outgoing handovers from the local cell
to a specific cell. This counter is used to find out the number of MS's successful outgoing
handovers from the local cell to a specific cell. It helps check the direction of handover
between cells.
For BSC-controlled inter-cell handover, the counter increments when the source cell
receives the handover completion message from the destination cell. The measurement
Figure 82-3 Measurement Point of Number of successful handovers from selected cell
to the adjacent cell - (1)
82-3

For SGSN-controlled external handover, when the source cell receives the release
command issued by SGSN and if the release is due to handover success, then the
to the adjacent cell - (2)
Unit
Times

adjacent cell to the selected cell
Statistics object
Cell
Description
This counter counts the number of MS's incoming handover attempts from a specific cell
to the local cell. This counter is used to find out the number of MS's incoming handover
attempts from a specific cell to the local cell. It helps check the direction of handover
between cells.
For BSC-controlled inter-cell handover, the counter increments when the destination cell
receives the radio channel request message from the source cell. The measurement point
82-4

Figure 82-5 Measurement Point of Number of handover attempts from adjacent cell
to the selected cell - (1)
For SGSN-controlled external handover, the counter increments when the destination cell
receives the handover request message from SGSN. The measurement point is A, as
Figure 82-6 Measurement Point of Number of handover attempts from adjacent cell
Unit
Times

from adjacent cell to the selected cell
Statistics object
Cell
Description
This counter counts the number of MS's successful incoming handovers from a specific cell
to the local cell. This counter is used to find out the number of MS's successful incoming
handovers from a specific cell to the local cell. It helps check the direction of handover
between cells.
82-5

For BSC-controlled inter-cell handover, the counter increments when the destination cell
receives the handover completion message from MS. The measurement point is A, as
Figure 82-7 Measurement Point of Number of successful handovers from adjacent cell
For SGSN-controlled external handover, the counter increments when the destination cell
receives the handover completion message from MS. The measurement point is A, as
Figure 82-8 Measurement Point of Number of successful handovers from adjacent cell
Unit
Times

selected cell to the adjacent cell due to better
uplink quality
Statistics object
Cell
Description
This counter counts the number of MS's outgoing handover attempts from the local cell to
a specific cell due to uplink qulaity. This counter is used to find out the number of MS's
82-6

outgoing handover attempts from the local cell to a specific cell due to uplink quality. It
helps check the direction of handover between cells.
For BSC-controlled inter-cell handover, when the destination cell receives the radio
channel request message from the source cell, if the handover is due to uplink quality, the
Figure 82-9 Measurement Point of Number of handover attempts from selected cell to
the adjacent cell due to better uplink quality - (1)
For SGSN-controlled external handover, when the destination cell receives the handover
request message from SGSN, if the handover is due to uplink quality, the counter
the adjacent cell due to better uplink quality - (2)
Unit
Times

downlink quality
Statistics object
Cell
82-7

Description
a specific cell due to downlink qulaity. This counter is used to find out the number of MS's
outgoing handover attempts from the local cell to a specific cell due to downlink quality. It
channel request message from the source cell, if the handover is due to downlink quality,
Figure 82-11 Measurement Point of Number of handover attempts from selected cell
to the adjacent cell due to better downlink quality - (1)
request message from SGSN, if the handover is due to downlink quality, the counter
Unit
Times
82-8


from selected cell to the adjacent cell due to better
uplink quality
Statistics object
Cell
Description
to a specific cell due to uplink qulaity. This counter is used to find out the number of MS's
successful outgoing handovers from the local cell to a specific cell due to uplink quality. It
For BSC-controlled inter-cell handover, when the source cell receives the handover
completion message from the destination cell, if the handover is due to uplink quality, the
Figure 82-13 Measurement Point of Number of successful handovers from selected

cell to the adjacent cell due to better uplink quality - (1)
command issued by SGSN, if the release is due to handover success and the handover
is due to uplink quality, the counter increments. The measurement point is A, as shown in
Figure 82-14.

cell to the adjacent cell due to better uplink quality - (2)
82-9

Unit
Times

downlink quality
Statistics object
Cell
Description
to a specific cell due to downlink qulaity. This counter is used to find out the number of
MS's successful outgoing handovers from the local cell to a specific cell due to downlink
quality. It helps check the direction of handover between cells.
completion message from the destination cell, if the handover is due to downlink quality,
command issued by SGSN, if the release is due to handover success and the handover is
due to downlink quality, the counter increments. The measurement point is A, as shown
in Figure 82-16.
82-10

Unit
Times

uplink strength
Statistics object
Cell
Description
a specific cell due to uplink strength. This counter is used to find out the number of MS's
outgoing handover attempts from the local cell to a specific cell due to uplink strength. It
channel request message from the source cell, if the handover is due to uplink strength,
the adjacent cell due to better uplink strength - (1)
82-11

request message from SGSN, if the handover is due to uplink strength, the counter
the adjacent cell due to better uplink strength - (2)
Unit
Times

downlink strength
Statistics object
Cell
Description
a specific cell due to downlink strength. This counter is used to find out the number of MS's
outgoing handover attempts from the local cell to a specific cell due to downlink strength.
It helps check the direction of handover between cells.
channel request message from the source cell, if the handover is due to downlink strength,
82-12

the adjacent cell due to better downlink strength - (1)
request message from SGSN, if the handover is due to downlink strength, the counter
the adjacent cell due to better downlink strength - (2)
Unit
Times

uplink strength
Statistics object
Cell
Description
to a specific cell due to uplink strength. This counter is used to find out the number of MS's
successful outgoing handovers from the local cell to a specific cell due to uplink strength.
It helps check the direction of handover between cells.
82-13

completion message from the destination cell, if the handover is due to uplink strength,

cell to the adjacent cell due to better uplink strength - (1)
is due to uplink strength, the counter increments. The measurement point is A, as shown
in Figure 82-22.

cell to the adjacent cell due to better uplink strength - (2)
Unit
Times

downlink strength
Statistics object
Cell
82-14

Description
to a specific cell due to downlink strength. This counter is used to find out the number of
MS's successful outgoing handovers from the local cell to a specific cell due to downlink
strength. It helps check the direction of handover between cells.
completion message from the destination cell, if the handover is due to downlink strength,
to the adjacent cell due to better downlink strength - (1)
is due to downlink strength, the counter increments. The measurement point is A, as
to the adjacent cell due to better downlink strength - (2)
Unit
Times
82-15


Statistics object
Cell
Description
a specific cell due to PBGT. This counter is used to find out the number of MS's outgoing
handover attempts from the local cell to a specific cell due to PBGT. It helps check the
direction of handover between cells.
channel request message from the source cell, if the handover is due to PBGT, the
the adjacent cell due to PBGT - (1)
request message from SGSN, if the handover is due to PBGT, the counter increments.
the adjacent cell due to PBGT - (2)
82-16

Unit
Times

from selected cell to the adjacent cell due to PBGT
Statistics object
Cell
Description
This counter counts the number of MS's successful outgoing handovers from the local
cell to a specific cell due to PBGT. This counter is used to find out the number of MS's
successful outgoing handovers from the local cell to a specific cell due to PBGT. It helps
check the direction of handover between cells.
completion message from the destination cell, if the handover is due to PBGT, the counter

cell to the adjacent cell due to PBGT - (1)
is due to PBGT, the counter increments. The measurement point is A, as shown in Figure
82-28.
82-17


cell to the adjacent cell due to PBGT - (2)
Unit
Times

selected cell to the adjacent cell due to large TA
Statistics object
Cell
Description
This counter counts the number of MS's outgoing handover attempts from the local cell
to a specific cell due to too large TA. This counter is used to find out the number of MS's
outgoing handover attempts from the local cell to a specific cell due to too large TA. It helps
check the direction of handover between cells.
channel request message from the source cell, if the handover is due to too large TA, the
to the adjacent cell due to large TA - (1)
82-18

request message from SGSN, if the handover is due to too large TA, the counter
Unit
Times

from selected cell to the adjacent cell due to large
TA
Statistics object
Cell
Description
to a specific cell due to too large TA. This counter is used to find out the number of MS's
successful outgoing handovers from the local cell to a specific cell due to too large TA. It
completion message from the destination cell, if the handover is due to too large TA, the
82-19

Figure 82-31 Measurement Point of Number of successful handover from selected cell
is due to too large TA, the counter increments. The measurement point is A, as shown in
Figure 82-32.
Unit
Times

selected cell to the adjacent cell due to high traffic
Statistics object
Cell
Description
a specific cell due to too heavy traffic. This counter is used to find out the number of MS's
outgoing handover attempts from the local cell to a specific cell due to too heavy traffic. It
82-20

channel request message from the source cell, if the handover is due to too heavy traffic,
the adjacent cell due to high traffic - (1)
request message from SGSN, if the handover is due to too heavy traffic, the counter
the adjacent cell due to high traffic - (2)
Unit
Times

from selected cell to the adjacent cell due to high
traffic
Statistics object
Cell
82-21

Description
to a specific cell due to too heavy traffic. This counter is used to find out the number of
MS's successful outgoing handovers from the local cell to a specific cell due to too heavy
traffic. It helps check the direction of handover between cells.
completion message from the destination cell, if the handover is due to too heavy traffic,
to the adjacent cell due to high traffic - (1)
command issued by SGSN, if the release is due to handover success and the handover is
due to too heavy traffic, the counter increments. The measurement point is A, as shown
in Figure 82-36.
to the adjacent cell due to high traffic - (2)
Unit
Times
82-22

Appendix A
Corresponding Relationship
between Basic Measurement
Counters and General
Measurement Counters
The ZXG10 iBSC performance statistic measurement at background has two types:
l Basic measurement
l General measurement
The general measurement is performed after the measurement task is created. The basic
measurement is used in daily performance report statistics, and user can output the report
without creating the measurement task.
A basic measurement counter and the corresponding general measurement counter
only differ in the counter ID. The two counters have the same name, description. and
measurement point. Table A-1 lists the corresponding relationship between the two types
of counters.
Table A-1 Corresponding Relationship between Basic Measurement Counters and

General Measurement Counters
Basic Measurement Counter ID Corresponding General Measurement Counter ID
C900040001 C901000007
C900040002 C901000016
C900040003 C901000017
C900040004 C901000018
C900040005 C901000019
C900040006 C901000020
C900040007 C901000021
C900040008 C901000022
C900040009 C901000029
A-1

C900040010 C901000038
C900040011 C901000039
C900040012 C901000040
C900040013 C901000041
C900040014 C901000042
C900040015 C901000043
C900040016 C901000044
C900040017 C901000049
C900040018 C901000051
C900040019 C901010008
C900040020 C901010015
C900040021 C901010016
C900040022 C901010017
C900040023 C901010018
C900040024 C901010019
C900040025 C901010020
C900040026 C901010021
C900040027 C901010029
C900040028 C901010036
C900040029 C901010037
C900040030 C901010038
C900040031 C901010039
C900040032 C901010040
C900040033 C901010041
C900040034 C901010042
C900040035 C901010047
C900040036 C901010049
C900040037 C901010051
C900040038 C901010052
C900040039 C901010053
C900040040 C901010054
C900040041 C901010055
C900040042 C901010057
A-2

Appendix A Corresponding Relationship between Basic Measurement
Counters and General Measurement Counters
C900040043 C901010058
C900040044 C901010059
C900040045 C901010060
C900040046 C901010061
C900040047 C901020010
C900040048 C901020011
C900040049 C901020012
C900040050 C901020013
C900040051 C901020015
C900040052 C901020016
C900040053 C901020017
C900040054 C901020018
C900040055 C901020027
C900040056 C901020028
C900040057 C901020029
C900040058 C901020030
C900040059 C901020032
C900040060 C901020033
C900040061 C901020035
C900040062 C901020036
C900040063 C901020037
C900040064 C901020038
C900040065 C901020039
C900040066 C901020040
C900040067 C901020042
C900040068 C901020043
C900040069 C901020045
C900040070 C901020046
C900040071 C901020047
C900040072 C901020048
C900040073 C901020049
C900040074 C901020051
C900040075 C901020052
A-3

C900040076 C901020053
C900040077 C901020054
C900040078 C901160015
C900040079 C901160016
C900040080 C901030001
C900040081 C901030002
C900040082 C901030003
C900040083 C901030004
C900040084 C901030005
C900040085 C901030015
C900040086 C901030016
C900040087 C901030017
C900040088 C901030018
C900040089 C901030028
C900040090 C901030029
C900040091 C901030030
C900040092 C901030031
C900040093 C901030043
C900040094 C901030044
C900040095 C901030045
C900040096 C901030046
C900040097 C901030047
C900040098 C901030057
C900040099 C901030058
C900040100 C901030059
C900040101 C901030060
C900040102 C901030070
C900040103 C901030071
C900040104 C901030072
C900040105 C901030073
C900040106 C901030096
C900040107 C901030097
C900040108 C901170001
A-4

C900040109 C901170006
C900040110 C901170021
C900040111 C901170022
C900040112 C901170034
C900040113 C901170035
C900040114 C901180001
C900040115 C901180006
C900040116 C901180021
C900040117 C901180022
C900040118 C901180034
C900040119 C901180035
C900040120 C901190001
C900040121 C901190014
C900040122 C901190036
C900040123 C901190037
C900040124 C901190049
C900040125 C901190050
C900040126 C901190062
C900040127 C901190063
C900040128 C901200001
C900040129 C901200014
C900040130 C901200036
C900040131 C901200037
C900040132 C901200049
C900040133 C901200050
C900040134 C901200062
C900040135 C901200063
C900040136 C901040003
C900040137 C901040007
C900040138 C901040008
C900040139 C901040016
C900040140 C901040017
C900040141 C901000002
A-5

C900040142 C901000003
C900040143 C901000004
C900040144 C901000008
C900040145 C901000024
C900040146 C901000025
C900040147 C901000026
C900040148 C901000030
C900040149 C901000053
C900040150 C901000054
C900040151 C901000055
C900040152 C901000056
C900040153 C901000057
C900040154 C901000059
C900040155 C901000060
C900040156 C901000061
C900040157 C901000062
C900040158 C901000063
C900040159 C901010003
C900040160 C901010004
C900040161 C901010005
C900040162 C901010063
C900040163 C901010024
C900040164 C901010025
C900040165 C901010026
C900040166 C901010030
C900040167 C901040015
C900040168 C901010009
C900040169 C901000064
C900040170 C901000065
C900040171 C901010062
C900040172 C901030006
C900040173 C901030007
C900040174 C901030008
A-6

C900040175 C901030009
C900040176 C901030010
C900040177 C901030011
C900040178 C901030012
C900040179 C901030013
C900040180 C901030014
C900040181 C901030019
C900040182 C901030020
C900040183 C901030021
C900040184 C901030022
C900040185 C901030023
C900040186 C901030024
C900040187 C901030025
C900040188 C901030026
C900040189 C901030027
C900040190 C901030032
C900040191 C901030033
C900040192 C901030034
C900040193 C901030035
C900040194 C901030036
C900040195 C901030037
C900040196 C901030038
C900040197 C901030039
C900040198 C901030040
C900040199 C901030048
C900040200 C901030049
C900040201 C901030050
C900040202 C901030051
C900040203 C901030052
C900040204 C901030053
C900040205 C901030054
C900040206 C901030055
C900040207 C901030056
A-7

C900040208 C901030061
C900040209 C901030062
C900040210 C901030063
C900040211 C901030064
C900040212 C901030065
C900040213 C901030066
C900040214 C901030067
C900040215 C901030068
C900040216 C901030069
C900040217 C901030074
C900040218 C901030075
C900040219 C901030076
C900040220 C901030077
C900040221 C901030078
C900040222 C901030079
C900040223 C901030080
C900040224 C901030081
C900040225 C901030082
C900030001 C901460004
C900030002 C901460005
C900060001 C901110005
C900060002 C901110007
C900060003 C901250001
C900060004 C901250002
C900060005 C901250003
C900060006 C901250004
C900060007 C901250006
C900060008 C901250008
C900060009 C901250009
C900060010 C901260001
C900060011 C901260003
C900060012 C901260004
C900060013 C901260006
A-8

C900060014 C901260008
C900060015 C901260009
C900060016 C901260012
C900060017 C901260014
C900060018 C901260015
C900060019 C901260020
C900060020 C901260022
C900060021 C901260023
C900060022 C901260025
C900060023 C901260027
C900060024 C901260028
C900060025 C901260039
C900060026 C901260051
C900060027 C901260052
C900060028 C901260063
C900060029 C901260064
C900060030 C901260069
C900060031 C901260071
C900060032 C901260072
C900060033 C901260074
C900060034 C901260076
C900060035 C901260077
C900060036 C901260088
C900060037 C901260089
C900060038 C901270001
C900060039 C901270003
C900060040 C901270004
C900060041 C901270006
C900060042 C901270020
C900060043 C901270022
C900060044 C901270023
C900060045 C901270025
C900060046 C901270069
A-9

C900060047 C901270071
C900060048 C901270072
C900060049 C901270074
C900060050 C901150003
C900060051 C901150008
C900060052 C901070006
C900060053 C901070050
C900060054 C901070051
C900060055 C901070052
C900060056 C901120019
C900060057 C901120020
C900060058 C901120021
C900060059 C901120022
C900060060 C901120023
C900060061 C901120025
C900060062 C901120026
C900060063 C901120027
C900060064 C901120028
C900060065 C901120029
C900060066 C901120036
C900060067 C901120037
C900060068 C901120038
C900060069 C901120039
C900060070 C901120040
C900060071 C901120041
C900060072 C901120042
C900060073 C901120043
C900060074 C901120044
C900060075 C901120045
C900060076 C901120046
C900060077 C901120047
C900060078 C901120048
C900060079 C901120049
A-10

C900060080 C901120050
C900060081 C901120051
C900060082 C901060025
C900060083 C901060026
C900060084 C901060027
C900060085 C901060028
C900060086 C901060029
C900060087 C901060030
C900060088 C901060031
C900060089 C901060032
C900060090 C901060033
C900060091 C901060034
C900060092 C901060047
C900060093 C901090002
C900060094 C901090003
C900060095 C901090009
C900060096 C901090010
C900060097 C901090012
C900060098 C901090019
C900060099 C901090029
C900060100 C901090031
C900060101 C901090033
C900060102 C901090036
C900060103 C901090050
C900060104 C901090051
C900060105 C901090056
C900060106 C901090057
C900060107 C901090070
C900060108 C901090071
C900060109 C901090076
C900060110 C901090077
C900060111 C901090082
C900060112 C901090083
A-11

C900060113 C901090088
C900060114 C901090089
C900060115 C901090094
C900060116 C901090095
C900060117 C901090100
C900060118 C901090101
C900060119 C901090106
C900060120 C901090107
C900060121 C901080013
C900060122 C901080001
C900060123 C901080002
C900060124 C901080005
C900060125 C901080009
C900060126 C901080010
C900060127 C901080015
C900060128 C901080021
C900060129 C901080023
C900060130 C901080031
C900060131 C901110025
C900060132 C901150013
C900060133 C901080007
C900060134 C901080028
C900060135 C901270015
C900060136 C901110002
C900060137 C901110030
C900060138 C901260029
C900060139 C901260030
C900060140 C901260031
C900060141 C901260040
C900060142 C901260041
C900060143 C901260042
C900060144 C901260043
C900060145 C901260053
A-12

C900060146 C901260054
C900060147 C901260055
C900060148 C901260078
C900060149 C901260079
C900060150 C901260080
C900060151 C901070041
C900060152 C901280058
C900060153 C901280059
C900060154 C901280060
C900060155 C901080019
C900060156 C901260034
C900060157 C901260035
C900060158 C901260036
C900060159 C901260037
C900060160 C901260046
C900060161 C901260047
C900060162 C901260048
C900060163 C901260049
C900060164 C901260058
C900060165 C901260059
C900060166 C901260060
C900060167 C901260061
C900060168 C901260066
C900060169 C901260083
C900060170 C901260084
C900060171 C901260085
C900060172 C901260086
C900060173 C901260091
C900060174 C901270009
C900060175 C901270028
C900060176 C901270029
C900060177 C901270030
C900060178 C901270031
A-13

C900060179 C901270034
C900060180 C901270035
C900060181 C901270036
C900060182 C901270037
C900060183 C901270040
C900060184 C901270041
C900060185 C901270042
C900060186 C901270043
C900060187 C901270046
C900060188 C901270047
C900060189 C901270048
C900060190 C901270049
C900060191 C901270052
C900060192 C901270053
C900060193 C901270054
C900060194 C901270055
C900060195 C901270058
C900060196 C901270059
C900060197 C901270060
C900060198 C901270061
C900060199 C901270063
C900060200 C901270064
C900060201 C901270066
C900060202 C901270077
C900060203 C901270078
C900060204 C901270079
C900060205 C901270080
C900060206 C901270083
C900060207 C901270084
C900060208 C901270085
C900060209 C901270086
C900060210 C901270088
C900060211 C901270089
A-14

C900060212 C901270091
C900060213 C901090014
C900060214 C901090016
C900060215 C901090018
C900060216 C901090035
C900060217 C901080020
C900060218 C901080029
C900060219 C901070013
C900060220 C901070020
C900060221 C901070027
C900060222 C901070034
C900060223 C901070048
C900060224 C901060048
C900060225 C901060049
C900060226 C901060050
C900060227 C901060051
C900060228 C901060052
C900060229 C901060053
C900060230 C901060054
C900060231 C901060055
C900060232 C901060056
C900060233 C901060057
C900060234 C901060070
C900060235 C901270014
C900060236 C901110004
C900060237 C901090143
C900060238 C901090144
C900060239 C901090146
C900060240 C901090147
C900060241 C901250013
C900060242 C901250014
C900060243 C901250015
C900060244 C901070016
A-15

C900060245 C901070037
C900050001 C901410004
C900050002 C901410003
A-16

Glossary
3G
- The 3rd Generation Mobile Communications
AGCH
- Absolute Grant Channel
BSC
- Base Station Controller
BSS
- Base Station System
BTS
- Base Transceiver Station
BVC
- BSSGP Virtual Connection
CMP
- Calling Main Processor
CPU
- Central Processing Unit
CS
- Circuit Switched
DB
- DataBase
DSP
- Digital Signal Processor
DTAP
- Direct Transfer Application Part
FDD
- Frequency Division Duplex
GPRS
- General Packet Radio Service
GSM
- Global System for Mobile Communication
HR
- Half Rate
IMSI
- International Mobile Subscriber Identity
I
IP
- Internet Protocol
LAPD
- Link Access Procedure for D-channel
LLC
- Logic Link Control
MAC
- Medium Access Control
MO
- Mobile Originated
MOC
- Mobile Original Call
MS
- Mobile Station
MSC
- Mobile Switching Center
MT
- Mobile Terminated
MTC
- Mobile Terminated Call
NACC
- Network Assisted Cell Change
NSE
- Network Service Entity
NSVC
- Network Service Virtual Connection
OMC-R
- Operations& Maintenance Center-Radio
PACCH
- Packet Associated Control Channel
PCH
- Paging Channel
PCU
- Packet Control Unit
PDTCH
- Packet Data Traffic Channel
PDU
- Packet Data Unit
II
Glossary
PRI
- Primary Rate Interface
PS
- Packet Switched
PSI
- PCF Session Identity
PSK
- Phase Shift Keying
QoS
- Quality of Service
RLC
- Radio Link Control
RMM
- RF Management Module
RMM is the control centre of RFS. It works on a 1+1 standby mode.The clock
reference is also provided by the RMM.
RR
- Resource Record
SACCH
- Slow Associated Control Channel
SAPI
- Service Access Point Identifier
SDCCH
- Stand alone Dedicated Control Channel
SGSN
- Service GPRS Supporting Node
SM
- Short Message
SMM
- Session Manage Module
TCH
- Traffic Channel
TDD
- Time Division Duplex
TDM
- Time Division Multiplexing
TFI
- TDM Fiber Interface
III
TFO
- Tandem Free Operation
TRX
- Transmitter and Receiver
TS
- Time Slot
UL
- Uplink
eMLPP
- enhanced Multi-Level Precedence and Pre-emption
IV

SJ-20100414142254-015-ZXG10 iBSC (V6.20.21) Base Station Controller Performance Counter Reference PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20100414142254-015-ZXG10 iBSC (V6.20.21) Base Station Controller Performance Counter Reference PDF

Uploaded by

Copyright:

Available Formats

ZXG10 iBSC

Base Station Controller

Revison No. Revision Date Revision Reason

R1.2 20101115 Add related features for the counters

Revise the description of basic measurement counters and general

R1.0 20100430 First edition

Serial Number: SJ-20100414142254-015

Publishing Date: 20101115(R1.2)

Chapter 2 PS Basic Measurement (Cell) .................................................. 2-1

Chapter 3 CPU Load Measurement........................................................... 3-1

Chapter 4 CS Basic Measurement ............................................................ 4-1

Chapter 5 Configuration Management Infomation Basic

Chapter 6 Downlink Data TBF Measurement ........................................... 6-1

Chapter 7 Uplink Data TBF Measurement ................................................ 7-1

Chapter 8 Data Flow Measurement........................................................... 8-1

Chapter 9 Uplink-Downlink RLC Statistic Measurement ........................ 9-1

Chapter 10 PS Resource Used Statistic Measurement......................... 10-1

Chapter 11 RMM Assignment Measurement.......................................... 11-1

Chapter 12 Handover Cause Measurement ........................................... 12-1

Chapter 13 RMM Call Drop Measurement .............................................. 13-1

Chapter 14 Radio Resource Availability Measurement ........................ 14-1

Chapter 15 General Handover Measurement......................................... 15-1

Chapter 16 Adjacent Cell Handover Measurement ............................... 16-1

Chapter 17 Radio Access Measurement ................................................ 17-1

Chapter 18 Radio Measurement.............................................................. 18-1

Chapter 19 Sub Cell Statistics................................................................. 19-1

Chapter 20 MS TA Measurement............................................................. 20-1

Chapter 21 SAPI3 Measurement ............................................................. 21-1

Chapter 22 Uplink and Downlink PACCH Statistics .............................. 22-1

Chapter 23 Downlink GPRS Data TBF Statistics ................................... 23-1

Chapter 24 Downlink EGPRS Data TBF Statistics................................. 24-1

Chapter 25 Uplink GPRS Data TBF Statistics ........................................ 25-1

Chapter 26 Uplink EGPRS Data TBF Statistics...................................... 26-1

Chapter 27 BSSGP Flow Statistic ........................................................... 27-1

Chapter 28 Gb Interface Message Statistics.......................................... 28-1

Chapter 29 TRX Measurement................................................................. 29-1

Chapter 30 Timeslot Measurement ......................................................... 30-1

Chapter 31 SDCCH Measurement ........................................................... 31-1

Chapter 32 TCH/F Measurement ............................................................. 32-1

Chapter 33 TCH/H Measurement............................................................. 33-1

Chapter 34 Abis Interface Message Counter Measurement ................. 34-1

Chapter 36 NSVC Statistic Measurement............................................... 36-1

Chapter 37 NSE Statistic Measurement ................................................. 37-1

Chapter 38 BTS TRX Measurement ........................................................ 38-1

Chapter 39 NSVC on IPGB HOST Measurement.................................... 39-1

Chapter 40 GB Message on IPGB HOST Measurement ........................ 40-1

Chapter 41 NSE on IPGB HOST Measurement ...................................... 41-1

Chapter 42 BSSMAP Message Measurement ........................................ 42-1

Chapter 43 A-Interface Message Measurement..................................... 43-1

Chapter 44 Terrestrial Resource Availability Measurement ................. 44-1

Chapter 45 Ater Message Measurement ................................................ 45-1

Chapter 46 MTP2 Signal Link Measurement .......................................... 46-1

Chapter 47 CPU MEM Measurement....................................................... 47-1

Chapter 48 SCTP AS Measurement ........................................................ 48-1

Chapter 49 IP Port Performance Statistics ............................................ 49-1

Chapter 50 GTRUNK Resource Statistics .............................................. 50-1

Chapter 51 Other Process Statistics ...................................................... 51-1

Chapter 52 FR Carried Links Statistics .................................................. 52-1

Chapter 53 OMP PS Service Statistics ................................................... 53-1

Chapter 54 SNS on OMP Statistics ......................................................... 54-1

Chapter 55 IPGB StrongARM NSVC Statistics ...................................... 55-1

Chapter 56 IPGB StrongARM Gb Statistics ........................................... 56-1

Chapter 57 Queue Measurement............................................................. 57-1